- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Unable to Clean Giants Rx Error in ProCurve Switch...
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
12-17-2015 01:16 AM
12-17-2015 01:16 AM
Unable to Clean Giants Rx Error in ProCurve Switch 5406zl(J8697A)
Hi Team,
I have unable to clean the Giants Rx errors in my Core SW at port D19. I have already clear statistic D19 and the errors disappear, but after 30 to 45 minutes error appear again. Fyi, port D19 is not used anymore. Hope you guys can help/advise and appreciate I so much.
CoreSwitch# sh int d19
Status and Counters - Port Counters for port D19
Name :
MAC Address : 2c4138-c5b1a5
Link Status : Down
Totals (Since boot or last clear) :
Bytes Rx : 656,911,662 Bytes Tx : 3448875674
Unicast Rx : 2,059,566,330 Unicast Tx : 1,875,205,509
Bcast/Mcast Rx : 13,260,911 Bcast/Mcast Tx : 6,531,089
Errors (Since boot or last clear) :
FCS Rx : 3,271,226 Drops Tx : 0
Alignment Rx : 0 Collisions Tx : 0
Runts Rx : 0 Late Colln Tx : 0
Giants Rx : 17,413 Excessive Colln : 0
Total Rx Errors : 3,288,639 Deferred Tx : 0
Others (Since boot or last clear) :
Discard Rx : 0 Out Queue Len : 0
Unknown Protos : 0
Rates (5 minute weighted average) :
Total Rx (bps) : 0 Total Tx (bps) : 0
Unicast Rx (Pkts/sec) : 0 Unicast Tx (Pkts/sec) : 0
B/Mcast Rx (Pkts/sec) : 0 B/Mcast Tx (Pkts/sec) : 0
Utilization Rx : 0 % Utilization Tx : 0 %
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-08-2016 08:53 AM
01-08-2016 08:53 AM
Re: Unable to Clean Giants Rx Error in ProCurve Switch 5406zl(J8697A)
What version of firmware are you running on the switch? I assume it's the latest version? After clearing out statistics on that port, have you rebooted the switch soon after? I know that may not be feasible, but it's at least worth a shot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-08-2016 08:59 AM
01-08-2016 08:59 AM
Re: Unable to Clean Giants Rx Error in ProCurve Switch 5406zl(J8697A)
Giants just mean that the switch recieved a packet that is larger than normal size of 1500 Bytes. This could be due to something sending jumbo packets, tagged packets when not configured to accept them, vxlan packets, etc. That said, you don't have that many and it may not be worth worring about. If you do want to investigate, but a packet capture device on the connection and look for larger packets. That will give you an idea what they are and who they are coming from. If you just want to allow them, then enable jumbo frames on the associated VLAN.
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP