cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
792
Views
0
Helpful
5
Replies

QoS on Metro E Links

Mikey John
Level 1
Level 1

Hi Guys,

 

We have a 50M p2p Metro E circuit between two locations. We had ordered this 50M circuit with 5M COS for Voice. Now, our requirement is to increase the Voice COS BW to 10M.

 

But, the carrier says "Elink+ bandwidths are equivalent to a guaranteed Class of Service in point-to-point circuits. If you want to make class of service changes, this can only be done on your router."

 

How can they guarantee BW for any traffic type (Voice or Data) without proper QoS? Am I missing something, or this is generally the way COS is provided in Metro E circuits.

 

Appreciate your inputs.

 

Cheers
Mikey

1 Accepted Solution

Accepted Solutions

Joseph W. Doherty
Hall of Fame
Hall of Fame
On a p2p link, for your traffic vis-a-vis itself, there's no point to MetroE QoS. Whatever QoS you might need, would/should be done on your devices that connect to the MetroE circuit.

However, where MetroE QoS might be of (great) importance, even on a p2p link, would be how your traffic is treated across the MetroE network relative to other customer's traffic. Unable to say what will happen to your VoIP traffic if you exceed your CIR for it. If your MetroE provider doesn't prioritize it, relative to other customer non-VoIP traffic, then using their CoS markings is unnecessary. If they do prioritize, relative to other customer non-VoIP traffic, but don't really enforce a CIR for it, you could consider marking all your traffic with their VoIP CoS tag (to insure all your traffic gets the best service across the MetroE network). If you provider does enforce a VoIP CIR, then depending how they enforce it will matter to how you use it.

View solution in original post

5 Replies 5

Hello Mikey,

 

hard to tell what they mean by that. When you put in the original order, how was that processed, did you have to configure anything on 'your' router ?

Joseph W. Doherty
Hall of Fame
Hall of Fame
On a p2p link, for your traffic vis-a-vis itself, there's no point to MetroE QoS. Whatever QoS you might need, would/should be done on your devices that connect to the MetroE circuit.

However, where MetroE QoS might be of (great) importance, even on a p2p link, would be how your traffic is treated across the MetroE network relative to other customer's traffic. Unable to say what will happen to your VoIP traffic if you exceed your CIR for it. If your MetroE provider doesn't prioritize it, relative to other customer non-VoIP traffic, then using their CoS markings is unnecessary. If they do prioritize, relative to other customer non-VoIP traffic, but don't really enforce a CIR for it, you could consider marking all your traffic with their VoIP CoS tag (to insure all your traffic gets the best service across the MetroE network). If you provider does enforce a VoIP CIR, then depending how they enforce it will matter to how you use it.

Hi George & Joseph,

 

I have this configured on my router. So, you mean on a p2p link, I can control the QoS classification from my end, and no intervention needed from the service providers?

 

policy-map QOS_POLICY_REV1
class Voice
priority percent 10
class Interactive_Video
bandwidth percent 25
class Call_Signaling
bandwidth percent 5
class Network_Control
bandwidth percent 2
class Critical_Data
bandwidth percent 27
random-detect dscp-based
class Scavenger
bandwidth percent 1
class class-default
bandwidth percent 25
random-detect
queue-limit 1024 packets

policy-map SHAPE_QOS_BASIC_WAN
class class-default
shape average 50000000 account user-defined 18
service-policy QOS_POLICY_REV1


Interface Gig0/0/0
service-policy output SHAPE_QOS_BASIC_WAN

 

 

 

Yes, except as noted, MetroE QoS may have an impact relative to other traffic within their network.

BTW, I recommend against using WRED, unless you're a QoS expert. Instead, if your platform supports it, FQ in all non-LLQ classes.

Thanks Joseph. Really helps!!