Running Multiple eNB
The purpose of this tutorial is to show you how to run multiple MME and let multiple eNB get connected to different MME.
(
- Test Setup
- Configuration
- Configuration File Setup
- Configuration for eNB0
- Configuration for eNB1
- Configuration for MME0
- Configuration for MME1
- Configuration for IMS0
- Configuration for IMS1
- Configuration for OTS
- Perform the test
- Log Analysis
Test Setup
In this setup, two instances of eNB/MME/IMS are running in the callbox. All the components will launch automatically by lte service and all the components will be automatically added to 'screen' window as well.
Configuration
Configuration File Setup
I used enb.default0.cfg and enb.default1.cfg which are copied from enb.default.cfg (These configuration files are located in /root/enb/config). Note that enb0.cfg and enb1.cfg are symbolically linked to enb.default.0.cfg and enb.default1.cfg respectively. (These configuration files are located in /root/mme/config).
I used two separate mme configuration files : mme-ims-2enb-0.cfg and mme-ims-2enb-1.cfg which are copied and modified from mme-ims.cfg. Note that mme0.cfg and mme1.cfg are symbolically linked to mme-ims-enb-0.cfg and mme-ims-enb-1.cfg respectively. (These configuration files are located in /root/mme/config).
I used two separate ims configuration files : mme.default.0.cfg and mme.default1.cfg which are copied and modified from ims.default.cfg. Note that ims0.cfg and ims1.cfg are symbolically linked to ims.default0.cfg and ims.default1.cfg respectively. (These configuration files are located in /root/mme/config).
I used ots-2enb-2mme.cfg which is copied and modiefied from ots.default.cfg (These configuration files are located in /root/ots/config).
Configuration for eNB 0
In enb.default0.cfg , I made modifications as follows. Note that this is exactly same as enb.default.cfg.
Configuration for eNB 1
In enb.default1.cfg , I made modifications as follows. Note that this is exactly same as enb.default.cfg.
Configuration for MME 0
Followings are the configuration in mme.default.0.cfg
Configuration for MME 1
Followings are the configuration in mme.default.1.cfg. NOTE that this MME has configured for the PLMN 00102 and use the gtp_addr which is different from MME 0.
Configuration for IMS 0
Followings are the configuration in ims.default0.cfg
Configuration for IMS 1
Followings are the configuration in ims.default1.cfg
Configuration for OTS
Followings are the configuration in ots-2enb-2mme.cfg
Perform the test
In this test, I would just run a lte service with additional enb, mme and ims. I would not try any UE attach. In this test, all the eNB,mme and ims are run automtically by lte service.
If you run lte service and get into screen mode, you will see a new components (enb1,mme1,ims1) are added as below. This addition is done by the configuration in ots.cfg as indicated below.
Now check out the network interface while the service is running and you will see many tun interfaces are created as shown below.
these are the tun interface created by mme0.cfg
these are the tun interface created by mme1.cfg
Followings are the ipv4 routing table created by the operating system and lte service.
Followings are the ipv6 routing table created by the operating system and lte service.
Now go back to lte service screen and check follows.
Check on the cell configuration of ENB0 as shown below.
Check on the mme (s1) that is connected to ENB0
Check on the cell configuration of ENB1 as shown below.
Check on the mme (s1) that is connected to ENB1
Go to MME (mme0) and check out the connected enb.
Go to MME (mme0) and check out the connected ims.
Go to MME (mme1) and check out the connected enb.
Go to MME (mme1) and check out the connected ims.
Go to MME (ims0) and check out the connected mme.
Go to MME (ims1) and check out the connected mme.
Log Analysis
If you run WebGUI, you would notice that a new components (ENB1,MME1,IMS1) are added as shown below.
Followings are some of highlighted steps you may want to check.
