The path control network map is a persisted and stateful presentation of the IGP topology layer which is associated to managed data layers for location positioning. The following options can be used to configure the path control network map:

Refresh

The Refresh button is located on the path control network map view. When clicked, the latest version of the map is fetched.

Search In Map

The Search In Map button is located on the path control network map view. When clicked, a window opens, in which you can provide device-specific information in order to locate a Link, Router, Prefix, or Region (when nodes are clustered by region) on the network map.

Export Network

Export Network can be selected from the contextual menu when the More button is clicked on the path control network map view. This option is used to export the current network as a .zip file so that it can be imported into the Simulation tool for testing purposes.

Save Map Changes

Save Map changes can be selected from the contextual menu when the More button is clicked on the path control network map view. When the NSP's Map Layouts and Groups views are part of the deployment, The path control function fetches and utilizes the node positions from that data, but users can reposition nodes on the network map as required. When Save Map changes is selected, the new node positions are persisted only in the path control network map.

Restore Common Map Layout

Restore Common Map Layout can be selected from the contextual menu when the More button is clicked on the path control network map view. When the NSP's Map Layouts and Groups views are part of the deployment, the path control function fetches and utilizes the node positions from that data, but users can reposition nodes on the network map as required. Users can then revert to the map configuration reflected in the NSP's Map Layouts and Groups views by selecting Restore Common Map Layout.

Rebuild

Rebuild can be selected from the contextual menu when the More button is clicked on the path control network map view and Map Actions is chosen. This options deletes, then rebuilds the network map to ensure synchronization with the IGP topology layer.

Auto Layout

Auto Layout can be selected from the contextual menu when the More button is clicked on the path control network map view and Map Actions is chosen. Runs layout algorithm on the server for the current map state and attempts to distribute the coordinates of the nodes' X and Y positions in an organic manner.

Clean-up References

Clean-up References can be selected from the contextual menu when the More button is clicked on the path control network map view and Map Actions is chosen. When network elements go down, NSP does not automatically delete topology data. This allows NBI configurations to be preserved. However, when Clean-up References is selected, any such objects found in the IGP topology layer will be deleted. This prevents the accumulation of stale data. The network map is simultaneously rebuilt to reflect these changes.

Toggle Hidden Devices

Toggle Hidden Devices can be selected from the contextual menu when the More button is clicked on the path control network map view and Map Actions is chosen. Depending on supported feature sets, some network elements may not appear on the network map. This option enables visibility of those entities.

The path control network map allows for the display of both IPv4 (MT 0) and IPv6 (MT 2) topologies. These topologies can be displayed simultaneously, or they can be isolated using the Topology drop-down menu on the network map.

To enable the advertisement and display of IPv6 topology information, the following CLI configurations are required:

A:99_999_ASBR_ISIS9>config>router>isis# info

....

ipv6-routing mt

no ipv6-multicast-routing

multi-topology

ipv6-unicast

exit

.....

A:99_999_ASBR_ISIS9>config>router>isis>segm-rtng# info

----------------------------------------------

multi-topology mt2

prefix-sid-range global

srlb "SRLB1"

no shutdown

Label stack compressed path must ensure consistent MT path usage, and when selecting the NSID to use, must be in the applicable MT for the path of the computed intended TE path. Currently, the NSP restricts TE computation to stay within a single MT topology value. This means only MT 0 or MT 2 can be traversed end-to-end. For label stack compression, the SID compression only supports the detection of a consistent MT value that is in use, and does not support paths with multiple MT values.

Anycast node SID prefix selection currently evaluates prefixes globally and cannot select for a specific MT value.

Note: BGP-LS discovery does not automatically identify the relationships between IPv4 and IPv6 addresses on the same interface. To discover these relationships, inventory synchronization with NFM-P or MDM-managed nodes is required, otherwise, bandwidth management may not function correctly.