Managing the GSN-GSS Services


Managing the GSN-GSS Services
 
 
This chapter provides the procedures for setting up GSS support on a ASR 5000 GSN - either an SGSN or a GGSN.
To edit the GSN configuratiConfigure the IP address of the system interface within the current context usedon, you must be connected to the GSN using the standard chassis’ command line interface (CLI). The recommended access technique is via the console port on the Switch Processor I/O (SPIO) card. CLI access and use information, beyond that provided in this chapter, is available in the Command Line Interface Reference.
Procedures mentioned in this chapter must be performed at the command line of the GSN that is to communicate with a GTPP Storage Server (GSS).
 
Deployment of GSS with a GSN
This section provides information about the deployment of a gateway GPRS support node (GGSN) connecting to a GTPP storage server (GSS). For more information about the GSS deployment scenarios, refer to the GTPP Storage Server Overview chapter in this guide.
The following figure shows a typical example of a GSS deployment with a GSS connected to a GGSN.
 
GSS in the GPRS/UMTS Network
The logical source context on the GGSN facilitates:
The logical destination context on the GGSN facilitates:
 
Configuring GGSN Support for GSS
Important: Before proceeding, the GGSN must be configured for all related services, such as the GGSN service, and the GTPP accounting support which can include support for GGSN use of a CGF. For more information on the GGSN configurations and procedures, refer to the GGSN Configuration Example chapter and the Service Configuration Procedures chapter in the GGSN Administration Guide.
In order to support connectivity with a GSS, the GGSN system is configured with two new components:
Important: GSS support on the GGSN can be configured in any context other than the local context. It is recommended that GSS component support be configured in the same source context as the GGSN service(s) - see Figure 5 above.
These instructions assume that you are connected to the GGSN and are using the GGSN’s command line interface (CLI) beginning at the root prompt in the Exec mode:
[local]host_name#
Step 1
configure
The following prompt appears:
[local]host_name(config)#
Step 2
gtpp single-source [ private-extensions ] [ centralized-lsrn-creation ]
private-extensions is an optional keyword and enables the proprietary use of the customer-specific GTPP extensions.
centralized-lsrn-creation optional keyword defines the LSRN generation at proxy. With this option enabled, the eG-CDRs will skip the session manager and be sent to the AAA manager and the AAA proxy will generate the LRSN for both the G-CDRs and the eG-CDRs.
Important: If private-extensions is not configured, all the customer specific private extensions related to the GTPP message transfer with the CGF and recovery through the GSS are disabled. Additionally, this command is customer specific. Please contact your local sales representative for additional information. For detailed information, see the gtpp single-source command in the Global Configuration Mode chapter of the Command Line Interface Reference.
Step 3
context context_name
context_name is the name of the system source context designated for GTPP accounting configuration. The name must be from 1 to 79 alpha and/or numeric characters and is case sensitive.
The following prompt appears:
[<context_name>]host_name(config-ctx)#
Step 4
gtpp charging-agent address ip_address [port port]
ip_address specifies the IP address of the interface configured within the current context that is used to transmit CDRs to the CGF. It must be configured using dotted decimal notation.
port specifies the charging agent UDP port and must be followed by an integer, ranging from 1 to 65535. Default port number is 49999.
Multiple interfaces can be configured within a single context if needed.
Important: Configuring the GTPP charging-agent on port 3386 may interfere with GGSN-service configured with the same IP address.
Step 5
gtpp server ip_address [max msgs] [priority priority] [udp-port port] [node-alive { enable | disable }]
msgs can be configured to any integer value from 1 to 256. The default is 256.
priority can be configured to any integer value from 1 to 1000. The default is 1.
port can be configured to any integer value between 1 and 65535. The default is 3386.
Multiple servers can be configured within a single context if needed. Repeat this step as needed to configure connections with multiple CGFs.
Step 6
gtpp storage-server ip-address port port_num
ip_address specifies the IP address of the GSS and port_num specifies the UDP port over which the GGSN communicates with the GSS. port can be configured to any integer value between 1 and 65535.
Important: The gtpp storage-server command only takes affect if the gtpp single-source [private-extensions] in the Global Configuration Mode has also been configured in step 2 of this procedure. For more details, check these command descriptions in the Command Line Interface. Additionally, this command is customer specific and you may need to contact your local sales representative for additional information.
Step 7
gtpp max-cdrs 255 wait time 5
Step 8
gtpp storage-server max-retries max_attempts
max_attempts specifies the number of times the system attempts to communicate with a GTPP back-up storage server that is not responding and it can be configured to any integer.
Step 9
gtpp storage-server timeout duration
duration specifies the maximum amount of time the system waits for a response from the GTPP back-up storage server before assuming the packet is lost. duration is measured in seconds and can be configured to any integer value from 30 to 120.
Step 10
Repeat step 3 through step 8 as needed to configure multiple GSSs with or without CGF.
Step 11
gtpp dictionary { custom1 | custom10 | custom11 | custom12 | custom13 | custom14 | custom15 | custom16 | custom17 | custom18 | custom19 | custom2 | custom20 | custom3 | custom4 | custom5 | custom6 | custom7 | custom8 | custom9 | standard }
For information on the GTPP dictionaries, refer to the G-CDR and Enhanced G-CDR Field Reference Tables chapter of the AAA Interface Administration and Reference.
Step 12
gtpp attribute { diagnostics | duration-ms | node-id-suffix STRING | local-record-sequence-number | plmn-id }
 
