Naming conventions for acls – Avaya P580 User Manual
Page 304
9-18
Avaya P550R, P580, P880, and P882 Multiservice Switch User Guide, v5.3.1
Chapter
Naming
Conventions for
ACLs
The Avaya Multiservice switch supports ACL names up to 32
characters (Alpha-Numeric). Spaces are allowed in the names but
are not recommended. Instead of spaces, use the underscore “_”
character.
ACL Names are entered when you create a rule. By using the same
ACL Name for multiple rules, you are effectively creating a list of
rules. The Access List Index determines the order of rules in the list.
For that reason, when you create a rule, you give the rule the Access
List Name and the Access List Index. No two rules in a list may have
the same index.
If you create rules with different ACL Names, you have created
different lists. This is useful when you need more than one ACL. For
example, you may have one ACL for normal working hours, one
ACL for nighttime hours, and a third list for Holidays. When you
enable (activate) an ACL, the currently enabled (active) ACL is
automatically disabled (de-activated). In other words, there can only
be one active ACL.
The only restriction on the amount of ACLs you can create is that
the total number of rules cannot exceed 512. So, you could create a
single ACL with 512 rules; or one ACL with 300 rules and a second
with 212 rules, etc.... See the section
guidelines to consider when designing ACLs.
An ACL name can be a number. For example, you can create a list
whose name is 1 or 151. If you chose to use numbers, keep in mind
the following restrictions:
■
Numbers 1 through 99 are reserved for Standard type Rules
ONLY. So, for example, if you try to create an Extended Rule
whose ACL Name is 1, it will be rejected.
■
Numbers 100 through 199 are reserved for Extended type
Rules ONLY. So, for example, if you try to create a Standard
Rule whose ACL Name is 100, it will be rejected.
■
ACL names that contain any letter (Alphabetic) character,
can be either Standard or Extended.
■
You cannot mix ACL types in a list. This means that if you
create an ACL with a Standard Rule with ACL Name Test1,
you cannot create an Extended Rule in ACL Test1. If you do,
you will receive the following message:
Access Rule Name is already being used by the
other type.
Choose a different name and try again