Emergency Maintenance(V600R003C00 01)

HUAWEI CX600 Metro Services PlatformV600R003C00

Emergency Maintenance

Issue 01

Date 2011-05-30

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.com

Email: [email protected]

Issue 01 (2011-05-30) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

PurposeNOTE

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

l On CX600 series excluding CX600-X1 and CX600-X2, line processing boards are called LineProcessing Units (LPUs) and switching fabric boards are called Switching Fabric Units (SFUs). Onthe CX600-X1 and CX600-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 handle emergencies on the HUAWEI CX600 Metro ServicesPlatform from the aspects of basic concept, operation procedure, and operation guide. The lastchapter of this document presents a table, which records information about emergencymaintenance for reference.

Intended AudienceThis document is intended for:

l Network administrators

l Network maintenance engineers

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

Symbol Description

DANGERAlerts you to a high risk hazard that could, if not avoided,result in serious injury or death.

WARNINGAlerts you to a medium or low risk hazard that could, ifnot avoided, result in moderate or minor injury.

HUAWEI CX600 Metro Services PlatformEmergency Maintenance About This Document


iii

Symbol Description

CAUTIONAlerts you to a potentially hazardous situation that could,if not avoided, result in equipment damage, data loss,performance deterioration, or unanticipated results.

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

NOTE Provides additional information to emphasize orsupplement important points in the main text.

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

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

About This DocumentHUAWEI CX600 Metro Services Platform


iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2011-05-30)

Contents

About This Document...................................................................................................................iii

1 Overview of Emergency Maintenance...................................................................................1-11.1 Definition of Emergency Maintenance...........................................................................................................1-21.2 Definition of Emergencies..............................................................................................................................1-21.3 Source of Emergency Maintenance.................................................................................................................1-21.4 Principle of Emergency Maintenance.............................................................................................................1-31.5 Precautions for Emergency Maintenance........................................................................................................1-31.6 Technical Support...........................................................................................................................................1-4

2 Flow of Emergency Maintenance............................................................................................2-12.1 Emergency Maintenance Flow Chart..............................................................................................................2-22.2 Flow of Emergency Maintenance...................................................................................................................2-2

2.2.1 Notifying Huawei of the Emergency.....................................................................................................2-32.2.2 Collecting Fault Information..................................................................................................................2-32.2.3 Handling the Emergency........................................................................................................................2-32.2.4 Seeking Help..........................................................................................................................................2-52.2.5 Checking the Handling Result................................................................................................................2-52.2.6 Recording Emergency Maintenance Information..................................................................................2-5

3 Emergency Maintenance Guidelines.....................................................................................3-13.1 Guide to Collecting Fault Information............................................................................................................3-2

3.1.1 Collecting Basic Fault Information........................................................................................................3-23.1.2 Collecting Device Fault Information......................................................................................................3-3

3.2 Guide to Handling Emergencies.....................................................................................................................3-33.2.1 Failed to Log in to the System Through the Serial Interface.................................................................3-43.2.2 Failed to Start the System.......................................................................................................................3-73.2.3 Status of Hardware Components Is Abnormal.....................................................................................3-103.2.4 Interface Status Is Abnormal................................................................................................................3-13

3.3 Guide to Restarting a Device........................................................................................................................3-173.3.1 Preparations for the Restart..................................................................................................................3-183.3.2 Guide to Restarting the CX600............................................................................................................3-183.3.3 Verification After the Restart...............................................................................................................3-203.3.4 Solution to the Restart Failure..............................................................................................................3-23

3.4 Built-in System Software Is Incorrect or Does Not Exist.............................................................................3-23

HUAWEI CX600 Metro Services PlatformEmergency Maintenance Contents


v

3.4.1 Loading the System Software Through the BootROM........................................................................3-233.4.2 Loading the System Software Through the CF Card/USB Port...........................................................3-32

4 Emergency Maintenance Record Table.................................................................................4-14.1 Emergency Maintenance Notice..................................................................................................................... 4-24.2 Emergency Handling Record..........................................................................................................................4-2

ContentsHUAWEI CX600 Metro Services Platform


vi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2011-05-30)

Figures

Figure 2-1 Emergency maintenance flow chart....................................................................................................2-2Figure 2-2 Flow chart of verifying the fault type.................................................................................................2-4Figure 3-1 Flowchart of solving the problem that users cannot log in to a system through the serial interface...............................................................................................................................................................................3-5Figure 3-2 Flow chart of solving the problem that the system cannot be started.................................................3-8Figure 3-3 Memory bar slots on an MPU/SRU..................................................................................................3-10Figure 3-4 Flow chart of solving the problem that the hardware component status is abnormal......................3-12Figure 3-5 Flow chart of solving the problem that the interface status is abnormal..........................................3-15Figure 3-6 interface of connection 1..................................................................................................................3-24Figure 3-7 interface of connection 2..................................................................................................................3-25Figure 3-8 interface of connection 3..................................................................................................................3-25Figure 3-9 Configuring FTP parameters............................................................................................................3-26

HUAWEI CX600 Metro Services PlatformEmergency Maintenance Figures


vii

Tables

Table 2-1 Method of verifying the fault type.......................................................................................................2-4Table 3-1 Basic fault information table................................................................................................................3-2Table 3-2 Fault information table.........................................................................................................................3-3Table 3-3 Fault information table.........................................................................................................................3-4Table 3-4 Fault information table.........................................................................................................................3-7Table 3-5 Fault information table.......................................................................................................................3-11Table 3-6 Fault information table.......................................................................................................................3-14Table 4-1 Emergency maintenance notice............................................................................................................4-2

HUAWEI CX600 Metro Services PlatformEmergency Maintenance Tables


ix

1 Overview of Emergency Maintenance

About This Chapter

This chapter describes the definition of emergencies, and the definition, sources, handlingguidelines, and precautions of emergencies maintenance.

1.1 Definition of Emergency MaintenanceThis section describes the definition and functions of emergency maintenance.

1.2 Definition of EmergenciesThis section describes the definition and classification of emergencies.

1.3 Source of Emergency MaintenanceThis section describes in what situations emergency maintenance is to be applied.

1.4 Principle of Emergency MaintenanceThis section describes the principles of emergency maintenance.

1.5 Precautions for Emergency MaintenanceThis section describes the precautions for emergency maintenance.

1.6 Technical SupportThis section describes how to seek Huawei technical support.

HUAWEI CX600 Metro Services PlatformEmergency Maintenance 1 Overview of Emergency Maintenance


1-1

1.1 Definition of Emergency MaintenanceThis section describes the definition and functions of emergency maintenance.

Emergency maintenance is a rectification method to handle emergencies, such as power-downor service interruption. With emergency maintenance, you can rapidly rectify the fault andrestore the normal operation of the system and device, and thus minimize the loss.

Emergency maintenance also guides maintenance personnel to take preventive measures toprotect the system from a great amount of service traffic.

This document describes how to apply emergency maintenance to the CX600.

1.2 Definition of EmergenciesThis section describes the definition and classification of emergencies.

An emergency is an unexpected fault on a device or a network, which happens suddenly, hasextensive involvement, and has serious consequences on the network security and quality ofservice (qos).

Emergencies that may occur on the CX600 can be classified into:

l Abnormal system - all services being interruptedl Abnormal main processing unit (mpu)/switch and route processing unit (sru) or switch

fabric unit (sfu) - all services being interruptedl Abnormal service board - partial services being interruptedl Abnormal link - services on the interface being interrupted

An emergency is an extreme situation, which may be foretold by abnormality alarms and logs.You can confirm whether an emergency occurs by checking either alarms and logs or acustomer's complaint.

NOTE

This section describes the roadmap for handling emergencies. for the roadmap for locating common faults,refer to the HUAWEI CX600 Metro Services Platform - troubleshooting.

1.3 Source of Emergency MaintenanceThis section describes in what situations emergency maintenance is to be applied.

An emergency may be caused by a software or hardware failure, an incorrect setting, impropermaintenance operation, maintenance maloperation, a line failure, or a natural disaster.Emergency maintenance is expected in either of the following situations:

l Customer' complaintA customer's complaint is the main reason for the application of emergency maintenance.When a fault reported by a customer or the Customer Service Center conforms to theconditions in section "1.2 Definition of Emergencies", emergency maintenance needs tobe applied.

l Alarm messages

1 Overview of Emergency MaintenanceHUAWEI CX600 Metro Services Platform


1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 01 (2011-05-30)