STRING: This is the configured Node-ID-Suffix having any string between 1 to 16 characters.
n: The first digit is the Session manager restart counter having a value between 0..7.
ddd: The number of sessmgr instances.
Uses the specified NodeID-suffix in all CDRs. The “Node-ID” field consists of sessMgr Recovery counter (1 digit) n + AAA Manager identifier (3 digits) ddd + the configured Node-Id-suffix (1 to 16 characters) STRING.
Important: If this node-id-suffix is not configured, the GGSN uses the GTPP context name as the Node-id-suffix (truncated to 16 characters).
Step 13
end
The following prompt appears:
[local]host_name#
Step 14
show configuration | grep gtpp
Step 15
show gtpp accounting servers
Step 16
show gtpp storage-server [ counters | statistics | status [ verbose ] ] [ | { grepgrep_options | more } ] ] | } ]
Important: For more commands and keywords to configure GTPP, CGF and related feature, refer to the Command Line Interface Reference and the GGSN Configuration Example chapter in the GGSN System Administration Guide.
Step 17
Save this modified GGSN system configuration as described in the Saving the GSN Configuration section in this chapter.
 
Configuring SGSN Support for GSS
Important: Before proceeding, the SGSN must be configured for all related services, such as the SGSN service, and the GTPP accounting support which can include support for the SGSN use of a CGF. For more information on the SGSN configurations and procedures, refer to the SGSN Configuration Example chapter and the Service Configuration Procedures chapter in the SGSN Administration Guide.
In order to support connectivity with a GSS, the SGSN system is configured with two new components:
Important: GSS support on the SGSN can be configured in any context other than the local context. It is recommended that GSS component support be configured in the accounting context .
These instructions assume that you are connected to the SGSN and are using the SGSN’s command line interface (CLI) beginning at the root prompt in the Exec mode:
[local]host_name#
Step 1
configure
The following prompt appears:
[local]host_name(config)#
Step 2
gtpp single-source [ private-extensions ] [ centralized-lsrn-creation ]
private-extensions is an optional keyword and enables the proprietary use of the customer-specific GTPP extensions.
centralized-lsrn-creation optional keyword defines the LSRN generation at proxy. With this option enabled, the S-CDRs or M-CDRs will skip the session manager and be sent to the If private-extensions is not configured, all the customer specific private extensions related to the GTPP message transfer with the CGF and recovery through the GSS are disabled. Additionally, this command is customer specific. Please contact your local sales representative for additional information. For detailed information, see the gtpp single-source command in the Global Configuration Mode chapter of the Command Line Interface Reference.
Step 3
context accounting_context
The context name must be from 1 to 79 alpha and/or numeric characters and it is case sensitive.
The following prompt appears:
[accounting_context]host_name(config-ctx)#
Step 4
gtpp charging-agent address ip_address [port port]
ip_address specifies the IP address of the interface configured within the current context that is used to transmit CDRs to the CGF. It must be configured using dotted decimal notation.
port specifies the charging agent UDP port and must be followed by an integer, ranging from 1 to 65535. Default port number is 49999.
Multiple interfaces can be configured within a single context if needed.
Important: Configuring the GTPP charging-agent on port 3386 may interfere with SGSN-service configured with the same IP address.
Step 5
gtpp server ip_address [ max msgs ] [ priority priority] [ udp-port port ] [ node-alive { enable | disable } ]
 
