HPE FlexNetwork 10500 SERIES Troubleshooting Manual

Troubleshooting Guide Part number: 5200-1913 Software version: 10500-CMW710-R7524 Document version: 6W100-20161230 The information in this document is subject to change without notice. © Copyright 2016 Hewlett Packard Enterprise Development LP

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 ········································································································ 6 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 ····················································· 13 Startup configuration file failure ··································································································· 13 Symptom ························································································································· 13 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 ··································································································· 16 Solution ··························································································································· 17 MPU boot failure ······················································································································ 17 Symptom ························································································································· 17 Troubleshooting flowchart ··································································································· 18 Solution ··························································································································· 18 Service module reboot failure ····································································································· 19 Symptom ························································································································· 19 Troubleshooting flowchart ··································································································· 19 Solution ··························································································································· 19 Service module boot failure ········································································································ 20 Symptom ························································································································· 20 Troubleshooting flowchart ··································································································· 21 Solution ··························································································································· 21 Unexpected card reboot ············································································································ 22 Symptom ························································································································· 22 Solution ··························································································································· 22 Operating power module failure ·································································································· 23 Symptom ························································································································· 23 Troubleshooting flowchart ··································································································· 23 Solution ··························································································································· 23 Newly installed power module failure ···························································································· 24 Symptom ························································································································· 24 Troubleshooting flowchart ··································································································· 25 Solution ··························································································································· 25 Fan tray failure ························································································································ 26 Symptom ························································································································· 26 Troubleshooting flowchart ··································································································· 26 Solution ··························································································································· 26 Related commands ·················································································································· 27

High CPU usage ······················································································································ 28 Symptom ························································································································· 28 Troubleshooting flowchart ··································································································· 28 Solution ··························································································································· 29 High memory usage ················································································································· 32 Symptom ························································································································· 32 Troubleshooting flowchart ··································································································· 32 Solution ··························································································································· 32 Temperature alarms ················································································································· 34 Symptom ························································································································· 34 Troubleshooting flowchart ··································································································· 34 Solution ··························································································································· 35 Related commands ·················································································································· 35 Troubleshooting ports ····································································· 35 10/100/1000Base-T copper port fails to come up ············································································ 35 Symptom ························································································································· 35 Troubleshooting flowchart ··································································································· 36 Solution ··························································································································· 36 1000-Mbps SFP fiber port fails to come up ···················································································· 37 Symptom ························································································································· 37 Troubleshooting flowchart ··································································································· 37 Solution ··························································································································· 37 10-Gigabit SFP+/XFP fiber port fails to come up ············································································· 40 Symptom ························································································································· 40 Troubleshooting flowchart ··································································································· 40 Solution ··························································································································· 41 40-GE QSFP+/CFP fiber port fails to come up ················································································ 41 Symptom ························································································································· 41 Troubleshooting flowchart ··································································································· 42 Solution ··························································································································· 42 100-GE CFP fiber port fails to come up ························································································· 43 Symptom ························································································································· 43 Troubleshooting flowchart ··································································································· 43 Solution ··························································································································· 43 A port goes down ····················································································································· 44 Symptom ························································································································· 44 Solution ··························································································································· 44 Port state flapping ···················································································································· 44 Symptom ························································································································· 44 Solution ··························································································································· 44 Transceiver module failure ········································································································· 45 Symptom ························································································································· 45 Solution ··························································································································· 45 Reporting non-HPE transceiver modules ······················································································· 47 Symptom ························································································································· 47 Troubleshooting flowchart ··································································································· 48 Solution ··························································································································· 48 Failure to support digital diagnosis on a transceiver module ······························································ 48 Symptom ························································································································· 48 Troubleshooting flowchart ··································································································· 49 Solution ··························································································································· 49 Error frames (for example, CRC errors) on a port ············································································ 49 Symptom ························································································································· 49 Troubleshooting flowchart ··································································································· 51 Solution ··························································································································· 51 Failure to receive or send packets ······························································································· 53 Symptom ························································································································· 53 Troubleshooting flowchart ··································································································· 54 Solution ··························································································································· 54

Troubleshooting IRF ······································································· 55 IRF fabric setup failure ·············································································································· 56 Symptom ························································································································· 56 Troubleshooting flowchart ··································································································· 57 Solution ··························································································································· 58 IRF split ································································································································· 60 Symptom ························································································································· 60 Troubleshooting flowchart ··································································································· 60 Solution ··························································································································· 60 BFD MAD failure ······················································································································ 61 Symptom ························································································································· 61 Troubleshooting flowchart ··································································································· 62 Solution ··························································································································· 62 LACP MAD failure ···················································································································· 64 Symptom ························································································································· 64 Troubleshooting flowchart ··································································································· 64 Solution ··························································································································· 64 PEX joining eIRF system failure ·································································································· 65 Symptom ························································································································· 65 Troubleshooting flowchart ··································································································· 66 Solution ··························································································································· 66 PEX split ································································································································ 71 Symptom ························································································································· 71 Troubleshooting flowchart ··································································································· 71 Solution ··························································································································· 71 Related commands ·················································································································· 72 Troubleshooting QoS and ACL ·························································· 72 ACL application failure for unsupported ACL rules ·········································································· 73 Symptom ························································································································· 73 Troubleshooting flowchart ··································································································· 73 Solution ··························································································································· 73 ACL application failure for insufficient resources ············································································· 73 Symptom ························································································································· 73 Troubleshooting flowchart ··································································································· 74 Solution ··························································································································· 74 ACL application failure without an error message ············································································ 75 Symptom ························································································································· 75 Troubleshooting flowchart ··································································································· 75 Solution ··························································································································· 75 Related commands ·················································································································· 76 Troubleshooting MDC ····································································· 76 Service module assignment failure ······························································································ 77 Symptom ························································································································· 77 Troubleshooting flowchart ··································································································· 77 Solution ··························································································································· 77 Interface assignment failure ······································································································· 79 Symptom ························································································································· 79 Troubleshooting flowchart ··································································································· 80 Solution ··························································································································· 80 Related commands ·················································································································· 82

