L2 QoS in MPLS

Hi All,
I want to know how to configure L2 QoS in FR-VLAN interworking in MPLS PE Routers, I used 7200VXR at VLAN side & 7300 at FR side and applied the attached QoS in the particular interfaces but I could see all the traffic passing through default...!!
I do mark ip dscp ef for VOICE at CE routers. 7300 having the IOS c7301-p-mz.122-25.S2.bin & 7200 having the IOS c7200-p-mz.122-25.S2.bin.
An early responce is Highly appriciated.
Tx,
Harin

Hi Sultan,
Thanks for the information... I think I've also done the same except for marking mpls exp..
In the literature I found that IP dscp or the precedence is copied to the MPLS exp, isn't that so? Have U tested on the IOS I've mentioned?
I've paste the contents of the attached file for Ur reference....
++++++++++++++++++++++++++++++++++++++++++++++++++++
Cisco 7200VXR
class-map match-any VOICE
match mpls experimental topmost 5
match ip precedence 5
match ip dscp ef
policy-map BR_OUT_POLICY
class VOICE
priority 48
class class-default
fair-queue
policy-map 128kL2_OUT_POLICY
class class-default
shape average 128000
service-policy BR_OUT_POLICY
interface GigabitEthernet0/3.100
encapsulation dot1Q 100
ip directed-broadcast
service-policy output 128kL2_OUT_POLICY
no cdp enable
xconnect 10.152.1.254 600 pw-class FR_ETHIP
Cisco 7300
class-map match-any VOICE
match mpls experimental topmost 5
match ip precedence 5
match ip dscp ef
policy-map HO_OUT_POLICY
class VOICE
priority 48
class class-default
fair-queue
interface Serial1/1:10
no ip address
ip directed-broadcast
encapsulation frame-relay IETF
frame-relay interface-dlci 100 switched
class 128kL2
frame-relay lmi-type ansi
frame-relay intf-type dce
map-class frame-relay 128kL2
no frame-relay adaptive-shaping
frame-relay cir 128000
frame-relay bc 1280
frame-relay be 0
frame-relay mincir 128000
service-policy output HO_OUT_POLICY
connect HARIN_TEST Serial1/1:10 100 l2transport
xconnect 10.151.1.254 600 pw-class FR_ETHIP
++++++++++++++++++++++++++++++++++++++++++++++++++++
Pls check the above & let me know...
Best Rgds,
Harin

Similar Messages

Best Practice QOS in MPLS core

Hi.
Wath is the recommendation in configuring QOS in the core mpls (PE-P)
we have a mixture of traffic of data, cell signalling, O&M, voice R4, IVR.etc. We have 7600 as PE and 12000 as P. The PE's have SIP-GE and WS-GE cards against the P. In some cases the traffic goes through two P's connected via SIP-GE cards. I Had seen that the WS cards have some special considerations about QOS.

Hi,
Here is a good starting point regarding the best practices:
http://www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRND/VPNQoS.html
The how to configure QoS for MPLS on 7600 :
WS cards: http://www.cisco.com/en/US/docs/routers/7600/ios/12.2SR/configuration/guide/mplsqos.html
SIP cards: http://www.cisco.com/en/US/docs/interfaces_modules/shared_port_adapters/configuration/7600series/76cfgsip.html#wp1162382
HTH
Laurent.

QoS in MPLS Packet drops

