HP HSR6600 Troubleshooting Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Network Router
  5. FlexNetwork HSR6600
  6. Troubleshooting manual
HP HSR6600 Troubleshooting Manual

HP HSR6600 Troubleshooting Manual

Hide thumbs Also See for HSR6600:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Configuration Manual
HP HSR6600/HSR6800 Routers
Troubleshooting Guide (V7)
© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained
herein is subject to change without notice. The only warranties for HP products and services
are set forth in the express warranty statements accompanying such products and services.
Nothing herein should be construed as constituting an additional warranty. HP shall not be
liable for technical or editorial errors or omissions contained herein.
Part number: 5998-8650

Advertisement

Table of Contents
loading

Related Manuals for HP HSR6600

Summary of Contents for HP HSR6600

  • Page 1 Troubleshooting Guide (V7) © Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services.

  • 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 ································································································································· 4 Contacting technical support ··········································································································································· 5 Troubleshooting CPOS interfaces··································································································································· 6 CPOS interface and serial interface down ·····················································································································...
  • Page 3 Troubleshooting IRF ························································································································································ 17 IRF fabric setup failure ··················································································································································· 17 Symptom ································································································································································· 17 Solution ··································································································································································· 17 Cross-chassis traffic forwarding failure ························································································································ 18 Symptom ································································································································································· 18 Solution ··································································································································································· 18 Cross-chassis packet loss problem ······························································································································· 19 Symptom ································································································································································· 19 Solution ··································································································································································· 19 IRF split ············································································································································································...
  • Page 4 Troubleshooting subcards ············································································································································· 35 Interfaces not present ····················································································································································· 36 Symptom ································································································································································· 36 Solution ··································································································································································· 36 Subcard not present ······················································································································································· 36 Symptom ································································································································································· 36 Solution ··································································································································································· 36 Related commands ························································································································································· 37...

  • Page 5: Introduction

    Introduction This document provides information about troubleshooting common software and hardware problems with HP HSR6600/HSR6800 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 6: Collecting Common Log Messages

    Table 1 Log and operating information Category File name format Content Common log logfileX.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 7: Collecting Diagnostic Log Messages

    <Sysname> dir chassis2#slot0#cfa0:/logfile/ Directory of chassis2#slot0#cfa0:/logfile 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.

  • Page 8: Collecting Operating Statistics

    Network and management ports are faster than the console port. Do not execute commands while operating statistics are being collected. • HP 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 9: Contacting Technical Support

    GE4/0/10 …… Contacting technical support If you cannot resolve a problem after using the troubleshooting procedures in this document, contact HP Support. When you contact an authorized HP support representative, be prepared to provide the following information: Information described in "General...

  • Page 10: 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 HP Support: Execute the debugging physical packet command to enable packet debugging on both devices ...

  • Page 11: 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 HP 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 12: Related Commands

    Related commands This section lists the commands that you might use for troubleshooting CPOS interfaces. Command Description clock master Sets the clock mode of the CPOS interface to 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 section, and...

  • Page 13: Troubleshooting Fip-600 Lpu

    In probe view, execute the display hardware internal dpaa slot slot-num bman pool-info command to view statistics about hardware buffer pools. Contact HP Support if a buffer pool with a BPID in the range of 0 to 3 meets the following conditions:...

  • Page 14: Failure To Forward Traffic

    In probe view, execute the display hardware internal fdp flow slot slot-num statistic command to view statistics about the Layer 3 packets sent to the CPU. If packet error or loss occurs, contact HP Support for information about the causes.

  • Page 15: Packet Loss

    In probe view, execute the display hardware internal fdp cdat slot slot-num statistics 8 command to view the packet loss statistics of the CPU and the logic module. Contact HP Support to learn the causes for the packet loss. In probe view, execute the debugging hardware internal fdp cdat slot slot-num bypass interface command to enable bypass logic on the interface where the packets to be forwarded are received.

  • Page 16: Related Commands

    Related commands This section lists the commands that you might use for troubleshooting FIP-600 LPUs. Command Description debugging hardware internal fdp cdat slot slot-num Enables the bypass logic feature. bypass debugging hardware internal fdp cdat slot slot-num Enables packet debugging for the CPU data debug channel.

  • Page 17: Troubleshooting Pos Interfaces

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

  • Page 18: Related Commands

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

  • Page 19: Troubleshooting Sap Modules

    Check the transceiver module and fiber for damages and connection faults. Adjust the fiber connector or reconnect the fiber connector to the transceiver module. Verify that the transceiver module and the fiber are compatible. If the problem persists, contact HP Support. Failure to forward traffic Symptom A SAP module fails to forward traffic.

  • Page 20: Packet Loss In Data Forwarding

    <slot> <chip> show/counter command to display statistics about packet loss and contact HP Support. If the packets are discarded after being sent to the CPU, contact HP 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.

  • Page 21: Troubleshooting Irf

    Troubleshooting IRF This section provides troubleshooting information for common IRF problems. In this section, IRF is referred to as IRF. IRF fabric setup failure Symptom Two HSR6800 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 command to ...

  • Page 22: Cross-Chassis Traffic Forwarding Failure

    IRF physical interfaces. Make sure a minimum of one card is active. If no card is active, contact HP Support to identify the cause. In probe view, execute the display hardware internal wanirf portinfo chassis chassis-number slot slot-number command to collect the IRF physical interface status and outgoing interface information.

  • Page 23: 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 HP Support to identify the cause. Execute the display cpu-usage command to check the CPU usage of MPUs and interface cards.

  • Page 24: Related Commands

    In probe view, execute the debug stack show globalvariable slot slot-number command to display IRF packet information for the MPUs. Collect and send the information to HP Support. In probe view, execute the display hardware internal wanirf stm pkt-info chassis chassis-number slot slot-number command to verify that STM packets can be forwarded from the active MPU on a device to the active MPU on the other device.
  • Page 25 Command Remarks display hardware internal wanirf topoinfo chassis Displays IRF topology information for a card. chassis-number slot slot-number reset hardware internal wanirf ibd pkt-info chassis Clears IBD packet statistics for an IRF physical chassis-number slot slot-number interface-type interface. interface-number reset hardware internal wanirf ipc pkt-info chassis Clears IPC packet statistics for an IRF physical chassis-number slot slot-number interface-type interface.

  • Page 26: Troubleshooting Cards

    Check whether the fans are rotating. If the fans are rotating, the device has been powered on. (For routers except for HSR6600.) If the device is not the fans are not rotating, wait for a while and remove the MPU. Identify whether the temperature of the CPU cooler on the MPU is higher than the room temperature.
  • Page 27 − If the system still displays the memory self-test failure information, the memory channel − hardware circuits might have problems. Contact HP Support. If the following information appears, both the extended BootWare segment and backup  extended BootWare segment have problems. You must manually upgrade the extended BootWare segment.
  • Page 28 |<5> Boot Backup Extend BootWare |<0> Reboot ========================================================================== Enter your choice(0-5): If no information is displayed after "Booting Normal Extend BootWare... ", contact HP Support.  System start booting... Booting Normal Extend BootWare..Verify that the Comware image files have been correctly loaded.
  • Page 29 HP HSR6608 BootWare, Version 1.18 ************************************************************************** Copyright (c) 2010-2015 Hewlett-Packard Development Company, L.P. Compiled Date : Jan 11 2008 CPU Type : MPC8548E CPU L1 Cache : 32KB CPU Clock Speed : 1000MHz Memory Type : DDR2 SDRAM Memory Size...

  • Page 30: Lpu Startup Failure

    Loading the main image files... Loading file cfa0:/boot.bin..................Done. <boot> If one of the following symptoms appears, contact HP 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 −...
  • Page 31 Startup—The LPU has been powered on. − Wait—The LPU has not been powered on. − If the LPU has not been powered on, identify whether the available power is sufficient. [HP-probe]display hardware internal sysm power-management System Power Total : 650 watts System Power Used...

  • Page 32: Related Commands

    − If the new LPU can start up correctly but the original LPU cannot, the original LPU has problems. If the new LPU cannot start up correctly, the IPC channel of the slot has problems. Contact HP − Support. If the following information is displayed repeatedly, the Comware image files are not correctly ...

  • Page 33: Troubleshooting Transceiver Modules

    Verify that the fiber type is compatible with the transceiver module. View the CPLD to determine whether a transmit or receive failure or a hardware failure has occurred. If the problem persists, contact HP Support. Transceiver module type not recognized Symptom A message is output that reports unknown transceiver module type.

  • Page 34: Interface Or Transceiver Module Alarm

    Execute the display transceiver alarm interface command to determine whether an alarm was generated and whether the alarm is consistent with the output messages. If the problem persists, contact HP Support. Related commands This section lists the commands that you might use for troubleshooting the transceiver modules.

  • Page 35: Troubleshooting Ports

    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 HP Support.

  • Page 36: 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 HP Support. Packet dropping Symptom An Ethernet interface drops packets.

  • Page 37: Related Commands

    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 HP Support. Related commands This section lists the commands that you might use for troubleshooting ports. Command...

  • Page 38: Troubleshooting Active/Standby Mpu Switchover

    Command Description display hardware internal module interface-name Displays status information for an Ethernet interface. interface-number status display hardware internal module interface-name Displays configuration information for an Ethernet interface-number message interface. display hardware internal module interface-name Displays FPGA information for an Ethernet interface. interface-number reg 1 display hardware internal module interface-name Displays MAC information for an Ethernet interface.

  • Page 39: Exceptional Active/Standby Mpu Switchover

    If a log message like the specified message is found, contact HP Support.  Exceptional active/standby MPU switchover Symptom While the device is operating correctly, the active MPU reboots and the standby MPU becomes the new active MPU. Solution To resolve the problem: In probe view, use the display hardware internal util slot slot-num rbinfo 5 detail command to display reboot records.

  • Page 40: Interfaces Not Present

    <09:00.00> tsi384 linking subslot 2 <10:00.00> pci device in subslot 2 <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 HP  Support.

  • Page 41: Related Commands

    If the first line in the command output is 0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff, replace the subcard. If the first line is not 0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff, contact HP Support.

This manual is also suitable for:

Hsr6800

Table of Contents