problems with 10500 switches. This document applies to Release 10500-CMW710-R7524. General guidelines IMPORTANT: To prevent a problem from causing loss of configuration, save the configuration each time you finish configuring a feature. For configuration recovery, regularly back up the configuration to a remote server. 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: 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.

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). 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. 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. system-view [Sysname] switchto mdc mdc2 ****************************************************************************** * Copyright (c) 2010-2016 Hewlett Packard Enterprise Development LP * * Without the owner's prior written consent, * * no decompiling or reverse-engineering shall be allowed. * ****************************************************************************** logfile save The contents in the log file buffer have been saved to the file flash:/logfile/logfile.log switchback [Sysname] switchto mdc mdc3

* Without the owner's prior written consent, * * no decompiling or reverse-engineering shall be allowed. * ****************************************************************************** logfile save The contents in the log file buffer have been saved to the file flash:/logfile/logfile.log 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. dir flash:/logfile/ Directory of flash:/logfile 0 -rw- 213339 Nov 10 2014 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. 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. 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. 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 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) dir flash:/mdc/mdc3/logfile/ Directory of flash:/mdc/mdc3/logfile 0 -rw- 465 Jul 11 2013 16:10:39 logfile.log

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). 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. 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. system-view [Sysname] switchto mdc mdc2 ****************************************************************************** * Copyright (c) 2010-2016 Hewlett Packard Enterprise Development LP * * Without the owner's prior written consent, * * no decompiling or reverse-engineering shall be allowed. * ****************************************************************************** diagnostic-logfile save The contents in the diagnostic log file buffer have been saved to the file flash:/diagfile/diagfile.log switchback [Sysname] switchto mdc mdc3 ****************************************************************************** * Copyright (c) 2010-2016 Hewlett Packard Enterprise Development LP * * Without the owner's prior written consent, * * no decompiling or reverse-engineering shall be allowed. * ****************************************************************************** diagnostic-logfile save The contents in the diagnostic log file buffer have been saved to the file flash :/diagfile/diagfile.log 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. dir 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. 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. 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. 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 dir flash:/diagfile/ Directory of flash:/diagfile 0 -rw- 349 Jul 11 2013 16:21:38 diagfile.log 1021104 KB total (421352 KB free) 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.

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. screen-length disable 2. Collect operating statistics for multiple feature modules. 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_10500_20141110-142231.tar.gz]: flash:/diag.tar.gz Diagnostic information is outputting to flash:/diag.tar.gz. Please wait... Save successfully. 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=============== 16:52:51 UTC Tue 19/07/2016 ================================================= ===============display version=============== HPE Comware Software, Version 7.1.070, Release 7523P01 Copyright (c) 2010-2016 Hewlett Packard Enterprise Development LP HP 10504 uptime is 0 weeks, 0 days, 1 hour, 19 minutes Last reboot reason : USER reboot Boot image: flash:/10500-cmw710-boot-r7523P01.bin Boot image version: 7.1.070, Release 7523P01 Compiled Jul 15 2016 12:00:00 System image: flash:/10500-cmw710-system-r7523P01.bin System image version: 7.1.070, Release 7523P01 Compiled Jul 15 2016 12:00:00 ... Contacting technical support If you cannot resolve a problem after using the troubleshooting procedures in this document, contact Hewlett Packard Enterprise Support. When you contact an authorized Hewlett Packard Enterprise support representative, be prepared to provide the following information:

• 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 of Hewlett Packard Enterprise Support for networking products: http://www.hpe.com/support/hpesc 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. 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

console login password. 4. Configure password authentication for console login and set the password. You can also configure a different login authentication mode. 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. 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: • 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. display current-configuration # version 7.1.070, Release 7523P01 # mdc Admin id 1 # sysname Sysname #

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 : Dec 9 2014 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 : 000A EXTENDED CPLD Version : 003 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: Note: The current operating device is flash Enter < Storage Device Operation > to select device. ====================================================

|<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: ==================================================== |<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. system-view [Sysname] line aux 1/1 [Sysname-line-aux1/1] authentication-mode password [Sysname-line-aux1/1] set authentication password simple 12345678

Enter < Storage Device Operation > to select device. ==================================================== |<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: ==================================================== |<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...

The Extend BootWare is self-decompressing................................. Done. After the device starts up, configure a new console login password. You can also configure a different login authentication mode. 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 6. Save the running configuration to use the configuration at the next reboot. 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. 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. 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.

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: 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. 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. 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. startup saved-configuration config.cfg 3. Reboot the device. 4. If the problem persists, contact Hewlett Packard Enterprise Support.

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 HPE FlexNetwork 10500 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.  Parity—None.  Stop bits—1.  Flow control—None.  Emulation—VT100. 5. Verify that the console cable is in good quality and is operating correctly. 6. If the problem persists, contact Hewlett Packard Enterprise Support.

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.  Parity—None.  Stop bits—1.  Flow control—None.  Emulation—VT100. 2. If the problem persists, contact Hewlett Packard Enterprise Support. MPU reboot failure Symptom An MPU fails to reboot. The RUN and ALM LEDs for the MPU are on. Troubleshooting flowchart Figure 1 Troubleshooting MPU reboot failure Contact the support MPU reboot failure No Yes No Yes No Yes Yes No Error continues to be reported? Resolved? Yes Yes No No Reinstall the MPU securely MPU memory runs correctly? System software image correct Replace the MPU Reload the system software image Resolved? Resolved? End

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 Hewlett Packard Enterprise Support. MPU boot failure Symptom An MPU designated as the standby MPU fails to boot after installation. The RUN and ALM LEDs for the MPU are on.

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 Newly installed standby MPU boot failure Same model as the active MPU? Replace the standby MPU Resolved? Same software version as the active MPU Upgrade the standby MPU Resolved? Contact the support End No No No Yes No Yes Yes Yes New MPU installed securely? Remove and reinstall the MPU Resolved? No No Yes Power sufficient? Add power modules Resolved? No No Yes Yes Yes

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 Hewlett Packard Enterprise Support. Service module reboot failure Symptom A service module fails to reboot. The RUN and ALM LEDs for the service module are on. 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. display boot-loader Software images on slot 1: Current software images: flash:/10500-CMW710-BOOT-R7524.bin flash:/10500-CMW710-SYSTEM-R7524.bin Loading records about the service module exist? System software image on the MPU correct? Another service module boots successfully in the slot? Replace the MPU No Yes No Yes No Yes Yes No No Yes Yes No Contact the support Service module reboot failure End Install the service module into another slot Reload the system software image Resolved? Resolved? Resolved?

flash:/10500-CMW710-BOOT-R7524.bin flash:/10500-CMW710-SYSTEM-R7524.bin Main startup software images: flash:/10500-CMW710-BOOT-R7524.bin flash:/10500-CMW710-SYSTEM-R7524.bin Main startup software images: flash:/10500-CMW710-BOOT-R7524.bin flash:/10500-CMW710-SYSTEM-R7524.bin Backup startup software images: None 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 10500-cmw710-boot-R7524.bin 6 -rw- 178325504 Dec 22 2013 14:39:02 10500-cmw710-system-R7524.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. display logbuffer %May 3 13:27:17:086 2013 HPE DEVM/4/BOARD_LOADING: Board is loading file on Chassis 1 Slot 7. %May 3 13:27:17:647 2013 HPE 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 Hewlett Packard Enterprise Support. Service module boot failure Symptom A newly-installed service module fails to boot. The RUN and ALM LEDs for the service module are on.

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. display boot-loader Software images on slot 1: Current software images: flash:/10500-CMW710-BOOT-R7524.bin flash:/10500-CMW710-SYSTEM-R7524.bin Main startup software images: flash:/10500-CMW710-BOOT-R7524.bin flash:/10500-CMW710-SYSTEM-R7524.bin System software image on the MPU correct? System software image supports the module? Reload the system software image Resolved? Upgrade the system software image Contact the support Newly installed service module boot failure No Yes No Yes Resolved? No Yes Yes No End Another module boots successfully in the slot? Replace the MPU Resolved? No Yes Yes No Loading records about the module exists? Install the module into another slot Resolved? Yes Yes No No Installed securely? Remove and reinstall the module Resolved? No No Yes Power sufficient? Add power modules Resolved? No No Yes Yes Yes

None 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 10500-cmw710-boot-R7524.bin 6 -rw- 178325504 Dec 22 2013 14:39:02 10500-cmw710-system-R7524.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 HPE DEVM/4/BOARD_LOADING: Board is loading file on Chassis 1 Slot 7. %May 3 13:27:17:647 2013 HPE 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 Hewlett Packard Enterprise 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.

HPE Comware Software, Version 7.1.070, Release 7523P01 Copyright (c) 2010-2016 Hewlett Packard Enterprise Development LP HP 10504 uptime is 0 weeks, 0 days, 2 hours, 11 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. If the problem persists, contact Hewlett Packard Enterprise Support. Operating power module failure Symptom An operating power module fails. On the MPU, the PWR OK LED is off and the PWR FAIL LED is on. 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. display power The power module in Absent state? Power cord connected securely? Remove and reinstall the power module Resolved? Operating power module failure Yes No No Yes Resolved? No Yes Yes No The temperature too high? Make sure the temperature is in the acceptable range Resolved? Yes Yes No No Contact the support End Connect the power cord securely

Power 1 State: Absent Power 2 State: Absent Power 3 State: Absent  Execute the display alarm command to view alarm information about the power module. display alarm Slot CPU Level Info - - INFO Power 1 is absent. - - INFO Power 2 is absent. - - INFO Power 3 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. display power Power 0 State: Normal Power 1 State: Absent Power 2 State: Absent Power 3 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 Hewlett Packard Enterprise Support. Newly installed power module failure Symptom A newly installed power module fails. On the MPU, the PWR OK LED is off and the PWR FAIL LED is on.

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. display power Power 0 State: Normal Power 1 State: Absent Power 2 State: Absent Power 3 State: Absent  Execute the display alarm command to view alarm information about the power module. display alarm Chassis Slot CPU Level Info 2 - - INFO power 1 is absent. 2 - - INFO power 2 is absent. 2 - - INFO power 3 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. The power module in Absent state? Power cord connected securely? Remove and reinstall the power module Resolved? Newly installed power module failure Yes No No Yes Resolved? No Yes Yes No Contact the support End Connect the power cord securely

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 Hewlett Packard Enterprise Support. Fan tray failure Symptom An operating fan tray or a newly installed fan tray fails. On the MPU, the FAN OK LED is off and the FAN FAIL LED is on. Troubleshooting flowchart Figure 7 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. display fan Fan Frame 0 State: Normal  Execute the display alarm command to view alarm information about the fan tray. 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. The fan tray in Absent state? The fan tray in Fault state? Remove and reinstall the fan tray Resolved? An operating or a newly installed fan tray failure Yes No No Yes Resolved? Yes Yes No No Contact the support End Replace the fan tray

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. − Execute the debug sysm fan fan-id get-speed command in probe view to view the fan speed information. If the fan speed is less than 500 rpm, 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 Hewlett Packard Enterprise Support. Related commands This section lists the commands that you might use for troubleshooting the hardware. Command Description debug sysm fan fan-id get-speed Displays fan speed information. 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.

