HPE FlexNetwork 10500 SERIES User manual

HPE FlexNetwork 10500 Switch Series
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

i
Contents
Introduction·····················································································1
General guidelines ·····················································································································1
Collecting log and operating information ·························································································1
Collecting common log messages···························································································2
Collecting diagnostic log messages·························································································4
Collecting operating statistics·································································································5
Contacting technical support ········································································································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

ii
Troubleshooting system management ················································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

iii
Related commands ··················································································································55
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

1
Introduction
This document provides information about troubleshooting common software and hardware
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:
B
y 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 aconsistent
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.

2
Table 1 Log and operating information
Category
File name format
Content
Common log
logfile.log
Command execution and operational log messages.
Diagnostic log diagfile.log
Diagnostic log messages about device operation, including the
following items:
•Parameter settings in effect when an error occurs.
•Information about a card startup error.
•Handshaking information between the MPU and interface
module when a communication error occurs.
Operating
statistics file-basename.gz
Current operating statistics for feature modules, including the
following items:
•Device status.
•CPU status.
•Memory status.
•Configuration status.
•Software entries.
•Hardware entries.
Collecting common log messages
1. Save common log messages from the log buffer to a log file:
By default, the log file is saved in the logfile directory of the flash memory on theactive MPU (in
standalone mode) or global active MPU (in IRF mode).
# Save log messages to the log file on the default MDC (Admin).
<Sysname> logfile save
The contents in the log file buffer have been saved to the file
flash:/logfile/logfile.log
# Identify non-default MDCs created on the device.
<Sysname> display mdc
ID Name Status
---------------------------------
1 Admin active
2 mdc2 active
3 mdc3 active
# Save log messages to the log file on each non-default MDC.
<Sysname> system-view
[Sysname] switchto mdc mdc2
******************************************************************************
* Copyright (c) 2010-2016 Hewlett Packard Enterprise Development LP *
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<HPE> logfile save
The contents in the log file buffer have been saved to the file
flash:/logfile/logfile.log
<HPE> switchback
[Sysname] switchto mdc mdc3

3
******************************************************************************
* Copyright (c) 2010-2016 Hewlett Packard Enterprise Development LP *
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<HPE> logfile save
The contents in the log file buffer have been saved to the file
flash:/logfile/logfile.log
<HPE> switchback
2. On the default MDC, identify the log file on each MPU for each MDC:
# Display the log file on the active MPU (in standalone mode) or global active MPU (in IRF
mode) for the default MDC.
<Sysname> dir flash:/logfile/
Directory of flash:/logfile
0 -rw-213339 Nov 10 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.
<Sysname> dir slot1#flash:/logfile/
Directory of slot1#flash:/logfile
0 -rw-21863 Jul 11 2013 16:00:37 logfile.log
1021104 KB total (421552 KB free)
In IRF mode, display the log file on each standby MPU.
<Sysname> dir chassis2#slot0#flash:/logfile/
Directory of chassis2#slot0#flash:/logfile
0 -rw-21863 Jul 11 2013 16:00:37 logfile.log
1021104 KB total (421552 KB free)
NOTE:
If a subordinate chassis has two MPUs, make sure you identify and export
the
log files on both
MPUs.
# Display the log file on each MPU for each non-default MDC.
<Sysname> dir flash:/mdc/
Directory of flash:/mdc
0 drw-- Jul 10 2013 14:56:50 mdc2
1 drw-- Jul 10 2013 16:48:04 mdc3
<Sysname> dir flash:/mdc/mdc2/logfile/
Directory of flash:/mdc/mdc2/logfile
0 -rw-465 Jul 11 2013 16:08:51 logfile.log
1021104 KB total (421476 KB free)
<Sysname> dir flash:/mdc/mdc3/logfile/
Directory of flash:/mdc/mdc3/logfile
0 -rw-465 Jul 11 2013 16:10:39 logfile.log

