Cisco Cisco Packet Data Interworking Function (PDIF)
Configuring the Evolved Packet Data Gateway
Configuring the System to Perform as an Evolved Packet Data Gateway ▀
ePDG Administration Guide, StarOS Release 17 ▄
87
The
aaa group
command configures the AAA server group in the ePDG context and the
diameter
authentication
commands specify the associated Diameter authentication settings.
The
ikev2-ikesa policy use-rfc5996-notification
command enables processing for new notification
payloads added in RFC 5996, and is disabled by default.
Creating the ePDG Service
Use the following configuration example to do the following:
Create the ePDG service.
Specify the context in which the MAG/EGTP service will reside.
Specify the ePDG FQDN (Fully Qualified Domain Name) used for longest suffix matching during P-GW
dynamic allocation.
Bind the crypto template to the ePDG service.
Specify the Diameter origin endpoint and associated settings.
Specify the name of the DNS client for DNS queries and bind the IP address.
Important:
When GTPv2 is used instead of mobile-access-gateway configuration, ePDG shall use associate
egtp-service
egtp_service_name
.
configure
context <epdg_context_name>
epdg-service <epdg_service_name>
plmn id mcc <code> mnc <code>
mobile-access-gateway context <egress_context_name> mag-service
<mag_service_name>
<mag_service_name>
setup-timeout <seconds>
fqdn <domain_name>
bind address <ip_address> crypto-template <crypto_template_name>
pgw-selection agent-info error-terminate
dns-pgw selection topology weight
exit
ip route <ip_address/subnet mask> <ip_address/subnet mask> <gateway_ip_address>
<mgmt_interface_name>
<mgmt_interface_name>
ip domain-lookup
ip name-servers <ip_address>