1. 1
Cisco SP Wi-Fi Mobility Solutions:
VoWi-Fi Trusted Model using
SaMoG Gateway Configuration Guide
Overview
This guide provides you step-by-step process of going over how the subscriber sessions are created on
SaMOG (S2a Mobility over GTP) and PGW running on standalone ASR5K simulated instance. It also
introduces you to other elements of the architecture such as Access Points, Wireless LAN Controller,
access switch etc. At the end of this exercise, you would get familiarity with how sessions are created on
PMIPv6 over WLAN Controller and how to configure the SaMOG gateway.
Outline
Here are the activities that would be done during this lab:
• Connect user equipment to the SSID
• Verify the configured credentials (both subscriber side and back end)
• Configure SaMOG on ASR5k
• Verify EPC/PGW on ASR5K
• Verifying the outputs using show commands.
• Finally, verify that you can get IP address on the client device
5. 5
Topology and Addressing Details of each pod:
Lab Devices Access:
Devices
ACCESS
User
ID
Password
SSH
Server
ssh
to
128.107.91.226
samogX
samogX
WLC
https://128.107.91.226
cisco
Cisco123
Samog0X
telnet://10.1.X.61
(
from
vnc
or
ssh
server)
cisco
Cisco123
PGW0X
telnet://10.1.X.51
(
from
vnc
or
ssh
server)
cisco
Cisco123
“X” refers to the POD you are connecting to
Wi-Fi Access:
SSID
authentication
Tunnel
Type
to
SaMOG
samog0X
eap-‐aka
PMIPv6
“X” refers to the POD you are connecting to
6. 6
Lab Devices Address:
1. Interface Addresses on SaMOG
Interface Name Context Port Role VLAN ID Address
LOCAL1 local 1/1 Mgmt - 10.1.X.61/24
samog-S2a samog 1/10 GTPc to PGW 18X 10.8.X.61/24
samog-STa samog 1/10 Diameter to AAA 13X 10.3.X.61/24
samog-SWw samog 1/10 PMIPv6 to MAG 14X 10.4.X.61/24
samog-aaa samog 1/10 AAA to Access 12X 10.2.X.61/24
samog-egress samog 1/10 GTPu to PGW 16X 10.6.X.61/24
“X” refers to the POD you are connecting to
2. Interface Addresses on EPC
Interface Name Context Port Role VLAN ID Address
LOCAL1 local 1/1 Mgmt - 10.1.X.51/24
pgw-ingress pgw 1/10 GTPu from SaMOG 16X 10.6.X.51/24
pgw-s2a pgw 1/10 GTPc from SaMOG 18X 10.8.X.51/24
web_portal web 1/10 Web interface 130 10.3.0.1X/24
“X” refers to the POD you are connecting to
3. POOL ADDRESS on EPC
POOL NAME Context Address WEB ADDRESS
s2a-poolX Pgw 10.99.X.0/24 www.samog.com
“X” refers to the POD you are connecting to
7. 7
Verification on clients:
Exercise Description
The first thing to do is to connect to SSID of respective POD, At this point the client will not be
able to connect into the network. There will be an authentication failure before configuring the
SaMOG and PGW.
Exercise Objective
After completing this task, we should be able to validate that the client cannot connect into the
network before actually configuring the SaMOG gateway and PGW.
Verification on client device:
Steps to Complete Task
Step 1: Open Wi-Fi Setting menu and select the SSID corresponding to your POD
8. 8
Step 2: Choose EAP-AKA from the drop down menu for available EAP options
Step 3: The client will show that there is an authentication error
9. 9
Solution Explanation and Clarification
In this section, you have connected the user equipment to SSID of the POD assigned
Task Verification
You verified that the client is not authenticated since your SaMOG Gateway has not been
configured yet.
10. 10
WLC Configuration Verification
Exercise Description
In this exercise, you would be verifying pre-configured WLC setting in order for the clients to be
associated to your SSID.
Exercise Objective
The objective of this exercise is to make sure that WLC has been correctly configured as a MAG for
SaMOG requirements. You would learn to verify the WLC configuration as a PMIPv6 MAG and how
to communicate to AAA server
Verification Configuration on Wireless Lan Controller (WLC):
Step 1: Connect to the Wireless LAN controller using the link https://128.107.91.226 from the web browser.
Use username/password cisco /Cisco123 to log into WLC Verify the details of the SSID’s associated with
each POD by clicking on WLANs Tab, and click on WLAN ID of the above output to get to the following
output
Step 2: Verify if the proper interface is associated
11. 11
Step 3: Verify the security parameters configured for the clients to associate to the AP.
(WPA2/AES + 802.1x)
Step 4: Verify the Authentication Server addresses are correct.
12. 12
Step 5: Verify that WLAN has PMIPv6 configured in the advanced tab
Solution Explanation and Clarification
In this section, you have connected to wireless LAN controller using the address provided above.
This was done using a browser and is accessed via User Interface after connecting to the VNC
server. This task was mainly a check on the parameters configured for setting up MAG on the WLC
Task Verification
In this section you also verified the security protocols configured to authenticate the clients and
other AAA parameters, which the WLC uses to communicate to SaMOG.
End Verification
13. 13
ASR 5K PGW Configuration
Exercise Description
In this exercise, you would be verifying the PGW configuration running on ASR5K. Mainly how it is
configured to be able to communicate to the SaMOG Gateway, and the address pool it assigns to
the clients.
Exercise Objective
The objective of this exercise is to make sure that the user device that connects to the network is
provided address, and is able to access the Web portal out of the Gi interface.
Access to PGW from SSH
Step 1: To access the PGW associated to your POD, use any SSH client to connect into the pod.
The
SSH IP: 172.28.43.223
SSH user ID: samogX
SSH password: samogX
Step 2: Telnet to your PGW from the SSH session. “telnet 10.1.X.51”,
Login ID: cisco
Password: Cisco123
“X” is your POD number
PGW Interface Configuration Breakdown
PGW is connected to the following four interfaces
- LOCAL1 (Mgmt Interface)
- pgw-ingress (GTP data interface from SaMOG)
- pgw-s2a (GTP data interface from SaMOG)
- sgi-ipv4 (Web Interface)
Interface Name Context Port Role VLAN ID Address
LOCAL1 local 1/1 Mgmt - 10.1.X.51/24
pgw-ingress pgw 1/10 GTPu from SaMOG 16X 10.6.X.51/24
pgw-s2a pgw 1/10 GTPc from SaMOG 18X 10.8.X.51/24
web-portal web 1/10 Web interface 130 10.3.0.1X/24
Address Pool on EPC
POOL NAME Context Address WEB ADDRESS
s2a-poolX pgw 10.99.X.0/24 www.samog.com
“X” refers to the POD you are connecting to
14. 14
PGW: Interface Configuration (verification)
Following configuration has already been done. Do not configure them again.
Verify the following contexts are there by using command “show context”
[local]sevt-pgw0X # show context
Context Name ContextID State
------------ --------- -----
local 1 Active
pgw 2 Active
web 3 Active
Verify that the different parameters that are required in the PGW are configured according to your POD
number X, using command “show configuration” from the CLI. Please verify various details listed below
to their corresponding context
context local
interface LOCAL1
ip address 10.1.X.51 255.255.255.0
#exit
ip route 10.1.0.0 255.255.0.0 10.1.X.1 LOCAL1
#exit
Please verify that the IP address and route is correct for your
corresponding POD
port ethernet 1/1
no shutdown
bind interface LOCAL1 local
#exit
Please verify that the interface is bind to local context
local context
local contextlocal context
15. 15
context pgw
interface pgw-ingress
ip address 10.8.X.51 255.255.255.0
#exit
interface pgw-s2a
ip address 10.6.X.51 255.255.255.0
#exit
Please verify that the IP has been defined for each interface for your
corresponding POD in the pgw context
context web
ip access-list ecs
redirect css service spwifi any
#exit
ip pool s2a-pool2 10.99.X.0 255.255.255.0
public 0 subscriber-gw-address 10.99.X.1
interface sgi-ipv4
ip address 10.7.X.51 255.255.255.0
#exit
subscriber default
exit
apn cisco.com
selection-mode subscribed sent-by-ms chosen-
by-sgsn
accounting-mode none
dns primary 10.3.0.241
ip source-violation ignore
ip address pool name s2a-pool2 exit
apn samog0X.com
selection-mode subscribed sent-by-ms chosen-
by-sgsn
virtual-apn preference 1 apn cisco.com
exit
aaa group default
#exit
gtpp group default
#exit
ip route 0.0.0.0 0.0.0.0 10.7.X.1 sgi-ipv4
ip igmp profile default
#exit
Please verify that the IP has been defined for each interface for your
corresponding POD for the web context. Also verify if IP pool has
pgw context
web context
16. 16
been defined for the corresponding POD. Verify if the APNs have
been defined as well
port ethernet 1/10
no shutdown
vlan 18X
no shutdown
bind interface pgw-ingress pgw
#exit
vlan 16X
no shutdown
bind interface pgw-s2a pgw
#exit
vlan 130
no shutdown
bind interface web_portal web
#exit
Please verify that the each interface has been bound and tied to a
context
PGW: Services verification
Verify the following lines in “pgw” context that map the services with the SaMOG gateway
config
context pgw
gtpu-service pgw-samog-gtpu
bind ipv4-address 10.6.X.51
exit
egtp-service pgw-in
interface-type interface-pgw-ingress
associate gtpu-service pgw-samog-gtpu
gtpc bind ipv4-address 10.8.X.51
exit
pgw-service pgw
plmn id mcc 222 mnc 90
associate egtp-service pgw-in
exit
Verification of Configured PGW pieces:
Now all portion required for PGW configuration is complete. The next task is to verify if the configuration has
been done correctly.
port verification
17. 17
Verification of Interfaces (local):
Verify that different interfaces are all up in the local context
[local]sevt-pgw0X # show ip interface summary
Interface Name Address/Mask Port Status
============================== =================== ================== ======
LOCAL1 10.1.X.51/24 1/1 untagged UP
Total interface count: 1
Verification of Interfaces (pgw):
Verify that different interfaces are all up in the pgw context
[pgw]sevt-samog0X # context pgw
[pgw]sevt-samog0X # show ip interface summary
Interface Name Address/Mask Port Status
============================== =================== ================== ======
pgw-ingress 10.8.X.51/24 1/10 vlan 18X UP
pgw-s2a 10.6.X.51/24 1/10 vlan 16X UP
Total interface count: 2
Verification of Interfaces (web):
Verify that different interfaces are all up in the pgw context
[pgw]sevt-samog0X # context web
[web]sevt-samog0X # show ip interface summary
Interface Name Address/Mask Port Status
============================== =================== ================== ======
============================== =================== ================== ======
web_portal 10.3.0.1X/24 1/10 vlan 130 UP
Total interface count: 1
Verification PGW services:
Verify that different services that are required in PGW for SaMOG are started from the pgw context
18. 18
[pgw]sevt-pgw01# show pgw-service all
Service name : pgw
Service-Id : 3
Context : pgw
Status : STARTED
EGTP Service : pgw-in
LMA Service : Not defined
GGSN Service : Not defined
IPNE Service : Not defined
Peer Map : Not defined
Session-Delete-Delay Timer : Disabled
Session-Delete-Delay Timeout : n/a
PLMN ID List : MCC: 222, MNC: 090
Newcall Policy : None
dns-client Context Name : pgw
gx-li context : pgw
gx-li transport : udp
QCI-QOS Mapping Table Name : n/a
Authorize : Disabled
S6b IPv6 Reporting: Disabled
Duplicate Subscriber Addr Request: Reject
Fqdn-name : Disabled
SAEGW service : n/a
EGTP Overcharge Protection : Disabled
EGTP Cause Code Handling : Disabled
Temp Failure: n/a
Retry Timeout: n/a
Maximum Retry: n/a
EGTP SGW Restoration Handling : Disabled
Session Hold Timer: n/a
Timeout: n/a
EGTP Modify berarer cmd negotiate qos : Disabled
GTPC Outgoing Throttling: Disabled
RLF Template Name: N/A
GTPC Incoming Throttling Params: Not Configured
Message Rate: Default
Delay Tolerance: Default
Queue Size: Default
[pgw]sevt-pgw01# show gtpu-service all
Service name: pgw-samog-gtpu
Context: pgw
State: Started
Echo Interval: Disabled
19. 19
Sequence number: Disabled
Include UDP Port Ext Hdr: FALSE
Max-retransmissions: 4
Retransmission Timeout: 5 (secs)
IPSEC Tunnel Idle Timeout:60 (secs)
Allow Error-Indication: Disabled
Address List: 10.6.X.51
GTPU UDP Checksum: Enabled - Attempt Optimize Default Mode
Path Failure Detection
on gtp echo msgs: Set
Path Failure Clear Trap : non-echo
[pgw]sevt-pgw01# show egtp-service all
Service name : pgw-in
Service-Id : 2
Context : pgw
Interface Type : pgw-ingress
Status : STARTED
Restart Counter : 23
Message Validation Mode : Standard
GTPU-Context : pgw
GTPC Retransmission Timeout : 5
GTPC Maximum Request Retransmissions : 4
GTPC IP QOS DSCP value : 10
GTPC Echo : Enabled
GTPC Echo Mode : Default
GTPC Echo Retransmission Timeout : 5
GTPC Echo Interval : 60
GTP-C Bind IPv4 Address : 10.8.X.51
GTP-C Bind IPv6 Address : Not configured
20. 20
ASR5K SaMOG Configuration
Exercise Description
In this exercise, you would be verifying and configuring SaMOG in order for the clients to connect to
the Internet. Also, you would be configuring it to be able to communicate to AAA server/HSS and
EPC.
Exercise Objective
The objective of this exercise is to make sure that the user device that connects to the network is
authenticated and accounted depending on the traffic being sent. You would learn to configure
SaMOG gateway to communicate to AAA server/HSS and EPC.
Access to SaMOG gateway from SSH
Step 1: To access the SaMOG gateway associated to your POD, use any SSH client to connect
into the pod. The
SSH IP: 128.107.91.226
SSH user ID: samogX
SSH password: samogX
Step 2: Telnet to your SaMOG from the SSH session. “telnet 10.1.X.61”,
Login ID: cisco
Password: Cisco123
“X” is your POD number
SaMOG Interface Configuration Breakdown
SaMOG is connected to the following six interfaces
- Mgmt Interface (for telnet access)
- samog-S2a (GTP control interface to PGW)
- samog-STa (SaMOG Diameter interface to AAA/HSS)
- samog-SWw (PMIPv6 access interface to WLC MAG)
- samog-aaa (AAA interface to Access WLC)
- samog-egress (GTP data interface to PGW)
Interface Name Context Port Role VLAN ID Address
LOCAL1 local 1/1 Mgmt - 10.1.X.61/24
samog-S2a samog 1/10 GTPc to PGW 18X 10.8.X.61/24
samog-STa samog 1/10 Diameter to AAA 13X 10.3.X.61/24
samog-SWw samog 1/10 PMIPv6 to MAG 14X 10.4.X.61/24
samog-aaa samog 1/10 AAA to Access 12X 10.2.X.61/24
samog-egress samog 1/10 GTPu to PGW 16X 10.6.X.61/24
“X” refers to the POD you are connecting to
21. 21
SaMOG: Interface Configuration (verification)
Following configuration has already been done. Do not configure them again.
Verify the following contexts are there by using command “show context”
[local]sevt-samog0X # show context
Context Name ContextID State
------------ --------- -----
local 1 Active
samog 2 Active
Verify that the different parameters that are required in the SaMOG gateway are configured according to
your POD number X, using command “show configuration” from the CLI. Please verify various details
listed below to their corresponding context
context local
interface LOCAL1
ip address 10.1.X.61 255.255.255.0
#exit
ip route 10.1.0.0 255.255.0.0 10.1.X.1 LOCAL1
#exit
Please verify that the IP address and route is correct for your
corresponding POD
local context
22. 22
port ethernet 1/1
no shutdown
bind interface LOCAL1 local
#exit
operator-policy name opr-samog
associate call-control-profile cc-samog
apn default-apn-profile samog0X.com
apn network-identifier samog0X.com apn-profile
samog0X.com
#exit
lte-policy
subscriber-map smap
precedence 1 match-criteria all operator-
policy-name opr-samog
exit
tai-mgmt-db tai-db
tai-mgmt-obj ob1
tai mcc 222 mnc 90 tac 1234
#exit
#exit
exit
call-control-profile cc-samog
authenticate context samog aaa-group STa
local-cause-code-mapping map-cause-code
roaming-not-allowed gmm-cause-code
local-cause-code-mapping map-cause-code
unknown-subscriber gmm-cause-code
local-cause-code-mapping map-cause-code
unknown-subscriber map-diag-info gprs-
subscription-unknown gmm-cause-code
local-cause-code-mapping map-cause-code
unknown-subscriber map-diag-info imsi-unknown gmm-
cause-code
#exit
apn-profile samog0X.com
address-resolution-mode local
pgw-address 10.8.X.51
qos default-bearer qci 5
qos default-bearer arp 1 preemption-capability
may vulnerability not-preemptable
qos apn-ambr max-ul 123 max-dl 22
accounting mode gtpp
#exit
Please verify that the interface is bind to local context. Also verify if
operator policy, LTE policy, call control policy and APN profile has
been defined for the correct POD
local contextlocal context
23. 23
context samog
interface samog-S2a
ip address 10.6.X.61 255.255.255.0
#exit
interface samog-STa
ip address 10.3.X.61 255.255.255.0
#exit
interface samog-SWw
ip address 10.4.X.61 255.255.255.0
#exit
interface samog-aaa
ip address 10.2.X.61 255.255.255.0
#exit
interface samog-egress
ip address 10.8.X.61 255.255.255.0
#exit
Please verify that the IP interfaces for the respective Samog services
has been defined for each interface for your corresponding POD.
aaa group STa
radius attribute nas-ip-address address 10.2.X.61
radius dictionary custom70
diameter authentication dictionary aaa-custom13
diameter authentication endpoint STa-endpoint
diameter authentication server 0001-sessmgr.eap-
endpoint priority 1
#exit
aaa group default
radius attribute nas-ip-address address 10.2.X.61
radius dictionary custom70
diameter authentication dictionary aaa-custom13
diameter authentication endpoint STa-endpoint
diameter authentication server 0001-sessmgr.eap-
endpoint priority 1
#exit
Please verify the AAA group configuration for the access-side
(Radius) and 3gpp-core side (STa) for each of your corresponding
POD’s has been configured.
samog context
samog context
24. 24
port ethernet 1/10
no shutdown
vlan 13X
no shutdown
bind interface samog-STa samog
#exit
vlan 16X
no shutdown
bind interface samog-S2a samog
#exit
vlan 12X
no shutdown
bind interface samog-aaa samog
#exit
vlan 14X
no shutdown
bind interface samog-SWw samog
#exit
vlan 18X
no shutdown
bind interface samog-egress samog
#exit
Please verify that the each interface has been bound and tied to a
context
port verification
25. 25
SaMOG: Services Configuration (configuration)
Configure the following lines in “samog” context for the different SaMOG services
config
context samog
gtpu-service cgw-s2a-user
source-port standard
bind ipv4-address 10.6.X.61
exit
twan-profile pmip
access-type pmip
radius client 10.1.0.31 key cisco disconnect-message dest-port 3799
#exit
mrme-service mrme-sww
bind address 10.2.X.61 auth-port 1645 acct-port 1646
no dns-pgw context
associate twan-profile pmip
#exit
cgw-service cgw-sww
bind ipv4-address 10.4.X.61
associate egress-egtp-service cgw-s2a
session-delete-delay timeout 10000
timestamp-replay-protection tolerance 0
#exit
samog-service samog-gw
associate mrme-service mrme-sww
associate cgw-service cgw-sww
associate subscriber-map smap
#exit
egtp-service cgw-s2a
no gtpc echo-interval
interface-type interface-cgw-egress
associate gtpu-service cgw-s2a-user
gtpc bind ipv4-address 10.8.X.61
exit
SaMOG: Diameter endpoint Configuration
Configure the following lines to define the diameter endpoints in the “samog” context
diameter endpoint STa-endpoint
origin realm mic.com
use-proxy
origin host sta-endpoint-sevt address 10.3.X.61
no watchdog-timeout
peer 0001-sessmgr.eap-endpoint realm mic2.com address 10.3.0.253 port 3869
route-entry realm mic2.com peer STa-endpoint
#exit
26. 26
Verification of Configured SaMOG pieces:
Now all portion required for SaMOG gateway configuration is complete. The next task is to verify if the
configuration has been done correctly.
Verification of Interfaces (local):
Verify that different interfaces are all up in the local context
[local]sevt-samog0X # show ip interface summary
Interface Name Address/Mask Port Status
============================== =================== ================== ======
LOCAL1 10.1.X.61/24 1/1 untagged UP
Total interface count: 1
Verification of Interfaces (samog):
Verify that different interfaces are all up in the samog context
[samog]sevt-samog0X # context samog
[samog]sevt-samog0X # show ip interface summary
Interface Name Address/Mask Port Status
============================== =================== ================== ======
samog-S2a 10.6.X.61/24 1/10 vlan 16X UP
samog-STa 10.3.X.61/24 1/10 vlan 13X UP
samog-SWw 10.4.X.61/24 1/10 vlan 14X UP
samog-aaa 10.2.X.61/24 1/10 vlan 12X UP
samog-egress 10.8.X.61/24 1/10 vlan 18X UP
Total interface count: 5
28. 28
[samog]sevt-samog0X# show samog-service all
Service name : samog-gw
Service-Id : 4
Context : samog
Status : STARTED
Associated MRME service : mrme-sww
Associated CGW service : cgw-sww
Setup Timeout (in sec) : 60
Absolute Timeout (in sec) : 0
Idle Timeout (in sec) : 0
Max Sessions : 96000
Subscriber Map : smap
[samog]sevt-samog04# show cgw-service all
Service name : cgw-sww
Service-Id : 3
Context : samog
Status : STARTED
Bind IPv4 Address : 10.4.X.61
Bind IPv6 Address : Not configured
Egress EGTP service : cgw-s2a
QCI-QOS mapping table : n/a
Subscriber Map Name: n/a
Lifetime: 00h10m00s
Binding Revocation: Disabled
Bind-Revocation Max Retries: 1 Bind-Revocation Timeout: 1000(msecs)
Session-Delete-Delay Timer : Enabled
Session-Delete-Delay timeout : 10000(msecs)
Timestamp Replay Protection: Enabled Timestamp Tolerance: 0 sec
Timestamp Option Validation: Disabled
[samog]sevt-samog04# show egtp-service all
Service name : cgw-s2a
Service-Id : 5
Context : samog
Interface Type : cgw-egress
Status : STARTED
Restart Counter : 25
Message Validation Mode : Standard
GTPU-Context : samog
GTPC Retransmission Timeout : 5
GTPC Maximum Request Retransmissions : 4
GTPC IP QOS DSCP value : 10
GTPC Echo : Disabled
GTP-C Bind IPv4 Address : 10.8.X.61
GTP-C Bind IPv6 Address : Not configured
[samog]sevt-samog04# show mrme-service all
Service name : mrme-sww
Service-Id : 2
29. 29
Context : samog
Status : STARTED
Bind IPv4 Address : 10.2.X.61
Authentication Port : 1645
Accounting Port : 1646
Radius Client List
1) IPv4 Address : 192.168.241.31
Dynamic Authorization : ENABLED
DM Dest-port : 3802
Disconnection Wait Time (in sec) : 30
Disconnection Delay Time (in sec) : 10
DNS-PGW
Context : samog
Selection : Weight
Associated SaMOG service : samog-gw
MRME operating mode : SaMOG
FQDN : N/A
STa Attributes
ANID : WLAN String
Calling Station Id : IMSI
Verification SaMOG Diameter setting:
Verify that Diameter settings are correct and the diameter peers are all up
[samog]sevt-samog0X# show diameter peers full all
-------------------------------------------------------------------------------
Context: samog Endpoint: STa-endpoint
-------------------------------------------------------------------------------
Peer Hostname: 0001-sessmgr.eap-endpoint
Local Hostname: 0001-diamproxy.sta-endpoint-sevt
Peer Realm: mic2.com
Local Realm: mic.com
Peer Address: 10.3.0.253:3869
Local Address: 10.3.X.61:33122
State: OPEN [TCP]
CPU: 1/0 Task: diamproxy-1
Messages Out/Queued: N/A
Supported Vendor IDs: 10415
Admin Status: Enable
DPR Disconnect: N/A
Peer Backoff Timer running:N/A
Peers Summary:
Peers in OPEN state: 1
Peers in CLOSED state: 0
Peers in intermediate state: 0
Total peers matching specified criteria: 1
30. 30
The SaMOG gateway configuration has now been complete and the client is now ready to
connect using the SaMOG gateway into the EPC
31. 31
Verification SaMOG Session
PMIPv6 Session Creation
Connect your client into the SSID corresponding to your POD. (samog0X)
Connect using an EAP-AKA profile
32. 32
Verification: Client’s IP address
Verify if the IP address assigned to the device is within the client pool range that has been assigned to it
Browse to the web portal http://10.3.0.200 for final confirmation of fully operational end-
to-end control and data-path.
Conclusion
After this training you should have a good understanding of the different configuration pieces that combine
together – UE, AP, WLC, SaMOG and PGW on ASR5000 to provide a full quality of experience for the user.
