Documente Academic
Documente Profesional
Documente Cultură
Troubleshooting Guide
Contents
General troubleshooting procedures 1
Obtaining diagnostic information 1
Obtaining other information 2
Checklist for deployment 2
Troubleshooting hardware 7
MPU reboot failure 7
Symptom 7
Troubleshooting flowchart 7
Solution 8
Operating power supply failure 8
Symptom 9
Solution 9
Newly-installed power supply failure 9
Symptom 9
Solution 9
Fan tray failure 10
Symptom 10
Solution 10
Related commands 11
Troubleshooting system management 11
Temperature alarming 11
Symptom 11
Troubleshooting flowchart 12
Solution 12
Related commands 13
Troubleshooting ports 13
10/100/1000Base-T copper port fails to go up 13
Symptom 13
Troubleshooting flowchart 14
Solution 14
100/1000-Mbps SFP fiber port fails to go up 15
Symptom 15
Troubleshooting flowchart 16
Solution 16
10-Gigabit XFP fiber port fails to go up 18
Symptom 18
Troubleshooting flowchart 19
Solution 19
10-Gigabit SFP+ fiber port fails to go up 21
Symptom 21
Troubleshooting flowchart 22
Solution 23
40-GE QSFP+ fiber port fails to go up 24
Symptom 24
Troubleshooting flowchart 25
Solution 25
40-GE CFP fiber port fails to go up 26
i
Symptom 26
Troubleshooting flowchart 27
Solution 28
Error frames (for example, CRC errors) on a port 28
Symptom 28
Troubleshooting flowchart 29
Solution 29
Failure to receive packets 31
Symptom 31
Troubleshooting flowchart 31
Solution 31
Failure to send packets 33
Symptom 33
Troubleshooting flowchart 33
Solution 33
Related commands 34
Troubleshooting IRF 35
IRF fabric establishment failure 35
Symptom 35
Troubleshooting flowchart 36
Solution 37
IRF split 38
Symptom 38
Troubleshooting flowchart 39
Solution 39
BFD MAD failure 40
Symptom 40
Troubleshooting flowchart 41
Solution 41
LACP MAD failure 43
Symptom 43
Troubleshooting flowchart 44
Solution 44
Related commands 45
Troubleshooting QoS and ACL 46
ACL application failure for unsupported ACL rules 46
Symptom 46
Troubleshooting flowchart 47
Solution 47
ACL application failure for insufficient resources 47
Symptom 47
Troubleshooting flowchart 48
Solution 48
ACL application failure without an error message 49
Symptom 49
Troubleshooting flowchart 49
Solution 49
Packet loss or forwarding failure 50
Symptom 50
Troubleshooting flowchart 51
Solution 51
Related commands 53
ii
This prompt asks you whether to save diagnostic information into a .diag file in the flash memory.
If the free space of the flash memory is larger than 10 MB, HP recommends that you enter y to save
diagnostic information into a .diag file. After you enter y, the following prompt appears:
Please input the file name(*.diag)[flash:/default.daig]:
Enter a name for the .diag file at the prompt. If you press Enter, the default name default.diag is
used. You can enter a name to differentiate between different .diag files.
If the name you entered already exists, the following prompt appears:
The file already exists, overwrite it? [Y/N]
If you enter y, the new file overwrites the old file. If you enter n, the system returns to the view in
which you executed the display diagnostic-information command. You need to re-execute the
display diagnostic-information command and enter a new name for the .diag file.
Please wait.................
The system keeps printing dots during saving the diagnostic information. If a fault occurs, the
interval between dots will increase, but it will not exceed 2 minutes.
After the system saves the diagnostic information, you can execute the dir command in user view
to verify whether the diagnostic file exists in the flash memory.
<Sysname>dir
Directory of flash:/
0
-rw-
6797
startup.cfg
drw-
patch6613
-rw-
3395
system.xml
-rw-
429516
mpu.btw
-rw-
13090
config.cwmp
drw-
seclog
-rw-
33339502
10500-cmw520-r1208.bin
-rw-
21288
10500-cmw520-r1208.bin
-rw-
468380
lsqsrp2xb05500.btw
724660
default.diag
drw-
If the diagnostic file is larger than 10000 bytes and the saving time is correct, the saving operation
is successful. If the diagnostic file has a size of 0 (-1) or the saving time is incorrect, the saving
operation failed, and you need to configure the system to print the diagnostic information on the
console. If the flash memory has no more space during the saving process, the system prints the
exceeding diagnostic information on the console.
You can use FTP to download the diagnostic file to a PC and send the file to HP Support.
If you enter n at the prompt "save or display diagnostic information (Y=save, N=display)? [Y/N]:",
the system prints all diagnostic information on the console. Before you select n, enable information
capture on the HyperTerminal or Telnet window.
If you are using the console port, the information collection takes about 20 minutes. If you are
using Telnet, the information collection takes about 3 minutes.
After you obtain the diagnostic information, send the file to HP Support.
LED state information, such as operation and alarm LEDs, power LEDs, fan LEDs, and port LEDs.
Operation information about other relevant devices, configuration information, and log files.
Environment
and card
hardware
status
Sub-item
Environment
Command or
method
display environment
Result
Remarks
OK
NOK
Not related
OK
Fan
display fan
NOK
Not related
Item
Sub-item
Command or
method
Result
OK
Power supply
display power
NOK
Not related
LED
Card operating
status
Active and
standby MPUs
CPU usage
Memory
usage
NOK
Not related
OK
display device
NOK
Not related
OK
display boot-loader
NOK
Not related
OK
dir slot#
OK
NOK
Not related
OK
NOK
Not related
OK
display memory slot
NOK
Not related
Is the port
operating in
half-duplex mode?
display interface
brief
Is flow control
enabled on the
port when not
necessary?
Check the
configuration to see
if flow control is
enabled.
Port
OK
NOK
Not related
OK
NOK
Not related
Remarks
The power supplies must be
operating correctly. (Evaluate
power backup by referring to
the power and system power
consumption.)
The RUN LED flashes slowly,
and the alarm LED is off.
All service cards must be
operating correctly, and the
MPUs are in active and
standby states.
Make sure the software
versions of the active and
standby MPUs are consistent.
If no configuration file exists,
execute the save command to
save the configuration file.
Item
Sub-item
Command or
method
Result
Remarks
Do the following:
OK
1.
2.
NOK
Not related
Do the following:
Are the
configurations on
the local and peer
fiber ports
consistent?
Fiber port
Trunk port
configurations
OK
display logbuffer
1.
2.
3.
NOK
Not related
display current
interface
OK
NOK
Not related
OK
display interface
NOK
Not related
display current
interface
display current
interface
display current
interface
OK
NOK
Not related
OK
NOK
Not related
OK
NOK
Not related
To connect an HP device to a
device of another vendor, HP
recommends that you set
consistent fiber port rate and
duplex mode on the two ends.
Verify that the optical power
has reached the threshold
value. To resolve this issue,
replace the transceiver
module or pigtail fiber, or
clean the connector of the
transceiver module.
If GVRP is configured for the
system and the undo port
trunk permit vlan 1 command
is configured for the trunk
port, configure the PVID of the
trunk port as the ID of a VLAN
permitted by the trunk port.
The VLANs permitted by the
trunk ports and the PVIDs of
the trunk ports connecting the
two devices are consistent.
The VLANs permitted by the
trunk ports connecting the two
devices are consistent.
Item
Sub-item
Command or
method
display current
interface
Timeout factor
STP
display
current-configuration
Result
OK
NOK
Not related
OK
NOK
Not related
OK
NOK
Not related
OK
NOK
Not related
OK
NOK
Not related
OK
NOK
Not related
Remarks
Item
VRRP
Sub-item
Command or
method
Does a TC attack
exist to cause
frequent STP status
changes on the
port?
Is the handshake
interval set to 3
seconds? Are the
handshake
intervals of the two
ends consistent?
Result
OK
NOK
Not related
OK
display vrrp
NOK
Not related
OK
display ospf peer
NOK
Not related
OK
NOK
Not related
OSPF
ARP
OK
NOK
Not related
OK
display ospf peer
NOK
Not related
OK
display logbuffer
NOK
Not related
Remarks
Make sure the stp edged-port
enable command is
configured on the port of the
device connected to the PC or
otherwise STP is disabled.
Disable STP on the ports
connected to the devices that
do not support STP.
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.
A router ID conflict might
result in a route learning error.
To restart route learning, you
must modify the router ID and
execute the reset ospf process
command.
If a large amount of OSPF
errors exist and the number
continues to increase, execute
the debugging ospf event
command for further analysis.
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.
View the up time of the OSPF
neighbor.
Verify that the IP address of
the host does not conflict with
other IP addresses. If a conflict
occurs, modify the IP address
of the host.
Item
Route
Sub-item
Command or
method
Result
OK
NOK
Not related
Remarks
If a routing loop exists, verify
the configurations of involved
devices. Adjust the route to
eliminate the loop. If TTL
exceeded packets are
received, verify that the
corresponding network route
is correct.
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 system management" and
"Troubleshooting ports."
Troubleshooting flowchart
Solution
To resolve the problem:
1.
2.
3.
4.
If the MPU is not securely installed, remove and reinstall the MPU.
Symptom
A trap is generated indicating that an operating power supply has failed.
Solution
To resolve the problem:
1.
1 State: Absent
Power
2 State: Normal
Chassis 2:
Power
1 State: Normal
Power
2 State: Absent
If the power supply is in Absent state, go to step 2. If the power supply is in Fault state, go to step 3.
2.
Remove and reinstall the power supply to make sure the power supply is installed correctly. Then,
execute the display power command to verify that the power supply has changed to Normal state.
If the power supply remains in Absent state, replace the power supply.
3.
A power supply might run into Fault state when it operates continuously at high temperatures or
when it is faulty.
a. Verify that the power supply surface is clean. If there is dust accumulated on the power supply,
remove the dust. Then remove and reinstall the power supply. Execute the display power
command to verify that the power supply has changed to Normal state. If the power supply
remains in Fault state, go to step b.
b. Install the power supply into an empty power supply slot. Then execute the display power
command to verify that the power supply has changed to Normal state in the new slot. If the
power supply remains in Fault state, replace the power supply.
4.
Solution
To resolve the problem:
1.
1 State: Absent
Power
2 State: Normal
Chassis 2:
Power
1 State: Normal
Power
2 State: Absent
If the power supply is in Absent state, go to step 2. If the power supply is in Fault state, go to step 3.
2.
A newly-installed power supply might run into Absent state when it is not securely installed.
a. Remove and reinstall the power supply to make sure the power supply is installed securely.
Then execute the display power command to verify that the power supply has changed to
Normal state. If the power supply remains in Absent state, go to step b.
b. Remove and install the power supply into an empty power supply slot. Then execute the display
power command to verify that the power supply has changed to Normal state in the new slot.
If the power supply remains in Absent state, go to step 4.
3.
Remove and install the power supply into an idle power supply slot. Then execute the display
power command to verify that the power supply has changed to Normal state in the new slot. If the
power supply remains in Fault state, go to step 4.
4.
Solution
To resolve the problem:
1.
Execute the display fan command to display the operating states of the fan tray.
<HP> display fan
Chassis 1:
Fan
1 State: Normal
Chassis 2:
Fan
1 State: Normal
2.
Remove and reinstall the fan tray to make sure the fan tray is securely installed. Then execute the
display fan command to verify that the fan tray has changed to Normal state. If the fan tray
remains in Absent state, replace the fan tray.
3.
Execute the display environment command to display temperature information. If the temperature
continues to rise, put your hand at the air outlet to verify that there is air being exhausted from the
air outlet. If there is no air being exhausted from the air outlet, remove and reinstall the fan tray.
Then execute the display fan command to verify that the fan tray has changed to Normal state. If
the fan tray remains in Fault state, replace the fan tray.
{
{
4.
If there is no new fan tray, power off the switch to avoid damage caused by high temperatures.
If there are cooling measures to maintain the switch operating temperature below 60C (140F),
the switch can be used temporarily.
Related commands
This section lists the commands that you might use for troubleshooting the hardware.
Command
Description
dir
display boot-loader
display environment
display fan
display logbuffer
Displays the state of the log buffer and the log information in
the log buffer.
display power
Temperature alarming
Symptom
Temperature alarms occur.
11
Troubleshooting flowchart
Figure 2 Troubleshooting temperature alarming
Solution
To resolve the problem:
1.
Identify whether the device temperature or the ambient temperature is too high.
{
If the ambient temperature is too high, lower the temperature by adding air conditioners or
taking other heat dissipation measures.
If the device temperature is too high, go to step 2.
2.
Use the display fan command to verify that the fan tray is operating correctly. If the system displays
"Fault," see HP 10500 Switch Series Installation Guide to resolve the problem.
3.
Verify that the air filters are clean. If they are not, clean them.
4.
Related commands
This section lists the commands that you might use for troubleshooting system management.
Command
Remarks
display environment
display fan
temperature-limit
Troubleshooting ports
This section provides troubleshooting information for common port problems.
13
Troubleshooting flowchart
Figure 3 Troubleshooting link up failure on a port
A port failed to go up
Speed/duplex
match on local and peer
port?
No
Configure matching
speed/duplex
Yes
Replace network
cable
Yes
Yes
Resolved?
No
No
Yes
Replace local port
Yes
Peer port
operating correctly?
Yes
No
No
Local port
operating correctly?
Resolved?
Resolved?
No
No
Yes
Replace peer port
Resolved?
No
Yes
Contact HP Support
End
Solution
To resolve the problem:
1.
Verify that the speed and duplex mode of the local port match the speed and duplex mode of the
peer port:
14
a. Execute the display interface brief command to examine whether the speed and duplex mode
of the port match the speed and duplex mode of the peer port.
b. If they do not match, use the speed command and the duplex command to set the speed and
duplex mode for the port.
2.
Replace the network cable with a new one to verify that the network cable is in good condition.
3.
Replace the local port with a new one (on a card of the same type, if possible) to verify that the
local port is operating correctly.
4.
Replace the peer port with a new one (on a card of the same type, if possible) to verify that the peer
port is operating correctly.
5.
15
Troubleshooting flowchart
Figure 4 Troubleshooting link up failure on a port
A port failed to go up
Speed/duplex
match on local and peer
port?
No
Configure matching
speed/duplex
Yes
Speed/duplex
match on transceiver
module and port?
No
Configure matching
speed/duplex
Resolved?
No
Replace transceiver
module
Yes
Resolved?
No
No
Fiber correct?
Yes
Replace fiber
Resolved?
No
Yes
No
Yes
Replace local port
Resolved?
No
Yes
No
Peer port
operating correctly?
Yes
No
Yes
Local port
operating correctly?
Yes
No
Yes
Transceiver
module correct?
Resolved?
Yes
Replace peer port
Resolved?
No
Yes
Contact HP Support
End
Solution
To resolve the problem:
16
1.
Verify that the speed and duplex mode of the local port match the speed and duplex mode of the
peer port:
a. Execute the display interface brief command to examine whether the speed and duplex mode
of the port match the speed and duplex mode of the peer port.
b. If they do not match, use the speed command and the duplex command to set the speed and
duplex mode for the port.
2.
Verify that the speed and duplex mode of the port match the speed and duplex mode of the
transceiver module:
a. Execute the display interface brief command to examine whether the speed and duplex mode
of the port match the speed and duplex mode of the transceiver module.
b. If they do not match, use the speed command and the duplex command to set the speed and
duplex mode for the port.
3.
The device displays alarms if the transceiver module fails or the type of the transceiver
module does not match the port type.
b. Use an optical power meter to verify that the Tx power and Rx power of the transceiver module
are stable and are within the correct range.
c. Execute the display transceiver interface command to verify that the wavelength and
transmission distance of the local transceiver module are consistent with the wavelength and
transmission distance of the peer transceiver module.
[HP] display transceiver interface ten-gigabitethernet 1/3/0/15
Ten-GigabitEthernet1/3/0/15 transceiver information:
Transceiver Type
: 1000_BASE_SX_SFP
Connector Type
: LC
Wavelength(nm)
: 850
Transfer Distance(m)
: 550(50um),270(62.5um)
: HP
Ordering Name
: SFP-GE-SX-MM850-A
d. If the transceiver module is not operating correctly, replace it with a new HP transceiver module
that matches the fiber port.
For more information about transceiver modules, see related installation guides.
4.
Replace the fiber with a new one to verify that the fiber is in good condition.
5.
Replace the local port with a new one (on a card of the same type, if possible) to verify that the
local port is operating correctly.
6.
Replace the peer port with a new one (on a card of the same type, if possible) to verify that the peer
port is operating correctly.
7.
17
18
Troubleshooting flowchart
Figure 5 Troubleshooting link up failure on a port
Solution
To resolve the problem:
19
1.
Verify that the speed and duplex mode of the local port match the speed and duplex mode of the
peer port:
a. Execute the display interface brief command to examine whether the speed and duplex mode
of the port match the speed and duplex mode of the peer port.
b. If they do not match, use the speed command and the duplex command to set the speed and
duplex mode for the port.
2.
Verify that the speed and duplex mode of the port match the speed and duplex mode of the
transceiver module:
a. Execute the display interface brief command to examine whether the speed and duplex mode
of the port match the speed and duplex mode of the transceiver module.
b. If they do not match, use the speed command and the duplex command to set the speed and
duplex mode for the port.
3.
The device displays alarms if the transceiver module fails or the type of the transceiver
module does not match the port type.
b. Use an optical power meter to verify that the Tx power and Rx power of the transceiver module
are stable and are within the correct range.
c. Execute the display transceiver interface command to verify that the wavelength and
transmission distance of the local transceiver module are consistent with the wavelength and
transmission distance of the peer transceiver module.
[HP] display transceiver interface ten-gigabitethernet 1/3/0/15
Ten-GigabitEthernet1/3/0/15 transceiver information:
Transceiver Type
: 10G_BASE_LR
Connector Type
: LC
Wavelength(nm)
: 1310
Transfer Distance(km)
: 10(SMF)
: FINISAR CORP.
Ordering Name
: XFP-Lx10-SM1310
d. If the transceiver module is not operating correctly, replace it with a new HP transceiver module
that matches the fiber port.
For more information about transceiver modules, see related installation guides.
4.
Verify that the fiber matches the transceiver module. If they do not match, replace the fiber with a
new one that matches the transceiver module.
5.
Replace the local port with a new one (on a card of the same type, if possible) to verify that the
local port is operating correctly.
6.
Replace the peer port with a new one (on a card of the same type, if possible) to verify that the peer
port is operating correctly.
7.
If the problem persists, execute the display diagnostic-information command to save the
diagnostic information, and contact HP Support.
<HP> display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y
20
21
Troubleshooting flowchart
Figure 6 Troubleshooting link up failure on a port
22
Solution
To resolve the problem:
1.
Verify that the speed and duplex mode of the local port match the speed and duplex mode of the
peer port:
a. Execute the display interface brief command to examine whether the speed and duplex mode
of the port match the speed and duplex mode of the peer port.
b. If they do not match, use the speed command and the duplex command to set the speed and
duplex mode for the port.
2.
Verify that the speed and duplex mode of the port match the speed and duplex mode of the
transceiver module:
a. Execute the display interface brief command to examine whether the speed and duplex mode
of the port match the speed and duplex mode of the transceiver module.
b. If they do not match, use the speed command and the duplex command to set the speed and
duplex mode for the port.
3.
Verify that the local and peer ports are operating correctly:
a. Use a 10-Gigabit SFP+ cable to directly connect the local port and another 10-Gigabit SFP+
fiber port of the same card. An SFP+ cable is suitable for short connections.
b. If the local port can go up, replace the peer port with a new one (on a card of the same type,
if possible) to verify that the peer port is operating correctly.
c. If the local port cannot go up, replace the local port with a new one (on a card of the same type,
if possible) to verify that the local port is operating correctly.
4.
The device displays alarms if the transceiver module fails or the type of the transceiver
module does not match the port type.
b. Use an optical power meter to verify that the Tx power and Rx power of the transceiver module
are stable and are within the correct range.
c. Execute the display transceiver interface command to verify that the wavelength and
transmission distance of the local transceiver module are consistent with the wavelength and
transmission distance of the peer transceiver module.
[HP] display transceiver interface Ten-GigabitEthernet 1/3/0/15
Ten-GigabitEthernet1/3/0/15 transceiver information:
Transceiver Type
: 1000_BASE_SX_SFP
Connector Type
: LC
Wavelength(nm)
: 850
Transfer Distance(m)
: 550(50um),270(62.5um)
: HP
Ordering Name
: SFP-GE-SX-MM850-A
d. If the transceiver module is not operating correctly, replace it with a new HP transceiver module
that matches the fiber port.
For more information about transceiver modules, see related installation guides.
23
5.
Verify that the fiber matches the transceiver module. If they do not match, replace the fiber with a
new one that matches the transceiver module.
6.
If the problem persists, execute the display diagnostic-information command to save the
diagnostic information, and contact HP Support.
<HP> display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y
24
Troubleshooting flowchart
Figure 7 Troubleshooting link up failure on a port
A port failed to go up
No
Local/peer port
operating correctly?
Yes
Replace local/peer
port
Resolved?
Yes
Transceiver
module/cable
correct?
No
No
Yes
Replace transceiver
module/cable
Resolved?
No
Yes
No
Fiber correct?
Yes
Replace fiber
Resolved?
No
Yes
Contact HP Support
End
Solution
To resolve the problem:
1.
Verify that the local and peer ports are operating correctly:
a. Use a QSFP+ cable to directly connect the local port and another 40-GE QSFP+ fiber port of
the same card. A QSFP+ cable is suitable for short connections.
b. If the local port can go up, replace the peer port with a new one (on a card of the same type,
if possible) to verify that the peer port is operating correctly.
c. If the local port cannot go up, replace the local port with a new one (on a card of the same type,
if possible) to verify that the local port is operating correctly.
25
2.
The device displays alarms if the transceiver module fails or the type of the transceiver
module does not match the port type.
b. Use an optical power meter to verify that the Tx power and Rx power of the transceiver module
are stable and are within the correct range.
c. Execute the display transceiver interface command to verify that the wavelength and
transmission distance of the local transceiver module are consistent with the wavelength and
transmission distance of the peer transceiver module.
[HP] display transceiver interface fortygige 1/0/1
FortyGigE1/1/0/4 transceiver information:
Transceiver Type
: 40G_BASE_SR4_QSFP_PLUS
Connector Type
: MPO
Wavelength(nm)
: 850
Transfer Distance(m)
: 100(OM3)
: HP
d. If the transceiver module is not operating correctly, replace it with a new HP transceiver module
that matches the fiber port.
For more information about transceiver modules, see related installation guides.
IMPORTANT:
If a QSFP+ to SFP+ cable is used, use an optical attenuator to make sure the Tx power of the QSFP+
module stays below the Rx power of the SFP+ module.
3.
Verify that the fiber matches the transceiver module. If they do not match, replace the fiber with a
new one that matches the transceiver module.
4.
If the problem persists, execute the display diagnostic-information command to save the
diagnostic information, and contact HP Support.
<HP> display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y
26
Troubleshooting flowchart
Figure 8 Troubleshooting link up failure on a port
A port failed to go up
Transceiver
module correct?
No
Replace transceiver
module
Yes
Resolved?
Yes
No
No
Fiber correct?
Yes
Replace fiber
Resolved?
Yes
Local port
operating correctly?
No
No
Yes
Replace local port
Resolved?
Yes
Peer port
operating correctly?
No
No
Yes
Replace peer port
Resolved?
No
Yes
Yes
Contact HP Support
End
27
Solution
To resolve the problem:
1.
The device displays alarms if the transceiver module fails or the type of the transceiver
module does not match the port type.
b. Use an optical power meter to verify that the Tx power and Rx power of the transceiver module
are stable and are within the correct range.
c. Execute the display transceiver interface command to verify that the wavelength and
transmission distance of the local transceiver module are consistent with the wavelength and
transmission distance of the peer transceiver module.
d. If the transceiver module is not operating correctly, replace it with a new HP transceiver module
that matches the fiber port.
For more information about transceiver modules, see related installation guides.
2.
Verify that the fiber matches the transceiver module. If they do not match, replace the fiber with a
new one that matches the transceiver module.
3.
Replace the local port with a new one (on a card of the same type, if possible) to verify that the
local port is operating correctly.
4.
Replace the peer port with a new one (on a card of the same type, if possible) to verify that the peer
port is operating correctly.
5.
If the problem persists, execute the display diagnostic-information command to save the
diagnostic information, and contact HP Support.
<HP> display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y
28
Troubleshooting flowchart
Figure 9 Troubleshooting error frames (for example, CRC errors) on a port
Error frames on the port
No
Optical power
of transceiver module
normal?
Replace it with a
transceiver
module with
normal optical
power
Yes
Speed and
duplex match the
peer port?
No
No
Configure the
speed and duplex
for ports
Yes
Resolved?
No
Yes
Yes
Resolved?
No
Yes
Yes
Resolved?
No
Contact HP Support
End
Solution
To resolve the problem:
1.
Examine the error frame statistics and identify the error frame type:
a. (Optional.) Use the reset counter interface command in user view to clear the packet statistics
of the port.
This command resets the values of each statistical field to 0, so that you can view the statistics
changes more clearly.
29
b. Use the display interface command to display the incoming packet statistics and outgoing
packet statistics of the port.
c. Determine the type of error frames that are accumulating.
2.
If the port is a fiber port, verify that the optical power of the transceiver module is operating
correctly:
a. Use the display transceiver diagnosis interface command to view the present measured values
of the digital diagnosis parameters for the transceiver module.
b. If the optical power of the transceiver module is not within the correct range, replace the
transceiver module with a transceiver module of the same model that is operating correctly.
[HP] display transceiver diagnosis interface gigabitethernet1/0/1
GigabitEthernet1/0/1 transceiver diagnostic information:
Current diagnostic parameters:
3.
Temp.(C)
Voltage(V)
40
3.34
Bias(mA)
1.13
RX power(dBM)
-20.43
TX power(dBM)
0.20
4.
Verify that the port and the link medium are operating correctly:
a. Plug the link medium into another port that is operating correctly, and determine whether the
same problem occurs.
b. If the problem still occurs, verify that the following items are operating correctly:
Transmission medium, including network cables, optical fibers, and transceiver modules.
5.
If the port is a fiber port, replace the transceiver module plugged into the port.
Determine whether the port has received a large amount of flow control frames:
a. Use the display interface command to view the number of pause frames.
If the number of pause frames is accumulating, you can determine that the port has sent or
received a large amount of flow control frames.
b. Verify that the incoming traffic and outgoing traffic have not exceeded the maximum traffic
processing capability of the local device and the peer device.
6.
If you determine that the configurations, the peer port, and the link are correct but the problem
persists, perform the following tasks:
{
Contact HP Support.
30
Troubleshooting flowchart
Figure 10 Troubleshooting the failure to receive packets
A port fails to receive
packets
Port
configurations affect packet
receiving?
No
Modify port
configurations
Yes
Resolved?
Yes
No
No
Yes
Resolved?
No
Yes
Contact HP Support
End
Solution
To resolve the problem:
1.
2.
a. Use the display interface brief command to verify that the port configurations are correct.
The port configurations include the duplex mode, speed, port type, and VLAN configurations
of the ports at both ends of the link.
b. If configuration errors exist, modify the port configurations. If the number of incoming packets
in the output from the display interface command is accumulating, you can determine that the
port can receive packets.
c. If the port fails to receive packets, use the shutdown command and then the undo shutdown
command to re-enable the port. If the number of incoming packets in the output from the
display interface command is accumulating, you can determine that the port can receive
packets.
d. If the port is configured with STP, use the display stp brief command to verify that the port is not
in the discarding state.
e. If a port is set to the discarding state by STP, examine and modify the STP-related
configurations to resolve the problem.
HP recommends that you configure the port as an edge port or disable STP on the port if it is
directly connected to a terminal.
f. If the port is assigned to an aggregation group, use the display link-aggregation summary
command to verify that the status of the port is Selected.
g. If the status of the port is Unselected, the port cannot send or receive data packets.
h. Determine the reasons why the port becomes Unselected, for example, the attribute
configurations of the port are different from the reference port. Modify the attribute
configurations of the port to make the port become Selected.
3.
Verify that the port and the link medium are operating correctly:
a. Plug the link medium into another port that is operating correctly, and determine whether the
same problem occurs.
b. If the problem still occurs, verify that the following items are operating correctly:
Transmission medium, including network cables, optical fibers, and transceiver modules.
4.
If the port is a fiber port, replace the transceiver module plugged into the port.
If you determine that the configurations, the peer port, and the link are correct but the problem
persists, perform the following tasks:
{
Contact HP Support.
32
Troubleshooting flowchart
Figure 11 Troubleshooting the failure to send packets
Solution
To resolve the problem:
1.
2.
a. Use the display interface brief command to verify that the port configurations are correct.
The port configurations include the duplex mode, speed, port type, and VLAN configurations
of the ports at both ends of the link.
b. If configuration errors exist, modify the port configurations. If the number of outgoing packets
in the output from the display interface command is accumulating, you can determine that the
port can send packets.
c. If the port fails to send packets, use the shutdown command and then the undo shutdown
command to re-enable the port. If the number of outgoing packets in the output from the display
interface command is accumulating, you can determine that the port can send packets.
d. If the port is configured with STP, use the display stp brief command to verify that the port is not
in the discarding state.
e. If a port is set to the discarding state by STP, examine and modify the STP-related
configurations to resolve the problem.
HP recommends that you configure the port as an edge port or disable STP on the port if it is
directly connected to a terminal.
f. If the port is assigned to an aggregation group, use the display link-aggregation summary
command to verify that the status of the port is Selected.
g. If the status of the port is Unselected, the port cannot send or receive data packets.
h. Determine the reasons why the port becomes Unselected, for example, the attribute
configurations of the port are different from the reference port. Modify the attribute
configurations of the port to make the port become Selected.
3.
Verify that the port and the link medium are correct:
a. Plug the link medium into another port that is operating correctly, and determine whether the
same problem occurs.
If the port is a copper port, replace the peer device with a PC.
b. If the problem still occurs, determine whether intermediate links and devices are operating
correctly (for example, optical converters, cable terminal racks, and transmission devices).
4.
If you determine that the configurations, the peer port, and the link are correct but the problem
persists, perform the following tasks:
{
Contact HP Support.
Related commands
This section lists the commands that you might use for troubleshooting ports.
Command
Description
display diagnostic-information
display interface
Command
Description
display logbuffer
Troubleshooting IRF
This section provides troubleshooting information for common IRF problems.
35
Troubleshooting flowchart
Figure 12 Troubleshooting IRF fabric establishment failure
IRF setup
failure
Fewer than 4
chassis
in the fabric?
Yes
Same chassis model?
No
Yes
No
No
No
No
No
Resolved?
Yes
Resolved?
Yes
Resolved?
Yes
Resolved?
Yes
No
Yes
Bridge MAC unique?
Yes
No
Yes
Same software version?
Resolved?
No
Yes
IRF links up?
No
No
Yes
Physical IRF
connections correct?
Yes
No
Yes
Member ID unique?
Resolved?
No
Resolved?
Yes
No
Yes
Contact HP
Support
End
36
Solution
To resolve the problem:
1.
Execute the display irf command to verify that the number of member chassis in the IRF fabric does
not exceed the upper limit of four.
If the upper limit is reached, you cannot add new chassis to the IRF fabric.
2.
Verify that the chassis is the same model as the chassis in the IRF fabric.
The 10500 switches must be the same model to form an IRF fabric.
3.
4.
Verify that the member ID of the chassis does not conflict with any member chassis in the IRF fabric:
a. Execute the display irf command to view member IDs.
b. If the member ID of the chassis is not unique, use the irf member renumber command to assign
a new member ID to the chassis.
5.
6.
If the field displays DOWN ( Administratively ), execute the undo shutdown command to
bring up the port.
If the field displays DOWN, verify that SFP+ or QSFP+ transceiver modules or cables are
used for IRF connection and that they are operating correctly.
d. If the IRF port is down when it contains at least one up link, verify that the MPUs of the chassis
are operating correctly.
7.
Verify that the member chassis is running the same software version as the IRF fabric:
a. Execute the display version command to identify the software version.
b. Upgrade the MPUs in the chassis to use the same software version as the IRF fabric.
37
NOTE:
Typically, the irf auto-update enable command can automatically synchronize a member chassis
with the software version of the master chassis. However, the synchronization might fail when the gap
between the software versions is large.
8.
b. If the chassis has the same bridge MAC address as the IRF fabric, remove the bridge MAC
conflict.
9.
IRF split
Symptom
An IRF fabric splits.
38
Troubleshooting flowchart
Figure 13 Troubleshooting IRF split
IRF fabric splits
Yes
Yes
Resolved?
Yes
No
No
Yes
No
No
Card rebooted?
Resolved?
Yes
Resolved?
Yes
No
No
Contact HP
Support
End
Solution
To resolve the problem:
1.
2.
Remove hardware problems that might cause recurring IRF split events:
a. Execute the display version command to identify the uptime of MPUs and interface cards that
have IRF links.
b. Compare the uptime of MPUs and interface cards to determine whether a member chassis or
interface card rebooted before the IRF split.
c. If the IRF split is caused by a chassis or card reboot, perform one of the following tasks:
If the split is caused by recurring card reboots, contact HP Support to resolve the problem.
39
3.
If the split is caused by a chassis reboot, use the methods described in "MPU reboot failure"
to resolve the problem.
40
Troubleshooting flowchart
Figure 14 Troubleshooting the BFD MAD failure
BFD MAD failure
No
No
Yes
BFD MAD VLAN interface
configured correctly?
No
No
No
Yes
Resolved?
Yes
Resolved?
Yes
No
No
Resolved?
Yes
No
Yes
BFD MAD port state changes
were occasional?
Resolved?
No
Yes
BFD MAD VLAN unique in a
multi-IRF fabrics network?
Yes
No
Yes
BFD MAD IP addresses
configured correctly?
Resolved?
No
Yes
Yes
No
Yes
All BFD MAD ports up?
Resolved?
No
Resolved?
Yes
No
Yes
End
Contact HP Support
Solution
To resolve the problem:
41
1.
2.
If you do not use an intermediate device, verify that each pair of member chassis has a
dedicated BFD MAD link.
If you use an intermediate device, verify that each member chassis has a dedicated BFD MAD
link with the intermediate device.
Verify that all physical ports used for BFD MAD are up:
a. Execute the display interface command.
b. Check the current state field in the command output:
3.
If the field displays DOWN ( Administratively ) for a port, execute the undo shutdown
command to bring up the port.
If the field displays DOWN for a port, check the physical link for a link failure.
4.
Verify that the BFD MAD VLAN and physical ports in the VLAN are configured correctly:
a. Execute the display vlan command to verify the following items:
The BFD VLAN contains all physical ports used for BFD MAD.
The BFD VLAN does not contain physical ports that are not used for BFD MAD.
If an intermediate device is used, this step must also be performed on the intermediate device.
b. Execute the display interface command to verify that the physical ports in the BFD VLAN are not
configured with any features.
For BFD MAD to operate correctly, you must disable all features on the physical ports in the
BFD MAD VLAN, including the spanning tree feature, ARP, and LACP.
5.
The MAD IP addresses are not addresses being used on the IRF fabric.
6.
If the network has multiple IRF fabrics, execute the display mad verbose command to verify that
their BFD MAD VLANs are different.
7.
If the physical ports in the BFD MAD VLAN are down continually:
42
a. Execute the display trapbuffer command or use system logs to check for BFD MAD port down
events that occurred around the split time.
b. Identify the cause of the event, and remove the issue.
8.
43
Troubleshooting flowchart
Figure 15 Troubleshooting LACP MAD failure
Solution
To resolve the problem:
1.
Verify that the intermediate device is an HP device that supports extended LACPDUs for MAD.
If the intermediate device does not support extended LACPDUs for MAD, replace the intermediate
device, or use BFD MAD for split detection.
2.
Verify that each member chassis has a link in the link aggregation with the intermediate device.
3.
4.
Verify that the aggregate interface and its member ports are up:
a. Execute the display interface command.
b. Check the current state field of the aggregate interface:
If the field displays DOWN ( Administratively ), execute the undo shutdown command to
bring up the interface.
If the field displays DOWN, check the state of all its physical ports.
An aggregate interface goes down only if all its physical ports are down.
5.
If the field displays DOWN ( Administratively ), execute the undo shutdown command to
bring up the port.
If the field displays DOWN, check the physical link of the port for a link failure.
If the intermediate device is also an IRF fabric, verify that the IRF domain IDs of the two IRF fabrics
are unique:
CAUTION:
The IRF member devices send extended LACPDUs with TLVs that convey the domain ID and the active
ID of the IRF fabric. For correct split detection, makes sure the IRF fabric has a unique domain ID.
a. Execute the display irf command to identify the domain ID of each IRF fabric.
b. If the IRF fabrics use the same domain ID, execute the irf domain command to change the
domain ID on one IRF fabric.
6.
7.
Related commands
This section lists the commands that you might use for troubleshooting IRF:
Command
Description
display diagnostic-information
display interface
display irf
Command
Description
display trapbuffer
display version
display vlan
46
Troubleshooting flowchart
Figure 16 Troubleshooting an ACL application failure
Solution
To resolve the problem:
1.
2.
Verify that the matching criteria in each ACL rule are of the same length:
a. If an ACL rule includes much more matching criteria than the other ACL rules, split it into multiple
rules.
b. Apply the adjusted ACL.
3.
Error: Slot=2 Fail to apply or refresh packet filter policy 3001 rule 25 on int
erface Vlan-interface6 due to lack of resources.
Warning: Classifier-behavior test in policy test applied on vlan 4079 failed in
slot 2.
Reason: Not enough hardware resource.
Troubleshooting flowchart
Figure 17 Troubleshooting an ACL application failure
Solution
Insufficient hardware resources might be caused by insufficient Counter, Meter, or ACL resources.
To resolve the problem:
1.
Verify that the number of ACL rules to be applied is no more than the number of remaining
resources:
Execute the display acl resource command to display the ACL resource usage. If the ACL is applied
globally (for example, to a VLAN), check remaining ACL resources on all cards.
[HP] display acl resource
Interface:
GE3/0/1 to GE3/0/24
--------------------------------------------------------------------Type
Total
Reserved
Configured
Remaining
Usage
--------------------------------------------------------------------VFP ACL
1024
256
768
25%
IFP ACL
4096
IFP Meter
2048
1024
316
2756
32%
512
1422
1422
30%
IFP Counter
EFP ACL
2048
512
1422
1422
30%
512
512
0%
EFP Meter
256
256
0%
EFP Counter
512
512
0%
a. If the number of ACL rules to be applied is greater than the number of remaining ACL resources,
delete unnecessary ACL rules.
b. Apply the ACLs.
2.
Troubleshooting flowchart
Figure 18 Troubleshooting an ACL application failure
Failure to apply an ACL
No
Overlapping
ACLs exist?
Yes
Conflicting behaviors
for packets matching
overlapping ACLs?
Yes
Reconfigure conflicting
behaviors
Yes
No
No
Contact HP Support
End
Solution
To resolve the problem:
1.
Problem resolved?
Verify that overlapping ACL rules that have been applied exist.
49
b. Execute the display acl command to verify that the applied ACL rules overlap.
For example, the output shows that rule 0 in ACL 3100 and rule 0 in ACL 3009 overlap. They
both can match traffic sourced from 2.2.2.1.
ACL number 3100
rule 0 permit ip source 2.2.2.2 255.255.0.0
ACL number 3009
rule 0 permit ip source 2.2.2.2 255.255.255.0
2.
Verify that the behaviors for packets matching the overlapping ACLs do not conflict.
If the behaviors conflict, the device chooses a behavior according to the rules shown in Table 2.
The ineffective behavior and the ACL for the associated traffic class do not take effect.
Table 2 Rules for an effective behavior between conflicting behaviors
3.
Conflicting behaviors
Effective behavior
redirect
filter permit
redirect
redirect
filter deny
filter deny
filter permit
filter deny
50
Troubleshooting flowchart
Figure 19 Troubleshooting a forwarding failure
Solution
To resolve the problem:
1.
Identify the characteristics of the packets that are not forwarded correctly.
Use a packet capture tool to identify the characteristics of the traffic, such as the IP address, MAC
address, or VLAN. Make sure the characteristics are unique among all traffic to be forwarded.
2.
a. Configure a QoS policy according to the traffic characteristics. In this example, use a
destination IP address 2.2.2.2.
<HP> system-view
System View: return to User View with Ctrl+Z.
[HP] time-range t1 from 12:00 11/11/2013 to 12:01 11/11/2013
[HP] acl number 3000 name geliACL
[HP-acl-adv-3000-geliACL] rule 0 permit ip destination 2.2.2.2 0 time-range t1
[HP-acl-adv-3000-geliACL] quit
[HP] traffic classifier count
[HP-classifier-count] if-match acl 3000
[HP-classifier-count] quit
[HP] traffic behavior count
51
[HP-behavior-count] accounting
[HP-behavior-count] quit
[HP] qos policy count
[HP-qospolicy-count] classifier count behavior count
b. Apply the QoS policy to interfaces on different devices on the forwarding path. In this example,
apply the QoS policy to GigabitEthernet 1/0/1 on Device B and GigabitEthernet 2/0/1 on
Device C.
The following shows the application on Device B:
[HP-qospolicy-count] quit
[HP] interface gigabitethernet 1/0/1
[HP-GigabitEthernet1/0/1] qos apply policy count inbound
3.
Execute the display qos policy interface command to display traffic statistics on the interfaces:
{
Interface: GigabitEthernet1/0/1
Direction: Inbound
Direction: Inbound
Policy: count
Classifier: count
Operator: AND
Rule(s) : If-match ACL 3000
Behavior: count
Accounting Enable:
251 (Packets)
The output shows that a total of 251 packets match ACL 3000.
{
Interface: GigabitEthernet2/0/1
Direction: Inbound
Direction: Inbound
Policy: count
Classifier: count
Operator: AND
Rule(s) : If-match ACL 3000
Behavior: count
Accounting Enable:
50 (Packets)
Compare the traffic statistics on the two interfaces. Packet loss or forwarding fault exists between
Device B and Device C.
52
Related commands
This section lists the commands that you might use for troubleshooting QoS and ACLs.
Command
Description
display acl
display diagnostic-information
53