Chapter 1 Overview
6 Avaya X330W-2DS1 User’s Guide
• A set of possible actions arranged in a Composite Operations Table.
• A set of DSCP mappings.
Several policy lists can be activated concurrently, with each list applied to a
different interface and direction.
Each Serial interface (PPP session), the Fast Ethernet port, and the
FabricFastEthernet interface can have an ingress and egress active Policy list. For the
FabricFastEthernet interface, this list applies to all L2 interfaces (VLANs) mapped to
this interface.
A default Policy list (list 0) is always present and active until a different Policy list is
activated. The default list has one rule (permit all), a default DSCP mapping, and a
default Composite Operations table.
Whenever a new Policy list is created, it contains a copy of the list 0 components.
Policy rules and the Composite Operations Table include the following actions:
• Access Control actions (for all types of interfaces):
—Drop
— Drop and Notify
—Forwarding
• QoS actions:
— DSCP coloring (value changing) for all types of interfaces.
— Priority tag modifications for:
— Packets that traverse the inband LAN or the Ethernet port. This will be
marked as the IEEE 802.1p tag in the packet (only on the
FabricFastEthernet interface).
— Classification into one of the 4 transmit queues.
The Composite Operation Table contains pre-defined entries for the basic policies
that existed in the P333R. These entries are created by the agent for each Access List
and are Read Only.
Controlling Network Access to the X330WAN
Using Policy lists, you can control all traffic designated to and from the X330WAN’s
CPU, including management and routing protocols traffic. By activating Policy
rules defined for a Loopback interface, you can control all traffic entering/leaving
the CPU from/to all X330WAN interfaces. Rules governing traffic to the CPU can be
defined at a single point, regardless of the actual interface which the packet entered
and the specific IP address being managed.
Note: A Policy list activated on a Loopback interface does not apply to packets
routed by the CPU.