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

Similar Messages

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.

CBWFQ style QoS on 6500 (Native)

Hi, Is it possible to have CBWFQ style QoS on 6500 SUP2/MFSC2/PFC2, 12.1.23E on the LAN cards, the cards with 1P2Q2T type ports (not the flexWANs). I have read 6500 PFC QoS documentation and did not found any reference to router style CBWFQ (I did not find an option for defining policy maps with 'bandwidth' under classes like the way we do on router IOS). Wondering if it is possible at all with HW/SW combination mentioned above.
If it not possible on the HW above, is it possible with any new HW like S720 etc and 12.2 codes ?
thanks
Iftikhar

CBWFQ is not supported on the 6500, except in the case of WAN interfaces, as the QoS is not supplied by the PFC for these modules.
HTH,
Bobby

MPLS QOS Diffserv Models Qn

Hi All
Maybe someone can explain to me the difference between Pipe and short pipe Model with regards to the Egress LSR actions.
This is the way i understand it, not really understanding, confused more less
With Pipe model, the egress LSR forwards Packets based on the LSP Diffserv Information, right ? MPLS per hop (exp bits and EXP bits are not propagated to IP Precedence.
Short pipe, the Egress LSR forwards the ip packet based on the tunneled Diffserv information
My question is ? With pipe model, at the egress LSR, how is the packet forwarded based on LSP Diffserv information ? This is the egress LSR, doesnt that mean that before the packet is forwarded to the output interface, the Label is stripped so, its now IPV4 therefore with original DSCP ? So what does the forwarding based on LSP Diffserv mean ? I can understand the Short pipe model as forwarding is based on the tunneled Diffserv information, original DSCP from the customer
As i said, am confused, someone put me right please
Regards
MM

Hi,
Well you are 100% correct!
The answer to your question is however, when the MPLS VPN label is sent into the PE router from the P router, a policy map is configured inbound on the interface (P-PE), this will then set the qos-group value, so that the value of the MPLS EXP is 'remembered' in memory, then on the outbound PE-CE link another policy-map, will be configured, with a class-map that matches the previously defined qos-group, and then sets the OOS settings as required.
Here is a link describing mpls qos.
http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_diffserv_tun_mode_ps6350_TSD_Products_Configuration_Guide_Chapter.html
HTH
LR

QOS on 6500 routed interface

All of the QOS configuration guidance I've seen in the documentation on this website refers to 6500 switched interfaces (switchport mode access/trunk).
Is the QOS configuration different on a 6500 routed interface. For instance on an interface between two core switches in a routed (Layer 3) core?
I have already reviewed all of the IOS-related 6500 Cisco documents I could find, and the latest QOS SRND with no luck finding info on this issue.
Thanks
Greg

This URL should help you:
http://www.cisco.com/application/pdf/en/us/guest/products/ps708/c2001/ccmigration_09186a00801a90cc.pdf

Without 'MLS QOS' in 6500 does any interface queueing and trusting take place?

I have a 6500 that does not have 'mls qos' global configured, although the interfaces do have 'mls qos trust dscp' on them as in:
interface GigabitEthernet3/3
switchport
switchport access vlan 536
switchport mode access
switchport voice vlan 910
logging event link-status
mls qos trust dscp
spanning-tree portfast
When I 'show queueing int gx/x', it does show the default queueing structure of the interface as in:
LLT-6509AS-A#sh queueing int g3/3
Interface GigabitEthernet3/3 queueing strategy: Weighted Round-Robin
QoS is disabled globally
Port is untrusted
Extend trust state: not trusted [COS = 0]
Default COS is 0
    Queueing Mode In Tx direction: mode-cos
    Transmit queues [type = 1p3q8t]:
    Queue Id    Scheduling Num of thresholds
       01         WRR                 08
       02         WRR                 08
       03         WRR                 08
       04         Priority              01
---- snip ----
    queue thresh cos-map
    1     1      0 1 2 3 4 5 6 7
    1     2
    1     3
    1     4
    1     5
    1     6
    1     7
    1     8
Packets dropped on Transmit:
    BPDU packets: 0
    queue              dropped [cos-map]
    1                        0 [0 1 2 3 4 5 6 7 ]
    2                        0 []
    3                        0 []
    4                        0 []
Packets dropped on Receive:
    BPDU packets: 0
    queue              dropped [cos-map]
    1                        0 [0 1 2 3 4 5 6 7 ]
So just what does the global 'mls qos' do? Without it is the command 'mls qos trust dscp' ignored?
I'm trying to track down where in our network dscp settings are being stripped out of packets and this is when I noticed the 'mls qos' was not configured.

it enables QOS on the switch, without it no QOS is being used.
Sent from Cisco Technical Support iPhone App

MPLS QoS on 7204 VXR with NPE-G1

Hi, I want to prioritize voice traffic which comes in on Gig0/2.30 (marked with ToS 5 (184)) and reserve a bandwidth for it of 5 Mbps (class PREMIUM priority 5000)on tag-switching interface Gig0/1.
Now sh int gig0/1 mpls-exp shows:
GigabitEthernet0/1
Input
Exp Value 0: 38 packets, 3256 bytes
Exp Value 5: 1000 packets, 1522000 bytes
Output
Exp Value 0: 38 packets, 3104 bytes
Exp Value 5: 1000 packets, 1518000 bytes
sh policymap int gig0/1 shows:
GigabitEthernet0/1
Service-policy output: QOS-OUT
Class-map: PREMIUM (match-all)
1000 packets, 1518000 bytes
5 minute offered rate 37000 bps, drop rate 0 bps
Match: mpls experimental topmost 5
Queueing
Strict Priority
Output Queue: Conversation 264
Bandwidth 5000 (kbps) Burst 125000 (Bytes)
(pkts matched/bytes matched) 0/0
(total drops/bytes drops) 0/0
It seems for me that this works, but I expected to see
(pkts matched/bytes matched) 1000/1518000 in stead of 0/0 !?
Does anyone know if this policy-map is working or not ?
Best regards,
Peter

Hello Peter,
a detailed explanation of all counters can be found in "Understanding Packet Counters in show policy-map interface Output"
http://www.cisco.com/en/US/tech/tk543/tk760/technologies_tech_note09186a0080108e2d.shtml
In brief: the counter does not increase, if you have no congestion and the packets are CEF switched. Basically it counts the amount of packets in the L3 queueing system matching the specific class. No congestion means no packets in L3 queueing system, thus (pkts matched/bytes matched) 0/0
Hope this helps! Please rate all posts.
Regards, Martin

MPLS QoS: RDM - DS-TE

On a RDM with DS-TE do I need to configure a tunnel per every class-type, as I saw on some examples?.

You need to configure tunnel for every class-type.
MPLS DiffServ Tunneling Modes has the following benefits:
â¢Tunneling modes provide added QoS functionality by the creative manipulation of the MPLS EXP field during label imposition, forwarding, and label disposition.
â¢Tunneling modes provide a common set of PHBs to different service provider customers.

MPLS QoS - SUP720BXL GE Port not supporting Strict Priority & Priority %

Hi Sir,
My customer have few C7609s with SUP720 3BXL and running IOS image s72033-advipservicesk9_wan-mz.122-18.SXF6.bin within the MPLS network.
What I experienced is that I can't configured the built-in GE port of the SUP720 for Strict Priority & Priority Percent QoS.
Is there anyone outside there know what is the equivalent or alternative to above mentioned two QoS features ? This is mainly to priortize the voice traffic.
Thanks in advance.
Ray.

The below has been recommended for a customer using 7600 in the
Core with GiGs as normal core facing links.
The implementation goes as below:
i) Enabling the MLS on the 7600 chassis.
mls qos
ii) Configuring Trust Boundary on all Interfaces.
interface GigabitEthernet1/1
mls qos trust
<--By default the Trust Command trusts the incoming DSCP/TOS.
When the ports are configured with the Trust Boundary as given above,
all incoming packets are mapped into Initial Internal DSCP values.
These values are used purely as a reference MAP for Internal QOS
processing on the 7600.
Internal DSCP Output COS
DSCP 0 7 COS 0
DSCP 8 15 COS 1
DSCP 16 23 COS 2
DSCP 24 31 COS 3
DSCP 32 39 COS 4
DSCP 40 47 COS 5
DSCP 48 55 COS 6
DSCP 56 63 COS 7
This deafault mapping can be modified by modifying the DSCP-COS MAP
within the MLS QOS. The the default mapping are as per standards,
and hence it is not recommended to change the mapping.
iii) Directing Traffic into the appropriate Egress Queue.
Once the incoming traffic is mapped to the Initial Internal DSCP,
and the same gets mapped to the Output COS, these values need to
be directed to the appropriate Queues for the desired QOS behavior
on the MPLS EXP packets.
interface x/x
wrr-queue cos-map
priority-queue cos-map
For Eg:
interface gigabitethernet 1/10
wrr-queue cos-map 2 threshold 2 0
wrr-queue cos-map 3 threshold 2 1 2
wrr-queue cos-map 4 threshold 2 3 4
priority-queue cos-map 1 5 6 7
iv) Defining Queue Bandwidth Limits.
After directing the COS to appropriate queues and then assigning them
to appropriate drop threshold values, it is required to define the
bandwidth allocation per queue. This can be done as below.
!<-- To Set minimum assured bandwidth to COS Queue 1,2 & 3
Use the Bandwdith Percentage command as below.
interface GigabitEthernet 1/1
wrr-queue bandwidth percent !
<--Total of Queue Weights should be =100%
To evenly distribute the available bandwidth during congestion for
all the 4 queues, it is required to set the Queue Scheduling Weights
between all the four Queues. This is done by assigning the queues
weights which are used during WRR scheduling.
!<--Set the Queue-Limit Weights of WRR Scheduling as below
interface GigabitEthernet 1/1
wrr-queue queue-limit
priority-queue queue-limit xx
!<--For Example:
interface GigabitEthernet 1/1
wrr-queue queue-limit 25 20 22
priority-queue queue-limit 33
!<-- The example above does a Queue scheduling for Queue 1 for 25% of BW,
Queue 2 for 20% and Queue 3 for 22 % and Priority Queue has 33 %.
To conclude if you want to use the conventional MQC based toggles,
you will need to use FlexWans with WAN ports or OSM's. Where you can
apply the conventional MQC based toggles.
FOr all the LAN ports in 7600 only hardware queues are supported which
can be controlled using MLS, the difference between SUP and Module based
LAN ports is withing the Scheduling alogirthms supported, the Egress and Ingress
buffers, and the number of queues and drop thresholds available.
For Reference use this link:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/software/122sr/swcg/qos.htm
HTH-Cheers,
Swaroop
PS:
Policy Map Class Command Restrictions
PFC QoS does not support these policy map class commands:
?bandwidth
?priority
?queue-limit
?random-detect
?set qos-group
?service-policy

