Cisco Cisco ASR 5000 Administrator's Guide

Page of 62
  HeNB Gateway in Wireless LTE Network 
Features and Functionality - Base Software  ▀   
 
Cisco ASR 5x00 Home eNodeB Gateway Administration Guide  ▄  
 
   
21 
Features and Functionality - Base Software 
This section describes the features and functions supported by default in base software on HeNB-GW service and do not 
require any additional license to implement the functionality with the HeNB-GW service. 
Following features and supports are discussed in this section: 
 
  
 
  
 
  
 
  
 
  
 
  
 
  
 
AAA Server Group Support 
It is a value-added feature to enable VPN service provisioning for enterprise or MVNO customers, however integrated 
SeGW is required to be enabled for this feature. It enables each corporate customer to maintain its own AAA servers 
with its own unique configurable parameters and custom dictionaries. 
This feature provides support for up to 800 AAA (RADIUS and Diameter) server groups and 800 NAS IP addresses that 
can be provisioned within a single context or across the entire chassis. A total of 128 servers can be assigned to an 
individual server group. Up to 1,600 accounting, authentication and/or mediation servers are supported per chassis and 
may be distributed across a maximum of 1,000 nodes. This feature also enables the AAA servers to be distributed across 
multiple nodes within the same context. 
Important:
  For more information on AAA Server Group configuration, if you are using StarOS 12.3 or an earlier 
release, refer to the AAA and GTPP Interface Administration and Reference. If you are using StarOS 14.0 or a later 
release, refer to the AAA Interface Administration and Reference
Access Control List Support 
Access Control Lists provide a mechanism for controlling (i.e. permitting, denying, redirecting, etc.) packets in and out 
of the system. 
IP access lists, or Access Control Lists (ACLs) as they are commonly referred to, are used to control the flow of packets 
into and out of the system. They are configured on a per-context basis and consist of “rules” (ACL rules) or filters that 
control the action taken on packets that match the filter criteria 
Once configured, an ACL can be applied to any of the following: 
 
An individual interface 
 
All traffic facilitated by a context (known as a policy ACL)