Hello,
schedulers and schedulers-map is to schdule traffic egress. The scheduler decides how much bandwidth a forwarding class gets. Ingress forwarding class is decided and also a drop priority ion case the traffic needs to be dropped. In the scheduler within a forwarding class different drop-priorities can be treated different through applying different drop profiles. When it comes to voice, it should have it's own forwarding class of a high priority. It should not be using different drop priorities and different drop profiles. It should have one that says: drop everything if you need to queue. Because voice traffic dont like to be queued and sent later. It will mess the sound up. In return voice traffic should have the highest priority and whatever bandwidth it need to push any other traffic away. Cheers Patrik > Forwarding class and loss priority is some of the confusing stuff in JUNOS > world. Can someone write about loss priority/scheduler maps in detail along > with a example. Like what if you are running MPLS VPN and you want to keep > priorities voice traffic (if you want to avoid jitter for the sip call) > weather the congestion is happening or not. How do you do it practically. > > > > voice-profile > > fill-level 0 drop-probability 0; > > fill-level 25 drop-probability 100; > > > > Is this good to have on Gig interface for Voice traffic. > > > > transmit-rate percent 20 exact; > > buffer-size percent 20; > > priority high; > > drop-profile-map loss-priority any protocol any drop-profile voice-profile; > > > > I will highly appreciate if someone can dig into this along with > configuration/comments. > > > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp -- //Patrik Webkom http://www.webkom.se +46 (0)709 35 22 99 +46 (0)8 559 26 488 _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
