Troubleshooting - Device Management (V100R002C00 - 02)

Quidway S9300 Terabit Routing Switch
V100R002C00
Troubleshooting - Device Management
Issue
02
Date
2009-09-30
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any
assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Copyright Huawei Technologies Co., Ltd. 2009. 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 the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
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 the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.


Contents
Contents
About This Document.....................................................................................................................1
1 Troubleshooting Overview......................................................................................................1-1
1.1 Classification of Troubleshooting...................................................................................................................1-2
1.1.1 Connectivity Faults................................................................................................................................1-2
1.1.2 Performance Faults.................................................................................................................................1-2
1.2 Objectives of Troubleshooting........................................................................................................................1-2
1.3 Methods of Fault Diagnosis............................................................................................................................1-3
1.4 Collection of Fault Information.......................................................................................................................1-3
1.5 Troubleshooting Assistance............................................................................................................................1-5
1.5.1 Customer Center.....................................................................................................................................1-5
1.5.2 Huawei Technical Support Website.......................................................................................................1-5
2 Routine Device Troubleshooting...........................................................................................2-1

2.1 Common Device Faults Overview..................................................................................................................2-2
2.2 Routine Troubleshooting.................................................................................................................................2-2
2.2.1 Collecting Information on Faults...........................................................................................................2-2
2.2.2 Locating Faults.......................................................................................................................................2-3
2.2.3 Removing Faults....................................................................................................................................2-4
2.3 Diagnostic Tools.............................................................................................................................................2-4
2.3.1 debugging Commands............................................................................................................................2-4
2.3.2 Commands for System Resetting and Channel Switchover...................................................................2-5
2.3.3 display Commands.................................................................................................................................2-6
3 Board Loading Troubleshooting.............................................................................................3-1

3.1 Board Loading Overview................................................................................................................................3-2
3.2 Troubleshooting Board Loading.....................................................................................................................3-2
3.2.1 Troubleshooting Flowchart....................................................................................................................3-2
3.2.2 Troubleshooting Procedure....................................................................................................................3-3
3.3 Troubleshooting Cases....................................................................................................................................3-3
3.3.1 File Loading Error..................................................................................................................................3-4
3.4 FAQs...............................................................................................................................................................3-5
3.5.2 debugging Commands............................................................................................................................3-5
Issue 02 (2009-09-30)

Contents

4 Board Registration Troubleshooting.....................................................................................4-1

4.1 Board Registration Overview..........................................................................................................................4-2
4.2 Troubleshooting Board Registration...............................................................................................................4-2
4.3.1 Failed to Register the LPU.....................................................................................................................4-4
4.3.2 LPU and Master Control Unit Cannot Communicate............................................................................4-5
4.3.3 Boards Cannot Be Powered On..............................................................................................................4-5
4.4 FAQs...............................................................................................................................................................4-6
5 CF Card Troubleshooting.........................................................................................................5-1
5.1 CF Card Overview..........................................................................................................................................5-2
5.2 Troubleshooting CF Card................................................................................................................................5-2
5.3 FAQs...............................................................................................................................................................5-3
6 POE Troubleshooting................................................................................................................6-1
6.1 Overview of PoE.............................................................................................................................................6-2
6.1.1 Introduction to PoE................................................................................................................................6-2
6.1.2 Power-on Process of PoE.......................................................................................................................6-2
6.1.3 PoE Working Mode Supported by theS9300.........................................................................................6-3
6.2.1 PoE Board Fails to Be Registered..........................................................................................................6-3
6.2.2 PSE Cannot Detect Any PD...................................................................................................................6-4
6.2.3 PSE Cannot Provide Power for PDs......................................................................................................6-5
6.3 Known Anomalies...........................................................................................................................................6-6
ii

Issue 02 (2009-09-30)

Figures
Figures
Figure 3-1 Board loading troubleshooting flowchart...........................................................................................3-3
Figure 4-1 Board registration flowchart...............................................................................................................4-3
Figure 5-1 CF card troubleshooting flowchart.....................................................................................................5-3
Issue 02 (2009-09-30)

iii

Tables
Tables
Table 6-1 Table 1-1 Commands used in manual mode........................................................................................6-3
Issue 02 (2009-09-30)


About This Document
About This Document

Purpose
This document describes the troubleshooting of the S9300. The content involves basic
knowledge, information collection, common troubleshooting flow, common troubleshooting
methods, and troubleshooting cases.
This document provides guides to troubleshoot the S9300.
Related Versions
The following table lists the product versions related to this document.
Product Name
Version
S9300
V100R002C00
Intended Audience
The intended audiences of this document are:
l
Commissioning engineer
System maintenance engineer
Organization
This document is organized as follows.
Issue 02 (2009-09-30)
Chapter
Description
1 Troubleshooting
Overview
This chapter describes the knowledge about troubleshooting

the S9300, including S9300 overview, troubleshooting
procedure, troubleshooting purposes, information collection,
and assistance.


About This Document
Chapter
Description
2 Routine Device
Troubleshooting
This chapter describes the knowledge about routine

troubleshooting, including common fault overview,
troubleshooting procedure, and diagnostic tools.
3 Board Loading
Troubleshooting

board loading, including board loading overview,
troubleshooting procedure, and troubleshooting cases.
4 Board Registration
Troubleshooting

board registration, including board registration overview,
troubleshooting procedure, troubleshooting cases, FAQs,
and diagnostic tools.
5 CF Card Troubleshooting
This chapter describes the knowledge about CF card,

including CF card overview, troubleshooting procedure, and
FAQs.
6 POE Troubleshooting
his chapter describes the knowledge about PoE, including

troubleshooting procedure.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
DANGER
WARNING
CAUTION
Indicates a hazard with a high level of risk, which if not

avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which
if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not
avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
TIP
Indicates a tip that may help you solve a problem or save

