> GTPP Server Group Configuration Mode Commands
> The GTPP Server Group Configuration Mode is used to create and manage the GTPP server groups within the context or system.
> GTPP server group commands facilitate the setup of the SMC hard disk for CDR storage. As well, for accounting and charging functionality within a context, these commands can be used to configure the management of a group (list) of charging gateway function (CGF) servers on a per subscriber or per GGSN APN level.
> In this mode, your prompt will be similar to [context_name]hostname(config-gtpp-group)#
> gtpp attribute
> Enables the specification of some of the optional fields in the CDRs that the GSN (GGSN or SGSN) generates and/or how the information is to be presented.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp attribute { camel-info | cell-plmn-id | diagnostics | duration-ms | imei | local-record-sequence-number | msisdn | node-id-suffix STRING | plmn-id | rat | record-extensions rat | sms { destination-number | recording-entity | service-centre } } +
> default gtpp attribute { cell-plmn-id | diagnostics | duration-ms | imei | local-record-sequence-number | msisdn | plmn-id | rat | record-extensions rat | sms { destination-number | recording-entity | service-centre } }
> no gtpp attribute { cell-plmn-id | diagnostics | duration-ms | imei | local-record-sequence-number | msisdn | node-id-suffix | plmn-id | rat | record-extensions rat | sms { destination-number | recording-entity | service-centre } }
> default
> Resets the default attribute values for this GTPP group configuration.
> no
> Disables the specified optional field so that the information will not be present in generated CDRs.
> camel-info
> SGSN only
> Default: Disabled
> Enter this keyword to include CAMEL-specific fields in SGSN CDRs.
> cell-plmn-id
> SGSN only
> Default: Disabled
> Enter this keyword to enable the system to include the Cell PLMN ID field in the M-CDR.
> diagnostics
> Default: Disabled
> Enter this keyword to enable the system to include the Diagnostic field in the CDR that is created when PDP contexts are released. The field will include one of the following values:

> • | 26 - For GGSN: if the GGSN sends “delete PDP context request” for any other reason (e.g., the operator types “clear subscribers” on the GGSN). For SGSN: The SGSN includes this cause code in the S-CDR to indicate that a secondary PDP context activation request or a PDP context modification request has been rejected due to insufficient resources.

> • | 36 - For GGSN: this cause code is sent in the G-CDR to indicate the PDP context has been deactivated in the GGSN due to the SGSN having sent a “delete PDP context request” to the GGSN. For SGSN, this cause code is used to indicate a regular MS or network-initiated PDP context deactivation.

> • | 37 - when the network initiates a QoS modification, the SGSN sends in the S-CDR to indicate that the MS initiation deactivate request message has been rejected with QoS not accepted as the cause.

> • | 38 - if the GGSN sends “delete PDP context request” due to GTP-C/GTP-U echo timeout with SGSN. If the SGSN sends this cause code, it indicates PDP context has been deactivated due to path failure, specifically GTP-C/GTP-U echo timeout.

> • | 39 - SGSN only - this code indicates the network (GGSN) has requested a PDP context reactivation after a GGSN restart.

> • | 40 - if the GGSN sends “delete PDP context request” due to receiving a RADIUS Disconnect-Request message.

> duration-ms
> Default: Disabled
> Specifies that the information contained in the mandatory Duration field be reported in milliseconds instead of seconds (as the standards require).
> imei
> Default: Disabled
> For SGSN: includes the IMEI value in the S-CDR.
> For GGSN: includes the IMEISV value in the G-CDR.
> local-record-sequence-number
> Default: Disabled
> This keyword provides both the local record sequence number and the Node ID. In the x-CDRs, this field indicates the number of CDRs generated by the node and is unique within the session manager.
> The Node ID field is included in the x-CDR for any of several reasons, such as when PDP contexts are released or if partial-CDR is generated based on configuration. The field will consist of a AAA Manager identifier automatically appended to the name of the SGSN or GGSN service.
> The name of the SGSN or GGSN service may be truncated, because the maximum length of the Node ID field is 20 bytes. Since each AAA Manager generates CDRs independently, this allows the Local Record Sequence Number and Node ID fields to uniquely identify a CDR.
> Important: If this keyword is enabled and the gtpp centralized-lrsn-creation option is enabled with the gtpp single-source centralized-lrsn command, then the Node ID format changes as follows. <1-byte-AAAproxy-restart-counter> <3-byte AAAproxy instance number> <node-id-suffix> If “centralized-lrsn-creation” is not enabled, then node-id format for CDRs generated by Sessmgr is as follows. <1-byte Sessmgr restart-value> <3-byte Sessmgr instance number> <node-id-suffix> If “centralized-lrsn-creation” is not enabled, then node-id format for CDRs generated by ACSMGR is as follows. <1-byte ACSmgr restart-value> <3-byte ACSmgr instance number> <Active charging service-name>
> msisdn
> Default: Enabled
> For SGSN: includes the MSISDN value in the S-CDR.
> For GGSN: includes the MSISDN value in the G-CDR.
> node-id-suffix STRING
> Default: Disabled
> Specifies the string suffix to use in the NodeID field of GTPP CDRs. Each Session Manager task generates a unique NodeID string per GTPP context.
> STRING: This is the configured Node-ID-Suffix having any string between 1 to16 characters.
> Important: The NodeID field is a printable string of the ndddSTRING format: n: The first digit is the Sessmgr restart counter having a value between 0 and 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. If the centralized LRSN feature is enabled, the “Node-ID” field will consist of only the specified NodeID-suffix (NodeID-prefix is not included). If this option is not configured, then GTPP group name will be used instead (For default GTPP groups, context-name will be used).
> 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) and the SGSN uses the GTPP group named as the node-id-suffix.
> plmn-id [ unknown-use ]
> Default: Enabled
> For SGSN, reports the SGSN PLMN Identifier value (the RAI) in the S-CDR provided if the dictionary supports it.
> For GGSN, reports the SGSN PLMN Identifier value (the RAI) in the G-CDR if it was originally provided by the SGSN in the GTP create PDP context request. It is omitted if the SGSN does not supply one.
> Normally when SGSN PLMN-id information is not available, the attribute sgsnPLMNIdentifier is not included in the CDR. This keyword enables the inclusion of the sgsnPLMNIdentifier with a specific value when the SGSN PLMN-id is not available.
> unknown-use hex_num: must be a hexadecimal number from 0x0 through 0xFFFFFF to identify a foreign SGSN that has not provided a PLMN-id. For GGSN only.
> rat
> Default: Enabled
> For SGSN: includes the RAT (identifies the radio access technology type) value in the S-CDR.
> For GGSN: includes the RAT (identifies the radio access technology type) value in the G-CDR.
> record-extensions rat
> Default: Disabled
> Enables network operators and/or manufacturers to add their own recommended extensions to the CDRs according to the standard record definitions from 3GPP TS 32.298 Release 7 or higher.
> sms { destination-number | recording-entity | service-centre }
> This keyword is specific to the SGSN.
> Entering this keyword causes the inclusion of an SMS-related field in the SMS-MO-CDR or SMS-MT-CDR.
> destination-number - Entering this option includes the "destinationNumber" field in the SMS-MO-CDR or SMS-MT-CDR.
> recording-entity - Entering this option includes the "recordingEntity" field in the SMS-MO-CDR or SMS-MT-CDR.
> service-centre - Entering this option includes the "serviceCentre" field in the SMS-MO-CDR or SMS-MT-CDR.
> +
> Indicates that this command can be entered multiple times to configure multiple attributes.
> Usage
> This command dictates some of the optional information fields that should be reported in CDRs generated by the GGSN. In addition, it controls how the information for some of the mandatory fields are reported.
> Fields described as optional by the standards but not listed above will always be present in the CDRs, except for Record Extensions (which will never be present).
> Example
> The following command dictates that the time provided in the Duration field of the CDR is reported in milliseconds:
> gtpp attribute duration-ms
> gtpp charging-agent
> Configures the IP address and port of the system interface within the current context used to communicate with the CGF or the GSS.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp charging-agent address ip_address [ port port ]
> no gtpp charging-agent
> no
> Removes a previously configured charging agent address.
> address ip_address
> Specifies the IP address of the interface configured within the current context that is used to transmit G-CDR records to the CGF or the GSS.
> ip_address must be configured using dotted decimal notation.
> port port
> It is an optional parameter. It specifies the Charging Agent UDP port. If port is not defined, the IP will take the default port number 49999.
> Default: 49999
> port must be followed by an integer, ranging from 1 to 65535.
> Important: Configuring GTPP charging-agent on port 3386 may interfere with ggsn-service configured with the same ip address.
> Usage
> This command can be used to establish a UDP interface to connect to the GSS or this command can establish a Ga interface to connect to the CFG. These interfaces must exist in the same context in which GTPP functionality is configured (refer to the gtpp commands in this chapter).
> This command instructs the system as to what interface to use. The IP address supplied is also the address by which the GGSN/SGSN is known to the CGF or the GSS. Therefore, the IP address used for the Ga or UDP interface could be identical to one bound to a GGSN/SGSN service (a Gn interface).
> If no GGSN/SGSN services are configured in the same context as the Ga/UDP interface, the address configured by this command is used to receive unsolicited GTPP packets.
> Example
> The following command configures the system to use the interface with an IP address of 192.168.13.10 as the accounting interface with port 20000 to the CGF:
> gtpp charging-agent address 192.168.13.10
> gtpp charging-agent address 192.168.13.10 port 20000
> gtpp data-request sequence-numbers
> Configures the range of sequence numbers to be used in the GTPP data record transfer record (DRT). Use this command to set the start value for the sequence number.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp data-request sequence-numbers start { 0 | 1 }
> default gtpp data-request sequence-numbers start
> default
> Default is 0 (zero).
> start { 0 | 1 }
> Specifies the value of the start sequence number for the GTPP Data Record Transfer Request. Default: 0

