VMware

This Question is Not Answered

1 "correct" answer available (10 pts) 1 "helpful" answer available (6 pts)
4 Replies Last post: Sep 18, 2009 9:12 AM by dmitrif  

HostNumericSensorInfo collection - does not work! posted: Sep 18, 2009 9:25 AM

Click to view dmitrif's profile Enthusiast 71 posts since
May 13, 2008
Hi all,

What would you say is persistent (can be used as an unique key) in the HostNumericSensorInfo collection (at HostSystem.runtime.healthSystemRuntime.systemHealthInfo.numericSensorInfo) during a session?

Size of the collection? Indexes of sensors? Sensor names?

I have a serious doubts about the only property that comes to mind (HostNumericSensorInfo.name) as it looks like it's being concatenated from an actual sensor name and its status: "System Board 1 FAN MOD 4D RPM - Normal", "Power Supply 2: Running/Full Power-Enabled", "Disk Drive Bay 1 Cable SAS A 0: Config Error - Deassert" etc (a very strange way to name something if you ask me).

Thanks in advance.

Re: HostNumericSensorInfo collection persistence

2. Sep 17, 2009 7:30 PM in response to: dmitrif
Click to view tmilner's profile Enthusiast 131 posts since
Oct 19, 2005

Dmitri,

There is no good unique ID for host sensors... :-( The best field to use is the name (which is quite lengthy). But this gets complicated because the hardware vendors decided to "help" by often appending the sensor status to the end of the name. Thus, if the status changes, the name changes. The only alternative I can think of is to use CIM to get the raw name value. Pretty ugly.

Tom

Developer Social Media

Communities