time.
NOTE
Provides additional information to emphasize or supplement

important points of the main text.
General Conventions
The general conventions that may be found in this document are defined as follows.
2

Issue 02 (2009-09-30)

About This Document
Convention
Description
Times New Roman
Normal paragraphs are in Times New Roman.
Boldface
Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic
Book titles are in italics.
Courier New
Examples of information displayed on the screen are in

Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
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. Several items or no item can be selected.
&<1-n>
The parameter before the & sign can be repeated 1 to n times.
A line starting with the # sign is comments.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Issue 02 (2009-09-30)
Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.


About This Document
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format
Description
Key
Press the key. For example, press Enter and press Tab.
Key 1+Key 2
Press the keys concurrently. For example, pressing Ctrl+Alt

+A means the three keys should be pressed concurrently.
Key 1, Key 2
Press the keys in turn. For example, pressing Alt, A means

the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action
Description
Click
Select and release the primary mouse button without moving

the pointer.
Double-click
Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag
Press and hold the primary mouse button and move the
pointer to a certain position.
Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Updates in Issue 02 (2009-09-30)

Based on issue 01 (2009-09-10), the document is updated as follows:
The following information is added:
l
Updates in Issue 01 (2009-09-10)

Initial commercial release.

Issue 02 (2009-09-30)

1 Troubleshooting Overview
Troubleshooting Overview
About This Chapter

This chapter describes the knowledge about troubleshooting the S9300, including S9300
overview, troubleshooting procedure, troubleshooting purposes, information collection, and
assistance.
1.1 Classification of Troubleshooting
This section describes the category of troubleshooting tasks.
1.2 Objectives of Troubleshooting
This section describes three purposes of troubleshooting.
1.3 Methods of Fault Diagnosis
This section describes the general methods and procedure of fault location.
1.4 Collection of Fault Information
This section describes how to collect fault information and locate the fault according to the
collected information.
1.5 Troubleshooting Assistance
This section shows the assistance methods provided by Huawei.
Issue 02 (2009-09-30)

1-1

1.1 Classification of Troubleshooting

This section describes the category of troubleshooting tasks.
1.1.1 Connectivity Faults
1.1.2 Performance Faults
1.1.1 Connectivity Faults

Connectivity faults include:
l
Hardware, medium, and power supply failure
Configuration error
Improper interactions
1.1.2 Performance Faults

Performance faults include:
l
Network congestion
Non-optimal route to the destination
Insufficient power supply
Routing loop
Network error
1.2 Objectives of Troubleshooting

This section describes three purposes of troubleshooting.
Objectives of troubleshooting are:
l
Fault diagnosis: obtaining the diagnostic information with the tools, locating the fault and
restoring the network
Network optimizing: finding out the defects in network plan and configuration, and
improving the performance
Routine maintenance: observing the running of the network, and detecting the
communication quality in time
Fault diagnosis is to use diagnostic tools to obtain diagnostic information, locate the fault, find
the reason, remove the fault, and make the network device operate in normal state.
Generally, a device fault may be caused by:
1-2
Connection failure of devices on the physical layer or hardware and line fault
Interface configuration fault of network device on the data link layer
Network protocol configuration or operation fault on the network layer
Performance or congestion fault on the transport layer

Issue 02 (2009-09-30)

l
Faults on the top three layers
You should diagnose the fault in terms of the OSI model from the physical layer. In this way,
locate the fault to recover the system.
1.3 Methods of Fault Diagnosis

This section describes the general methods and procedure of fault location.
You can use multiple tools for fault diagnosis, for example, diagnostic commands, network
management tools, and LAN analyzers.
The following lists how to diagnose a fault:
l
View the routing table.The ping, tracert and display, debugging commands are useful
tools to obtain the diagnostic information.
Always monitor the operation of the network.
Run the display diagnostic-information command to display the running information of

each module on the S9300. When a fault occurs in the system, the information helps the
engineer collect fault information and locate the fault.
Run the display interface command to obtain the information about each interface to be
detected.
Run the display cpu-usage command to display the usage of the CPU.
Run the display memory-usage command to display the usage of the memory.
Generally, the maintenance personnel troubleshoot the fault by the following five steps:
1.
Collect the all-around information and analyze the fault.
2.
Locate the fault range.
3.
Isolate the fault.
4.
Locate and remove the fault.
5.
Verify that the fault is removed.
1.4 Collection of Fault Information

This section describes how to collect fault information and locate the fault according to the
collected information.
In most cases, when asking for help, customers only describes a familiar problem, for example,
"I cannot log in to the FTP server". Then the personnel for maintenance and management should
guide the customers by a series of systematic, gradual and sequential questions to obtain all the
information about the fault.
Actually, locating the fault is a process in which the following questions should be asked:
l
Who Is Involved?
What Is the Fault?
When the Fault Occurs?
Where the Fault Occurs?
The preceding questions can be asked repeatedly.

Issue 02 (2009-09-30)

1-3

You should give questions continuously on the basis of the answer that the customer gives until
you obtain an exact knowledge about the fault.
Who Is Involved?
Does the failure involve one user, a group of users with common attributes, or all the users in
the network?
As for one user, you can ask questions from the following aspects:
l
The physical layer, including the network cable connecting the user's device
The hardware of the host
The software of the host, especially the network protocol
The IP address or subnet mask of the host
The default gateway
As for a group of users with common attributes or all the users, you can ask questions from the
following aspects:
l
The network device such as a hub or a switch
The interfaces of the router
The server
The setting of the access list
The configuration of VLAN
What Is the Fault?

Is it a connectivity fault or a performance fault? Is it a full connectivity fault or a partial
connectivity fault?
As for a full connectivity fault, you can ask questions from the following aspects:
l
Hardware
Remote telecom service
Routing protocols
As for a partial connectivity fault, you can ask questions from the following aspects:
l
The access list
The subnet mask
The incompatible routing protocols
As for a performance fault, you can ask questions from the following aspects:
1-4
Network congestion
Routing loop
Insufficient power supply
Non-optimal route
Issue 02 (2009-09-30)

When the Fault Occurs?

Is it an intermittent fault, a regular fault or a fault that occurred just now?
As for an intermittent fault, you can ask questions from the following aspects:
l
Network congestion or broadcast storm
Routing loop
Remote telecom service
Weak network medium
As for a fault that occurred just now, you can ask questions from the following aspects:
l
New hardware or medium error
New device or topology change
Change of access list configuration
Change of routing protocols
Where the Fault Occurs?

Does the fault occur in the core area, edge area or access area?
In the core area, you can ask questions from the following aspects:
l
Modification of routing protocols
Rerouting
Generally, a fault in the edge area is associated with the access list.
Possibly, a fault in the access area is associated with all the preceding questions.
1.5 Troubleshooting Assistance

This section shows the assistance methods provided by Huawei.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and
service. You can obtain the assistance for troubleshooting from the customer center or technical
support website.
1.5.1 Customer Center
1.5.2 Huawei Technical Support Website
1.5.1 Customer Center

The way to contact Huawei Customer Center is as follows:
Website of Huawei Technical Support: http://support.huawei.com
Mailbox of Huawei Technical Support: Support@huawei.com
1.5.2 Huawei Technical Support Website

Issue 02 (2009-09-30)

1-5

Huawei technical support website http://support.huawei.com describes all the products of

Huawei and covers:
l
Datacom and transmission
Switching and broadband
Optical and mobile communication
Intelligent and multimedia service
Supporting network
Parts closely related to troubleshooting are:

l
Documentation
Community
Documentation
The contents in Documentation involving datacom mainly include:
l
Product manuals that embody all the attached documentation about Huawei datacom
products
Functions and features that embody the application of new features of Huawei datacom
products
Case database that embodies all the troubleshooting cases and resolutions experienced by
Huawei technical support personnel
Precautions that embody all the points deserving attention in the use of Huawei datacom
products
Community
It provides a site for discussing the communications technology in terms of forum.
Any question about a fault can be posed here. A reply will be given promptly.
1-6

Issue 02 (2009-09-30)

2 Routine Device Troubleshooting
Routine Device Troubleshooting
About This Chapter

This chapter describes the knowledge about routine troubleshooting, including common fault
overview, troubleshooting procedure, and diagnostic tools.
2.1 Common Device Faults Overview
This section presents the category of common faults.
2.2 Routine Troubleshooting
This section describes the steps of routine troubleshooting.
2.3 Diagnostic Tools
This section describes the diagnostic tools for routine troubleshooting, namely, the commands
for system reboot and channel switchover, debugging commands, and display commands.
Issue 02 (2009-09-30)

2-1

2.1 Common Device Faults Overview

This section presents the category of common faults.
Depending on the severity and effect, device faults fall into the following two kinds:
l
Generic fault: refers to the fault found in routine device maintenance, which has minor
influence on the performance of the device.
Urgent fault: refers to the fault that results in system breakdown or service interruption,
which needs to be removed urgently.
The common device fault refers to the fault found in routine maintenance of the device.
2.2 Routine Troubleshooting

This section describes the steps of routine troubleshooting.
2.2.1 Collecting Information on Faults
2.2.2 Locating Faults
2.2.3 Removing Faults
2.2.1 Collecting Information on Faults

To collect the information on the faults can reduce the fault range and enhance the accuracy of
fault location. Collecting the information enhances the troubleshooting efficiency and decreases
the risk of the mistake in the operation of the device.
The following table lists the basic information that needs to be collected upon device faults and
the related commands.
Information
Command
Description
Basic information
display diagnosticinformation
This command is used to collect the

basic information of the device. It
displays the information of the
commands such as display currentconfiguration and display device.
The information of this command must
be collected when any network
problem occurs.
Note: Use this command after you
telnet the device. If you log in to the
S9300 through console, running this
command takes a long time and the
command cannot abort.
2-2
Version information
display version
Patch information
display patchinformation
You can run this command only in the

user view.

Issue 02 (2009-09-30)

Information
Command
Description
Detailed running
information of the
board
display device
Run the display device command to

display the running of the system.
System environment
information
display voltage slot
Run the display voltage slot slot-id

command to display the voltage status
on the board.
System temperature
display temperature slot
Run the display temperature slot slotid command to display the temperature
on the board.
Current configuration
display currentconfiguration
This command displays all the

configurations on the S9300. To find
out the desired information, you can
use regular expressions to filter the
configuration information.
Current time
display clock
Log
display logbuffer
Trap
display trapbuffer
Information on the
interface
display interface
This command displays the status of all

interfaces, while the display currentconfiguration interface command
displays the configuration information
of all interfaces.
Memory usage
display memory-usage
If no parameter is specified, the

memory usage of the active Master
Control Unit is displayed. Run the
display memory-usage slave
command to display the memory usage
of the standby Master Control Unit.
Run the display memory-usage slot
slot-id command to display the
memory usage of the LPU.
CPU usage
display cpu-usage
If no parameter is specified, the CPU

usage of the active Master Control Unit
is displayed. Run the display cpuusage slave command to display the
CPU usage of the standby Master
Control Unit. Run the display cpuusage slot slot-id command to display
the CPU usage of the LPU.
2.2.2 Locating Faults

Issue 02 (2009-09-30)

2-3

After collecting the information about faults, analyze it, judge the type and range of faults and
locate the faults.
The following common methods can be used to locate faults:
l
Analyzing the original information on faults
Analyzing alarm information
Analyzing the state of indicators
Analyzing with instrument and meters
Analyzing traffic statistics
Analyzing faults based on tests, for example:
Performing loopback
Comparing the running status with faults by shifting the interface, the sub-card or the
board to another one
Comparing the running status after the active/standby switchover
Resetting the register without power-off and with the configuration being saved
2.2.3 Removing Faults

