To forward downstream traffic to the correct PDP context, the GGSN uses either the GRE tunnel ID or the
VLAN ID to match the packet. When forwarding traffic upstream, the GGSN uses the tunnel and forwarding
information in the IP pool configuration; overlapping pools must be configured in the APN in such instances.
When a PDP context is created, the IP address is assigned from the IP pool. In this case the forwarding rules
are also configured into the GGSN. If the address is assigned statically, when the GGSN confirms the IP
address from the pool configured in the APN, the forwarding rules are also applied.
The GGSN can scale to as many actual overlapping pools as there are VLAN interfaces per context, and there
can be multiple contexts per GGSN. The limit is the number of IP pools. This scalability allows operators
who wish to provide VPN services to customers using the customer's private IP address space, not to be
concerned about escalating hardware costs or complex configurations.
RADIUS VLAN Support – Enhanced Charging Services
VPN customers often use private address space which can easily overlap with other customers. The subscriber
addresses are supported with overlapping pools which can be configured in the same virtual routing context.
RADIUS Server and NAS IP addresses do not need to be in separate contexts, thereby simplifying APN and
RADIUS configuration and network design. This feature allows the following scenarios to be defined in the
same context:
•
Overlapping RADIUS NAS-IP addresses for various RADIUS server groups representing different
APNs.
•
Overlapping RADIUS server IP addresses for various RADIUS servers groups.
Every overlapping NAS-IP address is given a unique next-hop address which is then bound to an interface
that is bound to a unique VLAN, thereby allowing the configuration to exist within the same context.
The system forwards RADIUS access requests and accounting messages to the next hop defined for that
NAS-IP; the connected routers forward the messages to the RADIUS server. The next hop address determines
the interface and VLAN to use. Traffic from the server is identified as belonging to a certain NAS-IP by the
port/VLAN combination.
The number of RADIUS NAS-IP addresses that can be configured is limited by the number of loopback
addresses that can be configured.
APN Support – PDN Gateway (P-GW)
P-GW Access Point Name (APN) supports extensive parameter configuration flexibility for the APN. VLAN
tagging may be selected by the APN, but are configured in the P-GW independently from the APN.
Creating VLAN Tags
Use the following example to create VLANs on a port and bind them to pre-existing interfaces. For information
on creating interfaces, refer to System Interfaces and Ports.
config
port ethernet slot/port
no shutdown
vlan vlan_tag_ID
ASR 5500 System Administration Guide, StarOS Release 21.5
236
VLANs
RADIUS VLAN Support – Enhanced Charging Services
To Next Page
Loading...
Need help?
General
