Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Network Node Manager i Software10.30

Use > Monitor with the NNM iSPI for MPLS > View the iSPI for MPLS Incidents

View the NNM iSPI for MPLS Incidents

The NNM iSPI for MPLS generates the incidents if any fault or change is detected on the network. You can monitor your critical MPLS-enabled nodes and MPLS objects by checking the inventory views and incidents tab. In addition, all the MPLS incidents appear in the NNMi Incident management or Incident Browsing workspace.

To view the MPLS incidents, follow any one of the steps:

From the Left navigation panel, select the MPLS workspace and click <MPLS> view (for example, MPLS- > MPLS L3 VPN Inventory).
Select an L3 VPN and click (the Open icon).
Select an Incident from the incident tab and click (the Open icon) to view an incident of your interest.

From the workspace navigation pane, select the Incident Management or Incident Browsing workspace.
Select the view and incident of your interest. (For example, select All incidents view and sort the incidents by the column Family (MPLS)).

The NNM iSPI for MPLS generates the following types of incidents:

MPLS Incidents

You can view the following MPLS incidents from the NNMi console or MPLS inventory:

Incidents generated for the MPLS-enabled nodes and objects
Service Impact Incidents
Pairwise Incidents for the MPLS objects

Incidents Generated for MPLS-enabled Nodes and Objects

MPLS Incidents
Incident Name	Description
MplsVFIDown	This incident is generated when the VFI belonging to the specified VPLS goes down.
MplsSdpDown	This incident is generated when a SDP between the specified source node and destination ip address is down.
MplsSdpBindDown	This incident is generated when the SDPBind between the specified SDP and its service is down.
MplsTETunnelDown	This incident is generated when TE Tunnel between the source and destination of the selected node is down. When generated, this incident displays "TE Tunnel $TunnelName is Down between $TunnelSrcName and $TunnelDestName$RCA". In this case, $TunnelName is the name of the TE Tunnel and $RCA is the node and interface name where the TE Tunnel went down.
MplsTETunnelUp	This incident is generated when a TE Tunnel is up. This incident is a part of the MPLS Traffic Engineering family.
MplsTETunnelReroute	This incident is generated when TE Tunnel between the two end points is rerouted. When generated, this incident displays the "TE Tunnel $TunnelName is Rerouted $RCA" message. In this case, $TunnelName is the name of the TE Tunnel and $RCA is the node and interface name where the reroute occurred in the path.
MplsVRFDown	The VRF incident is generated when the status of the selected VRF is down. It belongs to the MPLS L3 VPN family. This incident includes the description if the VRF is a hub and the status of the Hub VRF is down. This incident is also generated for VRF Lite when the status of the selected VRF Lite is down. Although, in case of a VRF Lite down the corresponding message displayed for the incident mentions that a VRF Lite is down.
MplsVRFUp	The VRF incident is generated when the status of the selected VRF is up. It belongs to the MPLS L3 VPN family. This incident includes the description if the VRF is a hub and the status of the Hub VRF is up. This incident is also generated for VRF Lite when the status of the selected VRF Lite is up. Although, in case of a VRF Lite up the corresponding message displayed for the incident mentions that a VRF Lite is up.
MplsVRFWarning	The VRF incident is generated when the status of one of the PE interfaces but not all the interfaces associated with the VRF is Down.
MplsPseudoWireVCDown	The Pseudowire VC incident appears when the PseudoWire VC is Down. This incident belongs to the MPLS PseudoWire VC family.
LSPReRoute	Generated when an LSP is re-routed.
LSPCritical	Generated when an LSP is down.

The LSP service impact incidents pick up the custom attributes of the corresponding source and destination services. For more information, see Incident Form: Custom Attribute Tab in NNMi Online Help for Operators.

Service Impact Incidents

The NNM iSPI for MPLS lists the Service Impact incidents for the selected L3 VPNs or L2 VPNs. The service impact incidents do not change the status of the L3 VPNs or L2 VPNs. You can view the Service Impact incidents from the NNMi Workspaces-> Incident Browsing -> Service Impact incidents.

The root-cause incident generated by NNMi generates a service impact incident. This incident provides details of the affected L3 VPN or L2 VPN on the network. For example, an Interface Down incident can change the status of a CE node participating in an L3 VPN. This incident is useful to identify and troubleshoot the service.

For example, when the status of the Hub VRF is Down, a service impact incident MplsL3VPNCritical is generated. The correlation nature of this incident is Service Impact incident.

MPLS Service incidents
Incident Name	Description
MVRFCritical	Generated when the status of an MVRF is Critical. The status of the MVRF is Critical when the VRF is down or the MTI associated with the MVRF is down. This is a service impact incident.
MplsL3VPNCritical	Generated when the status of an L3 VPN is critical because the status of the hub VRF is critical. This is a service impact incident.
MplsL3VPNImpacted	Generated when a fault (NodeDown, InterfaceDown, Connection Down or VRF Lite Down) is detected on a CE node or a shadow router. This is a service impact incident.
MplsServiceImpacted	Generated when the LSP belonging to a service is down or re-routed.

