BSC 22-01N401 BSC 22-01N402 BSC 22-01-06 BSC 22-0201 BSC 22-2314B BSC 23-4404A BSC 23-14H BSC 24-14L BSC 24-01N36 BSC 24-01N362 BSC 24-01N362B BSC 24-08A BSC 24-09G BSC 25-48 BSC 25-4803 BSC 25-4803F BSC 25-4803T BSC 25-N0803A BSC 25-Z601A c _ b+ _ nc _ afc _ gnd _ htr _ abl _ nc. 154 - 132A (intel) 154 - 132C 6174V - 600H (LG 21') 6174Z - 6040C (LG 21') BSC 23 - N0107 (LG 14') c _ 40v _ 16,5 _ htr _ gnd _ b+ _ 180v _ gnd _ abl _ 40v 154 189 C 154 189 H 154 277 C BSC 22-2314 H CF 0801-3701 FCM 20B027 c _ b+ _ 180v _ 16v _ 24v _ htr _ gnd _ abl _ afc _ nc. Persamaan ic nc. 6174V-6002U (LG 21') BSC 26-N2121(N) (LG 21') c - 180v - b+ - gnd - 12v - 26v - nc - abl - ht - afc BSC 65 A (changhong) c _ b+ _ 190v _ gnd _ nc _ nc _ 14,5v _ abl _ htr _ afc. 154-064G (goldstar14') 154-177E untk (goldstar20') c - 180v - b+(92v) - boost up - 24v - 12v - gnd - abl - htr - afc.

Ceragon software reviews reviews. HP have just released to address the in the Feb2013 release of the ESXi management bundles. Thanks for the recommendation and the new bundles. It has resolved the warning on the HP smart array P410 controller. But the following error, when starting a VM (WinXP), which was set up and ran well before Upgrading to ESXi 5.1, still appears every time: vmWare knowledge base: Powering on a virtual machine after upgrading to ESXi 5.1 fails with the error: File [VMFS volume] VM-name/VM-name.vmdk was not found (2036572) Does anybody know more about this issue? The proposed workaround, converting all vmdk files to flat, is quite poor, has just blown up the size of my vmdk by factor 7.8, but not resolved the problem.

Appreciate other experiences with that problem, thank you for any help in advance. Hi, Thanks for the feedback. I assume you’ve checked the HCL to see that the HP 8200 Elite is not supported by VMware? I understand that it’s a lab environment, so this is probably not a big issue for you. Anyway, I suspect that your on-board SATA controller and disks are not recognised by the management agents in the same way that supported array controllers are, which is why you don’t see them on the hardware tabs.

HP Management Tools To obtain the maximum benefit and optimized operations from HP Insight Management WBEM Providers, the following versions of HP management tools are recommended. HP Software Component Windows Platform Linux Platform ProLiant Servers HP System Insight Manager (HP SIM) v5.2 N/A HP System Management Home Page (HP SMH) v2.1 N/A. Powershell Cmdlets for Hewlett Packard Insight Management WBEM providers - perhof/hp-wbem. And build software together. Powershell Cmdlets for Hewlett Packard Insight Management WBEM providers. Powershell Cmdlets for Hewlett Packard Insight Management WBEM providers Functions in this module.

Unfortunately I don’t have one of these hardware models to test, but would suggest that you post this question in the VMware communities just in case someone already has a solution for this setup. For a lab setup though, I’m not sure you’ll get much benefit in monitoring this local storage but post it in the communities anyway, you never know if someone has already got this working in their own lab. Hi Kyle, No, I haven’t installed this updated VIB from HP. I am still running the following version; Name Version Vendor Acceptance Level Install Date -------------------- ---------------------------------- --------------- ---------------- ------------ scsi-hpsa 5.0.0-17vmw.500.0.0.469512 VMware VMwareCertified 2012-03-26 Looking at the enhancements though, I’m not sure that I will gain anything from this update; Added new controller support for Smart Array P822 and Smart Array P721m. Enabled Rapid Parity initialization support. New feature will keep newly created volumes offline until parity initialization is completed.

Driver will periodocally check the device to see if it is ready, and bring it online when the process is complete. Driver will indicate if there are offline volumes in /proc info file and /var/log/vmkernel log files.

Feature will be enabled by Smart Array firmware update. I could be wrong, but as I read it, HP docs suggest that you should only install the Management Agents which are relevant to your monitoring solution, not both as above. The following suggests that installing the AMS pack after the Managament Bundle has been installed will solely use AMS?