> • | 0: Designates the start sequence number as 0.

> • | 1: Designates the start sequence number as 1.

> Usage
> When the GGSN/SGSN is configured to send GTPP echo request packets, the SGSN always uses 0 as the sequence number in those packets. Re-using 0 as a sequence number in the DRT packets is allowed by the 3GPP standards; however, this CLI command ensures the possibility of inter-operating with CGFs that can not properly handle the re-use of sequence number 0 in the echo request packets.
> Example
> The following command sets the sequence to start at 1.
> gtpp data-request sequence-numbers start 1
> gtpp deadtime
> Configures the amount of time the GGSN/SGSN waits before attempting to communicate with a CGF that was previously marked as unreachable (non-responsive).
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp deadtime time
> default deadtime
> default
> Resets the deadtime to the default of 120 seconds.
> time
> Default: 120
> Specifies the amount of time that must elapse before the system attempts to communicate with a CGF that was previously unreachable.
> time is measured in seconds and can be configured to any integer value from 1 to 65535.
> Usage
> If the system is unable to communicate with a configured CGF, after a pre-configured number of failures the system marks the CGF as being down.
> This command specifies the amount of time that the system waits prior to attempting to communicate with the downed CGF.
> Refer to the gtpp detect-dead-server and gtpp max-retries commands for additional information on the process the system uses to mark a CGF as down.
> Example
> The following command configures the system to wait 60 seconds before attempting to re-communicate with a CGF that was marked as down:
> gtpp deadtime 60
> gtpp dead-server suppress-cdrs
> This command configures the action the GGSN or the SGSN will take on CDRs generated during a communication failure between the GGSN or the SGSN and the GTPP servers.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> [ no | default ] gtpp dead-server suppress-cdrs
> no
> Removes the suppression instruction from the configuration and sets the CDR suppression mode as disabled.
> default
> Resets the GGSN or the SGSN to the default mode: disable suppression of CDRs when GTPP server detected as “dead” or unreachable.
> Usage
> For the GGSN: This command works in conjunction with the gtpp detect-dead-server to set an action when a communication failure is detected between the GGSN and a configured GTPP server. It disables the archiving of CDRs on the system when the GTPP server is unreachable or dead.
> For the GGSN and the SGSN: Typically, duing a communication or server failure, the GGSN or SGSN retains the GTPP requests until the system buffer runs out of resources. This command enables suppression of the CDRs, so with this command the GGSN or the SGSN will start purging all CDRs associated with this GTPP group as soon as the GGSN/SGSN detects that the GTPP server is down or that a communication failure has occurred. The CDRs generated, for the period while the server is down/unreachable, will also be purged.
> Example
> The following command configures the system to start purging CDRs when a communication failure with a server is detected:
> gtpp dead-server suppress-cdrs
> gtpp detect-dead-server
> Configures the number of consecutive communication failures that could occur before the system marks a CGF as ‘dead’ (unreachable).
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp detect-dead-server consecutive-failures max_number
> default gtpp detect-dead-server consecutive-failures
> default
> Resets the system to the default number of consecutive failures.
> consecutive-failures max_number
> Default: 5
> Specifies the number of failures that could occur before marking a CGF as down. If 0 (zero) is the value entered, then the system will mark the CGF as dead after a single instance of max-retries has been attempted with no success, regardless of configured deadtime.
> max_number could be configured to any integer value from 0 to 1000.
> Usage
> This command works in conjunction with the gtpp max-retries parameter to set a limit to the number of communication failures that can occur with a configured CGF.
> The gtpp max-retries parameter limits the number of attempts to communicate with a CGF. Once that limit is reached, the system treats it as a single failure. The gtpp detect-dead-server parameter limits the number of consecutive failures that can occur before the system marks the CGF as down and communicate with the CGF of next highest priority.
> If all of the configured CGFs are down, the system ignores the detect-dead-server configuration and attempt to communicate with highest priority CGF again.
> If the system receives a GTPP Node Alive Request, Echo Request, or Echo Response message from a CGF that was previously marked as down, the system immediately treats it as being active.
> Refer to the gtpp max-retries command for additional information.
> Example
> The following command configures the system to allow 8 consecutive communication failures with a CGF before it marks it as down:
> gtpp detect-dead-server consecutive-failures 8
> gtpp dictionary
> This command designates specific dictionary used by GTPP for specific context.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp dictionary { custom1 | custom10 | custom11 | custom12 | custom13 | custom14 | custom15 | custom16 | custom17 | custom18 | custom19 | custom20 | custom21 | custom22 | custom23 | custom24 | custom25 | custom26 | custom27 | custom28 | custom29 | custom3 | custom30 | custom31 | custom32 | custom33 | custom34 | custom35 | custom36| custom37 | custom38 | custom39 | custom4 | custom40 | custom5 | custom6 | custom7 | custom8 | custom9 | standard }
> default gtpp dictionary
> default
> Configures the default dictionary.
> custom1
> Custom-defined dictionary. It conforms to TS 32.015 v 3.6.0 for R99. It supports the encoding of IP addresses in text format for G-CDRs.
> custom2
> Custom-defined dictionary.
> custom3
> Custom-defined dictionary. It conforms to TS 32.015 v 3.6.0 for R99 but it does support the encoding of IP addresses in binary format for CDRs.
> custom4
> Custom-defined dictionary. It conforms to TS 32.015 v 3.6.0 for R99 except that:

