HP FlexFabric 12900 series User manual

HP FlexFabric 12900 Switch Series
Troubleshooting Guide
© Copyright 2015 Hewlett-
Packard Development Company, L.P. The information contained
herein is subject to change without notice. The only warranties for HP products and services are
set forth in the express warranty statements accompanying such products and services. Nothing
herein should be construed as constituting an additional warranty
. HP shall not be liable for
technical or editorial errors or omissions contained herein.
Part number: 5998-7056

Contents
Introduction·······································································································································································1
General guidelines····························································································································································1
Collecting log and operating information ······················································································································1
Collecting common log messages ··························································································································2
Collecting operating statistics ·································································································································7
Contacting technical support ···········································································································································8
Removing deployment errors ··········································································································································9
Troubleshooting hardware············································································································································16
MPU reboot failure························································································································································· 16
Symptom································································································································································· 16
Troubleshooting flowchart ···································································································································· 17
Solution··································································································································································· 17
Newly installed standby MPU boot failure·················································································································· 18
Symptom································································································································································· 18
Troubleshooting flowchart ···································································································································· 18
Solution··································································································································································· 18
LPU reboot failure··························································································································································· 19
Symptom································································································································································· 19
Troubleshooting flowchart ···································································································································· 19
Solution··································································································································································· 19
Newly installed LPU boot failure ·································································································································· 20
Symptom································································································································································· 20
Troubleshooting flowchart ···································································································································· 21
Solution··································································································································································· 21
Operating power supply failure ··································································································································· 22
Symptom································································································································································· 22
Troubleshooting flowchart ···································································································································· 23
Solution··································································································································································· 23
Newly installed power supply failure ·························································································································· 24
Symptom································································································································································· 24
Troubleshooting flowchart ···································································································································· 25
Solution··································································································································································· 25
Fan tray failure ······························································································································································· 26
Symptom································································································································································· 26
Troubleshooting flowchart ···································································································································· 26
Solution··································································································································································· 26
Related commands························································································································································· 28
Troubleshooting system management··························································································································28
High CPU utilization on a card ···································································································································· 28
Symptom································································································································································· 28
Troubleshooting flowchart ···································································································································· 29
Solution··································································································································································· 29
High memory utilization on a card ······························································································································ 31
Symptom································································································································································· 31
Troubleshooting flowchart ···································································································································· 31
Solution··································································································································································· 31
Temperature alarms ······················································································································································· 33
i

Symptom································································································································································· 33
Troubleshooting flowchart ···································································································································· 33
Solution··································································································································································· 33
Related commands························································································································································· 34
Troubleshooting ports ····················································································································································34
10/100/1000Base-T copper port fails to come up ·································································································· 34
Symptom································································································································································· 34
Troubleshooting flowchart ···································································································································· 35
Solution··································································································································································· 35
1000-Mbps SFP fiber port fails to come up ················································································································ 36
Symptom································································································································································· 36
Troubleshooting flowchart ···································································································································· 36
Solution··································································································································································· 37
10-Gigabit SFP+ fiber port fails to come up ··············································································································· 37
Symptom································································································································································· 37
Troubleshooting flowchart ···································································································································· 38
Solution··································································································································································· 38
40-GE QSFP+ fiber port fails to come up ··················································································································· 39
Symptom································································································································································· 39
Troubleshooting flowchart ···································································································································· 40
Solution··································································································································································· 40
100-GE CFP fiber port fails to come up ······················································································································ 41
Symptom································································································································································· 41
Troubleshooting flowchart ···································································································································· 41
Solution··································································································································································· 42
Non-HP transceiver module error message ················································································································· 42
Symptom································································································································································· 42
Troubleshooting flowchart ···································································································································· 43
Solution··································································································································································· 43
Transceiver module does not support digital diagnosis····························································································· 43
Symptom································································································································································· 43
Troubleshooting flowchart ···································································································································· 44
Solution··································································································································································· 44
Error frames (for example, CRC errors) on a port······································································································ 44
Symptom································································································································································· 44
Troubleshooting flowchart ···································································································································· 45
Solution··································································································································································· 45
Failure to receive packets·············································································································································· 47
Symptom································································································································································· 47
Troubleshooting flowchart ···································································································································· 47
Solution··································································································································································· 47
Failure to send packets·················································································································································· 48
Symptom································································································································································· 48
Troubleshooting flowchart ···································································································································· 49
Solution··································································································································································· 49
Related commands························································································································································· 50
Troubleshooting IRF························································································································································51
IRF fabric setup failure··················································································································································· 51
Symptom································································································································································· 51
Troubleshooting flowchart ···································································································································· 52
Solution··································································································································································· 52
IRF split ············································································································································································ 54
Symptom································································································································································· 54
ii

