Workflow for path and prefix monitoring

Stages


1	Determine the map type you want to view: maps that show the topology maps that show protocol-specific topologies
2	Enable NFM-P performance statistics collection for IP and MPLS interfaces, and for LSPs. Configure the MIB entry policy for the required statistics object type, or class; see the procedure “To configure polling for a MIB statistics class” in the NSP NFM-P Statistics Management Guide. Set the Administrative State parameter in the MIB entry policy to Up. For network interfaces, enable the Ip Interface Stats object type on the Network Interface properties form. The MIB entry name is vRtrIfStatsEntry. For MPLS interfaces, enable MPLS Interface Stats on the MPLS Interface properties form. The MIB entry name is vRtrMplsIfStatEntry. For LSP utilization, enable the MPLS LSP Egress Stats object type on the Dynamic LSP properties form for each LSP. The MIB entry name is vRtrMplsLspStatisticsEntry. Set the polling interval to less than one hour.
3	For LSP utilization history: on the Accounting tab of the Dynamic LSP properties form for each LSP, assign an accounting policy and set the Administrative State to Up. See the procedure “To create a Dynamic LSP” in the NSP NFM-P Classic Management User Guide.
4	Configure monitoring, as required. Monitor an IP network path. See To monitor an IP network path for more information. Create an IP path monitor between two routers on a topology map. See To create an IP path monitor between two routers on a topology map for more information Monitor a bidirectional IP network path. See To monitor a bidirectional IP network path for more information. Create a bidirectional IP path monitor from a unidirectional IP path monitor. See To create a bidirectional IP path monitor from a unidirectional IP path monitor for more information. Monitor an LSP. See To monitor a dynamic LSP for more information. Create an LSP path monitor from an NFM-P-managed dynamic LSP. See To create an LSP path monitor from a dynamic LSP for more information. Create LSP path monitors for multiple LSP paths. See To create LSP path monitors for multiple LSP paths for more information. Monitor a bidirectional LSP path. See To monitor a bidirectional LSP path for more information. Monitor a P2MP LSP. See To monitor a P2MP LSP for more information. Create a P2MP LSP path monitor from an NFM-P-managed P2MP LSP . See To create a P2MP LSP path monitor from a P2MP LSP for more information. Monitor an SDP tunnel. See To monitor an SDP tunnel for more information. Create path monitors for multiple service tunnels. See To create path monitors for multiple service tunnels for more information. Configure BGP monitored prefixes. See To configure BGP monitored prefixes for more information.
5	Create a size constraint policy to specify the maximum number of historical path records that the CPAM retains, if required. See To configure the size constraint limit for path monitor records for more information.
6	View path records and historical path records, as required View IP path records of all of the monitored paths. See To view IP path records for more information. View LSP path records of all of the monitored paths. See To view LSP path records for more information. View path records of all of the monitored 2SL paths. See To view S2L path records for more information. View the historical path records of a monitored LSP path binding. See To view historical path records of a monitored LSP path binding for more information. Delete historical path records, as required. See To delete historical events for more information.
7	View status change history of monitored prefixes, if required. See To view status change history of monitored prefixes for more information.
8	View the total cost of IP paths and IP path segments, if required. See To view the total cost of IP paths and IP path segments for more information.
9	Navigate to a dynamic LSP or a monitored path on a topology map, if required. See To navigate to a dynamic LSP on a topology map and To navigate to a monitored path on a topology map for more information.
10	Determine the cause event of an IP or LSP path record, as required. Alternatively, navigate from a cause event to the IP or LSP path record of the monitored path, or navigate to the cause event of a path record of GRE or MPLS service tunnels. Find the cause event of an IP or LSP path record. See To find the cause event of an IP or LSP path record for more information. Find the cause event of a path record of a service tunnel. See To find the cause event of a path record of a service tunnel for more information. Find the IP or LSP path monitor record associated with a cause event. See To find the IP or LSP path monitor record associated with a cause event for more information.
11	Sort records, as required. Sort IP path records by error code. See To sort IP path records by error code for more information. Sort LSP path records by error code. See To sort LSP path records by error code for more information. Sort LSP path records by last reroute cause. See To sort LSP path records by last reroute cause for more information.

Use subject to agreed restrictions on disclosure and use.