Symptom The sustained CPU usage is over 80% on a card. Troubleshooting flowchart Figure 8 Troubleshooting high CPU usage High CPU usage Route flapping problem? Verify that the device is not being attacked Verify that no link loops exist Problem resolved? Problem resolved? Locate the card that has a high CPU resource usage Identify the job that has a high CPU usage Display the job's stack Contact the support End N Y N N Y Y

• 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. 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 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 Hewlett Packard Enterprise 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: [] schedule+0x570/0xde0 [] schedule_timeout+0x98/0xe0 [] ep_poll+0x4b4/0x5e0 [] DRV_Sal_EVENT_Read+0x1f8/0x290 [system] [] drv_sysm_gdb_console+0xc4/0x2d0 [system] [] thread_boot+0x84/0xa0 [system] [] kthread+0x130/0x140 [] kernel_thread_helper+0x10/0x20 Iteration 2 of 5 ------------------------------ Kernel stack: [] schedule+0x570/0xde0 [] schedule_timeout+0x98/0xe0 [] ep_poll+0x4b4/0x5e0

[] drv_sysm_gdb_console+0xc4/0x2d0 [system] [] thread_boot+0x84/0xa0 [system] [] kthread+0x130/0x140 [] kernel_thread_helper+0x10/0x20 Iteration 3 of 5 ------------------------------ Kernel stack: [] schedule+0x570/0xde0 [] schedule_timeout+0x98/0xe0 [] ep_poll+0x4b4/0x5e0 [] DRV_Sal_EVENT_Read+0x1f8/0x290 [system] [] drv_sysm_gdb_console+0xc4/0x2d0 [system] [] thread_boot+0x84/0xa0 [system] [] kthread+0x130/0x140 [] kernel_thread_helper+0x10/0x20 Iteration 4 of 5 ------------------------------ Kernel stack: [] schedule+0x570/0xde0 [] schedule_timeout+0x98/0xe0 [] ep_poll+0x4b4/0x5e0 [] DRV_Sal_EVENT_Read+0x1f8/0x290 [system] [] drv_sysm_gdb_console+0xc4/0x2d0 [system] [] thread_boot+0x84/0xa0 [system] [] kthread+0x130/0x140 [] kernel_thread_helper+0x10/0x20 Iteration 5 of 5 ------------------------------ Kernel stack: [] schedule+0x570/0xde0 [] schedule_timeout+0x98/0xe0 [] ep_poll+0x4b4/0x5e0 [] DRV_Sal_EVENT_Read+0x1f8/0x290 [system] [] drv_sysm_gdb_console+0xc4/0x2d0 [system] [] thread_boot+0x84/0xa0 [system] [] kthread+0x130/0x140 [] kernel_thread_helper+0x10/0x20 7. Save the information displayed in the previous steps. 8. Contact Hewlett Packard Enterprise Support.

Symptom The memory usage on a card is over 60% for more than 30 minutes. Troubleshooting flowchart Figure 9 Troubleshooting high memory usage Solution IMPORTANT: As a best practice, do not reboot the device before you contact Hewlett Packard Enterprise 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 Display memory usage information Display memory call information Contact the support High memory usage

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

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 Hewlett Packard Enterprise Support. Temperature alarms Symptom Temperature alarms occur. Troubleshooting flowchart Figure 10 Troubleshooting temperature alarms End Temperature alarms Device temperature too high? N Problem resolved? Y Fan tray operating correctly? Remove the fan tray and install it again N Problem resolved? Air filters clean? Clean the air filters N Problem resolved? Contact the support N Y Y Identify the card that has temperature alarms Adjust the card’s temperature alarm thresholds N Y Problem resolved? Y Y N N Ambient temperature too high? N Y Y Lower the ambient temperature Problem resolved? Y N

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 Hewlett Packard Enterprise 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//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.

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 Hewlett Packard Enterprise Support. Speed/duplex match on local and peer port? Network cable correct? Configure matching speed/duplex Resolved? Replace network cable Contact the support A port fails to come up No Yes No Yes Resolved? No Yes Yes No End Local port operating correctly? Replace local port Resolved? No Yes Yes No Peer port operating correctly? Replace peer port Resolved? No Yes Yes No

Symptom A 1000-Mbps SFP fiber 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. Speed/duplex match on local and peer port? Speed/duplex match on transceiver module and port? Configuring matching speed/duplex Resolved? Configuring matching speed/duplex A port fails to come up No Yes No Yes Resolved? No Yes Yes No Transceiver module correct? Replace transceiver module Resolved? No Yes Yes No Fiber correct? Replace fiber Resolved? No Yes Yes No Contact the support End Local port correct? Replace local port Resolved? No Yes Yes No Peer port correct? Replace peer port Resolved? No Yes Yes No

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

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

