4/12/2018

Arista EOS Trouble-shooting ipv4/v6 packet loss

Steps:
  • stop traffic and clear hw/sw drop counter
    • clear hardware counter drop - show hardware counter drop
    • clear counter - show cpu counter queue
  • start traffic, and repeat trigger or test case, hold for some time then stop traffic
  • check drop counter:
    • show hard counter drop
    • show cpu counter queue | nz
  • repeat this step along the data path if needed
Output:

wa462.bug228215.01:04:40#sh cpu counters queue | nz
....
---------------------------------------------------------------------------------------------------------------
Jericho5.0:
CPU Queue                                         Pkts             Octets           DropPkts         DropOctets

---------------------------------------------------------------------------------------------------------------
CpuQueueLinkLocal                                    5                610                  0                  0
CpuQueueLldp                                        31               8060                  0                  0
CpuQueueBgp                                         60               5370                  0                  0
CpuQueueL3DstMiss                               469817          121682603           89773442        23251321478
CpuQueueL3LpmOverflow                             1693             438487             754666          195458494
Jericho5.1:
CPU Queue                                         Pkts             Octets           DropPkts         DropOctets

CpuQueueL3DstMiss means, 1) unresolved ipv4 arp; 2) unresolved ipv6 neighbor. 

Solution:

After configuring no platform sand ipv6 host-route exact-match", the traffic is recovered. 

Finally it turns out that I missed the vxlan config. 

1 comment:

  1. Nice and good article. It is very useful for me to learn and understand easily. Thanks for sharing your valuable information and time. Please keep updating Hadoop Admin Online Training

    ReplyDelete