Cisco Cisco ASR 5000
Serving GPRS Support Node (SGSN) Overview
▀ Features and Functionality
▄ SGSN Administration Guide, StarOS Release 18
GPRS: Provides statistics for LLC, BSSGP, SNDCP, and NS layers
SCCP: Provides SCCP network layer statistics
SGTP: Provides SGSN-specific GPRS Tunneling Protocol (GTP) statistics
SGSN: Provides statistics for: mobility management (MM) and session management (SM) procedures; as well,
MAP, TCAP, and SMS counters are captured in this schema. SGSN Schema statistic availability is per service
(one of: SGSN, GPRS, MAP) and per routing area (RA)
(one of: SGSN, GPRS, MAP) and per routing area (RA)
SS7Link: Provides SS7 link and linkset statistics
SS7RD: Provides statistics specific to the proprietary SS7 routing domains
The system supports the configuration of up to 4 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 chassis or sent
at configured intervals. The bulk statistics are stored on the receiver(s) in files.
to collect specific sets of statistics from the various schemas. Statistics can be pulled manually from the chassis 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, chassis host name, chassis 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.
file headers, and/or footers to include information such as the date, chassis host name, chassis 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.
When the Web Element Manager is used as the receiver, it is capable of further processing the statistics data through
XML parsing, archiving, and graphing.
XML parsing, archiving, and graphing.
The Bulk Statistics Server component of the Web Element Manager parses collected statistics and stores the information
in the PostgreSQL database. If XML file generation and transfer is required, this element generates the XML output and
can send it to a Northbound NMS or an alternate bulk statistics server for further processing.
in the PostgreSQL database. If XML file generation and transfer is required, this element generates the XML output and
can send it to a Northbound NMS or an alternate bulk statistics server for further processing.
Additionally, if archiving of the collected statistics is desired, the Bulk Statistics server writes the files to an alternative
directory on the server. A specific directory can be configured by the administrative user or the default directory can be
used. Regardless, the directory can be on a local file system or on an NFS-mounted file system on the Web Element
Manager server.
directory on the server. A specific directory can be configured by the administrative user or the default directory can be
used. Regardless, the directory can be on a local file system or on an NFS-mounted file system on the Web Element
Manager server.
Bypassing APN Remap for Specific IMEI Ranges
Prior to Release 16, if a local default APN configured in an IMEI profile could not be used, then any default APN
configured under an operator policy was used. Also, only the
configured under an operator policy was used. Also, only the
apn-selection-default
CLI option, under the APN
Remap Table configuration associated with an IMEI profile, was valid. Other CLI options such as
apn-remap
and
blank-apn
were not applicable when a remap table was associated with an IMEI profile.
With Release 16, an APN Remap Table associated with an IMEI profile overrides a remap table associated with an
operator policy. This means activation will be rejected if a local default APN configured, in an APN Remap Table
associated with an IMEI profile, cannot be used. This will occur even if a valid local default APN is available in an
APN Remap Table associated with an operator policy.
operator policy. This means activation will be rejected if a local default APN configured, in an APN Remap Table
associated with an IMEI profile, cannot be used. This will occur even if a valid local default APN is available in an
APN Remap Table associated with an operator policy.
Important:
To achieve the previous default behavior, customers already using an APN Remap Table that is
associated with an IMEI profile will have to change the existing configuration to achieve the previous behavior. For
details and sample configurations, see the Release 16 specific information for
details and sample configurations, see the Release 16 specific information for
apn-selection-default
in the APN
Remap Table Configuration Mode Commands section of the Command Line Interface Reference for a Release 16 or
higher.
higher.