H3C MSR Series Troubleshooting Manual
  1. Manuals
  2. Brands
  3. H3C Manuals
  4. Network Router
  5. MSR Series
  6. Troubleshooting manual

H3C MSR Series Troubleshooting Manual

Hide thumbs Also See for MSR Series:
Table of Contents

Advertisement

Quick Links

Download this manual
H3C MSR Routers
Troubleshooting Guide
H3C MSR 810 routers (centralized devices)
H3C MSR 2600 routers (centralized devices)
H3C MSR 3600 routers (centralized devices)
H3C MSR 5600 routers (distributed devices)
Document version: 6W100-20200112
Copyright © 2020 New H3C Technologies Co., Ltd. All rights reserved.
No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New
H3C Technologies Co., Ltd.
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are
the property of their respective owners.
The information in this document is subject to change without notice.

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the MSR Series and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for H3C MSR Series

Summary of Contents for H3C MSR Series

  • Page 1 No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd. Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.

  • Page 2: Table Of Contents

    Contents Introduction ····················································································· 1   General guidelines ····················································································································· 1   Collecting log and operating information ························································································· 1   Collecting common log messages ··························································································· 2   Collecting diagnostic log messages ······························································································· 4   Collecting operating statistics ································································································· 5   Contacting technical support ········································································································ 7  ...

  • Page 3: Introduction

    To prevent a problem from causing loss of configuration, save the configuration each time you finish configuring a feature. For configuration recovery, regularly back up the configuration to a remote server. When you troubleshoot H3C MSR routers, follow these general guidelines: • To help identify the cause of the problem, collect system and configuration information, including: Symptom, time of failure, and configuration.

  • Page 4: Collecting Common Log Messages

    Table 1 Log and operating information Category File name format Content Common log Command execution and operational log messages. logfileX.log Diagnostic log messages about device operation, including the following items: • Parameter settings in effect when an error occurs. Diagnostic log diagfileX.log •...
  • Page 5 # Display the log file on the master device. <Sysname> dir cfa0:/logfile/ Directory of cfa0:/logfile 0 -rw- 21863 Jul 11 2013 16:00:37 logfile.log 1021104 KB total (421552 KB free) # Display the log file on each subordinate device. <Sysname> dir slot2#cfa0:/logfile/ Directory of slot2#cfa0:/logfile 0 -rw- 21863 Jul 11 2013 16:00:37...

  • Page 6: Collecting Diagnostic Log Messages

    Collecting diagnostic log messages Collecting diagnostic log messages on a standalone centralized device # Save diagnostic log messages from the diagnostic log file buffer to a diagnostic log file. By default, the diagnostic log file is saved in the diagfile directory of the storage medium on the device.

  • Page 7: Collecting Operating Statistics

    • Do not execute commands while operating statistics are being collected. • H3C recommends saving operating statistics to a file to retain the information. NOTE: The amount of time to collect statistics increases along with the number of cards. To collect operating statistics: Disable pausing between screens of output if you want to display operating statistics on the screen.
  • Page 8 # To save operating statistics, enter y at the prompt and then specify the destination file path. Save or display diagnostic information (Y=save, N=display)? [Y/N] :y Please input the file name(*.tar.gz)[cfa0:/diag.tar.gz] :cfa0:/diag.tar.gz Diagnostic information is outputting to cfa0:/diag.tar.gz. Please wait... Save successfully.

  • Page 9: Contacting Technical Support

    Contacting technical support If you cannot resolve a problem by using the troubleshooting procedures in this document, contact H3C Support. When you contact an authorized H3C support representative, be prepared to provide the following information: • Information described in "General guidelines."...

  • Page 10: Failure To Forward Packets

    2 command in probe view to collect the MAC information. Execute the display hardware internal module interface-name interface-number reg 3 command in probe view to collect the PHY information. Contact H3C Support. Failure to forward packets Symptom An Ethernet interface on an intermediate router cannot forward packets.

  • Page 11: Related Commands

    3 command in probe view to collect the PHY information. Execute the display hardware internal ibd pkt-info slot slot-number slot-number command in probe view to collect inter-card packet statistics. Contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting Ethernet interfaces.

  • Page 12: Troubleshooting E1 And T1 Interfaces

    Replace the host. If local loopback succeeds after the host is replaced, the host has hardware problems. In this case, proceed with the device component analysis process. Troubleshooting the cables Examine the cable quality. Verify the cables are H3C-standard cables.

  • Page 13: Troubleshooting The Configuration

    Identify whether the cable impedance matches the interface impedance. a. Execute the display controller or display fe1 command to view the interface impedance (text in blue in the command output). [H3C] display controller E1 1/0/0 E1 1/0/0 current state :DOWN Description : E1 1/0/0 Interface Basic Configuration: Work mode is E1 framed, Cable type is 120 Ohm balanced.

  • Page 14: Troubleshooting The Clocks

    TIP: The Cisco E1 interfaces use the CRC4 framing format by default. The H3C E1 interfaces use the no-CRC4 framing format by default. When interconnecting such E1 interfaces, make sure they use the same configuration.

  • Page 15: Troubleshooting The Grounding

    Troubleshooting the grounding Typically bad grounding and common grounding • The device is installed in a 19-inch cabinet, but the grounding cable of the device is not connected to the grounding strip of the cabinet. • The device and its peer device are in the same equipment room, both devices are grounded, but they are not commonly grounded.
  • Page 16 Figure 3 Grounding when grounding strips are provided When the device is installed in a 19-inch cabinet, you can connect the yellow-green grounding cable to the grounding terminal of the cabinet, and make sure the grounding terminal of the 19-inch cabinet is well connected to the grounding strips of the equipment room.
  • Page 17 of the DC power supply is well grounded in DC power supply output of the DC power supply cabinet. Otherwise, submit the rectification requirements to the customer as soon as possible. Figure 5 Grounding using the PGND wire of the DC power supply cabinet  ...
  • Page 18 Ground resistance Determine the ground resistance of the grounding strips according to the equipment room environment requirements. For the central telecom equipment room, determine the ground resistance according to YDJ26-89 (which requires the ground resistance to be smaller than 1Ω). For non-central telecom equipment rooms, the ground resistance must be lower than 5Ω.

  • Page 19: Troubleshooting Through Looping

    Figure 8 Identifying whether the devices are commonly grounded well Troubleshooting through looping Common looping points Figure 9 Common looping points (vice versa) Looping point 1 Method: Execute the loopback local command on the E1 interface of the router, and execute the fe1 loopback local command on the FE1 interface.

  • Page 20: Troubleshooting E1/T1 Interfaces

    If the command output shows that the number of received packets evenly increases by 12 packets, loopback is detected, and no error packets appear, the link is normal. Otherwise, the link fails. [H3C]dis int ser 1/0:0 Serial1/0:0 Current state: UP...

  • Page 21: Troubleshooting Physical Interface Anomaly

    Troubleshoot the hardware. Troubleshoot the cables. Troubleshoot the configuration. Troubleshoot the clocks. Troubleshoot grounding. Troubleshoot through looping. Collecting information If the issue persists, execute the following commands to collect information and contact H3C Support. • display diagnostic-information • display device verbose •...

  • Page 22: Troubleshooting Ipsec

    [H3C-probe]dis hardware internal physical Serial slot-number/port-number(:sub-channel-number) ? boardinfo show board info diag_info Cellular diagnosis information intinfo Base information intinfo_priv Private information rx_queue show receive queue rxbd show receive BD statistic show state tx_queue show transmit queue txbd show transmit BD Troubleshooting IPsec This section provides troubleshooting information for common problems with IPsec.
  • Page 23 Initiator  Receiver  Unencrypted, iCookie=xxx, rCookie=0, Payload: SA, KEY  EXCHANGE, NONCE, Vendor ID, Identification  Unencrypted, iCookie=xxx, rCookie=xxx, Payload: SA, KEY  Aggressive  EXCHANGE, NONCE, Vendor ID, Identification, HASH  mode  Encrypted, Payload: KEY EXCHANGE, NONCE, ID  Encrypted, Payload: SA, NONCE，ID  Quick mode  Encrypted, Payload: SA, NONCE, ID, HASH  Encrypted, Payload: HASH  IPsec SA negotiation is performed in phase 2 negotiation. Something wrong might occur in phase 2 negotiation. To resolve the problem: On the initiator, display IKE debugging information by using the debugging ike all command.
  • Page 24 *Nov 7 09:23:15:524 2014 ROUTER IKE/7/DEBUG: exchange state machine(I): finished step 2, advancing... //Phase 1 negotiation finished. ………………… *Nov 7 09:23:21:801 2014 ROUTER IKE/7/DEBUG: send message: //The device sent the first packet for the phase 2 negotiation. *Nov 7 09:23:21:902 2014 ROUTER IKE/7/DEBUG: ICOOKIE: 0xb8a20d7c014806fa *Nov 7 09:23:22:002 2014 ROUTER IKE/7/DEBUG:...
  • Page 25 //A matching IKE profile was found. ……… *Nov 6 17:03:05:528 2014 ROUTER IKE/7/Event: Found pre-shared key in keychain 1 matching address 10.1.1.1. //A matching keychain was found. ………. *Nov 6 17:03:05:535 2014 ROUTER IKE/7/Event: IKE SA state changed from IKE_P1_STATE_INIT to IKE_P1_STATE_SEND2. *Nov 6 17:03:05:535 2014 ROUTER IKE/7/Packet: Sending packet to 10.1.1.1 remote port 500, local port 500.

  • Page 26: Related Commands

    Display the IPsec policy configuration on the initiator and the receiver. The following shows the IPsec policy configuration on the receiver: ipsec policy hzbank 7000 isakmp transform-set 1 security acl 3000 ike-profile 1 reverse-route dynamic reverse-route tag 10 Verify that the transform set configuration (such as the encryption and authentication algorithms) is consistent on both devices.

  • Page 27: Troubleshooting Pppoe

    Command Description display ipsec sa [ brief | count | interface interface-type interface-number | { ipv6-policy | Displays information about IPsec SAs. policy } policy-name [ seq-number ] | profile profile-name | remote [ ipv6 ] ip-address ] Displays IKE error debugging information. debugging ike error Displays IKE event debugging information.

  • Page 28: Related Commands

    User-Name="\r0W'ZK5A9fd00001" User-Password=****** Service-Type=Framed-User NAS-Identifier="3640" NAS-Port=4096 NAS-Port-Type=Ethernet Calling-Station-Id="8c21-0a7e-71c5" Acct-Session-Id="00000005201410221400070000001e001 225" NAS-Port-Id="slot=65535;subslot=0;port=0;vlanid=0" H3c-Ip-Host-Addr="255.255.255.255 8c:21:0a:7e:71:c5" NAS-IP-Address=60.191.123.92 H3c-Product-Id="H3C MSR36-40" H3c-Nas-Startup-Timestamp=1413972953 …. *Oct 22 13:59:46:225 2014 3640 PPP/7/PAP_EVENT_0: PPP Event: Virtual-Access0 PAP Receive AAA Result Event State WaitAAA *Oct 22 13:59:46:225 2014 3640 PPP/7/AUTH_ERROR_0: PPP Error: Virtual-Access0 PAP: Receive AAA reject message, authentication failed! As the debugging information shows, the username received by PPP is incorrect.

This manual is also suitable for:

Msr 810Msr 2600Msr 3600Msr 5600

Table of Contents