Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Customer is polling OID "1.3.6.1.4.1.9.10.137.1.3.1.3" (MIB: ciscoBfdSessPerfEntry) and this is returning wrong uptime value. Please find the outputs below: BFD Uptime from CLI (which is reflecting correct value): RP/0/RSP0/CPU0:ASR-9010-C#show bfd session | in UP Mon Aug 24 19:28:14.896 UTC Hu0/1/0/3 10.135.13.210 0s(0s*0) 300ms(100ms*3) UP BE5043 10.135.13.210 n/a n/a UP RP/0/RSP0/CPU0:ASR-9010-C#show bfd session interface Hu0/1/0/3 detail Mon Aug 24 19:28:47.782 UTC I/f: HundredGigE0/1/0/3, Location: 0/1/CPU0 Dest: 10.135.13.210 Src: 10.135.13.209 State: UP for 3d:16h:27m:21s, number of times UP: 1 <<<<<<<<<<<<<<<<< Session type: PR/V4/SH/BM Received parameters: Version: 1, desired tx interval: 100 ms, required rx interval: 100 ms RP/0/RSP0/CPU0:ASR-9010-C#show bfd session interface BE5043 detail Mon Aug 24 19:29:11.557 UTC I/f: Bundle-Ether5043, Location: 0/RSP0/CPU0 Dest: 10.135.13.210 Src: 10.135.13.209 State: UP for 3d:16h:27m:47s, number of times UP: 1 <<<<<<<<<<<<<< Session type: PR/V4/SH/BI Session owner information: Desired Adjusted Client Interval Multiplier Interval Multiplier -------------------- --------------------- --------------------- 2. snmpwalk output for BFD uptime: ashisana@ASHISANA-M-N168 ~ % snmpwalk -v2c -c RJILTest 172.18.87.88 1.3.6.1.4.1.9.10.137.1.3.1.3 SNMPv2-SMI::enterprises.9.10.137.1.3.1.3.2147811330 = Timeticks: (1597978877) 184 days, 22:49:48.77 SNMPv2-SMI::enterprises.9.10.137.1.3.1.3.4294901780 = Timeticks: (1597978884) 184 days, 22:49:48.84 ashisana@ASHISANA-M-N168 ~ % snmpwalk -v2c -c RJILTest 172.18.87.88 1.3.6.1.4.1.9.10.137.1.3.1.3 SNMPv2-SMI::enterprises.9.10.137.1.3.1.3.2147811330 = Timeticks: (1597978877) 184 days, 22:49:48.77 .>> SNMPv2-SMI::enterprises.9.10.137.1.3.1.3.4294901780 = Timeticks: (1597978884) 184 days, 22:49:48.84
This is from BFD PI perspective and applies to all XR platforms with affected releases.
None
Customer is polling OID "1.3.6.1.4.1.9.10.137.1.3.1.3" (MIB: ciscoBfdSessPerfEntry) and this is returning wrong uptime value. Please find the outputs below: BFD Uptime from CLI (which is reflecting correct value): RP/0/RSP0/CPU0:ASR-9010-C#show bfd session | in UP Mon Aug 24 19:28:14.896 UTC Hu0/1/0/3 10.135.13.210 0s(0s*0) 300ms(100ms*3) UP BE5043 10.135.13.210 n/a n/a UP RP/0/RSP0/CPU0:ASR-9010-C#show bfd session interface Hu0/1/0/3 detail Mon Aug 24 19:28:47.782 UTC I/f: HundredGigE0/1/0/3, Location: 0/1/CPU0 Dest: 10.135.13.210 Src: 10.135.13.209 State: UP for 3d:16h:27m:21s, number of times UP: 1 <<<<<<<<<<<<<<<<< Session type: PR/V4/SH/BM Received parameters: Version: 1, desired tx interval: 100 ms, required rx interval: 100 ms RP/0/RSP0/CPU0:ASR-9010-C#show bfd session interface BE5043 detail Mon Aug 24 19:29:11.557 UTC I/f: Bundle-Ether5043, Location: 0/RSP0/CPU0 Dest: 10.135.13.210 Src: 10.135.13.209 State: UP for 3d:16h:27m:47s, number of times UP: 1 <<<<<<<<<<<<<< Session type: PR/V4/SH/BI Session owner information: Desired Adjusted Client Interval Multiplier Interval Multiplier -------------------- --------------------- --------------------- 2. snmpwalk output for BFD uptime: ashisana@ASHISANA-M-N168 ~ % snmpwalk -v2c -c RJILTest 172.18.87.88 1.3.6.1.4.1.9.10.137.1.3.1.3 SNMPv2-SMI::enterprises.9.10.137.1.3.1.3.2147811330 = Timeticks: (1597978877) 184 days, 22:49:48.77 SNMPv2-SMI::enterprises.9.10.137.1.3.1.3.4294901780 = Timeticks: (1597978884) 184 days, 22:49:48.84 ashisana@ASHISANA-M-N168 ~ % snmpwalk -v2c -c RJILTest 172.18.87.88 1.3.6.1.4.1.9.10.137.1.3.1.3 SNMPv2-SMI::enterprises.9.10.137.1.3.1.3.2147811330 = Timeticks: (1597978877) 184 days, 22:49:48.77 .>> SNMPv2-SMI::enterprises.9.10.137.1.3.1.3.4294901780 = Timeticks: (1597978884) 184 days, 22:49:48.84