PIC/1/hwCardFail_active

Message

PIC/1/hwCardFail_active: The card failed partially. (EntityPhysicalIndex=[EntityPhysicalIndex], EntPhysicalIndex=[EntPhysicalIndex], EntPhysicalName=[EntPhysicalName], EntityType=[EntityType], EntityTrapFaultID=[EntityTrapFaultID], Reason=[Reason])

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

Description

The subcard experienced a partial failure.

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.
Reason	Indicates the description of the cause of the trap.

Possible Causes

Cause 132140: The voltage exceeds the upper alarm threshold.
Cause 132142: The voltage is below the lower alarm threshold.
Cause 135168: The monitoring channel of the subcard was faulty.
Cause 135170: The sensor on the subcard was faulty.
Cause 135180: The chip was faulty.
Cause 135195: Interface MAC CRC error on a subcard.
Cause 135196: E-label CRC error on a subcard.
Cause 135197: A voltage drop occurred on the board.
Cause 135198: EEPROM is abnormal.

Procedure

Cause 132140: The voltage exceeds the upper alarm threshold.
1. If the power module fails, first rectify the fault.

2. Run the display voltage slot slot-id command in the user view to check whether the actual voltage exceeds the upper fatal threshold.

3. If the actual voltage exceeds the upper fatal threshold, collect the information about alarms, logs, and configurations, and then contact technical support personnel.
Cause 132142: The voltage is below the lower alarm threshold.
1. If the power module fails, first rectify the fault.

2. Run the display voltage slot slot-id command in the user view to check whether the actual voltage exceeds the upper fatal threshold.

3. If the actual voltage exceeds the upper fatal threshold, collect the information about alarms, logs, and configurations, and then contact technical support personnel.
Cause 135168: The monitoring channel of the subcard was faulty.
1. Power off the subcard and then power it on again. Check if the alarm is cleared.
- If the alarm is cleared, go to Step 3.
- If the alarm is not cleared, go to Step 2.
2. Collect alarm information, log information and configuration information, and then contact technical support personnel.

3. End.
Cause 135170: The sensor on the subcard was faulty.
1. Power off the subcard and then power it on again. Check if the alarm is cleared.
- If the alarm is cleared, go to Step 3.
- If the alarm is not cleared, go to Step 2.
2. Collect alarm information, log information and configuration information, and then contact technical support personnel.

3. End.
Cause 135180: The chip was faulty.
1. If services on the card are normal, collect the information about alarms, logs, and configurations, and then contact technical support personnel. Otherwise, if services are abnormal, go to Step 2.

2. Check whether the card is securely installed. If not, install the card firmly.

3. If the fault persists, replace the faulty card.

4. If the alarm persists, collect the information about alarms, logs, and configurations, and then contact technical support personnel.
Cause 135195: Interface MAC CRC error on a subcard.
Replace the subcard.
Cause 135196: E-label CRC error on a subcard.
Replace the subcard.
Cause 135197: A voltage drop occurred on the board.
1. Check whether external power supply is normal.If a power supply problem exists, locate and resolve the problem.

2. Remove the associated board and insert it again. Check whether the board can successfully register. If the registration fails, replace the board.
Cause 135198: EEPROM is abnormal.
1. Check whether the services on the subcard is running properly.
- If so, go to Step 4.
- If not, go to Step 2.
2. Insert the subcard properly,check whether the alarm is cleared.
- If so, go to Step 5.
- If not, go to Step 3.
3. Replace the subcard and check whether the alarm is cleared.
- If so, go to Step 5.
- If not, go to Step 4.
4. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.

5. End.