Cisco Cisco Packet Data Interworking Function (PDIF)
HeNB Gateway in Wireless LTE Network
▀ Features and Functionality - Base Software
▄ HeNB-GW Administration Guide, StarOS Release 18
24
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.
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.
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
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)
An individual subscriber
All subscriber sessions facilitated by a specific context
There are two primary components of an ACL:
Rule: A single ACL consists of one or more ACL rules. As discussed earlier, the rule is a filter configured to
take a specific action on packets matching specific criteria. Up to 128 rules can be configured per ACL.
Each rule specifies the action to take when a packet matches the specifies criteria. This section discusses the
rule actions and criteria supported by the system.
rule actions and criteria supported by the system.
Rule Order: A single ACL can consist of multiple rules. Each packet is compared against each of the ACL rules,
in the order in which they were entered, until a match is found. Once a match is identified, all subsequent rules
are ignored.
are ignored.
Important:
For more information on Access Control List configuration, refer IP Access Control List chapter in
System Administration Guide.
Bulk Statistics Support
The system's support for bulk statistics allows operators to choose to view not only statistics that are of importance to
them, but also to configure the format in which it is presented. This simplifies the post-processing of statistical data
since it can be formatted to be parsed by external, back-end processors.
them, but also to configure the format in which it is presented. This simplifies the post-processing of statistical data
since it can be formatted to be parsed by external, back-end processors.
When used in conjunction with the Web Element Manager, the data can be parsed, archived, and graphed.
The system can be configured to collect bulk statistics (performance data) and send them to a collection server (called a
receiver). Bulk statistics are statistics that are collected in a group. The individual statistics are grouped by schema.
Following is a partial list of supported schemas:
receiver). Bulk statistics are statistics that are collected in a group. The individual statistics are grouped by schema.
Following is a partial list of supported schemas:
System: Provides system-level statistics
Card: Provides card-level statistics
Port: Provides port-level statistics
GTP-U: Provides GPRS Tunneling Protocol - User message statistics