Symptom

100G optics which use single lane [such as but not limited to QSFP-100G-LR-S and QSFP-100G-FR-S] show the correct output in the show interfaces transceiver detail output where they display just Lane 1 show interfaces Hu1/0/52 status Port Name Status Vlan Duplex Speed Type Hu1/0/52 connected 1 full 100G QSFP 100G FR-S ! show interfaces Hu1/0/52 transceiver detail ... Optical High Alarm High Warn Low Warn Low Alarm Transmit Power Threshold Threshold Threshold Threshold Port Lane (dBm) (dBm) (dBm) (dBm) (dBm) --------- ---- --------------- ---------- --------- --------- --------- Hu1/0/52 1 0.8 7.0 4.0 -2.0 -6.4 Optical High Alarm High Warn Low Warn Low Alarm Receive Power Threshold Threshold Threshold Threshold Port Lane (dBm) (dBm) (dBm) (dBm) (dBm) --------- ---- --------------- ---------- --------- --------- --------- Hu1/0/52 1 -7.6 7.5 4.5 -6.4 -10.4 However, when polled over SNMP, results for 4 lanes are presented: snmpwalk -v2c -c entPhysicalDescr ... ENTITY-MIB::entPhysicalDescr.1828 = STRING: QSFP 100GE FR-S ENTITY-MIB::entPhysicalDescr.1829 = STRING: Hu1/0/52 Module Temperature Sensor ENTITY-MIB::entPhysicalDescr.1830 = STRING: Hu1/0/52 Supply Voltage Sensor ENTITY-MIB::entPhysicalDescr.1831 = STRING: Hu1/0/52 Bias Current Sensor ENTITY-MIB::entPhysicalDescr.1832 = STRING: Hu1/0/52 Transmit Power Sensor ENTITY-MIB::entPhysicalDescr.1833 = STRING: Hu1/0/52 Receive Power Sensor ENTITY-MIB::entPhysicalDescr.1834 = STRING: Hu1/0/52 Tx Lane 1 Power Sensor ENTITY-MIB::entPhysicalDescr.1835 = STRING: Hu1/0/52 Tx Lane 2 Power Sensor ENTITY-MIB::entPhysicalDescr.1836 = STRING: Hu1/0/52 Tx Lane 3 Power Sensor ENTITY-MIB::entPhysicalDescr.1837 = STRING: Hu1/0/52 Tx Lane 4 Power Sensor ENTITY-MIB::entPhysicalDescr.1838 = STRING: Hu1/0/52 Rx Lane 1 Power Sensor ENTITY-MIB::entPhysicalDescr.1839 = STRING: Hu1/0/52 Rx Lane 2 Power Sensor ENTITY-MIB::entPhysicalDescr.1840 = STRING: Hu1/0/52 Rx Lane 3 Power Sensor ENTITY-MIB::entPhysicalDescr.1841 = STRING: Hu1/0/52 Rx Lane 4 Power Sensor snmpwalk -v2c -c entSensorValue ... CISCO-ENTITY-SENSOR-MIB::entSensorValue.1829 = INTEGER: 291 CISCO-ENTITY-SENSOR-MIB::entSensorValue.1830 = INTEGER: 32 CISCO-ENTITY-SENSOR-MIB::entSensorValue.1831 = INTEGER: 695 CISCO-ENTITY-SENSOR-MIB::entSensorValue.1832 = INTEGER: 8 CISCO-ENTITY-SENSOR-MIB::entSensorValue.1833 = INTEGER: -76 CISCO-ENTITY-SENSOR-MIB::entSensorValue.1834 = INTEGER: 8 CISCO-ENTITY-SENSOR-MIB::entSensorValue.1835 = INTEGER: -400 CISCO-ENTITY-SENSOR-MIB::entSensorValue.1836 = INTEGER: -400 CISCO-ENTITY-SENSOR-MIB::entSensorValue.1837 = INTEGER: -400 CISCO-ENTITY-SENSOR-MIB::entSensorValue.1838 = INTEGER: -76 CISCO-ENTITY-SENSOR-MIB::entSensorValue.1839 = INTEGER: -400 CISCO-ENTITY-SENSOR-MIB::entSensorValue.1840 = INTEGER: -400 CISCO-ENTITY-SENSOR-MIB::entSensorValue.1841 = INTEGER: -400

Conditions

single-lane 100G transceiver Cat9500 switch polling ENTITY-MIB via SNMP for Digital Optical Monitoring [DOM] values

Workaround

none practical other than silencing the alarms on NMS side

Further Problem Description