Home > other >  H3C router recently often broken network, wan port has large error
H3C router recently often broken network, wan port has large error

Time:09-29

A huge view port status as follows, the output error and upload speed became very slow! Please inform what may be the cause!
GigabitEthernet3/1/0 of the current state: the UP
The Line protocol current state: the UP
Description: GigabitEthernet3/1/0 Interface
The Maximum Transmit Unit is 1500, and Hold The timer is 10 (SEC)
The Internet Address is XXXXX Primary
IP Packet Frame Type: PKTFMT_ETHNT_2, Hardware Address: XXX
IPv6 Packet Frame Type: PKTFMT_ETHNT_2, Hardware Address: XXX
Media type is twisted pair, the loopback not set, promiscuous mode not set
100 MB/s, Half - duplex, link type is autonegotiation
The Output flow - the control is disabled, the input flow - the control is disabled
The Output queue: (Urgent queuing: the Size/Length/Discards) 0/100/0
The Output queue: (Protocol queuing: the Size/Length/Discards) 0/500/0
The Output queue: (FIFO queuing: the Size/Length/Discards) 0/75/0
The Last clearing of counters: Never
The Last 300 seconds input rate 1346116.75 bytes/SEC, 10768928 bits/SEC and 1384.65 packets/SEC
The Last 300 seconds the output rate 185416.29 bytes/SEC, 1483328 bits/SEC and 996.35 packets/SEC
Input: 820722568 packets, 909557616439 bytes, 0 no buffers
39396 broadcasts and multicasts 0, 0 pauses
0 errors, 0 runts, 0 giants
CRC, 0 and align errors, 0 overruns
0 dribbles, 0 drops
Output: 576235929 packets, 150231359169 bytes
312 broadcasts and multicasts 0, 0 pauses
107488952 errors, 0 underruns, 21309687 collisions
86179265 deferred, lost 0 carriers

CodePudding user response:

Exporters, have a look, the cat cable, light in a root

CodePudding user response:

Collisions error is commonly caused by duplex, look at your display configuration of the port, port to negotiate for half duplex, into a mandatory full-duplex should be ok,

CodePudding user response:

Upstairs OK!

CodePudding user response:

Try to enforce a full-duplex and see,

CodePudding user response:

The same problem appear, thanks to upstairs
  • Related