List Info

Thread: Re: QOS for MPLS




Re: QOS for MPLS
country flaguser name
United States
2007-05-27 15:59:17
I've seen one or two setups where the MPLS was fully meshed
(all sites could talk to any other site), which makes QoS
even trickier. 

----- Original Message ----
From: "kelicarocomp.ro" <kelicarocomp.ro>
To: Jonathan Charles <jonvoipgmail.com>
Cc: cisco-voippuck.nether.net
Sent: Sunday, May 27, 2007 3:50:17 PM
Subject: Re: [cisco-voip] QOS for MPLS

That is correct (although you should take some overhead into
account  
as well). However, if you do not perform Call Admission
Control  
beforehand (you do not limit the maximum number of possible 

simultaneous calls) you've done nothing, or worse.

The classic example being when you have a line that supports
4 calls,  
when the fifth call enters the line, all calls will suffer
packet loss  
and delay, not only the fifth one.

I'm not too versed in MPLS QoS, but the idea is always the
same.  
Prioritize voice traffic, but don't let it kill your
bandwidth, nor  
itself. Thus the need for CAC, then something like CBWFQ/PQ.
If  
possible, voice traffic should be beneath shaping/policing
limits, so  
that neither would affect it.

regards,
   Zoltan

Quoting Jonathan Charles <jonvoipgmail.com>:

> My thinking is that I need to set the QOS to be the
same as the
> maximum number of calls to/from each site.
>
>
> Jonathan
>
> On 5/27/07, kelicarocomp.ro <kelicarocomp.ro> wrote:
>> As long as it is about "calls", CAC is
the sensitive way to go about
>> limiting the calls in the first place. Do QoS
"As close to the source,
>> as possible", remember? 
>>
>> If you do not have a CCM, but other set-up, you
should still look in
>> this direction first - to limit the calls to a
reasonable amount in
>> the given directions, before they are hitting your
MPLS router.
>>
>> regards,
>>   Zoltan
>>
>> Quoting Paul Choi <asobihoudaiyahoo.com>:
>>
>>> He's talking about QoS for MPLS, not CAC.
>>>
>>> --- "Clouse, Chris"
<chris.clouseberbee.com> wrote:
>>>
>>>> Use CallManager locations to perform Call
Admission
>>>> Control.
>>>>
>>>> Christopher Clouse, CCNP CCDP CCVP MCP
Network+
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: cisco-voip-bouncespuck.nether.net
>>>> [mailto:cisco-voip-bouncespuck.nether.net] On
>>>> Behalf Of Jonathan
>>>> Charles
>>>> Sent: Saturday, May 26, 2007 11:35 AM
>>>> To: ciscovoip
>>>> Subject: [cisco-voip] QOS for MPLS
>>>>
>>>> I have always understood that QOS settings
need to
>>>> match on both ends
>>>> of a circuit... so, if you allocate 800k on
one
>>>> side, you need to do
>>>> the same on the other.
>>>>
>>>> I am now working on an MPLS circuit that
has DS3s on
>>>> some sides, DS1s
>>>> on others... do I still need to match QOS
settings?
>>>>
>>>> Customer wants 800k on the T1s and 2500k on
the
>>>> DS3s... I don't think
>>>> it will matter as I am matching these bw
limits on
>>>> the locations...
>>>> but how do I throttle calls from a DS3-side
location
>>>> to a DS1
>>>> location?
>>>>
>>>> For example... main site is in Chicago,
they have a
>>>> DS3, one remote
>>>> site is in Wichita and has a T1... so, I
put 800k
>>>> for Wichita and
>>>> 2500k for Chicago... what is to stop
Chicago from
>>>> flooding Wichita
>>>> with 2.5MB of calls?
>>>>
>>>>
>>>>
>>>> Jonathan
>>>
>>>
>>>
>>>
>>>
>>>
>>
____________________________________________________________
________________________Building a website is a piece of
cake. Yahoo! Small Business gives you all the tools to   
>> get
>>> online.
>>> http://smal
lbusiness.yahoo.com/webhosting
>>>
_______________________________________________
>>> cisco-voip mailing list
>>> cisco-voippuck.nether.net
>>> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>
>>
>>
>>
------------------------------------------------------------
----
>> This message was sent using IMP, the Internet
Messaging Program.
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voippuck.nether.net
>> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
>>



------------------------------------------------------------
----
This message was sent using IMP, the Internet Messaging
Program.

_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip





 
____________________________________________________________
________________________
We won't tell. Get more on shows you hate to love 
(and love to hate): Yahoo! TV's Guilty Pleasures list.
http://tv.yahoo.c
om/collections/265 
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip

Re: QOS for MPLS
user name
2007-05-27 16:54:27
Which is the definition of MPLS, any-to-any communication.
All
circuits are point to point into the MPLS cloud and then
routing in
the cloud to each site.



Jonathan

On 5/27/07, Erick Bergquist <erickbeyahoo.com> wrote:
> I've seen one or two setups where the MPLS was fully
meshed (all sites could talk to any other site), which makes
QoS even trickier.
>
> ----- Original Message ----
> From: "kelicarocomp.ro" <kelicarocomp.ro>
> To: Jonathan Charles <jonvoipgmail.com>
> Cc: cisco-voippuck.nether.net
> Sent: Sunday, May 27, 2007 3:50:17 PM
> Subject: Re: [cisco-voip] QOS for MPLS
>
> That is correct (although you should take some overhead
into account
> as well). However, if you do not perform Call Admission
Control
> beforehand (you do not limit the maximum number of
possible
> simultaneous calls) you've done nothing, or worse.
>
> The classic example being when you have a line that
supports 4 calls,
> when the fifth call enters the line, all calls will
suffer packet loss
> and delay, not only the fifth one.
>
> I'm not too versed in MPLS QoS, but the idea is always
the same.
> Prioritize voice traffic, but don't let it kill your
bandwidth, nor
> itself. Thus the need for CAC, then something like
CBWFQ/PQ. If
> possible, voice traffic should be beneath
shaping/policing limits, so
> that neither would affect it.
>
> regards,
>    Zoltan
>
> Quoting Jonathan Charles <jonvoipgmail.com>:
>
> > My thinking is that I need to set the QOS to be
the same as the
> > maximum number of calls to/from each site.
> >
> >
> > Jonathan
> >
> > On 5/27/07, kelicarocomp.ro <kelicarocomp.ro> wrote:
> >> As long as it is about "calls", CAC
is the sensitive way to go about
> >> limiting the calls in the first place. Do QoS
"As close to the source,
> >> as possible", remember? 
> >>
> >> If you do not have a CCM, but other set-up,
you should still look in
> >> this direction first - to limit the calls to a
reasonable amount in
> >> the given directions, before they are hitting
your MPLS router.
> >>
> >> regards,
> >>   Zoltan
> >>
> >> Quoting Paul Choi <asobihoudaiyahoo.com>:
> >>
> >>> He's talking about QoS for MPLS, not CAC.
> >>>
> >>> --- "Clouse, Chris"
<chris.clouseberbee.com> wrote:
> >>>
> >>>> Use CallManager locations to perform
Call Admission
> >>>> Control.
> >>>>
> >>>> Christopher Clouse, CCNP CCDP CCVP MCP
Network+
> >>>>
> >>>>
> >>>> -----Original Message-----
> >>>> From: cisco-voip-bouncespuck.nether.net
> >>>> [mailto:cisco-voip-bouncespuck.nether.net] On
> >>>> Behalf Of Jonathan
> >>>> Charles
> >>>> Sent: Saturday, May 26, 2007 11:35 AM
> >>>> To: ciscovoip
> >>>> Subject: [cisco-voip] QOS for MPLS
> >>>>
> >>>> I have always understood that QOS
settings need to
> >>>> match on both ends
> >>>> of a circuit... so, if you allocate
800k on one
> >>>> side, you need to do
> >>>> the same on the other.
> >>>>
> >>>> I am now working on an MPLS circuit
that has DS3s on
> >>>> some sides, DS1s
> >>>> on others... do I still need to match
QOS settings?
> >>>>
> >>>> Customer wants 800k on the T1s and
2500k on the
> >>>> DS3s... I don't think
> >>>> it will matter as I am matching these
bw limits on
> >>>> the locations...
> >>>> but how do I throttle calls from a
DS3-side location
> >>>> to a DS1
> >>>> location?
> >>>>
> >>>> For example... main site is in
Chicago, they have a
> >>>> DS3, one remote
> >>>> site is in Wichita and has a T1... so,
I put 800k
> >>>> for Wichita and
> >>>> 2500k for Chicago... what is to stop
Chicago from
> >>>> flooding Wichita
> >>>> with 2.5MB of calls?
> >>>>
> >>>>
> >>>>
> >>>> Jonathan
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
____________________________________________________________
________________________Building a website is a piece of
cake. Yahoo! Small Business gives you all the tools to
> >> get
> >>> online.
> >>> http://smal
lbusiness.yahoo.com/webhosting
> >>>
_______________________________________________
> >>> cisco-voip mailing list
> >>> cisco-voippuck.nether.net
> >>> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
> >>>
> >>
> >>
> >>
> >>
------------------------------------------------------------
----
> >> This message was sent using IMP, the Internet
Messaging Program.
> >>
> >>
_______________________________________________
> >> cisco-voip mailing list
> >> cisco-voippuck.nether.net
> >> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
> >>
>
>
>
>
------------------------------------------------------------
----
> This message was sent using IMP, the Internet Messaging
Program.
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voippuck.nether.net
> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
>
>
>
____________________________________________________________
________________________
> We won't tell. Get more on shows you hate to love
> (and love to hate): Yahoo! TV's Guilty Pleasures list.
> http://tv.yahoo.c
om/collections/265
>
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip

Re: QOS for MPLS
country flaguser name
United States
2007-05-29 13:42:40
With MPLS and sites with different bandwidths, you should
set the QoS
based on the site bandwidth.  So it is ok to have 800k on
the T1's and
2500k on the DS3's.  Locations would prevent HQ from
flooding a
particular site.  

Because of the mesh possibilities of MPLS, I would set the
HQ Location
bandwidth to unlimited and the remote at ~800kb. 

If this is Unified CM 5.X you could use RSVP.  CM locations
are more
designed for a Hub and Spoke network.  RSVP accommodates a
meshed
topology.

-----Original Message-----
From: cisco-voip-bouncespuck.nether.net
[mailto:cisco-voip-bouncespuck.nether.net] On Behalf
Of Jonathan
Charles
Sent: Sunday, May 27, 2007 4:54 PM
To: Erick Bergquist
Cc: cisco-voippuck.nether.net
Subject: Re: [cisco-voip] QOS for MPLS

Which is the definition of MPLS, any-to-any communication.
All circuits
are point to point into the MPLS cloud and then routing in
the cloud to
each site.



Jonathan

On 5/27/07, Erick Bergquist <erickbeyahoo.com> wrote:
> I've seen one or two setups where the MPLS was fully
meshed (all sites
could talk to any other site), which makes QoS even
trickier.
>
> ----- Original Message ----
> From: "kelicarocomp.ro" <kelicarocomp.ro>
> To: Jonathan Charles <jonvoipgmail.com>
> Cc: cisco-voippuck.nether.net
> Sent: Sunday, May 27, 2007 3:50:17 PM
> Subject: Re: [cisco-voip] QOS for MPLS
>
> That is correct (although you should take some overhead
into account 
> as well). However, if you do not perform Call Admission
Control 
> beforehand (you do not limit the maximum number of
possible 
> simultaneous calls) you've done nothing, or worse.
>
> The classic example being when you have a line that
supports 4 calls, 
> when the fifth call enters the line, all calls will
suffer packet loss

> and delay, not only the fifth one.
>
> I'm not too versed in MPLS QoS, but the idea is always
the same.
> Prioritize voice traffic, but don't let it kill your
bandwidth, nor 
> itself. Thus the need for CAC, then something like
CBWFQ/PQ. If 
> possible, voice traffic should be beneath
shaping/policing limits, so 
> that neither would affect it.
>
> regards,
>    Zoltan
>
> Quoting Jonathan Charles <jonvoipgmail.com>:
>
> > My thinking is that I need to set the QOS to be
the same as the 
> > maximum number of calls to/from each site.
> >
> >
> > Jonathan
> >
> > On 5/27/07, kelicarocomp.ro <kelicarocomp.ro> wrote:
> >> As long as it is about "calls", CAC
is the sensitive way to go 
> >> about limiting the calls in the first place.
Do QoS "As close to 
> >> the source, as possible", remember? 
> >>
> >> If you do not have a CCM, but other set-up,
you should still look 
> >> in this direction first - to limit the calls
to a reasonable amount

> >> in the given directions, before they are
hitting your MPLS router.
> >>
> >> regards,
> >>   Zoltan
> >>
> >> Quoting Paul Choi <asobihoudaiyahoo.com>:
> >>
> >>> He's talking about QoS for MPLS, not CAC.
> >>>
> >>> --- "Clouse, Chris"
<chris.clouseberbee.com> wrote:
> >>>
> >>>> Use CallManager locations to perform
Call Admission Control.
> >>>>
> >>>> Christopher Clouse, CCNP CCDP CCVP MCP
Network+
> >>>>
> >>>>
> >>>> -----Original Message-----
> >>>> From: cisco-voip-bouncespuck.nether.net
> >>>> [mailto:cisco-voip-bouncespuck.nether.net] On Behalf Of Jonathan

> >>>> Charles
> >>>> Sent: Saturday, May 26, 2007 11:35 AM
> >>>> To: ciscovoip
> >>>> Subject: [cisco-voip] QOS for MPLS
> >>>>
> >>>> I have always understood that QOS
settings need to match on both 
> >>>> ends of a circuit... so, if you
allocate 800k on one side, you 
> >>>> need to do the same on the other.
> >>>>
> >>>> I am now working on an MPLS circuit
that has DS3s on some sides, 
> >>>> DS1s on others... do I still need to
match QOS settings?
> >>>>
> >>>> Customer wants 800k on the T1s and
2500k on the DS3s... I don't 
> >>>> think it will matter as I am matching
these bw limits on the 
> >>>> locations...
> >>>> but how do I throttle calls from a
DS3-side location to a DS1 
> >>>> location?
> >>>>
> >>>> For example... main site is in
Chicago, they have a DS3, one 
> >>>> remote site is in Wichita and has a
T1... so, I put 800k for 
> >>>> Wichita and 2500k for Chicago... what
is to stop Chicago from 
> >>>> flooding Wichita with 2.5MB of calls?
> >>>>
> >>>>
> >>>>
> >>>> Jonathan
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
____________________________________________________________
_______
> >> _________________Building a website is a piece
of cake. Yahoo! 
> >> Small Business gives you all the tools to get
> >>> online.
> >>> http://smal
lbusiness.yahoo.com/webhosting
> >>>
_______________________________________________
> >>> cisco-voip mailing list
> >>> cisco-voippuck.nether.net
> >>> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
> >>>
> >>
> >>
> >>
> >>
------------------------------------------------------------
----
> >> This message was sent using IMP, the Internet
Messaging Program.
> >>
> >>
_______________________________________________
> >> cisco-voip mailing list
> >> cisco-voippuck.nether.net
> >> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
> >>
>
>
>
>
------------------------------------------------------------
----
> This message was sent using IMP, the Internet Messaging
Program.
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voippuck.nether.net
> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
>
>
>
____________________________________________________________
__________
> ______________ We won't tell. Get more on shows you
hate to love (and 
> love to hate): Yahoo! TV's Guilty Pleasures list.
> http://tv.yahoo.c
om/collections/265
>
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip

Re: QOS for MPLS
country flaguser name
United States
2007-05-29 20:55:36
What about traffic shaping at the head end? 

-----Original Message-----
From: cisco-voip-bouncespuck.nether.net
[mailto:cisco-voip-bouncespuck.nether.net] On Behalf
Of Carter, Bill
Sent: Tuesday, May 29, 2007 1:43 PM
To: Jonathan Charles; Erick Bergquist
Cc: cisco-voippuck.nether.net
Subject: Re: [cisco-voip] QOS for MPLS

With MPLS and sites with different bandwidths, you should
set the QoS
based on the site bandwidth.  So it is ok to have 800k on
the T1's and
2500k on the DS3's.  Locations would prevent HQ from
flooding a
particular site.  

Because of the mesh possibilities of MPLS, I would set the
HQ Location
bandwidth to unlimited and the remote at ~800kb. 

If this is Unified CM 5.X you could use RSVP.  CM locations
are more
designed for a Hub and Spoke network.  RSVP accommodates a
meshed
topology.

-----Original Message-----
From: cisco-voip-bouncespuck.nether.net
[mailto:cisco-voip-bouncespuck.nether.net] On Behalf
Of Jonathan
Charles
Sent: Sunday, May 27, 2007 4:54 PM
To: Erick Bergquist
Cc: cisco-voippuck.nether.net
Subject: Re: [cisco-voip] QOS for MPLS

Which is the definition of MPLS, any-to-any communication.
All circuits
are point to point into the MPLS cloud and then routing in
the cloud to
each site.



Jonathan

On 5/27/07, Erick Bergquist <erickbeyahoo.com> wrote:
> I've seen one or two setups where the MPLS was fully
meshed (all sites
could talk to any other site), which makes QoS even
trickier.
>
> ----- Original Message ----
> From: "kelicarocomp.ro" <kelicarocomp.ro>
> To: Jonathan Charles <jonvoipgmail.com>
> Cc: cisco-voippuck.nether.net
> Sent: Sunday, May 27, 2007 3:50:17 PM
> Subject: Re: [cisco-voip] QOS for MPLS
>
> That is correct (although you should take some overhead
into account 
> as well). However, if you do not perform Call Admission
Control 
> beforehand (you do not limit the maximum number of
possible 
> simultaneous calls) you've done nothing, or worse.
>
> The classic example being when you have a line that
supports 4 calls, 
> when the fifth call enters the line, all calls will
suffer packet loss

