H3C S5830 Series User manual

H3C S5830 Switch Series Troubleshooting
Guide
Copyright © 2014 Hangzhou H3C Technologies Co., Ltd. All rights reserved.
No part of this manual may be reproduced or transmitted in any form or by any means
without prior written consent of Hangzhou H3C Technologies Co., Ltd.
The information in this document is subject to change without notice.

i
Contents
General troubleshooting procedures ·························································································································· 1
Obtaining diagnostic information ···································································································································1
Obtaining other information ············································································································································2
Checklist for deployment ············································································································································· 2
Troubleshooting hardware ·········································································································································· 7
Unexpected switch reboot················································································································································7
Symptom····································································································································································7
Troubleshooting flowchart ·······································································································································7
Solution······································································································································································8
Operating power supply failure ······································································································································8
Symptom····································································································································································8
Solution······································································································································································8
Newly-installed power supply failure······························································································································9
Symptom····································································································································································9
Solution······································································································································································9
Fan tray failure ··································································································································································9
Symptom····································································································································································9
Solution··································································································································································· 10
Related commands························································································································································· 10
Troubleshooting system management·······················································································································10
Temperature alarming ··················································································································································· 11
Symptom································································································································································· 11
Troubleshooting flowchart ···································································································································· 11
Solution··································································································································································· 11
Related commands························································································································································· 12
Troubleshooting ports·················································································································································12
10/100/1000Base-T copper port fails to go up······································································································· 12
Symptom································································································································································· 12
Troubleshooting flowchart ···································································································································· 13
Solution··································································································································································· 13
100/1000-Mbps SFP fiber port fails to go up ··········································································································· 14
Symptom································································································································································· 14
Troubleshooting flowchart ···································································································································· 15
Solution··································································································································································· 15
10-Gigabit SFP+ fiber port fails to go up···················································································································· 17
Symptom································································································································································· 17
Troubleshooting flowchart ···································································································································· 18
Solution··································································································································································· 19
Error frames (for example, CRC errors) on a port ······································································································ 20
Symptom································································································································································· 20
Troubleshooting flowchart ···································································································································· 21
Solution··································································································································································· 21
Failure to receive packets·············································································································································· 23
Symptom································································································································································· 23
Troubleshooting flowchart ···································································································································· 23
Solution··································································································································································· 23
Failure to send packets·················································································································································· 25

ii
Symptom································································································································································· 25
Troubleshooting flowchart ···································································································································· 25
Solution··································································································································································· 25
Related commands························································································································································· 26
Troubleshooting IRF····················································································································································27
IRF fabric establishment failure····································································································································· 27
Symptom································································································································································· 27
Troubleshooting flowchart ···································································································································· 28
Solution··································································································································································· 28
IRF split ············································································································································································ 30
Symptom································································································································································· 30
Troubleshooting flowchart ···································································································································· 30
Solution··································································································································································· 30
BFD MAD failure ···························································································································································· 31
Symptom································································································································································· 31
Troubleshooting flowchart ···································································································································· 32
Solution··································································································································································· 32
LACP MAD failure·························································································································································· 34
Symptom································································································································································· 34
Troubleshooting flowchart ···································································································································· 35
Solution··································································································································································· 35
Related commands························································································································································· 36
Troubleshooting QoS and ACL ·································································································································37
ACL application failure for unsupported ACL rules ···································································································· 37
Symptom································································································································································· 37
Troubleshooting flowchart ···································································································································· 38
Solution··································································································································································· 38
ACL application failure for insufficient resources ······································································································· 38
Symptom································································································································································· 38
Troubleshooting flowchart ···································································································································· 39
Solution··································································································································································· 39
ACL application failure without an error message····································································································· 40
Symptom································································································································································· 40
Troubleshooting flowchart ···································································································································· 41
Solution··································································································································································· 41
Packet loss or forwarding failure·································································································································· 42
Symptom································································································································································· 42
Troubleshooting flowchart ···································································································································· 42
Solution··································································································································································· 43
Related commands························································································································································· 44

