CloudEngine 6800&5800 V100R001C00 Troubleshooting Guide 02.pdf

CloudEngine 6800&5800 Series Switches

Troubleshooting

Issue 02Date 2013-07-10

HUAWEI TECHNOLOGIES CO., LTD.

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 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 a warranty of any kind, express or implied. Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://enterprise.huawei.com

Issue 02 (2013-07-10) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i

About This Document

Intended AudienceThis document describes common troubleshooting procedure and methods.This document is intended for:l Data configuration engineersl Commissioning engineersl Network monitoring engineersl System maintenance engineers

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

Symbol Description

DANGERIndicates a hazard with a high level or medium level of riskwhich, if not avoided, could result in death or serious injury.

WARNINGIndicates a hazard with a low level of risk which, if notavoided, could result in minor or moderate injury.

CAUTIONIndicates a potentially hazardous situation that, if notavoided, 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 supplementimportant points in the main text.

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

CloudEngine 6800&5800 Series SwitchesTroubleshooting About This Document


ii

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

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

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

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

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. You can select one or several items, or selectno 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 containsall updates made in previous issues.

Changes in Issue 02 (2013-07-10)This version has the following updates:The following information is modified:l 6.2.4 Fan Blades Were Damaged

Changes in Issue 01 (2013-05-10)Initial commercial release.

CloudEngine 6800&5800 Series SwitchesTroubleshooting About This Document


iii

Contents

About This Document.....................................................................................................................ii1 Instructions for Maintenance Engineers...................................................................................11.1 Precautions......................................................................................................................................................................21.2 Backing Up Data............................................................................................................................................................21.3 Troubleshooting Process.................................................................................................................................................21.4 Ask for Help...................................................................................................................................................................31.4.1 Huawei Enterprise Website.........................................................................................................................................31.4.2 Hotline.........................................................................................................................................................................32 Forgetting Passwords....................................................................................................................42.1 Recovering the Console Port Password..........................................................................................................................52.2 Recovering the Telnet Login Password..........................................................................................................................73 Information Collection.................................................................................................................83.1 Overview........................................................................................................................................................................93.2 Collecting Diagnostic Information.................................................................................................................................93.3 Health Status Information...............................................................................................................................................94 System Maintenance Methods..................................................................................................104.1 Restoring the Default Settings Using the Configuration File.......................................................................................114.2 Restarting the Device....................................................................................................................................................114.3 Upgrading the Device...................................................................................................................................................124.4 Transferring Files Using FTP/TFTP.............................................................................................................................125 Startup Failures............................................................................................................................165.1 Terminal Does Not Display Anything Or Displays Garbled Characters......................................................................176 Hardware.......................................................................................................................................186.1 Power Module Troubleshooting...................................................................................................................................196.1.1 The SYS and Power Module Indicators Are Off.......................................................................................................196.2 Fan Module Troubleshooting.......................................................................................................................................196.2.1 The Indicator of a Fan Module Is Steady Red...........................................................................................................196.2.2 Fan Noise Is Loud......................................................................................................................................................206.2.3 An Alarm Is Generated When the Fan Status Is Abnormal.......................................................................................206.2.4 Fan Blades Were Damaged.......................................................................................................................................216.3 Optical Module Troubleshooting..................................................................................................................................21

CloudEngine 6800&5800 Series SwitchesTroubleshooting Contents


iv

