Arista EOS Central Drop Counters

Transcription

1 Arista EOS Central Drop Counters eos.arista.com /eos f/drop-counters/ With this feature, user can fetch various internal hardware info from each switch and isolate the switch or fabric card or SerDes which is seeing abnormal internal. EOS aggregates following hardware from forwarding ASICs and fabric SerDeses: drop counters: IptCrcErrCnt, IngrReplFifoDrop, UcFifoFullDrop, DeqDeletePktCnt, RqpDiscardPacketCtr, RqpPC, McastDataBuffersDropCtr, PqpMcastPC, EnqPktCnt, IngressDiscardCounter, EgressDiscardCounter, FabricReceiveCellDiscard, SerdesCrcErrors, DchFifosDiscards, DchReordDiscards, DchFifosMulticastLow, RtpDrhMulticastLow, DchUnreachables, DcmFifosIp, DcmFifosTotal, DclFifosTotal Packet processor counters: dropvoqinportnotvlanmember, dropvoqinsaequalsda, dropvoqinsamulticast, dropvoqinrpf, dropvoqinipv6multicastsource, dropvoqinacl, dropvoqinnoarp, dropvoqinnullroute, dropvoqinrouteoverflow, dropvoqinpbr, dropvoqintunroute, dropvoqintunmpls, dropvoqinipv4checksumerror, dropvoqintungre, dropvoqinipv6versionerror, dropvoqinipv4versionerror, dropvoqintunvxlan, dropvoqinipv6unspecifieddestination, EgressAclDropCounter, The rate at which hardware seen in last 1 min, 10 min, 1 hr, 1 day and 1 week time intervals is maintained. This would give an idea if the hardware is happening continuously or in short bursts. For each drop counter, a threshold can be configured for syslog. Syslog message is generated every time a drop counter crosses a configured threshold from the last time the syslog message was generated. Logging is enabled by default. drop counter syslog logging is moved to EventMgr. More info at: Logging threshold configuration commands hardware counter drop log <countername> <threshold-value> have no effect. Contents [hide] Platform compatibility Configuration Drop counter Description Status Fabric Drop counters Show Commands 1/6

2 Examples Syslog Messages Platform compatibility DCS-7280E DCS-7500E series switches Configuration Command to configure syslog threshold for for a drop counter: Arista(config)# hardware counter drop log <counter-name> <count-threshold> Command to reset syslog threshold for a drop counter: Arista(config)# no hardware counter drop log <counter-name> Arista(config)# default hardware counter drop log <countername> Command to clear internal drop counters: Arista(config)# clear hardware counter drop Drop counter Description Name Type Description Drop Counter Ingress replication oversubscription Arad can only process 300Mpps, due to ingress replication due to ingress mirroring, copy to cpu. In particular this can happen when ingress only replication is enabled. Note that when this fifo gets large the mirror copies get dropped and packet goes back to unicast IRR Ingr Repl Fifo Drop (IngrReplFifoDrop) Ingress unicast oversubscription This counter should always be zero Uc Fifo Full Drop (UcFifoFullDrop) Voq Multicast These are multicast before replication due to multicast oversubscription. Note that storm control would be counted here. Queue discards in FMC0-3 and all ERP ports Stale packets in voqs These packets were in a voq for more than 500ms without getting credits so they were deleted since they are stale. This can be caused byoversubscribing with strict priority queueing iqm deleted packets ( DeqDeletePktCnt) 2/6