MPLS QoS Priority

Hi everybody,
I've seen guys saying that ICMP has low priority on MPLS Domain and normaly i can lost some packet when I ping some router on mpls domain, but I'd like to know when it is true, because I did mpls course and I didnt see nothing about that. ICMP has low priority just when I pratice MPLS TE on my network or it is include on mpls's struture.

Hi Santos,
What you heard is partially true.
1) ICMP has low processing priority and also as you ISP said should not be used for troubleshooting. Now a days you have inbuilt Control Plane Policing where you can do police or completely drop ICMP packets which are not from known destinations. But again this behaviour has nothing to do with MPLS in specific. Its general.
Also you may like to go through this link for academic purpose.
http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_tech_note09186a00800a6057.shtml#performance
2) As far as MPLS domain goes, If you ISP hasnt done any ratelimiting or ICMP discard at the edge then the packets shouldnt be lost or discarded in the Domain. Because whatever happens happends at the edge. As the devices in the CORE dont know whether the CE packet is a ICMP or HTTP or any other application packet.
HTH-Cheers,
Swaroop

IOS support for MPLS QoS as stated in RFC 3270 L-LSP

Hi,
does anybody know something about the degree of implementation of RFC 3270 (Multi-Protocol Label Switching (MPLS) Support of Differentiated Services), particularly on the classification based on Labels (L-LSP)?
From what is detailed on the CCO it seems that only Exp-bits based LSP are supported (configuring all links along the path for the proper data plane behaviour based on the Exp-bits values): E-LSP
Thanx in advance
Francesco

