GGSN Qos
GGSN Qos
This chapter describes how to configure Quality of Service (QoS) functions to differentiate traffic flow
through the GGSN.
For a complete description of the GGSN commands in this chapter, refer to the Cisco IOS Mobile
Wireless Command Reference. To locate documentation of other commands that appear in this chapter,
use the command reference master index or search online.
This chapter includes the following sections:
• Overview of QoS Support on the GGSN, page 9-1
• Configuring GPRS QoS on the GGSN, page 9-2
• Configuring UMTS QoS on the GGSN, page 9-12
• Configuring the GGSN Default QoS as Requested QoS, page 9-19
• Monitoring and Maintaining QoS on the GGSN, page 9-20
• Configuration Examples, page 9-27
GPRS QoS
GPRS QoS profiles is considered a single parameter that defines the following data transfer class
attributes according to the GSM standard:
• Precedence class
• Delay class
• Reliability class
UMTS QoS
To manage different level of QoS, UMTS has defined the four QoS traffic classes based on delay, jitter,
bandwidth, and reliability factors:
• Conversational
• Streaming
• Interactive
• Background
GGSN Release 4.0 delivers end-to-end UMTS QoS by implementing it using the Cisco IOS QoS
Differentiated Services (Diffserv).
This chapter describes the QoS support that the GGSN Release 4.0 provides for the GPRS and UMTS
QoS classes.
Table 9-1 shows how the GGSN maps the different combinations of GPRS QoS class attributes within a
PDP context request to a particular canonical QoS class, when canonical QoS is enabled on the GGSN.
For example, if the QoS profile of a PDP context request specifies the best effort delay class, and any
class of precedence and mean throughput, then the GGSN classifies that PDP context as the best effort
canonical class.
Table 9-1 GPRS QoS Class Attribute Combinations Mapped to GGSN Canonical QoS Classes
Delay Class Precedence Class Mean Throughput Class GGSN Canonical QoS Class
Best effort Any Any Best effort
1, 2, or 3 Low Any Best effort
1, 2, or 3 Any Best effort Best effort
1, 2, or 3 Normal Specified Normal
1, 2, or 3 High Specified Premium
Once you have enabled the canonical QoS method on the GGSN, you can map the canonical QoS classes
to IP Type of Service (ToS) categories. IP ToS mappings allow the GGSN to support differentiated
services according to RFC 2475, Architecture for Differentiated Services Framework. For more
information, see the “Mapping Canonical QoS Classes to IP ToS Precedence” section on page 9-4. For
more information about configuring the GGSN for differentiated services support, see the Cisco IOS
Quality of Service Solutions Configuration Guide and Command Reference publications.
For the canonical QoS method, the GGSN sets aside a configurable amount of resource to be used for
QoS processing. The GGSN allocates a portion of this total available resource for canonical QoS upon
PDP context activation, based upon the QoS class to which the PDP context has been assigned. Typically,
the GGSN uses more of its resources in support of the higher canonical QoS classes. As of GGSN
Release 3.0, the total default amount of resource set aside by the GGSN for canonical QoS support is
3,145,728,000 bits per second. You can modify this value using the gprs canonical-qos
gsn-resource-factor command. For more information, see the “Configuring Total GGSN Resources for
Canonical QoS Support” section on page 9-5.
When a request for a user session comes in as a PDP context activation request, the GGSN determines
whether the requested QoS for the session packets can be handled based on the amount of the
gprs canonical-qos gsn-resource-factor that is available on the GGSN. Based on this determination,
one of the following occurs:
• If the GGSN can provide the requested QoS, then the GGSN maintains that level of service.
• If the GGSN cannot provide the requested QoS, then the GGSN either lowers the QoS for the PDP
context, or it rejects the PDP context request.
Canonical QoS is not automatically enabled by the GGSN. To enable canonical QoS on the GGSN, use
the following command in global configuration mode:
Command Purpose
Router(config)# gprs qos map canonical-qos Enables mapping of GPRS QoS categories to a canonical
QoS method that includes best effort, normal, and premium
canonical QoS classes.
Once you have enabled the canonical QoS method on the GGSN, you can map the canonical QoS classes
to IP Type of Service (ToS) precedence. You can specify a mapping from the best effort, normal and
premium canonical QoS categories to the ToS precedence bits (between 0 and 7, although 6 and 7 are
not typically used). ToS precedence is reported in the IP header for packets transmitted over the Gn (GTP
tunnel) and Gi interfaces.
All of the keyword arguments for the command are optional. However, if you specify a value for the
normal argument, you must specify a value for the premium argument. And if you specify a value for
the best-effort argument, then you must specify a value for both the premium and the normal
arguments. The default Tos precedence values are 2 for premium, 1 for normal, and 0 for best effort.
The ToS precedence classes are defined as follows:
0 Routine
1 Priority
2 Immediate
3 Flash
4 Flash Override
5 Critical ECP
6 Internetwork Control
7 Network Control
Note The GTP signaling messages should always have the highest precedence in the GPRS network to help
ensure the expedited delivery of those control messages. You can configure the ToS for GTP signaling
messages using the gprs gtp map signalling tos command. The default value is 5.
To map canonical QoS classes to IP ToS precedence bits, use the following command in global
configuration mode:
Command Purpose
Router(config)# gprs canonical-qos map tos [premium (Optional) Specifies a QoS mapping from the canonical QoS
tos-value [normal tos-value [best-effort tos-value]]] classes to an IP ToS precedence value, where tos-value is an
integer between 0 and 7 (values of 6 and 7 are not typically
used).
This section describes some of the options that you can configure on the GGSN to further customize the
default canonical QoS configuration.
Once you enable canonical QoS, the GGSN establishes default values for the allocation of GGSN
resources to support canonical QoS processing. However, you most likely will want to modify the
defaults based upon the GPRS traffic patterns and QoS profiles in use on your network.
This section includes the following topics:
• Configuring Total GGSN Resources for Canonical QoS Support, page 9-5
• Configuring GGSN Resources for the Best Effort Class, page 9-6
• Configuring the Deviation Factor for the Premium Class, page 9-6
Command Purpose
Router(config)# gprs canonical-qos gsn-resource-factor (Optional) Specifies the total amount of resource that the
resource-factor GGSN uses to provide QoS service levels to mobile users.
The default is 3,145,728,000 bits per second.
Command Purpose
Router(config)# gprs canonical-qos best-effort (Optional) Specifies the bandwidth factor to be applied to the
bandwidth-factor bandwidth-factor canonical best-effort QoS class. The default value is 10 bps.
Command Purpose
Router(config)# gprs canonical-qos premium (Optional) Specifies a mean throughput deviation factor that
mean-throughput-deviation deviation-factor the GGSN uses to calculate the allowable data throughput
for the premium QoS class. The default is 100.
ip subnet-zero
!
!
no ip dhcp-client network-discovery
!
!
interface Loopback1
ip address 10.100.3.4 255.255.255.255
!
interface FastEthernet0/0
ip address 172.18.43.174 255.255.255.240
duplex half
!
interface Ethernet1/0
description Gi interface to gprt.cisco.com
ip address 10.8.8.6 255.255.255.0
no ip route-cache
no ip mroute-cache
duplex half
!
interface Ethernet1/1
description Gi interface to gprs.cisco.com
ip address 10.9.9.4 255.255.255.0
no ip route-cache
no ip mroute-cache
duplex half
!
interface Ethernet1/2
ip address 10.15.15.10 255.255.255.0
duplex half
!
interface loopback 1
ip address 10.40.40.3 255.255.255.0
!
interface Virtual-Template1
ip unnumber loopback 1
encapsulation gtp
gprs access-point-list gprs
!
. . .
!
gprs access-point-list gprs
access-point 1
access-mode non-transparent
access-point-name www.pdn1.com
aaa-group authentication foo
!
access-point 2
access-mode non-transparent
access-point-name www.pdn2.com
!
access-point 4
access-point-name www.pdn4.com
aaa-accounting enable
aaa-group accounting foo1
!
access-point 5
access-point-name www.pdn5.com
!
gprs maximum-pdp-context-allowed 90000
gprs qos map canonical-qos
gprs canonical-qos gsn-resource-factor 4294967295
gprs canonical-qos best-effort bandwidth-factor 10000
gprs canonical-qos premium mean-throughput-deviation 500
gprs canonical-qos map tos premium 3 normal 2 best-effort 1
gprs gtp path-echo-interval 30
gprs default aaa-group authentication foo2
gprs default aaa-group accounting foo3
gprs default charging-gateway 10.15.15.1
!
. . .
!
end
Table 9-2 GPRS QoS Class Attribute Combinations Mapped to GGSN Delay QoS Classes
Delay Class Precedence Class Mean Throughput Class GGSN Delay QoS Class
Undefined Any Any Best effort
Best effort Any Any Best effort
Class 1 Any Any Class 1
Class 2 Any Any Class 2
Class 3 Any Any Class 3
Delay QoS is not automatically enabled by the GGSN. To enable delay QoS on the GGSN, use the
following command in global configuration mode:
Command Purpose
Router(config)# gprs qos map delay Enables mapping of GPRS QoS categories to a delay QoS
method that includes the class 1, class 2, class 3, and best
effort classes.
Once you have enabled the delay QoS method on the GGSN, you can map the delay QoS classes to IP
Type of Service (ToS) precedence. You can specify a mapping from the class1, class2, class3, or class
best effort delay QoS categories to the ToS precedence bits (between 0 and 7, although 6 and 7 are not
typically used). ToS precedence is reported in the IP header for packets transmitted over the Gn (GTP
tunnel) and Gi interfaces.
The class2, class3 and class-best-effort keyword arguments are optional. However, if you specify a
value for the class3 argument, you must specify a value for the class2 argument. And, if you specify a
value for the class-best-effort argument, then you must specify a value for both the class2 and the class3
arguments.
The ToS precedence classes are defined as follows:
0 Routine
1 Priority
2 Immediate
3 Flash
4 Flash Override
5 Critical ECP
6 Internetwork Control
7 Network Control
Note The GTP signaling messages should always have the highest precedence in the GPRS network to help
ensure the expedited delivery of those control messages. You can configure the ToS for GTP signaling
messages using the gprs gtp map signalling tos command. The default value is 5.
To map delay QoS classes to IP ToS precedence bits, use the following command in global configuration
mode:
Command Purpose
Router(config)# gprs delay-qos map tos class1 (Optional) Specifies a QoS mapping from the delay QoS
tos-value [class2 tos-value [class3 tos-value classes to an IP ToS precedence value, where tos-value is an
[class-best-effort tos-value]]]
integer between 0 and 5 (values of 6 and 7 are not typically
used).
ip subnet-zero
!
!
no ip dhcp-client network-discovery
!
!
interface Loopback1
ip address 10.100.3.4 255.255.255.255
!
interface FastEthernet0/0
ip address 172.18.43.174 255.255.255.240
duplex half
!
interface Ethernet1/0
description Gi interface to gprt.cisco.com
ip address 10.8.8.6 255.255.255.0
no ip route-cache
no ip mroute-cache
duplex half
!
interface Ethernet1/1
description Gi interface to gprs.cisco.com
ip address 10.9.9.4 255.255.255.0
no ip route-cache
no ip mroute-cache
duplex half
!
interface Ethernet1/2
ip address 10.15.15.10 255.255.255.0
duplex half
!
interface loopback 1
ip address 10.40.40.3 255.255.255.0
!
interface Virtual-Template1
ip unnumber loopback 1
encapsulation gtp
gprs access-point-list gprs
!
. . .
!
gprs access-point-list gprs
access-point 1
access-mode non-transparent
access-point-name www.pdn1.com
aaa-group authentication foo
!
access-point 2
access-mode non-transparent
access-point-name www.pdn2.com
!
access-point 4
access-point-name www.pdn4.com
aaa-accounting enable
aaa-group accounting foo1
!
access-point 5
access-point-name www.pdn5.com
!
gprs maximum-pdp-context-allowed 45000
gprs qos map delay
gprs delay-qos map tos class1 4 class2 3 class3 2 class-best-effort 1
gprs gtp path-echo-interval 30
gprs default aaa-group authentication foo2
gprs default aaa-group accounting foo3
gprs default charging-gateway 10.15.15.1
!
. . .
!
end
GGSN Release 4.0 and later supports end-to-end UMTS QoS by implementing it using Cisco IOS
Differentiated Services (DiffServ) model. The DiffServ model is a multiple service model that can
satisfy differing QoS requirements. With DiffServ, the network tries to deliver a particular kind of
service based on the QoS specified by each packet. This specification can occur in different ways, for
example, using the 6-bit differentiated services code point (DSCP) setting in IP packets or source and
destination addresses. The network uses the QoS specification to classify, mark, shape, and police traffic,
and to perform intelligent queueing.
For complete information on Cisco IOS QoS and the DiffServ service model, see the Cisco IOS Quality
of Service Solutions Configuration Guide.
Command Purpose
Router(config)# gprs qos map umts Enables UMTS QoS mapping on the GGSN.
Note To successfully map UMTS QoS traffic classes to a DiffServ PHB, the class maps must be configured
using the class map and match ip dscp Cisco IOS software commands. For more information about
configuring class maps, see the Cisco IOS Quality of Service Solutions Configuration Guide.
To map a UMTS traffic class to a DiffServ PHB group, use the following command in global
configuration mode:
Command Purpose
Router(config)# gprs umts-qos map traffic-class Enables mapping of UMTS QoS traffic classes to a DiffServ
traffic-class diffserv-phb-group PHB, where the UMTS traffic classes are:
• signalling
• conversational
• streaming
• interactive
• background
and the DiffServ PHB groups are:
• signalling-class
• ef-class
• af1-class
• af2-class
• af3-class
• af4-class
• best-effort
Note Drop precedence indicates the order in which a packet will be dropped when there is congestion on the
network.
Note To successfully map UMTS QoS traffic classes to a DiffServ PHB and assign a DSCP value to a DiffServ
PHB group, the class maps must be configured using the class map and match ip dscp commands. For
more information about configuring class maps, see Cisco IOS Quality of Service Solutions
Configuration Guide and Cisco IOS Quality of Service Solutions Command Reference.
Note By default, signalling class is assigned to CS5 (101000), which is the equivalent of IP precedence 5.
To assign a DSCP value to a DiffServ PHB group, use the following command in global configuration
mode:
Command Purpose
Router(config)# gprs umts-qos map diffserv-phb Assigns a DSCP to a DiffServ PHB group where the DiffServ
diffserv-phb-group [dscp1] [dscp2] [dscp3] PHB groups are:
• signalling
• ef-class
• af1-class
• af2-class
• af3-class
• af4-class
• best-effort
and the DSCPs are:
• dscp1—Required for all classes. Specifies one of 64
DSCP values from 0 to 63. This DSCP value corresponds
to drop precedence 1.
• dscp2—(Optional for AF classes) Specifies one of 64
DSCP values from 0 to 63. This DSCP value corresponds
to drop precedence 2.
• dscp3—(Optional for AF classes) Specifies one of 64
DSCP values from 0 to 63. This DSCP value corresponds
to drop precedence 3.
Command Purpose
Router(config)# gprs umts-qos dscp unmodified [up | Specifies that the subscriber datagram be forwarded through
down | all] the GTP path without modifying its DSCP.
To return to the default value, issue the no gprs umts-qos dscp unmodified command.
class signaling
bandwidth percent 10
policy-map gi-police
class conversational
police cir 5000000 bc 100000
conform-action transmit
exceed-action transmit
violate-action drop
class streaming
police cir 10000000 bc 1000000
conform-action transmit
exceed-action transmit
violate-action drop
class interactive
police cir 50000000 bc 1000000
conform-action transmit
exceed-action transmit
violate-action drop
!
...
! description DHCP interface
!
interface Loopback0
ip address 10.1.1.1 255.255.255.255
!
interface Loopback1
description DHCP interface
ip address 10.7.0.1 255.255.255.255
!
...
!
! description Gn Interface
!
interface FastEthernet1/0
ip address 10.10.2.3 255.255.255.0
no keepalive
duplex full
speed 100
service-policy output gn-policy-outbound
!
! description Gi Interface
!
interface FastEthernet1/1
ip address 10.2.2.2 255.255.255.0
no keepalive
duplex full
speed 100
service-policy input gi-police
service-policy output gi-policy-outbound
!
! description Ga Interface
!
interface FastEthernet2/0
description Ga Interface
ip address 10.3.3.3 255.255.255.0
no ip mroute-cache
no keepalive
duplex full
!
interface Looback 1
ip address 10.40.40.3 255.255.255.0
!
interface Virtual-Template1
ip unnumber loopback 1
encapsulation gtp
gprs access-point-list gprs
!
...
!
gprs maximum-pdp-context-allowed 200001
gprs gtp path-echo-interval 0
!
...
!
! Enable UMTS QoS
gprs qos map umts
!
gprs charging transfer interval 100
gprs charging container volume-threshold 524288
gprs charging disable
snmp-server community public RO
!
...
!
end
Command Purpose
Router(config)# gprs qos default-response requested (Optional) Specifies that the GGSN sets its default QoS
values in the response message exactly as requested in the
create PDP context request message.
Note When the gprs qos default-response requested command is not configured, and GPRS canonical QoS
is not enabled, the GGSN sets its default QoS class to best effort.
Command Purpose
Router# show gprs gtp pdp-context imsi hex-data Displays PDP contexts by International Mobile Subscriber
Identity (IMSI).
Router# show gprs gtp pdp-context qos-delay {class1 | Displays PDP contexts for a specified delay class type.
class2 | class3 | classbesteffort} Applies to GPRS QoS only.
Router# show gprs gtp pdp-context qos-precedence {low Displays PDP contexts for a specified precedence type.
| normal | high} Apply to GPRS QoS only.
Router# show gprs gtp pdp-context tid hex-data Displays PDP contexts by tunnel ID.
Router# show gprs gtp pdp-context umts-class Displays PDP context by UMTS QoS traffic class. Apply to
{conversational | streaming | interactive | UMTS QoS only.
background}
Router# show gprs qos status Displays QoS statistics for the GGSN.
Router# show gprs umts-qos map traffic-class Displays UMTS QoS mapping information.
Note The canonical QoS class and effective bandwidth output fields only apply when GPRS QoS canonical
QoS is in use on the GGSN.
The following sections describe how you can interpret some of the GPRS QoS information that is
provided by the show gprs gtp pdp-context command:
• Determining the ToS Precedence, page 9-21
• Interpreting the Requested and Negotiated GPRS QoS, page 9-22
• Interpreting the Effective Bandwidth for a PDP Context, page 9-23 (Canonical QoS only)
To determine the ToS precedence for a PDP context, you need to convert the hexadecimal value shown
in the tos mask map output field of the show gprs gtp pdp-context command to binary format. From
there, you can interpret the ToS precedence bits, which are the first 3 bits of the binary conversion.
In the following example, we use a tos mask map value of 20 to show this conversion:
Step 1 Convert the value of the tos mask map field (20) to binary, where 2=0010 and 0=0000. This results in
the following binary format:
0010 0000
Step 2 Identify the first 3 bits of the binary representation, which is 001-0 in our example. (The remaining 0000
bits are ignored.)
Step 3 Convert the first 3 bits to a decimal number. In our example, 001=1. Therefore, the ToS precedence for
this PDP context is 1.
To determine the various GPRS QoS class attributes shown in the gprs qos_req and gprs qos_neg output
fields of the show gprs gtp pdp-context command, you need to convert the values provided to binary
format. From there, you can interpret the class attribute values according to the GSM specifications for
QoS, which can be found in GSM standards 02.60, 03.60, and 04.08.
In the following example, we use a GPRS QoS value of 25131F to show this conversion:
Step 1 Convert the hexadecimal value of the gprs qos_req or gprs qos_neq field (25131F) to binary, where
2=0010, 5=0101, 1=0001, 3=0011, 1=0001, and F=1111. This results in the following binary format:
0010 0101 0001 0011 0001 1111
Step 2 Group the bits in the following manner:
First 2 Next 3 bits Next 3 bits Next 4 bits Next 1 bit Next 3 bits Next 3 bits Last 5 bits
bits
00 100 101 0001 0 011 000 1 1111
don’t care delay reliability peak don’t care precedence don’t care mean
throughput
Step 3 Convert the bit groups to decimal numbers, and correlate the value to the QoS classes according to the
GSM specifications. For example, for the delay class, the binary 100=4, which corresponds to delay
class 4.
In this example, the corresponding QoS classes are delay class 4, reliability class 5, peak class 1,
precedence class 3, and mean throughput is best effort:
First 2 Next 3 bits Next 3 bits Next 4 bits Next 1 bit Next 3 bits Next 3 bits Last 5 bits
bits
00 100 101 0001 0 011 000 1 1111
don’t care delay reliability peak don’t care precedence don’t care mean
throughput
class 4 class 5 class 1 class 3 best effort
You can use the show gprs gtp pdp-context tid command to display an output field called effective
bandwidth in bits per second. The effective bandwidth is determined according to the GPRS canonical
QoS class (premium, normal, or best effort) for the PDP context. However, it is an estimate and does not
represent the actual bandwidth in use by the PDP context.
You can calculate the potential number of supported PDP contexts for a class of QoS using the effective
bandwidth value. To determine an estimate of the potential number of PDP contexts of a particular class
that can be supported on the GGSN, you can divide the total bandwidth available on the GGSN by the
effective bandwidth value for the GPRS QoS class.
The following example shows how to estimate the potential number of PDP contexts that the GGSN can
support for a particular canonical QoS class at an expected effective bandwidth:
Step 1 Use the show gprs gtp pdp-context command with either the tid or imsi keywords and find the value
of the effective bandwidth field. In our example, we will use 10000 bps.
Step 2 To estimate the number of best effort PDP contexts that the GGSN can support with an effective
bandwidth of 10000 bps, divide the total amount of resource on the GGSN for canonical QoS by the
effective bandwidth used.
In this example, we will use the default total resource value of 4294967295 and the following
calculation:
4294967295 ÷ 10000
where 4294957295 is the total resource. The result is an estimated 429496 best effort PDP contexts.
Note To verify the total amount of resource on the GGSN for canonical QoS, you can use the show
gprs qos status command.
Note The output of the show gprs qos status command varies depending on the type of QoS method in use
on the GGSN.
The following example shows 2 active PDP contexts on the GGSN that are using the best effort canonical
QoS class. The mean throughput for the 2 PDP contexts is 20000 bps (a cumulative value, which
corresponds to an effective bandwidth of 10000 bps for each PDP context in this example):
The following example displays output from the show gprs qos status command for canonical QoS:
router# show gprs qos status
GPRS QoS Status:
type:Canonical
gsn_used_bandwidth:20000 total gsn_resource:4294967295
mean_throughput_premium:0.000
mean_throughput_normal:0.000 mean_throughput_besteffort 0.000
qos_high_pdp:0 qos_normal_pdp:0
qos_low_pdp :2 qos_premium mean-throughput-deviation 0.500
Interpreting the GGSN Resources Allocated for GPRS Canonical QoS Support
When GPRS QoS is enabled on the GGSN, the show gprs qos status command shows cumulative values
for the currently active PDP contexts on the GGSN (the total gsn_resource and qos premium
mean-throughput-deviation values are not cumulative).
For multiple PDP contexts, the used resource is a cumulative value across all active PDP contexts and
can represent different QoS classes. In the example, the gsn_used_bandwidth value of 20000 bps
represents the total bps in use for the 2 best effort PDP contexts.
To determine the amount of available GGSN resource remaining for canonical QoS support, you can
subtract the current value of the gsn_used_bandwidth from the total gsn_resource. In this example, the
calculation is:
4294967295 – 20000
which equals an estimated 4294947295 resource remaining for canonical QoS processing.
Step 1 To verify the canonical QoS precedence class for which there are currently active PDP contexts, use the
show gprs qos status command. The following example shows that 1 PDP context is currently active
for the high precedence (or premium canonical QoS) class on the GGSN:
The following example displays output from the show gprs qos status command for canonical QoS:
router# show gprs qos status
GPRS QoS Status:
type:Canonical
gsn_used_bandwidth:800 total gsn_resource:1048576
mean_throughput_premium:0.220
mean_throughput_normal:0.000 mean_throughput_besteffort 0.000
qos_high_pdp:1 qos_normal_pdp:0
qos_low_pdp :0 qos_premium mean-throughput-deviation 0.100
Step 2 To display information about active PDP contexts in a particular precedence class, use the show gprs
gtp pdp-context qos-precedence command. The following example shows information about the active
PDP context in the high precedence (premium) class:
Router# show gprs gtp pdp-context qos-precedence high
TID MS Addr Source SGSN Addr APN
4444444444444444 10.2.0.4 Static 10.39.39.1 www.pdn2.com
Step 1 To verify the delay QoS classes for which there are currently active PDP contexts, use the show gprs
qos status command. The following examples shows that there are active PDP contexts for each of the
delay classes except class 3:
Step 2 To display information about PDP contexts in a particular delay class, use the show gprs gtp
pdp-context qos-delay command as shown in the following examples:
Example 1
The following example shows information about the active PDP contexts in the best effort delay QoS
class:
Router# show gprs gtp pdp-context qos-delay classbesteffort
TID MS Addr Source SGSN Addr APN
1111111111111111 10.8.8.1 Static 10.39.39.1 gprt.cisco.com
2222222222222222 10.8.8.2 Static 10.39.39.1 gprt.cisco.com
Example 2
The following example shows information about the active PDP context in delay class 1:
Router# show gprs gtp pdp-context qos-delay class1
TID MS Addr Source SGSN Addr APN
3333333333333333 10.8.8.4 Static 10.39.39.1 gprt.cisco.com
QoS class:interactive
QoS for charging: qos_req:000000 qos_neg:000000
rcv_pkt_count: 0 rcv_byte_count: 0
send_pkt_count: 0 send_byte_count: 0
cef_up_pkt: 0 cef_up_byte: 0
cef_down_pkt: 0 cef_down_byte: 0
cef_drop: 0
charging_id: 223415403
pdp reference count:2
primary dns: 0.0.0.0
secondary dns: 0.0.0.0
primary nbns: 0.0.0.0
secondary nbns: 0.0.0.0
ntwk_init_pdp: 0
Configuration Examples
This section includes the following examples:
• Canonical QoS Configuration Example, page 9-27
• Delay QoS Configuration Example, page 9-29
• UMTS QoS Configuration Example, page 9-30
ip subnet-zero
!
!
no ip dhcp-client network-discovery
!
!
interface Loopback1
ip address 10.100.3.4 255.255.255.255
!
interface FastEthernet0/0
ip address 172.18.43.174 255.255.255.240
duplex half
!
interface Ethernet1/0
description Gi interface to gprt.cisco.com
ip address 10.8.8.6 255.255.255.0
no ip route-cache
no ip mroute-cache
duplex half
!
interface Ethernet1/1
description Gi interface to gprs.cisco.com
ip address 10.9.9.4 255.255.255.0
no ip route-cache
no ip mroute-cache
duplex half
!
interface Ethernet1/2
ip address 10.15.15.10 255.255.255.0
duplex half
!
interface loopback 1
ip address 10.40.40.3 255.255.255.0
!
interface Virtual-Template1
ip unnumber loopback 1
encapsulation gtp
gprs access-point-list gprs
!
. . .
!
gprs access-point-list gprs
access-point 1
access-mode non-transparent
access-point-name gprt.cisco.com
aaa-group authentication foo
!
access-point 2
access-mode non-transparent
access-point-name gprs.cisco.com
!
access-point 4
access-point-name gpru.cisco.com
aaa-accounting enable
aaa-group accounting foo1
!
access-point 5
access-point-name gprv.cisco.com
!
gprs maximum-pdp-context-allowed 90000
!
! Enable canonical QoS
!
gprs qos map canonical-qos
!
! Configure total resource available
! for canonical QoS processing
!
gprs canonical-qos gsn-resource-factor 4294967295
!
! Configure bandwidth estimated for
! best effort canonical QoS class
!
gprs canonical-qos best-effort bandwidth-factor 10000
!
! Configure deviation factor for mean throughput
! calculation for premium QoS class
!
gprs canonical-qos premium mean-throughput-deviation 500
!
! Configure ToS precedence mapping to
ip subnet-zero
!
!
no ip dhcp-client network-discovery
!
!
interface Loopback1
ip address 10.100.3.4 255.255.255.255
!
interface FastEthernet0/0
ip address 172.18.43.174 255.255.255.240
duplex half
!
interface Ethernet1/0
description Gi interface to gprt.cisco.com
ip address 10.8.8.6 255.255.255.0
no ip route-cache
no ip mroute-cache
duplex half
!
interface Ethernet1/1
description Gi interface to gprs.cisco.com
ip address 10.9.9.4 255.255.255.0
no ip route-cache
no ip mroute-cache
duplex half
!
interface Ethernet1/2
ip address 10.15.15.10 255.255.255.0
duplex half
!
interface loopback 1
...
!
ip subnet-zero
ip cef
!
!
no ip domain-lookup
!
!
...
!
class-map match-all conversational
match ip dscp 46
class-map match-any background
description default class
match ip dscp 0
class-map match-any interactive
match ip dscp 26
match ip dscp 28
match ip dscp 30
class-map match-any streaming
match ip dscp 18
match ip dscp 20
match ip dscp 22
class-map match-all signaling
match ip dscp 40
!
!
policy-map gi-policy-outbound
class conversational
priority percent 5
class interactive
bandwidth percent 50
class streaming
bandwidth percent 10
class signaling
bandwidth percent 10
policy-map gn-policy-outbound
class conversational
shape peak 5000000
priority percent 5
class interactive
shape peak 50000000
bandwidth percent 50
class streaming
shape peak 10000000
bandwidth percent 10
class signaling
bandwidth percent 10
policy-map gi-police
class conversational
police cir 5000000 bc 100000
conform-action transmit
exceed-action transmit
violate-action drop
class streaming
police cir 10000000 bc 1000000
conform-action transmit
exceed-action transmit
violate-action drop
class interactive
police cir 50000000 bc 1000000
conform-action transmit
exceed-action transmit
violate-action drop
!
...
! description DHCP interface
!
interface Loopback0
ip address 10.1.1.1 255.255.255.255
!
interface Loopback1
description DHCP interface
ip address 10.7.0.1 255.255.255.255
!
...
!
! description Gn Interface
!
interface FastEthernet1/0
ip address 10.10.2.3 255.255.255.0
no keepalive
duplex full
speed 100
service-policy output gn-policy-outbound
!
! description Gi Interface
!
interface FastEthernet1/1
ip address 10.2.2.2 255.255.255.0
no keepalive
duplex full
speed 100
service-policy input gi-police
service-policy output gi-policy-outbound
!
! description Ga Interface
!
interface FastEthernet2/0
description Ga Interface
ip address 10.3.3.3 255.255.255.0
no ip mroute-cache
no keepalive
duplex full
!
interface Looback 1
ip address 10.40.40.3 255.255.255.0
!
interface Virtual-Template1
ip unnumber loopback 1
encapsulation gtp
gprs access-point-list gprs
!
...
!
gprs maximum-pdp-context-allowed 200001
gprs gtp path-echo-interval 0
!
...
!
! Enable UMTS QoS
gprs qos map umts
!
gprs charging transfer interval 100
gprs charging container volume-threshold 524288
gprs charging disable
snmp-server community public RO
!
...
!
end