Information Required
The following sections describe the minimum amount of information required to configure and make the GGSN operational on the network. To make the process more efficient, it is recommended that this information be available prior to configuring the system.
There are additional configuration parameters that are not described in this section. These parameters deal mostly with fine-tuning the operation of the GGSN in the network. Information on these parameters can be found in the appropriate sections of the Command Line Reference.
Source Context Configuration
| Required Information | Description |
|---|---|
| Source context name | An identification string from 1 to 79 characters (alpha and/or numeric) by which the source context will be recognized by the system. |
| Gn Interface Configuration | |
| Gn interface name | An
identification string between 1 and 79 characters (alpha
and/or numeric) by which the interface will be
recognized by the system.
Multiple names are needed if multiple interfaces will be configured. |
| IP address and subnet | These
will be assigned to the Gn interface.
Multiple addresses and/or subnets are needed if multiple interfaces will be configured. |
| Physical port number | The
physical port to which the interface will be bound. Ports
are identified by the chassis slot number where the line card resides
in, followed by the number of the physical connector on
the line card. For example, port 17/1 identifies
connector number 1 on the card in slot 17.
A single physical port can facilitate multiple interfaces. |
| Physical port description | An
identification string from 1 to 79 characters (alpha and/or
numeric) by which the physical port will be recognized
by the system.
Multiple descriptions are needed if multiple ports will be used. Physical ports are configured within the source context and are used to bind logical Gn interfaces. |
| Gateway IP address | Used when configuring static routes from the Gn interface(s) to a specific network. |
| GGSN service Configuration | |
| GGSN service name | An
identification string from 1 to 63 characters (alpha and/or
numeric) by which the GGSN service will be recognized by
the system.
Multiple names are needed if multiple GGSN services will be used. |
| Accounting context | The
name of the context configured on the system in which the processing
of GTPP accounting records is performed.
The context name is an identification string from 1 to 79 characters (alpha and/or numeric). By default, the system attempts to use the same context as the one in which the GGSN service is configured. |
| UDP port number for GTPC traffic | The port used by the GGSN service and the SGSN for communicating GTPC sockets for GTPv1. The UDP port number and can be any integer value from 1 to 65535. The default value is 2123. |
| Public Land Mobile Network (PLMN) Identifiers | Mobile Country Code (MCC): The MCC can be configured to any integer value from 0 to 999. |
| Mobile Network Code (MNC): The MNC can be configured to any integer value from 0 to 999. | |
| SGSN information (optional) | The
GGSN can be configured with information about the SGSN(s) that
it is to communicate with. This includes the SGSN's
IP address and subnet mask and whether or not the SGSN is on a foreign
PLMN.
Multiple SGSNs can be configured. |
| GGSN charging characteristics (CC) (optional) | Behavior Bits: If
charging characteristics will be configured on the GGSN, behavior
bits for the following conditions can be configured:
Each value must be a unique bit from 1 to 12 to represent the 12 possible behavior bits allowed for in the standards. The default configuration is disabled (0). |
Profile Index: If
the GGSN's charging characteristics will be used for subscriber
PDP contexts, profile indexes can be modified/configured
for one or more of the following conditions:
The system supports the configuration of up to 16 profile indexes numbered 0 through 15 . |
|
| PLMN policy | The
GGSN can be configured treat communications from unconfigured SGSNs
in one of the following ways:
|
| Ga Interface Configuration | |
| Ga interface name | An
identification string from 1 to 79 characters (alpha and/or
numeric) by which the interface will be recognized by the
system.
Multiple names are needed if multiple interfaces will be configured. |
| IP address and subnet | These
will be assigned to the Ga interface.
Multiple addresses and/or subnets are needed if multiple interfaces will be configured. |
| Physical port number | The
physical port to which the interface will be bound. Ports
are identified by the chassis slot number where the line card resides
in, followed by the number of the physical connector on
the line card. For example, port 17/1 identifies
connector number 1 on the card in slot 17.
A single physical port can facilitate multiple interfaces. |
| Physical port description | An
identification string between 1 and 79 characters (alpha
and/or numeric) by which the physical port will
be recognized by the system.
Multiple descriptions are needed if multiple ports will be used. Physical ports are configured within the source context and are used to bind logical Ga interfaces. |
| Gateway IP address | Used when configuring static routes from the Ga interface(s) to a specific network. |
| GTPP Configuration | |
| Charging gateway address | The IP address of the system's GGSN interface. |
| CGF server information | IP address: The
IP address of the CGF server to which the GGSN will send accounting
information.
Multiple CGFs can be configured. |
| Priority: If
more than on CGF is configured, this is the server's priority. It
is used to determine the rotation order of the CGFs when sending accounting
information.
The priority can be configured to any integer value from 1 to 1000. The default is 1. |
|
| Maximum number of messages: The
maximum number of outstanding or unacknowledged GTPP messages allowed
for the CGF.
The maximum number can be configured to any integer value from 1 to 256. The default is 256. |
|
| GCDR optional fields | The
following optional fields can be specified/configured in
CDRs generated by the GGSN:
|
| Network Requested PDP Context Support Configuration (optional) | |
| Activation Requirements | IP address: The
static IP address of the mobile station's for which network-requested
PDP context activation will be supported.
Up to 1000 addresses can be configured. |
| Destination context name: The name of the destination context configured on the system that contains the IP address pool containing the mobile station's static address. | |
| International Mobile Subscriber Identity (IMSI): The IMSI of the mobile station. | |
| APN: The name of the access point that will be passed to the SGSN by the GGSN for the mobile station. | |
| GSN-map node | Communications
with the HLR from the GGSN go through a GSN-map node that
performs the protocol conversion from GTPC to SS7.
The IP address of the map node must be configured. Only one GSN-map node can be configured per source context. |
Destination Context Configuration
| Required Information | Description | ||
|---|---|---|---|
| Destination context name | An identification string from 1 to 79 characters
(alpha and/or numeric) by which the destination context will be recognized by
the system.
|
||
| APN Configuration | |||
| APN name | An identification string by which the APN will be
recognized by the system. The name can be from 1 to 62 alpha and/or numeric
characters and is not case sensitive. It may also contain dots ( . ) and/or
dashes ( - ).
Multiple names are needed if multiple APNs will be used. |
||
| Accounting mode | Selects the accounting protocol. GTPP or RADIUS
are supported. In addition, accounting can be completely disabled. The default
is to perform accounting using GTPP.
|
||
| Authentication protocols used | Specifies how the system handles authentication: using a protocol (such as CHAP, PAP, or MSCHAP), or not requiring any authentication. | ||
| APN charging characteristics (CC) (optional) | Specifies whether or not the GGSN accepts the CC
from the SGSN for home, visiting, and roaming subscribers.
By default the GGSN accepts the CC from the SGSN for all three scenarios. If the GGSN is to use its own CC for any of these scenarios, then each scenario requires the specification of behavior bits and a profile index to use.
|
||
| Domain Name Service (DNS) information (optional) | If DNS will be used for the APN, IP addresses can be configured for primary and secondary DNS servers. | ||
| IP address allocation method | Specifies how sessions facilitated by this APN
will receive an IP address. IP addresses can be assigned using one of the
following methods:
By default, the system is configured to either dynamically assign addresses from a local pool and/or allow static addresses. |
||
| IP address pool name | If addresses will be dynamically assigned from a locally configured private pool, the name of the pool must be configured. If no name is configured, the system will automatically use any configured public pool. | ||
| IP destination context name | The name of the system destination context to use for subscribers accessing the APN. If no name is specified, the system automatically uses the system context in which the APN is configured. | ||
| Maximum number of PDP contexts | The maximum number of PDP contexts that are
supported for the APN.
The maximum number can be configured to any integer value from 1 to 1500000. The default is 1000000. |
||
| PDP type | The type of PDP contexts supported by the APN. The type can be IPv4, IPv6, both IPv4 and IPv6, or PPP. IPv4 support is enabled by default. For IPv6 PDP configuration, at least one IPv6 interface needs to be configured in the destination context. | ||
| Verification selection mode | The level of verification that will be used to
ensure a MS's subscription to use the APN. The GGSN uses any of the following
methods:
|
||
| DHCP Interface Configuration (optional) | |||
| DHCP interface name | An identification string from 1 to 79 characters
(alpha and/or numeric) by which the interface will be recognized by the system.
Multiple names are needed if multiple interfaces will be configured. |
||
| IP address and subnet | These will be assigned to the DHCP interface and
be bound to the DHCP service.
Multiple addresses and/or subnets are needed if multiple interfaces will be configured. |
||
| Gateway IP address | Used when configuring static routes from the DHCP interface(s) to a specific network. | ||
| Physical port number | The physical port to which the interface will be
bound. Ports are identified by the chassis slot number where the line card
resides in, followed by the number of the physical connector on the line card.
For example, port 17/1 identifies connector number 1 on the card in slot 17.
A single physical port can facilitate multiple interfaces. |
||
| Physical port description | An identification string from 1 to 79 characters
(alpha and/or numeric) by which the physical port will be recognized by the
system.
Multiple descriptions are needed if multiple ports will be used. Physical ports are configured within the source context and are used to bind logical DHCP interfaces. |
||
| DHCP Service Configuration (optional) | |||
| DHCP Service Name | This is an identification string between 1 and 63
characters (alpha and/or numeric) by which the DHCP service will be recognized
by the system.
Multiple names are needed if multiple GGSN services will be used. |
||
| DHCP Server Information | The IP address of each DHCP server that the system
is to communicate with must be configured
.Multiple servers can be configured. If multiple servers are configured, each can be assigned a priority from 1 to 1000. The default priority is 1. |
||
| Lease Duration | Specifies the minimum and maximum allowable lease
times that are accepted in responses from DHCP servers.
|
||
| AAA Interface Configuration | |||
| AAA interface name | This is an identification string from 1 to 79
characters (alpha and/or numeric) by which the interface will be recognized by
the system.
Multiple names are needed if multiple interfaces will be configured. |
||
| IP address and subnet | These will be assigned to the AAA interface.
Multiple addresses and/or subnets are needed if multiple interfaces will be configured. |
||
| Physical port number | This specifies the physical port to which the
interface will be bound. Ports are identified by the chassis slot number where
the line card resides in, followed by the number of the physical connector on
the line card. For example, port 17/1 identifies connector number 1 on the card
in slot 17.
A single physical port can facilitate multiple interfaces. |
||
| Physical port description | This is an identification string from 1 to 79
characters (alpha and/or numeric) by which the physical port will be recognized
by the system.
Multiple descriptions are needed if multiple ports will be used. Physical ports are used to bind logical AAA interfaces. |
||
| Gateway IP address | Used when configuring static routes from the AAA interface(s) to a specific network. | ||
| RADIUS Server Configuration | |||
| RADIUS Authentication server | IP Address: Specifies the IP address of the
RADIUS authentication server the system will communicate with to provide
subscriber authentication functions.
Multiple addresses are needed if multiple RADIUS servers will be configured. If multiple servers are configured, each can be assigned a priority. |
||
| Shared Secret: The shared secret is a
string between 1 and 15 characters (alpha and/or numeric) that specifies the
key that is exchanged between the RADIUS authentication server and the source
context.
A shared secret is needed for each configured RADIUS server. |
|||
| UDP Port Number: Specifies the port used by the source context and the RADIUS authentication server for communications. The UDP port number can be any integer value between 1 and 65535. The default value is 1812. | |||
| RADIUS Accounting server (optional) | IP Address: Specifies the IP address of the
RADIUS accounting server that the source context will communicate with to
provide subscriber accounting functions.
Multiple addresses are needed if multiple RADIUS servers will be configured.RADIUS accounting servers are configured within the source context. Multiple servers can be configured and each assigned a priority. |
||
| Shared Secret: The shared secret is a
string between 1 and 15 characters (alpha and/or numeric) that specifies the
key that is exchanged between the RADIUS accounting server and the source
context.
A shared secret is needed for each configured RADIUS server. |
|||
| UDP Port Number: Specifies the port used by the source context and the RADIUS Accounting server for communications. The UDP port number can be any integer value between 1 and 65535. The default value is 1813. | |||
| RADIUS attribute NAS Identifier | Specifies the name by which the source context will be identified in the Access-Request message(s) it sends to the RADIUS server. The name must be from 1 to 32 alpha and/or numeric characters and is case sensitive. | ||
| RADIUS NAS IP address | Specifies the IP address of the system's AAA interface. A secondary address can be optionally configured. | ||
| PDN Interface Configuration | |||
| PDN interface name | This is an identification string from 1 to 79
characters (alpha and/or numeric) by which the interface will be recognized by
the system.
Multiple names are needed if multiple interfaces will be configured. PDN interfaces are configured in the destination context. |
||
| IP address and subnet | These will be assigned to the PDN interface.
Multiple addresses and/or subnets are needed if multiple interfaces will be configured. |
||
| Physical port number | This specifies the physical port to which the
interface will be bound. Ports are identified by the chassis slot number where
the line card resides in, followed by the number of the physical connector on
the line card. For example, port 17/1 identifies connector number 1 on the card
in slot 17.
A single physical port can facilitate multiple interfaces. |
||
| Physical port description(s) | This is an identification string from 1 to 79
characters (alpha and/or numeric) by which the physical port will be recognized
by the system.
Multiple descriptions will be needed if multiple ports will be used. Physical ports are configured within the destination context and are used to bind logical PDN interfaces. |
||
| Gateway IP address(es) | Used when configuring static routes from the PDN interface(s) to a specific network. | ||
| IP Address Pool Configuration | |||
| IP address pool name(s) | This is an identification string from 1 to 31
characters (alpha and/or numeric) by which the physical port will be recognized
by the system.
Multiple descriptions will be needed if multiple ports will be used. |
||
| Pool addresses, subnet mask and type | The pool can consist of either of the following:
The pool can be configured as public, private, or static. Public pools can also be assigned a priority. |
||
Feedback