H3C S12500G-AF Series Troubleshooting Manual
  1. Manuals
  2. Brands
  3. H3C Manuals
  4. Switch
  5. S12500G-AF Series
  6. Troubleshooting manual

H3C S12500G-AF Series Troubleshooting Manual

Hide thumbs Also See for S12500G-AF Series:
Table of Contents

Advertisement

Quick Links

Download this manual
H3C S12500G-AF Switch Series
Troubleshooting Guide
Software version: Release 7595
Document version: 6W100-20200930
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 S12500G-AF Series and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for H3C S12500G-AF Series

Summary of Contents for H3C S12500G-AF 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 ······························································································································ 9 Removing deployment errors ······································································· 10 Dealing with password loss ··········································································...
  • Page 3 100-GE QSFP28 fiber port fails to come up····································································································· 48 Symptom ·················································································································································· 48 Troubleshooting flowchart ························································································································ 48 Solution ···················································································································································· 48 Reporting non-H3C transceiver modules ········································································································· 49 Symptom ·················································································································································· 49 Troubleshooting flowchart ························································································································ 50 Solution ···················································································································································· 50 Failure to support digital diagnosis on a transceiver module ··········································································· 50 Symptom ··················································································································································...
  • Page 4 Solution ···················································································································································· 65 Related commands ·········································································································································· 66 Troubleshooting QoS and ACL ···································································· 68 ACL application failure for unsupported ACL rules ·························································································· 68 Symptom ·················································································································································· 68 Troubleshooting flowchart ························································································································ 68 Solution ···················································································································································· 68 ACL application failure for insufficient resources ····························································································· 68 Symptom ··················································································································································...

  • Page 5: Introduction

    Introduction This document provides information about troubleshooting common software and hardware issues with H3C S12500G-AF switches. General guidelines IMPORTANT: To prevent an issue 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

    # Save log messages to the log file on each non-default MDC. <Sysname> system-view [Sysname] switchto mdc mdc2 ****************************************************************************** * Copyright (c) 2004-2020 New H3C Technologies Co., Ltd. All rights reserved.* * Without the owner's prior written consent, * no decompiling or reverse-engineering shall be allowed. ****************************************************************************** <Sysname>...
  • Page 7 * Without the owner's prior written consent, * no decompiling or reverse-engineering shall be allowed. ****************************************************************************** <Sysname> logfile save The contents in the log file buffer have been saved to the file flash:/logfile/logfile1.log <Sysname> switchback On the default MDC, identify the log file on each MPU for each MDC: # Display the log file on the active MPU (in standalone mode) or global active MPU (in IRF mode) for the default MDC.

  • Page 8: Collecting Diagnostic Log Messages

    # Save diagnostic log messages to the diagnostic log file on each non-default MDC. <Sysname> system-view [Sysname] switchto mdc mdc2 ****************************************************************************** * Copyright (c) 2004-2020 New H3C Technologies Co., Ltd. All rights reserved.* * Without the owner's prior written consent, * no decompiling or reverse-engineering shall be allowed. ****************************************************************************** <Sysname>...

  • Page 9: Collecting Operating Statistics

    0 -rw- 161321 Apr 27 2020 16:16:00 diagfile1.log 3710740 KB total (2508852 KB free) # Display the diagnostic log file on each standby MPU for the default MDC: In standalone mode, display the diagnostic log file on the standby MPU. ...
  • Page 10 ===============display version=============== H3C Comware Software, Version 7.1.070, Release 7595 Copyright (c) 2004-2020 New H3C Technologies Co., Ltd. All rights reserved. H3C S12508G-AF uptime is 0 weeks, 1 day, 6 hours, 23 minutes Last reboot reason : USER reboot Boot image: flash:/S12500G-CMW710-BOOT-E7595.bin Boot image version: 7.1.070, Release 7595...
  • Page 11 CPLD 1 Version: CPLD 2 Version: CPLD 3 Version: CPLD 4 Version: PowChip Version: NONE PLL Version: None Release Version: H3C S12516G-AF-7595 Patch Version: None Reboot Cause: UserReboot MPU(S) 1: Uptime is 0 weeks,1 days,8 hours,41 minutes BOARD TYPE: LSXM2SUPT2...
  • Page 12 PowChip Version: NONE PLL Version: None PCIE 1 Version: PCIE 2 Version: PCIE 3 Version: PCIE 4 Version: Release Version: H3C S12516G-AF-7595 Patch Version: None Reboot Cause: UserReboot NPU 18: Uptime is 0 weeks,1 day,8 hours,51 minutes BOARD TYPE: LSXM1SFT16F2...

  • Page 13: Contacting Technical Support

    …… Contacting technical support If an issue persists after you perform 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 14: Removing Deployment Errors

    Removing deployment errors Use the deployment checklist in Table 2 to eliminate issues that might be introduced at the deployment stage. Select items that are suitable for your site. Table 2 Deployment checklist Question Command or method Result Remarks Environment and card hardware status □OK Is the switch temperature Make sure the temperature...
  • Page 15 Question Command or method Result Remarks configuration file specifies the file as the next-startup configuration file on each MPU. CPU and memory usage Execute display command cpu-usage repeatedly. Does usage If the CPU of a card □OK change rate of any cards sustains a usage level of □Not OK (MPUs and LPUs) exceed...
  • Page 16 Question Command or method Result Remarks the peer port. Fiber ports To connect an H3C device □OK to a device from another Do the ports at the two display vendor, set the same port □Not OK ends use the same port...
  • Page 17 Question Command or method Result Remarks tree feature on the ports. □OK device running As a best practice to avoid MSTP, STP, or RSTP, and interoperability issues, set □Not OK display stp working with Cisco up a Layer 3 connection to □Not related PVST+ device? the Cisco device.
  • Page 18 Question Command or method Result Remarks handshake interval as 3 seconds, 5 seconds, and 7 seconds for the groups, respectively. If the log contains ARP □OK conflict records, verify that □Not OK display logbuffer Are there ARP conflicts? the hosts in conflict are legitimate, and remove the □Not related conflicts.
  • Page 19 Question Command or method Result Remarks packets with TTL 0 or 1. If TTL exceeded packets are received, check for network route errors. CPU security Execute the debug rxtx softcar show command in probe view to view □OK packet rate limit Are there packet attacks information for cards.

  • Page 20: Dealing With Password Loss

    Dealing with password loss Dealing with console login password loss Use either of the following methods: • (Preferred.) Telnetting to the device to change the console login password • Using BootWare menus to change the console login password Telnetting to the device to change the console login password Before you Telnet to the device, make sure the following requirements are met: •...

  • Page 21: Using Bootware Menus To Change The Console Login Password

    Configure password authentication for console login and set the password. You can also configure a different login authentication mode. <Sysname> system-view [Sysname] line aux 1/1 [Sysname-line-aux1/1] authentication-mode password [Sysname-line-aux1/1] set authentication password simple abc123 [Sysname-line-aux1/1] return 5. Save the running configuration to use the configuration at the next reboot. <Sysname>...
  • Page 22 2. Power on the device. System is Starting... Press Ctrl+D Into xmodem mode Press Ctrl+T to start memory test Booting Normal Extend Bootware Press Ctrl+V to start heavy memory test **************************************************************************** MPU BootWare, Version 3.02 **************************************************************************** Compiled Date : Apr 28 2019 10:27:24 Basic BootWare : 0107 CPU Type...
  • Page 23 Enter your choice(0-8): 4. Enter 6 to skip console login authentication. Enter your choice(0-8): 6 Clear Image Password Success! The extended BootWare menu is displayed again: ==========================<EXTENDED-BOOTWARE MENU>========================== |<1> Boot System |<2> Enter Ethernet SubMenu |<3> File Control |<4> Restore to Factory Default Configuration |<5>...
  • Page 24 1. Connect a configuration terminal to the console port of the device. 2. Power on the device. System is Starting... Press Ctrl+D Into xmodem mode Press Ctrl+T to start memory test Booting Normal Extend Bootware Press Ctrl+V to start heavy memory test **************************************************************************** MPU BootWare, Version 3.02 ****************************************************************************...

  • Page 25: Dealing With Telnet Password Loss

    Ctrl+C: Display Copyright Enter your choice(0-8): 4. Enter 4 and press Y to delete the next-startup configuration files. Enter your choice(0-8): 4 Because the password recovery capability is disabled, this operation can cause the configuration files to be deleted, and the system will start up with factory defaults.
  • Page 26 Configure password authentication and a new password for VTY lines. You can also configure a different login authentication mode. <Sysname> system-view [Sysname] line vty 0 63 [Sysname-line-vty0-63] authentication-mode password [Sysname-line-vty0-63] set authentication password simple abc123 [Sysname-line-vty0-63] return Save the running configuration to enable the configuration to survive a reboot. <Sysname>...

  • Page 27: Troubleshooting Configuration Loss

    Troubleshooting configuration loss This section provides troubleshooting information for common configuration management problems. Startup configuration file failure Symptom The device starts up with factory defaults because both the main and backup startup configuration files are not available or do not exist. Solution CAUTION: Do not execute the save command before you complete the tasks in this section.

  • Page 28: Related Commands

    <Sysname> startup saved-configuration config.cfg Reboot the device. If the issue persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting configuration loss.

  • Page 29: Troubleshooting Hardware

    Troubleshooting hardware This section provides troubleshooting information for common hardware issues. NOTE: This section describes how to troubleshoot MPUs, service modules, power modules, and fan trays. To troubleshoot transceiver modules, ports, and temperature alarms, see "Troubleshooting system management" and "Troubleshooting ports."...

  • Page 30: Newly Installed Standby Mpu Boot Failure

    If the MPU is not installed securely, remove and reinstall the MPU.  If the MPU is installed securely, replace the MPU.  If the issue persists, contact H3C Support. Newly installed standby MPU boot failure Symptom An MPU designated as the standby MPU fails to boot after installation.

  • Page 31: Solution

    Verify that the standby MPU runs the same software version as the active MPU. If the two MPUs run different software versions, upgrade the software version of the standby MPU to make sure the two MPUs run the same software version. If the issue persists, contact H3C Support. Service module reboot failure Symptom A service module fails to reboot.

  • Page 32: Newly Installed Service Module Boot Failure

     Verify that the service module has loaded files. <Sysname> display logbuffer %May 3 13:27:17:086 2020 H3C DEVM/4/BOARD_LOADING: Board is loading file on Chassis 1 Slot 7. %May 3 13:27:17:647 2020 H3C DEVM/5/LOAD_FINISHED: Board has finished loading file on Chassis 1 Slot 7.

  • Page 33: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 4 Troubleshooting service module boot failure Newly installed service module boot failure System software Reload the system software Resolved? image correct? image System software image Upgrade the system software Resolved? supports the service module? image Another service module boots Replace the MPU Resolved? successfully in the slot?

  • Page 34: Operating Power Module Failure

    Execute the display logbuffer command to verify that the service module has loaded files. [Sysname]display logbuffer %May 3 13:27:17:086 2020 H3C DEVM/4/BOARD_LOADING: Board is loading file on Chassis 1 Slot 7. %May 3 13:27:17:647 2020 H3C DEVM/5/LOAD_FINISHED: Board has finished loading file on Chassis 1 Slot 7.

  • Page 35: Troubleshooting Flowchart

    Contact the support Solution To resolve the issue: Identify the operating state of the power module. Execute the display power command to view the operating state of the power module.  <H3C>display power Input Power: 2364.0 W PowerID State Mode Current(A)
  • Page 36 Install the power module into an empty power module slot. Then execute the display power command to verify that the power module has changed to Normal state in the new slot. If the power module remains in Faulty state, replace the power module. If the issue persists, contact H3C Support.

  • Page 37: Newly Installed Power Module Failure

    Contact the support Solution To resolve the issue: Identify the operating state of the power module. Execute the display power command to view the operating state of the power module.  <H3C>display power Input Power: 2364.0 W PowerID State Mode Current(A)

  • Page 38: Fan Tray Failure

    Remove and install the power module into an empty power module slot. Then execute the display power command to check the power module state. If the power module remains in Faulty state, go to step 4. If the issue persists, contact H3C Support. Fan tray failure Symptom...

  • Page 39: Troubleshooting Flowchart

    Fault state? Contact the support Solution To resolve the issue: Execute the display fan command to view the operating state of the fan tray. <H3C>display fan Fan Frame 1 State: Normal Fan Frame 2 State: Normal If the fan tray is in Absent state, go to step 2. If the fan tray is in Fault state, go to step 3.

  • Page 40: Related Commands

    If the issue persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting the hardware. Command Description debug sysm fan fan-id get-speed Displays fan speed information. Displays information about files and directories. display alarm Displays alarm information.

  • Page 41: Troubleshooting System Management

    Contact the support Solution To resolve the issue: Identify the job that has a high CPU usage. For example: [H3C-probe] display process cpu slot 1 CPU utilization in 5 secs: 2.4%; 1 min: 2.5%; 5 mins: 2.4% 5Sec 1Min 5Min Name 0.0%...
  • Page 42 5 minutes. Typically, the average CPU usage of a job is less than 5% Display the job's stack. Perform this step for a minimum of five times. In this example, the job uses the ID of 145. [H3C-probe] follow job 145 slot 1 Attaching to process 145 ([mIPC] ) Iteration 1 of 5...

  • Page 43: High Memory Usage On A Module

    High memory usage Display memory usage information Display memory call information Contact the support Solution IMPORTANT: As a best practice, do not reboot the device before you contact H3C Support. You might lose critical diagnostic information if you reboot the device.
  • Page 44 To resolve the issue: Execute the display system internal kernel memory pool command multiple times to display memory usage information. [Sysname-probe] display system internal kernel memory pool slot 1 Active Number Size Align Slab Pg/Slab ASlabs NSlabs Name 9126 9248 kmalloc-64 16328 kmalloc-16328...

  • Page 45: Temperature Alarms

    1 drv_qacl_sal_rsc_init+0xc8/0x210 [system] age=4651968 pid=128 cpus=0 ---- More ---- The first field of the output shows the number of objects. The remaining fields show the call information. Save the information displayed in the previous steps and contact H3C Support. Temperature alarms Symptom Temperature alarms occur.

  • Page 46: Troubleshooting Flowchart

    Check the device temperature. If the device temperature is higher than the high-temperature warning threshold, use the display fan command to verify that the fan tray is operating correctly. If the status field displays Fault, see H3C S12500G-AF Switch Series Installation Guide to resolve the issue.
  • Page 47 Command Remarks display cpu-usage Displays the current CPU usage statistics. Displays temperature information, including the display environment current temperature and the temperature alarm thresholds. Displays the operating status of all fans on the display fan device. display memory Displays memory usage statistics. Displays the CPU usage statistics for jobs.

  • Page 48: Troubleshooting Ports

    Troubleshooting ports This section provides troubleshooting information for common port problems. 10-Gigabit SFP+ fiber port fails to come up Symptom A 10-Gigabit SFP+ fiber port cannot come up.

  • Page 49: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 11 Troubleshooting link up failure on a port A 10-GE SFP+ fiber port fails to come up Speed/duplex match Configure matching Resolved? on local and peer port? speed/duplex Speed/duplex Configure matching match on transceiver module and Resolved? speed/duplex port? Local/peer port...

  • Page 50: 40-Ge Qsfp+ Fiber Port Fails To Come Up

    If the transceiver module is not operating correctly, replace it with a new H3C transceiver module that matches the fiber port.

  • Page 51: Troubleshooting Flowchart

    If the transceiver module is not operating correctly, replace it with a new H3C transceiver module that matches the fiber port.

  • Page 52: 100-Ge Qsfp28 Fiber Port Fails To Come Up

    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 issue persists, contact H3C Support. 100-GE QSFP28 fiber port fails to come up Symptom A 100-GE QSFP28 fiber port fails to come up.

  • Page 53: Reporting Non-H3C Transceiver Modules

    If the transceiver module or cable is not operating correctly, replace it with a new H3C transceiver module or cable that matches the fiber port. For more information about transceiver modules and cables, see the installation guide for the switch.

  • Page 54: Troubleshooting Flowchart

    If the Vendor Name field is H3C, the transceiver module might be an H3C transceiver module without an electrical label or a non-H3C transceiver module. b. If the Vendor Name field is not H3C, you can determine that this is not an H3C transceiver module. Replace it with an H3C transceiver module.

  • Page 55: Troubleshooting Flowchart

    Determine whether the value of the Vendor Name field is H3C. c. Use the display transceiver manuinfo interface command to collect the transceiver module information. Send the bar code of the transceiver module to H3C Support to verify that the vendor of the transceiver module is H3C.

  • Page 56: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 16 Troubleshooting error frames (for example, CRC errors) on a port Error frames on the port Determine the type of error frames accumulating Optical power Replace it with a transceiver of transceiver module with correct optical Resolved? module correct? power Speed and...
  • Page 57 Ten-GigabitEthernet1/0/1 transceiver diagnostic information: Current diagnostic parameters: [module] Temp.(°C) 1stTX 2ndTX 1stRX 2ndRX Voltage(V) 3.3VTX 12VTX 3.3VRX 12VRX 3.29 3.40 [channel] TX Bias(mA) RX power(dBm) TX power(dBm) 6.09 0.91 -0.77 5.95 1.09 -0.16 6.05 1.58 -0.17 5.85 1.58 -0.14 6.07 2.23 -0.30 5.72...

  • Page 58: Failure To Receive Packets

    Verify that the incoming traffic and outgoing traffic have not exceeded the maximum traffic processing capability of the local device and the peer device. If the issue persists, contact H3C Support. Failure to receive packets Symptom A port is up, but it cannot receive packets.

  • Page 59: Failure To Send Packets

    If the port is a copper port, directly connect the port to a PC. − If the port is a fiber port, replace the transceiver module plugged into the port. If the issue persists, contact H3C Support. Failure to send packets Symptom...

  • Page 60: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 18 Troubleshooting failure to send packets A port failed to send packets View packet statistics of the port Port Modify port configurations affect packet Resolved? configurations sending? Port and link Use correct port and Resolved? medium correct? link medium Contact the support Solution...

  • Page 61: Related Commands

    H3C recommends that you configure the port as an edge port or disable the spanning tree feature on the port if it is directly connected to a terminal. c. If the port is in an aggregation group, use the display link-aggregation summary command to verify that the status of the port is Selected.

  • Page 62: Troubleshooting Irf

    Troubleshooting IRF This section provides troubleshooting information for common IRF issues. IRF fabric setup failure Symptom A chassis cannot be added to an IRF fabric.

  • Page 63: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 19 Troubleshooting IRF fabric setup failure IRF setup failure You cannot add the chassis to Number of chassis in the fabric the IRF fabric fewer than the upper limit? Replace with a chassis that is Same chassis model? the same model as existing IRF Resolved? member chassis...

  • Page 64: Solution

    IRF fabric. If the member chassis upper limit is reached for the software version, you cannot add new chassis to the IRF fabric. For more information about the upper limit, see H3C S12500G-AF Switch Series Virtual Technologies Configuration Guide for the software version.

  • Page 65: Irf Split

    The switch might support different transceiver modules or DAC cables depending on the software version and interface module model. For more information, see the latest installation guide and the configuration guides of the H3C S12500G-AF switch series for the software version in use.

  • Page 66: Troubleshooting Flowchart

    "Service module reboot failure" to resolve the issue. If the issue persists, contact H3C Support. BFD MAD failure Symptom BFD MAD fails to detect an IRF split event. Two IRF fabrics are operating with the same Layer 3...

  • Page 67: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 21 Troubleshooting BFD MAD failure BFD MAD failure BFD MAD link Correct the connections Resolved? connections correct? All BFD MAD Resolved? Bring up the ports ports up? BFD MAD VLAN interface Correct the settings Resolved? configured correctly? BFD MAD VLAN and ports Correct the settings Resolved?
  • Page 68 Execute the display trapbuffer command or use system logs to check for BFD MAD port-down events that occurred around the split time. b. Identify the cause of the events, and remove the issue. If the issue persists, contact H3C Support.

  • Page 69: Lacp Mad Failure

    LACP MAD failure Symptom LACP MAD fails to detect an IRF split event. Two IRF fabrics are operating with the same Layer 3 settings, including the same IP address. Troubleshooting flowchart Figure 22 Troubleshooting LACP MAD failure LACP MAD failure Intermediate device Replace the device or use Resolved?

  • Page 70: Related Commands

    Execute the display trapbuffer command or use system logs to check for port-down events around the split time. b. Identify the event cause and remove the issue. If the issue persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting IRF:...
  • Page 71 Command Description 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 buffer information and buffered notifications. display version Displays system version information.

  • Page 72: Troubleshooting Qos And Acl

    Delete the unsupported rule and apply the packet filter or QoS policy again. If the rule is indispensable and cannot be deleted, go to step 2. If the issue persists, collect device information and contact H3C Support. ACL application failure for insufficient resources Symptom The system fails to apply a packet filter or an ACL-based QoS policy to the hardware.

  • Page 73: Troubleshooting Flowchart

    Warning: Classifier-behavior test in policy test applied on vlan 4079 failed in slot 2. Reason: Not enough hardware resource. Troubleshooting flowchart Figure 24 Troubleshooting ACL application failure Failure to apply an ACL Hardware resources Delete unnecessary ACLs Resolved? are sufficient? Collect information and contact the support Solution...

  • Page 74: Acl Application Failure Without An Error Message

    If the ACL resources are sufficient, the reason might be that the ACL conflicts with a specific algorithm in the ASIC chip. In this case, go to step 4. Apply the packet filter or QoS policy again. If the issue persists, collect device information and contact H3C Support. ACL application failure without an error message Symptom The system applies a packet filter or an ACL-based QoS policy to the hardware.

  • Page 75: Solution

    Revise ACLs, packet filters, or QoS policies to remove the behavior conflict. If the issue persists, collect device information and contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting QoS and ACLs.

  • Page 76: Troubleshooting Mdc

    Troubleshooting MDC This section provides troubleshooting information for common MDC problems. Service module assignment failure Symptom The location command fails to assign a service module to an MDC. Troubleshooting flowchart Figure 26 Troubleshooting service module assignment failure Service module assignment failure Resources sufficient? Re-assign resources Resolved?
  • Page 77 Assign the service module to the mdcB. [Sysname-mdc-2-mdcA] mdc mdcB [Sysname-mdc-3-mdcB] location chassis 1 slot 3 Verify that the service module belongs to mdcB. [Sysname-mdc-3-mdcB] display this mdc mdcB id 3 location chassis 1 slot 3 mdc start Return If the issue persists, contact H3C Support.

  • Page 78: Interface Assignment Failure

    Interface assignment failure Symptom Interfaces on a service module fail to be assigned to a non-default MDC, or the interfaces are not available in MDC view. Troubleshooting flowchart Figure 27 Troubleshooting interface assignment failure Interface assignment failure Display interfaces of MDCs Reclaim the service module and its...
  • Page 79 MDC mdcA's interface(s): M-GigabitEthernet1/0/0/0 Ten-GigabitEthernet1/3/0/1 Ten-GigabitEthernet1/3/0/2 Ten-GigabitEthernet1/3/0/3 Ten-GigabitEthernet1/3/0/4 Ten-GigabitEthernet1/3/0/5 Ten-GigabitEthernet1/3/0/6 Ten-GigabitEthernet1/3/0/7 Ten-GigabitEthernet1/3/0/8 Ten-GigabitEthernet1/3/0/9 Ten-GigabitEthernet1/3/0/10 Ten-GigabitEthernet1/3/0/11 Ten-GigabitEthernet1/3/0/12 Ten-GigabitEthernet1/3/0/13 Ten-GigabitEthernet1/3/0/14 Ten-GigabitEthernet1/3/0/15 Ten-GigabitEthernet1/3/0/16 Ten-GigabitEthernet1/3/0/17 Ten-GigabitEthernet1/3/0/18 Ten-GigabitEthernet1/3/0/19 Ten-GigabitEthernet1/3/0/20 Ten-GigabitEthernet1/3/0/21 Ten-GigabitEthernet1/3/0/22 Ten-GigabitEthernet1/3/0/23 Ten-GigabitEthernet1/3/0/24 Ten-GigabitEthernet1/3/0/25 Ten-GigabitEthernet1/3/0/26 Ten-GigabitEthernet1/3/0/27 Ten-GigabitEthernet1/3/0/28 Ten-GigabitEthernet1/3/0/29 Ten-GigabitEthernet1/3/0/30 Ten-GigabitEthernet1/3/0/31 Ten-GigabitEthernet1/3/0/32 Ten-GigabitEthernet1/3/0/33 Ten-GigabitEthernet1/3/0/34 Ten-GigabitEthernet1/3/0/35 Ten-GigabitEthernet1/3/0/36 Ten-GigabitEthernet1/3/0/37 Ten-GigabitEthernet1/3/0/38 Ten-GigabitEthernet1/3/0/39...
  • Page 80 Return Assign the service module in slot 3 on member device 1 and its interface to mdcB. [Sysname]mdc mdcB [Sysname-mdc-3-mdcB] allocate interface Ten-GigabitEthernet 1/3/0/1 to Ten-GigabitEthernet 1/3/0/48 Configuration of the interfaces will be lost. Continue? [Y/N] :y [Sysname-mdc-3-mdcB] quit [Sysname-mdc-3-mdcB] location chassis 1 slot 3 [Sysname-mdc-3-mdcB] display this mdc mdcB id 3 location chassis 1 slot 3...

  • Page 81: Related Commands

    Ten-GigabitEthernet1/3/0/44 Ten-GigabitEthernet1/3/0/45 Ten-GigabitEthernet1/3/0/46 Ten-GigabitEthernet1/3/0/47 Ten-GigabitEthernet1/3/0/48 If the issue persists, contact H3C Support. Related commands This section lists the commands that you might use for troubleshooting MDC. Command Description allocate interface Assigns physical interfaces to an MDC. Displays operating statistics for multiple feature modules in display diagnostic-information the system.

  • Page 82: Troubleshooting Drni

    Troubleshooting DRNI DR system setup failure Symptom Two DRNI devices configured cannot form a DR system. Troubleshooting flowchart Figure 28 Flowchart for troubleshooting DR system setup failure DR system setup failure Assign unique system numbers Do member devices use unique system Resolved? to member devices.

  • Page 83: Dr System Split

    b. If the DR member devices use different DR system MAC addresses, use the drni system-mac command to change the DR system MAC addresses of the DR member devices to the same value. Verify that the DR member devices use the same DR system priority: a.

  • Page 84: Troubleshooting Flowchart

    Troubleshooting flowchart Figure 29 Flowchart for troubleshooting DR system split DR system split Is the IPP operating correctly? Resolve the IPP problem Resolved? Locate the cause of the Has the card that hosts the IPP reboot and resolve the Resolved? rebooted? problem Have...

  • Page 85: Member Ports Of A Dr Interface Cannot Be Selected

    Member ports of a DR interface cannot be selected Solution Some or all member ports of a DR interface cannot be selected. Troubleshooting flowchart Figure 30 Flowchart for troubleshooting member port selection failure on a DR interface Member ports of a DR interface cannot be selected Are the member ports operating...

  • Page 86: Related Commands

    Related commands This section lists the commands that you might use for troubleshooting DRNI. Command Description Displays information about configuration display drni consistency consistency check done by DRNI. display drni system Displays the DR system settings. Displays detailed information about the IPP and DR display drni verbose interfaces.

Table of Contents