6.3.1 Optical Modules on the Local and Remote Devices Cannot Communicate.............................................................216.4 Interface Troubleshooting.............................................................................................................................................246.4.1 A 40GE Interface Fails to Be Split into 10GE Interfaces or 10GE Interfaces Fail to Be Merged into A 40GE Interface............................................................................................................................................................................................246.4.2 An Electrical Interface Cannot Go Up.......................................................................................................................256.4.3 10GE Optical Interfaces Cannot Go Up....................................................................................................................266.4.4 40GE Optical Interfaces Cannot Go Up....................................................................................................................286.4.5 Packet Loss Occurs on An Interface..........................................................................................................................297 Patch and Upgrade Faults..........................................................................................................317.1 Patch Faults...................................................................................................................................................................327.1.1 Failed to Install a Patch.............................................................................................................................................328 Service Faults................................................................................................................................338.1 LAN..............................................................................................................................................................................348.1.1 VLAN Troubleshooting.............................................................................................................................................348.1.1.1 Users in a VLAN Cannot Communicate with Each Other.....................................................................................348.1.1.1.1 Common Causes..................................................................................................................................................348.1.1.1.2 Troubleshooting Flowchart..................................................................................................................................348.1.1.1.3 Troubleshooting Procedure..................................................................................................................................368.1.1.1.4 Relevant Alarms and Logs..................................................................................................................................388.1.2 MSTP Troubleshooting.............................................................................................................................................388.1.2.1 MSTP Topology Change Leads to Service Interruption........................................................................................388.1.2.1.1 Common Causes..................................................................................................................................................388.1.2.1.2 Troubleshooting Flowchart..................................................................................................................................388.1.2.1.3 Troubleshooting Procedure..................................................................................................................................408.1.2.1.4 Relevant Alarms and Logs..................................................................................................................................438.2 IP Forwarding and Routing..........................................................................................................................................448.2.1 RIP Troubleshooting .................................................................................................................................................448.2.1.1 Device Does not Receive Partial Routes or All the Routes....................................................................................448.2.1.1.1 Common Causes..................................................................................................................................................448.2.1.1.2 Troubleshooting Flowchart..................................................................................................................................448.2.1.1.3 Troubleshooting Procedure..................................................................................................................................468.2.1.1.4 Relevant Alarms and Logs..................................................................................................................................478.2.1.2 Device Does not Send Partial or All the Routes.....................................................................................................488.2.1.2.1 Common Causes..................................................................................................................................................488.2.1.2.2 Troubleshooting Flowchart..................................................................................................................................498.2.1.2.3 Troubleshooting Procedure..................................................................................................................................518.2.1.2.4 Relevant Alarms and Logs..................................................................................................................................538.2.1.3 Trouble Cases.........................................................................................................................................................538.2.1.3.1 A RIP Error Occurs due to Discontinuous Subnets.............................................................................................538.2.2 OSPF Troubleshooting..............................................................................................................................................558.2.2.1 OSPF Neighbor Relationship Is Down...................................................................................................................558.2.2.1.1 Common Causes..................................................................................................................................................55



v

8.2.2.1.2 Troubleshooting Flowchart..................................................................................................................................558.2.2.1.3 Troubleshooting Procedure..................................................................................................................................568.2.2.1.4 Relevant Alarms and Logs..................................................................................................................................608.2.2.2 OSPF Neighbor Relationship Cannot Enter the Full State.....................................................................................608.2.2.2.1 Common Causes..................................................................................................................................................608.2.2.2.2 Troubleshooting Flowchart..................................................................................................................................608.2.2.2.3 Troubleshooting Procedure..................................................................................................................................618.2.2.2.4 Relevant Alarms and Logs..................................................................................................................................638.2.3 BGP Troubleshooting................................................................................................................................................638.2.3.1 BGP Peer Relationship Fails to Be Established.....................................................................................................638.2.3.1.1 Common Causes..................................................................................................................................................638.2.3.1.2 Troubleshooting Flowchart..................................................................................................................................638.2.3.1.3 Troubleshooting Procedure..................................................................................................................................648.2.3.1.4 Relevant Alarms and Logs..................................................................................................................................688.2.3.2 BGP Public Network Traffic Is Interrupted...........................................................................................................688.2.3.2.1 Common Causes..................................................................................................................................................688.2.3.2.2 Troubleshooting Flowchart..................................................................................................................................688.2.3.2.3 Troubleshooting Procedure..................................................................................................................................698.2.3.2.4 Relevant Alarms and Logs..................................................................................................................................728.2.3.3 BGP Private Network Traffic Is Interrupted..........................................................................................................728.2.3.3.1 Common Causes..................................................................................................................................................728.2.3.3.2 Troubleshooting Flowchart..................................................................................................................................728.2.3.3.3 Troubleshooting Procedure..................................................................................................................................738.2.3.3.4 Relevant Alarms and Logs..................................................................................................................................788.2.3.4 Troubleshooting of the Fault that Prevents a Local BGP Peer (Route Sender) from Receiving ORFs from a RemotePeer (Route Receiver).........................................................................................................................................................788.2.3.4.1 Common Causes..................................................................................................................................................788.2.3.4.2 Troubleshooting Flowchart..................................................................................................................................788.2.3.4.3 Troubleshooting Procedure..................................................................................................................................808.2.3.4.4 Relevant Alarms and Logs..................................................................................................................................838.3 IP Multicast...................................................................................................................................................................838.3.1 Multicast Traffic Cannot Be Transmitted..................................................................................................................838.3.1.1 Common Causes.....................................................................................................................................................838.3.1.2 Troubleshooting Flowchart.....................................................................................................................................838.3.1.3 Troubleshooting Procedure.....................................................................................................................................848.3.1.4 Relevant Alarms and Logs.....................................................................................................................................858.3.2 The PIM Neighbor Relationship Remains Down......................................................................................................858.3.2.1 Common Causes.....................................................................................................................................................858.3.2.2 Troubleshooting Flowchart.....................................................................................................................................858.3.2.3 Troubleshooting Procedure.....................................................................................................................................868.3.2.4 Relevant Alarms and Logs.....................................................................................................................................888.3.3 MSDP Peers Cannot Generate Correct (S, G) Entries...............................................................................................888.3.3.1 Common Causes.....................................................................................................................................................88



