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

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

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 "Troubleshooting 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

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

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

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.

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.

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:

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.

Troubleshooting flowchart

Figure 4 Troubleshooting link up failure on a port

Solution

To resolve the problem:

1. Verify that the speed and duplex mode of the local port match the speed and duplex mode of the peer port:

a. Execute the display interface 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.

10-Gigabit SFP+ fiber port fails to go up

Symptom

A 10-Gigabit SFP+ fiber port cannot go up.

Troubleshooting flowchart

Figure 5 Troubleshooting link up failure on a port

Solution

To resolve the problem:

1. Verify that the speed and duplex mode of the local port match the speed and duplex mode of the peer port:

a. Execute the display interface 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 on the device. An SFP+ cable is suitable for short connections.

b. If the local port can go up, replace the peer port with a new one 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 to verify that the local port is operating correctly.

4. Verify that the transceiver module is operating correctly:

a. Execute the display transceiver alarm interface command to examine the alarms present on the transceiver module.

- The device displays None if no error occurs.

- The device displays alarms if the transceiver module fails or the type of the transceiver module does not match the port type.

b. Use an optical power meter to verify that the Tx power and Rx power of the transceiver module are stable and are within the correct range.

[H3C] display transceiver interface Ten-GigabitEthernet 1/0/15

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

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

<H3C> display diagnostic-information

Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y

Error frames (for example, CRC errors) on a port

Symptom

In the output from the display interface command, error frames exist (for example, CRC error frames).

Troubleshooting flowchart

Figure 6 Troubleshooting error frames (for example, CRC errors) on a port

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.

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.

[H3C] display transceiver diagnosis interface gigabitethernet1/0/1

GigabitEthernet1/0/1 transceiver diagnostic information:

Current diagnostic parameters:

Temp.(°C) Voltage(V) Bias(mA) RX power(dBM) TX power(dBM)

40 3.34 1.13 -20.43 0.20

3. Verify that the port configurations are correct:

a. Execute the display interface brief command.

b. Determine whether the speed and duplex mode of the port match the speed and duplex mode of the peer port.

c. If they do not match, use the speed command and the duplex command to set the speed and duplex mode for the port.

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:

- Intermediate links and devices, including optical-to-electrical converters, cable terminal racks, and transmission devices.

- Transmission medium, including network cables, optical fibers, and transceiver modules.

c. Examine the port:

- If the port is a copper port, directly connect the port to a PC.

- If the port is a fiber port, replace the transceiver module plugged into the port.

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

¡ Use the display diagnostic-information command to collect the diagnostic information.

¡ Contact H3C Support.

<H3C> display diagnostic-information

Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y

Failure to receive packets

Symptom

A port is up, but it cannot receive packets.

Troubleshooting flowchart

Figure 7 Troubleshooting the failure to receive packets

Solution

To resolve the problem:

1. Examine the packet statistics of the port:

a. (Optional.) Use the reset counter interface command in user view to clear the packet statistics of the port.

This command resets the values of each statistical field to 0, so that you can view the statistics changes more clearly.

b. Determine whether the ports at both ends are always up, and use the display interface command to determine whether the number of incoming packets is accumulating. At the same time, examine the outgoing packet statistics of the peer port.

c. View the values of the error packet fields and determine whether the number of error packets is accumulating.

2. Verify that the port configurations do not affect packet receiving:

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.

H3C 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 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:

- Intermediate links and devices, including optical-to-electrical converters, cable terminal racks, and transmission devices.

- Transmission medium, including network cables, optical fibers, and transceiver modules.

c. Examine the port:

- If the port is a copper port, directly connect the port to a PC.

- If the port is a fiber port, replace the transceiver module plugged into the port.

4. If you determine that the configurations, the peer port, and the link are correct but the problem persists, perform the following tasks:

¡ Use the display diagnostic-information command to collect the diagnostic information.

¡ Contact H3C Support.

<H3C> display diagnostic-information

Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y

Failure to send packets

Symptom

A port is up, but it cannot send packets.

Troubleshooting flowchart

Figure 8 Troubleshooting the failure to send packets

