L3VPN/2/TNL_EVENT

Message

L3VPN/2/TNL_EVENT: The tunnel up/down event is occurred. (VpnIndex=[VpnIndex], NextHop=[NextHop], Ckey=[Ckey], TrapType=[TrapType])

In VS mode, this log is supported only by the admin VS.

Description

The tunnel used by VPN services went up or down.

Parameters

Parameter Name	Parameter Meaning
VpnIndex	Index of a VPN instance. The value is the same as the value of the VPN-Instance Name and ID field in the display ip vpn-instance verbose command output.
NextHop	Next-hop address on the public network.
Ckey	Ckey value, which can be used to obtain recursion tunnel information. The value is the same as the value of the IID field in the display ip vpn-instance tunnel-info command output.
TrapType	Alarm event type: 0x0001: The tunnel used by VPN services went up. 0x0002: The tunnel used by VPN services went down.

Possible Causes

Cause 1: The tunnel used by VPN services went up or down.

Cause 2: During the switchover of VPN services to a tunnel, the result of tunnel iteration changed from success (a tunnel is iterated) to failure (a tunnel fails to be iterated); or the opposite.

Procedure

1. Run the display ip vpn-instance verbose vpn-instance-name command to check if the tnl-policy field exists.

If the field exists, go to Step 2.
If the field does not exist, go to Step 7.

2. Run the display tunnel-policy tunnel-policy-name command to check the tunnel policy.

If a tunnel policy in select-sequence mode is used, run the display tunnel-info all command to check if there are eligible tunnels. If the mpls te reserved-for-binding command is used to specify a tunnel for VPN binding, this tunnel cannot be used in select-sequence mode.
If there are eligible tunnels, go to Step 8.
If there are not eligible tunnels, go to Step 3.
If a tunnel policy in tunnel binding mode is used, run the display interface tunnel command to check if the bound tunnel interface is up.
If the bound tunnel interface is up, go to Step 4.
If the bound tunnel interface is down, go to Step 6.

3. Based on the networking, configure a needed LSP, or change the VPN tunnel policy. Then, check if the system will still generate the message L3VPNBASE/2/TNL_EVENT: The tunnel up event is occurred.

If the system will generate the message, go to Step 9.
If the system will not generate the message, go to Step 8.

4. Enter the tunnel interface view, and run the display this command to check if the mpls te reserved-for-binding command has been configured on the tunnel interface.

If it has been configured, go to Step 8.
If it has not been configured, go to Step 5.

5. Enter the tunnel interface view, and run the mpls te reserved-for-binding command. Then, check if the system will generate the message L3VPNBASE/2/TNL_EVENT: The tunnel up event is occurred.

If the system will generate the message, go to Step 9.
If the system will not generate the message, go to Step 8.

6. Check the configurations on the TE tunnel interface, and rectify faults based on the TE-related alarms. Then, check if the system will generate the message L3VPNBASE/2/TNL_EVENT: The tunnel up event is occurred.

If the system will generate the message, go to Step 9.
If the system will not generate the message, go to Step 8.

7. Check LDP LSP configurations , and rectify faults based on the LSP-related alarms. Then, check if the system will generate the message L3VPNBASE/2/TNL_EVENT: The tunnel up event is occurred.

If the system will generate the message, go to Step 9.
If the system will not generate the message, go to Step 8.

8. Collect log information and configuration information, and then contact technical support personnel.

9. End.