<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: QoS on ICX switch in ICX Switches</title>
    <link>https://community.ruckuswireless.com/t5/ICX-Switches/QoS-on-ICX-switch/m-p/30177#M1595</link>
    <description>Couple of things.&amp;nbsp; Make sure you rate limit the interface to match what your bandwidth is from your provider assuming this is going into a WAN or Metro-E circuit of some type.&amp;nbsp; The QOS mechanism works on bandwidth same as Cisco so if it thinks it has 1gbps then it won't shape the traffic until it starts getting full. &amp;nbsp; &lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Each interface needs to have the (trust dscp) just like Cisco.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;It is not necessary to grab the traffic in an ACL if the devices (phones) are marking the traffic with DSCP EF (46) or any DSCP marked traffic as the QOS mechanism will put them in the correct priority QUE.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Que 0 DSCP 0-7&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Que 1 DSCP 8-15&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Que 2 DSCP 16-23&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Que 3 DSCP 24-31&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Que 4 DSCP 32-39&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Que 5 DSCP 40-47&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Que 6 DSCP 48-55&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Que 7 DSCP 56-63&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;If you use and ACL just grab the IP address or subnet and apply that to the QUE that you want it in. There is no need to remark traffic if your phone system is already doing it.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;DON'T USE QUE 6-7 as these (like on Cisco) are reserved for routing protocols and device to device pathways, I have seen people put stuff in QUE 7 but that is wrong and can break your ability to SSH into the device if you run out of bandwidth.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Remember if you are not using L3 it falls back on the L2 or COS value which there are 7 and they match the Que numbers above, so COS 0 = Que 0 and COS 1 = Que 1 etc.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Since you are using mixed-SP-WRR as the queing mechanism QUE's 6-7 are strict priority and anything in those QUE's will go out first regardless (that is why you never use them for anything and are reserved).&amp;nbsp; &lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;The others are as follows.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Unicast per Queue details:      Bandwidth%