> • | the Data Record Format Version information element contains 0x1307 instead of 0x1308

> • | “QoSRequested” is not present in the LoTV containers

> • | “QoSnegotiated” is added only for the first container and the container after a QoS change

> custom5 ... custom20
> Custom-defined dictionaries.
> custom21 ... custom25
> Custom-defined dictionaries for GGSN only.
> custom26
> Custom-defined dictionary for customization of G-CDR records for GGSN only. This is compliant to 3GPP TS 32.298 (R6 v 6.5.0) for proprietory fields and encoding.
> custom27
> Custom-defined dictionary for customization of S-CDR records for SGSN only. This is compliant to 3GPP TS 32.298 (R6 v 6.6.0) for propriet fields and encoding.
> custom28 ... custom30
> Custom-defined dictionaries for GGSN only.
> custom31 ... custom40
> Custom-defined dictionaries based on 3GPP 32.298 v6.4.1 for SGSN only.

> • | custom31: Custom-defined dictionary for S-CDR encoding. Includes a field appended for PLMN-ID.

> • | custom33: Custom-defined dictionary for S-CDR encoding. Includes a field appended for PLMN-ID and does not support diagnostic or SGSN-change fields.

> standard
> Default: Enabled
> A dictionary conforming to TS 32.215 v 4.6.0 for R4 (and also R5 - extended QoS format).
> Usage
> Use this command to designate specific dictionary used by GTPP for specific context.
> Example
> The following command configures the system to use custom3 dictionary to encode IP address in Binary format in G-CDRs:
> gtpp dictionary custom3
> gtpp duplicate-hold-time
> This command configures the number of minutes to hold onto CDRs that are possibly duplicates while waiting for the primary CGF to come back up.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp duplicate-hold-time minutes minutes
> default gtpp duplicate-hold-time
> default
> Resets the configuration to the default value of 60 minutes for the duplicate hold time.
> minutes
> When the primary CGF is down, the number of minutes to hold onto CDRs that may be duplicates. minutes must be an integer from 1 to 10080. Default is 60.
> Usage
> Use this command to configure how long to hold onto CDRs, that are possibly duplicates, while waiting for the primary CGF to come back up. If the GGSN determines that the primary CGF is down, CDRs that were sent to the primary CGF, but not acknowledged, are sent by the GGSN to the secondary CGF as “possibly duplicates”. When the primary CGF comes back up, the GGSN uses GTPP to determine whether the possibly duplicate CDRs were received by the primary CGF. Then the secondary CGF is told whether to release or cancel those CDRs. This command configures how long the system should wait for the primary CGF to come back up. As soon as the configured time expires, the secondary CGF is told to release all of the possibly duplicate CDRs.
> Example
> Use the following command to set the amount of time to hold onto CDRs to 2 hours (120 minutes):
> gtpp duplicate-hold-time minutes 120
> gtpp echo-interval
> Configures the frequency at which the system sends GTPP echo packets to configured CGFs.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp echo-interval time
> { default | no } gtpp echo-interval
> default
> Resets the configuration to the default echo-interval of 60 seconds.
> no
> Disables the use of the echo protocol except for the scenarios described in the Usage section for this command.
> time
> Specifies the number of seconds for sending GTPP echo packets.
> time must be an integer from 60 to 3600. Default: 60
> Usage
> The GTPP echo protocol is used by the system to ensure that it can communicate with configured CGFs. The system initiates this protocol for each of the following scenarios:

> • | Upon system boot

> • | Upon the configuration of a new CGF server on the system using the gtpp server command as described in this chapter

> • | Upon the execution of the gtpp test accounting command as described in the Exec Mode Commands chapter of this reference

> • | Upon the execution of the gtpp sequence-numbers private-extensions command as described in this chapter

> The echo-interval command is used in conjunction with the gtpp max-retries and gtpp timeout commands as described in this chapter.
> In addition to receiving an echo response for this echo protocol, if we receive a GTPP Node Alive Request message or a GTPP Echo Request message from a presumed dead CGF server, we will immediately assume the server is active again.
> The alive/dead status of the CGFs is used by the AAA Managers to affect the sending of CDRs to the CGFs. If all CGFs are dead, the AAA Managers will still send CDRs, (refer to the gtpp deadtime command), albeit at a slower rate than if a CGF were alive. Also, AAA Managers independently determine if CGFs are alive/dead.
> Example
> The following command configures an echo interval of 120 seconds:
> gtpp echo-interval 120
> gtpp egcdr
> Configures the eG-CDR parameters and triggers.
> Product
> GGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp egcdr { final-record [ [ include-content-ids { all | only-with-traffic } ] [ closing-cause { same-in-all-partials | unique } ] ] | losdv-max-containers max_losdv_containers | lotdv-max-containers max_lotdv_containers | service-data-flow threshold { interval interval | volume { downlink bytes [ uplink bytes ] | total bytes | uplink bytes [ downlink bytes ] } } | service-idle-timeout { 0 | service_idle_timeout } }
> default gtpp egcdr { final-record include-content-ids only-with-traffic closing-cause same-in-all-partials | losdv-max-containers | lotdv-max-containers | service-idle-timeout 0 }
> no gtpp egcdr service-data-flow threshold { interval | volume { downlink [ uplink ] | total | uplink [ downlink ] } }
> final-record [ [ include-content-ids { all | only-with-traffic } ] [ closing-cause { same-in-all-partials | unique } ] ]
> Enables configuration of the final eG-CDR.

