0% found this document useful (0 votes)
481 views

Set LGW Mode On eNB

Uploaded by

Ruben Cheng
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
481 views

Set LGW Mode On eNB

Uploaded by

Ruben Cheng
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

Set LGW Mode on eNB

BaiBS_RTS_3.7.5
BaiBS_RTD_3.7.5
BaiBS_QRTB_2.5.4

March 2021

Version 1.6
About This Document
This document provides guidance for configuring the local gateway (LGW) mode on a Baicells eNodeB (eNB).
The information is intended for installers and network administrators responsible for configuring the eNB
network interfaces. This document is based on eNB software versions BaiBS_RTS_3.7.5, BaiBS_RTD_3.7.5,
and BaiBS_QRTB_2.5.4.

Terms used in this document or related to LTE are listed in alphabetical order and described in
Acronyms & Abbreviations, which can be found at Baicells > Support > Documents.

Copyright Notice
Baicells Technologies, Inc., copyrights the information in this document. No part of this document may be
reproduced in any form or means without the prior written consent of Baicells Technologies, Inc. The
Baicells logo is a proprietary trademark of Baicells Technologies, Inc. Other trademarks mentioned in this
document belong to their owners.

Disclaimer
All products, services, and features bought from Baicells Technologies, Inc., are subject to the constraints
of the company's business contract and terms. All or part of the products, services, or features described
in this document might not be your specific Baicells network. Unless stated in the contract, Baicells
Technologies, Inc., does not make any explicit or default statement or guarantee about the contents of this
document.

Unless stated otherwise, this document serves only as a user guide, and all descriptions/ information/
suggestions mean no guarantee, neither explicit nor implicit.

The information in this document is subject to change at any time without notice. For more information,
please consult with a Baicells technical engineer or the support team.

Revision Record
Date Version Description SMEs/Contributors Author/Editor

25-Mar-2021 V1.6 Updated for BaiBS_RTS_3.7.5, Nitisha Potti Kathy Clark


BaiBS_RTD_3.7.5, and
BaiBS_QRTB_2.5.4

12-Nov-2020 V1.5 Updated for BaiBS_RTS_3.6.6 Nitisha Potti Kathy Clark

28-Feb-2020 V1.4 New logo & colors Chris Culver Sharon Redfoot

17-Dec-2019 V1.3 Updated for RTS 3.4.8, new PLMN Nitisha Potti Sharon Redfoot

2-Mar-2018 V1.2 Updated preface Cameron Kilton Sharon Redfoot

18-Dec-2017 V1.1 Draft-2 Nitisha Potti Sharon Redfoot

1-May-2017 V1.0 Draft-1 Panda Xie

ii
Support Resources
• Documentation - Baicells product data sheets, this document, and other technical manuals may
be found at Baicells > Support > Documents.

• Support - How to open a support ticket, process an RMA, and the Support Forum are at Baicells >
Support.

Contact Us
Baicells Technologies Co., Ltd. Baicells Technologies North America, Inc.
China North America
Address: 3F, Bldg. A, No. 1 Kai Tuo Rd, Haidian Dist, Address: 5700 Tennyson Pkwy, #300, Plano, TX
Beijing, China 75024, USA

Phone: +86-10-62607100 Phone: +1-888-502-5585

Email: [email protected] or
E-mail: [email protected]
[email protected]

Website: www.Baicells.com Website: https://na.Baicells.com

iii
Table of Contents
1. OVERVIEW ................................................................................................................................................. 1

2. NAT MODE ................................................................................................................................................. 1

2.1 DESCRIPTION ......................................................................................................................................... 1

2.2 CONFIGURATION .................................................................................................................................... 3

3. ROUTER MODE .......................................................................................................................................... 4

3.1 DESCRIPTION ......................................................................................................................................... 4

3.2 CONFIGURATION .................................................................................................................................... 5

