24
Solution
To resolve the problem:
1.
Verify that no error packets have been received on the local port:
a.
Execute the
display interface
command and check for error packets.
<Sysname>display interface Ten-GigabitEthernet1/0/25
Ten-GigabitEthernet1/0/25 current state: UP
Line protocol state: UP
IP Packet Frame Type: PKTFMT_ETHNT_2, Hardware Address: aa11-2233-4496
……
Last 300 seconds input: 0 packets/sec 10 bytes/sec 0%
Last 300 seconds output: 0 packets/sec 10 bytes/sec 0%
Input (total): 1438 packets, 480292 bytes
0 unicasts, 0 broadcasts, 1438 multicasts, 0 pauses
Input (normal): 1438 packets, - bytes
0 unicasts, 0 broadcasts, 1438 multicasts, 0 pauses
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
0 CRC, 0 frame, - overruns, 0 aborts
- ignored, - parity errors
Output (total): 1440 packets, 475200 bytes
0 unicasts, 0 broadcasts, 1440 multicasts, 0 pauses
Output (normal): 1440 packets, - bytes
0 unicasts, 0 broadcasts, 1440 multicasts, 0 pauses
Output: 0 output errors, - underruns, - buffer failures
0 aborts, 0 deferred, 0 collisions, 0 late collisions
0 lost carrier, - no carrier
b.
If the statistics are not zero, the following failures might occur:
−
Interface hardware failure
—To test such a failure, connect the cable that is connected
to the local port to a correctly operating port (for example, Port A) with the same
configurations as the local port. If Port A forwards traffic correctly, you can determine
that the hardware of the local port fails. In this event, you must replace the local port with
a correctly operating port.
−
Transceiver module, fiber, or twisted pair failure
—To test and resolve such a failure,
replace the transceiver module, fiber, or twisted pair with a good one.
−
Inconsistent configurations
—Verify that the configurations (including speed and
duplex mode) of the peer are consistent with the local port. If they are inconsistent,
modify the configurations of the local port.
c.
If the problem persists, contact H3C Support.
When you contact H3C Support, provide the following diagnostic information if packet loss
occurs on the chip port with which the interface is associated:
# Execute the
debug port map slot 1
command in probe view to identify the chip port with
which the interface is associated.
[Sysname-probe]debug port map slot 1
[Interface] [Unit] [Port] [Name] [Combo?] [Active?] [IfIndex] [MID] [Link]
==============================================================================
=
SGE1/0/1 0 3 xe1 no no 0x1 1 up
SGE1/0/2 0 2 xe0 no no 0x2 1 down
SGE1/0/3 0 5 xe3 no no 0x3 1 down