BRASL2TP_1.3.6.1.4.1.2011.5.25.40.3.2.2.0.1 hwL2tpTunnelUpOrDown
Trap Buffer Description
The status of L2TP tunnel changed (LocalTunnelID=[LocalTunnelID], TunnelRemoteName=[TunnelRemoteName],PeerIPAddress=[PeerIPAddress],TunnelStatus=[TunnelStatus],TunnelDownReason=[TunnelDownReason],RemoteTunnelID=[RemoteTunnelID],SessionCount=[SessionCount]).
The status of L2TP tunnel changed.
In VS mode, this trap is supported only by the admin VS.
Trap Attributes
| Trap Attribute | Description |
|---|---|
Alarm or Event |
Event |
Trap Severity |
Warning |
Mnemonic Code |
hwL2tpTunnelUpOrDown |
Trap OID |
1.3.6.1.4.1.2011.5.25.40.3.2.2.0.1 |
MIB |
HUAWEI-BRAS-L2TP-MIB |
Alarm ID |
This is an event trap and does not involve alarm ID. |
Alarm Name |
This is an event trap and does not involve alarm name. |
Alarm Type |
This is an event trap and does not involve alarm type. |
Raise or Clear |
This is an event trap and does not involve alarm generation or clearance. |
Match trap |
- |
Trap Buffer Parameters
| Parameter | Description |
|---|---|
LocalTunnelID |
Local tunnel ID. |
TunnelRemoteName |
Remote tunnel name. |
PeerIPAddress |
IP address of the peer. |
TunnelStatus |
Status of a tunnel. |
TunnelDownReason |
Reason for a tunnel to go Down. |
RemoteTunnelID |
Remote tunnel ID. |
SessionCount |
Number of sessions of a tunnel. |
VB Parameters
| VB OID | VB Name | VB Index |
|---|---|---|
1.3.6.1.4.1.2011.5.25.40.3.2.1.1 |
hwL2tpTunnelID |
- |
1.3.6.1.4.1.2011.5.25.40.3.2.1.2 |
hwL2tpPeerName |
- |
1.3.6.1.4.1.2011.5.25.40.3.2.1.3 |
hwL2tpPeerIp |
- |
1.3.6.1.4.1.2011.5.25.40.3.2.1.4 |
hwL2tpTunnelStatus |
- |
1.3.6.1.4.1.2011.5.25.40.3.2.1.5 |
hwL2tpTunnelDownReason |
- |
1.3.6.1.4.1.2011.5.25.40.3.2.1.6 |
hwL2tpRemoteTunnelID |
- |
Procedure
1. Check whether the tunnel status is Up based on the prompted alarm information.
- If the tunnel status is Up, the L2TP tunnel is set up successfully. The prompted alarm is informational only and no action is required. Then, go to Step 11.
- If the tunnel status is Down, go to Step 2.
2. The L2TP users on the tunnel are logged out when the tunnel goes Down. The users can go online again. Check whether they can go online successfully.
- If the users can go online successfully, go to Step 11.
- If the users cannot go online, go to Step 3.
3. Ping the LNS on the LAC and check whether the LNS can be pinged.
- If the LNS can be pinged, go to Step 4.
- If the LNS cannot be pinged, check the route between the LAC and LNS.
4. Check whether the l2tp enable command is configured on the LAC and LNS.
- If the command is configured, go to Step 5.
- If the command is not configured, run the l2tp enable command in the system view on the LAC and LNS.
5. Check whether the LNS IP address configured for the L2TP group on the LAC is correct. The configured IP address must be consistent with the actual IP address of the LNS.
- If the IP addresses are consistent, go to Step 6.
- If the IP addresses are not consistent, run the start l2tp command in the L2TP group view to re-configure the LNS IP address.
6. Check whether consistent tunnel authentication passwords are configured on the LAC and the LNS. (A tunnel authentication request can be initiated by the LAC or the LNS. The LAC and the LNS can successfully set up an L2TP tunnel only when tunnel authentication is enabled on both ends and the authentication passwords are consistent and are not null on the two ends.)
- If the passwords are consistent, go to Step 7.
- If the passwords are not consistent, run the tunnel password command to re-configure the authentication password.
7. Check whether the virtual template and remote tunnel name specified for the L2TP group on the LNS are correct. (The remote tunnel name specified for the L2TP group on the LNS must be consistent with the local tunnel name configured on the LAC.)
- If the virtual template and remote tunnel name are consistent on the LAC and LNS, go to Step 8.
- If the virtual template and remote tunnel name are inconsistent on the LAC and LNS, run the allow l2tp virtual-template virtual-template-number remote remote-name command to change the virtual template and remote tunnel name.
8. Check whether the LNS group is correctly configured. (The LNS group must be bound to an interface that functions as the tunnel source interface to communicate with the LAC. In addition, the LNS group must be bound to a tunnel board.)
- If the LNS group is correctly configured, go to Step 9.
- If the LNS group is incorrectly configured, run the tunnel source command to bind the LNS group to a tunnel source interface, and run the bind slot command to bind the LNS group to a tunnel board.
9. Run the test l2tp-tunnel command to check tunnel connectivity.
- If the L2TP tunnel is running properly, the L2TP configurations are correct. If users can go online normally, go to Step 11; Otherwise, check user online configurations.
- If the L2TP tunnel is not running properly, go to Step 10.
10. Collect alarm, log, and configuration information, and contact technical support personnel.
11. End