Solution

To resolve the problem:

1. Examine the packet statistics of the port:

a. (Optional.) Use the reset counter interface command in user view to clear the packet statistics of the port.

This command resets the values of each statistical field to 0, so that you can view the statistics changes more easily.

b. Determine whether the ports at both ends are always up, and use the display interface command to determine whether the number of outgoing packets is accumulating.

c. Determine whether the number of error packets is accumulating.

2. Verify that the port configurations do not affect packet sending:

a. Use the display interface brief command to verify that the port configurations are correct.

The port configurations include the duplex mode, speed, port type, and VLAN configurations of the ports at both ends of the link.

b. If configuration errors exist, modify the port configurations. If the number of 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.

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

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.

- If the port is a fiber port, replace the transceiver module.

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:

¡ Use the display diagnostic-information command to collect the diagnostic information.

¡ Contact H3C Support.

<H3C> display diagnostic-information

Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y

Related commands

This section lists the commands that you might use for troubleshooting ports.

Command	Description
display diagnostic-information	Displays or saves running status data for multiple feature modules.
display interface	Displays Ethernet interface information.
display interface brief	Displays brief interface information.
display link-aggregation summary	Displays the summary information for all aggregation groups.
display stp brief	Displays brief spanning tree status and statistics.
display transceiver alarm interface	Displays the current transceiver module alarms.
display transceiver diagnosis interface	Displays the present measured values of the digital diagnosis parameters for transceiver modules.
display transceiver interface	Displays the key parameters of transceiver modules.

Troubleshooting IRF

This section provides troubleshooting information for common IRF problems.

IRF fabric establishment failure

Symptom

A device cannot be added to an IRF fabric.

Troubleshooting flowchart

Figure 9 Troubleshooting IRF fabric establishment failure

Solution

To resolve the problem:

1. Execute the display irf command to verify that the number of member devices in the IRF fabric does not exceed the upper limit of four.

If the upper limit is reached, you cannot add new member devices to the IRF fabric.

2. Verify that the member ID of the device does not conflict with any member devices in the IRF fabric:

a. Execute the display irf command to view member IDs.

b. If the member ID of the device is not unique, use the irf member renumber command to assign a new member ID to the device.

3. Verify that the physical IRF links are connected correctly:

IMPORTANT:

When you connect two neighboring IRF members, you must connect the physical ports of IRF-port 1 on one member to the physical ports of IRF-port 2 on the other.

a. Execute the display irf configuration command on each member device, and check the IRF-Port1 and IRF-Port2 fields for IRF port bindings.

b. Verify that the physical IRF connections are consistent with the IRF port bindings.

c. If there are inconsistencies, reconfigure the IRF port bindings or reconnect the physical IRF ports.

4. Verify that IRF links are 10 Gbps:

a. Verify that the transceiver modules or cables for IRF connection are labeled with 10Gbps or SFP+.

b. Replace a transceiver module or cable if it is not for 10 Gbps connection.

5. Verify that all IRF links are up:

a. Execute the display irf topology command, and then check the Link field.

b. If the Link field for an IRF port displays DOWN, execute the display interface command.

c. Check the current state field for each physical port bound to the IRF port:

- If the field displays DOWN ( Administratively ), execute the undo shutdown command to bring up the port.

- If the field displays DOWN, verify that the transceiver modules or cables are operating correctly.

If the IRF port is down when it contains at least one up link, go to step d.

d. Save the configuration, and then execute the irf-port-configuration active command in system view to activate the IRF port configuration.

IMPORTANT:

Activating IRF port configuration requires a reboot. To prevent configuration loss, you must save the configuration before you execute the irf-port-configuration active command.

6. Verify that the member device is running the same software version as the IRF fabric:

a. Execute the display version command to identify the software version.

b. Upgrade the member device to use the same software version as the IRF fabric.

NOTE:

Typically, the irf auto-update enable command can automatically synchronize a member device with the software version of the master device. However, the synchronization might fail when the gap between the software versions is too large. For more information, see the release notes for the software versions.

7. If the problem persists, contact H3C Support.