1
General troubleshooting procedures
This chapter describes how to obtain information for troubleshooting problems. This document is not
restricted to specific software or hardware versions.
Obtaining diagnostic information
Diagnostic information is important for locating and solving problems. You can execute the display
diagnostic-information command to obtain diagnostic information.
H3C recommends that you execute the display diagnostic-information command over Telnet instead of
the console port because information collection through the console port (9600 bps) takes a long time.
Information collection on an IRF fabric takes more time than on a single device.
To obtain diagnostic information:
<Sysname> display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N]:y
Please input the file name(*.diag)[flash:/default.diag]:aa.diag
Diagnostic information is outputting to flash:/aa.diag.
Please wait.................
Save successfully.
The following describes the output information above:
save or display diagnostic information (Y=save, N=display)? [Y/N]:
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, H3C recommends that you enter yto
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 execute the
display diagnostic-information command again and enter a new name for the .diag file.
Please wait.................
The system continues to print dots while 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 Jun 14 2012 10:37:42 startup.cfg
1 drw- - Sep 03 2010 11:03:06 patch6613
2 -rw- 3395 May 13 2013 13:07:13 system.xml

2
3 -rw- 429516 Aug 19 2010 15:59:51 mpu.btw
4 -rw- 13090 May 13 2013 13:07:03 config.cwmp
5 drw- - Apr 09 2010 13:47:34 seclog
6 -rw- 406528 Dec 11 2012 15:43:37 lsv158308616_v1.06.btw
7 -rw- 22600 Jul 01 2013 11:11:42 5830-cmw520-r1118h01.bin
8 drw- 724660 May 03 2013 14:05:15 default.diag
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. You must 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 excess
diagnostic information on the console.
You can use FTP to download the diagnostic file to a PC and send the file to H3C Support.
•If you enter nat 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 process takes about 20 minutes. If you
are using Telnet, the information collection process takes about 3 minutes.
After you obtain the diagnostic information, send the file to H3C Support.
Obtaining other information
Besides diagnostic information, the following information is also helpful for troubleshooting:
•LED state information, such as port LEDs, expansion interface card LEDs, and system status LEDs.
•Operation information about other relevant devices, configuration information, and log files.
•Your opinions on this problem.
•Measures taken on site and the results.
•Solution to the problem if the problem has been solved.
Checklist for deployment
The following checklist serves as a deployment guide to help you eliminate potential configuration errors
at different deployment sites. Select items according to your deployment environment.
Table 1 Checklist
Item Sub-item Command or
method
Result Remarks
Environment
and device
hardware
status
Environment display environment
□OK
□NOK
□Not related
The temperature of the device
must be lower than 62°C
(143.6°F).
Fan display fan
□OK
□NOK
□Not related
Make sure the fans are
operating correctly.

3
Item Sub-item Command or
method
Result Remarks
Power supply display power
□OK
□NOK
□Not related
Make sure the power supplies
are operating correctly.
Evaluate power backup by
referring to the power and
system power consumption.
LED
Examine the status of
all the LEDs on the
device.
□OK
□NOK
□Not related
For more information about
the LED description, see H3C
S5830 Switch Series
Installation Guide.
Device operating
status display device
□OK
□NOK
□Not related
The device must be operating
correctly.
CPU usage
Does the CPU
usage keep
changing between
10% and 60% or
stay at a high level
(the CPU usage
exceeds 60%)?
Execute the display
cpu-usage command
repeatedly.
□OK
□NOK
□Not related
Execute the debug ip packet
command to view the packets
delivered to the CPU and
analyze the cause.
Memory
usage
Does the memory
usage of the device
exceed 60%?
display memory slot
□OK
□NOK
□Not related
If the memory usage exceeds
60%, execute the display
memory command to view
memory usage and
troubleshoot the module that
occupies the most memory.
Port
Is the port
operating in
half-duplex mode?
display interface
brief
□OK
□NOK
□Not related
If a port is operating in
half-duplex mode, verify that
the configurations on the two
ends are consistent.
Is flow control
enabled on the
port when not
necessary?
Check the
configuration to see
if flow control is
enabled.
□OK
□NOK
□Not related
Use the undo flow control
command to disable flow
control on the port.
Are large numbers
of error packets
generated in the
outbound/inbound
direction of the
port?
Use the display
interface command
to verify that a large
number of errors are
generated and that
the number keeps
increasing.
□OK
□NOK
□Not related
Do the following:
1. Examine link quality and
the optical-electrical
converter.
2. Verify that the
configurations on the two
ends are consistent.

4
Item Sub-item Command or
method
Result Remarks
Does the port
change to
up/down
frequently?
display logbuffer
□OK
□NOK
□Not related
Do the following:
1. Examine the link and the
optical-electrical
converter.
2. Verify that the optical
power of the GE port has
reached the threshold
value.
3. Verify that the
configurations on the two
ends are consistent.
Fiber port
Are the
configurations on
the local and peer
fiber ports
consistent?
display current
interface
□OK
□NOK
□Not related
To connect an H3C device to
a device of another vendor,
H3C recommends that you set
consistent fiber port rate and
duplex mode on the two ends.
Does CRC error
occur on the fiber
port? Is the number
of CRC errors
increasing?
display interface
□OK
□NOK
□Not related
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.
Trunk port
configurations
Is the undo port
trunk permit vlan 1
command
configured on the
trunk port?
display current
interface
□OK
□NOK
□Not related
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.
Is the PVID of the
trunk port
consistent with the
peer port?
display current
interface
□OK
□NOK
□Not related
The VLANs permitted by the
trunk ports and the PVIDs of
the trunk ports connecting the
two devices are consistent.
Are the VLANs to
which the port is
assigned
consistent with the
peer port?
display current
interface
□OK
□NOK
□Not related
The VLANs permitted by the
trunk ports connecting the two
devices are consistent.
Are the ports
connecting two
devices configured
as a trunk port and
an access port?
display current
interface
□OK
□NOK
□Not related
Configure the same link type
for the ports as needed.

5
Item Sub-item Command or
method
Result Remarks
Does a loop occur
in VLAN 1?
Use the display
interface command
to verify that the trunk
ports of all devices
are assigned to
VLAN 1.
□OK
□NOK
□Not related
Remove the ports from VLAN 1
as needed.
STP
Timeout factor display
current-configuration
□OK
□NOK
□Not related
Verify that the stp timer-factor
command is configured. If not,
configure a timeout factor in
the range of 5 to 7 to enhance
the stability of STP.
Is the port on the
device connected
to the PC
configured as an
edge port?
Use the display
current interface
command to
examine the port
configurations. If an
edge port is
configured, stp
edged-port enable is
displayed.
□OK
□NOK
□Not related
H3C recommends configuring
the port on the device
connected to the PC as an
edge port or disabling STP on
the port. To prevent state
change of the ports from
interrupting STP calculation,
disable STP on the ports
connected to the
STP-incapable devices.
Can the H3C
device running
MSTP/STP/RSTP
communicate with
the Cisco device
running PVST+?
Verify that STP
calculation on each
device is correct.
□OK
□NOK
□Not related
To avoid communication
between the H3C device
running MSTP/STP/RSTP and
the Cisco device running
PVST+, H3C recommends that
you change the connection
mode to Layer 3 connection.
Are there too many
overlapping paths
among the
topologies of
different MSTIs?
Use the display
current interface
command to
examine port
configurations.
□OK
□NOK
□Not related
Plan VLANs and
VLAN-to-instance mappings
according to your network
environment in order to do the
following:
•Forward traffic of multiple
VLANs along different
paths.
•Avoid too many
overlapping paths among
the topologies of different
MSTIs.
Does a TC attack
exist to cause
frequent STP status
changes on the
port?
Use the display stp tc
and display stp
history commands to
examine the statistics
of TC/TCN BPDUs
received and sent on
the port and the
historical port role
calculation
information.
□OK
□NOK
□Not related
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.

