Herschelle's Posts

Have you seen this document? Pg 11. http://www.google.com.au/url?sa=t&rct=j&q=%22HP+service+manager%22+vmware+vmotion&source=web&cd=1&ved=0CDgQFjAA&url=http%3A%2F%2Fwww.techport13.com%2Fpublications%2Fnewsletter%2Fdetails%2Fhp_man_SM9%252020ReferenceConfigurationsSizingGuide&ei=adhBT4aTGeLnmAXk1PXPBw&usg=AFQjCNEj1VDYeaE3Vo6iK_jk5Bugjo5dIQ Not a very helpful document and does not explain any technical details.

You could try DB_SERVER_TYPE=[Bundled|Custom] This is from Page 4 of vsp_41_vcserver_cmdline_install.pdf, though it might also equally apply here to VUM Custom is for a remote database and Bundled is what you are looking for. In the notes if you use Bundled also need to add FORMAT_DB=1 to the command line as well. Update: Just found this document:  http://www.vmware.com/files/pdf/techpaper/vsp_4_vum_cmdline_install.pdf These look like the options you require: VCI_DB_SERVER_TYPE=Bundled VCI_FORMAT_DB=1 Message was edited by: Herschelle

assuming $mycol (from the check partition alignment link I posted) has returned you a list. I have taken the first item in the collection as an example. #remove everything from the comma onwards. $vmhddnumber = ($mycol[0].Partition).Substring(0,(($mycol[0].Partition).IndexOf(",")) ) #now remove all non numeric characters leaving on the disk number $vmhddnumber = $vmhddnumber -replace( "[^0-9]", "" ) #Convert to an integer, else can not add one. $vmhddnumber = [int] $vmhddnumber #The disk number counts within Windows is zero based, however VMware Hard Disk is not. Therefore you need to add one. $vmhddnumber++ Now if (and this is a big if, and I haven't tested anything here) there is a direct relationship between the Disk number from the guest OS and the VM hard disk number then you might be able to do something with the $vmhddnumber like so: #Now search for the VM hard disk that matches that number [vSphere PowerCLI] G:\Tools\PowerShell\Scripts> Get-HardDisk (Get-vm -name $mycol[0].VMName) | ? { $_.Name -eq "Hard disk " + $vmhddnumber } CapacityKB Persistence Filename ---------- ----------- -------- 16777216 Persistent [MyESX1-local] myVM1/myVM1.vmdk so you can see in the file name the datastore. You will need to probably wrap all of this into another foreach loop to cycle through all the returned data and return it in a format you like. Hopefully this has been helpful. I am very interested to know if there is a direct relationship or if there is a another way to get that linkage. Let us know how you go.

You are correct, forgot that the api connections do show up in the connections list. I guess a part of my question is whether a vSphere Client connection put additional overhead on the vCenter server? This question really starts to become moot with the release of vCenter 4.1 which allows 100 connections. In our current 3.5 and 4.0 environments we are hitting the limits for connections constantly, and that is not including the third party monitoring applications and internally run PowerCLI script connections.

Have you tried using the Indentifier instead of the PathID? If you go to the wizard and get to the select Disk/LUN page there will be columns Name, Path ID, LUN, Capacity etc If click and drag the column divider between Name and Path ID to the right, this will reveal an Identifier column. For my SAN LUNs they look like this naa.60020e80050001000000763100003f03, so then I used this command. $vmhost = Get-VMHost -Name myesx $LunName = "test-lun-01" $LunPath = "naa.60020e80050001000000763100003f03" $BlockSize = 1 New-Datastore -Vmfs -VMHost $vmhost -Name $LunName -Path $LunPath -BlockSizeMB $BlockSize I do not have a Host I can play with to test if this also work on Local storage, however this might assist.

