Cisco Bug: CSCup71112 - sam_getplan frr lsp npe when frr uses non-alu nodes
Dec 10, 2014
- Cisco MATE Collector
Known Affected Releases
Node dynamic bypass (link /node) LSP. 1) In multi-vendor environment: Problem : Calculating <ActualPathHop> when a path involves non ALU nodes ( which is not managed by SAM) is not possible. If a hop is to non ALU node than we will not be able to iterate and resolve the hop. Solution: Log an error saying path has non ALU node and such LSP will not have corresponding entries in <ActualPathHop> table. 2) As you know technically ISIS and OSPF can be enabled in the network ( node) and MPLS is protocol independent, what if a LSP path is taken via a node where it is on an interface running ISIS protocol and MC is run with OSPF protocol. Is it expected that <ActualPathHop> be populated ? Since as of now path resolution is only for IGP interfaces know to MC Solution: Log an error saying path has interface which is not part of protocol used by MC and such LSP will not have corresponding entries in <ActualPathHop> table. Symptom: <ActualPathHop> table will not have hop involving multi-vendor nodes Conditions: There is bypass LSP with hop having mult-vendor nodes.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases