CloudEngine 6800&5800 V100R002C00 Troubleshooting Guide 01.pdf

8/12/2019 CloudEngine 6800&5800 V100R002C00 Troubleshooting Guide 01.pdf

1/160

CloudEngine 6800&5800 Series Switches

V100R002C00

Troubleshooting

Issue 01

Date 2013-08-01

HUAWEI TECHNOLOGIES CO., LTD.


2/160

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written

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

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the

customer. All or part of the products, services and features described in this document may not be within the

purchase 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 representations

of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://enterprise.huawei.com

Issue 01 (2013-08-01) Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

i
http://enterprise.huawei.com/


3/160

About This Document

Intended Audience

This document describes common troubleshooting procedure and methods.

This document is intended for:

l Data configuration engineers

l Commissioning engineers

l Network monitoring engineers

l System maintenance engineers

Symbol Conventions

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

Symbol Description

DANGER

Indicates a hazard with a high level or medium level of risk

which, if not avoided, could result in death or serious injury.

WARNING

Indicates a hazard with a low level of risk which, if not

avoided, could result in minor or moderate injury.

CAUTION

Indicates a potentially hazardous situation that, if not

avoided, could result in equipment damage, data loss,

performance deterioration, or unanticipated results.

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

NOTE Provides additional information to emphasize or supplement

important points in the main text.

Command Conventions

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


Troubleshooting About This Document



ii


4/160

Convention Description

Boldface 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 all

items can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. You can select one or several items, or select

no item.

& The parameter before the & sign can be repeated 1 to n times.

# A line starting with the # sign is comments.

Change HistoryUpdates between document issues are cumulative. Therefore, the latest document issue contains

all updates made in previous issues.

Changes in Issue 01 (2013-08-01)

Initial commercial release.


Troubleshooting About This Document



iii


5/160

Contents

About This Document.....................................................................................................................ii

1 Instructions for Maintenance Engineers...................................................................................1

1.1 Precautions......................................................................................................................................................................2

1.2 Backing Up Data................................................................................................................ ............................................21.3 Troubleshooting Process.................................................................................................................................................2

1.4 Ask for Help...................................................................................................................................................................3

1.4.1 Huawei Enterprise Website.........................................................................................................................................3

1.4.2 Hotline.........................................................................................................................................................................3

2 Forgetting Passwords....................................................................................................................4

2.1 Recovering the Console Port Password..........................................................................................................................5

2.2 Recovering the Telnet Login Password..........................................................................................................................7

3 Information Collection.................................................................................................................8

3.1 Overview........................................................................................................................................................................9

3.2 CollectingDiagnostic Information.................................................................................................................................9

3.3 Health Status Information...............................................................................................................................................9

4 System Maintenance Methods..................................................................................................10

4.1 Restoring the Default Settings Using the Configuration File.......................................................................................11

4.2 Restartingthe Device....................................................................................................................................................11

4.3 Upgradingthe Device...................................................................................................................................................12

4.4 Transferring Files Using FTP/TFTP.............................................................................................................................12

5 Startup Failures............................................................................................................................165.1 Terminal Does Not Display Anything Or Displays Garbled Characters......................................................................17

6 Hardware.......................................................................................................................................18

6.1 Power Module Troubleshooting...................................................................................................................................19

6.1.1 The SYS and Power Module Indicators Are Off.......................................................................................................19

6.2 Fan Module Troubleshooting.......................................................................................................................................19

6.2.1 The Indicator of a Fan Module Is Steady Red...........................................................................................................19

6.2.2 Fan Noise Is Loud......................................................................................................................................................20

6.2.3 An Alarm Is Generated When the Fan Status Is Abnormal.......................................................................................20

6.2.4 Fan Blades Were Damaged.......................................................................................................................................21


Troubleshooting Contents



iv


6/160

6.3 Optical Module Troubleshooting..................................................................................................................................21

6.3.1 Optical Modules on the Local and Remote Devices Cannot Communicate.............................................................21

6.4 Interface Troubleshooting.............................................................................................................................................24

6.4.1 A 40GE Interface Fails to Be Split into 10GE Interfaces or 10GE Interfaces Fail to Be Merged into A 40GE Interface

............................................................................................................................................................................................24

6.4.2 An Electrical Interface Cannot Go Up.......................................................................................................................25

6.4.3 10GE Optical Interfaces Cannot Go Up....................................................................................................................26

6.4.4 40GE Optical Interfaces Cannot Go Up....................................................................................................................28

6.4.5 Packet Loss Occurs on An Interface..........................................................................................................................29

7 Patch and Upgrade Faults..........................................................................................................31

7.1 Patch Faults...................................................................................................................................................................32

7.1.1 Failed toInstall a Patch.............................................................................................................................................32

8 Service Faults................................................................................................................................338.1 LAN..............................................................................................................................................................................34

8.1.1 VLAN Troubleshooting.............................................................................................................................................34

8.1.1.1 Users in a VLAN Cannot Communicate with Each Other.....................................................................................34

8.1.1.1.1 Common Causes..................................................................................................................................................34

8.1.1.1.2 Troubleshooting Flowchart..................................................................................................................................34

8.1.1.1.3 Troubleshooting Procedure..................................................................................................................................36

8.1.1.1.4 Relevant Alarms and Logs..................................................................................................................................38

8.1.2 MSTP Troubleshooting.............................................................................................................................................38

8.1.2.1 MSTP Topology Change Leads to Service Interruption........................................................................................388.1.2.1.1 Common Causes..................................................................................................................................................38




8.2 IP Forwarding and Routing..........................................................................................................................................44

8.2.1 RIP Troubleshooting .................................................................................................................................................44

