uda access-list
Creates a user-defined ACL (UDA).
Syntax
uda access-list
extended
acl-name
no uda access-list
extended
acl-name
Command Default
No UDA is defined.
Parameters
- extended
- Specifies an extended ACL. Extended ACLs contain rules that permit or deny traffic according to source and destination addresses, as well as other parameters. UDAs cannot be standard ACLs, which filter by source address only.
- acl-name
- Specifies an ACL name unique among all ACLs (Layer 2, Layer 3, and UDAs). The name can be up to 63 characters in length, and must begin with an alphanumeric character. No special characters are allowed, except for the underscore and hyphen.
Modes
Global configuration mode
Usage Guidelines
After you create a UDA, use the
seq
seq-value
{
deny
|
permit
}command to create filtering rules for that UDA.
For UDAs applied to NPB interfaces:
- A UDA starts functioning only after it is applied to an interface, using the
uda access-group command.
- Traffic not specifically permitted is dropped by a default final deny rule.
You can also include UDAs in NPB route-maps.
To delete a UDA, use the
no form of this command. You can delete a UDA only after you first remove it from all interfaces to which it is applied, using the
no uda access-group command.
Examples
The following example creates a UDA.
device# configure terminal
device(config)# uda access-list extended uda_01
The following example deletes a UDA.
device# configure terminal
device(config)# no uda access-list extended uda_01