After locating faults, remove faults with the following steps:
1.
Examine and repairing the line.
2.
Modify the configuration.
3.
Reset the board.
4.
Switch over the system.
5.
Replace the board.

This section describes the diagnostic tools for routine troubleshooting, namely, the commands
for system reboot and channel switchover, debugging commands, and display commands.
2.3.1 debugging Commands
2.3.2 Commands for System Resetting and Channel Switchover
2.3.3 display Commands

CAUTION
2-4
Be cautious to use the debugging command, especially the debugging all command, because
it can slow down the system. Disable the debugging immediately after it is finished.
Before enabling the debugging, run the terminal debugging and terminal monitor
commands so that the debugging information is displayed on the terminal.

Issue 02 (2009-09-30)

Run the following commands in the user view.

Action
Command
Enable the debugging of the protocol.
debugging all
Disable the protocol debugging.
undo debugging all
Display the debugging.
display debugging [ interface { interface-type

interface-number| interface-name } ] [ modulename ]
Debug active/standby switchover.
debugging ha { all | message | resendipc | state }
Disable active/standby switchover.
undo debugging ha { all | message | resendipc |

state }
Debugging functions of the S9300 are:

l
Debugging of system operation and management

The system operation and management module manages the router and the functional
modules, such as Master Control Unit, LPU, power supply, power distribution, fan module,
and communication module.
The functional modules have their respective debugging information. You can control the
output of the information by enabling or disabling the debugging. The debugging
information of the modules is very important for the analysis of the module and is helpful
to locate the faults.
Debugging of active/standby switchover

The high speed and stability feature the S9300. To achieve the stability, the S9300 is
designed with 1:1 backup of the Master Control Unit. When the active Master Control Unit
fails, the standby Master Control Unit replaces it at once to bear services. The active/standby
module carries out the smooth switchover of data. The module is vital to the system and
provides output of the debugging information.
2.3.2 Commands for System Resetting and Channel Switchover
CAUTION
Do confirm whether to run the following commands because the commands may slow down the
system or even interrupt services.
Run the following commands in the user view or the system view.
Issue 02 (2009-09-30)
View
Action
Command
User view
Reset the board on the slot.
reset slot slot-id
Restart the S9300.
reboot

2-5

View
Action
Command
System
view
Restart the standby Master Control

Unit.
slave restart
Enable or disable active/standby

switchover by force.
slave switchover { enable | disable }
Perform active/standby
switchover by force.
slave switchover

Do as follows in any view.
Action
Command
Display version of the device.
display version
Display the alarm information or display alarm { all | slot slot-id }

status of the device.
2-6
Display the CPU usage of the

module.
display cpu-usage [ slave | slot slot-id ]
Display the memory usage.
display memory-usage [ slave | slot slot-id ]
Display the voltage status of the

module.
display voltage { all | slot slot-id }
Display the temperature of the

module.
display temperature { all | slot slot-id }
Display the power status.
display power
Display the patch version.
display patch-information
Display the status of the fan.
display fan

Issue 02 (2009-09-30)

3 Board Loading Troubleshooting
Board Loading Troubleshooting
About This Chapter

This chapter describes the knowledge about troubleshooting board loading, including board
loading overview, troubleshooting procedure, and troubleshooting cases.
3.1 Board Loading Overview
This section describes the knowledge you need to know before troubleshooting board loading.
3.2 Troubleshooting Board Loading
This section presents the flowchart and procedure of board loading troubleshooting.
3.3 Troubleshooting Cases
This section presents several troubleshooting cases.
3.4 FAQs
This section lists frequently asked questions and their answers.
This section describes the diagnostic tools for troubleshooting, namely the display and
debugging commands.
Issue 02 (2009-09-30)

3-1

3.1 Board Loading Overview

This section describes the knowledge you need to know before troubleshooting board loading.
Loading is an important module in the device management. Through board loading, system and
logical software can be downloaded from the CF card of the Master Control Unit to the storage
area of the LPU.
The storage area of the LPU falls into two categories:
l
BootROM
Logical chip
The types of the loaded software on different hardware are different, including:
l
BIOS, EPLD ( Erasable Programmable Logic Device ) for LPU
There are three ways to load the software:

l
Start-up loading: After the main system started, the board downloads the software to the
storage area of the relevant board according to the hardware type. The whole process
completes automatically. The loading files vary with board types, so the S9300 identifies
the loading files with different IDs.
On-line loading: It is also called force-loading and indicates that the relevant software
(except EPLD) or logical file is loaded to the board by the command line.
3.2 Troubleshooting Board Loading

This section presents the flowchart and procedure of board loading troubleshooting.
3.2.1 Troubleshooting Flowchart
3.2.2 Troubleshooting Procedure

If the board cannot register for a long time, and the display load fail-info command shows that
the board is not loaded, solve the problem according to Figure 3-1.
3-2

Issue 02 (2009-09-30)

Figure 3-1 Board loading troubleshooting flowchart

Board
loading fails
Enable
debugging
Is there
loading
information?
Upgrade the
system
through JTAG
No
Yes
Run display
load fail-info
Locate the fault
Fault
removed?
No
Technical
support
Yes
End

Procedure
Step 1 Run the debugging load info and debugging load event commands to enable debugging to see
whether there is loading information.
Step 2 If there is loading information, run the display load fail-info command to display the failure
information. Then locate the fault according to the failure information.
Step 3 If there is no loading information, run the following commands to upgrade the system:
<Quidway> upgrade all cfcard:/b02g.cc lpu_bootrom
----End

Issue 02 (2009-09-30)

3-3

3.3.1 File Loading Error
3.3.1 File Loading Error