8.2.1.1 Device Does not Receive Partial Routes or All the Routes....................................................................................44

8.2.1.1.1 Common Causes..................................................................................................................................................44




8.2.1.2 Device Does not Send Partial or All the Routes.....................................................................................................48

8.2.1.2.1 Common Causes..................................................................................................................................................48




8.2.1.3 Trouble Cases.........................................................................................................................................................53

8.2.1.3.1 A RIP Error Occurs due to Discontinuous Subnets.............................................................................................53

8.2.2 OSPF Troubleshooting..............................................................................................................................................55





v


7/160

8.2.2.1 OSPF Neighbor Relationship Is Down...................................................................................................................55

8.2.2.1.1 Common Causes..................................................................................................................................................55




8.2.2.2 OSPFNeighbor Relationship Cannot Enter the Full State.....................................................................................60

8.2.2.2.1 Common Causes..................................................................................................................................................60




8.2.3 BGP Troubleshooting................................................................................................................................................63

8.2.3.1 BGP Peer Relationship Fails to Be Established.....................................................................................................63

8.2.3.1.1 Common Causes..................................................................................................................................................63




8.2.3.2 BGP Public Network Traffic Is Interrupted...........................................................................................................69

8.2.3.2.1 Common Causes..................................................................................................................................................69




8.2.3.3 BGP Private Network Traffic Is Interrupted..........................................................................................................73

8.2.3.3.1 Common Causes..................................................................................................................................................73




8.2.3.4 Troubleshooting of the Fault that Prevents a Local BGP Peer (Route Sender) from Receiving ORFs from a Remote

Peer (Route Receiver).........................................................................................................................................................79

8.2.3.4.1 Common Causes..................................................................................................................................................79




8.3 IP Multicast...................................................................................................................................................................84

8.3.1 Multicast Traffic Cannot Be Transmitted..................................................................................................................84

8.3.1.1 Common Causes.....................................................................................................................................................84

8.3.1.2 Troubleshooting Flowchart.....................................................................................................................................84

8.3.1.3 Troubleshooting Procedure.....................................................................................................................................85

8.3.1.4 Relevant Alarms and Logs.....................................................................................................................................86

8.3.2 The PIMNeighbor Relationship Remains Down......................................................................................................86

8.3.2.1 Common Causes.....................................................................................................................................................86







vi


8/160


8.3.3 MSDP Peers Cannot Generate Correct (S, G) Entries...............................................................................................89

8.3.3.1 Common Causes.....................................................................................................................................................89




8.4 QoS...............................................................................................................................................................................93

8.4.1 Priority Mapping Troubleshooting............................................................................................................................93

8.4.1.1 Packets Enter Incorrect Queues..............................................................................................................................93

8.4.1.1.1 Common Causes..................................................................................................................................................94




8.4.1.2 Priority Mapping Results Are Incorrect.................................................................................................................97

8.4.1.2.1 Common Causes..................................................................................................................................................97



8.4.1.2.4 Relevant Alarms and Logs................................................................................................................................100

8.4.2 Traffic Policing Troubleshooting............................................................................................................................100

8.4.2.1 Interface-based Traffic Policing Results Are Incorrect........................................................................................100

8.4.2.1.1 Common Causes................................................................................................................................................100

8.4.2.1.2 Troubleshooting Flowchart................................................................................................................................100

8.4.2.1.3 Troubleshooting Procedure................................................................................................................................101


8.4.3 Traffic Shaping Troubleshooting.............................................................................................................................102

8.4.3.1 TrafficShaping Results of Queues Are Incorrect.................................................................................................102

8.4.3.1.1 Common Causes................................................................................................................................................102




8.4.4 Congestion Avoidance Troubleshooting.................................................................................................................107

8.4.4.1 Congestion Avoidance Fails to Take Effect.........................................................................................................107

8.4.4.1.1 Common Causes................................................................................................................................................107




8.4.5 Congestion Management Troubleshooting..............................................................................................................110

8.4.5.1 Congestion Management Fails to Take Effect.....................................................................................................111

8.4.5.1.1 Common Causes................................................................................................................................................111







vii


9/160


8.5 Device Management...................................................................................................................................................113

8.5.1 Stacking Troubleshooting........................................................................................................................................114

8.5.1.1 A Stack Failed to Be Set Up.................................................................................................................................114

8.5.1.1.1 Common Causes................................................................................................................................................114




8.5.1.2 Active/Standby Switchover Cannot Be Performed in a Stack.............................................................................116

8.5.1.2.1 Common Causes................................................................................................................................................117




8.6 TRILL.........................................................................................................................................................................118

8.6.1 TRILLNeighbor Relationship Fails to Be Established...........................................................................................118

8.6.1.1 Common Causes...................................................................................................................................................118

8.6.1.2 Troubleshooting Flowchart...................................................................................................................................118

8.6.1.3 Troubleshooting Procedure...................................................................................................................................119

8.6.1.4 Relevant Alarms and Logs...................................................................................................................................122

8.6.2 TRILL Traffic Failed to Be Forwarded...................................................................................................................122

8.6.2.1 Common Causes...................................................................................................................................................122




8.6.3 TRILL In-band NMS Fails to Manage RBs............................................................................................................125

8.6.3.1 Common Causes...................................................................................................................................................125




8.6.4 TRILL Fails to Be Enabled on an Interface.............................................................................................................127

8.6.4.1 Common Causes...................................................................................................................................................128




9 Common Fault Diagnostic Commands.................................................................................130

9.1 display Commands.....................................................................................................................................................131

9.1.1 Overview.................................................................................................................................................................131

9.1.2 Regular Expression in display Commands..............................................................................................................131

9.1.3 Common display Commands...................................................................................................................................135

