Troubleshooting - Hardware(V600R003C00_02)

HUAWEI NetEngine80E/40E RouterV600R003C00

Troubleshooting - Hardware

Issue 02Date 2011-09-10

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute the warranty of any kind, express or implied. Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.comEmail: [email protected]

Issue 02 (2011-09-10) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i

About This Document

PurposeNOTE

l This document takes interface numbers and link types of the NE40E-X8 as an example. In workingsituations, the actual interface numbers and link types may be different from those used in thisdocument.

l On NE80E/40E series excluding NE40E-X1 and NE40E-X2, line processing boards are called LineProcessing Units (LPUs) and switching fabric boards are called Switching Fabric Units (SFUs). Onthe NE40E-X1 and NE40E-X2, there are no LPUs and SFUs, and NPUs implement the same functionsof LPUs and SFUs to exchange and forward packets.

This document describes how to troubleshoot the services of the HUAWEI NetEngine80E/40E in terms of common faults and causes, troubleshooting cases, and FAQs.This document describes the procedure and method for troubleshooting for the HUAWEINetEngine80E/40E.

Related VersionsThe following table lists the product versions related to this document.

Product Name VersionHUAWEI NetEngine80E/40ERouter

V600R003C00

Intended AudienceThis document is intended for:l System maintenance engineersl Commissioning engineersl Network monitoring engineers

HUAWEI NetEngine80E/40E RouterTroubleshooting - Hardware About This Document


ii

Symbol ConventionsThe symbols that may be found in this document are defined as follows.

Symbol Description

DANGERIndicates a hazard with a high level of risk, which if notavoided, will result in death or serious injury.

WARNINGIndicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

CAUTIONIndicates a potentially hazardous situation, which if notavoided, could result in equipment damage, data loss,performance degradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or savetime.

NOTE Provides additional information to emphasize or supplementimportant points of the main text.

Command ConventionsThe command conventions that may be found in this document are defined as follows.

