Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
When the NCS 5508 running 7.5.2 is a transit hop in a IP or labeled path, it does not produce an IP address in the trace output being run from another device. If a trace is run directly "to" the NCS, it works as expected, but if it is just a transit hop, no IP address is produced.
Both in the customer's network as well as the local CALO lab, the issue is seen running XR 7.5.2 on an NCS 5508 with the following hardware: NAME: "0/0", DESCR: "NCS 5700 18x400GE Line Card with TCAM" PID: NC57-18DD-SE RP/0/RP0/CPU0:513E.G.57-NCS-5508-1#sh version Tue Oct 11 00:21:00.038 UTC Cisco IOS XR Software, Version 7.5.2 Copyright (c) 2013-2022 by Cisco Systems, Inc. Build Information: Built By : XXX Built On : Tue Apr 26 18:00:43 PDT 2022 Built Host : iox-ucs-101 Workspace : /auto/srcarchive14/prod/7.5.2/ncs5500/ws Version : 7.5.2 Location : /opt/cisco/XR/packages/ Label : 7.5.2 RP/0/RP0/CPU0:513E.G.57-NCS-5508-1#show platform Tue Oct 11 00:20:40.600 UTC Node Type State Config state -------------------------------------------------------------------------------- 0/0/CPU0 NC57-18DD-SE IOS XR RUN NSHUT 0/0/NPU0 Slice UP 0/0/NPU1 Slice UP 0/1/CPU0 NC57-18DD-SE IOS XR RUN NSHUT 0/1/NPU0 Slice UP 0/1/NPU1 Slice UP 0/RP0/CPU0 NC55-RP-E(Active) IOS XR RUN NSHUT FROM CALO LAB RECREATING THE ISSUE (AS THE CUSTOMER IS USING ALSO: ASR1K --- NCS 5508 ----ASR 9K: ALL CONFIGURED FOR ISIS, WITH PHYSICAL AND LOOPBACK IN ISIS: FROM 1K: 513E.E.23-ASR1009X-2#sh ip route Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP a - application route + - replicated route, % - next hop override, p - overrides from PfR Gateway of last resort is not set 1.0.0.0/32 is subnetted, 1 subnets C 1.1.1.1 is directly connected, Loopback0 2.0.0.0/32 is subnetted, 1 subnets i L2 2.2.2.2 [115/20] via 62.115.125.42, 00:04:39, HundredGigE0/0/0 3.0.0.0/32 is subnetted, 1 subnets i L2 3.3.3.3 [115/30] via 62.115.125.42, 00:00:35, HundredGigE0/0/0 62.0.0.0/8 is variably subnetted, 3 subnets, 2 masks C 62.115.125.0/24 is directly connected, HundredGigE0/0/0 L 62.115.125.41/32 is directly connected, HundredGigE0/0/0 i L2 62.115.148.0/24 [115/20] via 62.115.125.42, 00:04:39, HundredGigE0/0/0 NCS INTERFACES: RP/0/RP0/CPU0:513E.G.57-NCS-5508-1#sh ip int br Tue Oct 11 00:16:03.766 UTC Interface IP-Address Status Protocol Vrf-Name Loopback0 2.2.2.2 Up Up default MgmtEth0/RP0/CPU0/0 10.201.172.193 Up Up default PTP0/RP0/CPU0/0 unassigned Shutdown Down default HundredGigE0/0/0/0 62.115.125.42 Up Up default HundredGigE0/1/0/5 62.115.148.90 Up Up default TRACE FROM 1K ACCROSS NCS TO 9K LOOPBACK: 513E.E.23-ASR1009X-2#traceroute 3.3.3.3 source 1.1.1.1 Type escape sequence to abort. Tracing the route to 3.3.3.3 VRF info: (vrf in name/id, vrf out name/id) 1 * * * <<<<<<<<<<<<<<<<<<<<<<<<<<< 2 62.115.148.91 7 msec * 3 msec TRACE FROM 1K DIRECTLY TO NCS LOOPBACK: 513E.E.23-ASR1009X-2#trace 2.2.2.2 source 1.1.1.1 Type escape sequence to abort. Tracing the route to 2.2.2.2 VRF info: (vrf in name/id, vrf out name/id) 1 62.115.125.42 15 msec * 2 msec 513E.E.23-ASR1009X-2# SAME FROM 9K: RP/0/RSP0/CPU0:513E.B.30-ASR-9006-V2-2#trace 1.1.1.1 source 3.3.3.3 Mon Oct 10 06:56:06.159 UTC Type escape sequence to abort. Tracing the route to 1.1.1.1 1 * * * <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 2 62.115.125.41 2 msec * 2 msec RP/0/RSP0/CPU0:513E.B.30-ASR-9006-V2-2#trace 2.2.2.2 source 3.3.3.3 Mon Oct 10 06:56:27.660 UTC Type escape sequence to abort. Tracing the route to 2.2.2.2 1 62.115.148.90 9 msec * 3 msec RP/0/RSP0/CPU0:513E.B.30-ASR-9006-V2-2# SO WHENEVER NCS IS TRANSIT HOP, TRACEROUTE OUTPUT IS OMITTED, WHEN PING DIRECTLY TO NCS TRACEROUTE IS SUCCESSFUL
No workarounds have been found.
This issue is not service impacting, but does cause the customer headaches with their clients, and seems to have had similar issues in multiple versions of the XR software for this platform. The issue was not difficult to reproduce in the lab.