9.2 reset Commands.........................................................................................................................................................137

9.2.1 Overview.................................................................................................................................................................137





viii


10/160

9.2.2 reset Commands Clearing Packet Statistics.............................................................................................................137

9.2.3 Using reset Commands............................................................................................................................................138

9.3 Ping and Tracert..........................................................................................................................................................138

9.4 Traps...........................................................................................................................................................................141

9.5 Logs............................................................................................................................................................................143

9.6 Packet Header Capturing Function.............................................................................................................................143

10 Appendix: Indicators.............................................................................................................. 147

10.1 Fan Module Indicator...............................................................................................................................................148

10.2 Power Indicators.......................................................................................................................................................149





ix


11/160

1Instructions for Maintenance EngineersAbout This Chapter

1.1 Precautions

1.2 Backing Up Data

1.3 Troubleshooting Process

1.4 Ask for Help


Troubleshooting 1 Instructions for Maintenance Engineers



1


12/160

1.1 Precautions

If you are a maintenance engineer, read the following precautions before doing your work:

l Confirm whether the fault is an emergency fault. If it is an emergency fault, recover the

faulty module by using the pre-defined troubleshooting methods immediately, and then

restore services.

l Strictly conform to operation rules and industrial safety standards, ensuring human and

device safety.

l Wear the ESD wrist strap when touching device components.

l Record original information about the problems occurring during troubleshooting.

l Record all the operations you have performed, especially the key operations such as

restarting device and clearing database. Before performing the key operations, confirm theoperation feasibility, back up data, and prepare the emergency and security measures. Only

qualified personnel can perform key operations.

NOTE

After commands are configured to troubleshoot faults, pay attention to the configuration validation mode

to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to the

immediate validation mode.

l In immediate validation mode, configurations take effect after commands are input and the Enter key

is pressed.

l In two-phase validation mode, after commands are configured, the commitcommand needs to be run

to commit the configurations.

Saving the results of each troubleshooting step is recommended. If your troubleshooting fails to correct

the fault, you will have a record of your actions to provide Huawei technical support personnel.

1.2 Backing Up Data

Some faults cause resource or money loss for customers. Therefore, maintenance engineers

should focus on preventing faults and quickly restoring faults. Data backup helps you quickly

locate and recover faults. After a network is set up and operates normally, you should back up

important data as soon as possible.

Important data includes:

l Complete network topology, including device models, versions, and networking diagram

l Configuration files and license files

l System software and patch files

l (Optional) Logs

l (Optional) Feature library

1.3 Troubleshooting Process

Systematic troubleshooting is to find fault causes step by step, and finally recover the fault.





2


13/160

Generally, troubleshooting steps include observing fault symptom, collecting information,

analyzing problem, and finding the root cause. The possible causes of all faults can be grouped

into multiple cause sets, which make troubleshooting easier.

1.4 Ask for Help

1.4.1 Huawei Enterprise Website

At http://support.huawei.com/enterprise, you can:

l Search troubleshooting cases to find a way to fix your problem.

l Post your question on BBS and wait for answers from online technical experts.

1.4.2 Hotline

If you cannot recover the fault, you can:

l Contact the agent.

NOTE

Provide device and fault information to technical support personnel.





3


14/160

2Forgetting PasswordsAbout This Chapter

This section describes how to recover the console port and Telnet passwords. You are advised

to keep passwords secure and change them regularly.

2.1 Recovering the Console Port Password

2.2 Recovering the Telnet Login Password


Troubleshooting 2 Forgetting Passwords



4


15/160

2.1 Recovering the Console Port Password

Three methods are provided to recover the console port password.

l Method 1: Log in to the device using Telnet and change the console port password.

l Method 2: Change the console port password through the BIOS menu.

NOTE

Method 1 is recommended. If you forget the Telnet password, use method 2.

Logging In to the Device Using Telnet and Modifying the Console Port Password

If you can log in to the device using Telnet and your user right is level 3 or higher, log in to the

device using Telnet, change the console port password, and save the configuration.

1. Log in to the device using Telnet. Ensure that your user right is level 3 or higher.

Run the display userscommand to display all the users that have logged into the device.

The item with a "+" mark indicates your user account on user interface VTY1.

display users User-Intf Delay Type Network Address AuthenStatusAuthorcmdFlag 34 VTY 0 00:06:53 TEL 10.135.18.67 pass yesUsername : Unspecified

+ 35 VTY 1 00:00:00 TEL 10.135.18.91 pass yesUsername : Unspecified

36 VTY 2 00:08:11 TEL 10.135.18.54 pass yesUsername : Unspecified

Run the display user-interfacecommand to view the user right of all users. VTY1 has a

corresponding user right 15; therefore, you have the right to change the console port

password.

display user-interface Idx Type Tx/Rx Modem Privi ActualPrivi Auth Int0 CON 0 9600 - 15 - P -

+ 34 VTY 0 - 15 15 P -+ 35 VTY 1 - 15 15 P -+ 36 VTY 2 - 15 - P -37 VTY 3 - 15 15 P -

......

2. Change the console port password. In this example, you set the authentication mode topassword authentication.

system-view[~HUAWEI] user-interface console 0[~HUAWEI-ui-console0] authentication-mode passwordPlease configure the login password (6-16)Enter Password:Confirm Password:[~HUAWEI-ui-console0] user privilege level 15[~HUAWEI-ui-console0] commit[~HUAWEI-ui-console0] return

3. Save the configuration to prevent configuration loss after a restart.

save

Warning: The current configuration will be written to the device.Are you sure to continue? [Y/N]:y





5


16/160

Now saving the current configuration to the slot 1Info: Save the configuration successfully.

