- Blue, 1500 points or more
Currently in RME 4.2 DDR does not report the serial number of the TenGig modules (XenPak) though the ENTITY-MIB is reporting these values correctly. I attached a show version along with a snmp-walk and the "Detailed Device Report" of a Cat6500.
According to the user guide of RME 4.2 there should be the UDI (which contains the serial number) for all components of a device:
From RME 4.2 User Guide:
The Detailed Device report also displays the Unique Device Identifier (UDI) for all components of a device. UDI is unique to each component of a device. It is a combination of Product Identifier (PID), Version Identifier (VID) and Serial Number (SN).
The ENTITY-MIB does handle the XenPak as a port as well as a FRU (Field Replacable Unit). The fact that it is handled as a FRU should classify it as a component with the potential of a serial number and thus a UDI.
ENTITY-MIB::entPhysicalDescr.4009 = STRING: 10Gbase-ER
ENTITY-MIB::entPhysicalContainedIn.4009 = INTEGER: 4008
ENTITY-MIB::entPhysicalClass.4009 = INTEGER: port(10)
ENTITY-MIB::entPhysicalName.4009 = STRING: Te6/1
ENTITY-MIB::entPhysicalIsFRU.4009 = INTEGER: true(1)
Instead the slot in which the XenPak is inserted has a UDI asigned to it. This slot is handeled as a "Container" but it is not classified as a FRU.
ENTITY-MIB::entPhysicalDescr.4008 = STRING: 10-Gigabit Port Container
ENTITY-MIB::entPhysicalContainedIn.4008 = INTEGER: 4000
ENTITY-MIB::entPhysicalClass.4008 = INTEGER: container(5)
ENTITY-MIB::entPhysicalName.4008 = STRING: 10-Gigabit Port Container 6/1
ENTITY-MIB::entPhysicalIsFRU.4008 = INTEGER: false(2)
With regard to the fact that serial number tracking is a very important issue in todays network management tasks and asset management this should quickly be changed and "Module Port interfaces" should be enhanced with a "SerialNumber" and "UniqueDeviceIdentifier" field!
According to the User Guide I would even count this as a bug because the documentation says it should be their... - or am I wrong with this assumption?