DaHess_DNVGL's Posts

Hey Luke, this time the output looks much better. Thank you very much. VM      Name         SCSIid --      ----         ------ OSL2420 Hard disk 1  0:0 OSL2420 Hard disk 2  0:1 OSL24... See more...
Hey Luke, this time the output looks much better. Thank you very much. VM      Name         SCSIid --      ----         ------ OSL2420 Hard disk 1  0:0 OSL2420 Hard disk 2  0:1 OSL2420 Hard disk 14 0:2 OSL2420 Hard disk 18 0:3 OSL2420 Hard disk 19 0:4 OSL2420 Hard disk 20 0:5 OSL2420 Hard disk 21 0:6 OSL2420 Hard disk 15 1:0 OSL2420 Hard disk 16 1:1 OSL2420 Hard disk 17 1:2 OSL2420 Hard disk 3  1:3 OSL2420 Hard disk 4  1:4 OSL2420 Hard disk 5  1:5 OSL2420 Hard disk 22 1:6 OSL2420 Hard disk 23 1:8 OSL2420 Hard disk 24 1:9 OSL2420 Hard disk 25 1:10 OSL2420 Hard disk 6  2:0 OSL2420 Hard disk 7  2:1 OSL2420 Hard disk 8  2:2 OSL2420 Hard disk 9  2:3 OSL2420 Hard disk 10 2:4 OSL2420 Hard disk 11 2:5 OSL2420 Hard disk 12 3:0 OSL2420 Hard disk 13 3:1
Hi Luke, PS P:\> $PSVersionTable.PSVersion Major  Minor  Build  Revision -----  -----  -----  -------- 5      1      15063  726 PowerCLI Version ----------------    VMware PowerCLI... See more...
Hi Luke, PS P:\> $PSVersionTable.PSVersion Major  Minor  Build  Revision -----  -----  -----  -------- 5      1      15063  726 PowerCLI Version ----------------    VMware PowerCLI 6.5.1 build 5377412 --------------- Component Versions ---------------    VMware Cis Core PowerCLI Component 6.5 build 6983166    VMware VimAutomation Core PowerCLI Component 6.5 build 6234650
that didnt help either. The output leaves the SCSI-ID Column empty.: VM      Name         SCSIid --      ----         ------ OSL2420 Hard disk 1 OSL2420 Hard disk 2 OSL2420 Hard disk 14 ... See more...
that didnt help either. The output leaves the SCSI-ID Column empty.: VM      Name         SCSIid --      ----         ------ OSL2420 Hard disk 1 OSL2420 Hard disk 2 OSL2420 Hard disk 14 OSL2420 Hard disk 18 OSL2420 Hard disk 19 OSL2420 Hard disk 20 OSL2420 Hard disk 21 OSL2420 Hard disk 15 OSL2420 Hard disk 16 OSL2420 Hard disk 17 OSL2420 Hard disk 3 OSL2420 Hard disk 4 OSL2420 Hard disk 5 OSL2420 Hard disk 22 OSL2420 Hard disk 23 OSL2420 Hard disk 24 OSL2420 Hard disk 25 OSL2420 Hard disk 6 OSL2420 Hard disk 7 OSL2420 Hard disk 8 OSL2420 Hard disk 9 OSL2420 Hard disk 10 OSL2420 Hard disk 11 OSL2420 Hard disk 12 OSL2420 Hard disk 13
Hi Luke, thanks for your quick reply. That  comes close to what I was looking for, but it is still missing the Controller-ID. As an example, here the output for one of our Oracle RAC-Node VM... See more...
Hi Luke, thanks for your quick reply. That  comes close to what I was looking for, but it is still missing the Controller-ID. As an example, here the output for one of our Oracle RAC-Node VMs: PS P:\> Get-VM OSL2420 | Get-HardDisk | Select @{N='VM';E={$_.Parent.Name}},Name,@{N='SCSIid';E={$_.ExtensionData.UnitNumber}} VM      Name         SCSIid --      ----         ------ OSL2420 Hard disk 1       0 OSL2420 Hard disk 2       1 OSL2420 Hard disk 14      2 OSL2420 Hard disk 18      3 OSL2420 Hard disk 19      4 OSL2420 Hard disk 20      5 OSL2420 Hard disk 21      6 OSL2420 Hard disk 15      0 OSL2420 Hard disk 16      1 OSL2420 Hard disk 17      2 OSL2420 Hard disk 3       3 OSL2420 Hard disk 4       4 OSL2420 Hard disk 5       5 OSL2420 Hard disk 22      6 OSL2420 Hard disk 23      8 OSL2420 Hard disk 24      9 OSL2420 Hard disk 25     10 OSL2420 Hard disk 6       0 OSL2420 Hard disk 7       1 OSL2420 Hard disk 8       2 OSL2420 Hard disk 9       3 OSL2420 Hard disk 10      4 OSL2420 Hard disk 11      5 OSL2420 Hard disk 12      0 OSL2420 Hard disk 13      1 The vital piece of information I am missing in the output is the complete SCSI-ID that shows the controller ID followed by the Disk-ID in the same form as it is shown in the VM-Settings Dialog in the vSphere-Client. The Disk-ID on its own is useless if you use more than one SCSI-Controller. Is there any chance to get that full SCSI-ID displayed?
Hi, Is there an easy way to get the SCSI-ID of a VMs Virtual Disks displayed in a Get-VM | Get-Harddisk output? So far I could not find a way to retrieve the SCSI-IDs for the Virtual Disks ... See more...
Hi, Is there an easy way to get the SCSI-ID of a VMs Virtual Disks displayed in a Get-VM | Get-Harddisk output? So far I could not find a way to retrieve the SCSI-IDs for the Virtual Disks in the same output as "Get-HardDisk". It is simply not available, but it my opinion it should be there out of the box. I managed to get the SCSI-IDs of the Virtual Disks by importing this function and then run the command Get-VM <MyVM>  | Get-VMDisk, but I don't like the output really and I would rather like to have an Object "SCSI-ID" in the "Get-Harddisk" cmdlet output.
will this script still work in PowerCLI 6.5.2? We are still on vSphere 5.5 and are unable to add a new vDisk with the MultiWriter Flag while the RAC-Node-VM is running. So that script would be ... See more...
will this script still work in PowerCLI 6.5.2? We are still on vSphere 5.5 and are unable to add a new vDisk with the MultiWriter Flag while the RAC-Node-VM is running. So that script would be our only chance to achieve that without having to shut down both RAC Node-VMs. The other problem we are facing is that we are hitting the maximum allowed number of vDisks per virtual SCSI Controller (15 per Controller) so the only remaining option would be extending the existing disks which will also not work without downtime. That is why we are currently testing RAC Node VMs with RDM Disks to overcome those operational challenges. This feels to me like going two steps back and one forward and as the VMware and Storage Administrator don't like the added complexity when using RDMs over shared VMDKs. I guess our Oracle DBAS need to re-think their Disk-Design, especially when those VMs will be running on an All-Flash Array in the near future, so having a high number of small 10 to 15 GB Disks doesn't make much sense anymore, right?
Why don't you just this simple one liner and be done with it? Get-VMHostHardware The default output will give you the Hostname, Manufacturer, Model, Serial Number, etc and you can tweak it ... See more...
Why don't you just this simple one liner and be done with it? Get-VMHostHardware The default output will give you the Hostname, Manufacturer, Model, Serial Number, etc and you can tweak it to your needs. You got to be at least on PowerCLI 6.0 R2 I for this to work. Audit and Manage ESXi Hosts with PowerCLI - VMware PowerCLI Blog - VMware Blogs I personally run the PowerCLI in the latest version 6.5 Release 1 and it works like a charme. Just type in "Get-Help Get-VMHostHardware" to get some basic explanation and command examples, or just go directly to the online-help: Get-VMHostHardware - PowerCLI VMware.VimAutomation.Core Help Reference
all those referenced VMware KB Articles lead into en empty page! - The requested page may have been moved or deleted - You may have used an outdated or broken link - You may have typed the a... See more...
all those referenced VMware KB Articles lead into en empty page! - The requested page may have been moved or deleted - You may have used an outdated or broken link - You may have typed the address (URL) incorrectly Please use the search box to find alternative solutions. When you search for the topic, or the KB Number you will find nothing! Have they been removed, or changed? This is really frustrating.
Hi, I have experienced the exact same problem when trying to remediate one of my HP DL380p Gen 8 Rackmount Hosts. VMware Update Manager was throwing the following error in the vSphere Cient: ... See more...
Hi, I have experienced the exact same problem when trying to remediate one of my HP DL380p Gen 8 Rackmount Hosts. VMware Update Manager was throwing the following error in the vSphere Cient: The host returns esxupdate error code:15. The package manager transaction is not successful. Check the Update Manager log files and esxupdate log files for more details. When I looked at the esxupdate.log on the Host I could see the following lines: 2015-09-22T15:15:15Z esxupdate: HostImage: DEBUG: Live image has been updated but /altbootbank image has not.  This means a reboot is not safe. 2015-09-22T15:15:15Z esxupdate: imageprofile: INFO: Adding VIB VMware_locker_tools-light_5.0.0-3.68.2509828 to ImageProfile (Updated) HP-ESXi-5.0.2-standard-iso 2015-09-22T15:15:15Z esxupdate: HostImage: DEBUG: Live image has been updated but /altbootbank image has not.  This means a reboot is not safe. The Funny thing is that it has worked flawlessly on the second Host in the Cluster which is the exact same server model. I tried with to fix this with an Update Manager Expert in the VMware Support Organisation, but there was no way to fix it. It seems that the whole Image Profile on the Host has disappeared! you can see this by running the command "df -h" and look at the fist vFat Partition in the list and compare this with your other Hosts: Filesystem    Size             Used      Available        Use%       Mounted on vfat               249.7M         1.5M        248.2M             1%       /vmfs/volumes/08f4f5e0-5b7b00c2-8a0f-0504b88f0c3c vfat               249.7M     169.3M          80.4M           68%       /vmfs/volumes/5d59c6eb-b0cee482-c196-37c9b0d08443 vfat               285.8M     195.9M          89.9M           69%       /vmfs/volumes/51137f0c-c41939f3-2648-ac162d727eb5 It is basically empty! When I run a "esxcli software profile get" I get the following output: [Exception] No host image profile defined Please refer to the log file for more details. When I run a "esxcli software vib list" I get only the VMware-Tools-Light vib displayed: Name         Version             Vendor  Acceptance Level  Install Date -----------  ------------------  ------  ----------------  ------------ tools-light  5.0.0-3.68.2509828  VMware  VMwareCertified   2015-08-18 Today I tried an Upgrade using the látest HP Custom Image for ESXi 5.0 Update 3 "VMware-ESXi-5.0.0-Update3-1918656-HP-500.9.3.20.3-Jun2015.iso2" It furst detects the local SD-Card and after a scan detects that the Host is upgradable and offeres the "Upgrade" Option. When I select "upgrade" and press Enter to continue I get the "Confirm Upgrade" Screen displayed and I can stat the upgrade with "F11". When I do that the process starts, but stops at 24 percent with a cryptical error code and the message: AttributeError: ‚NoneType‘ object has no attribute ‚AddVibs‘   VMware Support has no solution for this problem. Looks like i will have to re install the Host from scratch.
I have experienced the exact same problem yesterday when trying to remediate one of my HP DL380p Gen 8 Rackmount Hosts. VMware Update Manager was throwing the following error in the vSphere Cien... See more...
I have experienced the exact same problem yesterday when trying to remediate one of my HP DL380p Gen 8 Rackmount Hosts. VMware Update Manager was throwing the following error in the vSphere Cient: The host returns esxupdate error code:15. The package manager transaction is not successful. Check the Update Manager log files and esxupdate log files for more details. When I looked at the esxupdate.log on the Host I could see the following lines: 2015-09-22T15:15:15Z esxupdate: HostImage: DEBUG: Live image has been updated but /altbootbank image has not.  This means a reboot is not safe. 2015-09-22T15:15:15Z esxupdate: imageprofile: INFO: Adding VIB VMware_locker_tools-light_5.0.0-3.68.2509828 to ImageProfile (Updated) HP-ESXi-5.0.2-standard-iso 2015-09-22T15:15:15Z esxupdate: HostImage: DEBUG: Live image has been updated but /altbootbank image has not.  This means a reboot is not safe. The Funny thing is that it has worked flawlessly on the second Host in the Cluster which is the exact same server model. I tried with to fix this with an Update Manager Expert in the VMware Support Organisation, but there was no way to fix it. It seems that the whole Image Profile on the Host has disappeared! you can see this by running the command "df -h" and look at the fist vFat Partition in the list and compare this with your other Hosts: Filesystem    Size             Used      Available        Use%       Mounted on vfat               249.7M         1.5M        248.2M             1%       /vmfs/volumes/08f4f5e0-5b7b00c2-8a0f-0504b88f0c3c vfat               249.7M     169.3M          80.4M           68%       /vmfs/volumes/5d59c6eb-b0cee482-c196-37c9b0d08443 vfat               285.8M     195.9M          89.9M           69%       /vmfs/volumes/51137f0c-c41939f3-2648-ac162d727eb5 It is basically empty! When I run a "esxcli software profile get" I get the following output: [Exception] No host image profile defined Please refer to the log file for more details. When I run a "esxcli software vib list" I get only the VMware-Tools-Light vib displayed: Name         Version             Vendor  Acceptance Level  Install Date -----------  ------------------  ------  ----------------  ------------ tools-light  5.0.0-3.68.2509828  VMware  VMwareCertified   2015-08-18 Seeing that User "kri-2" has the exact same problem that happen to emerge on the same type of server-model,  an HP DL380 Rackmount Host, it makes me think this is a problem with this particular HP-Server-Model. BTW: I updated a bunch of HP BL490c G7 Blades using the exact same Update Manager Baseline applying the exact same Patches and it worked on all of them.