Table Of Contents
Cisco IOS Mobile Wireless GGSN Commands
access-violation deactivate-pdp-context
clear ggsn quota-server statistics
clear gprs access-point statistics
clear gprs charging cdr all no-transfer
clear gprs redundancy statistics
clear gprs service-aware statistics
gprs canonical-qos best-effort bandwidth-factor
gprs canonical-qos gsn-resource-factor
gprs canonical-qos premium mean-throughput-deviation
Cisco IOS Mobile Wireless GGSN Commands
This book documents all of the Cisco IOS software commands in Cisco IOS Release 12.3(14)YU for the Gateway GPRS Support Node (GGSN), in alphabetical order.
aaa-accounting
To enable or disable accounting for a particular access point on the GGSN, use the aaa-accounting access-point configuration command.
aaa-accounting [enable | disable | interim update]
Syntax Description
Defaults
enable—For non-transparent APNs
disable—For transparent APNs
Interim accounting is disabled.
Command Modes
Access-point configuration
Command History
Usage Guidelines
You can configure AAA accounting services at an access point. However, for accounting to occur, you also must complete the configuration by specifying the following other configuration elements on the GGSN:
•
Enable AAA services using the aaa new-model global configuration command.
•
•
–
–
–
•
•
Note
You can verify whether AAA accounting services are configured at an APN using the show gprs access-point command.
There is not a no form of this command.
Enabling and Disabling Accounting Services for an Access Point
The Cisco Systems GGSN has different defaults for enabling and disabling accounting services for transparent and non-transparent access points:
•
•
To selectively disable accounting at specific APNs where you do not want that service, use the aaa-accounting disable access-point configuration command.
Configuring Interim Accounting for an Access Point
Using the aaa-accounting interim access-point configuration command, you can configure the GGSN to send Interim-Update Accounting requests to the AAA server when a routing area update (resulting in an SGSN change) or QoS change has occurred for a PDP context. These changes are conveyed to the GGSN by an Update PDP Context request.
Note
There is not a no form of this command.
Examples
Example 1
The following configuration example disables accounting at access-point 1:
interface virtual-template 1gprs access-point-list abc!gprs access-point-list abcaccess-point 1access-point-name gprs.pdn.com access-mode non-transparentaaa-accounting disableExample 2
The following configuration example enables accounting on transparent access-point 4. Accounting is disabled on access-point 5 because it is configured for transparent mode and the aaa-accounting enable command is not explicitly configured.
Accounting is automatically enabled on access-point 1 because it has been configured for non-transparent access mode. Accounting is explicitly disabled at access-point 3, because accounting is automatically enabled for non-transparent access mode.
An example of some of the AAA and RADIUS global configuration commands are also shown:
aaa new-model!aaa group server radius fooserver 10.2.3.4server 10.6.7.8aaa group server radius foo1server 10.10.0.1aaa group server radius foo2server 10.2.3.4server 10.10.0.1aaa group server foo3server 10.6.7.8server 10.10.0.1!aaa authentication ppp foo group fooaaa authentication ppp foo2 group foo2aaa authorization network default group radiusaaa accounting exec default start-stop group fooaaa accounting network foo1 start-stop group foo1aaa accounting network foo2 start-stop group foo2!gprs access-point-list gprsaccess-point 1access-mode non-transparentaccess-point-name www.pdn1.comaaa-group authentication foo!access-point 3access-point-name www.pdn2.comaccess-mode non-transparentaaa-accounting disableaaa-group authentication foo!access-point 4access-point-name www.pdn3.comaaa-accounting enableaaa-group accounting foo1!access-point 5access-point-name www.pdn4.com!gprs default aaa-group authentication foo2gprs default aaa-group accounting foo3!radius-server host 10.2.3.4 auth-port 1645 acct-port 1646 non-standardradius-server host 10.6.7.8 auth-port 1645 acct-port 1646 non-standardradius-server host 10.10.0.1 auth-port 1645 acct-port 1646 non-standardradius-server key ggsntelRelated Commands
aaa group server diameter
To group different server hosts into distinct lists and distinct methods, use the aaa group server diameter access-point configuration command. To remove a group, use the no form of this command
aaa group server diameter group-name
no aaa group server diameter group-name
Syntax Description
diameter
Defines a Diameter AAA group.
group name
Character string used to name the group of servers.
Defaults
No default behavior or values.
Command Modes
Access-point configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
The authentication, authorization, and accounting (AAA) server-group feature provides a way to group existing server hosts. The feature enables you to select a subset of the configured server hosts and use them for a particular service.
A server group is a list of server hosts of a particular type. Currently supported server host types are RADIUS server hosts, TACACS+ server hosts, and Diameter server hosts. A server group is used in conjunction with a global server host list. The server group lists the IP addresses of the selected server hosts.
Note
Examples
The following example shows the configuration of two AAA consisting of DCCA server hosts named dcca-sg1 and dcca-sg2:
aaa group server diameter dcca-sg1server dcca1aaa group server diameter dcca-sg2server dcca2Related Commands
aaa-group
To specify a AAA server group and assign the type of AAA services to be supported by the server group for a particular access point on the GGSN, use the aaa-group access-point configuration command. To remove a AAA server group, use the no form of this command.
aaa-group {authentication | accounting} server-group
no aaa-group {authentication | accounting} server-group
Syntax Description
Defaults
No default behavior or values.
Command Modes
Access-point configuration
Command History
Usage Guidelines
The Cisco Systems GGSN supports authentication and accounting at APNs using AAA server groups. By using AAA server groups, you gain the following benefits:
•
•
•
The GGSN supports the implementation of AAA server groups at both the global and access-point configuration levels. You can minimize your configuration by specifying the configuration that you want to support across most APNs, at the global configuration level. Then, at the access-point configuration level, you can selectively modify the services and server groups that you want to support at a particular APN. Therefore, you can override the AAA server global configuration at the APN configuration level.
To configure a default AAA server group to be used for all APNs on the GGSN, use the gprs default aaa-group global configuration command. To specify a different AAA server group to be used at a particular APN for authentication or accounting, use the aaa-group access-point configuration command.
If accounting is enabled on the APN, then the GGSN looks for an accounting server group to be used for the APN in the following order:
•
•
•
•
If none of the above commands are configured on the GGSN, then AAA accounting is not performed.
If authentication is enabled on the APN, then the GGSN first looks for an authentication server group at the APN, configured in the aaa-group authentication command. If an authentication server group is not found at the APN, then the GGSN looks for a globally configured, GPRS default authentication server group, configured in the gprs default aaa-group authentication command.
To complete the configuration, you also must specify the following configuration elements on the GGSN:
•
•
•
•
–
–
–
•
–
You can enable or disable accounting services at the APN using the aaa-accounting command.
–
You can verify the AAA server groups that are configured for an APN using the show gprs access-point command.
Note
Examples
The following configuration example defines four AAA server groups on the GGSN: foo, foo1, foo2, and foo3, shown by the aaa group server commands.
Using the gprs default aaa-group command, two of these server groups are globally defined as default server groups: foo2 for authentication, and foo3 for accounting.
At access-point 1, which is enabled for authentication, the default global authentication server group of foo2 is overridden and the server group named foo is designated to provide authentication services on the APN. Notice that accounting services are not explicitly configured at that access point, but are automatically enabled because authentication is enabled. Because there is a globally defined accounting server-group defined, the server named foo3 will be used for accounting services.
At access-point 2, which is enabled for authentication, the default global authentication server group of foo2 is used. Because there is a globally defined accounting server-group defined, the server named foo3 will be used for accounting services.
At access-point 4, which is enabled for accounting using the aaa-accounting enable command, the default accounting server group of foo3 is overridden and the server group named foo1 is designated to provide accounting services on the APN.
Access-point 5 does not support any AAA services because it is configured for transparent access mode, and accounting is not enabled.
aaa new-model!aaa group server radius fooserver 10.2.3.4server 10.6.7.8aaa group server radius foo1server 10.10.0.1aaa group server radius foo2server 10.2.3.4server 10.10.0.1aaa group server foo3server 10.6.7.8server 10.10.0.1!aaa authentication ppp foo group fooaaa authentication ppp foo2 group foo2aaa authorization network default group radiusaaa accounting exec default start-stop group fooaaa accounting network foo1 start-stop group foo1aaa accounting network foo2 start-stop group foo2aaa accounting network foo3 start-stop group foo3!gprs access-point-list gprsaccess-point 1access-mode non-transparentaccess-point-name www.pdn1.comaaa-group authentication foo!access-point 2access-mode non-transparentaccess-point-name www.pdn2.com!access-point 4access-point-name www.pdn4.comaaa-accounting enableaaa-group accounting foo1!access-point 5access-point-name www.pdn5.com!gprs default aaa-group authentication foo2gprs default aaa-group accounting foo3!radius-server host 10.2.3.4 auth-port 1645 acct-port 1646 non-standardradius-server host 10.6.7.8 auth-port 1645 acct-port 1646 non-standardradius-server host 10.10.0.1 auth-port 1645 acct-port 1646 non-standardradius-server key ggsntelRelated Commands
access-mode
To specify whether the GGSN requests user authentication at the access point to a PDN, use the access-mode access-point configuration command. To remove an access mode and return to the default value, use the no form of this command.
access-mode {transparent | non-transparent}
no access-mode {transparent | non-transparent}
Syntax Description
Defaults
transparent
Command Modes
Access-point configuration
Command History
Usage Guidelines
Use the access-mode command to specify whether users accessing a PDN through a particular access point associated with the virtual template interface have transparent or non-transparent access to the network.
Transparent access means that users who access the PDN through the current virtual template are granted access without further authentication.
Non-transparent access means that users who access the PDN through the current virtual template must be authenticated by the GGSN. You must configure non-transparent access to support RADIUS services at an access point. Authentication is performed by the GGSN while establishing the PDP context.
Examples
Example 1
The following example specifies non-transparent access to the PDN, gprs.pdn.com, through access-point 1:
interface virtual-template 1gprs access-point-list abc!gprs access-point-list abcaccess-point 1access-point-name gprs.pdn.com access-mode non-transparentExample 2
The following example specifies transparent access to the PDN, gprs.pdn2.com, through access-point 2:
interface virtual-template 1gprs access-point-list abc!gprs access-point-list abcaccess-point 2access-point-name gprs.pdn2.com
Note
Related Commands
access-point
To specify an access point number and enter access-point configuration mode, use the access-point access-point list configuration command. To remove an access point number, use the no form of this command.
access-point access-point-index
no access-point access-point-index
Syntax Description
Defaults
No default behavior or values.
Command Modes
Access-point list configuration
Command History
Usage Guidelines
Use the access-point command to create an access point to a PDN.
To configure an access point, first set up an access-point list using the gprs access-point-list command and then add the access point to the access-point list.
You can specify access point numbers in any sequence.
Note
Examples
The following example configures an access point with an index number of 7 in an access-point-list named "abc" on the GGSN:
gprs access-point-list abcaccess-point 7Related Commands
access-point-name
To specify the network (or domain) name for a PDN that users can access from the GGSN at a defined access point, use the access-point-name access-point configuration command. To remove an access point name, use the no form of this command.
access-point-name apn-name
no access-point-name
Syntax Description
apn-name
Specifies the network or domain name of the private data network that can be accessed through the current access point.
Defaults
There is no default value for this command.
Command Modes
Access-point configuration
Command History
Usage Guidelines
Use the access-point-name command to specify the PDN name of a network that can be accessed through a particular access point. An access-point name is mandatory for each access point.
To configure an access point, first set up an access-point list using the gprs access-point-list command and then add the access point to the access-point list.
The access-point name typically is the domain name of the service provider that users access, for example, www.isp.com.
Examples
The following example specifies the access-point name for a network:
access-point 1access-point-name www.isp.comexitRelated Commands
access-type
To specify whether an access point is real or virtual on the GGSN, use the access-type access-point configuration command. To return to the default value, use the no form of this command.
access-type {virtual [pre-authenticate [default-apn apn-name]] | real}
no access-type {virtual [pre-authenticate [default-apn apn-name]] | real}
Syntax Description
Defaults
real
Command Modes
Access-point configuration
Command History
Usage Guidelines
Use the access-type command to specify whether an access point is real or virtual on the GGSN.
The default access-type is real. Therefore, you only need to configure this command if the APN needs to be a virtual access point.
Virtual access types are used to configure virtual APN support on the Cisco GGSN to minimize provisioning issues in other GPRS network entities that require configuration of APN information.
By default, using the virtual APN feature on the GGSN, HLR subscription data can simply provide the name of the virtual APN. User's can still request access to specific target networks that are accessible by the GGSN without requiring each of those destination APNs to be provisioned at the HLR.
The default keyword, real, identifies a physical target network that the GGSN can reach. Real APNs must always be configured on the GGSN to reach external networks.
Virtual APNs can be configured in addition to real access points to ease provisioning in the GPRS PLMN.
Note
The default virtual APN support relies on the domain portion of the username to resolve the target APN. Once, the target is resolved, the user is then connection to that APN on the GGSN.
Cisco GGSN Release 6.0 and later, supports pre-authentication-based virtual access points. The pre-authentication-based virtual APN feature utilizes AAA servers to provide dynamic, per-user mapping of a virtual APN to a target (real) APN.
When the pre-authenticate keyword option is specified when configuring a virtual APN, a pre-authentication phase is applied to Create PDP Context requests received that include a virtual APN in the APN information element.
Pre-authentication-based virtual APN requires that the AAA server be configured to provision user profiles to include the target APN. The AAA maps a user to the target using user identifications such as the IMSI, user name, or MSISDN, etc. Additionally, the target APN must be locally configured on the GGSN.
The following is the typical call flow with regard to external AAA servers when a virtual APN is involve:
1.
2.
3.
–
–
–
4.
When configuring pre-authentication-based virtual APN functionality, please note the following:
When configuring pre-authentication-based virtual APN functionality, please note the following:
•
•
•
•
•
•
Note
Examples
Example 1
The following example shows configuration of a virtual access point type and a real access point type:
access-point 1access-point-name corporateaccess-type virtualexitaccess-point 2access-point-name corporatea.comip-address-pool dhcp-clientdhcp-server 10.21.21.1Example 2
The following example enables pre-authentication-based virtual APN functionality for virtual access point and specifies "cisco.com" as the default APN if a target APN is not resolved.
access-point 1access-point-name virtual-apn-allaccess-type virtual pre-authenticate default-apn cisco.comanonymous user anyone abcradius attribute user-name msisdnexitRelated Commands
access-violation deactivate-pdp-context
To specify that a user's session be ended and the user packets discarded when a user attempts unauthorized access to a PDN through an access point, use the access-violation deactivate-pdp-context command. To return to the default value, use the no form of this command.
access-violation deactivate-pdp-context
no access-violation deactivate-pdp-context
Syntax Description
This command has no arguments or keywords.
Defaults
The user's session remains active and the user packets are discarded.
Command Modes
Access-point configuration
Command History
Usage Guidelines
Use the access-violation deactivate-pdp-context command to specify the action that is taken if a user attempts unauthorized access through the specified access point.
The default is that the GGSN simply drops user packets when an unauthorized access is attempted. However, if you specify access-violation deactivate-pdp-context, the GGSN terminates the user's session in addition to discarding the packets.
Examples
The following example shows deactivation of a user's access in addition to discarding the user packets:
access-point 1access-point-name pdn.aaaa.comip-access-group 101 inaccess-violation deactivate-pdp-contextexitRelated Commands
Specifies the network (or domain) name for a PDN that users can access from the GGSN at a defined access point.
address ipv4
To configure a route to the host of the Diameter peer using IPv4, use the address ipv4 diameter peer configuration command. To remove the address, use the no form of this command.
address ipv4 ip-address
no address ipv4 ip-address
Syntax Description
Defaults
No default behavior or values.
Command Modes
Diameter peer configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the address ipv4 command to define the IP address of the host of the Diameter peer using IPv4.
Examples
The following configuration example defines the IP address of the host of the Diameter peer as 10.10.10.1:
diameter peer dcca1address ipv4 10.10.10.1Related Commands
.
advertise downlink next-hop
To configure the next hop address (the user address) on the GGSN downlink traffic (CSG-to-GGSN) to be advertised in Accounting Start requests, use the advertise downlink next-hop command access-point configuration mode. To remove a next hop address configuration, use the no form of this command.
advertise downlink next-hop ip-address
no advertise downlink next-hop ip-address
Syntax Description
Defaults
No default behavior or values.
Command Modes
Access-point configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the advertise downlink next-hop command to configure the next hop IP address, to which downlink traffic destined for the GGSN is to be routed, to be advertised in Accounting Start requests.
Examples
The following configuration example configures 10.10.150.2 as the next hop address to be advertised:
advertise downlink next-hop 10.10.150.2Related Commands
aggregate
To configure the GGSN to create an aggregate route in its IP routing table, when receiving PDP requests from MSs on the specified network, for a particular access point on the GGSN, use the aggregate access-point configuration command. To remove an aggregate route, use the no form of this command.
aggregate {auto | ip-network-prefix{/mask-bit-length | ip-mask}}
no aggregate {auto | ip-network-prefix{/mask-bit-length | ip-mask}}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Access-point configuration
Command History
Usage Guidelines
The GGSN uses a static host route to forward user data packets received from the Gi interface to the Gn interface using the virtual template interface of the GTP tunnel.
Without the aggregate command or gprs default aggregate command, the GGSN creates a static host route for each PDP context. For example, for 45,000 PDP contexts supported, the GGSN creates 45,000 static host routes in its IP routing table.
You can use the aggregate command to reduce the number of static routes implemented by the GGSN for PDP contexts at a particular access point. The aggregate command allows you to specify an IP network prefix to combine the routes of PDP contexts from the same network as a single route on the GGSN.
To configure the GGSN to automatically aggregate routes that are returned by a DHCP or RADIUS server, use the aggregate auto command at the APN.
Note
Automatic route aggregation can be configured at the access-point configuration level only on the GGSN. The gprs default aggregate global configuration command does not support the auto option; therefore, you cannot configure automatic route aggregation globally on the GGSN.
You can specify multiple aggregate commands at each access point to support multiple network aggregates. However, if you use the aggregate auto command at the APN, you cannot specify any other aggregate route ranges at the APN.
To globally define an aggregate IP network address range for all access points on the GGSN for statically derived addresses, you can use the gprs default aggregate command. You can use the aggregate command to override this default address range at a particular access point.
The GGSN responds in the following manner to manage routes for MSs through an access point, when route aggregation is configured in the following scenarios:
•
•
–
–
•
–
–
–
•
–
–
Use care when assigning IP addresses to an MS before you configure the aggregation ranges on the GGSN. A basic guideline is to aggregate as many addresses as possible, but to minimize your use of aggregation with respect to the total amount of IP address space being used by the access point.
Note
Use the show gprs access-point command to display information about the aggregate routes that are configured on the GGSN. The aggregate output field appears only when aggregate routes have been configured on the GGSN, or the auto option is configured.
Use the show ip route command to verify whether the static route is in the current IP routing table on the GGSN. The static route created for any PDP requests (aggregated or non-aggregated) appears with the code "U" in the routing table indicating a per-user static route.
Note
Examples
Example 1
The following example specifies two aggregate network address ranges for access point 8. The GGSN will create aggregate routes for PDP context requests received from MSs with IP addresses on the networks 172.16.0.0 and 10.0.0.0:
gprs access-point-list gprsaccess-point 8access-point-name pdn.aaaa.comaggregate 172.16.0.0/16aggregate 10.0.0.0/8
Note
Example 2
The following example shows a route aggregation configuration for access point 8 using DHCP on a GGSN implement on the Cisco 7200 series router platform, along with the associated output from the show gprs gtp pdp-context all command and the show ip route commands.
Notice that the aggregate auto command is configured at the access point where DHCP is being used. The dhcp-gateway-address command specifies the subnet addresses to be returned by the DHCP server. This address should match the IP address of a loopback interface on the GGSN. In addition, to accommodate route aggregation for another subnet 10.80.0.0, the gprs default aggregate global configuration command is used.
In this example, the GGSN aggregates routes for dynamically derived addresses for MSs through access point 8 based upon the address and mask returned by the DHCP server. For PDP context requests received for statically derived addresses on the 10.80.0.0 network, the GGSN also implements an aggregate route into its routing table, as configured by the gprs default aggregate command.
interface Loopback0ip address 10.80.0.1 255.255.255.255!interface Loopback2ip address 10.88.0.1 255.255.255.255!gprs access-point-list gprsaccess-point 8access-point-name pdn.aaaa.comip-address-pool dhcp-proxy-clientaggregate autodhcp-server 172.16.43.35dhcp-gateway-address 10.88.0.1exit!gprs default aggregate 10.80.0.0 255.255.255.0In the following output for the show gprs gtp pdp-context all command, 5 PDP context requests are active on the GGSN for pdn.aaaa.com from the 10.88.0.0/24 network:
GGSN# show gprs gtp pdp-context allTID MS Addr Source SGSN Addr APN6161616161610001 10.88.0.1 DHCP 172.16.123.1 pdn.aaaa.com6161616161610002 10.88.0.2 DHCP 172.16.123.1 pdn.aaaa.com6161616161610003 10.88.0.3 DHCP 172.16.123.1 pdn.aaaa.com6161616161610004 10.88.0.4 DHCP 172.16.123.1 pdn.aaaa.com6161616161610005 10.88.0.5 DHCP 172.16.123.1 pdn.aaaa.comThe following output for the show ip route command shows a single static route in the IP routing table for the GGSN, which routes the traffic for the 10.88.0.0/24 subnet through the virtual template (or Virtual-Access1) interface:
GGSN# show ip routeCodes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGPD - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter areaN1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGPi - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS interarea* - candidate default, U - per-user static route, o - ODRP - periodic downloaded static routeGateway of last resort is not set10.80.0.0/16 is subnetted, 1 subnetsC 10.80.0.0 is directly connected, Loopback010.113.0.0/16 is subnetted, 1 subnetsC 10.113.0.0 is directly connected, Virtual-Access1172.16.0.0/16 is variably subnetted, 3 subnets, 3 masksC 172.16.43.192/28 is directly connected, FastEthernet0/0S 172.16.43.0/24 is directly connected, FastEthernet0/0S 172.16.43.35/32 is directly connected, Ethernet2/310.0.0.0/8 is variably subnetted, 2 subnets, 2 masksU 10.88.0.0/24 [1/0] via 0.0.0.0, Virtual-Access1C 10.88.0.0/16 is directly connected, Loopback2Related Commands
anonymous user
To configure anonymous user access at an access point, use the anonymous user access-point configuration command. To remove the username configuration, use the no form of this command.
anonymous user username [password]
no anonymous user
Syntax Description
Defaults
No default behavior or values.
Command Modes
Access-point configuration
Command History
Usage Guidelines
Use this command to allow a mobile station (MS) to access a non-transparent mode APN without supplying the username and password in the GTP protocol configuration option (PCO) information element (IE) of the create PDP context request message. The GGSN will use the username and password configured on the APN for the user session.
This command enables anonymous access, which means that a PDP context can be created by an MS to a specific host without specifying a username and password.
Examples
The following example specifies the username george and the password abcd123 for anonymous access at access point 49:
gprs access-point-list abcaccess-point 49access-point-name www.pdn.comanonymous user george abcd123authorization
To define a method of authorization (AAA method list), in the DCCA client profile, that is used to specify the Diameter server groups, use the authorization DCCA client profile configuration command. To remove the method list configuration, use the no form of this command
authorization method-list
no authorization method-list
Syntax Description
method-list
Name of the method list defined using the aaa authorization command that describes the authorization methods to be queried for a user.
Defaults
No default behavior or values.
Command Modes
DCCA client profile configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the authorization command to define the method list to be used by the DCCA client to authorize users. The method list specifies the Diameter server groups to use for authorization and was created using the aaa authorization global configuration command.
Examples
The following configuration example defines dcca-method1 as the method of authorization for a DCCA client:
gprs dcca profile dcca-profile1authorization dcca-methodRelated Commands
auto-retrieve
To configure the GGSN to automatically initiate a G-CDR retrieval from the PSDs defined in a PSD server group when a charging gateway becomes active, use the auto-retrieve PSD group configuration command. To return to the default value, use the no form of this command.
auto-retrieve max-retrieve-rate
no auto-retrieve max-retrieve-rate
Syntax Description
group-name
Specifies the maximum number of retrieval requests that can be sent from the GGSN to the PSDs per minute. Valid value is a number between 1 and 600.
Defaults
60.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the auto-retrieve command to configure the GGSN to automatically retrieve G-CDRs from a PSD. When the auto-retrieve command is configured, the GGSN retrieves G-CDRs from the PSDs defined in the PSD server group. It initiates a retrieval from the "retrieve-only" PSD first, and then retrieves the G-CDRs from the local PSD.
If a retrieve-only PSD has been configured without the auto-retrieve command configured, the GGSN will not initiate a start retrieve when a retrieving event occurs.
Note
Examples
The following example configures the GGSN to automatically retrieve G-CDRs from the PSDs, using the default 60 as the number of retrieval requests that can be sent from the GGSN to the PSD per minute:
auto-retrieveRelated Commands
bandwidth
To define the total bandwidth for a bandwidth pool, use the bandwidth bandwidth pool configuration command. To return to the default value, use the no form of this command.
bandwidth value
no bandwidth value
Syntax Description
value
Specifies the total bandwidth, in kilobits per second, for a bandwidth pool. Valid value is a number from 1 to 4294967295.
Defaults
No default behavior or values.
Command Modes
Bandwidth pool configuration
Command History
Usage Guidelines
Use the bandwidth bandwidth pool configuration command to define the total bandwidth for a bandwidth pool.
Note
The total bandwidth defined for a bandwidth pool can be subdivided among traffic classes using the traffic-class bandwidth pool configuration command.
Examples
The following example allocates 10000 kilobits per second for the bandwidth pool "poolA":
gprs qos bandwidth-pool poolAbandwidth 10000Related Commands
bandwidth-pool
To enable the Call Admission Control (CAC) bandwidth management function and apply a bandwidth pool to an APN, use the bandwidth-pool access-point configuration command. To return to the default value, use the no form of this command.
bandwidth-pool {input | output} pool-name
no bandwidth-pool {input | output} pool-name
Syntax Description
Defaults
Disabled
Command Modes
Access-point configuration
Command History
Usage Guidelines
Use the bandwidth-pool access-point configuration command to enable the CAC bandwidth management function and apply a bandwidth pool to an APN.
Note
Examples
The following example enables the CAC bandwidth management function and applies bandwidth pool "pool A" to the Gn interface of an APN:
bandwidth-pool input poolARelated Commands
block-foreign-ms
To restrict GPRS access based on the mobile user's home PLMN (where the MCC and MNC are used to determine the point of origin), use the block-foreign-ms access-point configuration command. To disable blocking of foreign subscribers, use the no form of this command.
block-foreign-ms
no block-foreign-ms
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Access-point configuration
Command History
Usage Guidelines
The block-foreign-ms command enables the GGSN to block foreign MSs from accessing the GGSN via a particular access point.
When you use this command, the GGSN determines if an MS is inside or outside of the PLMN based on the mobile country code (MCC) and mobile network code (MNC). The MCC and MNC are specified using the gprs mcc mnc command.
Note
Additionally, before a GGSN is enabled to block foreign MSs, a valid PLMN should be configured using the gprs plmn ip address command. The block foreign MS feature will not take affect until a valid PLMN is configured and the GGSN will allow create PDP context requests from foreign MSs until then.Examples
The following example blocks access to foreign MSs at access point 49:
gprs access-point-list abcaccess-point 49access-point-name www.pdn.comblock-foreign-msRelated Commands
gprs mcc mnc
Configures the mobile country code and mobile network code that the GGSN uses to determine whether a create PDP context request is from a foreign MS.
cac-policy
To enable the maximum QoS policy function of the Call Admission Control (CAC) feature and apply a policy to an APN, use the cac-policy access-point configuration command. To return to the default value, use the no form of this command.
cac-policy policy-name
cac-policy policy-name
Syntax Description
Defaults
There is no policy attached to an APN.
Command Modes
Access-point configuration
Command History
Usage Guidelines
Use the cac-policy command to enable maximum QoS policy function of the CAC feature and apply a policy to an APN.
Note
Examples
The following example attaches maximum QoS policy A to an access point:
cac-policy ARelated Commands
category
To identify the subscriber billing method category to which a charging profile applies, enter the category charging profile configuration command. To return to the default value, issue the no form of this command.
category {hot | flat | prepaid | normal}
no category {hot | flat | prepaid | normal}
Syntax Description
Defaults
Flat
Command Modes
Charging profile configuration
Command History
Usage Guidelines
Use the category charging profile configuration command to identify to which subscriber billing method category a charging profile applies.
Examples
The following example indicates hot is the subscriber billing method category to which the profile applies:
category hotRelated Commands
.
ccfh
To configure a default Credit Control Failure Handling (CCFH) action to apply to CC sessions (PDP context) when a failure occurs and the CCA received from the DCCA server does not contain a value for the CCFH AVP, use the ccfh DCCA client profile configuration command. To return to the default value, use the no form of this command
ccfh [continue | terminate | retry_terminate]
no ccfh [continue | terminate | retry_terminate]
Syntax Description
Defaults
Terminate.
Command Modes
DCCA client profile configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the ccfa command to configure the CCFH AVP locally. The CCFH determines the behavior of the DCCA client in fault situations. The CCFH AVP can also be received from the Diameter home AAA server, DCCA server. A CCFH value received from the DCCA server in a CCA overrides the value configured locally.
The CCFH AVP is determines the action the DCCA client takes on a session, when the following fault conditions occur:
•
•
•
•
•
Examples
The following configuration example configures the DCCA client to allow a CC session and user traffic for the relevant category (or categories) to continue:
gprs dcca profile dcca-profile1authorization dcca-methodtx-timeout 12ccfh continueRelated Commands
cdr suppression
To specify that CDRs be suppressed as a charging characteristic in a charging profile, use the cdr suppression charging profile configuration mode command. To return to the default value, use the no form of the command.
cdr suppression
no cdr suppression
Syntax Description
This command has no arguments or keywords.
Defaults
CDRs are not suppressed.
Command Modes
Charging profile configuration
Command History
Usage Guidelines
Use the cdr suppression charging profile configuration command to specify that CDRs be suppressed as a charging characteristic in a charging profile.
Examples
The following example specifies that CDRs be suppressed:
cdr suppressionRelated Commands
.
cdr suppression prepaid
To specify that G-CDRs be suppressed for prepaid users, use the cdr suppression charging profile configuration mode command. To return to the default value, use the no form of the command.
cdr suppression prepaid
no cdr suppression prepaid
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled (G-CDRs are generated for users).
Command Modes
Charging profile configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the cdr suppression prepaid charging profile configuration command to specify that CDRs be suppressed users with an active connection to a DCCA server.
Charging for prepaid users is handled by the DCCA client, therefore G-CDRs do not need to be generated for prepaid users.
Note
Examples
The following example specifies that CDRs be suppressed for online users:
cdr suppression prepaidRelated Commands
.
charging profile
To specify a default charging profile for a user type for an access point, use the charging profile access-point configuration command. To remove the profile, use the no form of this command.
charging profile {home | roaming | visiting | any} [trusted] profile-number [override]
no charging profile {home | roaming | visiting | any} profile-number [trusted] profile-number [override]
Syntax Description
Defaults
No profile is associated with an APN.
Command Modes
Access-point configuration
Command History
Usage Guidelines
Use the charging profile access-point configuration command to apply a default charging profile to an APN for a specific type of use.
Note
The order in which a charging profile is selected for a PDP context, is as follows:
•
If a default charging profile has been configured at both the APN and global level to override the SGSN specification, the APN default charging profile is used first.
•
Exampless
The following example specifies charging profile number 10 to be the APN default for home users:
charging profile 10 homeRelated Commands
.
clear data-store statistics
To clear Persistent Storage Device (PSD)-related statistics, use the clear data-store statistics privilege exec command.
clear data-store statistics
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear data-store statistics command to clear PSD-related statistics. These statistics are displayed using the show data-store statistics command.
Examples
The following example clears PSD-related statistics on the GGSN:
clear data-store statisticsRelated Commands
clear ggsn quota-server statistics
To clear statistics (message and error counts) related to quota server processing, use the clear ggsn quota-server statistics privilege EXEC command.
clear ggsn quota-server statistics
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privilege EXEC
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the clear ggsn quota-server statistics command to clear statistics related to quota server process operations (displayed using the show ggsn quota server statistics command).
Examples
The following configuration example clears all statistics related to quota server operations:
clear ggsn quota-server statistics
Related Commands
show ggsn quota-server
Displays quota server parameters or statistics about the message and error counts.
.
clear gprs access-point statistics
To clear statistics counters for a specific access point or for all access points on the GGSN, use the clear gprs access-point statistics privileged EXEC command.
clear gprs access-point statistics {access-point-index | all}
Syntax Description
access-point-index
Index number of an access point. Information about that access point is cleared.
all
Information about all access points on the GGSN is cleared.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command clears the statistics that are displayed by the show gprs access-point statistics command and show policy-map apn command.
Examples
The following example clears the statistics at access point 2:
clear gprs access-point statistics 2The following example clears the statistics for all access points:
clear gprs access-point statistics allRelated Commands
show gprs access-point statistics
Displays data volume and PDP context activation and deactivation statistics for access points on the GGSN.
clear gprs charging cdr
To clear GPRS call detail records (CDRs), use the clear gprs charging cdr privileged EXEC configuration command.
clear gprs charging cdr {access-point access-point-index | all | partial-record | tid tunnel-id}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear gprs charging cdr command to clear the CDRs for one or more PDP contexts.
To clear CDRs by tunnel ID (TID), use the clear gprs charging cdr command with the tid keyword and specify the corresponding TID for which you want to clear the CDRs. To determine the tunnel ID (TID) of an active PDP context, you can use the show gprs gtp pdp-context all command to obtain a list of the currently active PDP contexts (mobile sessions).
To clear CDRs by access point, use the clear gprs charging cdr command with the access-point keyword and specify the corresponding access-point index for which you want to clear CDRs. To obtain a list of access points, you can use the show gprs access-point command.
When you clear CDRs for a TID, an access point, or for all access points, charging data records for the specified TID or access point(s) are sent immediately to the charging gateway. When you run these versions of this command, the following things occur:
•
•
•
To close all CDRs and open partial CDRs for existing PDP contexts on the GGSN, use the clear gprs charging cdr partial-record command.
The clear gprs charging cdr command is normally used before disabling the charging function.
Examples
The following example shows how to clear CDRs by tunnel ID:
Router# show gprs gtp pdp-context allTID MS Addr Source SGSN Addr APN1234567890123456 10.11.1.1 Radius 10.4.4.11 www.pdn1.com2345678901234567 Pending DHCP 10.4.4.11 www.pdn2.com3456789012345678 10.21.1.1 IPCP 10.1.4.11 www.pdn3.com4567890123456789 10.31.1.1 IPCP 10.1.4.11 www.pdn4.com5678901234567890 10.41.1.1 Static 10.4.4.11 www.pdn5.comRouter# clear gprs gtp charging cdr tid 1234567890123456The following example shows how to clear CDRs for access point 1:
Router# clear gprs charging cdr access-point 1Related Commands
clear gprs charging cdr all no-transfer
To clear all stored call detail records (CDRs) when a GGSN is in charging and global maintenance mode, including those in the pending queue, use the clear gprs charging cdr all no-transfer privileged EXEC configuration command.
clear gprs charging cdr all no-transfer
Syntax Descriptionclear gprs charging cdr no-transfer
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear gprs cdr all no-transfer command to clear stored and pending CDRs when the GGSN is in charging and global maintenance modes.
When you clear stored CDRs, the GGSN does not send the charging data accumulated for PDP contexts to the charging gateway when the global and charging service-mode states are returned to operational. Additionally, once the service-mode states are returned to operational, the GGSN no longer generates CDRs for the existing PDP contexts. Therefore, to return to normal CDR generation, clear existing PDP contexts using the clear gprs gtp pdp-context global configuration command.
Note
Note
Examples
The following example shows how to clear CDRs:
Router# clear gprs cdr all no-transferRelated Commands
clear gprs gtp pdp-context
To clear one or more PDP contexts (mobile sessions), use the clear gprs gtp pdp-context privileged EXEC configuration command.
clear gprs gtp pdp-context {tid tunnel-id | imsi imsi_value | path ip-address [remote_port_num] | access-point access-point-index | all}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear gprs gtp pdp-context command to clear one or more PDP contexts (mobile sessions). Use this command when operator intervention is required for administrative reasons—for example, when there are problematic user sessions or the system must be taken down for maintenance.
After the clear gprs gtp pdp-context command is issued, those users who are accessing the PDN through the specified TID, IMSI, path, or access point are disconnected.
Caution
To determine the tunnel ID of an active PDP context, you can use the show gprs gtp pdp-context command to obtain a list of the currently active PDP contexts (mobile sessions). Then, to clear a PDP context by tunnel ID, use the clear gprs gtp pdp-context command with the tid keyword and the corresponding tunnel ID that you want to clear.
To clear PDP contexts by access point, use the clear gprs gtp pdp-context command with the access-point keyword and the corresponding access-point index. To display a list of access points that are configured on the GGSN, use the show gprs access-point command.
If you know the IMSI of the PDP context, you can use the clear gprs gtp pdp-context with the imsi keyword and the corresponding IMSI of the connected user to clear the PDP context. If you want to determine the IMSI of a PDP context, you can use the show gprs gtp pdp-context all command to display a list of the currently active PDP contexts. Then, after finding the TID value that corresponds to the session that you want to clear, you can use the show gprs gtp pdp-context tid command to display the IMSI.
Examples
The following example shows how to clear PDP contexts by tunnel ID:
GGSN# show gprs gtp pdp-context allTID MS Addr Source SGSN Addr APN1234567890123456 10.11.1.1 Radius 10.4.4.11 www.pdn1.com2345678901234567 Pending DHCP 10.4.4.11 www.pdn2.com3456789012345678 10.21.1.1 IPCP 10.1.4.11 www.pdn3.com4567890123456789 10.31.1.1 IPCP 10.1.4.11 www.pdn4.com5678901234567890 10.41.1.1 Static 10.4.4.11 www.pdn5.comGGSN# clear gprs gtp pdp-context tid 1234567890123456The following example shows how to clear PDP contexts at access point 1:
GGSN# clear gprs gtp pdp-context access-point 1clear gprs gtp statistics
To clear the current GPRS GTP statistics, use the clear gprs gtp statistics privileged EXEC configuration command.
clear gprs gtp statistics
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear gprs gtp statistics command to clear the current GPRS GTP statistics. This command clears the counters that are displayed by the show gprs gtp statistics command.
Note
Examples
The following example clears the GPRS GTP statistics:
GGSN# clear gprs gtp statisticsclear gprs redundancy statistics
To clear statistics related to GTP session redundancy (GTP-SR), use the clear gprs redundancy statistics privileged EXEC command.
clear gprs redundancy statistics
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear gprs redundancy statistics command to clear the GTP-SR statistics that are displayed using the show gprs redundancy command.
Examples
The following example clears all GPRS redundancy-related statistics:
clear gprs redundancy statisticsRelated CommandsRouter# debug gprs gtp events
clear gprs service-aware statistics
To clear statistics (message and error counts) related to the service-aware features of the GGSN, use the clear ggsn quota-server statistics privilege EXEC command.
clear gprs service-aware statistics
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privilege EXEC
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the clear gprs service-aware statistics command to clear statistics related to the service-aware features of the GGSN (displayed using the show gprs service-aware statistics command).
Examples
The following configuration example clears all statistics related to the service-aware features of the GGSN:
clear gprs service-aware statistics
Related Commands
show gprs service-aware statistics
Displays statistics related to the service-aware features of the GGSN, such as packets sent to, and received from, the Diameter server or CSG.
.
clear gprs slb statistics
To clear Cisco IOS SLB statistics, use the clear gprs slb statistics privileged EXEC configuration command.
clear gprs slb statistics
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the clear gprs slb statistics command to clear Cisco IOS SLB statistics. This command clears the counters that are displayed by the show gprs slb statistics command.
Examples
The following example clears the Cisco IOS SLB statistics:
GGSN# clear gprs slb statisticsRelated Commands
content dcca profile
To specify a DCCA client to use to communicate with a DCCA server in a GGSN charging profile, use the dcca profile charging profile configuration command. To remove the profile configuration, use the no form of this command.
content dcca profile dcca-profile-name
no content dcca profile
Syntax Description
dcca-profile-name
Name of the DCCA client profile configured on the GGSN that defines the DCCA client to use to communicate with the DCCA server.
Defaults
No default behavior or values.
Command Modes
Charging profile configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
The presences of the content dcca profile statement in a charging profile indicates online billing is required. Therefore, regardless of whether a subscriber is prepaid or postpaid, the GGSN will contact the DCCA server if the content dcca profile command has been configured.
If the user is to be treated as a postpaid user, the server returns X and the user is treated as a postpaid user. If a charging profile does not contain a content dcca profile configuration, users using the charging profile will be treated as postpaid (offline billing).
Examples
The following configuration example defines a DCCA client profile named dcca-profile1 in Charging Profile 1:
gprs charging profile 1content dcca profile dcca-profile1Related Commands
.
content postpaid time
To specify as a trigger condition for postpaid users in a charging profile, the time duration limit that when exceeded causes the GGSN to collect upstream and downstream traffic byte counts and close and update the G-CDR for a particular PDP context, use the content postpaid time charging profile configuration command. To return to the default value, use the no form of this command.
content postpaid time number
no content postpaid time
Syntax Description
Defaults
1048576 seconds.
Command Modes
Charging profile configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the content postpaid time charging profile configuration command to specify the time limit, for postpaid users, that when exceeded, causes the GGSN to collect upstream and downstream traffic byte counts and close and update the G-CDR for a PDP context.
Examples
The following configuration example specifies a postpaid time duration limit 400 minutes in Charging Profile 1:
gprs charging profile 1content dcca profile dcca-profile1content postpaid time 400Related Commands
.
content postpaid validity
To specify as a trigger condition in a charging profile, the amount of time quota granted to a postpaid user is valid, use the content postpaid validity charging profile configuration command. To return to the default value, use the no form of this command.
content postpaid validity seconds
no content postpaid validity
Syntax Description
seconds
A value between 900 and 4294967295 seconds that specifies the amount of time granted quota is valid.
Defaults
Disabled.
Command Modes
Charging profile configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the content postpaid validity charging profile configuration command to configure the amount of time quota granted to postpaid users is valid.
Examples
The following example specifies a value of 21600:
gprs charging profile 1content dcca profile dcca-profile1content postpaid time 400content postpaid volume 2097152content postpaid validity 21600Related Commands
.
content postpaid volume
To specify as a trigger condition for postpaid users in a charging profile, the maximum number of bytes that the GGSN maintains across all containers for a particular PDP context before closing and updating the G-CDR, use the content postpaid volume charging profile configuration command. To return to the default value, use the no form of this command.
content postpaid volume threshold_value
no content postpaid volume
Syntax Description
threshold_value
A value between 1 and 4294967295 that specifies the container threshold value, in bytes. The default is 1,048,576 bytes (1 MB).
Defaults
1,048,576 bytes (1 MB).
Command Modes
Charging profile configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the content postpaid volume charging profile configuration command to configure as a trigger condition for postpaid users, the maximum number of bytes that the GGSN maintains across all containers for a particular PDP context before closing and updating the G-CDR.
Examples
The following example specifies a threshold value of 2097152:
gprs charging profile 1content dcca profile dcca-profile1content postpaid time 400content postpaid volume 2097152Related Commands
.
content rulebase
To associate a default rule-base ID to apply to PDP contexts using a particular charging profile, use the rulebase charging profile configuration mode command. To return to the default value, use the no form of the command.
content rulebase id
no content rulebase
Syntax Description
Defaults
Disabled.
Command Modes
Charging profile configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the content rulebase charging profile configuration command to define a default rulebase ID to a charging profile.
Rulebases contain the rules for defining categories of traffic; categories on which decisions such as whether to allow or disallow traffic, and how to measure the traffic, are based. The GGSN maps Diameter Rulebase IDs to CSG billing plans.
Note
Examples
The following example specifies a default rulebase with the ID of "PREPAID" in Charging Profile 1:
gprs charging profile 1content dcca profile dcca-profile1content postpaid time 400content rulebase PREPAIDRelated Commands
.
csg-group
To associate the quota server to a CSG server group that is to be used for quota server-to-CSG communication, use the csg-group quota server configuration command. To remove the association to a CSG group, use the no form of this command
csg-group csg-group-name
no csg-group csg-group-name
Syntax Description
Defaults
No default behavior or values.
Command Modes
Quota server configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the csg-group command to associate the quota server with the CSG server group to use for quota server-to-CSG communication.
This functionality requires that a CSG server group has been defined on the GGSN using the ggsn csg-group global configuration command and associated CSG group configuration commands.
Caution
Examples
The following configuration example specifies for the quota server to use CSG group "csg1" for quota server-to-CSG communication:
ggsn quota-server qs1interface loopback1echo-interval 90n3-requests 3t3-response 524csg group csg1Related Commands
.
data-store
To configure a Persistent Storage Device (PSD) server group to be used for GGSN-to-PSD communication, and enter PSD group configuration mode, use the data-store global configuration command. To disable the PSD server group, issue the no form of this command.
data-store psd-group-name
no data-store psd-group-name
Syntax Description
psd-group-name
Specifies the name of a PSD server group to be used for GGSN-to-PSD server communication.
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the data-store command to define a PSD server group for GGSN-to-PSD communication and enter data-store configuration mode.
When in data-store configuration mode, you can define PSDs and configure auto-retrieve options.
Note
Examples
The following example configures a PSD server group identified as "groupA":
data-store groupARelated Commands
description
To specify the name or a brief description of a charging profile, use the description charging profile configuration mode command. To delete a charging profile description, use the no form of the command.
description string
no description string
Syntax Description
Defaults
There is no charging profile description.
Command Modes
Charging profile configuration
Command History
Usage Guidelines
Use the description charging profile configuration mode command to provide a description of a charging profile.
Examples
The following example describes a profile as APN-level default for home users:
description APN-level_default_for_home_usersRelated Commands
.
destination host
To configure the Fully Qualified Domain Name (FQDN) of the Diameter peer, use the destination host diameter peer configuration command. To remove the FQDN, use the no form of this command
destination host string
no destination host
Syntax Description
Defaults
No default behavior or values.
Command Modes
Diameter peer configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the destination host command to define the FQDN of the Diameter peer. This FQDN will be sent in various messages so that intermediate proxies can properly route packets.
Examples
The following configuration example specifies "dcca1.cisco.com as the FQDN of the Diameter peer:
diameter peer dcca1address ipv4 10.10.10.1transport tcp port 4000security ipsecsource interface fastEthernet0timer connection 120destination host dcca1.cisco.comRelated Commands
.
destination realm
To configure the destination realm (part of the domain "@realm") in which the Diameter peer is located, use the destination realm diameter peer configuration command. To remove the destination realm configuration, use the no form of this command
destination realm name
no destination realm
Syntax Description
Defaults
No default behavior or values.
Command Modes
Diameter peer configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the diameter realm command to specify the destination realm to be included in messages exchanged with a Diameter peer.
The realm might be added by an AAA client when sending an AAA request. However, if the client does not add the attribute, then the value configured while in Diameter peer configuration mode is used when sending messages to the destination Diameter peer. If a value is not configured for a Diameter peer, the global value specified using the diameter destination realm global configuration command is used.
Examples
The following configuration example configures "cisco.com" as the destination realm:
Diameter peer dcca1address ipv4 10.10.10.1transport tcp port 4000security ipsecsource interface fastEthernet0timer connection 120destination host dcca1.cisco.comdestination realm cisco.comRelated Commands
.
destination-realm
To configure the destination realm to be sent in CCR initial requests to a DCCA server, use the destination-realm DCCA profile configuration command. To remove the destination realm configuration, use the no form of this command
destination-realm name
no destination-realm
Syntax Description
Defaults
No default behavior or values.
Command Modes
DCCA client configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the diameter-realm command to specify the destination realm to be sent in CCR initial requests to a DCCA server.
Examples
The following configuration example configures "cisco.com" as the destination realm:
Diameter peer dcca1address ipv4 10.10.10.1transport tcp port 4000security ipsecsource interface fastEthernet0timer connection 120destination host dcca1.cisco.comdestination realm cisco.comRelated Commands
dhcp-gateway-address
To specify the subnet in which the DHCP server should return addresses for DHCP requests for MS users entering a particular PDN access point, use the dhcp-gateway-address access-point configuration command. To remove a DHCP gateway address and return to the default, use the no form of this command.
dhcp-gateway-address ip-address
no dhcp-gateway-address ip-address
Syntax Description
ip-address
The IP address of the DHCP gateway to be used in DHCP requests for users who connect through the specified access point.
Defaults
When you do not configure a dhcp-gateway-address, the GGSN uses the virtual template interface address as the DHCP gateway address.
Command Modes
Access-point configuration
Command History
Usage Guidelines
The dhcp-gateway-address specifies the value of the giaddr field that is passed in DHCP messages between the GGSN and the DHCP server. If you do not specify a DHCP gateway address, the address assigned to the virtual template is used.
Though a default value for the virtual template address will occur, you should configure another value for the dhcp-gateway-address command whenever you are implementing DHCP services at an access point.
If the access point is configured for VRF, then the dynamic (or static addresses) returned for MSs of PDP contexts at the access point will also be part of that VRF address space. If the DHCP server is located within the VRF address space, then the corresponding loopback interface for the dhcp-gateway-address must also be configured within the VRF address space.
Examples
The following example specifies an IP address of 10.88.0.1 for the giaddr field (the dhcp-gateway-address) of DHCP server requests. Note that the IP address of a loopback interface, in this case Loopback2, matches the IP address specified in the dhcp-gateway-address command. This is required for proper configuration of DHCP on the GGSN.
interface Loopback2ip address 10.88.0.1 255.255.255.255!gprs access-point-list gprsaccess-point 8access-point-name pdn.aaaa.comip-address-pool dhcp-proxy-clientaggregate autodhcp-server 172.16.43.35dhcp-gateway-address 10.88.0.1exitRelated Commands
dhcp-server
To specify a primary (and backup) DHCP server to allocate IP addresses to MS users entering a particular PDN access point, use the dhcp-server access-point configuration command. To remove the DHCP server from the access-point configuration, use the no form of this command.
dhcp-server {ip-address} [ip-address] [vrf]
no dhcp-server {ip-address} [ip-address] [vrf]
Syntax Description
Defaults
Global routing table
Command Modes
Access-point configuration
Command History
Usage Guidelines
To configure DHCP on the GGSN, you must configure either the gprs default ip-address-pool global configuration command, or the ip-address-pool access-point configuration command with the dhcp-proxy-client keyword option.
After you configure the access point for DHCP proxy client services, use the dhcp-server command to specify a DHCP server.
Use the ip-address argument to specify the IP address of the DHCP server. The second, optional ip-address argument can be used to specify the IP address of a backup DHCP server to be used in the event that the primary DHCP server is unavailable. If you do not specify a backup DHCP server, then no backup DHCP server is available.
The DHCP server can be specified in two ways:
•
•
If you specify a DHCP server at the access-point level using the dhcp-server command, then the server address specified at the access point overrides the address specified at the global level. If you do not specify a DHCP server address at the access-point level, then the address specified at the global level is used.
Therefore, you can have a global address setting and also one or more local access-point level settings if you need to use different DHCP servers for different access points.
Use the vrf keyword when the DHCP server itself is located within the address space of a VRF interface on the GGSN. If the DHCP server is located within the VRF address space, then the corresponding loopback interface for the dhcp-gateway-address must also be configured within the VRF address space.
Examples
Example 1
The following example specifies both primary and backup DHCP servers to allocate IP addresses to mobile station users through a non-VPN access point. Because the vrf keyword is not configured, the default global routing table is used. The primary DHCP server is located at IP address 10.60.0.1, and the secondary DHCP server is located at IP address 10.60.0.2:
access-point 2access-point-name xyz.comdhcp-server 10.60.0.1 10.60.0.2dhcp-gateway-address 10.60.0.1exitExample 2
The following example from an implementation on the Cisco 7200 series router platform shows a VRF configuration for vpn3 (without tunneling) using the ip vrf global configuration command. Because the ip vrf command establishes both VRF and CEF routing tables, notice that ip cef also is configured at the global configuration level to enable CEF switching at all of the interfaces.
The following other configuration elements must also associate the same VRF named vpn3:
•
•
The DHCP server at access-point 2 also is configured to support VRF. Notice that access-point 1 uses the same DHCP server, but is not supporting the VRF address space. The IP addresses for access-point 1 will apply to the global routing table:
aaa new-model!aaa group server radius fooserver 10.2.3.4server 10.6.7.8!aaa authentication ppp foo group fooaaa authorization network default group radiusaaa accounting exec default start-stop group foo!ip cef!ip vrf vpn3rd 300:3!interface Loopback1ip address 10.30.30.30 255.255.255.255!interface Loopback2ip vrf forwarding vpn3ip address 10.27.27.27 255.255.255.255!interface FastEthernet0/0ip vrf forwarding vpn3ip address 10.50.0.1 255.255.0.0duplex half!interface FastEthernet1/0ip address 10.70.0.1 255.255.0.0duplex half!interface loopback 1ip address 10.8.0.1 255.255.255.0!interface Virtual-Template1ip unnumber loopback 1encapsulation gtpgprs access-point-list gprs!ip route 10.10.0.1 255.255.255.255 Virtual-Template1ip route vrf vpn3 10.100.0.5 255.255.255.0 fa0/0 10.50.0.2ip route 10.200.0.5 255.255.255.0 fa1/0 10.70.0.2!no ip http server!gprs access-point-list gprsaccess-point 1access-point-name gprs.pdn.comip-address-pool dhcp-proxy-clientdhcp-server 10.200.0.5dhcp-gateway-address 10.30.30.30network-request-activationexit!access-point 2access-point-name gprs.pdn2.comaccess-mode non-transparentip-address-pool dhcp-proxy-clientdhcp-server 10.100.0.5 10.100.0.6 vrfdhcp-gateway-address 10.27.27.27aaa-group authentication foovrf vpn3exit!gprs default ip-address-pool dhcp-proxy-clientgprs gtp ip udp ignore checksum!radius-server host 10.2.3.4 auth-port 1645 acct-port 1646 non-standardradius-server host 10.6.7.8 auth-port 1645 acct-port 1646 non-standardradius-server key ggsntelRelated Commands
diameter origin host
To define the host name of the host of a Diameter node, use the diameter origin host global configuration command. To remove the configuration, use the no form of this command
diameter origin host string
no diameter origin host
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the diameter origin host command to define the host name of a Diameter node. This information will be sent in requests to Diameter peers.
The global level configuration takes affect if an origin host is not defined at the server level using the destination host Diameter peer configuration command.
Examples
The following configuration example defines ggsn.cisco.com as the originating host:
diameter origin host ggsn.cisco.comRelated Commands
diameter origin realm
To configure the origin realm to be sent in requests to a Diameter peer for a Diameter node, use the diameter origin realm global configuration command. To remove the origin realm configuration, use the no form of this command
diameter origin realm name
no diameter origin realm
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the diameter origin realm command to specify the domain to which a Diameter client belongs. Origin realm information is included in each request sent to a Diameter client.
This global level configuration takes affect if an origin realm is not defined at the server level using the destination realm Diameter peer configuration command.
Examples
The following configuration example defines cisco.com as the origin to which a Diameter client belongs:
diameter origin realm cisco.comRelated Commands
diameter peer
To define a Diameter peer (server) and enter Diameter peer configuration mode, use the diameter peer global configuration command. To remove a Diameter peer configuration, use the no form of this command
diameter peer name
no diameter peer name
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the diameter peer command to define a Diameter peer and enter Diameter peer configuration mode. From Diameter peer configuration mode, you define the parameters to use to contact a Diameter server. These parameters include:
•
•
•
•
•
•
•
Examples
The following configuration example defines Diameter peer "dcca1":
diameter peer dcca1Related Commands
.
diameter redundancy
To enable a Diameter node to be a Cisco IOS Redundancy Facility (RF) client and to track session states, use the diameter redundancy global configuration command. To disable redundancy, use the no form of this command.
diameter redundancy
no diameter redundancy
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled.
Command Modes
Global configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the diameter redundancy command to enable the Diameter base protocol to be a Cisco IOS Redundancy Facility (RF) client and monitor and report Active/Standby transitions.
When a Diameter device is in Standby mode, it will not initiation a TCP connection to a peer. Upon a Standby to Active transition state, the Diameter device initiates a TCP connection to the Diameter peer.
Examples
The following example enables Diameter redundancy on a GGSN:
diameter redundancyRelated Commands
diameter timer
To configure Diameter protocol timers, use the diameter timer global peer configuration command. To remove the timer configurations, use the no form of this command
diameter timer {connection | transaction | watchdog} seconds
no diameter timer {connection | transaction | watchdog}
Syntax Description
Defaults
30 seconds.
Command Modes
Global configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the diameter timer command to configure global Diameter timers for a Diameter node.
The global level timers takes affect only if timers are not configured at the Diameter server level using the timer Diameter peer configuration command.
When configuring timers, note that the value for the transaction timers, should be larger than the value for the TX timer, and, on the SGSN, the values configured for the number GTP N3 requests and T3 retransmissions must be larger than the sum of all possible server timers (RADIUS, DCCA, and CSG). Specifically, the SGSN N3*T3 must be greater than 2 x RADIUS timeout + N x DCCA timeout + CSG timeout where:
•
•
Examples
The following configuration example sets the global connection timer to 120 seconds:
global diameter timer connection 120Related Commands
diameter vendor support
To configure the Diameter node to advertise various vendor AVPs that it supports in capability exchange messages to a Diameter peer, use the diameter vendor support global configuration command. To remove the advertising of a vendor AVP, use the no form of this command
diameter vendor support {Cisco | 3gpp | Vodafone}
no diameter vendor support {Cisco | 3gpp | Vodafone}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Multiple instances of this command can be configured if the vendor IDs differ.
Examples
The following configuration example configures the 3GPP AVPs to be advertised as a supported vendor AVP in capability exchange messages:
diameter vendor support 3gppRelated Commands
dns primary
To specify a primary (and backup) DNS to be sent in create PDP responses at the access point, use the dns primary access-point configuration command. To remove the DNS from the access-point configuration, use the no form of this command
dns primary ip-address [secondary ip-address]
Syntax Description
ip-address
IP address of the primary DNS.
secondary ip-address
(Optional) Specifies the IP address of the backup DNS.
Defaults
No default behavior or values.
Command Modes
Access-point configuration
Command History
Usage Guidelines
Use the dns primary command to specify the primary (and backup) DNS at the access point level.
This feature is benefits address allocation schemes where there is no mechanism to obtain these address. Also, for a RADIUS-based allocation scheme, it prevents the operator from having to configure a NBNS and DNS under each user profile.
The DNS address can come from three possible sources: DHCP server, RADIUS server, or local APN configuration. The criterion for selecting the DNS address depends on the IP address allocation scheme configured under the APN. Depending on the configuration, the criterion for selecting the DNS address is as follows:
1.
2.
3.
4.
Note
Examples
The following example specifies a primary and secondary DNS at the access point level:
access-point 2access-point-name xyz.comdns primary 10.60.0.1 secondary 10.60.0.2exitRelated Commands
echo-interval
To specify the number of seconds that the quota server waits before sending an echo-request message to the CSG, use the echo-interval quota server configuration command. To return to the default value, use the no form of this command
echo-interval interval
no echo-interval interval
Syntax Description
Defaults
60 seconds.
Command Modes
Quota server configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the echo-interval command to specify the interval that the quota server waits before sending an echo-request message to the CSG to check for GTP path failure.
Note
Examples
The following example configures the quota server to wait 90 seconds before sending an echo-request message:
ggsn quota-server qs1interface loopback1echo-interval 90Related Commands
.
encapsulation gtp
To specify the GPRS tunneling protocol (GTP) as the encapsulation type for packets transmitted over the virtual template interface, use the encapsulation gtp interface configuration command. To remove the GTP encapsulation type and return to the default, use the no form of this command.
encapsulation gtp
no encapsulation gtp
Syntax Description
This command has no arguments or keywords.
Defaults
PPP encapsulation
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the encapsulation gtp command to specify the GTP as the encapsulation type for a virtual template. This is a mandatory setting for both the GGSN and GDM.
Examples
The following example specifies the GPRS tunneling protocol (GTP) as the encapsulation type:
interface virtual-template 1ip unnumber loopback 1no ip directed-broadcastencapsulation gtpgbr traffic-class
To define in a Call Admission Control (CAC) maximum QoS policy, the highest guaranteed bit rate (GBR) that can be allowed for real-time traffic, use the gbr traffic-class CAC maximum QoS policy configuration command. To return to the default value, use the no form of this command.
gbr traffic-class traffic-class-name bitrate {uplink | downlink} [reject]
no gbr traffic-class traffic-class-name bitrate {uplink | downlink} [reject]
Syntax Description
Defaults
If the GBR in a create or update PDP context is greater than the configured value, the requested GBR is downgraded to the configured value.
Command Modes
CAC maximum QoS policy configuration
Command History
Usage Guidelines
Use the gbr traffic-class CAC maximum QoS policy configuration command to define the highest GBR that can be accepted for real-time traffic on an APN.
When the reject optional keyword is specified, if the requested GBR exceeds the configured value, the create PDP context is rejected.
If the reject keyword is not specified and the GBR in a create or update PDP context is greater than the configured value, the requested GBR is downgraded to the configured value.
Note
Examples
The following example configures the maximum GBR for conversational class as 1000 kilobits in the uplink direction:
gbr traffic-class conversational 1000 uplinkRelated Commands
ggsn csg-group
To configure a Content Services Gateway (CSG) group on the GGSN, to use for quota server-to-CSG communication, use the ggsn csg-group global configuration command. To deconfigure the CSG group, use the no form of this command
ggsn csg-group csg-group-name
no ggsn csg-group csg-group-name
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the ggsn csg-group command to configure a CSG server group on the GGSN that will be used for quota server-to-CSG communication when service-aware billing is enabled.
Only one CSG server group can be defined per quota server. Therefore, only on GTP path is established between the quota server and CSG at a time. On this GTP path, echo and node alive messages are exchanged.
Note
Issuing the ggsn csg-group command enters CSG server group configuration mode. In CSG server group configuration mode, you can define the virtual address of the CSG server group, the port number on which the CSG listens for quota server traffic, and the real addresses of up to two CSGs (Active and Standby).
Examples
The following configuration example configures a CSG server group named "csg1" and enters CSG server group configuration mode:
ggsn csg-group csg1Related Commands
ggsn quota-server
To configure the quota server process that interfaces with the Cisco Content Services Gateway (CSG) in a service-aware GGSN implementation, use the ggsn quota-server global configuration command. To disable the quota server process on the GGSN, use the no form of this command.
ggsn quota-server server-name
no ggsn quota-server server-name
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
Use the ggsn quota-server command to configure the quota server process on a GGSN and to enter quota server configuration mode. In service-aware GGSN configuration, the quota server process on the GGSN:
•
•
•
•
To complete the quota server configuration, while in quota server configuration mode, you must also complete the following tasks:
•
•
•
•
•
Examples
The following configuration example configures the GGSN quota server "gs1" and enters quota server configuration mode:
gprs quota-server qs1Related Commands
.
gprs access-point-list
To configure an access point list that you use to define PDN access points on the GGSN, use the gprs access-point-list global configuration command. To remove an existing access-point list, use the no form of this command.
gprs access-point-list list_name
no gprs access-point-list
Syntax Description
Defaults
No access-point list is defined
Command Modes
Global configuration
Command History
Usage Guidelines
Use the gprs access-point-list command to configure an access list that you use to define PDN access points on the GGSN. Currently, only one access list can be defined per virtual template.
Examples
The following example sets up an access-point list that is used to define two GPRS access points:
! Virtual Template configurationinterface virtual-template 1ip unnumber loopback 1no ip directed-broadcastencapsulation gtpgprs access-point-list abc!! Access point list configurationgprs access-point-list abcaccess-point 1access-point-name gprs.somewhere.comexit!access-point 2access-point-name xyz.comexitRelated Commands
gprs canonical-qos best-effort bandwidth-factor
To specify the bandwidth factor to be applied to the canonical best-effort Quality of Service (QoS) class, use the gprs canonical-qos best-effort bandwidth-factor global configuration command. To return to the default value, use the no form of this command.
gprs canonical-qos best-effort bandwidth-factor bandwidth-factor
no gprs canonical-qos best-effort bandwidth-factor bandwidth-factor
Syntax Description
bandwidth-factor
Integer from 1 to 4000000 that specifies the desired bandwidth factor (in bits per second). The default is 10 bits per second.
Defaults
10 bits per second
Command Modes
Global configuration
Command History
Usage Guidelines
The canonical qos best-effort bandwidth-factor command specifies an average bandwidth that is expected to be used by best-effort QoS class mobile sessions. The default value of 10 bps is chosen arbitrarily. If you observe that users accessing the GGSN are using a higher average bandwidth, then you should increase the bandwidth value.
Note
Examples
The following example configures a bandwidth factor of 20:
gprs canonical-qos best-effort bandwidth-factor 20Related Commands
gprs canonical-qos gsn-resource-factor
To specify the total amount of resource that the GGSN uses to provide canonical QoS service levels to mobile users, use the gprs canonical-qos gsn-resource-factor global configuration command. To return to the default value, use the no form of this command.
gprs canonical-qos gsn-resource-factor resource-factor
no gprs canonical-qos gsn-resource-factor resource-factor
Syntax Description
resource-factor
Integer between 1 and 4294967295 representing an amount of resource that the GGSN calculates internally for canonical QoS processing. The default value is 3145728000.
Defaults
3,145,728,000
Command Modes
Global configuration
Command History