4
1021104 KB total (421476 KB free)
3. Transfer the files to the desired destination by using FTP, TFTP, or USB. (Details not shown.)
Collecting diagnostic log messages
1. Save diagnostic log messages from the diagnostic log file buffer to a diagnostic log file:
By default, the diagnostic log file is saved in the diagfile directory of the flash memory on each
MPU.
# Save diagnostic log messages to the diagnostic log file on the default MDC (Admin).
<Sysname> diagnostic-logfile save
The contents in the diagnostic log file buffer have been saved to the file
flash:/diagfile/diagfile.log
# Identify non-default MDCs created on the device.
<Sysname> display mdc
ID Name Status
---------------------------------
1 Admin active
2 mdc2 active
3 mdc3 active
# Save diagnostic log messages to the diagnostic log file on each non-default MDC.
<Sysname> system-view
[Sysname] switchto mdc mdc2
******************************************************************************
* Copyright (c) 2010-2016 Hewlett Packard Enterprise Development LP *
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<HPE> diagnostic-logfile save
The contents in the diagnostic log file buffer have been saved to the file
flash:/diagfile/diagfile.log
<HPE> 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. *
******************************************************************************
<HPE> diagnostic-logfile save
The contents in the diagnostic log file buffer have been saved to the file
flash :/diagfile/diagfile.log
<HPE> switchback
2. On the default MDC, identify the diagnostic log file on each MPU for each MDC:
# Display the diagnostic log file on the active MPU (in standalone mode) or global active MPU
(in IRF mode) for the default MDC.
<Sysname> dir flash:/diagfile/

5
Directory of flash:/diagfile
0 -rw-161321 Jul 11 2013 16:16:00 diagfile.log
1021104 KB total (421416 KB free)
# Display the diagnostic log file on each standby MPU for the default MDC:
In standalone mode, display the diagnostic log file on the standby MPU.
<Sysname> dir slot1#flash:/diagfile/
Directory of slot1#flash:/diagfile
0 -rw-161321 Jul 11 2013 16:16:00 diagfile.log
1021104 KB total (421416 KB free)
In IRF mode, display the diagnostic log file on each standby MPU.
<Sysname> dir chassis2#slot0#flash:/diagfile/
Directory of chassis2#slot0#flash:/diagfile
0 -rw-161321 Jul 11 2013 16:16:00 diagfile.log
1021104 KB total (421416 KB free)
NOTE:
If a subordinate chassis has two MPUs, make sure you identify and export
the diagnostic log
files on both MPUs.
# Display the diagnostic log file on each MPU for each non-default MDC.
<Sysname> dir flash:/mdc/
Directory of flash:/mdc
0 drw-- Jul 10 2013 14:56:50 mdc2
1 drw-- Jul 10 2013 16:48:04 mdc3
<Sysname>dir flash:/diagfile/
Directory of flash:/diagfile
0 -rw-349 Jul 11 2013 16:21:38 diagfile.log
1021104 KB total (421352 KB free)
<Sysname> dir flash:/diagfile/
Directory of flash:/diagfile
0 -rw-349 Jul 11 2013 16:24:41 diagfile.log
1021104 KB total (421308 KB free)
3. Transfer the files to the desired destination by using FTP, TFTP, or USB. (Details not shown.)
Collecting operating statistics
You can collect operating statistics by saving the statistics to a file or displaying the statistics on the
screen.
When you collect operating statistics, follow these guidelines:
•Log in to the device through a network port or management port instead of the console port, if
possible. Network and management ports are faster than the console port.
•Do not execute commands while operating statistics are being collected.

6
•As a best practice, save operating statistics to a file to retain the information.
To collect operating statistics:
1. Disable pausing between screens of output if you want to display operating statistics on the
screen. Skip this step if you are saving statistics to a file.
<Sysname> screen-length disable
2. Collect operating statistics for multiple feature modules.
<Sysname> display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N] :
3. At the prompt, choose to save or display operating statistics:
# To save operating statistics, enter yat 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.
<Sysname> dir flash:/
Directory of flash:
......
6 -rw-898180 Jun 26 2013 09:23:51 diag.tar.gz
1021808 KB total (259072 KB free)
# To display operating statistics on the monitor terminal, enter nat 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:

