03-17-2011 04:13 PM - edited 03-06-2019 04:08 PM
Since install we have been having slowdowns in the network. We moved the SVI's back to our 6500's and had some improvement. After looking at the traffic for a couple of weeks, we see that we have packets showing up out of sequence.
My 1st thought was EIGRP load balancing’s default behavior, like we had per packet load balancing but turns out that is not on.
As of today we feel like we have bumped up against this bug in the code and will have to upgrade the code:
Unicast Packets not Forwarded via Peer-Link with Peer-Gateway Enabled | |
Symptom: |
Anyone else seen anything like this or have advance about where to look next?
03-20-2011 11:08 PM
5.1.2 is subject to "CSCtl85080 Netstack(vPC): MBUF failure due non standared size unicast ARP requests", and it appears that you have most of the conditions met to trigger this bug as well:
o vPC domain running 5.1.2
o peer-gateway enabled
o 3rd device connected via 1 leg vPC to SW01
o Unicast ARP requests (re-arp) are targeting SW02. Since its 1 leg vPC, the packets has to hit SW01, gets punted to Netstack, and finally tunneled to SW02.
o if the ARP packet size is not standard (not 64 bytes), SW01 will experience MBUF failures and will drop the ARP replies causing SW02 to drop all traffic targeting the related IP addresses.
The bug is fixed in 5.1.3, and the workaround is to disable the Peer-gateway feature, if possible. You can verify if you are hitting this bug by issuing "show ip arp internal buffers":
ARP Packet MBUF status:
Packet mbuf statistics:
mbufs obtained from page pool 30 --> should be around ~20 normally
m_bytes 8144 --> should be around 4000 normally
thanks
zz
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide