> GGSN Configuration Example
> This chapter provides information for configuring the system to function as a Gateway GPRS Support Node (GGSN) in General Packet Radio Service (GPRS) or Universal Mobile Telecommunications System (UMTS) wireless data networks.
> Important: This chapter does not discuss the configuration of the local context. Information about the local context can be found in the Command Line Interface Overview chapter of the System Administration Guide and the Command Line Interface Reference.
> The most simple configuration that can be implemented on the system to support GGSN functionality requires that two contexts (one source and one destination) be configured on the system as shown in the following figure.
> The source context facilitates the following:

> • | GGSN service(s) and Gn interface to the Service GPRS Support Node (SGSN)

> • | GPRS Tunneling Protocol Prime (GTPP) configuration and Ga interface to the Charging Gateway Function (CGF)

> The destination context facilitates the following:

> • | Access Point Name (APN) configuration

> • | RADIUS authentication configuration and the interface to the authentication server

> • | DHCP configuration and the interface to the DHCP server

> • | IP address pools

> • | Gi interface to the packet data network (PDN)

> This configuration supports IP (transparent and non-transparent) and PPP PDP contexts as well as network requested PDP contexts.
> GGSN Support Using a Single Source and Destination Context
> 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
> The following table lists the information that is required to configure the source context.
> Required Information for 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:
> • | GGSN use of the accounting server specified by the profile index
> • | GGSN rejection of Create PDP Context Request messages
> • | GGSN ceases sending accounting records
> 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 number of statistics container changes is met or exceeded causing an accounting record to be closed. The number can be configured from 1 to 15. The default is 4.
> • | The up and/or downlink traffic volume limits are met or exceeded within a specific time interval causing a partial record to be generated. The up and downlink volumes can be configured from 0 to 1000000 octets. The interval can be configured from 60 to 40000000 seconds.
> • | The up and/or downlink traffic volume limits are met or exceeded causing an accounting record to be closed. The up and downlink volumes can be configured from 100000 to 4000000000 octets.
> • | The number of SGSN switchovers is met or exceeded causing an accounting record to be closed. The number can be configured from 1 to 15. The default is 4.
> • | Specific tariff times within a day are reached causing an accounting record to be closed. Up to four times can be configured using the hour of the day (1-24) and the minute (1-60).
> • | Prepaid accounting can be disabled for a specified profile index.
> 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:
> • | Treat the SGSN as if it is on a foreign PLMN
> • | Treat the SGSN as if it is on a home PLMN
> • | Reject communications from unconfigured SGSNs (default)
> 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:
> • | diagnostics
> • | duration-ms (the time specified in the mandatory Duration field is reported in milliseconds)
> • | local-record-sequence-number
> • | plmn-id
> 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
> The following table lists the information that is required to configure the destination context.
> Required Information for 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. NOTE: For this configuration, the destination context name should not match the domain name of a specific APN.
> 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. NOTE: The examples discussed in this chapter assumes GTPP is used.
> 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. NOTE: The profile index parameters are configured as part of the GGSN service.
> 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:
> • | Dynamic: Address can be dynamically assigned from one of the sources.
> • | Dynamic Host Control Protocol (DHCP) server: The system can be configured to act as a DHCP proxy and receive address from the server in advance and assign them as needed or it can relay DHCP messages from the MS.
> • | Local address pools: The system can be configured with local address pools.
> • | Static: MS IP addresses can be permanently assigned.
> 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.
> 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:
> • | No verification and MS supplies APN
> • | No verification and SGSN supplies APN
> • | Verified by SGSN (default)
> 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.
> • | Minimum Lease Time: Measured in seconds and can be configured to any integer value from 600 to 3600. The default is 600 seconds.
> • | Maximum Lease Time: Measured in seconds and can be configured to any integer value from 10800 to 4294967295. The default is 86400 seconds.
> 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:
> • | An entire subnet configured using the initial address and the subnet mask
> • | A range of addresses configured using the first and last IP addresses in the range
> The pool can be configured as public, private, or static. Public pools can also be assigned a priority.

> ‌
> How This Configuration Works
> This section provides a description of how the information detailed in the previous sections of this chapter are used in the processing of the following types of subscriber sessions:

> • | Transparent IP PDP Context Processing

> • | Non-transparent IP PDP Context Processing

> • | PPP PDP Context Processing

> • | Network-requested PDP Context Processing

> Transparent IP PDP Context Processing
> The following figure and the text that follows describe how this configuration with a single source and destination context would be used by the system to process a transparent IP PDP context.
> Transparent IP PDP Context Call Processing

> 1. | If the DHCP client mode is used for the dynamic assignment of IP addresses for subscriber PDP contexts, the system will retrieve addresses from the server over the DHCP interface during boot up and store them in cache memory.

> 2. | A Create PDP Context Request message for a subscriber session is sent from the SGSN to the GGSN service over the Gn interface. The message contains information such as the PDP Type, APN, and charging characteristics.

