vMX

Expand all | Collapse all

Applying QoS rewrite rules defaults scheduler map

Jump to Best Answer
  • 1.  Applying QoS rewrite rules defaults scheduler map

    Posted 05-30-2018 02:39
      |   view attached

    There is a "jncie-cos" scheduler map applied to all interfaces (ge-*). After applying rewrite rules to some interface, scheduler map on this interface shown as "<default>". After deleting the rewrite rules scheduler map changes back to "jncie-cos". Please advise if it is a bug or a feature.

     

    Console output and config are in the attachment. The config is from QoS lab of JNCIE-SP-12.a bootcamp. vMX version is 17.4R1.16

     

     


    #JNCIE-SP
    #vmx
    #QOS

    Attachment(s)

    txt
    QoS lab.txt   2K 1 version


  • 2.  RE: Applying QoS rewrite rules defaults scheduler map

    Posted 05-30-2018 02:49

    I have seen similar behaviour on SRX and other junos platforms

    My conclusion was: the wildcards in COS like  ge-* only works when you do not set any other special QOS item on that interface. else specify the scheduler map on that interface again or only use interface specs and no wildcards in COS

     

    regards

     

    alexander

     



  • 3.  RE: Applying QoS rewrite rules defaults scheduler map
    Best Answer

    Posted 05-30-2018 05:05

    Hello,

    This is how JUNOS regex works. It picks the most specific regex to apply, not all matching regex.

    Instead of

    interfaces {
        ge-* {
            scheduler-map jncie-cos;
        }
        ge-0/0/2 {
            unit 0 {
                rewrite-rules {
                    dscp jncie-rw;
                }
            }
        }
    }

    please use

    interfaces {
        ge-* {
            scheduler-map jncie-cos;
        }
        ge-0/0/2 {
    	scheduler-map jncie-cos;
            unit 0 {
                rewrite-rules {
                    dscp jncie-rw;
                }
            }
        }
    }

    - and You should be golden.

    HTH

    Thx

    Alex