Modeling of LSP paths

This enhancement addresses the correlation gaps that were identified when an LSP Interface is shut down, and the Adapter diagnosed both Interface Disabled and LSP Down as root causes. To make this diagnosis, the Adapter relied on dynamic MPLS cross-connect data to establish the relationship between an LSP and the Interfaces that this path traverses. That data disappeared when the LSP went down, making the relationship disappear. Thus, the Adapter could not use the correlation with the Interfaces during root-cause analysis.

The Adapter takes advantage of the fact that all LSP paths are statically provisioned. Using the hop information that is specified when LSP paths are provisioned, the Adapter will create the relationships between the LSP paths and the Interfaces that will be traversed. This applies to both strict and loose hops.

LSP paths may be distinguished from the other LSP class instances with the following display name convention: <Source Node> -> <Destination Node>/LSP-X-PATH-Y (X represents the LSPid of the associated LSP, Y represents the LSP path binding ID).