> • | include-content-ids: Controls which content-ids are being included in the final eG-CDR.

> • | all: Specifies that all content-ids be included in the final eG-CDR.

> • | only-with-traffic: Specifies that only content-ids with traffic be included in the final eG-CDRs.

> • | closing-cause: Configures closing cause for the final eG-CDR.

> • | same-in-all-partials: Specifies that the same closing cause is to be included for multiple final eG-CDRs.

> • | unique: Specifies that the closing cause for final eG-CDRs is to be unique.

> losdv-max-containers max_losdv_containers
> The maximum number of List of Service Data Volume (LoSDV) containers in one eG-CDR.
> max_losdv_containers must be an integer from 1 through 255.
> Default: 10
> lotdv-max-containers max_lotdv_containers
> The maximum number of List of Traffic Data Volume (LoTDV) containers in one eG-CDR.
> max_lotdv_containers must be an integer from 1 through 8.
> Default: 8
> service-data-flow threshold { interval interval | volume { downlink bytes [ uplink bytes ] | total bytes | uplink bytes [ downlink bytes ] } }
> Configures the thresholds for closing a service data flow container within an eG-CDR.

> • | interval interval: Specifies the time interval, in seconds, to close the eG-CDR if the minimum time duration thresholds for service data flow containers satisfied in flow-based charging.

> interval must be an integer from 60 through 40000000.
> Default: Disabled

> • | volume { downlink bytes [ uplink bytes ] | total bytes | uplink bytes [ downlink bytes ] }: Specifies the volume octet counts for the generation of the interim eG-CDRs to service data flow container in FBC.

> • | downlink bytes: Specifies the limit for the number of downlink octets after which the eG-CDR is closed.

> • | total bytes: Specifies the limit for the total number of octets (uplink+downlink) after which the eG-CDR is closed.

> • | uplink bytes: Specifies the limit for the number of uplink octets after which the eG-CDR is closed.

> • | bytes must be an integer from 10000 through 400000000.

> A service data flow container has statistics for an individual content ID. When the threshold is reached, the service data flow container is closed.
> service-idle-timeout { 0 | service_idle_timeout}
> Specifies a time period where if no data is reported for a service flow, then the service container is closed and added to eG-CDR (as part of LOSDV container list) with service condition change as ServiceIdleOut.
> 0: Specifies there is no service-idle-timeout trigger.
> service_idle_timeout must be an integer from 10 through 86,400.
> Default: 0
> Usage
> Use this command to configure individual triggers for eG-CDR generation.
> Example
> Use the following command to set the maximum number of LoSDV containers to 7:
> gtpp egcdr losdv-max-containers 7
> gtpp error-response
> This command configures the response when the system receives an error response after transmitting a DRT (data record transfer) request.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp error-response { discard-cdr | retry-request }
> default gtpp error-response
> default
> Resets the system’s configuration to the default value for error-response. Default is retry-request.
> discard-cdr
> Instructs the system to purge the request upon receipt of an error response and not to retry.
> retry-request
> Instructs the system to retry sending a DRT after receiving an error response. This is the default behavior.
> Usage
> This command configures the system’s response to receiving an error message after sending a DRT request.
> Example
> gtpp error-response discard-cdr
> gtpp max-cdrs
> Configures the maximum number of charging data records (CDRs) to be included in a packet.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp max-cdrs max_cdrs [ wait-time wait_time ]
> default gtpp max-cdrs
> default
> Sets the default configuration.
> max_cdrs
> Default: 1
> Specifies the maximum number of CDRs to insert in a single packet.
> max_cdrsmust be an integer from 1 through 255.
> wait-time wait_time
> Default: Disabled
> Configures the number of seconds the GSN waits to send the packet while accumulating CDRs as defined by max-cdr. If the wait-time interval expires before max-cdrs is reached, then this keyword over-rides and the packet is sent.
> wait_time must be an integer from 1 through 300.
> Important: wait-time interval can only be enabled if the value for max-cdrs max_cdrs is greater than 1.
> Usage
> The system places CDRs into a packet until either max-cdrs is met, wait-time times out, or the maximum PDU size, configured by the gtpp max-pdu-size command, is met.
> The gtpp max-pdu-size and the wait-time parameters take priority over max-cdrs.
> Important: This command’s configuration is ignored if CDRs are stored on an SMC hard disk.
> Example
> The following command configures the system to place a maximum of 10 CDRs in a single GTPP packet with a wait-time of 30 seconds:
> gtpp max-cdrs 10 wait-time 30
> gtpp max-pdu-size
> Configures the maximum payload size of a single GTPP packet that could be sent by the system.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp max-pdu-size pdu_size
> default gtpp max-pdu-size
> default
> Resets the default max-pdu-size of 4096.
> pdu_size
> Default: 4096
> Specifies the maximum payload size of the GTPP packet. The payload includes the CDR and the GTPP header.
> pdu_size is measured in octets and can be configured to any integer value from 1024 to 65400.
> Usage
> The GTPP packet contains headers (layer 2, IP, UDP, and GTPP) followed by the CDR. Each CDR contains one or more volume containers. If a packet containing one CDR exceeds the configured maximum payload size, the system creates and send the packet containing the one CDR regardless.
> The larger the packet data unit (PDU) size allowed, the more volume containers that can be fit into the CDR.
> The system performs standard IP fragmentation for packets that exceed the system’s maximum transmission unit (MTU).
> Important: The maximum size of an IPv4 PDU (including the IPv4 and subsequent headers) is 65,535. However, a slightly smaller limit is imposed by this command because the system’s max-pdu-size doesn't include the IPv4 and UDP headers, and because the system may need to encapsulate GTPP packets in a different/larger IP packet (for sending to a backup device).
> Example
> The following command configures a maximum PDU size of 2048 octets:
> gtpp max-pdu-size 2048
> gtpp max-retries
> Configures the maximum number of times the system attempts to communicate with an unresponsive CGF.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp max-retries max_attempts
> default gtpp max-retries
> default
> Resets the systems max-retries to the default of 4.
> max_attempts
> Default: 4
> Specifies the number of times the system attempts to communicate with a CGF that is not responding.
> max_attempts can be configured to any integer value from 1 to 15.
> Usage
> This command works in conjunction with the gtpp detect-dead-server and gtpp timeout parameters to set a limit to the number of communication failures that can occur with a configured CGF.
> When the value specified by this parameter is met, a failure is logged. The gtpp detect-dead-server parameter specifies the number of consecutive failures that could occur before the server is marked as down.
> In addition, the gtpp timeout command controls the amount of time between re-tries.
> If the value for the max-retries is met, the system begins storing CDRs in Random Access Memory (RAM). The system allocates memory as a buffer, enough to store one million CDRs for a fully loaded chassis (a maximum of one outstanding CDR per PDP context). Archived CDRs are re-transmitted to the CGF until they are acknowledged or the system’s memory buffer is exceeded.
> Refer to the gtpp detect-dead-server and gtpp timeout commands for additional information.
> Example
> The following command configures the maximum number of re-tries to be 8.
> gtpp max-retries 8
> gtpp mbms bucket
> This command configures the traffic data volume (bucket) limit of charging buckets due to QoS changes of tariff time that can occur before a G-MBMS-CDR should be closed.
> Product
> GGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp mbms buckets number
> [ no ] gtpp mbms buckets
> no
> Disables the configured traffic data volume bucket limits trigger for G-MBMS-CDR generation for MBMs user service data.
> buckets number
> Default: 4
> Specifies the number of statistics container changes due to QoS changes or tariff time that can occur before a G-MBMS-CDR should be closed.
> number can be configured to any integer value from 1 through 4.
> Usage
> Use this command to configure the traffic data volume (bucket) based G-MBMS-CDR generation triggers for MBMS user data service.
> Example
> The following command configures the bucket-based trigger to generate G-MBMS-CDRs after changes in 2 container:
> gtpp mbms buckets 2
> gtpp mbms interval
> This command configures the interval duration for interval-based triggers for GTPP MBMS Charging Data Record (G-MBMS-CDR) generation.
> Product
> GGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp mbms interval duration_sec
> no gtpp mbms interval
> no
> Disables the interval-based trigger for G-MBMS-CDR generation for MBMs user service data.
> interval duration_sec
> Default: Disabled
> Specifies the normal time duration that must elapse before closing an accounting record provided that any or all of the following conditions occur:

