Aruba & ProVision-based
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to Clean Giants Rx Error in ProCurve Switch 5406zl(J8697A)

 
naempakcan
Occasional Visitor

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 %

2 REPLIES 2
Kemosabe
Occasional Advisor

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.

EricAtHP
Esteemed Contributor

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.