Scenario
After software loading, the S9300 is restarted. The Master Control Unit registers normally, but
some LPUs cannot register, and the "file's id error" message is outputted continuously, as shown
below:
%Oct 20 15:05:08 2008 CONNEX_PE1 LOAD/5/LOADRESULT:LoadResult:
Download of software to LPU board on slot 5 has failed
LPU on slot 5 occurs error, error Code:3, Error message:file's id error.
Total 3 file(s) matched, 0 file(s) download to 5 LPU.
Download file(ID/Index):331160a/58
340000a/12
350000a/13
Fault Analysis
You can enable the debugging:
<Quidway> debugging load packet snd
<Quidway> debugging load packet rcv
<Quidway> debugging load event
The following debugging information is displayed:

Total 3 file(s) matched, 0 file(s) download to 5 LPU.Download file(ID/Index):
331160a/58
340000a/12
350000a/13
In normal case, three files should be downloaded, but the debugging information shows that no
file is downloaded. That is to say, an error occurs when the first file is downloaded.
Run the dir command to check the system files:
<Quidway> dir
Directory of cfcard:/
0
-rw- 46424064
1
-rw44
2
-rw12001
3
-rw5709
4
-rw947
Oct
Oct
Oct
Oct
Oct
19
20
19
19
20
2008
2008
2008
2008
2008
15:49:18
14:30:22
18:06:58
18:07:04
14:30:24
s9300.cc
private-data.txt
paf.txt
license.txt
connex-pe1.cfg
The size of the system file is 46424064 bytes, while the size of the large package file released
with the product is 70000000 bytes.
Procedure
Step 1 Obtain the latest system software version and load it to the S9300.
Step 2 Run the startup system-software filename command to specify system software for the S9300
and restart the S9300.
If the fault persists, contact Huawei engineers.
----End
Summary
If the "file's id error" message is displayed, it indicates that the system file is incorrect. It is
possible that the loading of system file aborts. Therefore, some LPUs cannot register.
3-4

Issue 02 (2009-09-30)

3.4 FAQs
l
Q:Why Is the "write flash error" Message Displayed During LPU Start-up?
A: After reboot, the S9300 can work only after the system file is loaded from the Master
Control Unit to the Flash memory of the LPU. If the message is displayed, it indicates that
the board should be repaired.

This section describes the diagnostic tools for troubleshooting, namely the display and
debugging commands.

Command
Description
display load fail-info [ slot-id ]
Displays the reason for LPU loading failure.
NOTE
The display load fail-info command can run only in the user view.
display load fail-info

<Quidway> display load fail-info 6
S9306's Slot 6 Load Down Fail Info:
Total Fail Num: 0, OnLine Fail Num: 0 Startup Fail Num: 0
Issue 02 (2009-09-30)
Command
Description
debugging load info
Debugs the Load module.
debugging load event
Debugs the events of the Load module.
debugging load jtag
Debugs the JTAG module.
debugging load packet snd
Debugs packet sending of the Load module.
debugging load packet rcv
Debugs packet receiving of the Load module.
debugging load packet

s_detail
Debugs packet details sending of the Load module.

3-5

3-6
Command
Description
debugging load packet

r_detail
Debugs packet details receiving of the Load module.

Issue 02 (2009-09-30)

4 Board Registration Troubleshooting
Board Registration Troubleshooting
About This Chapter

This chapter describes the knowledge about troubleshooting board registration, including board
registration overview, troubleshooting procedure, troubleshooting cases, FAQs, and diagnostic
tools.
4.1 Board Registration Overview
This section describes the knowledge you need to know before troubleshooting board
registration.
4.2 Troubleshooting Board Registration
This section describes the procedure for board registration troubleshooting.
4.4 FAQs
This section describes the diagnostic tools for troubleshooting, namely the display commands.
Issue 02 (2009-09-30)

4-1

4.1 Board Registration Overview

This section describes the knowledge you need to know before troubleshooting board
registration.
Registration is a key part of device management. Registration indicates that the active Master
Control Unit manages the board after all hardware and software are initialized on the board
without any problems and the state of the board is reported to the active Master Control Unit.
In the registration process, the board needs to interact with the Master Control Unit.
Processing of the LPU

1.
Sends the registration request to the Master Control Unit. The request contains the version
and initialization self-check information of each module.
2.
Exits registration after receiving the registration response.
Processing of the Master Control Unit

1.
Receives the registration request from the LPU and check the self-check information.
2.
If the self-check information is correct, records the LPU information and sends a response
to the LPU. If the self-check information is incorrect, resets the LPU and records the
resetting reason in log and reports the alarm.
4.2 Troubleshooting Board Registration

This section describes the procedure for board registration troubleshooting.
CAUTION
Do not draw out the board or reset the board when the bootrom program or bootload program
is loading on the LPU; otherwise, the program will be damaged, and you should contact Huawei
engineers to repair it.
4-2

Issue 02 (2009-09-30)


Figure 4-1 Board registration flowchart
Board startup fails
Board
registration
error?
No
See board loading

troubleshooting
Yes
Enable
debugging
Fault removed?
No
Technical
support
Yes
End

Procedure
Step 1 Check whether the board is not registered within the start-up time. If it is still within the startup time, wait until the start-up time does not expire.
Start-up time refers to a period from the board power-on to registration. The start-up time of
each type of board is as follows:
l
The start-up time of the Master Control Unit is within three minutes. If the S9300 is restarted
after system upgrade, the start-up time is within five minutes.
The start-up time of the LPU is within five minutes. If the system software is upgraded, the
start-up time is within 10 minutes.
Step 2 Check whether the board start-up failure is caused by board registration fault.
l
Check whether the board registration fails. If it is a board registration fault, remove the fault
by referring to "3 Board Loading Troubleshooting".
Run the display device command to check the board status.
Step 3 Find the reasons for board resetting by commands.