I guess, in PPP and LAN environments, E-LSP is the preferred method and in the ATM only L-LSP is possible. Maybe cisco chose to implement only the E-LSP for the LAN and PPP environments, i am not sure though.
Anyone knows this for sure?
Check out http://www.cisco.com/warp/public/732/Tech/mpls/docs/mpls_qos_jayk.ppt for more details on MPLS-QoS

NBAR, Netflow, QoS Policing, 6500s, IOS 12.1(26)E7, and MARS

Hello. I'm having trouble seeing the forest OR the trees, and I'd appreciate some help from someone who has a better field view than myself. We're upgrading our internet connection to 200MB and management is wanting to upgrade our Packet Shaper to meet the new bandwidth. (The Packet Shaper shows top talkers, top protocols, and rate limits protocols or users.) I'm trying to make the argument that we can do this w/ existing tools (nbar, netflow, QoS policing, and MARS), at the same time I'm trying to make the argument that we need to have our supervisors (currently SUP2 MSFC2) on a 3-4 year upgrade cycle.
To get to the 12.2 IOS, I'd require a memory or sup upgrade. What I am hoping for is someone who has gone down this road who knows what I'm lacking in 12.1 code, or if in fact I can do it all here.
While it is self-evident to most in IT why we need to regularly upgrade equipment, I'm having difficulty making this argument to management with hard facts. I'm guessing they'd still be running Windows for Workgroups to save money...but that's another story.
My plan is to use Netflow and MARS to track top users and top protocols. It appears that I lose some mgt functionality w/ MARS in conjunction w/ IOS 12.1, but I am currently unclear if I lose any tracking capability. (MARS is new to us and awaiting install.)
Then, I hope to use NBAR to identify all the latest P2P traffic and police it appropriately w/ QoS tools.
Does my thinking sound solid? Will I be able to pull this off w/ 12.1? If not, what do I need that I lack in 12.1?
Thank you for your time,
Joshua

