1. For "F2E Egress Queue Drops" - Create a LAG (MLT / LACP) to enable more bandwidth as needed.
2. For "Fabric Drops" - Move port configuration over to a port in a new "lane", THEN swap the physical port over to ease up on the traffic load being processed in said
In addition, the CLI output that we have collected is used to determine (approximately), how much oversubscribed the link is.
If a particular queue on a port indicates “total pages 1000, dropped pages 200”, then we know the offered load was 20% (200/1000) greater than the link speed.
That said, there are TWO exceptions, queues 62/63 (or 6/7, dependent on the card type).
These queues are the “high priority” queues and both are rate-limited to prevent denial of service attacks.
The queues 6 or 62 are limited to 50% of link bandwidth, while 7 or 63 are limited to 5%. Queues are selected, one-to , by priority. Priorities 1-5 correspond to queues 4-0 (note inversion), priority 0 to 55 (or 5), priority 6 to 62 (or 6), and priority 7 to 63 (or 7).
So, if one attempts to send >500M at priority 6 to a port, then egress queue drops will occur.
If it is either of the high priority queues which are showing egress queue drops, the user can increase the limits via the CLI’s QoS configuration commands.