Cisco Cisco Packet Data Gateway (PDG)
APN Profile Configuration Mode
gateway-address ▀
Command Line Interface Reference, StarOS Release 17 ▄
1501
gateway-address
Configures the IPv4 or IPv6 address of the GGSN supporting the APN associated with this APN profile. Also, use this
command to create a secondary pool of GGSNs. This command is specific to the SGSN.
command to create a secondary pool of GGSNs. This command is specific to the SGSN.
Product
SGSN
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration > APN Profile Configuration
configure > apn-profile profile_name
Entering the above command sequence results in the following prompt:
[local]host_name(apn-profile-profile_name)#
Syntax
gateway-address ip_address { priority priority | weight weight [ secondary-pool ] }
no gateway-address ip_address
no
Disables the GGSN address configured in this APN profile.
ip_address
Specifies the IP address for the GGSN in IPv4 dotted-decimal or IPv6 colon-separated notation.
priority priority
Specifies the priority, for the configured GGSN address, to be considered during address selection. If the
highest priority GGSN fails to respond, the next priority level GGSN is selected.
highest priority GGSN fails to respond, the next priority level GGSN is selected.
priority
is an integer
from 1 through 100. Note that the lower integer has the higher priority, so that 1 is the highest priority.
weight weight [ secondary-pool ]
Specifies the weight (preference) assigned to a GGSN to facilitate load balancing.
weight
is an integer from
1 to 100 where 1 is the least preferred and 100 is the most preferred.
If a weight is assigned to an address, then load balancing (of primary CPC requests) depends on the weight
value. For example:
If a weight is assigned to an address, then load balancing (of primary CPC requests) depends on the weight
value. For example:
GGSN1 172.16.130.1 weight 30 and GGSN2 172.16.130.3 weight 70
With this configuration, 30% of the activation requests for this APN will go to GGSN1 and 70% of the
requests will go to GGSN2. Also note that the sum of the weights does not need to be 100. The calculation of
weight percentiles is carried out proportionately, so the following configuration will also yield the same 30%
- 70% results:
requests will go to GGSN2. Also note that the sum of the weights does not need to be 100. The calculation of
weight percentiles is carried out proportionately, so the following configuration will also yield the same 30%
- 70% results:
GGSN1 172.16.130.1 weight 6 and GGSN2 172.16.130.3 weight 14