> 3. | The GGSN determines whether or not it is configured with an APN identical to the one specified in the message. If so, it determines how to process the session based on the configuration of the APN.

> 4. | If the MS requires a dynamically assigned address, the GGSN assigns one from those stored in its memory cache.

> 5. | The GGSN returns an affirmative Create PDP Context Response to the SGSN over the Gn interface.

> 6. | The MS sends/receives data to/from the packet data network over the GGSN’s PDN interface.

> 7. | Upon termination of the subscriber session, the GGSN sends GGSN charging detail records to the CGF using GTPP over the Ga interface.

> Non-transparent IP PDP Context Processing
> The following figure and the text that follows describe how this configuration with a single source and destination context would be used by the system to process a non-transparent IP PDP context.
> Non-transparent IP PDP Context Call Processing

> 1. | If the DHCP client mode is used for the dynamic assignment of IP addresses for subscriber PDP contexts, the system will retrieve addresses from the server over the DHCP interface during boot up and store them in cache memory.

> 2. | A Create PDP Context Request message for a subscriber session is sent from the SGSN to the GGSN service over the Gn interface. The message contains information such as the PDP Type, APN, and charging characteristics.

> 3. | The GGSN determines whether or not it is configured with an APN identical to the one specified in the message. If so, it determines how to process the session based on the configuration of the APN.

> 4. | If the MS requires a dynamically assigned address, the GGSN assigns one from those stored in its memory cache.

> 5. | If subscriber authentication is required, the GGSN authenticates the subscriber by communicating with a RADIUS server over the AAA interface.

> 6. | The GGSN returns an affirmative Create PDP Context Response to the SGSN over the Gn interface.

> 7. | The MS sends/receives data to/from the packet data network over the GGSN’s PDN interface.

> 8. | Upon termination of the subscriber session, the GGSN sends GGSN charging detail records to the CGF using GTPP over the Ga interface.

> PPP PDP Context Processing
> The following figure and the following text describe how this configuration with a single source and destination context would be used by the system to process a PPP PDP context.
> PPP PDP Context Call Processing

> 1. | If the DHCP client mode is used for the dynamic assignment of IP addresses for subscriber PDP contexts, the system will retrieve addresses from the server over the DHCP interface during boot up and store them in cache memory.

> 2. | A Create PDP Context Request message for a subscriber session is sent from the SGSN to the GGSN service over the Gn interface. The message contains information such as the PDP Type, APN, and charging characteristics.

> 3. | The GGSN determines whether or not it is configured with an APN identical to the one specified in the message. If so, it determines how to process the session based on the configuration of the APN.

> 4. | The GGSN returns an affirmative Create PDP Context Response to the SGSN over the Gn interface.

> 5. | The MS and GGSN negotiate PPP.

> 6. | The GGSN authenticates the subscriber as part of the PPP negotiation by communicating with a RADIUS server over the AAA interface.

> 7. | Upon successful authentication, the GGSN assigns an IP address to the MS from one of those stored in its memory cache.

> 8. | The MS sends/receives data to/from the packet data network over the GGSN’s PDN interface.

> 9. | Upon termination of the subscriber session, the GGSN sends GGSN charging detail records to the CGF using GTPP over the Ga interface.

> Network-requested PDP Context Processing
> The following figure and the text that follows describe how this configuration with a single source and destination context would be used by the system to process a network-requested PDP context.
> Network-requested PDP Context Call Processing

> 1. | If the DHCP client mode is used for the dynamic assignment of IP addresses for subscriber PDP contexts, the system will retrieve addresses from the server over the DHCP interface during boot up and store them in cache memory.

> 2. | An IP packet data unit (PDU) is received by the GGSN from the PDN.

> 3. | The GGSN determines if it is configured to support network-initiated sessions. If so, it begins the Network-Requested PDP Context Activation procedure, otherwise it discards the packet.

> 4. | The GGSN determines if the MS is reachable by communicating with the HLR through a MAP node over one of the Gn interfaces.

> 5. | The GGSN works with the SGSN to activate the MS.

> 6. | Once activated, the MS initiates a PDP context resulting in the sending of a Create PDP Context Request message from the SGSN to the GGSN service over the Gn interface. The message contains information such as the PDP Type, APN, and charging characteristics.

> 7. | The GGSN determines whether or not it is configured with an APN identical to the one specified in the message. If so, it determines how to process the session based on the configuration of the APN.

> 8. | If the MS requires a dynamically assigned address, the GGSN assigns one from those stored in its memory cache.

> 9. | The GGSN returns an affirmative Create PDP Context Response to the SGSN over the Gn interface.

> 10. | The MS sends/receives data to/from the packet data network over the GGSN’s PDN interface.

> 11. | Upon termination of the subscriber session, the GGSN sends GGSN charging detail records to the CGF using GTPP over the Ga interface.

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883