Modifying the Console Port Password Through the BIOS Menu

The BIOS allows you to clear the console port password so that the device does not check the

password when you log in through the console port. Then the device restarts, enters the command

line interface, and prompts you to change the console port password.

CAUTION

l You must restart the device to display the BIOS menu, which results in service interruption.

Migrate services to a backup device and perform this operation in off-peak hours.

l Set a new password immediately after you log in to the device by clearing console login

password. Otherwise, you must repeat this operation when the login expires or the devicerestarts.

l Do not power off the device during the operation.

1. Connect a PC to the device with a serial cable and restart the device. When the message

"Press CTRL+B to enter BIOS menu" is displayed, press Ctrl+Band enter the BIOS

password ([email protected] default) to display the BIOS main menu.

2. Clear console login password.

BIOS Menu (Version: 126)

1. Continue to boot 2. Update from serial interface 3. Update from ethernet interface 4. Modify startup parameters 5. File system 6. Modify BIOS password 7. Modify console password 8. Reboot

Enter your choice(1-7): 7

Caution: A new console password must be set after the restart.Continue now? Yes(y) or No(n): y

3. After the system starts, authentication is not required when logging in to the device through

the console port, but you need to change the console port password in time. In this example,you set the authentication mode to password authentication.

system-view[~HUAWEI] user-interface console 0[~HUAWEI-ui-console0] authentication-mode passwordPlease configure the login password (6-16)Enter Password:Confirm Password:[~HUAWEI-ui-console0] user privilege level 15[~HUAWEI-ui-console0] commit[~HUAWEI-ui-console0] return

4. Save the configuration.

save

Warning: The current configuration will be written to the device.Are you sure to continue? [Y/N]:y





6


17/160

Now saving the current configuration to the slot 1Info: Save the configuration successfully.

2.2 Recovering the Telnet Login Password

You can use Telnet to remotely maintain and manage a device. If you forget the Telnet login

password, log in to the device using the console port and set a new password.

Currently, the device supports two authentication modes for Telnet login.

l AAA authentication: To log in to the device, you must have a user name and a password.

l Password authentication: To log in to the device, you must have a password.

In this example, the configurations for VTY0 to VTY4 are the same.

NOTE

After you log in to the device, run the display current-configuration configuration user-interfacecommand to view the authentication mode of the VTY user. You can change the password without changing

the authentication mode or configure a new authentication mode.

AAA Authentication system-view[~HUAWEI] user-interface vty 0 4[~HUAWEI-ui-vty0-4] authentication-mode aaa[~HUAWEI-ui-vty0-4] quit[~HUAWEI] aaa[~HUAWEI-aaa] local-user huawei password irreversible-cipher huawei@123[~HUAWEI-aaa] local-user huawei service-type telnet[~HUAWEI-aaa] local-user huawei level 15

[~HUAWEI-aaa] commit[~HUAWEI-aaa] return saveWarning: The current configuration will be written to the device.Are you sure to continue? [Y/N]:yNow saving the current configuration to the slot 1Info: Save the configuration successfully.

After the configuration is complete, you can use the user name huaweiand password

huawei@123to log in to the device.

Password Authentication system-view

[~HUAWEI] user-interface vty 0 4[~HUAWEI-ui-vty0-4] authentication-mode passwordPlease configure the login password (6-16)Enter Password:Confirm Password:[~HUAWEI-ui-vty0-4] user privilege level 15[~HUAWEI-ui-vty0-4] commit[~HUAWEI-ui-vty0-4] return saveWarning: The current configuration will be written to the device.Are you sure to continue? [Y/N]:yNow saving the current configuration to the slot 1Info: Save the configuration successfully.

After the configuration is complete, you can use the password huawei@123to log in to the

device.





7


18/160

3Information CollectionAbout This Chapter

This chapter describes the information collection method. You must collect detailed fault

information before locating faults by yourself or contacting agents or Huawei technical support

personnel for fault location.

NOTE

If you need to send fault information to agents or Huawei technical support personnel for fault location,

delete security information such as network configurations before sending the fault information.

3.1 Overview

3.2 Collecting Diagnostic Information

3.3 Health Status Information


Troubleshooting 3 Information Collection



8


19/160

3.1 Overview

After a device fault occurs, collect fault information immediately. This helps you locate the faultaccurately.

If you cannot locate the fault by yourself, provide the following information to agents or Huawei

technical support personnel:

l Fault occurrence time, network topology, operations triggering the fault, fault symptom,

measures that you have taken and results, and affected services

l Name, version, current configurations, interfaces of the faulty device. For the method of

obtaining these information, see 3.2 Collecting Diagnostic Informationand 9.1.3

Common display Commands.

l Logs generated when the fault occurs. For the method of obtaining the log information, see

Collecting Log Information.

3.2 Collecting Diagnostic Information

The display diagnostic-information[ [ module-name] & [ slotslot-id] |file-name]

command displays the device diagnostic information on screen or outputs the information to a

txt file. The device diagnostic information includes startup configuration, current configurations,

interface information, time, and system version. The following is an example:

display diagnostic-information dia-info.txtNow saving the diagnostic information to the device.............................

................................................................................

..............Info: The diagnostic information was saved to the device successfully.

The default storage path is the root directory of the system default storage device: flash:/. Using

the dircommand in the user view can confirm file generation.

After a device becomes faulty, provide the device diagnostic information to agents or Huawei

technical support personnel immediately for fast fault location. For the method of transmitting

the diagnostic information from the device to your computer, see 4.4 Transferring Files Using

FTP/TFTP.

NOTE

l Executing this command requires a long time. You can press Ctrl+Cto pause diagnosis information

display on screen.

