Page 1: Troubleshooting
Huawei AR2200-S Series Enterprise Routers V200R001C01 Troubleshooting Issue Date 2012-01-06 HUAWEI TECHNOLOGIES CO., LTD.
Page 2 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.
Page 3: About This Document
Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement NOTE important points of the main text. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 4: Command Conventions
Change History Updates between document issues are cumulative. Therefore, the latest document issue contains all updates made in previous issues. Changes in Issue 01 (2010-01-06) Initial commercial release. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 5: Table Of Contents
2.7.1 The Clock Is Not Synchronized.......................41 2.8 CWMP Troubleshooting...........................42 2.8.1 Failed to Manage AR2200-S Using CWMP...................42 3 Physical Connection and Interfaces..................46 3.1 Eth-Trunk Interface Troubleshooting.......................47 3.1.1 Eth-Trunk Interface Cannot Forward Traffic..................47 Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 6 6.1.1 No Feed Is Detected on a Telephone.....................139 6.1.2 No Dial Tone Is Heard After Offhook....................141 6.1.3 Call Quality Is Low..........................143 6.1.4 Busy Tone Is Heard After Offhook.......................145 Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 7 9.3.1 Traffic Policing Based on Traffic Classifiers Fails to Take Effect............247 9.3.2 Interface-based Traffic Policing Results Are Incorrect.................248 9.3.3 Troubleshooting Cases..........................251 9.4 Traffic Shaping Troubleshooting........................252 9.4.1 Queue-based Traffic Shaping Results Are Incorrect................252 9.4.2 Troubleshooting Cases..........................255 Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 8 11.2.3 Changed BFD Session Parameters Do Not Take Effect..............331 11.2.4 Dynamic BFD Session Fails to Be Created..................333 11.3 VRRP Troubleshooting..........................335 11.3.1 Troubleshooting Cases........................335 12 VPN............................340 12.1 GRE Troubleshooting...........................341 Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 9 12.2.3 IPSec Fails to Be Configured by Using an IPSec Policy Template............358 12.2.4 NAT Traversal in IPSec Fails......................365 12.2.5 GRE over IPSec Fails..........................372 12.2.6 Troubleshooting Cases........................379 Issue 01 (2012-01-06) Huawei Proprietary and Confidential viii Copyright © Huawei Technologies Co., Ltd.
Page 10: Issue
Huawei AR2200-S Series Enterprise Routers Troubleshooting 1 Hardware Hardware About This Chapter 1.1 Board Registration Troubleshooting Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 11: Board Registration Troubleshooting
Check whether the board is in an unregistered state after the board has finished startup. Check whether the board was reset. If the board was reset, locate the cause. Figure 1-1 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 12 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide to Huawei technical support personnel. Procedure Step 1 Check whether the board is starting.
Page 13 If the fault persists, go to step 3. Step 3 Collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure l Configuration file, log file, and alarm file of the AR2200-S...
Page 14: System
This chapter describes common causes of mirroring faults, and provides the corresponding troubleshooting flowcharts, troubleshooting procedures, alarms, and logs. 2.5 SNMP Troubleshooting 2.6 NQA Troubleshooting 2.7 NTP Troubleshooting 2.8 CWMP Troubleshooting Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 15: Cpu Troubleshooting
MAC address entries and ARP entries. The device generates a large number of logs, consuming a lot of CPU resources. Troubleshooting Flowchart Figure 2-1 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 16 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. The following procedures can be performed in any sequence.
Page 17 TC-BPDUs within a short period and frequently deletes MAC address entries and ARP entries. As a result, the device CPU usage becomes high. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 18 If a loop occurs on the network, an alarm is generated when two interfaces of the device learn the same MAC address entry. For example: Feb 22 2011 18:42:50 Huawei L2IFPPI/4/MAC_FLAPPING_ALARM:OID 1.3.6.1.4.1.2011.5.25.42.2.1.7.12The mac-address has flap value .
Page 19: Telnet Troubleshooting
Run the display logbuffer command to check whether a large number of logs are generated. If a certain log is repeatedly generated, go to step 6. Step 6 Collect the following information and contact Huawei technical support personnel: l Results of the preceding troubleshooting procedure...
Page 20 Troubleshooting Procedure NOTE 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. Issue 01 (2012-01-06) Huawei Proprietary and Confidential...
Page 21 If the user access protocol is "all", the user can log in to the server through Telnet or SSH. Step 5 Check that the authentication mode is configured in the user interface view. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 22: Ssh Troubleshooting
If you run the authentication-mode none command to configure the authentication mode to none, the authentication mode does not affect your login. Step 6 If the fault persists, collect the following information and contact Huawei technical support personnel: l Results of the preceding troubleshooting procedures...
Page 23 NOTE 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 whether the SSH client and SSH server can communicate with each other.
Page 24 If the SFTP service is enabled, run the local-user user-name ftp-directory directory command in the AAA view to configure the SFTP directory for the SSH user. l Create an SSH user. [Huawei] aaa [Huawei] local-user abc password simple abc-pass [Huawei] local-user abc service-type ssh [Huawei] local-user abc ftp-directory cfcard:/ssh l The default authentication mode of the SSH user is password.
Page 25 RSA public fails. <Huawei> system-view [Huawei] ssh client first-time enable Step 10 Collect the following information and contact Huawei technical support personnel: l Results of the preceding troubleshooting procedures l Configuration files, log files, and alarm files of the devices...
Page 26: Mirroring Troubleshooting
Troubleshooting Flowchart After port mirroring is configured on the AR2200-S, the monitoring device does not receive any mirrored packets. Figure 2-3 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 27 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check whether the mirrored port receives packets.
Page 28 – If the observing port is Up, go to step 4. If the number of packets sent by the observing port is not 0 and keeps increasing, go to step Step 4 Collect the following information and contact Huawei technical support personnel: l Results of the preceding troubleshooting procedure...
Page 29: 2.4.2 Monitoring Device Does Not Receive Any Mirrored Packets After Traffic Mirroring Is Configured
Troubleshooting Flowchart After traffic mirroring is configured on the AR2200-S, the monitoring device does not receive any mirrored packets. Figure 2-4 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 30 NOTE 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 whether the mirrored port receives packets.
Page 31 Otherwise, go to step 4. If the number of packets sent by the observing port is not 0 and keeps increasing, go to step Step 4 Collect the following information and contact Huawei technical support personnel: l Results of the preceding troubleshooting procedure...
Page 32: Troubleshooting Cases
Figure 2-5 Network diagram of port mirroring Internet LAN switchA Router Eth2/0/0 User Eth2/0/1 R&D Department Monitoring Device Fault Analysis Run the display interface command to check whether Eth2/0/0 receives packets from users. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 33 Internet. After the configuration is complete, the IT department cannot see mirrored packets on the monitoring device. Figure 2-6 Network diagram of traffic mirroring R&D Department Internet 10.1.1.0/24 SwitchA GE2/0/1 GE2/0/0 RouterA 10.1.2.0/24 Sales Department Monitoring Device Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 34 Check whether the traffic classifier and the traffic behavior in the traffic policy are correctly configured. Run the display traffic policy user-defined command to check whether the traffic behavior bound to the traffic policy contains the traffic mirroring action. <Huawei> display traffic policy user-defined tp1 User Defined Traffic Policy Information: Policy: tp1 Classifier: default-class...
Page 35: Snmp Troubleshooting
2.5.1 An SNMP Connection Cannot Be Established Common Causes This fault is commonly caused by one of the following: Packets cannot be exchanged between the host and the NMS. Configurations are incorrect. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 36 NOTE 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 Run the ping command to check whether the host and the NMS can successfully ping each other.
Page 37 If the IP address from which the NMS sends login requests is permitted by the ACL, go to Step 4. Step 4 Collect the following information and contact Huawei technical support personnel: l Results of the preceding troubleshooting procedure...
Page 38: The Nms Fails To Receive Trap Messages From The Host
Are the SNMP correctly configuration correct? View the system log and rectified the fault based on the table in troubleshooting procedure Is the fault rectified? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 39 NOTE 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 whether the SNMP configurations on the host are correct.
Page 40: Nqa Troubleshooting
The log message indicating that a specific trap is generated is as follows: #Jun 10 2010 09:55:03 Quideway IFNET/2/IF_PVCDOWN:OID 1.3.6.1.6.3.1.1.5.3 Interface 109 turned into DOWN state. Step 4 Collect the following information and contact Huawei technical support personnel: l Results of the preceding troubleshooting procedure...
Page 41 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. All the following commands, except the display commands, are used in the NQA test instance view. The display commands can be used in any views.
Page 42: A Drop Record Exists In The Udp Jitter Test Result
– If the fault is rectified, go to Step 5. – If the fault persists, go to Step 4. Step 4 If the fault persists, collect the following information and contact Huawei technical support personnel: l Results of the preceding troubleshooting procedures...
Page 43 NOTE 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 Run the display ip routing-table command on the NQA client to check whether the route along the test path exists.
Page 44: A Busy Record Exists In The Udp Jitter Test Result
IP addresses and recheck the configuration about NQA. l If the source IP address is not configured, go to Step 3. Step 3 If the fault persists, collect the following information and contact Huawei technical support personnel:...
Page 45 NOTE 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 Run the display nqa-agent admin-name test-name [ verbose ] command on the NQA client or the display this command in the NQA test instance view to check whether the VPN instance is configured.
Page 46: A Timeout Record Exists In The Udp Jitter Test Result
Ensure that the NQA server is configured Is the fault Is the NQA jitter tag- and is in the Active rectified? version 2? state Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 47 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. Unless otherwise stated, all the following commands, except display commands that can be run in all views, need to be run in the NQA test instance view.
Page 48: The Udp Jitter Test Result Is "Failed", "No Result" Or "Packet Loss
Is frequency set? large than (interval x rectified? probe-count x jitter- packetnum) Set fail-percent to a Is the fault Is fail-percent set? proper value rectified? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 49 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. All the following commands, except the display commands, are used in the NQA test instance view. The display commands can be used in any views.
Page 50: Ntp Troubleshooting
Context NOTE 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 the NTP status.
Page 51: Cwmp Troubleshooting
Fails. l If the packet loss percentage is 0.00%, the link is normal. Then proceed to step 4. Step 4 If the fault persists, collect the following information and contact Huawei technical support personnel: l Results of the preceding troubleshooting procedures...
Page 52 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Verify the CWMP settings on the AR2200-S.
Page 53 Step 3 Check whether the parameters in the packets received from the ACS are supported by the AR2200-S. Capture the packets exchanged between the ACS and the AR2200-S using Ethereal or other packet catchers, and check the parameters in <Name></Name>. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 54 If the parameters are not supported by the AR2200-S, the ACS cannot manage the AR2200- l If all parameters are supported by the AR2200-S, go to step 4. Step 4 Collect the following information and contact Huawei technical support personnel: l Results of the preceding troubleshooting procedure...
Page 55: Physical Connection And Interfaces
About This Chapter 3.1 Eth-Trunk Interface Troubleshooting This chapter describes common causes of Eth-Trunk interface faults, and provides the corresponding troubleshooting flowcharts, troubleshooting procedures, alarms, and logs. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 56: Eth-Trunk Interface Troubleshooting
Check that the number of Up member interfaces is greater than the configured lower threshold. Check that LACP negotiation succeeds if the Eth-Trunk interface is in static LACP mode. Figure 3-2 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 57 NOTE Saving the results of each troubleshooting step is recommended. If 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.
Page 58 If the number of member interfaces of the Eth-Trunk interface on Router A differs from the number on Router B, add the required physical interfaces to the Eth-Trunk interface. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 59 – Member interfaces fail, causing timeout of LACP protocol packets. To correct this problem, connect the cable to another idle interface and add the interface to the Eth-Trunk. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 60: Troubleshooting Cases
If the Eth-Trunk interface is not configured to work in static LACP mode, go to Step 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...
Page 61 Summary In the Layer 3 communication scenario, select the IP address-based load balancing modes. In the Layer 2 communication scenario, select the MAC address-based load balancing modes. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 62 RouterA and RouterB can ping each other successfully. ----End Summary When connecting a Huawei switch to a non-Huawei switch by using an Eth-Trunk, ensure that the two switches use the same link aggregation mode. Issue 01 (2012-01-06) Huawei Proprietary and Confidential...
Page 63 Step 4 Run the return command to return to the user view, and then run the save command to save the configuration. After the preceding operations are completed, RouterA and RouterB can communicate with each other. ----End Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 64 3 Physical Connection and Interfaces Summary The two ends of an Eth-Trunk must have the same number of member interfaces; otherwise, the two ends cannot communicate with each other. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 65 4.4 Transparent Bridging Troubleshooting This chapter describes common causes of transparent bridging faults, and provides the corresponding troubleshooting flowcharts, troubleshooting procedures, alarms, and logs. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 66: Vlan Troubleshooting
If users in different VLANs cannot communicate with each other, rectify the fault according to the IP Forwarding Troubleshooting. Troubleshooting Flowchart Figure 4-1 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 67 Is port isolation Is the fault Disable port isolation configured? rectified? Are static ARP Modify static ARP Is the fault entries on terminals entries rectified? correct? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 68 NOTE 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 the interfaces connected to the user terminals are in Up state.
Page 69 After the preceding operations: – If the MAC address entries are correct, go to Step Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 70: Mac Address Table Troubleshooting
If the static ARP entries are correct, go to Step Step 7 Collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure l Configuration file, log file, and alarm file of the AR2200-S...
Page 71 Check whether the configurations on the interface conflict or MAC address learning limit is configured on the interface. Check whether the number of learned MAC addresses exceeds the limit. Figure 4-2 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 72 NOTE 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 the configurations on the interface are correct.
Page 73 Run the display mac-address blackhole command to check whether any blackhole MAC address entry is configured. [Huawei] display mac-address blackhole M----------------------------------------------------------------------------- MAC Address VLAN/Bridge Learned-From Type ------------------------------------------------------------------------------ Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 74 – Run the port-security enable command on the interface to enable port security or run the mac-limit command to set the maximum number of MAC addresses that the interface can learn to 1. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 75: Mstp Troubleshooting
If the number of MAC addresses has not reached the maximum supported by the AR2200- S, go to Step Step 6 Collect the following information and contact Huawei technical support personnel. Results of the preceding troubleshooting procedure Configuration file, log file, and alarm file of the AR2200-S...
Page 76 Check that no physical interface on the device alternates between Up and Down. Check that the MSTP convergence mode is Normal. Figure 4-4 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 77 NOTE 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 the status of interfaces on MSTP devices.
Page 78 MSTP calculation error occurs. To solve this problem, go to Step If the MSTP status is correct, go to Step Step 2 Check that the MSTP configuration is correct. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 79 MSTP-enabled port changes. – If the port role does not change, go to Step – If the port role changes, go to Step Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 80 Normal. If services are not restored after the convergence mode is changed, go to Step 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 device...
Page 81: Transparent Bridging Troubleshooting
This fault is commonly caused by one of the following: Physical interfaces fail to be added to bridge groups. Member interfaces in bridge groups become faulty. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 82 NOTE 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 every bridge group has member interfaces.
Page 83 For example, check whether the interface is up and the protocol configuration is correct. If all member interfaces are Up, go to Step Step 3 Collect the following information and contact Huawei technical support personnel: l Results of the preceding troubleshooting procedure l Configuration, log, and alarm files...
Page 84: Traffic Forwarding In Ip Routing Of Bridge Groups Fails
Physical interfaces fail to be added to bridge groups. Member interfaces in bridge groups become faulty. Routes between the two enterprises are unreachable. Troubleshooting Flowchart Figure 4-8 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 85 NOTE 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 every bridge group has member interfaces.
Page 86 Realtime 0 seconds output rate 0 bits/sec, 0 packets/sec Input: 139 packets,0 bytes, 0 unicast,0 broadcast,0 multicast 0 errors,0 drops,0 unknownprotocol Output:140 packets,0 bytes, 0 unicast,0 broadcast,0 multicast Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 87 Run the display this command on Router A and Router B to check the configuration on network- side interfaces. # Check the network-side interface configuration on Router A. <RouterA> system-view [RouterA] interface ethernet2/0/1 [RouterA-Ethernet2/0/1] display this interface Ethernet2/0/1 bridge 2 undo shutdown return Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 88 Guide - LAN Access and MAN Access to add the network-side interfaces to the same bridge group. Step 6 Collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure l Configuration, log, and alarm files...
Page 89 5.5 ISDN Troubleshooting 5.6 PPPoE Troubleshooting 5.7 PPP Troubleshooting 5.8 xDSL Troubleshooting This chapter describes how to locate and troubleshoot common xDSL faults with examples. 5.9 3G Troubleshooting Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 90: E1/T1 Troubleshooting
This fault is commonly caused by one of the following: The CPLD logic version of the E1/T1 board is incorrect. Timeslots of the remote interface are incorrectly bound. Troubleshooting Flowchart Figure 5-1 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 91 NOTE Saving the results of each troubleshooting step is recommended. If 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 the local and remote interfaces have the same configurations.
Page 92 Link layer protocol is PPP LCP opened, IPCP opened Last physical up time : 2008-01-08 02:59:52 UTC-05:13 Last physical down time : 2008-01-07 22:40:43 UTC-05:13 Current system time: 2008-01-08 03:33:42-05:13 Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 93 If so, check whether the cable between them is properly installed. If the fault persists after the cable is properly installed, go to step 5. Step 5 Collect the following information and contact Huawei technical support personnel. Results of the preceding troubleshooting procedure...
Page 94: Fr Troubleshooting
If a ping operation is performed between two indirectly connected devices, check whether static routes are configured on the two devices in addition to checking the preceding items. Troubleshooting Flowchart Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 95 Is fault reachable routes to reachable routes rectified? each other? Seek technical support Figure 5-3 shows the troubleshooting flowchart in the scenario where a PVC group is configured. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 96 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure In the scenario where basic FR is configured: Check that a PVC is configured on the DTE-side interface.
Page 97 Check that InARP is enabled on the interface. Run the display this command on the interface to check the interface configuration. [Huawei-Serial2/0/0:2]display this V200R001C00B110] interface Serial2/0/0:2 link-protocol Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 98 Route Flags: G - Gateway Route, H - Host Route, U - Up Route S - Static Route, D - Dynamic Route, B - Black Hole Route ------------------------------------------------------------------------- ----- Table: Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 99 – If the preceding routing entry is not displayed, configure this route. – If the preceding routing entry is displayed, go to step 7. Collect the following information and contact Huawei technical support personnel. – Results of the preceding troubleshooting procedure –...
Page 100 PVCs. – If all the priorities have been configured for PVCs in the PVC group, go to step 3. Collect the following information and contact Huawei technical support personnel. – Results of the preceding troubleshooting procedure – Configuration files, log files, and alarm files of the device...
Page 101: Troubleshooting Cases
No IP address is assigned to the DTE-side interface. Procedure Step 1 Assign an IP address to the DTE-side interface. After step 1 is completed, the two Huawei AR2200-S Seriess can ping each other successfully. ----End Summary A DTE learns a PVC from a DCE using the LMI protocol after the link protocol status of the FR interfaces becomes Up.
Page 102: Local Device Fails To Ping The Remote Device When The Link Protocol Status Of Their Connected Mfr Interfaces Is Up
No IP address is configured in the virtual template interface. PPP negotiation fails. Troubleshooting Flowchart Figure 5-5 shows the troubleshooting flowchart in the scenario where basic MFR is configured. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 103 Troubleshooting Procedure NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Issue 01 (2012-01-06) Huawei Proprietary and Confidential...
Page 104 = 29, out bytes = 1160 If the number of configured PVCs has reached the threshold, no more PVCs can be created. The AR2200-S supports a maximum of 128 PVCs. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 105 Run the display fr map-info command to check whether the mapping between the PVC and peer address is generated. [Huawei]display fr map-info Map Statistics for interface MFR0/0/0 (DTE) DLCI = 22, IP INARP 5.5.5.1, MFR0/0/0 Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 106 6.6.6.2/32 127.0.0.1 t[496] InLoop0 255.255.255.255/32 127.0.0.1 t[487] InLoop0 127.255.255.255/32 127.0.0.1 t[487] InLoop0 127.0.0.1/32 127.0.0.1 t[487] InLoop0 127.0.0.0/8 127.0.0.1 t[487] InLoop0 6.6.6.0/24 6.6.6.2 t[496] 192.168.0.0/24 192.168.0.23 t[501] GE0/0/0 Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 107: Troubleshooting Cases
– If the preceding routing entry is not displayed, configure this route. – If the preceding routing entry is displayed, go to step 7. Collect the following information and contact Huawei technical support personnel. – Results of the preceding troubleshooting procedure –...
Page 108: Dcc Troubleshooting
InARP is disabled. Procedure Step 1 Enable InARP. After step 1 is completed, the two Huawei AR2200-S Seriess can ping each other successfully. ----End Summary A DTE learns a PVC from a DCE using the LMI protocol after the link protocol status of their connected MFR interfaces becomes Up.
Page 109 Is the data Rectify the data Is fault channel in Up channel fault rectified? state? Seek technical support Troubleshooting Procedure Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 110 NOTE Saving the results of each troubleshooting step is recommended. If 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 a link is set up successfully.
Page 111 AR2200-S rejects the call. l If the following information is displayed, the AR2200-S has rejected the call. Restart the AR2200-S. <Huawei> Oct 14 2007 08:56:10.30.1+08:00 AR2220 CC/7/CC_Debug: CC <-DDR : ISDN_DISC_REQ CallID=0x0 UserID=0x0 PortID=0x9 ServiceType=0x8 Channel=0x2 IsCompleted=0x0 Cause=0x00 Oct 14 2007 08:56:10.30.2+08:00 AR2220 CC/7/CC_Debug:...
Page 112: Failed To Receive Calls
Down. Rectify the fault according to 5.7.1 Protocol Status of a PPP Interface Is Down. Step 7 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 AR2200-S...
Page 113 Is fault rectified? side device refuse network-side device the call? Is the data Rectify the data channel protocol Is fault rectified? channel fault status Up? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 114 NOTE Saving the results of each troubleshooting step is recommended. If 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 a link is set up successfully.
Page 115 If the protocol status is Line protocol current state : DOWN, the protocol status of the data channel is Down. 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 AR2200-S...
Page 116: Isdn Troubleshooting
The cable between ISDN interfaces is faulty. The interface configuration is incorrect. Packets are incorrectly sent. The network-side device is faulty. Troubleshooting Flowchart Figure 5-9 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 117 NOTE Saving the results of each troubleshooting step is recommended. If 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 the physical status of the interface is Up.
Page 118 CE1 local and remote mode and slave clock mode interface view to correctly interfaces. respectively. configure the clock mode. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 119 02 01 7F. If the following information is displayed, the length and contents of the sent SABME frames are incorrect. Restart or replace the device. <Huawei> Oct 12 2007 11:54:42.240.1+08:00 Huawei Q921/7/Q921_Debug: Serial1/0/0:15 U->N Len=7 00 01 7F 00 00 00 00 U->N sapi=00 tei=00 c/r=0...
Page 120 U->N Len=7 00 01 7F 00 00 00 U->N sapi=00 tei=00 c/r=0 SABME If the following information is displayed, SABME frames are correctly sent. Go to step 3. <Huawei> Oct 12 2007 11:54:42.240.1+08:00 Huawei Q921/7/Q921_Debug: Serial1/0/0:15 U->N Len=3 00 01 U->N sapi=00 tei=00 c/r=0 SABME <Huawei>...
Page 121 [FUN: ISDN_Q921_HandleOnTEIAssign, LINE: 1054] ISDN Layer 2 link state change -> MULTIPLE_FRAME_ESTABLISHED Step 4 Collect the following information and contact Huawei technical support personnel. Results of the preceding troubleshooting procedure Configuration files, log files, and alarm files of the device...
Page 122: Pppoe Troubleshooting
The physical interface frequently alternates between Up and Down states. User authentication fails. No IP address is assigned to the PPPoE client. No echo message is received. Troubleshooting Flowchart Figure 5-10 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 123 NOTE Saving the results of each troubleshooting step is recommended. If 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 the physical interface is working properly.
Page 124 Info: Current terminal monitor is on. <Huawei-B>terminal debugging Info: Current terminal debugging is on. Info: Current terminal monitor is on. <Huawei-B>debugging ppp all interface Dialer 10 If the following information is displayed, authentication fails. <Huawei-B>Jan 21 2008 17:40:56.420.1+08:00 AR1220-B MID_PPP/7/debug2: PPP Packet:...
Page 125 Info: Current terminal monitor is on. <Huawei-B>terminal debugging Info: Current terminal debugging is on. <Huawei-B>debugging ppp lcp all interface Dialer If outgoing Echo Request messages are displayed but no incoming Echo Reply message is displayed, the client cannot receive heartbeat messages.
Page 126: Ppp Troubleshooting
If the client has received heartbeat messages but the fault persists, go to step 6. Step 6 Collect the following information and contact Huawei technical support personnel. Results of the preceding troubleshooting procedure Configuration files, log files, and alarm files of the device...
Page 127 NOTE 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.
Page 128 Check the user name and password of the authenticatee in the interface view. [Huawei-Serial2/0/0] display this interface Serial2/0/0 link-protocol ppp ppp pap local-user huawei password simple huawei undo shutdown return Check the user name and password of the authenticator in the AAA view.
Page 129 Physical layer is Packet Over SDH Scramble enabled, clock master, CRC-32, loopback: none Flag J0 "NetEngine " Flag J1 "NetEngine " Flag C2 22(0x16) SDH alarm: section layer: none Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 130 [Huawei] display interface Serial 2/0/0 Serial2/0/0 current state : UP Line protocol current state : DOWN Description:HUAWEI, AR Series, Serial 2/0/0 Interface Route Port,The Maximum Transmit Unit is 4470, Hold timer is 10(sec) Issue 01 (2012-01-06) Huawei Proprietary and Confidential...
Page 131: Xdsl Troubleshooting
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.
Page 132: Packets Fail To Be Forwarded On An Adsl Interface Working In Atm Mode
ADSL rectified? the ADSL interface Up? interface is Up Is ATM correctly Configure ATM Is fault configured? correctly rectified? Seek technical support Troubleshooting Procedure Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 133 IP address of the same network remote interface. segment as the IP address of the remote interface. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 134 PPP password. user name and password of the local VT interface to be the same as those of the remote interface. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 135 PVC. If the fault persists, go to step 3. Step 3 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 device...
Page 136: Packets Fail To Be Forwarded On A G.shdsl Interface Working In Atm Mode
The local and remote G.SHDSL interfaces are using different transmission standards. The local and remote G.SHDSL interfaces are working in different PSD modes. Troubleshooting Flowchart Figure 5-13 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 137 Run the display interface atm command in the system view to check whether the physical status of the G.SHDSL interface is Up. The following information uses the display on ATM1/0/0 as an example. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 138 If "Atm1/0/0 current state : UP" is displayed, ATM1/0/0 is in the Up state. Go to step 2. Step 2 Check that the local and remote G.SHDSL interfaces use the same transmission standard. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 139 IP address. correctly configured on the PVC. If IPoE packets are transmitted over ATM links, check the following items. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 140 PVC. whether PPPoA mapping is correctly configured on the PVC. If PPPoE packets are transmitted over ATM links, check the following items. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 141: G Troubleshooting
PVC. If the fault persists, go to step 5. 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 device...
Page 142 Is fault coverage area coverage area? rectified? Is the profile Configure a 3G Is fault configured on WCDMA modem profile rectified? network? Seek technical support Troubleshooting Procedure Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 143 The AR supports WCDMA and CDMA2000, but does not support TD-SCDMA. Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Run the display interface cellular interface-number command.
Page 144 Run the display cellular interface-number all command. If the following information is displayed, no 3G modem profile is configured. Configure a 3G modem profile on the AR. Profile Information. ==================== Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 145 If you cannot rectify the fault after performing the preceding troubleshooting procedure, perform the operations in this section. Procedure Step 1 Enable DCC debugging and dial up. Collect the debugging information and contact Huawei technical support personnel. NOTE Run the terminal monitor and terminal debugging commands to display debugging information on the terminal.
Page 146 Huawei AR2200-S Series Enterprise Routers Troubleshooting 5 WAN Jun 5 2011 10:08:558(DCC_TaskEntry) <-- 0x004c5f358+00:00 Huawei IFNET/6/ IF_PVCUP:OID 1.3.6.1.6.3.1.1.5.4 Interfa 0x04db8f74(vxTaskEntry) <-- 0x0ce 13 turned into UP state.(AdminStatus 1,OperStatus 1,InterfacepuID: -1, TaskID: 166, Sn: 256> Name Cellular0/0/0) Jun 5 2011 10:08:59+00:00 Huawei %%01IFNET/4/LINK_STATE(l)[3]:The line protocol PPP IPCP on the interface Cellular0/0/0 has entered the UP state.
Page 147: Voice
Huawei AR2200-S Series Enterprise Routers Troubleshooting 6 Voice Voice About This Chapter 6.1 Voice Service Troubleshooting Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 148: Voice Service Troubleshooting
Troubleshooting Procedure NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Issue 01 (2012-01-06) Huawei Proprietary and Confidential...
Page 149 2 subcard 0 port 1 ( telno 28780000 mgid 0 terminalid - ) under testing, Please wait..[Huawei-voice-vdiagnose] Testing port: 0/2/1 Telno 28780000 MGid Terminalid ------------------------------------------------------------------------- Test item Result Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 150: No Dial Tone Is Heard After Offhook
If the Conclusion field is not displayed as Normal, rectify the fault on the external line. If the Conclusion field is displayed as Normal, go to step 4. Step 4 Collect the following information and contact Huawei technical support personnel. Results of the preceding troubleshooting procedure...
Page 151 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check the status of the port connected to the telephone.
Page 152: Call Quality Is Low
If the SRU is not working properly, repair the SRU. If the SRU is working properly, go to step 4. Step 4 Collect the following information and contact Huawei technical support personnel. Results of the preceding troubleshooting procedure Configuration files, log files, and alarm files of the AR2200-S...
Page 153 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check whether there is any QoS alarm record.
Page 154: Busy Tone Is Heard After Offhook
If no fault occurs on the bearer network, go to step 5. Step 5 Collect the following information and contact Huawei technical support personnel. Results of the preceding troubleshooting procedure Configuration files, log files, and alarm files of the AR2200-S...
Page 155 Troubleshooting Procedure NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Issue 01 (2012-01-06) Huawei Proprietary and Confidential...
Page 156 : off Fskmode : BELL202 Fsk taspattern : NO TAS Run the display voice sipag auth running command to check the authentication configuration. [Huawei-voice-sipag-0]display voice sipag auth running 0 SIP auth para: MGID Auth Mode : single-user Password-mode : password...
Page 157 If no DSP channel is available, add DSP channels. If there are DSP channels available, go to Step Step 7 Collect the following information and contact Huawei technical support personnel. Results of the preceding troubleshooting procedure Configuration files, log files, and alarm files of the AR2200-S...
Page 158: A Call Fails To Be Connected
Is network Rectify network Is fault working properly? fault rectified? Is media Change the Is fault negotiation codec mode rectified? successful? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 159 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check whether the calling party configuration is complete.
Page 160 AR2200-S. If media negotiation is successful, go to step 5. Step 5 Collect the following information and contact Huawei technical support personnel. Results of the preceding troubleshooting procedure Configuration files, log files, and alarm files of the AR2200-S...
Page 161: Calling Number Is Not Displayed On The Called Party's Telephone
Troubleshooting Procedure NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Issue 01 (2012-01-06) Huawei Proprietary and Confidential...
Page 162 If the service configuration is incorrect, modify the configuration. If the service configuration is correct, go to Step Step 2 Check whether there is electromagnetic interference and whether the subscriber line is working properly. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 163 If the telephone supports one of the preceding formats, the calling number can be displayed. If the fault persists, go to Step Step 4 Collect the following information and contact Huawei technical support personnel. Issue 01 (2012-01-06) Huawei Proprietary and Confidential...
Page 164: Fax Service Fails
The fax transmission modes on the SIP devices at the calling party and called party sides are different. There are echoes or other environmental factors causing signal quality deterioration. Troubleshooting Flowchart Figure 6-7 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 165 NOTE Saving the results of each troubleshooting step is recommended. If 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 the fax service type is correct.
Page 166 If AR2200-S and modem use different fax transmission modes, set the same transmission mode for them. If the AR2200-S and modem use the same fax transmission mode, go to step 6. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 167: A Sip Ag Cannot Work Properly
Huawei AR2200-S Series Enterprise Routers Troubleshooting 6 Voice Step 6 Collect the following information and contact Huawei technical support personnel. Results of the preceding troubleshooting procedure Configuration files, log files, and alarm files of the AR2200-S ----End Relevant Alarms and Logs Relevant Alarms None.
Page 168 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check whether the AR2200-S can ping the softswitch.
Page 169 Secondary Proxy IP 1 Secondary Proxy IP 2 Primary Proxy Port : 5060 Secondary Proxy Port Primary Proxy Domain Name Secondary Proxy Domain Name Proxy Address Mode : IP Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 170 If the intermediate device that discards signaling packets cannot be located, go to step 5. Step 5 Collect the following information and contact Huawei technical support personnel. Results of the preceding troubleshooting procedure Configuration files, log files, and alarm files of the AR2200-S...
Page 171: Ip Forwarding And Routing
This chapter describes common causes of Dynamic Host Configuration Protocol (DHCP) faults, and provides troubleshooting flowcharts, troubleshooting procedures, alarms, and logs. 7.3 RIP Troubleshooting 7.4 OSPF Troubleshooting Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 172: A Ping Operation Fails
Ping packet is sent but the outbound interface of the packet has a smaller MTU. Routing entries or ARP entries (for Ethernet links) are incorrect. The hardware is faulty. Troubleshooting Flowchart Figure 7-1 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 173 Does the Ensure that the Is fault network layer of the network layer works rectified? device work properly properly? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 174 NOTE 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 whether or not the ping failure is caused by the too long link transmission delay.
Page 175 ICMP packets such as ICMP packets sent from the NMS. Do as follows to locate the fault. Perform a ping operation, and run the display icmp statistics command again to view statistics about ICMP packets. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 176 – On the intermediate device, apply the traffic policy in both the inbound and outbound directions of the associated interface. Take the following configurations as an example: interface GigabitEthernet1/0/0 Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 177 If the ACL is applied to a trunk interface or VLANIF interface, you need to configure the traffic policy on a physical member interface. Run the display traffic policy statisticsinterface command to view statistics about the Ping packets that match the ACL on each interface. <Huawei> display traffic policy statistics interface gigabitethernet 1/0/0 inbound Interface: GigabitEthernet1/0/0 inbound: test...
Page 178 ARP entry exists. If the required ARP entry does not exist, see the Huawei AR2200-S Series Troubleshooting - LAN Access and MAN Access. If the fault persists, go to Step 6.
Page 179 If error packet statistics increase, it indicates that the board on the device may become faulty. Then, collect the preceding information and contact Huawei technical support personnel. l If error packet statistics do not increase, go to Sub-step 3.
Page 180: Troubleshooting Cases
Ping packets are sent. If there is no information indicating that five Ping packets are sent, it indicates that ICMP packets are not delivered to an interface board. Step 9 Collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure...
Page 181 Step 1 Run the system-view command on Router B to enter the system view. Step 2 Run the undo arp static ip-address mac-address command to delete the static ARP entry. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 182: Dhcp Troubleshooting
If a static ARP entry is configured on a device, this entry must be modified after the MAC address changes. If Router B is a non-Huawei device and you cannot log in to it to check the configuration, configure the mirroring function to analyze packets transmitted between Router A and Router B, and then ping Router B from Router A.
Page 183 IP addresses in the global address pool and the interface IP address on the relay agent are on different network segments. There are no available addresses in the address pool. Troubleshooting Flowchart Figure 7-4 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 184 NOTE Saving the results of each troubleshooting step is recommended. If you are unable to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check whether a fault occurs on the link between the client and the DHCP server.
Page 185 Step 4 Check whether addresses in the global address pool and the IP address of the interface are on the same network segment. Run the display ip pool command to check whether a global address pool has been created. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 186 If the value of Idle(Expired) is greater than 0, there are idle (expired) IP addresses. Go to step 6. Step 6 Contact Huawei technical support personnel and provide them with the following information. l Results of the preceding troubleshooting procedure...
Page 187: A Client Cannot Obtain An Ip Address (The Ar2200-S Functions As The Dhcp Relay Agent)
DHCP server. The configurations of other devices along the link are incorrect. Troubleshooting Flowchart Figure 7-5 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 188 NOTE 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 whether a fault occurs between the DHCP client and the DHCP server.
Page 189 DHCP relay agent. Go to step 6. l If dhcp relay server-select group-name is displayed, the interface on the DHCP relay agent is bound to a DHCP server group. Go to step 5. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 190: Rip Troubleshooting
IP Address (the AR2200-S Functions as the DHCP Server). Step 7 Contact Huawei technical support personnel and provide them with the following information. l Results of the preceding troubleshooting procedure l Configuration file, log file, and alarm file of the AR2200-S...
Page 191: Device Does Not Receive Partial Or All The Routes
If a router receives partial or none routes or the display ip routing-table command dose not display routes learned by RIP, refer to the following troubleshooting flowchart, as shown in Figure 7-6. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 192 Troubleshooting Procedure NOTE Saving the results of each troubleshooting step is recommended. If you are unable to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Issue 01 (2012-01-06) Huawei Proprietary and Confidential...
Page 193 If the metric exceeds 16, the route is regarded as unreachable and is not added to the routing table. Step 7 Check whether the metric of the received routes is larger than 16. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 194: Device Does Not Send Some Or All Routes
Run the display ip routing-table protocol rip verbose command to view routes in the Inactive state. Step 10 If the fault persists, contact Huawei technical support personnel and provide them with the following information. l Results of the preceding troubleshooting procedure...
Page 195 The MTU value of the outgoing interface is less than 52. Troubleshooting Flowchart If a router sends partial or none routes, refer to the following troubleshooting flowchart, as shown Figure 7-7. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 196 Interface is enabled Any other multicast and peer Is fault problems? command is rectified? configured correctly Seek technical support Troubleshooting Procedure Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 197 NOTE Saving the results of each troubleshooting step is recommended. If you are unable to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check whether the outgoing interface is enabled with RIP.
Page 198: Ospf Troubleshooting
This potential source of the fault can be removed by configuring the peer command in the RIP mode to make routers send packets with unicast addresses. Step 9 If the fault persists, contact Huawei technical support personnel and provide them with the following information.
Page 199 Check the remote Is fault Due to 1-Wayhello device rectified? Received? Neighbor Down Check the remote Is fault Due to SequenceNum device rectified? Mismatch? Seek technical support Troubleshooting Procedure Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 200 NOTE Saving the results of each troubleshooting step is recommended. If you are unable to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check logs to find the cause of the fault.
Page 201 If the MTUs of the two interfaces are consistent, go to Step Step 7 Check whether there is an interface with a priority that is not 0. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 202 Check the Dead timer mismatch field. If the value of this field keeps increasing, the values of the dead timers on the two devices that establish the neighbor relationship are Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 203: The Ospf Neighbor Relationship Cannot Reach The Full State
If the fault persists, go to Step Step 9 Step 9 Contact Huawei technical support personnel and provide them with the following information. l Results of the preceding troubleshooting procedure l Configuration files, log files, and alarm files of the devices...
Page 204 Exstart state? Is the neighbor Is fault Perform the ping relationship always in rectified? operation. the Exchange state? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 205 NOTE Saving the results of each troubleshooting step is recommended. If you are unable to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Troubleshoot the fault based on the status of the OSPF neighbor relationship.
Page 206 OSPF process. If the fault persists, go to Step Step 2 Step 2 Collect the following information and contact Huawei technical support personnel. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 207: Trouble Cases
Fault Symptom On the network shown in Figure 7-10, Router C is a non-Huawei device. Router A and Router B are two routers. Router A and Router B have two upstream GE interfaces and are configured with two static routes.
Page 208 Router A to change the network type of the interface. Then, perform the same operation on Router B. After that, the fault is rectified. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 209 The FA field in the LSA sent by Router B is 10.1.2.26. The LSA is not calculated because the FA field of the LSA is incorrect. The conditions required to generate routes for load balancing are not met. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 210 The LSA with the FA field being set is not calculated because the priority of the LSA is lower. As a result, equal-cost routes cannot be formed. Procedure Step 1 To form equal-cost routes on the network, do as follows: Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 211 Run the following command on Router A to ping the peer device. Packet loss occurs. <RouterA> ping 10.1.1.0 PING 10.1.1.0: 56 data bytes, press CTRL_C to break Request time out Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 212 Figure 7-13 Network diagram of an OSPF routing loop that occurs because router IDs of the devices conflict City B City A Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 213 PE2. Services are restored after both OSPF processes restart. ----End Summary Specify the router ID of OSPF multi-instance as the unique addresses of the PEs. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 214: Multicast
Huawei AR2200-S Series Enterprise Routers Troubleshooting 8 Multicast Multicast About This Chapter 8.1 Layer 3 Multicast Troubleshooting Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 215: Layer 3 Multicast Troubleshooting
Check that the VLANs on the inbound and outbound interfaces of the multicast route function properly. Check that the PIM routing entries are created. Check that the multicast forwarding entries are created. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 216 NOTE Saving the results of each troubleshooting step is recommended. If 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 a route destined for the multicast source is available.
Page 217 Step 4 Check whether the multicast forwarding entries are created. Run the display multicast forwarding-table command to check that the multicast forwarding entries are created. If the fault persists, record the command output and contact Huawei technical support personnel. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright ©...
Page 218: The Pim Neighbor Relationship Remains Down
Huawei AR2200-S Series Enterprise Routers Troubleshooting 8 Multicast Step 5 Collect the following information and contact Huawei technical support personnel. Results of the preceding troubleshooting procedure Configuration files, log files, and alarm files of the devices ----End Relevant Alarms and Logs Relevant Alarms None.
Page 219 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, a record of the actions taken will exist to provide to Huawei technical support personnel. Procedure Step 1 Check that PIM is enabled on the interface.
Page 220 If the fault persists after the preceding operations are complete, go to Step Step 4 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 device...
Page 221: The Rpt On A Pim-Sm Network Fails To Forward Data
Configurations are incorrect, for example, the configurations of the TTL, MTU, or multicast boundary are improper. Troubleshooting Flowchart After a PIM-SM network is configured, the RPT cannot forward data. Figure 8-3 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 222 Is fault of the source-policy or Is a source-policy rectified? change the configurations configured? of the ACL Do correct (*, G) entries exist? Seek technical support Troubleshooting Procedure Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 223 NOTE Saving the results of each troubleshooting step is recommended. If 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 the PIM routing table contains correct (*, G) entries.
Page 224 DR. If the DR information in the command output is not marked with local, troubleshoot the involved DR following the preceding steps. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 225: The Spt On A Pim-Sm Network Fails To Forward Data
PIM routing table contains correct (*, G) entries. For details, see Step 1. If the fault persists after the preceding troubleshooting procedures are complete, go to Step 10. Step 10 Collect the following information and contact Huawei technical support personnel. Results of the preceding troubleshooting procedure...
Page 226 Configurations are incorrect. For example, the configurations of the TTL, MTU, switchover threshold, or multicast boundary are improper. Troubleshooting Flowchart After the PIM-SM network is configured, the SPT fails to forward data. Figure 8-4 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 227 Remove the configurations of the Is a source-policy Is fault source-policy or change the configured? rectified? configurations of the ACL Do correct (*, G) entries exist? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 228 NOTE Saving the results of each troubleshooting step is recommended. If 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 the PIM routing table contains correct (S, G) entries.
Page 229 If the command output contains an RPF route to the RP and the route is properly configured, go to Step 5. Step 5 Check that the interface that forwards multicast data is the receiver's DR. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 230: Msdp Peers Cannot Generate Correct (S, G) Entries
Run the display pim routing-table command on the device to check whether the PIM routing table contains (S, G) entries. For details, see Step 1. Step 9 Collect the following information and contact Huawei technical support personnel. Results of the preceding troubleshooting procedure...
Page 231 The SA message fails to pass RPF check. Troubleshooting Flowchart After configurations are complete on a multicast network, MSDP peers cannot generate correct (S, G) entries. Figure 8-5 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 232 MSDP Are import-source Remove or change the Is fault policies configured on configurations of the rectified? the current MSDP import-source policies peer? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 233 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, a record of the actions taken will exist to provide to Huawei technical support personnel. Procedure Step 1 Check that the status of MSDP peers is Up.
Page 234 (S, G) entries are permitted by the ACL. Then run the undo import-source command to delete the configurations of the ACL or change the configurations of the ACL rule. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 235: The Multicast Device Cannot Generate Igmp Entries Or Mld Entries
8 Multicast If no import policies are configured on the MSDP peers, go to Step Step 9 If the fault persists, collect the following information and contact Huawei technical support personnel. l Results of the preceding operation procedure l Configuration files, log files, and alarm files of the device...
Page 236 Are The Is fault Number of Entries And Re-plan network rectified? That of interfaces below the deployment upper limit? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 237 NOTE 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 multicast is enabled on the device.
Page 238 IGMP limit, or run the undo limit command in the IGMP view of the instance to delete the configured IGMP limit. If the command output does not contain the configurations of the IGMP limit for the instance, go to Step Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 239 If the fault persists after the preceding troubleshooting procedures are complete, go to Step Step 10 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...
Page 240 9.6 Congestion Management Troubleshooting This chapter describes common causes of congestion management faults, and provides the corresponding troubleshooting flowcharts, troubleshooting procedures, alarms, and logs. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 241: Traffic Policy Troubleshooting
The packets do not match rules of the traffic classifier in the traffic policy. The traffic behavior associated with the traffic classifier in the traffic policy is configured incorrectly. Troubleshooting Flowchart Figure 9-1 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 242 NOTE Saving the results of each troubleshooting step is recommended. If 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 the traffic policy is applied correctly.
Page 243 If yes, go to step 5. Step 5 Collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure l Configuration file, log file, and alarm file of the AR2200-S...
Page 244: Troubleshooting Cases
Run the display ip routing-table command to view the routing table. There is a route to 10.1.1.2/24. Run the display traffic-policy applied-record command in the view of Eth2/0/0 to check the traffic policy record. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 245 10.1.1.2. The fault is rectified. ----End Summary If PBR fails to take effect, the possible causes are as follows: The traffic policy fails to be applied. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 246: Priority Mapping Troubleshooting
– The traffic-policy outbound command with queue af, queue ef, or queue wfq configured has been used on the outbound interface of packets. Troubleshooting Flowchart Figure 9-3 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 247 NOTE Saving the results of each troubleshooting step is recommended. If 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 the type of the priority trusted by the inbound interface is correct.
Page 248 – If the display traffic behavior user-defined command output contains Assured Forwarding, Expedited Forwarding, or Flow based Weighted Fair Queuing, the Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 249: Priority Mapping Results Are Incorrect
4. l If the traffic-policy outbound command is not used, go to step 4. Step 4 Collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure l Configuration file, log file, and alarm file of the AR2200-S...
Page 250 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check whether packets carry the priority trusted by the inbound interface.
Page 251 If the traffic policy has been applied successfully, run the display traffic behavior user-defined command to check whether the traffic behavior contains packet priority re-marking, internal priority re-marking, or car with remark-8021p or remark-dscp. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 252 5. l If the traffic-policy outbound command is not used, go to step 5. Step 5 Collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure l Configuration file, log file, and alarm file of the AR2200-S...
Page 253: Troubleshooting Cases
----------------------------------------------------------------------------- ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- The preceding command output indicates that all packets enter queue 0. Packets should enter queues based on 802.1p priorities. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 254 After the preceding configurations are complete, run the display qos queue statistics interface ethernet 2/0/0 command. You can see that packets with 802.1p priorities 0 to 7 enter queues based on priorities. The fault is rectified. ----End Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 255 <RouterA> system-view [RouterA] interface ethernet 0/0/0 [RouterA-Ethernet0/0/0] display this trust 8021p [RouterA] interface ethernet 0/0/1 [RouterA-Ethernet0/0/1] display this trust 8021p traffic-policy tp1 inbound Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 256: Traffic Policing Troubleshooting
Traffic policing applies the traffic policy's Committed Access Rate (CAR) or aggregated CAR action to packet flows. Its troubleshooting roadmap is the same as that for traffic policy faults. For details, see 9.1.1 Traffic Policy Fails to Take Effect. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 257: Interface-Based Traffic Policing Results Are Incorrect
Interface-based traffic policing rate is incorrect Do statistics exist on interface? Correctly configure Is interface-based interface-based Is fault rectified? traffic policing set? traffic policing Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 258 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check the packet statistics on the interface configured with interface-based traffic policing.
Page 259 CIR value in the traffic behavior is greater than the CIR value for interface- based traffic policing, go to step 5. l If the traffic-policy command is not used, go to step 5. Step 5 Collect the following information and contact Huawei technical support personnel. Issue 01 (2012-01-06) Huawei Proprietary and Confidential...
Page 260: Troubleshooting Cases
[RouterA-Ethernet2/0/0] display this [V200R001C00B130] interface Ethernet2/0/0 ip address 10.0.0.1 255.255.255.0 qos car inbound cir 10000 cbs 1880000 pbs 3130000 green pass yellow pass red discard return Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 261: Traffic Shaping Troubleshooting
In combined scheduling mode, if the bandwidth is insufficient, the CIR value of other queues cannot be reached. This is a correct traffic shaping result. Troubleshooting Flowchart Figure 9-10 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 262 Incorrect Queues” Do queues use Do PQ Re-plan scheduling queues have excess combined scheduling mode? modes and weights packets? Is fault rectified? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 263 NOTE Saving the results of each troubleshooting step is recommended. If 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 queue-based traffic shaping parameters are set correctly.
Page 264: Troubleshooting Cases
This is a correct traffic shaping result. l If each queue uses PQ, WRR, DRR, or WFQ scheduling mode, go to step 6. Step 6 Collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure...
Page 265 CIR value for interface-based traffic shaping. Run the display this command in the view of the WAN-side interface on RouterA to check traffic shaping parameters. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 266: Congestion Avoidance Troubleshooting
9.5.1 Congestion Avoidance Fails to Take Effect This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure to use when congestion avoidance fails to take effect. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 267 Are WRED Is fault rectified? Set WRED parameters parameters correct? Do packets See “Packets Enter enter specified Is fault rectified? Incorrect Queues” queues? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 268 Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. The congestion avoidance mechanism discards packets based on the maximum number of packets buffered in a queue and the actual length of packets.
Page 269: Congestion Management Troubleshooting
9.2.1 Packets Enter Incorrect Queues. l If yes, go to step 4. Step 4 Collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure l Configuration file, log file, and alarm file of the AR2200-S...
Page 270 NOTE Saving the results of each troubleshooting step is recommended. If 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 traffic shaping is configured correctly on the outbound interface.
Page 271 If flow-based congestion management is configured on the interface, run the display traffic policy user-defined command to check whether scheduling parameters such as the scheduling mode and minimum bandwidth are correct. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 272: Troubleshooting Cases
9.2.1 Packets Enter Incorrect Queues. l If yes, go to step 5. Step 5 Collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure l Configuration file, log file, and alarm file of the AR2200-S...
Page 273 According to the preceding command output, queue 2 and queue 5 use WFQ scheduling, queue 6 and queue 7 use PQ scheduling, the weights of queue 2 and queue 5 are 50 and 20 Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 274 WRR queues. If bandwidth of PQ queues is not limited, service flows in PQ queues may occupy all the bandwidth of the interface, causing service interruption in other queues. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 275: Security
Huawei AR2200-S Series Enterprise Routers Troubleshooting 10 Security Security About This Chapter 10.1 AAA Troubleshooting 10.2 ARP Security Troubleshooting 10.3 NAC Troubleshooting 10.4 Firewall Troubleshooting 10.5 ACL Troubleshooting 10.6 NAT Troubleshooting Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 276: Aaa Troubleshooting
IP address, port number, shared key, and domain name carry method and resolution method configured on the RADIUS server are the same as those configured on the AR2200-S. Figure 10-1 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 277 Ensure that shared key RADIUS server record and user name format on Is the fault authentication RADIUS server and router rectified? failure? are the same Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 278 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Run the ping command to check whether the link between the AR2200-S and the RADIUS server is working.
Page 279 If debugging information is displayed, proceed according to the following debugging information. Debugging Information Solution Nov 10 2010 15:23:34.260.6 Huawei RDS/ The RADIUS module sent an 7/debug2: authentication packet. This message Radius Sent a Packet indicates that the AR2200-S can send...
Page 280 Huawei AR2200-S Series Enterprise Routers Troubleshooting 10 Security Debugging Information Solution Nov 10 2010 15:23:34.260.6 Huawei %% The RADIUS authentication server did not 01RDS/4/RDAUTHDOWN(l): send an authentication response packet. RADIUS authentication server ( IP: This may be because the link between the 192.168.1.128 )
Page 281: Hwtacacs Authentication Fails
Huawei AR2200-S Series Enterprise Routers Troubleshooting 10 Security Step 6 If the fault persists, collect the following information and contact Huawei technical support personnel: l Results of the preceding troubleshooting procedure l Configuration file, log file, and alarm file of the AR2200-S...
Page 282 Does key and user name HWTACACS server Is the fault formats on the record authentication rectified? HWTACACS server and failure? router are the same Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 283 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Run the ping command to check whether the link between the AR2200-S and the HWTACACS server is working.
Page 284 If debugging information is displayed, proceed according to the debugging information. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 285 Huawei AR2200-S Series Enterprise Routers Troubleshooting 10 Security Debugging Information Solution Nov 10 2010 15:43:35.500.6 Huawei TAC/ The HWTACACS module sent an 7/Event:HandleReqMsg: Session status authentication packet. This message is not connect now. indicates that the AR2200-S can send Nov 10 2010 15:43:35.500.7 Huawei TAC/ HWTACACS authentication packets.
Page 286 If the user is a network access user, rectify the fault according to "10.3 NAC Troubleshooting." Step 6 If the fault persists, collect the following information and contact Huawei technical support personnel: l Results of the preceding troubleshooting procedure...
Page 287: Troubleshooting Cases
Users are forced offline 10-plus seconds after they log in. Figure 10-3 Networking diagram of user access Domain huawei RouterB Network 129.7.66.66/24 RouterA 129.7.66.67/24 Destination network Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 288 15 seconds after login, users are forced offline. Procedure Step 1 Run the system-view command to enter the system view. Step 2 Run the aaa command to enter the AAA view. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 289 Huawei AR2200-S Series Enterprise Routers Troubleshooting 10 Security Step 3 Run the domain huawei command to enter the Huawei domain view. Step 4 Run the undo accounting-scheme provera command to configure the default accounting scheme (non-accounting) for users in the domain.
Page 290: Tacacs Server
RouterC Loopback0 Loopback0 After the configuration, the user fails to pass the Huawei Terminal Access Controller Access- Control System (HWTACACS) authentication by using the valid user name and password. Fault Analysis Check the user name and password configured on the HWTACACS server. The configured user name and password are the same as those entered by the user.
Page 291: Radius Server
..interface Ethernet2/0/0 port hybrid pvid vlan 10 dot1x enable dot1x max-user 1 dot1x port-method port dot1x reauthenticate ..authentication-scheme default authentication-scheme cams authentication-mode radius authorization-scheme default Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 292 Use the default authentication, authorization, and accounting schemes in the domain, that is, local authentication, local authorization, and no accounting. <Huawei> display domain name telnet Domain-name : telnet Domain-state : Active Authentication-scheme-name : default Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 293: Arp Security Troubleshooting
Create a local user whose user name contains the domain name. The Telnet user needs to enter the domain name for authentication. <Huawei> system-view [Huawei] aaa [Huawei-aaa] local-user telnetuser@telnet password simple 123456 [Huawei-aaa] local-user telnetuser@telnet service-type telnet ----End Summary Use different authentication modes for access users (such as 802.1x user), Telnet users, and Secure Shell (SSH) users.
Page 294 Increase rate-limit Are ARP replies connection value discarded by normal? CPCAR? Is the fault Rectify the link fault rectified? Is the fault rectified? Seek technical support Troubleshooting Procedure Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 295 NOTE 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 Run the display arp anti-attack configuration entry-check command on the AR2200-S to check that ARP anti-spoofing is enabled.
Page 296: The Gateway Address Is Maliciously Changed
Is the fault gateway anti-collision collision rectified? configured? Are gateway Configure a policy to Is the fault anti-collision entries discard attack packets rectified? generated? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 297 NOTE 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 the AR2200-S functions as the gateway. If the AR2200-S is not the gateway, the gateway anti-collision function does not take effect.
Page 298: User Traffic Is Interrupted By A Large Number Of Bogus Arp Packets
Subsequently, packets from the attacker will be discarded. l If no entry is displayed, go to step 5. Step 5 Collect the following information and contact Huawei technical support personnel: l Results of the preceding troubleshooting procedure...
Page 299 Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. ARP attack packets include ARP request packets and ARP reply packets. In the following procedure, the ARP attack packets are ARP request packetes.
Page 300: Ip Address Scanning Occurs
ARP requests is limited to 5 pps. After the rate of ARP requests reaches this limit, the AR2200-S discards subsequent ARP requests. Step 7 If the fault persists, collect the following information and contact Huawei technical support personnel:...
Page 301 Troubleshooting Procedure NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Issue 01 (2012-01-06) Huawei Proprietary and Confidential...
Page 302 ARP Miss packets, run the arp-miss anti-attack rate-limit command in the system view, VLAN view, or interface view. Step 6 If the fault persists, collect the following information and contact Huawei technical support personnel: Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright ©...
Page 303: Arp Learning Fails
ARP reply is discarded. The ARP reply is sent to the CPU but is The ARP module of the AR2200-S is faulty. discarded. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 304 NOTE Saving the results of each troubleshooting step is recommended. If 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 the link between the AR2200-S and the remote device works properly.
Page 305 Step 4 Check that the remote device correctly receives ARP request packets and sends ARP reply packets. If the remote device is a Huawei device, perform step 2 on the device. If the remote device is a non-Huawei device, see the manual of the device.
Page 306: Nac Troubleshooting
The user name or password entered by the user is incorrect. The number of online users reaches the maximum. Troubleshooting Flowchart A user fails to pass the 802.1x authentication. Figure 10-10 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 307 NOTE Saving the results of each troubleshooting step is recommended. If 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 802.1x authentication is enabled on the AR2200-S.
Page 308 AR2200-S to keep the user online if the accounting fails. Step 4 Check the configuration of the authentication server. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 309 If the authentication fails, check the configuration of the RADIUS server and RADIUS configuration on the AR2200-S. For details, see Troubleshooting Procedure 10.1.1 RADIUS Authentication Fails. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 310: Mac Address Authentication Of A User Fails
If the number of online 802.1x users reaches the maximum, the AR2200-S does not trigger authentication for subsequent users, and subsequent users cannot go online. Step 7 If the fault persists, collect the following information and contact Huawei technical support personnel:...
Page 311 NOTE Saving the results of each troubleshooting step is recommended. If 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 MAC address authentication is enabled on the AR2200-S.
Page 312 If local authentication is configured for the user domain, run the display local-user command to check whether the local user name and password are created on the Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 313 IP address, (source IP address), a mask, or a port src-ipmask (mask of number. source IP address), and tcp-srcport (source TCP port number). Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 314: Mac Address Bypass Authentication Of A User Fails
If the number of online MAC address authentication users has reached the maximum, the AR2200-S does not trigger authentication for subsequent users, and they cannot go online. Step 6 If the fault persists, collect the following information and contact Huawei technical support personnel:...
Page 315 NOTE Saving the results of each troubleshooting step is recommended. If 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 SYN Flood attack defense is enabled.
Page 316: Acl Troubleshooting
If the packet rate threshold is set properly, go to step 3. Step 3 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 switches...
Page 317 NOTE Saving the results of each troubleshooting step is recommended. If 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 the ACL referenced by the packet filtering firewall is configured correctly.
Page 318: Nat Troubleshooting
Outbound NAT is not properly configured on the outbound interface connected to the public network. The configuration of an ACL bound to outbound NAT is incorrect. Troubleshooting Flowchart Figure 10-14 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 319 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check whether packets are received on the interface.
Page 320 To view Easy IP information on the outbound interface, run the display nat outbound command on the AR2200-S. For example: [Huawei] display nat outbound NAT Outbound Information: ----------------------------------------------------------------- Interface Address-group/IP Type ----------------------------------------------------------------- GigabitEthernet0/0/1 2000 30.30.30.1 easyip ----------------------------------------------------------------- Total : 1 Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 321: External Hosts Fail To Access Internal Servers
VRRP status of the interface. Step 4 Collect the following information and contact Huawei technical support personnel: Results of the preceding troubleshooting procedure Configuration files, log files, and alarm files of the AR2200-S...
Page 322 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check whether services on the internal NAT server are running properly.
Page 323 If the gateway address or route configured on the internal NAT server is correct but the fault persists, go to step 5. Step 5 Collect the following information and contact Huawei technical support personnel: Results of the preceding troubleshooting procedure...
Page 324: Internal Host With A Conflicting Ip Address Fails To Access An External Server
IP address of an external server. The route between the temporary address pool and the outbound interface is not configured. Troubleshooting Flowchart Figure 10-16 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 325 Troubleshooting Procedure NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Issue 01 (2012-01-06) Huawei Proprietary and Confidential...
Page 326 IP address are configured. [AR2200-S]display nat dns-map NAT DNS mapping information: Domain-name : test1 Global IP : 10.1.1.1 Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 327 Run the display ip routing-table command on the AR2200-S to view all the routes on the public network. [AR2200-S]display ip routing-table Route Flags: R - relay, D - download to fib ------------------------------------------------------------------------------ Routing Tables: Public Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 328 If there is no correct route, reconfigure a route. l If the route is correct but the fault persists, go to step 5. Step 6 Collect the following information and contact Huawei technical support personnel: Results of the preceding troubleshooting procedure...
Page 329: Reliability
Huawei AR2200-S Series Enterprise Routers Troubleshooting 11 Reliability Reliability About This Chapter 11.1 Interface Backup Troubleshooting 11.2 BFD Troubleshooting 11.3 VRRP Troubleshooting Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 330: Interface Backup Troubleshooting
– The load balancing threshold and maximum bandwidth are not configured for the primary interface. – An equal-cost route is not generated. – Only one flow needs to be transmitted. Troubleshooting Flowchart Figure 11-2 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 331 Troubleshooting Procedure NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Issue 01 (2012-01-06) Huawei Proprietary and Confidential...
Page 332 Route Flags: R - relay, D - download to fib ---------------------------------------------------------------------------- Routing Tables: Public Destinations : 7 Routes : 7 Destination/Mask Proto Cost Flags NextHop Interface 2.2.2.0/24 Static 192.168.1.2 GigabitEthernet1/0/0 Static 192.168.2.2 GigabitEthernet2/0/0 Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 333: Troubleshooting Cases
If multiple flows are transmitted over links, 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 device...
Page 334 GE1/0/0. When the traffic volume of the primary interface falls below the lower threshold, the backup interface is disabled. Consequently, the backup interface frequently alternates between Up and Down states. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 335: Bfd Troubleshooting
The link detected by the BFD session fails. As a result, BFD packets cannot be exchanged between the two ends of the BFD session. The BFD session status flaps. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 336 Down exist? Is fault rectified? Is fault rectified? Two ends Of the BFD session can ping each other? Seek technical Check the link support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 337 NOTE 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 Run the display current-configuration command to check that the configurations of the BFD session is committed.
Page 338: Interface Forwarding Is Interrupted After A Bfd Session Detects A Fault And Goes Down
If the BFD detection time is longer than the delay time on the link, go to Step Step 9 If the fault persists, collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure.
Page 339 NOTE 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 Run the display interface interface-type interface-number command to check the status of the interface to which the BFD session is bound.
Page 340: Changed Bfd Session Parameters Do Not Take Effect
BFD session detected a fault and went Down. l If the process-interface-status command is not configured, go to Step Step 4 If the fault persists, collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure.
Page 341 NOTE 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 Run the display current-configuration configuration bfd-session command to check that the commit command is configured.
Page 342: Dynamic Bfd Session Fails To Be Created
If BFD session parameters are specified, the modified parameters take effect. l If BFD session parameters are not specified, go to Step Step 3 If the fault persists, collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure.
Page 343 Context NOTE 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. Issue 01 (2012-01-06) Huawei Proprietary and Confidential...
Page 344: Vrrp Troubleshooting
If such a command is not configured, go to step Step 5 If the fault persists, 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.
Page 345 Eth2/0/1 connected to RouterA or Eth2/0/2 connected to RouterB, indicating that the learned MAC address is incorrect. MAC address table of slot ------------------------------------------------------------------------------ MAC Address VLAN/ PEVLAN CEVLAN Port Type LSP/ VSI/SI MAC- Tunnel Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 346 0098-0113-0005 1 Eth2/0/2 dynamic 0018-824f-f5d1 1 Eth2/0/0 dynamic ------------------------------------------------------------------------------ Total matching items on slot 1 displayed = [RouterC] display mac-address dynamic MAC address table of slot ------------------------------------------------------------------------------ Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 347 Step 3 Run the undo loopback command to disable the loopback function on the interface. After the preceding operations are performed, no traffic is discarded. The fault is rectified. ----End Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 348 Enabling the loopback function on the interface of a Layer 2 device is not recommended. If the loopback function is enabled, incorrect MAC addresses will be learned. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 349 About This Chapter 12.1 GRE Troubleshooting This section describes how to troubleshoot common GRE faults and provides sample troubleshooting scenarios in the following sections. 12.2 IPSec Troubleshooting Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 350: Gre Troubleshooting
12-1, PC1 and PC2 cannot communicate. To rectify the fault, follow the troubleshooting flowchart shown in Figure 12-2. Figure 12-1 GRE networking diagram RouterA RouterB Tunnel RouterC 10.1.1.1/24 10.2.1.1/24 Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 351 NOTE Save the results of each troubleshooting step. If troubleshooting fails to correct the fault, you will have a record of your actions to provide to Huawei technical support personnel. Procedure To troubleshoot when the network layer protocol of one or both ends of a tunnel is Down,...
Page 352 – If there are reachable routes between the tunnel source and destination addresses but the fault persists, go to step 4. Collect the following information and contact Huawei technical support personnel. – Results of the preceding troubleshooting procedure – Configuration file, log file, and alarm file of the device...
Page 353: Troubleshooting Cases
– If IP addresses of the two interfaces are on the same network segment or reachable routes exist between the two devices, go to step 3. Collect the following information and contact Huawei technical support personnel. – Results of the preceding troubleshooting procedure –...
Page 354 Route Port,The Maximum Transmit Unit is 1500 Internet Address is 21.1.1.1/24 Encapsulation is TUNNEL, loopback not set Tunnel source 2.2.2.2 (LoopBack1), destination 1.1.1.1 Tunnel protocol/transport GRE/IP, key disabled keepalive disabled Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 355 Tunnel Tunnel0/0/1 10.1.1.1/16 10.2.1.1/16 Fault Analysis Possible causes are as follows: Routes from RouterA to PC2 do not exist. Routes from RouterB to PC1 do not exist. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 356: Ipsec Troubleshooting
IP addresses of local and remote devices are incorrect or SA parameters at both ends do not match. The ACLs referenced by IPSec policies at both ends do not mirror each other. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 357 Modify Do ACLs at configurations so Is fault both ends mirror each that the ACLs rectified? other? mirror each other Seek technical support Troubleshooting Procedure Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 358 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check whether the interfaces at both ends of the IPSec tunnel can ping each other.
Page 359 5 permit ip source 10.1.2.0 0.0.0.255 destination 10.1.1.0 0.0.0.255 If the ACLs referenced by IPSec policies at both ends of the IPSec tunnel do not mirror each other, modify the configuration according to Huawei AR2200-S Series Enterprise Routers Configuration Guide - IPSec.
Page 360: Sas Fail To Be Established By Using Ike Negotiation
If the ACLs referenced by IPSec policies at both ends of the IPSec tunnel mirror each other, go to step 6. Step 6 Collect the following information and contact Huawei technical support personnel. l Results of the preceding troubleshooting procedure...
Page 361 Is fault sent from specified are sent from rectified? interface? specified interface Do data flows Modify the ACL Is fault match the ACL? configuration rectified? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 362 IPSec rectified? policies match Modify Do ACLs at both configurations so Is fault ends mirror each other? that the ACLs rectified? mirror each other Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 363 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check whether the IPSec SA and IKE SA are established successfully.
Page 364 ACL referenced by the IPSec policy. If the data flows do not match the ACL, they cannot enter the IPSec tunnel. Instead, the data flows are forwarded directly. To modify the matching rule, see Huawei AR2200-S Series Enterprise Routers Configuration Guide - IPSec.
Page 365 5 permit ip source 10.1.2.0 0.0.0.255 destination 10.1.1.0 0.0.0.255 If the ACLs referenced by IPSec policies at both ends of the IPSec tunnel do not mirror each other, modify the configuration according to Huawei AR2200-S Series Enterprise Routers Configuration Guide - IPSec.
Page 366 If not, run the pre-shared-key command to change the preshared key. Step 10 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 Router...
Page 367: Ipsec Fails To Be Configured By Using An Ipsec Policy Template
IKE peers do not match. Troubleshooting Flowchart After IPSec is configured by using an IPSec policy template, IPSec cannot protect data. Figure 12-9 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 368 Do data flows Modify the ACL Is fault match the ACL? configuration rectified? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 369 IPSec rectified? policies match Modify Do ACLs at both configurations so Is fault ends mirror each other? that the ACLs rectified? mirror each other Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 370 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check whether the IPSec SA and IKE SA are established successfully.
Page 371 ACL referenced by the IPSec policy. If the data flows do not match the ACL, they cannot enter the IPSec tunnel. Instead, the data flows are forwarded directly. To modify the matching rule, see Huawei AR2200-S Series Enterprise Routers Configuration Guide - IPSec.
Page 372 If the DH groups at both ends are different, run the pfs { dh-group1 | dh- group2 } command to change the DH groups to be the same. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 373 If preshared key authentication is used, configure a preshared key for each peer. The preshared keys of peers that establish a connection must be the same. If not, run the pre-shared-key command to change the preshared key. Step 10 Collect the following information and contact Huawei technical support personnel. Issue 01 (2012-01-06) Huawei Proprietary and Confidential...
Page 374: Nat Traversal In Ipsec Fails
IKE peers do not match, NAT traversal is disabled, or the IKE peer ID type is not name. Troubleshooting Flowchart Figure 12-12 shows the troubleshooting flowchart. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 375 Do data flows Modify the ACL Is fault match the ACL? configuration rectified? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 376 Modify configurations Do ACLs at both Is fault so that the ACLs ends mirror each other? rectified? mirror each other Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 377 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check whether the IPSec SA and IKE SA are established successfully.
Page 378 ACL referenced by the IPSec policy. If the data flows do not match the ACL, they cannot enter the IPSec tunnel. Instead, the data flows are forwarded directly. To modify the matching rule, see Huawei AR2200-S Series Enterprise Routers Configuration Guide - IPSec.
Page 379 5 permit ip source 10.1.2.0 0.0.0.255 destination 10.1.1.0 0.0.0.255 If the ACLs referenced by IPSec policies at both ends of the IPSec tunnel do not mirror each other, modify the configuration according to Huawei AR2200-S Series Enterprise Routers Configuration Guide - IPSec.
Page 380 IPSec tunnel are the same. If the settings of IKE proposals at both ends of the IPSec tunnel are different, reconfigure IKE proposals according to Huawei AR2200-S Series Enterprise Routers Configuration Guide - IPSec.
Page 381: Gre Over Ipsec Fails
If not, run the pre-shared-key command to change the preshared key. Step 10 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 Router...
Page 382 Does IP header encapsulated on Modify the ACL Is fault GRE tunnel match configuration rectified? ACL? Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 383 IPSec rectified? policies match Modify Do ACLs at both configurations so Is fault ends mirror each other? that the ACLs rectified? mirror each other Seek technical support Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 384 NOTE Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel. Procedure Step 1 Check whether the IPSec SA and IKE SA are established successfully.
Page 385 ACL referenced by the IPSec policy. If the data flows do not match the ACL, they cannot enter the IPSec tunnel. Instead, the data flows are forwarded directly. To modify the matching rule, see Huawei AR2200-S Series Enterprise Routers Configuration Guide - IPSec.
Page 386 5 permit ip source 10.1.2.0 0.0.0.255 destination 10.1.1.0 0.0.0.255 If the ACLs referenced by IPSec policies at both ends of the IPSec tunnel do not mirror each other, modify the configuration according to Huawei AR2200-S Series Enterprise Routers Configuration Guide - IPSec.
Page 387 IPSec tunnel are the same. If the settings of IKE proposals at both ends of the IPSec tunnel are different, reconfigure IKE proposals according to Huawei AR2200-S Series Enterprise Routers Configuration Guide - IPSec.
Page 388: Troubleshooting Cases
Huawei AR2200-S Series Enterprise Routers Troubleshooting 12 VPN Step 10 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 Router ----End Relevant Alarms and Logs Relevant Alarms None.
Page 389 PC A and PC B are protected and the tunnel is used to encapsulate IP packets. After the configuration is complete, no SA is generated by using IKE negotiation. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 390 Run the sa trigger-mode auto command in the system view on Router A to change the SA triggering mode to automatic. Construct data flows to trigger negotiation. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
Page 391 After IPSec policies are configured at both ends, at least one end initiates IKE negotiation. If an IPSec policy template is used, the remote end must initiate negotiation. The SA triggering mode can be automatic or traffic-based triggering. Issue 01 (2012-01-06) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

This manual is also suitable for:

Ar2200-s series

Huawei V200R001C01 Troubleshooting Manual

About this Document

1 Hardware

2 System

3 Physical Connection and Interfaces

4 Lan

5 Wan

6 Voice

7 IP Forwarding and Routing

8 Multicast

9 Qos

10 Security

11 Reliability

12 Vpn

Quick Links

Troubleshooting

Troubleshooting

Related Manuals for Huawei V200R001C01

Summary of Contents for Huawei V200R001C01

This manual is also suitable for:

Table of Contents