Troubleshooting flowchart ···································································································································· 55
Solution··································································································································································· 55
BFD MAD failure ···························································································································································· 56
Symptom································································································································································· 56
Troubleshooting flowchart ···································································································································· 57
Solution··································································································································································· 57
LACP MAD failure·························································································································································· 59
Symptom································································································································································· 59
Troubleshooting flowchart ···································································································································· 59
Solution··································································································································································· 60
Related commands························································································································································· 60
Troubleshooting QoS and ACL ····································································································································61
ACL application failure for unsupported ACL rules ···································································································· 61
Symptom································································································································································· 61
Troubleshooting flowchart ···································································································································· 61
Solution··································································································································································· 62
ACL application failure for insufficient resources ······································································································· 62
Symptom································································································································································· 62
Troubleshooting flowchart ···································································································································· 62
Solution··································································································································································· 62
ACL application failure without an error message····································································································· 63
Symptom································································································································································· 63
Troubleshooting flowchart ···································································································································· 64
Solution··································································································································································· 64
Related commands························································································································································· 65
Troubleshooting MDC ···················································································································································65
LPU authorization failure ··············································································································································· 65
Symptom································································································································································· 65
Troubleshooting flowchart ···································································································································· 66
Solution··································································································································································· 66
Interface assignment failure ·········································································································································· 68
Symptom································································································································································· 68
Troubleshooting flowchart ···································································································································· 69
Solution··································································································································································· 69
Related commands························································································································································· 71
iii

Introduction
This document provides information about troubleshooting common software and hardware problems
with HP FlexFabric 12900 switches.
This document applies to Release 10xx and Release 11xx.
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 HP FlexFabric 12900 switches, 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-preventive 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, or TFTP.
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 files to a separate folder for each MPU, and include
their chassis and slot numbers in the folder names.
1

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
cards 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
Release 10xx
1. Save common log messages from the log buffer to a log file:
By default, the log file is saved in the logfile directory of the flash memory on the active MPU (in
standalone mode) or global active MPU (in IRF mode).
# Save log messages to the log file on the default MDC (Admin).
<Sysname> logfile save
The contents in the log file buffer have been saved to the file flash:/logfile/lo
Gfile.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-2014 Hewlett-Packard Development Company, L.P. *
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<HP> logfile save
2