Hi,
First of all - you need to be clear that although MARS uses netflow data, it uses it for the purpose of identifying security issues. If you want to use netflow for reporting and/or accounting purposes MARS isn't the tool you need, try one of the following freeware netflow tools:
http://www.cisco.com/warp/public/732/Tech/nmp/netflow/partners/freeware/index.shtml
or one of the following commercial tools:
http://www.cisco.com/warp/public/732/Tech/nmp/netflow/partners/commercial/index.shtml
The freeware ones are generally more difficult to set up but once running are just as good as the commercial ones.
However, this means you need two netflow destinations - one for MARS and one for your netflow tool, and this feature is called "Netflow Multiple Export Destinations" and initially appeared at 12.1(3)T, but it seems to be VERY platform specific - for example, because we only run GD software on our 3660's we had to upgrade to 12.3(20) to get it.
Looking at the Feature Navigator for SUP2/MSFC2 it appears that you need at least 12.2(18)SXF6 to get this feature so that might help your case.
I'd personally keep the PacketShaper for it's reporting capability if nothing else (IOS can do the job, but not as elegantly as the PacketShaper).
HTH - plz rate if useful.
Andrew.

6500's or ASR's for MPLS

In our enterprise a project is driving more bandwidth usage and is making us consider deploy
of MPLS on proposed core gig e WAN links that would link South England and Scottish datacentres
We are considering upgrading existing North and South sited core 6500's to terminate these
new MPLS links. Or alternatively purchase new north and south ASR platforms as termination.
Are there any 6500-platform-specific MPLS dependencies/restrictions
to consider that would not be encountered if we used ASR's ??
thnks
martyn