When the alarm messages output by the Network Management System (NMS) or displayedon the terminal initiate a large scale of service interruption, emergency maintenance needsto be applied.

l Natural disaster

When a natural disaster such as the earthquake, fire, or flood happens, it is required totemporarily power off devices and apply emergency maintenance.

1.4 Principle of Emergency MaintenanceThis section describes the principles of emergency maintenance.

Emergencies easily cause network access failures of numerous users, device breakdown, andservice interruption, resulting in serious consequences. To improve the efficiency in handlingemergencies and minimize the losses, you must comply with the following guidelines whenmaintaining devices:

l To keep the stable running of a device and minimize the occurrence probability ofemergencies, refer to the HUAWEI CX600 Metro Services Platform RoutineMaintenance.

l The core function of emergency maintenance is to recover system operation and serviceprovision as soon as possible. To efficiently handle emergencies, you need to set up schemesto handle various emergencies according to the emergency maintenance manual. Managersand maintenance personnel must be well-trained and familiar with these schemes.

l The maintenance personnel must attend the emergency maintenance training to learnmethods of identifying and handling emergencies.

l When an emergency occurs, keep calm and check whether the hardware and route of theCX600 are normal. Then, check whether the emergency is caused by the CX600. If so,handle the emergency according to the predetermined emergency handling schemes or theprocessing procedures in this manual.

l The CF card contains important data. When an emergency occurs, do not format the CFcard before consulting Huawei engineers.

l Contact the Customer Service Center or the local office of Huawei early for technicalsupport during troubleshooting.

l Once the emergency is solved, collect related alarm information and send the handlingreport, device alarm files, and log files to Huawei for analysis. This can help Huawei toimprove the after-sales service.

1.5 Precautions for Emergency MaintenanceThis section describes the precautions for emergency maintenance.

To ensure the security of the device and safety of the operators, comply with the followingguidelines.

Static Electricity

Wear an ESD wrist strap before operating a board or the backplane, and comply with thefollowing rules:

HUAWEI CX600 Metro Services PlatformEmergency Maintenance 1 Overview of Emergency Maintenance


1-3

l For precautions and procedures of board replacement, see "Replacing Boards" in HUAWEICX600 Metro Services Platform Parts Replacement.

l Place a board in an antistatic bag before installing it.

l Place a removed board in an antistatic bag.

Laser/LED

When you maintain a device with an optical module or optical interface, comply with thefollowing rules:

l When installing and maintaining the optical fiber, do not look into the optical fiber withouteye protection.

l When replacing the pluggable optical module, do not look into the connector of the opticalfiber without eye protection.

l Only personnel who attends the mandatory training can operate the optical module andoptical fiber on the CX device.

NOTE

When you install and maintain the optical fiber, keep the connector of the optical fiber clean, unfolded,and straight.

1.6 Technical SupportThis section describes how to seek Huawei technical support.

If a fault persists after the maintenance personnel performs emergency maintenance accordingto the flow chart, contact Huawei Technical Support Center or the local office for technicalsupport.

NOTE

Huawei Technologies Co. Ltd provides 24-hour technical support services.

You can contact Huawei Technical Support Center at:

l Telephone: +86-755-28560000, 8008302118, 4008302118

l Fax: +86-755-28560111

l Website: http://support.huawei.com

l Email: [email protected]

NOTE

l For contact information about local offices, log in to http://support.huawei.com.

l For convenience, you are recommended to create a phone tree containing at least two contact methodsof every superior maintenance personnel, Huawei engineer, transmission office maintenance personnel,and remote office maintenance personnel, and paste it at the prominent place.

Maintenance personnel need maintain a detailed record of the emergency maintenanceprocedures, notify Huawei of the type of the board to be replaced, and apply for a backup boardaccording to the warranty articles. This can help Huawei technical support personnel to rectifythe fault sooner. You can fax an Emergency Maintenance Notice to Huawei. For detailedinformation about the format, refer to Appendix A "4 Emergency Maintenance RecordTable."

1 Overview of Emergency MaintenanceHUAWEI CX600 Metro Services Platform



Issue 01 (2011-05-30)

2 Flow of Emergency Maintenance

About This Chapter

This chapter describes the flow of emergency maintenance.

2.1 Emergency Maintenance Flow ChartThis section describes the flow chart of emergency maintenance.

2.2 Flow of Emergency MaintenanceThis section describes the flow of emergency maintenance.

HUAWEI CX600 Metro Services PlatformEmergency Maintenance 2 Flow of Emergency Maintenance


2-1

2.1 Emergency Maintenance Flow ChartThis section describes the flow chart of emergency maintenance.

NOTE

l During troubleshooting, maintain detailed records of operation procedures and results, which canprovide reference for Huawei technical support personnel and thus handle the emergency sooner.

l When a fault persists, contact Huawei Customer Service Center. For contact information, see section"1.6 Technical Support."

The main purpose of emergency maintenance is to recover a system operation and serviceprovision as soon as possible. Figure 2-1 shows the flow chart of emergency maintenance.

Figure 2-1 Emergency maintenance flow chart

Start

Notify Huawei of the Emergency

Collect fault information

Locate the fault

Rectify the fault

Service recovery?

Check the handling result

Record information about emergency

maintenance

End

Obtain helpNo

Yes

2.2 Flow of Emergency MaintenanceThis section describes the flow of emergency maintenance.

2.2.1 Notifying Huawei of the Emergency

2.2.2 Collecting Fault Information

2 Flow of Emergency MaintenanceHUAWEI CX600 Metro Services Platform



Issue 01 (2011-05-30)

2.2.3 Handling the Emergency

2.2.4 Seeking Help

2.2.5 Checking the Handling Result

2.2.6 Recording Emergency Maintenance Information

2.2.1 Notifying Huawei of the Emergency

When an emergency occurs, immediately contact Huawei for technical support.

NOTE

Even if you can independently complete emergency maintenance with the guidance of this manual, notifyHuawei of the emergency. Then, Huawei technical personnel maintain records of the fault to improve after-sales services.

2.2.2 Collecting Fault Information

When an emergency occurs, collect and back up fault information in real time for reference.Then, provide the collected information to Huawei engineers for fault location and rectification.

For details about fault information collection, see the chapter "3.1 Guide to Collecting FaultInformation".

Recording Basic Fault Information

Collect the following basic information:

l Time when the fault occurs

l Detailed description of the fault

l Software version of the CX600

l Measures have been taken and the results

l Severity level of the problem and expected time of system recovery

Backing Up Fault Information

Back up the following information:

l Indicator status of the boards, power modules, and fans

l Alarm information

l Log information

l Configuration information

l Debugging information (if debugging is enabled)

2.2.3 Handling the Emergency

During emergency maintenance, follow the flow chart as shown in Figure 2-2 to verify the typeand range of the fault according to the method as shown in Table 2-1.



2-3

Figure 2-2 Flow chart of verifying the fault type

Start

Can log in throughthe consoleinterface?

System startsnormally?

Board status isnormal?

Interface status isnormal？

A service fault occurs A device fault occurs

No

No

No

No

Yes

Yes

Yes

Yes

Table 2-1 Method of verifying the fault type

Item Method

Login throughthe consoleinterface

Connect the serial interface of a PC or terminal to the console interface ofthe CX600 through the standard RS-232 configuration cable and setrelevant parameters on the terminal. For details, refer to the HUAWEICX600 Metro Services Platform Configuration Guide - BasicConfigurations.Check that a terminal display is provided.

System startup Check whether the system can be started normally and the commandprompt such as <HUAWEI> is displayed.

Board status Run the display device command on the terminal to check whether thestatus of all boards is Normal. In the case of a local fault, check the statusof the service board connected to the customer who reports the fault.

2 Flow of Emergency MaintenanceHUAWEI CX600 Metro Services Platform



Issue 01 (2011-05-30)

Item Method

Interface status Run the display interface command on the terminal to check whether thestatus of the interface connected to the customer who reports the fault isUp and whether the number of packets received on the interface increases.

After the fault type is verified, apply emergency maintenance according to the description in theChapter "3.2 Guide to Handling Emergencies".

l 3.2.1 Failed to Log in to the System Through the Serial Interfacel 3.2.2 Failed to Start the Systeml 3.2.3 Status of Hardware Components Is Abnormall 3.2.4 Interface Status Is Abnormal

2.2.4 Seeking Help

Seek Huawei technical support according to the contact information given in section "1.6Technical Support."

2.2.5 Checking the Handling Result

