Junos OS

 View Only

IMPORTANT MODERATION NOTICE

This community is currently under full moderation, meaning  all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you'll receive an email outlining the reason(s). We've implemented full moderation to control spam. Thank you for your patience and participation.



SRX CoS settings for ethernet-switching interface

  • 1.  SRX CoS settings for ethernet-switching interface

    Posted 10 days ago
    Hi!
    I need to lower the priority of the smb protocol between the client's network and the server's network. I made some settings, but it seems that something is wrong.
    There is the scheme:

    There are my settings R-M29-01.
    Version:
    itbn@R-M29-01> show version 
    Hostname: R-M29-01
    Model: srx240h2
    JUNOS Software Release [12.1X44-D35.5]​

    Interfaces:

    itbn@R-M29-01# show interfaces ge-0/0/7  
    description LAN;
    unit 0 {
        family ethernet-switching {
            port-mode trunk;
            vlan {
                members [ default vlan12 vlan13 vlan14 voice Video Vlan446 vlan15 vlan200 vlan19 vlan111 vlan201 ];
            }
            native-vlan-id default;
        }
    }
    
    itbn@R-M29-01# show interfaces vlan
    ...
    ...
    unit 111 {
        description "PC network; vlan111; teg 111";
        family inet {
            filter {
                input lan-filter;
            }
            address 192.168.111.1/24;
        }
    }
    ...
    ...
    
    itbn@R-M29-01# show interfaces ge-0/0/11   
    description "L2 VPN";
    unit 0 {
        family inet {
            address 10.254.254.1/28;
        }
    }
    

    Multifield classifiers for client's network:

    itbn@R-M29-01# show firewall family inet filter lan-filter 
    term cos-default-classifier {
        then {
            count cos-default-counter;
            loss-priority low;
            forwarding-class assured-forwarding;
            next term;
        }
    }
    term cos-network-control {
        from {
            precedence net-control;
        }
        then {
            count cos-network-control-counter;
            forwarding-class network-control;
            next term;
        }
    }
    term cos-destination-smb {
        from {
            destination-port 445;
        }
        then {
            count cos-destination-smb-counter;
            forwarding-class best-effort;
            next term;
        }
    }
    term cos-source-smb {
        from {
            source-port 445;
        }
        then {
            count cos-source-smb-counter;
            forwarding-class best-effort;
            next term;
        }
    }
    ...
    ...
    ...​
    CoS settings:
    itbn@R-M29-01# show class-of-service 
    interfaces {
        ge-0/0/7 {
            scheduler-map scheduler-map-v1;
        }
        ge-0/0/11 {
            scheduler-map scheduler-map-v1;
            unit 0 {
                classifiers {
                    inet-precedence default;
                }
                rewrite-rules {
                    inet-precedence default;
                }
            }
        }
    }
    scheduler-maps {
        scheduler-map-v1 {
            forwarding-class network-control scheduler nc-scheduler;
            forwarding-class assured-forwarding scheduler af-scheduler;
            forwarding-class best-effort scheduler be-scheduler;
        }
    }
    schedulers {
        nc-scheduler {
            transmit-rate percent 5;
            buffer-size percent 5;
            priority strict-high;
        }
        af-scheduler {
            transmit-rate percent 30;
            buffer-size percent 30;
            priority medium-high;
        }
        be-scheduler {
            transmit-rate {
                remainder;
            }
            buffer-size {
                remainder;
            }
            priority low;
        }
    }
    ​


    The second router (R-EST-01) have the same configuration.

    And this is what I see on the interfaces:
    itbn@R-M29-01> show interfaces ge-0/0/11 detail | find "Egress queues"
      Egress queues: 8 supported, 4 in use
      Queue counters:       Queued packets  Transmitted packets      Dropped packets
        0 best-effort           3920879911           3920879911                    0
        1 expedited-fo                   4                    4                    0
        2 assured-forw          3648204050           3648204050                    0
        3 network-cont           104323648            104323648                    0
      Queue number:         Mapped forwarding classes
        0                   best-effort 
        1                   expedited-forwarding
        2                   assured-forwarding
        3                   network-control
    
    itbn@R-M29-01> show interfaces ge-0/0/7 detail | find "Egress queues"    
      Egress queues: 8 supported, 4 in use
      Queue counters:       Queued packets  Transmitted packets      Dropped packets
        0 best-effort                    0                    0                    0
        1 expedited-fo                   0                    0                    0
        2 assured-forw                   0                    0                    0
        3 network-cont            24814481             24814481                    0
      Queue number:         Mapped forwarding classes
        0                   best-effort 
        1                   expedited-forwarding
        2                   assured-forwarding
        3                   network-control
    ​

    So i'm not sure about this:
    itbn@R-M29-01# show class-of-service 
    interfaces {
        ge-0/0/7 {
            scheduler-map scheduler-map-v1;
        }​


    Can I assign a scheduler to the ethernet-switching interface? Is it right? If so, how to check that the cos is working on this interface?
    Thank you!