Execute the display diagnostic-information command, save the diagnostic information, and provide it to H3C Support.

<H3C> display diagnostic-information

Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y

IRF split

Symptom

An IRF fabric splits.

Troubleshooting flowchart

Figure 10 Troubleshooting IRF split

Solution

To resolve the problem:

1. Verify that the IRF physical ports are operating correctly:

a. Execute the display trapbuffer command or view system logs to check for physical IRF link down events that occurred close to the split time.

b. If the split followed an IRF link down event, execute the display interface command to check port statistics for CRC errors.

c. If the port is an SFP+ port, execute the display transceiver diagnosis command to verify that the transmit and receive power does not exceed the power specifications of the fiber-optic module.

2. Remove hardware problems that might cause recurring IRF split events:

a. Execute the display version command to identify the uptime of member devices.

b. Compare the uptime of member devices to determine whether a member device rebooted before the IRF split.

c. If the IRF split is caused by a device reboot, use the methods described in "Unexpected switch reboot" to resolve the problem.

3. If the problem persists, contact H3C Support.

Execute the display diagnostic-information command, save the diagnostic information, and provide it to H3C Support.

<H3C> display diagnostic-information

Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y

BFD MAD failure

Symptom

BFD MAD fails to detect an IRF split event. Two IRF fabrics are operating with the same Layer 3 configurations, including the same IP address.

Troubleshooting flowchart

Figure 11 Troubleshooting the BFD MAD failure

Solution

To resolve the problem:

1. Verify that BFD MAD link connections are correct:

¡ If you do not use an intermediate device, verify that each pair of member devices has a dedicated BFD MAD link.

¡ If you use an intermediate device, verify that each member device has a dedicated BFD MAD link with the intermediate device.

2. Verify that all physical ports used for BFD MAD are up:

a. Execute the display interface command.

b. Check the current state field in the command output:

- If the field displays DOWN ( Administratively ) for a port, execute the undo shutdown command to bring up the port.

- If the field displays DOWN for a port, check the physical link for a link failure.

3. Verify that the BFD MAD VLAN interface is configured correctly:

a. Execute the display mad verbose command.

b. Check the MAD BFD enabled interface field to verify that VLAN-interface 1 is not used for BFD MAD.

c. If VLAN-interface 1 is used for BFD MAD, disable BFD MAD on VLAN-interface 1, and then enable BFD MAD on another VLAN interface.

d. Verify that the BFD MAD-enabled VLAN interface does not have any other features, including VPN.

e. Execute the display interface command to verify that the interface does not have the following IP addresses:

- IP address assigned by using the ip address command.

- VRRP virtual IP address.

4. Verify that the BFD MAD VLAN and physical ports in the VLAN are configured correctly:

a. Execute the display vlan command to verify the following items:

- The BFD VLAN contains all physical ports used for BFD MAD.

- The BFD VLAN does not contain physical ports that are not used for BFD MAD.

NOTE:

If you use an intermediate device, 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. Verify that the MAD IP addresses are correct:

a. Execute the display mad verbose command.

b. Check the mad ip address field to verify the following items:

- Each member device has a MAD IP address.

- All MAD IP addresses are on the same subnet.

- The MAD IP addresses are not addresses being used on the IRF fabric.

6. If the network has multiple IRF fabrics, execute the display mad verbose command to verify that their BFD MAD VLANs are different.

7. If the physical ports in the BFD MAD VLAN are down continually:

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. If the problem persists, contact H3C Support.

Execute the display diagnostic-information command, save the diagnostic information, and provide it to H3C Support.

<H3C> display diagnostic-information

Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y

LACP MAD failure

Symptom

LACP MAD fails to detect an IRF split event. Two IRF fabrics are operating with the same Layer 3 configurations, including the same IP address.

Troubleshooting flowchart

Figure 12 Troubleshooting LACP MAD failure

Solution

To resolve the problem:

1. Verify that the intermediate device is an H3C 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 device has a link in the link aggregation with the intermediate device.

3. Verify that the link aggregation is operating in dynamic mode.

To enable dynamic aggregation mode, use the link-aggregation mode dynamic command.