The contents in the log file buffer have been saved to the file
flash:/logfile/logfile.log
<HP> switchback
[Sysname] switchto mdc 3
******************************************************************************
* Copyright (c) 2010-2014 Hewlett-Packard Development Company, L.P. *
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<HP> logfile save
The contents in the log file buffer have been saved to the file
flash:/logfile/logfile.log
<HP> 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-21863 Jul 11 2013 16:00:37 logfile.log
1021104 KB total (421552 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 slot16#flash:/logfile/
Directory of slot16#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#slot17#flash:/logfile/
Directory of chassis2#slot17#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)
3

<Sysname> dir flash:/mdc/mdc3/logfile/
Directory of flash:/mdc/mdc3/logfile
0 -rw-465 Jul 11 2013 16:10:39 logfile.log
1021104 KB total (421476 KB free)
3. Transfer the files to the desired destination by using FTP or TFTP. (Details not shown.)
Release 11xx
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).
<Sysname> logfile save
The contents in the log file buffer have been saved to the file
flash:/logfile/logfile.log
2. Identify the log file on each MPU:
# Display the log file on the active MPU (in standalone mode) or global active MPU (in IRF mode).
<Sysname> dir flash:/logfile/
Directory of flash:/logfile
0 -rw-21863 Jul 11 2013 16:00:37 logfile.log
1021104 KB total (421552 KB free)
# Display the log file on each standby MPU:
In standalone mode, display the log file on the standby MPU.
<Sysname> dir slot16#flash:/logfile/
Directory of slot16#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#slot17#flash:/logfile/
Directory of chassis2#slot17#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.
3. Transfer the files to the desired destination by using FTP or TFTP. (Details not shown.)
Release 10xx
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 the active
MPU (in standalone mode) or global active MPU (in IRF mode).
# Save diagnostic log messages to the diagnostic log file on the default MDC (Admin).
<Sysname> diagnostic-logfile save
4

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-2014 Hewlett-Packard Development Company, L.P. *
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<HP> diagnostic-logfile save
The contents in the diagnostic log file buffer have been saved to the file
flash:/diagfile/diagfile.log
<HP> switchback
[Sysname] switchto mdc 3
******************************************************************************
* Copyright (c) 2010-2014 Hewlett-Packard Development Company, L.P. *
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
**********************************************************************
<HP> diagnostic-logfile save
The contents in the diagnostic log file buffer have been saved to the file
flash:/diagfile/diagfile.log
<HP> switchback
2. On the default MDC, identify the diagnostic log file on each MPU for each MDC:
# Display the diagnostic log file on the active MPU (in standalone mode) or global active MPU (in
IRF mode) for the default MDC.
<Sysname> dir flash:/diagfile/
Directory of flash:/diagfile
0 -rw-161321 Jul 11 2013 16:16:00 diagfile.log
1021104 KB total (421416 KB free)
# Display the diagnostic log file on each standby MPU for the default MDC:
In standalone mode, display the diagnostic log file on the standby MPU.
<Sysname> dir slot16#flash:/diagfile/
Directory of slot16#flash:/diagfile
0 -rw-161321 Jul 11 2013 16:16:00 diagfile.log
1021104 KB total (421416 KB free)
5

