context_name
is the name of the context containing the service with the default subscriber 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
interface
interface
ip address
ip_address/mask
exit
subscriber default
exit
subscriber name
subscriber_name
ip access-group
access_group_name
in
ip access-group
access_group_name
out
exit
pdsn-service
service_name
default subscriber
subscriber_name
end
Applying a Single ACL to Multiple Subscribers
As mentioned in the previous section, IP ACLs are applied to subscribers via attributes in their profile. The
subscriber profile could be configured locally on the system or remotely on a RADIUS server.
The system provides for the configuration of subscriber functions that serve as default values when specific
attributes are not contained in the individual subscriber's profile. The following table describes these functions.
Table 13: Functions Used to Provide "Default" Subscriber Attributes
Description
Function
Within each context, the system creates a subscriber called
default
. The
profile for the subscriber named
default
provides a configuration template
of attribute values for subscribers authenticated in that context.
Any subscriber attributes that are not included in a RADIUS-based
subscriber profile is configured according to the values for those attributes
as defined for the subscriber named
default
.
NOTE:
The profile for the subscriber named
default
is not used to provide
missing information for subscribers configured locally.
Subscriber named
default
This command allows multiple services to draw "default" subscriber
information from multiple profiles.
default subscriber
ASR 5500 System Administration Guide, StarOS Release 21.5
198
Access Control Lists
Applying a Single ACL to Multiple Subscribers