- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- Re: Understanding interface errors comware 5
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2018 01:14 AM - edited 09-13-2018 12:23 AM
09-12-2018 01:14 AM - edited 09-13-2018 12:23 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2018 04:19 AM
09-13-2018 04:19 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2018 06:47 AM - edited 09-17-2018 06:48 AM
09-17-2018 06:47 AM - edited 09-17-2018 06:48 AM
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).
I am an HPE Employee