10-Gigabit SFP+/XFP fiber port fails to come up Symptom A 10-Gigabit SFP+/XFP fiber port cannot come up. Troubleshooting flowchart Figure 13 Troubleshooting link up failure on a port No Yes No Yes No Yes Yes No No Yes Yes No No Yes Yes No No Yes Yes No A 10-GE SFP+/XFP fiber port fails to come up Contact the support Resolved? Speed/duplex match on local and peer port? Speed/duplex match on transceiver module and port? Local/peer port operating correctly? Transceiver module/cable correct? Fiber correct? Configure matching speed/duplex Configure matching speed/duplex Replace local/peer port Replace transceiver module/cable Replace fiber Resolved? Resolved? Resolved? Resolved? End

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 HPE 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 Hewlett Packard Enterprise Support. 40-GE QSFP+/CFP fiber port fails to come up Symptom A 40-Gigabit QSFP+/CFP fiber port cannot come up.

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 HPE transceiver module that matches the fiber port. For more information about transceiver modules, see related installation guides. Local/peer port correct? Replace local/peer port Resolved? A 40-GE QSFP+/CFP fiber port fails to come up No Yes No Yes Transceiver module/cable correct? Replace transceiver module/cable Resolved? No Yes Yes No Fiber correct? Replace fiber Resolved? No Yes Yes No Contact the support End

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 Hewlett Packard Enterprise Support. 100-GE CFP fiber port fails to come up Symptom A 100-GE 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 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. A 100-GE CFP fiber port fails to come up Replace transceiver module Replace fiber Yes Yes No No End Yes Yes No No Transceiver module correct? Fiber correct? Resolved? Resolved? Contact the support Local port correct? Replace local port Resolved? No Yes Yes No Peer port correct? Replace peer port Resolved? No Yes Yes No

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 HPE transceiver module that matches the fiber port. For more information about transceiver modules, see related installation guides. 2. 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. 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 Hewlett Packard Enterprise Support. A port goes down Symptom A port goes 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 Hewlett Packard Enterprise 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.

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 Hewlett Packard Enterprise 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. 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 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. display transceiver diagnosis interface Ten-GigabitEthernet1/2/0/15 transceiver diagnostic information: Current diagnostic parameters:

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. 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 : FINISAR CORP. 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 Hewlett Packard Enterprise Support. Reporting non-HPE transceiver modules Symptom When you use the display logbuffer command to view the system logs, the following reports about non-HPE transceiver modules appear in the system logs: 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 HPE. HPE therefore shall NOT guarantee the normal function of the device or assume the maintenance responsibility thereof!

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 HPE, the transceiver module might be an HPE transceiver module without an electrical label or a non-HPE transceiver module. b. If the Vendor Name field is not HPE, you can determine that this is not an HPE transceiver module. Replace it with an HPE transceiver module. 2. Contact Hewlett Packard Enterprise Support to determine whether the transceiver module vendor is HPE: 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 Hewlett Packard Enterprise Support to identify the vendor of the transceiver module. b. If you determine that the transceiver module vendor is not HPE, replace it with an HPE transceiver module. 3. If the transceiver module vendor is identified as HPE but the problem persists, contact Hewlett Packard Enterprise 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. Is the vendor name HPE? HPE transceiver module? Replace it with an HPE transceiver module Replace it with an HPE transceiver module No Yes No Yes No Yes Yes No Resolved? Contact the support Non-HPE transceiver module reported in system logs End Resolved?

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 HPE: a. Use the display transceiver interface command to display the transceiver information. b. Determine whether the value of the Vendor Name field is HPE. c. Use the display transceiver manuinfo interface command to collect the transceiver module information. Send the bar code of the transceiver module to Hewlett Packard Enterprise Support to verify that the vendor of the transceiver module is HPE. 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 Hewlett Packard Enterprise Support about whether the transceiver module supports digital diagnosis. 3. If the transceiver module vendor is identified as HPE and the transceiver module supports digital diagnosis but the problem persists, contact Hewlett Packard Enterprise 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. Transceiver module Supports digital diagnosis? Replace it with an HPE transceiver module System prompted that the transceiver module does not support digital diagnosis No Yes No Yes No Yes Contact the support End Resolved? HPE transceiver module?

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

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 it with a transceiver module with correct optical power Optical power of transceiver module correct? Determine the type of error frames accumulating Yes Configure matching speed and duplex No No Yes Use correct port and link medium No Yes No No No View the number of received flow control frames Yes Yes Yes Contact the support End Error frames on the port Resolved? Speed and duplex match the peer port? Port and link medium correct? Resolved? Resolved? No

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

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 Hewlett Packard Enterprise Support. Failure to receive or send packets Symptom A port is up, but it cannot receive or send 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 A port fails to receive or send packets Modify port configurations End Port configurations affect packet receiving or sending? Resolved? Contact the support Port and link medium correct? Yes Use correct port and link medium Resolved No No Yes View packet statistics of the port No No Yes Yes

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 Hewlett Packard Enterprise 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.

