•
If neither the
in
nor the
out
keyword is specified, the ACL will be applied to all inbound and outbound
packets.
•
The ACL to be applied must be configured in the context specified by this command.
•
Up to 16 ACLs can be applied to a group provided that the number of rules configured within the ACL(s)
does not exceed the 256-rule limit for the interface.
Verifying the ACL Configuration to the Subscriber Named default
These instructions are used to verify the ACL configuration.
Verify that your ACL lists were applied properly by entering the following command in Exec Mode:
[local]
host_name
#
show configuration context context_name
context_name
is the name of the context containing the subscriber default to which the ACL(s) was/were applied.
The output of this command displays the configuration of the entire context. Examine the output for the commands
pertaining to interface configuration. The commands display the ACL(s) applied using this procedure.
configure
context
context_name
ip access-list
acl_name
deny host
ip_address
deny ip any host
ip_address
exit
ip access-group
access_group_name
service-redundancy-protocol
exit
interface
interface
ip address
ip_address/mask
exit
subscriber name default
ip access-group
access_group_name
in
ip access-group
access_group_name
out
exit
aaa group default
exit
gtpp group default
exit
content-filtering server-group
cfsg_name
response-timeout
response_timeout
connection retry-timeout
retry_timeout
end
Applying an ACL to Service-specified Default Subscriber
This section provides information and instructions for applying an ACL to the subscriber to be used as the
"default" profile by various system services.
ASR 5500 System Administration Guide, StarOS Release 21.5
196
Access Control Lists
Applying an ACL to Service-specified Default Subscriber