Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
DOM info may not be available on GUI and CLI even though DOM is enabled by policy. GUI: Fabric -> Incentory -> Pod 1 -> (Leaf) -> Interfaces -> Phsical Interfaces -> eth1/X -> DOM Stats CLI: show interface ethernet1/X transceiver detail leaf1# show interface ethenet1/1 transceiver detail Ethernet1/1 transceiver is present type is 10Gbase-SR name is CISCO-XXXXXXXXXXX part number is XXXXXXXXXXX revision is 1 serial number is XXXXXXXXXXX nominal bitrate is 10300 MBit/sec Link length supported for 50/125um OM2 fiber is 8 m Link length supported for 62.5/125um fiber is 2 m Link length supported for 50/125um OM3 fiber is 300 m cisco id is -- cisco extended id number is 4 DOM is Enabled DOM info not available <======================= Though GUI and CLI(show int transceiver) don't show DOM value , moquery shows DOM info like below. Not only CurrentStats , other all DOM info are also available with moquery. A-leaf_2-33_S020# moquery -c ethpm.DOMCurrentStats Total Objects shown: 11 # ethpm.DOMCurrentStats alert : none childAction : dn : sys/phys-[eth1/1]/phys/domstats/current hiAlarm : 10.000000 hiWarn : 8.500000 loAlarm : 2.600000 loWarn : 3.000000 modTs : never rn : current status : value : 6.248000 Though above output shows dn "sys/phys-[eth1/1]/phys/domstats/current" but there was no current or other DOM info directories under domstats directory of the port. A-leaf_2-33_S020# pwd /mit/sys/phys-[eth1--1]/phys/domstats A-leaf_2-33_S020# ls -l total 0 -r--r----- 1 admin admin 0 Mar 17 22:08 summary
all version 2.0 are affected this issue But version 2.1 and 2.2 aren't affected this issue
workaround1: query following MOs with using moquery , visore , REST API ethpm.DOMTempStats ethpm.DOMVoltStats ethpm.DOMCurrentStats ethpm.DOMTxPwrStats ethpm.DOMRxPwrStats workaround2: use following command instead of "show interface e1/X transceiver detail" modify eth1--25 to intended port leaf1# cat \/mit\/sys\/phys-\[eth1--25\]\/phys\/domstats\/{current,rxpower,temperature,txpower,voltage}\/summary | egrep '^#|^hi|^lo|^status|^value' # Digital Optical Monitor, Current details hiAlarm : 10.000000 hiWarn : 8.500000 loAlarm : 2.600000 loWarn : 3.000000 status : value : 5.522000 # Digital Optical Monitor, Rx Power details hiAlarm : 0.158490 hiWarn : 0.079430 loAlarm : 0.004070 loWarn : 0.010230 status : value : 0.059540 # Digital Optical Monitor, Temperature details hiAlarm : 75.000000 hiWarn : 70.000000 loAlarm : -4.992188 loWarn : 0.000000 status : value : 33.667969 # Digital Optical Monitor, Tx Power details hiAlarm : 0.147910 hiWarn : 0.074130 loAlarm : 0.007410 loWarn : 0.018620 status : value : 0.060430 # Digital Optical Monitor, Voltage details hiAlarm : 3.630000 hiWarn : 3.465000 loAlarm : 2.970000 loWarn : 3.135000 status : value : 3.346600 workaround3: disable/enable DOM policy recover the issue but the issue may happen again after several days
Fixed version of this is 2.3 but it is implementation of sanity check. The issue itself doesn't happen version 2.1 or later.