&lt;PRE alt="" name="" rel="" target="" title="" type="" value=""&gt;Traffic Class 0                     15%
Traffic Class 1                     15%
Traffic Class 2                     15%
Traffic Class 3                     15%
Traffic Class 4                     15%
Traffic Class 5                     25%
Traffic Class 6                     sp
Traffic Class 7                     sp
Multicast per Queue details:    Bandwidth%
Traffic Class 0                     15%
Traffic Class 1                     15%
Traffic Class 2                     15%
Traffic Class 3                     15%
Traffic Class 4                     15%
Traffic Class 5                     25%
Traffic Class 6                     sp
Traffic Class 7                     sp  &lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;/PRE&gt;So if you have a 100mbps link the and vice has DSCP set at EF (dscp 46) it will get 25% or 25mbps &lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;of the 100mbps if it needs it and will get you out first after any SP traffic (same as Cisco) and does&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;not reserve that amount of traffic so other things can use it if it is not being used by voice.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
    <pubDate>Mon, 10 Aug 2020 16:05:07 GMT</pubDate>
    <dc:creator>tim_brumbaugh</dc:creator>
    <dc:date>2020-08-10T16:05:07Z</dc:date>
    <item>
      <title>QoS on ICX switch</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/QoS-on-ICX-switch/m-p/30176#M1594</link>
      <description>I am planning to replace Cisco router to ICX switch with L3 license.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Currently I am using QoS on Cisco as below. I want to implement same QoS on ICX.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I tried to create config for ICX. Will this work and do similar behavior?&lt;BR /&gt;Please advice how I can implement QoS like Cisco on ICX switch.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Cisco&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;---&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;class-map match-any VOICE&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;match access-group name Phones&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;match access-group name P_Controller&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;class-map match-any DATA&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;match access-group name Data&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;match access-group name Critical_System&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;class-map match-any INTERNET&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;match access-group name Internet&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;policy-map Company_QOS&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;class VOICE&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp; set dscp ef&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp; priority percent 20&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;class DATA&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp; bandwidth percent 30&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp; set dscp af21&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;class INTERNET&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp; bandwidth percent 10&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp; set dscp af11&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;ip access-list extended Phones&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;permit ip any 192.168.101.0 0.0.0.255&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;permit ip 192.168.101.0 0.0.0.255 any&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;ip access-list extended P_Controller&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;&lt;B&gt;deny&amp;nbsp; &amp;nbsp;ip any any fragments&lt;/B&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;permit udp any any range 5000 5100&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;permit tcp any any range 5000 5100&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;ip access-list extended Data&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;permit ip any 192.168.100.0 0.0.0.255&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;permit ip 192.168.100.0 0.0.0.255 any&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;ip access-list extended Critical_System&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;permit ip any 192.168.200.0 0.0.0.255&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;permit ip 192.168.200.0 0.0.0.255 any&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;ip access-list extended&amp;nbsp;Internet&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;&lt;B&gt;deny&amp;nbsp; &amp;nbsp;ip any 192.168.0.0 0.0.255.255&lt;/B&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;permit ip any any&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;interface GigabitEthernet0/0/0&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;description UPLINK&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;ip address 10.0.0.1 255.255.255.254&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;service-policy output Company_QOS&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;---&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;ICX 7450&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;---&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;ip access-list extended Company_QOS&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;remark !!!!_ip access-list extended Phones&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;sequence 10 permit ip any 192.168.101.0 0.0.0.255 dscp-marking 46&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;sequence 20 permit ip 192.168.101.0 0.0.0.255 any dscp-marking 46&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;remark !!!!_ip access-list extended P_Controller&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;sequence 30 permit udp any any range 5000 5100 dscp-marking 46&amp;nbsp; &amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;sequence 40 permit tcp any any range 5000 5100 dscp-marking 46&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;remark !!!!_ip access-list extended Data&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;sequence 50 permit ip any 192.168.100.0 0.0.0.255 dscp-marking 18&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;sequence 60 permit ip 192.168.100.0 0.0.0.255 any dscp-marking 18&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;remark !!!!_ip access-list extended Critical_System&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;sequence 70 permit ip any 192.168.200.0 0.0.0.255 dscp-marking 18&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;sequence 80 permit ip 192.168.200.0 0.0.0.255 any dscp-marking 18&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;remark !!!!_ip access-list extended&amp;nbsp;Internet&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;sequence 90 permit ip ant any dscp-marking 10&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;qos scheduler-profile AAA mechanism mixed-sp-wrr&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;qos scheduler-profile AAA profile qosp0 10 qosp1 10 qosp2 30 qosp3 30 qosp4 20 qosp5 20 qosp6 sp qosp7 sp&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;interface ethernet 1/2/1&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;port-name UPLINK&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;ip address 10.0.0.1 255.255.255.254&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;route-only&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;ip access-group Company_QOS out&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;scheduler-profile AAA&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Sun, 09 Aug 2020 13:42:55 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/QoS-on-ICX-switch/m-p/30176#M1594</guid>
      <dc:creator>ys</dc:creator>
      <dc:date>2020-08-09T13:42:55Z</dc:date>
    </item>
    <item>
      <title>Re: QoS on ICX switch</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/QoS-on-ICX-switch/m-p/30177#M1595</link>
      <description>Couple of things.&amp;nbsp; Make sure you rate limit the interface to match what your bandwidth is from your provider assuming this is going into a WAN or Metro-E circuit of some type.&amp;nbsp; The QOS mechanism works on bandwidth same as Cisco so if it thinks it has 1gbps then it won't shape the traffic until it starts getting full. &amp;nbsp; &lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Each interface needs to have the (trust dscp) just like Cisco.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;It is not necessary to grab the traffic in an ACL if the devices (phones) are marking the traffic with DSCP EF (46) or any DSCP marked traffic as the QOS mechanism will put them in the correct priority QUE.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Que 0 DSCP 0-7&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Que 1 DSCP 8-15&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Que 2 DSCP 16-23&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Que 3 DSCP 24-31&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Que 4 DSCP 32-39&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Que 5 DSCP 40-47&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Que 6 DSCP 48-55&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Que 7 DSCP 56-63&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;If you use and ACL just grab the IP address or subnet and apply that to the QUE that you want it in. There is no need to remark traffic if your phone system is already doing it.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;DON'T USE QUE 6-7 as these (like on Cisco) are reserved for routing protocols and device to device pathways, I have seen people put stuff in QUE 7 but that is wrong and can break your ability to SSH into the device if you run out of bandwidth.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Remember if you are not using L3 it falls back on the L2 or COS value which there are 7 and they match the Que numbers above, so COS 0 = Que 0 and COS 1 = Que 1 etc.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Since you are using mixed-SP-WRR as the queing mechanism QUE's 6-7 are strict priority and anything in those QUE's will go out first regardless (that is why you never use them for anything and are reserved).&amp;nbsp; &lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;The others are as follows.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Unicast per Queue details:      Bandwidth%
&lt;PRE alt="" name="" rel="" target="" title="" type="" value=""&gt;Traffic Class 0                     15%
Traffic Class 1                     15%
Traffic Class 2                     15%
Traffic Class 3                     15%
Traffic Class 4                     15%
Traffic Class 5                     25%
Traffic Class 6                     sp
Traffic Class 7                     sp
Multicast per Queue details:    Bandwidth%
Traffic Class 0                     15%
Traffic Class 1                     15%
Traffic Class 2                     15%
Traffic Class 3                     15%
Traffic Class 4                     15%
Traffic Class 5                     25%
Traffic Class 6                     sp
Traffic Class 7                     sp  &lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;/PRE&gt;So if you have a 100mbps link the and vice has DSCP set at EF (dscp 46) it will get 25% or 25mbps &lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;of the 100mbps if it needs it and will get you out first after any SP traffic (same as Cisco) and does&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;not reserve that amount of traffic so other things can use it if it is not being used by voice.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Mon, 10 Aug 2020 16:05:07 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/QoS-on-ICX-switch/m-p/30177#M1595</guid>
      <dc:creator>tim_brumbaugh</dc:creator>
      <dc:date>2020-08-10T16:05:07Z</dc:date>
    </item>
    <item>
      <title>Re: QoS on ICX switch</title>
      <link>https://community.ruckuswireless.com/t5/ICX-Switches/QoS-on-ICX-switch/m-p/30178#M1596</link>
      <description>Hello,&amp;nbsp;Tim,&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Thank you for your advice. This helps me for more understanding.</description>
      <pubDate>Wed, 12 Aug 2020 00:40:21 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ICX-Switches/QoS-on-ICX-switch/m-p/30178#M1596</guid>
      <dc:creator>ys</dc:creator>
      <dc:date>2020-08-12T00:40:21Z</dc:date>
    </item>
  </channel>
</rss>

