PIC/1/hwCardInvalid_active

Message

PIC/1/hwCardInvalid_active: The card failed completely. (EntityPhysicalIndex=[EntityPhysicalIndex], EntPhysicalIndex=[EntPhysicalIndex], EntPhysicalName=[EntPhysicalName], EntityType=[EntityType], EntityTrapFaultID=[EntityTrapFaultID], ReasonDescription=[ReasonDescription])

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

Description

The card failed completely.

Parameters

Parameter Name	Parameter Meaning
EntityPhysicalIndex	Indicates the index of the physical entity.
EntPhysicalIndex	Indicates the index of the physical entity.
EntPhysicalName	Indicates the name of the physical entity.
EntityType	Indicates the type of the physical entity.
EntityTrapFaultID	Indicates the error code.
ReasonDescription	Indicates the description of the cause of the trap.

Possible Causes

Cause 8: The subcard failed the self check.
Cause 135424: The EPLD logic of the subcard was faulty.
Cause 135425: The FPGA logic of the subcard was faulty.
Cause 135426: The key component on the subcard was faulty.
Cause 135427: The clock unit on the subcard was faulty.
Cause 135428: The subcard does not match the slot.
Cause 135429: The PIC NP failed.
Cause 135430: The heartbeat of the subcard was faulty.
Cause 135432: Subcard registration failed.
Cause 135433: The storage component on the subcard was faulty.
Cause 135434: The data channel of the subcard was faulty.
Cause 135439: The subcard is powered off.
Cause 135442: The subcard is uncompatible with system software.
Cause 135444: The slave control bus of the card %s is abnormal.
Cause 135447: The slave data channel of the subcard was faulty.
Cause 135448: The slave key component of the subcard was faulty.
Cause 135467: The forwarding channel resources became insufficient.

Procedure

Cause 8: The subcard failed the self check.
1.If the motherboard on which the subcard resides does not support FPIC, go to Step 5.

2.If the motherboard on which the subcard resides resets, no action is required.

3.Power off the subcard and then power it on again.

4.If the subcard cannot be registered or the alarm persists after the subcard is registered, replace the subcard.

5.If the motherboard supports only one subcard, power off the motherboard and then power it on again.

6.If the motherboard does not support FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the motherboard.

7.If the motherboard supports FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the subcard. If the fault persists, replace the motherboard.

8.Collect the information about alarms, logs, and configurations, and then contact technical support personnel.

9.End.
Cause 135424: The EPLD logic of the subcard was faulty.
1.If the motherboard on which the subcard resides does not support FPIC, go to Step 5.

2.If the motherboard on which the subcard resides resets, no action is required.

3.Power off the subcard and then power it on again.

4.If the subcard cannot be registered or the alarm persists after the subcard is registered, replace the subcard.

5.If the motherboard supports only one subcard, power off the motherboard and then power it on again.

6.If the motherboard does not support FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the motherboard.

7.If the motherboard supports FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the subcard. If the fault persists, replace the motherboard.

8.Collect the information about alarms, logs, and configurations, and then contact technical support personnel.
Cause 135425: The FPGA logic of the subcard was faulty.
1.If the motherboard on which the subcard resides does not support FPIC, go to Step 5.

2.If the motherboard on which the subcard resides resets, no action is required.

3.Power off the subcard and then power it on again.

4.If the subcard cannot be registered or the alarm persists after the subcard is registered, replace the subcard.

5.If the motherboard supports only one subcard, power off the motherboard and then power it on again.

6.If the motherboard does not support FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the motherboard.

7.If the motherboard supports FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the subcard. If the fault persists, replace the motherboard.

8.Collect the information about alarms, logs, and configurations, and then contact technical support personnel.
Cause 135426: The key component on the subcard was faulty.
1.If the motherboard on which the subcard resides does not support FPIC, go to Step 5.

2.If the motherboard on which the subcard resides resets, no action is required.

3.Power off the subcard and then power it on again.

4.If the subcard cannot be registered or the alarm persists after the subcard is registered, replace the subcard.

5.If the motherboard supports only one subcard, power off the motherboard and then power it on again.

6.If the motherboard does not support FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the motherboard.

7.If the motherboard supports FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the subcard. If the fault persists, replace the motherboard.

8.Collect the information about alarms, logs, and configurations, and then contact technical support personnel.
Cause 135427: The clock unit on the subcard was faulty.
1.If the motherboard on which the subcard resides does not support FPIC, go to Step 5.

2.If the motherboard on which the subcard resides resets, no action is required.

3.Power off the subcard and then power it on again.

4.If the subcard cannot be registered or the alarm persists after the subcard is registered, replace the subcard.

5.If the motherboard supports only one subcard, power off the motherboard and then power it on again.

6.If the motherboard does not support FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the motherboard.

7.If the motherboard supports FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the subcard. If the fault persists, replace the motherboard.

8.Collect the information about alarms, logs, and configurations, and then contact technical support personnel.
Cause 135428: The subcard does not match the slot.
1.Install a subcard that matches the slot.
Cause 135429: The PIC NP failed.
1.If the motherboard on which the subcard resides does not support FPIC, go to Step 5.