l When a large amount of diagnostic information is displayed, the CPU usage may be high in a short

period.

3.3 Health Status Information

The device provides the display healthcommand. You can run the command to check the health

status information, including the temperature, power supply, fan, CPU usage, memory usage,

and storage medium usage of the device. The following is an example:

display health


Troubleshooting 3 Information Collection



9


20/160

4System Maintenance MethodsAbout This Chapter

This section describes how to restore default settings, restart a device, and transfer files.

4.1 Restoring the Default Settings Using the Configuration File

4.2 Restarting the Device

4.3 Upgrading the Device

4.4 Transferring Files Using FTP/TFTP


Troubleshooting 4 System Maintenance Methods



10


21/160

4.1 Restoring the Default Settings Using the Configuration

FileWhen the device is powered on, it reads the configuration file from the default directory for

initialization. Therefore, the configuration in the file is called the initial configuration. If no

configuration file is stored in the default directory, the device uses the default parameters for

initialization. You must restart the device to make the recovered default settings take effect.

1. Restore the configuration file using the FTP/TFTP server.

For detailed operations, see Using FTP/TFTP to Transfer Files. Download the default

configuration file to the device.

2. Run the startup saved-configurationcommand to specify the default configuration file

for the next startup and restore the default settings.

startup saved-configuration config.zip reboot fast

NOTE

When restoring the default settings, do not save the configuration. Otherwise, the device starts up

using the current configuration.

4.2 Restarting the Device

Some network faults will be rectified after you restart the device. This section describes how to

restart a device.

You can restart the device using any of the methods in the following table.

Table 4-1Device restart methods

Method Description

Turn off and then turn on the power switch to

restart the device.

Cold restart is performed manually. In cold

restart, a device can be restarted only by

pressing the power button, which has

limitations and is applicable to onsite

maintenance.Save the configurations in real time because

the device will restart directly without saving

the current configuration.

Run the rebootcommand in the user view to

restart the device.

Hot restart uses commands, which is adopted

by maintenance personnel who remotely

manages the device.

In restart, the system asks whether to save the

configuration, which effectively prevents

configuration loss.





11


22/160

4.3 Upgrading the Device

The upgrade of a device is closely related to the released software versions. The corresponding

upgrade guide is released with each new version and you can upgrade the device according to

the guide. To obtain the upgrade guides, visit http://support.huawei.com/enterprise, choose

Software> Product Software> Enterprise Networking> Switch> Data Center Switch,

and download the upgrade guide based on the product name and version.

4.4 Transferring Files Using FTP/TFTP

During system maintenance such as software upgrade and configuration file backup, files must

be transferred between a PC and the device. FTP/TFTP is used to transfer files.

When transferring files using FTP/TFTP, the roles of PC and device vary in different methods:

l PC functioning as an FTP server: You must install the FTP server software on your PC.

l PC functioning as a TFTP server: You must install the TFTP server software on your

PC. TFTP is easy to configure but this method has low security and transmission speed.

l Device functioning as an FTP server: You can perform configurations on the device

without installing any software. When there are a large number of devices on a network,

the first two methods are recommended.

PC Functioning as an FTP Server

Figure 4-1Networking diagram

FTP Client FTP Server

192.168.0.2/24192.168.0.1/24

MEth0/0/0

1. Run the FTP server software on the FTP server and configure the FTP service. For details,

see relevant help documentation.

2. Connect the device and the FTP server. (The IP addresses are used as an example.)

a. Connect the FTP server to MEth0/0/0 of the device using a network cable.

b. Configure an IP address 192.168.0.1/24 for MEth0/0/0.

c. Configure an IP address 192.168.0.2/24 forthe FTP server.

system-view[~HUAWEI] interface meth 0/0/0[~HUAWEI-MEth0/0/0] ip address 192.168.0.1 24[~HUAWEI-MEth0/0/0] commit[~HUAWEI-MEth0/0/0]ping 192.168.0.2 PING 192.168.0.2: 56 data bytes, press CTRL_C to break Reply from 192.168.0.2: bytes=56 Sequence=1 ttl=128 time=4 ms Reply from 192.168.0.2: bytes=56 Sequence=2 ttl=128 time=3 ms Reply from 192.168.0.2: bytes=56 Sequence=3 ttl=128 time=18 ms Reply from 192.168.0.2: bytes=56 Sequence=4 ttl=128 time=3 ms Reply from 192.168.0.2: bytes=56 Sequence=5 ttl=128 time=3 ms

--- 192.168.0.2 ping statistics ---





12
http://support.huawei.com/enterprise/


23/160

5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 3/6/18 ms

[~HUAWEI-MEth0/0/0] return

NOTE

l In this example, the FTP server and the device are directly connected. If they are not directly

connected, you must ensure that they have reachable routes to each other.

l After the configuration is complete, run the pingcommand to test the connectivity between the

FTP server and device.

3. Log in to the FTP server using FTP.

ftp 192.168.0.2Trying 192.168.0.2 ...Press CTRL + K to abortConnected to 192.168.0.2.220 FTP Server ready.

User(192.168.0.2:(none)):ftpuser

331 Password required for ftpuser.Enter password:230 User logged in.

[ftp]

4. Run the putcommand to upload files to the FTP server or run the getcommand to download

files from the FTP server to the device.

[ftp]put vrpcfg.zip200 Port command okay.150 Opening ASCII mode data connection for /vrpcfg.zip./ 100% [***********]226 Transfer complete.FTP: 1098 byte(s) sent in 0.131 second(s) 8.38Kbyte(s)/sec.