7
•Information described in "General guidelines."
•Product serial numbers.
•Technical support registration numbers (if applicable).
This information will help the support engineer assist you as quickly as possible.
The following is the contact 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.
<Sysname> display users
Idx Line Idle Time Pid Type
1 AUX 1/1 00:00:36 Oct 08 16:35:09 543
+ 16 VTY 0 00:00:00 Oct 08 17:02:03 566 TEL
Following are more details.
VTY 0 :
Location: 192.168.29.1
+ : Current operation user.
F : Current operation user works in async mode.
The output shows that two users are online. You are using VTY 0. Your IP address is
192.168.29.1. The other user is using AUX 1/1.
3. Display the user roles assigned to the user line you are using.
[Sysname] line vty 0
[Sysname-line-vty0] display this
#
line aux 1/1
user-role network-operator
#
line vty 0
authentication-mode none

8
user-role level-15
user-role network-admin
user-role network-operator
#
return
The output shows that VTY 0 has the user role level-15. You have the right to change the
console login password.
4. Configure password authentication for console login and set the password. You can also
configure a different login authentication mode.
<Sysname> system-view
[Sysname] line aux 1/1
[Sysname-line-aux1/1] authentication-mode password
[Sysname-line-aux1/1] set authentication password simple 12345678
[Sysname-line-aux1/1] return
5. Save the running configuration to use the configuration at the next reboot.
<Sysname> save
The current configuration will be written to the device. Are you sure? [Y/N] :y
Please input the file name(*.cfg)[flash:/default.cfg]
(To leave the existing filename unchanged, press the enter key):default.cfg
Validating file. Please wait....
Saved the current configuration to mainboard device successfully.
Using BootWare menus to change the console login
password
CAUTION:
•
Use this method only if you cannot access the CLI.A reboot is required to access BootWare
menus.
•Do not power off the device while you are using this method.
The procedure for using BootWare menus to change the console login password depends on
whether password recovery capability is enabled:
•If password recovery capability is enabled, you can use the Skip Authentication for Console
Login option to skip console login authentication and configure a new password.
•If password recovery capability is disabled, you can use the Restore to Factory Default
Configuration option to restore the factory-default configuration and configure a new
password.
To determine whether password recovery capability is enabled, use either of the following methods:
•Telnet to the device and display the running configuration. If the password-recovery enable
command is configured, password recovery capability is enabled.
<Sysname> display current-configuration
#
version 7.1.070, Release 7523P01
#
mdc Admin id 1
#
sysname Sysname
#

9
command-alias enable
command-alias mapping undo no
command-alias mapping quit exit
command-alias mapping return end
#
password-recovery enable
#
•View the bootstrap information displayed when you access the extended BootWare menu. If the
message "Password recovery capability is enabled." is displayed, password recovery capability
is enabled.
Changing the console login password when password recovery capability is enabled
1. Connect a configuration terminal to the console port of the device.
2. Power on the device.
RAM test successful.
Press Ctrl+T to start five-step full RAM test...
Press Ctrl+Y to start nine-step full RAM test...
System is starting...
Press Ctrl+D to access BASIC-BOOTWARE MENU...
Booting Normal Extended BootWare
The Extended BootWare is self-decompressing....Done.
****************************************************************************
* *
* BootWare, Version 1.08 *
* *
****************************************************************************
Compiled Date : 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 + Bwithin 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.
==========================<EXTENDED-BOOTWARE MENU>==========================

10
|<1> Boot System |
|<2> Enter Serial SubMenu |
|<3> Enter Ethernet SubMenu |
|<4> File Control |
|<5> Restore to Factory Default Configuration |
|<6> Skip Current System Configuration |
|<7> BootWare Operation Menu |
|<8> Skip Authentication for Console Login |
|<9> Storage Device Operation |
|<0> Reboot |
============================================================================
Ctrl+Z: Access EXTENDED ASSISTANT MENU
Ctrl+F: Format File System
Enter your choice(0-9): 8
Clear Image Password Success!
4. Enter 8to skip console login authentication.
Enter your choice(0-9): 8
Clear Image Password Success!
The extended BootWare menu is displayed again:
==========================<EXTENDED-BOOTWARE MENU>==========================
|<1> Boot System |
|<2> Enter Serial SubMenu |
|<3> Enter Ethernet SubMenu |
|<4> File Control |
|<5> Restore to Factory Default Configuration |
|<6> Skip Current System Configuration |
|<7> BootWare Operation Menu |
|<8> Skip Authentication for Console Login |
|<9> Storage Device Operation |
|<0> Reboot |
============================================================================
Ctrl+Z: Access EXTENDED ASSISTANT MENU
Ctrl+F: Format File System
Enter your choice(0-9):
5. Enter 0to reboot the device. The device will ignore the console login password to access the
CLI and load the next-startup configuration file.
Enter your choice(0-9): 0
DDR2 SDRAM test successful.
System is starting...
Booting Normal Extend BootWare
The Extend BootWare is self-decompressing.................................
Done.
6. After the device starts up, configure a new console login password. You can also configure a
different login authentication mode.
<Sysname> system-view
[Sysname] line aux 1/1
[Sysname-line-aux1/1] authentication-mode password
[Sysname-line-aux1/1] set authentication password simple 12345678

