Wired Intelligent Edge

 View Only
  • 1.  Question about QoS on Procurve switches

    Posted Mar 14, 2025 01:56 PM

    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

    Posted Mar 14, 2025 07:57 PM

    802.1p of value 1 has the lowest priority and generally it is used for background traffic.

    and 802.1p value of 0 is used for best-effort traffic



    ------------------------------
    If my post was useful accept solution and/or give kudos.
    Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
    ------------------------------



  • 3.  RE: Question about QoS on Procurve switches

    Posted Mar 17, 2025 04:14 AM
      |   view attached

    Hi,

    If WMM QoS is configured p-bit = 1 and 2 is background traffic according to the standard which is a bit stupid because the p-bit settings for WMM in Wifi is not the same as for for wired QoS. What you could do is to change the number of queues on the AOS-S switch from 8 to 4 or 2 with the command qos queue-config < 2-queues | 4-queues | 8-queues>
    That will change the % allocated to each queue, it requirers a reboot of the switch. Test in on a non production switch to see what is best for you. 




  • 4.  RE: Question about QoS on Procurve switches

    Posted Mar 17, 2025 10:26 AM

    Thanks for the replies.  Good graphic.  I think I'm ok with the controller grouping 8 CoS queues into 4 WMM queues.  Do you know what the default guaranteed bandwidth is for the WMM queues and the wireless controllers?




  • 5.  RE: Question about QoS on Procurve switches

    Posted Mar 18, 2025 04:57 AM

    The controller uses Strict Priority on all 4 queues.
    p-bit 6,7 queue 0
    p-bit 4,5 queue 1
    p-bit 2,3 queue 2
    p-bit 0,1 queue 3