Verifying The Acl Configuration To The Subscriber Named Default; Applying An Acl To Service-Specified Default Subscriber - Cisco ASR 5500 System Administration Manual

Applying an ACL to Service-specified Default Subscriber

• If neither the in nor the out keyword is specified, the ACL will be applied to all inbound and outbound
• 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)

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:
host_name
[local]
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_name
context
ip access-list
deny host
deny ip any host
exit
ip access-group
service-redundancy-protocol
exit
interface
ip address
exit
subscriber name default
ip access-group
ip access-group
exit
aaa group default
exit
gtpp group default
exit
content-filtering server-group
response-timeout
connection retry-timeout
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
packets.
does not exceed the 256-rule limit for the interface.
show configuration context context_name
#
acl_name
ip_address
ip_address
access_group_name
interface
ip_address/mask
access_group_name
access_group_name
response_timeout
retry_timeout
end
in
out
cfsg_name
Access Control Lists