vi

8.3.3.2 Troubleshooting Flowchart.....................................................................................................................................888.3.3.3 Troubleshooting Procedure.....................................................................................................................................908.3.3.4 Relevant Alarms and Logs.....................................................................................................................................928.4 QoS...............................................................................................................................................................................928.4.1 Priority Mapping Troubleshooting............................................................................................................................928.4.1.1 Packets Enter Incorrect Queues..............................................................................................................................928.4.1.1.1 Common Causes..................................................................................................................................................928.4.1.1.2 Troubleshooting Flowchart..................................................................................................................................938.4.1.1.3 Troubleshooting Procedure..................................................................................................................................948.4.1.1.4 Relevant Alarms and Logs..................................................................................................................................958.4.1.2 Priority Mapping Results Are Incorrect.................................................................................................................958.4.1.2.1 Common Causes..................................................................................................................................................958.4.1.2.2 Troubleshooting Flowchart..................................................................................................................................968.4.1.2.3 Troubleshooting Procedure..................................................................................................................................978.4.1.2.4 Relevant Alarms and Logs..................................................................................................................................988.4.2 Traffic Policing Troubleshooting..............................................................................................................................988.4.2.1 Interface-based Traffic Policing Results Are Incorrect..........................................................................................988.4.2.1.1 Common Causes..................................................................................................................................................988.4.2.1.2 Troubleshooting Flowchart..................................................................................................................................988.4.2.1.3 Troubleshooting Procedure..................................................................................................................................998.4.2.1.4 Relevant Alarms and Logs................................................................................................................................1008.4.3 Traffic Shaping Troubleshooting.............................................................................................................................1008.4.3.1 Traffic Shaping Results of Queues Are Incorrect.................................................................................................1008.4.3.1.1 Common Causes................................................................................................................................................1008.4.3.1.2 Troubleshooting Flowchart................................................................................................................................1008.4.3.1.3 Troubleshooting Procedure................................................................................................................................1028.4.3.1.4 Relevant Alarms and Logs................................................................................................................................1048.4.4 Congestion Avoidance Troubleshooting.................................................................................................................1048.4.4.1 Congestion Avoidance Fails to Take Effect.........................................................................................................1048.4.4.1.1 Common Causes................................................................................................................................................1048.4.4.1.2 Troubleshooting Flowchart................................................................................................................................1048.4.4.1.3 Troubleshooting Procedure................................................................................................................................1068.4.4.1.4 Relevant Alarms and Logs................................................................................................................................1078.4.5 Congestion Management Troubleshooting..............................................................................................................1078.4.5.1 Congestion Management Fails to Take Effect.....................................................................................................1078.4.5.1.1 Common Causes................................................................................................................................................1088.4.5.1.2 Troubleshooting Flowchart................................................................................................................................1088.4.5.1.3 Troubleshooting Procedure................................................................................................................................1098.4.5.1.4 Relevant Alarms and Logs................................................................................................................................1108.5 Device Management...................................................................................................................................................1108.5.1 Stacking Troubleshooting........................................................................................................................................1118.5.1.1 A Stack Failed to Be Set Up.................................................................................................................................111



vii

8.5.1.1.1 Common Causes................................................................................................................................................1118.5.1.1.2 Troubleshooting Flowchart................................................................................................................................1118.5.1.1.3 Troubleshooting Procedure................................................................................................................................1128.5.1.1.4 Relevant Alarms and Logs................................................................................................................................1138.5.1.2 Active/Standby Switchover Cannot Be Performed in a Stack.............................................................................1138.5.1.2.1 Common Causes................................................................................................................................................1138.5.1.2.2 Troubleshooting Flowchart................................................................................................................................1148.5.1.2.3 Troubleshooting Procedure................................................................................................................................1148.5.1.2.4 Relevant Alarms and Logs................................................................................................................................1148.6 TRILL.........................................................................................................................................................................1158.6.1 TRILL Neighbor Relationship Fails to Be Established...........................................................................................1158.6.1.1 Common Causes...................................................................................................................................................1158.6.1.2 Troubleshooting Flowchart...................................................................................................................................1158.6.1.3 Troubleshooting Procedure...................................................................................................................................1168.6.1.4 Relevant Alarms and Logs...................................................................................................................................1198.6.2 TRILL Traffic Failed to Be Forwarded...................................................................................................................1198.6.2.1 Common Causes...................................................................................................................................................1198.6.2.2 Troubleshooting Flowchart...................................................................................................................................1208.6.2.3 Troubleshooting Procedure...................................................................................................................................1208.6.2.4 Relevant Alarms and Logs...................................................................................................................................1228.6.3 TRILL In-band NMS Fails to Manage RBs............................................................................................................1228.6.3.1 Common Causes...................................................................................................................................................1228.6.3.2 Troubleshooting Flowchart...................................................................................................................................1228.6.3.3 Troubleshooting Procedure...................................................................................................................................1238.6.3.4 Relevant Alarms and Logs...................................................................................................................................1248.6.4 TRILL Fails to Be Enabled on an Interface.............................................................................................................1248.6.4.1 Common Causes...................................................................................................................................................1248.6.4.2 Troubleshooting Flowchart...................................................................................................................................1248.6.4.3 Troubleshooting Procedure...................................................................................................................................1258.6.4.4 Relevant Alarms and Logs...................................................................................................................................1269 Common Fault Diagnostic Commands.................................................................................1279.1 display Commands.....................................................................................................................................................1289.1.1 Overview.................................................................................................................................................................1289.1.2 Regular Expression in display Commands..............................................................................................................1289.1.3 Common display Commands...................................................................................................................................1329.2 reset Commands.........................................................................................................................................................1349.2.1 Overview.................................................................................................................................................................1349.2.2 reset Commands Clearing Packet Statistics.............................................................................................................1349.2.3 Using reset Commands............................................................................................................................................1349.3 Ping and Tracert..........................................................................................................................................................1359.4 Traps...........................................................................................................................................................................1389.5 Logs............................................................................................................................................................................139



viii

9.6 Packet Header Capturing Function.............................................................................................................................14010 Appendix: Indicators.............................................................................................................. 14410.1 Fan Module Indicator...............................................................................................................................................14510.2 Power Indicators.......................................................................................................................................................146



ix

1 Instructions for Maintenance EngineersAbout This Chapter

1.1 Precautions1.2 Backing Up Data1.3 Troubleshooting Process1.4 Ask for Help

CloudEngine 6800&5800 Series SwitchesTroubleshooting 1 Instructions for Maintenance Engineers


1

1.1 PrecautionsIf 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 thenrestore services.

l Strictly conform to operation rules and industrial safety standards, ensuring human anddevice 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. Onlyqualified personnel can perform key operations.

NOTEAfter commands are configured to troubleshoot faults, pay attention to the configuration validation modeto ensure that the configurations take effect. Unless otherwise specified, this manual defaults to theimmediate 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 commit command needs to be run

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

1.2 Backing Up DataSome faults cause resource or money loss for customers. Therefore, maintenance engineersshould focus on preventing faults and quickly restoring faults. Data backup helps you quicklylocate and recover faults. After a network is set up and operates normally, you should back upimportant data as soon as possible.Important data includes:l Complete network topology, including device models, versions, and networking diagraml Configuration files and license filesl System software and patch filesl (Optional) Logsl (Optional) Feature library

1.3 Troubleshooting ProcessSystematic troubleshooting is to find fault causes step by step, and finally recover the fault.Generally, troubleshooting steps include observing fault symptom, collecting information,analyzing problem, and finding the root cause. The possible causes of all faults can be groupedinto multiple cause sets, which make troubleshooting easier.



2

1.4 Ask for Help1.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 HotlineIf you cannot recover the fault, you can:l Contact the agent.

NOTE

Provide device and fault information to technical support personnel.



3

2 Forgetting PasswordsAbout This Chapter

This section describes how to recover the console port and Telnet passwords. You are advisedto keep passwords secure and change them regularly.

2.1 Recovering the Console Port Password2.2 Recovering the Telnet Login Password

CloudEngine 6800&5800 Series SwitchesTroubleshooting 2 Forgetting Passwords