[ftp]binary200 Type set to I.[ftp] get devicesoft.cc200 Port command okay.150 Opening BINARY mode data connection for /devicesoft.cc.\ 6482944 bytes transferred226 Transfer complete.FTP: 6482944 byte(s) received in 54.500 second(s) 1117.40Kbyte(s)/sec.[ftp]

PC Functioning as a TFTP Server


TFTP Client TFTP Server

192.168.0.2/24192.168.0.1/24

MEth0/0/0

1. Run the TFTP server software on the TFTP server (PC) and configure the TFTP service.

For details, see relevant help documentation.

2. Connect the TFTP server and the device and configure IP addresses for them. For details,

see PC Functioning as an FTP Server.

3. Run the tftp putcommand to upload files to the TFTP server or run the tftp getcommand

to download files from the TFTP server to the device.





13


24/160

tftp 192.168.0.2 get vrpcfg.zip vrpcfg1.zipInfo: Transfer file in binary mode.Please wait for a while.../ 8174 bytes transferredInfo: Downloaded the file successfully. tftp 192.168.0.2 put vrpcfg.zip vrpcfg2.zip

Info: Transfer file in binary mode.Please wait for a while.../ 100% [***********]Info: Uploaded the file successfully.

Device Functioning as an FTP Server


FTP Server FTP Client

192.168.0.2/24192.168.0.1/24

MEth0/0/0

1. Connect the PC and the device and configure IP addresses for them. For details, see PC

Functioning as an FTP Server.

2. Enable FTP on the device, and create a user name, password, and FTP path.

NOTE

You must set the user level to level 3 or above to establish an FTP connection.

system-view[~HUAWEI] ftp server enable[~HUAWEI] aaa

[~HUAWEI-aaa] local-user huawei password irreversible-cipher huawei@123[~HUAWEI-aaa] local-user huawei service-type ftp[~HUAWEI-aaa] local-user huawei ftp-directory flash:[~HUAWEI-aaa] local-user huawei level 15[~HUAWEI-aaa] commit[~HUAWEI-aaa] quit[~HUAWEI] quit

3. Log in to the device by running the ftpcommand on the FTP server. Run the getcommand

to download files to the FTP server or run the putcommand to upload files from the FTP

server to the device.

For example, on an FTP server with the Windows operating system, choose Start> Run,

enter cmd, and click OK.

C:\Documents and Settings\Administrator> ftp 192.168.0.1Connected to 192.168.0.1.220 FTP service ready.User (192.168.0.1:(none)): huawei331 Password required for huawei.Password:230 User logged in.ftp> get vrpcfg.zip200 Port command okay.150 Opening ASCII mode data connection for vrpcfg.zip.226 Transfer complete.ftp: 5203 bytes received in 0.01Seconds 346.00Kbytes/sec.ftp> lcdLocal directory now C:\Documents and Settings\Administrator.ftp>put vrpcfg.zip

200 Port command okay.150 Opening ASCII mode data connection for vrpcfg.zip.





14


25/160

226 Transfer complete.ftp: 5203 bytes sent in 0.01Seconds 346.87Kbytes/sec

NOTE

If you use the user name Administratorto log in to the PC, the output differs from the above.

You can run the lcdcommand to view the path where backup configuration files are saved.

The commands vary with the operating system. For details, see relevant help documentation of each

operating system.





15


26/160

5Startup FailuresAbout This Chapter

This section describes how to troubleshoot device startup failures.

5.1 Terminal Does Not Display Anything Or Displays Garbled Characters


Troubleshooting 5 Startup Failures



16


27/160

5.1 Terminal Does Not Display Anything Or Displays

Garbled CharactersFault Description

After a terminal connecting to a router starts, it cannot display anything or displays garbled

characters.

Possible Cause

l The power module of the router is faulty or the router is not powered on.

l The serial interface connecting to the router is incorrectly configured.

l The cable between the terminal and router is faulty or not firmly connected to the serial

interface.

Troubleshooting Roadmap

l Check the power indicator on the router's front panel to ensure that the power module is

working properly.

l Ensure that the serial interface is correctly configured.

l Install the cable firmly or replace the cable.

Troubleshooting Procedure

1. Check the power indicator on the router's front panel. If the power indicator is On, the

power module is working properly. If the power indicator is Off, rectify the fault according

to Power Module Troubleshooting.

2. Check whether the combo interface type is correct and whether the physical attributes of

the PC is consistent with those of the serial interface. The default parameters are as follows:

l Baud rate: 9600

l Data bit: 8

l Stop bit: 1

l Parity check: None

lFlow control: None

3. Ensure that the cable is firmly connected to the serial interface. You can replace it with a

new cable to verify whether the cable is faulty.


Troubleshooting 5 Startup Failures



17


28/160

6HardwareAbout This Chapter

6.1 Power Module Troubleshooting

6.2 Fan Module Troubleshooting

6.3 Optical Module Troubleshooting

6.4 Interface Troubleshooting


Troubleshooting 6 Hardware



18


29/160

6.1 Power Module Troubleshooting

6.1.1 The SYS and Power Module Indicators Are Off

Fault Description

The SYS indicator and power module indicators are all off, and the chassis cannot be powered

on.

Possible Causes

l The power modules are turned off.

l

Power cables are not securely connected to the sockets.l The power modules are faulty.


1. Ensure that the power switches on the power modules are turned on.

2. Ensure that the power cables are securely connected to the sockets.

3. Replace the power modules with normal power modules of the same model. If the chassis

is powered on, the original power modules on the chassis are faulty. Send the faulty power

modules to Huawei for repair.

4. If the chassis still fails to be powered on, contact Huawei Technical Assistance Center.

6.2 Fan Module Troubleshooting

6.2.1 The Indicator of a Fan Module Is Steady Red

Fault Description

