Aricent EPCLite Startup and Auto-configuration Utility v1.

13

Aricent EPCLite StartUp and Auto-Configuration Utility

This note captures the procedure for startup and auto-configuration of EPCLite setup.

1 Purpose
This utility is used for installation & auto-configuration of all EPC nodes for
the mandatory configuration required to bring up EPC nodes for EPC
Release 2.1.2.18

2 EPCLite Dependencies
No.

Package Description

1
2
3
4
5
6

Linux kernel version 2.6.18-164

GNU bash, version 3.2.25
GCC version 4.1.2
GNU Make version 3.81
Python version 2.4.3
MOD Python version 3.2.8-3.1
Mod SSL version 2.2.3-3.1 (Optional- required for
https support)
MySQL Database
MySQL Database Development Version
Apache version 2.2.3
Sqlite3 Database v3.6.23.1
Mozilla Firefox version 3.0.12 for Linux machine
Firefox version 3.6.8/3.6.9 for Windows machine
NetSNMP 5.3.2.2 for SNMP support
Perl v5.8.8 for SNMP support
perl-Net-IP-1.25-2
RPM v4.4.2.3
RPM Build 4.4.2.3
Tar GNU tar 1.15.1
Gzip 1.3.5
ncurses-5.5-24
elf utils
sensors
HTTP server 2.2.3-45
Syslog

7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

Package Name
bash
gcc
make
python
mod_python
mod_ssl
mysql
mysql-devel
httpd
sqlite3
firefox
net-snmp
perl
perl-Net-IP
rpm
rpm-build
tar
gzip
ncurses-devel
elfutils
lm_sensors
httpd
sysklogd

ARICENT COPYRIGHT, 2013

All rights reserved. This publication and its contents are proprietary to Aricent Inc.

Aricent EPCLite Startup and Auto-configuration Utility v1.13

26
27

Expect 5.43
cpio-2.6

expect
cpio

3 Prerequisites
1. All dependencies of Aricent EPClite software are available on target
machine.
2. Quick Install utility should be executed on the same machine on which
the EPC nodes are to be installed.
3. Linux package Expect should be installed at /usr/bin/
4. Linux package bash should be present at /bin/bash
5. root privilege is required to run this utility.
6. EMS IP address should be configured on target machine.
7. The swap memory of the server should be double the RAM size
(recommended)
8. The physical IP address of Nodes must be pre-configured on server (in
case of HA)

4 Usage
4.1) NON-HA Installation
1. Untar the <QuickInstall*.tar.gz >file.
2. Change parameters in <config_epc.cfg> as per setup.
(Please note that this file contains only sample configuration).
3. Place all RPMs at ./QuickInstall/RPM/
4. Place all License files in ./QuickInstall/LICENSE/
5. Execute epc_install binary as:
./epc_install
a. Select Option 1 for complete EPC node installation
b. Select Options 2-7 for Node Patch Installation.
c. Select Option 8 to Quit

4.2) HA Installation
1. Untar the <QuickInstall*.tar.gz >file.
2. Change parameters in <config_epc.cfg> as per setup
3. Change parameters in <config_epc_ha.cfg > as per setup

ARICENT COPYRIGHT, 2013

All rights reserved. This publication and its contents are proprietary to Aricent Inc.

Aricent EPCLite Startup and Auto-configuration Utility v1.13

4. Place all RPMs at ./QuickInstall/RPM/

5. Place all License files in ./QuickInstall/LICENSE/
6. Execute epc_ha_install binary as:
./epc_ha_install
a. Select Option 1 for complete EPC node installation on ActiveMode server
b. Select Options 3-8 for Node Patch Installation.
c.

Select Option 9 to Quit

After installation of the EPC software on this server, a success message

is displayed.
For the standby (mate) machine, copy the same QuickInstall Utility and
select Option 2 (Fresh Installation on Standby Node) in the command line
of epc_ha_install script.
7. Start the services on mate system using the command:
startepc

5 Successful Installation
Once the utility completes the configuration of EPC nodes, you may check the
running status of each node via the following commands:

service ems status

service epgw status

service esgw status

service hss status

service mme status

The administrator can now view the configuration and EPC node status using the
EMS by following the steps:

1. Input the EMS IP address in the address URL on the internet browser
2. Login to the EMS using the default administrator credentials (login:
admin; password: admin)
System is now installed, setup and configured. The EPC can now start its function.

ARICENT COPYRIGHT, 2013

All rights reserved. This publication and its contents are proprietary to Aricent Inc.

Aricent EPCLite Startup and Auto-configuration Utility v1.13

6 PCRF Installation
6.1 Prerequisites
1. EMS, HSS and PGW nodes must be installed, configured and running.

6.2 Usage
6.2.1) Non-HA Installation
1. Change parameters in <config_pcrf.cfg> as per setup
2. Place PCRF RPM at ./QuickInstall/RPM/
3. Place PCRF License files at ./QuickInstall/LICENSE/
4. Execute pcrf_install binary as:
./pcrf_install

6.2.2) HA Installation
1. Change parameters in <config_pcrf_ha.cfg > as per setup
2. Place PCRF License files at ./QuickInstall/LICENSE/
4. Execute pcrf_ha_install binary as:
./pcrf_ha_install
After installation of HA a success message is displayed
5. For standby/mate machine, run epc_ha_install script and select
Option 2 Fresh Installation StandbyMode. It will ask for pcrf install also
on SM machine. Give the input as y for pcrf installation
6. Start the PCRF service on mate system as service pcrf start

6.3 Successful Installation

Once the utility completes the configuration of PCRF node, you may check the
running status of pcrf node using the following command:
service pcrf status

7 Subscriber Management
The QuickInstall Utility creates a default EMS user with credentials: (login:
hssuser; password: hssuser). This login may be used to individually view, modify
or add subscribers & their subscription data.

ARICENT COPYRIGHT, 2013

All rights reserved. This publication and its contents are proprietary to Aricent Inc.

Aricent EPCLite Startup and Auto-configuration Utility v1.13

8 EPC Nodes Start-up & Stop Commands

8.1 EPC restart
The QuickInstall Utility installs two scripts at the /sbin/ directory. These scripts
namely, startepc and stopepc, can be used to start and stop all EPC services at
once.
By default, the QuickInstall utility will update the Linux server start-up
configuration (file: /etc/rc.d/rc.local) so that the EPC services come up
automatically on reboot of EPC server.

8.2 EPC individual node restart

Individual node may be restarted using the following commands:
service mme restart
service esgw restart
service epgw restart
service edataplane restart
service hss restart
service ems restart

Note that in case of combined Datapath (co-located SGW and PGW); the services SGW, PGW
and Dataplane need to be restarted:
service esgw stop
service epgw stop
service edataplane stop
service esgw start
service epgw start
service edataplane start

Please note that the EPC services can also be restarted using the EMS GUI.

ARICENT COPYRIGHT, 2013

All rights reserved. This publication and its contents are proprietary to Aricent Inc.

Aricent EPCLite Startup and Auto-configuration Utility v1.13

9 Advanced Debugging
9.1 Failure in Installation
In case the QuickInstall Utility fails to install the EPC packages, log file placed at path
QuickInstall/install_log.txt will guide to the exact failure cause.
For HA failure use QuickInstall/install_ha_log.txt to find cause of exact failure

9.2 Node Failure

In case any of the EPC nodes go down (or doesnt come up), then please check logs files for license
expiry as one of the causes.

EMS:

/var/EMS/ems.log

HSS:

/var/log/HSS.log

MME:

/opt/lte/mme/log/mme.log

SGW: /opt/lte/esgw/log/esgw.log
PGW: /opt/lte/epgw/log/epgw.log
PCRF: /opt/lte/pcrf/log/pcrf.log

9.3 Configuration File

9.3.1 Format
Please ensure that no blank lines, whitespaces or tabs are inserted in the configuration file
(config_epc.cfg/ config_epc_ha.cfg/config_pcrf.cfg/ config_pcrf_ha.cfg) at the time of editing.
Also note that any deviation from the standard template of configuration file may result in malfunction of
QuickInstall utility.

9.3.2 Description
9.3.2.1 Configuration file for redundancy disabled (config_epc.cfg)
MCC, MNC:
These fields abbreviate the Mobile Country Code (MCC) & Mobile Network Code (MNC).
Combination of MCC and MNC is called the PLMN and this configuration should be the same as that
configured on the eNodeBs connected to MME.
TAC1:

ARICENT COPYRIGHT, 2013

All rights reserved. This publication and its contents are proprietary to Aricent Inc.

Aricent EPCLite Startup and Auto-configuration Utility v1.13

