Virtual Evolved Packet Core User Manual
Note 1: The IP address for the APN interface must to be from the same subnet as the IP pool of the APN. Default GW of the OS should be on the APN subnet (ex. 10.0.31.1). Default GW (ex. 10.0.31.1) needs to be configured on the border router used by UE to access Core Network/Internet. 1.1. Scripts for network interfaces (VLAN or without VLAN) This is an example of interface configuration for MME with VLAN. [root@epc]# cat /etc/sysconfig/network-scripts/ifcfg-eth0.11:mme DEVICE=eth0.11:MME TYPE=Ethernet ONBOOT=yes NM_CONTROLLED=no BOOTPROTO=none IPADDR=192.168.11.106 NETMASK=255.255.255.0 VLAN=yes [root@epc]# cat /etc/sysconfig/network-scripts/ifcfg-eth0.32:apn DEVICE=eth0.32:APN TYPE=Ethernet ONBOOT=yes NM_CONTROLLED=no BOOTPROTO=none IPADDR=10.0.31.2 NETMASK=255.255.255.192 GATEWAY=10.0.31.65 DEFROUTE=yes This is an example without VLAN: [root@epc]# cat /etc/sysconfig/network-scripts/ifcfg-eth0:mme DEVICE=eth0:MME TYPE=Ethernet ONBOOT=yes NM_CONTROLLED=no BOOTPROTO=none IPADDR=192.168.11.106 NETMASK=255.255.255.0
Note 2Each enodeb tac must be added and mapped to the SCW gtpc interface Ex for TAC 43: unhide Vendor set MME ENodeB tai-list 43 sgw-pool-id 1 neighbor-tac 11 set MME serving-gateway-pool 1 sgw-ip-address 192.168.11.107 supported-tac-list 43 2. Configuration step by step The following parameters are mandatory and it needs to be configured under configuration mode, prompt %. MME IP address set MME ENodeB self-ip-address 192.168.11.106 SGWC IP configuration set sgw gtpc ip-address 192.168.11.107 SGWU IP configuration set sgw gtpu ip-address 192.168.11.113 PGWC IP configuration set pgw gtpc ip-address 192.168.11.108 PGWU IP configuration set pgw gtpu ip-address 192.168.11.109 APN IP pool configuration set pgw apn internet ipv4-pool-start-address 10.0.31.40 ipv4-pool-netmask 255.255.255.0 Note 3: The PGW automatically calculates the available hosts based on the start address and the netmask. For this case only 215 (254-39) hosts will be available. PLMN ID configuration set General general plmnid 001001 New UE configuration set MME ueentry-list 001001000007180 authentication-key 0CE14E65809F20886BB7FAD489460E56 op-oropc 71EA16407A3EFB8639FAECF9149229C8 ue-ambr-dl 80000000 ue-ambr-ul 8000000 apn internet pgw-ipaddress-type IPv4Address pgw-ip-address 10.50.1.118 qos-profile 6 The rest of the UE parameters are using default values: apn=internet.. Note 4: The pgw-ip-address needs to be equal with PGWC IP address
Defining SGW ip address into the serving gateway pool unhide Vendor set MME serving-gateway-pool 1 sgw-ip-address 192.168.11.107 In case you use other values than 1 for TAC MME-S6A IP configuration unhide Vendor set MME s6a-app ip-address 192.168.11.111 set MME mme ip-address 192.168.11.111 3. Other configuration 3.1. QCI configuration By default qos-profile 1 with QCI 6 is configured for all the UEs it other is not specified. In order to add another qos profile go into configuration mode and add it using the following command. prompt% set MME qos-profile-list 2 qci 8 In order to attach it to an IMSI: prompt% set MME ueentry-list 001010000001090 qos-profile 2 To view the settings for dscp-qci-mapping, execute: prompt>show configuration pgw dscp-qci-mapping qci0-9 Update dscp-qci-mapping: prompt% set pgw dscp-qci-mapping qci0 44 3.2. Static IP Configuration Define an APN with IP allocation type Static set pgw apn StaticIP ip-allocation-type Static ipv4-pool-start-address 10.0.40.40 ipv4-pool-netmask 255.255.255.0 Define UE with attached to this APN and the desired ip: set MME ueentry-list 001010000001090 apn StaticIP pdn-address-allocation 10.0.40.40
4. Normal operation 4.1. Start/Stop/Status Under the installation directory perform the following commands Start epc:./epc start Stop EPC:./epc stop Check status:./epc status 4.2. CLI access In order to check/modify configuration, run: confd_cli or /ConfD_Install_Dir/bin/confd_cli The CLI can be opened through SSH connection on port 2024 and any ip address of the EPC login (admin/admin) 4.3. Maintenance Commands show MME_APP_STATS show MME_APP_STATS MME_APP_STATS NumAttachedIMSI 1 MME_APP_STATS NumActiveIMSI 1 MME_APP_STATS NumBearer 1 MME_APP_STATS NumGBRBearer 0 MME_APP_STATS NumS1HO 0 IMSI IDX IMSIVAL ----------------------- 1 001001000002520 E NBIDX E NBID ---------------- 1 0110000 show PGW_APP_STATS > show PGW_APP_STATS PGW_APP_STATS NumBearer 1 PGW_APP_STATS NumPeerSGW 1 PGW_APP_STATS NumAPN 1 PGW_APP_STATS NumGtpPeerRecovery 0 PGW_APP_STATS NumGtpPathFailure 0 PGW ALLOCATED
UEIDX UE IP ADDR ---------------------- 1 192.168.60.30 5. Observations 5.1. General Any change/updated to the configuration except adding new UE entries, implies epc restart. The application logs are dumped into the system logs (/var/log/messages) The console logs are dumped into folder log from the EPC_install_Dir In order to enable logs for a specific application use the log-level parameter under each of the module. Ex: MME logs: set MME mme log-level LogInfo MME s6a: set MME s6a-app log-level LogInfo SGW gtpc: set sgw gtpc log-level LogInfo SGW gtpu: set sgw gtpu log-level LogInfo PGW gtpc: set pgw gtpc log-level LogInfo PGW gtpu: set pgw gtpu log-level LogInfo Note 5 Logs for SGW/PGW GTPU module should not be enabled on LogInfo when you run traffic. Leave it on default value LogError