Design Reference

Figure 59: Filter decision-making process
Configure filters through the use of Access Control Lists (ACL) and Access Control Entries (ACE),
which are implemented in hardware. An ACL can include both security and QoS type ACEs. The
platform supports 2048 ACLs and 1000 ACEs for each ACL to a maximum of 16,000 ACEs for each
plaform.
The following steps summarize the filter configuration process:
1. Determine your desired match fields.
2. Create an ACL.
3. Create an ACE within the ACL.
4. Configure the desired precedence, traffic type, and action.
You determine the traffic type by creating an ingress or egress ACL.
5. Modify the parameters for the ACE.
Policing and shaping
As part of the filtering process, you can police ingress traffic. Policing is performed according to the
traffic filter profile assigned to the traffic flow. For enterprise networks, policing ensures that traffic
flows conform to the criteria assigned by network managers.
Traffic policers identify traffic using a traffic policy. Traffic that conforms to this policy is guaranteed
for transmission, whereas nonconforming traffic is considered to be in violation. Traffic policers drop
packets if traffic is excessive, or remark the DSCP or 802.1p markings by using filter actions. With
VSP 4000, you can define multiple actions in case of traffic violation.
For service providers, policing at the network edge provides different bandwidth options as part of a
service-level agreement (SLA). For example, in an enterprise network, you can police the traffic rate
from one department to give critical traffic unlimited access to the network. In a service provider
network, you can control the amount of traffic customers send to ensure that they comply with their
SLA. Policing ensures that users do not exceed their traffic contract for a QoS level.
VSP 4000 supports two-rate, three-color marking for policers as described in RFC2698. Policers
mark packets as Green, Yellow, or Red. Red packets are dropped automatically. Out of profile
packets cannot be re-marked to a lower QoS level.
QoS design guidelines
128 Network Design Reference for Avaya VSP 4000 Series December 2014
Comments? [e-mail]