4

2.1 Recovering the Console Port PasswordThree 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 PasswordIf you can log in to the device using Telnet and your user right is level 3 or higher, log in to thedevice 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 users command 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 AuthenStatus AuthorcmdFlag 34 VTY 0 00:06:53 TEL 10.135.18.67 pass yes Username : Unspecified

+ 35 VTY 1 00:00:00 TEL 10.135.18.91 pass yes Username : Unspecified

36 VTY 2 00:08:11 TEL 10.135.18.54 pass yes Username : Unspecified

Run the display user-interface command to view the user right of all users. VTY1 has acorresponding user right 15; therefore, you have the right to change the console portpassword. display user-interface Idx Type Tx/Rx Modem Privi ActualPrivi Auth Int 0 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. saveWarning: The current configuration will be written to the device.Are you sure to continue? [Y/N]:y



5

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

Modifying the Console Port Password Through the BIOS MenuThe BIOS allows you to clear the console port password so that the device does not check thepassword when you log in through the console port. Then the device restarts, enters the commandline interface, and prompts you to change the console port password.

CAUTIONl 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+B and enter the BIOSpassword ([email protected] by 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 throughthe 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. 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 1 Info: Save the configuration successfully.



6

2.2 Recovering the Telnet Login PasswordYou can use Telnet to remotely maintain and manage a device. If you forget the Telnet loginpassword, 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.

NOTEAfter 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 changingthe 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 1 Info: Save the configuration successfully.

After the configuration is complete, you can use the user name huawei and passwordhuawei@123 to 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 1 Info: Save the configuration successfully.

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



7

3 Information CollectionAbout This Chapter

This chapter describes the information collection method. You must collect detailed faultinformation before locating faults by yourself or contacting agents or Huawei technical supportpersonnel 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 Overview3.2 Collecting Diagnostic Information3.3 Health Status Information

CloudEngine 6800&5800 Series SwitchesTroubleshooting 3 Information Collection


8

3.1 OverviewAfter 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 Huaweitechnical support personnel:l Fault occurrence time, network topology, operations triggering the fault, fault symptom,

measures that you have taken and results, and affected servicesl Name, version, current configurations, interfaces of the faulty device. For the method of

obtaining these information, see 3.2 Collecting Diagnostic Information and 9.1.3Common display Commands.

l Logs generated when the fault occurs. For the method of obtaining the log information, seeCollecting Log Information.

3.2 Collecting Diagnostic InformationThe display diagnostic-information [ [ module-name ] & [ slot slot-id ] | file-name ]command displays the device diagnostic information on screen or outputs the information to atxt 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:/. Usingthe dir command in the user view can confirm file generation.After a device becomes faulty, provide the device diagnostic information to agents or Huaweitechnical support personnel immediately for fast fault location. For the method of transmittingthe diagnostic information from the device to your computer, see 4.4 Transferring Files UsingFTP/TFTP.

NOTE

l Executing this command requires a long time. You can press Ctrl+C to pause diagnosis informationdisplay on screen.

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

3.3 Health Status InformationThe device provides the display health command. You can run the command to check the healthstatus 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

CloudEngine 6800&5800 Series SwitchesTroubleshooting 3 Information Collection


9

4 System 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 File4.2 Restarting the Device4.3 Upgrading the Device4.4 Transferring Files Using FTP/TFTP

CloudEngine 6800&5800 Series SwitchesTroubleshooting 4 System Maintenance Methods


10

4.1 Restoring the Default Settings Using the ConfigurationFile

When the device is powered on, it reads the configuration file from the default directory forinitialization. Therefore, the configuration in the file is called the initial configuration. If noconfiguration file is stored in the default directory, the device uses the default parameters forinitialization. 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 defaultconfiguration file to the device.

2. Run the startup saved-configuration command to specify the default configuration filefor 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 upusing the current configuration.

4.2 Restarting the DeviceSome network faults will be rectified after you restart the device. This section describes how torestart a device.You can restart the device using any of the methods in the following table.

Table 4-1 Device restart methodsMethod DescriptionTurn off and then turn on the power switch torestart the device.

Cold restart is performed manually. In coldrestart, a device can be restarted only bypressing the power button, which haslimitations and is applicable to onsitemaintenance.Save the configurations in real time becausethe device will restart directly without savingthe current configuration.

Run the reboot command in the user view torestart the device.

Hot restart uses commands, which is adoptedby maintenance personnel who remotelymanages the device.In restart, the system asks whether to save theconfiguration, which effectively preventsconfiguration loss.



11

4.3 Upgrading the DeviceThe upgrade of a device is closely related to the released software versions. The correspondingupgrade guide is released with each new version and you can upgrade the device according tothe guide. To obtain the upgrade guides, visit http://support.huawei.com/enterprise, chooseSoftware > 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/TFTPDuring system maintenance such as software upgrade and configuration file backup, files mustbe 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 ServerFigure 4-1 Networking diagram

FTP Client FTP Server

192.168.0.2/24192.168.0.1/24MEth0/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 for the 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 --- 5 packet(s) transmitted 5 packet(s) received



12

0.00% packet loss round-trip min/avg/max = 3/6/18 ms

[~HUAWEI-MEth0/0/0] return

NOTEl 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 ping command 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)):ftpuser331 Password required for ftpuser.Enter password: 230 User logged in.