> • | Downlink traffic volume is reached within the time interval

> • | Tariff time based trigger occurred within the time interval

> • | Data volume (up and downlink) bucket trigger occurred within the time interval

> duration_sec is measured in seconds and can be configured to any integer value from 60 through 40,000,000.
> Usage
> Use this command to configure the G-MBMS-CDR generation triggers for MBMS user data service.
> Example
> The following command configures the interval-based trigger to generate G-MBMS-CDRs in every 60 seconds:
> gtpp mbms interval 60
> gtpp mbms tariff
> This command configures the tariff slots for tariff-based triggers for GTPP MBMS Charging Data Record (G-MBMS-CDR) generation.
> Product
> GGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp mbms tariff time1 mins hours [ time2 mins hours [ time3 mins hours [ time4 mins hours ] ] ]
> [ no ] gtpp mbms tariff
> no
> Disables the tariff-based triggers for GTPP MBMS Charging Data Record (G-MBMS-CDR) generation.
> tariff time1 mins hours [ time2 mins hours [ time3 mins hours [ time4 mins hours ] ] ]
> Default: Disabled
> Specifies time-of-day time values to close the current statistics container (but not necessarily the accounting record).
> Important: The system assumes that the billing system uses the day/date to determine if the statistics container represents an actual tariff period.
> For each of the different tariff times, the following parameters must be configured:

> • | mins: The minutes of the hour, an integer value from 0 through 59.

> • | hours: The hour of the day, an integer value from 0 through 23.

> Usage
> Use this command to configure the tariff-time-based triggers for G-MBMS-CDR generation in MBMS user data service.
> Example
> The following command configures the tariff-time-based trigger to generate G-MBMS-CDRs every day at 11 hours and 30 min:
> gtpp mbms tariff time1 30 11
> gtpp mbms volume
> This command configures the download traffic data volume based trigger for GTPP MBMS Charging Data Record (G-MBMS-CDR) generation.
> Product
> GGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp mbms volume download_bytes
> [ no ] gtpp mbms volume
> no
> Disables the configured download traffic data volume based trigger for G-MBMS-CDR generation for MBMs user service data.
> volume download_bytes
> Default: Disabled
> Specifies the threshold of downlink data volumes that must be met before a G-MBMS-CDR should be closed.
> download_bytes is the total download traffic volume measured in octets and can be configured to any integer value from 100,000 through 4,000,000,000.
> Usage
> Use this command to configure the traffic data volume (download) based G-MBMS-CDR generation triggers for MBMS user data service.
> Example
> The following command configures the traffic data volume (download) limit to trigger to generate G-MBMS-CDRs after reaching 150,000 octets:
> gtpp mbms volume download_bytes
> gtpp redirection-allowed
> Configures the system to allow/disallow the redirection of CDRs when the primary CGF is unavailable.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> [ default | no ] gtpp redirection-allowed
> default
> Resets the system to allow redirection of CDRs.
> no
> Removes the redirection definition from the configuration.
> Usage
> This command allows operators to better handle erratic network links, without having to remove the configuration of the backup server(s) via the no gtpp server command.
> This functionality is enabled by default.
> If the no gtpp redirection-allowed command is executed, the system only sends CDRs to the primary CGF. If that CGF goes down, the system will buffer the CDRs in memory until the CGF comes back or until the system runs out of buffer memory. In addition, if the primary CGF announces its intent to go down (with a GTPP Redirection Request message), the system responds to that request with an error response.
> Example
> The following command configures the system to allow the redirection of CDRs when the primary CGF is unavailable:
> default gtpp redirection-allowed
> gtpp redirection-disallowed
> This command has been obsoleted and is replaced by the gtpp redirection-allowed command.
> gtpp server
> Configures the charging gateway function (CGF) accounting server(s) with in GTPP server group that the system is to communicate with.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp server ip_address [ max msgs ] [ priority priority ] [ udp-port port ] [ node-alive { enable | disable } ] [ -noconfirm ]
> no gtpp server ip_address [ udp-port port ]
> no
> Deletes a previously configured CGF.
> ip_address
> Specifies the IP address of the CGF in dotted decimal notation for IPv4 or colon notation for IPv6.
> max msgs
> Default: 256
> Specifies the maximum number of outstanding or unacknowledged GTPP packets (from any one AAA Manager task) allowed for this CGF before the system begins buffering the packets.
> msgs can be configured to any integer value from 1 to 256.
> priority priority
> Default:1000
> Specifies the relative priority of this CGF. When multiple CGFs are configured, the priority is used to determine which CGF server to send accounting data to.
> priority can be configured to any integer value from 1 to 1000. When configuring two or more servers with the same priority you will be asked to confirm that you want to do this. If you use the -noconfirm option, you are not asked for confirmation and multiple servers could be assigned the same priority.
> udp-port port
> Default: 3386
> Specifies the UDP port over which the GGSN communicates with the CGF. port can be configured to any integer value between 1 and 65535.
> node-alive { enable | disable }
> Default: Disable.
> This optional keyword allows operator to enable/disable GGSN to send Node Alive Request to GTPP Server (i.e. CGF). This configuration can be done per GTPP Server basis.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Usage
> Use this command to configure the CGF(s) that the system sends CDR accounting data to.
> Multiple CGFs can be configured using multiple instances of this command subject to the following limits:

