CPAM topology overview

Introduction to CPAM network topology

You can view the following network topology maps on the CPAM:

Note: See Chapter 5, MPLS topology management for information about MPLS topology maps.

Topology maps display real-time network topology information. The coordinates are synchronized for all of the routers in the network. If a router is also managed by the NFM-P, the NFM-P physical layer map (L1) coordinates may not be the same as the CPAM coordinates.

A map toolbar, which consists of a view selector and a collection of buttons, is used to manage the map views.

CPAM administrative domains
WARNING 

WARNING

Equipment Damage

The IGP administrative domain should generally be public IP address spaces, and not private IP address spaces. If two different IGP administrative domains have duplicate router IDs, for example, some functionality—such as the IP Path Monitor and Managed Routes—may not work correctly.

An administrative domain is a user-configured grouping that represents a logical routed network. The CPAM supports the following administrative domains:

An IGP administrative domain is uniquely identified by a domain number and name that are configured at creation. A CPAA which is configured with an IGP role must be assigned to an IGP administrative domain. Each CPAA can be assigned to only one IGP administrative domain. A BGP AS is identified by a BGP AS number, which should be identical to the network-configured BGP AS, a BGP AS name, and BGP AS type. Each BGP AS administrative domain is associated with only one IGP administrative domain. An IGP administrative domain can be associated with several BGP AS administrative domains. A CPAA which is configured with a BGP role must be assigned to each BGP AS administrative domain. Each CPAA can be assigned to only one BGP AS administrative domain.

See Chapter 10, BGP management for information about BGP network management.

Flat maps

A flat map is available for the CPAM by choosing Tools→Route Analysis→Flat Maps from the main menu. The map options available using a flat map are:

  • IGP Topology

  • OSPF Topology

  • OSPFv3 Topology

  • ISIS Topology

  • MPLS Topology

  • Multicast Topology

The flat map is used to view a large number of network objects and links. Double-click on a object in the flat map to display the properties of the object.

The flat map provides similar navigation and functionality to other topology maps, such as:

The flat map supports up to 1000 objects and 8 links per object. To narrow the range of objects that are displayed in a flat map, you can create, name, and save multiple filters by creating filter definition trees.

You can also click on the Display Filterable Flat Map button to quickly display a flat map of the current topology map view.

Filter definition tree

A filter definition tree allows you to apply one or more filters to a map view to narrow the range of objects that are displayed. Filter definition trees can be saved for future searches on similar objects. You can configure a filter definition tree only in flat maps. Once a filter is applied the name of the filter is displayed on the screen in the top-left, next to the filter icon. The filter definition tree form is launched by clicking on the Filter icon.

Map filtering

You can filter the IGP, OSPF, ISIS, and MPLS topology maps to reduce the number of objects that you are viewing. You can filter:

See To filter objects displayed on a topology map and To filter highlighted objects displayed on a topology map for information.

Suspended devices

When you need to exclude a device from CPAM management, but do not want to lose the CPAM information about the device, you can use a GUI or OSS client to suspend the management of the device. Once a device is suspended, SNMP communication fails. As a result, the following features cannot be used:

  • Auto LSP Ping OAM

  • Auto LSP Trace OAM

  • Auto P2MP LSP Ping OAM

  • Auto P2MP LSP Trace OAM

  • Auto IP Path ICMP Ping OAM

  • Auto IP Path ICMP Trace OAM

  • LSP Active Path with LSP Ping

  • P2MP Active Path with LSP Ping

  • SDP of MPLS LDP Service Tunnel

  • IP Path SPF with Ping

  • Path Resource Audit

  • OAM Multicast Tree

Both suspended devices and unreachable devices appear as purple on all CPAM topology maps. See “To manage, suspend, or unmanage a device” in the NSP NFM-P Classic Management User Guide for more information about suspended devices, including how to suspend device management.

CPAM span of control

For CPAM topology maps, the movement of objects on the map, and drag-and-drop management of groups and NEs, is disabled by default. To move and manage map objects, you must create a custom CPAM span of control, and select the required equipment group objects to add to that span. You must then add the custom CPAM span of control to the span of control profile for the required user group. There are no default CPAM spans. See the section on NFM-P user security in the NSP System Administrator Guide for more information about span of control.

The following CPAM topology map types support span of control:

CPAM topology maps support span of control configuration only for the Equipment Group object type. In the context of CPAM span of control, the Equipment Group span object type corresponds to the groups on CPAM topology maps. The system-defined span objects are the system-defined groups in each map; for example, the OSPF or ISIS root group object, or the Discovered Vertices group object. User-defined groups are also available as span objects.

CPAM span of control supports equipment groups from the CPAM application only. Equipment groups from the CPAM Simulator application are not supported for span of control.

CPAM span of control supports only the Edit Access span type. View Access, Blocked View, and Blocked Edit spans are not supported. Span of control settings for CPAM objects do not affect the visibility of map objects; users can always view all CPAM topology map objects.

Workflow to configure span of control for CPAM topology maps

You must have the required administrative scope of command permissions to perform span of control configurations.

 
1 

Create user-defined groups as required in CPAM topology maps; see To create user-defined groups on topology maps.

2 

Create a custom span of control for CPAM that includes the required CPAM map groups; see the section on creating a span of control in the NSP System Administrator Guide.

During span of control configuration, you must choose Equipment Group as the object type from the Add menu on the Contents tab. On the Select Equipment Group – Span form, you can select system-defined or user-defined CPAM groups.

The selected groups are explicitly added to the span. Child objects of a group have the same edit access as the explicitly added group.

When selecting groups to add to the span (on the Select Equipment Group – Span form), you can sort or filter for CPAM groups using the Application column. You must choose CPAM as the application type, not CPAM Simulator.

3 

Add the custom CPAM span to the required span of control profile for the user group; see the section on creating a span of control profile in the NSP System Administrator Guide.

When you add the custom CPAM span to the profile, you must choose Edit Access as the span type. The View Access, Blocked View, and Blocked Edit span types are not supported for CPAM.

4 

Ensure that the span of control profile with the CPAM span is assigned to the required user group; see the section on creating an NFM-P user group in the NSP System Administrator Guide.

© 2024 Nokia. Nokia Confidential Information

Use subject to agreed restrictions on disclosure and use.