H3C S7500E Switch Series Troubleshooting Guide-R7568-6W100

HomeSupportSwitchesH3C S7500E Switch SeriesDiagnose & MaintainTroubleshootingH3C S7500E Switch Series Troubleshooting Guide-R7568-6W100
Download Book

 

H3C S7500E Switch Series Troubleshooting Guide

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

H3C_彩色.emf

 


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 7

Dealing with password loss· 7

Dealing with console login password loss· 7

Telnetting to the device to change the console login password· 7

Using BootWare menus to change the console login password· 8

Dealing with Telnet password loss· 13

Troubleshooting configuration loss· 14

Startup configuration file failure· 14

Symptom·· 14

Solution· 14

Related commands· 15

Troubleshooting hardware· 15

Configuration terminal display failure· 15

No display on the configuration terminal 15

Garbled display on the configuration terminal 16

MPU reboot failure· 16

Symptom·· 16

Troubleshooting flowchart 17

Solution· 17

MPU boot failure· 18

Symptom·· 18

Troubleshooting flowchart 18

Solution· 19

Service module reboot failure· 19

Symptom·· 19

Troubleshooting flowchart 20

Solution· 20

Service module boot failure· 21

Symptom·· 21

Troubleshooting flowchart 22

Solution· 22

Unexpected card reboot 23

Symptom·· 23

Solution· 23

Operating power module failure· 24

Symptom·· 24

Troubleshooting flowchart 24

Solution· 25

Newly installed power module failure· 25

Symptom·· 25

Troubleshooting flowchart 26

Solution· 26

External PoE power supply failure· 27

Symptom·· 27

Troubleshooting flowchart 27

Solution· 27

Fan tray failure· 28

Symptom·· 28

Troubleshooting flowchart 28

Solution· 28

Related commands· 29

Troubleshooting system management 29

High CPU usage· 30

Symptom·· 30

Troubleshooting flowchart 30

Solution· 31

High memory usage· 33

Symptom·· 33

Troubleshooting flowchart 34

Solution· 34

Temperature alarms· 36

Symptom·· 36

Troubleshooting flowchart 36

Solution· 36

Related commands· 37

Troubleshooting ports· 37

10/100/1000Base-T copper port fails to come up· 37

Symptom·· 37

Troubleshooting flowchart 38

Solution· 38

1000-Mbps SFP fiber port fails to come up· 39

Symptom·· 39

Troubleshooting flowchart 39

Solution· 39

10-Gigabit SFP+/XFP fiber port fails to come up· 42

Symptom·· 42

Troubleshooting flowchart 42

Solution· 42

40-GE QSFP+/CFP fiber port fails to come up· 43

Symptom·· 43

Troubleshooting flowchart 44

Solution· 44

A port goes down· 45

Symptom·· 45

Solution· 45

Port state flapping· 45

Symptom·· 45

Solution· 45

Transceiver module failure· 46

Symptom·· 46

Solution· 46

Reporting non-H3C transceiver modules· 48

Symptom·· 48

Troubleshooting flowchart 49

Solution· 49

Failure to support digital diagnosis on a transceiver module· 49

Symptom·· 49

Troubleshooting flowchart 50

Solution· 50

Error frames (for example, CRC errors) on a port 50

Symptom·· 50

Troubleshooting flowchart 52

Solution· 52

Failure to receive or send packets· 54

Symptom·· 54

Troubleshooting flowchart 55

Solution· 55

Related commands· 56

Troubleshooting IRF· 56

IRF fabric setup failure· 57

Symptom·· 57

Troubleshooting flowchart 58

Solution· 59

IRF split 61

Symptom·· 61

Troubleshooting flowchart 61

Solution· 61

BFD MAD failure· 62

Symptom·· 62

Troubleshooting flowchart 63

Solution· 63

LACP MAD failure· 65

Symptom·· 65

Troubleshooting flowchart 65

Solution· 65

Related commands· 66

Troubleshooting EPON· 67

Incompatibility with an optical transceiver module· 67

Symptom·· 67

Solution· 67

Down OLT port 67

Symptom·· 67

Solution· 67

High or low receiving power on an OLT port 68

Symptom·· 68

Solution· 68

Down ONU port 69

Symptom·· 69

Troubleshooting flowchart 69

Solution· 69

User network access failure· 70

Symptom·· 70

Solution· 70

Related commands· 70

Troubleshooting QoS and ACL· 70

ACL application failure for unsupported ACL rules· 71

Symptom·· 71

Troubleshooting flowchart 71

Solution· 71

ACL application failure for insufficient resources· 71

Symptom·· 71

Troubleshooting flowchart 72

Solution· 72

ACL application failure without an error message· 73

Symptom·· 73

Troubleshooting flowchart 73

Solution· 73

Related commands· 74

Troubleshooting MDC· 74

License problems· 75

Symptom·· 75

Troubleshooting flowchart 75

Solution· 75

Service module assignment failure· 76

Symptom·· 76

Troubleshooting flowchart 76

Solution· 76

Interface assignment failure· 78

Symptom·· 78

Troubleshooting flowchart 79

Solution· 79

Related commands· 81

 


Introduction

This document provides information about troubleshooting common software and hardware problems with H3C S7500E switches.

This document applies to Release S7500E-CMW710-R7568.

General guidelines

IMPORTANT

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.

 

When you troubleshoot the switch, follow these general guidelines:

·     To help identify the cause of the problem, collect system and configuration information, including:

?     Symptom, time of failure, and configuration.

?     Network topology information, including the network diagram, port connections, and points of failure.

?     Log messages and diagnostic information. For more information about collecting this information, see "Collecting log and operating information."

?     Physical evidence of failure:

-     Photos of the hardware.

-     Status of the card, power, and fan status LEDs.

?     Steps you have taken, such as reconfiguration, cable swapping, and reboot.

?     Output from the commands executed during the troubleshooting process.

·     To ensure safety, wear an ESD wrist strap when you replace or maintain a hardware component.

·     If hardware replacement is required, use the release notes to verify the hardware and software compatibility.

Collecting log and operating information

IMPORTANT

IMPORTANT:

By default, the information center is enabled. If the feature is disabled, you must use the info-center enable command to enable the feature for collecting log messages.

 

Table 1 shows the types of files that the system uses to store operating log and status information. You can export these files by using FTP, TFTP, or USB.

These files are stored on the active MPU (in standalone mode) or global active MPU (in IRF mode). Multiple MPUs will have log files if active/standby or master/subordinate switchovers have occurred. You must collect log files from all these MPUs. To more easily locate log information, use a consistent rule to categorize and name files. For example, save log information files to a separate folder for each MPU, and include their chassis and slot numbers in the folder names.

Table 1 Log and operating information

Category

File name format

Content

Common log

logfile.log

Command execution and operational log messages.

Diagnostic log

diagfile.log

Diagnostic log messages about device operation, including the following items:

·     Parameter settings in effect when an error occurs.

·     Information about a card startup error.

·     Handshaking information between the MPU and interface module when a communication error occurs.

Operating statistics

file-basename.gz

Current operating statistics for feature modules, including the following items:

·     Device status.

·     CPU status.

·     Memory status.

·     Configuration status.

·     Software entries.

·     Hardware entries.

 

Collecting common log messages

1.     Save common log messages from the log buffer to a log file:

By default, the log file is saved in the logfile directory of the flash memory on the active MPU (in standalone mode) or global active MPU (in IRF mode).

# Save log messages to the log file on the default MDC (Admin).

<Sysname> logfile save

The contents in the log file buffer have been saved to the file flash:/logfile/logfile.log

# Identify non-default MDCs created on the device.

<Sysname> display mdc

ID         Name            Status

---------------------------------

1          Admin           active

2          mdc2            active

3          mdc3            active

# Save log messages to the log file on each non-default MDC.

<Sysname> system-view

[Sysname] switchto mdc mdc2

******************************************************************************

* Copyright (c) 2010-2017 New H3C Technologies Co., Ltd. All rights reserved.*

* Without the owner's prior written consent,                                 *

* no decompiling or reverse-engineering shall be allowed.                    *

******************************************************************************

<H3C> logfile save

The contents in the log file buffer have been saved to the file flash:/logfile/logfile.log

<H3C> switchback

[Sysname] switchto mdc mdc3

******************************************************************************

* Copyright (c) 2010-2017 New H3C Technologies Co., Ltd. All rights reserved.*

* Without the owner's prior written consent,                                 *

* no decompiling or reverse-engineering shall be allowed.                    *

******************************************************************************

 

<H3C> logfile save

The contents in the log file buffer have been saved to the file flash:/logfile/logfile.log

<H3C> switchback

2.     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.

<Sysname> dir flash:/logfile/

Directory of flash:/logfile

   0 -rw-      213339 Nov 10 2016 14:18:54   logfile.log

 

503808 KB total (173812 KB free)

# Display the log file on each standby MPU for the default MDC:

?     In standalone mode, display the log file on the standby MPU.

<Sysname> dir slot1#flash:/logfile/

Directory of slot1#flash:/logfile

   0 -rw-       21863 Jul 11 2013 16:00:37   logfile.log

 

1021104 KB total (421552 KB free)

?     In IRF mode, display the log file on each standby MPU.

<Sysname> dir chassis2#slot0#flash:/logfile/

Directory of chassis2#slot0#flash:/logfile

   0 -rw-       21863 Jul 11 2013 16:00:37   logfile.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.

 

# Display the log file on each MPU for each non-default MDC.

<Sysname> dir flash:/mdc/

Directory of flash:/mdc

   0 drw-           - Jul 10 2013 14:56:50   mdc2

   1 drw-           - Jul 10 2013 16:48:04   mdc3

<Sysname> dir flash:/mdc/mdc2/logfile/

Directory of flash:/mdc/mdc2/logfile

   0 -rw-         465 Jul 11 2013 16:08:51   logfile.log

 

1021104 KB total (421476 KB free)

<Sysname> dir flash:/mdc/mdc3/logfile/

Directory of flash:/mdc/mdc3/logfile

   0 -rw-         465 Jul 11 2013 16:10:39   logfile.log

 

1021104 KB total (421476 KB free)

3.     Transfer the files to the desired destination by using FTP, TFTP, or USB. (Details not shown.)

Collecting diagnostic log messages

1.     Save diagnostic log messages from the diagnostic log file buffer to a diagnostic log file:

By default, the diagnostic log file is saved in the diagfile directory of the flash memory on each MPU.

# Save diagnostic log messages to the diagnostic log file on the default MDC (Admin).

<Sysname> diagnostic-logfile save

The contents in the diagnostic log file buffer have been saved to the file flash:/diagfile/diagfile.log

# Identify non-default MDCs created on the device.

<Sysname> display mdc

ID         Name            Status

---------------------------------

1          Admin           active

2          mdc2            active

3          mdc3            active

# Save diagnostic log messages to the diagnostic log file on each non-default MDC.

<Sysname> system-view

[Sysname] switchto mdc mdc2

******************************************************************************

* Copyright (c) 2010-2017 New H3C Technologies Co., Ltd. All rights reserved.*

* Without the owner's prior written consent,                                 *

* no decompiling or reverse-engineering shall be allowed.                    *

******************************************************************************

<H3C> diagnostic-logfile save

The contents in the diagnostic log file buffer have been saved to the file flash:/diagfile/diagfile.log

<H3C> switchback

[Sysname] switchto mdc mdc3

******************************************************************************

* Copyright (c) 2010-2017 New H3C Technologies Co., Ltd. All rights reserved.*

* Without the owner's prior written consent,                                 *

* no decompiling or reverse-engineering shall be allowed.                    *

******************************************************************************

<H3C> diagnostic-logfile save

The contents in the diagnostic log file buffer have been saved to the file flash :/diagfile/diagfile.log

<H3C> switchback

2.     On the default MDC, identify the diagnostic log file on each MPU for each MDC:

# Display the diagnostic log file on the active MPU (in standalone mode) or global active MPU (in IRF mode) for the default MDC.

<Sysname> dir flash:/diagfile/

Directory of flash:/diagfile

   0 -rw-      161321 Jul 11 2013 16:16:00   diagfile.log

 

