TWAMP_1.3.6.1.4.1.2011.5.25.333.1.4.7 hwTwampTwoWayLocExceed

Trap Buffer Description

The two-way loss ratio of the TWAMP test instance reached the LOC threshold in three consecutive test intervals. (Test SessionId=[sessionId], Value=[Value], Sender IP=[sender-address], Reflector IP=[reflector-address], Sender Port=[sender-port], Reflector Port=[reflector-port], VPN Instance=[vpn-name])

The packet loss rate of a TWAMP test instance exceeded the threshold (100%) in three consecutive measurement periods.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	hwTwampTwoWayLocExceed
Trap OID	1.3.6.1.4.1.2011.5.25.333.1.4.7
MIB	HUAWEI-TWAMP-MIB
Alarm ID	0x00F1005e
Alarm Name	TWAMP_TWOWAY_LOC
Alarm Type	qualityOfServiceAlarm
Raise or Clear	Raise
Match trap	TWAMP_1.3.6.1.4.1.2011.5.25.333.1.4.8 hwTwampTwoWayLocRecovery

Trap Buffer Parameters

Parameter	Description
sessionId	TWAMP Light test session ID.
Value	Packet loss rate
sender-address	IP address of the sender.
reflector-address	IP address of the reflector.
sender-port	Port number of the sender.
reflector-port	Port number of the reflector.
vpn-name	Indicates the VPN instance name.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.333.1.1.10.1.1	hwTwampTwoWayLossRatio	hwTwampSenderId
1.3.6.1.4.1.2011.5.25.333.1.1.3.1.3	hwTwampSenderLocalIpAddress	hwTwampSenderId
1.3.6.1.4.1.2011.5.25.333.1.1.3.1.5	hwTwampSenderRemoteIpAddress	hwTwampSenderId
1.3.6.1.4.1.2011.5.25.333.1.1.3.1.6	hwTwampSenderLocalUDPPort	hwTwampSenderId
1.3.6.1.4.1.2011.5.25.333.1.1.3.1.7	hwTwampSenderRemoteUDPPort	hwTwampSenderId
1.3.6.1.4.1.2011.5.25.333.1.1.3.1.8	hwTwampSenderVrfName	hwTwampSenderId

Impact on the System

The TWAMP test fails, which may interrupt services.

Possible Causes

The packet loss rate of a TWAMP test instance exceeded the threshold (100%) in three consecutive measurement periods.

Procedure

1. Check whether the peer NE is configured as the TWAMP reflector.

If the peer NE is not configured or incorrectly configured as the TWAMP reflector, correctly configure the NE as the TWAMP reflector.
If the peer NE is correctly configured as the TWAMP reflector, go to Step 2.

2. Check whether some nodes on the TWAMP test path have generated the HARD_BAD, ETH_LOS, or ETH_LINK_DOWN alarm.

If some nodes on the path have generated the HARD_BAD, ETH_LOS, or ETH_LINK_DOWN alarm, clear the alarm.
If no node on the path has generated the HARD_BAD, ETH_LOS, or ETH_LINK_DOWN alarm, go to Step 3.

3. Check whether VPN bearer layers, such as the MPLS and PW layers, are faulty.

If some VPN bearer layers are faulty, rectify the faults.
If no VPN bearer layer is faulty, go to Step 4.

4. Check whether the tunnel bandwidth is used up.

If the bandwidth is used up, increase the bandwidth or eliminate the root cause that leads to the transmission of a large amount of invalid data.
If the bandwidth is not used up, go to Step 5.

5. Collect alarm information and configuration information, and then contact technical support personnel.