Symptom
Traceback is seen in logging from mpls_lsd about missing protocol information
RP/0/RSP0/CPU0:Mar 27 19:06:59.864 UTC: mpls_lsd[334]: %ROUTING-FIB-3-ASSERT : FIB internal inconsistency detected: upd msg decode 477 unexpected protocol 3 : pkg/bin/mpls_lsd : (PID=3113144) : -Traceback= ffa455c f96ed36 ffa4441 ffa44cb ff7190d ff72db5 ff7a23c ff7ac0f ff7ae33 425247d 42527f2 4210860 4211556 420009e c899b4f c897b78
RP/0/RSP0/CPU0:Mar 27 19:06:59.865 UTC: mpls_lsd[334]: %ROUTING-FIB-3-ASSERT_RL : FIB internal inconsistency detected: upd msg decode 366 missing protocol indication : pkg/bin/mpls_lsd : (PID=3113144) : -Traceback= ffa4514 f96ed36 ffa4456 ffa44cb ff715b1 ff7160a ff72db5 ff783b9 ff7a281 ff7ac0f ff7ae33 425247d 42527f2 4210860 4211556 420009e
RP/0/RSP0/CPU0:Mar 27 19:06:59.865 UTC: mpls_lsd[334]: %ROUTING-FIB-3-ASSERT : FIB internal inconsistency detected: upd msg encode 2876 ??protocol:3?? (ifh:0x6003840,10.12.1.2,0xe0000000,flags=0x400,pid=8:bpid=0) failed to find backup path with path-id 0 [0,??protocol:3??,{{ifh:0x6003840,10.12.1.2,0xe0000000,flags=0x400,pid=8:bpid=0}:{ifh:0x6002440,100.1.7.2,0xe0000000,pid=7:bpid=255}:{ifh:0x6002480,100.1.6.2,0xe0000000,pid= : pkg/bin/mpls_lsd : (PID=3113144) : -Traceback= ffa455c f96ed36 ffa4441 ffa44cb ff7a2b3 ff7ac0f ff7ae33 4252(TRUNCATED)
Conditions
Platform independent issue, and could potentially be seen since 05.02.00 Release.
This can be seen when LSD is sent an update with invalid Path Protection information.
The traceback is meant to display issues with incorrect backup path updates from protocols.
But in the case of pure cross-connect MPLS rewrites, the traceback is missing information on what Local Label is having the issues. This makes triaging very difficult
Further Problem Description
This issue is not about the fact a 'failed to find backup path' traceback is seen. That could truly be an separate issue.
The problem addressed here, are the preceding 'missing protocol information' which makes triaging the issue more difficult
