22
5.
Verify the core network connection between the eNB and the Mobility Management
Entity (MME) in the Baicells CloudCore. Go to Network > MME/IPSec Binding (Figure
3-18). Do not change the
IPSec Setting
fields. They should be left with their default
values. In the
IPSec Tunnel List
, verify there are 2 tunnels enabled. The
IPSec Binding
should show the 2 CloudCore MME IP addresses, 10.3.0.9 and 10.5.0.9.
Figure 3-18: MME&IPSec Binding
6.
Configure the eNB's local gateway (LGW) connection to the backhaul network. The eNB splits
the data plane and control plane. The data plane is sent out the LGW path, while the control
plane is routed through the IPSec tunnel to the CloudCore EPC.
a.
Go to the Network > LGW menu (Figure 3-19). LGW should be enabled.
b.
Select one of 3 LGW modes:
i.
NAT - Network Address Translation modifies the network address in the IP
packet headers. To reach a CPE remotely, enter:
https://<eNB IP address><5+last 4 digits of CPE IMSI>
Leave the CPE Web GUI https port as 433; do not change the port number. IP
binding uses address range 10.10.0.1 to 10.10.0.254.
ii.
Router - Enable static IP addressing, and identify the range of addresses. The
LGW will assign a local IP address when a CPE attaches. IP binding uses
address range 10.10.0.1 to 10.10.0.254.
iii.
Bridge - Layer 2 will create a virtual interface for each CPE that attaches
using a DHCP request to create a 1:1 mapping between the CPE IP address
(from the EPC) and the LGW IP addresss. A CPE's MAC address is generated
from its IMSI: Convert the last 12 digits to hex, and then prefix it with "8A".
For example, if the IMSI = 311980000002918, the MAC would be
8A:E4:2C:8D:53:66.
