No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

PIC Fails to Register Due to An Error in the System Software Package on the CF Card

Publication Date:  2013-09-27 Views:  47 Downloads:  0
Issue Description

During the software commissioning of NE40E-X3 V300R006C01SPC003, a PIC subboard failed to register, as shown in the following:

=============================================================

===============display device pic-status===============

=============================================================

Pic-status information in Chassis 1:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

SLOT PIC Status Type Port_count Init_result Logic down

1 0 Registered ETH_12XGF_CARD 12 SUCCESS SUCCESS

2 0 Registered ETH_12XGF_CARD 12 SUCCESS SUCCESS

4 1 Online ETH_12XGF_CARD 0 FAILURE NULL  
Handling Process

Possible causes were as follows:

Cause 1: The PCI subboard had a hardware fault.

Cause 2: The system control board was faulty.

Huawei performed the following operations to diagnose the fault:

For cause 1:

Installed the PCI subboard on another NE40E-X3 and found that the subboard could be registered. Therefore, this issue was not caused by cause 1.

For cause 2:

Performed a switchover on the active and standby system control boards of the NE40E-X3 and found that the PIC subboard could be registered successfully. Therefore, the issue was caused by the active system control board. Generally, a PIC subboard registration failure was caused by a drive file uploading failure. When a PIC subboard was powered on, the system read the drive file from the CF card. If an error occurred during the process, error logs were generated. Therefore, the fault could be located by analyzing the error logs generated during the power-on and power-off of the PIC subboard.

Huawei performed the following operations to diagnose the fault:

Enabled the debug function on the device and power-cycled the subboard. Then, analyzed the debugging load info and debugging load event logs and found no errors. After the main board started normally, analyzed the logs of the subboard.

Collected the latest stdout-buffer information on the subboard in hidden mode, as follows:

    [hidecmd]display stdout-buffer slot 4

The logs were as follows:

MPU packet for slot 4 File[253] ID:0X3000200e, Version:0X50000, CRC:0Xb2a2.

5.4085530181 63_siverek_h4_1 SRM/7/DBG:

MPU packet for slot 4 File[254] ID:0X3000200f, Version:0X10000, CRC:0X1f9b.

5.4085530181 63_siverek_h4_1 SRM/7/DBG:

Info:NO available slave pack for loading

5.4085530182 63_siverek_h4_1 SRM/7/DBG:

5.4087818046 63_siverek_h4_1 SRM/7/DBG:

The sub fileID is error!                                          //Error in reading the sub file header.

5.4087818046 63_siverek_h4_1 SRM/7/DBG:

The sub fileID is -1966533464

The fault cause was as follows: The system control board read only the 254th file in the system software package on the CF card, but the subboard drive file was the 291st file. The analysis indicated that the sub file header in the system software package was incorrect. Therefore, the MPU card failed to read the subboard drive file and as a result the subboard failed to register.
Root Cause
An error occurred in the system software package on the CF card of the active system control board.
Solution

1. Perform a switchover on the active and standby system control boards, and rewrite the CF file. The preceding issue was resolved onsite using this method.

2. Replace the CF card.
Suggestions
If a PIC subboard fails to register, the possible cause is that the MPU card fails to read the subboard drive file. Therefore, check the file system of the CF card.

END