The script does appear to run the same for me, it's just that in vSphere the fields you are after are significantly longer. VirtualCenter2.5 Name : vmhba1:0:100 ScsiLunId : HostSystem-host-61257/vmhba1:0:100 LunPath : vmhba1:0:100 SanId : 101:102:117:104:100:123:101:121 State : Active Preferred : True ScsiCanonicalName : vmhba1:0:100 vCenter4.0 Name : fc.5001438000c43f8d:5001438000c43f8c-fc.50060e800476310d:50060e800476310d-naa.60060e80047631000000763100003f46 ScsiLunId : HostSystem-host-489/naa.60060e80047631000000763100003f46 LunPath : fc.5001438000c43f8d:5001438000c43f8c-fc.50060e800476310d:50060e800476310d-naa.60060e80047631000000763100003f46 SanId : 101:102:117:104:100:109:100:116 State : Active Preferred : True ScsiCanonicalName : naa.60060e80047631000000763100003f46 So unless you have a very wide screen you might have trouble get a nice list to display with any truncation.

Ok, I tried the same thing on a clean ESXi 4.0 U1 Build 208167 with the same result. I downloaded and installed vMA 4.0.0-161993 Ran the same comand as you did and received the same result. "No Host Found." Interestingly when I deliberately put in a wrong password, I get the following message: "Cannot complete login due to an incorrect user name or password." So it does seem to be contacting the server and authenticating, something past that point doesn't seem to work though. The one thing I will say is that these esx servers are currently using DHCP and does not have DNS entries. So I used an existing configured IP/DNS record, currently unused, for the server (don't ask) and the command works just fine. So this is what I found: These do not work: hostops.pl --target_host <ESX IP> --username root --password password --server <ESX IP> --operation exit_maintenance hostops.pl --target_host <ESX IP> --username root --password password --server <ESX FQDN> --operation exit_maintenance These work: hostops.pl --target_host <ESX FQDN> --username root --password password --server <ESX IP> --operation exit_maintenance hostops.pl --target_host <ESX FQDN> --username root --password password --server <ESX FQDN> --operation exit_maintenance Not being a perl expert I can not tell what \ where in the script, needs then FQDN or if it is a bug. Howerver I guess that is my answer for now. Thanks for your assistance William.

I applied the following two bundles to bring the Build version up: ESXi400-200912001.zip ESXi400-201002001.zip I'll see if I have a server without the bundles already installed and see if I get the same result.

Interesting I get the same thing in my environment VC: 20811 ESX: 4U1 219382 PCLI: 208462 Here is a another way to access some of the information, depending on what exactly you are after: Get-VM -name xpsoe | get-view | Select @{N="Name"; E={$_.Name}}, @{N="MemoryMB"; E={$_.Config.Hardware.MemoryMB}} Name MemoryMB ---- -------- XPSOE 256 Other items: .Config.Name .Config.Hardware.NumCPU .Config.Hardware.MemoryMB .Config.CpuAllocation.Reservation .Config.CpuAllocation.Limit .Config.CpuAllocation.Shares.Shares .Config.MemoryAllocation.Reservation .Config.MemoryAllocation.Limit .Config.MemoryAllocation.Shares.Shares HTH in the mean time Herschelle42

