Avaya Stackable Switch P3343T-ML - Manual (Page 129)

Chapter 11 Avaya P330 Layer 2 Features
Avaya P334T-ML User’s Guide 113
• TCP/UDP port ranges can only have sizes of 2
n
, where the lower port of the
range is aligned to the range number.
— For example, for a range of 32 ports (2
5
), the lower ports can have the value
of 32, 64, 96, etc.
— This limitation does not apply when the device is in “Router” policy type.
• Only L3 rules (based on Src/Dest IP address) will be enforced on IP fragments.
Therefore, if an L4 rule is applicable to an IP fragment, the fragment will be
dropped.
• The following rules are not supported for TCP/UDP port numbers:
— “lower then”
— “greater then”
• If a packet matches a rule with a “permit” action and subsequently a rule with
“fwd…” action, the packet’s priority will be changed to the one specified in the
second rule, instead of being forwarded with the original priority as per
“permit” action
— This limitation is relevant only for Layer 2 policy (i.e., when the policy type
is “all”).
Configuring the P334T-ML for Multilayer Policy
This section describes the configuration of the P334T-ML for Multilayer Policy
functionality.
Configuration Requirements
The following specific requirements impact on the configuration of Multilayer
Policy in an Avaya P334T-ML:
•
Multilayer Policy must be configured separately on each P334T-ML in the stack.
This is done by opening a “session” to the module.
• If the device Mode is “Layer 2,” the policy commands will appear in the L2 CLI
tree; if the Device Mode is “Router,” the commands will appear in the L3 CLI
tree.
• Policy List validation will be performed during list activation.
• A CLI command for policy simulation is available.
Configuration File Management
The following specific requirements impact on the management of the Multilayer
Policy configuration file:
•
Unlike other Layer 2 settings, the Layer 2 policy is not automatically saved in
NVRAM. In order to save the Layer 2 or Layer 3 policy configuration, the user
must copy the running configuration to the startup configuration file. To do
this, use the command copy running-config startup-config.