[ftp]4. Run the put command to upload files to the FTP server or run the get command 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 transferred 226 Transfer complete.FTP: 6482944 byte(s) received in 54.500 second(s) 1117.40Kbyte(s)/sec.[ftp]

PC Functioning as a TFTP ServerFigure 4-2 Networking diagram

TFTP Client TFTP Server

192.168.0.2/24192.168.0.1/24MEth0/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 put command to upload files to the TFTP server or run the tftp get commandto download files from the TFTP server to the device. tftp 192.168.0.2 get vrpcfg.zip vrpcfg1.zipInfo: Transfer file in binary mode. Please wait for a while... / 8174 bytes transferred



13

Info: Downloaded the file successfully. tftp 192.168.0.2 put vrpcfg.zip vrpcfg2.zipInfo: Transfer file in binary mode. Please wait for a while... / 100% [***********] Info: Uploaded the file successfully.

Device Functioning as an FTP ServerFigure 4-3 Networking diagram

FTP Server FTP Client

192.168.0.2/24192.168.0.1/24MEth0/0/0

1. Connect the PC and the device and configure IP addresses for them. For details, see PCFunctioning 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 ftp command on the FTP server. Run the get commandto download files to the FTP server or run the put command to upload files from the FTPserver 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.zip200 Port command okay.150 Opening ASCII mode data connection for vrpcfg.zip.226 Transfer complete.ftp: 5203 bytes sent in 0.01Seconds 346.87Kbytes/sec



14

NOTEIf you use the user name Administrator to log in to the PC, the output differs from the above.You can run the lcd command to view the path where backup configuration files are saved.The commands vary with the operating system. For details, see relevant help documentation of eachoperating system.



15

5 Startup FailuresAbout This Chapter

This section describes how to troubleshoot device startup failures.

5.1 Terminal Does Not Display Anything Or Displays Garbled Characters

CloudEngine 6800&5800 Series SwitchesTroubleshooting 5 Startup Failures


16

5.1 Terminal Does Not Display Anything Or DisplaysGarbled CharactersFault Description

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

Possible Causel 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 Roadmapl 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 Procedure1. 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 accordingto Power Module Troubleshooting.

2. Check whether the combo interface type is correct and whether the physical attributes ofthe PC is consistent with those of the serial interface. The default parameters are as follows:l Baud rate: 9600l Data bit: 8l Stop bit: 1l Parity check: Nonel Flow control: None

3. Ensure that the cable is firmly connected to the serial interface. You can replace it with anew cable to verify whether the cable is faulty.

CloudEngine 6800&5800 Series SwitchesTroubleshooting 5 Startup Failures


17

6 HardwareAbout This Chapter

6.1 Power Module Troubleshooting6.2 Fan Module Troubleshooting6.3 Optical Module Troubleshooting6.4 Interface Troubleshooting

CloudEngine 6800&5800 Series SwitchesTroubleshooting 6 Hardware


18

6.1 Power Module Troubleshooting6.1.1 The SYS and Power Module Indicators Are OffFault Description

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

Possible Causesl The power modules are turned off.l Power cables are not securely connected to the sockets.l The power modules are faulty.

Troubleshooting Procedure1. 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 powermodules to Huawei for repair.

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

6.2 Fan Module Troubleshooting6.2.1 The Indicator of a Fan Module Is Steady RedFault Description

The indicator of a fan module is steady red.

Possible Causesl 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.

Troubleshooting Procedure1. 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.l If fan blades are blocked by an obstacle, remove the obstacle.



19

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 DescriptionThe device is running properly and no fan alarm is generated; however, the fan noise is loud.

