Nexus 5500 qos drop priority

Hi
If I have two COS values within the same queue on a 5500 port can I set drop priority for them ? I am looking at setting in contract and out of contract data rates for some VMs, setting the COS value dependant on this and then getting the 5K to be more likely to drop out of contact data.
Its whjat I would do on a 6k or 7k with assigning different tail drop thresholds to different COS values in the same queue.

Thats what I kind of figured after reading all the docs. Makes it a bit of a pain as there really arent quite enough queues for what I want to do.
Viideo & Voice
Call SIgnnaling
Critical Data
Network Ctrl (ssh, VMware vmotion and ctrl etc)
Bulk Data
Best Efforts
Thats six and since we are using FCoE tehre are only 5 qos groups we can use ......
I am going to have to combine two of the above.

Similar Messages

  • Mix of Nexus 5500 & Catalyst 6500

    Hi there,
    Does Nexus 5500 series require a Nexus 7000 parent device? or it will be supported with Catalyst 6509?
    If this is the scenario :
    CAT6509 - Core Layer 3
    CAT6509 - Distribution Layer 2/3
    NX-5548 - Access Layer 2
    And FYI, no VSS on Catalyst 6509.
    Thanks in advance,
    Gerard

    Hello Chad,
    Cool thanks ... that is perfect. We're eventually moving towards NX at the Core and Distribs really soon. Yeah, that's what I've known with the Extenders requirement with parent 5k or 7k too ... 
    Gerard

  • Nexus 5500 duplicate ICMP echo-replay

    I am experiencing inconsistent echo-replay from devices connected via VPC to Nexus 5500s while pinging from the Nexus exec prompt.
    In some cases I receive normal response when pinging from one Nexus,  but no response when pinging from the other switch. In other instance I receive normal response to one Nexus, and duplicate replays to the other. It looks like a VPC related bug. NXOS is 5.1.3.N2.1
    5501# ping 10.12.12.232
    PING 10.12.12.232 (10.12.12.232): 56 data bytes
    64 bytes from 10.12.12.232: icmp_seq=0 ttl=253 time=8.585 ms
    64 bytes from 10.12.12.232: icmp_seq=0 ttl=254 time=9.227 ms (DUP!)
    64 bytes from 10.12.12.232: icmp_seq=1 ttl=253 time=1.011 ms
    64 bytes from 10.12.12.232: icmp_seq=2 ttl=253 time=8.097 ms
    64 bytes from 10.12.12.232: icmp_seq=2 ttl=254 time=9.429 ms (DUP!)
    64 bytes from 10.12.12.232: icmp_seq=3 ttl=253 time=18.195 ms
    64 bytes from 10.12.12.232: icmp_seq=4 ttl=253 time=8.807 ms
    5502# ping 10.12.12.232
    PING 10.12.12.232 (10.12.12.232): 56 data bytes
    64 bytes from 10.12.12.232: icmp_seq=0 ttl=254 time=0.985 ms
    64 bytes from 10.12.12.232: icmp_seq=1 ttl=254 time=0.884 ms
    64 bytes from 10.12.12.232: icmp_seq=2 ttl=254 time=0.875 ms
    64 bytes from 10.12.12.232: icmp_seq=3 ttl=254 time=3.105 ms
    64 bytes from 10.12.12.232: icmp_seq=4 ttl=254 time=8.378 ms
    Thanks
    Jarek

    Hi
    I found this in the configuration guide for the Nexus 7000 configuring VPCs
    "When you enable this feature (peer-gateway), Cisco NX-OS automatically disables IP redirects on all interface VLANs mapped over a vPC VLAN to avoid generation of IP redirect messages for packets switched through the peer gateway router."
    However this is not happening automatically on the 5K, so you need to manually add "no ip redirects" on each VPC vlan interface to prevent duplicate pings.

  • Connecting the nexus 5500 with multiple vsans

    Hi,
    it's my first experience in the fibre channel world and i have a few doubts about the best way to connect the nexus 5500 to a EMC storage.
    This is my scenario
    this is my configuration:
    vsan database
    vsan 2
    vsan 2 interface fc 1/1
    vsan 3
    vsan 3 interface fc 1/2
    interface fc1/1
    switchport mode f
    no shut
    interface fc1/2
    switchport mode f
    no shut
    now I don't know how can I connect the port fc1/3 to the vnx storage, I think I can't make a trunk like ethernet, can anyone help me?
    Or i only can do this with zoning
    Thanks
    Fred

    Hello Fred,
    All interfaces must be in the same vsan for them to see each other
    vsan database
    vsan 2 interface fc1/1, fc1/2, fc1/3
    exit
    Then you can zone each separately
    example:
    zone name host1 vsan 2
    member pwwn 11:11:11:11:11:11:11:11    (host1 pwwn)
    member pwwn 33:33:33:33:33:33:33:33    (VNX)
    zone name host2 vsan 2
    member pwwn 22:22:22:22:22:22:22:22    (host2 pwwn)
    member pwwn 33:33:33:33:33:33:33:33    (VNX)
    zoneset name Zoneset1 vsan 2
    mem host1
    mem host2
    zoneset activate name Zoneset1 vsan 2
    Thanks

  • Uplink-ID 0 in Nexus 5500 with FEX 2248.

    Hi all,
    I've got 2 Nexus 5548 and a fex 2248 connected to both of them via a vPC. 1 Uplink port goes to N5K-01 e1/10 and a second Uplink port goes to N5K-02 to port e1/10.
    On the log of the first Nexus 5500 I see this:
    N5K-01 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 103 that is connected with Ethernet1/10 changed its status from Configured to Fabric Up
    N5K-01 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 1 of Fex 103 that is connected with Ethernet1/10 changed its status from Fabric Up to Connecting
    N5K-01 1 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 1 of Fex 103 that is connected with Ethernet1/10 changed its status from Connecting to Active
    On the log of the second nexus 5500, I see this:
    N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 0 of Fex 103 that is connected with Ethernet1/10 changed its status from Configured to Fabric Up
    N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 2 of Fex 103 that is connected with Ethernet1/10 changed its status from Fabric Up to Connecting
    N5K-02 %FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID 2 of Fex 103 that is connected with Ethernet1/10 changed its status from Connecting to Active
    What is the difference between Uplink-ID 0, 1 and 2? If I only have 2 uplink ports, why is there a third one?
    Thanks in advace for your assistance.

    Hi Sonu,
    I see the similar problem on my nexus5ks. show cfs peer does not display the peer information. I have been waiting for hours now.
    sw01# sh cfs peerCFS Discovery is in Progress ..Please waitCould not get response. The network topology may be under going change.Please try after about 30 seconds
    Did you find the fix7workaround of this problem ?
    Regards,
    Umair

  • Cannot InterVlan on Cisco Nexus 5500

    Dear All,
    I have problem with my nexus 5500,
    Intervlan on my nexus not work,
    i dont know why..
    Before i have only this kind of license:
    Feature                      Ins  Lic   Status Expiry Date Comments
                                     Count
    FCOE_NPV_PKG                  No    -   Unused             -
    FM_SERVER_PKG                 No    -   Unused             -
    ENTERPRISE_PKG                Yes   -   Unused Never       -
    FC_FEATURES_PKG               Yes   -   Unused Never       -
    VMFEX_FEATURE_PKG             Yes   -   Unused Never       -
    ENHANCED_LAYER2_PKG           No    -   Unused             -
    LAN_BASE_SERVICES_PKG         No    -   Unused        -
    LAN_ENTERPRISE_SERVICES_PKG   No    -   Unused             -
    and feature i used is :
    - feature privilege
    - feature telnet
    - feature interface-vlan
    - feature hsrp
    - feature dhcp
    - feature lldp
    I make few vlan on nexus and then i check the interface status and the result is all vlan Interface is UP but intervlan is not work.
    And then, i install license for LAN_BASE_SERVICES_PKG, this is result for install licensed:
    Feature                      Ins  Lic   Status Expiry Date Comments
                                     Count
    FCOE_NPV_PKG                  No    -   Unused             -
    FM_SERVER_PKG                 No    -   Unused             -
    ENTERPRISE_PKG                Yes   -   Unused Never       -
    FC_FEATURES_PKG               Yes   -   Unused Never       -
    VMFEX_FEATURE_PKG             Yes   -   Unused Never       -
    ENHANCED_LAYER2_PKG           No    -   Unused             -
    LAN_BASE_SERVICES_PKG         Yes   -   In use Never       -
    LAN_ENTERPRISE_SERVICES_PKG   No    -   Unused             -
    I used vlan configuration vlan before, but the interface VLAN is DOWN/DOWN.
    and then i read this article:
    http://www.layerzero.nl/blog/2012/10/nexus-5000-non-routable-vdc-mode/
    Yes, thats solution work for 1 Vlan with "management" command on interface VLAN.
    But, the other vlan is still DOWN. and Intervlan is not work to.
    Anyone, can help me please?
    I have experience configure Nexus 5000 with VPC, FEX, Storage, etc, and everything fine without isue in intervlan.
    Thanks.

    Marvin,
    This is the output.
    `show module`
    Mod Ports Module-Type                       Model                  Status
    1   48    O2 48X10GE/Modular Supervisor     N5K-C5596UP-SUP        active *
    Mod  Sw              Hw      World-Wide-Name(s) (WWN)
    1    5.2(1)N1(1b)    1.0     --
    `show interface brief`
    Ethernet      VLAN    Type Mode   Status  Reason                   Speed     Port
    Interface                                                                    Ch #
    Eth1/1        1       eth  trunk  up      none                        10G(D) --
    Eth1/2        1       eth  trunk  up      none                        10G(D) --
    Eth1/3        1       eth  trunk  up      none                        10G(D) --
    Eth1/4        1       eth  trunk  up      none                        10G(D) --
    Eth1/5        1       eth  trunk  down    Link not connected          10G(D) --
    Eth1/6        1       eth  trunk  up      none                        10G(D) --
    Eth1/7        1       eth  trunk  up      none                        10G(D) --
    Eth1/8        1       eth  trunk  down    Link not connected          10G(D) --
    Eth1/9        1       eth  access down    SFP not inserted            10G(D) --
    Eth1/10       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/11       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/12       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/13       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/14       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/15       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/16       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/17       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/18       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/19       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/20       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/21       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/22       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/23       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/24       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/25       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/26       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/27       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/28       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/29       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/30       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/31       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/32       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/33       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/34       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/35       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/36       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/37       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/38       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/39       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/40       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/41       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/42       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/43       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/44       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/45       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/46       1       eth  access down    SFP not inserted            10G(D) --
    Eth1/47       1       eth  trunk  down    SFP not inserted            10G(D) --
    Eth1/48       1       eth  trunk  down    SFP not inserted            10G(D) --
    Port   VRF          Status IP Address                              Speed    MTU
    mgmt0  --           down   --                                      --       1500
    Interface Secondary VLAN(Type)                    Status Reason                
    Vlan1     --                                      down   Administratively down 
    Vlan199   --                                      up     --       
    Vlan999   --                                      down   Non-routable VDC mode 
    sh ip int bri
    IP Interface Status for VRF "default"(1)
    Interface            IP Address      Interface Status
    Vlan199              192.168.36.10   protocol-up/link-up/admin-up      
    Vlan999              192.168.99.1    protocol-down/link-down/admin-up  
    sh vlan
    VLAN Name                             Status    Ports
    1    default                          active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/9, Eth1/10, Eth1/11
                                                    Eth1/12, Eth1/13, Eth1/14
                                                    Eth1/15, Eth1/16, Eth1/17
                                                    Eth1/18, Eth1/19, Eth1/20
                                                    Eth1/21, Eth1/22, Eth1/23
                                                    Eth1/24, Eth1/25, Eth1/26
                                                    Eth1/27, Eth1/28, Eth1/29
                                                    Eth1/30, Eth1/31, Eth1/32
                                                    Eth1/33, Eth1/34, Eth1/35
                                                    Eth1/36, Eth1/37, Eth1/38
                                                    Eth1/39, Eth1/40, Eth1/41
                                                    Eth1/42, Eth1/43, Eth1/44
                                                    Eth1/45, Eth1/46, Eth1/47
                                                    Eth1/48
    5    A                       active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    199  B                          active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    391  C                     active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    392  D                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    393  E                       active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    394  F                        active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    395  G                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    500  H                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    526  I                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                    Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                    Eth1/47, Eth1/48
    VLAN Type  Vlan-mode
    1    enet  CE    
    5    enet  CE    
    199  enet  CE    
    391  enet  CE    
    392  enet  CE    
    393  enet  CE    
    394  enet  CE    
    395  enet  CE    
    500  enet  CE    
    526  enet  CE    
    Remote SPAN VLANs
    Primary  Secondary  Type             Ports

  • DCNM SAN 6.2 + Nexus 5500 not using interface mgmt

    When trying to discover a newly setup fabric we have set the SVI of one of the Nexus 5500 switches as seed device in DCNM SAN server. Problem do seem to be the same in DCNM 6.2 as in DCNM 5.x, one can not use a SVI.... After adding the seed switch with the IP adress of the SVI it appears in the Admin->Data sources->Fabric with the ip address of the mgmt interface. Thing is that this ip address can not be reached from the DCNM SAN server since we have only used a cross over ethernet cable for peer-keepalive over the mgmt interfaces.
    Is there a way in DCNM SAN 6.2 to force SAN management over a SVI instead of the mgmt interface?

    Here is the solution:
    in the menubar on the top, in the lower one go to Admin > Server Properties
    scroll to the middle of the list, locate “fabric.managementIpOverwrite” and set it to false 
    restart the DCNM Servers

  • Nexus 5500 FCoE

    Hi,
    If I use a SFP-10G-SR transceiver in a Nexus 5500, can I have FCoE in this port?
    Sorry for the question but i'm begining in the FCoE world
    Thanks

    Thanks Vinayak
    I'm very excited to be working with Nexus switches. Currently we only going to use ethernet, but with the new servers will be able to use FCoE.

  • Nexus 5500 to Nexus 5500 Fiber Etherchannel with different lengths

    Hi,
    I'm in the very first phase of designing a small datacenter infrastructure based on the Nexus 5500 series. I haven't got any hands-on nexus experience yet so please forgive me if I'm asking a silly question here...
    What I would like to build is a 4 unit, redundant datacenter design. Two units in one DC, and two units in the other. I would like to connect both DCs together using a redundant darkfiber. One link is 10 miles, the other is 20 miles.
    The Nexus switches are going to be connected "back-to-back" with and the redundant etherchannel between the DCs, like this http://www.netcraftsmen.net/component/content/article/69-data-center/859-configuring-back-to-back-vpcs-on-cisco-nexus-switches.html
    Can I expect any problems with this design? In particular with the different lengths of fiber, like buffering issues or failing transmissions?
    Thanks!

    That should not be an issue.  You will need single mode fiber and single mode optics, and as long as all your optics support distance of 20 miles or more, then you should be fine.
    HTH

  • Qos using priority queue drops

    I have following config for Qos.
    Basically Access-list match the voip/signalling traffic & put that in High queue. I am trying to figure without hight utilization why I am seeing output drops in high queue.
    7206#sh int s5/1/5:0
    Serial5/1/5:0 is up, line protocol is up
    Hardware is PA-MC-2T3+
    Description: T1
    Internet address is 172.17.133.105/30
    MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec,
    reliability 255/255, txload 24/255, rxload 23/255
    Encapsulation HDLC, crc 16, loopback not set
    Keepalive set (10 sec)
    Last input 00:00:06, output 00:00:00, output hang never
    Last clearing of "show interface" counters 01:58:03
    Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 1800
    Queueing strategy: priority-list 4
    Output queue (queue priority: size/max/drops):
    high: 0/20/1764, medium: 0/20/0, normal: 0/15/36, low: 0/15/0
    5 minute input rate 143000 bits/sec, 82 packets/sec
    5 minute output rate 145000 bits/sec, 83 packets/sec
    734269 packets input, 148368640 bytes, 0 no buffer
    Received 708 broadcasts, 0 runts, 0 giants, 0 throttles
    0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
    734855 packets output, 148838576 bytes, 0 underruns
    0 output errors, 0 collisions, 0 interface resets
    0 output buffer failures, 0 output buffers swapped out
    0 carrier transitions no alarm present
    Timeslot(s) Used: 1-24, subrate: 1536Kb/s, transmit delay is 0 flags
    non-inverted data
    ==============================================================================
    7200#sh run int s2/1/5:0
    Building configuration...
    Current configuration : 254 bytes
    interface Serial2/1/5:0
    description T1
    ip address x.x.x.x
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    no snmp trap link-status
    priority-group 4
    no cdp enable
    end
    ====================================================================================
    Define access-list to match voice/signalling traffic
    access-list 140 permit udp any any range 1024 1151
    access-list 140 permit udp any any range 16384 32767
    access-list 140 permit udp any any eq 2427
    access-list 140 permit udp any any eq 2429
    access-list 140 permit udp any any eq 5060
    priority-list 4 protocol ip high list 140
    priority-list 4 queue-limit 20 20 15 15

    Hi,
    your queue limit is 20 packets. This can explain the behaviour. If there are 20 packets in the queueing system waiting to be serviced any newly arriving packet will be dropped.
    Basically you can have drops in any queue in any queueing system if there is a permanent overload situation. There is no magic trick, if you f.e. permanently send 2 Mbps voip towards a T1. There will be drops.
    QoS does not create resources, it just distributes them among your important traffic classes.
    Besides this I also would suggest you to use class based queueing based on Modular QoS CLI (MQC). It is more flexible and precise than the old legacy methods like priority queueing, which you are using. On the other hand, if this is sufficient for you, why not.
    Regards, Martin

  • QOS on Nexus 5500

    Hi:
    Can someone give me a QOS example config for my scenario below:
    I have read the config guide and is confused.
    Let's say I have a router leg on e1/1 of N5K1.
    I want to limit on the outbound( N5K1 to router) http 25%, icmp 10K  and remaining goes to default.
    Any sample configurations welcome. I have already checked the ones in thc config guide.
    thanks

    Hello Ben,
    Since you have not received a reply, I am moving this post to our data center community for greater visibility.
    Thank you,
    Fabienne

  • Nexus 5500 VoIP cos 3 and FCoE

    Hi
    I have a requirment to do QoS for a DC that includes some VoIP as well FCoE with CNAs in the servers. I want to use COS 3 for the VoIP signalling and drop it in the same input and output quues to the servers as FCoE.
    so we have
    class-map type qos class-fcoe
    class-map type queuing class-fcoe
      match qos-group 1
    which is the default for FCoE and I have 50% bandwidth assoicated with it.
    policy-map type queuing
         class type queuing class-fcoe
           bandwidth percent 50
         class type queing someother class etc
    The issue is the "class-fcoe" is a default class and there doesnt seem to be anywhere I can edit it to add the VOIP control traffic to the same class or can I just add it here:
    class-map type queuing match any class-fcoe
      match qos-group 1
      match cos 3
    Thanks
    Pat

    Hmm
    From the UCS 8 SRND
    For instance, voice signaling traffic with L3 DSCP  value of CS3 is mapped to L2 CoS value of 3 by Nexus 1000V. All Fibre  Channel over Ethernet (FCoE) traffic is marked with L2 CoS value of 3 by  Cisco UCS. When voice signaling and FCoE traffic enter the Cisco  UCS 6100 Fabric Interconnect Switch, both will carry a CoS value of 3.  In this situation voice signaling traffic will share queues and  scheduling with the Fibre Channel priority class and will be given  lossless behavior. (Fibre Channel priority class for CoS 3 in the  UCS 6100 Fabric Interconnect Switch does not imply that the class cannot  be shared with other types of traffic.)
    This seems ti pmply you can run Call SIgnalling COS 3 in the same queueu as FCOE COS 3. I kow its talking about a 6100 fabric switch but thats very similar to a 5500.
    Could I not do something like:
    class-map type qos match-all voice-signal-global
       match-cos 3
    policy-map type qos classify-global
       class voice-signal-global
          set qos-group 1
       class class-fcoe
          set qos-group 1
    But then I cant see how to link this where we set the queuing bandwidth percentages as this uses the "class-fcoe"
    policy-map type queuing global-fcoe-queuing-in
       class type queuing class-fcoe
          bandwidth percent 50
    Could I create a class to replace "class-fcoe" and jsut match on qos-group 1 to define whats in it ?
    Regards
    Pat

  • 6500-qos-drops

    I have a problem with an interface Gi that it has qos enable. It drops packets in priority queue ( cos 5 asignated), following the q2 and there is not drops on q1.
    This is the status:
    Interface GigabitEthernet9/32 queueing strategy: Weighted Round-Robin
    Port QoS is enabled
    Trust state: trust COS
    Extend trust state: not trusted [COS = 0]
    Default COS is 0
    Transmit queues [type = 1p2q2t]:
    Queue Id Scheduling Num of thresholds
    1 WRR low 2
    2 WRR high 2
    3 Priority 1
    WRR bandwidth ratios: 100[queue 1] 255[queue 2]
    queue-limit ratios: 70[queue 1] 15[queue 2]
    queue random-detect-min-thresholds
    1 40[1] 70[2]
    2 40[1] 70[2]
    queue random-detect-max-thresholds
    1 70[1] 100[2]
    2 70[1] 100[2]
    queue thresh cos-map
    1 1 0 1
    1 2 2 3
    2 1 4 6
    2 2 7
    3 1 5
    Receive queues [type = 1q2t]:
    Queue Id Scheduling Num of thresholds
    1 Standard 2
    queue tail-drop-thresholds
    1 100[1] 100[2]
    queue thresh cos-map
    1 1 0 1 2 3 4
    1 2 5 6 7
    Packets dropped on Transmit:
    BPDU packets: 0
    queue thresh dropped [cos-map]
    1 1 0 [0 1 ]
    1 2 0 [2 3 ]
    2 1 0 [4 6 ]
    2 2 486* [7 ]
    3 1 486* [5 ]
    * - shared transmit counter
    Packets dropped on Receive:
    BPDU packets: 0
    queue thresh dropped [cos-map]
    1 1 0 [0 1 2 3 4 ]
    1 2 0 [5 6 7 ]
    Thanks,
    Marcelo

    check out the following link on Troubleshooting Output Drops with Priority Queueing, hope this helps :
    http://www.cisco.com/en/US/tech/tk39/tk51/technologies_tech_note09186a0080103e8a.shtml

  • 7600 QoS Strict-Priority

    Hello,
    I'm testing in a LAB QoS configuration for 7600 (SUP720-3B) with 12.2-18.SXF3 with many diffenents cards.
    Following Cisco documentation, I have two diferent scenarios:
    1. OSM and WAN interfaces supports CBWFQ and LLC and it works fine, as I understand it should work. We could create a priority queue and many standard queues to clasify the traffic and assign differents BW.
    2. LAN interfaces don't support CBWFQ and LLC and we should use the Queue Architecture of the card and WRR and WRED, which are implemented on the ASICs. This is what Cisco calls Hardware-Switched Traffic.
    Here it depends of the card you use what Queue Architecture you could use. But most cards have a Strict-Priority Queue and one or more standard queues.
    My question is regarding about the diferent behavior of the priority queue (LLC) and the Strict-Priority queue in case of congestion on the interface.
    From my testings I got:
    + 1st scenario (Priotity Queue - LLC)
    In case of congestion of the interface, QoS provide to the Priority Queue just the BW configured. If the BW offered in this queue is higher than the BW configured, there're packet drops.
    The rest of the standard queues shares the rest of the BW available on the interface.
    + 2nd scenario (Hardware-Switched Traffic)
    Even with or without congestion, I get almost the same behavior. The router always try to transmit the traffic of the strict-priority queue first. So it doesn't matter how much BW you allocate to the strict-priority queue and the standard queues. The card always try to transmit the traffic of strict-priority queue first.
    Is this the desired behavior or there's something wrong?
    The behavior of the priority queue should be the same in both scenarios?
    I got the following answers from Cisco Web Site which doesn't answer my question completely (See attached file).
    Anyone tried this before???
    Thanks.
    Paco

    Hello Baley,
    Thanks for your reply. I read this link before but it doesn't explain exactly what happens in the scenario described before.
    Few days ago I got an answer from Cisco which confirms what I read from the FAQ: Till Strict-Priority Queue isn't empty, packets on the WRR queues aren't send. This behavior is completely different from the well known LLQ.
    Catalyst 6500/6000 QoS FAQ
    Q. On egress queuing, if the strict priority queue is saturated, will traffic eventually be served in the weighted round-robin (WRR) queues?
    A. No, the WRR queues are not served until the priority queue is completely empty.

  • Nexus 5k QoS Classifcation

    Hello,
      From what I have gathered from documentation the Nexus is able to mark any DSCP value between 0-63. I would assume it would be able to classify based on any DSCP value as well.  The documentation however leads me to believe otherwise. The language for marking suggest valid values are from 0 to 63. For classification the language suggests classification can only match standard DSCP values. I would test but do not have a Nexus at my disposal. Can someone with experience please confirm?
    Classification
    http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/command/reference/qos/n5k-qos_cmds_m.html#wp1079436
    Marking
    http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/command/reference/qos/n5k-qos_cmds_s.html#wp1159955
    regards,
    ryan

    Hi Ryan,
    As you can see from my 5010 lab switch:
    24.09.5010B.1(config)# policy-map type qos my_policy
    24.09.5010B.1(config-pmap-qos)# class type qos my_class
    24.09.5010B.1(config-pmap-c-qos)# set dscp ?
      <0-63>   DSCP value
      af11     AF11 dscp (001010)
      af12     AF12 dscp (001100)
      af13     AF13 dscp (001110)
      af21     AF21 dscp (010010)
      af22     AF22 dscp (010100)
      af23     AF23 dscp (010110)
      af31     AF31 dscp (011010)
      af32     AF32 dscp (011100)
      af33     AF33 dscp (011110)
      af41     AF41 dscp (100010)
      af42     AF42 dscp (100100)
      af43     AF43 dscp (100110)
      cs1      CS1(precedence 1) dscp (001000)
      cs2      CS2(precedence 2) dscp (010000)
      cs3      CS3(precedence 3) dscp (011000)
      cs4      CS4(precedence 4) dscp (100000)
      cs5      CS5(precedence 5) dscp (101000)
      cs6      CS6(precedence 6) dscp (110000)
      cs7      CS7(precedence 7) dscp (111000)
      default  Default dscp (000000)
      ef       EF dscp (101110)
    The only DSCP values you can set are 0-63, as you suspected.
    However, these are the only DSCP values you are supposed to be able to match as well:
    24.09.5010B.1(config-cmap-qos)# match dscp ?
    <0-63>   List of DSCP values
      af11     AF11 dscp (001010)
      af12     AF12 dscp (001100)
      af13     AF13 dscp (001110)
      af21     AF21 dscp (010010)
      af22     AF22 dscp (010100)
      af23     AF23 dscp (010110)
      af31     AF31 dscp (011010)
      af32     AF32 dscp (011100)
      af33     AF33 dscp (011110)
      af41     AF41 dscp (100010)
      af42     AF42 dscp (100100)
      af43     AF43 dscp (100110)
      cs1      CS1(precedence 1) dscp (001000)
      cs2      CS2(precedence 2) dscp (010000)
      cs3      CS3(precedence 3) dscp (011000)
      cs4      CS4(precedence 4) dscp (100000)
      cs5      CS5(precedence 5) dscp (101000)
      cs6      CS6(precedence 6) dscp (110000)
      cs7      CS7(precedence 7) dscp (111000)
      default  Default dscp (000000)
      ef       EF dscp (101110)
    This output was taken on our latest version of code, and the 5500 series is the same.
    - Amanda

Maybe you are looking for