Chassis in IRF mode? Same IRF operating mode? Enable IRF mode Set the chassis to operate in the same IRF mode as the member chassis in the IRF fabric No Yes No Yes Physical IRF connections correct? Modify IRF port bindings or reconnect IRF physical interfaces No Yes Remove the duplicate MAC condition Yes Bridge MAC unique? IRF setup failure Resolved? Resolved? Resolved? Resolved? No No No No Yes Yes Yes Same chassis model? Replace with a chassis that is the same model as existing IRF member chassis No Yes Resolved? No Yes IRF links up? Remove link failure conditions to bring up the IRF links No Yes Resolved? No Yes Same software version? Upgrading the MPUs with the software version running on the IRF fabric No Yes Resolved? No Yes Yes Member ID unique? Assign a unique member ID to the chassis No Yes Resolved? No Yes No Number of chassis in the fabric fewer than the upper limit? You cannot add the chassis to the IRF fabric No Yes Same system operating mode? Set the chassis to operate in the same mode as the member chassis in the fabric Resolved? Yes Contact the support Same maximum number of ECMP routes? Yes No No End No Set the chassis to have the same maximum number of ECMP routes as the member chassis in the IRF fabric Resolved? Yes Yes

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 HPE FlexNetwork 10500 Switch Series Virtual Technologies Configuration Guide for the software version. 2. Verify that the chassis is a 10500 switch. The 10500 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 physical IRF links are connected correctly: 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.

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. 7. 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 HPE FlexNetwork 10500 Switch Series Virtual Technologies Configuration Guide. 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. 8. 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. 9. 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. 10. 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.

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. 11. 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. 12. If the problem persists, contact Hewlett Packard Enterprise 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. End IRF fabric splits Contact the support Member chassis or module that has IRF links rebooted? Identify the cause and resolve the problem Yes No Resolved? No Yes IRF physical interfaces down? Identify the cause and resolve the problem Yes No Resolved? No Yes

diagnosis command. Make sure the transmit and receive power has not exceeded the power specifications of the fiber module. d. Remove hardware problems that might cause recurring IRF split events: e. Execute the display version command to identify the uptime of MPUs and interface modules that have IRF links. f. Compare the uptime of MPUs and interface modules to determine whether a member chassis or interface module had rebooted before the IRF split. g. 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. 2. If the problem persists, contact Hewlett Packard Enterprise 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.

Solution To resolve the problem: 1. Verify that BFD MAD link connections are correct: BFD MAD VLAN and ports configured correctly? No Yes BFD MAD failure No Yes BFD MAD VLAN interface configured correctly? No Yes No Yes BFD MAD link connections correct? Correct the connections No Yes No Yes BFD MAD VLAN unique in a multi-IRF fabrics network? No No Yes Yes BFD MAD ports always up? No No Yes Yes No No Yes Yes All BFD MAD ports up? No No Yes Yes BFD MAD IP addresses configured correctly? Bring up the ports Correct the settings Correct the settings Correct the BFD MAD IP address settings Assign each IRF fabric a unique BFD MAD VLAN Identify port-down event cause and remove the issue End Resolved? Resolved? Resolved? Resolved? Resolved? Resolved? Resolved? Contact the support

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 Hewlett Packard Enterprise Support.

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 HPE device that supports extended LACPDUs for MAD. No No Yes No Yes No Yes No Yes No Yes No Yes Yes No No Yes Yes No No Yes Yes Yes No Replace the device or use BFD MAD for detection Intermediate device supports extended LACPDUs for MAD? Resolved? Each member has a link to the intermediate device? Correct the connections Resolved? Dynamic aggregation mode used? Enable dynamic aggregation mode for the aggregate interface Resolved? Aggregate interface and its member ports all up? Bring up the aggregate interface and all its member ports Resolved? IRF domain ID unique? Assign a unique domain ID to the IRF fabric Resolved? Member ports in the link aggregation always up? Identify port-down event cause and remove the issue Resolved? End Contact the support LACP MAD failure

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: 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 Hewlett Packard Enterprise Support. PEX joining eIRF system failure Symptom A device fails to join an eIRF system as a PEX.

Solution To resolve the problem: 1. Verify that you can use the device as a PEX. The following switches can be used as PEXs for the 10500 switch: A device failed to join an eIRF system as a PEX Number of PEXs fewer than the upper limit in the eIRF system? Change the IRF operating mode or give up the adding attempt Resolved? Is the device’s Boot ROM PEX capable? Upgrade the Boot ROM of the device to a PEX-capable version Resolved? Is the device operating in PEX mode? Change the operating mode to PEX Resolved? End No No No No No Yes Yes No Yes Yes Yes Yes Is eIRF capability enabled on the parent fabric? Is the device PEX capable? Is PEX startup software images specified? PEX links up? Specify PEX startup software images for the device on the parent fabric Resolved? Bring up the PEX links Resolved? Strictly follow the binding restrictions and guidelines to bind and connect PEX physical interfaces Resolved? No No No Yes Yes Yes Yes Yes No No No The device cannot join the eIRF system as a PEX Enable eIRF capability on the parent fabric Yes Yes No No Yes Resolved? No Contact the support Are PEX port bindings correct?

2. Verify that eIRF capability is enabled on the parent fabric: a. Execute the display irf command and check the IRF mode field for eIRF capability status. b. If the field displays normal, execute the irf mode command to enable light IRF mode or enhanced IRF mode. Make sure all modules can correctly operate in the IRF mode. 3. Verify that the number of PEXs in the eIRF system does not exceed the upper limit. The maximum number of PEXs in an eIRF system varies by PEX model and IRF mode.  In light IRF mode, the eIRF system can contain a maximum of 30 PEXs.  In enhanced IRF mode, the eIRF system can contain a maximum of 60 PEXs. 4. Verify that the Boot ROM of the device is PEX capable from the device's release notes. If the Boot ROM does not support PEX, upgrade the Boot ROM to a PEX-capable version. For more information, see software upgrade in HPE FlexNetwork 10500 Switch Series Fundamentals Configuration Guide. 5. Verify that the device is operating in PEX mode: a. Reboot the device and press Ctrl+B at the prompt. If you have set a Boot menu password, you must enter the correct password to access the Extended Boot menu. Starting...... Press Ctrl+D to access BASIC BOOT MENU ****************************************************************************** * * * HP FF 5700-40XG-2QSFP+ Switch BOOTROM, Version 150 * * * ****************************************************************************** Copyright (c) 2010-2016 Hewlett-Packard Development Company, L.P. Creation Date : Jan 12 2016,19:17:00 CPU Clock Speed : 1000MHz Memory Size : 2048MB Flash Size : 512MB CPLD Version : 002/002 PCB Version : Ver.B Mac Address : 70F96D44F89A PEX mode is disabled. Press Ctrl+B to access EXTENDED BOOT MENU...0 Password recovery capability is enabled. b. If PEX mode is disabled, press Ctrl+Y to change the operating mode to PEX. BOOT MENU 1. Download application file to flash 2. Select application file to boot 3. Display all files in flash 4. Delete file from flash 5. Restore to factory default configuration 6. Enter BootRom upgrade menu 7. Skip current system configuration 8. Reserved