11
[Sysname-line-aux1/1] return
7. Save the running configuration to use the configuration at the next reboot.
<Sysname> save
The current configuration will be written to the device. Are you sure? [Y/N] :y
Please input the file name(*.cfg)[flash:/default.cfg]
(To leave the existing filename unchanged, press the enter key):default.cfg
Validating file. Please wait....
Saved the current configuration to mainboard device successfully.
Changing the console login password when password recovery capability is disabled
IMPORTANT:
Restoring the factory-default configuration deletes the next-startup configuration files.
To change the console login password when password recovery capability is disabled:
1. Connect a configuration terminal to the console port of the device.
2. Power on the device.
RAM test successful.
Press Ctrl+T to start five-step full RAM test...
Press Ctrl+Y to start nine-step full RAM test...
System is starting...
Press Ctrl+D to access BASIC-BOOTWARE MENU...
Booting Normal Extended BootWare
The Extended BootWare is self-decompressing....Done.
****************************************************************************
* *
* BootWare, Version 1.08 *
* *
****************************************************************************
Compiled Date : 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 + Bwithin three seconds after the "Press Ctrl+B to access
EXTENDED-BOOTWARE MENU..." prompt message appears.
The extended BootWare menu is displayed:
Password recovery capability is disabled.

12
Note: The current operating device is flash
Enter < Storage Device Operation > to select device.
==========================<EXTENDED-BOOTWARE MENU>==========================
|<1> Boot System |
|<2> Enter Serial SubMenu |
|<3> Enter Ethernet SubMenu |
|<4> File Control |
|<5> Restore to Factory Default Configuration |
|<6> Skip Current System Configuration |
|<7> BootWare Operation Menu |
|<8> Skip Authentication for Console Login |
|<9> Storage Device Operation |
|<0> Reboot |
============================================================================
Ctrl+Z: Access EXTENDED ASSISTANT MENU
Ctrl+F: Format File System
Enter your choice(0-9): 5
Because the password recovery capability is disabled, this operation can
cause the configuration files to be deleted, and the system will start up
with factory defaults. Are you sure to continue?[Y/N] Y
Setting...Done.
4. Enter 5and press Yto delete the next-startup configuration files.
Enter your choice(0-9): 5
Because the password recovery capability is disabled, this operation can
cause the configuration files to be deleted, and the system will start up
with factory defaults. Are you sure to continue?[Y/N] Y
Setting...Done.
The extended BootWare menu is displayed again:
==========================<EXTENDED-BOOTWARE MENU>==========================
|<1> Boot System |
|<2> Enter Serial SubMenu |
|<3> Enter Ethernet SubMenu |
|<4> File Control |
|<5> Restore to Factory Default Configuration |
|<6> Skip Current System Configuration |
|<7> BootWare Operation Menu |
|<8> Skip Authentication for Console Login |
|<9> Storage Device Operation |
|<0> Reboot |
============================================================================
Ctrl+Z: Access EXTENDED ASSISTANT MENU
Ctrl+F: Format File System
Enter your choice(0-9): 0
5. Enter 0to reboot the device. The device will reboot with the factory defaults.
Enter your choice(0-9): 0
DDR2 SDRAM test successful.
System is starting...