If the board does not complete the registration beyond the startup time, process it as follows:
Running the display logbuffer slot slot-id command, you can check reasons for board resetting,
and then locate the faults according to the fault cause.
<Quidway> display logbuffer slot 5
Logging buffer configuration and contents:enabled
Allowed max buffer size : 1024
Actual buffer size : 512
Issue 02 (2009-09-30)

4-3

Channel number : 4 , Channel name : logbuffer

Dropped messages : 0
Overwritten messages : 0
Current messages : 107
If the reason why the board does not register cannot be displayed by the display logbuffer
slot slot-id command, it means that the board never registers. Then you need to check that the
board is loaded successfully by connecting the board with a serial port cable. For detailed
procedure, see "3 Board Loading Troubleshooting".
----End

4.3.1 Failed to Register the LPU
4.3.2 LPU and Master Control Unit Cannot Communicate
4.3.3 Boards Cannot Be Powered On
4.3.1 Failed to Register the LPU

Scenario
During the registration of LPU, the system prompts you that the software loading on the board
is incomplete when you run the following commands:
<Quidway> reset slot 1
Caution!!! Confirm to reset slot 1! Continue?[Y/N]?y
<Quidway> terminal monitor
Info:Current terminal monitor is on
<Quidway> terminal logging
Info:Current terminal logging is on
Fault Analysis
The possible reasons are as follows:
l
When the S9300 is started, the main system loads logical software automatically. The
versions of the small system and the main system must be matched; otherwise, the loading
cannot complete.
Procedure
Step 1 Run the check version command to check whether the versions of the main system and the small
system are matched. If they are unmatched, upgrade the version which is earlier.
<Quidway> upgrade all startup

----End
4-4

Issue 02 (2009-09-30)

4.3.2 LPU and Master Control Unit Cannot Communicate

Scenario
None.
Fault Analysis
The LPU cannot register for a long time. The log is as follows:
%Oct 15 11:34:19 2008 Quidway ALML/4/ENTRESET:
LPU6 is reset, The reason is:
Warm reset board for no receiving message in a long time
The preceding log is generated if the LPU cannot communicate with the active Master Control
Unit in three minutes.
The possible causes of communication failure are as follows:
l
The LPU is not well connected to the backplane.
The EPLD of the LPU is not upgraded.
Procedure
Step 1 Insert the LPU again.
Step 2 Upgrade the EPLD through JTAG. For detailed procedure, see 4.3.1 Failed to Register the
LPU.
Step 3 Wait three minutes. If the fault is not removed, upgrade the software version of the main system
and the small version through JTAG. For detailed procedure, see 4.3.1 Failed to Register the
LPU.
----End
4.3.3 Boards Cannot Be Powered On

Scenario
When the S9300 is powered on, the fan works normally, but all the boards cannot be powered
on. The indicators such as RUN and ACTIVE are off.
Fault Analysis
The possible reasons are as follows:
l
The backplane is faulty.
The Master Control Unit is faulty. The LPUs cannot be powered on if the Master Control
Unit is not powered on.
Issue 02 (2009-09-30)

4-5

Procedure
Step 1 Pull out all the LPUs and power on the S9300 again. Check whether the Master Control Unit
can be powered on.
----End
4.4 FAQs
l
Q: Can the LPU Be Powered On Separately?

A: No. The LPU can be powered on only after the Master Control Unit is powered on.

This section describes the diagnostic tools for troubleshooting, namely the display commands.
4-6
Command
Description
display device
Displays the basic information on the S9300.

Issue 02 (2009-09-30)

CF Card Troubleshooting
About This Chapter

This chapter describes the knowledge about CF card, including CF card overview,
troubleshooting procedure, troubleshooting cases, and FAQs.
5.1 CF Card Overview
This section describes the knowledge you need to know before troubleshooting the CF card.
5.2 Troubleshooting CF Card
This section describes the flow and procedure of CF card troubleshooting.
5.3 FAQs
This section lists the frequently asked questions and their answers.
Issue 02 (2009-09-30)

5-1

5.1 CF Card Overview

This section describes the knowledge you need to know before troubleshooting the CF card.
CAUTION
The compact flash (CF) card on the panel of the Master Control Unit does not support hot swap.
The S9300 has one CF card, which is installed on the panel of the Master Control Unit. The CF
card stores system file, configuration file, PAF, license file, and log files.
The log files of the S9300 are stored in the CF card, so the storage space of the CF card may be
full when the S9300 operates for a long time. In this case, the S9300 deletes the log files by
generation date. The earliest log file is deleted first. To save the log files, you can transfer the
files through FTP or TFTP, and then delete the files from the CF card.
5.2 Troubleshooting CF Card

This section describes the flow and procedure of CF card troubleshooting.

CAUTION
The CF card is not hot swappable. Do not remove or insert the CF card when the S9300 is in
operation.
If the preceding problem occurs when you plug the CF card or one minute later after you plug
the CF card, solve the problem following Figure 5-1.
5-2

Issue 02 (2009-09-30)

Figure 5-1 CF card troubleshooting flowchart

An error occurs in
the CF card
Is CF card
plugged?
Yes
Reset the MPU
Fault
removed?
Yes
No
No
Is storage
space full?
Yes
Transfer log files

and release storage
space
Fault
removed?
Yes
No
No
Replace the
CF card
Fault
removed?
Yes
End
No
Technical
support

Procedure
Step 1 Check whether the CF card is operating when you plug the CF card. If it is operating, restart the
Master Control Unit.
Step 2 Run the dir command to check the idle space in the CF card. If the storage space of the CF card
is full, transfer the log files, and then delete the log files from the CF card.
Step 3 If the fault still exists, the CF card may be damaged. Contact Huawei engineers to replace the
CF card.
----End
5.3 FAQs
This section lists the frequently asked questions and their answers.
l
Q: How Can I Do When the CF Card Is Occupied by Log Files?

