Transcript
HUAWEI NetEngine5000E Core Router V800R002C01
Troubleshooting - Interface and Data Link Issue
01
Date
2011-10-15
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd. Address:
Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China
Website:
http://www.huawei.com
Email:
[email protected]
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
i
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
About This Document
About This Document Intended Audience This document describes the troubleshooting workflow and methods for HUAWEI NetEngine5000E. This document describes the troubleshooting of HUAWEI NetEngine5000E with various services, including information collection methods, common processing flows, common troubleshooting methods, and troubleshooting cases. This document is intended for: l
System maintenance engineers
l
Commissioning engineers
l
Network monitoring engineers
Related Versions (Optional) The following table lists the product versions related to this document. Product Name
Version
HUAWEI NetEngine5000E Core Router
V800R002C01
Symbol Conventions The symbols that may be found in this document are defined as follows. Symbol
Description Alerts you to a high risk hazard that could, if not avoided, result in serious injury or death. Alerts you to a medium or low risk hazard that could, if not avoided, result in moderate or minor injury.
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
ii
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
Symbol
About This Document
Description Alerts you to a potentially hazardous situation that could, if not avoided, result in equipment damage, data loss, performance deterioration, or unanticipated results. Provides a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points in the main text.
Command Conventions (Optional) 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.
Change History Updates between document issues are cumulative. Therefore, the latest document issue contains all updates made in previous issues.
Changes in Issue 01 (2011-10-15) The initial commercial release. Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
iii
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
Contents
Contents About This Document.....................................................................................................................ii 1 GE Interface Troubleshooting....................................................................................................1 1.1 The Physical Status of GE Interfaces Cannot Go Up.........................................................................................2 1.1.1 Common Causes........................................................................................................................................2 1.1.2 Troubleshooting Flowchart........................................................................................................................2 1.1.3 Troubleshooting Procedure........................................................................................................................3 1.1.4 Relevant Alarms and Logs........................................................................................................................4
2 Eth-Trunk Interface Troubleshooting.......................................................................................5 2.1 Eth-Trunk Interface Cannot Forward Traffic.....................................................................................................6 2.1.1 Common Causes........................................................................................................................................6 2.1.2 Troubleshooting Flowchart........................................................................................................................6 2.1.3 Troubleshooting Procedure........................................................................................................................8 2.1.4 Relevant Alarms and Logs......................................................................................................................10 2.2 Trouble Cases...................................................................................................................................................11 2.2.1 Certain Users Cannot Access the Internet by Dialing Up After a Member Interface of the Eth-Trunk Interface Becomes Faulty.................................................................................................................................11
3 POS Interface Troubleshooting................................................................................................13 3.1 The Physical Status of POS Interfaces Cannot Go Up.....................................................................................14 3.1.1 Common Causes......................................................................................................................................14 3.1.2 Troubleshooting Flowchart......................................................................................................................14 3.1.3 Troubleshooting Procedure......................................................................................................................15 3.1.4 Relevant Alarms and Logs......................................................................................................................17
4 PPP Troubleshooting..................................................................................................................18 4.1 Protocol Status of a PPP Interface Is Down.....................................................................................................19 4.1.1 Common Causes......................................................................................................................................19 4.1.2 Troubleshooting Flowchart......................................................................................................................19 4.1.3 Troubleshooting Procedure......................................................................................................................20 4.1.4 Relevant Alarms and Logs......................................................................................................................24
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
iv
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
1
1 GE Interface Troubleshooting
GE Interface Troubleshooting
About This Chapter 1.1 The Physical Status of GE Interfaces Cannot Go Up
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
1
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
1 GE Interface Troubleshooting
1.1 The Physical Status of GE Interfaces Cannot Go Up 1.1.1 Common Causes This fault is commonly caused by one of the following: l
Optical modules are not matched.
l
Optic fiber is incorrectly connected.
l
Types of optic fiber and optical modules are not matched.
1.1.2 Troubleshooting Flowchart If the physical layer of GE interface cannot be Up, perform the troubleshooting flow as shown in Figure 1-1. Figure 1-1 Troubleshooting flow of GE interface The physical layer of a GE interface cannot go Up
Do boards and cards on the local device function properly?
No
Yes
Does the optical module match?
No
Replace it with the matched optical module
Is the fault rectified? Yes
No Yes
Is the optic fiber properly plugged in?
No
Properly plug in the optic fiber or replace it with the matched optic fiber.
Is the fault rectified? Yes
No Yes
Is the optic fiber inserted inversely?
Yes
Adjust the optic fiber to the correct transmission and receiving directions.
Yes
No
Yes
Seek Huawei technical support
Issue 01 (2011-10-15)
Is the fault rectified?
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
End
2
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
1 GE Interface Troubleshooting
1.1.3 Troubleshooting Procedure NOTE
After commands are configured to troubleshoot faults, pay attention to the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to the immediate validation mode. l In immediate validation mode, configurations take effect after commands are input and the Enter key is pressed. l In two-phase validation mode, after commands are configured, the commit command needs to be run to commit the configurations. Saving the results of each troubleshooting step is recommended. If your troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel.
Procedure Step 1 Check that boards and cards on the local device function properly. If an Ethernet interface functions improperly, run the loopback local command on the interface to enable the loopback function and perform the local loopback test. Then, run the display this interface command to view the interface status. l If the interface is in the Up state, go to Step 2. l If the interface is in the Down state, contact Huawei technical support engineer to rectify the fault in the hardware. Step 2 Check that the optical modules on both ends match each other. Run the display interfacegigabitethernet [ interface-number ] command on the local and remote devices to view information about optical modules and interface configurations on both ends. Note that if the local or remote device is a device of another vendor, run the corresponding command of the vendor to view the information. By viewing the information, you can determine: l Whether optical modules on the local and remote interfaces are matched and whether the optic fiber that connects to the optical modules and the power of the optical modules meet the requirement. If the optic fiber or either of the optical modules does not meet the requirement, replace it. l Whether the transmit optical power or receive optical power is within the normal range. If the transmit optical power is not within the normal range, you need to replace the optical module. If the receive optical power falls below the receiver sensitivity of the optical module, you need to replace the optical module or adjust the link. l Check that interface configurations on both ends are consistent. If they are inconsistent, adjust them to ensure configuration consistency. – If the connected interfaces are Ethernet optical interfaces or 1000M Ethernet electric interfaces, the working mode of the interfaces must be configured as 1000M full-duplex, with auto-negotiation disabled. – If the connected interfaces are 10M/1000M Ethernet electric interfaces, the working mode of the interfaces is auto-negotiation. In this case, both ends negotiates the duplex mode and working rate automatically. Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
3
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
1 GE Interface Troubleshooting
l If the fault persists, go to Step 3. Step 3 Check whether the optical modules or the optic fiber is properly connected. Both the optical module and the optic fiber have card fasteners. If a "clap" sound is heard during the insertion of the optic fiber or the optical module, it indicates that the optic fiber or the optical module has been properly inserted. If the fault persists, go to Step 3. Step 4 Check whether the two ends of the optic fiber are inserted into correct optical interfaces. Remove the optic fiber and then change the optical interface into which one end of the optic fiber is inserted, for example, if the one end of the optic fiber is inserted into the transmit optical interface of the optical module, insert it into the receive optical interface of the optical module. If the fault is rectified, it indicates that the two ends of the optic fiber are inserted into incorrect optical interfaces. If the fault persists, do not change the optical interfaces into which the two ends of the optic fiber are inserted and go to Step 4. Step 5 Collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure l Configuration files, log files, and alarm files of the devices ----End
1.1.4 Relevant Alarms and Logs Relevant Alarms None.
Relevant Logs None.
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
4
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
2
2 Eth-Trunk Interface Troubleshooting
Eth-Trunk Interface Troubleshooting
About This Chapter This chapter describes common causes of Eth-Trunk interface faults, and provides the corresponding troubleshooting flowcharts, troubleshooting procedures, alarms, and logs. 2.1 Eth-Trunk Interface Cannot Forward Traffic This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that an Eth-Trunk interface cannot forward traffic. 2.2 Trouble Cases
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
5
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
2 Eth-Trunk Interface Troubleshooting
2.1 Eth-Trunk Interface Cannot Forward Traffic This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that an Eth-Trunk interface cannot forward traffic.
2.1.1 Common Causes After an Eth-Trunk interface is configured, it cannot forward traffic. l
Eth-Trunk member interfaces are faulty.
l
Configurations of Eth-Trunk member interfaces on the two ends are inconsistent.
l
The number of Up Eth-Trunk member interfaces is smaller than the lower threshold.
l
Negotiation between member interfaces of the Eth-Trunk interface in static LACP mode fails.
l
BFD, which is used to detect an Eth-Trunk member interface, is incorrectly configured.
2.1.2 Troubleshooting Flowchart On the network shown in Figure 2-1, the Eth-Trunk interface cannot forward traffic. Figure 2-1 Networking diagram of Eth-Trunk interfaces RouterA
GE1/0/1 GE1/0/2 GE1/0/3
GE1/0/1 GE1/0/2 GE1/0/3
Eth-Trunk1
RouterB
Eth-Trunk1
The troubleshooting roadmap is as follows: l
Check that Eth-Trunk member interfaces work properly.
l
Check information about Eth-Trunk member interfaces on both ends.
l
Check that the number of Up member interfaces is greater than the configured lower threshold.
l
Check that LACP negotiation succeeds if the Eth-Trunk interface is in static LACP mode.
l
Check that BFD configurations are correct if BFD is configured to track the status of an Eth-Trunk member interface.
Figure 2-2 shows the troubleshooting flowchart.
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
6
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
2 Eth-Trunk Interface Troubleshooting
Figure 2-2 Troubleshooting flowchart for the fault that the Eth-Trunk interface cannot forward traffic Eth-Trunk interface cannot forward traffic
Eth-Trunk member interfaces work properly?
Yes
Check physical links connecting member interfaces and rectify the link fault
Yes Is fault rectified? No
No Member interfaces on both ends are consistent?
Yes
Modify the configuration
Yes Is fault rectified?
No
No
Number of Up member interfaces is below the lower threshold?
Yes
Change the lower threshold
Yes Is fault rectified? No
No Negotiation between Eth-Trunk interfaces working in static LACP mode fails?
Locate the cause of the Yes negotiation failure and modify the configuration
Yes Is fault rectified?
No No BFD is configured to track the status of an EthTrunk member interface?
Yes Yes Check and modify BFD configurations
Is fault rectified?
No
No Collect information
Seek technical support
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
End
7
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
2 Eth-Trunk Interface Troubleshooting
2.1.3 Troubleshooting Procedure NOTE
After commands are configured to troubleshoot faults, pay attention to the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to the immediate validation mode. l In immediate validation mode, configurations take effect after commands are input and the Enter key is pressed. l In two-phase validation mode, after commands are configured, the commit command needs to be run to commit the configurations. Saving the results of each troubleshooting step is recommended. If your troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel.
Procedure Step 1 Check that Eth-Trunk member interfaces work properly. Run the display eth-trunk 1 command in any view to check the status of the Eth-Trunk interface. [HUAWEI] display eth-trunk 1 Eth-Trunk1's state information is: WorkingMode: NORMAL Hash arithmetic: According to flow Least Active-linknumber: 3 Max Bandwidth-affected-linknumber: 16 Operate status: down Number Of Up Port In Trunk: 0 -------------------------------------------------------------------------------PortName Status Weight GigabitEthernet1/0/1 Down 1 GigabitEthernet1/0/2 Down 1 GigabitEthernet1/0/3 Down 1
l
If a member interface is Down, you need to troubleshoot the physical interface. For detailed troubleshooting procedures, see "Physical Interconnection Troubleshooting".
l
If all member interfaces are Up, go to Step 2.
Step 2 Check information about Eth-Trunk member interfaces on both ends. l Check information about member interfaces of the Eth-Trunk interface on Router A. [~RouterA] display eth-trunk 1 Eth-Trunk1's state information is: WorkingMode: NORMAL Hash arithmetic: According to flow Least Active-linknumber: 3 Max Bandwidth-affected-linknumber: 16 Operate status: down Number Of Up Port In Trunk: 3 ------------------------------------------------------------------------------PortName Status Weight GigabitEthernet1/0/1 Up 1 GigabitEthernet1/0/2 Up 1 GigabitEthernet1/0/3 Up 1
l Check information about member interfaces of the Eth-Trunk interface on Router B. [~RouterB] display eth-trunk 1 Eth-Trunk1's state information is: WorkingMode: NORMAL Hash arithmetic: According to flow Least Active-linknumber: 3 Max Bandwidth-affected-linknumber: 16 Operate status: down Number Of Up Port In Trunk: 2 ------------------------------------------------------------------------------PortName Status Weight GigabitEthernet1/0/1 Up 1 GigabitEthernet1/0/2 Up 1
l
Issue 01 (2011-10-15)
If the number of member interfaces of the Eth-Trunk interface on Router A is different from that on Router B, add the required physical interfaces to the Eth-Trunk interface. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
8
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
l
2 Eth-Trunk Interface Troubleshooting
If the number of member interfaces of the Eth-Trunk interface on Router A is the same as that on Router B, go to Step 3.
Step 3 Check whether the Eth-Trunk interface is configured with a lower threshold of Up member interfaces. Run the display eth-trunk 1 command on Router A and Router B to view the configuration of the Eth-Trunk interface. [~RouterA] display eth-trunk 1 Eth-Trunk1's state information is: WorkingMode: NORMAL Hash arithmetic: According to flow Least Active-linknumber: 3 Max Bandwidth-affected-linknumber: 16 Operate status: down Number Of Up Port In Trunk: 3 -------------------------------------------------------------------------------PortName Status Weight GigabitEthernet1/0/1 Up 1 GigabitEthernet1/0/2 Up 1 GigabitEthernet1/0/3 Down 1
The preceding command output shows that the lower threshold of Up member interfaces of the Eth-Trunk interface has been set to 3. However, the number of Up member interfaces of the EthTrunk interface is actually 2, which causes the Eth-Trunk interface to go Down. l
If the Eth-Trunk interface is configured with a lower threshold of Up member interfaces and the configured lower threshold is greater than the actual number of Up member interfaces, set the lower threshold to a proper value.
l
If the Eth-Trunk interface is not configured with a lower threshold of Up member interfaces, go to Step 4.
Step 4 Check whether Eth-Trunk interfaces work in static LACP mode. Run the display eth-trunk 1 command on Router A and Router B to view the configuration of the Eth-Trunk interface. [~RouterA] display eth-trunk 1 Eth-Trunk1's state information is: Local: LAG ID: 1 WorkingMode: STATIC Preempt Delay: Disabled Hash arithmetic: According to flow System Priority: 32768 System ID: 0018-826f-fc7a Least Active-linknumber: 3 Max Active-linknumber: 16 Operate status: down Number Of Up Port In Trunk: 0 -------------------------------------------------------------------------------ActorPortName Status PortType PortPri PortNo PortKey PortState Weight GigabitEthernet1/0/1 Unselect 1GE 32768 264 305 11100010 1 GigabitEthernet1/0/2 Unselect 1GE 32768 265 305 11100010 1 GigabitEthernet1/0/3 Unselect 1GE 32768 266 305 11100011 1 Partner: -------------------------------------------------------------------------------ActorPortName SysPri SystemID PortPri PortNo PortKey PortState GigabitEthernet1/0/1 0 0000-0000-0000 0 0 0 11100011 GigabitEthernet1/0/2 0 0000-0000-0000 0 0 0 11100011 GigabitEthernet1/0/3 0 0000-0000-0000 0 0 0 11100011
l
If the Eth-Trunk interface is configured to work in static LACP mode and no physical interface is selected, it indicates that LACP negotiation is unsuccessful. Possible causes for unsuccessful LACP negotiation are as follows: – Member interfaces fail, causing timeout of LACP protocol packets. In this case, you need to troubleshoot member interfaces. – The Eth-Trunk interface on one end is configured to work in static LACP mode, whereas the Eth-Trunk interface on the other end is not.
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
9
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
2 Eth-Trunk Interface Troubleshooting
Correct the configurations of the two ends of the Eth-Trunk link to make them consistent. After the configurations are corrected and LACP negotiation succeeds, the output of the display eth-trunk 1 command is as follows: [~RouterB] display eth-trunk 1 Eth-Trunk1's state information is: Local: LAG ID: 1 WorkingMode: STATIC Preempt Delay: Disabled Hash arithmetic: According to flow System Priority: 32768 System ID: 0018-826f-fc7a Least Active-linknumber: 3 Max Active-linknumber: 16 Operate status: up Number Of Up Port In Trunk: 3 ------------------------------------------------------------------------------ActorPortName Status PortType PortPri PortNo PortKey PortState Weight GigabitEthernet1/0/1 Selected 1GE 32768 264 305 11111100 1 GigabitEthernet1/0/2 Selected 1GE 32768 265 305 11111100 1 GigabitEthernet1/0/3 Selected 1GE 32768 266 305 11111100 1 Partner: ------------------------------------------------------------------------------ActorPortName SysPri SystemID PortPri PortNo PortKey PortState GigabitEthernet1/0/1 32768 0018-823c-c473 32768 2056 305 11111100 GigabitEthernet1/0/2 32768 0018-823c-c473 32768 2057 305 11111100 GigabitEthernet1/0/3 32768 0018-823c-c473 32768 2058 305 11111100
If LACP negotiation fails after the configurations are corrected, go to Step 5. l
If the Eth-Trunk interface is not configured to work in static LACP mode, go to Step 5.
Step 5 Check whether BFD is configured to track the status of an Eth-Trunk member interface. Run the display current-configuration command to view the configuration files of the devices at the two ends of the Eth-Trunk link to check whether BFD is configured to track the status of an Eth-Trunk member interface. l
If a device is configured with bfd Eth-Trunk bind peer-ip default-ip interface gigabitethernet 1/0/1, it indicates that the device has been configured with BFD to track the status of an Eth-Trunk member interface. Run the display bfd session all verbose command to check the information about the BFD session. The value of the State field displays the status of the BFD session. – If the state about the BFD session is down, see the BFD Troubleshooting to restore. – If the state about the BFD session is up, go to Step 6.
l
If no device is configured with BFD to track the status of Eth-Trunk member interfaces, go to Step 6.
Step 6 Collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure l Configuration files, log files, and alarm files of the devices ----End
2.1.4 Relevant Alarms and Logs Relevant Alarms None. Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
10
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
2 Eth-Trunk Interface Troubleshooting
Relevant Logs None.
2.2 Trouble Cases 2.2.1 Certain Users Cannot Access the Internet by Dialing Up After a Member Interface of the Eth-Trunk Interface Becomes Faulty NOTE
After commands are configured to troubleshoot faults, pay attention to the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to the immediate validation mode. l In immediate validation mode, configurations take effect after commands are input and the Enter key is pressed. l In two-phase validation mode, after commands are configured, the commit command needs to be run to commit the configurations. Saving the results of each troubleshooting step is recommended. If your troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel.
Fault Symptom As shown in Figure 2-3, the NE5000E is connected to the authentication server through an EthTrunk. Certain PPPoE users attached to the NE5000E cannot access the Internet by dialing up. These users are widely distributed and do not reside in one physical area. Figure 2-3 Networking diagram of user access
Dial-up user1 Eth-Trunk
Dial-up user2
DSLAM
Router
Server
Dial-up user3
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
11
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
2 Eth-Trunk Interface Troubleshooting
Fault Analysis 1.
Check the MAC addresses of the users where faults occur. The result shows that these MAC addresses are widely distributed and do not have common characteristics. Therefore, it can be inferred that the NE5000E or the authentication server is not configured with restrictions on these users.
2.
Run the ping command to check the connectivity of each link between the user and the authentication server. The result shows that packet loss occurs on the link connecting the NE5000E and the authentication server.
3.
Run the display interface eth-trunk 1 command on the NE5000E to check the status of each member interface.
The result shows that one member interface cannot forward data although the interface is Up at the physical and link layers.
Procedure Step 1 Run the shutdown command on the interface of the faulty link to shut down the link so that the Eth-Trunk can sense the link fault. Step 2 Replace the faulty link between the NE5000E and the authentication server. After the preceding operations, users can normally access the Internet by dialing up. The fault is rectified. ----End
Summary l
When users in different physical areas cannot access the Internet, check whether these users have common characteristics, for example, whether their MAC addresses are close to each other. If so, do as follows: – Check whether the link connecting the user is faulty. – Check whether a specific policy is configured on the NE5000E or the authentication server to restrict users.
l
Issue 01 (2011-10-15)
When users that reside in different areas cannot access the Internet, check whether there is a Trunk. If so, check the status of member interfaces. If a member interface is faulty, the traffic on the faulty interface cannot be forwarded.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
12
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
3
3 POS Interface Troubleshooting
POS Interface Troubleshooting
About This Chapter NOTE
POS interfaces cannot be configured on the X1 and X2 models of the NE5000E.
3.1 The Physical Status of POS Interfaces Cannot Go Up
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
13
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
3 POS Interface Troubleshooting
3.1 The Physical Status of POS Interfaces Cannot Go Up 3.1.1 Common Causes This fault is commonly caused by one of the following: l
Interfaces at both ends of the connection are shut down.
l
The optical module specification or the link is faulty.
l
SDH alarms exist at both ends of the connection.
l
The fiber is not properly connected.
l
The fiber is inserted into the transmit optical port/receive optical port of the optical module on one end but is inserted into the receive optical port/transmit optical port of the optical module on the other end.
l
The board or the optical module is faulty.
3.1.2 Troubleshooting Flowchart When POS interfaces of two NE5000Es are connected, the physical status of POS interfaces cannot go Up. The troubleshooting flowchart is as follows: l
Run the command to check whether configurations of the local device are correct.
l
Check the fiber, optical module, and board on site.
Figure Figure 3-1 shows the troubleshooting flowchart.
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
14
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
3 POS Interface Troubleshooting
Figure 3-1 Troubleshooting flowchart of the fault that the physical status of POS interfaces cannot be Up Physical layer of the POS interface goes Down.
Are interfaces at both ends of the connection turned on?
No
Run the undo shutdown command to turn on interfaces.
Is the fault rectified?
Yes
No
Yes Are the receiving and transmitting optical power on the interfaces winthin the normal range?
No
Change the optical module or adjust the link to ensure that the receiving or transmitting optical power is within the normal range.
Is the fault rectified?
Clear SDH alarms.
Is the fault rectified?
Yes Are SDH alarms cleared on interfaces?
No
Yes
No
Yes
No
Yes Is the fiber or the optical module properly inserted?
No
Properly insert the fiber.
Is the fault rectified?
Yes
No
Yes Are the two ends of the fiber inserted into correct interfaces?
No
Insert the two ends of the fiber into correct interfaces.
Is the fault rectified?
Yes
No
Yes Are the board and optical module normal?
No
Replace the board or optical module and then restore the link.
Is the fault rectified?
Yes
No
Yes seek technical support.
End
3.1.3 Troubleshooting Procedure Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
15
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
3 POS Interface Troubleshooting
NOTE
After commands are configured to troubleshoot faults, pay attention to the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to the immediate validation mode. l In immediate validation mode, configurations take effect after commands are input and the Enter key is pressed. l In two-phase validation mode, after commands are configured, the commit command needs to be run to commit the configurations. Saving the results of each troubleshooting step is recommended. If your troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel.
Procedure Step 1 Check that interfaces at both ends of the connection are shut down, the transmit/receive optical power is normal, and SDH alarms exist on the interfaces at both ends of the connection. Run the display interface pos [ interface-number ] command to check the following items: l If the field current state is "Administratively down", it indicates that the POS interfaces are shut down. In this case, you need to run the undo shutdown command in the view of the POS interface. l If the transmit optical power is not within the normal range, you need to replace the optical module. l If the receive optical power falls below the receiver sensitivity of the optical module, you need to replace the optical module or adjust the link. l If the SDH alarm field is not "none" and the SDH error fields indicates that the number of B1, B2, or B3 error codes increases: – The number of B1, B2, and B3 error codes increases:Check the transmission stability of the link (including optical modules at both ends of the link) between the router and the SDH transmission device. If the direct link is a WDM link, you need to check the transmission stability of the WDM link. – The number of only B3 error codes increases: This problem occurs in the scenario where the router and the SDH transmission device are directly connected through a link. In this case, you need to check the transmission stability of the direct link. If the direct link is a WDM link, you need to check the transmission stability of the WDM link. If the fault persists, go to Step 2. Step 2 Check whether the optical modules or the fiber is properly connected. Both the optical module and the fiber have card fasteners. If a "clap" sound is heard during the insertion of the fiber or the optical module, it indicates that the fiber or the optical module has been properly inserted. If the fault persists, go to Step 3. Step 3 Check whether the two ends of the fiber are inserted into correct optical interfaces. Remove the fiber and then change the optical interface into which one end of the fiber is inserted, for example, if the one end of the fiber is inserted into the transmit optical interface of the optical module, insert it into the receive optical interface of the optical module. If the fault is rectified, it indicates that the two ends of the fiber are inserted into incorrect optical interfaces. Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
16
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
3 POS Interface Troubleshooting
If the fault persists, do not change the optical interfaces into which the two ends of the fiber are inserted and go to Step 4. Step 4 Perform the loopback test on the local fiber. Use a fiber in good condition to connect the transmit optical interface to the receive optical interface of the local optical module: l If the physical status of the two interface goes Up, all SDH alarms on the interfaces are cleared and the number of B1, B2, or B3 error codes is not increased. It can thus be concluded that the board and the optical module on the local device are normal. You need to check the link or the peer device. l If the physical status of the two interface remains Down, it can be concluded that the board or the optical module of the local device is faulty. You need to replace the board or the optical module, or cut over services on the faulty interface to another interface that runs normally. NOTE
When performing the loopback test on the local fiber, you need to set the clock mode of the interface as Master.
If the fault persists, go to Step 5. Step 5 Check whether the two ends of the fiber are inserted into correct optical interfaces. Remove the fiber and then change the optical interface into which one end of the fiber is inserted, for example, if the one end of the fiber is inserted into the transmit optical interface of the optical module, insert it into the receive optical interface of the optical module. If the fault is rectified, it indicates that the two ends of the fiber are inserted into incorrect optical interfaces. If the fault persists, do not change the optical interfaces into which the two ends of the fiber are inserted and go to Step 4. Step 6 Collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure l Configuration files, log files, and alarm files of the devices ----End
3.1.4 Relevant Alarms and Logs Relevant Alarms None.
Relevant Logs None.
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
17
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
4 PPP Troubleshooting
4
PPP Troubleshooting
About This Chapter NOTE
PPP cannot be configured on the X1 and X2 models of the NE5000E.
4.1 Protocol Status of a PPP Interface Is Down This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that the protocol status of a PPP interface is Down.
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
18
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
4 PPP Troubleshooting
4.1 Protocol Status of a PPP Interface Is Down This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure for the fault that the protocol status of a PPP interface is Down.
4.1.1 Common Causes After an interface is configured with PPP, LCP negotiation fails, which causes the protocol status of the interface to be Down. This fault is commonly caused by one of the following: l
PPP configurations on the two ends of the link are incorrect.
l
The physical status of the interface is Down.
l
PPP packets are discarded.
l
A loop occurs on the link.
l
The link delay is too long.
4.1.2 Troubleshooting Flowchart The troubleshooting roadmap is as follows: l
Check that PPP configurations on the two ends of the link are correct.
l
Check that the physical status of the interface is Up.
l
Check that the interface can sent and receive protocol packets.
l
Check that the link is loop-free.
l
Check that the link delay is tolerant.
Figure 4-1 shows the troubleshooting flowchart.
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
19
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
4 PPP Troubleshooting
Figure 4-1 Troubleshooting flowchart for a PPP Interface Is Down LCP negotiation fails
PPP configurations on the two ends of the link are correct?
No
Modify PPP configurations
Is fault rectified?
Yes
No
Yes
Physical status of the interface is Up?
No Locate and rectify transmission or lower-layer faults
Yes Is fault rectified? No
Yes Interface can sent and receive protocol packets?
No Locate and rectify transmission or lower-layer faults
Is fault rectified?
Yes
No Yes Link is loop-free?
No
Eliminate the loop
Yes Is fault rectified? No
Yes Yes Link delay is tolerant
Check the link delay
Yes Is fault rectified? No
No Seek technical support
End
4.1.3 Troubleshooting Procedure NOTE
After commands are configured to troubleshoot faults, pay attention to the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to the immediate validation mode. l In immediate validation mode, configurations take effect after commands are input and the Enter key is pressed. l In two-phase validation mode, after commands are configured, the commit command needs to be run to commit the configurations. Saving the results of each troubleshooting step is recommended. If your troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel.
Procedure Step 1 Check that PPP configurations on the two ends of the link are correct. Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
20
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
4 PPP Troubleshooting
Run the display this command in the view of the interface whose protocol status is Down to check PPP configurations. [~HUAWEI-Pos1/0/1] display this # interface Pos1/0/1 link-protocol ppp undo shutdown ip address 10.10.1.1 255.255.255.0 # return
l
Check whether the following configurations on the two ends are consistent. If not, modify the configuration referring to the chapter "PPP Configuration". – Check whether the authenticator and authenticatee are configured with the same authentication mode. The ppp authentication-mode authentication-mode command indicates the authentication mode adopted by the local end that functions as the authenticator. You need to check the authentication mode adopted by the peer. For example, if the ppp pap local-user user-name password simple password command has been configured, it means that the peer adopts PAP authentication. – Check whether the authenticator and authenticatee are configured with the same password for PPP authentication. – If PAP authentication is adopted, do as follows to check the configured user name and password: Check the user name and password of the authenticatee in the interface view. [~HUAWEI-Pos1/0/0] display this # interface Pos1/0/0 link-protocol ppp ppp pap local-user huawei password cipher N`C55QK<`=/Q=^Q`MAF4<1!! undo shutdown # return
Check the user name and password of the authenticator in the AAA view. [~HUAWEI] aaa [~HUAWEI-aaa] display this # aaa local-user huawei password cipher N`C55QK<`=/Q=^Q`MAF4<1!! # return
– If the authenticator adopts unidirectional CHAP authentication and is configured with a user name, do as follows to check the user name and password: Check the user name of the authenticatee in the interface view, and then check the password in the AAA view based on the user name. [~HUAWEI-Pos1/0/0] display this # interface Pos1/0/0 link-protocol ppp ppp chap user huawei undo shutdown # return [~HUAWEI-Pos1/0/0] aaa [~HUAWEI-aaa] display this # aaa local-user huawei password cipher N`C55QK<`=/Q=^Q`MAF4<1!! # return
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
21
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
4 PPP Troubleshooting
Check the user name and password of the authenticator in the AAA view. [~HUAWEI] aaa [~HUAWEI-aaa] display this # aaa local-user huawei password cipher N`C55QK<`=/Q=^Q`MAF4<1!!# return
– If the authenticator adopts unidirectional CHAP authentication but is not configured with a user name, do as follows to check the user name and password: Check the user name and password of the authenticatee in the interface view. [~HUAWEI-Pos1/0/0] display this # interface Pos1/0/0 link-protocol ppp ppp chap user huawei ppp chap password simple huawei undo shutdown # return
Check the user name and password of the authenticator in the AAA view. [~HUAWEI] aaa [~HUAWEI-aaa] display this # aaa local-user huawei password cipher N`C55QK<`=/Q=^Q`MAF4<1!!# return
l
If the preceding configurations are correct but the fault persists, go to Step 2.
Step 2 Check that the physical status of the interface is Up. Run the display interface interface-type interface-number command to check the physical status of the interface. l
If the physical status of the interface is Down, you need to rectify the physical fault of the interface. For detailed troubleshooting procedures, see "Physical Interconnection Troubleshooting".
l
If the physical status of the interface is Up but the fault persists, go to Step 3.
Step 3 Check that the interface can sent and receive protocol packets. Run the display interface interface-type interface-number command to check the number of sent packets and received packets to determine whether the interface sends and receives protocol packets. [~HUAWEI] display interface Pos 1/0/0 Pos1/0/0 current state : UP Line protocol current state : UP Last line protocol up time : 2010-02-05 06:35:43 Description:HUAWEI, Quidway Series, Pos1/0/0 Interface Route Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec) Internet Address is 108.108.1.1/24 Link layer protocol is PPP LCP opened, IPCP opened The Vendor PN is HFBR-57E0P The Vendor Name is AVAGO Port BW: 155M, Transceiver max BW: 155M, Transceiver Mode: MultiMode WaveLength: 1310nm, Transmission Distance: 2000m Physical layer is Packet Over SDH Scramble enabled, clock master, CRC-32, loopback: none Flag J0 "NetEngine " Flag J1 "NetEngine " Flag C2 22(0x16)
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
22
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
4 PPP Troubleshooting
SDH alarm: section layer: none line layer: none path layer: none SDH error: section layer: B1 0 line layer: B2 0 REI 44 path layer: B3 0 REI 23 Statistics last cleared:never Last 300 seconds input rate 24 bits/sec, 0 packets/sec Last 300 seconds output rate 24 bits/sec, 0 packets/sec Input: 70945 packets, 1135144 bytes Input error: 0 shortpacket, 0 longpacket, 0 CRC, 0 lostpacket Output: 70945 packets, 1135140 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
l
If the number of received or sent packets is 0, or the number does not increase, it indicates that packets are discarded during transmission. Check whether the physical connection is correct. For detailed information, see "Physical Interface Cannot Go Up".
l
If the physical connection is correct, you need to locate the cause of packet loss. For detailed troubleshooting procedures, see "Packet Loss Troubleshooting".
l
If packets can be received and sent but the fault persists, go to Step 4.
CAUTION Debugging affects the system performance. Therefore, after debugging, run the undo debugging all command to disable it immediately. In addition, you can run the debugging ppp all interface interface-type interface-number command to check the number of sent and received protocol packets and the status changes of the PPP state machine. Jun 2 2010 17:19:41.310.1 HUAWEI PPP/7/debug2:Slot=1; PPP Event: Pos1/0/0 LCP TO+(Timeout with counter > 0) Event state acksent , Retransmit = 4 Jun 2 2010 17:19:41.310.2 HUAWEI PPP/7/debug2:Slot=1; PPP Packet: Pos1/0/0 Output LCP(c021) Pkt, Len 18 State acksent, code ConfReq(01), id 3, len 14 MRU(1), len 4, val 1176 MagicNumber(5), len 6, val 00abb891 Jun 2 2010 17:19:41.310.1 HUAWEI PPP/7/debug2:Slot=1; PPP Packet: Pos1/0/0 Input LCP(c021) Pkt, Len 18 State acksent, code ConfAck(02), id 3, len 14 MRU(1), len 4, val 1176 MagicNumber(5), len 6, val 00abb891 Jun 2 2010 17:19:41.310.2 HUAWEI PPP/7/debug2:Slot=1; PPP Event: Pos1/0/0 LCP RCA(Receive Config Ack) Event state acksent
Step 4 Check that the link is loop-free. Run the display interface interface-type interface-number command to check the physical status of the interface. [~HUAWEI] display interface Pos 1/0/0 Pos1/0/0 current state : UP Line protocol current state : DOWN
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
23
HUAWEI NetEngine5000E Core Router Troubleshooting - Interface and Data Link
4 PPP Troubleshooting
Description:HUAWEI, Quidway Series, Pos1/0/2 Interface Route Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec) Internet protocol processing : disabled Link layer protocol is PPP, loopback is detected LCP closed The Vendor PN is HFBR-57E0P The Vendor Name is AVAGO Port BW: 155M, Transceiver max BW: 155M, Transceiver Mode: MultiMode WaveLength: 1310nm, Transmission Distance: 2000m Physical layer is Packet Over SDH Scramble enabled, clock master, CRC-32, loopback: local Flag J0 "NetEngine " Flag J1 "NetEngine " Flag C2 22(0x16) SDH alarm: section layer: none line layer: none path layer: none SDH error: section layer: B1 22 line layer: B2 94 REI 145 path layer: B3 44 REI 86 Statistics last cleared:never Last 300 seconds input rate 56 bits/sec, 0 packets/sec Last 300 seconds output rate 56 bits/sec, 0 packets/sec Input: 40530 packets, 890400 bytes Input error: 0 shortpacket, 0 longpacket, 2 CRC, 0 lostpacket Output: 36512 packets, 946612 bytes Output error: 0 lostpackets Output error: 0 overrunpackets, 0 underrunpackets
l
If loopback is detected is displayed, it indicates that a loop occurs on the link. You need to locate the cause of the loop and eliminate the loop.
l
If no loop occurs but the fault persists, go to Step 5.
Step 5 Check that the link delay is tolerant. Use a tester to test the link delay. On a Huawei Router, the transmission of a PPP packet times out in 3 seconds, and the timeout period is configurable. The link delay must be smaller than the timeout period. l
If the link delay is too long, replace or maintain the relevant device.
l
If the link delay is tolerant but the fault persists, go to Step 6.
Step 6 Collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure l Configuration files, log files, and alarm files of the devices ----End
4.1.4 Relevant Alarms and Logs Relevant Alarms None.
Relevant Logs None.
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
24