13
Booting Normal Extend BootWare
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.
<Sysname> system-view
[Sysname] line aux 1/1
[Sysname-line-aux1/1] authentication-mode password
[Sysname-line-aux1/1] set authentication password simple 12345678
[Sysname-line-aux1/1] return
6. Save the running configuration to use the configuration at the next reboot.
<Sysname> save
The current configuration will be written to the device. Are you sure? [Y/N] :y
Please input the file name(*.cfg)[flash:/default.cfg]
(To leave the existing filename unchanged, press the enter key):default.cfg
Validating file. Please wait....
Saved the current configuration to mainboard device successfully.
Dealing with Telnet password loss
1. Log in to the device through the console port.
2. Configure password authentication and a new password for VTY lines. You can also configure
a different login authentication mode.
<Sysname> system-view
[Sysname] line vty 0 63
[Sysname-line-vty0-63] authentication-mode password
[Sysname-line-vty0-63] set authentication password simple 12345678
[Sysname-line-vty0-63] return
3. Save the running configuration to enable the configuration to survive a reboot.
<Sysname> save
The current configuration will be written to the device. Are you sure? [Y/N] :y
Please input the file name(*.cfg)[flash:/default.cfg]
(To leave the existing filename unchanged, press the enter key):default.cfg
Validating file. Please wait....
Saved the current configuration to mainboard device successfully
Troubleshooting configuration loss
This section provides troubleshooting information for common configuration management problems.
Startup configuration file failure
Symptom
The device starts up with factory defaults because both the main and backup startup configuration
files are not available or do not exist.

14
Solution
CAUTION:
Do not execute the
save command before you complete the tasks in this section. The save
operation overwrites the restored startup configuration file with the running configuration.
To resolve the problem:
1. Transfer a backup copy of the startup configuration file to the root directory of the default
storage medium on each MPU:
IMPORTANT:
The device loads startup configuration files from the default storage medium.
•
Make sure all MPUsuse the same type of storage medium as the default storage medium. I
n
this section, the flash memory is used on each MPU.
•
If a partitioned USB disk is used, make sure the configuration file is transferred to the root
directory of the first partition on the USB disk.
a. Download configuration file config.cfg from the FTP server to the root directory of the flash
memory on the active MPU.
<Sysname> ftp 192.168.29.1
Press CTRL+C to abort.
Connected to 192.168.29.1 (192.168.29.1).
220 WFTPD 2.0 service (by Texas Imperial Software) ready for new user
User (192.168.29.1:(none)): 1
331 Give me your password, please
Password:
230 Logged in successfully
Remote system type is MSDOS.
ftp> binary
200 Type is Image (Binary)
ftp> get config.cfg flash:/config.cfg
227 Entering Passive Mode (192,168,29,1,209,24)
150 "F:\config.cfg" file ready to send (18494 bytes) in IMAGE / Binary mode
226 Transfer finished successfully.
18494 bytes received in 0.0383 seconds (471.1 kbyte/s)
ftp> quit
221 Windows FTP Server (WFTPD, by Texas Imperial Software) says goodbye
b. Copy the configuration file to the root directory of the flash memory on the standby MPU.
<Sysname> copy config.cfg slot1#flash:/config.cfg
Copy flash:/config.cfg to slot1#flash:/config.cfg?[Y/N] :y
Coping file flash:/config.cfg to slot1#flash:/config.cfg...Done.
2. Specify the configuration file as the main startup configuration file. Skip this step if the
configuration file uses the same name as the corrupt main startup configuration file.
<Sysname> startup saved-configuration config.cfg
3. Reboot the device.
4. If the problem persists, contact Hewlett Packard Enterprise Support.

15
Related commands
This section lists the commands that you might use for troubleshooting configuration loss.
Command
Description
binary Sets the file transfer mode to binary.
copy Copies a file and saves the file to the destination directory.
ftp
Logs in to an FTP server and enters FTP client view.
get
Downloads a file from the FTP server and saves the file.
startup saved-configuration Specifies a file as a startup configuration file for each MPU.
Troubleshooting hardware
This section provides troubleshooting information for common hardware problems.
NOTE:
•
This section describes how to troubleshoot terminal display, cards, power modules, and fan
trays. To troubleshoot transceiver modules, ports, and temperature alarms, see "
Troubleshooting
system management" and "Troubleshooting ports."
•
For more information about the LEDs, see 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.

16
Garbled display on the configuration terminal
Symptom
The configuration terminal has a garbled display when the switch is powered on.
Solution
To resolve the problem:
1. Verify that the following settings are configured for the terminal:
Baud rate—9600.
Data bits—8.
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