existing 65's are 6509's with sup720-3B's but 'could' be upgraded if neeed. ASR model that could be used is to be decided.
Horsepower on the device to be used can be brought with money, which can be be got if necessary. What i'm after is a high level expert finger in the air compare on the MPLS implementations on 6500's and ASR's , to the aim of IF i deploy on multi purposes 65's might i have obscure issues pop up down the road, as opposed to a 'proper' ASR edge router MPLS
implementation.
thnks
rgds

URGENT: MPLS P/ PE support on 7600/Sup720-BXL and 3750 Metro switch

I'm need to design a MPLS network for a Cable Operator.
They will start small with some Cisco CMTS doing MPLS-PE and needing only two devices to aggregate these PE and delivering Services (Internet connection, VoD, ...) , so they will need to work has P/PE.
For that I want to know if it's possible to:
1 - Use 3750 Metro and 7600/Sup720-BXL as P and PE
2 - Who many customers (L2VPN/VLANs and/or L3VPN/VRF) can they support?
Searching in CCO I found these values/features but, need URGENT to check:
1 - sup720-bxl supports P and PE but 3750 only PE?
2 - 3750 supports 1024 VLANs and 8,192 MPLS labels but no values on L3VPN/VRF?
SUP720 supports more than 1000 VRF?
Really need urgent HELP on this design/capabilities for these two devices.
Thanks in advance,
MP
Network Consultant - CCIE

before you even get anywhere close to the numbers of L2/L3 on a 7200 I would seriously consider asking what throughput you can get through a 7200 with MPLS, QOS, L3vpns and L2vpns configured. I have done this testing already but dont think it is appropriate to quote the figures publically.

6500 xconnect and QinQ frames

Hi, I want to pass all vlanes from a client. I have a tunnel-port in both 3560 and then I have an mpls xconnect between 6500. The 6500's are connected with a pvc with encapsulation aal5snap. This is the schema:
3560 --Gb -- 6500 -- ATM PVC -- 6500 -- Gb 3560
The problem is that the xconnect does not carry QinQ frames, it only sends the frames from the client that are untagged.
How can I pass the QinQ frames between the 6500's?
Thanks

This is the current 6500 configuration, I have tried with the same result this configuration and other using subinterfaces. The xconnect works because I could see the untagged frame int both sites. The interface Gig1/9 from the 6500 is connected with the interface Fa0/1 from the 3560.
interface GigabitEthernet1/9
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
mtu 9216
no ip address
interface Vlan3003
description VLL_CLIENT1
no ip address
xconnect 10.0.0.3 3003 encapsulation mpls
show modules:
#sh mod
Mod Ports Card Type                              Model              Serial No.
1    9 Supervisor Engine 32 8GE (Active)      WS-SUP32-GE-3B     SAL12426MVE
2    0 4-subslot SPA Interface Processor-200 7600-SIP-200       JAE1244Z5PF
Mod MAC addresses                       Hw    Fw           Sw           Status
1 0021.d89e.c846 to 0021.d89e.c851   4.6   12.2(18r)SX2 12.2(18)SXF1 Ok
2 0021.a06d.fdc0 to 0021.a06d.fdff   2.303 12.2(18)SXF1 12.2(18)SXF1 Ok
Mod Sub-Module                  Model              Serial       Hw     Status
1 Policy Feature Card 3       WS-F6K-PFC3B       SAL12405HZN 2.4    Ok
1 Cat6k MSFC 2A daughterboard WS-F6K-MSFC2A      SAL12426HJD 4.0    Ok
2/0 2xOC3 ATM SPA               SPA-2XOC3-ATM      JAE1244Z6G2 1.1    Ok
Mod Online Diag Status
1 Pass
2 Pass
2/0 Not Applicable
The 3560 configuration is this:
interface FastEthernet0/1
description 6500_Uplink
switchport trunk encapsulation dot1q
switchport mode trunk
interface FastEthernet0/8
description CLIENT1
switchport access vlan 3003
switchport mode dot1q-tunnel
l2protocol-tunnel cdp
l2protocol-tunnel lldp
l2protocol-tunnel stp
l2protocol-tunnel vtp
no cdp enable
Thanks in advance

MPLS QoS on 6500

Similar Messages

Maybe you are looking for