Filter
Top Products
Page 35 | AlliedWare Plus™ OS: Overview of QoS
4: Policing combined traffic types on separate ports
In this scenario, two types of traffic are collectively policed on a per-port basis. The policing is
done on several different ports. On each port, the policer counts all packets that match
either type’s class map.
This scenario uses multiple aggregate policers.
Use this type of scenario when you need to police some particular traffic types on a per-port
basis, but not set an overall bandwidth limit on ports.
For example, this would be useful if you want to give all users unlimited bandwidth for traffic
that is going to most addresses within the LAN, but put a limit on the level of traffic they can
send to addresses that are out on the Internet, and also put a limit on the amount of traffic
they can send to some particular internal service (such as an internally hosted on-line game
that is used during lunchbreaks). So, there would be an aggregate bandwidth limit collectively
applied to the traffic destined to the Web proxy server, and traffic associated with the on-line
game, but default traffic (i.e. traffic to all other internal addresses) would have no limit
applied.
The following figure shows this scenario.
policy-map 2
port
match
match
class-map 2
match
match
class-map 1
aggregate
policer 2
policy-map 1
port
match
match
class-map 2
ACL
match
match
class-map 1
match <parameter>
match access-group
class <map-name>
class <map-name>
aggregate
policer 1
police aggregate <name>
service-policy
input <name>
policer-4.eps