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.
The map displays the service path (MPLS and IGP layers) for services using autobind. NSP supports the provisioning of various autobind tunnel configurations on services and the ability to determine the likely active tunnel path between service sites. Users can visualize the active service tunnel path as an overlay across the IGP and physical network topology. This support applies only to SROS NEs.
The selected LSP for the tunnel is determined by the SROS NE, tracking the state until the map data is refreshed.
The service map displays autobind tunnels for EVPN-EPIPE, EVPN-VPLS, and VPRN services.
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 feature requires the Service Oper Model to be deployed (included in the feature packs serviceAssurance, networkInfrastructureManagement-basicManagement, or serviceActivationAndConfiguration-intentBasedServiceFulfillment). The VSR-NRC+IP MPLS optimization visualizer feature pack is required to view IGP and Physical layers. Autobind must be enabled in the Service Oper Model.
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.
The MPLS layer does not display if the tunnels configured for a service do not have any associated LSPs.
Figure 2-3: Multi-layer map
Troubleshooting pathway
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 autobind
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 – TE |
|
RSVP – TE |
|
UDP BGP RIB – API SR – ISIS SR – OSPF SR – Policy MPLS Forwarding Policy |
Not supported. |