cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
438
Views
0
Helpful
4
Replies

Nexus interface output discards - CRC - Jumbo Frames

Dennis Topo Jr
Level 1
Level 1

Dear Cisco community. I wanted to get your take on some interface issues we've been having between or Nexus 9K and Catalyst C6807. Seeing CRC errors on the 6807 (wancore) - and output errors and discards on the connected links on the 2 Nexus switches (1 and 2) - it's a port channeled link - VPC across the 2 9Ks. I will include screen shots and a diagram here as well. These errors \ discards have yet to take notice in production but they are obviously unhealthy even though they are not rapidly increasing. Besides looking at cabling, I was hoping to get some insight on how best to troubleshoot this. We have jumbo frames enabled on some of the nexus ports for esxi servers and such - so these frames are present at the EtherChannel trunk links connecting our wancore. We of course do not want or need jumbo frames in our wancore \ wan links, so my question is, would these jumbo frames account for the discards and errors on seen on the nexus interfaces, and the crc\ input errors on the receiving wancore interfaces? I read that ideally, you want to separate your jumbo framed traffic, but w our hosted environment, and having everything L2 trunked, this is the situation we have. Appreciate any ideas or insight in advance! Thanks...Dennis

4 Replies 4

M02@rt37
VIP
VIP

Hello @Dennis Topo Jr 

Could you please run these two commands on both Nexus switch? I'm trying to rule out any vpc or mtu mismatches that might be contribute to the errors.

#show vpc brief
#show vpc consistency-parameters

 

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

Dennis Topo Jr
Level 1
Level 1

Thanks M02, for taking the time to look at this ! I put the output in the attached txt file : VPC-NK1-2.txt. Nothing glaring that I can see

assume you wanted the output with the "global" keyword  - show vpc consistency-parameters global

Hello @Dennis Topo Jr 

Thanks for these outputs. Consistency is ok.

Concerning mtu, do you have check both ends of the EtherChannel ?

If nexus shows mtu 9216, and the 6807 shows1500, this could be your problem.

 

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

Dennis Topo Jr
Level 1
Level 1

Thanks M02, 

Correct - that was my initial concern. The Nexus uplink interfaces \ associated port channel interfaces have the default MTU of 1500 - matching the 6807. My concern \ curiosity was the down-level interface ports (for esxi hosts) on the nexus that are configured as trunks, and set to use jumbo frames - and since those vlan tags are trunked on up to wan core as well, does that indeed pose an issue ?? Or, am I looking at cabling \ optics etc causing the errors? That's what I wanted to determine - again, appreciate your help