No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Troubleshooting Guide

CloudEngine 16800, 12800, 12800E, 8800, 7800, 6800, and 5800 Series Switches

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Troubleshooting Procedure

Troubleshooting Procedure

After commands are configured to troubleshoot faults, pay attention to the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to the two-phase validation mode.

  • In immediate validation mode, the configuration takes effect immediately after you run a command and press Enter.
  • In two-phase validation mode, you must run the commit command after commands are configured to commit the configuration.

Save the results of each troubleshooting step, so you can provide related information to Huawei technical support if your troubleshooting fails.

Procedure

  1. Check whether the switch restarts because of stack competition.

    Except in initial stack setup, stack competition often occurs because of a stack split and then a stack merge. When a stack split occurs, the alarm DAD_1.3.6.1.4.1.2011.5.25.246.1.1 hwDadConflictDetect indicating a stack split or the alarm STACKMNG_1.3.6.1.4.1.2011.5.25.183.1.22.24 hwStackMemberLeave indicating that a member switch leaves is often generated. You can run the display trapbuffer command to check the alarms.

    If the switch restarts because of a stack split and then a stack merge, check the reason for the stack split. A stack split is often caused by port failures. Check the stack split time and determine whether any port Down alarm occurred in this time period. If there is a port Down alarm, rectify the fault according to Interface Troubleshooting.

  2. Check whether the switch restarts because of software or hardware failures.

    • Run the display device board reset slot-id command in the diagnostic view to check the reason for the switch restart.

      <HUAWEI> system-view
      [~HUAWEI] diagnose
      [~HUAWEI-diagnose] display device board reset 4
      Board 4 reset information:
      -- 1. DATE:2013-10-28  TIME:16:11:34  BARCODE:NULL  RESET Num:1
      --    
      --    BootMode:NORMAL
      --    BootCode:0x060100ff

      The stack-related BootCode ranges from 0x80000020 to 0x80000038.

      Handle the problem using the solution provided for the specific cause in Table 18-1.

      Table 18-1 Card reset causes and troubleshooting instructions

      Cause

      Description

      Suggestion

      User operations

      Reset board from command.

      A user has reset the board using the command line interface or network management system.

      Check whether the board is manually reset using a command or powered off.

      Power off the board.

      Reset board from PIC command.

      Get pic offline message, and power off.

      Canbus request to power off the board.

      Power off board from command.

      Environment

      board cold reset(COLD Reset) The device is powered off. Check the power supply environment to ensure normal power supply for the device.

      System loading

      EPLD is upgrade, and reset board.

      The board resets after the EPLD is updated.

      This is a normal reset and no action is required.

      Board update by JTAG, and reset board.

      The board resets after it is upgraded through the JTAG channel.

      Board update mbus, and reset board.

      The board resets after the Mbus is updated.

      Software exceptions

      Board task exception occurs and reset lpu.

      The system detects a software exception.

      Collect logs, diagnostic information, and the output of the display reset-snapshot time (in diagnostic view) command, and contact technical support personnel.

      Board task deadloop occurs and reset lpu.

      The system detects a deadloop on the board.

      Collect logs, diagnostic information, and the output of the display reset-snapshot time (in diagnostic view) command, and contact technical support personnel.

      Board no enough Memory, and reset board.

      The memory is used up.

      1. Check whether the memory usage is high.

      2. Collect memory information, logs, and diagnostic information, and contact technical support personnel.

      Board Memory overload, and reset board.

      Component report failure. The component fails to report a failure. Run the display reportfailure number verbose slot slot-id command to check the failure reason, collect logs, diagnostic information, and the output of the display reset-snapshot time (in diagnostic view) command, and contact technical support personnel.

      LAN Switch parity/ecc error, and reset board.

      A soft error occurred on a chip.

      Collect logs, diagnostic information, and the output of the display reset-snapshot time (in diagnostic view) command, and contact technical support personnel.

      Device management

      The heartbeat lost and reset lpu.

      The MPU does not receive heartbeat messages from the board.

      Collect logs, diagnostic information, and the output of the display reset-snapshot time (in diagnostic view) command, and contact technical support personnel.

      Semls register failed, and reset board.

      The board fails to register after trying for a long time.

      Collect serial port information recorded during startup of the board and contact technical support personnel.

      Hardware components

      Board selftest error, and reset board.

      Self check of the board fails.

      Reinstall the board or install it into another slot, and then check whether the board can work normally. If the fault persists, the board is faulty. Contact technical support personnel.

    • Run the display device alarm hardware and display alarm active commands in any view to check whether hardware failures occur. If so, rectify the hardware failures.

  3. If the fault persists, collect trap, log, and configuration information, and contact technical support personnel.
Translation
Download
Updated: 2020-01-07

Document ID: EDOC1000060766

Views: 611755

Downloads: 2956

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next