0. Reboot Ctrl+F: Format File System Ctrl+P: Skip Super Password Ctrl+Y: Change Work Mode Ctrl+R: Download application to SDRAM and Run Ctrl+Z: Access EXTEND-ASSISTANT MENU Enter your choice(0-9): 0 c. Enter Y to confirm the operating mode change. PE mode is disabled. Are you sure you want to enable PE mode? [Y/N]Y Done! d. Enter 0 in the Extended Boot menu to reboot the device. At startup, the device loads the startup images from the parent fabric. While the device is starting up, the parent fabric displays messages about PEX port state changes, PEX registration, and PEX startup. 6. Verify that you have specified the PEX startup software images for the device on the parent fabric: a. Execute the display boot-loader pex command and check the PEX startup software images for the device. b. If no PEX startup software images are specified for the device, use FTP or TFTP to transfer the PEX startup software images of the device to the parent fabric. NOTE: You must store the image file in the root directory of a flash memory on the parent fabric. c. Specify the file as the startup image file for the device. This example provides the following methods: boot-loader pex PEX-5700 file ipe flash:/5700PEX.ipe main Verifying the IPE file and the images....Done. Decompressing file 5700pex-10500-cmw710-boot-r7523P01.bin to flash:/ 5700pex-10500-cmw710-boot-r7523P01.bin.....................Done. Decompressing file 5700pex-10500-cmw710-system-r7523P01.bin to flash:/ 5700pex-10500-cmw710-system-r7523P01.bin...................................... ......................................................................Done. d. Verify the result. display boot-loader pex Startup software image files for PEXs to load from the parent device: PEX model: PEX-5120HI None PEX model: PEX-5700 flash:/5700pex-10500-cmw710-boot-r7523P01.bin flash:/5700pex-10500-cmw710-system-r7523P01.bin 7. Verify that the PEX links are up: a. Execute the display interface pex command. display interface Pex Pex101/0/0/29 Current state: UP

IP packet frame type: Ethernet II, hardware address: 5cdd-70b2-8758 Description: Pex101/0/0/29 Interface Bandwidth: 10000000 kbps Loopback is not set Media type is optical fiber, port hardware type is 10G_BASE_SR_SFP 10Gbps-speed mode, full-duplex mode Link speed type is autonegotiation, link duplex type is autonegotiation Maximum frame length: 9216 MDI type: Automdix Last clearing of counters: Never Peak input rate: 5635 bytes/sec, at 2016-03-06 03:53:32 Peak output rate: 4555 bytes/sec, at 2016-03-06 03:53:58 Last 300 second input: 8 packets/sec 1433 bytes/sec 0% Last 300 second output: 7 packets/sec 1624 bytes/sec 0% Input (total): 18619 packets, 3705456 bytes 11023 unicasts, 0 broadcasts, 7596 multicasts, 0 pauses Input (normal): 18619 packets, - bytes 11023 unicasts, 0 broadcasts, 7596 multicasts, 0 pauses Input: 0 input errors, 0 runts, 0 giants, 0 throttles 0 CRC, 0 frame, - overruns, 0 aborts - ignored, - parity errors Output (total): 17300 packets, 3250852 bytes 12468 unicasts, 0 broadcasts, 4832 multicasts, 0 pauses Output (normal): 17300 packets, - bytes 12468 unicasts, 0 broadcasts, 4832 multicasts, 0 pauses Output: 0 output errors, - underruns, - buffer failures 0 aborts, 0 deferred, 0 collisions, 0 late collisions 0 lost carrier, - no carrier Pex101/0/0/30 Current state: DOWN Line protocol state: DOWN IP packet frame type: Ethernet II, hardware address: 5cdd-70b2-8759 Description: Pex101/0/0/30 Interface Bandwidth: 10000000 kbps Loopback is not set Media type is not sure, port hardware type is no connector Unknown-speed mode, unknown-duplex mode Link speed type is autonegotiation, link duplex type is autonegotiation Maximum frame length: 9216 MDI type: Automdix Last clearing of counters: Never Peak input rate: 0 bytes/sec, at 2016-03-06 03:49:23 Peak output rate: 0 bytes/sec, at 2016-03-06 03:49:23 Last 300 second input: 0 packets/sec 0 bytes/sec -% Last 300 second output: 0 packets/sec 0 bytes/sec -% Input (total): 0 packets, 0 bytes