Hello
I have experienced the following situation recently. It hasn't fixed yet. If you have any idea, please advise. Any comments are welcome!
The problem was that the voice packets have been dropped in class Voice despite the fact that the interface's utilization is quite low. Please see the policy-map interface output below.
Service-policy output: out_(3072k/3072k)_QoS (4754)
queue stats for all priority classes:
queue limit 192 (packets)
(queue depth/total drops/no-buffer drops) 0/297/0
(pkts queued/bytes queued) 12372/1041424
Class-map: Voice (match-all) (4755/7)
12098 packets, 1042365 bytes
5 minute offered rate 32000 bps, drop rate 3000 bps
Match: ip precedence 5 (4756)
Priority 50 (%) (1536 kbps) burst 1250000 (bytes)
I removed the service-module from the multilink interface and restored. I repeated the procedure for a few times. At some point, I noticed that queue-limit of LLQ changed from 192 to 384. I didn't change it manually. It was changed by itself. Then the drop stopped.
Service-policy output: out_(3072k/3072k)_QoS (6339)
queue stats for all priority classes:
queue limit 384 (packets)
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts queued/bytes queued) 2628/221321
Class-map: Voice (match-all) (6340/7)
2653 packets, 228634 bytes
5 minute offered rate 14000 bps, drop rate 0 bps
Match: ip precedence 5 (6341)
Priority 50 (%) (1536 kbps) burst 1250000 (bytes)
* I omitted some of the output due to the text size in this forum.
The average packet sizes in queue-limit 192 and 384 are almost same (86 bytes/packet).
Does anyone know how does the IOS calculate the queue-limit in LLQ? I know that it changes dynamic in LLQ but would like to know the algorithm.
Did anyone have a similar experience?
Thank you,

Hello Creed,
>> I just think that the P router might not able to police the traffics as it get routed into the tunnels...
With both LDP LSPs and MPLS TE LSPs traffic is forwarded inside MPLS frames and so EXP field of the topmost label is accessible to P routers to provide diffserv QoS treatments.
Usually P routers implement only outgoing scheduling (queueing) combined with congestion avoidance (WRED).
The service policies are applied outbound the physical interfaces.
Rate control of what traffic enters the MPLS cloud both LDP LSPs and MPLS TE LSPs is made on PE at the edge before traffic enters the MPLS space.
DSCP bits should not be accessible inside the MPLS cloud once the ip packet travel inside an MPLS label stack.
Actually some inside inspections can be performed for flow based load-balancing purposes.
So policing on the P routers is not used in general.
Hope to help
Giuseppe

An MPLS Cloud

Hi,
I'm looking at a topology where a number of collapsed PE/P nodes (50>100) access a L2 cloud in a full-mesh topology. The underlying cloud architecture could be something like VPLS from an external provider with the MPLS domain mapped on top. The attached shows the nodes on the periphery of the cloud and these could be spread globally. What I'm looking for are pros and cons and whether there is a case study or CVD for this type of topoolgy. Particular interest is on scalability around IGP, LSP's, sub-optimal routing conditions, IGP/LSP synchronisation, IGP link/domain costs etc... The network will provision L2/L3 VPN's and other standard MPLS features.
Thanks, Wayne

Hi,
You'd need to implement QOS for sure. What many people do is to have data traffic use precedence/EXP 0 and Voice precedence/EXP 5. You could make the video traffic precedence/EXP 4, for example. This also maps to certain DSCP values.
You could also consider MPLS Traffic Engineering (TE). There is point-to-point TE for your data traffic, but you could also deploy (check platform and IOS support) point-to-multipoint (p2mp) TE to carry the IP multicast (video) traffic. With TE, you could steer traffic through the network and have fast protection (FRR). You'd still need to use QOS, because MPLS TE does not automatically hook into QOS.
Regards,
Luc

MPLS Benefit???????

Hi all,
I am investigating why we, as an enterprise, should move toward MPLS. What benefit does it give you? Anyone implements MPLS (not buying MPLS service) on their network and do you notice any difference? Do you gain any more speed? Are you able to control traffic better than tuning/redesigning IGP? Why QoS on MPLS is better? Please let me know. Thank you!

Hi,
here is some links.. I think they would be useful for you.
http://www.eventreg.com/cisco_emea_nw2005/content_viewer/
- IPM-D02 - Designing an Enterprise MPLS Network
- IPM-D03 - Advanced MPLS Deployment in Enterprise Networks
http://www.cisco.com/en/US/netsol/ns483/networking_solutions_customer_profile0900aecd802b1d7f.html
http://www.cisco.com/en/US/netsol/ns656/networking_solutions_program_category_home.html
- Next Generation Enterprise MPLS VPN-Based MAN Design and Implementation Guide
A little bit off topic :-)
http://www.juniper.net/solutions/literature/white_papers/200183.pdf
Regards,
Alexander