In IRF mode, display the diagnostic log file on each standby MPU.
<Sysname> dir chassis2#slot17#flash:/diagfile/
Directory of chassis2#slot17#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, or TFTP. (Details not shown.)
Release 11xx
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 the active
MPU (in standalone mode) or global active MPU (in IRF mode).
<Sysname> diagnostic-logfile save
The contents in the diagnostic log file buffer have been saved to the file
flash:/diagfile/diagfile.log
2. Identify the diagnostic log file on each MPU:
# Display the diagnostic log file on the active MPU (in standalone mode) or global active MPU (in
IRF mode).
<Sysname> dir flash:/diagfile/
Directory of flash:/diagfile
0 -rw-161321 Jul 11 2013 16:16:00 diagfile.log
1021104 KB total (421416 KB free)
# Display the diagnostic log file on each standby MPU:
In standalone mode, display the diagnostic log file on the standby MPU.
<Sysname> dir slot16#flash:/diagfile/
Directory of slot16#flash:/diagfile
6

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#slot17#flash:/diagfile/
Directory of chassis2#slot17#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.
3. Transfer the files to the desired destination by using FTP or TFTP. (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 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.
•
HP recommends saving operating statistics to a file to retain the information.
NOTE:
The amount of time to collect statistics increases along with the number of cards.
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_HP_20141106-131947.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:
7

…
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. The output from this
command varies by software version.
Save or display diagnostic information (Y=save, N=display)? [Y/N] :n
===============================================
===============display clock===============
10:27:16 UTC Mon 11/03/2014
=================================================
===============display version===============
HP Comware Software, Version 7.1.045, Release 1005P12
Copyright (c) 2010-2014 Hewlett-Packard Development Company, L.P.
HP 12900 uptime is 0 weeks, 6 days, 20 hours, 15 minutes
Last reboot reason : USER reboot
Boot image: flash:/12900-CMW710-BOOT-R1005P12.bin
Boot image version: 7.1.045P41, Release 1005P12
Compiled Oct 21 2014 16:39:21
System image: flash:/12900-CMW710-SYSTEM-R1005P12.bin
System image version: 7.1.045, Release 1005P12
Compiled Oct 21 2014 16:39:46
LPU Chassis 1 Slot 1:
Uptime is 0 weeks,6 days,20 hours,12 minutes
HP 12900 LPU with 1 XLP308 Processor
BOARD TYPE: LSX1TGS48EA1
DRAM: 2048M bytes
FLASH: 0M bytes
NVRAM: 0K bytes
PCB 1 Version: VER.B
Bootrom Version: 106
CPLD 1 Version: 002
CPLD 2 Version: 002
CPLD 3 Version: 002
Release Version: HP 12900-1005P12
Patch Version : None
Reboot Cause : UserReboot
……
Contacting technical support
If you cannot resolve a problem after using the troubleshooting procedures in this document, contact HP
Support. When you contact an authorized HP support representative, be prepared to provide the
following information:
8

•
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 HP Support for networking products:
http://www.hp.com/networking/support
Removing deployment errors
Use the deployment checklist in Table 2 to eliminate issues that might be introduced at the deployment
stage. Select items that are suitable for your site.
Table 2 Deployment checklist
Question
Command or method
Result
Remarks
Environment and card
hardware status
Is the switch temperature at
least 20°C (68°F) lower
than the warning
temperature threshold?
display environment
□OK
□Not OK
□Not related
Make sure the temperature
of the switch is 20°C (68°F)
lower than the warning
temperature threshold.
Are the fan trays operating
correctly? display fan
□OK
□Not OK
□Not related
Make sure the fan trays are
operating correctly.
Are sufficient power
supplies installed and are
they operating correctly?
display power
□OK
□Not OK
□Not related
Make sure the following
conditions are met:
•You have installed
sufficient power supplies
to provide power
redundancy.
•The power supplies are
operating correctly. The
display power
command shows that
their state is Normal.
Are the LEDs all displaying
correct statuses?
Visually check the RUN LED
and alarm LED on each card
□OK
□Not OK
□Not related
Verify that the RUN LED
flashes slowly, and the
alarm LED is off.
Are all cards operating
correctly? display device
□OK
□Not OK
□Not related
Make sure all cards are
operating correctly.
•All service cards are in
Normal state.
•The active MPU is in
Master state.
•The standby MPUs are in
Standby state.
9

Question
Command or method
Result
Remarks
Active and standby MPUs
Are the software versions of
the active and standby
MPUs the same?
display boot-loader
□OK
□Not OK
□Not related
Make sure the software
versions of the active and
standby MPUs are the same.
Do the standby MPUs have
a startup configuration file? dir
□OK
□Not OK
□Not related
If any standby MPUs do not
have a startup configuration
file, execute the save
command without
specifying any parameters.
This command enables you
to save the running
configuration to a
configuration file and
specifies the file as the
next-startup configuration
file on each MPU.
CPU and memory usage
Does the CPU usage
change rate of any cards
(MPUs and LPUs) exceed
10%? Does the sustained
CPU usage exceed 60%?
display cpu-usage
□OK
□Not OK
□Not related
Execute the display
cpu-usage command
repeatedly.
If the CPU of a card sustains
a usage level of over 60%
or has a change rate higher
than 10%, execute the
debug ip packet command
to view the packets
delivered to the CPU for
analysis.
Does the memory usage of
the MPUs and LPUs exceed
60%? display memory
□OK
□Not OK
□Not related
If memory usage exceeds
60%, execute the display
system internal kernel
memory pool slot command
in probe view to identify the
module that is using the most
memory.
Ports
Is flow control unnecessarily
enabled on ports?
display current-configuration
interface
□OK
□Not OK
□Not related
Execute the undo
flow-control command if
flow control is not needed
on a port.
10

Question
Command or method
Result
Remarks
Are large numbers of error
packets generated in the
outbound or inbound
direction of the port?
display interface
□OK
□Not OK
□Not related
If an error counter displays
a non-zero value and the
value is increasing, check
for the following errors:
•Link and
optical-electrical
converter errors.
•Port setting
inconsistencies with the
peer port.
Does the port change
between an up and down
state frequently?
display logbuffer
□OK
□Not OK
□Not related
If the port state flaps, check
for the following errors:
•Link and
optical-electrical
converter errors.
•Optical power threshold
crossing events if the
port is a fiber port.
•Port setting
inconsistencies with the
peer port.
Fiber ports
Do the ports at the two ends
use the same port settings?
display current-configuration
interface
□OK
□Not OK
□Not related
To connect an HP device to
a device from another
vendor, HP recommends
that you set the same port
rate and duplex mode
settings at the two ends.
Are CRC errors present on
any fiber port? Is the
number of CRC errors
increasing?
display interface
□OK
□Not OK
□Not related
If CRC errors persist,
replace the transceiver
module or pigtail fiber, or
clean the transceiver
module connector.
Trunk port configuration
Do the peer trunk ports use
the same PVID? display current-configuration interface
□OK
□Not OK
□Not related
Make sure the same PVID is
configured on the trunk
ports between two devices.
Are the peer ports assigned
to the same VLANs?
display current-configuration
interface
□OK
□Not OK
□Not related
Make sure the trunk ports
between two devices are
assigned to the same
VLANs.
For example, if you assign a
trunk port to all VLANs, also
assign its peer port to all
VLANs.
11

Question
Command or method
Result
Remarks
Are the peer ports set to the
same link type?
display current-configuration
interface
□OK
□Not OK
□Not related
Make sure the ports
between two devices use the
same link type.
Is a loop present in VLAN
1?
loopback-detection global
enable vlan 1
□OK
□Not OK
□Not related
Remove ports from VLAN 1
as needed.
Spanning tree feature
Is the timeout factor
correctly set? display current-configuration
□OK
□Not OK
□Not related
HP recommends that you set
a timeout factor in the range
of 5 to 7 on a stable network
to avoid unnecessary
recalculations.
Are ports connected to
end-user devices configured
as edge ports?
display current-configuration
interface
□OK
□Not OK
□Not related
Verify that the output from
the display
current-configuration
interface command contains
the "stp edged-port enable"
string for ports connected to
end-user devices.
HP recommends that you
configure ports connected to
end-user devices (PCs, for
example) as edge ports, or
disable the spanning tree
feature on the ports.
Is the spanning tree feature
disabled on ports
connected to devices that
do not support spanning
tree protocols?
display current-configuration
interface
□OK
□Not OK
□Not related
Disable the spanning tree
feature on ports connected
to devices that do not
support spanning tree
protocols. Make sure the
output from the display
current-configuration
interface command contains
the "undo stp enable" string
for these ports.
12

Question
Command or method
Result
Remarks
Can the device calculate the
spanning tree correctly if it
works with a Cisco PVST+
device?
display stp
□OK
□Not OK
□Not related
Verify that spanning tree
calculation is correct on
each device.
To avoid interoperability
issues, HP recommends you
use one of the following
solutions:
•On the Cisco device,
configure the
spanning-tree mode mst
command to be
compatible with IEEE
spanning tree protocols.
•Set up a Layer 3
connection to the Cisco
PVST+ device if the HP
device is operating in
MSTP, RSTP, or STP
mode.
Do the topologies of MSTIs
meet the design?
Are there as few
overlapping paths as
possible among MSTIs?
display current-configuration
interface
□OK
□Not OK
□Not related
If the topologies deviate
from the design, reassign
ports to VLANs and revise
the VLAN and instance
mappings.
For optimal load balancing,
plan VLANs and
VLAN-to-instance mappings
to minimize overlapping
paths among different
MSTIs.
13

Question
Command or method
Result
Remarks
Does a TC attack exist to
cause frequent STP status
changes on any ports?
display stp tc
display stp history
□OK
□Not OK
□Not related
Examine the following items
in the command output for
TC attacks:
•Incoming and outgoing
TC/TCN BPDU statistics.
•Historical port role
calculation information.
There is a risk of TC attack if
frequent STP status changes
occur on a stable network.
Make sure you have
configured the following
settings:
•Configure ports
connected to end-user
devices as edge ports,
and enable BPDU
guard. Alternatively,
disable the spanning
tree feature on the ports.
•Disable the spanning
tree feature on ports
connected to devices
that do not support
spanning tree protocols.
•Do not disable TC-BPDU
guard.
VRRP
Is the handshake interval
correctly set?
Are the handshake intervals
of the two ends the same?
display vrrp
□OK
□Not OK
□Not related
Change the handshake
interval to 3 seconds if the
number of VRRP groups is
less than five.
If five or more VRRP groups
exist, assign three or five
VRRP groups into one
group, and configure the
handshake interval as 3
seconds, 5 seconds, and 7
seconds for each group.
ARP
Are there ARP conflicts? display logbuffer
□OK
□Not OK
□Not related
If the log contains ARP
conflict records, verify that
the hosts in conflict are
legitimate, and remove the
conflicts.
OSPF
14

Question
Command or method
Result
Remarks
Is the router ID of the device
unique on the network? display ospf peer
□OK
□Not OK
□Not related
Change the router ID if it is
not unique on the network.
To restart route learning
after you remove the router
ID conflict, you must execute
the reset ospf process
command.
Are there a lot of errors in
the output from the display
ospf statistics error
command?
display ospf statistics error
□OK
□Not OK
□Not related
If a large number of OSPF
errors has occurred and the
number continues to
increase, collect the error
information for further
analysis.
Are there severe route
flappings?
display ip routing-table
statistics
□OK
□Not OK
□Not related
Examine the statistics for
added and deleted routes
during the system uptime.
If route flapping occurs,
locate the flapping route
and the source device to
analyze the cause. You can
use the display ospf lsdb
command multiple times to
view the age of routes and
locate the flapping route.
Is the OSPF status stable? display ospf peer
□OK
□Not OK
□Not related
View the up time of the
OSPF neighbor.
Routes
Is the default route correct?
Are there any routing
loops?
tracert
debug ip packet
□OK
□Not OK
□Not related
Use the tracert command to
trace the path to a
nonexistent network
(1.1.1.1, for example) to
check for routing loops. If a
routing loop exists, check
the configuration of the
involved devices for errors.
Adjust the route to remove
the loop.
Use the debug ip packet
command to check for
packets with TTL 0 or 1. If
TTL exceeded packets are
received, check for network
route errors.
CPU security
15

Question
Command or method
Result
Remarks
Are there packet attacks on
CPU?
debug rxtx softcar show □OK
□Not OK
□Not related
Execute the debug rxtx
softcar show command in
probe view to view packet
rate limit information for
cards.
The CPU is under attack if
the number of packets of a
type keeps increasing
unusually.
Records in the local log
buffer
Does the local log buffer
contain exception records?
•In standalone mode:
local logbuffer slot
slot-number display
•In IRF mode:
local logbuffer chassis
chassis-number slot
slot-number display
□OK
□Not OK
□Not related
Execute the local logbuffer
display command in probe
view.
If the local log buffer
contains exception records,
contact HP Support to
troubleshoot the exceptions.
Use the following
commands in probe view to
clear the history records
after the exceptions are
removed:
•In standalone mode:
local logbuffer slot
slot-number clear
•In IRF mode:
local logbuffer chassis
chassis-number slot
slot-number clear
Troubleshooting hardware
This section provides troubleshooting information for common hardware problems.
NOTE:
This section describes how to troubleshoot MPUs, LPUs, power supplies, and fan trays. To troubleshoot
transceiver modules, ports, and
temperature alarms, see "Troubleshooting ports" and "Troubleshooting
system management."
MPU reboot failure
Symptom
An MPU fails to reboot.
16