The indicator of a fan module is steady red.

Possible Causes

l The fan module is not properly installed in the fan slot.

l Fan blades are blocked or stop rotating because of heavy dust.

l The fan module is faulty.


1. Check whether the fan module is securely installed. If not, remove and reinstall the fan

module (hot swappable).

2. Remove the fan module and check whether fan blades are blocked or covered with heavy

dust.





19


30/160

l If fan blades are blocked by an obstacle, remove the obstacle.

l If fan blades have heavy dust, use a brush to clean fan blades.

3. Install another fan module of the same model into the fan slot. If the new fan module can

work normally, the original fan module has failed.

6.2.2 Fan Noise Is Loud

Fault Description

The device is running properly and no fan alarm is generated; however, the fan noise is loud.

Common Causes

l The fan rotation speed is high.


1. Run the display device fancommand to check the fan rotation speed.

2. If the fan rotation speed is high, run the set fan-speedslotslot-idpercentpercentcommand

to reduce the fan rotation speed. The following is an example:

system-view[~HUAWEI] diagnose[~HUAWEI-diagnose] set fan-speed slot 1 percent 50

CAUTION

Reducing the fan speed may cause the overtemperature of the device. Therefore, use this

command with caution.

3. If the fan noise is still loud after the fan rotation speed is reduced, run the upgrade fan

command to upgrade the fan version. The following is an example:

system-view[~HUAWEI] diagnose[~HUAWEI-diagnose] upgrade fan all

4. If the fault persists, use a new fan module.

6.2.3 An Alarm Is Generated When the Fan Status Is Abnormal

Fault Description

The display devicecommand output shows that the fan status is abnormal.

display deviceDevice status:-----------------------------------------------------------------------------Slot Sub Type Online Power Register Alarm Primary-----------------------------------------------------------------------------1 - CE5850-48T4S2Q-EI Present On Registered Normal Master

FAN2 - Present On Registered AbnormalNA

PWR2 - Present On Registered Normal NA-----------------------------------------------------------------------------





20


31/160

Common Causes

l The fan is not installed properly.

l Fan blades are blocked or have heavy dust.


1. Check whether the fan is properly installed and whether fan blades are blocked by an

obstacle or have heavy dust. If so, properly install the fan, remove the obstacle, or use a

brush to clean fan blades.

2. Run the upgrade fancommand to upgrade the fan version. The following is an example:

system-view[~HUAWEI] diagnose[~HUAWEI-diagnose] upgrade fan all

3. If the fault persists, use a new fan module.

6.2.4 Fan Blades Were Damaged

Fault Description

The display device alarm hardwarecommand output contains the following fan alarm.

display device alarm hardware--------------------------------------------------------------------------------Index Level Date Time Info--------------------------------------------------------------------------------

1 critical 2013-04-10 03:03:36 The fan partially failed.(FanID=FAN 1,Reason=The first fan failed.)--------------------------------------------------------------------------------

Common Causes

l Fan blades are damaged.


1. Use a new fan module.

6.3 Optical Module Troubleshooting

6.3.1 Optical Modules on the Local and Remote Devices CannotCommunicate

Fault Description

An optical interface of a CE switch is connected to a remote device through an optical fiber. The

two optical interfaces are Down and cannot communicate with each other.





21


32/160

Possible Causes

l The optical module installed on the optical interface is not a Huawei certified optical

module.

l The optical module type does not match the optical fiber type.

l At least one of the two optical interfaces has been manually shut down.

l The transmit power of the optical module is too low or too high.

l The receive power of the optical module is too low or too high.


1. Check whether a Huawei certified optical module is installed on the optical interface. The

CE series switches must use Huawei certified optical modules. Non-Huawei-certified

optical module cannot ensure service reliability and stability. If a non-Huawei-certified

optical module is used, replace it with a Huawei certified optical module.

2. Check whether the optical module matches the optical fiber. If not, replace the optical fiberor optical module.

l A single-mode optical module (generally with a center wavelength of 1310 nm or 1550

nm) must work with a single-mode optical fiber (generally yellow).

l A multimode optical module (generally with a center wavelength of 850 nm) must work

with a multimode optical fiber (generally orange).

3. Run the display interface transceivercommand to check whether any alarm information

has been generated for the optical module. display interface 10ge 1/0/1 transceiver10GE1/0/1 transceiverinformation:

-------------------------------------------------------------------Common

information:Transceiver Type :

10GBASE_SRConnector

Type :LCWavelength (nm) :

850Transfer Distance (m) :80(50um),30(62.5um),300

(OM3)Digital Diagnostic

Monitoring :YESVendor

Name :AVAGO

Vendor PartNumber :AFBR-703SDZ

OrderingName :-------------------------------------------------------------------Manufacture

information:Manu. Serial

Number :AD1148A07G7Manufacturing Date :

2011-12-05Vendor

Name :AVAGO-------------------------------------------------------------------Alarm information:

LOS Alarm-------------------------------------------------------------------





22


33/160

If a LOS alarm is displayed, the local optical interface does not receive signals from the

remote interface. Run the display thiscommand in the interface view to check whether the

two interfaces have been manually shut down. If an interface is shut down, run the undo

shutdowncommand on the interface.

4. Run the display interface transceiver verbosecommand to display diagnostic informationabout the optical module on the interface. Check whether the diagnostic information

displays alarms about abnormal transmit or receive power. display interface 10ge 1/0/1 transceiver verbose10GE1/0/1 transceiverinformation:-------------------------------------------------------------------Common

information:Transceiver Type :

10GBASE_SRConnector

Type :LCWavelength (nm) :

850Transfer Distance (m) :80(50um),30(62.5um),300(OM3)

