SUMMARY: Accessing entPhysicalName on Sun Fire X4100 M2 service processors

I had received no answers, from anyone in the Sun Managers community,
but I did figure out a work around.

Since I was checking for information within the sunPlatEquipmentTable, I
found that the sunPlatEquipmentLocationName OID provides nearly the same
information as the entPhysicalName OID.  (Actually, in most
circumstances, more.)



Note: There are actually many complaints against Sun (Oracle) concerning
the use of these two OIDs/arrays/tables on systems with service
processors.  I've seen systems where the entPhysicalName OID is missing
indexes, and other systems where the values of the
sunPlatEquipmentLocationName OIDs are truncated.







From: Stier, Matthew
Sent: Wednesday, June 01, 2011 6:05 PM
To: 'sunmanagers@sunmanagers.org'
Subject: Accessing entPhysicalName on Sun Fire X4100 M2 service
processors



I have X4200's X4200-M2's and X4170's but I've inherited three
X4100-M2's and have a problem snmpwalk-ing 'entPhysicalName'. This OID
is used to map system sensors names to sensor table indexes.



I have no problem snmpwalk-ing this OID on the other systems; including
the X4200-M2.



I have no problem snmpwalk-ing the entPhysicalTable or entPhysicalEntry
OID's on any of the systems.



I have no problem snmpget-ing the individual entPhysicalName indexes.



I cannot snmpwalk any of entPhysicalName's siblings on these three
systems.



The systems ILOM/BIOS/Firmware is up to date.



The OID for entPhyscialName is:  1.3.6.1.2.1.47.1.1.1.1.7



Any hints?  Any history?



--

Matthew Stier
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers