GGSN Service Configuration
Mode Commands
The Gateway GPRS Support
Node (GGSN) Configuration Mode is used to create and manage GGSN
services within the current context.
IMPORTANT:
The commands or keywords/variables
that are available are dependent on platform type, product version,
and installed license(s).
accounting
Configures the name
of the context configured on the system that processes accounting
for PDP contexts handled by this GGSN service.
Privilege:
Security Administrator,
Administrator
Syntax
accounting context context_name
no accounting context
no
Removes a previously
configured accounting context.
context_name
Specifies the name
of the context to be used for accounting. context_name must
be an alphanumeric string of 1 through 79 characters that is case
sensitive.
Usage:
By default, the system
attempts to use the same context as the one in which the GGSN service
is configured for accounting purposes. This command can be used
to either change the system’s default behavior, or allow
GPRS Tunneling Protocol Prime (GTPP) accounting to a charging gateway
(CG).
By default when GTPP
accounting is used, accounting records will be sent to the accounting
servers configured in whichever context the GGSN service is configured.
This command may be used to override that default.
Example:
The following command
configures the GGSN service’s accounting context to be
plmn1:
accounting context plmn1
associate gtpu-service
This command associates
a previously configured GTP-U service to bind the GGSN service with
a peer. A GTP-U service must be configured in Context Configuration
mode before using this configuration.
Privilege:
Security Administrator,
Administrator
Syntax
associate gtpu-service svc_name
noassociate gtpu-service
no
Removes the associated
GTP-U service from this GGSN service configuration.
svc_name
Identifies the name
of the GTP-U service preconfigured in Context Configuration mode
to associate with a GGSN service. svc_name is
an alphanumeric string from 1 through 63 characters.
Usage:
Use this command to
configure GTP-U data plan between GGSN service and peer node. The
service defined for GTP-U can be configured in Context configuration mode.
Example:
Following command associates
GTP-U service named
gtpu-hnb1 with
specific GGSN service.
associate gtpu-service
gtpu-hnb1
associate pgw-service
This command enables
a previously configured P-GW service to which handover will be done
by the GGSN service. The P-GW service must be configured in Context Configuration
mode before using this configuration.
Privilege:
Security Administrator,
Administrator
Syntax
associate pgw-service svc_name
no associate pgw-service
no
Removes the associated
P-GW service from this GGSN service configuration.
svc_name
Identifies the name
of the P-GW service preconfigured in Context Configuration mode
to which handover will be done.
The svc_name must
be an alphanumeric string from 1 through 63 characters.
Usage:
Use this command to
allow enabling/disabling bearer handover from GGSN to a
P-GW service. The service defined for P-GW can be configured in
Context configuration mode.
The P-GW’s
eGTP service should have the same bind address as GGSN service and
P-GW and GGSN should share same GTP-U, otherwise handover will fail.
Example:
Following command enables
P-GW service named
pgw-test handover
with specific GGSN service.
associate pgw-service
pgw-test
authorize-with-hss
This command enables
or disables subscriber session authorization via a Home Subscriber
Server (HSS) over an S6b Diameter interface. This feature is required
to support the interworking of GGSN with P-GW and HA.
Privilege:
Security Administrator,
Administrator
Syntax
[ default | no ] authorize-with-hss
no
Disables the default
authorization of subscriber over S6b interface. Resets the command
to the default setting of “authorize locally” from
an internal APN authorization configuration.
Usage:
Use this command to
enable/disable the authorization support for subscriber
over S6b interface, which is used between GGSN and the 3GPP AAA
to exchange the information related to charging, P-CSCF discovery,
etc.
By use of this feature
allows the GGSN service to interact with HSS over S6b interface through
Diameter configuration which is already configured on the system.
IMPORTANT:
Diameter configuration
must be available before enabling this command. For more information
of Diameter interface configuration, refer Diameter Endpoint Configuration
Mode Commands chapter.
IMPORTANT:
This command is a license-enabled
feature.
Example:
The following command
enables the subscriber authorization via an HSS over an S6b Diameter
interface to provide session interoperability between GGSN and PGW
and HA in this GGSN service:
authorize-with-hss
bind
Binds the GGSN service
to a logical IP interface serving as the Gn interface. Specifies
the maximum number of subscribers that can access this service over
the interface.
Privilege:
Security Administrator,
Administrator
Syntax
bind address ip_address max [ total-pdp-contexts max_total | ppp-pdp-contexts max_ppp ]
no bind address address
no
Removes a previously
configured binding for the GGSN service.
ip_address
Specifies the IP address
(address) of the interface configured as the Gn interface. ip_address is
specified in IPv4 dotted-decimal notation.
max
Configures the maximum
limits for total/PPP PDP contexts.
total-pdp-contexts max_total
Default: 1500000
Specifies the maximum
number of PDP contexts (both IP and PPP) that can access this service
on this interface.
count is
an integer from 0 through 4000000.
IMPORTANT:
The maximum number
of supported subscriber contexts varies based on the installed session capacity
license and the number of active packet processing cards installed
in the system. Note that each PPP PDP context is treated as two
IP PDP contexts. Refer to the license key command
for additional information.
ppp-pdp-contexts max_ppp
Default: 750000
Specifies the maximum
number of PPP PDP contexts that can access this service on this interface.
count can
be configured to an integer from 0 and 2500000.
IMPORTANT:
The maximum number
of supported subscriber contexts varies based on the installed session capacity
license and the number of active packet processing cards installed
in the system. Refer to the license
key command for additional information.
Usage:
Used to associate or
tie the GGSN service to a specific logical IP address. The logical
IP address or interface takes on the characteristics of a Gn interface.
Only one interface can be bound to a service. The interface should
be configured prior to issuing this command.
This command also sets
a “soft” limit as to the number of simultaneous
subscriber contexts that can be facilitated by the service/interface
at any given time. Soft limits are based on measurements gathered
at regular short intervals (several times per minute) as opposed
to measurements taken in real-time. Therefore, the sampled measurement
may not match the actual number of PDP contexts currently being
processed. Every PDP context request received is compared against
the result of the last sample. If the sample is less than the soft
limit configured, the request will be processed. If it is more,
the request will be rejected.
When configuring the
total-pdp-contexts or
ppp-pdp-contexts options,
be sure to consider the following:
- Each PPP PDP context
is treated as two IP PDP contexts due to the additional CPU and
memory resources required
- The total number of
configured Gn interfaces
- The maximum number
of subscriber PDP contexts that all of the interfaces may handle during
peak busy hours
- The average bandwidth
for each of the PDP contexts
- The type of physical
port (10/100Base-T
or 1000Base-Tx) to which these interfaces are bound
Taking these factors
into account and distributing your subscriber contexts across all available
interfaces allows you to configure your interfaces to optimally
handle PDP contexts without degrading performance.
Example:
The following command
would bind the logical IP interface with the address of
192.168.3.1 to
the GGSN service and specifies that a maximum of
600 simultaneous
subscriber sessions can be facilitated by the interface/service
at any given time:
bind address 192.168.3.1
max-subscribers 600
The following command
disables a binding that was previously configured:
no bind address
cc behavior
Configures the 3GPP
behavior bits associated with the GGSN’s charging characteristics
(CC).
Privilege:
Security Administrator,
Administrator
Syntax
cc behavior | no-records nr_value
{ default | no } cc behavior
no-records nr_value
Default: 0 (disabled)
Specifies the behavior
bit upon which the GGSN ceases sending accounting records to a server.
nr_value can
be configured to an integer from 1 through 12 corresponding to the
12 behavior bits – B1 through B12.
Usage:
3GPP standards after
3GPP R98 included 12 behavior bits as part of GGSN charging characteristics.
Like the charging characteristics profile index, the behavior bits
are sent by the SGSN to the GGSN in the Create PDP Context request
message.
This command configures
the behavior bits for each of the conditions described.
Example:
The following command
configures a behavior bit of 10 for no-records:
cc behavior no-records 10
cc profile
Configures the charging
characteristic (CC) profile index properties.
Privilege:
Security Administrator,
Administrator
Syntax
cc profile index [ buckets number | interval time [ downlink down_octets uplink up_octets | total total_octets ] | prepaid { prohibited | use-rulebase-configuration } | sgsns num_changes | tariff time1 mins hours [ time2 mins hours [ time3 mins hours [ time4 mins hours [ time5 mins hours [ time6 mins hours ] ] ] ] | volume { downlink vol_down_octets uplink vol_up_octets | total total_octets } ]
no cc profile index { buckets | interval | prepaid | sgsns | tariff | volume }
default cc profile index
no
Removes a previously
configured profile index.
default
Returns the specified
cc profile to the original default system settings.
index
Configures a profile
index for the parameter to be specified. index can be configured
to an integer from 0 through 15.
IMPORTANT:
3GPP standards suggest
that profile index values of 1, 2, 4, and 8 be used for hot billing,
flat rate billing, prepaid billing and normal billing, respectively.
A single charging characteristics profile can contain multiple behavior
settings.
buckets number
Default: 4
Specifies the number
of statistics container changes due to QoS changes or tariff time
that can occur before an accounting record should be closed.
number can
be configured to an integer from 1 through 4.
interval time [downlink down_octets uplink up_octets | total total_octets ]
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
- Uplink traffic volume
is reached within the time interval
- Total traffic volume
(up and downlink) is reached within the time interval
time is measured
in seconds and can be configured to an integer from 60 through 40000000.
down_octets is
the downlink traffic volume measured in octets and can be configured
to an integer from 0 through 1000000.
up_octets is
the uplink traffic volume measured in octets and can be configured
to an integer from 0 through 1000000.
total_octets is
the total traffic volume measured in octets and can be configured
to an integer from 0 through 1000000.
prepaid { prohibited | use-rulebase-configuration }
This command enables
or disables prepaid for the specified profile index.
Default: N/A
prohibited:
Disable prepaid for the specified profile index.
use-rulebase-configuration:
Use the prepaid configuration in the rulebase.
sgsns num_changes
Default: 4
Specifies the number
of SGSN changes (such as, inter-SGSN switchovers) resulting in a new
RAI (Routing Area Identity) that can occur before closing an accounting
record.
num_changes can
be configured to an integer from 1 through 15.
tariff time1 mins hours time2 mins hours time3 mins hours time4 mins hours time5 mins hours time6 mins hours
Specifies time-of-day
time values to close the current statistics container (but not necessarily the
accounting record). Six different tariff times may be specified.
If less than six times are required, the same time can be specified
multiple times.
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 to 59.
- hours: The
hour of the day, an integer value from 0 to 23.
volume {downlink vol_down_octets uplink vol_up_octets | total total_octets }
Specifies the downlink,
uplink, and total volumes that must be met before closing an accounting
record.
vol_down_octets is
measured in octets and can be configured to an integer from 100000
to 4000000000.
vol_up_octets is
measured in octets and can be configured to an integer from 100000
to 4000000000.
total_octets is
the total traffic volume (up and downlink) measured in octets and
can be configured to an integer from 100000 to 4000000000.
Usage:
Charging characteristics
consist of a profile index and behavior settings. This command configures
profile indexes for the GGSN’s charging characteristics.
The GGSN supports up to 16 profile indexes.
This command works
in conjunction with the cc-sgsn command
located in the APN Configuration Mode that dictates which CCs should
be used for subscriber PDP contexts.
Example:
The following command
configures a profile index of
10 for tariff
times of 7:00 AM and 7:30 PM:
cc profile 10 tariff
time1 0 7 time2 30 19 time3 0 7 time4 30 19
default
Sets/restores
the default value assigned for the specified parameter.
Privilege:
Security Administrator,
Administrator
Syntax
[ default ] { cc { behavior | profile index } | echo-interval | gtpu
echo-interval | gtpu reorder { context | sequence-numbers | timeout } | guard-interval | ip { local-port
gtpc-v1 | qos-dscp } | max-retransmissions | plmn { unlisted-sgsn } | setup-timeout | timeout }
cc { behavior | profile index }
Restores the GGSN’s
charging characteristics parameters to the following default settings:
- behavior: Restores
all behavior parameters to their default values of 0 (disabled).
- profile: For the
specified index, the following defaults are applied:
buckets: 4
interval: Disabled
volume: Disabled
sgsns: 4
tariff-time: Disabled
echo-interval
Restores the GTP echo-interval
parameter to its default setting of 60.
gtpu echo-interval
Restores the GTPU echo-interval
parameter to its default setting of 60.
gtpu reorder { context | sequence-numbers | timeout }
Restores the gtpu reordering
parameters to the following default settings:
- gtpu reorder context:
Disabled
- gtpu reorder sequence-numbers:
Disabled
- gtpu reorder timeout:
100 milliseconds
gtpu udp-checksum insert
Restores the GGSN gtpu
udp-checksum parameter to its default setting of enabled.
guard-interval
Restores the GGSN guard-interval
parameter to its default setting of 100.
ip {local-port
gtpc-v1 | qos-dscp }
Restores the GGSN ip
parameters to the following default setting:
- local-port gtpc-v1:
2123
- qos-dscp:
conversational ef streaming af11 interactive af21 background be
max-retransmissions
Restores the GGSN max-retransmissions
parameter to its default setting of 4.
plmn { unlisted-sgsn }
Restores the GGSN plmn
unlisted-ggsn parameter to its default setting of reject.
setup-timeout
Restores the GGSN setup-timeout
parameter to its default setting of 60.
timeout
Restores the GGSN timeout
parameter to its default setting of 5.
Usage:
After the system has
been modified from its default values, this command is used to set/restore
specific parameters to their default values.
Example:
The following command
restores the GGSN service’s guard interval parameter to
its default setting:
default guard-interval
dns-client
This command defines
the context name where a DNS client is configured. It associates
an existing DNS client configuration with the GGSN to perform a
DNS query for P-CSCF, if a P-CSCF query request in an AAA message
is received from the Diameter node.
Privilege:
Security Administrator,
Administrator
Syntax
dns-client context dns_ctxt_name
{ no | default } dns-client context
no
Removes the association
of DNS context which was configured to perform DSN query in this
GGSN service.
default
Sets the default context
for the DNS client.
dns_ctxt_name
Specifies the name
of the context in which a DNS client configuration is present. Typically this
should be the same context in which this GGSN service is configured.
dns_ctxt_name is
a context name and must be alphanumeric string of 1 through 79 characters.
Usage:
Use this command to
associate a DNS client configuration to perform DNS query used for the
resolution of P-CSCF query received in AAA message from Diameter
peer, on the basis of DNS client parameters configured in a context.
A DNS client configuration
must be present in the same context as GGSN service before enabling
this command to perform DNS query for P-CSCF.
IMPORTANT:
This command is a license-enabled
feature.
Example:
The following command
associates a DNS client configuration to perform DNS query for P-CSCF
with this GGSN service which is configured in same context as GGSN
service:
default dns-client context
echo-interval
Configures the rate
at which GPRS Tunneling Protocol (GTP) v1-C Echo packets are sent
from the GGSN service to the SGSN.
Privilege:
Security Administrator,
Administrator
Syntax
echo-interval seconds
{ default | no } echo-interval
default
Configures the default
value (60 seconds) for echo interval.
no
Disables the sending
of GTPv1-C Echo packets.
seconds
Default: 60
Specifies the frequency
at which the GGSN service sends GTPv1-C Echo packets to the SGSN(s)
it is configured to communicate with.
seconds is
measured in seconds and can be configured to an integer from 60
through 3600.
Usage:
Use this command to
adjust the rate at which the GGSN sends these packets. GTPv1-C Echo
packets are used to detect whether SGSNs that the GGSN service is
communicating with, has become unresponsive or has rebooted.
The system initiates
this protocol for each of the following scenarios:
- Upon system boot
- Upon the configuration
of a new SGSN on the system using the sgsn address command
as described in this chapter
- Upon the execution
of the path failure detection policy as described in path-failure command
of this chapter
The echo-interval command
is used in conjunction with the max-retransmissions and retransmission-timeout commands
as described in this chapter.
In addition to receiving
an echo response for this echo protocol, if GGSN receives a Node Alive
Request message or a Echo Request message from a presumed dead SGSN,
it will immediately assume the SGSN is active again.
If the GGSN discovers
that an SGSN has become unresponsive, it will terminate all PDP contexts
that had been established with the SGSN.
Example:
The following command
configures the GGSN service to send GTP Echo packets every 120 seconds:
echo-interval 120
end
Exits the current
configuration mode and returns to the Exec mode.
Privilege:
Security Administrator,
Administrator
Usage:
Use this command to
return to the Exec mode.
exit
Exits the current
mode and returns to the parent configuration mode.
Privilege:
Security Administrator,
Administrator
Usage:
Use this command to
return to the parent configuration mode.
fqdn
This command defines
Fully Qualified Domain Name (FQDN) which would be used for authorization
over S6b interface between GGSN and 3GPP AAA/HSS.
Privilege:
Security Administrator,
Administrator
Syntax
fqdn host host_name realm realm_id
{ no | default } fqdn
no
Removes the configured
FQDN host name and realm ID from the GGSN service.
default
Sets the system to
default mode for this command and configures the host and realm
ID value to NULL.
host host_name
Specifies the name
of the host to be used for authorization over an S6b interface to
a 3GPP AAA server/HSS from the GGSN service.
host_name is
a unique node name for authorization over the S6b interface from
this GGSN service.
host_name must
be an alphanumeric string of 1 through 127 characters. Punctuation
marks are allowed.
realm realm_id
Specifies the realm
as an FQDN to be used for authorization over S6b interface with
3GPP AAA server/HSS from GGSN service. The realm may typically
be a company or service name.
realm_id is
a unique identifier configured for the authorization over S6b interface
from this GGSN service, expressed as an alphanumeric string of 1
through 127 characters. Punctuation marks are allowed.
host_name
Usage:
Use this command to
define host and realm as the FQDN for a 3GPP AAA server/HSS
that would be used for authorization over an S6b interface with
the GGSN. The realm specified as an FQDN may typically be a company
or service name.
By default the FQDN host
and realm will be NULL
IMPORTANT:
This command is a license-enabled
feature.
Example:
The following configures
the
hss1 as
host name and
xyz.com as
realm to support authorization over an S6b from this GGSN service:
fqdn host hss1 realm xyz.com
gtpc nsapi-in-create-pdp-response
This command excludes
or includes the optional information element (IE) Network Service
Access Point Identifier (NSAPI) within “Create PDP Context
Response” messages in GTP-C.
Privilege:
Security Administrator,
Administrator
Syntax
[ default | no ] gtpc
nsapi-in-create-pdp-response
default
Sets the default mode
for GTP-C messages not to include the NSAPI IE in “Create
PDP Context Response” messages.
no
Removes the preconfigured
mode for GTP-C messages; the GTP-C message will not include the
NSAPI IE in “Create PDP Context Response” messages.
By default it is disabled.
Usage:
Use this command to
exclude or include the NSAPI IE in “Create PDP Context
Response” GTP-C messages received from the SGSN.
Example:
The following command
configures the GGSN service to include the optional NSAPI IE in “Create
PDP Context Response” messages:
gtpc nsapi-in-create-pdp-response
gtpc private-extension
This command includes
customer-specific private extensions in GTP-C messages.
Privilege:
Security Administrator,
Administrator
Syntax
gtpc private-extension { { { focs | odb } access-list acl_name in disconnect-on-violation } | ggsn-preservation-mode | loss-of-radio-coverage | none }
default gtpc private-extension
no gtpc private-extension [ focs | ggsn-preservation-mode | loss-of-radio-coverage ]
default
Sets the default mode
for GTP-C messages. By default it is disabled.
no
Disables the configured
private extensions for GTP-C messages.
{focs | odb} access-list acl_name in disconnect-on-violation
Configures the Free-Of-Charge-Service
(FOCS) and Operator Determined Barring (ODB) extensions for all
packet-oriented services as defined by operators.
focs: Enables
or disables Free of Charge Services for the subscriber who has no
credit, and also takes the access-list acl_name to
be applied for FOCS.
odb: Enables
or disables “all packet oriented service barred” for
the subscriber, and also takes the access-list acl_name to
be applied for ODB.
acl_name is
the name of a configured access control list (ACL) for this service.
IMPORTANT:
These are the customer-specific
keywords and need customer-specific license to use them.
ggsn-preservation-mode
Enables the processing
of customer-specific private extension in Update PDP Context requests.
This extension indicates whether the subscriber is active or idle,
and whether RAN resources have been released. It also indicates
the desired “type” of preservation mode behavior.
When ggsn-preservation-mode is
configured, different types of accounting records are generated
based on the “type” of mode. To enable the generation of
different accounting records, the trigger for preservation mode
must be configured for RADIUS or GTPP for that accounting protocol.
If that trigger is not configured, there will be no change in the
generation of accounting records.
IMPORTANT:
This is a customer-specific
keyword and needs customer-specific license to use this feature.
loss-of-radio-coverage
Enables the protection
against overcharging a subscriber due to loss of radio coverage (LORC)
in a GGSN service. It also enables the system to understand the
private extension for LORC) in GTP-C Update PDP Context messages
from the SGSN.
IMPORTANT:
This is a license enabled
keyword and need feature-specific license to use it.
none
Removes the private
extensions from record which are from GTP-C messages received from the
SGSN.
Usage:
Use this command to
configure the processing of private extensions within GTP-C messages
received from the SGSN. It also configures the customer specific
features, such as preservation mode for GGSN service.
Overcharging protection
(LORC) is a solution which provides the ability to accurately bill customers.
This implementation
is based on Cisco-specific private extension to GTP messages and/or any
co-relation of G-CDRs and S-CDRs. It also does not modify any RANAP
messages.
IMPORTANT:
This is a license enabled
command that requires installation of feature-specific licenses
to use this command.
Example:
The following command
configures the GGSN service to record the private extension for protecting
the subscribers from overcharging during loss of radio coverage:
gtpc private-extension
loss-of-radio-coverage
gtpc ran-procedure-ready-delay
This command configures
the GGSN to enable the RAN Procedure Ready feature for the particular
GGSN service and specify the timeout period for the RAN procedure timer
in the GGSN. This timer starts on arrival of every secondary Create
PDP Context request.
Privilege:
Security Administrator,
Administrator
Syntax
gtpc ran-procedure-ready-delay [ timeout dur ]
{ default | no } gtpc
ran-procedure-ready-delay
default
Sets the default mode
of RAN Procedure Ready feature for this GGSN service. By default
it is disabled.
no
Disables the RAN Procedure
Ready feature for this GGSN service. By default it is disabled.
timeout dur
Default: 10
Specifies the timeout
duration (in seconds) for the RAN procedure timer. This timer starts
on the arrival of every secondary “Create PDP Context Request” message.
This is an optional
keyword. If no timeout period is specified, the default value is
10 seconds.
dur must
be an integer from 1 through 40.
Usage:
Use this command to
enable the RAN Procedure Ready feature for this GGSN service and specify
the timeout period for the RAN procedure timer. This timer starts
on the arrival of every secondary “Create PDP Context Request” message.
The GGSN waits until
the Radio Access Bearer setup is completed and “Update
PDP Context Request” is sent by the SGSN. If any downlink
data is received before arrival of the “Update PDP Context
Request” or before timer expiry, the downlink packets will
be queued or buffered.
If
the buffer becomes full (total buffer limit is of 1024 packets),
all newly arriving packets are dropped.
The RAN Procedure Ready
feature supports the following scenarios when RAB setup timer starts
at the GGSN:
- If the GGSN receives
the “Update PDP Context Request” before timer
expiry, the GGSN stops the timer, sends all the queued/buffered
packets in ‘first-in first-out’ manner and disables
buffering of subsequent downlink data.
- If the GGSN receives
the “Update PDP Context Request” before the timer
expires, it processes the “Update PDP Context Request” as
usual, but does not disable the buffering of downlink data. It then
waits for another “Update PDP Context Request” to
come with the RAN Procedure Ready set, or waits for timer to expire.
- If the GGSN does not
receive the “Update PDP Context Request” with
RAN Procedure Ready set before timer expiry, the timer is fired
and the GGSN starts sending all queued packets and disables buffering
of subsequent downlink data (assuming that the corresponding SGSN
does not support this feature).
- If the timer has expired
and the GGSN receives an “Update PDP Context Request” for a
secondary PDP context with or without RAN Procedure Ready bit set,
the UPC will be processed normally without buffering the packets.
IMPORTANT:
This feature does not
affect the Enhanced Charging Service or deep packet inspection (DPI) since
the buffering of downlink data is done before sending it to an ACSMgr.
IMPORTANT:
During an SGSN handoff
scenario all packets are processed normally and the downlink packets
are buffered until the timer expires.
Example:
The following command
configures the GGSN service to enable the RAN Procedure Ready feature
and specify the timeout period as
20 seconds
for the RAN Procedure timer in GGSN:
gtpc ran-procedure-ready-delay
timeout 20
gtpu echo-interval
This command
is obsolete and now available for configuration in GTP-U service configuration
mode.
guard-interval
Configures the time
period after which a redundant PDP context request received from
an SGSN is treated as a new request rather than a re-send of a previous request.
Privilege:
Security Administrator,
Administrator
Syntax
guard-interval guard_time
{ default | no }
guard-interval
default
Configures the default
value for guard-interval function for the GGSN service.
no
Disables the guard-interval
function for the GGSN service.
guard_time
Default: 100
Specifies the amount
of time that must pass before a GGSN service treats a redundant
PDP context request as a new request instead of a re-send of a previous
request.
guard_time is
measured in seconds and can be configured to an integer from 10
through 3600.
Usage:
The guard interval
is used to protect against replay attacks. Without a guard interval configured,
information from a valid PDP context request could be used to gain
un-authorized network access.
If the GGSN service
receives a PDP context request in which the International Mobile Subscriber
Identity (IMSI), the Network Service Access Point Identifier (NSAPI),
the end user IP address, and the GTP sequence number are identical
to those received in a previous request, the GGSN treats the new
request as a re-send of the original. Therefore, information from
a valid PDP context request could be collected and re-sent at a
later time by an un-authorized user to gain network access.
Configuring a guard
interval limits the amount of time that the information contained within
a PDP context request remains valid.
Example:
The following command
configures the GGSN service with a guard interval of
60 seconds:
guard-interval 60
ip local-port
Configures the local
User Datagram Protocol (UDP) port for the Gn interfaces’ GTP-C
socket for GTPv1.
Privilege:
Security Administrator,
Administrator
Syntax
ip local-port gtpc-v1 port#
default ip local-port
gtpc-v1
default
Configures the default
value for the local UDP port for GTP Version 1 control messaging
for this GGSN service.
gtpc-v1 port#
Default: 2123
Specifies the UDP port
number for GTPv1 GTPC sockets.
port# can
be configured to an integer from 1 through 65535.
Usage:
By default, the GGSN
service attempts to use GTPv1 when communicating with SGSNs. This
parameter configures the UDP port over which the GTP control (GTP-C)
sockets are sent.
If an SGSN only supports
GTPv0, the GGSN service automatically switches to GTPv0 when communicating
with this SGSN. In the scenario, the GGSN service communicates with the
SGSN on UDP port 3386 and does not have a GTP-C socket.
IMPORTANT:
The UDP port setting
on the SGSN must match the local-port setting for the GGSN service on
the system in order for the two devices to communicate.
Example:
The following command
configures the GGSN service to use UDP port
2500 for exchanging
GTPC sockets with SGSNs when using GTPv1:
ip local port 2500
ip qos-dscp
Configures the quality
of service (QOS) differentiated service code point (DSCP) used when
sending data packets over the Gn interface.
Privilege:
Security Administrator,
Administrator
Syntax
ip qos-dscp { qci { 1 { dscp } | 2 { dscp } | 3 { dscp } | 4 { dscp } | 5 { dscp | allocation-retention-priority } | 6 { dscp | allocation-retention-priority } | 7 { dscp | allocation-retention-priority } | 8 { dscp | allocation-retention-priority } | 9 { dscp }} | gtpc } +
no ip qos-dscp { qci { 1 | 2 | 3 | 4 | 5 { allocation-retention-priority | dscp } | 6 { allocation-retention-priority | dscp } | 7 { allocation-retention-priority | dscp } | 8 { allocation-retention-priority | dscp } | 9 } | gtpc } +
allocation-retention-priority
Specifies the DSCP
for interactive class if the allocation priority is present in the
QOS profile.
allocation-retention-priority can
be the integer 1, 2, or 3.
DSCP values use the
following matrix to map based on traffic handling priority and Alloc/Retention
priority if the allocation priority is present in the QOS profile.
The following table
shows the DSCP value matrix for allocation-retention-priority.
Table 1. Default DSCP Value
Matrix
| Allocation Priority |
1 |
2 |
3 |
| Traffic Handling Priority |
. |
. |
. |
| 1 |
ef |
ef |
ef |
| 2 |
ef |
ef |
ef |
| 3 |
af21 |
af21 |
af21 |
| . |
af21 |
af21 |
af21 |
qci
Configures the QoS
Class Identifier (QCI) attribute of QOS. Here the qci_val is
the QCI for which the negotiate limit is being set; it ranges from
1 to 9.
dscp
Default QCI:
- 1: ef
- 2: ef
- 3: af11
- 4: af11
- 5: ef
- 6: ef
- 7: af21
- 8: af21
- 9: be
Specifies the DSCP
for the specified traffic pattern. dscp can
be configured to any one of the following:
- af11: Assured Forwarding
11 per-hop-behavior (PHB)
|
- af32: Assured Forwarding
32 PHB
|
- af12: Assured Forwarding
12 PHB
|
- af33: Assured Forwarding
33 PHB
|
- af13: Assured Forwarding
13 PHB
|
- af41: Assured Forwarding
41 PHB
|
- af21: Assured Forwarding
21 PHB
|
- af42: Assured Forwarding
42 PHB
|
- af22: Assured Forwarding
22 PHB
|
- af43: Assured Forwarding
43 PHB
|
- af23: Assured Forwarding
23 PHB
|
- be: Best effort forwarding PHB
|
- af31: Assured Forwarding
31 PHB
|
- ef: Expedited forwarding PHB
|
+
More than one of the
above keywords can be entered within a single command.
Usage:
DSCP levels can be
assigned to specific traffic patterns in order to ensure that data
packets are delivered according to the precedence with which they
are tagged. The diffserv markings are applied to the outer IP header
of every GTP data packet. The diffserv marking of the inner IP header
is not modified.
The traffic patterns
are defined by QCI (1 to 9). Data packets falling under the category
of each of the traffic patterns are tagged with a DSCP that further
indicate their precedence as shown in the following tables:
Table 2. Class structure
for assured forwarding (af) levels
| Drop Precedence |
Class |
| Class 1 |
Class 2 |
Class 3 |
Class
4 |
|
Low
|
af11
|
af21
|
af31
|
af41
|
|
Medium
|
af12
|
af22
|
af32
|
af41
|
|
High
|
af13
|
af23
|
af33
|
af43
|
Table 3. DSCP Precedence
| Precedence (low to
high) |
DSCP |
|
0
|
Best Effort (be)
|
|
1
|
Class 1
|
|
2
|
Class 2
|
|
3
|
Class 3
|
|
4
|
Class 4
|
|
5
|
Express Forwarding
(ef)
|
The DSCP level can
be configured for multiple traffic patterns within a single instance
of this command.
The no ip qos command
can be issued to remove a QOS setting and return it to it’s
default setting.
Example:
The following command
configures the DSCP level for QCI to be Expedited Forwarding,
ef:
ip qos-dscp qci 1 ef
max-retransmissions
Configures the maximum
number of times that GTP control packets are retransmitted to an
SGSN before it marks it unreachable.
Privilege:
Security Administrator,
Administrator
Syntax
max-retransmissions max_number
default max-retransmissions
default
Configures the default
value for maximum retries for GTP control packets for the GGSN service.
max_number
Default: 4
Indicates the maximum
number of times that GTP control packets are retransmitted.
max_number can
be configured to an integer from 0 through 15.
Usage:
This command is used
in conjunction with the timeout command
to control the retransmission of GTP control packets when no response
is received from an SGSN. It is equivalent to the N3-REQUESTS parameter
discussed in 3GPP TS 29.060.
If no response is received
from the SGSN prior to the expiration of the timeout value, the GTP
control packets are re-sent by the GGSN. This process occurs as
many times as allowed by the configuration of this command.
If the max-retransmissions
value is exceeded, the GGSN records a “Path Failure” for
that SGSN and releases all PDP contexts associated with it.
Example:
The following command
configures the maximum number of retransmissions to
8:
max-retransmissions 8
mbms policy
This command enables/disables
the Multimedia Broadcast Multicast Services (MBMS) user service
support for multicast and/or broadcast mode. It also specifies
the policy for MBMS user service mode.
Privilege:
Security Administrator,
Administrator
Syntax
mbms policy { multicst
broadcast | none }
{ no | default } mbms policy
no
Removes or disables
the configured MBMS support for multicast and/or broadcast
mode in this GGSN service.
default
Restores the default
mode of MBMS support in this GGSN service.
multicst broadcast
Enables the MBMS support
and configures the policy for multicast and broadcast of user service.
Usage:
Use this command to
enable/disable the MBMS user service support for Multicast
and/or Broadcast mode. It also specifies the policy for
MBMS user service mode.
Example:
The following command
enables MBMS support in this GGSN service:
mbms policy multicast broadcast
newcall
This command enables
or disables the new call related behavior of this GGSN service when
duplicate sessions with the same IP address request are received.
This feature is required to support interworking with P-GW and HA.
Privilege:
Security Administrator,
Administrator
Syntax
newcall duplicate-subscriber-requested-address { accept | reject }
default newcall duplicate-subscriber-requested-address
default
Restores the default
mode for new call session with the same address request received
in this GGSN service. It rejects calls with duplicate address requests.
accept
Sets the system to “accept” another
session using the same IP address for a new call. The new session
will be created and the old session will be torn down.
Default: Disabled
reject
Rejects new calls with
duplicate address requests. This is the default behavior.
Default: Enabled
Usage:
Use this command to
enable or disable new call connections when the UE is not able to gracefully
disconnect from the Enterprise PDN before attempting to reconnect
via another access method. When enabled this command tears down
the old session in order to accept the new connection with the same
IP address assignment.
This feature also allows
the GGSN to accept a request for a static subscriber address, even if
the address is already used by another session. If this feature
is not enabled, a new request with the same IP address for another
session will be rejected.
IMPORTANT:
This command is a license-enabled
feature.
Example:
The following command
allows the GGSN to accept the duplicate call session request with the
same IP address:
newcall duplicate-subscriber-requested-address accept
path-failure
Determines the GTP
path-failure behavior on echo/non-echo messages.
Privilege:
Security Administrator,
Administrator
Syntax
path-failure detection-policy
gtp { echo [ non-echo ] | non-echo [ echo ] }
{ no | default } path-failure
detection-policy
no
No defined detection
policy means path-failures are not detected.
default
Sets the path-failure
detection-policy to GTP in echo mode.
detection-policy gtp {echo [ non-echo ] | non-echo [ echo ] }
Detection-policy is
the policy to be used when path-failure is in active state. GTP
messages are either gtp(u) (user) or gtp(c) (control) type, and
the gtp keyword takes either echo or non-echo as message type.
echo: gtp(u)
or gtp(c) message.
non-echo:
a message type other than gtp(u) or gtp(c).
Usage:
Under current circumstances,
a GGSN shuts down the GTP tunnel if the associated SGSN does not
respond to multiple retries of an echo or non-echo message from
the GGSN. In this way, a single call failure could be responsible
for the loss of all active calls in the tunnel.
This is also an issue
when echo is disabled, or when there is very little traffic on the
SGSN and the GGSN is configured with large echo intervals.
This behavior adversely
impacts the user experience because the customer has to reconnect
every time this happens with their SGSN.
Example:
The following example
detects path failures when the SGSN fails to respond to multiple echo
message retries:
path-failure detection-policy
gtp echo
The following example
turns off path-failure detection. On timeout of gtp(c) message retries,
the particular context will be purged:
no path-failure detection-policy
plmn id
Configures the GGSN’s
public land mobile network (PLMN) identifiers. Up to five PLMN IDs
can be configured for each GGSN service.
Privilege:
Security Administrator,
Administrator
Syntax
plmn id mcc mcc_valuemnc mnc_value [ primary ]
no plmn id mcc mcc_value mnc mnc_value
no
Removes a previously
configured PLMN identifier for the GGSN service.
mcc mcc_value
Specifies the mobile
country code (MCC) portion of the PLMN’s identifier.
mcc_number is
the PLMN MCC identifier and can be configured to an integer between
100 and 999.
mnc mnc_value
Specifies the mobile
network code (MNC) portion of the PLMN’s identifier.
mnc_number is
the PLMN MNC identifier and can be configured to any 2- or 3-digit
integer from 00 through 999.
primary
When multiple PLMN
IDs are configured, the primary keyword
can be used to designate one of the PLMN IDs to be used for the
AAA attribute (3GPP-GGSN-MCC-MNC).
Usage:
The PLMN identifier
is used by the GGSN service to determine whether or not a mobile station
is visiting, roaming, or home. Multiple GGSN services can be configured
with the same PLMN identifier. Up to five PLMN IDs can be configured
for each GGSN Service.
Example:
The following command
configures the PLMN identifier with an MCC of
462 and MNC
of
2:
plmn id mcc 462 mnc 02
plmn unlisted-sgsn
Configures the GGSN’s
policy for handling communications from SGSNs with which it is not
configured to communicate.
Privilege:
Security Administrator,
Administrator
Syntax
default
plmn unlisted-sgsn
plmn
unlisted-sgsn [[ foregn [ disable-gtpc-echo | reject-foreign-subscriber ] | home [ disable-gtpc-echo ]] | reject ] ]
default
Resets configured parameters
to their default settings.
foreign
Default: Disabled
Specifies that the
GGSN service accepts messages from SGSNs that are not configured within
the service using the sgsn
address command.
This keyword also dictates
that unlisted SGSNs are treated as if they belong to a foreign PLMN.
Therefore, PDP contexts originating from them are treated as visiting
or roaming.
mcc mcc_value
Specifies the mobile
country code (MCC) portion of the PLMN’s identifier.
mcc_value is
the PLMN MCC identifier and can be configured to an integer from
100 through 999.
mnc mnc_value
Specifies the mobile
network code (MNC) portion of the PLMN’s identifier.
mnc_value is
the PLMN MNC identifier and can be configured to a 2- or 3-digit
integer from 00 through 999.
disable-gtpc-echo
Default: Send GTPC
Echo messages to unlisted SGSNs.
When this keyword is
specified, GTPC echo messages are not sent to unlisted SGSNs.
reject-foreign-subscriber
Default: Disabled
Specifies that incoming
calls from foreign subscribers are rejected.
home
Default: Disabled
Specifies that the
GGSN service accepts messages from SGSNs that are not configured within
the service using the sgsn
address command.
This keyword also dictates
that unlisted SGSNs are treated as if they belong to the GGSN service’s
home PLMN.
rat-type { GAN | GERAN | HSPA | UTRAN | WLAN }
This keyword configures
the type of radio access technology.
GAN: Specifies
the Generic Access Network type of Radio Access Technology (RAT).
GERAN: Specifies
the GSM EDGE Radio Access Network type of RAT.
HSPA: Specifies
the High Speed Packet Access type of RAT.
UTRAN: Specifies
the UMTS Terrestrial Radio Access Network type of RAT.
WLAN: Specifies
the Wireless Local Access Network type of RAT.
reject
Default: Enabled
Specifies that the
GGSN service rejects messages from SGSNs that are not configured within
the service using the sgsn
address command.
When the GGSN service
rejects the message(s), it returns a cause code of No Resources
199 (C7H, No resources available).
Usage:
This command works
in conjunction with the sgsn command
that configures the GGSN service to communicate with specific SGSNs.
Any messages received from SGSNs not configured in that list are
subject to the rules dictated by the unlisted-sgsn policy.
Example:
The following command
configures the GGSN service to accept messages from unlisted SGSNs
and treat the SGSN as if it is on the GGSN’s home network:
plmn unlisted-sgsn
accept home
policy
Specifies the reject
code to be used in the “Create PDP Context” response message
when a RADIUS server timeouts.
Privilege:
Security Administrator,
Administrator
Syntax
policy { accounting-server-timeout
use-reject-code { system-failure | no-resources } | authentication-server-timeout
use-reject-code { system-failure | user-authentication-failure } }
default policy { authentication-server-timeout | accounting-server-timeout }
default
Restores the specified
parameter to its default setting.
accounting-server-timeout
use-reject-code { system-failure | no-resources }
Default: no-resources
Specifies the reject
code used by the GGSN if communication with an accounting server times
out. The possible reject codes are:
- system-failure (204
(CCH))
- no-resources (199 (C7H))
authentication-server-timeout
use-reject-code {system-failure | user-authentication-failure }
Default: user-authentication-failure
Specifies the reject
code used by the GGSN if communication with an authentication server times
out. The possible reject codes are:
- system-failure (204
(CCH))
- user-authentication-failure
(209 (D1H))
Usage:
This command is used
to configure the cause code used by the GGSN if communication with
either a RADIUS authentication or accounting server times out.
When this parameter
is used in conjunction with Radius accounting servers, the response
is only set if a flag is configured in the APN Delay GTP Response,
only after getting a response to the Accounting Start.
Example:
The following command
configures the GGSN response to a RADIUS authentication server timeout
to be
system-failure:
policy authentication-server-timeout
use-reject-code system-failure
retransmission-timeout
Configures the timeout
period in between retransmissions of GTP control packets. This timeout
configuration is not applicable on Echo Request retransmission.
Privilege:
Security Administrator,
Administrator
Syntax
retransmission-timeout retransmit_time
default retransmission-timeout
default
Configures the default
time interval that must pass without an SGSN response before the GGSN
service retransmits GTP control packets.
retransmit_time
Default: 5
Specifies the amount
of time that must pass without an SGSN response before the GGSN service
retransmits GTP control packets.
retransmit_time is
measured in seconds and can be configured to an integer from 1 through
20.
Usage:
This command is used
in conjunction with the max-retransmissions command
to control the retransmission of GTP control packets when no response
is received from an SGSN.
If no response is received
from the SGSN prior to the expiration of the timeout value, the GTP
control packets are re-sent by the GGSN. This process occurs as
many times as allowed by the configuration of the max-retransmissions
command.
If the max-retransmissions
value is exceeded within the retransmission-timeout period, the GGSN
records a “Path Failure” for that SGSN and releases
all PDP contexts associated with it.
IMPORTANT:
This retransmission
timeout configuration in not applicable for Echo Requests message retransmission.
Echo are sent/retransmitted every echo interval, which
can be configured separately.
Example:
The following command
configures a timeout value of
20 seconds:
retransmission-timeout 20
setup-timeout
Configures the maximum
amount of time the GGSN service allows for the setting up of PDP
contexts.
Privilege:
Security Administrator,
Administrator
Syntax
setup-timeout setup_time
default setup-timeout
default
Configures the default
maximum amount of time the GGSN service allows for the setting up of
PDP contexts.
setup-time
Default: 60
Specifies the maximum
amount of time the GGSN service allows for the setting up of PDP contexts.
setup_time is
measured in seconds and can be configured to an integer from 1 through
6000.
Usage:
Use this command to
limit the amount of time allowed for setting up PDP contexts. If
the PDP context is not setup within the configured time frame, the
GGSN service rejects the PDP context with a cause code of 199 (C7H,
No resources available).
Example:
The following command
allows a maximum of
120 seconds
for the setting up of PDP contexts:
setup-timeout 120
sgsn address
Configures the SGSNs
that this GGSN service is allowed to communicate with.
Privilege:
Security Administrator,
Administrator
Syntax
sgsn address { { ip_address [ subnetmask netmask ] } | ip_address/netmask } [ plmn-foreign [ reject-foreign-subscriber ] | mcc mcc_code mnc mnc_code [ reject-foreign-subscriber ] ] [ rat-type { GAN | GERAN | HSPA | UTRAN | WLAN } ] [ description description ] [ disable-gtpc-echo ]
no sgsn { address ip_address [ subnetmask netmask ] }
no
Removes a specific
SGSN from the list or all configured SGSNs.
address
Configures the IP address
of the SGSN.
ip_address must
be expressed in IPv4 dotted-decimal notation.
subnetmask
Configures the subnet
mask of the SGSN.
netmask must
be expressed in IPv4 dotted-decimal notation.
disable-gtpc-echo
Default: Send GTPC
Echo messages to unlisted SGSNs.
When this keyword is
specified, GTPC echo messages are not sent to unlisted SGSNs.
plmn-foreign
Indicates whether or
not the SGSN belongs to a foreign public land mobile network (PLMN).
reject-foreign-subscriber
Default: Disabled
Specifies that incoming
calls from foreign subscribers are rejected.
mcc mcc_code
Specifies the mobile
country code (MCC) portion of the PLMN’s identifier.
mcc_code is
the PLMN MCC identifier and configured as an integer from 100 through
999.
mnc mnc_code
Specifies the mobile
network code (MNC) portion of the PLMN’s identifier.
mnc_code is
the PLMN MNC identifier and configured as a 2- or 3-digit integer
from 00 through 999.
rat-type {GAN | GERAN | HSPA | UTRAN | WLAN }
This keyword configures
the type of radio access technology.
GAN: Specifies
the Generic Access Network type of Radio Access Technology (RAT).
GERAN: Specifies
the GSM EDGE Radio Access Network type of RAT.
HSPA: Specifies
the High Speed Packet Access type of RAT.
UTRAN: Specifies
the UMTS Terrestrial Radio Access Network type of RAT.
WLAN: Specifies
the Wireless Local Access Network type of RAT.
description description
Add description field
to the SGSN entry in GGSN service.
description is
an alphanumeric string of 1 through 63 characters.
Usage:
Use this command to
configure a list of SGSNs that the GGSN service is to communicate with.
This command can be entered multiple times to configure multiple
SGSNs.
IMPORTANT:
The GGSN only communicates
with the SGSNs configured using this command unless a plmn-policy
is enabled to allow communication with unconfigured SGSNs. PLMN
policies are configured using the plmn unlisted-sgsn command.
Example:
The following command
configures the GGSN to communicate with an SGSN on a foreign PLMN
with an IP address of
192.168.1.100 and
subnet mask of
255.255.255.0:
sgsn address 192.168.1.100
subnetmask 255.255.255.0 plmn-foreign
sgsn define-multiple-address-group
This command defines
an SGSN Multiple Address Group and enters SGSN Multiple Address
Group Configuration mode. Whenever there is a change in the control
address in a GTPC UPC message, it is treated as an inter-SGSN handoff
because an SGSN is usually identified uniquely by a single IP-address.
This command supports a multiple address group feature which allows
you to specify a set of addresses that specify a single SGSN. When
a UPC handoff is received from any address in the group, it is treated
as an intra-SGSN handoff.
Privilege:
Security Administrator,
Administrator
Syntax
sgsn define-multiple-address-group grp_name [ -noconfirm ]
no sgsn define-multiple-address-group grp_name
no
Removes a specific
SGSN Multiple Address Group from the list GGSN service configuration.
grp_name
Specifies the name
of an SGSN multiple address group to create or configure.
grp_nameis
an alphanumeric string from 1 through 63 characters.
-noconfirm
Specifies that the
command must execute without any additional prompt and confirmation from
the user.
Usage:
Use this command to
create or configure an SGSN Multiple Address Group that the GGSN service
is to communicate with. This command can be entered multiple times
to configure multiple SGSN Multiple Address Groups.
Example:
The following command
creates an SGSN Multiple Address Group named
sgsngrp1 and
enters SGSN Multiple Address Group Configuration mode:
sgsn define-multiple-address-group sgsngrp1
sgsn multiple-address-group
Configures the SGSN
multiple address groups that this GGSN service is allowed to communicate
with.
Privilege:
Security Administrator,
Administrator
Syntax
sgsn multiple-address-group grp_name [ disable-gtpc-echo ] [ mcc mcc_code mnc mnc_code [ reject-foreign-subscriber ] ] [ plmn-foreign [ reject-foreign-subscriber ] [ rat-type { GAN | GERAN | HSPA | UTRAN | WLAN } ] [ description description ]
no sgsn multiple-address-group grp_name
no
Removes a specific
SGSN multiple address group from the list of configured SGSN multiple address
groups.
grp_name
Specifies the name
of a configured SGSN multiple address group to use.
disable-gtpc-echo
Default: Send GTPC
Echo messages to unlisted SGSNs.
When this keyword is
specified, GTPC echo messages are not sent to unlisted SGSNs.
plmn-foreign
Indicates whether or
not the SGSN multiple address group belongs to a foreign public
land mobile network (PLMN).
reject-foreign-subscriber
Default: Disabled
Specifies that incoming
calls from foreign subscribers are rejected.
mcc mcc_code
Specifies the mobile
country code (MCC) portion of the PLMN’s identifier.
mcc_code is
the PLMN MCC identifier and can be configured to an integer from
100 through 999.
mnc mnc_code
Specifies the mobile
network code (MNC) portion of the PLMN’s identifier.
mnc_code is
the PLMN MNC identifier configured as a 2- or 3-digit integer from
00 through 999.
rat-type { GAN | GERAN | HSPA | UTRAN | WLAN }
This keyword configures
the type of radio access technology.
GAN: Specifies
the Generic Access Network type of Radio Access Technology (RAT).
GERAN: Specifies
the GSM EDGE Radio Access Network type of RAT.
HSPA: Specifies
the High Speed Packet Access type of RAT.
UTRAN: Specifies
the UMTS Terrestrial Radio Access Network type of RAT.
WLAN: Specifies
the Wireless Local Access Network type of RAT.
description description
Add a description field
to the SGSN multiple address group entry in the GGSN service configuration.
description must
be an alphameric string of 1 through 63 characters.
Usage:
Use this command to
configure a list of SGSN multiple address groups with which the GGSN
service is to communicate. This command can be entered multiple
times to configure multiple SGSN multiple address groups.
IMPORTANT:
The GGSN only communicates
with the SGSN multiple address groups configured using this command
unless a plmn-policy is enabled to allow communication with unconfigured
SGSNs. PLMN policies are configured using the plmn unlisted-sgsn command.
Example:
The following command
configures the GGSN to communicate with an SGSN with multiple address
that is defined by an SGSN multiple address group named
sgsngrp1 that
is on a foreign PLMN:
sgsn multiple-address-group
sgsngrp1 plmn-foreign
sgsn mcc-mnc
This command configures
sgsn mcc-mnc for this GGSN service.
Privilege:
Security Administrator,
Administrator
Syntax
sgsn mcc-mnc { prefer-rai | prefer-uli }
default sgsn mcc-mnc
default
Configures the default
option for sgsn mcc-mnc. Default is ‘prefer-uli’.
prefer-rai
Configures sgsn mcc-mnc
using rai.
prefer-uli
Configures sgsn mcc-mnc
using uli.
Usage:
Use this command to
configure the sgsn mcc-mnc.
Example:
The following command
configures the sgsn mcc-mnc to ‘prefer-rai’:
sgsn mcc-mnc prefer-rai
trace-collection-entity
This command configures
the trace collection entity IP address. Trace collection entity
is the destination node to which trace files are transferred and
stored.
Privilege:
Security Administrator,
Administrator
Syntax
trace-collection-entity IPv4_addr
no trace-collection-entity
no
Removes the configured
IPv4 address for trace collection in this GGSN service.
IPv4_addr
Specifies the IP address
in IPv4 dotted-decimal notation.
Usage:
Use this command to
configure the trace collection entity IP address. This configuration
is required because during signaling session trace activation, CPC
REQ and UPC REQ do not provide the IP address for the trace collection
entity.
Example:
The following command
configures the trace collection entity IP address with this GGSN service:
trace-collection-entity 192.36.56.56