6
Item Sub-item Command or
method
Result Remarks
VRRP
Is the
advertisement
timer set to 3
seconds? Is the
timer value the
same between the
two ends?
display vrrp
□OK
□NOK
□Not related
If fewer than five VRRP groups
exist, set the advertisement
timer to 3 seconds for all the
groups.
If five or more VRRP groups
exist, set the advertisement
timer to different values for
every three or five VRRP
groups. The timer value can
be 3 seconds, 5 seconds, or 7
seconds.
OSPF
Are the router IDs
of two devices the
same?
display ospf peer
□OK
□NOK
□Not related
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.
Are there a lot of
errors from the
output of the
display ospf error
command?
display ospf error
□OK
□NOK
□Not related
If a large amount of OSPF
errors exist and the number
continues to increase, execute
the debugging ospf event
command for further analysis.
Does severe route
flapping occur?
Use the display ip
routing-table
statistics command to
examine the number
of added and
deleted routes.
□OK
□NOK
□Not related
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
□NOK
□Not related
View the up time of the OSPF
neighbor.
ARP
Are there a lot of
ARP entry
conflicts?
display logbuffer
□OK
□NOK
□Not related
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.
Route
Is the default route
correct? Is there
any routing loop?
Trace the path to a
nonexistent network
(1.1.1.1, for
example) by using
the tracert command
to check routing
loops. Use the debug
ip packet command
to check if packets
with TTL 0 or 1 exist.
□OK
□NOK
□Not related
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.

7
Troubleshooting hardware
This section provides troubleshooting information for common hardware problems.
NOTE:
This section describes how to troubleshoot unexpected switch reboot, power supply failure, and fan tray
failure. To troubleshoot transceiver modules, ports, and temperature alarms, see "Troubleshootin
g
system
management" and "Troubleshooting ports."
Unexpected switch reboot
Symptom
The switch reboots unexpectedly when it is operating.
Troubleshooting flowchart
Figure 1 Troubleshooting unexpected switch reboot
The switch reboots unexpectedly
Can the CLI be
accessed?
Collect log messages Reload the system
software image
Yes
No
Is the fault
rectified?
End
Contact H3C Support
Yes No
Yes
No
Is the system software
image correct?