After services resume, check the device status, board indicators, and alarms to confirm that thesystem runs normally. Make a dialing test to prove that services are normal. For detailedoperations, refer to the HUAWEI CX600 Metro Services Platform - Routine Maintenance.

You are recommended to arrange technical personnel to monitor the system running during theservice peak time so that further problems can be handled immediately.

2.2.6 Recording Emergency Maintenance Information

Record emergency maintenance information, including the emergency maintenance time,version, fault symptom, handling procedures, and result, for a future query. For the format ofthe maintenance record information table, refer to Appendix A "4 Emergency MaintenanceRecord Table."



2-5

3 Emergency Maintenance Guidelines

About This Chapter

This chapter guides you how to perform emergency maintenance.

3.1 Guide to Collecting Fault InformationThis section guides you how to collect and back up fault information as the reference fortroubleshooting.

3.2 Guide to Handling EmergenciesThis section guides you how to handle emergencies.

3.3 Guide to Restarting a DeviceThis section guides you how to restart a device when a fault on the device causes services to beinterrupted and the device fails to restart automatically.

3.4 Built-in System Software Is Incorrect or Does Not ExistIncorrect or no system software was delivered along with the device. You need to copy thecorrect system software through cfcard2 (located on the panel of the MPU/SRU) or USB port.You can also load the system software through the BootROM.

HUAWEI CX600 Metro Services PlatformEmergency Maintenance 3 Emergency Maintenance Guidelines


3-1

3.1 Guide to Collecting Fault InformationThis section guides you how to collect and back up fault information as the reference fortroubleshooting.

When an emergency occurs, you need collect and back up fault information on time for reference.When seeking Huawei technical support, you need provide the collected information to Huaweiengineers for fault location and rectification.

When a fault occurs, collect the following information:

l Basic fault information

l Device fault information

3.1.1 Collecting Basic Fault InformationThis section describes what items need to be collected and how to collect basic fault information.

3.1.2 Collecting Device Fault InformationThis section describes what items need to be collected and how to collect the device faultinformation.

3.1.1 Collecting Basic Fault InformationThis section describes what items need to be collected and how to collect basic fault information.

Table 3-1 lists the basic fault information to be collected when a fault occurs.

Table 3-1 Basic fault information table

No. Item Collection Method

1 Occurrence time Record the time when the fault occurs. The value shouldbe accurate to a minute.

2 Fault symptom Collect the fault symptom and maintain detailed records.

3 Fault severity level Record the fault severity level according to the range andthe severity of the fault.

4 Software version Collect information about the software version on consolethrough the display version command when you can login to the device through Telnet or the serial interface.

5 Networkinginformation

Draw a networking diagram showing upstream anddownstream devices and the peer interfaces.

6 Taken measures Record the measures that have been taken and the results.

NOTE

When collecting fault information through command lines, you can copy the information displayed on theconsole, such as the serial interface or the Telnet terminal, and then attach it to a txt. file for a record.

3 Emergency Maintenance GuidelinesHUAWEI CX600 Metro Services Platform



Issue 01 (2011-05-30)

3.1.2 Collecting Device Fault InformationThis section describes what items need to be collected and how to collect the device faultinformation.

When a fault occurs and you can log in to the device through Telnet or the serial interface, collectthe following information.

Table 3-2 Fault information table


1 Device information Run the display device command to collect the deviceinformation.

2 Temperature Run the display temperature command to collect thetemperature information.

3 CPU usage Run the display cpu-usageslotslot-id command to collectthe CPU usage information.

4 Routing tableinformation

Run the display ip routing-table command to collect therouting table information.

5 Log information Run the display logbuffer command to collect the loginformation.

6 Alarm information Run the display trapbuffer command to collect the alarminformation.

7 Configurationinformation

Run the display current-configuration command tocollect the configuration information.

8 Diagnosticinformation

Run the display diagnostic-information file-namecommand to collect the diagnostic information.NOTE

By default, running the display diagnostic-information file-name command saves the device's diagnostic information to thefile with a specified filename in Cfcard:/.

9 Interface information Run the display interface command to collect theinterface information.

10 Network connectivityinformation

Run the ping command to collect information about thenetwork connectivity and record the results.

NOTE

When a device runs normally, you are recommended to back up the historical traps and logs in the CF cardthrough the Trivial File Transfer Protocol (TFTP) or File Transfer Protocol (FTP). For detailed operations,refer to the HUAWEI CX600 Metro Services Platform Configuration Guide - Basic Configuration.

3.2 Guide to Handling EmergenciesThis section guides you how to handle emergencies.



3-3

3.2.1 Failed to Log in to the System Through the Serial Interface

3.2.2 Failed to Start the System

3.2.3 Status of Hardware Components Is Abnormal

3.2.4 Interface Status Is Abnormal

3.2.1 Failed to Log in to the System Through the Serial Interface

Fault SymptomAfter the serial interface of a PC or a terminal is connected to the console interface of theCX600 through the standard RS-232 configuration cable and the relevant parameters are set,nothing is displayed on the terminal.

Fault Information CollectionIf you are unable to log in to the system through the serial interface, collect the followinginformation besides the generic information described in the Chapter "3.1 Guide to CollectingFault Information" for future reference.



1 Communicationsparameters of theserial interface

Check whether the communication parameters set for thesoftware such as Windows-based HyperTerminal for thecommunication between serial interfaces are consistentwith the communication parameters set on the consoleport of the CX600, such as the bard rate, data bit, paritycheck or not, stop bit, and flow control or not.

2 Indicator status Check the status of the following indicators:l RUN, ALM, LINK, and ACT indicators of the MPU/

SRUl PWR IN, PWR OUT, and ALM indicators of the

power modulesl RUN and ALM indicators of the fansNOTE

The indicators on the CX600-X1 and CX600-X2 series includethe STAT, ACT, USB, ETH LINK, and ETH ACT indicators onMPUs, the OUT and IN indicators on power modules, and theFAN indicators on fan modules.




Issue 01 (2011-05-30)

Processing Procedure

Figure 3-1 Flowchart of solving the problem that users cannot log in to a system through theserial interface

Start

Does the power module

work normally?

Is the cable ingood condition?

Are parameters for the

serial interfacecorrect?

Doesthe MPU/SRU work

normally?

Reset the system

No

No

No

No

Yes

Yes

Yes

Yes

Repair thepower supply

system

Replace thecable

Modify theparameters

Exchange orreplace theMPU/SRU

Is the faultrectified?





Seek technicalsupport

No

No

No

No

End

Yes

Yes

Yes

Yes

Yes

CAUTIONAll the following steps are performed only when the customer's services are already interrupted,and therefore have no adverse effect on services. If the customer's services are not interrupted,collect fault information and provide it to Huawei engineers for further processing.



3-5

ProcedureStep 1 Check and repair the power supply system.

