|
Home > Archive > Voice over IP Cisco > December 2007 > QoS for Circuit Emulation over IP ?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
QoS for Circuit Emulation over IP ?
|
|
| d4rk f1br 2007-12-27, 7:11 pm |
| I am in the midst of deploying two cisco 2821's, each of them contain a
NM-CEM-4TE1. Each 2821 connects to a 6509. Each 6509 is connected via gig
fiber links.
The T1 side of each 2821 connects to some Aspect system.
Anyway, I have things up and working, the circuit emulation is working and
the remote Aspect shelf comes up which in turn brings up the Aspect phones.
Voice quality is not perfect though, and I need to figure out some QoS to
try to ensure this traffic gets the highest priority.
Not sure the best way to approach this, as I suck (MAJOR SUCK) at QoS, my
track record thus far is umm... well lets move on, thank god for autoqos!
:-)
My guess is I have to do something on the 2821s although I am not sure if
that really is needed since the only thing the 2821's do is handle this
single T1.
I am certain the 6509's are going to need something to prioritize the
traffic coming in from the 2821's and ensure that this traffic takes
precedence both coming in and leaving.
I got the QoS SRND (my cisco sales engineer sent it to me when I asked about
suggestions related to this) gee thanks huh... 300+ pages of qos
material... yeah!
Trying to narrow down what I need to look for and research, not asking for a
cut and paste example config, as I know every network is different. I am
just not sure where to approach this from.
Anything special about the circuit emulation I would need to consider, do I
tag it some how the same as my other voip traffic for the cisco phones? Not
sure where to start looking you know, so any suggestions or tips would be
appreciated.
Thx!
| |
| Jason Wydra 2007-12-28, 1:12 am |
| Not sure about Aspect phones. Do they automatically mark for voice traffic?
If not, then I believe you need to manually mark voice traffic on the
ingress switch ports.
On Dec 27, 2007 6:22 PM, d4rk f1br <d4rkf1ber@gmail.com> wrote:
> I am in the midst of deploying two cisco 2821's, each of them contain a
> NM-CEM-4TE1. Each 2821 connects to a 6509. Each 6509 is connected via gig
> fiber links.
>
> The T1 side of each 2821 connects to some Aspect system.
>
> Anyway, I have things up and working, the circuit emulation is working and
> the remote Aspect shelf comes up which in turn brings up the Aspect phones.
>
> Voice quality is not perfect though, and I need to figure out some QoS to
> try to ensure this traffic gets the highest priority.
>
> Not sure the best way to approach this, as I suck (MAJOR SUCK) at QoS, my
> track record thus far is umm... well lets move on, thank god for autoqos!
> :-)
>
> My guess is I have to do something on the 2821s although I am not sure if
> that really is needed since the only thing the 2821's do is handle this
> single T1.
>
> I am certain the 6509's are going to need something to prioritize the
> traffic coming in from the 2821's and ensure that this traffic takes
> precedence both coming in and leaving.
>
> I got the QoS SRND (my cisco sales engineer sent it to me when I asked
> about suggestions related to this) gee thanks huh... 300+ pages of qos
> material... yeah!
>
> Trying to narrow down what I need to look for and research, not asking for
> a cut and paste example config, as I know every network is different. I am
> just not sure where to approach this from.
>
> Anything special about the circuit emulation I would need to consider, do
> I tag it some how the same as my other voip traffic for the cisco phones?
> Not sure where to start looking you know, so any suggestions or tips would
> be appreciated.
>
> Thx!
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| Scott Voll 2007-12-28, 1:11 pm |
| I'm with Jason.
if the traffic is not marked by default.... mark it as close to to the
ingress as possible. IE. at the 2800 mark it so as it goes across your
network it's marked all the way. Since it's Voice I would mark it with DSCP
EF like your other voice traffic so autoQOS could still be your friend. (but
my Qos is almost as bad as yours)
Scott
On Dec 27, 2007 5:14 PM, Jason Wydra <jasonwydra@gmail.com> wrote:
> Not sure about Aspect phones. Do they automatically mark for voice
> traffic? If not, then I believe you need to manually mark voice traffic on
> the ingress switch ports.
>
> On Dec 27, 2007 6:22 PM, d4rk f1br <d4rkf1ber@gmail.com> wrote:
>
>
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| d4rk f1br 2007-12-29, 1:12 am |
| "I don't think the traffic is marked but I may be wrong.
There is a command "ip dscp ??" that can be used to mark packets originating
from the CEM. But the examples list numbers like "ip dscp 36" not EF
You can find a diagram of the layout here:
http://www.mediafire.com/?czgmxvd6dxs
You mentioned marking it as close to the ingress as possible, I assume that
would be the 2821s?
On Dec 28, 2007 9:49 AM, Scott Voll <svoll.voip@gmail.com> wrote:
>
> I'm with Jason.
>
> if the traffic is not marked by default.... mark it as close to to the
> ingress as possible. IE. at the 2800 mark it so as it goes across your
> network it's marked all the way. Since it's Voice I would mark it with DSCP
> EF like your other voice traffic so autoQOS could still be your friend. (but
> my Qos is almost as bad as yours)
>
> Scott
> On Dec 27, 2007 5:14 PM, Jason Wydra <jasonwydra@gmail.com> wrote:
>
>
>
| |
| Justin Steinberg 2007-12-29, 1:11 pm |
| Assuming you want to mark your CEM traffic as EF, add the command 'ip dscp 46'
dscp 46 = EF
You will then need to verify your QoS policies end-to-end on the IP
path between the two 2821's to verify that dscp EF traffic has
priority.
On Dec 28, 2007 9:40 PM, d4rk f1br <d4rkf1ber@gmail.com> wrote:
> "I don't think the traffic is marked but I may be wrong.
>
> There is a command "ip dscp ??" that can be used to mark packets originating
> from the CEM. But the examples list numbers like "ip dscp 36" not EF
>
> You can find a diagram of the layout here:
>
> http://www.mediafire.com/?czgmxvd6dxs
>
>
> You mentioned marking it as close to the ingress as possible, I assume that
> would be the 2821s?
>
>
>
>
>
>
> On Dec 28, 2007 9:49 AM, Scott Voll <svoll.voip@gmail.com> wrote:
>
> ingress as possible. IE. at the 2800 mark it so as it goes across your
> network it's marked all the way. Since it's Voice I would mark it with DSCP
> EF like your other voice traffic so autoQOS could still be your friend. (but
> my Qos is almost as bad as yours)
> traffic? If not, then I believe you need to manually mark voice traffic on
> the ingress switch ports.
> a NM-CEM-4TE1. Each 2821 connects to a 6509. Each 6509 is connected via
> gig fiber links.
> and the remote Aspect shelf comes up which in turn brings up the Aspect
> phones.
> to try to ensure this traffic gets the highest priority.
> my track record thus far is umm... well lets move on, thank god for autoqos!
> :-)
> if that really is needed since the only thing the 2821's do is handle this
> single T1.
> traffic coming in from the 2821's and ensure that this traffic takes
> precedence both coming in and leaving.
> about suggestions related to this) gee thanks huh... 300+ pages of qos
> material... yeah!
> for a cut and paste example config, as I know every network is different. I
> am just not sure where to approach this from.
> do I tag it some how the same as my other voip traffic for the cisco phones?
> Not sure where to start looking you know, so any suggestions or tips would
> be appreciated.
>
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
|
|
|
|
|