Input (normal): 0 packets, - bytes 0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses Input: 0 input errors, 0 runts, 0 giants, 0 throttles 0 CRC, 0 frame, - overruns, 0 aborts - ignored, - parity errors Output (total): 0 packets, 0 bytes 0 unicasts, 0 broadcasts, 0 multicasts, 0 pauses Output (normal): 0 packets, - bytes 0 unicasts, 0 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 b. Check the Current state field for link down events: − If the field displays DOWN ( Administratively ), execute the undo shutdown command to bring up the PEX physical interface. − If the field displays DOWN, verify that SFP+ or QSFP+ transceiver modules or DAC cables are used for PEX links and that they are operating correctly. Do not use DAC cables to connect 40-GE ports for PEX links. NOTE: The 10500 switch might support transceiver modules or DAC cables that provide higher speed than SFP+ or QSFP+, depending on the software version and interface module model. For more information, see the latest HPE FlexNetwork 10500 Switch Series Virtual Technologies Configuration Guide. 8. Verify that the PEX physical interface connections and bindings are correct. a. Verify that the physical interfaces connected to PEXs are PEX capable. The following table shows the available PEX physical interfaces: Switch model Candidate PEX physical interfaces 10500 (parent) Use the 10-GE and 40-GE ports on the following modules for PEX links: • EC interface module: LSUM1TGS24EC0(JH194A, JH202A). • SF interface modules:  LSU1QGS8SF0(JG392A, JG393A).  LSU1TGS32SF0(JC755A, JG344A).  LSUM2TGS16SF0(JH193A, JH201A). • SG interface modules. 5700-40XG-2QSFP+ Use the following physical interfaces to connect to the parent fabric: • The 10-GE ports 37 through 40 on the front panel. • The 40-GE ports 41 and 42 on the front panel. 5700-32XGT-8XG-2QSFP+ The 40-GE ports 41 and 42 on the front panel. 5700-48G-4XG-2QSFP+ Use the following physical interfaces to connect to the parent fabric: • The 10-GE ports 49 through 52 on the front panel. • The 40-GE ports 53 and 54 on the front panel.

restrictions and guidelines: − If ports in a group are used, you must use all or none of the ports for PEX links. The ports can be assigned to different PEX ports. To shut down or bring up any ports in the group, you must make sure all the ports have been assigned to or removed from PEX ports. − The breakout interfaces of a 40-GE port are considered to be in a port group. You must follow the binding restrictions for port groups. − On PEXs, do not use both 10-GE and 40-GE ports to connect to the parent fabric. − On PEXs, you must use transceiver modules for 40-GE ports on PEX links. − On PEXs, the breakout interfaces of a 40-GE port cannot be connected to the parent fabric. For more information about the binding and connection restrictions, see HPE FlexNetwork 10500 Switch Series Virtual Technologies Configuration Guide. 9. If the problem persists, contact Hewlett Packard Enterprise Support. PEX split Symptom One or multiple PEXs split from an eIRF system. Troubleshooting flowchart Figure 25 Troubleshooting PEX split Solution To resolve the problem: 1. Verify that the PEX physical interfaces are operating correctly: a. Execute the display trapbuffer command or view system logs to check for physical PEX link down events that occurred around the split time. b. If the split followed a PEX link down event, execute the display interface command to check port statistics for CRC errors. PEXs left eIRF system PEX physical interfaces down? Identify the cause and resolve the problem Resolved? Device or module that has PEX links rebooted? Identify the cause and resolve the problem Resolved? Contact the support End Yes No No No Yes No Yes Yes

diagnosis command. Make sure the transmit and receive power has not exceeded the power specifications of the fiber module. d. Remove hardware problems that might cause recurring PEX split events: e. Execute the display version command to identify the uptime of devices or interface modules that have PEX links. f. Compare the uptime of devices or interface modules to determine whether a device or interface module had rebooted before the PEX split. g. If the PEX split is caused by a reboot, use the methods described in "Troubleshooting hardware" to resolve the problem. 2. If the problem persists, contact Hewlett Packard Enterprise Support. Related commands This section lists the commands that you might use for troubleshooting IRF: Command Description display boot-loader pex Displays PEX startup software images. 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 interface pex Displays PEX physical 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 pex-port Displays information about PEX ports. 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 QoS and ACL This section provides troubleshooting information for common QoS and ACL problems.

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 26 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 Hewlett Packard Enterprise 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. Rule unsupported? Delete the unsupported rule Problem resolved? Failure to apply an ACL Yes No Yes Contact the support End No

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% Hardware resources are sufficient? Delete unnecessary ACLs Resolved? Failure to apply an ACL Yes No No Yes Contact the support End

 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 Hewlett Packard Enterprise 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 28 Troubleshooting ACL application failure Solution To resolve the problem: 1. Check the ACLs used by QoS policies and packet filters for overlapping rules: Overlapping ACLs exist? Yes No No Yes Conflicting behaviors for packets matching overlapping ACLs? Revise ACLs/packet filters/QoS policies Yes No Resolved? Contact the support End Failure to apply an ACL

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 Hewlett Packard Enterprise 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.

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: Service module assignment failure Resources sufficient? Re-assign resources Resolved? The module belongs to another MDC? Reclaim the module Resolved? Contact the support End No No No Yes Yes No Yes Yes

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

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 Hewlett Packard Enterprise 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.

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 Interface assignment failure Interfaces assigned to another MDC? Reclaim the service module and its interfaces from the MDC and re-assign them Resolved? All interfaces on the service module assigned to the same MDC? Assign all interfaces on the service module to the same MDC Resolved? Contact the support End Yes No No No No Yes Yes Yes Display interfaces of MDCs

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

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 Hewlett Packard Enterprise 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 mdc resource Displays CPU, disk space, and memory space usage of MDCs. location Assigns a service module to an MDC.