A: Transfer the log files through FTP or TFTP. Do not replace the CF card in this case.
Issue 02 (2009-09-30)

5-3

POE Troubleshooting
About This Chapter

This chapter describes the method to troubleshoot the POE faults.
6.1 Overview of PoE
This section provides an introduction to the PoE power.
This section provides several troubleshooting cases.
6.3 Known Anomalies
This section describes the known anomalies of the PoE feature on theS9300.
Issue 02 (2009-09-30)

6-1

6.1 Overview of PoE

This section provides an introduction to the PoE power.
6.1.1 Introduction to PoE
6.1.2 Power-on Process of PoE
6.1.3 PoE Working Mode Supported by theS9300
6.1.1 Introduction to PoE

Power over Ethernet (PoE) involves the power sourcing equipment (PSE) and the power device
(PD). The PoE technology is used on the wired Ethernet and is most widely used on local area
networks (LANs). This technology transmits power coupled with data to terminals through
cables or transmits power without data through idle lines. The S9300 transmits power coupled
with data at a rate of 1000 Gbit/s.
Currently, the S9300 V100R001 does not support the PoE feature, and the S9300 V100R002
supports this feature.
6.1.2 Power-on Process of PoE

This section describes the standard power-on process of PoE. The S9300 can automatically
complete steps 1, 2, 4, and 5. Step 3 can be performed automatically or manually and the actual
operation varies in the two modes:
l
In automatic mode, you do not need to perform any operation.
In manual mode, you need to run certain commands to complete the operation.
The PSE powers on a PD as follows:

1.
Detection: The PSE detects whether the PD exists.

The PSE detects whether the PD exists by detecting the capacitive resistance between
output power supply pairs. In the detection stage, the PSE provides certain voltage, and
then calculates the feature resistance of the PD based on the returned current. The PSE
proceeds to the next step only if the feature resistance of the PD is within the valid range.
2.
Classification: The PSE determines the power consumption of the PD.

The PSE determines the power level of the PD according to the output current. In the
classification stage, the port connected to the PD provides certain voltage, and then
calculates the power range according to the returned current.
3.
Power-on: The PSE provides power for the PD.

When detecting that the downstream device connected to the port is a valid PD and
classifying the PD, the PSE provides -48 V power for the PD.
6-2
4.
RTP & Power management: The PSE provides functions of over-current protection,
current/voltage detection, short-circuit protection, open-circuit protection, and
troubleshooting.
5.
Disconnection: The PSE detects whether the PD is disconnected.

Issue 02 (2009-09-30)

The PSE detects whether the PD is disconnected by using a special detection method. If
the PD is disconnected, the PSE shuts down the port to stop providing the voltage. The port
then enters the detection state.
6.1.3 PoE Working Mode Supported by theS9300

Automatic Mode
In automatic mode, the PSE automatically detects, classifies, and powers on PDs. If no valid PD
is detected on a port, the PSE repeats the detection step until it detects a valid PD.
Manual Mode
In manual mode, the PSE automatically detects and classifies PDs but does not power on PDs.
You need to run certain commands to power on PDs. To manually power on or power off PDs,
you must set the PoE working mode of the relevant board to manual mode in system mode.
Table 6-1 describes the commands that are used in manual mode.
Table 6-1 Table 1-1 Commands used in manual mode
Function
Command
Set the POE working mode

to manual mode.
poe power-management { auto | manual }

slot slot-id
Power on PDs on a
specified port manually.
poe power-on interface { interface-name |

interface-type interface-num}
Power off PDs on a

specified port manually.
poe power-off interface { interface-name |

interface-type interface-num}

This section provides several troubleshooting cases.
6.2.1 PoE Board Fails to Be Registered
6.2.2 PSE Cannot Detect Any PD
6.2.3 PSE Cannot Provide Power for PDs
6.2.1 PoE Board Fails to Be Registered

Fault Symptom
After the DIMM is installed on a PoE board, the board cannot be registered. The following
information is displayed when the PoE board starts:
POE fatal error!System will reboot![chipIndex:0]
Issue 02 (2009-09-30)

6-3

Fault Analysis
This fault occurs usually because the PoE power supply does not provide power.
1.
1. Ensure that the PoE power supply is well connected.
2.
2. If the PoE power supply is well connected, ensure that the PoE power supply is powered
on and works normally.
Run the following command to view information about the PoE power supply in the
corresponding slot.
<Quidway> display poe-power
Available total POE power(mW) : 800000
System reserved POE power(mW) : 48000
User reserved POE power percent : 20
POE power backup-mode
: 2+0
POE power 1 :
Power value(mW) : Voltage value(V) : Current value(A) : POE power 2 :
Power value(mW) : 800000
Voltage value(V) : 53.57
Current value(A) : 0.24
If the PoE power supply works normally, it indicates that the fault lies in the DIMM. In
this case, you need to replace the DIMM. Remove the PoE board from the subrack, and
then replace the DIMM.
6.2.2 PSE Cannot Detect Any PD

Fault Symptom
After a PD is connected to a port of the S9300, this port keeps in Detecting state.
Fault Analysis
Theoretically, a port can automatically detect and classify a PD are the PD is connected. If the
power of the port is sufficient, the port can provide power for the PD automatically. If the power
of the port is insufficient, the port keeps in Classification completed state. If the port retains in
the Detecting state after a PD is connected, locate the fault as follows:
1.
Check whether the PD is an device according with 802.3af or 80.2.3at.
2.
Run the following command to view the status of each PoE port on the board.
<Quidway> display poe power-state slot 4
PortName
PowerOn/Off Enabled Priority
Status
------------------------------------------------------------------------------GigabitEthernet4/0/0
off
enable
Low
Classification
completed
GigabitEthernet4/0/1
off
enable
Low
Detecting
off
enable
Low
Detecting
off
enable
Low
Detecting
off
enable
Low
Detecting
Find the port that is connected to the PD and is in Detecting state.
6-4
3.
Replace the network cable of the port and check whether the fault is rectified.
4.
If the network cable is normal, check the grounding of the S9300. If the S9300 is not
grounded, ground it.
Issue 02 (2009-09-30)

