There are many ways to do it, but if you are going to use the example you would have toapply it on both sides. The example provided can only be used as INPUT service policy, so you need to apply same configuration on both ends, but with reverse ACL.
ACL provided in example only uses source address match. on the other end you need to write it for destination. As in:
access-list 111 permit ip any 10.1.1.1 0.0.0.255
access-list 112 permit ip any 10.2.2.2 0.0.0.255
class-map match-any vl1
match access-group 111
class-map match-any vl2
match access-group 112
police 700000000 20000000
police 300000000 9000000
interface fa 0/41
service-policy input test
Check to see if the packets match into your classes with
"show policy-map interface gigaXX/XX/XX" command (the trunk).
Also, you might have to adjust burst sizes, since I have included recommended burst size, which is POLICE_RATE/32. But it may have to be reduced, depending on the switch. You can use smaller bursts, like 1MB (1000000). It will be ok at that speed.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...