H3C S5830 Series Troubleshooting Manual
H3C S5830 Series Troubleshooting Manual

H3C S5830 Series Troubleshooting Manual

Hide thumbs Also See for S5830 Series:
Table of Contents

Advertisement

Quick Links

H3C S5830 Switch Series Troubleshooting
Guide
Copyright © 2014 Hangzhou 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 Hangzhou H3C Technologies Co., Ltd.
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 S5830 Series and is the answer not in the manual?

Questions and answers

Summary of Contents for H3C S5830 Series

  • Page 1 H3C S5830 Switch Series Troubleshooting Guide Copyright © 2014 Hangzhou 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 Hangzhou H3C Technologies Co., Ltd.
  • Page 2: Table Of Contents

    Contents General troubleshooting procedures ·························································································································· 1   Obtaining diagnostic information ··································································································································· 1   Obtaining other information ············································································································································ 2   Checklist for deployment ············································································································································· 2   Troubleshooting hardware ·········································································································································· 7   Unexpected switch reboot ················································································································································ 7   Symptom ···································································································································································· 7   Troubleshooting flowchart ·······································································································································...
  • Page 3 Symptom ································································································································································· 25   Troubleshooting flowchart ···································································································································· 25   Solution ··································································································································································· 25   Related commands ························································································································································· 26   Troubleshooting IRF ···················································································································································· 27   IRF fabric establishment failure ····································································································································· 27   Symptom ································································································································································· 27   Troubleshooting flowchart ···································································································································· 28   Solution ··································································································································································· 28  ...
  • Page 4: General Troubleshooting Procedures

    (Y=save, N=display)? [Y/N]: This prompt asks you whether to save diagnostic information into a .diag file in the flash memory. If the free space of the flash memory is larger than 10 MB, H3C recommends that you enter y to •...
  • Page 5: Obtaining Other Information

    If the flash memory has no more space during the saving process, the system prints the excess diagnostic information on the console. You can use FTP to download the diagnostic file to a PC and send the file to H3C Support. If you enter n at the prompt "save or display diagnostic information (Y=save, N=display)? [Y/N]:", •...
  • Page 6 □NOK referring to the power and □Not related system power consumption. For more information about □OK Examine the status of the LED description, see H3C all the LEDs on the □NOK S5830 Switch Series device. □Not related Installation Guide. □OK...
  • Page 7 □Not related frequently? value. Verify that the configurations on the two ends are consistent. Are the To connect an H3C device to □OK configurations on a device of another vendor, display current the local and peer H3C recommends that you set □NOK...
  • Page 8 STP on the ports edged-port enable is connected to the displayed. STP-incapable devices. To avoid communication Can the H3C between the H3C device device running □OK Verify that STP running MSTP/STP/RSTP and MSTP/STP/RSTP calculation on each the Cisco device running □NOK...
  • Page 9 Command or Item Sub-item Result Remarks method If fewer than five VRRP groups exist, set the advertisement timer to 3 seconds for all the Is the groups. advertisement □OK timer set to 3 If five or more VRRP groups VRRP seconds? Is the display vrrp □NOK...
  • Page 10: Troubleshooting Hardware

    The switch reboots unexpectedly when it is operating. Troubleshooting flowchart Figure 1 Troubleshooting unexpected switch reboot The switch reboots unexpectedly Can the CLI be accessed? Reload the system Is the system software Collect log messages software image image correct? Is the fault rectified? Contact H3C Support...
  • Page 11: Solution

    The system software image in the flash memory is automatically set to the current system software image during the BootWare loading process. If the problem persists, contact H3C Support. Operating power supply failure Symptom A trap is generated indicating that an operating power supply has failed.
  • Page 12: Newly-Installed Power Supply Failure

    Normal state in the new slot. If the power supply remains in Fault state, replace the power supply. If the problem persists, contact H3C Support. Newly-installed power supply failure Symptom A newly-installed power supply fails.
  • Page 13: Solution

    If there are cooling measures to maintain the switch operating temperature below 60°C (140°F), the switch can be used temporarily. If the problem persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting the hardware.
  • Page 14: Temperature Alarming

    Use the display fan command to verify that the fan tray is operating correctly. If the system displays "Fault," see H3C S5830 Switch Series Installation Guide to resolve the problem. Use the temperature-limit command to set the temperature alarm thresholds.
  • Page 15: Related Commands

    Related commands This section lists the commands that you might use for troubleshooting system management. Command Remarks Displays temperature information, including the current temperature display environment and the temperature alarm thresholds. display fan Displays the operating status of all fan trays on the switch. temperature-limit Sets temperature alarm thresholds.
  • Page 16: Troubleshooting Flowchart

    Resolved? operating correctly? Peer port Replace peer port Resolved? operating correctly? Contact H3C Support Solution To resolve the problem: Verify that the speed and duplex mode of the local port match the speed and duplex mode of the peer port:...
  • Page 17: 100/1000-Mbps Sfp Fiber Port Fails To Go Up

    Replace the local port with a new one to verify that the local port is operating correctly. Replace the peer port with a new one to verify that the peer port is operating correctly. If the problem persists, contact H3C Support. 100/1000-Mbps SFP fiber port fails to go up Symptom A 100/1000-Mbps SFP fiber port cannot go up.
  • Page 18: Troubleshooting Flowchart

    Replace transceiver Transceiver Resolved? module module correct? Fiber correct? Replace fiber Resolved? Local port Replace local port Resolved? operating correctly? Peer port Replace peer port Resolved? operating correctly? Contact H3C Support Solution To resolve the problem:...
  • Page 19 : H3C Ordering Name : SFP-GE-SX-MM850-A If the transceiver module is not operating correctly, replace it with a new H3C transceiver module that matches the fiber port. For more information about transceiver modules, see related installation guides. Replace the fiber with a new one to verify that the fiber is in good condition.
  • Page 20: 10-Gigabit Sfp+ Fiber Port Fails To Go Up

    10-Gigabit SFP+ fiber port fails to go up Symptom A 10-Gigabit SFP+ fiber port cannot go up.
  • Page 21: Troubleshooting Flowchart

    Speed/duplex Configure matching Resolved? match on transceiver speed/duplex module and port? Local/peer port Replace local/peer Resolved? operating correctly? port Transceiver Replace transceiver Resolved? module/cable correct? module/cable Fiber correct? Replace fiber Resolved? Contact H3C Support...
  • Page 22: Solution

    Digital Diagnostic Monitoring : YES Vendor Name : H3C Ordering Name : SFP-GE-SX-MM850-A If the transceiver module is not operating correctly, replace it with a new H3C transceiver module that matches the fiber port. For more information about transceiver modules, see related installation guides.
  • Page 23: Error Frames (For Example, Crc Errors) On A Port

    Verify that the fiber matches the transceiver module. If they do not match, replace the fiber with a new one that matches the transceiver module. If the problem persists, execute the display diagnostic-information command to save the diagnostic information, and contact H3C Support. <H3C> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y...
  • Page 24: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 6 Troubleshooting error frames (for example, CRC errors) on a port Solution To resolve the problem: Examine the error frame statistics and identify the error frame type: (Optional.) Use the reset counter interface command in user view to clear the packet statistics of the port.
  • Page 25 If the optical power of the transceiver module is not within the correct range, replace the transceiver module with a transceiver module of the same model that is operating correctly. [H3C] display transceiver diagnosis interface gigabitethernet1/0/1 GigabitEthernet1/0/1 transceiver diagnostic information: Current diagnostic parameters: Temp.(°C)
  • Page 26: Failure To Receive Packets

    Port and link Use normal port Resolved? medium normal? and link medium Contact H3C Support Solution To resolve the problem: Examine the packet statistics of the port: (Optional.) Use the reset counter interface command in user view to clear the packet statistics of the port.
  • Page 27 If a port is set to the discarding state by STP, examine and modify the STP-related configurations to resolve the problem. H3C recommends that you configure the port as an edge port or disable STP on the port if it is directly connected to a terminal.
  • Page 28: Failure To Send Packets

    Failure to send packets Symptom A port is up, but it cannot send packets. Troubleshooting flowchart Figure 8 Troubleshooting the failure to send packets Solution To resolve the problem: Examine the packet statistics of the port: (Optional.) Use the reset counter interface command in user view to clear the packet statistics of the port.
  • Page 29: Related Commands

    If a port is set to the discarding state by STP, examine and modify the STP-related configurations to resolve the problem. H3C recommends that you configure the port as an edge port or disable STP on the port if it is directly connected to a terminal.
  • Page 30: Troubleshooting Irf

    Command Description Displays the summary information for all display link-aggregation summary aggregation groups. display stp brief Displays brief spanning tree status and statistics. display transceiver alarm interface Displays the current transceiver module alarms. Displays the present measured values of the display transceiver diagnosis interface digital diagnosis parameters for transceiver modules.
  • Page 31: Troubleshooting Flowchart

    Upgrade software to the Same software version? Resolved? same version in the fabric Contact H3C Support Solution To resolve the problem: Execute the display irf command to verify that the number of member devices in the IRF fabric does not exceed the upper limit of four.
  • Page 32 For more information, see the release notes for the software versions. If the problem persists, contact H3C Support. Execute the display diagnostic-information command, save the diagnostic information, and provide it to H3C Support.
  • Page 33: Irf Split

    <H3C> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y IRF split Symptom An IRF fabric splits. Troubleshooting flowchart Figure 10 Troubleshooting IRF split Solution To resolve the problem: Verify that the IRF physical ports are operating correctly: Execute the display trapbuffer command or view system logs to check for physical IRF link down events that occurred close to the split time.
  • Page 34: Bfd Mad Failure

    If the problem persists, contact H3C Support. Execute the display diagnostic-information command, save the diagnostic information, and provide it to H3C Support. <H3C> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y BFD MAD failure Symptom BFD MAD fails to detect an IRF split event. Two IRF fabrics are operating with the same Layer 3...
  • Page 35: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 11 Troubleshooting the BFD MAD failure Solution To resolve the problem:...
  • Page 36 Verify that BFD MAD link connections are correct: If you do not use an intermediate device, verify that each pair of member devices has a dedicated BFD MAD link. If you use an intermediate device, verify that each member device has a dedicated BFD MAD link with the intermediate device.
  • Page 37: Lacp Mad Failure

    Execute the display trapbuffer command or use system logs to check for BFD MAD port down events that occurred around the split time. Identify the cause of the event, and remove the issue. If the problem persists, contact H3C Support. Execute the display diagnostic-information command, save the diagnostic information, and provide it to H3C Support.
  • Page 38: Troubleshooting Flowchart

    Solution To resolve the problem: Verify that the intermediate device is an H3C device that supports extended LACPDUs for MAD. If the intermediate device does not support extended LACPDUs for MAD, replace the intermediate device, or use BFD MAD for split detection.
  • Page 39: Related Commands

    Execute the display trapbuffer command or use system logs to check for port down events close to the split time. Identify the cause of the event and remove the issue. If the problem persists, contact H3C Support. Execute the display diagnostic-information command, save the diagnostic information, and provide it to H3C Support.
  • Page 40: Troubleshooting Qos And Acl

    Command Description display irf configuration Displays the IRF configuration on each member device. display irf topology Displays the IRF topology. display mad verbose Displays detailed MAD configuration. Displays the present measured values of the digital diagnosis display transceiver diagnosis parameters for transceiver modules. display trapbuffer Displays trap data in the trap buffer.
  • Page 41: Troubleshooting Flowchart

    If an ACL rule includes much more matching criteria than the other ACL rules, split it into multiple rules. Apply the adjusted ACL. If the problem persists, contact H3C Support. Execute the display diagnostic-information command, save the diagnostic information, and provide it to H3C Support.
  • Page 42: Troubleshooting Flowchart

    Execute the display acl resource command to display the ACL resource usage. In IRF mode, if the ACL is applied globally (for example, to a VLAN), identify the remaining ACL resources on all IRF devices. [H3C] display acl resource Interface: GE3/0/1 to GE3/0/24...
  • Page 43: Acl Application Failure Without An Error Message

    If the number of ACL rules to be applied is greater than the number of remaining ACL resources, delete unnecessary ACL rules. Apply the ACLs. If the problem persists, contact H3C Support. Execute the display diagnostic-information command, save the diagnostic information, and provide it to H3C Support.
  • Page 44: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 15 Troubleshooting an ACL application failure Solution To resolve the problem: Verify that overlapping ACL rules that have been applied exist. Use one of the following commands to display applied ACLs: − display qos policy user-defined display traffic classifier user-defined −...
  • Page 45: Packet Loss Or Forwarding Failure

    The behavior configured first. • filter deny If the problem persists, contact H3C Support. Execute the display diagnostic-information command, save the diagnostic information, and provide it to H3C Support. <H3C> display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y...
  • Page 46: Solution

    System View: return to User View with Ctrl+Z. [H3C] time-range t1 from 12:00 11/11/2013 to 12:01 11/11/2013 [H3C] acl number 3000 name geliACL [H3C-acl-adv-3000-geliACL] rule 0 permit ip destination 2.2.2.2 0 time-range t1 [H3C-acl-adv-3000-geliACL] quit [H3C] traffic classifier count [H3C-classifier-count] if-match acl 3000...
  • Page 47: Related Commands

    Behavior: count Accounting Enable: 251 (Packets) The output shows that a total of 251 packets match ACL 3000. On GigabitEthernet 2/0/1 on Device C: [H3C-GigabitEthernet2/0/1] display qos policy interface gigabitethernet 2/0/1 Interface: GigabitEthernet2/0/1 Direction: Inbound Direction: Inbound Policy: count Classifier: count...

Table of Contents