msgs can be configured to any integer value from 1 to 256. The default is 256.
priority can be configured to any integer value from 1 to 1000. The default is 1.
port can be configured to any integer value between 1 and 65535. The default is 3386.
Multiple servers can be configured within a single context if needed. Repeat this step as needed to configure connections with multiple CGFs.
Step 6
gtpp storage-server ip-address port port_num
ip_address specifies the IP address of the GSS and port_num specifies the UDP port over which the SGSN communicates with the GSS. port can be configured to any integer value between 1 and 65535.
Important: The gtpp storage-server command only takes affect if the gtpp single-source [private-extensions] in the Global Configuration Mode has also been configured in step 2 of this procedure. For more details, check these command descriptions in the Command Line Interface. Additionally, this command is customer specific and you may need to contact your local sales representative for additional information.
Step 7
gtpp max-cdrs 255 wait time 5
Step 8
gtpp storage-server max-retries max_attempts
max_attempts specifies the number of times the system attempts to communicate with a GTPP back-up storage server that is not responding and it can be configured to any integer.
Step 9
gtpp storage-server timeout duration
duration specifies the maximum amount of time the system waits for a response from the GTPP back-up storage server before assuming the packet is lost. duration is measured in seconds and can be configured to any integer value from 30 to 120.
Step 10
Repeat step 3 through step 8 as needed to configure multiple GSSs with or without CGF.
Step 11
gtpp dictionary { custom1 | custom10 | custom11 | custom12 | custom13 | custom14 | custom15 | custom16 | custom17 | custom18 | custom19 | custom2 | custom20 | custom3 | custom4 | custom5 | custom6 | custom7 | custom8 | custom9 | standard }
For information on the GTPP dictionaries, refer to the SGSN and Mobility Management Charging Detail Record Field Reference Tables chapter of the AAA Interface Administration and Reference.
Step 12
gtpp attribute { diagnostics | duration-ms | node-id-suffix STRING | local-record-sequence-number | plmn-id }
 
STRING: This is the configured Node-ID-Suffix having any string between 1 to 16 characters.
n: The first digit is the Session manager restart counter having a value between 0..7.
ddd: The number of sessmgr instances. Uses the specified NodeID-suffix in all CDRs.
The "Node-ID" field is consists of sessMgr Recovery counter (1 digit) n + AAA Manager identifier (3 digits) ddd + the configured Node-Id-suffix (1 to 16 characters) STRING.
Important: If this node-id-suffix is not configured, the GGSN uses the GTPP context name as the Node-id-suffix (truncated to 16 characters).
Step 13
end
The following prompt appears:
[local]host_name#
Step 14
show configuration | grep gtpp
Step 15
show gtpp accounting servers
Step 16
show gtpp storage-server [ counters | statistics | status [ verbose ] ] [ | { grep grep_options | more } ]
Important: For more commands and keywords to configure GTPP, CGF and related feature, refer to the Command Line Interface Reference and the SGSN Configuration Example chapter in the SGSN System Administration Guide.
Step 17
Save this modified SGSN system configuration as described in the Saving the GSN Configuration section in this chapter.
 
Saving the GSN Configuration
After modifying the GSN system configuration to include support for GSN-GSS services, the GSN configuration information can be saved to a file locally (on the GSN) or to a remote node on the network. This file is known as a configuration file and can also be used on any other systems that require the same configuration.
Files saved locally can be stored in the CompactFlash on the SPC/SMC or on a PCMCIA memory card installed in either slot 1 or 2 of the SPC/SMC. Files that are saved to a remote network node can be transmitted using either FTP or TFTP.
These instructions assume that you are at the prompt for the Exec mode in the chassis’ CLI -
[local]host_name#
To save your configuration, enter the following command:
save configuration url [-redundant] [-noconfirm] [showsecrets] [verbose]
 
Important: Use of the SMC hard drive as an option is not supported in this release.
port# is the network server’s logical port number. Defaults are:
Important: host_name can only be used if the networkconfig parameter is configured for DHCP and the DHCP server returns a valid nameserver.dx.
username is the username required to gain access to the server if necessary.
password is the password for the specified username if required.
/directory specifies the directory where the file is located if one exists.
/file_name specifies the name of the configuration file to be saved.
Important: Configuration files should be named with a .cfg extension.
Important: This keyword will only work for local devices that are located on both the active and standby SPCs/SMCs. For example, if you save the file to the /pcmcia1 device on the active SPC, that same type of device (a PC-Card in Slot 1 of the standby SPC) must be available. Otherwise, a failure message is displayed. If saving the file to an external network (non-local) device, the system disregards this keyword.
Important: This keyword does not synchronize the local file system. If you have added, modified, or deleted other files or directories to or from a local device for the active SPC/SMC, then you must synchronize the local file system on both SPCs/SMCs.
To save a configuration file called system.cfg to a directory that was previously created on the SPC/SMC CompactFlash called cfgfiles, enter the following command:
save configuration /flash/cfgfiles/system.cfg
To save a configuration file called simple_ip.cfg to a directory called host_name_configs using an FTP server with an IP address of 192.168.34.156 on which you have an account administrator and password secure, enter the following command:
save configuration ftp://administrator:secure@192.168.34.156/host_name_configs/simple_ip.cfg
To save a configuration file called init_config.cfg to the root directory of a TFTP server with a hostname of config_server, enter the following command:
save configuration tftp://config_server/init.config.cfg
 
 
 
 

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