Options - other than what you already mentioned - depend on the licensed vSphere edition and the old ESXi version you are running. If you are running vSphere Esentials Plus or better, and there's an option to upgrade one of the old hosts to ESXi 5.5, you will be able to live migrate the vCenter Server from the old to the new storage.
André
Not in front of a PC with access to test at the moment, but from memory you need to pass a vSwitch object to New-VirtualPortGroup. So something like this:
Connect-VIServer vc
$hostarray = @("host1","host2","host3")
foreach ($vmhost in $hostarray) {
$vSwitch = New-VirtualSwitch -VMHost $vmhost -Name vSwitch4
New-VirtualPortGroup -VirtualSwitch $vSwitch -Name vlan10 -VLanId 10 -Confirm:$false
New-VirtualPortGroup -VirtualSwitch $vSwitch -Name vlan15 -VLanId 15 -Confirm:$false
New-VirtualPortGroup -VirtualSwitch $vSwitch -Name vlan17 -VLanId 17 -Confirm:$false
New-VirtualPortGroup -VirtualSwitch $vSwitch -Name vlan20 -VLanId 20 -Confirm:$false
New-VirtualPortGroup -VirtualSwitch $vSwitch -Name vlan30 -VLanId 30 -Confirm:$false
New-VirtualPortGroup -VirtualSwitch $vSwitch -Name vlan40 -VLanId 40 -Confirm:$false
New-VirtualPortGroup -VirtualSwitch $vSwitch -Name vlan50 -VLanId 50 -Confirm:$false
New-VirtualPortGroup -VirtualSwitch $vSwitch -Name vlan60 -VLanId 60 -Confirm:$false
New-VirtualPortGroup -VirtualSwitch $vSwitch -Name vlan160 -VLanId 160 -Confirm:$false
New-VirtualPortGroup -VirtualSwitch $vSwitch -Name vlan162 -VLanId 162 -Confirm:$false
New-VirtualPortGroup -VirtualSwitch $vSwitch -Name vlan220 -VLanId 220 -Confirm:$false
}
No, the C# version is the Windows version of client that differs from vSphere Web Client.... if you don't have it installed, just open a web browser, point to IP address of your ESXi host and find a link to download the vSphere Client.
I have found on the exam it kind of goes both ways. I have found that moving a VDS or a VSS with the port groups on it sometimes go along, while other times it doesn't. The anchor system I built is different then the one on the exam, so you have to move them separately as the anchor system only cares about the connections in mine. On the Exam as much of a pain it is, if I have to move the VDS or VSS around I always move each piece individually if anything is out of line.
I'm currently working on dependency questions for the simulator, just been tied up with things and studying so I haven't had as much time to work on it, but will hopefully have it up in the next week or so.
Yeah the tool is just to get people in the right mind set and give them an idea of what the exam will actually function like. Especially for first time writers. The first time I wrote the DCD I killed so much time figuring out the mechanics of it. The simulator is there to help cut down on that time so you have more time to think about the questions 
This is a good report.
One question though:
When it checks for visible LUNs, is it checking for LUNs which are PMODE RDMs and claimed by the VM which is using them, or is it only checking the LUNs used by the ESXI hosts as datastores?
ok thanks!
Hi all I have created a datastore report with specification to SCSI LUN ID and NFS export path.
But I have no idea to query the NFS export path of a datastore. Can you help me in the following script?
$report = @()
$VMHost = Get-VMHost -Location
$cluster foreach($cluster in Get-Cluster){
(Get-Datastore -VMHost $VMHost | where {$_.Type -eq "VMFS"}) | %{
$info = "" | select DataCenter, Cluster, Name, Capacity, Provisioned, Available, DSType, State, LUNid, NFSPath
$info.Datacenter = $_.Datacenter
$info.Cluster = $cluster.Name
$info.Name = $_.Name
$info.Capacity = [math]::Round($_.capacityMB/1024,2)
$info.Provisioned = [math]::Round(($_.ExtensionData.Summary.Capacity - $_.ExtensionData.Summary.FreeSpace + $_.ExtensionData.Summary.Uncommitted)/1GB,2)
$info.Available = [math]::Round($info.Capacity - $info.Provisioned,2)
$info.DSType = $_.Type
$info.State = $_.State
$info.LUNid = Get-ScsiLun -Datastore $_
$info.NFSPath = "n/a"
$report += $info
}
(Get-Datastore -VMHost $VMHost | where {$_.Type -eq "NFS"}) | %{
$info = "" | select DataCenter, Cluster, Name, Capacity, Provisioned, Available, DSType, State, LUNid, NFSPath
$info.Datacenter = $_.Datacenter
$info.Cluster = $cluster.Name
$info.Name = $_.Name
$info.Capacity = [math]::Round($_.capacityMB/1024,2)
$info.Provisioned = [math]::Round(($_.ExtensionData.Summary.Capacity - $_.ExtensionData.Summary.FreeSpace + $_.ExtensionData.Summary.Uncommitted)/1GB,2)
$info.Available = [math]::Round($info.Capacity - $info.Provisioned,2)
$info.DSType = $_.Type
$info.State = $_.State
$info.LUNid = "n/a"
$info.NFSPath = "I don't know"
$report += $info
}
Thanks.
Yes, VMware tech support confirmed that they are supposed to appear in the tmp directory. There was nothing in my tmp directory (and no updatecache subdirectory).
Turns out that some updates are actually installs of new vibs. Maybe that's why it wasn't there at all.
You can use the RemoteHost and RemotePath attributes of the datastore to get the path in whatever format you wish.
e.g. $info.NFSPath = "$($_.RemoteHost):/$($_.RemotePath)"
Thanks Porto, I did find it connecting to the host. I'm trying to find documentation on how to use the cli for windows, but it doesn't seem to be loading in any of my browsers. It's one of those days I guess. Is there a command to revert to a snapshot for the vCenter server once I get connected to the ESXi host?
Hello parsnipz,
I am aware how it looks and I agree with you that my reply could have been worded better.
However there had been a trend in personal attacks going up recently and without now going into the blame game of what/who I just had to try and stop the personal remarks. Something had to be said before things derail and get completely off topic.
For whatever it matters we also have reached out to Woody already as well but off the board.
Please let us moderators worry about keeping the forums a welcome place and focus back to the issue at hand: Fusion 5 and Yosemite.
Thanks
--
Wil
Same way you do when connected on vCenter: Revert to a Snapshot in the vSphere Client
I think partly I know what I need to check, and partly I'd like to find out the things I might want to check, but haven't thought of.
Here are the things I would like to check:
-Consistent VLAN trunking
-Jumbo Frames - consistent configuration
-DNS resolution
-IP address conflicts
-Networks which should be isolated / non-routed are in fact isolated/non-routed
-Default gateway works Networks which should not be isolated / non-routed
-Potential latency issues on the physical network
-Potential routing issues on the physical network
-Potential issues with the number of hops on the physical network
I'l let a networking expert, who wrote the script or the software tool I am theorizing about, determine if some or all of these are significant vs. non-relevant.
The idea is, I go to put an ESXi server into production for a client, on whose site I have never set foot. Without needing permissions for logging in to their Physical Cisco Switches, I can do whatever checking I can do from my tool, and get as much of a feel for how things are on the physical network as I can get, to make me confident that the physical network is well oiled and tuned.
Ok, so how do I actually connect to the ESXI hosts using the windows cli? The documentation page on the vmware site isn't working.
Thanks sneddo, that's it!
I have tried it both ways. Resizing and straight P2V. Both produce the same result.
You are correct, we don't document any differences between vPostgres and an external database like SQL Server or Oracle as it was tested at the same scale limits as the others. I think the embedded vPostgres option is likely to be a popular choice, especially for new installations.
For customers upgrading an existing installation they will likely stick with what they already have as there isn't a VMware provided migration tool. Another reason why you may want to stick with an external database is because your organization may simply have more mature people, processes, and/or tools for handling those databases within their organization. For example if your backup tool has built in agents for protecting SQL Server (like VDPA for example) then you may want to stick with that and have consistency org wide.
Here's the KB article -> VMware KB: When configuring Network Mappings within VMware vCenter Site Recovery Manager using the vSphere Web Clien…
I'd recommending subscribing to that so you are notified when it is updated with details of the fix. The KB does list some workarounds that may or may not work in your environments. As this is a UI issue I also think configuring network mappings via the VCO workflows we added in 5.8 would also work as that uses the external APIs directly.
Does that fix survive a reboot? On my system the modules are built on the fly at boot time. So rebuilding them would have to be done after every reboot.
