L2VPN/3/hwSingleCCCVcDown_active

Message

L2VPN/3/hwSingleCCCVcDown_active: The status of the single CCC VC turned DOWN. (InterfaceIndex=[inInterfaceIndex], InterfaceIndex=[outInterfaceIndex], HWL2VpnStateChangeReason=[HWL2VpnStateChangeReason], InInterfaceName=[InInterfaceName], OutInterfaceName=[outInterfaceName])

Description

The single CCC VC went Down.

Parameters

Parameter Name	Parameter Meaning
inInterfaceIndex	Index of the traffic incoming-AC interface connected to a CE
outInterfaceIndex	Index of the traffic outgoing-AC interface connected to a CE.
HWL2VpnStateChangeReason	Cause for the CCC VC status change
InInterfaceName	Name of the traffic incoming-AC interface connected to a CE
outInterfaceName	Name of the traffic outgoing-AC interface connected to a CE

Possible Causes

Cause 1: Invalid reason type.
Cause 3: Delete single CCC.
Cause 19: The status of single CCC interface or out-interface turned DOWN.
Cause 28: Outgoing interface was unavailable.
Cause 94: Single 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 single CCC.
1. Check and determine whether the single CCC service instance has to be deleted.
- If it has to be deleted, go to Step 4.
- If it does not have to be deleted, go to Step 2.
2. Re-establish a CCC connection and check whether the trap is cleared.
- If the trap is cleared, go to Step 4.
- If the trap is not cleared, go to Step 3.
3. Collect alarm information and configuration information, and then contact technical support personnel.

4. End.
Cause 19: The status of single CCC interface or out-interface turned DOWN.
1. Run the display vll ccc ccc-name command to check the status of the inbound and outbound interfaces of the CCC services.
- If one of the interfaces is Down, go to Step 2.
- If the inbound and outbound interfaces are both Up, go to Step 5.
2. Locate the cause why the interface went Down and rectify the fault. Then check whether the trap is cleared.
- If the trap is cleared, go to Step 6.
- If the trap is not cleared, go to Step 5.
3. Collect alarm information and configuration information, and then contact technical support personnel.

4. End.
Cause 28: Outgoing interface was unavailable.
1. Check whether the current configuration is the same as the original configuration. For example, check whether MPLS is globally enabled or enabled on the outbound interface of the CCC services.
- If the configurations are the same, go to Step 3.
- If the configurations are different, go to Step 2.
2. Restore the original configuration, and check whether the fault is rectified.
- If the fault is rectified, go to Step 9.
- If the fault is not rectified, go to Step 3.
3. Run the display vll ccc ccc-name command to check the status of the inbound and outbound interfaces of the CCC services.
- If one of the interfaces is Down, go to Step 4.
- If the inbound and outbound interfaces are both Up, go to Step 8.
- If only one interface is available and Up and the next hop IP address of the other interface is displayed, go to Step 5.
4. Locate the cause why the interface went Down and rectify the fault. Then check whether the trap is cleared.
- If the trap is cleared, go to Step 9.
- If the trap is not cleared, go to Step 8.
5. Run the display ip routing-table command to check whether the next hop IP address is reachable.
- If the IP address is reachable, go to Step 8.
- If the IP address is not reachable, go to Step 6.
6. Run the display ip interface brief command to check whether an IP address exists on the same network segment as the next hop IP address does.
- If such IP address exists, go to Step 4.
- If such IP address does not exist, the outbound interface address has been deleted or modified. Then go to Step 7.
7. Enter the outbound interface view and reconfigure the IP address according to the original configuration. Then check whether the trap is cleared.
- If the trap is cleared, go to Step 9.
- If the trap is not cleared, go to Step 8.
8. Collect alarm information and configuration information, and then contact technical support personnel.

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