Common Causesl The fan rotation speed is high.

Troubleshooting Procedure1. Run the display device fan command to check the fan rotation speed.2. If the fan rotation speed is high, run the set fan-speed slot slot-id percent percent command

to reduce the fan rotation speed. The following is an example: system-view[~HUAWEI] diagnose[~HUAWEI-diagnose] set fan-speed slot 1 percent 50

CAUTIONReducing the fan speed may cause the overtemperature of the device. Therefore, use thiscommand with caution.

3. If the fan noise is still loud after the fan rotation speed is reduced, run the upgrade fancommand 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 DescriptionThe display device command 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 Abnormal NA PWR2 - Present On Registered Normal NA -----------------------------------------------------------------------------



20

Common Causesl The fan is not installed properly.l Fan blades are blocked or have heavy dust.

Troubleshooting Procedure1. 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 abrush to clean fan blades.

2. Run the upgrade fan command 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 DescriptionThe display device alarm hardware command 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 Causesl Fan blades are damaged.

Troubleshooting Procedure1. Use a new fan module.

6.3 Optical Module Troubleshooting6.3.1 Optical Modules on the Local and Remote Devices CannotCommunicateFault Description

An optical interface of a CE switch is connected to a remote device through an optical fiber. Thetwo optical interfaces are Down and cannot communicate with each other.

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

module.



21

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.

Troubleshooting Procedure1. 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-certifiedoptical module cannot ensure service reliability and stability. If a non-Huawei-certifiedoptical 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 transceiver command to check whether any alarm information

has been generated for the optical module. display interface 10ge 1/0/1 transceiver 10GE1/0/1 transceiver information: ------------------------------------------------------------------- Common information: Transceiver Type :10GBASE_SR Connector Type :LC Wavelength (nm) :850 Transfer Distance (m) :80(50um),30(62.5um),300(OM3) Digital Diagnostic Monitoring :YES Vendor Name :AVAGO Vendor Part Number :AFBR-703SDZ Ordering Name : ------------------------------------------------------------------- Manufacture information: Manu. Serial Number :AD1148A07G7 Manufacturing Date :2011-12-05 Vendor Name :AVAGO ------------------------------------------------------------------- Alarm information: LOS Alarm -------------------------------------------------------------------

If a LOS alarm is displayed, the local optical interface does not receive signals from theremote interface. Run the display this command in the interface view to check whether thetwo interfaces have been manually shut down. If an interface is shut down, run the undoshutdown command on the interface.



22

