Mls qos trust cos vs mls qos cos in cat6k

Hello
I am trying to configure basic qos topology with two 6k connected to each other by the trunk port.
According to the documentation, if I set the mls qos cos value at the interface level I should modify the default cos on it, and all packets leaving incoming to this port, should be marked with the new cos value.
http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6000-series-switches/24055-173.html
Unfortunately, when I set such config, all incoming packets transmitted through this interface was tagged with cos = 0 until I set the "mls qos trust cos" on the same interface.
Does anybody can explain to me this strange behavior?
I would like to mention that both 6k was connected to each other with ws-x6548-GE-TX modules.
Thank you in advance.
Ragards
Lukas

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

Similar Messages

  • "mls qos trust dscp" vs. "mls qos trust cos"

    Are these statements correct ?
    1. If using QoS profile without setting "wired qos protocol", always use "mls qos trust dscp" on the WLC trunk port
    - downstream wmm traffic will be policed down to "?" (this one I'm not sure, is it "not policed" or "policed down to cos 6 for platinum, etc")
    2. If using QoS profile with setting "wired qos protocol",
    - use "mls qos trust cos" on the WLC trunk port if you want outgoing LWAPP traffic COS/DSCP to reflect QoS profile setting and if you want to rewrite DSCP in the outgoing upstream traffic to QoS profile setting
    - use "mls qos trust dscp" on the WLC trunk port if you want LWAPP traffic COS/DSCP to reflect original DSCP setting and if you want to leave DSCP alone in the outgoing upstream traffic
    3. With either "mls qos trust cos" or "mls qos trust dscp" on WLC trunk port, downstream wmm traffic will be policed down to "wired qos protocol" setting (What if "wired qos protocol" is not set, will it be policed down to, for example, cos 6 for Platinum?)
    4. Always use "mls qos trust dscp" on non-HREAP AP ports
    Use "mls qos trust dscp" on HREAP AP ports, if you want to preserve upstream DSCP for locally switched WLANs
    Use "mls qos trust cos" on HREAP AP ports, if you want to QoS profile 802.1p to override upstream DSCP for locally switched WLANs
    5. Use either "mls qos trust dscp" or "mls qos trust cos" on switch-to-switch trunks

    Are these statements correct ?
    1. If using QoS profile without setting "wired qos protocol", always use "mls qos trust dscp" on the WLC trunk port
      - downstream wmm traffic will be policed down to "?" (this one I'm not sure, is it "not policed" or "policed down to cos 6 for platinum, etc")
    Ans: Not sure about always. you can use both 'mls qos trust dscp' and 'mls qos trust cos'. Since it is a trunk port the packets will have a cos value (802.1p tag) and hence you can trust cos. Downstream and upstream traffic both are capped to the WLAN max QoS value. for example if Wlan is set to silver, and if a packet comes in at platinum QoS, the AP will cap it to silver in upstream direction. Same holds true for a cos 5 / dscp 46 packet coming in from the wired side.
    2. If using QoS profile with setting "wired qos protocol",
      - use "mls qos trust cos" on the WLC trunk port if you want outgoing LWAPP traffic COS/DSCP to reflect QoS profile setting and if you want to rewrite DSCP in the outgoing upstream traffic to QoS profile setting
      - use "mls qos trust dscp" on the WLC trunk port if you want LWAPP traffic COS/DSCP to reflect original DSCP setting and if you want to leave DSCP alone in the outgoing upstream traffic
    Ans:
    3. With either "mls qos trust cos" or "mls qos trust dscp" on WLC trunk port, downstream wmm traffic will be policed down to "wired qos protocol" setting (What if "wired qos protocol" is not set, will it be policed down to, for example, cos 6 for Platinum?)
    Ans: Traffic in both direction wil always get capped to WLAN max QoS. Untagged (802.1p = 0) traffic will be treated as best effort.
    4. Always use "mls qos trust dscp" on non-HREAP AP ports
       Use "mls qos trust dscp" on HREAP AP ports, if you want to preserve upstream DSCP for locally switched WLANs
       Use "mls qos trust cos" on HREAP AP ports, if you want to QoS profile 802.1p to override upstream DSCP for locally switched WLANs
    Ans:
    5. Use either "mls qos trust dscp" or "mls qos trust cos" on switch-to-switch trunks
    Ans: I think on purely layer 2 switches you can trust dscp, but am not 100% sure.

  • Mls qos trust{cos/ip-precedence/dscp} command

    Hi every body!
    I have few questions
    1)
    The command " mls qos trust dscp" is only valid on mulilayer switch or it is also valid for layer 2 switch? If layer 2 switch is configured with that command, can it modify the dcsp value based on policy?
    2)is the following correct:
    switch(config-if) mls qos trust dscp
    switch will set the cos value to set default. If the default set is zero, then frame will be processed by best-effort delivery.
    But the egress-queue will be decided by dscp value in the packet. A dscp to cos map will be used to drive the cos value and then frame will be placed in the queue that corresponds to cos value.( off course if egress port is configured for trunk)
    thanks a lot and I wish America and all of you a happy new year!
    thanks a lot!

    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

  • Cisco 3560 switch| mls qos trust dscp question

    Hi everybody
    Hi everybody .
    Please consider the following example:
    3560 sw f1/1--------trunk---SW2
    3560 sw
    f1/1
    mls qos trust dscp
    3560 is using default cos-dscp map, assume a 3560 receives a frame carrying IP packet on f1/1 with COS 4, what will 3560 switch do?
    1) will it use its default cos --dscp map  ( cos 4--.dscp 32) and rewrite 32 in dscp field  of the packet in the frame and provide PHB for dscp 32 ?
    Much appreciated!!
    Have  a great weekend.

    Hi
    No it will not trust the cos value, because You have configured to trust dcsp. So, the switch will trust the dcsp value in the incoming frame.
    /Mikael

  • Mls qos VS mls qos trust

    Hello world!
    I want to enable qos on a 3560 switch,
    So, I put:
    Overall setup mode "mls qos"
    Question:
    is what it is Verily nessaiire to interface configuration mode: "mls qos trust"?
    Regards,

    Disclaimer
    The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
    Liability Disclaimer
    In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
    Posting
    Generally, on many Catalyst switches, once you enable QoS, they will erase an ingress CoS/ToS markings unless your trust it or otherwise (i.e. policy) maintain it.
    I.e. the answer to your question is an "it depends"; but unless you want the markings reset to zero, the answer is probably yes (you want to trust).

  • Mls qos trust

    Hello, if the command 'mls qos trust xxxxx' is not issued, and qos is turned on for the interface, does this mean the switch will erase all cos and dscp markings received, therefore preventing me from testing packets/frames against these cos/dscp values ?
    So if I want to set up class maps, policy maps, and then service policies, it is essential that I:
    1. turn on mls qos ?
    2. enter a trust statement in order to preserve the cos or dscp values that I want to test against ?
    3. now I can test against against cos or dscp values ?
    Thanks for clarification.

    That is correct, when you would use for instance mls qos trust cos. You would need to define you cos<>dscp mappings on the switch and the switch will apply qos accordingly.
    So really if you have an ingress switch port and you trust cos or dscp, you can still have egress policies on a port (on the same switch), using these cos or dscp values.
    the mls qos trus command is just a way to make it easier to rely on existing cos/dscp values that a phone sends (based on your CUCM configuration,), without the need for you having to configure it explicitly on each access port.
    =============================
    Please remember to rate useful posts, by clicking on the stars below. 
    =============================

  • Qos trust cos or qos trust dscp?

    My core switches are a pair Cisco catalyst 4006s with a sup 4 module. The questions are:
    1. Should I use qos trust cos or qos trust dscp when setting up qos on a per port basis?
    2. Which is preferred?
    3. I have a cos to dscp mapping so does it really matter?
    Any help is greatly appreciated. I just want to make sure that I'm honoring all tags.
    Mark

    If you have ip phones connected to the switch, you can enter qos trust cos on the switch and in the router which is connected to the switch enter the command to trust the DSCP since the switch will pass the dscp information to teh router.
    http://www.cisco.com/en/US/docs/ios/qos/command/reference/qos_m2.html#wp1015945

  • Why does mls qos trust dscp dissapear after reboot?

    The command takes but after reboot, Invlaid inputs detected show up and "mls qos tust dscp" is gone from every interface.
    Happens on both 2960-24PC-S / 2960-48PST-S switches.

    Hi,
    thanks for your reply.
    mls qos
    interface GigabitEthernet3/34
    description *** DATA VLAN 35 - VOICE VLAN 34 ***
    switchport
    switchport trunk native vlan 36
    switchport trunk allowed vlan 34,36
    switchport mode trunk
    mls qos trust dscp
    no cdp enable
    spanning-tree portfast trunk
    If i don't include the global 'mls qos' command then the voice packets keep the dscp 46 value.  If I add the mls qos command this causes the switch to set the dscp values to zero.
    Thanks again 
    ps.  there are some other mls commands on the switch... i don't know if these could interfere but they were already on there so i'm reluctant to remove them..

  • Mls qos trust dscp??? is setting my DSCP values to zero!?

    Hi,
    I was just doing some testing to ensure that the command 'mls qos trust dscp' is working on my 6509 switches before rolling out QoS.
    Before adding any configuration I could see using wireshark that traffic from my Avaya 9608 handset was coming through with a DSCP value of 46 (as it is supposed to).
    I then added the command 'mls qos' (at global level)
    on examining the wireshark output this time, the DSCP value had been set to zero (i.e. it defaulted it to best effort)
    I then expected by adding the commmand 'mls qos trust dscp' on the interface the phone is connected to that the DSCP value would would again be left alone?
    does anybody know why this is happening?
    Many thanks in advance.
    Andy

    Hi,
    thanks for your reply.
    mls qos
    interface GigabitEthernet3/34
    description *** DATA VLAN 35 - VOICE VLAN 34 ***
    switchport
    switchport trunk native vlan 36
    switchport trunk allowed vlan 34,36
    switchport mode trunk
    mls qos trust dscp
    no cdp enable
    spanning-tree portfast trunk
    If i don't include the global 'mls qos' command then the voice packets keep the dscp 46 value.  If I add the mls qos command this causes the switch to set the dscp values to zero.
    Thanks again 
    ps.  there are some other mls commands on the switch... i don't know if these could interfere but they were already on there so i'm reluctant to remove them..

  • QoS trust dscp or cos on catalyst 4500

    We have a 4510R with Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software cat4500e-UNIVERSALK9-M), Version 03.05.02.E RELEASE SOFTWARE (fc1).
    I want use qos trust dscp or qos trust cos on the interface conected to other cisco switch or wlan controller.
    The current IOS version, do not support qos trust dscp:
    SW(config)#interface gi10/16
    SW(config-if)#qos tr
    SW(config-if)#qos trust ?
      device  trusted device class
      extend  Extend trust through a connected device
    SW(config-if)#qos trust device ?
      cisco-phone   Cisco IP Phone
      cts           Cisco-telepresence
      ip-camera     Cisco video surveillance camera
      media-player  Cisco Digital Media Player
    SW(config-if)#qos trust device
    What is the software that I need for this?. I tried with command lookup tool but the cat4500 do not appears.

    That is even new for me.
    I did a search and found that, now a days you no longer have to provide the Trust DSCP command, it is by default trusted.
    Went through this White Paper and excerpts are below:
    http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-4500-series-switches/white_paper_c11-539588.html
    The answer to your question comes from the following excerpt :-
    "Previously supervisor engines relied on “port trust” to classify traffic; however, this does not fall into the MQC CLI construct. MQC provides a more flexible capability, i.e. all traffic is trusted by default, an administrator can change this trust state using a policy map. Another difference is the “internal DSCP” value used within the switch to place packets in the proper queue.
    Cisco Catalyst 4500E Supervisor Engines do not use “internal DSCP”; rather, it relies on explicit matching of QoS values using class maps so that packets can be placed in the correct queue.
    Also, note that there is no specific priority queue: it is not queue 3 or queue 1. The priority queue is simply configured within a class; therefore, it is not tied to a specific queue. One final difference is that of classification. Cisco Catalyst 4500E Supervisor Engines provide sequential classification rather than parallel. This allows the network administrator to classify traffic at egress based on the ingress markings. These markings can be done unconditionally, using a policer or using a table map. Based on these changes, QoS CLI will now be more contiguous on the Supervisor Engines as it will now have standard Cisco MQC CLI, making configuration management much simpler"
    HTH,
    Please rate all helpful posts.
    Regards

  • Problem on the QoS trust boundary on FEX

    HI: all
         During a test, we found the N5K attached FEX will override all the DSCP marking to 0  for the class-default traffic. Based on my understanding, the N5K will enable the qos trust on all access port by defual. But how about I configure a policy-map on the interface for DSCP marking, and want to leave the unclassified traffic as the original DSCP tag, is that possible?
        Thanks!
    BR
    LIBING

    Hi There,
    Take a look at the QoS config guide, it has some of the answers you are after.
    You should refer to the guide relevant to your OS version.
    http://www.cisco.com/en/US/partner/docs/switches/datacenter/nexus5500/sw/qos/602_N1_1/b_5500_QoS_Config_602N11_chapter_0110.html
    Any incoming packet not tagged with an 802.1p CoS value is assigned the default untagged CoS value of zero (which maps to the default Ethernet drop system class). You can override the default untagged CoS value for an Ethernet or EtherChannel interface.
    On a Cisco Nexus device, you can configure a type qos policy map and untagged CoS on the same interface.
    Trust Boundaries
    The trust boundary is enforced by the incoming interface as follows:
    All Fibre Channel and virtual Fibre Channel interfaces are automatically classified into the FCoE system class.
    By default, all Ethernet interfaces are trusted interfaces.The 802.1p CoS and DSCP are preserved unless the marking is configured. There is no default CoS to queue and DSCP to queue mapping. You can define and apply a policy to create these mappings. By default, without a user defined policy, all traffic is assigned to the default queue.
    Any packet that is not tagged with an 802.1p CoS value is classified into the default drop system class. If the untagged packet is sent over a trunk, it is tagged with the default untagged CoS value, which is zero.
    You can override the default untagged CoS value for an Ethernet interface or port channel.
    You can override the default untagged CoS value for an Ethernet interface or a port channel interface using the untagged cos cos-value command.
    You can override the default untagged Cos value for an Ethernet or a Layer 3 interface or a port channel interface using the untagged cos cos-value command.
    After the system applies the untagged CoS value, QoS functions the same as for a packet that entered the system tagged with the CoS value.
    Hope that helps.

  • QoS Trust

    Hi,
    I just want to confirm the best practice with CUCM and LAN QoS. I have a CUCM 10.5 cluster attached to a 4948 edge. CUCM is marking all signalling traffic with the appropriate DSCP markings. Therefore I assume all that is required on the LAN is to trust the QoS/DSCP markings?
    An example edge port with AutoQoS to a CUCM Subscriber:
    *The key command being  'auto qos voip trust'
    *This switch port is connected to a UCS C-Series
    SWITCH#sh run int Gig 1/47
    Building configuration...
    Current configuration : 285 bytes
    interface GigabitEthernet1/47
    description CUCM_SUB
    switchport trunk encapsulation dot1q
    switchport mode trunk
    media-type rj45
    qos trust cos
    auto qos voip trust
    tx-queue 3
    bandwidth percent 33
    priority high
    shape percent 33
    service-policy output autoqos-voip-policy
    end
    All uplinks in the LAN also have the same ' auto qos voip trust' command set. So we should have 'end to end' QoS in the LAN?
    Edge ports to IP Phones are set as 'auto qos voip cisco-phone'.
    Thanks!
    Dean

    Thanks you for your response.
    Yes you’re right there, but the problem is that if an incoming packed has a dscp value 0 (not marked) than it should be remarked and only then. Therefore I need the trust dscp command as shown in the IOS CLI configuration segment I posted, otherwise the incoming packed is remarked no matter what dscp value it has. I didn’t find another way yet to solve this without the trust dscp command.

  • 'qos trust extend' command on 4500E causes Alcatel phones to reboot

    Hi, We have autoqos configured on our 3560G access layer switches, when entering the 'qos trust extend' command on the 4500 interfaces which connect to the access layer switches this caused out Alcatel Phones to reboot.
    I thought that this command just trusts the DSCP/CoS markings but obviously there is something else going on.
    Any advice would be appreciated.
    Thanks,
    Paul

    Hello.
    I doubt if "auto qos voip trust" would suit you on inter-switch links, as per documentation the command applies policy-map that gives only 320K for voice and signalling traffic (+ remarking exceeded traffic to BE).
    If you want to protect your video traffic in the future, you will have to design new QoS policy and apply it per link.
    Regarding "trust dscp" toward WLC/AP - if you configure this, all your laptops will be able to inject marked traffic into your network, abusing your QoS policy; that is why the best practice for VoIP phones is to be placed into dedicated voice VLAN + trust cos (not dscp).
    PS: I would suggest you to try the command[s] on one switch and see what configuration will be applied per port (+global).

  • Any one ever worked on 6500 series Cisco switches QOS or 6503 or 6524 QOS(Urgent help needed)

    Hi All,
    I am having issue specifally doing QOS configuration on 6503 or 6524 or 6509 switches. I am unable to match any EF(voice) traffic for eompls(vlan based) on 6503 cisco switch. If i use any other router as 2811 or 2821 my QOS configuration works perfect but if i put 6503 as PE2 it does not work.i am using vlan based eompls.
    Below is the scenario & configuration which i am having issue.
    CE1(2821 router)(dot1Q)--------->PE1(2821 router)------->P(6524 switch)-------->PE2(6503 switch)------->(dot1Q)(2821 switch)CE2.
    On CE1 i can match ip-precedence 5 traffic and mark that traffic to cos5 on outbound port.On PE1 i can match cos5 packet and mark with mpls exp top5 on inbound port, on outbound port i can match mpls exp 5. 
    On PE2(6503) i am unable to match that mpls exp5 packet on inbound port. none of the configuration worked on 6500 series switches with mls qos, ,mls qos trust dscp,mls qos trust cos etc. Although i can match cos5 traffic on CE2 on inbound interface.i can not match mpls exp 5 traffic on 6503 and all i can see traffic as default-class on 6503 switch. I tried many things and many configurations on 6503 but nothing worked.If i put 2821 router as PE2 instead of 6503 my qos configuration works. but why if i put 6503 my same qos configuration does not work? 
    ---match means=classification or classify
    Can anyone tell me how qos works on 6500 series switches or where i am having issue in my scenario.
    i am using this ios on 6503: s72033-advipservicesk9_wan-mz.122-33.SXI3.bin.
    below r my questions for 6503 qos:
    1.do i need to use some other map tables,am i  using correct map tables on 6503 as cos-dscp,dscp-cos,exp-dscp etc.
    2.any other configutaion of qos needed on 6503?
    3.i am unable to match anything on outbound port of 6503.
    4.on 6503 i am using sup720 and PFC3BXL.any specific configuration needed for PFC3bxl.
    5. 6503 not allowing me to match qos-group on inbound interface, not allowing me to set cos5 on outbound interface. not allowing me to set cos5 as an inbound interface.
    CE1(2821) config:
    class-map match-any EF
     match ip precedence 5
    class-map match-any data
     match ip precedence 3
    policy-map ip2mpls
     class EF
      set cos 5
     class data
      set cos 3
    interface FastEthernet0/0
     no ip address
     duplex auto
     speed auto
    interface FastEthernet0/0.455
     encapsulation dot1Q 455
     ip address 172.16.15.1 255.255.255.252
     service-policy output EF
    PE1(2821) config:
    mls qos map cos-dscp 0 8 16 24 32 40 48 56
    class-map match-all exp_3
     match mpls experimental topmost 3
    class-map match-all mpls_exp
     match mpls experimental topmost 5
    class-map match-any cos3
     match cos  3
    class-map match-any LOO1
     match cos  5
    policy-map EF
     class LOO1
      set mpls experimental imposition 5
     class cos3
      set mpls experimental imposition 3
    policy-map QOS_G_5
     class mpls_exp
      priority
     class exp_3
      bandwidth 500
    interface Loopback0
     ip address 3.3.3.3 255.255.255.255
    interface FastEthernet0/0
     ip address 192.168.23.2 255.255.255.0
     ip ospf network point-to-point
     duplex auto
     speed auto
     mpls ip
     service-policy output QOS_G_5
    interface FastEthernet0/1.455
     encapsulation dot1Q 455
     xconnect 5.5.5.5 455 encapsulation mpls
     service-policy input EF
    PE2(6503 qos):
    R1#show module
    Mod Ports Card Type                              Model              Serial No.
      1    4  CEF720 4 port 10-Gigabit Ethernet      WS-X6704-10GE      SAL09401U2L
      2   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     SAL114247YN
      3   16  16 port 1000mb GBIC ethernet           WS-X6416-GBIC      SAL0712AM69
      4   24  CEF720 24 port 1000mb SFP              WS-X6724-SFP       SAL10019J4N
      5    2  Supervisor Engine 720 (Hot)            WS-SUP720-3BXL     SAD102805VM
      6    2  Supervisor Engine 720 (Active)         WS-SUP720-BASE     SAD0846060F
    Mod  Sub-Module                  Model              Serial       Hw     Status
      1  Distributed Forwarding Card WS-F6700-DFC3BXL   SAD102504EF  5.3    Ok
      2  Centralized Forwarding Card WS-F6700-CFC       SAD111300PD  3.1    Ok
      4  Centralized Forwarding Card WS-F6700-CFC       SAL1004BQ2A  2.0    Ok
      5  Policy Feature Card 3       WS-F6K-PFC3BXL     SAD10270189  1.8    Ok
      5  MSFC3 Daughterboard         WS-SUP720          SAD102801G5  2.5    Ok
      6  Policy Feature Card 3       WS-F6K-PFC3BXL     SAL1415FE95  1.11   Ok
      6  MSFC3 Daughterboard         WS-SUP720          SAD08440794  2.4    Ok
    R1#show mls qos maps
       Normal Burst Policed-dscp map:                                  (dscp= d1d2)
         d1 :  d2 0  1  2  3  4  5  6  7  8  9
          0 :    01 01 02 03 04 05 06 07 08 09
          1 :    10 11 12 13 14 15 16 17 18 19
          2 :    20 21 22 23 24 25 26 27 28 29
          3 :    30 31 32 33 34 35 36 37 38 39
          4 :    40 41 42 43 44 45 01 47 48 49
          5 :    50 51 52 53 54 55 56 57 58 59
          6 :    60 61 62 63
       Maximum Burst Policed-dscp map:                                  (dscp= d1d2)
         d1 :  d2 0  1  2  3  4  5  6  7  8  9
          0 :    00 01 02 03 04 05 06 07 08 09
          1 :    10 11 12 13 14 15 16 17 18 19
          2 :    20 21 22 23 24 25 26 27 28 29
          3 :    30 31 32 33 34 35 36 37 38 39
          4 :    40 41 42 43 44 45 46 47 48 49
          5 :    50 51 52 53 54 55 56 57 58 59
          6 :    60 61 62 63
       Dscp-cos map:                                  (dscp= d1d2)
         d1 :  d2 0  1  2  3  4  5  6  7  8  9
          0 :    00 00 00 00 00 00 00 00 01 01
          1 :    01 01 01 01 01 01 02 02 02 02
          2 :    02 02 02 02 03 03 03 03 03 03
          3 :    03 03 04 04 04 04 04 04 04 04
          4 :    05 05 05 05 05 05 05 05 06 06
          5 :    06 06 06 06 06 06 07 07 07 07
          6 :    07 07 07 07
       Dscp-exp map:                                  (dscp= d1d2)
         d1 :  d2 0  1  2  3  4  5  6  7  8  9
          0 :    00 00 00 00 00 00 00 00 01 01
          1 :    01 01 01 01 01 01 02 02 02 02
          2 :    02 02 02 02 03 03 03 03 03 03
          3 :    03 03 04 04 04 04 04 04 04 04
          4 :    05 05 05 05 05 05 05 05 06 06
          5 :    06 06 06 06 06 06 07 07 07 07
          6 :    07 07 07 07
    Cos-dscp map:
             cos:   0  1  2  3  4  5  6  7
            dscp:   0 10 18 24 34 46 48 56
       IpPrecedence-dscp map:
          ipprec:   0  1  2  3  4  5  6  7
            dscp:   0  8 16 24 32 40 48 56
       Exp-dscp map:
             exp:   0  1  2  3  4  5  6  7
            dscp:   0  8 16 24 32 40 48 56
    mls netflow interface
    mls qos map cos-dscp 0 10 18 24 34 46 48 56
    mls qos
    class-map match-all exp_3
     match mpls experimental topmost 3
    class-map match-all EXP_5
     match mpls experimental topmost 5
    class-map match-all QOS_GROUP_5
     match qos-group 5
    class-map match-all prec5
     match ip precedence 5
    class-map match-all cos5
     match cos  5
    policy-map mpls2ip
    class QOS_GROUP_5
     set cos 5
    policy-map IN_FROM_R3
     class EXP_5
      set qos-group 5
    interface Loopback0
     ip address 5.5.5.5 255.255.255.255
    interface GigabitEthernet2/2
     mls qos trust cos 
    or <------------ (tried both individually but none worked)
     mls qos trust dscp
    interface GigabitEthernet2/2.455
     encapsulation dot1Q 455
     xconnect 3.3.3.3 455 encapsulation mpls
     service-policy output mpls2ip
    interface GigabitEthernet2/1
     ip address 192.168.34.4 255.255.255.0
     ip ospf network point-to-point
     mls qos trust cos 
    or <------------ (tried both individually but none worked)
     mls qos trust dscp
     mpls ip
     service-policy input IN_FROM_R4
    Thanks & regards,
    Ahsan Rasheed

    Hi All,.
    I am still having issue on 6503 or 6524 Cisco Switch. 
    " Can any one give me any sample of 6524 or 6503 QOS working configuration, i would be really thankful "
    As i have mentioned in my prevoius post of configuration of 6503. I am unable to match mpls exp 5 packet on 6503. My qos configuration on PE1(2811 router) is working perfectly. I am unable to classify mpls ex5 or mpls exp3 on 6503 switch. Am i missing something on configuration?
    PE2 config:"6503 switch"
    class-map match-all mpls_exp
     match mpls experimental topmost 5
    policy-map EF
    class mpls_exp
    R!#mls qos
    int Gi2/4
    service-policy input EF
    mls qos trust cos
        dscp:   0 10 18 24 34 46 48 56
       Exp-dscp map:
             exp:   0  1  2  3  4  5  6  7
            dscp:   0 10 18 24 34 46 48 56
    Thanks,
    Ahsan Rasheed

  • 802.1p on 3750 ingress COS tag vs Egress COS tag

    Greetings,
    Hopefully someone will have some insight in to this.
    I have a 3750 configured for switchports to trust the cos value recieved from the device it is connected to. When I run Ethereal, I am seeing the COS tags with a correct value that was assigned. What I am NOT seeing is egress traffic on the port retain or assign any value. What am I missing?? The switchport config is below.
    interface GigabitEthernet1/0/3
    switchport voice vlan dot1p
    duplex full
    mls qos trust cos
    spanning-tree portfast
    ip igmp max-groups 130

    Thank you for the reply.
    Currently I believe the source and destinations are within the same switch so no trunkports should be doing the COS rewrites. I have thought about the default DSCP-COS maps possibly rewriting the values but as you see in the QOS config (which is very basic) that should not be happening.
    Here are the global QOS config.
    mls qos
    no mls qos rewrite ip dscp
    Tonight I will be verifying that the VLAN ID assignment form the server matches the voice VLAN ID. Also I am going to ask my co-worker (server guy) to let the vlan assignments and COS tags come from the switch as opposed to the server.
    I look forward to more input!
    Thanks!
    RA

Maybe you are looking for