Cisco Cisco Packet Data Gateway (PDG)
exit
port ethernet
<
slot_number/port_number
>
no shutdown
vlan
vlan
<
tag
>
bind interface
<
epdg_dns_interface_name
> <
epdg_context_name
>
exit
port ethernet
<
slot_number/port_number
>
no shutdown
vlan
vlan
<
tag
>
bind interface
<
swm_interface_name
> <
epdg_context_name
>
exit
port ethernet
<
slot_number/port_number
>
no shutdown
vlan
vlan
<
tag
>
bind interface
<
s2b_interface_name
> <
egress_context_name
>
exit
end
The mag-service command creates the MAG (Mobile Access Gateway) service that communicates with the
LMA (Local Mobility Anchor) service on the P-GW to provide network-based mobility management. The
ipv6 route command configures a static IPv6 route to the next-hop router. In this configuration, it configures
a static route from the ePDG to the P-GW over the S2b interface. The bind interface command binds each
logical interface to a physical Ethernet port.
LMA (Local Mobility Anchor) service on the P-GW to provide network-based mobility management. The
ipv6 route command configures a static IPv6 route to the next-hop router. In this configuration, it configures
a static route from the ePDG to the P-GW over the S2b interface. The bind interface command binds each
logical interface to a physical Ethernet port.
Egress Context and EGTP Service Configuration
Create the Egress context and the EGTP (Evolved GPRS Tunnel Protocal) service by following the configuration
example in the section
example in the section
Configuring the Egress Context and EGTP Service, on page 103
Configuring the Egress Context and EGTP Service
Use the following configuration example to configure thegress context, the EGTP (Evolved GPRS Tunnel
Protocal) service, the S2b interface and S2b loopback interface to the P-GW, and bind all of the logical
interfaces to the physical Ethernet ports.
Protocal) service, the S2b interface and S2b loopback interface to the P-GW, and bind all of the logical
interfaces to the physical Ethernet ports.
configure
context
<
egress_context_name
>
interface
<
s2b_interface_name
>
ipv4/ipv6 address
<
ipv6_address
>
exit
interface
<
s2b_loopback_interface_name
>
ipv4/ipv6 address
<
ipv6_address
>
exit
subscriber default
exit
aaa group default
exit
gtpp group default
exit
gtpu-service
<
gtpu-service-name
>
reg-lifetime
<
seconds
>
bind ipv4/ipv6-address
<
s2bloopbackipv4/ipv6_address
>
exit
egtp-service egtp-epdg-egress
ePDG Administration Guide, StarOS Release 19
103
Configuring the Evolved Packet Data Gateway
Egress Context and EGTP Service Configuration