Ask a CBWFQ and LLQ question

we config qos on mpls network.use llq in CBWFQ. i have a question.
if i config LLQ for bandwidth 1m on 2M E1 line, and business data 0.5M(CBWFQ),defautl class 0.5M(CBWFQ). can i config this llq burst to 2M if line does not congest. or can i config business data or default class burst to 2M when line does not congest.
IF line congest. can llq and business,default class get gurantee bandwith?
i find when i config llq,i can use burst parameter:
priority bandwidth burst
when i need llq to burst to 2m, Does i need config this burst parameter. or i don't need config this burst parameter, i can get burst too.
thank you!
Tom

(Yet another explanation.)
"if i config LLQ for bandwidth 1m on 2M E1 line, and business data 0.5M(CBWFQ),defautl class 0.5M(CBWFQ). can i config this llq burst to 2M if line does not congest."
LLQ should allow up to the full 2 Mbps, if there's no congestion. If there's congestion, LLQ will police itself at the rate specified. More on bursting, below.
"or can i config business data or default class burst to 2M when line does not congest."
Either the business data or default classes should also be able to obtain full bandwidth, if there's no congestion. Excess demand will queue the excess packets.
"IF line congest. can llq and business,default class get gurantee bandwith?"
Yes, if there's congestion, LLQ will police its traffic, i.e. immediately drop excess, other classes will queue excess traffic; will drop if queues overflow (and/or WRED drop).
"i find when i config llq,i can use burst parameter:
priority bandwidth burst
when i need llq to burst to 2m, Does i need config this burst parameter. or i don't need config this burst parameter, i can get burst too."
If you specify burst, you're really adjusting the time interval the policier operates. I believe the default is based on 200ms, so if there's more than 25,000 bytes (1 Mbps * .2 sec / 8 bits/byte), the excess will be dropped. (All the non-dropped bytes will transmit at full rate.)
When to adjust burst? If your traffic's long term average is under your LLQ bandwidth setting, but short term traffic rate is very variable (e.g. many video streams), you should increase the burst size to avoid dropping packets.

PBTS on ASR 9k

I'm trying to implement Policy Based Tunnel Selection on ASR 9k. Official documentation is completely wrong about it, stating we should use "policy-class" command. Instead, I was told by TAC a while ago that we should be using "forward-class", which should be assigned by policy-map type pbr on inbound interface. I couldn't find any documentation about it.
TAC also mentioned that
"Any traffic that does NOT match the configured policy definition, will be
associated with this default-class, and only TEs associated with
default-class will be used for forwarding. Similarly, if the traffic is
classified to forward-class X, but there is no TE associated with this
class (X), then, the traffic will use the
default-class TEs. (Note that if there is no TE in the default-class,
then the packet will be DROPPED in this case)."
What I'm seeing on 9k with 5.1.3 is that in absence of "default tunnel" any traffic without explicitly configured tunnel for that class follows tunnel with smallest forwarding class, and in absence of any tunnel, just normal IGP path. Even in MPLS L3 VPN environment, when pbr is applied to interface in VRF and BGP next-hop of VPN prefix is routed over TE tunnel.
I wonder if I'm not looking at things correctly, or DROP behavior was changed in 5.1.3.
Any additional info on PBTS feature will be appreciated.

My main concern is about what happens when traffic is assigned some non-default class by PBR and there is NO TUNNEL AT ALL (no class-specific, no default) for that destination.
4.3.1 doc says "All non-TE interfaces through the destination route was learned will be pushed down by routing protocol to the forwarding plane with forwarding class set to default-class."
I understand it as "no matter what forward-class is assigned by PBR, if there is no TE tunnel to given destination, traffic will follow normal IGP path". Is it correct?
In my scenario, I get traffic in VRF interface and do inbound QoS marking MPLS EXP imposition based on incoming DSCP. If I want PBTS on the same interface to classify based on newly imposed MPLS label stack EXP, I should use "service-policy apply-order qos pbr", right?
Any plans for supporting PBTS on BVI interfaces?

