ASR920_segment_routing opaque llsa issues

faruk.zaimovic · ‎03-12-2021

Hello,

Does anybody have experience with segment routing and ME3400 device? The problem is below:

Issues with ME3400 (reload, stuck) devices after clearing OSPF process on ASR920.

This issue affected round 30 ME3400 devices in the IP/MPLS network.

Maybe problem was that ME3400 are in same area as all devices ASR9010_PE, ASR920_, ASR9006_PE.

If we change area 0 to area 1 (stub) on ME3400 devices, will we stop opaque LSA (SR LSA) to propagate in the area1?

Why did this messages are propagate throw network?

Is version of ASR920 reason why this issue happened ?

How can you explain this invalid LSA in the logging?

Mar 11 14:47:38.634: %OSPF-4-BADLSATYPE: Invalid lsa: Bad LSA type Type 10, Length 44, LSID 7.0.0.0 from 10.100.94.193, 10.100.155.166, Mar 11 14:47:41.966: %OSPF-5-ADJCHG: Process 8000, Nbr 10.103.238.202 on Vlan2612 from FULL to DOWN, Neighbor Down: Dead timer expired Mar 11 14:47:44.454: %OSPF-4-BADLSATYPE: Invalid lsa: Bad LSA type Type 10, Length 44, LSID 7.0.0.0 from 10.100.94.193, 10.100.108.233, Mar 11 14:47:50.862: %ALIGN-3-SPURIOUS: Spurious memory access made at 0x927E51C reading 0x1D Mar 11 14:47:50.862: %ALIGN-3-TRACE: -Traceback= 0x927E51C 0x926C078 0xAFBBA2C 0xAFB5CD0 0x0 0x0 0x0 0x0 Mar 11 14:47:50.862: %ALIGN-3-TRACE: -Traceback= 0x927E558 0x926C078 0xAFBBA2C 0xAFB5CD0 0x0 0x0 0x0 0x0 Mar 11 14:47:50.862: %ALIGN-3-TRACE: -Traceback= 0x927E62C 0x926C078 0xAFBBA2C 0xAFB5CD0 0x0 0x0 0x0 0x0

Giuseppe Larosa · ‎03-12-2021

Hello @faruk.zaimovic ,

>> Maybe problem was that ME3400 are in same area as all devices ASR9010_PE, ASR920_, ASR9006_PE.

Yes , the first step is to put the affected devices in a non backbone area this may help them.

About the log messages we can say that the affected device attempts to understand the received LSA type 10 it is not able to process it and this causes SW errors and tracebacks a clear sign of issues.

>> Invalid lsa: Bad LSA type Type 10, Length 44, LSID 7.0.0.0 from 10.100.94.193, 10.100.108.233, Mar 11 14:47:50.862: %ALIGN-3-SPURIOUS: Spurious memory access made at 0x927E51C reading 0x1D Mar 11 14:47:50.862: %ALIGN-3-TRACE: -Traceback= 0x927E51C 0x926C078 0xAFBBA2C 0xAFB5CD0

Are the ME3400 configured for traditional MPLS TE extensions on OSPF ? This might be the root cause of the issue they may be able to understand OSPF opaque LSA for MPLS TE butr not the new ones used by Segment Routing.

EDit:

see

https://tools.ietf.org/html/rfc5250

and extensions for Segment Routing

https://tools.ietf.org/html/rfc8665

Hope to help

Giuseppe

MHM Cisco World · ‎03-14-2021

...

faruk.zaimovic · ‎03-15-2021

Hello ,

Thank you for your help. ME3400 doesn't have MPLS TE enable. it is CE device. i think that we will try put in other area and hope that it will solve problem.