Comware Based
cancel
Showing results for 
Search instead for 
Did you mean: 

Understanding interface errors comware 5

 
Highlighted
Regular Advisor

Understanding interface errors comware 5

Hi all,

I'm struggling to finding excessive details on errors on physical interfaces, at the moment I'm interested in "aborts". The only info I found states that:

"Packets that failed to be forwarded at the MAC layer due to network congestion."

.

Input (total):  711778 packets, 125017408 bytes
         705716 unicasts, 1097 broadcasts, 4965 multicasts, 0 pauses
 Input (normal):  711778 packets, - bytes
         705716 unicasts, 1097 broadcasts, 4965 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): 1665475 packets, 721243485 bytes
         961260 unicasts, 571926 broadcasts, 131654 multicasts, 0 pauses
 Output (normal): 1664840 packets, - bytes
         961260 unicasts, 571926 broadcasts, 131654 multicasts, 0 pauses
 Output: 635 output errors, - underruns, - buffer failures
         635 aborts, 0 deferred, 0 collisions, 0 late collisions
         0 lost carrier, - no carrier

 

Any help would be much appriciated

2 REPLIES 2
Highlighted
Regular Advisor

Re: Understanding interface errors comware 5

Could the cause be at layer 2? I've noticed when chenging duplex and speed to fixed values I started seeing input errors but no output this time

Highlighted
HPE Pro

Re: Understanding interface errors comware 5

Hi,

Greetings!

Please find the details about 'aborts'.

 

Aborts - Total number of illegal inbound packets:

• Fragment frames—CRC error frames shorter than 64 bytes. The length can be an integral or non-integral value.

• Jabber frames—CRC error frames greater than the maximum frame length supported on the Ethernet interface (with an integral or non-integral length). For an Ethernet interface that does not permit jumbo frames, jabber frames refer to CRC error frames greater than 1518 bytes (without VLAN tags) or 1522 bytes (with VLAN tags). For an Ethernet interface that permits jumbo frames, jabber frames refer to CRC error frames greater than the maximum length of Ethernet frames that are allowed to pass through the interface (which is configured when you configure jumbo frame support on the interface). • Symbol error frames—Frames that contained at least one undefined symbol.

• Unknown operation code frames—Non-pause MAC control frames

• Length error frames—Frames whose 802.3 length fields did not accord with the actual frame length (46 to 1500 bytes).

 

http://www.h3c.com.hk/Technical_Support___Documents/Technical_Documents/Switches/H3C_S5830/H3C_S5830_Series_Switches/Command/Command_Reference/H3C_S5830_CR-Release_1109-6W100/03/

 

 

Thank You!
I am an HPE Employee

Accept or Kudo