Convention DescriptionBoldface The keywords of a command line are in boldface.Italic Command arguments are in italics.[ ] Items (keywords or arguments) in brackets [ ] are optional.{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

& The parameter before the & sign can be repeated 1 to n times.# A line starting with the # sign is comments.



iii

Change HistoryChanges between document issues are cumulative. The latest document issue contains all thechanges made in earlier issues.

Changes in Issue 02 (2011-08-12)The second commercial release. There is no update compared with the previous issue.

Changes in Issue 01 (2011-05-30)Initial field trial release.



iv

Contents

About This Document.....................................................................................................................ii1 Boards Cannot Be Registered......................................................................................................1

1.1 Slave MPU Cannot Be Registered......................................................................................................................21.1.1 Common Causes........................................................................................................................................21.1.2 Troubleshooting Flowchart........................................................................................................................21.1.3 Troubleshooting Procedure........................................................................................................................41.1.4 Relevant Alarms and Logs........................................................................................................................6

1.2 LPU or SFU Cannot Be Registered....................................................................................................................61.2.1 Common Causes........................................................................................................................................61.2.2 Troubleshooting Flowchart........................................................................................................................61.2.3 Troubleshooting Procedure........................................................................................................................71.2.4 Relevant Alarms and Logs........................................................................................................................9

1.3 Subcard Cannot Be Registered...........................................................................................................................91.3.1 Common Causes........................................................................................................................................91.3.2 Troubleshooting Flowchart........................................................................................................................91.3.3 Troubleshooting Procedure......................................................................................................................101.3.4 Relevant Alarms and Logs......................................................................................................................10

1.4 Related Troubleshooting Cases........................................................................................................................101.4.1 The ALM Indicator on the LPU Is On and the Log SRM/2/TMLINEERR Is Displayed.......................101.4.2 1GB Memory of the NE80E/40E MPU Remains the Same After the Memory Is Expanded to 2GB..........................................................................................................................................................................121.4.3 A TCAM Chip Failure Causes All MPLS Tunnels to Go Down............................................................131.4.4 The NE80E/40E SFU Cannot Register Due to Installation of a New Backplane...................................141.4.5 Slave MPU Cannot Be Registered Because the System Software Package and the Master MPU Do NotMatch................................................................................................................................................................15

HUAWEI NetEngine80E/40E RouterTroubleshooting - Hardware Contents


v

1 Boards Cannot Be RegisteredAbout This Chapter

1.1 Slave MPU Cannot Be Registered1.2 LPU or SFU Cannot Be Registered1.3 Subcard Cannot Be Registered1.4 Related Troubleshooting Cases

HUAWEI NetEngine80E/40E RouterTroubleshooting - Hardware 1 Boards Cannot Be Registered


1

1.1 Slave MPU Cannot Be Registered

1.1.1 Common CausesThis fault is commonly caused by one of the following:l The slave MPU has not finished start-up yet.l The slave MPU fails to be powered on.l The system software package loaded to the slave MPU is different from that loaded to the

master MPU.l The EPLD, BootROM, and BootLoad of the slave MPU have not been upgraded.l The memory stick is not properly inserted or is faulty.l The CF card of the slave MPU is faulty.

1.1.2 Troubleshooting FlowchartFigure 1-1 shows the troubleshooting flowchart.



2

Figure 1-1 Troubleshooting flowchart for the fault that the slave MPU cannot be registeredSlave MPU cannot be registered

Seek technical support End

Is fault rectified?

Is fault rectified?

Is fault rectified?

Is fault rectified?

Is fault rectified?

Is fault rectified?

Is fault rectified?

Is fault rectified?

No

Yes

Yes

No

Yes

Yes

Yes

Yes

Yes

Yes

Yes

No

No

No

No

No

No

No

Yes

Yes

Yes

No

No

No

No

No

Yes

Yes

Replace the faulty memory stick

Wait until the start-up time expires

Adjust power supply of the slave

MPU

Insert the memory stick properly

Remove and then insert the CF card

Specify the system software package loaded

to the master MPU as that to be loaded to the

slave MPU

CF card works properly?

Memory stick works properly?

Memory stick is properly inserted on the slave MPU?

Upgrade the EPLD of the slave MPU

Upgrade the BootROM and BootLoad of the slave MPU

Start-up time of the slave MPU has expired?

Slave MPU has been powered on?

System software package loaded to the slave MPU is the same as that loaded to the

master MPU?



3

1.1.3 Troubleshooting ProcedureNOTESaving the results of each troubleshooting step is recommended. If your troubleshooting fails to correctthe fault, you will have a record of your actions to provide Huawei technical support personnel.

ProcedureStep 1 Check that the start-up time of the board has expired.

The time required for a board to complete registration after it is powered on is called the start-up time.The start-up time of an MPU is less than 3 minutes in most cases. If the system software isupgraded and then the device is rebooted, the MPU will finish start-up within 5 minutes.Wait until the start-up time expires. If the slave MPU is still unregistered when the start-up timeexpires, go to Step 2.

Step 2 Check that the slave MPU has been powered on.Run the power on slot ? command in the user view. If "" is displayed, it indicates thatall boards have been powered on.If the slot number of the slave MPU is displayed, it indicates that the slave MPU is not poweredon. Check whether the power supply of the slot where the slave MPU resides is normal. If theindicator on the slave MPU is on, it indicates that the power supply of this slot is normal.l If the power supply of the slot is abnormal, contact Huawei technical support personnel.l If the power supply of the slot is normal but the system still prompts that the slave MPU is

not powered on, it indicates that the power supply module on the slave MPU is faulty. In thiscase, you need to replace the board.

If the power supply of the slave MPU is normal but the slave MPU cannot be registered, go toStep 3.

Step 3 Check that the system software package loaded to the slave MPU is the same as that loaded tothe master MPU.Connect the console port of the slave MPU to a PC, and then check whether the system softwarepackage shown in the field "The start file is" in the feedback information of the console port isthe same as that of the master MPU.If the system software package loaded to the slave MPU is different from that loaded to themaster MPU, refer to the troubleshooting procedure in 1.4.5 Slave MPU Cannot Be RegisteredBecause the System Software Package and the Master MPU Do Not Match.If the system software packages loaded to both MPUs are the same but the slave MPU still cannotbe registered, go to Step 4.

Step 4 Upgrade the EPLD of the slave MPU.Run the upgrade mpu by-testbus slot-id startup mbus_epld and upgrade mpu by-testbusslot-id startup outer_epld commands in the user view to upgrade the EPLD of the slave MPU.If the slave MPU still cannot be registered after the EPLD is upgraded, go to Step 5.



4

NOTE

The upgrade mpu by-testbus slot-id startup mpu_epld command is used to upgrade the EPLD on the slaveMPU of the NE80E/40E-X1/X2.

Step 5 Upgrade the BootROM and BootLoad of the slave MPU.Run the upgrade mpu by-testbus slot-id startup bootrom and upgrade mpu by-testbus slot-id startup bootload commands in the user view to upgrade the BootROM and BootLoad of theslave MPU. If the slave MPU still cannot be registered after the BootROM and BootLoad areupgraded, go to Step 6.

Step 6 Check that the memory stick is properly inserted on the slave MPU.An MPU has two memory slots. In the case of only one memory stick, the memory stick mustbe inserted into slot 0; otherwise, the MPU cannot be powered on.If the slave MPU still cannot be registered after the memory stick is properly inserted, go to Step7.

NOTE

The MPU of the NE80E/40E-X1/X2 has no memory stick but a DDR chip so that this step is not applicable tothe NE80E/40E-X1/X2.

Step 7 Check that memory sticks are not faulty.1. Run the board-channel-check disable command on the master MPU to disable the

detection of inter-board communication.NOTEDisabling the detection of inter-board communication does not affect services on the other boards.

2. Power off the slave MPU, and then remove it. After 30 seconds, connect the console portof this board to the COM port of a PC, and then insert the slave MPU back and power iton. When the message "Press CTRL+T to start sdram full test in xx seconds!" is displayed,press Ctrl+T to perform a thorough check on the memory of the board.If a memory fault is detected, a prompt containing the word "fail" will be displayed. In thiscase, you need to remove the memory stick and then insert it back. If the fault persists afterseveral attempts, you need to replace the faulty memory stick.

NOTE

The MPU of the NE80E/40E-X1/X2 has no memory stick but a DDR chip so that this step is not applicableto the NE80E/40E-X1/X2.

NOTEIf no information is displayed on the PC, it indicates that the memory stick is faulty. In this case,remove the memory stick and then insert it back. If the fault persists after several attempts, replacethe faulty memory stick.

After the preceding operations, if the slave MPU still cannot be registered, go to Step 8.Step 8 Check that CF cards work properly.

NOTE

The MPU of the NE80E/40E-X1/X2 has only a CF card so that this step is not applicable to the NE80E/40E-X1/X2.

Remove the slave MPU and all the CF cards, and then insert the slave MPU and CF cards back.If the slave MPU still cannot be registered, go to Step 9.



5

Step 9 Collect the following information and contact Huawei technical support personnel.l Results of the preceding troubleshooting procedurel Configuration files, log files, and alarm files of the device----End

1.1.4 Relevant Alarms and Logs

Relevant AlarmsNone.

Relevant LogsNone.

1.2 LPU or SFU Cannot Be RegisteredSFU is not supported on the X1 and X2 models of the NE80E/40E

1.2.1 Common CausesThis fault is commonly caused by one of the following:l The board has not finished start-up yet.l The board type is not supported by the system software.l The board fails to be powered on.l The EPLD, BootROM, and BootLoad of the board have not been upgraded.l The board is not securely inserted.




6

Figure 1-2 Troubleshooting flowchart for the fault that an LPU or SFU cannot be registeredLPU or SFU cannot be

registered

Board has been pow ered on?

U pgrade the EPLD of the board

U pgrade the BootR O M and BootLoad of the board

Seek technica l support End

Is fau lt rectified?W ait until the start-up tim e expires

Is fau lt rectified?





U se a board supported by the system softw are version

Adjust pow er supply of the board

N o

Yes

Yes

No

Yes

Yes

Yes

Yes

Yes

N o

N o

N o

N o

N o

Yes

Yes

N o

N o

R em ove and then insert the board

S tart-up tim e of the board has expired ?

Board type is supported by the system softw are?


ProcedureStep 1 Check that the start-up time of the board has expired.

The time required for a board to complete registration after it is powered on is called the start-up time.Normally, an LPU can complete the start-up process within 5 minutes. If the system softwareand related files need to be updated, an LPU can complete the start-up process within 10 minutes.



7

Normally, an SFU can complete the start-up process within 2 minutes. If the system softwareand related files need to be updated, an SFU can complete the start-up process within 5 minutes.Wait until the start-up time expires. If the board is still unregistered when the start-up timeexpires, go to Step 2.

Step 2 Check that the board type is supported by the system software.Supported board types vary with system software versions. For the types of boards that aresupported by this software version, see the chapter titled "Boards" in the HUAWEINetEngine80E/40E Router Hardware Description.If the board type is supported by this system software version but the board cannot be registered,go to Step 3.

Step 3 Check that the board has been powered on.Run the power on slot ? command in the user view. If "" is displayed, it indicates thatall boards have been powered on.If the slot number of the board is displayed, it indicates that the board is not powered on. Checkwhether the power supply of the slot where the board resides is normal. If the indicator on theboard is on, it indicates that the power supply of this slot is normal.l If the power supply of the slot is abnormal, contact Huawei technical support personnel.l If the power supply of the slot is normal but the system still prompts that the board is not

powered on, it indicates that the power supply module on the board is faulty. In this case,you need to replace the board.

If the power supply of the board is normal but the board cannot be registered, go to Step 4.Step 4 Upgrade the EPLD of the board.

Run the upgrade lpu by-testbus slot-id startup lpu_epld and upgrade lpu by-testbus slot-id startup lpu_epld2 commands in the user view to upgrade the EPLD of the LPU.Run the upgrade sfu by-testbus slot-id startup mbus_epld, upgrade sfu by-testbus slot-idstartup sfu_epld1, and upgrade sfu by-testbus slot-id startup sfu_epld2 commands in theuser view to upgrade the EPLD of the SFU.If the board still cannot be registered after the EPLD is upgraded, go to Step 5.

Step 5 Upgrade the BootROM and BootLoad of the board.Run the upgrade lpu by-testbus slot-id startup lpu_bootrom and upgrade lpu by-testbusslot-id startup lpu_bootload commands in the user view to upgrade the BootROM andBootLoad of an LPU.Run the upgrade sfu by-testbus slot-id startup sfu_bootrom and upgrade sfu by-testbus slot-id startup sfu_bootload commands in the user view to upgrade the BootROM and BootLoadof the concerned SFU.If the board still cannot be registered after the EPLD is upgraded, go to Step 6.

Step 6 If a new board cannot be registered, remove the board and then insert it back. If the board stillcannot be registered, go to Step 7.

Step 7 Collect the following information and contact Huawei technical support personnel.l Results of the preceding troubleshooting operations



8

l Configuration files, log files, and alarm files of the device----End



Relevant LogsNone.

1.3 Subcard Cannot Be Registered

1.3.1 Common CausesThis fault is commonly caused by one of the following:l The subcard fails to be powered on.l The subcard is not securely inserted.


Figure 1-3 Troubleshooting flowchart for the fault that a subcard cannot be registeredSubcard cannot be

registered

Seek technical support End

Is fault rectified?

Is fault rectified?

Adjust power supply of the subcard

Yes

Yes

No

No

Yes

No

Remove and then insert the subcard

Subcard has been powered on?



9


ProcedureStep 1 Check that the subcard has been powered on.

Check whether the indicator on the subcard is on. If the indicator is off, it indicates that thesubcard is not powered on. In this case, you need to check whether the subcard is securelyinserted. Insert the subcard completely into the slot, and then tighten screws to fix the subcard.If the subcard is powered on but cannot be registered, go to Step 2.

Step 2 Remove the subcard and then insert it.If the subcard still cannot be registered, go to Step 4.

Step 3 Collect the following information and contact Huawei technical support personnel.l Results of the preceding troubleshooting procedurel Configuration files, log files, and alarm files of the device----End



Relevant LogsNone.

1.4 Related Troubleshooting Cases

1.4.1 The ALM Indicator on the LPU Is On and the Log SRM/2/TMLINEERR Is Displayed

The ALM indicator on the LPU is always On and the log SRM/2/TMLINEERR is displayed.

Fault Analysis1. The system displays the following alarm messages. Through analysis, you can find that the

system generates an alarm due to packet loss on LPU2.Jul 31 2008 15:54:01 TZ-XQ-R-01 %%01SRM/2/TMLINEERR(l): LPU2 occur line error! Error Code=2.2!



10

Jul 31 2008 15:53:01 TZ-XQ-R-01 %%01SRM/2/TMLINEERR(l): LPU2 occur line error! Error Code=2.1!

2. Run the display interface interface-type interface-number command to check informationabout interfaces on LPU2, and you can find that GE 2/0/0 transmits packets at a rate closeto the line rate. The command output is as follows:Last 30 seconds output rate: 968093056 bits/sec, 209961 packets/sec

3. After checking the configuration of GE 2/0/0, you can find that port mirroring is configuredon the device where GE 2/0/0 functions as an observing port and GE 2/0/1 and GE 2/0/2function as mirrored ports.(1) Run the display this command in the view of GE 2/0/0, and you can find that port

mirroring is configured on the device.[HUAWEI-GigabitEthernet2/0/0] display this#interface GigabitEthernet2/0/0 undo shutdown port-observing observe-index 2#return

(2) Run the display port-observing slot command to obtain the slot ID of the mirroredport through the reference slot item.[HUAWEI] display port-observing slot slot 2 observe-port : GigabitEthernet2/0/0 reference slot : 2

(3) Run the display port-mirroring interface slot slot-id command to view the mirroredport number.[HUAWEI] display port-mirroring interface slot 2 ------------------------------------------------------------------------------ Interface Local/Remote CAR Type In/Out WithLinkHeader Instance ------------------------------------------------------------------------------ GI2/0/1 Local - Port In - - GI2/0/2 Local - Port In - - ------------------------------------------------------------------------------

ProcedureStep 1 You can cancel the observing port or decreases the number of mirrored ports to clear the fault.

NOTE

The fault occurs because traffic from two mirrored ports is mirrored to one observing port. In this case,there is too much traffic on the observing port, which causes the generation of an alarm and packet loss.If port mirroring is configured to monitor traffic on the mirrored ports, you can reduce the number ofmirrored ports or mirror the traffic to other ports in addition to the observing port.

Step 2 Canceling the observing port1. Run the system-view view to enter the system view.2. Run the interface interface-type interface-number command to enter the interface view.

In this step, the view of the observing port, that is, GE 2/0/0, is displayed.



11

3. Run the undo port-observing observe-index observe-index-number command to cancelport mirroring.

Step 3 Reducing the number of mirrored ports1. Run the system-view view to enter the system view.2. Run the interface interface-type interface-number command to enter the interface view.

In this step, the view of a mirrored port, that is, GE 2/0/1 or GE 2/0/2, is displayed.3. Run the undo port-mirroring { inbound | outbound } command to cancel port mirroring.

Step 4 After the preceding operations, the ALM indicator on the LPU recovers and no logs are displayedany longer.

----End

SummaryWhen traffic from multiple mirrored ports is mirrored to one observing port, traffic on theobserving port may reach line rate and packet loss occurs. Before configuring port mirroring,ensure that the traffic can be processed on the observing port.

1.4.2 1GB Memory of the NE80E/40E MPU Remains the Same Afterthe Memory Is Expanded to 2GB

The MPU on the NE80E/40E is currently installed with a 1GB memory bar manufactured byvendor A. The MPU memory now needs to be expanded to 2GB through additional installationof another 1GB memory bar. After one 1GB memory bar manufactured by vendor B is installedin the MPU, it is displayed that the MPU memory is still 1GB.

Fault AnalysisNOTE

This troubleshooting case is not applicable to the NE80E/40E-X1/X2.

1. Remove and then install the memory bar manufactured by vendor B from or in the MPU.Then, run the display memory-usage command, and you can find that the memory is still1GB. This rules out the possibility that the memory bar manufactured by vendor B isimproperly installed.

2. Replace the memory bar manufactured by vendor B with another memory bar manufacturedby vendor B. The display memory-usage command displays that the memory of the MPUis still 1GB. This rules out the possibility of failures of the memory bars manufactured byvendor B.

3. Remove the memory bar manufactured by vendor B, and then install two 1GB memorybars to the MPU. Then, the display memory-usage command displays that the memoryon the MPU is 2GB. The fault is thus rectified.

The memory of the NE80E/40E MPU is currently 1GB. To meet service requirement, another1GB memory bar must be installed. The newly installed memory bar, however, is incompatiblewith the existing memory bar of the MPU. Therefore, the newly installed memory bar cannotbe identified. After a 1GB memory bar of the same vendor with that of the existing memory isinstalled to the MPU, the memory of the MPU is displayed as 2GB.



12

ProcedureStep 1 Remove the memory bar manufactured by vendor B, and then install two 1GB memory bars

manufactured by vendor A to the MPU.After the operations, run the display memory-usage command displays that the memory on theMPU is 2GB. The fault is thus rectified.----End

SummaryWhen the memory on the MPU is expanded, ensure that the MPU must be installed with twomemory bars manufactured by the same vendor.

1.4.3 A TCAM Chip Failure Causes All MPLS Tunnels to Go Down

Fault SymptomThe network of an area has two planes. In normal situations, when the master plane fails, servicesare automatically switched to the slave plane.Once, all services on the bearer network are interrupted. Through analysis, it is found that allprimary/backup tunnels between the bearer network and backbone network go Down, causinga failure in establishing LSPs between nodes in this area and nodes in other areas. In this case,services are interrupted.

Fault Analysis1. All primary/backup tunnels are established on interfaces of the LPU in slot 1. Run the

display interface tunnel interface-number command to view the status of tunnelsestablished on interfaces of LPUs in other slots, and you can find that these tunnels arenormal.

2. IS-IS runs on the current network. Run the display isis route command to view the statusof IS-IS on the LPU in slot 1, and you can find that IS-IS runs normally.Because tunnels are established through RSVP or LDP that needs to search the FIB table,it can be preliminarily inferred that a fault occurs when RSVP or LDP searches the FIBtable.

3. The control plane delivers FIB entries to all LPUs. Run the display fib command to checkwhether the FIB entries on the LPUs other than the LPU in slot 1 are normal.If the FIB entries on the other LPUs are normal, it indicates that the control plane properlydelivers the FIB entries. In this case, it can be inferred that a fault occurs on the TCAMchip that stores FIB entries.

ProcedureStep 1 Replace the LPU in slot 1. The fault is thus rectified and services are restored.

----End

SummaryThe possible causes for the failure in searching the FIB table are as follows:



13

l The control plane improperly delivers FIB entries.l A fault occurs on the TCMP chip that stores FIB entires.

1.4.4 The NE80E/40E SFU Cannot Register Due to Installation of aNew Backplane

When the device is installed with four SFUs, all four SFUs can be registered. After the SFUs inslots 21 and 22 are removed, the remaining two SFUs fail to be registered, causing the registrationfailure of the LPUs.

Fault AnalysisNOTEThis troubleshooting case can only be supported on 16 slot device.

SFU is not supported on the X1 and X2 models of the NE80E/40E1. Run the display device command to view the status of boards.

Because the SFUs in slots 21 and 22 are removed, the remaining two SFUs are in theUnregistered state. display deviceDevice status:Slot # Type Online Register Status Primary - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -1 LPU/SPU Present Unregistered Abnormal NA 2 LPU/SPU Present Unregistered Abnormal NA 17 MPU Present NA Normal Master 18 MPU Present Registered Normal Slave 19 SFU Present Unregistered Abnormal NA 20 SFU Present Unregistered Abnormal NA 23 CLK Present Registered Normal Master 24 CLK Present Registered Normal Slave

2. Run the display version command to view the backplane type. display versionHuawei Versatile Routing Platform SoftwareVRP (R) software, Version 5.30 (V300R002C06B325)Copyright (C) 2000-2008 Huawei Technologies Co., LtdNetEngine uptime is 0 day, 6 hours, 35 minutes BKP 0 version information: 1. PCB Version : CR52BKPC REV A 2. MPU Slot Quantity: 2 3. SRU Slot Quantity: 0 4. SFU Slot Quantity: 4 5. LPU Slot Quantity: 16The displayed PCB shows that the backplane type is BKPC, which indicates that the SFUis required to be installed in slot 21 or slot 22.

NOTE

The synchronization clock signals of the BKPA backplane are offered by the MPU whereas thesynchronization clock signals of the BKPC backplane are offered by the SFUs in slots 21 and 22. Ifthere are no SFUs in slots 21 and 22, the device cannot locate the synchronization clock; thus, allboards cannot be registered. In this case, when there are two SFUs, they must be installed in slots 21and 22.



14

ProcedureStep 1 Remove the SFUs from slots 19 and 20 and then install them in slots 21 and 22.Step 2 After the preceding operation, run the display device command to check the status of boards.

You can find that all boards are properly registered. The fault is thus rectified.----End

SummaryIf there is only one SFU, the SFU must be installed in slot 21 or slot 22. Otherwise, the LPUscannot be registered. If the SFU is installed in slot 19 or slot 20, no LPUs can be registered.If there are two SFUs, the two SFUs must be installed in slots 21 and 22. In this case, the twoSFUs can function as master and slave clock sources.

NOTE

If one SFU is installed in slot 19 or slot 20, the LPUs can be registered but the system displays theinformation that the SFU in slot 19 or slot 20 cannot be registered and prompts you to move the SFU toslot 21 or slot 22.

1.4.5 Slave MPU Cannot Be Registered Because the SystemSoftware Package and the Master MPU Do Not Match

Fault SymptomThe slave MPU cannot be registered.

Fault AnalysisLog in to the device through Telnet, and then run the display startup command to view thesystem software package loaded to the master MPU.MainBoard: Configured startup system software: cfcard:/V600R002C00.cc Startup system software: cfcard:/V600R002C00.cc Next startup system software: cfcard:/V600R002C00.cc Startup saved-configuration file: cfcard:/vrpcfg.cfg Next startup saved-configuration file: cfcard:/vrpcfg.cfg Startup paf file: cfcard:/paf-V600R002C00.txt Next startup paf file: cfcard:/paf-V600R002C00.txt Startup license file: cfcard:/license-V600R002C00.txt Next startup license file: cfcard:/license-V600R002C00.txt Startup patch package: cfcard:/patch.bat Next startup patch package: cfcard:/patch.bat

Connect the console port of the slave MPU to a PC, and then check the system software versiondisplayed in the field "The start file is" in the feedback information of the console port. Theresult shows that the configuration file for startup of the slave MPU is different from that of themaster MPU. This is why the slave MPU cannot be registered.

ProcedureStep 1 Run the board-channel-check disable command in the user view to disable the self-check of

the channel.



15

NOTE

Without this operation, the slave MPU may be reboot during the upgrade.

Step 2 Connect the console port of the device to the COM port of the PC, and configure theHyperTerminal.You can configure a PC to function as both an FTP server and a terminal.In this troubleshooting example, it is presumed that the operating system of the PC is WindowsXP.1. Choose Start > Programs > Accessories > Communications > HyperTerminal. Then,

in the displayed window, enter a name for the connection, for example, test.

2. Click OK. The following window is displayed. Select a COM port. It is recommended toselect COM1.

3. Click OK. The following window is displayed. Set the properties of COM1. In the Bitsper second drop-down list, choose 9600. For the other parameters, use the default settings.



16

Click OK. The configurations of the HyperTerminal is complete.Step 3 Run the FTP server program on the PC and create an FTP user.

NOTEIn this step, the window displayed may vary with the FTP software.

Set parameters of the FTP server program, including the directory, username, and password.

Figure 1-4 Configuration of FTP parameters

Step 4 Restart the device. Press Ctrl+B within 3 seconds after Press Ctrl+B to enter Main Menu...

3 is displayed on the HyperTerminal. ****************************************************



17

* * * 8090 boot ROM, Ver 214.00 * * * ****************************************************

Copyright 2001-2010 Huawei Tech. Co., Ltd. Creation date: Mar 27 2010, 17:47:31

CPU type : MPC7447A CPU L2 Cache : 512KB CPU Core Frequency : 1GHz BUS Frequency : 133MHz

Press Ctrl+B to enter Main Menu... 3

Step 5 Enter the password to enter the main menu.password:

NOTEThe default password is 8090. You can change the password by selecting 6. Modify boot ROMpassword in the main menu.

Main Menu(bootload ver: 216.00)

1. Boot with default mode 2. Boot from CFcard 3. Enter serial submenu 4. Enter ethernet submenu 5. Set boot file and path 6. Modify boot ROM password 7. List file in CFcard 8. Chkdsk CFcard 9. Set patch mode 10. Set version back signal 11. RebootEnter your choice(1-11):4

Step 6 Select 4. Enter ethernet submenu to enter the Ethernet interface submenu. Ethernet Submenu

1. Download file to SDRAM through ethernet interface and boot 2. Download file to CFcard through ethernet interface 3. Modify ethernet interface boot parameters 4. Return to main menu

Be sure to select 3 to modify boot parameters before downloading!Enter your choice(1-4): 3

Step 7 Select 3. Modify ethernet interface boot parameters to set booting parameters.te: two protocols for download, tftp & ftp. You can modify the flags following the menu. tftp--0x80, ftp--0x0.

'.' = clear field; '-' = go to previous field; ^D = quit

boot device : mgi0 \\ mgi0 or mgi2. If it is set to mgi0 but files cannot be loaded, set it to mgi2.processor number : 2 \\If mgi0 is adpoted, set the processor number to 2; if mgi2 is adopted, set the processor number to 0.host name : host \\No action is required.file name : V300R006C01.cc \\Enter the system software name on the server.inet on ethernet (e) : 100.1.1.100:FFFFFF00 \\Set the IP address and mask that can be used to communicate with the FTP server.inet on backplane (b): \\This indicates the backup interface used to communicate with the FTP server. It can be set or not.host inet (h) : 100.1.1.3 \\This indicates the address of the FTP server.gateway inet (g) \\This indicates the gateway used to communicate with the FTP server, which is set as required.



18

user (u) : mpu \\This indicates the FTP user name, which must have been configured on the FTP server.ftp password (pw) (blank = use rsh): mpua \\This indicates the password of the FTP user.flags (f) : 0x0 \\Set FTP or TFTP upgrade. By default, FTP upgrade is adopted. To use TFTP upgrade, enter 0x80. This case uses FTP upgrade, and thus this value does not need to be changed.

target name (tn) \\No action is required.startup script (s) \\No action is required.other (o) : \\No action is required.

Ethernet Submenu



The configuration is now completed. The system returns to the Ethernet interface submenu.Step 8 Select 2. Download file to CFcard through ethernet interface to download the system

software to the CF card.Be sure to select 3 to modify boot parameters before downloading! Enter your choice(1-4): 2 C address:0xa 0xb 0xc 0x0 0x9 0x0Attached TCP/IP interface to mgi2.Attaching network interface lo0... done.

boot device : mgiunit number : 2processor number : 0host name : hostfile name : V300R006C01.ccinet on ethernet (e) : 100.1.1.100:FFFFFF00host inet (h) : 100.1.1.3user (u) : mpuftp password (pw) : mpuaflags (f) : 0x0target name (tn) : Loading...Done! Writing to CFcard...Done!

Ethernet Submenu



After the system software is loaded, the system returns to the Ethernet interface submenu.Step 9 Select 4. Return to main menu. The system returns to the main menu.

Main Menu(bootload ver: 216.00)

1. Boot with default mode 2. Boot from CFcard 3. Enter serial submenu 4. Enter ethernet submenu 5. Set boot file and path



19

6. Modify boot ROM password 7. List file in CFcard 8. Chkdsk CFcard 9. Set patch mode 10. Set version back signal 11. RebootEnter your choice(1-11):5

Step 10 Select 5. Set boot file and path to specify the configuration file for startup. Boot Files Submenu

1. Modify the boot file 2. Modify the paf file 3. Modify the license file 4. Modify the config file 5. Modify the patch file 6. Modify the patch states file 7. Return to main menu

Enter your choice(1-7): 1

Step 11 Select 1. Modify the boot file to modify the configuration file for startup.boot file is cfcard:/V300R006C01.cc, modify the file name if needed. Please input correctly, e.g.: cfcard:/V300R006C01.cc cfcard:/v300r006c01.cc \\Enter the name of the system software that has just been loaded, and then press Enter. The absolute path of the system software must be specifiedThe file name you input is cfcard:/v300r006c01.cc.Are you sure? Yes or No(Y/N)y

NOTEThe method of specifying the PAF and license files is the same as the method of specifying the configurationfile, and is not mentioned here.

Step 12 Enter y, and then press Enter. After files are successfully loaded, the system returns to the BootFiles Submenu.Setting ...Read flag rec from nvram ......................OK!

Write descriptor to nvram ......................OK!Done!

Clear version back signal...Done!

Boot Files Submenu

1. Modify the boot file 2. Modify the paf file 3. Modify the license file 4. Modify the config file 5. Modify the patch file 6. Modify the patch states file 7. Return to main menu

Enter your choice(1-7):7

Step 13 Select 7. Return to main menu. The system returns to the main menu. Main Menu(bootload ver: 216.00)

1. Boot with default mode 2. Boot from CFcard 3. Enter serial submenu 4. Enter ethernet submenu 5. Set boot file and path 6. Modify boot ROM password 7. List file in CFcard 8. Chkdsk CFcard 9. Set patch mode 10. Set version back signal



20

11. Reboot

Enter your choice(1-11): 2

Select 2. Boot from Cfcard to start from the CF card. The slave MPU restarts using the newly-loaded system software.The slave MPU is successfully registered. The fault is rectified.

Step 14 Run the board-channel-check enable command in the user view to enable the self-check of thechannel.----End

SummaryEach MPU is loaded with a system software package when being produced. This softwarepackage is inconsistent with that running a device on the existing network in most cases.Therefore, you need to replace the system software loaded to the MPU.



21

About This DocumentContents1 Boards Cannot Be Registered1.1 Slave MPU Cannot Be Registered1.1.1 Common Causes1.1.2 Troubleshooting Flowchart1.1.3 Troubleshooting Procedure1.1.4 Relevant Alarms and Logs

1.2 LPU or SFU Cannot Be Registered1.2.1 Common Causes1.2.2 Troubleshooting Flowchart1.2.3 Troubleshooting Procedure1.2.4 Relevant Alarms and Logs

1.3 Subcard Cannot Be Registered1.3.1 Common Causes1.3.2 Troubleshooting Flowchart1.3.3 Troubleshooting Procedure1.3.4 Relevant Alarms and Logs

1.4 Related Troubleshooting Cases1.4.1 The ALM Indicator on the LPU Is On and the Log SRM/2/TMLINEERR Is Displayed1.4.2 1GB Memory of the NE80E/40E MPU Remains the Same After the Memory Is Expanded to 2GB1.4.3 A TCAM Chip Failure Causes All MPLS Tunnels to Go Down1.4.4 The NE80E/40E SFU Cannot Register Due to Installation of a New Backplane1.4.5 Slave MPU Cannot Be Registered Because the System Software Package and the Master MPU Do Not Match

Documents

Troubleshooting - Hardware(V600R003C00_02)