4. Run the display interface transceiver verbose command to display diagnostic informationabout the optical module on the interface. Check whether the diagnostic informationdisplays alarms about abnormal transmit or receive power. display interface 10ge 1/0/1 transceiver verbose 10GE1/0/1 transceiver information: ------------------------------------------------------------------- Common information: Transceiver Type :10GBASE_SR Connector Type :LC Wavelength (nm) :850 Transfer Distance (m) :80(50um),30(62.5um),300(OM3) Digital Diagnostic Monitoring :YES Vendor Name :AVAGO Vendor Part Number :AFBR-703SDZ Ordering Name : ------------------------------------------------------------------- Manufacture information: Manu. Serial Number :AD1148A07G7 Manufacturing Date :2011-12-05 Vendor Name :AVAGO ------------------------------------------------------------------- Alarm information: RxPower Low ------------------------------------------------------------------- Diagnostic information: Temperature (C) :34.77 Voltage (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.00 Default RX Power High Threshold (dBM) :3.01 Default RX Power Low Threshold (dBM) :-15.02 Current TX Power (dBM) :-2.57 Default TX Power High Threshold (dBM) :3.01 Default TX Power Low Threshold (dBM) :-9.00 ------------------------------------------------------------------- The display interface transceiver verbose command displays the current transmit andreceive power values of the optical module, as well as the default maximum and minimumpower values.l If RxPower Low is 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 themaximum transmission distance of the optical module. If the distance is within the



23

transmission distance of the optical module, check whether the optical module on theremote interface or the optical fiber is damaged. If they are damaged, replace them.

l If RxPower High is displayed, the receive signal strength is too high. The possiblereason is that the distance between the two devices is short but a long-distance opticalmodule is used. In this case, install an optical attenuator on the optical module to reducethe transmit power.

l If TxPower Low is displayed, the transmit signal strength on the local optical moduleis too low. This may cause a low receive power on the remote optical module. As aresult, the remote interface cannot turn Up or drops packets sent from the local interface.

l If TxPower High is displayed, the transmit signal strength on the local optical moduleis too high. This may cause a high receive power on the remote optical module. If thehigh 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 andreceive power alarms after the two interfaces have optical modules installed and connectedusing an optical fiber. Ensure that the transmit and receive power values of the two opticalmodules are in the normal range. Otherwise, traffic forwarding on the optical interfacesmay 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 interfacesare 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 opticalmodules or optical fiber has been damaged. If the interfaces are still Down, contact HuaweiTechnical Assistance Center.

6.4 Interface Troubleshooting6.4.1 A 40GE Interface Fails to Be Split into 10GE Interfaces or 10GEInterfaces Fail to Be Merged into A 40GE InterfaceFault Description

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

Common Causesl Corresponding commands are not correctly configured.l The card is not restarted.

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

1. Run the display current-configuration command to check whether configurationinformation about port split is available. If not, run the port split interface interface-type interface-number1 [ to interface-type interface-number2 ] command in thesystem view to split the 40GE interface into 10GE interfaces.

2. Run the display port split command to check the current interface status. If thecommand output displays the following information, restart the card. display port splitNote:*Enable : Enabled after board reset



24

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

l 10GE interfaces fail to be merged into a 40 GE interface.1. Run the display current-configuration command to check whether configuration

information about port split is available. If not, run the undo port split interfaceinterface-type interface-number1 [ to interface-type interface-number2 ] command inthe system view to merge 10GE interfaces into the 40GE interface.

2. Run the display port split command to check the current interface status. If thecommand 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/58 10GE4/0/59 10GE4/0/60 ----------------------------------------------------

6.4.2 An Electrical Interface Cannot Go UpFault 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 is 9216 Internet protocol processing : disabled IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 0025-9e95-7c10 Port Mode: COMMON COPPER, Port Split: - Speed : 10000, Loopback:NONE Duplex: FULL, Negotiation: ENABLE Mdi : AUTO, Last physical up time : - Last physical down time : 2013-04-09 16:27:40



25

Common Causesl The power cable is faulty.l Negotiation between the local and remote interfaces fails.

Troubleshooting Procedure1. Check the cable status. Run the virtual-cable-test command in the interface view to check

the cable status. If the cable status is displayed as Open or Short rather than OK, replacethe cable.

2. Check configurations on the local and remote interfaces.l If the remote interface works in auto-negotiation mode, run the restart command in the

local interface view to restart the interface.l If the remote interface works in non-auto negotiation and has a rate configured, run the

speed { 10 | 100 | 1000 } or speed { 100 | 1000 | 10000 } command in the local interfaceview to configure the same rate as that of the remote interface.

6.4.3 10GE Optical Interfaces Cannot Go UpFault Description

A 10GE optical interface cannot go up physically. The interface status is as follows: display interface 10ge4/0/210GE4/0/2 current state : DOWN (ifindex: 9) Line protocol current state : DOWN Description: Switch Port, PVID : 1, TPID : 8100(Hex), The Maximum Frame Length is 9216 Internet protocol processing : disabled IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 0025-9e01-0204 Port Mode: COMMON FIBER, Port Split: - Speed : 10000, Loopback: NONE Duplex: FULL, Negotiation: DISABLE Mdi : - Last physical up time : - Last physical down time : 2013-04-10 03:12:43 Current system time: 2013-04-13 10:42:27 ......

Common Causesl The type, rate, and wavelength of the local and remote optical modules are different.l An incorrect type or length of optical fiber is used.



26

l The optical module is incorrectly installed or the optical fiber fails.l Negotiation between the local and remote end fails.l The optical module fails.

Troubleshooting Procedure1. Ensure that the type, rate (10GE or GE), and wavelength of the local and remote optical

modules are the same. The remote optical module must transmit optical signals properly.2. Ensure that the local and remote optical modules have the same optical fiber transmission

mode (single-mode or multimode) and use optical fibers of proper length.l If the transmission distance is long, the optical module must use an optical attenuator

to prevent excessively high optical power.l If the transmission distance is short, use optical fibers of proper length.

3. Run the display interface [ interface-type interface-number ] transceiver verbosecommand to check whether optical module information is correct.l If alarm messages are displayed, install the optical module correctly or replace the

optical fiber. Then, run the restart command to restart the in

CloudEngine 6800&5800 V100R001C00 Troubleshooting Guide 02.pdf

Documents

Transcript of CloudEngine 6800&5800 V100R001C00 Troubleshooting Guide 02.pdf