Cisco Cisco ASR 5000
Serving Gateway Overview
Features and Functionality - Base Software ▀
S-GW Administration Guide, StarOS Release 18 ▄
25
These measures are applicable to the ASR 5x00 Platform and an element management system since both require
password authentication. A subset of these guidelines where applicable to each platform will be implemented. A known
subset of guidelines, such as certificate authentication, are not applicable to either product. Furthermore, the platforms
support a variety of authentication methods such as RADIUS and SSH which are dependent on external elements. ANSI
T1.276 compliance in such cases will be the domain of the external element. ANSI T1.276 guidelines will only be
implemented for locally configured operators.
password authentication. A subset of these guidelines where applicable to each platform will be implemented. A known
subset of guidelines, such as certificate authentication, are not applicable to either product. Furthermore, the platforms
support a variety of authentication methods such as RADIUS and SSH which are dependent on external elements. ANSI
T1.276 compliance in such cases will be the domain of the external element. ANSI T1.276 guidelines will only be
implemented for locally configured operators.
APN-level Traffic Policing
The S-GW now supports traffic policing for roaming scenarios where the foreign P-GW does not enforce traffic classes.
Traffic policing is used to enforce bandwidth limitations on subscriber data traffic. It caps packet bursts and data rates at
configured burst size and data rate limits respectively for given class of traffic.
Traffic policing is used to enforce bandwidth limitations on subscriber data traffic. It caps packet bursts and data rates at
configured burst size and data rate limits respectively for given class of traffic.
Traffic Policing is based on RFC2698- A Two Rate Three Color Marker (trTCM) algorithm. The trTCM meters an IP
packet stream and marks its packets green, yellow, or red. A packet is marked red if it exceeds the Peak Information
Rate (PIR). Otherwise it is marked either yellow or green depending on whether it exceeds or doesn't exceed the
Committed Information Rate (CIR). The trTCM is useful, for example, for ingress policing of a service, where a peak
rate needs to be enforced separately from a committed rate.
packet stream and marks its packets green, yellow, or red. A packet is marked red if it exceeds the Peak Information
Rate (PIR). Otherwise it is marked either yellow or green depending on whether it exceeds or doesn't exceed the
Committed Information Rate (CIR). The trTCM is useful, for example, for ingress policing of a service, where a peak
rate needs to be enforced separately from a committed rate.
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 an element management system, 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:
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:
System: Provides system-level statistics
Card: Provides card-level statistics
Port: Provides port-level statistics
MAG: Provides MAG service statistics
S-GW: Provides S-GW node-level service statistics
IP Pool: Provides IP pool statistics
APN: Provides Access Point Name statistics
The system supports the configuration of up to four sets (primary/secondary) of receivers. Each set can be configured
with to collect specific sets of statistics from the various schemas. Statistics can be pulled manually from the system or
sent at configured intervals. The bulk statistics are stored on the receiver(s) in files.
The format of the bulk statistic data files can be configured by the user. Users can specify the format of the file name,
file headers, and/or footers to include information such as the date, system host name, system uptime, the IP address of
the system generating the statistics (available for only for headers and footers), and/or the time that the file was
generated.
An element management system is capable of further processing the statistics data through XML parsing, archiving, and
graphing.
with to collect specific sets of statistics from the various schemas. Statistics can be pulled manually from the system or
sent at configured intervals. The bulk statistics are stored on the receiver(s) in files.
The format of the bulk statistic data files can be configured by the user. Users can specify the format of the file name,
file headers, and/or footers to include information such as the date, system host name, system uptime, the IP address of
the system generating the statistics (available for only for headers and footers), and/or the time that the file was
generated.
An element management system is capable of further processing the statistics data through XML parsing, archiving, and
graphing.