| Required
Information |
Description |
| Destination
context name |
An
identification string from 1 to 79 characters (alpha and/or
numeric) by which the destination context will be recognized
by the system.
NOTE: For
this configuration, the destination context name should not match the domain
name of a specific APN.
|
| APN Configuration |
| APN
name |
An
identification string by which the APN will be recognized by the
system. The name can be from 1 to 62 alpha and/or
numeric characters and is not case sensitive. It may also
contain dots ( . ) and/or dashes ( - ).
Multiple names are
needed if multiple APNs will be used.
|
| Accounting
mode |
Selects
the accounting protocol. GTPP or RADIUS are supported. In addition, accounting
can be completely disabled. The default is to perform accounting
using GTPP.
NOTE: The
examples discussed in this chapter assumes GTPP is used.
|
| Authentication
protocols used |
Specifies
how the system handles authentication: using a protocol (such
as CHAP, PAP, or MSCHAP), or
not requiring any authentication. |
| APN
charging characteristics (CC) (optional) |
Specifies
whether or not the GGSN accepts the CC from the SGSN for home, visiting, and
roaming subscribers.
By default the GGSN
accepts the CC from the SGSN for all three scenarios.
If the GGSN is to use
its own CC for any of these scenarios, then each scenario
requires the specification of behavior bits and a profile index
to use.
NOTE: The
profile index parameters are configured as part of the GGSN service.
|
| Domain
Name Service (DNS) information (optional) |
If
DNS will be used for the APN, IP addresses can be configured
for primary and secondary DNS servers. |
| IP
address allocation method |
Specifies
how sessions facilitated by this APN will receive an IP address. IP addresses
can be assigned using one of the following methods:
-
Dynamic: Address
can be dynamically assigned from one of the sources.
-
Dynamic Host Control
Protocol (DHCP) server: The system
can be configured to act as a DHCP proxy and receive address from
the server in advance and assign them as needed or it can relay DHCP
messages from the MS.
-
Local address pools: The
system can be configured with local address pools.
-
Static: MS
IP addresses can be permanently assigned.
By default, the
system is configured to either dynamically assign addresses from
a local pool and/or allow static addresses.
|
| IP
address pool name |
If
addresses will be dynamically assigned from a locally configured
private pool, the name of the pool must be configured. If
no name is configured, the system will automatically use
any configured public pool. |
| IP
destination context name |
The
name of the system destination context to use for subscribers accessing the
APN. If no name is specified, the system automatically
uses the system context in which the APN is configured. |
| Maximum
number of PDP contexts |
The
maximum number of PDP contexts that are supported for the APN.
The maximum number
can be configured to any integer value from 1 to 1500000. The
default is 1000000.
|
| PDP
type |
The
type of PDP contexts supported by the APN. The type can
be IPv4, IPv6, both IPv4 and IPv6, or
PPP. IPv4 support is enabled by default. For IPv6
PDP configuration, at least one IPv6 interface needs to
be configured in the destination context. |
| Verification
selection mode |
The
level of verification that will be used to ensure a MS’s
subscription to use the APN. The GGSN uses any of the following
methods:
- No verification and
MS supplies APN
- No verification and
SGSN supplies APN
- Verified by SGSN (default)
|
| DHCP Interface Configuration (optional) |
| DHCP
interface name |
An
identification string from 1 to 79 characters (alpha and/or
numeric) by which the interface will be recognized by the
system.
Multiple names are
needed if multiple interfaces will be configured.
|
| IP
address and subnet |
These
will be assigned to the DHCP interface and be bound to the DHCP service.
Multiple addresses
and/or subnets are needed if multiple interfaces will be
configured.
|
| Gateway
IP address |
Used
when configuring static routes from the DHCP interface(s) to
a specific network. |
| Physical
port number |
The
physical port to which the interface will be bound. Ports
are identified by the chassis slot number where the line card resides
in, followed by the number of the physical connector on
the line card. For example, port 17/1 identifies
connector number 1 on the card in slot 17.
A single physical port
can facilitate multiple interfaces.
|
| Physical
port description |
An
identification string from 1 to 79 characters (alpha and/or
numeric) by which the physical port will be recognized
by the system.
Multiple descriptions
are needed if multiple ports will be used.
Physical ports are
configured within the source context and are used to bind logical
DHCP interfaces.
|
| DHCP Service Configuration (optional) |
| DHCP
Service Name |
This
is an identification string between 1 and 63 characters (alpha
and/or numeric) by which the DHCP service will
be recognized by the system.
Multiple names are
needed if multiple GGSN services will be used.
|
| DHCP
Server Information |
The
IP address of each DHCP server that the system is to communicate
with must be configured
.Multiple
servers can be configured. If multiple servers are configured, each
can be assigned a priority from 1 to 1000. The default
priority is 1.
|
| Lease
Duration |
Specifies
the minimum and maximum allowable lease times that are accepted
in responses from DHCP servers.
-
Minimum Lease Time: Measured
in seconds and can be configured to any integer value from 600 to
3600. The default is 600 seconds.
-
Maximum Lease Time: Measured
in seconds and can be configured to any integer value from 10800
to 4294967295. The default is 86400 seconds.
|
| AAA Interface Configuration |
| AAA
interface name |
This
is an identification string from 1 to 79 characters (alpha
and/or numeric) by which the interface will be
recognized by the system.
Multiple names are
needed if multiple interfaces will be configured.
|
| IP
address and subnet |
These
will be assigned to the AAA interface.
Multiple addresses
and/or subnets are needed if multiple interfaces will be
configured.
|
| Physical
port number |
This
specifies the physical port to which the interface will be bound. Ports are
identified by the chassis slot number where the line card resides
in, followed by the number of the physical connector on
the line card. For example, port 17/1
identifies connector number 1 on the card in slot 17.
A single physical port
can facilitate multiple interfaces.
|
| Physical
port description |
This
is an identification string from 1 to 79 characters (alpha
and/or numeric) by which the physical port will
be recognized by the system.
Multiple descriptions
are needed if multiple ports will be used.
Physical ports are
used to bind logical AAA interfaces.
|
| Gateway
IP address |
Used
when configuring static routes from the AAA interface(s) to
a specific network. |
| RADIUS Server Configuration |
| RADIUS Authentication
server |
IP Address: Specifies
the IP address of the RADIUS authentication server the system will
communicate with to provide subscriber authentication functions.
Multiple addresses
are needed if multiple RADIUS servers will be configured. If
multiple servers are configured, each can be assigned a priority.
|
| Shared Secret: The
shared secret is a string between 1 and 15 characters (alpha
and/or numeric) that specifies the key that is
exchanged between the RADIUS authentication server and the source
context.
A shared secret is
needed for each configured RADIUS server.
|
| UDP Port Number: Specifies
the port used by the source context and the RADIUS authentication
server for communications. The UDP port number can be any
integer value between 1 and 65535. The default value is 1812. |
| RADIUS Accounting server (optional) |
IP Address: Specifies
the IP address of the RADIUS accounting server that the source context
will communicate with to provide subscriber accounting functions.
Multiple addresses
are needed if multiple RADIUS servers will be configured.RADIUS
accounting servers are configured within the source context.
Multiple servers can
be configured and each assigned a priority.
|
| Shared Secret: The
shared secret is a string between 1 and 15 characters (alpha
and/or numeric) that specifies the key that is
exchanged between the RADIUS accounting server and the source context.
A shared secret is
needed for each configured RADIUS server.
|
| UDP Port Number: Specifies
the port used by the source context and the RADIUS Accounting server
for communications. The UDP port number can be any integer
value between 1 and 65535. The default value is 1813. |
| RADIUS
attribute NAS Identifier |
Specifies
the name by which the source context will be identified in the Access-Request
message(s) it sends to the RADIUS server. The
name must be from 1 to 32 alpha and/or numeric characters
and is case sensitive. |
| RADIUS
NAS IP address |
Specifies
the IP address of the system’s AAA interface. A
secondary address can be optionally configured. |
| PDN Interface Configuration |
| PDN
interface name |
This
is an identification string from 1 to 79 characters (alpha
and/or numeric) by which the interface will be
recognized by the system.
Multiple names are
needed if multiple interfaces will be configured.
PDN interfaces are
configured in the destination context.
|
| IP
address and subnet |
These
will be assigned to the PDN interface.
Multiple addresses
and/or subnets are needed if multiple interfaces will be
configured.
|
| Physical
port number |
This
specifies the physical port to which the interface will be bound. Ports are
identified by the chassis slot number where the line card resides
in, followed by the number of the physical connector on
the line card. For example, port 17/1
identifies connector number 1 on the card in slot 17.
A single physical port
can facilitate multiple interfaces.
|
| Physical
port description(s) |
This
is an identification string from 1 to 79 characters (alpha
and/or numeric) by which the physical port will
be recognized by the system.
Multiple descriptions
will be needed if multiple ports will be used.
Physical ports are
configured within the destination context and are used to bind logical
PDN interfaces.
|
| Gateway
IP address(es) |
Used
when configuring static routes from the PDN interface(s) to
a specific network. |
| IP Address Pool Configuration |
| IP
address pool name(s) |
This
is an identification string from 1 to 31 characters (alpha
and/or numeric) by which the physical port will
be recognized by the system.
Multiple descriptions
will be needed if multiple ports will be used.
|
| Pool
addresses, subnet mask and type |
The
pool can consist of either of the following:
- An entire subnet configured
using the initial address and the subnet mask
- A range of addresses
configured using the first and last IP addresses in the range
The pool can be configured
as public, private, or static. Public
pools can also be assigned a priority.
|