Cisco Cisco Packet Data Gateway (PDG)
Configuring the Evolved Packet Data Gateway
Configuring the System to Perform as an Evolved Packet Data Gateway ▀
ePDG Administration Guide, StarOS Release 18 ▄
91
Required
Information
Information
Description
Physical Ethernet
port number
port number
The physical Ethernet port to which the interface(s) will be bound. Ports are identified by the chassis slot
number where the line card resides, followed by the number of the physical connectors on the card. For
example, port 24/1 identifies connector number 1 on the card in slot 24. A single physical port can facilitate
multiple interfaces.
number where the line card resides, followed by the number of the physical connectors on the card. For
example, port 24/1 identifies connector number 1 on the card in slot 24. A single physical port can facilitate
multiple interfaces.
Required Information for ePDG Context and Service Configuration
The following table lists the information that is required to configure the ePDG context and service on the ePDG.
Table 21. Required Information for ePDG Context and Service Configuration
Required Information
Description
ePDG Context Configuration
ePDG context name
The name of the ePDG context, which can be from 1 to 79 alpha and/or numeric characters.
EAP profile name(s)
The name(s) of the EAP profile(s) to be used for UE authentication via the EAP authentication method.
IPSec transform set
name(s)
name(s)
The name(s) of the IPSec transform set(s) to be used by the ePDG service.
IKEv2 transform set
name(s)
name(s)
The name(s) of the IKEv2 transform set(s) to be used by the ePDG service.
Crypto template
name(s)
name(s)
The name(s) of the IKEv2 crypto template(s) to be used by the ePDG service.
Configuration for the SWu, SWm, and DNS Interfaces, and the SWu and SWm Loopback Interfaces
SWu interface name
The name of the SWu interface, which can be from 1 to 79 alpha and/or numeric characters. This is the
interface that carries the IPSec tunnels between the WLAN UEs and the ePDG.
interface that carries the IPSec tunnels between the WLAN UEs and the ePDG.
SWm interface name
The name of the SWm interface, which can be from 1 to 79 alpha and/or numeric characters. This is the
interface between the ePDG and the external 3GPP AAA server.
interface between the ePDG and the external 3GPP AAA server.
DNS interface name
The name of the DNS interface, which can be from 1 to 79 alpha and/or numeric characters. This is the
interface between the ePDG and the external DNS.
interface between the ePDG and the external DNS.
SWu loopback
interface name
interface name
The name of the SWu loopback interface, which can be from 1 to 79 alpha and/or numeric characters.
SWm loopback
interface name
interface name
The name of the SWm loopback interface, which can be from 1 to 79 alpha and/or numeric characters.
IP addresses and subnet
masks
masks
The IP addresses assigned to the SWu (IPv4), SWm (either IPv4 or IPv6), and DNS interfaces (either
IPv4 or IPv6), and to the SWu (IPv4) and SWm (either IPv4 or IPv6) loopback interfaces.
IPv4 or IPv6), and to the SWu (IPv4) and SWm (either IPv4 or IPv6) loopback interfaces.
Physical Ethernet port
numbers
numbers
The physical Ethernet ports to which the SWu, DNS, and SWm interfaces will be bound. Ports are
identified by the chassis slot number where the line card resides, followed by the number of the physical
connectors on the card. For example, port 19/1 identifies connector number 1 on the card in slot 19. A
single physical port can facilitate multiple interfaces.
identified by the chassis slot number where the line card resides, followed by the number of the physical
connectors on the card. For example, port 19/1 identifies connector number 1 on the card in slot 19. A
single physical port can facilitate multiple interfaces.