Here is what I wrote to do a similar thing, when changing all existing VMs that had the default e1000 nics. In my environment though all my VMs are connected to vNetwork Distributed Switches, but the process should be similar. # Description: Adds an vmxnet3 nic to a vm and connects it to the same virtual # port group (on a vNetwork Distributed Switch) as the first nic on the vm. # Author: Herschelle42 # Usage 1: Add-Additional-VMXNet3NIC.ps1 <VM as [object]> # Usage 2: Add-Additional-VMXNet3NIC.ps1 (Get-VM -Name "MyVMName") # Uasge 3: $vm = Get-VM -Name "MyVMName" # Add-Additional-VMXNet3NIC.ps1 $vm Process { #Firstly check that the parameter that has been passed is a VM object if ( $_ -isnot [http://VMware.VimAutomation.Client20.VirtualMachineImpl|http://VMware.VimAutomation.Client20.VirtualMachineImpl] ) { Write-Output "Invalid input recieved: A Virtual Machine object is expected." continue } # end if $vmview = Get-View -viewtype VirtualMachine -filter @{"Name" = $_.Name} Write-Output $_.Name #Get the vNetwork Port group the VM is currently attached to $dvPortGroup = $vmview.Network[0].Value #dvportgroup-191 #Get the Switch UUID of the current Network interface. foreach ($item in $vmview.Config.Hardware.Device) { if($item.Backing.Port.PortgroupKey -eq $dvPortGroup) { $SwitchUUID=$item.Backing.Port.SwitchUuid #Write-output "SwitchUUID: "$SwitchUUID #f3 40 20 50 15 c0 d1 8d-02 4d f8 b4 48 9b df 06 } # end if } # end foreach # Now add a new NIC of vmxnet3 to the same network. $spec = New-Object VMware.Vim.VirtualMachineConfigSpec $spec.deviceChange = New-Object VMware.Vim.VirtualDeviceConfigSpec[] (1) $spec.deviceChange[0] = New-Object VMware.Vim.VirtualDeviceConfigSpec $spec.deviceChange[0].operation = "add" $spec.deviceChange[0].device = New-Object VMware.Vim.VirtualVmxnet3 $spec.deviceChange[0].device.key = -100 $spec.deviceChange[0].device.backing = New-Object VMware.Vim.VirtualEthernetCardDistributedVirtualPortBackingInfo $spec.deviceChange[0].device.backing.port = New-Object VMware.Vim.DistributedVirtualSwitchPortConnection $spec.deviceChange[0].device.backing.port.switchUuid = $SwitchUUID $spec.deviceChange[0].device.backing.port.portgroupKey = $dvPortGroup $spec.deviceChange[0].device.connectable = New-Object VMware.Vim.VirtualDeviceConnectInfo $spec.deviceChange[0].device.connectable.startConnected = $true $spec.deviceChange[0].device.connectable.allowGuestControl = $true $spec.deviceChange[0].device.connectable.connected = $true $spec.deviceChange[0].device.controllerKey = 100 $spec.deviceChange[0].device.addressType = "generated" $spec.deviceChange[0].device.wakeOnLanEnabled = $true $_this = Get-View -Id $vmview.MoRef $_this.ReconfigVM_Task($spec) Write-Output "Script Finished" } # end process Something to note that this will not move any IP address configuration from the e1000 to the vmxnet3 nic, you will need to do this inside the Guest O/S. Another thing is that before you remove the old nic from the VM, ensure you have disabled and or uninstalled the e1000 nic from within the guest os. This is for Windows guests anyway, otherwise you will end up with devices in device manager. And if you do not removed any fixed IP address from the e1000 you will not be able to assign that same IP address to the vmxnet3 nic as it will already "be in use" according to Windows. Just a trap I fell into myself. So for my Windows VMs I basically did the following steps. 1. Ran my script to add a vmxnet3 nic 2. Open a Vi Client console window and within Windows change the old nic to dhcp 3. Set new nic to the fixed ip address 4. disable old nic 5. Open device manager, uninstall the old e1000 nic 6. Remove the old nic from the VM. Of course if your VMs do not have any fixed IP and only use DHCP you can skip some of the steps. Hope that helps. Herschelle42

I have the same question. I tried looking at the Get-ScsiLun CmdLet to return all the visible luns to the host and tried to see if there was a property like there is on the Get-Datastore for Type or a link to a datastore. None that I could find. Also tried seeing if I could link them some how by doing a comparison between the Get-ScsiLun back to the datastore instead like seeing if the datastore object had the scsilun information in it, again none that i could find. I do not know how to use the SDK properly to find out this type of information, so am stuck too.

I did a quick test and the colon : is fine. The other I notice is that you replaced the parameter value $vmhost with $esxhn in the Get-Datastore command. Get-DataStore -VMHost {color:red}$esxhn{color} | Where-Object... Now the $vmhost variable is an ESX Host object created when the Get-VMHost -Name command retreives the host with the supplied name, which is a string. So you have replaced the $vmhost object variable with the $esxhn ? variable. Try changing the $esxhn back to $vmhost, only for the Get-Datastore part, like so: Get-DataStore -VMHost {color:red}$vmhost{color} | Where-Object...