> RNC Configuration Mode Commands
> The RNC (radio network controller) configuration mode defines the parameters related to the SGSN connection with an RNC.
> This mode is access from the IuPS Service configuration mode and the command prompt for this mode will appear similar to:
> [<context_name>]hostname(config-ctx-iups-service-rnc)#
> Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
> associate-gtpu-bind-address
> This command defines the GTP-U loopback address and associates (binds) this address with a particular interface (non-loopback) address.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> [ no ] associate-gtpu-bind-address ip_address to-interface-address ip_address
> no
> Removes the loopback address definition and interface association from the current RNC configuration.
> ip_address
> ip_address: Must be specified using the standard IPv4 dotted decimal notation.
> Usage
> Use this command to setup associations between loopback GTP-U addresses and a non-loopback addresses.
> Example
> associate-gtpu-bind-address 123.1.1.1 to-interface-address 222.1.1.1
> description
> This command defines an alphanumeric string that is intended to provide descriptive information about the radio network controller (RNC). This is used for operator reference only.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> description string
> no description
> no
> Removes the description string from the current RNC configuration.
> string
> Specifies the alphanumeric string that is stored. must be from 1 through 255 alphanumeric characters. Strings with spaces must be enclosed in double-quotes. See the example below.
> Usage
> Use this command to set a description for reference by operators.
> Example
> The following command sets the description to identify a particular RNC and carrier in Uganda:
> description “RNC1 Carrier2 Uganda”
> direct-tunnel
> This command enables/disables the direct tunnel feature through the interface to the radio network controller (RNC).
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> direct-tunnel not-permitted-by-rnc
> default direct-tunnel
> default
> Sets the direct tunnel support on RNC to default mode; i.e. enabling direct tunnel.
> not-permitted-by-rnc
> Default: enabled
> Disables the direct-tunnel support on radio network controller (RNC).
> Usage
> Use this command to disable/enable the direct-tunnel function through the interface to the RNC.
> Example
> Following command disables the direct tunnel support to the RNC:
> direct-tunnel not-permitted-by-rnc
> dual-address-pdp
> This command enables the SGSN to work with an RNC with functioning dual address (IPv4v6) bearer support capability. By default, it is assumed that the RNC does not support dual PDP-type addressing.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> dual-address-pdp { not-supported | supported }
> default dual-address-pdp
> default
> Resets the SGSN to function with an RNC that is not supporting dual PDP addressing.
> not-supported
> Default
> Enables the SGSN to work with an RNC that does not support dual PDP-type addressing. It allows a single address bearer PDP-type to be activated with a configured PDP-type.
> supported
> Enables the SGSN to work with an RNC that does support dual PDP-type addressing.
> Usage
> This command enables the SGSN to support dual PDP-type addressing (IPv4v6) per RNC.
> For a dual PDP context to be activated, the RNC should support the PDP-type IPv4v6 in the RAB assignment request. For an RNC that does support the dual PDP-type addressing, use this command to change the default configuration and to configure the SGSN to work with the RNC's dual address bearer support capability.
> If the RNC does not support this functionality, then the default form of this command should be configured to enable the SGSN to activate a single-address bearer PDP context even if (1) the UE requests PDP type IPv4v6 and if (2) the subscription allows this PDP type. The single address bearer PDP type will be activated with a configured PDP type.
> When a UE moves from an RNC that supports dual PDP-type addressing to another RNC that does not support dual PDP-type addressing, then the SGSN will deactivate the PDP context. This is done because, even if we preserve the PDP contexts, the UE would be unaware of the preserved PDP context. This would lead to nonsynchronized behavior in the network. So the SGSN deactivates the PDP context with cause code "reactivation-required" to ensure the UE, RNC, SGSN, and GGSN are in synch. As well, this gives the UE the opportunity to activate a PDP context again without dual bearers.
> The sgsn-rnc-no-dual-pdp-init-pdp-deact disconnect reason is used to indicate that a PDP context has been deactivated because of roaming into an RNC that does not support this feature.
> Important: For this configuration to function, support for dual PDP-type addressing must be enabled at the global level (the default). To confirm the functionality is enabled, issue the show sgsn-mode command from the Exec mode. If the PDP-type addressing is not enabled, then refer to the instructions for the dual-address-pdp command in the SGSN Global Configuration Mode Commands section.
> Example
> Use the following command to enable dual PDP-type addressing with a supporting RNC:
> dual-address-pdp supported
> end
> Exits the configuration mode and returns to the Exec mode.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> end
> Usage
> Change the mode to the Exec mode.
> exit
> Exits the current configuration mode and returns to the IuPS Service configuration mode.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> exit
> Usage
> Return to the previous configuration mode.
> lac
> This command identifies a Local Area Concentrator (LAC) and a Remote Area Concentrator (RAC) and associates them with this RNC definition.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> [ no ] lac lac_id rac rac_id
> no
> Deletes the LAC and RAC information from the system configuration.
> lac_id
> A unique numeric identifier for the LAC associated with the RNC.
> lac_id must be an integer between 1 and 65535.
> rac_id
> A unique numeric identifier for the RLAC associated with the RNC.
> rac_id must be an integer between 1 and 255.
> Usage
> Creates an association with a specific LAC and RAC.
> Example
> lac 545 rac 23
> mbms
> Configures RNC options for multimedia broadcast multicast service.
> Important: This feature and command are currently under development and not yet operational.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> mbms
> Usage
> Information will be provided when this command has been fully developed and released.
> overload-action disable
> This command maps an action to be taken if traffic reaches or exceeds defined levels.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> overload-action disable { activate | attach | auth-challenge | modify-request | paging-downlink-data | ptmsi-reallocation | service-request-data | sms } traffic-level traffic-level
> [ no | default ] overload-action disable { activate | attach | auth-challenge | modify-request | paging-downlink-data | ptmsi-reallocation | service-request-data | sms }
> no
> Removes the defined overload action from configuration.
> default
> Resets the traffic level to the default level for the associated overload action.
> activate traffic-level traffic-level
> The system rejects new requests to activate PDP contexts if the defined traffic-level is exceeded.
> traffic-level: An integer 1 to 15.
> Default: 14
> attach traffic-level traffic-level
> The system rejects new requests for GPRS attach if the defined traffic-level is exceeded.
> traffic-level: An integer 1 to 15.
> Default: 15
> auth-challenge traffic-level traffic-level
> The system skips performing authentication challenges if the defined traffic-level is exceeded.
> traffic-level: An integer 1 to 15.
> Default: 4
> modify-request traffic-level
> The system rejects requests to modify a PDP context if the defined traffic-level is exceeded.
> traffic-level: An integer 1 to 15.
> Default: 12
> paging-downlink-data traffic-level traffic-level
> If the defined traffic-level is exceeded, then paging is not performed for data during downlinks if RABs are not available.
> traffic-level: An integer 1 to 15.
> Default: 11
> ptmsi-reallocation traffic-level traffic-level
> The system skips performing ptmsi-reallocation if the defined traffic-level is reached or exceeded.
> traffic-level: An integer from 1 to 15.
> Default: 4
> service-request-data traffic-level traffic-level
> The system rejects service requests to accept data and establish new RABs if the defined traffic-level is reached or exceeded.
> traffic-level: An integer from 1 to 15.
> Default: 10
> sms traffic-level traffic-level
> The system rejects SMS signaling if the defined traffic-level is reached or exceeded.
> traffic-level: An integer 1 to 15.
> Default: 8
> Usage
> This command defines traffic levels and the actions to take if traffic exceeds the defined levels. The command can be re-entered multiple times to create individual definitions for each type of traffic level and action.
> Example
> Use the following to instruct the system to reject service requests to establish new RABs if the traffic level reaches 3.\:
> overload-action disable service-request-data traffic-level 3
> paging-non-searching-indication
> This command instructs the SGSN to include the non-searching indicator flag in the page-request message.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> paging-non-searching-indication { non-searching | searching }
> [ no | default ] paging-non-searching-indication
> no | default
> This is the default. Entering no or default with this command disables the inclusion of the flag.
> non-searching
> Set the non-searching-indication to non-searching in the page-request message.
> searching
> Set the non-searching-indication to searching in the page-request message.
> Usage
> Use this command to determine which type of search indicator flag will be included in the page-request message.
> Example
> Use this command to include the non-searching flag in page-request messages:
> paging-non-searching-indication non-searching
> pointcode
> Configures the point code of the RNC.
> The access protocol that is part of the IuPS Service configuration mode must be configured prior to defining the RNC’s point code.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> pointcode pt_code
> no pointcode
> no
> Deletes the RNC’s point code information from the system configuration.
> pt_code
> Point code in dotted-decimal format :

> • | ITU Range 0.0.1 to 7.255.7

> • | ANSI Range 0.0.1 to 255.255.255

> • | TTC Range 0.0.1 to 15.31.255

> • | string of 1 to 11 characters

> Usage
> Use this command to identify the point code of the associated RNC.
> Example
> pointcode 1.234.2
> pooled
> Configure an RNC as either ‘pooled’ or ‘non-pooled’.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> pooled
> [ default | no ] pooled
> default | no
> Entering either default or no returns the RNC configuration to the default ‘non-pooled’ state.
> Usage
> Each RNC, one-at-a-time, can be identified as ‘pooled’ -- as participating within an SGSN pool -- or ‘non-pooled’. Pooled RNCs can co-exist with non-pooled RNCs.
> Example
> Identify this RNC as being part of an SGSN pool:
> pooled
> rab-modify-procedure
> This command configures how the RAB (radio access bearer) assignment procedure will be modified
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> rab-modify-procedure { normal-modify | release-and-establish }
> default rab-modify-procedure
> default
> Returns the configuration to the default setting for this command parameter.
> normal-modify
> Selects the normal RAB modify procedure.
> release-and-establish
> Instructs the system to release and establish the RAB procedure.
> Usage
> Set the procedure to establish the radio access bearer (RAB).
> Example
> rab-modify-procedure normal-modify
> ranap paging-cause-ie
> This command sets the paging cause value and either includes or suppresses the Paging Cause IE in responses to Paging Requests due to various sources. This command is available in releases 8.1 and higher.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> ranap { paging-cause-ie { all | background-data [ value ] | conversational-data [ value ] | gmm-signalling [ value ] | gs-signalling [ value ] | interactive-data [ value ] | sm-signalling [ value ] | sms-signalling [ value ] | streaming-data [ value ] }
> [ default | no ] ranap { paging-cause-ie { all | background-data | conversational-data | gmm-signalling | gs-signalling | interactive-data | sm-signalling | sms-signalling | streaming-data }
> default
> Resets the specific parameters value to default.
> no
> Suppresses the Paging Cause IE so that it is not included in responses to Paging Requests from respective sources.
> all
> Using all sets the action for the Paging Cause IE value for all paging due to all sources.
> background-data [ value ]
> Default: 3 (terminating background call)
> Set the Paging Cause IE value for paging due to background data.
> value : Must be an integer from 0 to 5. See Paging Cause value mapping in Usage section.
> conversational-data [ value ]
> Default: 5 (terminating high priority signaling)
> Set the Paging Cause IE value for paging due to coversational data.
> value : Must be an integer from 0 to 5. See Paging Cause value mapping in Usage section.
> gmm-signalling [ value ]
> Default: 5 (terminating high priority signaling)
> Set the Paging Cause IE value for paging due to gmm-signaling.
> value : Must be an integer from 0 to 5. See Paging Cause value mapping in Usage section.
> gs-signalling [ value ]
> Default: 5 (terminating high priority signaling)
> Set the Paging Cause IE value for paging due to VLR Paging Request.
> value : Must be an integer from 0 to 5. See Paging Cause value mapping in Usage section.
> interactive-data [ value ]
> Default: 2 (terminating interactive call)
> Set the Paging Cause IE value for paging due to interactive data.
> value : Must be an integer from 0 to 5. See Paging Cause value mapping in Usage section.
> sm-signalling [ value ]
> Default: 5 (terminating high priority signaling)
> Set the Paging Cause IE value for paging due to SM signaling.
> value : Must be an integer from 0 to 5. See Paging Cause value mapping in Usage section.
> sms-signalling [ value ]
> Default: 4 (terminating low priority signaling)
> Set the Paging Cause IE value for paging due to SMS signaling.
> value : Must be an integer from 0 to 5. See Paging Cause value mapping in Usage section.
> streaming-data [ value ]
> Default: 5 (terminating high priority signaling)
> Set the Paging Cause IE value for paging due to streaming data.
> value : Must be an integer from 0 to 5. See Paging Cause value mapping in Usage section.
> Usage
> This command can be used to set the value (meaning) of the Paging Cause IE included in responses to Paging Requests or it can be used to suppress the inclusion of the Paging Cause IE in the responses. These actions can be configured for paging for all sources or for a specified source.
> The following values are applicable to all Paging Cause IEs:

> • | 0 - Terminating conversational call

> • | 1 - Terminating streaming call

> • | 2 - Terminating interactive call

> • | 3 - Terminating background call

> • | 4 - Terminating low priority signaling

> • | 5 - Terminating high priority signaling

> Example
> Use the following command to set Paging Cause value to 3 for paging due to GMM signaling without affecting cause values for other sources:
> ranap paging-cause-ie gmm-signalling 3
> Use the following command to suppress the Paging Cause IE from all Paging Requests to the RNC:
> no ranap paging-cause-ie all
> Either of the following commands will cause the Paging Cause IE to be included in Paging Requests with the default value for SM signaling without affecting the cause for other sources:
> ranap paging-cause-ie sm-signalling
> default ranap paging-cause-ie sm-signalling
> ranap signalling-indication-ie
> This command enables/disables the inclusion of the Signaling Indication IE in either or both the RAB Assignment Request and/or the Relocation Request RANAP messages.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> ranap signalling-indication-ie { rab-assignment-request [ relocation-request ] | relocation-request [ rab-assignment-request ] }
> no ranap signalling-indication-ie
> default ranap signalling-indication-ie
> no
> Sets the configuration so that the SGSN never includes the IE.
> default
> Resets the configuration to the default - the SGSN includes the IE in the messages if preconditions are met (see Usage section).
> rab-assignment-request | relocation-request
> Including one or both of these keywords configures what type of RANAP message will include the IE.
> Usage
> The command enables the operator to determine whether the signalling indication information element is included in either or both the RAB Assignment Request and Relocation Request messages during the PDP context setup procedure.
> For this command configuration to work so that the IE is included, two preconditions must be met:

> • | Received QoS traffic class for the context must be interactive

> • | Received QoS has a signalling indication value as optimized

> When an RNC receives this IE, the RNC assumes that the customer is using IMS signaling and allocates massive amounts of bandwidth, potentially causing cell congestion. This command enables the operator to determine the usage of this IE which provides the operator with additional session management control.
> Example
> Use the following command to include the signalling indication IE in the RAB Assignment Request:
> ranap signalling-indication-ie rab-assignment-request
> ran-information-management
> Use this command to inform the SGSN which RNC are capable of handling RAN information management (RIM) messages.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> [ default | no ] ran-information-management
> default
> Resets the default so RIM is disabled.
> no
> Disables the RIM support in the configuration file.
> Usage
> By default, handling of RAN information management (RIM) messages is disabled. This command informs the SGSN which RNC are capable of handling RIM messages. This configuration only becomes ‘operational’ if the ran-information-management command is enabled in the SGSN global configuration mode.
> When RIM support is enabled on both the SGSN and the destination node, then all RIM PDUs are forwarded to the BSC/RNC. If RIM message handling is not enabled on both nodes, then the RIM PDUs are dropped silently.
> Example
> Use the following command to enable RIM support:
> ran-information-management
> Use the following command to disable RIM support that has been added to the configuration:
> no ran-information-management
> release-compliance
> This command allows the SGSN to support 3GPP release 6 HSPA or release 7 HSPA+.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> release-compliance { pre-release-7 | release-7 }
> default release-compliance
> default
> Returns the configuration to the default value, which is release-7.
> pre-release-7
> Identifies 3GPP Release 6 (R6) as the release the RNC is compliant with.
> release-7
> Identifies 3GPP Release 7 (R7) as the release the RNC is compliant with.
> Usage
> Use this command to match the 3GPP release support by the RNC. As the 3GPP releases each support differing data rate options - R6 supports HSPA and R7 supports HSPA+ - then selecting the compliance is a method of preforming data rate management on a per RNC basis.
> Example
> Enable HSPA fallback to R6 compliance:
> release-compliance pre-release-7
> reset-resource
> This command enables the operator to control message length by configuring the number of IuConIDs sent in each RANAP Reset Resource messages.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> reset-resource max-iuconid-per-msg number
> default reset-resource max-iuconid-per-msg
> default
> Resets the number of Iu connection Ids included in the Reset Resource messages. Default is 250.
> max-iuconid-per-msg number
> Sets the number of Iu connection Ids to be included in the Reset Resource messages.
> number: Integer from 1 to 250.
> Default : 250
> Usage
> Id numbers for each Iu connection are included in the RANAP Reset Resource messages. Including this potentially long stream of numbers can make the message very long. With this command, the operator can control the size of the messages by controlling the number of Id messages included in the messages.
> Example
> Limit the number of Iu connection Ids to 30:
> reset-resource max-iuconid-per-msg 30

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