5.
If the S9300 is grounded, check whether the PD is faulty.

Method:
Move the PD to another working port, and then run the display PoE power-state command
to check the status of the port. If the port is in Powered state, it indicates that the original
port is faulty. If this port still fails to detect the PD, it indicates that the PD is faulty.
6.
If the fault cannot be located, contact Huawei technical personnel.
6.2.3 PSE Cannot Provide Power for PDs

Fault Symptom
After a PD is connected to a port of the S9300 through a network cable, the PD cannot be powered
on.
Fault Analysis
Theoretically, a port can automatically detect and classify a PD when the PD is connected to the
port. If the power of the port is sufficient, the port can provide power for the PD automatically.
If the power of the port is insufficient, the port keeps in Classification completed state. If the
port keeps in Classification completed state but cannot power on the PD, do as follows to locate
the fault:
1.
Run the following command to view the status of each PoE port on the board.
<Quidway> display poe power-state slot 4
PortName
PowerOn/Off Enabled Priority
Status
------------------------------------------------------------------------------GigabitEthernet4/0/0
off
enable
Low
Power condition is
good
off
enable
Low
Power condition is
good
off
enable
Low
Power condition is
good
off
enable
Low
Power condition is
good
off
enable
Low
Classification
completed
2.
Run the following command to view information about the port that fails to be powered
on.
<Qwidway> display poe power-state interface GigabitEthernet 4/0/4
Port power enabled
: enable
Port power ON/OFF
: off
Port power status
: Classification completed
Port PD class
: 0
Port reference power(mW)
: 15400
Port power priority
: low
Port max power(mW)
: 20000
Port current power(mW)
: 0
Port peak power(mW)
: 0
Port average power(mW)
: 0
Port current(mA)
: 0.00
Port voltage(V)
: 0.00
Issue 02 (2009-09-30)
The value of Port power enabled must be enable.
The Port reference power(mW) field indicates the reference power of the port. If this
port needs to power a PD, the available power of the board must be greater than or equal
to the reference power of the port.
6-5

l
3.
The Port max power(mW) field indicates the maximum power of the port. If this port
needs to power a PD, the maximum power of the port must be greater than or equal to
the reference power of the port.
Run the following command to check the power supply information in the corresponding
slot.
<Quidway> display poe information slot 4
Codes: USMPW(User Set Max Power), AVTPW(Available Total Power),
TRPW(Total Reference Power), TPWC(Total Power Consumption),
PKVAL(Peak Value), PWMGM(Power-Management mode)
Slot 4
------------------------------------------------------------------------------------------------------------------USMPW(mW) AVTPW(mW) TRPW(mW) TPWC(mW) PKVAL(mW) PWMGM
1440000
592000
60000
4586
5000
auto
-------------------------------------------------------------------------------------------------------------------
(1) Check the value of AVTPW. If the value is 0, it indicates that the board does not
obtain power, and hence cannot provide power for the port.
(2) The value of PWMGM should be auto. If the value of PWMGM is manual, run the
poe power-on interface { interface-name | interface-type interface-num } command
in the system view to power on the port manually.
(3) Calculate the available power of the board by using the formula: Available power =
Min. (USMPW, AVTPW) TPWC.
Compare the reference power of the port with the available power of the board. If the
reference power of the port is larger, it indicates that the available power of the board
is insufficient for the PD.
(4) 4. Run the following command to view information about the PoE power supplies.
Check whether at least one PoE power supply works normally.
<Quidway> display poe-power
Available total POE power(mW) : 800000
System reserved POE power(mW) : 48000
User reserved POE power percent : 20
POE power backup-mode
: 4+0
POE power 1 :
Power value(mW)
: Voltage value(V) : Current value(A) : POE power 2 :
Power value(mW)
: Voltage value(V) : Current value(A) : POE power 3 :
Power value(mW) : 800000
Voltage value(V) : 53.47
Current value(A) : 0.21
POE power 4 :
Power value(mW)
: Voltage value(V) : Current value(A) : -
(5) 5. If at least one PoE power supply works normally, check the value of User reserved
POE power percent. If the value is 100, it indicates that all the power of the PoE
power supply is reserved, so the port cannot be powered on.
6.3 Known Anomalies

This section describes the known anomalies of the PoE feature on theS9300.
6-6

Issue 02 (2009-09-30)

Some Ports May Fail to Be Powered on If the S9300 Is Not Grounded

Layout of network cables is uncontrollable, so network cables easily undergo interference of
signals, for example, from a large power base station. When the S9300 is not grounded, the
disturbance signals may affect the detection signals in network cables. As a result, the S9300
cannot detect PDs, and hence cannot power on the PDs.
PoE Function Is Unavailable on All Ports Due to Faults of PoE Power Supplies
When the S9300 Works Under Full Power
Assume that two 800 W PoE power supplies are installed on an S9312, so the total power of the
system is 1600 W. When the total power consumption of the S9300 exceeds 800 W and a PoE
power supply is faulty at this time, the system software cannot shut down PoE ports in time.
Therefore, the instant power is too large, causing over-load protection of the other PoE. Then
all PDs are powered off. After the PoE power recovers, the S9300 powers on the PoE ports
according to their priorities.
Issue 02 (2009-09-30)

6-7

Troubleshooting - Device Management (V100R002C00 - 02)

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Troubleshooting - Device Management (V100R002C00 - 02)

Hochgeladen von

Copyright:

Verfügbare Formate

Quidway S9300 Terabit Routing Switch