Shaping on the ethernet

[admin@atrinnet.net]

Hi i used his for shaping

ip access-list meshali
10 permit ip any X.X.X.X/28
15 permit ip any Y.Y.Y.Y/28
ip access-list sadedel
10 permit ip any A.A.A.A/28
20 permit ip any B.B.B.B/28
class-map type qos match-all meshali
match access-group name meshali
class-map type qos match-all sadedel
match access-group name sadedel
policy-map type qos meshali
class meshali
police cir 500 mbps bc 200 ms conform transmit violate drop
policy-map type qos sadedel
class sadedel
police cir 900 mbps bc 250 ms conform transmit violate drop

No i want assign two shaping rules ti same ethernet for output

for example shaping meshali

and saddel to ethernet 1/1 out put

How can do this ?

[balaji.bandi]

what is the device model and IOS code runnning ?

is this interface gig ? or 10Gig ?   ( we see that config has 900MB and 500MB ?)

check below thread :

https://community.cisco.com/t5/routing/qos-police-bandwidth-sharing/m-p/4666048#M371144

[admin@atrinnet.net]

Hi interface Speed is 10Gbps

full-duplex, 10 Gb/s, media type is 10G

IOS version is nxos64-cs.10.3.4a.M.bin

The latest start version for nexus 93180

Now how can apply multi shaping on the inteface?

[balaji.bandi]

i think @Joseph W. Doherty  aleady suggested sample syntax

if that is still not working, post complete your configuration to look.

Note : you have other thread with same question - i have suggested some URL guide, have you looked that one ?

[Joseph W. Doherty · Accepted solution]

BTW, police statements don't shape.

Unsure your Nexus supports shaping.

As far as I know, you cannot have multiple CBWFQ statements, for input or output, for same traffic kind, like IP.  However, a policy-map can have multiple classes.  If fact, in yours, there already should be two, i.e. your explicitly defined class and an implicit default class.

E.g. (possibly)

policy-map type qos sample

class meshali

police cir 500 mbps bc 200 ms conform transmit violate drop

class sadedel

police cir 900 mbps bc 250 ms conform transmit violate drop

[Ruben Cocheno]

admin@atrinnet.net 

Nexus supports traffic shaping, and you need to combine both classes under the same policy map before call it on the Interface level. Also you might need to carve out the TCAM for QOS, depending on how you deployed the switch initially.

https://www.cisco.com/c/en/us/td/docs/dcn/nx-os/nexus9000/104x/configuration/qos/cisco-nexus-9000-series-nx-os-quality-of-service-configuration-guide-104x/m-configuring-queuing-and-scheduling.html#concept_0DB17702228C493D9391B3850CFE0517

[admin@atrinnet.net · Accepted solution]

I assign resources to L3 egrees Traffic shaping

show hardware access-list tcam region
NAT ACL[nat] size = 0
Ingress PACL [ing-ifacl] size = 0
VACL [vacl] size = 0
Ingress RACL [ing-racl] size = 1792
Ingress L2 QOS [ing-l2-qos] size = 256
Ingress L3/VLAN QOS [ing-l3-vlan-qos] size = 512
Ingress SUP [ing-sup] size = 512
Ingress L2 SPAN filter [ing-l2-span-filter] size = 256
Ingress L3 SPAN filter [ing-l3-span-filter] size = 256
Ingress FSTAT [ing-fstat] size = 0
span [span] size = 512
Egress RACL [egr-racl] size = 1280
Egress SUP [egr-sup] size = 256
Ingress Redirect [ing-redirect] size = 0
Egress L2 QOS [egr-l2-qos] size = 0
Egress L3/VLAN QOS [egr-l3-vlan-qos] size = 512
Ingress Netflow/Analytics [ing-netflow] size = 0
Ingress NBM [ing-nbm] size = 0
TCP NAT ACL[tcp-nat] size = 0
Egress sup control plane[egr-copp] size = 0
Ingress Flow Redirect [ing-flow-redirect] size = 0
Ingress CNTACL [ing-cntacl] size = 0
Egress CNTACL [egr-cntacl] size = 0
MCAST NAT ACL[mcast-nat] size = 0
Ingress DACL [ing-dacl] size = 0
Ingress PACL Super Bridge [ing-pacl-sb] size = 0
Ingress Storm Control [ing-storm-control] size = 0
Ingress VACL redirect [ing-vacl-nh] size = 0
Egress PACL [egr-ifacl] size = 0
Egress Netflow [egr-netflow] size = 0

Now Working ???

[admin@atrinnet.net]

I test The police on Nexus 93180 Work very Well