Digital DiagnosticMonitoring :YES

VendorName :AVAGO

Vendor PartNumber :AFBR-703SDZ

OrderingName :-------------------------------------------------------------------Manufacture

information:Manu. Serial

Number :AD1148A07G7Manufacturing Date :2011-12-05

VendorName :AVAGO-------------------------------------------------------------------Alarm information:RxPower Low

-------------------------------------------------------------------Diagnostic

information:Temperature (C) :

34.77Voltage (V) :

3.29

Bias Current (mA) :7.19

Bias High Threshold (mA) :10.50

Bias Low Threshold (mA) :2.50

Current RX Power (dBM) :-40.00Default RX Power High Threshold (dBM) :3.01Default RX Power Low Threshold (dBM) :-15.02Current TX Power (dBM) :-2.57Default TX Power High Threshold (dBM) :3.01Default TX Power Low Threshold (dBM) :-9.00

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





23


34/160

The display interface transceiver verbosecommand displays the current transmit and

receive power values of the optical module, as well as the default maximum and minimum

power values.

l If RxPower Lowis displayed, the receive signal strength is too low. The possible reason

is that the remote interface is Down or packets sent from the remote interface are droppedduring transmission. Check whether the distance between the two devices exceeds the

maximum transmission distance of the optical module. If the distance is within the

transmission distance of the optical module, check whether the optical module on the

remote interface or the optical fiber is damaged. If they are damaged, replace them.

l If RxPower Highis displayed, the receive signal strength is too high. The possible

reason is that the distance between the two devices is short but a long-distance optical

module is used. In this case, install an optical attenuator on the optical module to reduce

the transmit power.

l If TxPower Lowis displayed, the transmit signal strength on the local optical module

is too low. This may cause a low receive power on the remote optical module. As a

result, the remote interface cannot turn Up or drops packets sent from the local interface.

l If TxPower Highis displayed, the transmit signal strength on the local optical module

is too high. This may cause a high receive power on the remote optical module. If the

high receives power lasts for a long time, the remote optical module will be burned.

To ensure normal communication between two optical interfaces, check for transmit and

receive power alarms after the two interfaces have optical modules installed and connected

using an optical fiber. Ensure that the transmit and receive power values of the two optical

modules are in the normal range. Otherwise, traffic forwarding on the optical interfaces

may be abnormal or the optical modules may be damaged.

5. If no transmit and receive power alarms are displayed on the two ends but the two interfaces

are still Down, collect detailed information and logs about the optical modules, and thenreplace the optical modules or optical fiber. If the interfaces can turn Up, the original optical

modules or optical fiber has been damaged. If the interfaces are still Down, contact Huawei

Technical Assistance Center.

6.4 Interface Troubleshooting

6.4.1 A 40GE Interface Fails to Be Split into 10GE Interfaces or 10GE

Interfaces Fail to Be Merged into A 40GE Interface

Fault Description

A 40GE interface fails to be split into 10GE interfaces or 10GE interfaces fail to be merged into

a 40GE interface.

Common Causes

l Corresponding commands are not correctly configured.

l The card is not restarted.





24


35/160


l A 40GE interface fails to be split into 10GE interfaces.

1. Run the display current-configurationcommand to check whether configuration

information about port splitis available. If not, run the port splitinterfaceinterface-typeinterface-number1[ tointerface-typeinterface-number2] command in the

system view to split the 40GE interface into 10GE interfaces.

2. Run the display port splitcommand to check the current interface status. If the

command output displays the following information, restart the card. display port splitNote:*Enable : Enabled after board reset

*Disable : Disabled after board reset----------------------------------------------------Port Status Split-port----------------------------------------------------40GE4/0/1 *Enable 10GE4/0/49

10GE4/0/5010GE4/0/51

10GE4/0/52----------------------------------------------------

l 10GE interfaces fail to be merged into a 40 GE interface.

1. Run the display current-configurationcommand to check whether configuration

information about port splitis available. If not, run the undo port splitinterface

interface-typeinterface-number1[ tointerface-typeinterface-number2] command in

the system view to merge 10GE interfaces into the 40GE interface.

2. Run the display port splitcommand to check the current interface status. If the

command output displays the following information, restart the card. display port splitNote:*Enable : Enabled after board reset

*Disable : Disabled after board reset----------------------------------------------------Port Status Split-port----------------------------------------------------40GE4/0/3 *Disable 10GE4/0/57

10GE4/0/5810GE4/0/5910GE4/0/60

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

6.4.2 An Electrical Interface Cannot Go Up

Fault Description

An electrical interface cannot go up physically. The interface status is as follows:

display interface 10GE1/0/610GE1/0/6 current state : DOWN(ifindex:10)Line protocol current state :DOWN

Description:

Switch Port, PVID : 1, TPID : 8100(Hex), The Maximum Frame Length is9216Internet protocol processing :disabled

IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is





25


36/160

0025-9e95-7c10Port Mode: COMMON COPPER, Port Split:-Speed : 10000,Loopback:NONE

Duplex: FULL, Negotiation:ENABLEMdi :AUTO,

Last physical up time :-

Last physical down time : 2013-04-09 16:27:40

Common Causes

l The power cable is faulty.

lNegotiation between the local and remote interfaces fails.


1. Check the cable status. Run the virtual-cable-testcommand in the interface view to check

the cable status. If the cable status is displayed as Openor Shortrather than OK, replace

the cable.

2. Check configurations on the local and remote interfaces.

l If the rem

CloudEngine 6800&5800 V100R002C00 Troubleshooting Guide 01.pdf

Documents

Transcript of CloudEngine 6800&5800 V100R002C00 Troubleshooting Guide 01.pdf