This field abbreviates the Tracking Area Code. This should be the same as that configured on the
eNodeB.
MME_IP:
This field represents the MME IP towards eNodeB (S1 interface), HSS (S6a interface) and SGW (S11
interface).
This IP also represents the floating IP of MME in case of HA setup.
HSS_IP:
This is the protocol IP of HSS to interface with MME and PCRF.
This IP also represents the floating IP of HSS in case of HA setup.
SGW_IP:
This is the protocol IP of the SGW to interface with MME and PGW.
This IP also represents the floating IP of SGW in case of HA setup.
PGW_IP:
This is the protocol IP of the PGW to interface with SGW and PCRF.
This IP also represents the floating IP of PGW in case of HA setup.
In case of redundancy disabled (non-HA setup), this IP shall interface with eNodeB for transfer of user
data traffic (GTP tunneling).
PGW_IP_FROM_PDN_INTF:
This is the IP exposed towards PDN interface for UE data packets in the Downlink direction.
S1_ETH:
The interface which connects eNodeB with MME.
PDN_ETH:
The interface which connects PDN network with PGW.
EMS_IP:
The IP address of the EPC server machine on which EMS is intended to run.
MAX_SUBSCRIBERS
This value represents the max value of subscribers for the default HSS Group.
APN:
The default APN that will be configured on EPC nodes. This must be the same as that configured on the
UE.
GW_IP:
This represents the default GW IP to which the PGW will send UE packets in the Uplink direction.
UE_IP_RANGE_START, UE_IP_RANGE_END:
This represents the range of IPs that will be allocation to UEs by the PGW (dynamic allocation).
IMSI, K, OP:
This represents the IMSI and associated Authentication Key (Ki) and Operator Value (OP) of USIM.
Please note that these values need to be entered encrypted using HSS Key-Encryptor Tool.
QCI:
QCI represents the QCI of the default bearer.

ARICENT COPYRIGHT, 2013

All rights reserved. This publication and its contents are proprietary to Aricent Inc.

Aricent EPCLite Startup and Auto-configuration Utility v1.13

9.3.2.2 Configuration file for redundancy enabled (config_epc_ha.cfg)

Kindly configure the config_epc_ha.cfg in addition to the configuration file config_epc.cfg

<Node-Name>_HA_MULTICAST_IP:
IP address used by HAF (High Availability Framework) for communication between peer nodes.
<Node-Name>_HA_MULTICAST_PORT:
Port used by HAF (High Availability Framework) for communication between peer nodes.
<Node-Name>_NODE<Number>_IP:
This is the Physical IP of Node. This IP is used to transfer periodic and bulk updates between peer
nodes. This IP must be pre-configured on node and should be different from the floating (protocol) IP of
each node.
Please note the floating IPs are defined in config_epc.cfg.
SGW_GTPU_IP:
This is the GTP-User IP of SGW node visible to eNodeB for transport of UE traffic on GTP tunnels.
This IP must be different from the GTP Control port of SGW or PGW.
PGW_GTPU_IP:
This is the GTP-User IP of PGW node visible to SGW for transport of UE traffic on GTP tunnels.
This IP must be different from the GTP Control port of SGW or PGW.

ARICENT COPYRIGHT, 2013

All rights reserved. This publication and its contents are proprietary to Aricent Inc.

Aricent EPCLite Startup and Auto-configuration Utility v1.13

9.3.2.3 HTTP Recommendations

There are some customization recommendations for HTTP server on Linux. Kindly follow them in case
you face issue memory issue with HTTP.

1. Take backup of existing httpd.conf configuration file placed at path /etc/httpd/conf/.

Edit the http configuration file to load only the following modules:
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule mime_module modules/mod_mime.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
LoadModule alias_module modules/mod_alias.so
LoadModule cgi_module modules/mod_cgi.so

Comment the remaining modules in the HTTP configuration file:

Example:
#LoadModule auth_digest_module modules

2. Edit the ems.conf file placed at path /etc/httpd/conf.d/ems.conf to stop https redirection:
Comment the following line: #Redirect permanent https://xx.xx.xx.xx/

Please note that after the above mentioned changes, EMS will be accessible using the http:// option in
browser (instead of https://)

ARICENT COPYRIGHT, 2013

All rights reserved. This publication and its contents are proprietary to Aricent Inc.

Aricent EPCLite Startup and Auto-configuration Utility v1.13

Revision History

Revision No.

1.11

Date

5-August-2013

1.12

29-September-2013

1.13

24-December-2013

Description of Change

1. Enhanced to function with EPC 2.1.2.14

2. Enhanced to patch-upgrade previous EPC
2.1.2.x releases to EPC 2.1.2.14
3. Documentation updated for HTTP
customizations
1. Enhanced to function with EPC 2.1.2.15
1. Patch upgrade functions
release 2.1.2.18

ARICENT COPYRIGHT, 2013

All rights reserved. This publication and its contents are proprietary to Aricent Inc.

updated

for