4. Verify that the aggregate interface and its member ports are up:

a. Execute the display interface command.

b. Check the current state field of the aggregate interface:

- If the field displays DOWN ( Administratively ), execute the undo shutdown command to bring up the interface.

- If the field displays DOWN, check the state of all its physical ports.

An aggregate interface goes down only if all its physical ports are down.

c. Check the current state field of each member port:

- If the field displays DOWN ( Administratively ), execute the undo shutdown command to bring up the port.

- If the field displays DOWN, check the physical link of the port for a link failure.

5. If the intermediate device is also an IRF fabric, verify that the IRF domain IDs of the two IRF fabrics are unique:

CAUTION:

The IRF member devices send extended LACPDUs with TLVs that convey the domain ID and the active ID of the IRF fabric. For correct split detection, make sure the IRF fabric has a unique domain ID. False detection causes IRF split.

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. If the physical ports in the link aggregation are down continually:

a. Execute the display trapbuffer command or use system logs to check for port down events close to the split time.

b. Identify the cause of the event and remove the issue.

7. If the problem persists, contact H3C Support.

Execute the display diagnostic-information command, save the diagnostic information, and provide it to H3C Support.

<H3C> display diagnostic-information

Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y

Related commands

This section lists the commands that you might use for troubleshooting IRF:

Command	Description
display diagnostic-information	Displays or saves the operating statistics for multiple feature modules.
display interface	Displays interface information.
display interface brief	Displays brief interface information.
display irf	Displays IRF fabric information, including the member ID, role, priority, bridge MAC address, and description of each IRF member.
display irf configuration	Displays the IRF configuration on each member device.
display irf topology	Displays the IRF topology.
display mad verbose	Displays detailed MAD configuration.
display transceiver diagnosis	Displays the present measured values of the digital diagnosis parameters for transceiver modules.
display trapbuffer	Displays trap data in the trap buffer.
display version	Displays system version information.
display vlan	Displays VLAN information.

Troubleshooting QoS and ACL

This section provides troubleshooting information for common QoS and ACL problems.

ACL application failure for unsupported ACL rules

Symptom

The system fails to apply a packet filter or an ACL-based classifier in a QoS policy to the hardware. It displays an error message that the ACL is not supported:

Error: Slot=2 Fail to apply or refresh packet filter policy 3180 rule 5 on interface Vlan-interface20. Not supported.

Troubleshoot ing flowchart

Figure 13 Troubleshooting an ACL application failure

Solution

To resolve the problem:

1. Verify that the ACL is configured correctly:

Execute the display acl command to identify whether the ACL is configured correctly. If the ACL is configured incorrectly, reconfigure it.

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. If the problem persists, contact H3C Support.

Execute the display diagnostic-information command, save the diagnostic information, and provide it to H3C Support.

<H3C> display diagnostic-information

Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y

ACL application failure for insufficient resources

Symptom

The system fails to apply a packet filter or an ACL-based classifier in a QoS policy to the hardware. It displays one of the following error messages that the hardware resources are not sufficient:

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 14 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. In IRF mode, if the ACL is applied globally (for example, to a VLAN), identify the remaining ACL resources on all IRF devices.

[H3C] display acl resource

Interface:

GE3/0/1 to GE3/0/24

---------------------------------------------------------------------

Type Total Reserved Configured Remaining Usage

---------------------------------------------------------------------

VFP ACL 2048 512 0 1536 25%

IFP ACL 4096 1536 0 2560 37%

IFP Meter 2048 768 0 1280 37%

IFP Counter 2048 768 0 1280 37%

EFP ACL 512 0 0 512 0%

EFP Meter 256 0 0 256 0%

EFP Counter 512 0 0 512 0%

Interface:

GE3/0/25 to GE3/0/50, XGE3/0/51 to XGE3/0/52

---------------------------------------------------------------------

Type Total Reserved Configured Remaining Usage

---------------------------------------------------------------------

VFP ACL 2048 512 0 1536 25%

IFP ACL 4096 1536 0 2560 37%

IFP Meter 2048 768 0 1280 37%

