[j-nsp] CoS Configuration Assistance

Harry Reynolds harry at juniper.net
Fri Jan 20 16:36:06 EST 2006


Can you elaborate on which classes have the quality issue?  I assume you
are not worried about quality in the voice-BE class, for example.  Have
you confirmed that the schedulers and that all that are correctly
applied with various show class-of-service commands? Given the info its
hard to tell if other routers are involved, or if the VOIP sources are
directly attached. Your rewrite makes me think there is BA
classification down-stream. Have you confirmed that those router have
the correct ingress classification and egress scheduling?

Also, any chance there is packet loss between the nodes that accounts
for the corruption?  May want to do some rapid pings to confirm the
forwarding path.

Regards




> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of IPGN J-NSP
> Sent: Friday, January 20, 2006 1:11 PM
> To: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] CoS Configuration Assistance
> 
> I am running into garbled voice that would seem to be caused 
> by delayed or out of sequence packets.
> 
> I apologize for not including the full configuration but the 
> schedulers are defined.
> 
> forwarding-classes {
>     queue 0 best-effort;
>     queue 1 expedited-forwarding;
>     queue 2 assured-forwarding;
>     queue 3 network-control;
> }
> 
> schedulers {
>     voice-t1-ef {
>         transmit-rate percent 30;
>         priority strict-high;
>     }
>     voice-t1-be {
>         transmit-rate percent 55;
>         priority low;
>     }
>     voice-ef {
>         transmit-rate percent 30;
>         priority strict-high;
>     }
>     voice-af {
>         transmit-rate percent 5;
>         priority low;
>     }
>     voice-nc {
>         transmit-rate percent 5;
>         priority high;
>     }
>     voice-be {
>         transmit-rate percent 60;
>         priority low;
>     }
>     voice-t1-af {
>         transmit-rate percent 10;
>         priority low;
>     }
>     voice-t1-nc {
>         transmit-rate percent 5;
>         priority high;
>     }
> }
> 
> Thanks
> 
> 
> >
> > -----Original Message-----
> > From: Harry Reynolds [mailto:harry at juniper.net]
> > Sent: Friday, January 20, 2006 3:05 PM
> > To: IPGN J-NSP; juniper-nsp at puck.nether.net
> > Subject: RE: [j-nsp] CoS Configuration Assistance
> >
> > Hello,
> >
> > I do not see the definition of any schedulers in your 
> config. If not 
> > defined the default bandwidth is 95/5 for queue 0 and 3 
> respectively.
> >
> > Here I a sample scheduler definition stanza:
> >
> > [edit class-of-service]
> > lab at San_Jose# show schedulers
> > be-scheduler {
> >    transmit-rate 1m exact;
> >    priority low;
> >    drop-profile-map loss-priority low protocol tcp drop-profile 
> > low-red;
> >    drop-profile-map loss-priority high protocol tcp drop-profile 
> > high-red; } ef-scheduler {
> >    transmit-rate 20m;
> >    buffer-size temporal 200000;
> >    priority high;
> > }
> > nc-scheduler {
> >    transmit-rate percent 5;
> >    priority low;
> > }
> >
> > HTHs
> >
> >
> >> -----Original Message-----
> >> From: juniper-nsp-bounces at puck.nether.net
> >> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of 
> IPGN J-NSP
> >> Sent: Friday, January 20, 2006 12:57 PM
> >> To: juniper-nsp at puck.nether.net
> >> Subject: [j-nsp] CoS Configuration Assistance
> >>
> >> I am attempting to prioritize voip traffic to/from T1 
> customers for 
> >> our specific application.  I would like to know if anyone sees any 
> >> problems with the configuration below because I am running 
> into a few 
> >> quality issues.
> >> Thank you in advance for any advice you can provide.
> >>
> >> Basically, I have firewall filters (mf classifier) that 
> match input 
> >> traffic patterns from T1 customers as well as input from the 
> >> FastEthernet port that connects the softswitch.
> >> These filters place the traffic into the appropriate queue 
> which is 
> >> basically expedited-forwarding for voip and best-effort for 
> >> everything else.  Then I have a rewrite-marker on the 
> interfaces that 
> >> set specific dscp values per each queue and dscp classifiers that 
> >> assign the appropriately tagged dscp packets to their respective 
> >> queue.
> >>
> >>
> >>
> >> > show configuration class-of-service
> >> classifiers {
> >>     dscp ipgn-dscp {
> >>         forwarding-class expedited-forwarding {
> >>             loss-priority low code-points ef;
> >>             loss-priority high code-points cs4;
> >>         }
> >>         forwarding-class best-effort {
> >>             loss-priority high code-points be;
> >>             loss-priority low code-points cs1;
> >>         }
> >>         forwarding-class assured-forwarding {
> >>             loss-priority high code-points af11;
> >>             loss-priority low code-points af12;
> >>         }
> >>         forwarding-class network-control {
> >>             loss-priority high code-points nc1;
> >>             loss-priority low code-points nc2;
> >>         }
> >>     }
> >> }
> >>
> >> rewrite-rules {
> >>     dscp ipgn-rewrite {
> >>         forwarding-class expedited-forwarding {
> >>             loss-priority low code-point ef;
> >>             loss-priority high code-point cs4;
> >>         }
> >>         forwarding-class best-effort {
> >>             loss-priority high code-point be;
> >>             loss-priority low code-point cs1;
> >>         }
> >>         forwarding-class network-control {
> >>             loss-priority high code-point nc1;
> >>             loss-priority low code-point nc2;
> >>         }
> >>         forwarding-class assured-forwarding {
> >>             loss-priority low code-point af12;
> >>             loss-priority high code-point af11;
> >>         }
> >>     }
> >> }
> >>
> >> scheduler-maps {
> >>     map-ethernet {
> >>         forwarding-class best-effort scheduler best-effort;
> >>         forwarding-class expedited-forwarding scheduler 
> >> expedited-forwarding;
> >>         forwarding-class network-control scheduler network-control;
> >>     }
> >>     voice-t1-map {
> >>         forwarding-class best-effort scheduler voice-t1-be;
> >>         forwarding-class expedited-forwarding scheduler 
> voice-t1-ef;
> >>         forwarding-class network-control scheduler voice-t1-nc;
> >>         forwarding-class assured-forwarding scheduler voice-t1-af;
> >>     }
> >> }
> >> interfaces {
> >>     t1-0/0/* {
> >>         scheduler-map voice-t1-map;
> >>         unit 0 {
> >>             classifiers {
> >>                 dscp ipgn-dscp;
> >>             }
> >>             rewrite-rules {
> >>                 dscp ipgn-rewrite;
> >>             }
> >>         }
> >>     }
> >>     fe-1/3/0 {
> >>         scheduler-map ethernet-map;
> >>         unit 202 {
> >>             classifiers {
> >>                 dscp ipgn-dscp;
> >>             }
> >>             rewrite-rules {
> >>                 dscp ipgn-rewrite;
> >>             }
> >>         }
> >>     }
> >> }
> >>
> >>
> >> > show configuration interfaces t1-0/0/0:15
> >> encapsulation ppp;
> >> unit 0 {
> >>     family inet {
> >>         filter {
> >>             input ipgn-cust-t1-input;
> >>         }
> >>         address 1.1.1.1/30;
> >>     }
> >> }
> >>
> >> > show configuration interfaces fe-1/3/0.202
> >> vlan-id 202;
> >> family inet {
> >>     filter {
> >>         input vipgn-mfc-in;
> >>     }
> >>     address 2.2.2.2/27;
> >> }
> >>
> >>
> >> /J
> >>
> >> _______________________________________________
> >> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> >> http://puck.nether.net/mailman/listinfo/juniper-nsp
> >>
> > 
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> http://puck.nether.net/mailman/listinfo/juniper-nsp
> 



More information about the juniper-nsp mailing list