Calling DSCP or IP Precedence on traffic Policing

Hi Guys,
I have a good question and I can say it's challenging questiion. we have some policy-map on some interfaces but because these interfaces are dedicated to some customers that they are using just for voice and video. I put some detaqil for better understanding
router#sh policy-map QOS:POLICE:100M:pm-q
Policy Map QOS:POLICE:100M:pm-q
    Class class-default
     police cir 100000000 bc 3125000
       conform-action transmit
       exceed-action drop
     service-policy QOS:RATE:30-x:pm-q
router#sh policy-map QOS:RATE:30-x:pm-q
Policy Map QOS:RATE:30-x:pm-q
    Class QOS:REALTIME:cm-q
      set qos-group 5
     police cir percent 30
       conform-action transmit
       exceed-action drop
    Class QOS:INTERACTIVE:cm-q
      set qos-group 3
    Class QOS:CONTROL:cm-q
      set qos-group 6
     police cir percent 10
       conform-action transmit
       exceed-action drop
    Class QOS:BUSINESSDATA:cm-q
      set qos-group 1
    Class class-default
      set qos-group 0
we put this because we expected gauranty 30% of that bandwidth. It means we expected gauranty 30mbps but now guys saying this type of configuration is not working because calling dscp on policing is not working.
now we have to change it to below
router#Policy Map QOS:POLV2:GWS:100M:pm-q
    Class QOS:INT:MPLS:cm-q
     police cir 120000000 bc 21000000 be 42000000
       conform-action transmit
       exceed-action drop
       violate-action drop
now question is this change right ?
Thanks
Majid

Sarah
1) L2 switches can trust the dscp marking as well. The 2960 is a layer 2 only switch and the default is untrusted but if you then enter
"mls qos trusted" you have a choice of 'cos|dscp|ip-precedence'. The default if no choice is entered is DSCP.
2) If "mls qos trust dscp" is entered then the switch will use the DSCP marking found in the packet. This will then be used as the internal DSCP marking that all switches use. Unless you have a DSCP-DSCP mutation map the value used will be the value received in the packet.
Jon

URGENT: QoS Design on Data Center MPLS - MediaNet Question...

