TWAMP/4/TWAMP_MEM_TWOWAY_JITTER_active: The two-way jitter of the TWAMP test instance exceeded the upper threshold in three consecutive test intervals. (Test SessionId=[sessionId], MemberId=[memberId], MemberName=[memberName], Value=[Value], UpperLimitThreshold=[UpperLimitThreshold], LowerLimitThreshold=[LowerLimitThreshold], Sender IP=[sender-address], Reflector IP=[reflector-address], Sender Port=[sender-port], Reflector Port=[reflector-port], VPN Instance=[vpn-name])
The two-way jitter of a TWAMP test instance exceeded the threshold in three consecutive measurement periods.
| Parameter Name | Parameter Meaning |
|---|---|
|
sessionId |
TWAMP Light test session ID. |
|
memberId |
TWAMP Light test session member ID. |
|
memberName |
TWAMP Light test session member name. |
|
Value |
Jitter value. |
|
UpperLimitThreshold |
The jitter trigger-alarm threshold value. |
|
LowerLimitThreshold |
The clear-alarm jitter threshold value. |
|
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. |
Cause 1: The network bandwidth usage reached or exceeded the preset bandwidth threshold.
Cause 2: The service traversed a large number of NEs.
Cause 1: The network bandwidth usage reached or exceeded the preset bandwidth threshold. 1. Check whether the network bandwidth usage reached or exceeded the preset bandwidth threshold. - If yes, expand the capacity. - If not, go to step 2. 2. Collect alarm information and configuration information, and then contact technical support personnel. Cause 2: The service traversed a large number of NEs. 1. Check whether the service traversed a large number of NEs. - If yes, perform rerouting. Alternatively, delete the original path and establish a new one. - If not, go to step 2. 2. Collect alarm information and configuration information, and then contact technical support personnel.