> and delay, not only the fifth one.
>
> I'm not too versed in MPLS QoS, but the idea is always
the same.
> Prioritize voice traffic, but don't let it kill your
bandwidth, nor 
> itself. Thus the need for CAC, then something like
CBWFQ/PQ. If 
> possible, voice traffic should be beneath
shaping/policing limits, so 
> that neither would affect it.
>
> regards,
>    Zoltan
>
> Quoting Jonathan Charles <jonvoipgmail.com>:
>
> > My thinking is that I need to set the QOS to be
the same as the 
> > maximum number of calls to/from each site.
> >
> >
> > Jonathan
> >
> > On 5/27/07, kelicarocomp.ro <kelicarocomp.ro> wrote:
> >> As long as it is about "calls", CAC
is the sensitive way to go 
> >> about limiting the calls in the first place.
Do QoS "As close to 
> >> the source, as possible", remember? 
> >>
> >> If you do not have a CCM, but other set-up,
you should still look 
> >> in this direction first - to limit the calls
to a reasonable amount

> >> in the given directions, before they are
hitting your MPLS router.
> >>
> >> regards,
> >>   Zoltan
> >>
> >> Quoting Paul Choi <asobihoudaiyahoo.com>:
> >>
> >>> He's talking about QoS for MPLS, not CAC.
> >>>
> >>> --- "Clouse, Chris"
<chris.clouseberbee.com> wrote:
> >>>
> >>>> Use CallManager locations to perform
Call Admission Control.
> >>>>
> >>>> Christopher Clouse, CCNP CCDP CCVP MCP
Network+
> >>>>
> >>>>
> >>>> -----Original Message-----
> >>>> From: cisco-voip-bouncespuck.nether.net
> >>>> [mailto:cisco-voip-bouncespuck.nether.net] On Behalf Of Jonathan

> >>>> Charles
> >>>> Sent: Saturday, May 26, 2007 11:35 AM
> >>>> To: ciscovoip
> >>>> Subject: [cisco-voip] QOS for MPLS
> >>>>
> >>>> I have always understood that QOS
settings need to match on both 
> >>>> ends of a circuit... so, if you
allocate 800k on one side, you 
> >>>> need to do the same on the other.
> >>>>
> >>>> I am now working on an MPLS circuit
that has DS3s on some sides, 
> >>>> DS1s on others... do I still need to
match QOS settings?
> >>>>
> >>>> Customer wants 800k on the T1s and
2500k on the DS3s... I don't 
> >>>> think it will matter as I am matching
these bw limits on the 
> >>>> locations...
> >>>> but how do I throttle calls from a
DS3-side location to a DS1 
> >>>> location?
> >>>>
> >>>> For example... main site is in
Chicago, they have a DS3, one 
> >>>> remote site is in Wichita and has a
T1... so, I put 800k for 
> >>>> Wichita and 2500k for Chicago... what
is to stop Chicago from 
> >>>> flooding Wichita with 2.5MB of calls?
> >>>>
> >>>>
> >>>>
> >>>> Jonathan
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
____________________________________________________________
_______
> >> _________________Building a website is a piece
of cake. Yahoo! 
> >> Small Business gives you all the tools to get
> >>> online.
> >>> http://smal
lbusiness.yahoo.com/webhosting
> >>>
_______________________________________________
> >>> cisco-voip mailing list
> >>> cisco-voippuck.nether.net
> >>> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
> >>>
> >>
> >>
> >>
> >>
------------------------------------------------------------
----
> >> This message was sent using IMP, the Internet
Messaging Program.
> >>
> >>
_______________________________________________
> >> cisco-voip mailing list
> >> cisco-voippuck.nether.net
> >> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
> >>
>
>
>
>
------------------------------------------------------------
----
> This message was sent using IMP, the Internet Messaging
Program.
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voippuck.nether.net
> h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
>
>
>
____________________________________________________________
__________
> ______________ We won't tell. Get more on shows you
hate to love (and 
> love to hate): Yahoo! TV's Guilty Pleasures list.
> http://tv.yahoo.c
om/collections/265
>
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voippuck.nether.net
h
ttps://puck.nether.net/mailman/listinfo/cisco-voip

[1-4]

about | contact  Other archives ( Real Estate discussion Medical topics )