Switching

last person joined: 2 days ago 

Ask questions and share experiences about EX and QFX portfolios and all switching solutions across your data center, campus, and branch locations.
  • 1.  qfx5100 VC multicast traffic BW allocation

    Posted 08-04-2016 04:28

    Hi community,

     

    we have a VC built-up by x4 Juniper 5100. Mos of the traffic crossing this platform is video mcast traffic and we suspect of mcast traffic lost. Client servers are connected via 10G ports but we also have a probe system connected on a 1Gb port. For this interface we are suffering some lost of traffic on the end system, and while checking the interface counters i saw that around a 0,6% of the mcast is being dropped:

    Queue counters: Queued packets Transmitted packets Dropped packets

     8                             0                             3071553518              19857689

     

    Queue number: Mapped forwarding classes

     0 best-effort
    3 fcoe
    4 no-loss
    7 network-control
    8 mcast

     

    coS information:
    Direction : Output
    CoS transmit queue Bandwidth Buffer Priority Limit

    8 mcast 20% 2000000000 20% 0 low none

     

    As mcast traffic seems to use up to a 40% of the total BW, i wonder if this can be changed or not as this interface is mostly dideciated for cast traffic. i tried to assigned a different FC but not been succesful. )

     

    any help on this is appreciated.

     

    Thanks

    Gab



  • 2.  RE: qfx5100 VC multicast traffic BW allocation

    Posted 08-05-2016 05:00

    Hi 

     

    i've tried creating a new scheduler with new transmit and shaping rate percent values as well as priorty so mcast is kind of priorized on the egress interface. i fiind no way to  macth this scheduler to the FC mcast and apply  it on the intended interface. Any help wth this config is apprecaited.

     

    Thanks

    Gabi



  • 3.  RE: qfx5100 VC multicast traffic BW allocation
    Best Answer

     
    Posted 08-06-2016 03:22

    Hi,

     

    Could you possibly try creating a scheduler-map and then apply the scheduler-map to the interface:

    set class-of-service scheduler-maps xxxxx forwarding-class mcast scheduler yyyyy
    set class-of-service interfaces xxx scheduler-map xxxxx

    Cheers,

    Ashvin



  • 4.  RE: qfx5100 VC multicast traffic BW allocation

    Posted 08-08-2016 00:02

    Hi Ashvin,

     

    THis is the config i just applied:

     

    + class-of-service {
    + interfaces {
    + xe-2/0/5 {
    + scheduler-map test-mcst-eth-cos-map;
    + }
    + }
    + scheduler-maps {
    + test-mcst-eth-cos-map {
    + forwarding-class mcast scheduler test_video_mcast_scheduler;
    + }
    + }
    + schedulers {
    + test_video_mcast_scheduler {
    + transmit-rate percent 50;
    + shaping-rate percent 80;
    + buffer-size percent 20;
    + priority strict-high;
    + }
    + }
    + }

     

    but when i commit and i print the interface counters, i dont see that  the queue's BW percentage are changed:

     

    show interfaces xe-2/0/5 extensive:

     

    CoS information:
    Direction : Output
    CoS transmit queue Bandwidth Buffer Priority Limit
    % bps % usec
    0 best-effort 5 500000000 5 0 low none
    3 fcoe 35 3500000000 35 0 low none
    4 no-loss 35 3500000000 35 0 low none
    7 network-control 5 500000000 5 0 low none
    8 mcast 20 2000000000 20 0 low none

     

    Maybe i missed any ther step on the CoS configuration¿?

     

    Thanks

    Gab



  • 5.  RE: qfx5100 VC multicast traffic BW allocation

    Posted 08-08-2016 00:56

    It seems the secheduler-map is still the default one

     

    show class-of-service interface xe-2/0/5


    Physical interface: xe-2/0/5, Index: 692
    Queues supported: 12, Queues in use: 5
    Scheduler map: <default>, Index: 2
    Congestion-notification: Disabled

    Logical interface: xe-2/0/5.0, Index: 607
    Object Name Type Index
    Classifier ieee8021p-untrust untrust 16



  • 6.  RE: qfx5100 VC multicast traffic BW allocation

     
    Posted 08-08-2016 01:44

    Hi, 

     

    It appears the config is sighlty different on QFX and you may need to add forwarding-class-set and traffic-control-profile.

    http://www.juniper.net/documentation/en_US/junos12.3/topics/example/queue-schedulers-cos-configuring.html

     

    Cheers,

    Ashvin



  • 7.  RE: qfx5100 VC multicast traffic BW allocation

    Posted 08-08-2016 02:57

    Thanks Ashvin

     

    it seems the config was commited succesfuly although priority strict-high was not permitted, i had to change it to low.

    on the show interface xe-2/0/5 extensive printout now i dont see the percentages shown or cos information for the trasmit queue , bit strange

     

     

     

    traffic-control-profiles {
    mcast-video {
    scheduler-map test-mcst-eth-cos-map;
    }
    }
    forwarding-class-sets {
    fc-mcast-video {
    class mcast;
    }
    }
    interfaces {
    xe-2/0/5 {
    forwarding-class-set {
    fc-mcast-video {
    output-traffic-control-profile mcast-video;
    }
    }
    }
    }
    scheduler-maps {
    test-mcst-eth-cos-map {
    forwarding-class mcast scheduler test_video_mcast_scheduler;
    }
    }
    schedulers {
    test_video_mcast_scheduler {
    transmit-rate percent 50;
    shaping-rate percent 80;
    buffer-size percent 20;
    priority low;
    }
    }



  • 8.  RE: qfx5100 VC multicast traffic BW allocation

     
    Posted 08-08-2016 04:36

    Hi, 

    You could check for:

    show class-of-service interface xe-2/0/5 comprehensive
    show interfaces queue xe-2/0/5

    Could you share the ouputs including "show interfaces extensive".

    Also note since there are now custom config for the schedulers, you will probably see only the configured forwarding-class in the custom scheduler-map applied on that interface which may not be ideal.

     

    Cheers,

    Ashvin



  • 9.  RE: qfx5100 VC multicast traffic BW allocation

    Posted 08-09-2016 00:14

    Thansk Ashvin.

     

    firts cmd seems to not be supported:

     

    show class-of-service interface xe-2/0/5 comprehensive
    error: command is not valid on the qfx5100-96s-8q.

     

    the other one shows the traffic being handled by queue 8, the drops are just the ones happened when i applied the configuration. Right now we have decrease the throughput so i can not check if the scheduler will work fine when going aobve 4xx mbps. I'll try to test it later and let you know.

     

    Thanks!

    Gab

     

    show interfaces queue xe-2/0/5
    Physical interface: xe-2/0/5, Enabled, Physical link is Up
    Interface index: 692, SNMP ifIndex: 610
    Forwarding classes: 16 supported, 5 in use
    Egress queues: 12 supported, 5 in use
    Queue: 0, Forwarding classes: best-effort
    Queued:
    Packets : 0 0 pps
    Bytes : 0 0 bps
    Transmitted:
    Packets : 0 0 pps
    Bytes : 0 0 bps
    Tail-dropped packets : Not Available
    RL-dropped packets : 0 0 pps
    RL-dropped bytes : 0 0 bps
    Total-dropped packets: 0 0 pps
    Total-dropped bytes : 0 0 bps
    Queue: 3, Forwarding classes: fcoe
    Queued:
    Packets : 0 0 pps
    Bytes : 0 0 bps
    Transmitted:
    Packets : 0 0 pps
    Bytes : 0 0 bps
    Tail-dropped packets : Not Available
    RL-dropped packets : 0 0 pps
    RL-dropped bytes : 0 0 bps
    Total-dropped packets: 0 0 pps
    Total-dropped bytes : 0 0 bps
    Queue: 4, Forwarding classes: no-loss
    Queued:
    Packets : 0 0 pps
    Bytes : 0 0 bps
    Transmitted:
    Packets : 0 0 pps
    Bytes : 0 0 bps
    Tail-dropped packets : Not Available
    RL-dropped packets : 0 0 pps
    RL-dropped bytes : 0 0 bps
    Total-dropped packets: 0 0 pps
    Total-dropped bytes : 0 0 bps
    Queue: 7, Forwarding classes: network-control
    Queued:
    Packets : 0 0 pps
    Bytes : 0 0 bps
    Transmitted:
    Packets : 14767 0 pps
    Bytes : 5227518 0 bps
    Tail-dropped packets : Not Available
    RL-dropped packets : 0 0 pps
    RL-dropped bytes : 0 0 bps
    Total-dropped packets: 0 0 pps
    Total-dropped bytes : 0 0 bps
    Queue: 8, Forwarding classes: mcast
    Queued:
    Packets : 0 0 pps
    Bytes : 0 0 bps
    Transmitted:
    Packets : 4736744788 13600 pps
    Bytes : 6451444798496 148189928 bps
    Tail-dropped packets : Not Available
    RL-dropped packets : 0 0 pps
    RL-dropped bytes : 0 0 bps
    Total-dropped packets: 23 0 pps
    Total-dropped bytes : 31326 0 bps