IFP Counter 2048 768 0 1280 37%

EFP ACL 512 0 0 512 0%

EFP Meter 256 0 0 256 0%

EFP Counter 512 0 0 512 0%

¡ IFP—Resource usage for inbound traffic.

¡ EFP—Resource usage for outbound traffic.

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. If the problem persists, contact H3C Support.

Execute the display diagnostic-information command, save the diagnostic information, and provide it to H3C Support.

<H3C> display diagnostic-information

Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y

ACL application failure without an error message

Symptom

The system applies a QoS policy that contains ACLs to the hardware. However, the ACL does not take effect.

Troubleshooting flowchart

Figure 15 Troubleshooting an ACL application failure

Solution

To resolve the problem:

1. Verify that overlapping ACL rules that have been applied exist.

a. Use one of the following commands to display applied ACLs:

- display qos policy user-defined

- display traffic classifier user-defined

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

Conflicting behaviors	Effective behavior
· redirect · filter permit	redirect
· redirect · filter deny	filter deny
· filter permit · filter deny	The behavior configured first.

3. If the problem persists, contact H3C Support.

Execute the display diagnostic-information command, save the diagnostic information, and provide it to H3C Support.

<H3C> display diagnostic-information

Save or display diagnostic information (Y=save, N=display)? [Y/N]:Y

Packet loss or forwarding failure

Symptom

The network experiences packet loss or packet forwarding failure. You can use ACLs to count traffic statistics to determine the location of the fault.

Troubleshooting flowchart

Figure 16 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. Configure a QoS policy and apply it to an interface:

Figure 17 Traffic path

a. Configure a QoS policy according to the traffic characteristics. In this example, use a destination IP address 2.2.2.2.

<H3C> system-view

System View: return to User View with Ctrl+Z.

[H3C] time-range t1 from 12:00 11/11/2013 to 12:01 11/11/2013

[H3C] acl number 3000 name geliACL

[H3C-acl-adv-3000-geliACL] rule 0 permit ip destination 2.2.2.2 0 time-range t1

[H3C-acl-adv-3000-geliACL] quit

[H3C] traffic classifier count

[H3C-classifier-count] if-match acl 3000

[H3C-classifier-count] quit

[H3C] traffic behavior count

[H3C-behavior-count] accounting

[H3C-behavior-count] quit

[H3C] qos policy count

[H3C-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:

[H3C-qospolicy-count] quit

[H3C] interface gigabitethernet 1/0/1

[H3C-GigabitEthernet1/0/1] qos apply policy count inbound

3. Execute the display qos policy interface command to display traffic statistics on the interfaces:

¡ On GigabitEthernet 1/0/1 on Device B:

[H3C-GigabitEthernet1/0/1] display qos policy interface gigabitethernet 1/0/1

Interface: GigabitEthernet1/0/1

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.

¡ On GigabitEthernet 2/0/1 on Device C:

[H3C-GigabitEthernet2/0/1] display qos policy interface gigabitethernet 2/0/1

Interface: GigabitEthernet2/0/1

Direction: Inbound

Policy: count

Classifier: count

Operator: AND

Rule(s) : If-match ACL 3000

Behavior: count

Accounting Enable:

50 (Packets)

The output shows that a total of 50 packets match ACL 3000.

4. Compare the traffic statistics on the two interfaces. Packet loss or forwarding fault exists between Device B and Device C.

Related commands

This section lists the commands that you might use for troubleshooting QoS and ACLs.

Command	Description
display acl	Displays configuration and match statistics for ACLs.
display acl resource	Displays ACL resource usage.
display diagnostic-information	Displays or saves running status data for ACLs.
display qos policy interface	Displays information about the QoS policies applied to specified interfaces.
display qos policy user-defined	Displays user-defined QoS policy configuration.
display traffic classifier user-defined	Displays user-defined classes.

H3C S5830 Troubleshooting Guide-6W101

Newly-installed power supply failure

Solution

Troubleshooting IRF

Troubleshooting flowchart

Solution

ACL application failure without an error message

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us

Troubleshoot ing flowchart