2.If the motherboard on which the subcard resides resets, no action is required.

3.Power off the subcard and then power it on again.

4.If the subcard cannot be registered or the alarm persists after the subcard is registered, replace the subcard.

5.If the motherboard supports only one subcard, power off the motherboard and then power it on again.

6.If the motherboard does not support FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the motherboard.

7.If the motherboard supports FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the subcard. If the fault persists, replace the motherboard.

8.Collect the information about alarms, logs, and configurations, and then contact technical support personnel.

9.End.
Cause 135430: The heartbeat of the subcard was faulty.
1.If the motherboard on which the subcard resides does not support FPIC, go to Step 5.

2.If the motherboard on which the subcard resides resets, no action is required.

3.Power off the subcard and then power it on again.

4.If the subcard cannot be registered or the alarm persists after the subcard is registered, replace the subcard.

5.If the motherboard supports only one subcard, power off the motherboard and then power it on again.

6.If the motherboard does not support FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the motherboard.

7.If the motherboard supports FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the subcard. If the fault persists, replace the motherboard.

8.Collect the information about alarms, logs, and configurations, and then contact technical support personnel.

9.End.
Cause 135432: Subcard registration failed.
Collect the information about alarms, logs, and configurations, and then contact technical support personnel.
Cause 135433: The storage component on the subcard was faulty.
1.If the motherboard on which the subcard resides does not support FPIC, go to Step 5.

2.If the motherboard on which the subcard resides resets, no action is required.

3.Power off the subcard and then power it on again.

4.If the subcard cannot be registered or the alarm persists after the subcard is registered, replace the subcard.

5.If the motherboard supports only one subcard, power off the motherboard and then power it on again.

6.If the motherboard does not support FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the motherboard.

7.If the motherboard supports FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the subcard. If the fault persists, replace the motherboard.

8.Collect the information about alarms, logs, and configurations, and then contact technical support personnel.

9.End.
Cause 135434: The data channel of the subcard was faulty.
1.If the motherboard on which the subcard resides does not support FPIC, go to Step 5.

2.If the motherboard on which the subcard resides resets, no action is required.

3.Power off the subcard and then power it on again.

4.If the subcard cannot be registered or the alarm persists after the subcard is registered, replace the subcard.

5.If the motherboard supports only one subcard, power off the motherboard and then power it on again.

6.If the motherboard does not support FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the motherboard.

7.If the motherboard supports FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the subcard. If the fault persists, replace the motherboard.

8.Collect the information about alarms, logs, and configurations, and then contact technical support personnel.
Cause 135439: The subcard is powered off.
Replace the faulty card or Power on the card.
Cause 135442: The subcard is uncompatible with system software.
1.Reseat the card and check whether the alarm is cleared. If the alarm persists, go to step 2.

2.Replace a new card and check whether the alarm is cleared. If the alarm persists, go to step 3.

3.Collect information about alarms, logs, and configurations, and then contact technical support personnel.
Cause 135444: The slave control bus of the card %s is abnormal.
1.If the motherboard on which the subcard resides does not support FPIC, go to Step 5.

2.If the motherboard on which the subcard resides resets, no action is required.

3.Power off the subcard and then power it on again.

4.If the subcard cannot be registered or the alarm persists after the subcard is registered, replace the subcard.

5.If the motherboard supports only one subcard, power off the motherboard and then power it on again.

6.If the motherboard does not support FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the motherboard.

7.If the motherboard supports FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the subcard. If the fault persists, replace the motherboard.

8.Collect the information about alarms, logs, and configurations, and then contact technical support personnel.

9.End.
Cause 135447: The slave data channel of the subcard was faulty.
1.If the motherboard on which the subcard resides does not support FPIC, go to Step 5.

2.If the motherboard on which the subcard resides resets, no action is required.

3.Power off the subcard and then power it on again.

4.If the subcard cannot be registered or the alarm persists after the subcard is registered, replace the subcard.

5.If the motherboard supports only one subcard, power off the motherboard and then power it on again.

6.If the motherboard does not support FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the motherboard.

7.If the motherboard supports FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the subcard. If the fault persists, replace the motherboard.

8.Collect the information about alarms, logs, and configurations, and then contact technical support personnel.

9.End.
Cause 135448: The slave key component of the subcard was faulty.
1.If the motherboard on which the subcard resides does not support FPIC, go to Step 5.

2.If the motherboard on which the subcard resides resets, no action is required.

3.Power off the subcard and then power it on again.

4.If the subcard cannot be registered or the alarm persists after the subcard is registered, replace the subcard.

5.If the motherboard supports only one subcard, power off the motherboard and then power it on again.

6.If the motherboard does not support FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the motherboard.

7.If the motherboard supports FPIC, and the motherboard cannot be registered or the alarm persists after the motherboard is registered, replace the subcard. If the fault persists, replace the motherboard.

8.Collect the information about alarms, logs, and configurations, and then contact technical support personnel.

9.End.
Cause 135467: The forwarding channel resources became insufficient.
1.Replace another card, and then check whether the fault is rectified. - If not, go to step 2.

2.Collect information about alarms, logs, and configurations, and then contact technical support personnel.