L2VPN_1.3.6.1.4.1.2011.5.25.119.3.2.1 hwCCCVcDown

Trap Buffer Description

The status of the CCC VC turned DOWN. (CccName=[CccName], InterfaceIndex=[InterfaceIndex], InterfaceIndex=[InterfaceIndex2], HWL2VpnStateChangeReason=[HWL2VpnStateChangeReason], InterfaceName=[InterfaceName])

The trap was generated when the CCC VC was Down.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Error
Mnemonic Code	hwCCCVcDown
Trap OID	1.3.6.1.4.1.2011.5.25.119.3.2.1
MIB	HUAWEI-CCC-MIB
Alarm ID	0x0d500001
Alarm Name	hwCCCVcDown
Alarm Type	communicationsAlarm
Raise or Clear	Raise
Match trap	L2VPN_1.3.6.1.4.1.2011.5.25.119.3.2.2 hwCCCVcUp

Trap Buffer Parameters

Parameter	Description
CccName	Indicates the name of the CCC connection.
InterfaceIndex	Indicates the index of the AC interface that connects to the first CE.
InterfaceIndex2	Indicates the index of the AC interface that connects to the second CE.
HWL2VpnStateChangeReason	Indicates the cause of the VC status change.
InterfaceName	Indicates the AC interface name.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.119.3.1.1.1.4	hwCCCVcIfIndex	hwCCCVcName
1.3.6.1.4.1.2011.5.25.119.3.1.5	hwCCCVcStateChangeReason	-
1.3.6.1.2.1.31.1.1.1.1	ifName	ifIndex

Impact on the System

Services will be interrupted and traffic cannot be forwarded normally.

Possible Causes

Cause 1: Invalid reason type.
Cause 3: Delete CCC.
Cause 19: The status of CCC interface or out-interface turned DOWN.
Cause 28: Outgoing interface was unavailable.
Cause 94: CCC service token exceed.

Procedure

Cause 1: Invalid reason type.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 3: Delete CCC.
1. Confirm that whether the CCC is need to be deleted.
- If so, go to Step 4.
- If not, go to Step 2.
2. Recreate the CCC connection. Then, check whether the alarm is cleared.
- If so, go to Step 4.
- If not, go to Step 3.
3. Collect alarm information and configuration information, and then contact technical support personnel.

4. End.
Cause 19: The status of CCC interface or out-interface turned DOWN.
1. Check whether the current configuration is the same as the original configuration. For example, check whether MPLS is enabled globally, or whether MPLS is enabled on the CCC outbound interface.
- If so, go to Step 3.
- If not, go to Step 2
2. Restore the original configuration. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 9.
- If the alarm is not cleared, go to Step 3.
3. Run the display vll ccc ccc-name command to check the status of the incoming and outgoing interfaces of the CCC VC.
- If either interface is Down or both interfaces are Down, go to Step 4.
- If both interfaces are Up, go to Step 8.
- If one interface goes UP, and the IP address of next hop of the other interface are displayed, go to Step 5.
4. View the cause why the interface is Down and restore the interface to the Up status. Then, check whether the alarm is cleared.
- If cleared, go to Step 9.
- If persists, go to Step 8.
5. Run the display ip routing-table command to check whether the IP address is reachable.
- If so, go to Step 8.
- If not, go to Step 6
6. Run the display ip interface brief command to check whether there are addresses that are in the same segment with the IP address.
- If so, go to Step 4.
- If not, it indicates that the outbound interface address is deleted or changed. In this case, go to Step 7.
7. Enter the view of the outbound interface and reconfigure an IP address in consistent with the original configuration. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 9.
- If the alarm is not cleared, go to Step 8.
8. Collect alarm information and configuration information, and then contact technical support personnel.

9. End.
Cause 28: Outgoing interface was unavailable.
1. Check whether the current configuration is the same as the original configuration.
- If they are the same, go to step 3.
- If they are different, go to step 2.
2. Restore the original configuration and check whether the alarm is cleared.
- If the alarm is cleared, go to step 9.
- If the alarm persists, go to step 3.
3. Run the display vll ccc ccc-name command to check the inbound and outbound interface status of the CCC.
- If the status of one or both interfaces is Down, go to step 4.
- If the status of both interfaces is Up, go to step 8.
- If only one interface is configured and the other is a next hop IP address, go to step 5.
4. Configure the interfaces to go Up and check whether the alarm is cleared.
- If the alarm is cleared, got to step 9.
- If the alarm persists, go to step 8.
5. Run the display ip routing-table command to check whether the IP address is reachable.
- If the IP address is reachable, go to step 8.
- If the IP address is unreachable, go to step 6.
6. Run the display ip interface brief command to check whether IP addresses that are on the same network segment as this IP address exist.
- If such IP addresses exist, go to step 4.
- If such IP addresses do not exist, the outbound interface IP address has been modified or deleted. In this case, go to step 7.
7. Enter the outbound interface view, re-configure the IP address, and check whether the alarm is cleared.
- If the alarm is cleared, go to step 9.
- If the alarm persists, go to step 8.
8. Contact technical support personnel.

9. End.
Cause 94: CCC service token exceed.
Collect alarm information and configuration information, and then contact technical support personnel.