8
Solution
To resolve the problem:
1. Verify that you can access the CLI after the switch reboot.
{If you can access the CLI, execute the display diagnostic-information command to collect log
messages.
{If you cannot access the CLI, go to step 2.
2. Verify that the system software image on the switch is correct.
a. Log in to the switch through the console port and restart the switch. If the system reports that a
CRC error occurs or that no system software image is available during the BootWare loading
process, reload the system software image.
b. Verify that the system software image in the flash memory is the same as the one on the server.
If no system software image is available in the flash memory, or if the image is different than
the one on the server, reload the system software image. Then set the reloaded system software
image to the current system software image. The system software image in the flash memory is
automatically set to the current system software image during the BootWare loading process.
3. If the problem persists, contact H3C Support.
Operating power supply failure
Symptom
A trap is generated indicating that an operating power supply has failed.
Solution
To resolve the problem:
1. Execute the display power command to display power supply information.
<H3C> display power
Slot 1
Power 1
State : Absent
Power 2
State : Normal
Type : AC
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

9
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. If the problem persists, contact H3C Support.
Newly-installed power supply failure
Symptom
A newly-installed power supply fails.
Solution
To resolve the problem:
1. Execute the display power command to display power supply information.
<H3C> display power
Slot 1
Power 1
State : Absent
Power 2
State : Normal
Type : AC
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. If the problem persists, contact H3C Support.
Fan tray failure
Symptom
An operating fan tray or a newly-installed fan tray fails.

10
Solution
To resolve the problem:
1. Execute the display fan command to display the operating states of the fan tray.
<H3C> display fan
Slot 1
Fan 1
State : Normal
Direction : Power to port(Preferred)
Load average : 43%
{If the fan tray is in Absent state, go to step 2.
{If the fan tray is in Fault state, go to step 3.
2. 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 air is 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.
{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 60°C (140°F),
the switch can be used temporarily.
4. If the problem persists, contact H3C Support.
Related commands
This section lists the commands that you might use for troubleshooting the hardware.
Command Descri
p
tion
display environment Displays temperature information.
display fan Displays the operating states of the fan tray.
display power Displays power supply information.
Troubleshooting system management
This section provides troubleshooting information for common system management problems.

11
Temperature alarming
Symptom
Temperature alarms occur.
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 H3C S5830 Switch Series Installation Guide to resolve the problem.
3. Use the temperature-limit command to set the temperature alarm thresholds.
You can use the display environment command to identify whether the temperature alarm
thresholds are set successfully.
{If they are not, contact H3C Support.
{If they are but temperature alarms still occur, contact H3C Support.

12
Related commands
This section lists the commands that you might use for troubleshooting system management.
Command Remarks
display environment Displays temperature information, including the current temperature
and the temperature alarm thresholds.
display fan Displays the operating status of all fan trays on the switch.
temperature-limit Sets temperature alarm thresholds.
Troubleshooting ports
This section provides troubleshooting information for common port problems.
10/100/1000Base-T copper port fails to go up
Symptom
A 10/100/1000Base-T copper port cannot go up.

13
Troubleshooting flowchart
Figure 3 Troubleshooting link up failure on a port
Solution
To resolve the problem:
1. Verify that the speed and duplex mode of the local port match the speed and duplex mode of the
peer port:
Speed/duplex
match on local and peer
port?
Network cable correct?
Configure matching
speed/duplex Resolved?
Replace network
cable
Contact H3C Support
A port failed to go up
No
Yes No
Yes
Resolved?
No Yes
Yes No
End
Local port
operating correctly? Replace local port Resolved?
No Yes
Yes No
Peer port
operating correctly? Replace peer port Resolved?
No Yes
Yes No

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 to verify that the local port is operating correctly.
4. Replace the peer port with a new one to verify that the peer port is operating correctly.
5. If the problem persists, contact H3C Support.
100/1000-Mbps SFP fiber port fails to go up
Symptom
A 100/1000-Mbps SFP fiber port cannot go up.

15
Troubleshooting flowchart
Figure 4 Troubleshooting link up failure on a port
Solution
To resolve the problem:
Speed/duplex
match on local and peer
port?
Speed/duplex
match on transceiver
module and port?
Configure matching
speed/duplex Resolved?
Configure matching
speed/duplex
A port failed to go up
No
Yes No
Yes
Resolved?
No Yes
Yes No
Transceiver
module correct? Replace transceiver
module Resolved?
No Yes
Yes No
Fiber correct? Replace fiber Resolved?
No Yes
Yes No
Contact H3C Support End
Local port
operating correctly? Replace local port Resolved?
No Yes
Yes No
Peer port
operating correctly? Replace peer port Resolved?
No Yes
Yes No

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. Verify that the transceiver module is operating correctly:
a. Execute the display transceiver alarm interface command to examine the alarms present on the
transceiver module.
−The device displays None if no error occurs.
−The device displays alarms if the transceiver module fails or the type of the transceiver
module does not match the port type.
b. Use an optical power meter to verify that the Tx power and Rx power of the transceiver module
are stable and are within the correct range.
c. Execute the display transceiver interface command to verify that the wavelength and
transmission distance of the local transceiver module are consistent with the wavelength and
transmission distance of the peer transceiver module.
[H3C] display transceiver interface gigabitethernet 1/0/15
GigabitEthernet1/0/15 transceiver information:
Transceiver Type : 1000_BASE_SX_SFP
Connector Type : LC
Wavelength(nm) : 850
Transfer Distance(m) : 550(50um),270(62.5um)
Digital Diagnostic Monitoring : YES
Vendor Name : H3C
Ordering Name : SFP-GE-SX-MM850-A
d. If the transceiver module is not operating correctly, replace it with a new H3C transceiver
module that matches the fiber port.
For more information about transceiver modules, see related installation guides.
4. Replace the fiber with a new one to verify that the fiber is in good condition.
5. Replace the local port with a new one to verify that the local port is operating correctly.
6. Replace the peer port with a new one to verify that the peer port is operating correctly.
7. If the problem persists, contact H3C Support.

17
10-Gigabit SFP+ fiber port fails to go up
Symptom
A 10-Gigabit SFP+ fiber port cannot go up.