•
Up to 12 charging gateway functions (CGFs) for GTPP accounting can be configured per context.
•
Up to 16 bidirectional forwarding detection (BFD) sessions per context (64 per chassis)
Refer to Engineering Rules in your product administration guide for additional information on
product-specific operating limits.
Important
Subscriber Rules
The following engineering rules apply to subscribers configured within the system:
•
Configure a maximum of 2,048 local subscribers per context.
•
You may configure attributes for each local subscriber.
•
The system creates a default subscriber for each context when the context is made. Configure attributes
for each default subscriber. If a AAA-based subscriber is missing attributes in the authentication reply
message, the default subscriber attributes in the context where the subscriber was authenticated are used.
Default is not used when local authentication (for local subscribers) is performed.Important
•
Configure default subscriber templates on a per AAA realm (domain aliases configured within a context)
basis.
•
Configure default subscriber templates on a per PDSN, FA, ASN-GW, or HA service.
•
For AAA authenticated subscribers, the selection of local subscriber template to use for setting attributes
is in the following order:
•
If the username (NAI) matches any local domain name and the domain name has a local subscriber
name configured, that local subscriber template is used.
•
If the first case fails, and if the serving service has a default username configured, that subscriber
template is used.
•
If the first two cases fail, the default subscriber template in the AAA context is used.
Service Rules
The following engineering rules apply to services configured within the system:
•
Configure a maximum of 256 services (regardless of type) per system.
ASR 5500 System Administration Guide, StarOS Release 21.5
310
Engineering Rules
Subscriber Rules
To Next Page
Loading...
Need help?
General
