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

H3C SR6600 Series Troubleshooting Manual

Hide thumbs Also See for SR6600 Series:
Table of Contents

Advertisement

Quick Links

Download this manual
H3C SR6600&SR6600-X Routers
Troubleshooting Guide
SR6600 Router Series
SR6600-X Router Series
Software version: R7606
Document version: 6W101-20181015
Copyright © 2018 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.
i

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for H3C SR6600 Series

Summary of Contents for H3C SR6600 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 ··········································································································· 3 Collecting operating statistics····················································································································· 3 Contacting technical support ······························································································································ 5 Troubleshooting CPOS interfaces ·································································· 6 CPOS interface and serial interface down ·········································································································...
  • Page 3 Cross-chassis packet loss problem ················································································································· 19 Symptom ·················································································································································· 19 Solution ···················································································································································· 19 IRF split ···························································································································································· 19 Symptom ·················································································································································· 19 Solution ···················································································································································· 19 Related commands ·········································································································································· 20 Troubleshooting cards ················································································· 22 MPU or SR6602-X device startup failure ········································································································· 22 Symptom ·················································································································································· 22 Solution ····················································································································································...

  • Page 4: Introduction

    Introduction This document provides information about troubleshooting common software and hardware problems with H3C SR6600/SR6600-X routers. General guidelines IMPORTANT: 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.

  • Page 5: Collecting Common Log Messages

    Table 1 Log and operating information Category File name format Content logfileX.log Common log Command execution and operational log messages. Diagnostic log messages about device operation, including the following items: • Parameter settings in effect when an error occurs. Diagnostic log diagfileX.log •...

  • Page 6: Collecting Diagnostic Log Messages

    0 -rw- 21863 Jul 11 2013 16:00:37 logfile8.log 1021104 KB total (421552 KB free) NOTE: If a subordinate chassis has two MPUs, make sure you identify and export the log files on both MPUs. Transfer the files to the desired destination by using FTP, TFTP, or USB. (Details not shown.) Collecting diagnostic log messages Save diagnostic log messages from the diagnostic log file buffer to a diagnostic log file.
  • Page 7 Do not execute commands while operating statistics are being collected. • H3C recommends saving operating statistics to a file to retain the information. To collect operating statistics: Disable pausing between screens of output if you want to display operating statistics on the screen.

  • Page 8: Contacting Technical Support

    …… Contacting technical support If you cannot resolve a problem after 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...

  • Page 9: Troubleshooting Cpos Interfaces

    Verify that the HDLC chip of the CPOS interface collects packet statistics correctly. If the problem persists, collect the following statistics and contact H3C Support: Execute the debugging physical packet command to enable packet debugging on both ...

  • Page 10: Data Link Layer Protocol Flapping Or Traffic Forwarding Failure On Serial Interface

    "CPOS interface and serial interface down" to resolve the problem. If the problem persists, collect the following statistics and contact H3C Support: Execute the display hardware internal module interface-number command in probe view  to determine whether the serial interface has received or sent error packets and collect packet statistics.
  • Page 11 Command Description Sets the clock mode of the CPOS interface to clock master master. debugging physical packet Enables packet debugging on the device. Displays status information for CPOS interfaces, including alarms and errors that occurred to the display controller cpos interface-name regenerator section, multiplex...

  • Page 12: Troubleshooting Fip-600 Modules

    4 command. In probe view, execute the display hardware internal fdp cdat slot slot-num statistics 8 command to view the packet drop statistics of the CPU and the logic module. Contact H3C Support to learn the causes for the packet drop.

  • Page 13: Failure To Forward Traffic

    Execute the display hardware internal fdp cdat slot slot-num statistics 8 command in  probe view to view the packet loss statistics. Contact H3C Support to learn the causes for the packet loss. Execute the display hardware internal fdp flow slot slot-num statistic command to view ...

  • Page 14: Packet Loss

    If the packets are dropped by the logic module before being sent to the CPU, execute the display hardware internal fdp cdat slot slot-num statistics 8 command in probe view to view the packet loss statistics of the logic module. Contact H3C Support to learn the causes for the packet loss.
  • Page 15 Command Description display hardware internal fdp cdat slot slot-num Displays the CPU data channel statistics. statistics display hardware internal fdp cdat slot slot-num Displays the CPU data channel status information. status display hardware internal fdp flow slot slot-num Displays statistics about received Layer 3 packets. statistic Displays information about the CPU hardware display hardware internal nae slot slot-num freein...

  • Page 16: Troubleshooting Pos Interfaces

    If an LOS or LOF error was generated, verify that the optical module on the two ends and  the optical fiber are working correctly. If the problem persists, contact H3C Support. Data link layer down Symptom The physical state of the POS interface is up, but the data link layer state is down.

  • Page 17: Related Commands

    Use the display hardware internal module pos interface-number reg 1 command in probe view to verify that the FPGA configuration is correct. If the problem persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting POS interfaces.

  • Page 18: Troubleshooting Sap Modules

    If the command displays packet information, the packets are sent to the CPU correctly. − If the command does not display packet information, packets are not sent to the CPU. Enter probe view and execute the bcm slot chip show/counter command to display statistics about packet loss and contact H3C Support.

  • Page 19: Packet Loss In Data Forwarding

    If the packets are discarded after being sent to the CPU, contact H3C Support. Execute the bcm slot chip l3/defip/show command in probe view to determine whether the routing entries are correct and whether the packets match the routing entries. If not, contact H3C Support If the problem persists, contact H3C Support.

  • Page 20: Troubleshooting Wan-Irf

    Troubleshooting WAN-IRF This section provides troubleshooting information for common WAN-IRF problems. In this section, WAN-IRF is referred to as IRF. IRF fabric setup failure Symptom Two routers cannot form an IRF fabric. Solution To resolve the problem: Execute the display device command on each device to verify that the devices are operating in IRF mode and have unique IRF member IDs: If the Chassis field is not available for a device, use the chassis convert mode irf ...

  • Page 21: Cross-Chassis Traffic Forwarding Failure

    In probe view, execute the display hardware internal wanirf topoinfo chassis chassis-number slot slot-number command to check the status of each slot that provides IRF physical interfaces. Make sure a minimum of one slot is active. If no slot is active, contact H3C Support to identify the cause.

  • Page 22: Cross-Chassis Packet Loss Problem

    In probe view, execute the display hardware internal wanirf portinfo chassis chassis-number slot slot-number command to check the IRF physical interface status and outgoing interface information. If any abnormalities occur, contact H3C Support to identify the cause. Execute the display cpu-usage command to check the CPU usage. Verify that the CPUs are not overwhelmed.

  • Page 23: Related Commands

    MPU and a slot that provides IRF physical interfaces. In probe view, execute the debug stack show globalvariable slot slot-number command, and collect and send the output information to H3C Support. (SR6602-X routers.) Use this command to display IRF packet information for the member ...
  • Page 24 Command Remarks chassis-number slot slot-number display hardware internal wanirf stm debugging Displays STM packet debugging information of chassis chassis-number slot slot-number { receive | IRF physical interfaces for a slot. send | all on | off } (SR6602-X routers.) Displays STM packet statistics on a member device.

  • Page 25: Troubleshooting Cards

    System is starting... Press Ctrl+D to access BASIC-BOOTWARE MENU... Press Ctrl+T to start memory test Booting Normal Extended BootWare The Extended BootWare is self-decompressing..Done. **************************************************************************** H3C SR66 BootWare, Version 2.05 **************************************************************************** Copyright (c) 2004-2016 Hangzhou H3C Technologies Co., Ltd.
  • Page 26 If the RAM initialization failure alert is not displayed, there might be CPU problems. Contact H3C Support for further troubleshooting. − If the RAM initialization failure alert is displayed, contact H3C Support to replace the memory module. If the information like the following appears, the memory self-test failed.
  • Page 27 If the following information is displayed, the Comware image files have been loaded and  decompressed successfully: **************************************************************************** H3C SR66 BootWare, Version 2.05 **************************************************************************** Copyright (c) 2004-2016 Hangzhou H3C Technologies Co., Ltd. Compiled Date : Jan 18 2016 CPU Type : P2020 CPU L1 Cache...
  • Page 28  and you must download the files to the storage medium again: **************************************************************************** H3C SR66 BootWare, Version 2.05 **************************************************************************** Copyright (c) 2004-2016 Hangzhou H3C Technologies Co., Ltd. Compiled Date : Jan 18 2016 CPU Type : P2020 CPU L1 Cache...

  • Page 29: Lpu Startup Failure

    Loading the main image files... Loading file cfa0:/boot.bin..................Done. <boot> If one of the following symptoms appears, contact H3C Support:  − The system stops at the "System image is starting..." message. − After displaying the "System image is starting..." message, the system does not enter the CLI but repeatedly reboots.
  • Page 30 If the State field displays Disable, the LPU might have been unmounted. Use the undo remove slot command to mount the LPU. If the LPU has been powered on, the basic BootWare segment might have been corrupted. Contact H3C Support. Reboot the device. Identify whether the Comware image files have been correctly loaded: If the following information is displayed repeatedly, the IPC channel is not available.

  • Page 31: Related Commands

    If the following information is displayed repeatedly, the Comware image files are not  correctly loaded. %Jul 17 14:01:48:947 2014 H3C DEV/3/LOAD_FAILED: -MDC=1; Board in slot 3 failed to load software images. %Jul 17 14:01:48:948 2014 H3C DEV/3/LOAD_FAILED: -MDC=1; Board in slot 3 failed to load software images.

  • Page 32: Transceiver Module Type Not Recognized

    Execute the display hardware internal module interface-type interface-number reg 0 command to view the CPLD. Determine whether a transmit or receive failure or a hardware failure has occurred. If the problem persists, contact H3C Support. Transceiver module type not recognized Symptom The system generates a message that reports unknown transceiver module type.

  • Page 33: Troubleshooting Ports

    Command Description display hardware internal module interface-name Displays configuration and operating information interface-number reg 6 about a transceiver module. display hardware internal transceiver register interface interface-name interface-number device Displays register values on a transceiver module. device-index address length length display transceiver alarm interface interface-name Displays alarm information...

  • Page 34: Failure To Forward Packets

    For interfaces on a FIP-240 or SAP-4EXP LPU, execute the display hardware internal  dpaa slot slot-number bman pool-info command in probe view to collect the hardware buffer information. Contact H3C Support. Failure to forward packets Symptom An Ethernet interface on an intermediate router cannot forward packets.

  • Page 35: Packet Dropping

    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 ports. Command...

  • Page 36: Troubleshooting Active/Standby Mpu Switchover

    Command Description display hardware internal dpaa slot slot-number Displays hardware buffer information for interfaces bman pool-info on a FIP-240 or SAP-4EXP LPU. display hardware internal himadp slot Displays statistics for interfaces on a HIM of a slot-number cnt FIP-240 LPU. display hardware internal ibd pkt-info slot Displays packet statistics transmitted between slot-number slot-number...

  • Page 37: Exceptional Active/Standby Mpu Switchover

    No action is required. Next time you want to use the reboot slot command to reboot the active MPU, make sure the standby MPU has started up. If a log message like the specified message is found, contact H3C Support.  Exceptional active/standby MPU switchover...

  • Page 38: Interface Information Not Displayed

    <02:06.00> pex8624 unit 1 port 6 <14:00.00> fpga for subslot 2 … … … … If the command output does not contain the pci device in subslot x message, contact H3C  Support. If the command output contains the message, go to step 3.

  • Page 39: Related Commands

    Replace the interface module. If the first line is not 0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff, contact H3C Support. If the problem persists, contact H3C Support.

This manual is also suitable for:

Sr6600-x series

Table of Contents