4. BRIDGE MODE ........................................................................................................................................... 7

4.1 DESCRIPTION ......................................................................................................................................... 7

4.2 CONFIGURATION .................................................................................................................................... 8

List of Figures
FIGURE 2-1: NAT MODE PROCESS .............................................................................................................................. 1

FIGURE 2-2: ICMP PING .......................................................................................................................................... 2

FIGURE 2-3: BAICELLS NAT MODE EXAMPLE................................................................................................................. 3

FIGURE 2-4: CONFIGURE LGW = NAT ......................................................................................................................... 4

FIGURE 3-1: ROUTER PROCESS ................................................................................................................................... 4

FIGURE 3-2: BAICELLS ROUTER MODE EXAMPLE ............................................................................................................ 5

FIGURE 3-3: CONFIGURE LGW = ROUTER .................................................................................................................... 6

FIGURE 4-1: LAYER 2 BRIDGE MODE PROCESS ............................................................................................................... 7

FIGURE 4-2: BAICELLS BRIDGE MODE EXAMPLE ............................................................................................................. 8

FIGURE 4-3: CONFIGURE LGW = BRIDGE ..................................................................................................................... 8

List of Tables
Table 3-1: LGW = Router Configuration Settings

iv
1. Overview
When using the Baicells CloudCore to provide LTE Evolved Packet Core (EPC) network functions, you need
to configure the local gateway (LGW) mode in the eNodeB (eNB). The eNB splits the data plane and the
control plane, so there are two IP addresses per user equipment (UE)/Customer Premise Equipment (CPE).
The data plane is sent out the local gateway, while the control plane is routed through an IPSec tunnel to
the CloudCore EPC.

Most manufacturers do not split the two planes, and all traffic is sent through a hardware EPC. You have
that option with Baicells as well, but operators using the Baicells CloudCore EPC use LGW. You can choose
one of three LGW configurations in the eNB GUI:

• Network Address Translation (NAT) mode


• Router mode
• Bridge mode (most commonly used)

The remainder of this document explains each mode and the configuration fields.

NOTE: Whenever you change the LGW mode, you must reboot the eNB for the new settings
to take effect. Rebooting the eNB will interrupt service temporarily.

2. NAT Mode

2.1 Description
Network Address Translation (NAT) is a method of remapping one IP address into another by modifying the
network address information in the IP header of packets while they are in transit across the traffic routing
device. In NAT mode, the eNB uses Source Network Address Transfer (SNAT) and changes the CPE’s IP
address to the eNB’s WAN IP address (Figure 2-1).

Figure 2-1: NAT Mode Process

1
To remotely access a CPE, you would enter https://<IP address> <port>:
36T 36T

• IP Address = eNB IP address


• Port = 5xxxx, where xxxx = last 4 digits of the CPE’s IMSI

By default, the CPE’s Web GUI HTTPS port is 433. Do not change the port number.

Using LGW = NAT, an Internet Control Message Protocol (ICMP) ping from the CPE will flow as shown in
Figure 2-2.

Figure 2-2: ICMP Ping

An example NAT setup for a Baicells system is illustrated in Figure 2-3.

2
Figure 2-3: Baicells NAT Mode Example

2.2 Configuration
To configure LGW mode = NAT (Figure 2-4):
1. Log in to the eNB GUI by going to http://192.168.150.1.

2. Go to Network > LGW.

3. Enable the LGW feature.

4. Select NAT as the LGW Mode.

5. Set the Interface Binding to WAN (Wide Area Network). Use the same WAN interface you
configured in Network > WAN/LAN/VLAN. The default value is WAN.

6. Enter the IP Pool and Netmask. The IP binding range is 10.10.0.1 to 10.10.0.254.

7. Save.

3
Figure 2-4: Configure LGW = NAT

3. Router Mode