MPLS Pairwise Incidents

You can view the following MPLS Pairwise incidents in the Incidents tab. For more information about Pairwise Incidents, see NNMi help, Incident Pairwise Configuration.

Pairwise MPLS Incidents
Name	Description
CiscoMplsVRFIfDownUpPair	Cancels a CiscoMPLSVRFDown incident with a CiscoMPLSVRFUp incident from the same node and interface.
JnxMplsTETunnelDownUpPair	Cancels a Juniper MPLS TE Tunnel down incident with a Juniper MPLS TE Tunnel up incident from the same node and TE Tunnel.
JnxMplsVpnIfDownUpPair	Cancels a down incident with an up incident from the Juniper- enabled interface participating to form an L2VPN and L3 VPN from the same node and VPN.

SNMP Traps

After NNMi discovered devices are configured, they generate SNMP traps that are received by NNMi. The NNM iSPI for MPLS supports the trap driven polling. When the traps are received, the State Poller starts polling the device, updates the status, and generates the incidents, if required. The SNMP traps are correlated under the MPLS incidents, if required. There is a one minute delay to correlate the root cause with the symptom.

For example, the CiscoMplsPseudoWireVCDown trap starts the poll on the associated Pseudowire VC. After polling, correlates the root cause with the trap and generates MplsPseudoWireVCDown incident.

SNMP Traps
Name	Family	Correlation Type	Description
CiscoMplsTETunnelUp	MPLS Traffic Engineering	-	Generated when the status of the configured TE Tunnel returns from Down to Up. This trap is generated by a Cisco node.
CiscoMplsTETunnelDown	MPLS Traffic Engineering	MplsTETunnelDown	Generated when the status of the configured tunnel is Down. This trap is generated by a Cisco node.
CiscoMplsTETunnelRerouted	MPLS Traffic Engineering	-	Generated when a tunnel originating from the router/device is rerouted because of some change in network or policy. This trap is generated by a Cisco node.
CiscoMplsVRFIfUp	MPLS Interface	-	Generated when the status of the VRF interface returns from Down to Up. This trap is generated by a Cisco node.
CiscoMplsVRFIfDown	MPLS Interface	MplsVRFDown	Generated when the status of the VRF interface is Down. This trap is generated by a Cisco node.
CiscoMplsL3VPNVrfUp	MPLS L3 VPN	-	Generated when the status of the VRF associated with an L3 VPN returns from Down to Up. This trap is generated by a Cisco node.
CiscoMplsL3VPNVrfDown	MPLS L3 VPN	-	Generated when the status of the VRF associated with an L3 VPN goes Down. This trap is generated by a Cisco node.
CiscoMplsPseudoWireVCUp	MPLS PseudoWire VC	-	Generated when the status of the configured PseudoWire VC returns from Down to Up. This trap is generated by a Cisco node.
CiscoMplsPseudoWireVCDown	MPLS PseudoWire VC	MplsPseudowireVCDown	Generated when the status of the configured PseudoWire VC is Down. This trap is generated by a Cisco node.
JnxMplsTETunnelUp	MPLS Traffic Engineering	-	Generated when the status of the configured tunnel is Up. This trap is generated by a Juniper node.
JnxMplsTETunnelDown	MPLS Traffic Engineering	MplsTETunnelDown	Generated when the status of the configured tunnel is Down. This trap is generated by a Juniper node.
JnxMplsVpnIfUp	MPLS Interface	-	Generated when the status of the VPN-enabled interface is Up. This trap is generated by a Juniper node.
JnxMplsVrfIfDown	MPLS Interface	MplsVRFDown	Generated when the status of the VRF interface is Down. This trap is generated by a Juniper node.
JnxMplsPseudoWireVCDown	MPLS PseudoWire VC	MplsPseudowireVCDown	Generated when the status of the configured PseudoWire VC is down.This trap is generated by a Juniper node.
JnxMplsPseudoWireVCUp	MPLS PseudoWire VC	-	Generated when the status of the configured PseudoWire VC is up. This trap is generated by a Juniper node.
AlcatelMplsLspDown	MPLS Traffic Engineering	MplsTETunnelDown	Generated when the status of the configured TE Tunnel is down. This trap is generated by an Alcatel node.
AlcatelMplsLspUp	MPLS Traffic Engineering	-	Generated when the status of the configured TE Tunnel returns from Down to Up. This trap is generated by an Alcatel node.
AlcatelMplsStateChange	MPLS Interface	-	Generated when the MPLS module state is changed. This trap is generated by an Alcatel node.
AlcatelMplsIfStateChange	MPLS Interface	-	Generated when the MPLS interface State is changed. This trap is generated by an Alcatel node.

The following SNMP traps are generated by the Cisco IOS-XR devices:

CiscoMplsL3VPNVrfUp
CiscoMplsL3VPNVrfDown
CiscoIOSXRMplsTETunnelUp
CiscoIOSXRMplsTETunnelDown
CiscoIOSXRMplsTETunnelRerouted

By default, the Cisco IOS-XR traps are disabled.

Send Help Center feedback