> • | Up to 4 CGFs can be configured in one GTPP server group

> • | Total 32 CGFs can be configured per context.

> Each configured CGF can be assigned a priority. The priority is used to determine which server to use for any given subscriber based on the routing algorithm that has been implemented. A CGF with a priority of “1” has the highest priority.
> Important: The configuration of multiple CGFs with the same IP address but different port numbers is not supported.
> Each CGF can also be configured with the maximum allowable number of unacknowledged GTPP packets. Since multiple AAA Manager tasks could be communicating with the same CGF, the maximum is based on any one AAA Manager instance. If the maximum is reached, the system buffers the packets Random Access Memory (RAM). The system allocates memory as a buffer, enough to store one million CDRs for a fully loaded chassis (a maximum of one outstanding CDR per PDP context).
> Example
> The following command configures a CGF with an IP address of 192.168.2.2 and a priority of 5.
> gtpp server 192.168.2.2 priority 5
> The following command deletes a previously configured CGF with an IP address of 100.10.35.7:
> no gtpp server 100.10.35.7
> gtpp source-port-validation
> This command configures whether the system validates the UDP source port in received GTPP messages.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> [no | default] gtpp source-port-validation
> no
> Validates the IP source address but not the UDP source port.
> default
> Restores this parameter to its default setting of enabled.
> Usage
> This command configures whether the system validates the UDP source port in received GTPP messages.
> Example
> The following command disables UDP port validation:
> no gtpp source-port-validation
> gtpp storage-server
> Configures information for the GTPP back-up storage server.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp storage-server ip_address port port_num
> no gtpp storage-server ip_address port port_num
> no
> Removes a previously configured back-up storage server.
> ip_address
> The IP address of the back-up storage server expressed in dotted decimal notation.
> port port_num
> Default: 3386
> Specifies the UDP port number over which the GGSN communicates with the back-up storage server.
> Usage
> This command identifies the connection to the GSS. One backup storage server can be configured per GTPP group.
> Example
> The following command configures a GSS with an IP address of 192.168.1.2:
> gtpp storage-server 192.168.1.2
> gtpp storage-server local file
> Configures the parameters for GTPP files stored locally on the GTPP storage server.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp storage-server local file { compression { gzip | none } | format { custom1 | custom2 | custom3 | custom4 | custom5 | custom6 | custom7 | custom8 } | name { format string [ max-file-seq-num seq_number ] | prefix prefix } | purge-processed-files [ file-name-pattern name_pattern | purge-interval purge_interval ] | rotation { cdr-count count | time-interval time [ force-file-rotation ] | volume mb size } }
> default gtpp storage-server local file { compression | format | name { format | prefix } | purge-processed-files | rotation { cdr-count | time-interval | volume } }
> no gtpp storage-server local file { purge-processed-files | rotation { cdr-count | time-interval } }
> no
> Removes a previously configured parameters for local storage of CDR files on HDD on SMC card.
> compression { gzip | none }
> Configures the type of compression to be used on the files stored locally.
> gzip — Enables Gzip file compression.
> none — Disables Gzip file compression -this is the default value.
> format custom1 .. 8
> Configures the file format to be used to format files to be stored locally.
> custom1 — File format custom1 - this is the default file format.
> custom2 to custom5 Customer specific CDR file formats.
> custom6 — File format custom6 with a block size of 8K for CDR files.
> custom7 — File format custom7 is a customer specific CDR file formate.
> custom8 — File format custom8 is a customer specific CDR file format. It uses node-id-suffix_date_time_fixed-length-seq-num.u format for file naming where:

> • | date is date in MMDDYYYYY (01312010) for mat

> • | time is time in HHMMSS (023508) format

> • | fixed-length-seq-num is the fixed length of srquence number for specific file having 6 digit counter starting from 000001 and end to 999999. Once file sequence reached to 999999 the sequence will be reset to 000001.

> name format string
> This keyword allows the format of the CDR filenames to be configured independently from the file format.so that the name format contains the file name with conversion specifications.
> string — Enter a string of 1 to 127 alphanumeric characters. The string must begin with the % (percent sign).

> • | %y: = year as a decimal number without century (range 00 to 99).

> • | %Y: = year as a decimal number with century.

> • | %m: = month as a decimal number (range 01 to 12).

> • | %d: = day of the month as a decimal number (range 01 to 31).

> • | %H: = hour as a decimal number 24-hour format (range 00 to 23).

> • | %h: = hour as a decimal number 12-hour format (range 01 to 12).

> • | %M: = minute as a decimal number (range 00 to 59).

> • | %S: = second as a decimal number (range 00 to 60). (The range is up to 60 to allow occasional leap seconds.)

> • | %Q: = File sequence number. Field width may be specified between the % and the Q .If the natural size of the field is smaller than this width, then the result string is padded (on the left) to the specified width with 0s

> • | %N: = No of CDRs in the file. Field width may be specified between the % and the N .If the natural size of the field is smaller than this width, then the result string is padded (on the left) to the specified width with 0s

> • | %%: = This field is used to add % to the CDR file name.

> • | max-file-seq-no: This can be configured optionally. It indicates the maximum value of sequence number in file name (starts from 1). Once the configured max-file-seq-no limit is reached, the sequence number will restart from 1. If no max-file-seq-no is specified then file sequence number ranges from 1- 4294967295.

