cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2117
Views
0
Helpful
8
Replies

Nexus 7000 Layer 3 QoS

James Hogan
Level 1
Level 1

has anyone seen a good Document on LAYER 3 QoS on a Nexus 7000? especially for LLQ

8 Replies 8

Oleksandr Nesterov
Cisco Employee
Cisco Employee

Hi

As I understand, You Need to implement a custom queuing policies based ACLs to provide LLQ/CWFQ functionality on a N7k.

Bandwidth and priority commands can only be implementing in queueing policies and queueing policies are restricted to system queueing class-maps which match only on CoS values.

To implement what you are trying to perform, you can use a QoS policy to mark the DSCP/CoS value.  The system queuing class-maps will dictate the queue the packet is sent to in outgoing interface. For example:

ip access-list test_ip_af2

  10 permit ip any 172.17.1.10/32

ip access-list test_ip_af4

  10 permit ip any 172.17.1.20/32

ip access-list test_ip_ef

  10 permit ip any 172.17.1.1/32

class-map type qos match-any test_input_ef

  match access-group name test_ip_ef

class-map type qos match-any test_input_af2

  match access-group name test_ip_af2

class-map type qos match-any test_input_af4

  match access-group name test_ip_af4

NOTE: Following system class-maps configuration can be done ony in default VDC and applies to all existong VDC:

class-map type queuing match-any 1p3q4t-out-pq1

    match cos 7

class-map type queuing match-any 1p3q4t-out-q2

    match cos 4

class-map type queuing match-any 1p3q4t-out-q-default

    match cos 1

policy-map type qos test_in

  class test_input_ef

    set cos 7

  class test_input_af4

    set cos 4

  class test_input_af2

    set cos 1

interface Ethernet X/Y

description -=incomming interface=-

service-policy type qos input test_in

interface Ethernet A/B

description -=outgoing interface=-

service-policy type queuing output test_shaping_out

Hi, I have a similar problem but  when I try to attach a policiing to the interface VLAN is not posible:

 

interface VLAN

description -=incomming interface=-

service-policy type qos input test_in <= That is no posible.

 

 

Hello,

 

I think applying a policy map to a VLAN interface using a service-policy command under the interface configuration mode for the SVI is not supported. You have to use the syntax below (in this example Vlan 10 is used, change that accordingly):

 

N7K#conf t

N7K(config)#int vlan 10

N7K(config-if)#vlan configuration 10

N7K(config-vlan-config)#service-policy input test_in

Yes I'm using this but how we have a lot of VLANs and policing this is causing a problem on the TCAMs memorys on each module.

 

I found this https://lists.gt.net/cisco/nsp/136698%C3%A7

 

Hello,

 

which NX-OS version are you running ?

6.2(16)

Hello,

 

I don't know of any other way to implement this. Since you are apparently having problems with TCAM, have you tried to pool resources using the bank chaining feature ?

 

https://www.cisco.com/c/en/us/support/docs/routers/7000-series-routers/116151-problemsolution-product-00.html

Oleksandr Nesterov
Cisco Employee
Cisco Employee

Also please consider that each line-card type has it's own system class maps:

http://www.cisco.com/en/US/docs/switches/datacenter/sw/4_2/nx-os/qos/configuration/guide/cpl.html#wp1089686

Review Cisco Networking for a $25 gift card