3 Packet corruption in dram These packets are dropped because the crc covering the packet and internal headers was wrong after reading the packet from dram memory. ipt crc packets (IptCrcErrCnt) Reassembly discarded packets These packets are dropped due to cell reassembly over the fabric, could be due to missing cell, mismatch in packet crc. Note with vlan floodsets when the vlan membership changes during traffic these counters can increment. Rqp Discard Packet (RqpDiscardPacketCtr) Multicast packets dropped due to lack of buffers buffering discards These multicast packets are dropped because of lack of global egress buffers. CGM Multicast Data Buffers Drop Fabric receive cell discard These cells were dropped due to oversubscription FDRDiscard Counter Aprimary + FDRDiscard Counter Bprimary + FDRFifo Discard Counter Aprimary + FDRFifo Discard Counter BPrimary Port not Vlan Member Port is not a member of the Vlan inportnotvlanmemberdropvoq SA equals DA Mac src address and dest address are the same insaequalsdadropvoq SA Multicast Rpf IPv4 version error IPv4 bad checksum Mac src address is a multicast address insamulticastdropvoq Packet fails Rpf check inrpfdropvoq IP version is invalid inipv4versionerrordropvoq The IPv4 checksum is bad inipv4checksumerrordropvoq IPv4 header length The IPv4 header length is invalid. These are now counted asdropvoqinipv4checksumerror inipv4headerlengtherrordropvoq IPv6 version error IPv6 unspecified destination IP version is invalid inipv6versionerrordropvoq IPv6 address is all zeros inipv6unspecifieddestinationdropvoq IPv6 multicast source address IPv6 source address is a multicast address inipv6multicastsourcedropvoq Ingress Acl Packets dropped by ingress Acl inacldropvoq No Arp Packets dropped because there is no arp entry. Arp entry could not be allocated in hw. dropvoqinnoarp 3/6

4 *Null Route Routed packets that were dropped because they matched the null route innullroutedropvoq Route Overflow Routed packets that were dropped because of a lpm table overflow inrouteoverflowdropvoq Pbr Route packets dropped because of Policy Based Routing inpbrdropvoq Tun Route Tunnel resource overflow intunroutedropvoq Tun Gre GRE tunnel resource overflow intungredropvoq Tun Mpls MPLS tunnel resource overflow intunmplsdropvoq Tun Vxlan VXLAN tunnel resource overflow intunvxlandropvoq *Note: Null route are also used for all cases where the next hop is set to nexthopdrop. This includes routes pointing to Null0, tunnel drop, tunnel gre, tunnel mpls and tunnel vxlan. These different will be broken out into their own drop voq s. Before, these were silently dropped and not counted. Fabric Drop counters Name Type Description Drop Counter DRH Multicast Low DCM0 Fifos Ip DCM Fifos Total Fabric multicast packet cell ( internal packet fragment ) dropped due to system wide fabric multicast oversubscription Unicast packet cell ( internal packet fragment ) dropped due to fifos overflow. Due to misconfiguration or hardware issue Unicast and fabric multicast cells dropped due to fifo overflow. For multicast this could be due to system multicast oversubscription for unicast should not happen. Status Show Commands To display hardware drop counts: Arista# show hardware counter drop 4/6

5 To display rates of hardware drop counts: Arista# show hardware counter drop rates Examples Arista# show hardware counter drop Summary: Total (A) : 0 Total Congestion (C) : 0 Total Packet Processor (P) : 104 Type Chip CounterName : Count : First Occurrence : Last Occurrence P Arad5/0 inportnotvlanmemberdropvoq : 46 : :47:28 : :32:00 P Arad5/4 inportnotvlanmemberdropvoq : 25 : :47:34 : :31:54 P Arad6/2 inportnotvlanmemberdropvoq : 23 : :44:52 : :31:48 P Arad5/2 inacldropvoq : 8 : :18:53 : :24:23 P Arad6/2 inacldropvoq : 2 : :14:53 : :15:17 Arista# show hardware counter drop rates Type Chip CounterName Count 1-Min 10-Min 1-Hour 1-Day 1-Week P Arad5/0 inportnotvlanmemberdropvoq NA NA P Arad5/4 inportnotvlanmemberdropvoq NA NA P Arad6/2 inportnotvlanmemberdropvoq NA NA P Arad5/2 inacldropvoq NA NA P Arad6/2 inacldropvoq NA NA Arista(config)# hardware counter drop log IptCrcErrCnt 100 Syslog threshold for IptCrcErrCnt = 100 Arista(config)# no hardware counter drop log IptCrcErrCnt Arista(config)# default hardware counter drop log IptCrcErrCnt Arista(config)# clear hardware counter drop Syslog Messages Example syslog message: 5/6

6 %HARDWARE-3-DROP_COUNTER: Internal drop 'DeqDeletePktCnt' occurred on Arad3/3 6/6