Cisco Cisco Packet Data Gateway (PDG)
Context Configuration Mode Commands A-D
apn ▀
Command Line Interface Reference, StarOS Release 18 ▄
2331
apn
Creates or deletes Access Point Name (APN) templates and enters the APN Configuration Mode within the current
context.
context.
Product
GGSN
P-GW
SAEGW
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration > Context Configuration
configure > context context_name
Entering the above command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
[ no ] apn apn_name [ -noconfirm ]
no
Deletes a previously configured APN template.
apn_name
Specifies a name for the APN template as an alphanumeric string of 1 through 62 characters that is case
insensitive. It may also contain dots (.) and/or dashes (-).
insensitive. It may also contain dots (.) and/or dashes (-).
-noconfirm
Executes the command without any additional prompt and confirmation from the user.
Caution:
If this keyword option is used with the
no apn
apn_name
command, the APN named
apn_name
will
be deleted with all active/inactive subscribers without prompting any warning or confirmation.
Usage
This command creates an APN within the system and causes the CLI to enter the APN Configuration Mode.
The APN is a logical name for a packet data network and/or a service to which the system supports access.
When a create PDP context request is received by the system, it examines the APN information element
within the packet. The system determines if an APN with the identical name is configured. If so, the system
uses the configuration parameters associated with that APN as a template for processing the request. If the
names do not match, the request is rejected with a cause code of 219 (DBH, Missing or unknown APN).
APN templates should be created/configured within destination contexts on the system.
The APN is a logical name for a packet data network and/or a service to which the system supports access.
When a create PDP context request is received by the system, it examines the APN information element
within the packet. The system determines if an APN with the identical name is configured. If so, the system
uses the configuration parameters associated with that APN as a template for processing the request. If the
names do not match, the request is rejected with a cause code of 219 (DBH, Missing or unknown APN).
APN templates should be created/configured within destination contexts on the system.
Up to 1000 APNs can be configured in the GGSN.
In StarOS v12.x and earlier, up to 1024 APNs can be configured in the P-GW.