CUSP_1.3.6.1.4.1.2011.5.25.351.2.1 hwCuspConnectionDown

Trap Buffer Description

CUSP connection is down.(IP Type=[CuspIpType], Local IP=[CuspLocalIp], Remote IP=[CuspRemoteIp], VrfName=[VrfName], DatapathId=[DatapathId], AuxiliaryId=[AuxiliaryId], SubReason=[SubReason], Reason=[Reason])

The CUSP connection was interrupted.

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

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	hwCUSPSessionDown
Trap OID	1.3.6.1.4.1.2011.5.25.351.2.1
MIB	HUAWEI-CUSP-MIB
Alarm ID	0x00F1023e
Alarm Name	hwCUSPSessionDown
Alarm Type	communicationsAlarm
Raise or Clear	Raise
Match trap	CUSP_1.3.6.1.4.1.2011.5.25.351.2.2 hwCuspConnectionDownClear

Trap Buffer Parameters

Parameter	Description
CuspIpType	Type of an IP address
CuspLocalIp	IP address of a forwarder of a CUSP connection
CuspRemoteIp	IP address of a controller of a CUSP connection
VrfName	Index of a VRF instance in which a CUSP connection is established
DatapathId	ID of a CUSP forwarder
AuxiliaryId	Auxiliary connection ID
SubReason	Reason why a CUSP connection was interrupted
Reason	Reason why a CUSP session went Down

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.351.1.2.1.1.1	hwCuspIpType	hwCuspIpType hwCuspRemoteIp hwCuspLocalIp hwCuspVpnInstanceName hwCuspDatapathId hwCuspAuxiliaryId
1.3.6.1.4.1.2011.5.25.351.1.2.1.1.2	hwCuspRemoteIp	hwCuspIpType hwCuspRemoteIp hwCuspLocalIp hwCuspVpnInstanceName hwCuspDatapathId hwCuspAuxiliaryId
1.3.6.1.4.1.2011.5.25.351.1.2.1.1.3	hwCuspLocalIp	hwCuspIpType hwCuspRemoteIp hwCuspLocalIp hwCuspVpnInstanceName hwCuspDatapathId hwCuspAuxiliaryId
1.3.6.1.4.1.2011.5.25.351.1.2.1.1.4	hwCuspVpnInstanceName	hwCuspIpType hwCuspRemoteIp hwCuspLocalIp hwCuspVpnInstanceName hwCuspDatapathId hwCuspAuxiliaryId
1.3.6.1.4.1.2011.5.25.351.1.2.1.1.5	hwCuspDatapathId	hwCuspIpType hwCuspRemoteIp hwCuspLocalIp hwCuspVpnInstanceName hwCuspDatapathId hwCuspAuxiliaryId
1.3.6.1.4.1.2011.5.25.351.1.2.1.1.6	hwCuspAuxiliaryId	hwCuspIpType hwCuspRemoteIp hwCuspLocalIp hwCuspVpnInstanceName hwCuspDatapathId hwCuspAuxiliaryId
1.3.6.1.4.1.2011.5.25.351.1.2.1.1.7	hwCuspConnectionDownSubReason	hwCuspIpType hwCuspRemoteIp hwCuspLocalIp hwCuspVpnInstanceName hwCuspDatapathId hwCuspAuxiliaryId

Impact on the System

The CUSP connection was interrupted, interrupting CUSP session services.

Possible Causes

Cause 1: A TCP connection became abnormal.
Cause 2: CUSP heartbeat packets timed out.
Cause 3: A forwarder received invalid packets sent by the controller of a CUSP session or incorrectly processed received packets.

Procedure

Cause 1: A TCP connection became abnormal.
1. Check whether the CUSP configuration on the controller is modified or deleted.
- If the configuration is changed, correct the configuration on the remote device.
- If the configuration is not changed, go to Step 2.
2. Run the ping command on both ends of the CUSP connection to monitor link connectivity.
- If the ping is successful, go to Step 3.
- If the ping fails, rectify the connectivity fault. Then go to Step 3.
3. Run the display cusp session command to view the CUSP session status.
- If the CUSP session status is not "REGISTERED", go to Step 4.
- If the CUSP session status is "REGISTERED", go to Step 5.
4. Collect alarm information and configuration information, and then contact technical support personnel.

5. End.
Cause 2: CUSP heartbeat packets timed out.
1. Run the ping command on both ends of the CUSP connection to monitor link connectivity.
- If the ping is successful, go to Step 2.
- If the ping fails, rectify the connectivity fault. Then go to Step 2.
2. Run the display cusp session command to view the CUSP session status.
- If the CUSP session status is not "REGISTERED", go to Step 3.
- If the CUSP session status is not "REGISTERED", go to Step 4.
3. Collect alarm information and configuration information, and then contact technical support personnel.

4. End.
Cause 3: A forwarder received invalid packets sent by the controller of a CUSP session or incorrectly processed received packets.
Collect alarm information and configuration information, and then contact technical support personnel.