Hello,
Afaik no. Nexus 3k is considered as Low Latency Queueing switch and shaping and policing triggers the queueing (if we talk about egress one) which does not fit in low latency theory as per developers.
The way to configure QoS is to split traffic into queues and limit bandwidth for those.
E.G.
N3k-1(config)# class-map type qos QUE_class
N3k-1(config-cmap-qos)# match cos 0-7
2) Create a queuing policy-map:
N3k-1(config-cmap-qos)# policy-map type queuing QUE_policy
3) Assign a class to this policy map:
N3k-1(config-pmap-que)# class type queuing QUE_class
4) Set bandwidth percentage to 5%, which would be 50Mb on a 1G
interface
N3k-1(config-pmap-c-que)# bandwidth percent 5
5) Set the bandwidth on the class-default to 0%:
N3k-1(config-pmap-que)# class type queuing class-default
N3k-1(config-pmap-c-que)# bandwidth percent 0
6) Apply this policy-map to an interface:
N3k-1(config)# int e1/1
N3k-1(config-if)# service-policy type queuing output QUE_policy
N3k-1(config-if)# service-policy input QUE_policy
Here is what your interface should look like:
N3k-1# show policy-map int e1/1 in
Global statistics status : disabled
Ethernet1/1
Service-policy (qos) input: QUE_policy
policy statistics status: disabled
Class-map (qos): QUE_class (match-all)
Match: cos 0-7
Class-map (qos): class-default (match-any)
Match: any
set qos-group 0
N3k-1# show policy-map int e1/1 out
Global statistics status : disabled
Ethernet1/1
Service-policy (queuing) output: QUE_policy
policy statistics status: disabled
Class-map (queuing): QUE_class (match-any)
bandwidth percent 5
Class-map (queuing): class-default (match-any)
Match: qos-group 0
bandwidth percent 0
Nik
HTH,
Niko