1021104 KB total (421416 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.

<Sysname> dir slot1#flash:/diagfile/

Directory of slot1#flash:/diagfile

   0 -rw-      161321 Jul 11 2013 16:16:00   diagfile.log

 

1021104 KB total (421416 KB free)

?     In IRF mode, display the diagnostic log file on each standby MPU.

<Sysname> dir chassis2#slot0#flash:/diagfile/

Directory of chassis2#slot0#flash:/diagfile

   0 -rw-      161321 Jul 11 2013 16:16:00   diagfile.log

 

1021104 KB total (421416 KB free)

 

 

NOTE:

If a subordinate chassis has two MPUs, make sure you identify and export the diagnostic log files on both MPUs.

 

# Display the diagnostic log file on each MPU for each non-default MDC.

<Sysname> dir flash:/mdc/

Directory of flash:/mdc

   0 drw-           - Jul 10 2013 14:56:50   mdc2

   1 drw-           - Jul 10 2013 16:48:04   mdc3

<Sysname>dir flash:/diagfile/

Directory of flash:/diagfile

   0 -rw-         349 Jul 11 2013 16:21:38   diagfile.log

 

1021104 KB total (421352 KB free)

 

<Sysname> dir flash:/diagfile/

Directory of flash:/diagfile

   0 -rw-         349 Jul 11 2013 16:24:41   diagfile.log

 

1021104 KB total (421308 KB free)

3.     Transfer the files to the desired destination by using FTP, TFTP, or USB. (Details not shown.)

Collecting operating statistics

You can collect operating statistics by saving the statistics to a file or displaying the statistics on the screen.

When you collect operating statistics, follow these guidelines:

·     Log in to the device through a network port or management port instead of the console port, if possible. Network and management ports are faster than the console port.

·     Do not execute commands while operating statistics are being collected.

·     As a best practice, save operating statistics to a file to retain the information.

To collect operating statistics:

1.     Disable pausing between screens of output if you want to display operating statistics on the screen. Skip this step if you are saving statistics to a file.

<Sysname> screen-length disable

2.     Collect operating statistics for multiple feature modules.

<Sysname> display diagnostic-information

Save or display diagnostic information (Y=save, N=display)? [Y/N] :

3.     At the prompt, choose to save or display operating statistics:

# To save operating statistics, enter y at the prompt and then specify the destination file path.

Save or display diagnostic information (Y=save, N=display)? [Y/N] : Y

Please input the file name(*.tar.gz)[flash:/diag_S7500E_20161110-142231.tar.gz]:

flash:/diag.tar.gz

Diagnostic information is outputting to flash:/diag.tar.gz.

Please wait...

Save successfully.

<Sysname> dir flash:/

Directory of flash:

……

   6 -rw-      898180 Jun 26 2013 09:23:51   diag.tar.gz

 

1021808 KB total (259072 KB free)

# To display operating statistics on the monitor terminal, enter n at the prompt.

Save or display diagnostic information (Y=save, N=display)? [Y/N] :n

===============================================

  ===============display clock===============

10:28:57 UTC Mon 11/06/2016

=================================================

  ===============display version===============

H3C Comware Software, Version 7.1.070, Release R7568

Copyright (c) 2010-2017 New H3C Technologies Co., Ltd. All rights reserved.

H3C S7503E uptime is 0 weeks, 0 days, 1 hour, 38 minutes

Last reboot reason : Cold reboot

 

Boot image: flash:/S7500E-CMW710-SYSTEM-R7568.bin

Boot image version: 7.1.070P22, Release R7568

  Compiled Jul 15 2016 12:24:56

System image: flash:/S7500E-CMW710-SYSTEM-R7568.bin

System image version: 7.1.070, Release R7568

  Compiled Jul 15 2016 12:25:17

 

 

MPU(M) Chassis 2 Slot 1:

Uptime is 0 weeks,0 days,1 hour,38 minutes

BOARD TYPE:         LSQM2MPUD0

DRAM:               4096M bytes

FLASH:              1024M bytes

NVRAM:              1M bytes

PCB 1 Version:      VER.A

Bootrom Version:    110

CPLD 1 Version:     001

CPLD 2 Version:     001

CPLD 3 Version:     001A

Release Version:    H3C S7503E-R7568

Patch Version  :    None

Reboot Cause  :     ColdReboot

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 guidelines."

·     Product serial numbers.

·     Technical support registration numbers (if applicable).

This information will help the support engineer assist you as quickly as possible.

The following is the contact information for H3C Support:

·     Telephone number400-810-0504.

·     E-mail—service@h3c.com.

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:

·     You can log in to the device by using Telnet.

·     After login, you are assigned the user role network-admin or level-15.

To Telnet to the device to change the console login password:

1.     Telnet to the device. (Details not shown.)

2.     Determine the user line you are using.

<Sysname> display users

  Idx  Line    Idle       Time              Pid     Type

  1    AUX 1/1 00:00:36   Oct 08 16:35:09   543

+ 16   VTY 0   00:00:00   Oct 08 17:02:03   566     TEL

 

Following are more details.

VTY 0   :

        Location: 192.168.29.1

 +    : Current operation user.

 F    : Current operation user works in async mode.

The output shows that two users are online. You are using VTY 0. Your IP address is 192.168.29.1. The other user is using AUX 1/1.

3.     Display the user roles assigned to the user line you are using.

[Sysname] line vty 0

[Sysname-line-vty0] display this

#

line aux 1/1

 user-role network-operator

#

line vty 0

 authentication-mode none

 user-role level-15

 user-role network-admin

 user-role network-operator

#

return

The output shows that VTY 0 has the user role level-15. You have the right to change the console login password.

4.     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 12345678

[Sysname-line-aux1/1] return

5.     Save the running configuration to use the configuration at the next reboot.

<Sysname> save

The current configuration will be written to the device. Are you sure? [Y/N] :y

Please input the file name(*.cfg)[flash:/default.cfg]

(To leave the existing filename unchanged, press the enter key):default.cfg

Validating file. Please wait....

Saved the current configuration to mainboard device successfully.

Using BootWare menus to change the console login password

CAUTION

CAUTION:

·     Use this method only if you cannot access the CLI. A reboot is required to access BootWare menus.

·     Do not power off the device while you are using this method.

 

The procedure for using BootWare menus to change the console login password depends on whether password recovery capability is enabled:

·     If password recovery capability is enabled, you can use the Skip Authentication for Console Login option to skip console login authentication and configure a new password.

·     If password recovery capability is disabled, you can use the Restore to Factory Default Configuration option to restore the factory-default configuration and configure a new password.

To determine whether password recovery capability is enabled, use either of the following methods:

·     Telnet to the device and display the running configuration. If the password-recovery enable command is configured, password recovery capability is enabled.

<Sysname> display current-configuration

#

 version 7.1.070, Release 7568

#

mdc Admin id 1

#

 sysname Sysname

#

 command-alias enable

 command-alias mapping undo no

 command-alias mapping quit exit

 command-alias mapping return end

#

 password-recovery enable

#

·     View the bootstrap information displayed when you access the extended BootWare menu. If the message "Password recovery capability is enabled." is displayed, password recovery capability is enabled.

Changing the console login password when password recovery capability is enabled

1.     Connect a configuration terminal to the console port of the device.

2.     Power on the device.

RAM test successful.

Press Ctrl+T to start five-step full RAM test...

Press Ctrl+Y to start nine-step full RAM test...

System is starting...

Press Ctrl+D to access BASIC-BOOTWARE MENU...

Booting Normal Extended BootWare

The Extended BootWare is self-decompressing....Done.

 

****************************************************************************

*                                                                          *

*                         BootWare, Version 1.08                           *

*                                                                          *

****************************************************************************

Compiled Date         : Jul 15 2016

CPU Type              : XLP208

CPU Clock Speed       : 1000MHz

Memory Type           : DDR3 SDRAM

Memory Size           : 8192MB

Memory Speed          : 667MHz

BootWare Size         : 1536KB

Flash Size            : 4MB

BASIC CPLD Version    : 001

EXTENDED CPLD Version : 001

PCB Version           : Ver.A

 

 

BootWare Validating...

Press Ctrl+B to access EXTENDED-BOOTWARE MENU...

3.     Press Ctrl + B within three seconds after the "Press Ctrl+B to access EXTENDED-BOOTWARE MENU..." prompt message appears.

The extended BootWare menu is displayed:

Password recovery capability is enabled.

Note: The current operating device is flash

Enter < Storage Device Operation > to select device.

 

==========================<EXTENDED-BOOTWARE MENU>==========================

|<1> Boot System                                                           |

|<2> Enter Serial SubMenu                                                  |

|<3> Enter Ethernet SubMenu                                                |

|<4> File Control                                                          |

|<5> Restore to Factory Default Configuration                              |

|<6> Skip Current System Configuration                                     |

|<7> BootWare Operation Menu                                               |

|<8> Skip Authentication for Console Login                                 |

|<9> Storage Device Operation                                              |

|<0> Reboot                                                                |

============================================================================

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format File System

Enter your choice(0-9): 8

Clear Image Password Success!

4.     Enter 8 to skip console login authentication.

Enter your choice(0-9): 8

Clear Image Password Success!

The extended BootWare menu is displayed again:

==========================<EXTENDED-BOOTWARE MENU>==========================

|<1> Boot System                                                           |

|<2> Enter Serial SubMenu                                                  |

|<3> Enter Ethernet SubMenu                                                |

|<4> File Control                                                          |

|<5> Restore to Factory Default Configuration                              |

|<6> Skip Current System Configuration                                     |

|<7> BootWare Operation Menu                                               |

|<8> Skip Authentication for Console Login                                 |

|<9> Storage Device Operation                                              |

|<0> Reboot                                                                |

============================================================================

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format File System

Enter your choice(0-9):

5.     Enter 0 to reboot the device. The device will ignore the console login password to access the CLI and load the next-startup configuration file.

Enter your choice(0-9): 0

DDR2 SDRAM test successful.

System is starting...

Booting Normal Extend BootWare

The Extend BootWare is self-decompressing.................................

Done.

6.     After the device starts up, configure a new console login 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 12345678

[Sysname-line-aux1/1] return

7.     Save the running configuration to use the configuration at the next reboot.

<Sysname> save

The current configuration will be written to the device. Are you sure? [Y/N] :y

Please input the file name(*.cfg)[flash:/default.cfg]

(To leave the existing filename unchanged, press the enter key):default.cfg

Validating file. Please wait....

Saved the current configuration to mainboard device successfully.

Changing the console login password when password recovery capability is disabled

IMPORTANT

IMPORTANT:

Restoring the factory-default configuration deletes the next-startup configuration files.

 

To change the console login password when password recovery capability is disabled:

1.     Connect a configuration terminal to the console port of the device.

2.     Power on the device.

RAM test successful.

Press Ctrl+T to start five-step full RAM test...

Press Ctrl+Y to start nine-step full RAM test...

System is starting...

Press Ctrl+D to access BASIC-BOOTWARE MENU...

Booting Normal Extended BootWare

The Extended BootWare is self-decompressing....Done.

 

****************************************************************************

*                                                                          *

*                         BootWare, Version 1.08                           *

*                                                                          *

****************************************************************************

Compiled Date         : Jul 15 2016

CPU Type              : XLP208

CPU Clock Speed       : 1000MHz

Memory Type           : DDR3 SDRAM

Memory Size           : 8192MB

Memory Speed          : 667MHz

BootWare Size         : 1536KB

Flash Size            : 4MB

BASIC CPLD Version    : 001

EXTENDED CPLD Version : 001

PCB Version           : Ver.A

 

 

BootWare Validating...

Press Ctrl+B to access EXTENDED-BOOTWARE MENU...

3.     Press Ctrl + B within three seconds after the "Press Ctrl+B to access EXTENDED-BOOTWARE MENU..." prompt message appears.

The extended BootWare menu is displayed:

Password recovery capability is disabled.

Note: The current operating device is flash

Enter < Storage Device Operation > to select device.

 

==========================<EXTENDED-BOOTWARE MENU>==========================

|<1> Boot System                                                           |

|<2> Enter Serial SubMenu                                                  |

|<3> Enter Ethernet SubMenu                                                |

|<4> File Control                                                          |

|<5> Restore to Factory Default Configuration                              |

|<6> Skip Current System Configuration                                     |

|<7> BootWare Operation Menu                                               |

|<8> Skip Authentication for Console Login                                 |

|<9> Storage Device Operation                                              |

|<0> Reboot                                                                |

============================================================================

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format File System

Enter your choice(0-9): 5

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. Are you sure to continue?[Y/N] Y

Setting...Done.

4.     Enter 5 and press Y to delete the next-startup configuration files.

Enter your choice(0-9): 5

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. Are you sure to continue?[Y/N] Y

Setting...Done.

The extended BootWare menu is displayed again:

==========================<EXTENDED-BOOTWARE MENU>==========================

|<1> Boot System                                                           |

|<2> Enter Serial SubMenu                                                  |

|<3> Enter Ethernet SubMenu                                                |

|<4> File Control                                                          |

|<5> Restore to Factory Default Configuration                              |

|<6> Skip Current System Configuration                                     |

|<7> BootWare Operation Menu                                               |

|<8> Skip Authentication for Console Login                                 |

|<9> Storage Device Operation                                              |

|<0> Reboot                                                                |

============================================================================

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format File System

Enter your choice(0-9): 0

5.     Enter 0 to reboot the device. The device will reboot with the factory defaults.

Enter your choice(0-9): 0

DDR2 SDRAM test successful.

System is starting...

Booting Normal Extend BootWare

The Extend BootWare is self-decompressing.................................

Done.

6.     After the device starts up, configure a new console login 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 12345678

[Sysname-line-aux1/1] return

7.     Save the running configuration to use the configuration at the next reboot.

<Sysname> save

The current configuration will be written to the device. Are you sure? [Y/N] :y

Please input the file name(*.cfg)[flash:/default.cfg]

(To leave the existing filename unchanged, press the enter key):default.cfg

Validating file. Please wait....

Saved the current configuration to mainboard device successfully.

Dealing with Telnet password loss

1.     Log in to the device through the console port.

2.     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 12345678

[Sysname-line-vty0-63] return

3.     Save the running configuration to enable the configuration to survive a reboot.

<Sysname> save

The current configuration will be written to the device. Are you sure? [Y/N] :y

Please input the file name(*.cfg)[flash:/default.cfg]

(To leave the existing filename unchanged, press the enter key):default.cfg

Validating file. Please wait....

Saved the current configuration to mainboard device successfully

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

CAUTION:

Do not execute the save command before you complete the tasks in this section. The save operation overwrites the restored startup configuration file with the running configuration.

 

To resolve the problem:

1.     Transfer a backup copy of the startup configuration file to the root directory of the default storage medium on each MPU:

 

IMPORTANT

IMPORTANT:

The device loads startup configuration files from the default storage medium.

·     Make sure all MPUs use the same type of storage medium as the default storage medium. In this section, the flash memory is used on each MPU.

·     If a partitioned USB disk is used, make sure the configuration file is transferred to the root directory of the first partition on the USB disk.

 

a.     Download configuration file config.cfg from the FTP server to the root directory of the flash memory on the active MPU.

<Sysname> ftp 192.168.29.1

Press CTRL+C to abort.

Connected to 192.168.29.1 (192.168.29.1).

220 WFTPD 2.0 service (by Texas Imperial Software) ready for new user

User (192.168.29.1:(none)): 1

331 Give me your password, please

Password:

230 Logged in successfully

Remote system type is MSDOS.

ftp> binary

200 Type is Image (Binary)

ftp> get config.cfg flash:/config.cfg

227 Entering Passive Mode (192,168,29,1,209,24)

150 "F:\config.cfg" file ready to send (18494 bytes) in IMAGE / Binary mode

226 Transfer finished successfully.

18494 bytes received in 0.0383 seconds (471.1 kbyte/s)

ftp> quit

221 Windows FTP Server (WFTPD, by Texas Imperial Software) says goodbye

b.     Copy the configuration file to the root directory of the flash memory on the standby MPU.

<Sysname> copy config.cfg slot1#flash:/config.cfg

Copy flash:/config.cfg to slot1#flash:/config.cfg?[Y/N] :y

Coping file flash:/config.cfg to slot1#flash:/config.cfg...Done.

2.     Specify the configuration file as the main startup configuration file. Skip this step if the configuration file uses the same name as the corrupt main startup configuration file.

<Sysname> startup saved-configuration config.cfg

3.     Reboot the device.

4.     If the problem persists, contact H3C Support.

Related commands

This section lists the commands that you might use for troubleshooting configuration loss.

 

Command

Description

binary

Sets the file transfer mode to binary.

copy

Copies a file and saves the file to the destination directory.

ftp

Logs in to an FTP server and enters FTP client view.

get

Downloads a file from the FTP server and saves the file.

startup saved-configuration

Specifies a file as a startup configuration file for each MPU.

 

Troubleshooting hardware

This section provides troubleshooting information for common hardware problems.

 

 

NOTE:

·     This section describes how to troubleshoot terminal display, cards, power modules, and fan trays. To troubleshoot transceiver modules, ports, and temperature alarms, see "Troubleshooting system management" and "Troubleshooting ports."

·     For more information about the LEDs, see H3C S7500E Switch Series Installation Guide.

 

Configuration terminal display failure

No display on the configuration terminal

Symptom

The configuration terminal does not have display when the switch is powered on.

Solution

To resolve the problem:

1.     Verify that the power system is operating correctly.

2.     Verify that the MPU is operating correctly.

3.     Verify that the console cable is connected to the console port or the USB console port on the MPU and the specified serial port on the configuration terminal correctly.

4.     Verify that the following settings are configured for the terminal:

?     Baud rate—9600.

?     Data bits—8.

?     ParityNone.

?     Stop bits—1.

?     Flow controlNone.

?     EmulationVT100.

5.     Verify that the console cable is in good quality and is operating correctly.

6.     If the problem persists, contact H3C Support.

Garbled display on the configuration terminal

Symptom

The configuration terminal has a garbled display when the switch is powered on.

Solution

To resolve the problem:

1.     Verify that the following settings are configured for the terminal:

?     Baud rate—9600.

?     Data bits—8.

?     ParityNone.

?     Stop bits—1.

?     Flow controlNone.

?     EmulationVT100.

2.     If the problem persists, contact H3C Support.

MPU reboot failure

Symptom

An MPU fails to reboot. The LEDs for the MPU are in the following state:

·     LSQM3MPUA0 MPU—The RUN LED is off.

·     LSQM3MPUB0 MPU—The RUN and ALM LEDs are on.

·     LSQM2MPUC0/LSQM2MPUD0/LSQM1SRP8X2QE0/LSQM2MPUDS0 MPU—The SLOT X LED is red.

Troubleshooting flowchart

Figure 1 Troubleshooting MPU reboot failure

 

Solution

To resolve the problem:

1.     Verify that the system software image on the MPU is correct.

a.     Log in to the MPU through the console port and restart the switch. If the system reports that a CRC error occurs or that no system software image is available during the BootWare loading process, reload the system software image.

b.     Verify that the system software image in the flash memory is the same size as the one on the server. If no system software image is available in the flash memory, or if the image size is different from the one on the server, reload the system software image. Then set the reloaded system software image to the current system software image.

The system software image in the flash memory is automatically set to the current system software image during the BootWare loading process.

2.     Verify that the MPU memory is running correctly.

Reboot the MPU, and immediately press CTRL+T to examine the memory. If a memory fault is detected, replace the MPU.

RAM test successful.

Press Ctrl+T to start five-step full RAM test...

Press Ctrl+Y to start nine-step full RAM test...

Running five-step RAM test...

This operation may take several minutes. Please wait...

RAM dataline testing...                    [ PASS ]

RAM unit testing...                        [ PASS ]

Five-step RAM test succeeded.

3.     Verify that no error is reported during the BootWare loading process.

If there are still errors reported during the BootWare loading process, identify the faulty module and verify that the MPU is installed securely.

?     If the MPU is not installed securely, remove and reinstall the MPU.

?     If the MPU is installed securely, replace the MPU.

4.     If the problem persists, contact H3C Support.

MPU boot failure

Symptom

An MPU designated as the standby MPU fails to boot after installation. The LEDs for the MPU are in the following state:

·     LSQM3MPUA0 MPU—The RUN LED is off.

·     LSQM3MPUB0 MPU—The RUN and ALM LEDs are on.

·     LSQM2MPUC0/LSQM2MPUD0/LSQM1SRP8X2QE0/LSQM2MPUDS0 MPU—The SLOT X LED is red.

Troubleshooting flowchart

Figure 2 Troubleshooting newly installed standby MPU boot failure

 

 

Solution

To resolve the problem:

1.     Remove and reinstall the MPU to make sure the MPU is installed securely.

2.     Execute the display power-info command to verify that the surplus power is sufficient.

If the power is insufficient, add power modules to the switch and examine whether the MPU is operating correctly.

[Sysname-probe] display power-info

  Device Power: 2500

  Fan Power: 195

  Surplus power: 2089

  Slot No.     Power

   3           60

   6           78      --reserve  for  mainboard

   7           78

Board Exist Reg50: 0xbf  Reg51: 0xf7  Reg52: 0x52

Power  up   Reg5A: 0x 0  Reg5B: 0xc8  Reg5C: 0x5c  Reg15B: 0xc8  Reg15C: 0xff

 

  Power Event Information:

 

POE Power Chassis 0: Fail

3.     Verify that the MPU is the same model as the active MPU. If they are not the same model, replace the MPU with one that is the same model as the active MPU.

4.     Verify that the 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.

5.     If the problem persists, contact H3C Support.

Service module reboot failure

Symptom

A service module fails to reboot. The LEDs for the service module are in the following state:

·     LSQM3MPUA0/LSQM3MPUB0 MPU—The RUN and ALM LEDs are on.

·     LSQM2MPUC0/LSQM2MPUD0/LSQM1SRP8X2QE0/LSQM2MPUDS0 MPU—The SLOT X LED is red.

Troubleshooting flowchart

Figure 3 Troubleshooting service module reboot failure

 

Solution

To resolve the problem:

1.     Verify that the system software image is available and that the image is the same size as the one on the server. If no system software image is available, or the system software image size is different from the one on the server, reload the system software image.

<Sysname> display boot-loader

  Software images on slot 1:

Current software images:

  flash:/S7500E-CMW710-BOOT-R7568.bin

  flash:/S7500E-CMW710-SYSTEM-R7568.bin

Main startup software images:

  flash:/S7500E-CMW710-BOOT-R7568.bin

  flash:/S7500E-CMW710-SYSTEM-R7568.bin

Main startup software images:

  flash:/S7500E-CMW710-BOOT-R7568.bin

  flash:/S7500E-CMW710-SYSTEM-R7568.bin

Main startup software images:

  flash:/S7500E-CMW710-BOOT-R7568.bin

  flash:/S7500E-CMW710-SYSTEM-R7568.bin

Backup startup software images:

  None

<Sysname> dir

Directory of flash:

   0 drw-           - Sep 26 2013 16:18:06   core

   1 drw-           - Jun 30 2013 11:32:34   diagfile

   2 -rw-        7122 Dec 23 2013 10:02:46   ifindex.dat

   3 drw-           - Dec 11 2013 19:00:37   start-zy.cfg

   4 drw-           - Aug 30 2013 11:51:15   logfile

   5 -rw-    20529152 Dec 22 2013 14:28:40   S7500E-cmw710-boot-R7568.bin

   6 -rw-   178325504 Dec 22 2013 14:39:02   S7500E-cmw710-system-R7568.bin

   7 drw-           - Jun 30 2013 11:32:34   seclog

   8 -rw-       17175 Dec 23 2013 10:02:48   startup.cfg

   9 -rw-      276535 Dec 23 2013 10:02:48   startup.mdb

  10 drw-           - Nov 12 2013 11:11:54   versionInfo

 

503808 KB total (125896 KB free)

2.     Install another service module into the slot.

?     If the new service module boots successfully, no failure occurs on the MPU and backplane. Go to step 3.

?     If the new service module fails to boot, replace the MPU.

3.     Verify that the service module has loaded files.

<Sysname> display logbuffer

%May  3 13:27:17:086 2013 H3C DEVM/4/BOARD_LOADING: Board is loading file on Chassis 1 Slot 7.

%May  3 13:27:17:647 2013 H3C DEVM/5/LOAD_FINISHED: Board has finished loading file on Chassis 1 Slot 7.

?     If there are loading records about the service module, install the service module into another slot to verify that the service module can boot successfully.

?     If there are no loading records about the service module, go to step 4.

4.     If the problem persists, contact H3C Support.

Service module boot failure

Symptom

A newly-installed service module fails to boot. The LEDs for the service module are in the following state:

·     LSQM3MPUA0/LSQM3MPUB0 MPU—The RUN and ALM LEDs are on.

·     LSQM2MPUC0/LSQM2MPUD0/LSQM1SRP8X2QE0/LSQM2MPUDS0 MPU—The SLOT X LED is red.

Troubleshooting flowchart

Figure 4 Troubleshooting service module boot failure

 

Solution

To resolve the problem:

1.     Verify that the system software image is available and that the image is the same size as the one on the server. If no system software image is available, or the system software image size is different from the one on the server, reload the system software image.

<Sysname>display boot-loader

  Software images on slot 1:

Current software images:

  flash:/S7500E-CMW710-BOOT-R7568.bin

  flash:/S7500E-CMW710-SYSTEM-R7568.bin

Main startup software images:

  flash:/S7500E-CMW710-BOOT-R7568.bin

  flash:/S7500E-CMW710-SYSTEM-R7568.bin

Backup startup software images:

  None

<Sysname>dir

Directory of flash:

   0 drw-           - Sep 26 2013 16:18:06   core

   1 drw-           - Jun 30 2013 11:32:34   diagfile

   2 -rw-        7122 Dec 23 2013 10:02:46   ifindex.dat

   3 drw-           - Dec 11 2013 19:00:37   start-zy.cfg

   4 drw-           - Aug 30 2013 11:51:15   logfile

   5 -rw-    20529152 Dec 22 2013 14:28:40   S7500E-cmw710-boot-R7568.bin

   6 -rw-   178325504 Dec 22 2013 14:39:02   S7500E-cmw710-system-R7568.bin

   7 drw-           - Jun 30 2013 11:32:34   seclog

   8 -rw-       17175 Dec 23 2013 10:02:48   startup.cfg

   9 -rw-      276535 Dec 23 2013 10:02:48   startup.mdb

  10 drw-           - Nov 12 2013 11:11:54   versionInfo

 

503808 KB total (125896 KB free)

2.     Remove and reinstall the service module to make sure the service module is installed securely.

3.     Verify that the power system of the switch provides sufficient power. Add power modules to the switch to verify that the MPU is operating correctly.

4.     See the release notes to determine whether the system software image supports the service module. If the system software image does not support the service module, upgrade the system software image to the version that supports the service module.

5.     Install another service module that is compatible with the system software image into the slot to verify that the service module can boot successfully. If the service module boots successfully, no failure occurs on the MPU and backplane. If the service module fails to boot, replace the MPU.

6.     Execute the display logbuffer command to verify that the service module has loaded files.

<Sysname> display logbuffer

%May  3 13:27:17:086 2013 H3C DEVM/4/BOARD_LOADING: Board is loading file on Chassis 1 Slot 7.

%May  3 13:27:17:647 2013 H3C DEVM/5/LOAD_FINISHED: Board has finished loading file on Chassis 1 Slot 7.

?     If the service module has loaded files, install the service module into another slot to verify that the service module can load files successfully.

?     If the service module has not leaded files, go to step 7

7.     If the problem persists, contact H3C Support.

Unexpected card reboot

Symptom

A card rebooted unexpectedly and is currently in Normal state.

Solution

To resolve the problem:

1.     Check the logs for the time range during which the card rebooted. Determine whether a user used the reboot command to reboot the switch.

2.     Execute the command to identify the reason that caused the most recent reboot.

H3C Comware Software, Version 7.1.070, Release 7568

Copyright (c) 2010-2017 New H3C Technologies Co., Ltd. All rights reserved.

H3C S7506E uptime is 0 weeks, 0 days, 1 hour, 44 minutes

Last reboot reason : USER reboot

……

Last reboot reason : USER reboot indicates that the user rebooted the switch.

3.     If all the cards have rebooted, verify that the power system of the switch is operating correctly.

a.     Identify whether power failures occurred on the power source.

b.     Identify whether the power cords are connected securely.

4.     For the S7510E switch, make sure the slot supports the card in current forwarding mode.

5.     If the problem persists, contact H3C Support.

Operating power module failure

Symptom

An operating power module fails. The LEDs for the power module are in the following state:

·     LSQM3MPUA0/LSQM3MPUB0 MPU—The PWR OK LED is off, and the PWR FAIL LED is on or off.

·     LSQM2MPUC0/LSQM2MPUD0/LSQM1SRP8X2QE0/LSQM2MPUDS0 MPU—The PWR LED is red or off.

Troubleshooting flowchart

Figure 5 Troubleshooting operating power supply failure

 

Solution

To resolve the problem:

1.     Identify the operating state of the power module.

?     Execute the display power command to view the operating state of the power module.

<Sysname> display power

 Power        1 State: Normal

 Power        2 State: Absent

?     Execute the display alarm command to view alarm information about the power module.

<Sysname> display alarm

Slot   CPU   Level   Info

-      -     INFO    Power 2 is absent.

If the power module is in Absent state, go to step 2. If the power module is in Fault state, go to step 3.

2.     Verify that the power module is installed securely.

Remove and reinstall the power module to make sure the power module is installed securely. Then observe the power module LEDs on the MPU. If the LEDs still indicate power module failure, exchange the power module with another power module that is operating correctly. Then execute the display power command to verify that the power module has changed to Normal state. If the power module remains in Absent state, replace the power module.

3.     Verify that the power module is operating correctly.

a.     Verify that the power cord is connected to the power module securely.

<Sysname> display power

 Power        1 State: Normal

 Power        2 State: Fault

If the voltage and current of the power module are 0 and the power module state is Fault, the power cord is disconnected. Connect the power cord securely to the power module. Then execute the display power command to verify that the power module has changed to Normal state.

b.     Determine whether the power module is in high temperature. If dust accumulation on the power module causes the high temperature, remove the dust. Then remove and reinstall the power module. Execute the display power command to verify that the power module has changed to Normal state.

c.     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 Fault state, replace the power module.

4.     If the problem persists, contact H3C Support.

Newly installed power module failure

Symptom

A newly installed power module fails. The LEDs for the power module are in the following state:

·     LSQM3MPUA0/LSQM3MPUB0 MPU—The PWR OK LED is off, and the PWR FAIL LED is on or off.

·     LSQM2MPUC0/LSQM2MPUD0/LSQM1SRP8X2QE0/LSQM2MPUDS0 MPU—The PWR LED is red or off.

Troubleshooting flowchart

Figure 6 Troubleshooting newly installed power module failure

 

Solution

To resolve the problem:

1.     Identify the operating state of the power module.

?     Execute the display power command to view the operating state of the power module.

<Sysname> display power

 Power        1 State: Normal

 Power        2 State: Absent

?     Execute the display alarm command to view alarm information about the power module.

<Sysname> display alarm

Slot   CPU   Level   Info

-      -     INFO    Power 2 is absent.

If the power module is in Absent state, go to step 2. If the power module is in Fault state, go to step 3.

2.     Verify that the power module is installed securely.

a.     Remove and reinstall the power module to make sure the power module is installed securely. Then execute the display power command to verify that the power module has changed to Normal state.

b.     Remove and 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 Absent state, go to step 4.

3.     Verify that the power module is operating correctly.

a.     Verify that the power module is connected to the power source correctly. If it is not, connect it to the power source correctly. Then execute the display power command to verify that the power module has changed to Normal state.

b.     Remove and 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 Fault state, go to step 4.

4.     If the problem persists, contact H3C Support.

External PoE power supply failure

Symptom

The external PoE power supply for the S7502E switch fails unexpectedly.

Troubleshooting flowchart

Figure 7 Troubleshooting PoE power supply failure

 

Solution

To resolve the problem:

1.     Determine whether you are required to reboot the switch.

The external PoE power supply might fail to supply power to the switch after you reboot the switch. Do not reboot the switch if possible.

2.     If rebooting the switch is not required, wait 30 seconds and repower the external PoE power supply.

3.     If you are required to reboot the switch, perform the following steps:

a.     Repower the external PoE power supply.

b.     Power on the device or execute the reboot command to reboot the device.

c.     Delete PoE configuration from the switch and reconfigure PoE on the switch.

4.     If the problem persists, contact H3C Support.

Fan tray failure

Symptom

An operating fan tray or a newly installed fan tray fails. The LEDs for the fan tray are in the following state:

·     LSQM3MPUA0/LSQM3MPUB0 MPU—The FAN OK LED is off, and the FAN FAIL LED is on.

·     LSQM2MPUC0/LSQM2MPUD0/LSQM1SRP8X2QE0/LSQM2MPUDS0 MPU—The FAN LED is red.

Troubleshooting flowchart

Figure 8 Troubleshooting fan tray failure

 

Solution

To resolve the problem:

1.     Identify the operating state of the fan tray.

?     Execute the display fan command to view the operating state of the fan tray.

<Sysname> display fan

Fan Frame 0  State: Normal

?     Execute the display alarm command to view alarm information about the fan tray.

<Sysname> display alarm

Chassis Slot   CPU   Level   Info

2       -      -     INFO    fan 1 is absent.

If the fan tray is in Absent state, go to step 2. If the fan tray is in Fault state, go to step 3.

2.     Verify that the fan tray is installed securely.

Remove and reinstall the fan tray to make sure the fan tray is installed securely. Then execute the display fan command to verify that the fan tray has changed to Normal state. If the fan tray remains in Absent state, replace the fan tray.

3.     Verify that the fan tray is operating correctly.

a.     Identify whether the fan tray is faulty.

-     Execute the display environment command to view temperature information.

If the temperature continues to rise, put your hand at the air outlet to feel if air is being expelled out of the air outlet. If no air is being expelled out of the air outlet, the fan tray is faulty.

b.     If the fan tray is faulty, remove and reinstall the fan tray to make sure the fan tray is installed securely. Then execute the display fan command to verify that the fan tray has changed to Normal state.

c.     If the fan tray remains in Fault state, replace the fan tray.

You must make sure the switching operating temperature is below 60°C (140°F) while you replace the fan tray. If a new fan tray is not readily available, power off the switch to avoid damage caused by high temperature.

4.     If the problem persists, contact H3C Support.

Related commands

This section lists the commands that you might use for troubleshooting the hardware.

 

Command

Description

dir

Displays information about files and directories.

display alarm

Displays alarm information.

display boot-loader

Displays current configuration files and system software images.

display device

Displays device information.

display environment

Displays temperature information.

display fan

Displays the operating states of the fan tray.

display logbuffer

Displays the state of the log buffer and the log information in the log buffer.

display power

Displays power module information.

display power-info

Displays power information.

probe

Enters probe view.

 

Troubleshooting system management

This section provides troubleshooting information for common system management problems.

High CPU usage

Symptom

The sustained CPU usage is over 80% on a card.

Troubleshooting flowchart

Figure 9 Troubleshooting high CPU usage

 

Solution

Possible reasons for high CPU usage problems include:

·     Route flapping is taking place.

·     The device is being attacked.

·     A link loop exists. A link loop might cause broadcast storm and network flapping problems. If such a problem occurs, large amounts of protocol packets are sent to the CPU. Many interfaces on the device receive heavy traffic. The interface usage might reach 90% or be even higher.

To resolve the problem:

1.     Display routing table information multiple times. If route entries change frequently, route flapping is taking place. Go to step 7.

2.     Verify that the device is not being attacked:

a.     Use a packet capture tool to capture packets on ports of the device. For example, you can use Sniffer, Wireshark, or WinNetCap.

b.     Analyze packet characteristics to identify the attack sources.

c.     Configure attack prevention against the attack sources.

For more information, see Security Configuration Guide.

3.     Verify that no link loops exist:

a.     Display interface information to view the inbound packet statistics for interfaces on the device.

<Sysname> display interface gigabitethernet3/0/1

GigabitEthernet3/0/1

Current state: UP

Line protocol state: UP

Description: GigabitEthernet3/0/1 Interface

Bandwidth: 1000000 kbps

Maximum transmission unit: 1500

Internet address: 2.1.1.2/24 (primary)

IP packet frame type: Ethernet II, hardware address: 0000-fc00-9276

IPv6 packet frame type: Ethernet II, hardware address: 0000-fc00-9276

Loopback is not set

Media type is twisted pair, port hardware type is 1000_BASE_T

Port priority: 0

1000Mbps-speed mode, full-duplex mode

Link speed type is autonegotiation, link duplex type is autonegotiation

Flow-control is not enabled

Maximum frame length: 9216

Last clearing of counters: Never

 Peak input rate: 8 bytes/sec, at 2016-03-19 09:20:48

 Peak output rate: 1 bytes/sec, at 2016-03-19 09:16:16

 Last 300 second input: 26560 packets/sec 123241940 bytes/sec 99%

 Last 300 second output: 0 packets/sec 0 bytes/sec 0%

......

If the interface usage is 90% or higher, a link loop exists.

b.     If a link loop exists, perform the following tasks:

-     Verify that relevant links are correctly connected.

-     Verity that relevant interfaces are correctly configured.

-     Verify that STP is enabled and correctly configured.

-     Verify that STP is operating correctly on neighboring devices.

c.     If the problem persists, an STP protocol calculation error might have occurred or interfaces are not blocked at the driver level as expected. Shut down the uplink interface of the loop or disconnect the cable and then connect the cable again to trigger STP recalculation to recover services. Send the symptom information to H3C Support for analysis.

4.     If the problem persists, execute the display cpu-usage command multiple times to locate the card that has a high CPU resource usage.

5.     If you still cannot locate the problem, identify the job that has a high CPU usage. For example:

[Sysname-probe] display process cpu slot 1

CPU utilization in 5 secs: 2.4%; 1 min: 2.5%; 5 mins: 2.4%

    JID      5Sec      1Min      5Min    Name

      1      0.0%      0.0%      0.0%    scmd

      2      0.0%      0.0%      0.0%    [kthreadd]

      3      0.0%      0.0%      0.0%    [migration/0]

      4      0.0%      0.0%      0.0%    [ksoftirqd/0]

      5      0.0%      0.0%      0.0%    [watchdog/0]

      6      0.0%      0.0%      0.0%    [migration/1]

      7      0.0%      0.0%      0.0%    [ksoftirqd/1]

      8      0.0%      0.0%      0.0%    [watchdog/1]

      9      0.0%      0.0%      0.0%    [migration/2]

     10      0.0%      0.0%      0.0%    [ksoftirqd/2]

     11      0.0%      0.0%      0.0%    [watchdog/2]

......

The output shows the average CPU usage values of jobs for the last 5 seconds, 1 minute, and 5 minutes. Typically, the average CPU usage of a job is less than 5%

6.     Display the job's stack. Perform this step for a minimum of five times. In this example, the job uses the ID of 145.

[Sysname-probe] follow job 145 slot 1

Attaching to process 145 ([dGDB])

Iteration 1 of 5

------------------------------

Kernel stack:

[<ffffffff80355290>] schedule+0x570/0xde0

[<ffffffff80355da8>] schedule_timeout+0x98/0xe0

[<ffffffff802047e4>] ep_poll+0x4b4/0x5e0

[<ffffffffc05587a8>] DRV_Sal_EVENT_Read+0x1f8/0x290 [system]

[<ffffffffc07351e4>] drv_sysm_gdb_console+0xc4/0x2d0 [system]

[<ffffffffc1a04114>] thread_boot+0x84/0xa0 [system]

[<ffffffff8015c420>] kthread+0x130/0x140

[<ffffffff801183d0>] kernel_thread_helper+0x10/0x20

 

Iteration 2 of 5

------------------------------

Kernel stack:

[<ffffffff80355290>] schedule+0x570/0xde0

[<ffffffff80355da8>] schedule_timeout+0x98/0xe0

[<ffffffff802047e4>] ep_poll+0x4b4/0x5e0

[<ffffffffc05587a8>] DRV_Sal_EVENT_Read+0x1f8/0x290 [system]

[<ffffffffc07351e4>] drv_sysm_gdb_console+0xc4/0x2d0 [system]

[<ffffffffc1a04114>] thread_boot+0x84/0xa0 [system]

[<ffffffff8015c420>] kthread+0x130/0x140

[<ffffffff801183d0>] kernel_thread_helper+0x10/0x20

 

Iteration 3 of 5

------------------------------

Kernel stack:

[<ffffffff80355290>] schedule+0x570/0xde0

[<ffffffff80355da8>] schedule_timeout+0x98/0xe0

[<ffffffff802047e4>] ep_poll+0x4b4/0x5e0

[<ffffffffc05587a8>] DRV_Sal_EVENT_Read+0x1f8/0x290 [system]

[<ffffffffc07351e4>] drv_sysm_gdb_console+0xc4/0x2d0 [system]

[<ffffffffc1a04114>] thread_boot+0x84/0xa0 [system]

[<ffffffff8015c420>] kthread+0x130/0x140

[<ffffffff801183d0>] kernel_thread_helper+0x10/0x20

 

Iteration 4 of 5

------------------------------

Kernel stack:

[<ffffffff80355290>] schedule+0x570/0xde0

[<ffffffff80355da8>] schedule_timeout+0x98/0xe0

[<ffffffff802047e4>] ep_poll+0x4b4/0x5e0

[<ffffffffc05587a8>] DRV_Sal_EVENT_Read+0x1f8/0x290 [system]

[<ffffffffc07351e4>] drv_sysm_gdb_console+0xc4/0x2d0 [system]

[<ffffffffc1a04114>] thread_boot+0x84/0xa0 [system]

[<ffffffff8015c420>] kthread+0x130/0x140

[<ffffffff801183d0>] kernel_thread_helper+0x10/0x20

 

Iteration 5 of 5

------------------------------

Kernel stack:

[<ffffffff80355290>] schedule+0x570/0xde0

[<ffffffff80355da8>] schedule_timeout+0x98/0xe0

[<ffffffff802047e4>] ep_poll+0x4b4/0x5e0

[<ffffffffc05587a8>] DRV_Sal_EVENT_Read+0x1f8/0x290 [system]

[<ffffffffc07351e4>] drv_sysm_gdb_console+0xc4/0x2d0 [system]

[<ffffffffc1a04114>] thread_boot+0x84/0xa0 [system]

[<ffffffff8015c420>] kthread+0x130/0x140

[<ffffffff801183d0>] kernel_thread_helper+0x10/0x20

7.     Save the information displayed in the previous steps.

8.     Contact H3C Support.

High memory usage

Symptom

The memory usage on a card is over 60% for more than 30 minutes.

Troubleshooting flowchart

Figure 10 Troubleshooting high memory usage

 

Solution

IMPORTANT

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.

 

To resolve the problem:

1.     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    64       8     32   1       289     289    kmalloc-64

105       112     16328    0     2    8       54      56     kmalloc-16328

14        14      2097096  0     1    512     14      14     kmalloc-2097096

147       225     2048     8     15   8       12      15     kmalloc-2048

7108      7232    192      8     32   2       226     226    kmalloc-192

22        22      524232   0     1    128     22      22     kmalloc-524232

1288      1344    128      8     21   1       64      64     kmalloc-128

0         0       67108808 0     1    16384   0       0      kmalloc-67108808

630       651     4096     8     7    8       93      93     kmalloc-4096

68        70      131016   0     1    32      68      70     kmalloc-131016

1718      2048    8        8     64   1       31      32     kmalloc-8

1         1       16777160 0     1    4096    1       1      kmalloc-16777160

2         15      2048     0     15   8       1       1      sgpool-64

0         0       40       0     42   1       0       0      inotify_event_cache

325       330     16328    8     2    8       165     165    kmalloc_dma-16328

0         0       72       0     30   1       0       0      LFIB_IlmEntryCache

0         0       1080     0     28   8       0       0      LFIB_IlmEntryCache

0         0       1464     0     21   8       0       0      MFW_FsCache

1         20      136      0     20   1       1       1      L2VFIB_Ac_cache

0         0       240      0     25   2       0       0      CCF_JOBDESC

0         0       88       0     26   1       0       0      NS4_Aggre_TosSrcPre

0         0       128      0     21   1       0       0      IPFS_CacheHash_cachep

---- More ----

Each value line shows the memory information for a slab. The Number field shows the number of objects (memory blocks) allocated to the module. The product of the Number field and the Size field shows the size of the memory space that is used by a slab. If the memory space used by a slab keeps increasing, the slab might have memory leakage problems.

2.     Display the memory call information for the slabs that might have leak problems. This example uses the kmalloc-2048 slab.

[Sysname-probe] view /sys/kernel/slab/kmalloc-2048/alloc_calls

     23 kque_create+0x58/0x260 age=4262117/4404939/4692659 pid=128-372 cpus=0,2-3

      2 sys_init_module+0x1bdc/0x1e50 age=4746250/4748179/4750108 pid=109-128 cpus=9,12

      4 __vmalloc_area_node+0x154/0x1b0 age=4652363/4677089/4747310 pid=128-166

cpus=0-1,12

     16 percpu_populate+0x3c/0x60 age=4322758/4322758/4322758 pid=128 cpus=0

     21 alloc_pipe_info+0x24/0x60 age=4/3888025/4320768 pid=1-564 cpus=0-4,9,11

     29 alloc_pci_dev+0x18/0x40 age=4758366/4758366/4758368 pid=1 cpus=15

      2 init_dev+0x1c0/0x870 age=510128/2630142/4750157 pid=1-542 cpus=0,2

      1 init_dev+0x4dc/0x870 age=510128 pid=542 cpus=2

      2 kobj_map_init+0x2c/0xd0 age=4758371/4758535/4758700 pid=0-1 cpus=0,15

      2 usb_alloc_dev+0x38/0x200 age=4750540/4750605/4750671 pid=1 cpus=15

      1 usb_create_hcd+0x34/0x120 age=4750540 pid=1 cpus=15

     16 exception_notifier_init+0x298/0x4f8 age=4750380/4750380/4750381 pid=1 cpus=15

      1 drv_port_module_varialbe_init+0x24/0x80 [system] age=4651959 pid=128 cpus=0

      1 DRV_VLAN_BasicFunc_Init+0x1ec/0x700 [system] age=4651871 pid=128 cpus=0

      1 drv_vlan_maccash_init+0x124/0x240 [system] age=4651869 pid=128 cpus=0

      1 drv_ipmc_spec_init+0x54/0x840 [system] age=4650355 pid=128 cpus=0

      1 drv_evb_add_broadcast_group+0x964/0xa50 [system] age=4264182 pid=312 cpus=1

      2 DRV_EVB_MAP_AddRec+0x160/0x2a0 [system] age=4264142/4264175/4264209 pid=288 cpus=9

      1 drv_evi_localmac_init+0x160/0x650 [system] age=4651896 pid=128 cpus=0

      1 DRV_QINQ_Init+0x278/0x890 [system] age=4650270 pid=128 cpus=0

      1 DRV_QINQ_Init+0x478/0x890 [system] age=4650270 pid=128 cpus=0

      1 Drv_Qacl_InitAddUdfTemplate+0x68/0xb30 [system] age=4651968 pid=128 cpus=0

      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.

3.     Save the information displayed in the previous steps.

4.     Contact H3C Support.

Temperature alarms

Symptom

Temperature alarms occur.

Troubleshooting flowchart

Figure 11 Troubleshooting temperature alarms

 

 

Solution

To resolve the problem:

1.     Check the ambient temperature. If the ambient temperature is higher than 45°C (113°F), lower the ambient temperature by adding air conditioners or taking other heat dissipation measures.

2.     Check the device temperature. If the device temperature is higher than 68°C (154.4°F), use the display fan command to check the fan tray operating status. If the status field displays Fault, remove the fan tray and then install the fan tray again.

3.     Identify whether the air filters are clean. If they are not, clean them.

4.     Read the temperature alarms to identify the involved card.

5.     Use the temperature-limit command to adjust the temperature alarm thresholds for the card.

6.     Use the display environment command to identify whether the temperature alarm thresholds have been adjusted successfully. If the thresholds have not been adjusted, replace the card.

7.     If the problem persists, contact H3C Support.

Related commands

This section lists the commands that you might use for troubleshooting system management.

 

Command

Remarks

display cpu-usage

Displays the current CPU usage statistics.

display environment

Displays temperature information, including the current temperature and the temperature alarm thresholds.

display fan

Displays the operating status of all fans on the device.

display memory

Displays memory usage statistics.

display process cpu

Displays the CPU usage statistics for jobs.

This command is available in probe view.

display system internal kernel memory pool

Displays memory block usage statistics.

This command is available in probe view.

follow job job-id

Displays the stack of a job.

This command is available in probe view.

temperature-limit

Sets temperature alarm thresholds.

view  /sys/kernel/slab/<modulename>/alloc_calls

Displays the number of allocated memory blocks and the call information.

 

Troubleshooting ports

This section provides troubleshooting information for common port problems.

10/100/1000Base-T copper port fails to come up

Symptom

A 10/100/1000Base-T copper port cannot come up.

Troubleshooting flowchart

Figure 12 Troubleshooting link up failure on a port

 

Solution

To resolve the problem:

1.     Verify that the speed and duplex mode of the local port match the speed and duplex mode of the peer port:

a.     Execute the display interface command to verify that the port is up.

b.     If the port is down, use the undo shutdown command to bring up the port.

c.     Execute the display interface brief command to examine whether the speed and duplex mode of the port match the speed and duplex mode of the peer port.

d.     If they do not match, use the speed command and the duplex command to set the speed and duplex mode for the port.

 

 

NOTE:

The speed and duplex mode of network management ports cannot be configured in the current software version.

 

2.     Replace the network cable with a new one to verify that the network cable is in good condition.

3.     Replace the local port with a new one (on an interface module of the same type, if possible) to verify that the local port is operating correctly.

4.     Replace the peer port with a new one (on an interface module of the same type, if possible) to verify that the peer port is operating correctly.

5.     If the problem persists, contact H3C Support.

1000-Mbps SFP fiber port fails to come up

Symptom

A 1000-Mbps SFP fiber port cannot come up.

Troubleshooting flowchart

Figure 13 Troubleshooting link up failure on a port

 

Solution

To resolve the problem:

1.     Verify that the speed and duplex mode of the local port match the speed and duplex mode of the peer port:

a.     Execute the display interface command to verify that the port is up.

b.     If the port is down, use the undo shutdown command to bring up the port.

c.     Execute the display interface brief command to examine whether the speed and duplex mode of the port match the speed and duplex mode of the peer port.

d.     If they do not match, use the speed command and the duplex command to set the speed and duplex mode for the port.

2.     Verify that the speed and duplex mode of the port match the speed and duplex mode of the transceiver module:

a.     Execute the display interface brief command to examine whether the speed and duplex mode of the port match the speed and duplex mode of the transceiver module.

b.     If they do not match, use the speed command and the duplex command to set the speed and duplex mode for the port.

3.     Verify that the transceiver module is operating correctly:

a.     Execute the display transceiver alarm interface command to examine the alarms present on the transceiver module.

-     The device displays None if no error occurs.

-     If input errors occur, verify that the peer port, fiber, and intermediate device are operating correctly.

-     If output errors, current errors, or voltage errors occur, verify that the local port is operating correctly.

<Sysname> display transceiver alarm interface GigabitEthernet 2/0/1

GigabitEthernet2/0/1 transceiver current alarm information:

  TX fault

  RX power high

Table 2 Transceiver module alarms

Field

Description

SFP/SFP+/CFP/QSFP+

RX loss of signal

Incoming (Rx) signal is lost.

RX power high

Incoming (Rx) power is high.

RX power low

Incoming (Rx) power is low.

TX fault

Transmit (Tx) fault.

TX bias high

Tx bias current is high.

TX bias low

Tx bias current is low.

TX power high

Tx power is high.

TX power low

Tx power is low.

Temp high

Temperature is high.

Temp low

Temperature is low.

Voltage high

Voltage is high.

Voltage low

Voltage is low.

Transceiver info I/O error

Transceiver information read and write error.

Transceiver info checksum error

Transceiver information checksum error.

Transceiver type and port configuration mismatch

Transceiver type does not match port configuration.

Transceiver type not supported by port hardware

The port does not support the transceiver type.

XFP

RX loss of signal

Incoming (Rx) signal is lost.

RX not ready

Rx is not ready.

RX CDR loss of lock

Rx clock cannot be recovered.

RX power high

Rx power is high.

RX power low

Rx power is low.

TX not ready

Tx is not ready.

TX fault

Tx fault.

TX CDR loss of lock

Tx clock cannot be recovered.

TX bias high

Tx bias current is high.

TX bias low

Tx bias current is low.

TX power high

Tx power is high.

TX power low

Tx power is low.

Module not ready

Module is not ready.

APD supply fault

Avalanche Photo Diode (APD) supply fault.

TEC fault

Thermoelectric Cooler (TEC) fault.

Wavelength unlocked

Wavelength of optical signal exceeds the manufacturer's tolerance.

Temp high

Temperature is high.

Temp low

Temperature is low.

Voltage high

Voltage is high.

Voltage low

Voltage is low.

Transceiver info I/O error

Transceiver information read and write error.

Transceiver info checksum error

Transceiver information checksum error.

Transceiver type and port configuration mismatch

Transceiver type does not match port configuration.

Transceiver type not supported by port hardware

Transceiver type is not supported on the port.

 

b.     Use an optical power meter to verify that the Tx power and Rx power of the transceiver module are stable and are within the correct range.

c.     Execute the display transceiver interface command to verify that the wavelength and transmission distance of the local transceiver module are consistent with the wavelength and transmission distance of the peer transceiver module.

d.     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.

4.     Replace the fiber with a new one to verify that the fiber is in good condition.

5.     Replace the local port with a new one (on an interface module of the same type, if possible) to verify that the local port is operating correctly.

6.     Replace the peer port with a new one (on an interface module of the same type, if possible) to verify that the peer port is operating correctly.

7.     If the problem persists, contact H3C Support.

10-Gigabit SFP+/XFP fiber port fails to come up

Symptom

A 10-Gigabit SFP+/XFP fiber port cannot come up.

Troubleshooting flowchart

Figure 14 Troubleshooting link up failure on a port

 

Solution

To resolve the problem:

1.     Verify that the speed and duplex mode of the local port match the speed and duplex mode of the peer port:

a.     Execute the display interface brief command to examine whether the speed and duplex mode of the port match the speed and duplex mode of the peer port.

b.     If they do not match, use the speed command and the duplex command to set the speed and duplex mode for the port.

2.     Verify that the speed and duplex mode of the port match the speed and duplex mode of the transceiver module:

a.     Execute the display interface brief command to examine whether the speed and duplex mode of the port match the speed and duplex mode of the transceiver module.

b.     If they do not match, use the speed command and the duplex command to set the speed and duplex mode for the port.

3.     Verify that the local and peer ports are operating correctly:

a.     Use a 10-GE SFP+ cable (or XFP transceiver module and fiber) to directly connect the local port and another 10-GE SFP+ or XFP fiber port of the same interface module. A 10-GE SFP+ cable is suitable for short connections.

b.     If the local port can come up, replace the peer port with a new one to verify that the peer port is operating correctly.

c.     If the local port cannot come up, replace the local port with a new one to verify that the local port is operating correctly.

4.     Verify that the transceiver module is operating correctly:

a.     Execute the display transceiver alarm interface command to examine the alarms present on the transceiver module.

-     The device displays None if no error occurs.

-     The device displays alarms if the transceiver module fails or the type of the transceiver module does not match the port type.

b.     Use an optical power meter to verify that the Tx power and Rx power of the transceiver module are stable and are within the correct range.

c.     Execute the display transceiver interface command to verify that the wavelength and transmission distance of the local transceiver module are consistent with the wavelength and transmission distance of the peer transceiver module.

d.     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.

5.     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.

6.     If the problem persists, contact H3C Support.

40-GE QSFP+/CFP fiber port fails to come up

Symptom

A 40-Gigabit QSFP+/CFP fiber port cannot come up.

Troubleshooting flowchart

Figure 15 Troubleshooting link up failure on a port

 

Solution

To resolve the problem:

1.     Verify that the local and peer ports are operating correctly:

a.     Use a QSFP+ cable (or CFP transceiver module and fiber) to directly connect the local port and another 40-GE QSFP+ or CFP fiber port of the same interface module. A QSFP+ cable is suitable for short connections.

b.     If the local port can come up, replace the peer port with a new one (on an interface module of the same type, if possible) to verify that the peer port is operating correctly.

c.     If the local port cannot come up, replace the local port with a new one (on an interface module of the same type, if possible) to verify that the local port is operating correctly.

2.     Verify that the transceiver module is operating correctly:

a.     Execute the display transceiver alarm interface command to examine the alarms present on the transceiver module.

-     The device displays None if no error occurs.

-     The device displays alarms if the transceiver module fails or the type of the transceiver module does not match the port type.

b.     Use an optical power meter to verify that the Tx power and Rx power of the transceiver module are stable and are within the correct range.

c.     Execute the display transceiver interface command to verify that the wavelength and transmission distance of the local transceiver module are consistent with the wavelength and transmission distance of the peer transceiver module.

d.     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.

 

IMPORTANT

IMPORTANT:

If a QSFP+ to SFP+ cable is used, use an optical attenuator to make sure the Tx power of the QSFP+ module stays below the Rx power of the SFP+ module.

 

3.     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.

4.     If the problem persists, contact H3C Support.

A port goes down

Symptom

A port does down.

Solution

To resolve the problem:

1.     Verify that the port is not configured with the shutdown command.

2.     Verify that the port is not shut down because of abnormal errors.

3.     Verify that the local and peer port configuration, network cable, transceiver module, and fiber are correct.

4.     If the problem persists, contact H3C Support.

Port state flapping

Symptom

A port flaps between the up and down states.

Solution

To resolve the problem:

1.     If the port is a fiber port, verify that the transceiver module is operating correctly.

a.     Display the transceiver module alarms to verify that the local and peer transceiver modules and fibers are correct.

b.     For transceiver modules that support digital diagnosis, display the upper and lower limits for the optical power.

-     If the Tx power reaches the limit, verify that the local transceiver module and fiber are operating correctly.

-     If the Rx power reaches the limit, verify that the remote transceiver module and fiber are operating correctly.

2.     If the port is a copper port, set the speed and duplex mode for the local and peer ports.

3.     Verify that the link, peer device, and intermediate device are operating correctly.

4.     If the problem persists, contact H3C Support.

Transceiver module failure

Symptom

A fiber port installed with a transceiver module cannot operate correctly.

Solution

To resolve the problem:

1.     Execute the display transceiver alarm interface command to examine the alarms present on the transceiver module.

?     If input errors occur, verify that the peer port, fiber, and intermediate device are operating correctly.

?     If output errors, current errors, or voltage errors occur, verify that the local port is operating correctly.

<Sysname> display transceiver alarm interface GigabitEthernet1/2/0/15

GigabitEthernet1/2/0/15 transceiver current alarm information:

  TX fault

  RX power high

Table 3 Transceiver module alarms

Field

Description

SFP/SFP+/CFP/QSFP+

RX loss of signal

Incoming (Rx) signal is lost.

RX power high

Incoming (Rx) power is high.

RX power low

Incoming (Rx) power is low.

TX fault

Transmit fault.

TX bias high

Tx bias current is high.

TX bias low

Tx bias current is low.

TX power high

Tx power is high.

TX power low

Tx power is low.

Temp high

Temperature is high.

Temp low

Temperature is low.

Voltage high

Voltage is high.

Voltage low

Voltage is low.

Transceiver info I/O error

Transceiver information read and write error.

Transceiver info checksum error

Transceiver information checksum error.

Transceiver type and port configuration mismatch

Transceiver type does not match port configuration.

Transceiver type not supported by port hardware

The port does not support the transceiver type.

XFP

RX loss of signal

Incoming (Rx) signal is lost.

RX not ready

Rx is not ready.

RX CDR loss of lock

Rx clock cannot be recovered.

RX power high

Rx power is high.

RX power low

Rx power is low.

TX not ready

Tx is not ready.

TX fault

Tx fault.

TX CDR loss of lock

Tx clock cannot be recovered.

TX bias high

Tx bias current is high.

TX bias low

Tx bias current is low.

TX power high

Tx power is high.

TX power low

Tx power is low.

Module not ready

Module is not ready.

APD supply fault

APD supply fault.

TEC fault

TEC fault.

Wavelength unlocked

Wavelength of optical signal exceeds the manufacturer's tolerance.

Temp high

Temperature is high.

Temp low

Temperature is low.

Voltage high

Voltage is high.

Voltage low

Voltage is low.

Transceiver info I/O error

Transceiver information read and write error.

Transceiver info checksum error

Transceiver information checksum error.

Transceiver type and port configuration mismatch

Transceiver type does not match port configuration.

Transceiver type not supported by port hardware

Transceiver type is not supported on the port.

 

2.     Verify that the Tx and Rx optical powers of the transceiver module are within the correct range.

a.     Execute the display transceiver diagnosis interface command to display the Tx and Rx optical powers of the transceiver module.

<Sysname> display transceiver diagnosis interface

Ten-GigabitEthernet1/2/0/15 transceiver diagnostic information:

  Current diagnostic parameters:

    Temp.(°C)  Voltage(V)  Bias(mA)  RX power(dBM)  TX power(dBM)

    41         3.26        42.43     -40.00         -2.20

b.     Execute the display transceiver interface and display transceiver diagnosis interface commands to display the value ranges for the optical powers of the transceiver module.

If the value range in the output from the display transceiver interface command is different than the display transceiver diagnosis interface command, the smaller range takes effect.

The output from the display transceiver diagnosis interface command also displays the current temperature, voltage, bias current, and the value ranges for these parameters.

<Sysname> display transceiver interface Ten-GigabitEthernet 1/2/0/15

Ten-GigabitEthernet1/2/0/15 transceiver information:

  Transceiver Type              : 10G_BASE_SR_SFP

  Connector Type                : LC

  Wavelength(nm)                : 850

  Transfer Distance(km)         : 80(50um),20(62.5um),300(om3)

  Digital Diagnostic Monitoring : YES

  Vendor Name                   : H3C

  Ordering Name                 : SFP-XG-SX-MM850-A

<Sysname> display transceiver diagnosis interface Ten-GigabitEthernet 1/2/0/15

Ten-GigabitEthernet1/2/0/15 transceiver diagnostic information:

  Current diagnostic parameters:

    Temp.(°C) Voltage(V)  Bias(mA)  RX power(dBM)  TX power(dBM

    43         3.35        46.33     -3.60          -2.38

  Alarm thresholds:

          Temp.(°C)  Voltage(V)  Bias(mA)  RX power(dBM)  TX power(dBM

    High  73         3.80        92.40     2.50           3.50

    Low   -3         2.81        1.00      -16.40         -11.20

3.     Verify that the transceiver module, peer device, and intermediate link are operating correctly.

4.     If the problem persists, contact H3C Support.

Reporting non-H3C transceiver modules

Symptom

When you use the display logbuffer command to view the system logs, the following reports about non-H3C transceiver modules appear in the system logs:

<Sysname> display logbuffer

%Oct 17 21:37:24:812 2011 nl-denbo-ro01 OPTMOD/4/PHONY_MODULE:

  -Chassis=2-Slot=3;    GigabitEthernet2/3/0/5: This transceiver is NOT sold by H3C. H3C  therefore shall NOT guarantee the normal function of the device or  assume the maintenance responsibility thereof!

Troubleshooting flowchart

Figure 16 Troubleshooting non-H3C transceiver module reports

 

Solution

To resolve the problem:

1.     Identify the vendor of the transceiver module plugged into the port:

a.     Use the display transceiver interface command to display the transceiver information.

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.

2.     Contact H3C Support to determine whether the transceiver module vendor is H3C:

a.     Use the debug port optical-eeprom command in probe view to collect the transceiver module information. Send the bar code of the transceiver module to H3C Support to identify the vendor of the transceiver module.

b.     If you determine that the transceiver module vendor is not H3C, replace it with an H3C transceiver module.

3.     If the transceiver module vendor is identified as H3C but the problem persists, contact H3C Support.

Failure to support digital diagnosis on a transceiver module

Symptom

When you use the display transceiver diagnosis interface command to display the diagnostic information of a transceiver module, the system displays a message that the transceiver module does not support digital diagnosis.

<Sysname> display transceiver diagnosis interface gigabitethernet 1/0/1

Error: The transceiver does not support this function.

Troubleshooting flowchart

Figure 17 Troubleshooting the failure to support digital diagnosis on a transceiver module

 

Solution

To resolve the problem:

1.     Verify that the vendor of the transceiver module is H3C:

a.     Use the display transceiver interface command to display the transceiver information.

b.     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.

2.     Verify that the transceiver module supports digital diagnosis:

a.     Use the display transceiver interface command to display transceiver module information.

b.     Determine whether the value of the Digital Diagnostic Monitoring field is Yes.

c.     Consult H3C Support about whether the transceiver module supports digital diagnosis.

3.     If the transceiver module vendor is identified as H3C and the transceiver module supports digital diagnosis but the problem persists, contact H3C Support.

Error frames (for example, CRC errors) on a port

Symptom

The output from the display interface command shows that error frames exist (for example, CRC error frames) on a port.

<Sysname> display interface gigabitethernet3/0/1

GigabitEthernet3/0/1

Current state: DOWN

Line protocol state: DOWN

Description: GigabitEthernet3/0/1 Interface

Bandwidth: 1000000 kbps

Maximum transmission unit: 1500

Internet address: 2.1.1.2/24 (primary)

IP packet frame type: Ethernet II, hardware address: 0000-fc00-9276

IPv6 packet frame type: Ethernet II, hardware address: 0000-fc00-9276

Loopback is not set

Media type is twisted pair, port hardware type is 1000_BASE_T

Port priority: 0

1000Mbps-speed mode, full-duplex mode

Link speed type is autonegotiation, link duplex type is autonegotiation

Flow-control is not enabled

Maximum frame length: 9216

Last clearing of counters: Never

 Peak input rate: 8 bytes/sec, at 2016-03-19 09:20:48

 Peak output rate: 1 bytes/sec, at 2016-03-19 09:16:16

 Last 300 second input: 0 packets/sec 0 bytes/sec -%

 Last 300 second output: 0 packets/sec 0 bytes/sec -%

 Input (total):  2892 packets, 236676 bytes

          24 unicasts, 2 broadcasts, 2866 multicasts, 0 pauses

 Input (normal):  2892 packets, - bytes

          24 unicasts, 2 broadcasts, 2866 multicasts, 0 pauses

 Input:  0 input errors, 0 runts, 0 giants, 0 throttles

          3 CRC, 0 frame, - overruns, 0 aborts

          - ignored, - parity errors

 Output (total): 29 packets, 1856 bytes

          24 unicasts, 5 broadcasts, 0 multicasts, 0 pauses

 Output (normal): 29 packets, - bytes

          24 unicasts, 5 broadcasts, 0 multicasts, 0 pauses

 Output: 0 output errors, - underruns, - buffer failures

          0 aborts, 0 deferred, 0 collisions, 0 late collisions

          0 lost carrier, - no carrier

Troubleshooting flowchart

Figure 18 Troubleshooting error frames (for example, CRC errors) on a port

 

Solution

To resolve the problem:

1.     (Optional.) Use the reset counter interface command in user view to clear the packet statistics of the port.

This command resets the values of each statistical field to 0, so that you can view the statistics changes more clearly.

2.     Use the display interface command to display the incoming packet statistics and outgoing packet statistics of the port.

?     If the value of the input CRC, frame, or throttles field is increasing, perform the following tasks:

# Verify that the link is operating correctly.

Poor link quality or excessive optical attenuation might cause packet transmission errors. Replace the cable or fiber if the link is not operating correctly.

# Replace the local port with a new one to verify that the local port is operating correctly.

-     If error frames stop accumulating, replace the local port and send the error information to the technical support.

-     If error frames continue to accumulate, check the peer device and the intermediate link.

?     If the value of the input overruns field is increasing, verify that the interface module is operating correctly.

The value of the overruns field represents the number of packets dropped because the input rate of the port exceeded the queuing capability.

If only one port or only the device connected to the port has error frames, execute the display interface command multiple times. If the value of input errors field is increasing, and the increased number equals to the increased number of the overruns field, the interface module is incorrect. Send the error information to the technical support.

?     If the value of the input giants field is increasing, verify that the local and peer ports have the same jumbo frame configuration.

3.     If the port is a fiber port, verify that the optical power of the transceiver module is operating correctly:

a.     Use the display transceiver diagnosis interface command in probe view to view the present measured values of the digital diagnosis parameters for the transceiver module.

b.     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.

[Sysname-probe] display transceiver diagnosis interface ten-gigabitethernet 1/0/1

Ten-GigabitEthernet1/0/1 transceiver diagnostic information:

  Current diagnostic parameters:

    [module]  Temp.(°C)

              1stTX   2ndTX   1stRX   2ndRX

              N/A     N/A     N/A     N/A

              Voltage(V)

              3.3VTX  12VTX   3.3VRX  12VRX

              3.29    N/A     3.40    N/A

    [channel] TX Bias(mA)    RX power(dBm)  TX power(dBm)

    1         6.09           0.91           -0.77

    2         5.95           1.09           -0.16

    3         6.05           1.58           -0.17

    4         5.85           1.58           -0.14

    5         6.07           2.23           -0.30

    6         5.72           2.85           -0.47

    7         6.11           3.01           -0.08

    8         5.50           1.17           -0.02

    9         5.89           -0.85          -0.17

    10        5.94           -40.00         0.29

    11        6.05           -40.00         0.18

    12        5.78           -40.00         -0.30

 

  Alarm thresholds:

    [module]  Temp.(°C) Voltage(V)  Bias(mA)  RX power(dBM)  TX power(dBM)

    High      0          3.63        10.00     1.58           5.44

    Low       0          2.97        0.50      3.13           -11.61

4.     Verify that the port configurations are correct:

a.     Execute the display interface brief command.

b.     Determine whether the speed and duplex mode of the port match the speed and duplex mode of the peer port.

c.     If they do not match, use the speed command and the duplex command to set the speed and duplex mode for the port.

5.     Verify that the port and the link medium are operating correctly:

a.     Plug the link medium into another port that is operating correctly, and determine whether the same problem occurs.

b.     If the problem still occurs, verify that the following items are operating correctly:

-     Intermediate links and devices, including optical-to-electrical converters, cable terminal racks, and transmission devices.

-     Transmission medium, including network cables, optical fibers, and transceiver modules.

c.     Examine the port:

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

6.     Determine whether the port has received a large amount of flow control frames:

a.     Use the display interface command to view the number of pause frames.

If the number of pause frames is accumulating, you can determine that the port has sent or received a large amount of flow control frames.

b.     Verify that the incoming traffic and outgoing traffic have not exceeded the maximum traffic processing capability of the local device and the peer device.

7.     If the problem persists, contact H3C Support.

Failure to receive or send packets

Symptom

A port is up, but it cannot receive or send packets.

Troubleshooting flowchart

Figure 19 Troubleshooting the failure to receive packets

 

Solution

To resolve the problem:

1.     Examine the packet statistics of the port:

a.     (Optional.) Use the reset counter interface command in user view to clear the packet statistics of the port.

This command resets the values of each statistical field to 0, so that you can view the statistics changes more clearly.

b.     Determine whether the ports at both ends are always up, and use the display interface  command to determine whether the number of incoming or outgoing packets is accumulating. At the same time, examine the outgoing or incoming packet statistics of the peer port.

c.     View the values of the error packet fields and determine whether the number of error packets is accumulating.

2.     Verify that the port configurations do not affect packet receiving or sending:

a.     Use the display interface brief command to verify that the port configurations are correct.

The port configurations include the duplex mode, speed, port type, and VLAN configurations of the ports at both ends of the link.

b.     If configuration errors exist, modify the port configurations. If the number of incoming packets in the output from the display interface command is accumulating, you can determine that the port can receive packets.

c.     If the port fails to receive packets, use the shutdown command and then the undo shutdown command to re-enable the port. If the number of incoming packets in the output from the display interface command is accumulating, you can determine that the port can receive packets.

d.     If the port is configured with STP, use the display stp brief command to verify that the port is not in the discarding state.

e.     If a port is set to the discarding state by STP, examine and modify the STP-related configurations to resolve the problem.

As a best practice, configure the port as an edge port or disable STP on the port if it is directly connected to a terminal.

f.     If the port is assigned to an aggregation group, use the display link-aggregation summary command to verify that the status of the port is Selected.

g.     If the status of the port is Unselected, the port cannot send or receive data packets.

h.     Determine the reasons why the port becomes Unselected, for example, the attribute configurations of the port are different from the reference port. Modify the attribute configurations of the port to make the port become Selected.

3.     Verify that the port and the link medium are operating correctly:

a.     Plug the link medium into another port that is operating correctly, and determine whether the same problem occurs.

b.     Examine the port.

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

4.     If the problem persists, contact H3C Support.

Related commands

This section lists the commands that you might use for troubleshooting ports.

 

Command

Description

display diagnostic-information

Displays or saves operating information for features and hardware modules.

display interface

Displays Ethernet interface information.

display interface brief

Displays brief interface information.

display link-aggregation summary

Displays brief information about all aggregation groups.

display logbuffer

Displays the state of the log buffer and the log information in the log buffer.

display stp brief

Displays brief information about the spanning tree status and statistics.

display transceiver alarm interface

Displays the alarms present on the transceiver module.

display transceiver diagnosis

Displays the current values of the digital diagnosis parameters on the transceiver module.

display transceiver interface

Displays the key parameters of the transceiver module.

 

Troubleshooting IRF

This section provides troubleshooting information for common IRF problems.

IRF fabric setup failure

Symptom

A chassis cannot be added to an IRF fabric.

Troubleshooting flowchart

Figure 20 Troubleshooting IRF fabric setup failure

Solution

To resolve the problem:

1.     Verify that the number of member chassis in the IRF fabric does not exceed the upper limit.

The upper limit varies by software version and depends on the IRF mode. Execute the display version command to identify the software version of the IRF fabric.

?     If the member chassis upper limit is reached for the software version, you cannot add new chassis to the IRF fabric.

?     If the member chassis upper limit is not reached for the software version, execute the display irf command to identify the IRF mode of the IRF fabric. Verify that the member chassis upper limit is not reached for the IRF mode.

For more information about the upper limit, see H3C S7500E Switch Series Virtual Technologies Configuration Guide for the software version.

2.     Verify that the chassis is an H3C S7500E switch.

The S7500E switches can form an IRF fabric only with devices in the same series.

3.     Verify that the chassis is operating in IRF mode:

a.     Execute the display interface brief command to verify that the physical port numbers on the chassis have changed from three segments to four segments. In IRF mode, the member ID is added to physical port numbers as the first segment (for example, Ten-GigabitEthernet 1/4/0/1).

b.     Execute the chassis convert mode irf command to change the operating mode to IRF.

4.     Verify that the chassis is operating in the same IRF mode as the IRF fabric:

a.     Execute the display irf command and check the IRF mode field.

[Sysname] display irf

MemberID  Slot  Role   Priority  CPU-Mac         Description

 *+1      0     Master 1         00e0-fc0f-8c08  ---

--------------------------------------------------

 * indicates the device is the master.

 + indicates the device through which the user logs in.

 

 The Bridge MAC of the IRF is: 0000-fc00-2500

 Auto upgrade                : yes

 Mac persistent              : always

 Domain ID                   : 0

 Auto merge                  : yes

 IRF mode                    : light

b.     If the chassis is operating in an IRF mode different than the IRF fabric, execute the irf mode command to change the IRF mode for the chassis. The changed mode will take effect after a reboot.

5.     Verify that the member ID of the chassis does not conflict with any member chassis in the IRF fabric:

a.     Execute the display irf command to view member IDs.

b.     If the member ID of the chassis is not unique, use the irf member renumber command to assign a new member ID to the chassis.

6.     Verify that the MPUs that provide 10-GE or 40-GE IRF physical interfaces are the same model. If the MPUs are not the same model, use one of the following methods to resolve the problem:

?     Replace the MPUs to the same model and reconfigure IRF port bindings.

?     Use the ports on interface modules as IRF physical interfaces.

7.     Verify that the physical IRF links are connected correctly:

 

IMPORTANT

IMPORTANT:

When you connect two neighboring IRF members, you must connect the physical interfaces of IRF-port 1 on one member to the physical interfaces of IRF-port 2 on the other.

 

a.     Execute the display irf configuration command on each member chassis, and check the IRF-Port1 and IRF-Port2 fields for IRF port bindings.

b.     Verify that the physical IRF connections are consistent with the IRF port bindings.

c.     If there are inconsistencies, reconfigure the IRF port bindings or reconnect the IRF physical interfaces.

8.     Verify that all IRF links are up:

a.     Execute the display irf topology command, and then check the Link field.

b.     If the Link field for an IRF port displays DOWN, execute the display interface command.

c.     Check the current state field for each physical interface bound to the IRF port.

-     If the field displays DOWN ( Administratively ), execute the undo shutdown command to bring up the interface.

-     If the field displays DOWN, verify that SFP+, QSFP+, or CFP transceiver modules or DAC cables are used for IRF connection and that they are operating correctly.

 

 

NOTE:

The switch might support transceiver modules or DAC cables that provide higher speed than SFP+, QSFP+, or CFP, depending on the software version and interface module model. For more information, see the latest H3C S7500E Switch Series Virtual Technologies Configuration Guide.

 

d.     If the IRF port is down when it contains a minimum of one up link, verify that the MPUs of the chassis are operating correctly.

9.     Verify that the member chassis is running the same software version as the IRF fabric:

a.     Execute the display version command to identify the software version.

b.     Upgrade the MPUs in the chassis to use the same software version as the IRF fabric.

 

 

NOTE:

Typically, the irf auto-update enable command can automatically synchronize a member chassis with the software version of the master chassis. However, the synchronization might fail when the gap between the software versions is large.

 

10.     Verify that the chassis has a unique bridge MAC address:

a.     Execute the display interface vlan-interface 1 command, and then check the Hardware Address field.

[Sysname] display interface vlan-interface 1

Vlan-interface1 current state: UP

Line protocol current state: UP

Description: Vlan-interface1 Interface

The Maximum Transmit Unit is 1500

Internet protocol processing : disabled

IP Packet Frame Type: PKTFMT_ETHNT_2,  Hardware Address: 0023-8912-3d07

IPv6 Packet Frame Type: PKTFMT_ETHNT_2,  Hardware Address: 0023-8912-3d07

b.     If the chassis has the same bridge MAC address as the IRF fabric, remove the bridge MAC conflict.

11.     Verify that the chassis is in the same system operating mode as the IRF fabric:

a.     Execute the display system-working-mode command and check the The next system working mode field.

[Sysname] display system-working-mode

The current system working mode is advance.

The next system working mode is advance.

b.     If the system operating mode of the chassis is different than the IRF fabric, execute the system-working-mode command to change the system operating mode for the chassis. The changed mode will take effect after a reboot.

12.     Verify that the chassis has the same maximum number of ECMP routes as the IRF fabric:

a.     Execute the display max-ecmp-num command and check the Max-ECMP-Num at the next reboot field.

[Sysname] display max-ecmp-num

  Max-ECMP-Num in use: 17

  Max-ECMP-Num at the next reboot: 17

b.     If the maximum number of ECMP routes of the chassis is different than the IRF fabric, execute the max-ecmp-num command to change the number for the chassis. The changed number will take effect after a reboot.

13.     If the problem persists, contact H3C Support.

IRF split

Symptom

An IRF fabric splits.

Troubleshooting flowchart

Figure 21 Troubleshooting IRF split

 

Solution

To resolve the problem:

1.     Verify that the IRF physical interfaces are operating correctly:

a.     Execute the display trapbuffer command or view system logs to check for physical IRF link down events that occurred around the split time.

b.     If the split followed an IRF link down event, execute the display interface command to check port statistics for CRC errors.

c.     If transceiver modules and fibers are used, execute the display transceiver diagnosis command. Make sure the transmit and receive power has not exceeded the power specifications of the fiber module.

2.     Remove hardware problems that might cause recurring IRF split events:

a.     Execute the display version command to identify the uptime of MPUs and interface modules that have IRF links.

b.     Compare the uptime of MPUs and interface modules to determine whether a member chassis or interface module had rebooted before the IRF split.

c.     If the IRF split is caused by a member chassis or interface module reboot, use the methods described in "Troubleshooting hardware" to resolve the problem.

3.     If the problem 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 settings, including the same IP address.

Troubleshooting flowchart

Figure 22 Troubleshooting BFD MAD failure

 

Solution

To resolve the problem:

1.     Verify that BFD MAD link connections are correct:

?     If you do not use an intermediate device, verify that each pair of member chassis has a dedicated BFD MAD link.

?     If you use an intermediate device, verify that each member chassis has a dedicated BFD MAD link with the intermediate device.

2.     Verify that all physical ports used for BFD MAD are up:

a.     Execute the display interface command.

b.     Check the current state field in the command output:

-     If the field displays DOWN ( Administratively ) for a port, execute the undo shutdown command to bring up the port.

-     If the field displays DOWN for a port, check the physical link for a link failure.

3.     Verify that the BFD MAD VLAN interface is configured correctly:

a.     Execute the display mad verbose command.

b.     Check the MAD BFD enabled interface field to verify that VLAN-interface 1 is not used for BFD MAD.

c.     If VLAN-interface 1 is used for BFD MAD, disable BFD MAD on VLAN-interface 1, and then enable BFD MAD on another VLAN interface.

d.     Verify that the BFD MAD-enabled VLAN interface does not have any other features, including VPN.

e.     Execute the display interface command to verify that the interface does not have the following IP addresses:

-     IP address assigned by using the ip address command.

-     VRRP virtual IP address.

4.     Verify that the BFD MAD VLAN and physical ports in the VLAN are configured correctly:

a.     Execute the display vlan command to verify the following items:

-     The BFD VLAN contains all physical ports used for BFD MAD.

-     The BFD VLAN does not contain physical ports that are not used for BFD MAD.

If an intermediate device is used, you must also perform this step on the intermediate device.

b.     Execute the display interface command to verify that the physical ports in the BFD VLAN are not configured with any features.

For BFD MAD to operate correctly, you must disable all features on the physical ports in the BFD MAD VLAN, including the spanning tree feature, ARP, and LACP.

5.     Verify that the MAD IP addresses are correct:

a.     Execute the display mad verbose command.

b.     Check the mad ip address field to verify the following items:

-     Each member chassis has a MAD IP address.

-     All MAD IP addresses are on the same subnet.

-     The MAD IP addresses are not addresses being used on the IRF fabric.

6.     If the network has multiple IRF fabrics, execute the display mad verbose command to verify that their BFD MAD VLANs are different.

7.     Verify that the physical ports in the BFD MAD VLAN are always up:

a.     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.

8.     If the problem persists, contact H3C Support.

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 23 Troubleshooting LACP MAD failure

 

Solution

To resolve the problem:

1.     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.

2.     Verify that each member chassis has a link in the link aggregation with the intermediate device.

3.     Verify that the link aggregation is operating in dynamic mode.

To enable dynamic aggregation mode, use the link-aggregation mode dynamic command.

4.     Verify that the aggregate interface and its member ports are up:

a.     Execute the display interface command.

b.     Check the current state field of the aggregate interface:

-     If the field displays DOWN ( Administratively ), execute the undo shutdown command to bring up the interface.

-     If the field displays DOWN, check the state of all its physical ports.

An aggregate interface goes down only if all its physical ports are down.

c.     Check the current state field of each member port:

-     If the field displays DOWN ( Administratively ), execute the undo shutdown command to bring up the port.

-     If the field displays DOWN, check the physical link of the port for a link failure.

5.     If the intermediate device is also an IRF fabric, verify that the IRF domain IDs of the two IRF fabrics are unique:

 

CAUTION

CAUTION:

The IRF member devices send extended LACPDUs with TLVs that convey the domain ID and the active ID of the IRF fabric. To avoid split detection failure, make sure the IRF fabric has a unique domain ID.

 

a.     Execute the display irf command to identify the domain ID of each IRF fabric.

b.     If the IRF fabrics use the same domain ID, execute the irf domain command to change the domain ID on one IRF fabric.

6.     Verify that the physical ports in the link aggregation are always up:

a.     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.

7.     If the problem persists, contact H3C Support.

Related commands

This section lists the commands that you might use for troubleshooting IRF:

 

Command

Description

display diagnostic-information

Displays or saves the operating statistics for multiple feature modules.

display interface

Displays interface information.

display interface brief

Displays brief interface information.

display irf

Displays IRF fabric information, including the member ID, role, priority, bridge MAC address, and description of each IRF member.

display irf configuration

Displays the IRF configuration on each member chassis.

display irf topology

Displays the IRF topology.

display mad verbose

Displays detailed MAD configuration.

display max-ecmp-num

Displays the maximum number of ECMP routes.

display system-working-mode

Displays system operating mode information.

display transceiver diagnosis

Displays the present measured values of the digital diagnosis parameters for transceiver modules.

display trapbuffer

Displays trap data in the trap buffer.

display version

Displays system version information.

display vlan

Displays VLAN information.

 

Troubleshooting EPON

This section provides troubleshooting information for common EPON problems.

Incompatibility with an optical transceiver module

Symptom

When an optical transceiver module is installed in an OLT port, the switch displays a log message that the transceiver module is not supported. The following are sample messages:

%Aug 19 09:53:07:661 2016 H3C OPTMOD/4/MODULE_IN: -MDC=1-Slot=3; Olt3/0/12: The transceiver is 1000_BASE_LX_SFP.                                            

^Aug 19 09:53:07:915 2016 H3C DRVMNT/2/ERRORCODE: -MDC=1-Slot=3; MdcId=1-ModuleId=0xf0b-Level=2; ErrCode = 1326120980, SYSM: ManuInfo Fail.          

                                                                                

%Aug 19 09:53:08:111 2016 H3C OPTMOD/3/CFG_ERR: -MDC=1-Slot=3; Olt3/0/12: Transceiver type and port configuration mismatched!                                   

%Aug 19 09:53:08:344 2016 H3C OPTMOD/3/TYPE_ERR: -MDC=1-Slot=3; Olt3/0/12: Transceiver type not supported!     

Solution

To resolve the problem, use a 1000_BASE_PX_SFP optical transceiver module to replace the incompatible transceiver module.

Down OLT port

Symptom

ONUs can correctly register with an OLT port of an EPON module. After a warm or cold reboot is performed on the EPON module, the OLT port cannot come up.

Solution

To resolve the problem:

1.     Verify that the optical transceiver module and the OLT port have good contact:

a.     Execute the display transceiver diagnosis interface command and verify that all parameters in the command output are correct.

<H3C>display transceiver diagnosis interface Olt2/0/12

Olt2/0/12 transceiver diagnostic information:

  Current diagnostic parameters:

    Temp.(°C) Voltage(V)  Bias(mA)  RX power(dBm)  TX power(dBm)

    -1         6.50        130.05    -40.00         8.13

  Alarm thresholds:

          Temp.(°C) Voltage(V)  Bias(mA)  RX power(dBm)  TX power(dBm)

    High  N/A        N/A         N/A       N/A            N/A

Low   N/A        N/A         N/A       N/A            N/A

b.     If some parameters are not correct, remove and reinstall the optical transceiver module.

2.     If the problem persists, contact H3C Support.

High or low receiving power on an OLT port

Symptom

The receiving power exceeds the threshold of an OLT port in the output from the display transceiver diagnosis interface command.

<H3C>dis transceiver diagnosis interface olt3/0/8                               

Olt3/0/8 transceiver diagnostic information:                                   

  Current diagnostic parameters:                                               

    Temp.(°C) Voltage(V)  Bias(mA)  RX power(dBm)  TX power(dBm)               

    38         3.27        5.61      -40.00          4.53                       

  Alarm thresholds:                                                            

          Temp.(°C) Voltage(V)  Bias(mA)  RX power(dBm)  TX power(dBm)         

    High  85         3.60        100.00    -4.00          8.00                 

    Low   -13        3.00        0.00      -32.10         1.00    

Solution

To resolve the problem:

1.     Verify that all ONU ports on the OLT port are down.

Typically, the receiving power exceeds the threshold when no ONU port is up. The receiving power will be in the valid range if ONU ports come up.

2.     If there are up ONU ports, perform the following tasks:

a.     Execute the display transceiver diagnosis interface command to display diagnosis information for any up ONU port.

b.     Execute the display transceiver diagnosis interface command to display diagnosis information for the OLT port. This command triggers the display of the most recent receiving power.

3.     If the problem persists, contact H3C Support.

Down ONU port

Symptom

The state of an ONU port is down in the output from the display interface command.

Troubleshooting flowchart

Figure 24 Troubleshooting a down ONU port

 

Solution

To resolve the problem:

1.     Verify that the ONU binding is correct:

?     If the ONU is manually bound to the ONU port, use the display onu command to verify that the ONU MAC address is correct.

?     If the ONU is bound to the ONU port through batch binding or automatic binding, execute the onu bind batch or onu bind auto command again. Make sure the number of ONUs on the OLT port does not exceed 63.

2.     Check the optical transceiver module by following the procedure in "1000-Mbps SFP fiber port fails to come up."

3.     Verify that compatibility with third-party ONUs is enabled if the ONU is from a third-party vendor.

4.     If compatibility with third-party ONUs is disabled, perform the following tasks:

a.     Enable compatibility with third-party ONUs.

b.     Use the deregister onu command to deregister the third-party ONU, or use the shutdown command to shut down the ONU port and then use the undo shutdown command to bring it up.

5.     Verify that no physical connectivity problems exist:

a.     If the other ONU ports on the same OLT port are also down, verify the following items:

-     The OLT port is up and uses the 1000_BASE_PX_SFP optical transceiver module (see "Incompatibility with an optical transceiver module").

-     The PON LEDs on the ONUs are on.

-     The POS is working correctly.

b.     If there are up ONU ports on the OLT port, verify the following items:

-     The ONU is working correctly. You can replace the ONU with another ONU to verify this item.

-     The optical fiber between the ONU and the POS is operating correctly. You can verify this item by switching the optical fiber of the ONU with the optical fiber of an up ONU connected to the same POS.

6.     If the problem persists, contact H3C Support.

User network access failure

Symptom

A user terminal cannot access the network even if the connected ONU has registered correctly.

Solution

To resolve the problem:

1.     Verify that the seventh bit in the first byte of the user MAC address is not 1. If the seventh bit is 1, for example, 02xx-xxxx-xxxx, the OLT determines that the MAC address is incorrect and drops packets from the address. Typically, the incorrect MAC address is user configured.

2.     If the incorrect MAC address is user configured, restore the original MAC address.

3.     If the problem persists, contact H3C Support.

Related commands

This section lists the commands that you might use for troubleshooting EPON:

 

Command

Description

display interface

Displays interface information.

display interface brief

Displays brief interface information.

display transceiver diagnosis

Displays the current values of the digital diagnosis parameters on transceiver modules.

display transceiver interface

Displays the key parameters of transceiver modules.

 

Troubleshooting QoS and ACL

This section provides troubleshooting information for common QoS and ACL problems.

ACL application failure for unsupported ACL rules

Symptom

The system fails to apply a packet filter or an ACL-based QoS policy to the hardware. It displays an error message that an unsupported rule exists in the ACL. The following is a sample error message:

Error: Slot=2 Fail to apply or refresh packet filter policy 3180 rule 5 on interface Vlan-interface20. Not supported.

Troubleshooting flowchart

Figure 25 Troubleshooting ACL application failure

 

Solution

To resolve the problem:

1.     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.

2.     If the problem persists, 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. It displays an error message that the hardware resources are not sufficient. The following are sample error messages:

Error: Slot=2 Fail to apply or refresh packet filter policy 3001 rule 25 on interface Vlan-interface6 due to lack of resources.

 

Warning: Classifier-behavior test in policy test applied on vlan 4079 failed in slot 2.

Reason: Not enough hardware resource.

Troubleshooting flowchart

Figure 26 Troubleshooting ACL application failure

 

Solution

Insufficient hardware resources might be insufficient Counter, Meter, or ACL resources.

To resolve the problem:

1.     Check the ACL, Counter, and Meter resource usage for insufficiency.

Execute the display qos-acl resource command to display the resource usage. If the number of ACLs to be applied is higher than the value of the Remaining field, resources are insufficient. If the ACLs are to be applied globally, check remaining resource usage on all cards.

[Sysname] display qos-acl resource

Interfaces: XGE2/3/0/1 to XGE2/3/0/4

---------------------------------------------------------------------

 Type             Total      Reserved   Configured Remaining  Usage

---------------------------------------------------------------------

 VFP ACL          2048       1024       0          1024       50%

 IFP ACL          8192       3072       0          5120       37%

 IFP Meter        4096       1536       0          2560       37%

 IFP Counter      4096       1536       0          2560       37%

 EFP ACL          1024       0          0          1024       0%

 EFP Meter        512        0          0          512        0%

 EFP Counter      512        0          0          512        0%

 

Interfaces: XGE2/3/0/5 to XGE2/3/0/8

---------------------------------------------------------------------

 Type             Total      Reserved   Configured Remaining  Usage

---------------------------------------------------------------------

 VFP ACL          2048       1024       0          1024       50%

 IFP ACL          8192       3072       0          5120       37%

 IFP Meter        4096       1536       0          2560       37%

 IFP Counter      4096       1536       0          2560       37%

 EFP ACL          1024       0          0          1024       0%

 EFP Meter        512        0          0          512        0%

 EFP Counter      512        0          0          512        0%

?     IFP—Resource usage for inbound traffic.

?     EFP—Resource usage for outbound traffic.

2.     Delete unnecessary ACLs to release resources if the failure is caused by ACL resource insufficiency. Delete unnecessary ACLs that use Meter or Counter resources if the failure is caused by Meter or Counter resource insufficiency.

If you cannot release enough resources, go to step 4.

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.

3.     Apply the packet filter or QoS policy again.

4.     If the problem persists, 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. However, the ACL does not take effect.

Troubleshooting flowchart

Figure 27 Troubleshooting ACL application failure

 

Solution

To resolve the problem:

1.     Check the ACLs used by QoS policies and packet filters for overlapping rules:

a.     Use the following commands to display ACLs that are used by QoS policies and packet filters:

-     display packet-filter

-     display qos policy user-defined

-     display traffic classifier user-defined

b.     Execute the display acl command to check for overlapping rules in the ACLs.

For example, the following sample output shows that rule 0 in ACL 3100 and rule 0 in ACL 3009 can both match traffic sourced from 2.2.2.1.

ACL number 3100

rule 0 permit ip source 2.2.2.2 0.0.255.255

ACL number 3009

rule 0 permit ip source 2.2.2.2 0.0.0.255

2.     Check the filters and policies that use overlapping ACLs for a behavior conflict.

If two behaviors conflict, the device performs the behavior that has higher priority, as shown in Table 4.

Table 4 Rules for selecting a higher priority behavior from conflicting behaviors

Conflicting behaviors

Higher priority behavior

·     redirect

·     filter permit

redirect

·     redirect

·     filter deny

filter deny

·     filter permit

·     filter deny

The behavior configured first.

 

3.     Revise ACLs, packet filters, or QoS policies to remove the behavior conflict.

4.     If the problem persists, contact H3C Support.

Related commands

This section lists the commands that you might use for troubleshooting QoS and ACLs.

 

Command

Description

display acl

Displays configuration and match statistics for ACLs.

display diagnostic-information

Displays operating statistics for multiple feature modules in the system.

display packet-filter

Displays ACL application information for packet filtering.

display qos-acl resource

Displays ACL resource usage.

display qos policy user-defined

Displays user-defined QoS policies.

display traffic classifier user-defined

Displays user-defined traffic classes.

 

Troubleshooting MDC

This section provides troubleshooting information for common MDC problems.

License problems

Symptom

The mdc command returns the "The feature MDC has no available license." error message.

Troubleshooting flowchart

Figure 28 Troubleshooting MDC license problems

 

Solution

The MDC feature requires a license. You must install a valid license to use the MDC feature.

To resolve the problem:

1.     Display license information.

[Sysname]display license

Chassis 3:

No license information to display.

[Sysname]display license feature

Chassis 3:

Total: 4  Usage: 0

Feature         Licensed        State

EVB             N               -

evi             N               -

mdc             N               -

FCoE            N               -

2.     If no license is installed for the MDC feature or the license has expired, apply for and install a license.

3.     If the problem persists, contact H3C Support.

Service module assignment failure

Symptom

The location command fails to assign a service module to an MDC.

Troubleshooting flowchart

Figure 29 Troubleshooting service module assignment failure

 

Solution

Typical service module assignment failure reasons include:

·     The available hardware resources are insufficient.

·     The service module belongs to another MDC. A service module can belong to only one MDC. Before you assign a service module to a non-default MDC, you must remove the existing assignment of the service module.

To resolve the problem:

1.     Display the CPU, disk space, and memory space resources for MDCs.

[Sysname]display mdc resource

Memory:

chassis 3 Slot 3:

 Used 35.2MB, Free 1279.5MB, Total 1314.7MB:

    ID    Name             Quota(MB)    Used(MB)    Available(MB)

    ----------------------------------------------------------------

    1     Admin            1314.7       35.2         1279.5

chassis 3 Slot 6:

 Used 34.0MB, Free 1280.7MB, Total 1314.7MB:

    ID    Name             Quota(MB)    Used(MB)    Available(MB)

    ----------------------------------------------------------------

    1     Admin            1314.7       34.0         1280.7

chassis 3 Slot 7:

 Used 34.0MB, Free 1284.7MB, Total 1318.7MB:

    ID    Name             Quota(MB)    Used(MB)    Available(MB)

    ----------------------------------------------------------------

    1     Admin            1318.7       34.0         1284.7

chassis 3 Slot 0:

 Used 583.5MB, Free 7289.1MB, Total 7872.6MB:

    ID    Name             Quota(MB)    Used(MB)    Available(MB)

    ----------------------------------------------------------------

    1     Admin            7872.6       583.5        7289.1

    2     mdcA             7872.6       0.0          7289.1

CPU:

chassis 3 Slot 3:

    ID    Name             Weight       Usage(%)

    -------------------------------------------------

    1     Admin            10           7

chassis 3 Slot 6:

    ID    Name             Weight       Usage(%)

    -------------------------------------------------

    1     Admin            10           0

chassis 3 Slot 7:

    ID    Name             Weight       Usage(%)

    -------------------------------------------------

    1     Admin            10           1

chassis 3 Slot 0:

    ID    Name             Weight       Usage(%)

    -------------------------------------------------

    1     Admin            10           0

    2     mdcA             10           0

Disk:

chassis 3 Slot 0:

flash:: Used 474.1MB, Free 17.9MB, Total 492.0MB:

    ID    Name             Quota(MB)    Used(MB)     Available(MB)

    --------------------------------------------------------------

    1     Admin            492.0        474.1        17.9

    2     mdcA             492.0        0.0          17.9

2.     If the CPU, disk space, or memory space resources assigned to an MDC are insufficient, re-assign resources to the MDC. (Details not shown.)

3.     Display the MDC to which the service module belongs. In this example, the service module is installed in slot 3 of member device 3. The service module is required to be assigned to mdcB.

If the output is as follows, the undo location command has not been executed for any service modules on the default MDC, and all service modules belong to the default MDC:

[Sysname]mdc Admin

[Sysname-mdc-1-Admin]display this

#

mdc Admin id 1

#

Return

If the output is as follows, the service module belongs to mdcA:

[Sysname-mdc-2-mdcA]display this

#

mdc mdcA id 2

 location chassis 3 slot 3

 mdc start

#

Return

4.     Reclaim the service module. In this example, the service module belongs to the default MDC.

[Sysname-mdc-1-Admin]undo location chassis 3 slot 3

The configuration associated with the specified slot of MDC will be lost. Continue? [Y/N]:y

5.     Verify that the service module does not belong to the default MDC.

[Sysname-mdc-1-Admin]display this

#

mdc Admin id 1

 undo location chassis 3 slot 3

#

Return

6.     Assign the service module to the mdcB.

[Sysname-mdc-2-mdcA]quit

[Sysname]mdc mdcB

[Sysname-mdc-3-mdcB]location chassis 3 slot 3

7.     Verify that the service module belongs to mdcB.

[Sysname-mdc-3-mdcB]display this

#

mdc mdcB id 3

 location chassis 3 slot 3

 mdc start

#

Return

8.     If the problem persists, contact H3C Support.

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 30 Troubleshooting interface assignment failure

 

Solution

To successfully assign interfaces to a non-default MDC, make sure the following requirements are met:

·     A service module on the device can belong to only one MDC.

·     All interfaces on a service module must be assigned to the same MDC by using a single command.

·     Before assigning a service module to an MDC, assign all interfaces on the service module to the MDC by using a single allocate command.

To reclaim a service module from the default MDC, only the undo location command is required. You do not need to use the undo allocate command.

To resolve the problem:

1.     Display the interfaces of MDCs.

[Sysname]display mdc interface

 MDC Admin's interface(s):

  M-GigabitEthernet1/0/0/0             FortyGigE3/4/0/1

  FortyGigE3/4/0/2                     FortyGigE3/4/0/3

  FortyGigE3/4/0/4                     FortyGigE3/5/0/1

  FortyGigE3/5/0/2                     FortyGigE3/5/0/3

  FortyGigE3/5/0/4

 

 MDC mdcA's interface(s):

  M-GigabitEthernet1/0/0/0             GigabitEthernet3/3/0/1

  GigabitEthernet3/3/0/2               GigabitEthernet3/3/0/3

  GigabitEthernet3/3/0/4               GigabitEthernet3/3/0/5

  GigabitEthernet3/3/0/6               GigabitEthernet3/3/0/7

  GigabitEthernet3/3/0/8               GigabitEthernet3/3/0/9

  GigabitEthernet3/3/0/10              GigabitEthernet3/3/0/11

  GigabitEthernet3/3/0/12              GigabitEthernet3/3/0/13

  GigabitEthernet3/3/0/14              GigabitEthernet3/3/0/15

  GigabitEthernet3/3/0/16              GigabitEthernet3/3/0/17

  GigabitEthernet3/3/0/18              GigabitEthernet3/3/0/19

  GigabitEthernet3/3/0/20              GigabitEthernet3/3/0/21

  GigabitEthernet3/3/0/22              GigabitEthernet3/3/0/23

  GigabitEthernet3/3/0/24              Ten-GigabitEthernet3/3/0/25

  Ten-GigabitEthernet3/3/0/26

 

 MDC mdcB's interface(s):

  M-GigabitEthernet1/0/0/0

 

[Sysname]mdc mdcA

 

[Sysname-mdc-2-mdcA]display this

#

mdc mdcA id 2

 location chassis 3 slot 3

 mdc start

 allocate interface GigabitEthernet3/3/0/1 to GigabitEthernet3/3/0/24 Ten-GigabitEthernet3/3/0/25 Ten-GigabitEthernet3/3/0/26

#

return

The output shows that the service module in slot 3 of member device 3 and its interfaces belong to mdcA.

2.     Reclaim the service module in slot 3 on member device 3 and its interfaces from mdcA.

[Sysname-mdc-2-mdcA]undo allocate interface GigabitEthernet 3/3/0/1 to GigabitEthernet 3/3/0/24 Ten-GigabitEthernet 3/3/0/25 Ten-GigabitEthernet 3/3/0/26

Configuration of the interfaces will be lost. Continue? [Y/N]:y

[Sysname-mdc-2-mdcA]undo location chassis 3 slot 3

[Sysname-mdc-2-mdcA]display this

#

mdc mdcA id 2

 mdc start

#

return

3.     Assign the service module in slot 3 on member device 3 and its interface to mdcB.

[Sysname] mdc mdcB

[Sysname-mdc-3-mdcB]allocate interface GigabitEthernet 3/3/0/1 to GigabitEthernet 3/3/0/24

Ten-GigabitEthernet 3/3/0/25 Ten-GigabitEthernet 3/3/0/26

Configuration of the interfaces will be lost. Continue? [Y/N]:y

 [Sysname-mdc-3-mdcB]location chassis 3 slot 3

[Sysname-mdc-3-mdcB]display this

#

mdc mdcB id 3

 location chassis 3 slot 3

 mdc start

 allocate interface GigabitEthernet3/3/0/1 to GigabitEthernet3/3/0/24  Ten-GigabitEthernet3/3/0/25 to Ten-GigabitEthernet3/3/0/26

#

return

[Sysname-mdc-3-mdcB]quit

[Sysname]display mdc interface

 MDC Admin's interface(s):

  M-GigabitEthernet1/0/0/0             FortyGigE3/4/0/1

  FortyGigE3/4/0/2                     FortyGigE3/4/0/3

  FortyGigE3/4/0/4                     FortyGigE3/5/0/1

  FortyGigE3/5/0/2                     FortyGigE3/5/0/3

  FortyGigE3/5/0/4

 

 MDC mdcA's interface(s):

  M-GigabitEthernet1/0/0/0

 

 MDC mdcB's interface(s):

  M-GigabitEthernet1/0/0/0             GigabitEthernet3/3/0/1

  GigabitEthernet3/3/0/2               GigabitEthernet3/3/0/3

  GigabitEthernet3/3/0/4               GigabitEthernet3/3/0/5

  GigabitEthernet3/3/0/6               GigabitEthernet3/3/0/7

  GigabitEthernet3/3/0/8               GigabitEthernet3/3/0/9

  GigabitEthernet3/3/0/10              GigabitEthernet3/3/0/11

  GigabitEthernet3/3/0/12              GigabitEthernet3/3/0/13

  GigabitEthernet3/3/0/14              GigabitEthernet3/3/0/15

  GigabitEthernet3/3/0/16              GigabitEthernet3/3/0/17

  GigabitEthernet3/3/0/18              GigabitEthernet3/3/0/19

  GigabitEthernet3/3/0/20              GigabitEthernet3/3/0/21

  GigabitEthernet3/3/0/22              GigabitEthernet3/3/0/23

  GigabitEthernet3/3/0/24              Ten-GigabitEthernet3/3/0/25

  Ten-GigabitEthernet3/3/0/26

4.     If the problem 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.

display diagnostic-information

Displays operating statistics for multiple feature modules in the system.

display license

Displays detailed license information.

display license feature

Displays brief license information for features.

display mdc resource

Displays CPU, disk space, and memory space usage of MDCs.

location

Assigns a service module to an MDC.

 

  • Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
All Support
  • Become a Partner
  • Partner Resources
  • Partner Business Management
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
新华三官网