Wired Intelligent Edge

 View Only
  • 1.  Question about QoS on Procurve switches

    Posted Mar 14, 2025 05:35 AM
    Edited by Herman Robers Mar 17, 2025 05:09 AM

    Hi,

    I setup QoS on our network switches which are all Procurve/Aruba.  If I look at the command, show interface queues [port number,]  I can see if there are any drops due to congestion.

    When I do that command on the ETH interface that connects to our Aruba wireless controller, I see the most drops in Q1:

    switch# sh interface queues a17

     Status and Counters - Port Counters for port A17

      Name  : Aruba-Primary
      Link Status      : Up
      Port Enabled     : Yes
      Port Totals (Since boot or last clear) :
       Rx Packets      : 1,121,417,377      Tx Packets      : 1,157,635,163
       Rx Bytes        : 3,134,138,169      Tx Bytes        : 4,060,872,517
       Rx Drop Packets : 0                  Tx Drop Packets : 615,860
       Rx Drop Bytes   : 0                  Tx Drop Bytes   : 866,746,192

      Egress Queue Totals (Since boot or last clear) :
         Tx Packets         Dropped Packets    Tx Bytes           Dropped Bytes
     Q1  347,175,323        528,989            378,345,756,886    742,624,654
     Q2  910,876            0                  379,784,933        0
     Q3  720,055,318        86,589             531,821,082,168    123,714,184
     Q4  2,890,254          26                 3,492,622,776      37,544
     Q5  37,539,447         31                 34,274,523,625     44,270
     Q6  33,740,343         225                27,541,578,923     325,540
     Q7  12,726,796         0                  7,069,669,915      0
     Q8  2,596,839          0                  388,447,992        0

    Looking at the switches, it appears that Q3 is priority 0 and guaranteed 30 percent of the bandwidth.  I believe this to be normal traffic (best effort) probably Internet browsing, etc.

    Can anyone tell me what type of traffic is in Q1?  I'm wondering what is getting dropped, and what type of traffic that is?  according to what I'm seeing in the switch, this is categorized as priority 1.  I'm just using the Procurve defaults:

    Egress Queue Configuration
    Number of Queues: 8
    Queue  | 802.1p Priorities
     1               1
     2               2
     3               0
     4               3
     5               4
     6               5
     7               6
     8               7
    Outbound Guaranteed Minimum Bandwidth %

    Port   Q1  Q2     Q3  Q4     Q5  Q6  Q7  Q8
     ------ --- ------ --- ------ --- --- --- --------------
     A1     2  3      30  10     10  10  15  20


  • 2.  RE: Question about QoS on Procurve switches
    Best Answer

    Posted 26 days ago

    It's hard to say which traffic is placed in queue 1. By default AOS-S (Procurve) switches will trust the 802.1p tag in the packets. If the 802.1p tag is set to priority 1 the packets will be placed in queue 1. Queue 1 is also known as the background queue.

    To find out which traffic is marked as background you can make a packet capture and filter on 802.1p tag 1. The switches can also log traffic using ACL's. With a MAC ACL you can match all traffic with CoS / 802.1p value 1. For example:

    mac-access-list extended "300"
         10 permit any any any cos 1 log
         20 permit any any any
       exit
    

    Then apply the MAC access list on 1 or more VLANs.



    ------------------------------
    Willem Bargeman
    Systems Engineer Aruba
    ACEX #125
    ------------------------------



  • 3.  RE: Question about QoS on Procurve switches

    Posted 25 days ago

    That's a great idea I'll try that.