Hello,
I am posting this in hopes I can get some guidance from anyone who has done this in the field. We have a large enterprise customer with 21 sites all around the world, they have Verizon MPLS and are experiencing QoS related issues on their WAN regarding Video/Voice. We have proposed remediating their network acccording to the Enterprise QoS SRND 3.3 and the new MediaNet SRND to account for Video and TP QoS (
http://www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRND_40/QoSCampus_40.html )
Here is the problem/question that was proposed in our presales meeting and I honestly don't know where to look for an answer... I am not asking for anyone to design a solution for me, just merely point me in the right direction:
The Data Center has a ~40MB MPLS Connection ( full mesh ) into the cloud ( Verizon )
Site A has a 8MB connection
Site B has a 4MB connection
I know on the Service policy and the interfaces at SiteA and SiteB I can assign "Bandwidth xxxx" and use ~95% of the bandwidth to do queuing and shaping/policing ect. I am not concerned with SiteA and SiteB, that I think I can handle...
Question was posed from the customer, "How can we ensure at the DataCenter level the 40MB MPLS is "chopped" up so that only 8MB of the total speed goes to SiteA ALONG with an attached QoS policy designed for that specific site, as well as ensure only 4MB goes to SiteB with an attached QoS policy.
So I am looking for a way to allocate bandwith per site on the DC 40MB connection going into the cloud ( so that SiteB cannot use more than 4MB ) and attach a MediaNet specific QoS Service policy to that site. The customer does not have seperate MPLS circuits for each site, they all come into the DC on 40MB shared ethernet connection ( no VC, or dedicated circuits to other sites ).
Any thoughts on if this is possible?
Thanks!
Alex

This is an example I have seen and I hope that is useful to you.
Site A
Subnet: 172.16.1.0/24
Site B
Subnet:172.16.2.0/24
HeadOffice:
ip access-list extended Site_A
permit ip any 172.16.1.0 0.0.0.255
ip access-list extended Site_B
permit ip any 172.16.2.0 0.0.0.255
class-map match-any Site_A
match access-group name Site_A
class-map match-any Site_B
match access-group name Site_B
policy-map To_Spokes
class Site_A
shape average 8000000
service-policy Sub_Policy(Optional)
class Site_B
shape average 4000000
service-policy Sub_Policy(Optional)
class class-default
shape average 28000000
service-policy Sub_Policy(Optional)
Interface G0/0
Description To MPLS cloud
bandwidth 40000000
service-policy output To_Spokes
interface G0/1
Description To HeadOffice
bandwidth 40000000
service-policy output To_Spokes
It would be greatly appreciated if someone can correct this or improve it as I am still learning.
Please see the netflow graph from one of our routers using a similar policy as above.

QoS best practise in MPLS

Hi, I'm having a scenarios for applying QoS on the entire customer network. Its something like this:
i. Equipment -> Layer2 SW -> PE VRF -> P
The equipment's traffics are not marked with anything at least, the equipment gateway would be the PE VRF. I'm thinking of such QoS in these scenarios:
i. PE ingress, match any based on the VRF and set dscp marking from here
ii. PE egress, match by the dscp marked @ the ingress interface and perform policing/shaping and then conversion to MPLS Experimental bit
iii. P ingress, implement congestion avoidance here, as far as I understand, congestion avoidance are based on dscp, if I perform DSCP convertion to EXP bit in the PE egress interface, would the P ingress interface still use the congestion avoidance?
I'm venturing into the possibility on how the QoS is best implemented in such scenarios, and appreciate if you guys with such experiences to shed some lights and ideas here...
Thanks and have a nice day

can I safely says the approach would be something like this?
@ the PE
Router(config)# policy-map policy1
Router(config-pmap)# class class1
Router(config-pmap-c)# configure the dscp marking
check-in this policy as input under the vrf table as this is where the traffic would initiate from the equipment
Router(config)# policy-map policy2
Router(config-pmap)# class class2
Router(config-pmap-c)# match the dscp marked @ the input vrf
Router(config-pmap-c)# set the mpls experimental topmost bit
Router(config-pmap-c)# policing the traffic based on bandwidth percent or CIR
check-in this policy as input @ the PE egress interfaces -> P routers, means the PE egress interface will perform the EXP marking based on the DSCP bit and perform the policing here, would be be efficient way of doing QoS?
Then from there onwards, P routers only based on the EXP bit to adjust the congestion avoidance? But I saw we can use random-detect dscp @ the P routers, is there any congestion avoidance using the EXP bit @ the P routers end? As if we set the EXP bit on the PE egress interface, P routers would not be able to configure congestion avoidance based on the DSCP right?
I'm just venturing out the easier and cleaner way to configure the QoS so configuration maintenance would be better in near future.
Thanks for your suggestion bro

QoS MPLS VRFs

Hi guys,
we are creating a new MPLS cloud with the following VRFs: VRF- Voice, VRF- Data and VRF - Citrix.
My question is: is VRF traffic indepedent from other VRFs (talking about QoS) or I have to request to my MPLS provider to apply QoS?
I would like to have 3 Levels of QoS: Voice, Citrix and Data (that matches with the VRFs).
So it is QoS needed on the MPLS Provider side to increase my traffic performance for voice and Citrix?
Thank you very much for your help.
Jordi

Hi Jordi
You will need to have QOS configured for all the VRFs separately because of two main reasons:
1. Creating a VRF doesn't guarantee that you will get priority.
2. After the traffic enters the Service Provider backbone its all MPLS traffic and many customers share the same backbone, so to have an effective treatment of your traffic you will need to define proper QOS.
Regads
Vivek

MPLS Qos

hi, i had a doubt.
our network is ip N/w and our service provider is C&W MPLS N/w , we had configured Qos in our routers and marking done by using DSCP for voice traffic and for IPSEC traffic we are using access-list , i know few thing like if our data want to cross MPLS network, DSCP to IP Precedence mapping will be done in Provider Edge router because MPLS Qos is based on MPLS exp bit 3 bit , but my doubt is how the ipsec data will be marked in PE router of C&w which we had mark it by using Access-list...

HI Hariharan, [Pls RATE if HELPS]
For the IPSec marking's to work please enable "qos pre-classify" command in CE Router.
When packets are encapsulated by encryption headers, QoS features are unable to examine the original packet headers and correctly classify the packets. Packets traveling across the same tunnel have the same encrypted headers, so the packets are treated identically if the physical interface is congested. With the Quality of Service for Virtual Private Networks (VPNs) feature, packets can now be classified before the encryption occur.
The qos pre-classify command enables the QoS for VPNs feature .
Hope this Helps. Please Rate if HELPS
Best Regards,
Guru Prasad R.

L3 VPN on MPLS and QoS

Hi there
I've got some problems with QoS for one of our L3 VPN customers.
Our network consist of 76xx / SUP720-3B routers with SIP400 interfaces for core facing and various LAN interfaces for customer facing.
The customer VRF interfaces are configured as ordinary Vlan SVI's, e.g.
interface vlan123
ip vrf forwarding VPN
ip address 1.1.1.1 255.255.255.252
When setting up the VPN for QoS, I've done some digging and decided that "Short Pipe mode" is the right type for me. I've configred the system just as described in the manual for 7600 SR software, but I still don't get any QoS settings transferred across my network. Actually a "show mls qos" tell me, that I'm currently using "Pipe mode" for the MPLS VPN.
Anyone who might have some relevant information to share on QoS on L3 VPN MPLS.
Regards,
Lars

its been a while but Layer 2 cards are cheap cards and have no smart functionality. I thought pipe mode was for EoMPLS type functions and not layer 3 vpns.

MPLS QoS on 6500

N/A

Hi Siddigirf
The requirements which you have mentioned I think can be very well implemented on c6500 Platform.
Howerver before putting up my understanding in front of you regarding this QoS requirement I would like to confirm with you why you specifically need Long Pipe (PIPE) mode of operation here..As your requirement is that Customer;s DSCP ie IP QoS marking be remain untouched through MPSL Cloud then I would like to mention that in MPLS QoS the default mode of operation is Short PIPE Mode wherein that the Customer QoS remains untouched and passed transparently across the cloud and PHP has no effect on this behaviour. Remember PHP is on EXP and Customer QoS is in DSCP which is in the underlying IP Packet.Under default mode of Short PIPE operation the PHB((Per Hop Behaviour)) at the Egress PE is decided based on underlying DSCP value of the IP Packet
PIPE mode is useful in Carrier Supporting Carrier Scenarios weherby we want to send traffic to the upstream Carrier with the same PHB treatment as in the porivider's own MPLS Cloud and the PHB is based on EXP value and not DSCP Value.
Having said that I think we should be using Short PIPE Mode only and PHP enabled on the Egress PEs.Please confirm so that I can think more on the actual QoS requirement at the Ingress and Egress PEs.
Regards
Varma

For encrypted flows, how does the MPLS do the QOS?

After encrypting the data, send them to MPLS, how does the MPLS do the QOS?

Hi,
the IPSec standard mandates, that the ToS Byte from the original header is copied to the new IPSec header. So if your IP packets are already marked everything is straight forward - MPLS does not make any difference. For the MPLS network it will be just marked IP packets and the marking is copied to the MPLS experimental bits. QoS policies within an MPLS core only use experimental bits only.
Regards, Martin

L2 QoS in MPLS

Similar Messages

Maybe you are looking for