When you find that the indicators of all the boards are off and all the fans fail to work (whichcan be identified by fan's rotating), or the indicator of the power module is abnormal, the powersupply system of the device is possibly faulty and need repairing. The power supply systemconsists of the following:

l Power supply system of the equipment room, chassis, or cabinetl Power modulel Power supply system of the backplane

You can solve the problem according to the steps:

1. Check whether the power module is switched on. When there are multiple power modules,ensure that at least one works normally.

2. Check whether the PWR IN indicator of the power module is on. If not, it can be concludedthat the power input of the power module is abnormal. You can use tools such as amultimeter to check the power supply of the equipment room, chassis, and cabinet. If thepower supply is abnormal, ask electricians for help.

NOTE

For the CX600-X1 and CX600-X2 series, check whether the IN indicators on power modules are on.

3. Check whether the PWR OUT indicator of the power module is on. If not, it can beconcluded that the power output of the power module is abnormal. You can replace thepower module to solve the problem.

4. Check whether the ALM indicator of the power module is on. If so, it can be concludedthat the power module is faulty. You can replace the power module to solve the problem.

NOTE

For CX600-X1 and CX600-X2 series, check whether the OUT indicators on power modules aresteady green. If the indicators are not steady green, the power modules are faulty. You can replacethe power modules to solve the problem.

5. When none of the preceding problems is found, but the power supply system fails to work,seek Huawei technical support according to 1.6 Technical Support.

Step 2 Check and replace the cable.Check whether the cable is in good condition. You can replace the cable with a new one to checkthat you can normally log in.

Step 3 Check parameters of the serial interface.

Check whether parameters set for the serial interface are identical with those for the consoleinterface on the CX600. If they are not identical, modify the parameters of the serial interface.

By default, set the baud rate of the console interface on the CX600 to 9600 bit/s, data bit to 8,stop bit to 8 1, and parity check and flow control to none. When the parameters of the consoleinterface are modified, adopt the modification.

Step 4 Exchange and replace the MPU/SRU.If the serial interface, cable, power supply system are normal, the problem may be caused bythe fault on the MPU/SRU. When two MPUs/SRUs are installed in the system, try to press andhold the OFL button for about 6s till the OFL indicator is on before removing a board. And insertthe terminal of the cable into the console port of the slave MPU/SRU; when there is only oneMPU/SRU, you can replace it with a spare one.




Issue 01 (2011-05-30)

NOTE

The MPUs on the CX600-X1 and CX600-X2 series do not have an OFL button. Before replacing an MPU,run the power off slot slot-id command in the system view to power off the MPU.

Step 5 Reset the system.If the fault persists after the preceding steps are performed, you can reset the system by switchingoff the power module and then switching it on three minutes later to solve the problem. Fordetails, see 3.3 Guide to Restarting a Device.

Step 6 Seek Huawei technical support.If the fault persists after the preceding steps are performed, you can seek Huawei technicalsupport according to "1.6 Technical Support."

----End

3.2.2 Failed to Start the System

Fault SymptomThe system is failed to be started and the prompt may be displayed on the terminal as follows:l "The SDRAM testing.........FAIL!", which indicates that the self-test of memory fails.l "XXXXX selftest.........FAIL!", which indicates that the self-test of a certain module fails.l The system remains in the phase of file decompression for a long time.l The system is repeatedly restarted.

Fault Information CollectionIf you are unable to start the system, collect the following information besides the genericinformation described in the chapter "3.1 Guide to Collecting Fault Information" for futurereference.



1 System startupinformation

Copy system startup information on the console such asthe serial interface or Telnet terminal to a .txt file forstorage.

2 Name of the startupfile

Check the name of the startup file through the Basic Input/Output System (BIOS) menu.



3-7


Figure 3-2 Flow chart of solving the problem that the system cannot be started

Start

Is the memory self-check failed?

Is the module self-check

failed?

Is the filedecompression

failed?

Is the system repeatedly

restarted?

Yes

No

Remove andinsert the

memory bar





Seek technicalsupport

No

No

No

No

End

Yes

Yes

Yes

Yes

Make thestartup files ofthe master andslave MPUs/

SRUs identical

Replace thememory bar

Debug andreplace theMPU/SRU

Re-upload thestartup file

through BIOS

No

No


No

Yes

Yes

Is the power module work

normally?

Yes

No Repair thepower supply

system


Yes

Yes

No

Yes

No

CAUTIONAll the following steps are performed only when the customer's services are already interrupted,and therefore have no adverse effect on services. If the customer's services are not interrupted,do not perform the following steps. Instead, collect fault information and feed it back to Huaweiengineers for further processing.




Issue 01 (2011-05-30)

Procedure

Step 1 Check and repair the power supply system.

When you find that the indicators of all the boards are off and all the fans fail to work (whichcan be identified by fan's rotating), or the indicator of the power module is abnormal, the powersupply system of the device is possibly faulty and need repairing. The power supply systemconsists of the following:

l Power supply system of the equipment room, chassis, or cabinet

l Power module

l Power supply system of the backplane




NOTE

For the CX600-X1 and CX600-X2 series, check whether the IN indicators on power modules are on.



NOTE

For CX600-X1 and CX600-X2 series, check whether the OUT indicators on power modules aresteady green. If the indicators are not steady green, the power modules are faulty. You can replacethe power modules to solve the problem.


Step 2 Insert and remove the memory bar.When the system displays "The SDRAM testing.........FAIL!", the memory bar is possibly looseor is incorrectly inserted (only when there is a single memory bar). You can try the followingoperations to solve the problem:

NOTE

There no memory bars on the CX600-X1 and CX600-X2 series, Step 2 and Step 3 do not need to be checked.

1. Remove the MPU/SRU.

2. Remove the memory bar and then re-install it. When there is only one memory bar, checkwhether it is inserted in slot 1. If so, remove it and then insert it in slot 0.

NOTE

Figure 3-3 shows how the memory bar slots on an MPU/SRU are numbered. When two memorybars are inserted on the MPU/SRU, the slot where the upper memory bar is inserted is numbered 0and the slot where the lower memory bar is inserted is numbered 1.



3-9

Figure 3-3 Memory bar slots on an MPU/SRU

3. Re-insert the MPU/SRU.

Step 3 Replace the memory bar.If the problem cannot be solved by removing and re-insertion of the memory bar, the memorybar is possibly faulty. You can replace the memory bar with a new one of the same specification.For the type and specification of memory bars, contact Huawei technical support personnel.

Step 4 Exchange and replace the MPU/SRU.When the system prompts "XX XXX selftest.........FAIL!", or the memory self-test still failsafter you perform Steps 1 and 2, the MPU/SRU is possibly faulty. When two MPUs/SRUs areinstalled in the system, try to press and hold the OFL button for about 6s till the OFL indicatoris on before removing a board. And insert the terminal of the cable into the console port of theslave MPU/SRU; when there is only one MPU/SRU, you can replace it with a spare one.

NOTE

The MPUs on the CX600-X1 and CX600-X2 series do not have an OFL button. Before replacing an MPU,run the power off slot slot-id command in the system view to power off the MPU.

Step 5 Upload the startup file through BIOS again.When the system remains in the phase of file decompression or is repeatedly restarted, the startupfile is possibly incorrect or damaged. You can try to upload the startup file through BIOS.

It is complicated to upload the startup file through BIOS. Contact Huawei technical supportpersonnel and perform the uploading under their guidance. For detailed operation procedures,refer to Appendix B "3.4 Built-in System Software Is Incorrect or Does Not Exist."

Step 6 Seek Huawei technical support.Seek Huawei technical support according to "1.6 Technical Support."

----End

3.2.3 Status of Hardware Components Is Abnormal




Issue 01 (2011-05-30)

Fault SymptomHardware components refer to hardware modules including board modules, power supplymodules, and fan modules. The abnormality of hardware component status includes (one ormultiple items):l When you run the display device command in any view to view information about a

hardware component where services are interrupted, the hardware component status isAbnormal.

l When you run the display device command in any view to view information about ahardware component where services are interrupted, the hardware component status isUnregistered.

l The RUN or STATUS indicator of a hardware component blinks or is off, or the ALMindicator of the hardware component is on.

l The hardware component where services are interrupted is repeatedly restarted.

NOTEGenerally, if the indicator blinks once every 2s (0.5 Hz), the LPU is in the normal state. If the indicatorblinks twice every 1s (2 Hz), the LPU is in the alarm state. For details, please refer to HUAWEICX600 CX device- Hardware Description.

Fault Information CollectionWhen you find that the status of the hardware component is abnormal, collect the followinginformation besides the generic information described in the Chapter "3.1 Guide to CollectingFault Information" for future reference.



1 Indicator status of ahardware component

Check that the status of the indicator on a hardwarecomponent is off, on, blinking quickly, or blinking slowly.Observe whether the RUN and ALARM indicators of thefan modules and power supply modules are normal.Normally, the RUN indicator is green and the ALARMindicator is off.

2 Detailed informationabout a hardwarecomponent

Run the display device slot-id command in any view toview detailed information about the specified hardwarecomponent.

3 Status of a PICchannel

Run the display device pic-status command in any viewto collect information about the status of a PIC channel.



3-11


Figure 3-4 Flow chart of solving the problem that the hardware component status is abnormal

Reset the component

Start

Is the fault rectified?

Yes

No

Cut over the services on the board and seek

technical support

Replace the component

Is the fault rectified?

End

No

Yes


Procedure

Step 1 Reset the hardware component.

The processing of the hardware component abnormality is complex.

When you find that the indicators of all the boards are off and all the fans fail to work (whichcan be identified by fan's rotating), or the ALM indicator of the power module is on, the powersupply system of the device is possibly faulty and need repairing. The power supply systemconsists of the following:

l Power supply system of the equipment room, chassis, or cabinetl Power modulel Power supply system of the backplane





Issue 01 (2011-05-30)






If the abnormality occurs on the fan modules, directly replace the fan modules.

If a board is abnormal and the situation is urgent, reset and replace the board. Relevant causelocation will be performed by Huawei technical support personnel.

You can reset a board by using the reset slot slot-id command in the user view, pressing theRESET button on the panel, or pulling out and inserting the board.

NOTE

You are recommended not to pull out and insert in the board for resetting. This can avoid damages on theboard.

Step 2 Replace the hardware component.When the problem cannot be solved by resetting the hardware component, you can try to replacethe hardware component with a spare one.

Step 3 Cut over services on the board and seek Huawei technical support.When the preceding methods cannot solve the problem, you can cut over services on the faultyboard to a normal board or a board in an idle slot. For operation details, contact Huawei technicalsupport personnel or comply with your cutover scheme.

In addition, report the fault information to the local Huawei office for technical support.

----End

3.2.4 Interface Status Is Abnormal

Fault SymptomThe abnormality of the interface status includes:l When the display interface [ interface-type interface-number ] command is run in any

view to check an interface where services are interrupted, the interface status is Down.l When the display interface [ interface-type interface-number ] command is run in any

view to check an interface where services are interrupted, the number of packets transmittedon the interface remains unchanged.

l When the display interface [ interface-type interface-number ] command is run in anyview to check the interface where services are interrupted, a large number of CRC packetsare received.



3-13

l The indicator status of an interface is abnormal. For example, the LINK indicator of theinterface is off.

Fault Information CollectionWhen you find the interface status is abnormal, collect the following information besides thegeneric information described in the chapter "3.1 Guide to Collecting Fault Information" forfuture reference.



1 Indicator status of aninterface

Check whether the indicator (LINK/ACT) on a faultyinterface is off, on, or blinking. If the indicator is on, thelink is Up. If the indicator is blinking, the data is beingreceive or transmit. If the indicator is off, the link is Down.

2 Detailed informationabout an interface

Run the display interface [ interface-type interface-number ] command in any view to collect detailedinformation about an interface.

3 Brief IP-relatedinformation about aninterface

Run the display ip interface brief [ interface-typeinterface-number ] command in any view to collect briefIP-related information about an interface.

4 Brief informationabout all interfaces

Run the display interface brief command in any view tocollect brief information about all interfaces.




Issue 01 (2011-05-30)


Figure 3-5 Flow chart of solving the problem that the interface status is abnormal

Start

Statusof interface

indicatornormal?

Interfacestatusis Up?

Packets aretranseivednormally?

Yes

No

Yes

No

Faultrectified?

Reset theinterface

Proceed to theflow for handling

service faults

Detect the link Faultrectified?

Shut up theinterface

Performa local

loopback test

Is the statusnormal?

Check and modify theconfiguration of thedata link layer or theupper layer protocol

Is manuallyshut down?

End

No

Yes

EndYes

Cut overtheservices

on theboard andseek boardand seeksupport

NoNo

Yes

No

Yes

Yes

No




3-15

NOTEUsually, the interface fault is caused by the problem of the cable or optical module.

l When the cable is broken or the optical module is damaged, the interface fails to go Up.

l When the cable or optical module on an interface has been being used for many years, the signalattenuation may be severe. In this case, although the interface is Up, a large number of packets arediscarded.

Replace the cable or optical module on the faulty interface. If the problem persists, perform the followingoperations.

Procedure

Step 1 Start the interface manually.Run the display this in the interface view to check the configuration files of the faulty interface.When you find that an interface is shut down through the shutdown command, run the undoshutdown command in the interface view to start it.

Step 2 Check the link and rectify the link fault.Before checking a link, check whether the LINK indicator of the interface is on.

If so, it indicates that the physical link is Up and you can detect the link as follows:

1. Run the display this interface command in the interface view to check whether theinterface parameters at both ends of the link are identical, such as the duplex mode and rate.

2. In the case of optical interfaces, use the optical power meter to check whether the receivingand sending optical signals at both ends are normal. If it is not convenient to use the opticalpower meter, you can use the optical power detecting function in the optical module: rundisplay this interface in the error interface and compare the parameters in the displayinformation with the optical module parameters, and check whether the power of the sendor receive optical signals are in normal range. If optical interfaces only send or receiveoptical signals, the optical module is possibly faulty or the optical fiber does not match theoptical module. Then, you can try to replace the optical module or the optical fiber.

3. If the interface is an electric interface, observe the pinouts in the RJ-45 connectors on bothends of the case to check whether the cable should be straight-through or crossover cablefor the specified interface.

DANGERWhen you check the receiving and sending of optical signals, do not look into the optical fiberwithout eye protection. You must use the optical power meter to measure the optical power.

When the LINK indicator of the interface is off, you can check the link as follows:

1. Perform a physical loopback test on the device. That is, connect the faulty interface to aninterface is in the normal state through an optical fiber or cable in good condition. Payattention to the two interfaces' type should match with each other.

2. If the LINK indicator is on, it indicates that the interface is normally. In this situation, youneed to check whether the optical fiber or cable is damaged and the trunk link runs normally.Usually, you need to check the optical fibers, cables, and trunk links at the neighboringsites.




Issue 01 (2011-05-30)

3. If the LINK indicator is off, it indicates that the interface hardware is faulty. When apluggable optical module is used, you can replace the optical module; otherwise, cut overservices on the faulty interface to other interfaces in the normal state.

Step 3 Conduct a local loopback test.When the interface status is Up, but the number of packets transmitted on the interface remainsunchanged during a specified period, it indicates that the interface can neither receive nor sendany packets. In this situation, you can run the loopback local command on the interface toperform a local loopback test and then run the ping command to initiate a data transmission testto check whether the number of packets changes. After the local loopback test is complete, runthe undo loopback command to disable the local loopback.

NOTE

The procedures of testing the receiving and sending of packets through the ping command in Ethernetinterfaces are as follows:

1. Run the arp static ip-address mac-address command in the system view to construct an IP address onthe same segment with the faulty interface and a MAC address in the local ARP table. You can selectthe MAC address at will, but it cannot be the local MAC address, a broadcast or multicast address. Thefeature of broadcast or multicast address is: the 8th bit of MAC address is 1.

2. Run the ping command in the view of the faulty interface ( it does not matter that ping succeed orfailed. ) to send a certain number of ping packets to the constructed IP address.

3. Run the display this interface command in the view of the faulty interface to check whether the numberof received and sends packets are correct. Because the ARP is just configured, the first ping may discarda few packets. Ping for the second time, the number of received and sent packets will equal. If so, thelocal loopback test is successful and this indicates that the local interface is normal.

4. Run undo arp static command to delete the MAC address, and run undo loopback command in theinterface view to disable the local loopback.

Above operation can only location interface faulty. If the interface is OK, maybe the optical module isfaulty. You can location optical module faulty as follows: connect the RX and TX ports of optical modulewith two ends of an optical fiber, and run undo shutdown in interface view to test the receiving and sendingof packets again.

Step 4 Check and modify the data link layer or upper layer protocol.If the interface still fails to send and receive packets in the local loopback test, check the datalink layer or upper layer protocol. For example, check whether the Point-to-Point Protocol (PPP)or the High level Data Link Control (HDLC) protocol at both ends are identical and the routingprotocol runs normally.

Step 5 Reset the interface.If the fault persists after the preceding steps are performed, you can reset the interface to solvethe problem.

Run the shutdown command to disable the interface, and then run the undo shutdown commandto enable the interface to reset the interface.

Step 6 Seek Huawei technical support.Seek Huawei technical support according to 1.6 Technical Support.

----End

3.3 Guide to Restarting a DeviceThis section guides you how to restart a device when a fault on the device causes services to beinterrupted and the device fails to restart automatically.



3-17

CAUTIONl Restart the CX600 with caution. If it is required to restart the CX600, go over the principles

and precautions described in Chapter 1, or perform the restart operation under the guidanceof Huawei technical personnel.

l Before the CX600 is successfully restarted, all services on the CX600 are interrupted unlessthe dual-system hot backup networking is adopted.

When a critical fault occurs on the CX600 during the equipment running, the CX600 isautomatically restarted. After the restart, the CX600 runs normally. The CX600 needs to berestarted manually only in emergency or exception, for example, services are interrupted becauseof the fault occurred on the CX600, and the CX600 fails to automatically restart or recover byusing other methods.

3.3.1 Preparations for the RestartThis section describes the preparations for the restart of the CX600.

3.3.2 Guide to Restarting the CX600This section describes procedures and precautions of restarting the CX600.

3.3.3 Verification After the RestartThis section describes how to verify the device after the restart.

3.3.4 Solution to the Restart FailureThis section describes how to handle the failure in the restart of the CX600.

3.3.1 Preparations for the RestartThis section describes the preparations for the restart of the CX600.

Before restarting the CX600, confirm whether configuration files of the CX600 need to bebacked up. Configuration files should be backed up and executed automatically after the restart.In this case, services can be automatically resumed.

For the backup and restoration of configuration files, refer to "Guide to Emergency Maintenance"in the Chapter HUAWEI CX600 Metro Services Platform - Routine Maintenance.

3.3.2 Guide to Restarting the CX600This section describes procedures and precautions of restarting the CX600.

CAUTIONThe MPU/SRU is not hot swappable. Therefore, do not plug out and plug in the MPU/SRU inservice. Boards of other types are hot swappable.

You can restart the CX600 in any of the following methods:l Running the reboot commandl Running the schedule reboot commandl Switching the system off and then on




Issue 01 (2011-05-30)

l Operating through the NMS

NOTE

You are recommended not to restart the CX600 remotely. Otherwise, once the restart operation fails,services may be interrupted for a long period.

Checking Whether Configuration Files Are Correct

Run the display startup command to check whether configuration files are correct. For example:

<HUAWEI> display startupMainBoard: Configed startup system software: cfcard:/V600R003C00.cc Startup system software: cfcard:/V600R003C00.cc Next startup system software: cfcard:/V600R003C00.cc Startup saved-configuration file: cfcard:/vrpcfg.zip Next startup saved-configuration file: cfcard:/vrpcfg.zip Startup paf file: cfcard:/paf.txt Next startup paf file: cfcard:/paf_V600R003C00.txt Startup license file: cfcard:/license.txt Next startup license file: cfcard:/license_V600R003C00.txt Startup patch package: NULL Next startup patch package: NULL SlaveBoard: Configed startup system software: cfcard:/V600R003C00.cc Startup system software: cfcard:/V600R003C00.cc Next startup system software: cfcard:/V600R003C00.cc Startup saved-configuration file: cfcard:/vrpcfg.zip Next startup saved-configuration file: cfcard:/vrpcfg.zip Startup paf file: cfcard:/paf.txt Next startup paf file: cfcard:/paf_V600R003C00.txt Startup license file: cfcard:/license.txt Next startup license file: cfcard:/license_V600R003C00.txt Startup patch package: NULL Next startup patch package: NULL

The displayed "vrpcfg.zip" denotes the name of the current configuration file.

Running the reboot Command

Before manually restart CX600, run the reboot command on the configuration terminal.

Enter the reboot command in the user view and press Y after the display to restart the CX600.The operation example is as follows:

<HUAWEI> rebootMaster mpu:Next startup system software: cfcard:/V600R003C00.ccPaf: V600R003C00License: V600R003C00Next startup saved-configuration file: cfcard:/vrpcfg.zipSlave mpu:Next startup system software: cfcard:/V600R003C00.ccPaf: V600R003C00License: V600R003C00Next startup saved-configuration file: cfcard:/vrpcfg.zip

Info:The system is now comparing the configuration, please wait.Info:Save current configuration?[Y/N]:



3-19

NOTE

The reboot command output varies with system versions. Take the command output of the current systemversion as the standard.

Running the schedule reboot CommandThe schedule reboot command is run in the user view and has two modes, namely, schedulereboot delay and schedule reboot at.l The schedule reboot delay command is used to enable the scheduled reboot function and

set the wait delay for the CX600.The wait delay set for the scheduled restart of the CX600 can be expressed in two formats:"hour: minute" and "absolute minutes". The total minutes cannot be greater than 30 x 24 x60 minutes.

l The schedule reboot at command is used to enable the scheduled restart function and setthe specific restart date and time for the CX600. Note that the specified date cannot be 30days later than the current date.If the schedule reboot at command sets a specific date (yyyy/mm/dd) and the date is afuture date, the CX600 is restarted at the set time and the error is within 1 minute. If nospecific date is set, the following situations occur:– If the set time is later than the current time, the CX device is restarted at this time that

day.– If the set time is earlier than the current time, the CX device is restarted at this time the

next day.

After the schedule reboot delay or schedule reboot at command is run, the system promptsyou to confirm the restart. Enter Y or y, and the configuration takes effect. If the relatedconfiguration exists, the latest configuration overrides the previous one.

NOTE

If you adjust the system time through the clock command after running the schedule reboot delay orschedule reboot at command, the parameter set through the schedule reboot delay or schedule rebootat command becomes invalid.

You can run the undo schedule reboot command to remove the parameter set through theschedule reboot delay or schedule reboot at command.

You can run the display schedule reboot command to view the parameter set through theschedule reboot delay or schedule reboot at command.

Operating Through the NMSOperation for restarting CX600 differ from different type of NMS. For detail, refer to the NMSOnline Help.

3.3.3 Verification After the RestartThis section describes how to verify the device after the restart.




Issue 01 (2011-05-30)

CAUTIONAfter the CX600 is restarted, check that the configuration data is recovered correctly andcompletely. The loss of configuration data will result in the service interruption and you aretherefore required to manually add the configuration data and save it.

Verifying the Restart InformationIf you log in to the CX600 through the console interface and restart the CX600 by running thereboot command, the display on the configuration terminal after the restart is as follows:<HUAWEI> rebootmpu 9:Next startup system software: cfcard:/V600R003C00.ccPaf: V600R003C00License: V600R003C00Next startup saved-configuration file: cfcard:/vrpcfg.zipInfo:The system is now comparing the configuration, please wait.Warning: All the configuration will be saved to the configuration file for the next startup:cfcard:/vrpcfg.zip, Continue?[Y/N]:yNow saving the current configuration to the slot 9 ..Save the configuration successfully. System will reboot! Continue?[Y/N]:y ************************************************************** Copyright 2000-2009 Huawei Tech. Co., Ltd. **************************************************************Board Name ....................................... CR52SRUASDRAM Size ....................................... 1024MBEnable the instruction cache ..................... pass!Disable the data cache ........................... pass!Disable the ECC................................... pass!The sdram data bus walk 1 testing ................ pass!The sdram data bus walk 0 testing ................ pass!The sdram address bus walk 1 testing ............. pass!The sdram address bus walk 0 testing ............. pass!Press CTRL+T to start sdram full test in 01 seconds!The SDRAM ECC initializing ....................... pass!Now begin to initialize systemCache library initializing........................ pass!Exception vectors initializing.................... pass!The host bridge initializing...................... pass!Page table initializing........................... pass!CPU initializing.................................. pass!Console device initializing....................... pass!PCI scanning...................................... pass!L2 cache initializing............................. pass!Wind kernel configuration initializing............ pass!Instruction cache initializing.................... pass!Data cache initializing........................... pass!MMU initializing.................................. pass!System clock initializing......................... pass!I/O and file system initializing.................. pass!TTY devices creating and initializing............. pass!Standard input/output/error device setting........ pass!Exception show routines initializing.............. pass!Exception handling installing..................... pass!Log task initializing............................. pass!WDT starting...................................... pass!PHYs resetting.................................... pass!MUX devices initializing.......................... pass!Now begin to test key chipsThe serial port testing .......................... pass!The bridge register testing ...................... pass!The bridge internal sram(256K Bytes) testing ..... pass!The epld1 testing ................................ pass!



3-21

The epld2 testing ................................ pass!The main boot ROM and backup boot ROM comparing .. pass!The boot ROM testing ............................. pass!The battery testing .............................. pass!Press CTRL+T to start sdram full test in 2 seconds!The slot ID testing .............................. pass!Starting...Uncompressing..................Done!Starting at 0x1600000...CLOCK_REALTIME(yyyy/mm/dd - hh:mm:ss) is: 2007/11/14 - 11:22:21Start file system check...cfcard:/ - Volume is OKcfcard2:/ - Volume is OKcfcard2:/ - Volume is OK **************************************************** * * * 8090 boot ROM, Ver 204.00 * * * **************************************************** Copyright 2001-2009 Huawei Tech. Co., Ltd. Creation date: Oct 31 2007, 11:29:00 CPU type : MPC7447 CPU L2 Cache : 512KB CPU Core Frequency : 1GHz BUS Frequency : 133MHzPress Ctrl+B to enter Main Menu... 0Auto-booting...Booting from CFcard...The start file is cfcard:/V600R003C00.ccThe config file is cfcard:/vrpcfg.zipThe paf file is cfcard:/paf_V600R003C00.txtThe license file is cfcard:/license_V600R003C00.txtLoading.......// Omitted. Information note: ModuNo = 0xd0000, InfoType = 1, InfoNo = 0Recover configuration...OK!Press ENTER to get started.

The preceding display shows that the device is restarted successfully. You can press Enter andenter the user view.

Checking Whether the Software Version Is CorrectRun the display version command to check whether the software version is correct. For example:

<HUAWEI> display versionHuawei Versatile Routing Platform Software VRP (R) software, Version VRP 5.90 (CX600 V600R003C00) Copyright (C) 2000-2009 Huawei Technologies Co., Ltd HUAWEI CX600 uptime is 0 day, 1 hour, 44 minutes......

The preceding command output shows the Versatile Routing Platform (VRP) version, hostversion, and patch version. You can check whether the version number before and after therestart is identical.

Checking Whether Configuration Files Are CorrectRun the display startup command to check whether configuration files are correct. For example:

<HUAWEI> display startupMainBoard: Configed startup system software: cfcard:/V600R003C00.cc Startup system software: cfcard:/V600R003C00.cc Next startup system software: cfcard:/V600R003C00.cc




Issue 01 (2011-05-30)

Startup saved-configuration file: cfcard:/vrpcfg.zip Next startup saved-configuration file: cfcard:/vrpcfg.zip Startup paf file: cfcard:/paf.txt Next startup paf file: cfcard:/paf_V600R003C00.txt Startup license file: cfcard:/license.txt Next startup license file: cfcard:/license_V600R003C00.txt Startup patch package: NULL Next startup patch package: NULL SlaveBoard: Configed startup system software: cfcard:/V600R003C00.cc Startup system software: cfcard:/V600R003C00.cc Next startup system software: cfcard:/V600R003C00.cc Startup saved-configuration file: cfcard:/vrpcfg.zip Next startup saved-configuration file: cfcard:/vrpcfg.zip Startup paf file: cfcard:/paf.txt Next startup paf file: cfcard:/paf_V600R003C00.txt Startup license file: cfcard:/license.txt Next startup license file: cfcard:/license_V600R003C00.txt Startup patch package: NULL Next startup patch package: NULL

The displayed "vrpcfg.zip" denotes the name of the current configuration file.

3.3.4 Solution to the Restart FailureThis section describes how to handle the failure in the restart of the CX600.

If the system fails to be upgraded, to ensure that the CX600 operates normally, you need to rollback the version. For the rollback procedures, see the Upgrade Guide.

If any problem arises during the restart of the CX600, contact the local Huawei technical supportpersonnel.

3.4 Built-in System Software Is Incorrect or Does Not ExistIncorrect or no system software was delivered along with the device. You need to copy thecorrect system software through cfcard2 (located on the panel of the MPU/SRU) or USB port.You can also load the system software through the BootROM.

3.4.1 Loading the System Software Through the BootROMIntroduction to uploading the systems software through the network management interface andloading the system software through the BootROM.

3.4.2 Loading the System Software Through the CF Card/USB PortIntroduction the method of loading the system software through the CF Card/USB port of CXdevice.

3.4.1 Loading the System Software Through the BootROMIntroduction to uploading the systems software through the network management interface andloading the system software through the BootROM.

ContextTo upgrade the system through the BIOS, you have to adopt the File Transfer Protocol (FTP)or Trivial File Transfer Protocol (TFTP) client mode. The operation terminal (PC) must be



3-23

connected to the CX device through the serial interface and communicate with the CX devicethrough HyperTerminal.

Procedure

Step 1 Connect the console interface of the MPU/SRU of the CX600 to be upgraded to the COMinterface of the PC and configure the HyperTerminal.

One PC can function as both the FTP server and the terminal.

For instructions on how to configure the HyperTerminal, it is assumed that the operating systemis Windows XP.

1. Choose Start > Programs > Accessories > Communications > HyperTerminal. Then,in the window that is displayed, enter a name for the connection, for example, COMM1.

Figure 3-6 interface of connection 1

2. Click OK. The following window is displayed. In the Connecting using drop-down list,choose COM interfaces.




Issue 01 (2011-05-30)


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.


Then, click OK to complete the HyperTerminal configuration.



3-25

The terminal displays the device prompt CX600, indicating that the device is ready forlogin.

Step 2 Connect the MGMT-ETH interface on the master MPU/SRU of the CX600 to the networkmanagement interface on the PC. Then, run the FTP server program on the PC and create anFTP user.

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

Set parameters of the FTP server program, including the home directory, user name, andpassword, as shown in Figure 3-9.

Figure 3-9 Configuring FTP parameters

Step 3 Restart the CX600. The HyperTerminal interface displays the following product information:*********************************************************** * Copyright 2001-2009 Huawei Tech. Co., Ltd. * *********************************************************** BOARD TYPE ....................................... CR56RPUASDRAM Size ....................................... 3584MBSDRAM ECC initializing ........................... pass!Memory Test ...................................... pass!Press CTRL+T for full memory test ................ skip! Cache library initializing........................ pass! Exception vectors initializing.................... pass! Usr kernel initializing........................... pass! Instruction cache initializing.................... pass! Data cache initializing........................... pass! Usr kernel core initializing...................... pass! Memory pool initializing.......................... pass!I/O and file system initializing.................. pass! Console driver initializing....................... pass! Stdio set ........................................ pass! Pipe driver installing............................ pass! Exception show routines initializing.............. pass! Exception initializing............................ pass! Initializing Flash Module......................... pass! Start small boot from bootrom... Starting...Uncompressing...Done!CLOCK_REALTIME(yyyy/mm/dd - hh:mm:ss) is: 2009/08/20 - 20:08:52ADAPT FPGA load................................. OKStart file system check...CFCARD FPGA load................................ OKpFd->pVolDesc->devHdr.name = cfcard:.




Issue 01 (2011-05-30)

pVolDesc->devHdr.name = cfcard:.cfcard:/ - Volume is OKpFd->pVolDesc->devHdr.name = cfcard2:. pVolDesc->devHdr.name = cfcard2:.cfcard2:/ - Volume is OKUSB Host Controller initializing..............pass! **************************************************** * * * 8090 boot ROM, Ver 02.25 * * * **************************************************** Copyright 2001-2009 Huawei Tech. Co., Ltd. Creation date: Aug 16 2009, 20:07:04 CPU type : MPC8572E - Security EnginePress Ctrl+B to enter Main Menu... 0 *

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

Step 4 At the prompt of Press Ctrl+B to enter Main Menu... 3, press Ctrl+B within three seconds.password:

Step 5 Enter the password for entering the big BootROM menu.NOTEThe default password is 8090. You can change the password by selecting 6. Modify boot ROMpassword in the big BootROM menu.

Main Menu(bootload ver: 02.25)

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. List file in USB Device 10. Set patch mode 11. Set version back signal 12. Reboot Enter 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 change the boot parameters.Note: 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 : motetsec0 processor number : 0 host name : host \\This parameter does not need to be configured.file name : V600R003C00.cc \\Enter the name of the system software on the FTP server.



3-27

inet on ethernet (e) : 1.1.1.100:FFFFFF00 \\Configure an IP address and mask that can be used f or communication with the FTP server.inet on backplane (b): \\This is the backup interface for connection with the FTP server. You can choose not to configure this.host inet (h) : 1.1.1.2 \\This is the IP address of the FTP server. gateway inet (g) \\This is the gateway used for communication with the FTP server. You can configure this as required.user (u) : 8090 \\This is the name of an existing FTP user.ftp password (pw) (blank = use rsh): 8090 \\This is the password of the FTP user.flags (f) : 0x0 \\Choose to upgrade the system software by means of FTP or TFTP. The default upgrade method is FTP. In this upgrade instance, the FTP server is adopted, and you do not have to change the parameter 0x0.

NOTETo choose the TFTP method, change the parameter to 0x80.

target name (tn) \\This parameter does not need to be configured.startup script (s) \\This parameter does not need to be configured.other (o) : \\This parameter does not need to be configured.

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 systemsoftware 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 : mgi \\You can set the parameter to motetsec0 for the MPUC/SRUC, mottsec3 for the MPUD.

unit number : 2processor number : 0host name : hostfile name : V600R003C00.ccinet on ethernet (e) : 1.1.1.100:FFFFFF00host inet (h) : 1.1.1.3user (u) : 8090ftp password (pw) : 8090flags (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.




Issue 01 (2011-05-30)

Step 9 Select 4. Return to main menu. The system returns to the big BootROM menu.Main Menu(bootload ver: 02.25)

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. List file in USB Device 10. Set patch mode 11. Set version back signal 12. RebootEnter your choice(1-11):5

Step 10 Select 5. Set boot file and path to configure the startup system software. 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 change the startup system software.boot file is cfcard:/ V600R003C00.cc, modify the file name if needed.Please input correctly, e.g.: cfcard:/V200R001B019.cc cfcard:/V600R003C00.cc\\Enter the name of the system software that has just been loaded. The absolute path must be used.The file name you input is cfcard:/ V600R003C00.cc.Are you sure? Yes or No(Y/N)y

After changing the startup system software, select 1 Modify the boot file to check the result. Boot Files Submenu


Enter your choice(1-7): 1 boot file is cfcard:/ V600R003C00.cc, modify the file name if needed. Please input correctly, e.g.: cfcard:/V200R001B019.cc

NOTEThe method of specifying the PAF, License, and configuration file is the same, 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!



3-29

Boot Files Submenu


Enter your choice(1-7):7

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

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. List file in USB Device 10. Set patch mode 11. Set version back signal 12. Reboot

Enter your choice(1-11):

Step 14 Uploading the system software of the slave MPU/SRU.

CAUTIONThe version of the slave MPU/SRU must be the same as the version of the master MPU/SRU.Otherwise, the slave MPU/SRU keeps restarting when the device is started.

Plug the console cable to the console interface of the slave MPU/SRU, and plug the networkmanagement cable to the MTMG-ETH interface on the slave MPU/SRU. Then, restart theCX600. The loading process is the same as that with the master MPU/SRU.

Step 15 After the system software is loaded to the slave MPU/SRU, plug the console cable to the consoleinterface on the master MPU/SRU and enter the big BootROM menu. Then, select 2. Boot fromCfcard to start the CX600 from the CF card. The setting process is the same as that with theslave MPU/SRU.

NOTEIf no slave MPU/SRU exists on the CX600, you can skip Step 14 and directly restart the CX600.

Booting from CFcard Be sure the baudrate be 9600bps!^@ The start file is cfcard:/ V600R003C00.cc The config file is cfcard:/vrpcfg1.zip The paf file is cfcard:/paf_V600R003C00.txt The license file is cfcard:/license_V600R003C00.txtLoading................................................................................................................................................................................................................................................................................................................................................................Done!




Issue 01 (2011-05-30)

Took time : 23sBSP_UpgradeBootLoad :Clear version back signal...Done! Update main boot ROM... Writing data to boot ROM...Took time : 8sDone![sysToMonitor] reboot ... *********************************************************** * Copyright 2001-2009 Huawei Tech. Co., Ltd. * *********************************************************** BOARD TYPE ....................................... CR56RPUASDRAM Size ....................................... 3584MBSDRAM ECC initializing ........................... pass!Memory Test ...................................... pass!Press CTRL+T for full memory test ................ skip! Cache library initializing........................ pass! Exception vectors initializing.................... pass! Usr kernel initializing........................... pass! Instruction cache initializing.................... pass! Data cache initializing........................... pass! Usr kernel core initializing...................... pass! Memory pool initializing.......................... pass!I/O and file system initializing.................. pass! Console driver initializing....................... pass! Stdio set ........................................ pass! Pipe driver installing............................ pass! Exception show routines initializing.............. pass! Exception initializing............................ pass! Initializing Flash Module......................... pass! Start small boot from bootrom... Starting...Uncompressing...Done!Copy boot ROM main system to flash...OK! CLOCK_REALTIME(yyyy/mm/dd - hh:mm:ss) is: 2009/08/20 - 20:46:42ADAPT FPGA load................................. OKStart file system check...CFCARD FPGA load................................ OKpFd->pVolDesc->devHdr.name = cfcard:. pVolDesc->devHdr.name = cfcard:.cfcard:/ - Volume is OKpFd->pVolDesc->devHdr.name = cfcard2:. pVolDesc->devHdr.name = cfcard2:.cfcard2:/ - Volume is OKUSB Host Controller initializing..............pass! **************************************************** * * * 8090 boot ROM, Ver 02.25 * * * **************************************************** Copyright 2001-2009 Huawei Tech. Co., Ltd. Creation date: Aug 4 2009, 22:29:56 CPU type : MPC8572E - Security Engine

Press Ctrl+B to enter Main Menu... Auto-booting...

Step 16 Auto-booting...Verify the upgrade.<HUAWEI> check version startupInfo: Software version match Ok!

The prompt Software version match Ok! indicates that the upgrade is successful. Otherwise,you need to perform the upgrade again.

----End



3-31

3.4.2 Loading the System Software Through the CF Card/USB PortIntroduction the method of loading the system software through the CF Card/USB port of CXdevice.

ContextThe method of loading the system software through the CF card/USB port is used mainly duringthe engineering stage or troubleshooting process. Before loading the system software throughthe CF card/USB port, prepare two CF cards or two USB devices. If there are two CF cards onthe MPUB (SRUA), do as follows to load the system software. Replace the CF cards on thepanels of the master MPU/SRU and slave MPU/SRU with these new CF cards. With this method,you do not have to pull out the MPU/SRU.

Procedure

Step 1 Connect the two new CF cards (cfard2s) to the PC using a card reader, and set up a file namedstartup on each of the two new CF cards.

Step 2 Copy the next startup files to the directory cfcard2:/startup. Operation on two cfcard2s are thesame.

The rebooting files should be named as following:l System software: ends with .cc.l Config file: contains vrpcfg, and ends with .cfg or .zip.l License file: contains license, and ends with .txt.l PAF file: contains paf, and ends with .txt.l GTL license file: ends with .dat.

Step 3 Power off the device, and then replace the CF cards on the master and slave MPU/SRU with thetwo new CF cards having the startup files.

Step 4 Power on the device. The device automatically copies the startup files from the directorycfcard2:/startup to the directory cfcard:/. After the startup files are copied, the device clearsand deletes the directory cfcard2:/startup. Then, the device sets the copied files as the nextstartup files.




Issue 01 (2011-05-30)

CAUTION1. Make sure that the directory cfcard:/ has enough space for storing the startup files that are

copied from the directory cfcard2:/startup.2. The system compares the startup files on the cfcard2s with those on the original CF cards

before copying startup files to the CF cards. The system copies every startup file from thecfcard2s whose name or size is different from that of the startup file on the CF cards.

3. If multiple startup files of the same type exist on the cfcard2s, the system copies only thelatest one.

4. If the name of a startup file on the cfcard2 is the same as that on the CF card, the startup fileof the CF card is overwritten.

5. The original system software on the CF card, however, is not overwritten.

Step 5 Run the display startup command to check whether the system software and configuration fileare successfully loaded.

The process of loading the system software through the USB port is the same as that of loadingthe system software through the CF card, and is not mentioned here. If the device has bothcfcard2s and USB ports, copy the startup files through the USB port preferentially.

----End



3-33

4 Emergency Maintenance Record Table

About This Chapter

This chapter describes how to fill up the emergency maintenance record table.

4.1 Emergency Maintenance Notice

4.2 Emergency Handling Record

HUAWEI CX600 Metro Services PlatformEmergency Maintenance 4 Emergency Maintenance Record Table


4-1

4.1 Emergency Maintenance Notice

If your maintenance personnel cannot remove a fault through emergency maintenance, pleasecall or fax Huawei technical support personnel for help. The maintenance personnel needmaintain a detailed record of the emergency maintenance procedures, notify Huawei of the typeof the board to be replaced, and apply for a spare one according to the warranty articles. Thishelp Huawei technical support personnel rectify the fault sooner.

You can fax an emergency maintenance notice to Huawei. The format of the notice is as follows:

Table 4-1 Emergency maintenance notice

* Filled by the customer

Telecomoffice

Devicemodel

Capacity

Customer Phonenumber

Version

Complainttime

Requiredresponsetime

In warranty Yes ¨ No

Fault description and handling procedure (in detail):Approved by: Signature:

* Filled by Huawei engineers

Handlingmethod

¨ Guide in call ¨ Remote maintenance ¨ On-site support

Result (attachment):Handled by: Date:

Known anomalies:

4.2 Emergency Handling Record

Emergency handling record

Site:__________________Date: MM/DD/YY_________________.

Emergencyoccured at

Emergencyhandled at

Person onduty

Emergencyhandled by

4 Emergency Maintenance Record TableHUAWEI CX600 Metro Services Platform



Issue 01 (2011-05-30)

Fault source Customercomplaint

Basic information:

Routinemaintenance

Alarms

Other sources

Fault symptom:

Solution and result:

HUAWEI CX600 Metro Services PlatformEmergency Maintenance 4 Emergency Maintenance Record Table


4-3

Documents

Emergency Maintenance(V600R003C00 01)