> By default the above keyword is not configured (default gtpp storage-server local file name format). In which case the CDR filenames are generated based on the file format as before (maintains backward compatibility).
> name prefix prefix
> Defines the prefix to be used for the file name. By default the file name prefix would be ‘GTPP-group-name + VPN-ID’. It is possible to have a NULL value prefix where the system would enter a default, which would be group+vpn,
> prefix — Enter a string of 1 to 64 alphanumeric characters or do not enter a value (NULL).
> purge-processed-files [ file-name-pattern name_pattern | purge-interval purge_interval ]
> Default: Disabled
> Enables the GSN to periodically delete locally processed (*.p) CDR files from the HDD on the SMC card.
> Important: This option is available only when GTPP server storage mode is configured for local storage of CDRs with the gtpp storage-server mode local command and the purge-processed-files parameters is enabled.
> file-name-pattern name_pattern defines a pattern for the file name that will be used to match against the files to be purged. This means that the only files to be selected and deleted will be those with names matching this pattern and whose age (when to purge) has been specified with the existing purge-interval parameter.
> name_pattern enter a string up to 127 characters in length that can contain ‘*’ (wild card to match 0+ chars) and one or more ‘:’ (to specify alternate, synonymous with ‘|’); for example: file-name-pattern “*.P:*.dat” matches “anything.P” AND “anything.dat”
> purge-interval purge_interval provides an option for user to control the purge interval duration in minutes by setting purge_interval.
> purge_interval must be an integer from 1 through 259200.
> Default: 60 minutes
> rotation { cdr-count count | time-interval time [ force-rotation ] | volume size }
> Specifies rotation related configuration for GTPP files stored locally.
> cdr-count count - Configure the CDR count for the file rotation. Enter a value from 1000 to 65000. Default value 10000.
> time-interval time - Configure the time interval for file rotation. Enter a value in seconds ranging from 30 to 86400. Default value is 3600 seconds (1 hour).
> force-file-rotation - Force CDR file-rotation at specified interval, configured with time-interval time keyword, even if there are no CDRs generated. By default this keyword is “Disbaled”.
> volume size — Configure the file volume, in MB, for file rotation. Enter a value ranging from 2 to 40. This trigger can not be disabled. Default value is 10MB.
> Usage
> This command configures the parameters for storage of GTPP packets as files on the local server - meaning the hard disk.
> Example
> The following command configures rotation for every 1.5 hours for locally stored files.
> gtpp storage-server local file rotation time-interval 5400
> Configuring file name format along with max-file-seq-no:
> gtpp storage-server local file name format processed_2g_%Y%m%d_%5Q_%N.cdr max-file-seq-no 2345
> Configuring file name prefix with a NULL value:
> gtpp storage-server local file name prefix NULL
> Configure the file name pattern and purge interval to setup file purging from the HDD:
> gtpp storage-server local file purge-processed-files file-name-pattern *.z purge-interval 4
> gtpp storage-server max-retries
> Configures the maximum number of times the system attempts to communicate with an unresponsive GTPP back-up storage server.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp storage-server max-retries max_attempts
> default gtpp storage-server max-retries
> default
> Restores the system to the default value of 2 retry attempts.
> max_attempts
> Default: 2
> Specifies the number of times the system attempts to communicate with a GTPP back-up storage server that is not responding.
> max_attempts can be configured to any integer value from 1 to 15.
> Usage
> This command works in conjunction with the gtpp storage-server timeout parameters to set a limit to the number of communication failures that can occur with a configured GTPP back-up storage server.
> The gtpp storage-server timeout command controls the amount of time between re-tries.
> Refer to the gtpp storage-server timeout command for additional information.
> Example
> The following command configures the maximum number of re-tries to be 8.
> gtpp storage-server max-retries 8
> gtpp storage-server mode
> This command configures storage mode, local or remote, for CDRs. Local storage mode is available with ASR 5000 platforms only.
> Product
> GGSN, SGSN, P-GW, S-GW
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp storage-server mode { local | remote | streaming }
> default gtpp storage-server mode
> default
> Returns the GTPP group configuration to the default ‘remote’ value for the GTPP storage server mode.
> local
> Default: Disabled
> Specifies the use of the hard disk on the SMC for storing CDRs.
> Important: This option is available with ASR 5000 platforms only.
> remote
> Specifies the use of an external server for storing CDRs. This is the default value.
> Important: When the external server is down, the Session Managers will start buffering up to a maximum of 26400 CDRs or a total of 120 MB worth of CDRs, whichever limit reaches first. The maximum CDR limit specified is per the session manager. The chassis level limit varies depending on the number of session manager instances and number of active cards.
> streaming
> Default: Disabled
> This keyword allows the operator to configure “streaming” mode of operation for GTPP group. When this keyword is supplied the CDRs will be stored in following fashion:

> • | When GTPP link is active with CGF, CDRs are sent to a CGF via GTPP and local hard disk is NOT used as long as every record is acknowledged in time.

> • | If the GTPP connection is considered to be down, all streaming CDRs will be saved temporarily on the local hard disk and once the connection is restored, unacknowledged records will be retrieved from the hard disk and sent to the CGF.

> Important: This option is available with ASR 5000 platforms only.
> Usage
> This command configures whether the CDRs should be stored on the hard disk of the SMC or remotely, on an external server.
> Example
> The following command configures use of a hard disk for storing CDRs.
> gtpp storage-server mode local
> gtpp storage-server timeout
> Configures the amount of time that must pass with no response before the system re-attempts to communicate with the GTPP back-up storage server.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp storage-server timeout duration
> default gtpp storage-server timeout
> default
> Restores the timeout duration to the 30-second default.
> duration
> Default: 30
> 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.
> Usage
> This command works in conjunction with the gtpp storage-server max-retries command to establish a limit on the number of times that communication with a GTPP back-up storage server is attempted before a failure is logged.
> This parameter specifies the time between retries.
> Example
> The following command configures a retry timeout of 60 seconds:
> gtpp storage-server timeout 60
> gtpp suppress-cdrs zero-volume-and-duration
> This command suppresses the CDRs created by session having zero duration and/or zero volume. By default this mode is ‘disabled’.
> Product
> GGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp suppress-cdrs zero-volume-and-duration { gcdrs [ egcdrs ] | egcdrs [ gcdrs ] }
> default gtpp suppress-cdrs zero-volume-and-duration
> default
> Disables the CDR suppression mode.
> gcdrs [ egcdrs ]
> Specifies that this command will handle G-CDRs before eG-CDRs.
> gcdrs [ egcdrs ]
> Specifies that this command will handle eG-CDRs before G-CDRs.
> Usage
> Use this command to suppress the CDRs (G-CDRs and eG-CDRs) which were created due with zero-duration session and zero-volume session due to any reason. By default this command is disabled and system will not suppress any CDR.
> Example
> The following command configures the system to suppression the eG-CDRs created for a zero duration session or zero volume session:
> gtpp suppress-cdrs zero-volume-and-duration egcdrs gcdrs
> gtpp timeout
> Configures the amount of time that must pass with no response before the system re-attempts to communicate with the CGF.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp timeout time
> default gtpp timeout
> default
> Resets the systems GTPP timeout value to 20 seconds.
> time
> Default: 20
> Specifies the maximum amount of time the system waits for a response from the CGF before assuming the packet is lost.
> time is measured in seconds and can be configured to any integer value from 1 to 60.
> Usage
> This command works in conjunction with the gtpp max-retries command to establish a limit on the number of times that communication with a CGF is attempted before a failure is logged.
> This parameter specifies the time between retries.
> Example
> The following command configures a retry timeout of 30 seconds:
> gtpp timeout 30
> gtpp trigger
> This commands disables GTPP trigger conditions that cause either partial CDR record closure or opening of a new CDR record container. GTPP Triggers are specified in 3GPP TS 32.251 v6.6.0. All GTPP trigger changes take affect immediately, except volume-limit.
> Product
> ECS, GGSN, P-GW, S-GW, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> [ no ] gtpp trigger { cell-update | direct-tunnel | egcdr max-losdv | inter-plmn-sgsn-change | ms-timezone-change | plmn-id-change | qos-change | rat-change | routing-area-update | sgsn-change-limit | serving-node-change-limit | tariff-time-change | time-limit | volume-limit }
> default gtpp trigger
> default
> Sets the specified trigger condition back to the default setting. All trigger conditions are enabled by default.
> no
> Re-enables the specified trigger condition.
> cell-update
> Enables the cell update trigger for S-CDRs, if the dictionary specified in the gtpp dictionary configuration includes support for cell update. This trigger is available only for 2G. Currently, custom18 dictionary supports the cell update trigger.
> direct-tunnel
> Enables the direct tunnel trigger for CDRs.
> egcdr max-losdv
> Default: Disabled
> Enables the trigger for an eG-CDR if the List of Service Data Volume (LoSDV) containers crosses the configured limit for LOSDV containers.
> inter-plmn-sgsn-change
> This keyword is for GGSN only.
> Default: Enabled
> Disabling this trigger ignores an Inter-PLMN SGSN change and doesn't release a G-CDR.
> ms-timezone-change
> This keyword is specific to GGSN.
> Default: Enabled
> No partial record closure for a time zone change occurs when this trigger is disabled. MS Time zone change should be applicable only for 3GPP R6 based GTPP dictionaries.
> plmn-id-change
> This trigger keyword is specific to the 2G SGSN and is proprietary (non-standard).
> Default: Disabled
> Enables the PLMNID change trigger for S-CDRs if the dictionary specified in the gtpp dictionary configuration supports the PLMNID change. If enabled, the SGSN generates a partial S-CDR when the MS changes the PLMN while under the same SGSN (intra-system intra-SGSN PLMN-ID handover). Currently, custom18 dictionary supports this trigger.
> qos-change
> Default: Enabled
> Enables the QoS-change trigger for CDRs. Disabling this trigger ignores a QoS-change and does not open a new CDR for it.
> rat-change
> Default: Enabled
> This keyword enable/disable the partial record closure for a RAT change. If disabled no partial record closure for a RAT change occurs. RAT change should be applicable only for 3GPP R6 based GTPP dictionaries.
> In SGSN, RAT change trigger (2G<->3G) means inter-service handoff (SGSN service <-> GPRS service). If this trigger is enabled, after the RAT change interim CDR is generated. After this RAT change CDR, CDR thresholds such as volume/time etc. and GTPP Group are applicable from new service. If RAT change trigger is disabled, the CDR thresholds and GTPP group etc. will not change and will continue to use from old service.
> After the RAT change the System Type field in CDR changes to indicate the new system type. If this trigger is disabled then the next CDR generated will indicate System Type but the data count in the CDR doesnot necessarily belong to the system type indicated in CDR instead it may belong to both 2G and 3G as CDR is not closing when handover takes place.
> Important: However System Type field in CDR related change is not applicable to customized CDR formats which does not use System Type field
> routing-area-update
> Enables the routing-area-update trigger for CDRs.
> sgsn-change-limit [ also-intra-sgsn-multiple-address-group-change ]
> This keyword is obsolete and is available to maintain the backward compatibility for existing customers. The new keyword for sgsn-change-limit is serving-node-change-limit.
> Default: Enabled
> Disabling this trigger ignores an SGSN change and does not add the SGSN IP address into the SGSN address list of the CDR. This helps to reduce the release of CDRs due to SGSN changes crossing the configured limit.
> also-intra-sgsn-multiple-address-group-change : This keyword includes Intra-SGSN group changes as an SGSN change.
> serving-node-change-limit [ also-intra-sgsn-multiple-address-group-change ]
> This keyword is enabled for PGW, SGW, and GGSN. However, the also-intra-sgsn-multiple-address-group-change is enabled only for GGSN.
> Default: Enabled
> Disabling this trigger ignores an SGSN change and does not add the SGSN IP address into the SGSN address list of the CDR. This helps to reduce the release of CDRs due to SGSN changes crossing the configured limit.
> also-intra-sgsn-multiple-address-group-change : This keyword includes Intra-SGSN group changes as an SGSN change.
> tariff-time-change
> Default: Enabled
> When this trigger is disabled container closure does not happen for a tariff-time change.
> This trigger is applicable for G-MB-CDRs for MBMS session too.
> time-limit
> Default: Enabled
> When this trigger is disabled no partial record closure occurs when the configured time limit is reached.
> This trigger is applicable for G-MB-CDRs for MBMS session too.
> volume-limit
> Default: Enabled
> When this trigger is disabled no partial record closure occurs when volume limit is reached.
> This trigger is applicable for G-MB-CDRs for MBMS session too.
> Usage
> Use this command to disable or re-enable GTTP triggers that can cause partial CDR record closure or cause a new CDR to be created.
> Example
> The following command disables partial record closure when a configured time limit is reached:
> gtpp trigger time-limit
> The following command re-enables partial record closure when a configured time limit is reached:
> no gtpp trigger time-limit
> gtpp transport-layer
> This commands selects the transport layer protocol for Ga interface for communication between AGW (GSNs) and GTPP servers.
> Product
> GGSN, SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> gtpp transport-layer { tcp | udp }
> default gtpp transport-layer
> default
> Resets the transport layer protocol to GTPP servers to the default UDP.
> tcp
> Default: Disabled
> Enables the system to implement TCP as transport layer protocol for communication with GTPP server.
> udp
> Default: Enabled
> Enables the system to implement UDP as transport layer protocol for communication with GTPP server.
> Usage
> Use this command to select the TCP or UDP as the transport layer protocol for Ga interface communication between GTPP servers and AGWs (GSNs).
> Example
> The following command enables TCP as the transport layer protocol for the GSN’s Ga interface.
> gtpp transport-layer tcp

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