3.1 Description
The LGW Router mode enables you to configure a static route entry in the external router connected to the
eNB in order to access the LGW subnet. The interface that the LGW uses to offload data is the eNB's WAN
interface defined under Network > WAN/LAN/VLAN, e.g., WAN.

When the CPE attaches, the LGW will assign a local IP address from an IP pool (and netmask) that you
configure. Figure 3-1 illustrates the LGW = Router process.

Figure 3-1: Router Process

An example Router setup for a Baicells system is illustrated in Figure 3-2.


NOTE: The yellow highlights denote the differences between Router and NAT mode.

4
Figure 3-2: Baicells Router Mode Example

3.2 Configuration
To configure LGW mode = Router (Figure 3-3):

1. Log in to the eNB GUI by going to http://192.168.150.1.


2. Go to Network > LGW.
3. Enable the LGW feature.
4. Select Router as the LGW Mode.
5. Set the Interface Binding to WAN (Wide Area Network). Use the same WAN interface you
configured in Network > WAN/LAN/VLAN. The default value is WAN.
6. Enter the IP Pool and Netmask. The IP binding range is 10.10.0.1 to 10.10.0.254.
7. Optional: Enable Static Address, and identify the range of IP addresses available by entering the
first and last IP addresses.
8. Optional: You can bind a static IP to a CPE IMSI. For additional details, refer to Table 3-1.
9. Save.

5
Figure 3-3: Configure LGW = Router

Table 3-1: LGW = Router Configuration Settings

Field Name Description

LGW Enable

LGW Mode Router

LGW Interface Binding The interface that the LGW uses to offload data. Should be set to the
WAN interface of the eNB. The default value is eth2.

LGW IP Pool When the CPE attaches, the LGW will assign a local IP address to the
CPE from this IP pool. The first IP address of a subnet is 10.10.0.1.
LGW IP Pool Netmask This is the LGW IP Pool netmask. The default value is 255.255.255.0. If
you add 10.10.0.1 and 255.255.255.0, there will be 255 IP addresses in
the pool, from 10.10.0.1 to 10.10.0.255.

Static Address Used to configure a static address. If enabled, the next 2 fields display.

Configure Static Address Configure the first and last static address in the range that may be
Range used. All static IMSI to IP binding addresses must be set within this
range. Otherwise, there will be a Web page error.

IMSI to IP Binding You can bind a local IP address with an IMSI here. Input the IMSI and IP
address, and then click on the + (Add) icon. You will see that a new
record has been added. After binding the IMSI and IP address, when
this CPE/IMSI attaches it will always get the specific IP address that was
added.

6
4. Bridge Mode

4.1 Description
In Layer 2 Bridge mode, the eNB creates a virtual interface for every CPE that attaches. Each virtual interface
makes a DHCP request and creates a 1:1 mapping between the CPE IP (from the CloudCore EPC) and the
LGW IP. Most operators use bridge mode. Figure 4-1 illustrates the LGW = Bridge process.

With Layer 2 bridging, the CPE’s MAC address is generated from its SIM card's IMSI number. To calculate
the CPE MAC address:

1. Convert the last 12 digits of the IMSI number to hex.


2. Prefix the hex number with 8A.
Example:
• If IMSI = 117040000002918
• MAC address = 8A:95:02:F9:B6:6

Once you know the MAC address, you can provision your network accordingly. There are a number of free
hex conversion calculators online.

Figure 4-1: Layer 2 Bridge Mode Process

An example Bridge setup for a Baicells system is illustrated in Figure 4-2.

7
NOTE: The yellow highlights denote the differences between Bridge and Router mode.

Figure 4-2: Baicells Bridge Mode Example

4.2 Configuration
To configure Bridge mode, simply select Bridge as the LGW mode and select WAN (Wide Area Network) as
the interface binding (Figure 4-3). Use the same WAN interface you configured in Network >
WAN/LAN/VLAN. The default value is WAN.

Figure 4-3: Configure LGW = Bridge

You might also like