LSP and Related Tunnel Events for LinkDown and LinkUp

Correlation of Interface Index and Tunnel Index

When there is correlation of the interface index and tunnel index, the following applies:

• Interface index and tunnel index information is collected from the network.

• Interface and tunnel details are updated in interface and tunnel events by using their index information.

Two separate tasks collect the interface index and tunnel index information by using SNMP polling. The collected information is then used to update the interface and tunnel events by correlating the index (Element Type) with the corresponding component (Element Name).

The correlation is accomplished by configuring the following two items in the SNMP Trap Editor:

• Map the interface index (Element Type) to Interface Name (Element Name).

• Map the tunnel index (Element Type) to LSP Name (Element Name).

Run the Use-Defined SNMP Collection task to collect the interface index and tunnel index information.

Mapping the Interface Index to Interface Name

Launch the SNMP Trap Editor from the Live Event Browser to configure the SNMP traps.

1. Select Fault > Live Event Browser.

   The Live Event Browser is displayed.

2. In the Live Event View pane, right-click the interface that you want to configure.

   The SNMP Trap Editor window is displayed.

3. Select the Trap Configuration tab and in Element type, select Interface from the drop-down list.

   You can specify the trap name, trap OID, severity, and a comment. For trap event types that used interface or tunnel indexes for correlating element names, the proper names will be updated. For example, original mplsTunnelDown event with tunnel index 12345 will be mapped to a tunnel name like Lsp12345. The jnxLdpSesDown trap with an interface index 123, will be mapped to ge-0/1/0.1.

   Select or clear the Trap enabled check box to control whether or not the SNMP trap server can process the trap. Figure 1 displays the Trap Configuration tab.

   Figure 1: SNMP Trap Editor Trap Configuration Tab

   

4. Select the Advanced Configuration tab and in both the Element Attribute column and Event Attribute column, click the plus sign (+) and add the attribute name. Figure 2 displays the Advanced Configuration tab.

   Figure 2: SNMP Trap Editor Advanced Configuration Tab

   

5. Select the Trap Attributes tab. The Trap Attributes tab contains a list of the various MIB Attribute OIDs associated with this trap and the corresponding MIB Attribute name. The OIDs used as the key to identify the trap with its associated network element are indicated in the Element Key Priority column with nonzero values starting with “1.”

   The Event Attribute column is used to map the value from the trap to the appropriate column of the Event Browser. In the case of the jnxLdpSesDown trap, the keyword “name” in the Event Attribute column refers to the interface name, since the element type configured on the Trap Configuration tab is the interface.

   Figure 3: SNMP Trap Editor Trap Attributes Tab

   

6. (Optional) Click Reset to automatically fix incorrect OIDs entered previously.

LSPs and Associated LSP Events

LinkDown and LinkUp events include the affected interface name that is associated with a link. If an interface becomes up or down, it impacts the associated link and LSPs. Using both endpoint IP addresses of the link, impacted LSPs are identified. A panel in the Live Event Browser shows all the impacted LSPs and the associated LSP events.

Displaying LSP Events During LinkDown

1. Select Fault > Live Event Browser.

   The Live Event Browser is displayed.

2. In the Live Event View pane, select the interface to check with the LinkDown type, and then right-click and select Show Impacted LSPs, as shown in Figure 4.

   Figure 4: Show Impacted LSPs

   

   The impacted LSPs for the event are displayed in the Impacted Tunnel Viewer window. Figure 4 displays the Impacted Tunnel Viewer.