What is the multi-layer map?
Multi-layer map
The multi-layer map is a display option on the Service Troubleshooting map. It allows you to view services through a series of separate network layers.
Note: The MPLS, IGP, and Physical layers are sourced through either CPAM/CPAA or VSR/NRC (NRC-P), which must be configured in NSP in order for the map to display services on managed NEs. The IGP topology layer displays a persisted and stateful combination of both the ISIS and OSPF topologies.
The multi-layer map uses the SPF algorithm to calculate IGP paths. If Flex algorithms are being used to calculate IGP paths elsewhere in NSP, the service map may display differing results.
Troubleshooting workflow
Use the following Multi-layer Map features to troubleshoot map objects:
-
View map object details; see How do I view information about an object in the Service Troubleshooting map?.
Protocol support
The multi-layer map supports the following protocols and protocol-adjacent technologies: PCEP (if NSP PCE is deployed), RSVP, SR-TE, MPLS, IGP (OSPF/ISIS), and BGP (BGP-LS). See How does NSP enable path control? and (if NSP PCE is deployed) How does NSP function as a PCE? in the NSP Path Control and Simulation Guide for more information.
Tunnel support
The tables below list the different supported tunnel types in which an LSP path can be determined based on the IGP topology source (CPAM or VSR-NRC) to populate the IGP layer in the multi-layer map.
Table 2-1: Multi-layer map tunnel support for SDP
|
Tunnel type |
Support notes |
|
GRE |
CPAM/CPAA runs SPF protocol to get actual path of LSP recorded in NFM-P. Both endpoints need to be in the same admin domain. VSR-NRC runs NRC-P path calculation. Endpoints do not need to be in the same admin domain. |
|
MPLS – LDP |
CPAM/CPAA runs SPF protocol to get actual path of LSP recorded in NFM-P. Both endpoints need to be in the same admin domain. VSR-NRC runs NRC-P path calculation. Endpoints do not need to be in the same admin domain. |
|
MPLS – LSP |
CPAM/CPAA runs SPF protocol to get actual path of LSP recorded in NFM-P. Both endpoints need to be in the same admin domain. VSR-NRC returns PCEP related path discovered by NRC-P. If no PCEP related path is available, NRC-P runs path calculation to determine path. Endpoints do not need to be in the same admin domain. |
|
MPLS – SR-TE-LSP |
VSR-NRC returns PCEP related path discovered by NRC-P. If no PCEP related path is available, NRC-P runs path calculation to determine path. Endpoints do not need to be in the same admin domain. |
|
MPLS – SR-ISIS |
VSR-NRC runs NRC-P path calculation. Endpoints do not need to be in the same admin domain. |
|
MPLS – SR-OSPF |
VSR-NRC runs NRC-P path calculation. Endpoints do not need to be in the same admin domain. |
|
RSVP/TE (PCE) |
CPAM/CPAA runs SPF protocol to get actual path of LSP recorded in NFM-P. Both endpoints need to be in the same admin domain. VSR-NRC returns PCEP related path discovered by NRC-P. If no PCEP related path is available, NRC-P runs path calculation to determine path. Endpoints do not need to be in the same admin domain. |
|
L2TPv3 MPLS – BGP Tunnel MPLS – Class forwarding MPLS – Mixed LSP Mode Eth-GRE-Bridged Static |
Not supported. |
Table 2-2: Multi-layer map tunnel support for auto-bind
|
Tunnel type |
Support notes |
|
LDP |
CPAM/CPAA runs SPF protocol to get actual path of LSP recorded in NFM-P. Both endpoints need to be in the same admin domain. VSR-NRC runs NRC-P path calculation. Endpoints do not need to be in the same admin domain. |
|
SR – ISIS SR – OSPF UDP BGP RIB – API RSVP SR – Policy SR – TE MPLS Forwarding Policy |
Not supported. |