Networks vMME Operator Guide

vMME
Affirmed Networks vMME Operator Guide
Part Number: 550-00328

Revision: C
Date: October 2015
Release Identifier 8.1
Abstract: Affirmed Networks vMME Operator Guide for MME8.1 including MME and SGSN functionality
Copyright© 2015 Affirmed Networks, Inc. All Rights Reserved.
AFFIRMED & DESIGN®, AN3000®, ACUITAS SERVICE MANAGEMENT SYSTEM®, AFFIRMED

NETWORKS MOBILE CONTENT CLOUD™, AFFIRMED OPEN WORKFLOW™, AFFIRMED MOBILE
CONTENT CLOUD™ and other trademarks and designs are the registered or unregistered trademarks of
Affirmed Networks, Inc. and its subsidiaries in the United States and in foreign countries. All other
trademarks are the property of their respective owners. The Affirmed Networks, Inc. trademarks may not
be used in connection with any product or service that is not Affirmed Networks' in any manner that is
likely to cause confusion among customers or in any manner that disparages or discredits Affirmed
Networks, Inc.
This document contains information that is the property of Affirmed Networks, Inc. This document may not
be copied, reproduced, reduced to any electronic medium or machine readable form, or otherwise
duplicated, and the information herein may not be used, disseminated or otherwise disclosed, except with
the prior written consent of Affirmed Networks, Inc.
References
Ref. # Part Number Document Name

1 550-00325 Affirmed Networks vMME Product Overview, Release 8.1
2 550-00326 Affirmed Networks vMME Monitoring Guide, Release 8.1
3 550-00327 Affirmed Networks vMME SGSN Billing Samples, Release 8.1
4 550-00328 Affirmed Networks vMME Operator Guide, Release 8.1
5 550-00329 Affirmed Networks vMME Configuration Management Guide, Release 8.1
6 550-00330 Affirmed Networks vMME CLI Reference Guide, Release 8.1
7 550-00331 Affirmed Networks vMME CSL Reference Guide, Release 8.1
8 550-00332 Affirmed Networks vMME Performance Management Reference Guide, Release 8.1
9 550-00333 Affirmed Networks vMME Fault Management Reference Guide, Release 8.1
10 550-00334 Affirmed Networks vMME CLI User Guide, Release 8.1
11 550-00335 Affirmed Networks vMME Product Overview - VMware Solution, Release 8.1
12 550-00336 Affirmed Networks vMME Operator Guide - VMware Solution, Release 8.1
13 550-00337 Affirmed Networks vMME Open Source Acknowledgements, Release 8.1
14 550-00338 Affirmed Networks vMME CIQ User Manual, Release 8.1
15 550-00339 Affirmed Networks vMME and SGSN Engineering Guide, Release 8.1
16 550-00340 Affirmed Networks vMME SGSN Deployment Guide - Migrating from an Existing
MME/SGSN, Release 8.1
17 550-00341 Affirmed Networks vMME LTE MME and SGSN Supportability Guide, Release 8.1
18 550-00342 Affirmed Networks Lawful Interception Interface Guide for Packet Data, Release 8.1
19 551-00343 Affirmed Networks vMME and SGSN Engineering Guide – VMWare Solution,
Release 8.1
20 551-00189 Affirmed Networks Software Release Notes for the vMME, Release 8.1

Part Number: 550-00328-C Affirmed Networks Proprietary and Confidential
iii
Contents
1 About the Documentation .................................................................................................................... 1
1.1 Purpose of the Document .......................................................................................................... 1
2 New in this Release ............................................................................................................................. 3

2.1 Documentation changes ............................................................................................................ 3
3 Common Setup .................................................................................................................................... 4

3.1 Mandatory Common Setup ........................................................................................................ 4
3.1.1 Platform Mandatory .......................................................................................................... 4
3.1.2 OAM Mandatory ............................................................................................................... 5
3.1.3 DNS Service ..................................................................................................................... 6
3.2 Optional Common Setup ............................................................................................................ 9
3.2.1 OAM Optional ................................................................................................................... 9
3.2.2 CSL (Call Summary Log)................................................................................................ 14
3.2.3 Load Balancer VM .......................................................................................................... 19
3.2.4 Non-VLAN Support for Load Balancer ........................................................................... 21
4 MME Configuration ............................................................................................................................ 23

4.1 MME Mandatory Configuration ................................................................................................ 23
4.1.1 Virtual Machine Configuration ........................................................................................ 23
4.1.2 NAS (Non-Access Stratum) Layer Configuration ........................................................... 24
4.1.3 S1 Configuration ............................................................................................................. 26
4.1.4 S11/S10 GTP Interfaces................................................................................................. 27
4.1.5 TA Table and PLMNID Mapping .................................................................................... 33
4.1.6 S6 Interface to HSS ........................................................................................................ 34
4.2 MME Optional Configuration .................................................................................................... 36
4.2.1 ATAM (Advanced Tracking Area Management) ............................................................ 36
4.2.2 Trace............................................................................................................................... 38
4.2.3 S11 Interface Optional Features .................................................................................... 40
4.2.4 PGW Selection and Reselection Options ....................................................................... 40
4.2.5 PGW/SGW to MME Inter-nodal Congestion Control...................................................... 41
4.2.6 MVNO - PGW Type Classification.................................................................................. 41
4.2.7 S101 to CDMA eAN........................................................................................................ 42
4.2.8 S102 to CDMA IWS ........................................................................................................ 44

iv
4.2.9 S102 Initiated Priority Paging ......................................................................................... 44
4.2.10 S13 to EIR .................................................................................................................... 45
4.2.11 DIAMETER AVP M-bit Override ................................................................................... 47
4.2.12 SGs to VLR ................................................................................................................... 47
4.2.13 Sv to VLR ..................................................................................................................... 49
4.2.14 Sv GTP Mobility ............................................................................................................ 49
4.2.15 SBc to ETWS/PWS CBC .............................................................................................. 50
4.2.16 FXA to AAA .................................................................................................................. 52
4.2.17 GUTI Allocation during TAU ......................................................................................... 53
4.2.18 EMM Cause Code Mapping ......................................................................................... 54
4.2.19 EMM Emergency Number ............................................................................................ 55
4.2.20 EMM Information Message .......................................................................................... 55
4.2.21 Overload Controls......................................................................................................... 56
4.2.22 Capacity and engineering ............................................................................................. 57
4.2.23 Single Radio Voice Call Continuity (SRVCC) ............................................................... 58
4.2.24 IMS Emergency Call ..................................................................................................... 59
4.2.25 Multimedia Priority Service ........................................................................................... 60
4.2.26 HSS Based NPLI .......................................................................................................... 61
4.2.27 Location Service ........................................................................................................... 63
5 SGSN Configuration .......................................................................................................................... 68

5.1 SGSN Mandatory Configuration .............................................................................................. 68
5.1.1 Virtual Machine Configuration ........................................................................................ 68
5.1.2 NAS (Non-Access Stratum) Configuration ..................................................................... 69
5.1.3 Gr/S6d HLR/HSS Interface............................................................................................. 70
5.1.4 Gn/S4 and Gp/S3 GTP Interfaces .................................................................................. 75
5.1.5 PLMN configuration ........................................................................................................ 78
5.1.6 SGSN Radio Access Interfaces ..................................................................................... 78
5.2 SGSN Optional Configuration .................................................................................................. 85
5.2.1 S16 GTP Mobility............................................................................................................ 85
5.2.2 Gf/S13 EIR Interface ...................................................................................................... 85
5.2.3 Ge - SCP (CAMEL) ........................................................................................................ 87
5.2.4 Gd - SMS ........................................................................................................................ 88
5.2.5 Gs – VLR (MSC)............................................................................................................. 90
5.2.6 Ga – CGF (Accounting) .................................................................................................. 93

v
5.2.7 Gn S4 Selection.............................................................................................................. 96
5.2.8 S4 Interface Optional Features ...................................................................................... 98
5.2.9 Iu Flex and Gb Flex ........................................................................................................ 98
5.2.10 Traffic Shaping ............................................................................................................. 99
5.2.11 RAN Information Management ................................................................................... 100
5.2.12 RAN Admission Control .............................................................................................. 100
5.2.13 Sessionless Subscriber Detach.................................................................................. 100
5.2.14 Packet Flow Context (PFC) ........................................................................................ 101
5.2.15 IMEI Forwarding During IRAU .................................................................................... 101
5.2.16 Dataplane Options ...................................................................................................... 102
5.2.17 Periodic Paging Resumption ...................................................................................... 105
5.2.18 QoS Negotiation ......................................................................................................... 106
5.2.19 QoS Conversion ......................................................................................................... 106
5.2.20 Second Authentication................................................................................................ 107
5.2.21 GMM Cause Code Mapping ....................................................................................... 107
5.2.22 Capacity and engineering ........................................................................................... 107
5.2.23 Sigtran Enhancements ............................................................................................... 109
6 Optional Common Application Setup .............................................................................................. 111

6.1 NAS Common ........................................................................................................................ 111
6.2 LI – Lawful Intercept ............................................................................................................... 111
6.2.1 HI2 Protocol Support .................................................................................................... 112
6.3 Roamer Classification ............................................................................................................ 114
6.4 SNR (Seamless National Roaming)....................................................................................... 115
6.4.1 Roamer Control ............................................................................................................ 116
6.5 PLMN Based Admission Controls and Alarms ...................................................................... 118
6.6 Load Rebalancing .................................................................................................................. 119
6.7 Directional Offload.................................................................................................................. 119
6.8 UE Purge................................................................................................................................ 120
6.9 Overload Controls .................................................................................................................. 122
6.10 Femto Cell Support .............................................................................................................. 124
6.11 VoLTE Support..................................................................................................................... 125
6.12 Local EPS QoS Control ....................................................................................................... 126
6.13 PCC Based NPLI ................................................................................................................. 128
6.14 Flexible Gateway Selection.................................................................................................. 129

vi
6.15 UPM Enhancements ............................................................................................................ 130
6.16 eNB Relocation .................................................................................................................... 131
6.17 TAC Level Control ................................................................................................................ 133
6.17.1 IMS Voice over PS and IMS Emergency.................................................................... 134
6.17.2 Timezone .................................................................................................................... 135
6.17.3 MME Location Service................................................................................................ 135
7 Bring Application into Service .......................................................................................................... 136

7.1 Bring MME into Service ......................................................................................................... 136
7.2 Bring SGSN into Service ........................................................................................................ 136
8 Combined Node Variations.............................................................................................................. 138

8.1 Add MME to an SGSN ........................................................................................................... 138
8.1.1 Overview ....................................................................................................................... 138
8.2 Add SGSN to an MME ........................................................................................................... 140
8.2.1 Overview ....................................................................................................................... 140
8.3 PLMN Configuration ............................................................................................................... 141
8.3.1 Overview ....................................................................................................................... 141
8.3.2 Example ........................................................................................................................ 141
9 FGW Configuration .......................................................................................................................... 143

9.1 FGW Platform Configuration .................................................................................................. 143
9.2 FGW Mandatory Configuration .............................................................................................. 143
9.2.1 Enable Virtual Machines ............................................................................................... 143
9.2.2 Activate PLMNs supported by FGW............................................................................. 144
9.2.3 Activate S1 ENB Interface ............................................................................................ 144
9.2.4 Activate S1 MME Interface ........................................................................................... 145
9.2.5 Define MME Peer ......................................................................................................... 145
9.3 FGW Optional Configuration .................................................................................................. 146
9.3.1 FGW Engineering ......................................................................................................... 146
9.3.2 FGW Optional Features................................................................................................ 147
9.3.3 FGW Status Profile ....................................................................................................... 147
9.3.4 FGW Multimedia Priority Service ................................................................................. 147
9.4 Bring FGW into Service ......................................................................................................... 148
9.4.1 Activate the Virtual Machines ....................................................................................... 148
10 Maintenance .................................................................................................................................. 149

vii
10.1 System Maintenance Commands ........................................................................................ 149
10.1.1 Partial Nodal Reset for GTP ....................................................................................... 150
10.2 System Health Check .......................................................................................................... 151
10.3 Software Update .................................................................................................................. 152
10.4 Backup/Restore.................................................................................................................... 152
10.4.1 Binary File Method...................................................................................................... 152
10.4.2 XML File Method ........................................................................................................ 153
10.5 Security ................................................................................................................................ 153
10.5.1 Login Classes ............................................................................................................. 153
10.5.2 Password Complexity Rules ....................................................................................... 154
10.5.3 Add a User .................................................................................................................. 154
10.5.4 Delete a User .............................................................................................................. 155
10.5.5 Modify a User ............................................................................................................. 155
10.5.6 View Security Logs ..................................................................................................... 156
10.5.7 View Active Sessions ................................................................................................. 156
11 Glossary......................................................................................................................................... 157
Appendix A - Default Logins ............................................................................................................... 158

viii
List of Figures
Figure 1. LI HI Reference Model .................................................................................................. 113

ix
List of Tables
Table 1. “Shrubbery” TACACS+ server configuration example ........................................................ 13
Table 2. MME-SGSN TACACS+ client configuration example ......................................................... 13
Table 3. Attribute Combinations ........................................................................................................ 22
Table 4. VM Type to MME Application Mapping ............................................................................... 23
Table 5. VM Type to SGSN Application Mapping ............................................................................. 68
Table 6. VM Type to FGW Application Mapping ............................................................................. 143

x
1 About the Documentation
1.1 Purpose of the Document

This document is intended for use by support teams and customers who wish to install and maintain
the MME product from an application perspective, with release 8.1 software, performing in the role of
MME, SGSN, or a combined node.
This document provides:
 Configuration procedure samples for a standalone MME, and a standalone SGSN, and variations
on a combined node.
 Procedures for maintenance of the MME and SGSN functions.
Pre-Requisites:
 This document assumes that the reader has a good understanding of 3GPP networks and is
familiar with tailf Command Line Interface (CLI).
 Hardware commissioning completed and the Contrail hypervisor is installed.
 Engineering and planning completed as described in the following document:
→ vMME and SGSN Engineering Guide
What this document does not cover:
 Platform/solution based installation content. This information is now housed in separate

documents: Operator Guide for Contrail Solution and Operator Guide for VMWare Solution.
 vMME Operations Administration and Maintenance (OAM) details – please refer to the OAM
Reference Guides (for CM, CLI, FM, PM, CSL):
→ vMME CM Reference Guide
→ vMME CLI Commands
→ vMME Fault Management Reference Guide
→ vMME Performance Management Reference Guide
→ vMME CSL Reference Guide
Relationship of the documents:
 The CM/CLI/FM/PM/CSL reference guides are word format references.

1
About the Document
 The Operator’s Guide is considered a layer above the reference guides and is more procedure
oriented.
 The Monitoring Guide is intended for end customers to help diagnose systems using formally
modeled alarms, counters and logs. Issues that are not resolved by reading this should be
referred to support teams.

2
2 New in this Release
The following sections were added as a result of these release 8.1 features:
 AGW-23400 Local Config for VLR SV address resolution – New section Sv to VLR
 AGW-24211 LI HI2 Protocol Support – New section HI2 Protocol Support
 AGW-24479 GTP Timers IP Config S3-S10-S16-SV – New sections Sv GTP Mobility, S16 GTP
Mobility and Partial Nodal Reset for GTP
 AGW-24606 TACACS+ for AAA – New section TACACS+ for AAA
 AGW-24205 Non-VLAN Support for Load Balancer – New section Non-VLAN Support for Load
Balancer
The following sections were updated as a result of these release 8.1 features:
 AGW-23400 Local Config for VLR SV address resolution – Updated sections SGs to VLR and Gs
– VLR (MSC)
 AGW-24479 GTP Timers IP Config S3-S10-S16-SV – Updated section GTP Feature Overview
2.1 Documentation changes

Encase stand-alone output in boxes.

3
3 Common Setup
The following sections describe VNF (MME-SGSN virtual network function) configuration applied from
the CLI of the active MGMT VM.
3.1 Mandatory Common Setup
3.1.1 Platform Mandatory
3.1.1.1 Set System Timezone
The following configuration allows the timezone to be established.
user@host% set system timezone America/Chicago

[ok][2014-10-20 01:49:03]
[edit]
user@host% show system timezone
timezone America/Chicago;
[ok][2014-10-20 01:49:06]
3.1.1.2 Set System Contact and Location Information (Optional)
Optionally within ‘system’, you can set contact and location information.
user@host % set system contact "Bob Smith x214 555-5555"
user@host % set system location "Ricahrdson, TX. Lab 2, Rack 3, Shelf 4"
3.1.1.3 NTP Setup for Time Sync to External Server
An operator can setup NTP for up to three external servers.
user@host% set ntp server nist.time.nosc.us ip-address 96.226.242.9

[ok][2014-10-20 01:50:53]
[edit]
user@host% show ntp
server nist.time.nosc.us {
ip-address 96.226.242.9;
}
[ok][2014-10-20 01:50:56]

4
Common Setup
3.1.2 OAM Mandatory
3.1.2.1 PM Collection Format and Timing
The MME supports periodic PM output in 3GPP XML format at three different intervals of 5, 15, or 30
minutes. The PM XML output is in the following directory on the MGMT VM:
/usr/local/epc/statistics/reports.
Step # Action
1 Configure the collection interval and retention policy.
In this example we will collect every 15 minutes, and retain the maximum reports allowed.
user@host> configure
Entering configuration mode private
[ok][2014-05-07 21:25:43]
[edit]
user@host% set mme-sgsn statistics collection-interval 15
user@host% set mme-sgsn statistics retention-report 288
user@host% commit
Commit complete.
[ok][2014-05-07 21:59:38]
Note: The retention limits vary depending on the collection interval configured.
2 Check the configuration.
user@host% show mme-sgsn statistics

collection-interval 15;
retention-report 288;
3.1.2.2 OAM IP Configuration
The floating IP address for the NMS interface to the active MGMT VM.
Step # Action
1 oam ip interface configuration:
[ok][2014-05-07 21:25:43]
[edit]
user@host% set mme-sgsn oam-ip-address 1.2.3.4
user@host% commit
Commit complete.
[ok][2014-05-07 21:59:38]
Note: The MGMT VM will be reset after changing the oam-ip-address.

5
Common Setup
3.1.3 DNS Service

In order for PGW/SGW and MME resolution to occur, the MME uses DNS to resolve an IP address.
This can be done locally using DNS Static Cache, or can be used with an external server, or a
combination of both. Static entries take priority, followed by dynamic cache and external query. The
MME supports NAPTR (Name Authority Pointer), SRV, A-Record, and AAAA-Records according to
the Straight-forward NAPTR (S-NAPTR) procedure. Similarly, in order for APN to GGSN resolution to
occur, the SGSN uses DNS to resolve an IP address. The Gn-SGSN only needs A-Records, whereas
an S4-SGSN uses the S-NAPTR procedure as it applies to EPC nodes. This is defined in 3GPP
standards 23.003 (section 19.4.2) and 29.303 (section 4.3.3). Node names should always follow
29.303 conventions, and MNC and MCC should always be three digits, even for a 2-digit MNC it
should be zero prefixed. The service-protocol delimiter is ‘:’ (colon), and service names are always
prefixed by ‘x-3gpp’.
Note:
A complete list of all service parameters supported by the MME/SGSN and the
associated procedures and adjacent nodes to be selected is provided in the DNS
section of the vMME Product Overview document.
Caution:
Review all entries in the static cache or on the DNS server carefully and check
compliancy to applicable standards and MME/SGSN documentation mentioned
above. Any errors, even typographical, can lead to call processing failures.
WARNING:
In order to ensure both static and external DNS queries complete successfully, the
DNS I/F must be configured.
Note: In configurations where an external DNS is not available or present, the
DNS interface must still be configured.
Example: set mme-sgsn dns dns-if ip-address 10.0.0.0
For configurations using an external DNS server, please also refer to the DNS vendor’s user guide.

6
Common Setup
Step # Action
1 Define local DNS Interface. A loopback interface is required for the DNS IP address.
user@host% set mme-sgsn dns dns-if dscp-mark de dynamic-cache-size 5 initial-retry-timer 500 ip-
address 172.18.248.14 max-retry-timer 10 negative-cache-ttl 300 override-ttl off retry-count 6
routing-instance EPCCore01
user@host% show mme-sgsn dns

[snip]
dns-if {
routing-instance EPCCore01;
ip-address 172.18.248.24;
dscp-mark de;
override-ttl off;
negative-cache-ttl 300;
dynamic-cache-size 5;
initial-retry-timer 500;
max-retry-timer 10;
retry-count 6;
}
[ok][2015-01-23 11:34:06]
2 Define at least one external DNS server if using dynamic lookups.

Syntax:
user@host% set mme-sgsn dns server <name of dns server> server-ip-address <ip> weight <value>
user@host% show mme-sgsn dns server
server lab-dns {
server-ip-address 172.16.239.34;
weight 10;
}
[ok][2015-01-23 11:36:59]
3.1.3.1 A-Record
Step # Action
1 Define local A-Record Replacement.
user@host% set mme-sgsn dns static-cache a-record 1 node-name traffic-test node-ip-address

172.16.42.50
user@host% show mme-sgsn dns static-cache a-record

1 {
node-name traffic-test;
node-ip-address 172.16.42.50;
}
3.1.3.2 NAPTR-Record
Step # Action
1 Define APN-FQDN for PGW lookup.
user@host% set mme-sgsn dns static-cache naptr-record 10 domain-name test-

7
Common Setup
Step # Action
apn.apn.epc.mnc011.mcc111.3gppnetwork.org services x-3gpp-pgw:x-s5-pmip:x-s5-gtp replacement
traffic-test order 1 preference 1 flags 'a'
user@host% show mme-sgsn dns static-cache naptr-record 10
domain-name test-apn.apn.epc.mnc011.mcc111.3gppnetwork.org;
services x-3gpp-pgw:x-s5-pmip:x-s5-gtp;
replacement traffic-test;
order 1;
preference 1;
flags 'a';
3.1.3.3 SRV-Record
Step # Action
1 Add srv-record into static cache.
user@host% set mme-sgsn dns static-cache srv-record 1 node-name sss port 2 priority 1 target-name
a1 weight 12
user@host% show mme-sgsn dns static-cache srv-record
1 {
node-name sss;
target-name a1;
port 2;
priority 1;
weight 12;
}
}
3.1.3.4 AAAA-Record
Step # Action
1 Configure aaaa-record and display the details.
Syntax:
user@host% set mme-sgsn dns static-cache aaaa-record <entry-index> node-name <node value > node
node-ip <node-ip-address>
user@host% show mme-sgsn dns static-cache aaaa-record
3 {
node-name ip.sgw2.rch.tx.affirmed-cta.com;
node-ip-address 2280::ec01:213:172:236:8;
}

8
Common Setup
3.2 Optional Common Setup
3.2.1 OAM Optional
3.2.1.1 SNMPV2 for Alarms/Logs
The SNMP OID prefix for all alarms is: .1.3.6.1.4.1.116.6.41.1.1.1.1.1
iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hitachi (116) networkExMib

(6) packetCore (41) epc (1) mme (1) mmeType (1) mme1 (1) alarms (1)
The SNMP OID prefix for all logs is: .1.3.6.1.4.1.116.6.41.1.1.1.1.2
iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hitachi (116) networkExMib

(6) packetCore (41) epc (1) mme (1) mmeType (1) mme1 (1) events (2)
SNMPv2 is used for reporting of alarms and logs to the NMS. For instructions to view logs and
manage alarms and logs, refer to the vMME Fault Management guide.
Step # Action
1 Configure the target to which traps are sent.
The following configuration enables the TCP socket in default routing-instance for SNMP master agent on the MGMT
VM.
user@host% set snmp trap-targets 172.16.239.47 community public
The following configuration enables the TCP socket for SNMP Managers
user@host% set snmp managers 172.16.239.50 community public
2 Check the configuration.
user@host% show snmp

trap-targets 172.16.239.47 {
community public;
}
managers 172.16.239.47 {
community public;
}
3.2.1.2 MME/SGSN Health Threshold Crossing Alarms (TCA)
The MME/SGSN provides on-board continuous health monitoring capability on a per SC service
instance basis. It will periodically compute the most important KPI (attach and activation success rate,
as defined in the vMME Monitoring Guide), and raise an alarm if the configurable threshold values are
met. This capability is ‘on’ by default and the default values may be reasonable for some operators.

9
Common Setup
However, the following parameters are adjustable. This applies to GPRS, UMTS, and LTE
technologies. The corresponding alarms are:
 MmeSc1301 LTE attach success rate
 MmeSc1302 LTE session activation success rate
 MmeSc1303 LTE bearer activation success rate
 MmeSc1313 GPRS attach success rate
 MmeSc1314 GPRS activation success rate
 MmeSc1315 UMTS attach success rate
 MmeSc1316 UMTS activation success rate
The algorithm is based on a sliding window of samples, taken at every ‘update-period’ and averaged
over the ‘window’ duration. If ‘min-data-threshold’ samples are not taken for a given ‘update-period’,
then the KPI is not updated (this minimizes the risk of spurious alarms during low traffic periods).
Step # Action
1 Display the default health profile (default values shown).
[edit]
admin@host% show mme-sgsn status profile
update-period 3;
window 15;
min-data-threshold 100;
attach-major-threshold 90;
attach-minor-threshold 95;
attach-clear-threshold 98;
act-major-threshold 90;
act-minor-threshold 95;
act-clear-threshold 98;
[ok][2015-01-21 09:38:10]
2 Modify the default health profile configuration details.
[edit]
admin@host% set mme-sgsn status profile update-period 5
admin@host% show mme-sgsn status profile

update-period 5;
window 15;
attach-major-threshold 90;
attach-minor-threshold 95;
attach-clear-threshold 98;
act-major-threshold 90;
act-minor-threshold 95;
act-clear-threshold 98;
[ok][2015-01-21 09:40:08]
[edit]
admin@host%

10
Common Setup
3.2.1.3 PM Collection on a Peer Entity Basis
The MME/SGSN collects performance monitoring statistics on a per service instance (ie. VM) basis
for the most part. There is an option to enable collection of selected statistics groupsets on a per peer
entity basis, but this is off by default due to the potentially large volume of data that it may produce.
Enabling these features would only be recommended for a short duration of critical analysis or on
small systems. For MME, this includes statistics per eNB and per FXA RADIUS peer, and for both
MME and SGSN per GTP path. These boolean controls are located under the feature control table.
Only those group-sets explicitly listed below are activated by these features. When the ‘Feature
Status’ value is ‘off’, the associated group-sets do not appear on the CLI or in the PM report system.
 ‘per-enb-stats’ controls group-set:
→ s1Enb
 ‘per-gtp-path-stats’ controls group-sets:
→ gtpV1Path
→ gtpV2Path
 ‘per-fxa-peer-stats’ controls group-set:
→ fxaPeer
Step # Action
1 Display the current feature control settings.
user@host% show mme-sgsn feature control
control direct-tunnel {
status on;
}
control fxa {
status on;
}
control gs {
status on;
}
control hspa-plus {
status on;
}
control lawful-intercept {
status on;
}
control s101 {
status on;
}
control s102 {
status on;
}
control s4-sgsn {
status on;
}
control sbc {
status on;
}

11
Common Setup
Step # Action
control sgs {
status on;
}
control trace {
status on;
}
2 Enable the stats features as needed.
Caution:
Enabling these features may generate a large volume of PM XML

output at /usr/local/epc/statistics/reports. It should only be performed on
small systems, or where a short sample period is required.
This only applies to MME:
user@host% set mme-sgsn feature control per-enb-stats status on

user@host% show mme-sgsn feature control per-enb-stats
status on;
This only applies to MME:
user@host% set mme-sgsn feature control per-fxa-peer-stats status on

status on;
This applies to MME and SGSN:
user@host% set mme-sgsn feature control per-gtp-path-stats status on

status on;
3.2.1.4 TACACS+ for AAA
This feature augments the ‘sshd’ PAM service (on MME-SGSN OAM interfaces) by inserting
pam_tacacs into its auth, account and session stacks. Augmented ‘sshd’ PAM service stacks are
arranged to fall-back/fall-through to the default ‘sshd’ PAM service stack’s modules (mostly comprised
of common-[auth|account|session]) in the event that TACACS+ servers are unreachable. The
augmented account stack derives a “Group ID” (GID) from the service(s) users have configured in
TACACS+. The derived GID is the basis for the user’s access control.
Once MME-SGSNs have TACACS+ servers configured, users can be administrated centrally,
eliminating the need to manually create user accounts on each MME-SGSN node.
The MME-SGSN CLI is accessed via ssh to the (floating) OAM IP address jointly owned by the
management VMs. User accounts are created so that their shells launch the CLI.

12
Common Setup
The following procedure describes TACACS+ server configuration for “shrubbery” tac_plus. The
following requires sudo (or root) on the host running the tac_plus server. For the purpose of this
example, the IP address of the tac_plus server host is 192.168.40.86.
Table 1. “Shrubbery” TACACS+ server configuration example
Step # Action
1 Configure tac_plus secret key in /etc/tacacs+/tac_plus.conf
1a Edit /etc/tacacs+/tac_plus.conf as root
sudo vi /etc/tacacs+/tac_plus.conf
1b Add/modify secret key as follows
key = testing123
2 Add ‘bob/bob’ as an ‘admin’ user to tac_plus config in /etc/tacacs+/tac_plus.conf

2a Edit /etc/tacacs+/tac_plus.conf as root
sudo vi /etc/tacacs+/tac_plus.conf
2b Add/modify user ‘bob’ as follows (password=’bob’ for all authentication methods)
user = bob {
global = cleartext bob
service = hcta-admin {}
}
3 Restart tac_plus server with new configuration
sudo /etc/init.d/tacacs_plus restart
The following procedure describes MME-SGSN configuration corresponding to the tac_plus server
configured in the preceding table.
Table 2. MME-SGSN TACACS+ client configuration example
Step # Action
1 Configure common TACACS+ authentication/authorization mandatory properties
[edit]
admin@host% set aaa tacacs-plus authentication auth-type login
[ok][2014-12-10 21:40:18]
2 Add TACACS+ authentication/authorization server with mandatory members
[edit]
admin@host% set aaa tacacs-plus authentication server server1 ip-address 192.168.40.86 secret
testing123
[ok][2014-12-10 21:50:40]

13
Common Setup
3 Configure common TACACS+ accounting mandatory properties

NOTE: The ‘service’ chosen has no significance other than as a field in the resulting accounting record.
[edit]
admin@host% set aaa tacacs-plus accounting service shell
[ok][2014-12-10 21:55:23]
4 Add TACACS+ accounting server with mandatory members
[edit]
admin@host% set aaa tacacs-plus accounting server server1 ip-address 192.168.40.86 secret
testing123
5 Commit modified configuration
[edit]
admin@host% commit
Commit complete.
[ok][2014-12-10 22:00:14]
3.2.2 CSL (Call Summary Log)

Call Summary Log is an MME/SGSN feature that generates a binary record for every call
release/reject on the system. The output goes to a single file at /usr/local/epc/csl, which is rotated and
kept for a configurable period of time. The files may be retrieved by SFTP pull. Features include CSL
Remote Streaming, CSL Record Throttling and CSL Streaming Fallback).
Caution:
The CSL feature can generate large volumes of data depending on which events
are enabled and depending on the user traffic load on the system. Choose the
events and triggers carefully. By default all failure events are enabled.
CSL application is configured automatically to run on the MGMT VM (active and standby).
Step # Action
1 Configure CSL Events and File Behavior.
user@host% show mme-sgsn csl profile

pdnconn-events-mme true;
bearer-events-mme true;
mobility-events-mme true;
radiobearer-events-mme true;
file-creation-period 30;
file-retention-period 60;
max-records-per-file 780000;

14
Common Setup
Step # Action
triggers-mme fail,reject,release;
max-records-per-period no-limit;
Configure to close the file every 5 minutes:
user@host% set mme-sgsn csl profile file-creation-period 300

Disable normal release as a trigger:
user@host% set mme-sgsn csl profile triggers-mme fail,reject

triggers-mme fail,reject;
max-records-per-period no-limit;
2 Check file output directory.

File name starting with letter ‘o’ is the currently open file.
user@host> start shell
Login into the MGMT VM (determine the MGMT IP from the OpenStack UI)
%ssh mtc@172.24.255.253
Password:
mtc@vse01-vm01:~$cd /usr/local/epc/csl/closed
mtc@vse01-vm01:/usr/local/epc/csl/closed$ ls -l
total 4
-rw-r--r-- 1 root root 18 Dec 23 15:40 csl-MME-2-20131223154030-0600
mtc@vse01-vm01:/usr/local/epc/csl/closed$ cd ../open
mtc@vse01-vm01:/usr/local/epc/csl/open$ ls -l
total 4
-rw-r--r-- 1 root root 18 Dec 23 15:41 ocsl-MME-2-20131223154100-0600
mtc@vse01-vm01:/usr/local/epc/csl/open$
3 Invoke Decode Utilities on the Binary File.

A perl script for decoding the binary CSL format is built into the MME/SGSN. The results go to stdout.
mtc@vse01-vm01:~$ csl-decode -h
Usage: /usr/local/epc/bin/csl-decode [<option>] [<filter>] <csl_file_list>
where <option> can be one of the following
-b will print hex format output (you can give -binary also)
-d will print detailed output (you can give -detailed also)
-brief print output in brief mode
-summary print output in summary mode
-csv print output into a file, in xls readable format(.csv)
where <filter> can be one of the following
-release print only release CSL records
-reject print only reject CSL records
-failure print only failure CSL records
-success print only success CSL records
-abnormal-release print only abnormal-release CSL records
-normal-release print only normal-release CSL records
and <csl_file_list> can be one or more csl files
Only files of name beginning with csl or ocsl are processed
Filters can be used only with -d and -brief option

15
Common Setup
Step # Action
When filters are used with out any option, -d is used by default.
mtc@vse01-vm01:/usr/local/epc/csl/closed$
mtc@vse01-vm01:/usr/local/epc/csl/closed$ csl-decode -d csl-MME-2-20131223154030-0600
3.2.2.1 CSL Binary File SFTP Pull
CSL file transfer may be initiated by the NMS on a periodic basis. File deletion is to be done by the
NMS so it does not have to track what remains to be pulled.
Step # Action
1 SFTP to the MME/SGSN (non-gui sftp client is shown but any sftp client should work). Use the oam-ip-
address as provisioned on the MME/SGSN in section 3.1.2.2
sftp sftpuser@<sftpip>
2 Change to the directory that contains the files to pull.
sftp> cd /usr/local/epc/csl/closed
3 List the files in the closed directory.
sftp> ls
csl-MME-4-20120419115100-0500 csl-MME-4-20120419120830-0500
4 Make a new directory to move the files to pull into (a name besides ‘pull’ can be used).
sftp> mkdir pull
5 Move (rename) the closed files into the new ‘pull’ directory.
sftp> rename csl-MME-4-20120419115100-0500 pull/csl-MME-4-20120419115100-0500

sftp> rename csl-MME-4-20120419120830-0500 pull/csl-MME-4-20120419120830-0500
ALERT: Use the above command for each file to be pulled. A graphical sftp client will make this much easier since
multiple files can be highlighted and dropped into the ‘pull’ folder.
ALERT: A new directory is created because the MME/SGSN may still be writing new files to disk while the files are
being pulled. This allows for an easy way to tell which files should be deleted after the pulling is complete. Some
graphical clients allow you to ‘move’ files (copy and then delete) directly from remote to local and thus the need to
move them to a temporary directory is no longer necessary.
6 Get the files from the ‘pull’ directory.
sftp> cd pull
sftp> get *
Fetching /usr/local/epc/csl/pull/csl-MME-4-20120419115100-0500 to csl-MME-4-20120419115100-0500
Fetching /usr/local/epc/csl/pull/csl-MME-4-20120419120830-0500 to csl-MME-4-20120419120830-0500
7 Check that the files are in the destination directory.
sftp> lls –l
ALERT: The command is ‘lls’ not ‘ls’. ‘lls’ is for ‘local ls’.

16
Common Setup
Step # Action
ALERT: It is probably better to check the destination directory using a local file manager or local terminal.
8 Clean up.
sftp> rm *
sftp> cd ..
sftp> rmdir pull
3.2.2.2 CSL Remote Streaming
Remote streaming allows operators to stream CSL records to remote server(s) rather than to the
active MGMT VM. This offloads the MGMT VM for high traffic nodes. If remote streaming is not
provisioned, then legacy streaming to the MGMT VM occurs.
Before configuring CSL remote streaming, remote CSL server(s) must first be installed and
commissioned. Once complete, follow these steps to configure CSL remote streaming at the
MME/SGSN node. Note that legacy streaming to the MGMT VM is disabled once the streaming
component is configured.
If remote streaming is provisioned:
 it should be done during a maintenance window since CSL records may be dropped while
remote-server connections are established
 the MGMT VM will only generate CSL records if streaming-fallback is enabled and there
are connection issues with the remote streaming server
 if the agwCmnCsl service remains provisioned, then empty CSL files are not generated on the
MGMT VM during periods of inactivity as long as the streaming component remains
provisioned
Step # Action
1 Add the default CSL SCTP profile and if desired, modify the default values.
user@host% set mme-sgsn interface sctp csldefaultsctp
user@host% show mme-sgsn interface sctp csldefaultsctp

rto-initial 500;
rto-min 250;
rto-max 2000;
path-max-retrans 5;
association-init-max-transmit 3;
association-max-retrans 6;
no-delay true;
max-out-stream 11;
max-in-stream 11;
hb-interval 30;
rx-buffer-size 149000;
tx-buffer-size 149000;
sack-delay 200;
sack-frequency 2;
2 Add the streaming csl component and configure local streaming information. A loopback interface is

17
Common Setup
Step # Action
required for the CSL IP address.
Syntax:
user@host% set mme-sgsn csl streaming <sctp-profile> <routing-instance> <local-ip-address>
<remote-ip-address1> <remote-port1> <cr or additional parameters>
For example, to provision the local endpoint and one remote server:
user@host% set mme-sgsn csl streaming sctp-profile csldefaultsctp routing-instance EPCCore01

local-ip-address 172.18.249.154 remote-ip-address1 172.16.236.179 remote-port1 30000
user@host% show mme-sgsn csl streaming
sctp-profile csldefaultsctp;
local-ip-address 172.18.249.154;
remote-ip-address1 172.16.236.179;
remote-port1 30000;
3 Modify the streaming configuration as required.
user@host% set mme-sgsn csl streaming sctp-profile csldefaultsctp local-ip-address 10.1.1.10

user@host% set mme-sgsn csl streaming sctp-profile csldefaultsctp remote-ip-address1 20.1.1.20
user@host% set mme-sgsn csl streaming sctp-profile csldefaultsctp remote-port1 20000
user@host% show mme-sgsn csl streaming

sctp-profile csldefaultsctp;
local-ip-address 10.1.1.10;
remote-ip-address1 20.1.1.20;
remote-port1 20000;
3.2.2.3 CSL Record Throttling
By default, the MME/SGSN does not perform CSL overload record throttling when streaming CSL
records to the active MGMT VM. Follow these steps to limit the maximum number of records that are
written within 10 second intervals. Operational counter ‘records-dropped’ displays the total number of
records dropped due to throttling. This counter is reset to zero anytime the provisioned value ‘max-
records-per-period’ is changed.
Step # Action
1 Modify the default record throttling parameter.
user@host% set mme-sgsn csl profile max-records-per-period 12000

triggers-mme fail,reject;
max-records-per-period 12000;

18
Common Setup
3.2.2.4 CSL Streaming Fallback
As a fallback mechanism, there is a configurable parameter that allows operators to redirect CSL
records to the MGMT VM when the connection to the remote server is down. By default, if remote
streaming is provisioned and the CSL-Clients are unable to connect to at least one remote CSL
server, then CSL records are discarded until at least one remote connection is established. This
behavior can be overridden to allow fallback to legacy MGMT VM streaming by performing the steps
outlined in the following table. Empty CSL files are not generated on the MGMT VM during periods of
inactivity as long as the streaming component is provisioned.
Note that the agwCmnCsl service must be provisioned before setting ‘streaming-fallback’ to ‘enable’.
Step # Action
1 Modify the streaming fallback parameter.
user@host% set mme-sgsn csl streaming streaming-fallback enable
user@host% show mme-sgsn csl streaming streaming-fallback

streaming-fallback enable;
3.2.3 Load Balancer VM

The Load Balancing (LB) Virtual Machine forwards ingress packets to the 3GPP address of the target
VMs. On the LB VM, the LBCtrl process programs steering policies into a forwarding infrastructure
running within the LB VM kernel. This configuration is used to steer incoming traffic to specific target
VMs.
Two or more (up to 8) LBCtrls can be instantiated on separate hosts. All policies are programmed on
each LB VM allowing the ability to load balance ingress 3GPP traffic across all LB VMs. Egress traffic
is handled on the target VM by routing the packets back to the LB VM using multi-path routing (in
order to load balance the egress 3GPP traffic). 2G and 3G user data does not transverse the LB VM
and is routed directly to the target Data VMs with a static route configured in the next-hop router/L3-
capable switch.
Attention:
It is recommended to have the LB VM interface and the 3GPP interfaces IP addresses in
different subnets.
If 3GPP interfaces share the same subnet as the LB VM, the next hop router sends an ARP
request for the 3GPP interfaces to the LB VM interface but the LB will not respond to the
ARP request.
To allow for the 3GPP interfaces and the LB VM to share the same subnet one of the
following actions can be taken on the next-hop router:
(1) - If the next-hop router supports static routes, then adding static routes for each 3GPP
interface by specifying the destination IP address and the next-hop router IP address
where:

19
Common Setup
• Destination IP address is the IP of the 3GPP interface

• Next-hop router is the IP of the LB interface
(2) - Adding static ARP entries for each 3GPP interface by specifying the destination IP
address and the MAC address where:
• Destination IP address is the IP of the 3GPP interface
• MAC address of the LB interface
Specific command syntax is dependent on the router manufacturer.
The integrity of the SRM policies is maintained by keeping steering policies in an internal distributed
database to ensure data consistency.
Step # Action
1 Set the steering mechanism to ‘load-balancer’:
user@host% set mme-sgsn system steering load-balancer
2 Configure the load balancer VMs:
user@host% set mme-sgsn system lb unit 0 vm-instance <vm-instance>

user@host% set mme-sgsn system lb unit 1 vm-instance <vm-instance>
3 Configure the routing instances; follow the example below:

MME example:
user@host% set routing-instances instance EPCAccess01 vlan-tag1 100
user@host% set routing-instances instance EPCAccess01 next-hop-ipv4-gw-addr1 172.27.100.1/24
user@host% set routing-instances instance EPCAccess01 vlan-host-interface1 eth3
user@host% set routing-instances instance EPCAccess01 lb-instance 0 if1-ipv4-addr 172.27.100.2/24
user@host% set routing-instances instance EPCCore01 vlan-tag1 200
user@host% set routing-instances instance EPCCore01 next-hop-ipv4-gw-addr1 172.27.200.1/24
user@host% set routing-instances instance EPCCore01 vlan-host-interface1 eth3
user@host% set routing-instances instance EPCCore01 lb-instance 0 if1-ipv4-addr 172.27.200.2/24
SGSN or combo MME-SGSN example:

user@host% set routing-instances instance EPCAccess01 next-hop-ipv6-gw-addr1
fd02::100:0:0:ac1b:6401/64
user@host% set routing-instances instance EPCAccess01 next-hop-ipv6-gw-addr2
fd02::101:0:0:ac1b:6501/64
user@host% set routing-instances instance EPCAccess01 lb-instance 0 if1-ipv6-addr
fd02::100:0:0:ac1b:6402/64
fd02::101:0:0:ac1b:6502/64
fd02::100:0:0:ac1b:6403/64

20
Common Setup
Step # Action
fd02::101:0:0:ac1b:6503/64
user@host% set routing-instances instance EPCAccess01 data-instance 0 if1-ipv4-addr
172.27.100.4/24
fd02::100:0:0:ac1b:6404/64
172.27.101.4/24
fd02::101:0:0:ac1b:6504/64
172.27.100.5/24
fd02::100:0:0:ac1b:6405/64
172.27.101.5/24
fd02::101:0:0:ac1b:6505/64
user@host% set routing-instances instance EPCCore01 next-hop-ipv6-gw-addr1
fd02::200:0:0:ac1b:c801/64
user@host% set routing-instances instance EPCCore01 next-hop-ipv6-gw-addr2
fd02::201:0:0:ac1b:c901/64
user@host% set routing-instances instance EPCCore01 lb-instance 0 if1-ipv6-addr
fd02::200:0:0:ac1b:c802/64
fd02::201:0:0:ac1b:c902/64
fd02::200:0:0:ac1b:c803/64
fd02::201:0:0:ac1b:c903/64
user@host% set routing-instances instance EPCCore01 data-instance 0 if1-ipv4-addr 172.27.200.4/24
user@host% set routing-instances instance EPCCore01 data-instance 0 if1-ipv6-addr
fd02::200:0:0:ac1b:c804/64
fd02::201:0:0:ac1b:c904/64
fd02::200:0:0:ac1b:c805/64
fd02::201:0:0:ac1b:c905/64
3.2.4 Non-VLAN Support for Load Balancer

This feature adds distinct network interfaces in the Load Balancer VM for every ‘external’ routing
instance. As well, it retains existing VLAN functionality as an option for the VMWare solution. The VM
network interface setup procedure changes to be common across different configurations. The eth0-
eth2 are common to all VM types and is configured during VM initialization. Other interfaces become
variable based on SDN configuration and is configured after configuration download to the VM.

21
Common Setup
To activate this feature, set the vlan-tagging to ‘disable’, sdn to ‘contrail’ and steering to ‘load-
balancer’. Follow these steps.
Step # Action
1 Turn the feature on feature by setting sdn to contrail, steering to load-balancer and vlan-tagging to
disable.
user@host% set mme-sgsn system sdn contrail

user@host% set mme-sgsn system steering load-balancer
user@host% set routing-instances vlan-tagging disable
2 Configure the network interfaces.
user@host% set routing-instances instance <instance> bfd disable

user@host% set routing-instances instance <instance> next-hop-ipv4-gw-addr1 <ip-address>
user@host% set routing-instances instance <instance> lb-vm-if1 <lb-interface-name1>
user@host% set routing-instances instance <instance> data-vm-if1 <data-interface-name1>
user@host% set routing-instances instance <instance> lb-instance <instance> if1-ipv4-addr <ip-
address>
user@host% set routing-instances instance <instance> data-instance <instance> if1-ipv4-addr <ip-
address>
The following table is provided for guidance regarding valid combinations and usage of the
associated attributes.
Table 3. Attribute Combinations
SDN STEERING VLAN-TAGGING Usage

(contrail/none) (contrail/load-balancer/off) enable/disable
contrail contrail enable Invalid
contrail load-balancer enable Not Supported
contrail off enable Invalid
contrail contrail disable Depreciated
contrail load-balancer disable non-VLAN (this feature)
contrail off disable Invalid
none contrail enable Invalid
none load-balancer enable VMWare VLAN (the default)
none off enable Invalid
none contrail disable Invalid
none load-balancer disable VMWare/OpenStack (future)
none off disable SIM

22
4 MME Configuration
4.1 MME Mandatory Configuration

This section contains all the mandatory configuration procedures.
The following table provides the mapping between the virtual machine type and the MME applications
that reside on that virtual machine type. This table is all inclusive, meaning it contains both mandatory
and optional elements.
Table 4. VM Type to MME Application Mapping
Virtual Machine Type MME Application

MGMT CM, PM, FM, CSL, Trace
RM RM, LI, SBc, UPSM, S1M
CALLP SC, SGs, DC, SLs
SIG UPM, S1
SLB LB
4.1.1 Virtual Machine Configuration

Nodes/virtual machines and applications on the MME are managed by the Nodal Manager (NM) and
the Life Cycle Manager (LCM) respectively. Virtual machine instance creations are done through the
OpenStack UI and operator is advised to refer to the UI for the actual VM instance name and instance
number to use in the commands below.
Virtual machines are pre-defined to be home for a set of applications, with some being optional.
Optional processes are those that can be enabled through configuration of a specific interface or the
enabling of a feature through CLI.
The following steps describe the definition of the virtual machines required for a typical MME
configuration.
Step # Action
1 Define the MGMT VM which governs the following processes: CM, PM, FM, CSL, Trace
user@host% set mme-sgsn system mgmt unit 0 vm-instance vse01-vm01

2 Define the CALLP VM which governs the following processes: SC, SGs, DC, SLs
user@host% set mme-sgsn system callp 0 unit 0 vm-instance vse01-vm02


23
MME Configuration
Step # Action
3 Define the SIG VM which governs the following processes: UPM, S1
user@host% set mme-sgsn system sig unit 0 vm-instance vse01-vm03
4 Define the RM VM which governs the following processes: RM, LI, SBc, UPSM, S1M
user@host% set mme-sgsn system rm unit 0 vm-instance vse05-vm02
4.1.2 NAS (Non-Access Stratum) Layer Configuration
4.1.2.1 NAS EMM Configuration
The NAS (Non-Access Stratum) EMM (Mobility Management) table is instantiated automatically and
pre-populated with recommended defaults at install time. Most of the default NAS MM parameters do
not need require any adjustment. However, depending on other network criteria, some of these MME
parameters may need adjustment.
Step # Action
1 Optional: Display the default EMM NAS parameters and modify as desired.
user@host% set mme-sgsn interface nas emm default ue-retry-delay-t3402-value 12 ue-periodic-tau-

t3412-value 54 paging-t3413-initial 5 paging-t3413-increment 2 paging-retry-n3413 2 targeted-
first-page all-ta nwk-init-detach-t3422 6 nwk-init-detach-retry-n3422 2 guti-allocation-t3450 6
guti-allocation-retry-n3450 3 guti-lifetime 12 security-t3460 6 security-retry-n3460 2 identity-
t3470 6 identity-retry-n3470 2 mobile-reachable-timer t3412plus4 opt-authentication-control off
vector-retrieval-failure ignore ciphering-algorithms eea0,eea1,eea2 integrity-algorithms
eia1,eia2,null src-mme-resource-release-timer 15 cancel-location-wait-timer 10 imeisv-req-sec-
mode-cmd on tai-list-max 1 nas-token-window 5 ue-service-reject-t3442-value 60 ta-list-allocation
unrestricted s1-release-delay-timer disabled guti-allocation-intra-tau enable
voice-paging-t3413 disable voice-paging-retry-n3413 0 cancel-location-detach-cause eps-services-
not-allowed-7
user@host% show mme-sgsn interface nas

emm {
ue-retry-delay-t3402-value 12;
ue-periodic-tau-t3412-value 54;
paging-t3413-initial 5;
paging-t3413-increment 2;
paging-retry-n3413 2;
targeted-first-page all-ta;
nwk-init-detach-t3422 6;
nwk-init-detach-retry-n3422 2;
guti-allocation-t3450 6;
guti-allocation-retry-n3450 3;
guti-lifetime 12;
security-t3460 6;
security-retry-n3460 2;
identity-t3470 6;
identity-retry-n3470 2;
mobile-reachable-timer t3412plus4;
opt-authentication-control off;
vector-retrieval-failure ignore;
ciphering-algorithms eea0,eea1,eea2;
integrity-algorithms eia1,eia2,null;
src-mme-resource-release-timer 15;
cancel-location-wait-timer 10;

24
MME Configuration
Step # Action
imeisv-req-sec-mode-cmd on;
tai-list-max 1;
nas-token-window 5;
ue-service-reject-t3442-value 60;
ta-list-allocation unrestricted;
s1-release-delay-timer disabled;
guti-allocation-intra-tau enable;
voice-paging-t3413 disable;
voice-paging-retry-n3413 0;
eps-services-not-allowed-7
}
[snip]
4.1.2.2 NAS ESM Configuration
The NAS (Non-Access Stratum) ESM (Session Management) table is instantiated automatically and
pre-populated with recommended defaults at install time. Most of the default NAS ESM parameters
do not need require any adjustment. However, depending on other network criteria, some of these
MME parameters may need adjustment. In particular, the APN defaults are meant to match what is
configured in the operator’s DNS servers if those features are desired.
Step # Action
1 Optional: Display the default ESM configuration.
user@host% set mme-sgsn interface nas esm activate-bearer-t3485 5 activate-bearer-retry-n3485 2

modify-bearer-t3486 5 modify-bearer-retry-n3486 2 esm-info-t3489 4 esm-info-retry-n3489 2
deactivate-bearer-t3495 5 deactivate-bearer-retry-n3495 2 max-bearers-per-ue 7 max-pdn-conn-per-
ue 8 deactivate-bearer-page-fail disable pgw-ip-type ipv4 deactivate-bearer-enodeb-fail disable
user@host% show mme-sgsn interface nas

[snip]
esm {
activate-bearer-t3485 5;
activate-bearer-retry-n3485 2;
modify-bearer-t3486 5;
modify-bearer-retry-n3486 2;
esm-info-t3489 4;
esm-info-retry-n3489 3;
deactivate-bearer-t3495 5;
deactivate-bearer-retry-n3495 2;
max-bearers-per-ue 7;
max-pdn-conn-per-ue 8;
deactivate-bearer-page-fail disable;
pgw-ip-type ipv4;
deactivate-bearer-enodeb-fail disable;
}
2 Optional: Modify the ESM parameters.
user@host% set mme-sgsn interface nas esm activate-bearer-retry-n3485 5
user@host% show mme-sgsn interface nas esm

admin@host% show mme-sgsn interface nas esm
esm-info-t3489 4;

25
MME Configuration
Step # Action
pgw-ip-type ipv4;
pcscf-restore-mod-fail-action ignore;
[ok][2015-01-26 07:06:37]
4.1.3 S1 Configuration
Since LTE supports dynamic ENB registration, the minimum configuration required for the S1 is to
create the S1 interface and link the SCTP profile. You can also define the maximum eNBs the system
will support.
Step # Action
1 Configure the SCTP layer.
user@host% set mme-sgsn interface sctp s1defaultsctp rto-initial 500 rto-min 100 rto-max 1000
path-max-retrans 2 association-init-max-transmit 2 association-max-retrans 2 no-delay true max-
out-stream 10 max-in-stream 10 hb-interval 30
admin@host% show mme-sgsn interface sctp

sctp s1defaultsctp {
rto-initial 500;
rto-min 100;
rto-max 1000;
path-max-retrans 2;
no-delay true;
max-out-stream 10;
max-in-stream 10;
hb-interval 30;
}
[snip]
2 Define S1 Interface.
user@host% set mme-sgsn interface s1 s1-if routing-instance 3 sctp-profile s1defaultsctp ip-

address1-v4 172.16.44.2 ip-address2-v4 0.0.0.0 port 36412 reloc-prep-timer 3 reloc-overall-timer
5 indirect-tunnel-hold-timer 5 handover-resource-release-timer 5 ue-context-release-timer 5 ue-
context-modification-timer 5 wait-for-tau-timer 5 dscp-mark de inter-rat-indirect-forwarding
never indirect-data-fwd-ip-address 0.0.0.0 version 9.5.1 enb-alarm-clear-time 24 fgw-sctp-profile
s1default sctp sgw-gtpu-dual-tla-ip-filter enable
user@host% show mme-sgsn interface s1

s1-if {
routing-instance1 EPCAccess01;
sctp-profile s1defaultsctp;
ip-address1-v4 172.18.248.17;
ip-address2-v4 0.0.0.0;
port 36412;
reloc-prep-timer 3;
reloc-overall-timer 5;
indirect-tunnel-hold-timer 5;
handover-resource-release-timer 5;
ue-context-release-timer 5;
ue-context-modification-timer 5;

26
MME Configuration
Step # Action
wait-for-tau-timer 5;
dscp-mark de;
inter-rat-indirect-forwarding never;
indirect-data-fwd-ip-address 0.0.0.0;
version 10.6.0;
enb-alarm-clear-time 24;
location-reporting-control disable;
fgw-sctp-profile s1defaultsctp;
.... sgw-gtpu-dual-tla-ip-filter enable;
}
[ok][2015-02-17 09:32:59]
3 Define the Max ENBs for the system.
user@host% set mme-sgsn engineering s1-capacity max-num-enodeb 600
user@host% show mme-sgsn engineering s1-capacity

max-enodebs 600;
4.1.4 S11/S10 GTP Interfaces
4.1.4.1 GTP Feature Overview
In this release the GTP Timers and IP Configurability feature alters GTP functionality such that this
section was created to provide the user with a greater understanding from a complete feature
perspective.
An MME/SGSN tunnels GTP control plane signaling messages to peer nodes over the following
defined interfaces:
 S4/S11: Tunnel message to SGW (SGW may use S5/S8 interface to message the PGW, based
on the PLMN)
 Gn/Gp: (GnTunnel):
→ Gn for tunnel procedures: gtpV1 tunnel messages to GGSN (GGSN communication may
be on Gn or Gp interface based on the PLMN). (Referred to as GnTunnel)
→ Gn for mobility procedures: gtpV1 mobility messages to peer SGSN/MME. (Referred to

as GnMobility)
 S10/S3/S16: gtpV2 mobility messaging towards peer MME/SGSN
 Sv: messaging to MSC
 S101: messaging to EHRPD
IP Separation and Timer Overview:
8.1 feature GTP Timers IP Config S3-S10-S16-Sv) enables the operator to configure and use
separate local IP addresses for the each of the GTP mobility interfaces, namely S3, S10, S16, Gn for

27
MME Configuration
mobility procedures, and for the Sv interface. This functionality was provided for the GTP tunnel
interfaces, namely S4, S11, Gn for tunnel procedures by feature GTP Timers and IP Configurability
feature in 8.0. It allowed a single separate IP for all GTP mobility interfaces as a whole. The feature
provided flexibility to the operator to set different path management timer values like the N3-REQ, T3-
RESP, heartbeat and inactivity timers on a per interface basis for these interfaces. The S101
interface still uses the timers and IP configured in the s101 GTP profile (mme-sgsn interface gtp
profile s101).
GTP Profile Overview:
The GTP profile is the OAM configuration entity that defines the operational behavior of GTP
interfaces. The profile contains configurations that define IP connectivity information, as well as timing
and reliability parameters that govern the GTP message timers and path management behavior. The
8.0 feature added the capability to designate a GTP profile of these categories:
 Default GTP profile
 S101 GTP profile
 Interface specific GTP profile
 PLMN specific GTP profile
The 8.0 feature allowed the preceding profile categories to be used for the GTP tunnel interfaces (S4,
S11, Gn Tunnel), and the “default” profile applied to the remaining GTP interfaces (except S101). The
8.1 feature extends this to the GTP mobility interfaces (S3, S10, S16, Gn for mobility messages, and
Sv).
Interface Specific GTP Profile Overview:
In previous releases, there were three GTP profiles, namely, “tunnel”, “mobility” and “s101”, which
defined the IP connectivity and messaging timers for all GTP based interfaces. The “tunnel” profile
managed the S11, S4 and gnTunnel interfaces. The “mobility” profile managed S10, S3, S16, Sv and
gnMobility interfaces. The “s101” profile managed the S101 interface.
The “tunnel” and “mobility” profiles were mandatory configurations required for the system to function.
The 8.0 feature replaced the above mentioned three profiles with a mandatory “default” profile. The
“s101’ profile remains unchanged. All other gtp-profiles are referred to as generic gtp-profiles, which
may be mapped as interface specific or PLMN specific profiles.
Operators have the option of configuring profiles on a per interface basis to customize the timers and
IP addresses for each of the tunnel interfaces. The following config entities were defined in 8.0 and
used:
 s11-if
 s4-if
 gn-if

28
MME Configuration
The 8.1 feature enhances this by providing the option of configuring profiles on a per interface basis
for the mobility interfaces and the Sv interface. In order to do this, the following config entities are
defined and used:
 s3-if
 s10-if
 s16-if
 sv-if
 gn-if
Each of the preceding config entities have “gtp-profile” attributes, which can be linked to any generic
gtp-profile. If a generic profile has been linked to one of these interface entities, then any messaging
on that interface will use the IP and routing parameters and associated messaging and path
management timer values as configured in the linked generic profile.
Up to 32 GTP profiles may be configured in the system, including the default gtp-profile and the s101
gtp-profile. This leaves operators a choice of up to 30 generic GTP profiles that may be configured for
use as interface-based profiles for tunnel and s101 interfaces or PLMN based timer profiles.
Partner PLMN Specific GTP Timers:
Network operators generally have roaming agreements with several partners, enabling UEs to roam
across multiple PLMNs. This can lead to network latency issues in certain cases based on the
topological location of the nodal elements across the different PLMNs. The 8.0 feature helped to
alleviate this by allowing operators to use a different set of N3-REQ/T3-RESP timer values for GTP
tunnel interface messaging across different partner PLMNs for the GTP tunnel interfaces. The 8.1
feature extends this to the GTP mobility interfaces. S101 interface is not affected by this
configuration.
This is achieved by linking a configured generic gtp-profile name to a specific plmn-id in the
subscriber-plmn table. When the MME/SGSN detects that GTP messaging being routed across a
PLMN which has a linked gtp-profile, then the N3-REQ/T3-RESP values are selected from the linked
profile. However, the local sender IP/Routing-instance settings are used from the interface based
profiles.
Global GTP Parameters Overview:
The 8.0 feature relocated globally applicable GTP attributes such as max-pending-transactions,
gtpv1-version and gtpv2-version which were present in the gtp-profile to a parent gtp entity. These
global attributes apply to messaging on all GTP based interfaces.
The following procedure is based on a fresh install.
Step # Action
1 Configure GTP common profile parameters.

29
MME Configuration
Step # Action
user@host% set mme-sgsn interface gtp max-pending-transactions 20000

user@host% set mme-sgsn interface gtp gtpv1-version 10.8.0
2 Configure GTP Default profile.
user@host% set mme-sgsn interface gtp profile default ip-address-v4 192.168.40.233 routing-
instance EPCCore01 ip-address-v6 :: dscp-mark de echo-interval 300 t3-echo-response 15 n3-echo-
request 8 t3-response 5 n3-request 2 inactivity-timer 10 n3-request-session-creation 2 t3-
response-session-creation 5 n3-request-bearer-modification 2 t3-request-bearer-modification 5 n3-
request-context-request 2 t3-Response-context-request 5 n3-request-forward-relocation 2 t3-
response-forward-relocation 5
3 Configure Generic GTP profiles for interfaces.
user@host% set mme-sgsn interface gtp profile profile1 ip-address-v4 192.168.40.234 routing-
4 Link GTP timer profiles with the Interfaces.

For MME:
user@host% set mme-sgsn interface s11 s11-if gtp-profile profile1
For SGSN:
user@host% set mme-sgsn interface gn gn-if gn-tunnel-profile profile1
5 Configure generic GTP profile for PLMN.

user@host% set mme-sgsn interface gtp-profile profile3 ip-address-v4 0.0.0.0 routing-instance
NULL ip-address-v6 :: dscp-mark de echo-interval 300 t3-echo-response 15 n3-echo-request 8 t3-
response 5 n3-request 2 inactivity-timer 10 n3-request-session-creation 2 t3-response-session-
creation 5 n3-request-bearer-modification 2 t3-request-bearer-modification 5 n3-request-context-
request 2 t3-Response-context-request 5 n3-request-forward-relocation 2 t3-response-forward-
relocation 5
6 Link GTP timer profiles with the PLMN ids.
user@host% set mme-sgsn subscriber subscriber-plmn <plmn> gtp-profile profile3
To configure the S10/S3 and S11 interface’s you will create two GTP profiles. A tunnel profile for S11,
and a mobility profile for S10/S3.
Step # Action
1 Configure the GTP common profile parameters.


30
MME Configuration
Step # Action
1a Define the S11 default profile.

The following is the default profile for tunnel type interfaces (e.g. S4/S11/Gn), this is required as a minimum:
user@host% set mme-sgsn interface gtp profile default routing-instance EPCCore01 ip-address-v4
172.16.44.3 ip-address-v6 :: dscp-mark de echo-interval 300 t3-echo-response 15 n3-echo-request 8
t3-response 5 n3-request 2 inactivity-timer 10 n3-request-session-creation 2 t3-response-session-
request 2 t3-response-context-request 5 n3-request-forward-relocation 2 t3-response-forward-
relocation 5
user@host% show mme-sgsn interface gtp profile default

ip-address-v4 172.16.44.3;
ip-address-v6 ::;
dscp-mark de;
echo-interval 300;
t3-echo-response 15;
n3-echo-request 8;
t3-response 5;
n3-request 2;
inactivity-timer 10;
n3-request-session-creation 2;
t3-response-session-creation 5;
n3-request-bearer-modification 2;
t3-request-bearer-modification 5;
n3-request-context-request 2;
t3-response-context-request 5;
n3-request-forward-relocation 2;
t3-response-forward-relocation 5;
Optionally, if separation of S4 and S11 source IP addresses is desired, configure a profile specific to the S11
interface or S4 interface and link it under that interface. This will override the implied reference to the generic tunnel
profile for that particular interface.
user@host% set mme-sgsn interface gtp profile s11 ip-address-v4 1.2.3.4 routing-instance
EPCCore01
user@host% set mme-sgsn interface s11 s11-if gtp-profile s11
2 Define the S10/S3 Interface.
user@host% set mme-sgsn interface gtp profile mobility routing-instance EPCCore01 ip-address-v4
relocation 5
Unless specified, the Tunnel and Mobility IPs can be the same.
user@host% show mme-sgsn interface gtp profile mobility routing-instance EPCCore01

ip-address-v4 172.16.44.3;
ip-address-v6 ::;
dscp-mark de;
echo-interval 300;
n3-echo-request 8;
t3-response 5;
n3-request 2;

31
MME Configuration
Step # Action
Interface IP Address Separation:
The following procedure is based on a fresh install.
Step # Action
1 Configure GTP Default profile.
user@host% set mme-sgsn interface gtp profile default ip-address-v4 192.168.40.233 routing-
response-session-creation 5 n3-request-bearer-modification 2 t3-request-bearer-modification 5
n3-request-context-request 2 t3-Response-context-request 5 n3-request-forward-relocation 2 t3-
2 Configure Generic GTP profiles for interfaces.
3 Link GTP timer profiles with the Interfaces.
user@host% set mme-sgsn interface sv sv-if gtp-profile profile1
user@host% set mme-sgsn interface gn gn-if gn-mobility-profile profile2
user@host% set mme-sgsn interface gn gn-if gn-tunnel-profile default
4 Configure generic GTP profile for PLMN.
user@host% set mme-sgsn interface gtp profile profile3 ip-address-v4 0.0.0.0 routing-instance
NULL ip-address-v6 :: dscp-mark de echo-interval 300 t3-echo-response 15 n3-echo-request 8 t3-
response 5 n3-request 2 inactivity-timer 10 n3-request-session-creation 2 t3-response-session-

32
MME Configuration
Step # Action
creation 5 n3-request-bearer-modification 2 t3-request-bearer-modification 5 n3-request-
context-request 2 t3-Response-context-request 5 n3-request-forward-relocation 2 t3-response-
forward-relocation 5
5 Link GTP timer profiles with the PLMN ids.
user@host% set mme-sgsn subscriber subscriber-plmn <plmn> gtp-profile profile3
6 Partial nodal reset for GTP.

NOTE: Lock all data VMs, then all sig VMs, then all callp VM pairs with standby first and active second, then the
standby rm VM and lastly the active rm VM.
user@host% request mme-sgsn system data lock unit-id <n> force
user@host% request mme-sgsn system sig lock unit-id <m> force
user@host% request mme-sgsn system callp <x> lock unit-id <z>
user@host% request mme-sgsn system callp <x> lock unit-id <y> force
user@host% request mme-sgsn system rm lock unit-id <b>
user@host% request mme-sgsn system rm lock unit-id <a> force
NOTE: Unlock the rm VM pair, then the callp VM pairs, then the sig VMs, and lastly the data VMs.
user@host% request mme-sgsn system rm unlock unit-id <a>
user@host% request mme-sgsn system rm unlock unit-id <b>
user@host% request mme-sgsn system callp <x> unlock unit-id <y>
user@host% request mme-sgsn system callp <x> unlock unit-id <z>
user@host% request mme-sgsn system sig unlock unit-id <m>
user@host% request mme-sgsn system data unlock unit-id <n>
4.1.5 TA Table and PLMNID Mapping
Step # Action
1 Define the MME Pools.
user@host% set mme-sgsn service-area mme-pool pool2 mme-name mme78 mme-groupid 32768 mme-code 64
relative-capacity 100
user@host% show mme-sgsn service-area mme-pool pool2
mme-name mme78;
mme-groupid 32768;
mme-code 64;
relative-capacity 100;
ALERT: To avoid STMSI collisions within a node, configure unique mme-codes across all mme-pools.
2 Define the PLMID to Pool Mapping.
user@host% set mme-sgsn service-area plmn 10068 mme-pool pool1 sgsn-pool default

33
MME Configuration
Step # Action
user@host% show mme-sgsn service-area plmn 10068
mme-pool pool1;
sgsn-pool default;
3 Define the PLMID/Subscriber Mapping.
user@host% set mme-sgsn subscriber subscriber-plmn <plmn> gtp-profile none ims-local-breakout

allow protocol-type gtp suppress-hss-notify disable ims-support disable local-breakout allow
local-breakout-apn-list test native-mme-group-ids none lgw-protocol-type pmip mt-lr disable mo-lr
disable nri-bit-length 5 dns-preference s-naptr
user@host% show mme-sgsn subscriber subscriber-plmn <plmn>

gtp-profile none;
protocol-type gtp;
suppress-hss-notify disable;
ims-local-breakout allow;
ims-support disable;
local-breakout allow;
local-breakout-apn-list test
native-mme-group-ids none;
lgw-protocol-type pmip;
mt-lr disable;
mo-lr disable;
nri-bit-length 5;
dns-preference s-naptr;
These attributes can be modified as needed.
4.1.6 S6 Interface to HSS

For the MME interface to the HSS, S6a is mandatory. The S4-SGSN interface to HSS, S6d, is
optional if Gr is configured instead. However, both S6a and S6d share the same interface
configuration on a combined MME/SGSN node, so it is called simply S6. Selection between Gr and
S6 for an S4-SGSN is done on a per UE basis according to IMSI and the hss-hlr-routing table
configured on the SGSN. The ability is improved for a Combined MME/S4-SGSN or a stand-alone
S4-SGSN to retrieve authentication information over the Gr interface for an EPC subscriber located in
a GERAN/UTRAN coverage area, and then to retrieve subscription information for the EPC capable
subscriber over the S6a interface. This can be used by an operator who has an HSS deployment that
does not support the S6d interface. This development also provides the flexibility to retry the
authentication or subscription information over Gr interface, if the attempt to retrieve over S6 interface
fails.
Step # Action
user@host% set mme-sgsn interface sctp s6defaultsctp rto-initial 500 rto-min 100 rto-max 1000
path-max-retrans 2 association-init-max-transmit 2 association-max-retrans 2 no-delay true max-
out-stream 10 max-in-stream 10 hb-interval 30
user@host% show mme-sgsn interface sctp s6defaultsctp

rto-initial 500;
rto-min 100;
rto-max 1000;
path-max-retrans 2;

34
MME Configuration
Step # Action
no-delay true;
max-out-stream 10;
max-in-stream 10;
hb-interval 30;
2 Define local diameter profile.
user@host% set mme-sgsn interface diameter profile sctp-profile s6defaultsctp mme-realm affirmed-
cta.com watchdog-timer 30 reconnect-timer 30 peer-state-timer 30 dscp-mark de peer-selection-alg
load-based
user@host% show mme-sgsn interface diameter profile sctp-profile s6defaultsctp

mme-realm affirmed-cta.com;
watchdog-timer 30;
reconnect-timer 30;
peer-state-timer 30;
dscp-mark de;
peer-selection-alg load-based;
3 Add the S6 interface.
user@host% set mme-sgsn interface s6 s6-if request-timer 5 request-retry 0 air-vector-limit 1

include-dest-host disable dual-vector-type disable g-u-vector-limit 1 version 9.5.0 ue-timezone
disable t-ads-retrieval disable
user@host% show mme-sgsn interface s6 s6-if

request-timer 5;
request-retry 0;
air-vector-limit 1;
include-dest-host disable;
dual-vector-type disable;
g-u-vector-limit 1;
version 9.5.0;
ue-timezone disable;
t-ads-retrieval disable;
4 Define initial diameter client (local). A loopback interface is required for the diameter client IP address.
user@host% set mme-sgsn interface diameter client-instance <callp-service-id> host-id-prefix

client routing-instance1 EPCCore01 routing-instance2 EPCCore02 ip-address1 172.18.249.19 ip-
address2 172.18.249.20 port 11111 max-transactions-per-peer 10000
user@host% show mme-sgsn interface diameter client-instance

0 {
host-id-prefix client;
routing-instance1 EPCCore01;
ip-address1 172.18.249.19;
ip-address2 172.18.249.20;
port 11111;
max-transactions-per-peer 10000;
}
5 Define remote peer (HSS or Proxy).
user@host% set mme-sgsn interface diameter peer <host-identity> ip-address 172.16.42.2 ip-
address2 0.0.0.0 port-number 3868
user@host% show mme-sgsn interface diameter peer

hss02501.ds.epc.mnc005.mcc450.3gppnetwork.org ip-address 172.16.42.2 port-number 3868 ip-address2
0.0.0.0;

35
MME Configuration
Step # Action
6 Map the realm to the Diameter remote peer.
user@host% set mme-sgsn interface diameter realm-peer-map ds.epc.mnc005.mcc450.3gppnetwork.org

host-identity hss02501.ds.epc.mnc005.mcc450.3gppnetwork.org activity-role primary
user@host% show mme-sgsn interface diameter realm-peer-map

ds.epc.mnc005.mcc450.3gppnetwork.org host-identity hss02501.ds.epc.mnc005.mcc450.3gppnetwork.org
activity-role primary;
7 Add the subscriber to Realm Mapping.
user@host% set mme-sgsn imsi-routing hss-hlr-routing 45005 interface-type s6 routing-option

standard hss-realm ds.epc.mnc005.mcc450.3gppnetwork.org;
user@host% show mme-sgsn imsi-routing

hss-hlr-routing {
45005 interface-type s6 routing-option standard hss-realm ds.epc.mnc005.mcc450.3gppnetwork.org;
}
8 Modify the HLR/HSS route to enable routing options of: s6d-override, gr-fallback, s6d-override-and-gr-
fallback, standard. The default is standard.
user@host% set mme-sgsn imsi-routing hss-hlr-routing 45005 routing-option s6d-override
OR
user@host% set mme-sgsn imsi-routing hss-hlr-routing 45005 routing-option gr-fallback
OR
user@host% set mme-sgsn imsi-routing hss-hlr-routing 45005 routing-option s6d-override-and-gr-
fallback
OR
user@host% set mme-sgsn imsi-routing hss-hlr-routing 45005 routing-option ue-epc-capability
To remove any routing option provisioned, set the routing option to standard:
user@host% set mme-sgsn imsi-routing hss-hlr-routing 45005 routing-option standard
4.2 MME Optional Configuration

The following sections list optional features on the MME that can be activated in any order.
4.2.1 ATAM (Advanced Tracking Area Management)

This feature implements the advanced tracking area management functionality on the MME. The key
concepts utilized by this feature are:
 The MME predicts the tracking area a UE is likely going to travel into, based on the mobility
information of all UEs on the MME.

36
MME Configuration
 By including the likely TAs in the TAI list for a UE, the UE does not have to perform a tracking
area update when it moves into a tracking area in the list, thereby minimizing the non-revenue
generating control signaling.
 A UE that has a high probability of being paged relative to its tracking area updates will have a
smaller tracking area list, since the cost of paging is typically higher than a single tracking area
update.
Step # Action
1 Enable the ATAM feature.
When enabled, MME will use the TA probability computation to generate a UEs TA list.
When disabled, MME will create the TA probability table, but not use it for a UEs TA list generation.
user@host% set mme-sgsn feature control advanced-ta-mgmt status on
user@host% show mme-sgsn feature control advanced-ta-mgmt

status on;
2 Optionally enable TAI list generation.
user@host% set mme-sgsn feature advanced-ta-mgmt tai-list-generation enable

To turn it back off:
user@host% set mme-sgsn feature advanced-ta-mgmt tai-list-generation disable
3 View the computed neighbor TAI list per tracking area.
user@host> show mme-sgsn service-area tracking-area detail
NEIGHBORTAI
PLMN PERCENT
ID TAC SGWRELOC
----------------------------
50502 0x1001 -
50502 0x1002 -
50502 0x1003 -
50502 0x1004 -
50502 0x1006 -
50502 0x1118 -
50502 0x1145 -
50502 0x2001 -
50502 0x2002 -
50502 0x2118 -
50502 0x31a4 -
50502 0x41a4 -
50502 0x5152 -
50502 0x5154 -
50502 0x8001 -
50502 0x8002 -
50502 0x8003 -
50502 0x8004 -
50502 0x9001 -
50502 0x9002 -
50631 0x1001 -
50631 0x1002 -
50631 0x1003 -
50631 0x1004 -
50631 0x1006 -

37
MME Configuration
Step # Action
50631 0x1118 -
50631 0x1145 -
50631 0x2001 -
50631 0x2002 -
50631 0x2118 -
50631 0x31a4 -
50631 0x41a4 -
50631 0x5152 -
50631 0x5154 -
50631 0x8001 -
50631 0x8002 -
50631 0x8003 -
50631 0x8004 -
50631 0x9001 -
50631 0x9002 -
[ok][2014-12-11 11:20:32]
4 Enable optimized paging.

The MME allows the operator to configure if the first page request shall be sent to last known TA only or all the TAs in
the UEs TAI list. This option is only applicable to UEs that have successfully responded with a new GUTI, if one was
allocated by MME during TAU or GUTI reallocation procedures. The default value is ‘all-ta’.
user@host% set mme-sgsn interface nas nas-mm targeted-first-page last-known-ta
4.2.2 Trace
The MME supports trace of external messaging on a per UE basis with output in XML file format as
defined by 3GPP standards 32.421, 32,422, 32.423. Basic configuration is shown in the following.
Please refer to the Monitoring Guide for more detailed examples of using this feature. 3GPP Trace
functionality runs on two different VMs, the CALLP VM, where the trace data is collected and the
MGMT VM, where the trace files are written.
Step # Action
1 Enable the feature.
user@host% set mme-sgsn feature control trace status on
2 Activate up to ten Concurrent Sessions, many options and variations.

Syntax:
user@host% set mme-sgsn trace session <target-type> <target-value> <session-id> <mme-interface-
mask> <mme-event-mask> <enb-interface-mask> <sgw-interface-mask> <sgw-event-mask> <pgw-interface-
mask> <pgw-event-mask> <trace-depth> <nms-ip>
For different target-type:

user@host% set mme-sgsn trace session <target-type> imsi 312980911000003 12345.123411 s1 att-tau-
det s1 s11 bearer-act-mod-del off none med 1.2.3.4
user@host% set mme-sgsn trace session <target-type>imeisv 1234567892222202 12345.123411 s1 att-

tau-det s1 s11 bearer-act-mod-del off none med 1.2.3.4

38
MME Configuration
Step # Action
user@host% set mme-sgsn trace session <target-type> imei 210000011000060 12345.123411 s1 att-tau-
det s1 s11 bearer-act-mod-del off none med 1.2.3.4
For multiple mme-interface-mask:

user@host% set mme-sgsn trace session <target-type> imsi 312980911000003 12345.123411 s1,s10,s11
att-tau-det s1 s11 bearer-act-mod-del off none med 1.2.3.4
user@host% set mme-sgsn trace session <target-type> imeisv 1234567892222202 12345.123411

s1,s10,s11 att-tau-det s1 s11 bearer-act-mod-del off none med 1.2.3.4
user@host% set mme-sgsn trace session <target-type> imei 210000011000060 12345.123411

For multiple mme-event-mask:

handover,bearer-act-mod-del,ue-pdn-disconn,att-tau-det s1 s11 bearer-act-mod-del off none med
1.2.3.4

s1,s10,s11 handover,bearer-act-mod-del,ue-pdn-disconn,att-tau-det s1 s11 bearer-act-mod-del off
none med 1.2.3.4
user@host% set mme-sgsn trace session <target-type> imei 210000011000060 12345.123411

s1,s10,s11 handover,bearer-act-mod-del,ue-pdn-disconn,att-tau-det s1 s11 bearer-act-mod-del off
none med 1.2.3.4
For multiple enb-interface-mask:

att-tau-det s1, x2,uu s11 bearer-act-mod-del off none med 1.2.3.4

s1,s10,s11 att-tau-det s1, x2,uu s11 bearer-act-mod-del off none med 1.2.3.4
user@host% set mme-sgsn trace session <target-type> imei 210000011000060 12345.123411 s1,s10,s11
att-tau-det s1, x2,uu s11 bearer-act-mod-del off none med 1.2.3.4
For different trace-depth:

att-tau-det s1 s11 bearer-act-mod-del off none max 1.2.3.4

user@host% set mme-sgsn trace session <target-type> imei 210000011000060 12345.123411 s1,s10,s11
att-tau-det s1 s11 bearer-act-mod-del off none min 1.2.3.4
For deleting:
user@host% delete mme-sgsn trace session <target-type> imsi 312980911000003
user@host% delete mme-sgsn trace session <target-type> imeisv 1234567892222202
user@host% delete mme-sgsn trace session <target-type> imei 210000011000060
3 Check file output directory on the MGMT VM.
user@host> shell
user@host:~$ cd /usr/local/epc/trace/
user@host:/usr/local/epc/trace$ ls -ltr open closed
The File is 3GPP defined XML format and may be transferred off-board by SFTP pull.

39
MME Configuration
4.2.3 S11 Interface Optional Features
Step # Action
1 Add the S11 interface table to control any optional features for that interface, or to point to a unique gtp-
profile for this particular interface when required
The change-reporting parameter indicates whether MME/SGSN provides user location information (ULI) for every
mobility event.
The uli-inclusion parameter controls if MME will send ULI in the below GTPv2 messages if it is set to 'force-in-all'
• Create Session Request(HO/TAU)
• Modify Bearer Request
• Delete Session Request
• Delete Bearer Command
And if it is set to 'force-in-mbr', then ULI will be included in every Modify Bearer Request message when requested by
GW.
user@host% set mme-sgsn interface s11 s11-if change-reporting off echoless-path-management

disabled gtp-profile s11 load-status-private-extension off pgw-load-status-lifetime 15 pgw-
quarantine-duration 15 quarantine-non-responsive-pgw off ue-timezone-inclusion standard uli-
inclusion standard
[ok][2014-10-17 13:24:48]

s11-if {
change-reporting off;
uli-inclusion standard;
ue-timezone-inclusion standard;
load-status-private-extension off;
pgw-load-status-lifetime 15;
quarantine-non-responsive-pgw off;
pgw-quarantine-duration 15;
gtp-profile s11;
echoless-path-management disabled;
}
4.2.4 PGW Selection and Reselection Options

This feature changes the PDN Gateway (PGW) selection and reselection procedure. While selecting
or reselecting a PGW, the procedure also makes use of the following to determine its dynamic
selection:
 PDN Connection request type
 PDN Selection type
 Configurable parameter to control the use of PDN Gateway Identity (PGWid) received from HSS
Step # Action
1 Enable the PGW selection feature and adjust reselection retry count (default off, and 2 respectively).
user@host% set mme-sgsn interface nas nas-common use-pgwid-from-hss enable

user@host% set mme-sgsn interface nas nas-common gw-reselection-retries 2

40
MME Configuration
Step # Action
user@host% show mme-sgsn interface nas nas-common

ppf-reset-timer disable;
reset-timer 60;
topological-search enable;
security-context-lifetime disable;
pdn-type-preference ipv4;
full-network-name 3gppnetworkk;
short-network-name 3gppnetwork;
mm-info-triggers none;
mm-info-lifetime disable;
version 9.5.0;
use-pgwid-from-hss enable;
gw-reselection-retries 2;
4.2.5 PGW/SGW to MME Inter-nodal Congestion Control

The MME selects the destination SGW and PGW but there is no method defined for the MME to
know the load status of SGWs and PGWs or the failure status of PGWs. As a result, an MME could
select a highly-loaded SGW/PGW or a PGW that has been failing. The initial Inter-nodal Congestion
Control feature added support for proprietary extensions that enable the load status of SGW and
PGW and the failure status of PGW to be passed to an MME and subsequent usage of that status by
the MME when selecting SGW and PGW. Enhancements to this feature allow the MME to remove a
PGW IP address from selection for new sessions for a period of time. If the MME receives a create
session response message with a cause of remote peer not responding with a CS bit of 0, the MME
can remove that particular PGW IP address from selection. This only applies to GTP based PGWs.
Step # Action
1 Enable the feature under the s11 interface config.
user@host% set mme-sgsn interface s11 s11-if load-status-private-extension on
2 Unless the functionality is also enabled on SGW and PGW, no behavior differences will occur.
Check feature support and configuration on SGW and PGW nodes.
4.2.6 MVNO - PGW Type Classification

This feature adds support for Mobile Virtual Network Operator (MVNO) architecture on the MME as
well as provides the capability to control the bearer establishment procedure for MVNO PDNs using
PGW type classification. This implies that HSS, DNS, and FXA configuration for a given PGW must
be setup in a particular way if you wish for PDN connections to that PGW to follow MVNO
parameters.
Step # Action
1 Ensure adjacent nodes are configured correctly for the desired PGW.
• DNS: The operator must provision the PDN GW on the DNS server for use by MVNO PDN with only the x-s5-gtp
app-protocol.

41
MME Configuration
Step # Action
• HSS: The HSS must not send an IP address for the PDN GW Identity for an APN that may be used for a MVNO
PDN.
• FXA: The AAA (Fxa Interface) must not send an IP address for the PDN GW Identity for an APN that may be used
for a MVNO PDN.
2 Provision a bearer-limits-profile for MVNO default bearers (ALERT: Provision QCIs in the range of 5-9).
Syntax:
user@host% set mme-sgsn subscriber bearer-limits-profile mvno-default qos-class-identifier <qos-
class-identifier> arp-priority <arp-priority>
user@host% set mme-sgsn subscriber bearer-limits-profile mvno-default qos-class-identifier qci5

arp-priority 1
arp-priority 2
arp-priority 3
3 Provision a bearer-limits-profile for MVNO dedicated bearers (Note: Provision QCIs in the range of 1-9):
Syntax:
user@host% set mme-sgsn subscriber bearer-limits-profile mvno-dedicated qos-class-identifier
<qos-class-identifier> arp-priority <arp-priority> max-bitrate-uplink <max-bitrate-uplink> max-
bitrate-downlink <max-bitrate-downlink> guaranteed-bitrate-uplink <guaranteed-bitrate-uplink>
guaranteed-bitrate-downlink <guaranteed-bitrate-downlink>
user@host% set mme-sgsn subscriber bearer-limits-profile mvno-dedicated qos-class-identifier qci1

arp-priority 1 max-bitrate-uplink 100000 max-bitrate-downlink 100000 guaranteed-bitrate-uplink
100000 guaranteed-bitrate-downlink 100000
4 Provision an ‘mvno’ local-eps-qos-entry.
user@host% set mme-sgsn subscriber local-eps-qos-entry mvno default-bearer-limits-profile mvno-

default dedicated-bearer-limits-profile mvno-dedicated
5 Provision the list of MVNO APNs.
user@host% set mme-sgsn subscriber mvno-apn-list <apn-name>
6 Turn the feature on.
user@host% set mme-sgsn feature control mvno-pgw-type status on
4.2.7 S101 to CDMA eAN

The S101 interface connects the MME to the eAN/ePCF in the 3GPP2 eHRPD access network. The
MME and eAN communicate using GTPv2 messages. The UPM service units are used to service the
UDP path that carries the S101 connection to the eANs (maximum of 15000); therefore no additional
service units are configured for this optional feature.
To configure the S101 interface you will first create the optional S101 GTP profile.

42
MME Configuration
For a greater understanding of GTP profile usage, see GTP Feature Overview.
Step # Action
1 Verify the GTP common profile parameters.

1a Define S101 GTP Interface.
user@host% set mme-sgsn interface gtp profile s101 routing-instance EPCCore01 ip-address-v4
relocation 5
user@host% show mme-sgsn interface gtp profile
s101 {
ip-address-v4 172.16.44.3;
ip-address-v6 ::;
dscp-mark de;
echo-interval 4;
n3-echo-request 8;
t3-response 5;
n3-request 2;
}
2 Enable the feature and add the S101 interface.
user@host% set mme-sgsn feature control s101 status on

user@host% set mme-sgsn interface s101 s101-if gtp-profile profile1 tunnel-change-delay-timer 5
wait-for-notification-timer 5 handover-hold-timer 5 version 9.2.0
gtp-profile profile1;
tunnel-change-delay-timer 5;
wait-for-notification-timer 5;
handover-hold-timer 5;
version 9.2.0;
3 Configure the EAN.

Syntax:
user@host% set mme-sgsn interface s101 ean <ehrpd-access-id> ip-address <ip-address>
user@host% set mme-sgsn interface s101 ean 0x12345678 ip-address 172.16.236.10
user@host% show mme-sgsn interface s101 ean

}
ean 0x12345678 {
ip-address 172.16.236.10;

43
MME Configuration
Step # Action
}
[snip]
4.2.8 S102 to CDMA IWS

The S102 interface connects the MME to the 1xRTT Interworking System (IWS). The MME and IWS
communicate using A21 messages to facilitate Circuit Switched Fallback to 1xRTT. The interface
depends on existing diameter peer configuration for the ‘hss-realm-for-min-query’ configuration. The
UPM service units are used to service the UDP path that carries the S102 connection to the IWS
servers (maximum of 200); therefore no additional service units are configured for this optional
feature.
Step # Action
1 Enable the feature and configure the interface.
user@host% set mme-sgsn feature control s102 status on

user@host% set mme-sgsn interface s102 s102-if routing-instance EPCCore01 hss-realm-for-min-query
foo-realm.com ip-address-v4 137.168.68.54

hss-realm-for-min-query foo-realm.com;
ip-address-v4 137.168.54.0;
2 Configure the IWS.
user@host% set mme-sgsn interface s102 iws 0x0102 ip-address 172.16.241.148 port 4598
user@host% show mme-sgsn interface s102 iws

iws 0x0102 {
ip-address 172.16.241.148;
port 4598;
}
[ok][2015-01-26 07:44:01]
3 Show the eNB to IWS mapping (discovered, persistent, but not configured on MME).
Supports up to 15000 entries, so selective command variants are helpful.
user@host> show mme-sgsn interface s102 enb-iws-map

PLMN ENODEB ENODEB IWS IP
ID ID TYPE IWS ID ADDRESS
----------------------------------------------
50631 2513 macro 0x0102 172.16.236.39
50631 2513 macro 0x0103 172.16.236.45
[ok][2014-03-12 09:56:38]
4.2.9 S102 Initiated Priority Paging

This feature makes use of the GEC (Global Emergency Call) bit received in the GCSNA (Generic
Circuit Services Notification Application) status over the S102 interface to provide high priority paging
over the S1-MME interface.

44
MME Configuration
Step # Action
1 Ensure the S1 interface is configured for 9.5.1 version of the standards.
user@host% set mme-sgsn interface s1 s1-if version 9.5.1
ip-address1-v4 172.18.249.1;
ip-address2-v4 172.18.249.11;
ip-address1-v6 ::;
ip-address2-v6 ::;
port 36412;
time-to-wait 60;
reloc-prep-timer 3;
dscp-mark de;
version 9.5.1;
location-reporting-control disable;
lrc-timer-direct 5;
csg-expiration-release-timer 5;
sgw-gtpu-dual-tla-ip-filter enable
2 Enable the priority paging feature under the s102 interface.
user@host% set mme-sgsn interface s102 s102-if priority-paging enable
hss-realm-for-min-query affirmed-cta.com;
ip-address-v4 172.18.249.81;
ip-address-v6 ::;
port 23272;
version icd-v2;
dscp-mark de;
echo-interval 4;
t-ack-21-timer 5;
request-retry 1;
max-pending-transactions 250;
priority-paging enable;
enb-map-lifetime 24;
4.2.10 S13 to EIR

The S13 interface to the EIR is used for equipment identity checks against IMEI. This interface is
based on DIAMETER protocol and can share the diameter client configuration used by the S6
interface. This example re-uses the diameter and sctp configuration for S6 including client instance.
Step # Action

45
MME Configuration
Step # Action
1 Configure the interface.
Syntax:
user@host% set mme-sgsn interface s13 s13-if realm-name <realm-name> request-timer <request-
timer> request-retry <request-retry> include-imsi <include-imsi> eir-host-id <eir-host-id>
version <version>

s13-if {
realm-name foo-realm.com;
request-timer 5;
request-retry 0;
include-imsi enable;
eir-host-id none;
version 9.5.0;
}
[ok][2015-01-26 08:02:50]
2 Configure the peer and the realm to peer mapping.
user@host% set mme-sgsn interface diameter peer foo-eir ip-address 1.2.3.4 ip-address2 0.0.0.0
port-number 3868
user@host% show mme-sgsn interface diameter peer foo-eir

ip-address 1.2.3.4;
port-number 3868;
ip-address2 0.0.0.0;
[ok][2015-01-26 08:06:55]
user@host% set mme-sgsn interface diameter realm-peer-map foo-realm.com host-identity foo-eir

activity-role primary
user@host% show mme-sgsn interface diameter realm-peer-map

}
realm-peer-map foo-realm.com foo-eir {
activity-role primary;
}
3 Configure and activate the feature.
user@host% set mme-sgsn feature equip-identity-check allow-grey-mobile enable log-black-gray-

mobile disable imei-check-lifetime disable imei-check-during-internode on
user@host% show mme-sgsn feature equip-identity-check

allow-grey-mobile enable;
log-black-grey-mobile disable;
imei-check-lifetime disable;
imei-check-during-internode on;
user@host% set mme-sgsn feature control equip-id-check status on

ims-emergency status on;

equip-id-check status on;
per-enb-stats status off;
per-fxa-peer-stats status off;
per-gtp-path-stats status off;
advanced-ta-mgmt status on;
trace status on;

46
MME Configuration
4.2.11 DIAMETER AVP M-bit Override

This feature supports ignoring of AVP’s with M-bit set instead of discarding the entire Diameter
message. The operator may configure AVP codes for which the M-bit suppression is allowed. A
maximum of 100 AVPs can be configured. As per RFC-3588 if an AVP with the 'M' bit set is received
by a Diameter client, server or proxy and either the AVP or its value is unrecognized, the message
MUST be rejected. As a part of this feature, an OAM configuration is provided to override this
behavior.
Step # Action
1 Add an AVP for which M-bit override is desired for s6, s13, or base application.
user@host% set mme-sgsn interface diameter avp-mbit-override 405 application-identifier s6
4.2.12 SGs to VLR

The SGs interface connects the MME to the Mobile Switching Center/Visitor Location Register
(MSC/VLR), providing support for Circuit Switched Fallback to GSM or UMTS.
Step # Action
1 Configure the SCTP profile.
user@host% set mme-sgsn interface sctp sctpSgs rto-initial 500 rto-min 250 rto-max 2000 path-max-
retrans 2 association-init-max-transmit 2 association-max-retrans 2 no-delay true max-out-stream
1 max-in-stream 1 hb-interval 30 rx-buffer-size 149000 tx-buffer-size 149000 sack-delay 200 sack-
frequency 2
user@host% show mme-sgsn interface sctp sctpSgs

rto-initial 500;
rto-min 250;
rto-max 2000;
path-max-retrans 2;
no-delay true;
max-out-stream 1;
max-in-stream 1;
hb-interval 30;
sack-delay 200;
sack-frequency 2;
2 Enable the feature and configure the SGs interface. A loopback interface is required for the SGs
interface IP address.
user@host% set mme-sgsn feature control sgs status on
user@host% set mme-sgsn interface sgs sgs-if routing-instance1 EPCCore01 routing-instance2

EPCCore02 ip-address 172.18.249.27 sctp-profile sctpSgs loc-upd-guard-ts6-1 10 eps-detach-guard-
ts8 4 explicit-imsi-detach-guard-ts9 4 implicit-imsi-detach-guard-ts10 4 mme-reset-ind-guard-
ts12-2 4 loc-upd-retry-ns6 2 eps-detach-retry-ns8 2 explicit-imsi-detach-retry-ns9 2 implicit-
imsi-detach-retry-ns10 2 mme-reset-ind-retry-ns12 2 sms-only false mme-reset-paging-type cs-
paging mme-reset-indication true version 9.3.0 dscp-mark de ip-address2 0.0.0.0
user@host% show mme-sgsn interface sgs sgs-if

47
MME Configuration
Step # Action
ip-address 172.18.249.27;
sctp-profile sctpSgs;
loc-upd-guard-ts6-1 10;
eps-detach-guard-ts8 4;
explicit-imsi-detach-guard-ts9 4;
implicit-imsi-detach-guard-ts10 4;
mme-reset-ind-guard-ts12-2 4;
loc-upd-retry-ns6 2;
eps-detach-retry-ns8 2;
explicit-imsi-detach-retry-ns9 2;
implicit-imsi-detach-retry-ns10 2;
mme-reset-ind-retry-ns12 2;
sms-only false;
mme-reset-paging-type cs-paging;
mme-reset-indication true;
version 9.3.0;
dscp-mark de;
3 Configure up to 64 VLRs.
ALERT: The length of the name should be limited to 31 chars so that it matches the name configured
under vlr-pool in the next step. Although the standards recommend an FQDN for the name, it actually is
not sent in any message for MME/SGSN and only has internal significance to link these two tables
together.
Note: Attribute vlr-type can be: Gs, SGs, Sv or combination of interfaces. For a VLR that supports more
than one type, input one set command for each type, but use the same VLR name each time.
user@host% set mme-sgsn service-area vlr sgsserver.affirmed.com vlr-type sgs vlr-number 1 callp-
service-id 2 sgs-ip-address1 172.16.236.11 sgs-ip-address2 0.0.0.0
user@host% show mme-sgsn service-area vlr sgsserver.affirmed.com

vlr-type sgs;
vlr-number 1;
callp-service-id 2;
sgs-ip-address1 172.16.236.11;
sgs-ip-address2 0.0.0.0;
4 Configure the default VLR for the VLR pool, up to 32 VLR pools are supported.
user@host% set mme-sgsn service-area vlr-pool pool1 vlr-selection-digits default vlr-name

sgsserver.affirmed.com
5 (Optional) Configure the VLR pool with the selected VLR for an IMSI hash range, up to 32 non-
overlapping IMSI hash ranges are supported for a VLR pool.
user@host% set mme-sgsn service-area vlr-pool pool1 vlr-selection-digits 000-100 vlr-name

sgsserver.affirmed.com
Note: The MSC selection is not based on the actual IMSI digits, but on the IMSI hash result specified in TS 23.236.
The MME first does the IMSI hash and then uses that output to select a VLR from the VLR pool: ((IMSI div 10)
modulo 1000) Which reveals a number between the range 0 to 999.
The configuration vlr-selection-digits is the actual range of IMSI hash that is mapped to a particular vlr-pool
0..200 => POOL1 201..599 => POOL2 600..999 => POOL3
This ultimately translates to the use of the digits of the IMSI: 123451234512xxx5

48
MME Configuration
Step # Action
6 Configure the Location Area.
Syntax:
set mme-sgsn service-area location-area <plmn-id> <lac> vlr-pool-name <vlr pool name>
user@host% set mme-sgsn service-area location-area 50631 0x1000 vlr-pool-name pool1
user@host% show mme-sgsn service-area location-area 50631 0x1000

plmn 50631;
lac 0x1000;
vlr-pool-name pool1;
4.2.13 Sv to VLR
The Sv interface supports the Single Radio Voice Call Continuity procedure between the MME and
the VLR such that a voice call started on the EPC network using VoLTE can be handed over to the
legacy circuit domain seamlessly.
Follow these steps to configure the Sv interface IP address of the VLR and to set the type of VLR
discovery (either local or DNS).
Step # Action
1 Configure the VLR discovery type (local or DNS).
Note: If the attribute value is ‘dns’ then the MME uses DNS query to look up the MSC server.
Note: If the attribute value is ‘local-config’ then the MME uses the locally configured Sv interface ip-
address and bypasses the DNS query.
user@host% set mme-sgsn interface sv sv-if vlr-discovery local-config

OR
user@host% set mme-sgsn interface sv sv-if vlr-discovery dns
2 Configure the vlr-type and sv-ip-address of VLR for Sv interface.

user@host% set mme-sgsn service-area vlr <vlr-name> vlr-type sv

user@host% set mme-sgsn service-area vlr <vlr-name> sv-ip-interface <ipv4-address or ipv6-
address>
4.2.14 Sv GTP Mobility

See GTP Feature Overview.

49
MME Configuration
4.2.15 SBc to ETWS/PWS CBC

The SBc interface connects the MME to the CBC (Cell Broadcast Center) node of the ETWS (Early
Tsunami Warning System) and/or PWS (Public Warning System). This interface is based on SBc
protocol messages carried over SCTP as the transport layer. This interface is used for warning
message delivery and control functions. The MME will broadcast warning messages to all eNBs in the
tracking areas designated by the CBC. Operators are able to define the sbc-type as either etws or
pws. The MME is capable of starting and stopping the broadcast of PWS messages, as well can
prioritize the delivery of Commercial Mobile Alert System (CMAS) messages.
Step # Action
1 Create a sctp profile, and modify the default buffer sizes to be larger than default values.
user@host% set mme-sgsn interface sctp sctpSbc rto-initial 500 rto-min 250 rto-max 2000 path-max-
retrans 2 association-init-max-transmit association-max-retrans 2 no-delay true max-out-stream 1
max-in-stream 1 hb-interval 30 rx-buffer-size 200000 tx-buffer-size 200000 sack-delay 200 sack-
frequency 2
[ok][ 2014-06-22 23:10:02]
user@host% show mme-sgsn interface sctp sctpSbc

rto-initial 500;
rto-min 250;
rto-max 2000;
path-max-retrans 2;
no-delay true;
max-out-stream 1;
max-in-stream 1;
hb-interval 30;
sack-delay 200;
sack-frequency 2;
[ok][ 2014-06-22 23:10:02]
2 Enable the feature and create the SBc interface. A loopback interface is required for the SBc interface
IP address. In this example, the sbc-type is set to ‘pws’ (vs the other option of ‘etws’).
user@host% set mme-sgsn feature control sbc status on

[ok][ 2014-06-22 23:10:02]
user@host% set mme-sgsn interface sbc sbc-if routing-instance1 EPCCore01 sctp-profile

s1defaultsctp ip-address1 137.168.68.83 ip-address2 port 29168 dscp-mark ef max-outstanding-
requests 5 version 10.2.0 sbc-type pws warning-message-ttl 1
[ok][ 2014-06-22 23:10:02]
user@host% show mme-sgsn interface sbc sbc-if

ip-address1 172.18.249.23;
port 29168;
max-outstanding-requests 5; (only used if sbc-type is set to etws)
dscp-mark ef;
sbc-type pws;
warning-msg-ttl 1;
version 10.2.0;
[ok][ 2014-06-22 23:10:02]

50
MME Configuration
Step # Action
3 Display warning message retries and retry timer.

port 36412;
reloc-prep-timer 3;
dscp-mark de;
version 10.6.0;
message-logging none;
warning-message-timer 5;
warning-message-retry 3;
[ok][2014-06-22 22:34:30]
4 Configure the retry timer and retries to non-default values.
user@host% set mme-sgsn interface s1 s1-if warning-message-retry 4

[ok][2014-06-22 22:34:07]
user@host% set mme-sgsn interface s1 s1-if warning-message-timer 7

[ok][2014-06-22 22:34:20]

ip-address1-v4 192.168.40.233;
port 36412;
reloc-prep-timer 3;
dscp-mark de;
version 10.6.0;
message-logging none;
warning-message-timer 7;
warning-message-retry 4;
[ok][2014-06-22 22:34:30]

51
MME Configuration
4.2.16 FXA to AAA

The FXA interface to a RADIUS server is used to enable an optional P-GW lookup procedure that is
configured on a per APN basis. The UPM service units are used to service the UDP path that carries
the RADIUS connection to the AAA servers, therefore no additional service units are configured for
this optional feature.
Step # Action
1 Activate the FXA feature.
user@host% set mme-sgsn feature control fxa status on

mvno-pgw-type status on;
s101 status on;
s102 status on;
sgs status on;
sbc status on;
fxa status on;
2 Define up to 4096 APN NI that will trigger the FXA based P-GW selection procedure.
user@host% set mme-sgsn interface fxa fxa-apn foo
user@host% show mme-sgsn interface fxa fxa-apn

fxa-apn foo;
3 Define FXA interface.

Syntax:
set mme-sgsn interface fxa fxa-if routing-instance <routing-instance> ip-address <local ip
address> ports <local ports> path-mgmt-user-name <path management user name> path-mgmt-user-
password <path management user password> path-mgmt-imsi <path management IMSI>
user@host% set mme-sgsn interface fxa fxa-if routing-instance EPCCore01 ip-address 172.18.249.88
ports 36664,36665 path-mgmt-user-name qwerty path-mgmt-user-password qwertyqwertyqwerty path-
mgmt-imsi 1234567890123456
user@host% show mme-sgsn interface fxa fxa-if

ip-address 172.18.249.88;
ports 36664,36665;
path-mgmt-user-name qwerty;
path-mgmt-user-password qwertyqwertyqwerty;
path-mgmt-imsi 123456789012345;
req-timer 10;
req-retry 2;
path-mgmt-interval 60;
path-mgmt-retry-timer 15;
path-mgmt-retry-value 8;
path-mgmt-success-indicator accept-AA-only;
dscp-mark de;
4 Define Radius Profile.

Syntax:
set mme-sgsn interface radius profile max-num-peer-retry <max-num-peer-retry> user-password <user
password> peer-down-state-timer <peer-down-state-timer>
user@host% set mme-sgsn interface radius profile max-num-peer-retry 2 user-password

1111111111111111 peer-down-state-timer 30

52
MME Configuration
Step # Action
user@host% show mme-sgsn interface radius profile

user-password 1111111111111111;
max-num-peer-retry 2;
peer-down-state-timer 30;
5 Define Radius Peers (up to 128).

Syntax:
set mme-sgsn interface radius peer <peer ip address> port-number <port-number> application-
identifier <application-identifier>
user@host% set mme-sgsn interface radius peer 172.16.241.131 port-number 1812 application-
identifier fxa
user@host% show mme-sgsn interface radius peer

}
peer 172.16.241.131 {
port-number 1812;
application-identifier fxa;
}
4.2.17 GUTI Allocation during TAU

For efficiencies on the air interface, this feature provides an option to control if a new GUTI needs to
be allocated for intra-MME TAU. When this option is turned off, no new GUTI is allocated, the TAU
Accept will not include the GUTI and the UE does not need to send in the TAU Complete which
results in message reduction. However, be aware that using the same GUTI has a potential security
risk if the TAU Request with GUTI is not ciphered. This is the tradeoff for reducing the air interface
messaging. The default behavior is to keep the same behavior as the previous releases, i.e., allow
new GUTI to be allocated.
If the guti-lifetime has expired for the UE, the MME will allocate a new GUTI during intra-MME TAU
regardless of the setting of the new option.
Step # Action
1 Disable GUTI allocation during TAU (enabled by default), a NAS EMM function.
user@host% set mme-sgsn interface nas emm guti-allocation-intra-tau disable
2 Display the NAS EMM parameters.
user@host% show mme-sgsn interface nas emm
ue-retry-delay-t3402-value 12;
ue-periodic-tau-t3412-value 54;
paging-t3413-initial 5;
paging-t3413-increment 2;
paging-retry-n3413 2;
targeted-first-page all-ta;
nwk-init-detach-t3422 6;
nwk-init-detach-retry-n3422 2;
guti-allocation-t3450 6;
guti-allocation-retry-n3450 3;
guti-lifetime 12;
security-t3460 6;

53
MME Configuration
Step # Action
security-retry-n3460 2;
identity-t3470 6;
identity-retry-n3470 2;
mobile-reachable-timer t3412plus4;
opt-authentication-control off;
vector-retrieval-failure ignore;
ciphering-algorithms eea0,eea1,eea2;
integrity-algorithms eia1,eia2,null;
src-mme-resource-release-timer 15;
cancel-location-wait-timer 10;
imeisv-req-sec-mode-cmd on;
tai-list-max 1;
nas-token-window 5;
ue-service-reject-t3442-value 60;
ta-list-allocation unrestricted;
s1-release-delay-timer disabled;
guti-allocation-intra-tau disable;
voice-paging-t3413 disable;
voice-paging-retry-n3413 0;
4.2.18 EMM Cause Code Mapping

This component is used to map EMM cause codes with respect to different error scenarios.
Step # Action
1 Setting the default EMM cause code and error description mapping. Also displaying the cause code
value.
user@host% set mme-sgsn interface nas emm-cause-mapping user-unknown cause-code eps-service-not-
allowed-in-this-plmn-1 unknown-scptn-no-gprs-data cause-code eps-service-not-allowed-7 unknown-
scptn-gprs-data cause-code no-suitable-cells-in-ta-15 rat-not-allowed cause-code eps-service-not-
allowed-in-this-plmn-14 roaming-not-allowed cause-code eps-service-not-allowed-in-this-plmn-14
equipment-unknown cause-code eps-service-not-allowed-in-this-plmn-1 authentication-data-
unavailable cause-code network-failure-17 access-restricted cause-code eps-service-not-allowed-
in-this-plmn-14 operator-determined-barring cause-code eps-service-not-allowed-in-this-plmn-14
sm-layer-failure cause-code esm-failure-19 unknown-hss cause-code eps-service-not-allowed-in-
this-plmn-14 dns-mapping-failure cause-code ue-id-cannot-be-derived-9 ta-restricted cause-code
roaming-not-allowed-in-this-ta-13 authorization-rejected cause-code no-suitable-cells-in-ta-15
application-unsupported cause-code no-suitable-cells-in-ta-15 command-unsupported cause-code no-
suitable-cells-in-ta-15 out-of-space cause-code congestion-22 too-busy cause-code congestion-22
unable to comply cause-code no-suitable-cells-in-ta-15 unknown-serving-node cause-code imsi-
unknown-in-hss-2 roaming-restricted-in-mme-due-to-unsupported-feature cause-code no-suitable-
cells-in-ta-15
user@host% show mme-sgsn interface nas emm-cause-mapping access-restricted
cause-code eps-service-not-allowed-in-this-plmn-14;
In the preceding command, error description should be chosen from the listed string values and cause code can be
any of the listed strings or a numeric value in the range of 1-255.
2 Modify the EMM cause code and error description mapping.
user@host% set mme-sgsn interface nas emm-cause-code-mapping <error> cause-code <cause code>
Example:
user@host% set mme-sgsn interface nas emm-cause-code-mapping access-restricted cause-code
congestion-22
user@host% show mme-sgsn interface nas emm-cause-code-mapping

access-restricted cause-code congestion-22;

54
MME Configuration
In the preceding command, error description should be chosen from the listed string values and
cause code can be any of the listed strings or a numeric value in the range of 1-255.
4.2.19 EMM Emergency Number

Follow the steps in this procedure to add and modify and emergency number.
Step # Action
1 Setting an Emergency Number into the list.
user@host% set mme-sgsn interface nas emergency-number-list 1234 emergency-category ambulance
user@host% show mme-sgsn interface nas emergency-number-list emergency-number-list 1234 {

emergency-category ambulance;
}
2 Modify the Emergency Number list.
Syntax:
user@host% set mme-sgsn interface nas emergency-number-list <emergency-number> emergency-category
<emergency-category>
user@host% set mme-sgsn interface nas emergency-number-list 911 emergency-category police

emergency-number-list 1234 {
emergency-category ambulance;
}
emergency-number-list 911 {
emergency-category police;
}
4.2.20 EMM Information Message

This feature implements the sending of the EMM Information message from the MME to UEs based
on locally provisioned information. If the UE is in idle mode, the UE will not be paged, but the EMM
Information message will be sent once the UE is back in active mode. If the operator uses the MM-
Information procedure via the SGs interface, it is recommended to disable this feature to avoid
sending duplicate or different network information to the UE.
EMM Information is an optional message that is sent from the MME to the UE so the UE can update
the network name and time information. The EMM Information message is by default only sent by the
MME if initiated by the VLR. This feature adds the ability for the MME to send the EMM Information
message on any combination of the following provisioned triggers:
 Attach
 Inter-MME TAU
 Daylight saving time change
 Configuration change related to time and/or network name

55
MME Configuration
For the provisioned triggers above, the EMM Information message will include the locally provisioned
information. For the VLR initiated trigger, the EMM Information message will include the information
from the VLR. The usage of the information message can be measured by the following PM counter:
lteMm::procedure::VS.MM.EmmInformation
Step # Action
1 Enable EMM Information to any one of the triggers (example: dst-change).
user@host% set mme-sgsn interface nas nas-common mm-info-triggers dst-change

reset-timer 60;
full-network-name 3gppnetwork;
mm-info-triggers dst-change;
version 10.10.0;
native-mme-groups disable;
2 Disabling the EMM Information feature.
user@host% set mme-sgsn interface nas nas-common mm-info-triggers none
4.2.21 Overload Controls

Overload Controls allows an operator to configure at which point overload levels occur and are
abated and what actions the MME will take when overload conditions occur in the MME.
Step # Action
1 Setting the default configuration for paging overload.
user@host% set mme-sgsn engineering paging-overload minor-ovld enable minor-onset 325 minor-abate
300 paging-delay-minor 10 paging-reject-minor 0 major-ovld enable major-onset 375 major-abate 350
paging-delay-major 20 paging-reject-major 0 critical-ovld enable critical-onset 425 critical-
abate 400 paging-delay-critical 40 paging-reject-critical 0
user@host% show mme-sgsn engineering paging-overload

minor-ovld enable;
minor-onset 325;
minor-abate 300;
paging-delay-minor 10;
paging-reject-minor 0;
major-ovld enable;
major-onset 375;
major-abate 350;
paging-delay-major 20;
paging-reject-major 0;
critical-ovld enable;
critical-onset 425;
critical-abate 400;
paging-delay-critical 40;

56
MME Configuration
Step # Action
paging-reject-critical 0;
2 Modify the paging overload parameters.
user@host% set mme-sgsn engineering paging-overload minor-onset 325
user@host% show mme-sgsn engineering paging overload

minor-ovld enable;
minor-onset 325;
minor-abate 300;
paging-delay-minor 10;
paging-reject-minor 0;
major-ovld enable;
major-onset 375;
major-abate 350;
paging-delay-major 20;
paging-reject-major 0;
critical-onset 425;
critical-abate 400;
paging-delay-critical 40;
paging-reject-critical 0;
3 Set configuration for S1 overload.
user@host% set mme-sgsn engineering s1-overload zero-rel-cap-subs-trigger sub-ovld-major zero-

rel-cap-cong-trigger congestion-minor zero-rel-cap-duration 10 ovld-start-impact 10 ovld-start-
duration 10 ovld-start-minor-cause no-rrc-for-non-emg-modt ovld-start-major-cause no-rrc-for-non-
emg-sig ovld-start-critical-cause no-rrc-for-non-emg-sig
user@host% show mme-sgsn engineering s1-overload
zero-rel-cap-subs-trigger sub-ovld-major;
zero-rel-cap-cong-trigger congestion-minor;
zero-rel-cap-duration 10;
ovld-start-impact 10;
ovld-start-duration 10;
ovld-start-minor-cause no-rrc-for-non-emg-modt;
ovld-start-major-cause no-rrc-for-non-emg-sig;
ovld-start-critical-cause no-rrc-for-non-emg-sig;
4 Modify the S1 overload parameters.
user@host% set mme-sgsn engineering s1-overload zero-rel-cap-subs-trigger sub-ovld-major
user@host% show mme-sgsn engineering s1-overload

zero-rel-cap-subs-trigger sub-ovld-major;
zero-rel-cap-cong-trigger congestion-minor;
zero-rel-cap-duration 10;
ovld-start-minor-cause no-rrc-for-non-emg-modt;
ovld-start-major-cause no-rrc-for-non-emg-sig;
ovld-start-critical-cause no-rrc-for-non-emg-sig;
4.2.22 Capacity and engineering
Step # Action
1 Modify and display the SC engineering configuration details.

57
MME Configuration
Step # Action
user@host% set mme-sgsn engineering sc-engineering pdn-average 105 dedicated-bearer-average 200
apn-average 200 csg-average 200
user@host% show mme-sgsn engineering sc-engineering

pdn-average 105;
dedicated-bearer-average 200;
apn-average 200;
csg-average 200;
2 Configure S1 capacity on MME.

This configures the maximum number of eNodeBs supported per S1 Listener.
user@host% set mme-sgsn engineering s1-capacity max-enodebs 16
user@host% show mme-sgsn engineering s1-capacity

max-enodebs 16;
3 Configure the capacity limit for each CALLP VM.

This configures the maximum number of subscribers to be supported per CALLP in units of thousand
subscribers.
Syntax:
user@host% set mme-sgsn engineering sc-capacity <callp-service-id> subs-per-su <subs-per-su>
user@host% set mme-sgsn engineering sc-capacity 0 subs-per-su 400
user@host% show mme-sgsn engineering sc-capacity

sc-capacity 0 {
subs-per-su 400;
}
4.2.23 Single Radio Voice Call Continuity (SRVCC)

Single Radio Voice Call Continuity (SRVCC) functionality is defined in TS 23.216v10.2.0 and TS
29.280v10.3.0. SRVCC functionality enables a SRVCC-capable UE to seamlessly move an active
IMS voice call (in PS domain) from LTE coverage to legacy circuit domain. The following types of
SRVCC HO are supported by this feature:
 E-UTRAN to GERAN without DTM support
 E-UTRAN to GERAN with DTM without DTM HO
 E-UTRAN to UTRAN without PS HO
 E-UTRAN to UTRAN with PS HO
Follow these actions to implement this feature.
Step # Action
1 Configure the gtp mobility profile version to release 10.

58
MME Configuration
Step # Action

user@host% show mme-sgsn interface gtp profile mobility
ip-address-v4 172.18.249.17;
ip-address-v6 ::;
dscp-mark de;
echo-interval 300;
n3-echo-request 8;
t3-response 5;
n3-request 2;
2 Configure the s1 interface version to release 10.

version 10.6.0;
3 Configure the s6 interface version to release 10.

version 10.7.0;
4 Enable the SRVCC feature, and check sv path usage.
user@host% set mme-sgsn feature control srvcc status on
user@host% show mme-sgsn feature control srvcc

srvcc status on;
user@host> show mme-sgsn interface sv path detail

ROUTING PATH
IP ADDRESS INSTANCE STATUS LOCATION SERVICE VERSION
---------------------------------------------------------------
172.16.236.30 EPCCore01 running vsim051 sig-0 2
[ok][2014-05-23 10:00:45]
4.2.24 IMS Emergency Call

Emergency bearer services are functionalities provided by the network to support IMS emergency
sessions. This feature adds support for Emergency bearer services on the MME. An emergency
bearer could be a default EPS bearer which was activated for emergency, or any dedicated EPS
bearer associated to this default EPS bearer.
A UE can request for emergency services using one of two available procedures:

59
MME Configuration
 E-UTRAN Initial Attach procedure with ‘emergency’ indicators
 PDN Connectivity procedures with ‘emergency’ indicators
Follow these steps to provision IMS emergency call functionality.
Step # Action
1 Verify that attributes ‘max-pdn-conn-per-ue’ and ‘max-bearers-per-ue’ in mme-sgsn interface nas esm
are at least 2.
Use the modify command if they are not.
user@host% set mme-sgsn interface nas esm max-bearers-per-ue 7 max-pdn-conn-per-ue 8
esm-info-t3489 4;
pgw-ip-type ipv4;
2 Set the gtp mobility profile to release 10.
user@host% set mme-sgsn feature control ims-emergency status on
4 Set/ modify attributes if need be.
user@host% set mme-sgsn feature ims-emergency emg-user-option all-ues apn-network-id emergency

apn-operator-id use-serving-plmn qci-default-bearer 5 arp-priority-default-bearer 1 apn-ul-ambr
32 apn-dl-ambr 32 pgw-hostname EASTPGW pdn-type ipv4 pgw-ip-address1 137.168.69.23 pgw-ip-
address2 0.0.0.0 pgw-protocol-type gtp imei-check-during-emg-attach disable skip-authentication
enable emg-mobile-reachable-timer t3412plus1 deactivate-emg-pdn-after-srvcc enable
4.2.25 Multimedia Priority Service

This feature introduces the Multimedia Priority Service (MPS) on the MME. During emergency
situations (e.g. floods, hurricanes, earthquakes, terrorist attacks), government and emergency
management officials and other authorized users may rely on public network services for
communication. MPS allows authorized users to obtain preferential treatment over normal users by
providing favored access to the next available radio resource on a priority basis before normal users.
MPS also allows authorized users the ability to communicate during congestion conditions when
session and bearer establishment attempts are normally blocked. Follow these actions to enable
MPS.

60
MME Configuration
Step # Action
1 Verify that attributes ‘max-pdn-conn-per-ue ‘and ‘max-bearers-per-ue’ in interface nas esm are at least
2.
Use the modify command if they are not.
user@host% set mme-sgsn interface nas esm max-bearers-per-ue 7 max-pdn-conn-per-ue 8
esm-info-t3489 4;
pgw-ip-type ipv4;
2 Set the following interface versions to Rel 10: s1-if, s6-if, gtp and sgs-if

user@host% set mme-sgsn interface sgs sgs-if version 10.9.0
user@host% set mme-sgsn feature control multimedia-priority-service status on
4 (optional) Modify MPS ARP limit (default – 1)
user@host% set mme-sgsn subscriber nodal-qos mps-arp-limit 2
5 Set overload start cause attributes if need be.
user@host% set mme-sgsn engineering s1-overload ovld-start-minor-cause no-rrc-for-non-emg-modt

ovld-start-major-cause no-rrc-for-non-emg-sig ovld-start-critical-cause no-rrc-for-non-emg-sig
4.2.26 HSS Based NPLI

This mechanism for NPLI (Network Provided Location Information) retrieval is provided over the Sh
interface which is between HSS and the Application Server (AS). For a Mobile Terminated (MT) or
Mobile Originated (MO) session, the AS requests the location information from the HSS using the
existing Sh interface.
When the UE attaches to the network, as part of update location request (ULR) the NPLI capabilities
of the MME/SGSN is provided to the HSS, if the feature is turned on. The MME/SGSN indicates
support of State/Location Information Retrieval and UE time zone retrieval for the UE.
When the MME/SGSN supports NPLI retrieval, the HSS will query for user state, location information,
UE time zone information in a subsequent Insert Subscriber Data Request (IDR) towards that

61
MME Configuration
MME/SGSN. The MME/SGSN will send the response back to HSS with the UE state, location
information, UE Time Zone in Insert Subscriber Data response (IDA).
In this method of NPLI retrieval, the following UE information may be retrieved:
 User State
 E-UTRAN-Cell-Global-Identity (eCGI)
 Tracking-Area-Identity (TAI)
 Cell-Global-Identity (CGI)
 Location-Area-Identity (LAI)
 Service-Area-Identity (SAI)
 Routing-Area-Identity (RAI)
 Age of Location
 UE Time zone
Follow these steps to enable HSS based NPLI.
Step # Action
1 Verify/set the s6-if to Rel 10.
2 Turn the feature on via the feature control table.
user@host% set mme-sgsn feature control hss-npli status on
3 (optional) Enable ue-timezone to support an MME with UE Time Zone reporting towards the HSS.
user@host% set mme-sgsn interface s6 s6-if t-ads-retrieval enable
4 (optional) Enable support for S1AP location reporting to the eNB.
user@host% set mme-sgsn interface s1 s1-if routing-instance1 EPCAccess01 routing-instance2

EPCAccess02 sctp-profile s1defaultsctp ip-address1-v4 172.18.249.1 ip-address2-v4 172.18.249.11
ip-address1-v6 0:0:0:0:0:0:0:0 ip-address2-v6 0:0:0:0:0:0:0:0 port 36412 time-to-wait 60 reloc-
prep-timer 3 csg-expiration-release-timer 5 handover-resource-release-timer 5 lrc-timer-direct 5
reloc-overall-timer 5 ue-context-modification-timer 5 ue-context-release-timer 5 dscp-mark de
inter-rat-indirect-forwarding never indirect-data-fwd-ip-address 0.0.0.0 enb-alarm-clear-time 24
version 10.7.0 location-reporting-control disable wait-for-tau-timer 5 sgw-gtpu-dual-tla-ip-
filter enable
4a Enable the location reporting.
user@host% set mme-sgsn interface s1 s1-if location-reporting-control enable

62
MME Configuration
4.2.27 Location Service

Location service (LCS) furnishes users with information about the physical location of a UE. This
positioning information is typically used by:
 Value added services LCS Clients
 PLMN Operator LCS Clients
 Emergency Services LCS Clients
 Lawful Intercept Clients
The SLs process is added for the SLs interface. This is an optional process that resides in a CallP VM
together with the subscriber control processes. It is created when:
 the sls-if is configured
 at least one E-SMLS is linked to the callp
In the following activation steps, we assume that a callp VM is already established and a diameter
process is already added.
Step # Action
1 Add the slg-if:
Syntax:
user@host% set mme-sgsn interface slg slg-if gmlc-realm <gmlc realm> request-timer <timer value>
request-retry <retry times> version <version>
To use predefined default values:
user@host% set mme-sgsn slg slg-if gmlc-realm <gmlc realm>
Examples:
user@host% set mme-sgsn slg slg-if gmlc-realm affirmed-cta.com request-timer 5 request-retry 0
version 10.1.0
user@host% show mme-sgsn interface slg

slg-if {
gmlc-realm affirmed-cta.com;
request-timer 5;
request-retry 0;
version 10.1.0;
}
2 Add the gmlc:
Syntax:
user@host% set mme-sgsn interface gmlc <gmlc-number> host-identity <host identity> gmlc-usage
<regular|emergency|roamer|emergency-regular>
user@host% set mme-sgsn interface slg gmlc <gmlc-number> host-identity <host identity>
Examples:
user@host% set mme-sgsn interface slg gmlc 460161003029 host-identity host1 gmlc-usage emergency-

63
MME Configuration
Step # Action
regular
user@host% show mme-sgsn interface slg gmlc 460161003029

host-identity host1;
gmlc-usage emergency-regular;
3 Add the sctp-profile for sls:

Syntax:
user@host% set mme-sgsn interface sctp <sctp profile name> rto-initial <RTO initial> rto-min <RTO
minimum value> rto-max <RTO maximum value> path-max-retrans < path max retransmits> association-
init-max-transmit <association INIT chunk max retransmits> association-max-retrans <association
max retransmits> no-delay <true/false> max-out-stream <max out stream> max-in-stream <max in
stream> hb-interval <Heart-beat interval> rx-buffer-size <receive buffer size> tx-buffer-size
<transmit buffer size> sack-delay <sack delay value> sack-frequency <sack frequency>
user@host% set mme-sgsn interface sctp <sctp profile name>
Examples:
user@host% set mme-sgsn interface sctp sctpSls rto-initial 500 rto-min 250 rto-max 2000 path-max-
frequency 2
user@host% show mme-sgsn interface sctp sctpSls

rto-initial 500;
rto-min 250;
rto-max 2000;
path-max-retrans 2;
no-delay true;
max-out-stream 1;
max-in-stream 1;
hb-interval 30;
sack-delay 200;
sack-frequency 2;
4 Add the virtual router for sls:

Syntax:
user@host% set routing-instances <name> instance <type>
Example:
user@host% set routing-instances EPCCore01 instance virtual-router
5 Add the sls-if:

Syntax:
user@host% set mme-sgsn interface sls sls-if routing-instance1 <routing instance name> routing-
instance2 <routing instance name> sctp-profile <sctp profile name> local-ip-address1 <local IP
address 1> local-ip-address2 <local IP address 2 for multi-homing> port <port number> location-
request-t3x01 <T3x01 value> reset-request-t3x02 <T3x02 value> reset-request-retry <retry times>
version <version> dscp-mark <dscp mark> max-transactions-per-peer <maximum transactions per peer>

user@host% set mme-sgsn interface sls sls-if routing-instance1 <routing instance name> routing-
instance2 <routing instance name> sctp-profile <sctp profile name> local-ip-address1 <local IP
address 1>

64
MME Configuration
Step # Action
Example:
user@host% set mme-sgsn interface sls sls-if routing-instance1 EPCCore01 routing-instance2 0
sctp-profile sctpSls local-ip-address1 192.168.40.23 local-ip-address2 0.0.0.0 port 9082
location-request-t3x01 60 reset-request-t3x02 3 reset-request-retry 0 version 10.4.0 dscp-mark de
max-transactions-per-peer 5000
user@host% show mme-sgsn interface sls sls-if

routing-instance2 0;
sctp-profile sctpSls;
local-ip-address1 192.168.40.23;
local-ip-address2 0.0.0.0
port 9082;
location-request-t3x01 60;
location-request-retry 0;
reset-request-t3x02 3;
reset-request-retry 0;
version 10.4.0;
dscp-mark de;
max-transactions-per-peer 5000;
6 Add the e-smlc-pool:

Syntax:
user@host% set mme-sgsn service-area tracking-area<plmn-id> tac <tac> e-smlc-pool <pool name>
service-area <service area>
Examples:
user@host% set mme-sgsn service-area tracking-area 000000 tac 0x0000 e-smlc-pool pool1 service-
area global
user@host% show mme-sgsn service-area tracking-area e-smlc-pool pool1

service-area global;
When a TA entry does not previously exist (initial creation):
cli% set mme-sgsn service-area tracking-area 50631 tac 0x1001 ims-support disable emergency-
support disable e-smlc-pool-name esmlcPool2
OR, if an existing TA entry is modified for the pool name:

cli% set mme-sgsn service-area tracking-area 50631 tac 0x1001 e-smlc-pool-name esmlcPool2
OR, for a PLMN:

cli% set mme-sgsn service-area tracking-area 50502 tac 0x1001 e-smlc-pool-name esmlcPool3
…
cli% set mme-sgsn service-area tracking-area 50502 tac 0x10ff e-smlc-pool-name esmlcPool3
7 Add the e-smlc:

Syntax:
user@host% set mme-sgsn interface sls e-smlc <e-smlc-id> callp-service-id <callp service id> e-
smlc-pool <e-smlc pool name> ip-address1 <e-smlc IP address> ip-address2 <e-smlc IP address for
multi-homing>
To use predefined default values of service-area:
user@host% set mme-sgsn interface sls e-smlc <e-smlc-id> callp-service-id <callp service id> e-
smlc-pool <e-smlc pool name> ip-address1 <e-smlc IP address>
Examples:
user@host% set mme-sgsn interface sls e-smlc 1 callp-service-id 0 e-smlc-pool pool1 ip-address1
192.168.40.23 ip-address2 0.0.0.0

65
MME Configuration
Step # Action
user@host% show mme-sgsn interface sls e-smlc
e-smlc 1 {
callp-service-id 0;
e-smlc-pool pool1;
ip-address1 172.16.236.63;
}
8 Modify the subscriber-plmn:
Syntax:
user@host% set mme-sgsn subscriber subscriber-plmn <default|plmn-id> mt-lr <enable|disable> mo-lr
<disable>
user@host% set mme-sgsn subscriber subscriber-plmn
Examples:
user@host% set mme-sgsn subscriber subscriber-plmn 31298 mt-lr enable mo-lr disable
user@host% show mme-sgsn subscriber subscriber-plmn 31298

protocol-type gtp;
suppress-hss-notify disable;
ims-support disable;
native-mme-group-ids none;
lgw-protocol-type pmip;
mt-lr enable;
mo-lr disable;
9 Add the avp-mbit-override if needed:

Syntax:
user@host% set mme-sgsn interface diameter avp-mbit-override <avp-code> application-identifier
<s6|s13|slg|base>
user@host% set mme-sgsn interface diameter avp-mbit-override <avp-code>

Examples:
user@host% set mme-sgsn interface diameter avp-mbit-override 2500 application-identifier slg
user@host% show mme-sgsn interface diameter avp-mbit-override

avp-mbit-override 2500 {
application-identifier slg;
}
10 Turn the feature on in feature-control table:
Syntax:
user@host% set mme-sgsn feature control lcs status <on|off>
Examples:
user@host% set mme-sgsn feature control lcs status on
user@host% show mme-sgsn feature control lcs

status on;
The lcs entity is automatically added with the following default value:
name lcs;
loc-notification-timer-tlcsn 15;
lcs-over-sgs disable;
If you wish to change one of them, use one of the following commands:

66
MME Configuration
Step # Action
user@host% set mme-sgsn feature lcs loc-notification-timer-tlcsn 20
11 Commit the configurations:
user@host% commit
12 Make sure the SCTP association to E-SMLC is operational:
user@host> show mme-sgsn interface sls e-smlc detail | tab

E SMLC_ID CALLP SERVICE ID E SMLC POOL IP ADDRESS1 IP ADDRESS2 CONNECTION STATUS
1 0 pool1 192.168.40.23 0.0.0.0 up
13 Make sure the SCTP association to GMLC is operational:
admin@vmcg03-0 07:27:08> show mme-sgsn interface diameter peer detail

mme-sgsn interface diameter peer
host-identity host1
ip-address 172.16.236.1
ip-address2 0.0.0.0
port-number 3868
status open
process-name callp0_SU_0
negotiated-app-id SLg

67
5 SGSN Configuration
5.1 SGSN Mandatory Configuration

With the introduction of the S3, S4, and S6d interfaces as of MME6.0, the SGSN has the option of
interworking with EPC network elements, including MME, SGW, and HSS respectively. This leads to
three possible deployment models for SGSN:
 Gn-SGSN refers to an SGSN which supports the Gn interface to GGSN, but does not support the
S4 interface to SGW.
 S4-SGSN refers to an SGSN which supports the S4 interface, but does not support the Gn
interface.
 Simply SGSN refers to an SGSN supporting both the S4 and the Gn interfaces.
An S4-SGSN may optionally use S6d and S13 interfaces as well, or continue with Gr and Gf
interfaces for older networks. The S3 and S16 interfaces are mobility variants of GTP path, and the
S4 interface is a tunnel variant of GTP path. The S4-SGSN requires R9 or greater standard
compliancy on the relevant interfaces; R8 variants are not supported.
The following table provides the mapping between the virtual machine type and the SGSN
applications that reside on that virtual machine type. This table is all inclusive, meaning it contains
both mandatory and optional elements.
Table 5. VM Type to SGSN Application Mapping
Virtual Machine Type SGSN Application
MGMT CSL, Trace, CM, PM, FM
RM RM, LI, SBc, Ga, UPSM
CALLP SC, SGS, DC, Iu, Ge
SIG UPM, ASP, IPSP, TCAP
DATA SD, GB
SLB LB
5.1.1 Virtual Machine Configuration

Nodes/virtual machines and applications on the SGSN are managed by the Nodal Manager (NM) and
the Life Cycle Manager (LCM) respectively. Virtual machine instance creations are done through the
OpenStack UI and operator is advised to refer to the UI for the actual VM instance name and instance
number to use in the commands below.

68
SGSN Configuration
Virtual machines are pre-defined to be home for a set of applications, with some being optional.
Optional processes are those that can be enabled through configuration of a specific interface or the
enabling of a feature through CLI.
The following steps describe the definition of the virtual machines required for a typical SGSN
configuration.
Step # Action
1 Define the MGMT VM which governs the following processes: CSL, Trace, CM, PM, FM

2 Define the CALLP VM which governs the following processes: SC, SGS, DC, Iu, Ge

3 Define the SIG VM which governs the following processes: UPM, ASP, IPSP, TCAP
user@host% set mme-sgsn system sig unit 0 vm-instance vse01-vm03
4 Define the DATA VM which governs the following processes: SD, Gb
user@host% set mme-sgsn system data unit 0 vm-instance vse01-vm04
5 Define the RM VM which governs the following processes: RM, LI, SBc, Ga, UPSM

5.1.2 NAS (Non-Access Stratum) Configuration
5.1.2.1 NAS GMM
The setting of NAS GMM is shown in the following table. The config values assigned are default
values. They need to be modified for specific network operation.
Step # Action
1 Set the GMM NAS parameters.
user@host% set mme-sgsn interface nas gmm mobile-reachable-timer 58 cancel-location-timer 20

paging-timer-t3313 8 paging-retry-n3313 1 nwk-init-detach-timer-t3322 6 nwk-init-detach-retry-
n3322 4 id-request-timer-t3370 6 id-request-retry-n3370 4 radio-priority-level 4 auth-ciphering-
timer-t3360 6 auth-ciphering-retry-n3360 4 reset-ppf-radio-status disable
ptmsi-realloc-timer-t3350 6 ptmsi-realloc-retry-n3350 4 t3-tunnel-timer 12 opt-authentication-
control off send-old-and-new-tlli enable second-auth-attempts disable ready-timer-t3314 44
periodic-ra-update-timer-t3312 28 gprs-ciphering-algorithms no-ciphering umts-ciphering-
algorithms no-ciphering attach-acc-force-standby disable detach-req-force-standby disable detach-
acc-force-standby disable intra-rau-acc-force-standby disable inter-rau-acc-force-standby disable
rau-reject-force-standby disable umts-integrity-algorithms uia1 ptmsi-lifetime 12 periodic-rau-
tmr-t3312-offload 4 ims-voice-sgsn disable cancel-location-detach-cause gprs-service-not-allowed-
7

69
SGSN Configuration
5.1.2.2 NAS SM
The setting of NAS SGSN SM is shown in the following table. The config values assigned are default
values and they do not require adjustment. However, depending on other network criteria, some of
these SGSN parameters may need adjustment. In particular, the APN defaults are meant to match
what is configured in the operator’s DNS servers if those features are desired.
Step # Action
1 Set the SM NAS parameters.
Show the defaults after new install:
user@host% show mme-sgsn interface nas sm
nwk-pdp-deact-timer-t3395 8;
nwk-pdp-deact-retry-n3395 4;
ppp-def-apn-network-id default.ppp-apnni.com;
ip-def-apn-network-id default.ip-apnni.com;
def-apn-operator-id default.apnoi.gprs;
nwk-pdp-modify-timer-t3386 8;
nwk-pdp-modify-retry-n3386 4;
pdp-activations-per-mobile 7;
ipv6-enduser-address disable;
route-advance enable;
qos-negotiation disable;
qos-upgrade-support enable;
local-qos-control never;
old-sgsn-buffering disable;
user@host% set mme-sgsn interface nas sm nwk-pdp-deact-timer-t3395 8 nwk-pdp-deact-retry-n3395 4

ppp-def-apn-network-id default.ppp-apnni.com ip-def-apn-network-id default.ip-apnni.com def-apn-
operator-id default.apnoi.gprs nwk-pdp-modify-timer-t3386 8 nwk-pdp-modify-retry-n3386 4 pdp-
activations-per-mobile 8 ipv6-enduser-address disable route-advance enable qos-negotiation
disable qos-upgrade-support disable local-qos-control never old-sgsn-buffering enable secondary-
pdp-context enable
Adjust any of the APN defaults, if used, to match DNS configuration:

user@host% set mme-sgsn interface nas sm def-apn-operator-id <operator-value>.apnoi.gprs
user@host% set mme-sgsn interface nas sm ppp-def-apn-network-id <operator-value>
user@host% set mme-sgsn interface nas sm ip-def-apn-network-id <operator-value>
5.1.3 Gr/S6d HLR/HSS Interface

For a Gn-SGSN, the Gr interface to an HLR is mandatory, and S6d is not supported. For a S4-SGSN,
you may chose between Gr over SIGTRAN to the HLR, S6d over DIAMETER to the HSS (potentially
the same node as HLR), or both. Selection between Gr and S6d is based on IMSI range of the UE
and the hss-hlr-routing table that is configured on the SGSN. A combined MME/S4-SGSN or a stand-
alone S4-SGSN retrieves authentication information over the Gr interface for an EPC subscriber
located in a GERAN/UTRAN coverage area, and then retrieves subscription information for the EPC
capable subscriber over the S6a interface. This can be used by an operator who has an HSS
deployment that does not support the S6d interface. This development also provides the flexibility to
retry the authentication or subscription information over Gr interface, if the attempt to retrieve over S6
interface fails.

70
SGSN Configuration
5.1.3.1 Gr SIGTRAN Interface
To configure the Gr interface, you will need to link the SCTP/M3UA information to the local SS7
information. The rest of the Gr interface will be configured based on the network design. At a
minimum, one remote peer and GTT transaction needs to be configured to route messages external
and internal to the SGSN.
Step # Action
user@host% set mme-sgsn interface sctp sctpSgsn rto-initial 500 rto-min 100 rto-max 1000 path-
max-retrans 2 association-init-max-transmit 2 association-max-retrans 2 no-delay true max-out-
stream 10 max-in-stream 10 hb-interval 30
user@host% show mme-sgsn interface sctp sctpSgsn
rto-initial 500;
rto-min 100;
rto-max 1000;
path-max-retrans 2;
no-delay true;
max-out-stream 10;
max-in-stream 10;
hb-interval 30;
2 Configure the M3UA layer.
user@host% set mme-sgsn interface m3ua m3uaSigtran sctp-profile sctpSgsn audit-interval 30000
multiple-network-appearances enable max-deactivate-attempts 3 fsm-timeout 2000 network-indicator
natl cong-onset-level1 auto-configure cong-abatement-level1 auto-configure cong-onset-level2
auto-configure cong-abatement-level2 auto-configure cong-onset-level3 auto-configure cong-
abatement-level3 auto-configure cong-report-frequency 8 reconnect-timer 10
user@host% show mme-sgsn interface m3ua m3uaSigtran

sctp-profile sctpSgsn;
audit-interval 30000;
multiple-network-appearances enable;
max-deactivate-attempts 3;
fsm-timeout 2000;
network-indicator natl;
cong-onset-level1 auto-configure;
cong-abatement-level1 auto-configure;
cong-report-frequency 8;
reconnect-timer 10;
3 Configure the local SS7 pointcode and E.164 number. A loopback interface is required for the ASP IP
address.
user@host% set mme-sgsn interface ss7 ss7 sgsn-number 601001001001 signaling-variant ansi map-
cgpa-routing-indicator global-title version 10.8.0 dscp-mark de map-importance-level auto-
configure bssap-importance-level auto-configure cap-importance-level auto-configure map-
subsystem-number standard bssap-subsystem-number 192 cap-subsystem-number unused
user@host% show mme-sgsn interface ss7 ss7

sgsn-number 601001001001;
signaling-variant ansi;
map-cgpa-routing-indicator global-title;

71
SGSN Configuration
Step # Action
version 10.8.0;
dscp-mark de;
map-importance-level auto-configure;
bssap-importance-level auto-configure;
cap-importance-level auto-configure;
map-subsystem-number standard;
bssap-subsystem-number 192;
cap-subsystem-number unused;
user@host% set mme-sgsn interface ss7 app-server default

user@host% set mme-sgsn interface ss7 asp-instance unit 1 routing-instance EPCCore01 ip-address
172.18.249.21 app-server-name default port 2905
Repeat addition for each SIGTRAN ASP required. Each Sigtran instance (VM) requires a unique IP address.
user@host% set mme-sgsn interface ss7 m3ua m3ua-prof-name m3uaAsp 5.200.3
user@host% show mme-sgsn interface ss7 m3ua

m3ua-prof-name m3uaAsp;
4 Modify the SCCP parameters (network specific).
user@host% set mme-sgsn interface ss7 sccp stat-info-timer 7

user@host% set mme-sgsn interface ss7 sccp congestion-timer 5
user@host% set mme-sgsn interface ss7 sccp attack-timer 60
user@host% set mme-sgsn interface ss7 sccp decay-timer 5
user@host% set mme-sgsn interface ss7 sccp unknown-destination-alarm enable
user@host% set mme-sgsn interface ss7 sccp reassembly-timer 10
user@host% show mme-sgsn interface ss7 sccp

stat-info-timer 7;
congestion-timer 5;
attack-timer 60;
decay-timer 5;
unknown-destination-alarm enable;
reassembly-timer 10;
5 Set the TCAP parameters (network specific).
user@host% set mme-sgsn interface ss7 tcap xudt-option on e214-trans-type 10
user@host% show mme-sgsn interface ss7 tcap

xudt-option on;
e214-trans-type 10;
max-map-transactions 2000;
max-map-invokes 3000;
max-cap-transactions 2000;
max-cap-invokes 3000;
6 Create the Gr interface.
user@host% set mme-sgsn interface gr gr-if sai-message-version v3 odb-sms disable send-rej-for-

roaming-restrict disable automatic-device-detection enable num-of-imsi-digits 6 request-timer 13
ugl-retry 4 sai-retry 3 afr-retry 2 mc-fallback-timer 21 sai-vector-limit 4 odb-ps disable
user@host% show mme-sgsn interface gr gr-if

sai-message-version v3;
odb-sms disable;
send-rej-for-roaming-restrict disable;
automatic-device-detection enable;
num-of-imsi-digits 6;
request-timer 13;

72
SGSN Configuration
Step # Action
ugl-retry 4;
sai-retry 3;
afr-retry 2;
mc-fallback-timer 21;
sai-vector-limit 4;
odb-ps disable
7 Configure a remote SS7 peer (repeat to configure multiple remote nodes).
user@host% set mme-sgsn interface ss7 remote-destination <destination point code> <remote-
subsystems (SSN)> xudt-option enable ludt-option disable
user@host% show mme-sgsn interface ss7 remote-destination 100.90.200

xudt-option enable;
ludt-option disable;
remote-subsystems 6;
user@host% set mme-sgsn interface ss7 peer <peer name> app-server-name <app-server name> ip-
address1 <Peer IP Address> peer-type ipspSe association-creation initiate 0.0.0.0 <Peer Port>
standard 0
user@host% show mme-sgsn interface ss7 peer HLR01

app-server-name default;
ip-address1 172.16.254.150;
ip-address2 172.16.254.160;
peer-type ipspSe;
association-creation initiate;
port 2905;
compat-mode standard;
network-appearance 0;
ALERT: For Gr, the SGSN is the SCTP Client. Set the association-creation to initiate.
Alert: For SIGTRAN m3ua ss7 peer configuration attribute 'association-creation' should always remain as 'initiate'
(the default).
Syntax:
user@host% set mme-sgsn interface ss7 dest-peer-map <destination point code> g-peer-name <g-peer
name>
user@host% show mme-sgsn interface ss7 dest-peer-map

dest-peer-map 100.90.200 HLR01;
8 Add the SS7 GTT Result.

Syntax:
user@host% set mme-sgsn interface ss7 gtt-result <instance> destination-point-code <destination
point code> routing-indicator <route-on-gt/route-on-ssn> use-original-gtai <enable/disable>
subsystem <SSN of GTT result> global-title-indicator <gti0/gti1/gti2/gti3/gti4> translation-type
<0..255> numbering-plan <0..15> nature-of-addr-indicator <0..127> global-title-addr-info <global
title address info>
Minimum result is two. One for outbound traffic and one for inbound traffic.
GTT Result for HLR01:
user@host% set mme-sgsn interface ss7 gtt-result 1 destination-point-code 100.90.200 routing-
indicator route-on-gt use-original-gtai enable subsystem 6 global-title-indicator gti2
translation-type 10 numbering-plan 1 nature-of-addr-indicator 4 global-title-addr-info
358203060000010

73
SGSN Configuration
Step # Action
GTT Result for inbound traffic for SGSN MAP:
indicator route-on-ssn use-original-gtai enable subsystem 149 global-title-indicator gti2
translation-type 10 numbering-plan 1 nature-of-addr-indicator 4 global-title-addr-info
01001001001
user@host% show mme-sgsn interface ss7 gtt-result 1
destination-point-code 100.90.200;
routing-indicator route-on-gt;
use-original-gtai enable;
subsystem 6;
global-title-indicator gti2;
translation-type 10;
numbering-plan 1;
nature-of-addr-indicator 4;
global-title-addr-info 358203060000010;

routing-indicator route-on-ssn;
subsystem 149;
numbering-plan 1;
9 Configure the GTT Entries.

Syntax:
user@host% set mme-sgsn interface ss7 gtt-entry <instance> lower-gtai <lower global title
address info> upper-gtai <upper global title address info> primary-result <primary result>
secondary-result <secondary result> global-title-indicator <gti0/gti1/gti2/gti3/gti4>
translation-type <translation type> numbering-plan <numbering plan> nature-of-address-indicator
<nature of address indicator>
SGSN MAP Inbound GTT:

user@host% show mme-sgsn interface ss7 gtt-entry 3
lower-gtai "6010010#";
upper-gtai 0;
primary-result 3;
secondary-result 3;
numbering-plan 1;
HLR MAP Outbound GTT e.164 for HLR:

upper-gtai 0;
primary-result 1;
secondary-result 1;
numbering-plan 1;
E.214 Outbound GTT (ITU):


74
SGSN Configuration
Step # Action
upper-gtai 0;
primary-result 2;
secondary-result 2;
translation-type 0;
numbering-plan 7;
10 PLMNID to CC/NC Mapping.

This table is used for PLMN mapping to Country and Network Code.
Syntax:
user@host% set mme-sgsn interface ss7 address-translation <plmn id> country-code <country code>
network-code <network code>
user@host% set mme-sgsn interface ss7 address-translation 24405 country-code 358 network-code 20
user@host% show mme-sgsn interface ss7 address-translation 24405
country-code 358;
network-code 20;
11 IMSI routing to HLR via Gr interface.

In this example for IMSI of prefix 228, they get routed to Gr interface (as opposed to S6).
user@host% set mme-sgsn imsi-routing hss-hlr-routing 228 interface-type gr routing-option
standard hss-realm nortel.com
user@host% show mme-sgsn imsi-routing hss-hlr-routing 228
interface-type gr;
routing-option standard;
hss-realm nortel.com;
5.1.3.2 S6d - DIAMETER over SCTP Interface
Please refer to the S6 configuration section under MME, as it is common to MME and SGSN. S6a
and S6d are the same interface for a node that is both MME and SGSN.
5.1.4 Gn/S4 and Gp/S3 GTP Interfaces

For a Gn-SGSN (or S4-SGSN with data-plane enabled), in addition to the Gn and Gp interfaces,
there is a need to configure the GTP-U interface for the user plane. The Gn-SGSN also includes
support for older GTPV1 interfaces, but that is implicitly supported on the same interfaces as GTPV2.
For an S4-SGSN, the GTP protocol compliance versions must be 9 or greater.
For a greater understanding of recent changes to GTP, see GTP Feature Overview.
Step # Action
1 Configure the GTP common profile parameters.

75
SGSN Configuration
Step # Action
1a Define the GTP default profile (Gn to GGSN, S4 to SGW).
The following ‘tunnel’ profile is shared for Gn/S4:
Syntax:
user@host% set mme-sgsn interface gtp profile default routing-instance <id> ip-address-v4 <Local
IPV4 address> ip-address-v6 <Local IPV6 address> dscp-mark <DSCP marking for gtp profile> echo-
interval <echo interval> t3-echo-response <echo response timer> n3-echo-request <number of echo
request> t3-response <response timer> n3-request <number of request> inactivity-timer <inactivity
timer> n3-request-session-creation 2 t3-response-session-creation 5 n3-request-bearer-
modification 2 t3-request-bearer-modification 5 n3-request-context-request 2 t3-response-context-
request 5 n3-request-forward-relocation 2 t3-response-forward-relocation 5
user@host> show mme-sgsn interface gtp profile default
ip-address-v4 172.18.249.17;
ip-address-v6 ::;
dscp-mark de;
echo-interval 300;
n3-echo-request 8;
t3-response 5;
n3-request 2;
Optional: If you wish to separate the MME/SGSN source address for S4 and S11 paths, add another gtp-profile
specific to that interface and link it under the interface. This will override the default "tunnel" profile for that selected
interface.
user@host% set mme-sgsn interface gtp profile s4 ip-address-v4 5.6.7.8 routing-instance EPCCore01
user@host% set mme-sgsn interface s4 s4-if gtp-profile s4
2 Define the GTP mobility profile (Gp to SGSN, S3 to MME and S16 to SGSN).
Syntax:
user@host% set mme-sgsn interface gtp profile mobility routing-instance <id> ip-address-v4 <Local
IPV4 address> ip-address-v6 <Local IPV6 address> dscp-mark <DSCP marking for gtp profile> echo-
interval <echo interval> t3-echo-response <echo response timer> n3-echo-request <number of echo
request> t3-response <response timer> n3-request <number of request> inactivity-timer <inactivity
timer> n3-request-session-creation 2 t3-response-session-creation 5 n3-request-bearer-
modification 2 t3-request-bearer-modification 5 n3-request-context-request 2 t3-response-context-
request 5 n3-request-forward-relocation 2 t3-response-forward-relocation 5
Unless specified the Tunnel and Mobility IPs can be the same.
user@host% show mme-sgsn interface gtp profile mobility

ip-address-v4 172.18.249.17;
ip-address-v6 ::;
dscp-mark de;
echo-interval 300;
n3-echo-request 8;
t3-response 5;
n3-request 2;

76
SGSN Configuration
Step # Action
3 S4-SGSN only: Enable the S4 feature, and select treatment for non-epc UE and data plane usage.
user@host% set mme-sgsn feature control s4-sgsn status on

Enable the S-NAPTR based DNS procedures even for Gn based activation.
user@host% set mme-sgsn feature s4-sgsn non-epc-aware-ue-activation gn
Configure whether S4-SGSN data-plane is used when UEs activate sessions in IU mode (never or always)
user@host% set mme-sgsn feature s4-sgsn data-plane always
user@host% show mme-sgsn feature s4-sgsn

non-epc-aware-ue-activation gn;
data-plane always;
4 Gn-SGSN only: Define Gn Profile.

user@host% set mme-sgsn interface gn gn-if gn-tunnel-profile profile1
user@host% set mme-sgsn interface gn gn-if pdp-downselect-version ipv4
user@host% show mme-sgsn interface gn gn-if
gn-tunnel-profile profile1;
pdp-downselect-version ipv4;
5 Gn-SGSN (or S4-SGSN with data-plane): Define the GTP-U interface.

Syntax:
user@host% set mme-sgsn interface gtp-u unit <id> gn-data-routing-instance <id> gn-data-ipaddress
<GTP-U Loopback address>
user@host% set mme-sgsn interface gtp-u unit 0 gn-data-routing-instance EPCCore01 gn-data-
ipaddress 172.18.249.10
user@host% show mme-sgsn interface gtp-u
gn-data-routing-instance EPCCore01;
unit 0 {
gn-data-ipaddress 172.18.249.10;
}
6 Gn-SGSN only: Define the GGSNs (up to 200).

Adding GGSN configuration is optional.
If direct tunnel option is desired, then enable the feature on the SGSN first.
user@host% set mme-sgsn feature control direct-tunnel status on

Syntax:
user@host% set mme-sgsn interface gn ggsn <ggsn-ip-address> name <GGSN name> direct-tunnel
<direct functionality Enable/Disable> blacklisted <GGSN blacklisting>
user@host% set mme-sgsn interface gn ggsn 172.16.241.136 name ggsndt1 direct-tunnel enable
blacklisted false
user@host% show mme-sgsn interface gn ggsn 172.16.241.136

77
SGSN Configuration
Step # Action
name ggsndt1 direct-tunnel enable blacklisted false;
6a Optional: Configure direct tunnel apn screening

The apn list is a comma separated list of APNs. This table is used to disable direct-tunnel for UMTS
SGSN to a GGSN on a per APN basis. This is in addition to the direct tunnel configuration under ‘mme-
sgsn interface gn ggsn direct-tunnel’ which controls the capability to enable on a per GGSN basis. APN
screening takes precedence over per GGSN config on the SGSN.
user@host% set mme-sgsn subscriber direct-tunnel-apn-screening <apn-list>
5.1.5 PLMN configuration

For a standalone Gn-SGSN or S4-SGSN, the PLMNs supporting 2G/3G access must be provisioned
with the 'default' sgsn-pool.
Step # Action
1 Create the SGSN Pool.
user@host% set mme-sgsn service-area sgsn-pool default
2 Create the PLMN to support only 2G or 3G access.
user@host% set mme-sgsn service-area plmn <plmnid> sgsn-pool default

user@host% show mme-sgsn service-area
plmn 10067 {
sgsn-pool default;
}
plmn 10027 {
sgsn-pool Pool1;
}
sgsn-pool {
nri-bit-length 2;
load-balancing enable;
non-broadcast-rai none;
cn-id 1;
}
5.1.6 SGSN Radio Access Interfaces
5.1.6.1 Iu – UMTS/3G Access
The UMTS interface to the radio access equipment (e.g. RNC then BTS), runs over the IP transport
mechanism. Legacy ATM transport is not directly supported by the SGSN. In order to ensure
endpoint redundancy, each RNC should be configured to terminate to two different IPSP instances on
the SGSN, which reside on different IPSP-instances. Additionally, path redundancy is support by
enhancing the IPSP instance to have multi-homed local endpoints. This allows upgrade and in-
service patching procedures to occur and still maintain the Iu connection to each RNC.

78
SGSN Configuration
Step # Action
user@host% set mme-sgsn interface sctp sctpIu rto-initial 500 rto-min 100 rto-max 1000 path-max-
frequency 2
user@host% show mme-sgsn interface sctp sctpSgsn

rto-initial 500;
rto-min 100;
rto-max 1000;
path-max-retrans 2;
no-delay true;
max-out-stream 10;
max-in-stream 10;
hb-interval 30;
sack-delay 200;
sack-frequency 2;
2 Configure the M3UA layer.

user@host% set mme-sgsn interface m3ua m3uaIu sctp-profile sctpSgsn audit-interval 30000
multiple-network-appearances disable max-deactivate-attempts 3 fsm-timeout 2000 network-indicator
natl cong-onset-level1 auto-configure cong-abatement-level1 auto-configure cong-onset-level2
auto-configure cong-abatement-level2 auto-configure cong-onset-level3 auto-configure cong-
abatement-level3 auto-configure cong-report-frequency 8 reconnect-timer 10
user@host% show mme-sgsn interface m3ua m3uaIu
multiple-network-appearances disable;
fsm-timeout 2000;
reconnect-timer 10;
3 Create the Iu-If interface (singleton) with details, and optionally enable HSPA+ feature.
For an S4-SGSN, the Iu standards version must be 9.5.0 or greater.
Determine if the SS7 networking will be ANSI or ITU (this affects the point code formats) and select the
signaling-variant here.
user@host@ set mme-sgsn interface iu iu-if csg-expiration-release-timer 5 reset-ack-timer-tratr

60 reset-timer-trafr 90 reset-retry-trafr 1 sccp-class-of-service connection-less,connection-
oriented sccp-connection-establish-timer 60 sccp-inactivity-test-timer 300 sccp-inactivity-
receive-timer 660 sccp-timer-release 10 sccp-timer-repeat-release 20 sccp-pause-delay-timer 120
trab-assgt-timer 4 trab-assgt-retry 4 reloc-alloc-timer 10 reloc-complete-timer 25 iu-release-
timer 5 iu-signaling-act-timer disable security-mode-timer 5 security-mode-retry 2 srns-rau-timer
5 inter-rat-indirect-forwarding never indirect-data-fwd-ip-address 0.0.0.0 indirect-tunnel-hold-
timer 5 version 9.5.0 reloc-resource-release-timer 5 dscp-mark de signaling-variant itu
user@host% show mme-sgsn interface iu iu-if
csg-expiration-release-timer 5;
reset-ack-timer-tratr 60;

79
SGSN Configuration
Step # Action
reset-timer-trafr 90;
reset-retry-trafr 1;
sccp-class-of-service connection-less,connection-oriented;
sccp-connection-establish-timer 60;
sccp-inactivity-test-timer 300;
sccp-inactivity-receive-timer 660;
sccp-timer-release 10;
sccp-timer-repeat-release 20;
sccp-pause-delay-timer 120;
trab-assgt-timer 4;
trab-assgt-retry 4;
reloc-alloc-timer 10;
reloc-complete-timer 25;
iu-release-timer 5;
iu-signaling-act-timer disable;
security-mode-timer 5;
security-mode-retry 2;
srns-rau-timer 5;
version 9.5.0;
reloc-resource-release-timer 5;
dscp-mark de;
signaling-variant itu;
To add support for the Enhanced SRNS (Serving Radio Network Subsystem) Relocation Procedures as well as
increasing the number of RNCs (Radio Network Controller) supported by the SGSN from 256 to 4096, enable the
hspa-plus feature.
user@host% set mme-sgsn feature control hspa-plus status on
4 Configure the Local Iu Server. A loopback interface is required for the Iu IPSP address.
user@host% set mme-sgsn interface iu ipsp-instance <unit> 0 ip-address1 <Access IP Address1> ip-
address2 <Access IP Address2> routing-instance1 <routing-instance1> routing-instance2 <routing-
instance2> port <Local Port>
user@host# show mme-sgsn interface iu ipsp-instance
0 ip-address1 172.18.249.2 ip-address2 172.18.249.4 routing-instance1 EPCAccess01 routing-
instance2 EPCAccess02 port 3905
As with the Sigtran ASP each instance of the IPSP service unit require a unique ipsp-instance and IP address.
5 Configure Iu M3UA Pointcode.
user@host% set mme-sgsn interface iu m3ua m3ua-profile m3uaIu <local point code> 2.200.3
user@host% show mme-sgsn interface iu m3ua

2.200.3;
m3ua-profile m3uaIu;
6 Create the RNC entry and map to an Iu Service Group – Multiple.

ALERT: with hspa-plus feature, up to 4096 RNC per SGSN and 1024 per SU are allowed
ALERT: without hspa-plus feature, up to 256 RNC per SGSN and 32 per SU are allowed
ALERT: the rnc-id is a 16 bit number, so it may go up to 65535, and the values must be unique across
all PLMN, not just per PLMN, based on the current SGSN implementation.
user@host% set mme-sgsn interface iu rnc 600 destination-point-code 1.200.0 callp-service-id 0

direct-tunnel enable max-iu-connections 1000

80
SGSN Configuration
Step # Action
ALERT: The SGSN will need to be engineered to properly distribute the RNCs across the configured IU Service
Units.
user@host% show mme-sgsn interface iu rnc 600

callp-service-id 0;
direct-tunnel enable;
max-iu-connections 1000;
7 Configure the RNC M3UA Peer – Multiple.
user@host% set mme-sgsn interface iu peer AIRVANAFAP01 port <number> ip-address1 <M3UA peer
process1 ip address> ip-address2 <M3UA peer process2 ip address> peer-type <type of m3ua process>
compat-mode <compatible m3ua mode> association-creation <sctp association to peer> network-
appearance <network appearance>
user@host% show mme-sgsn interface iu peer AIRVANAFAP01
port 2905;
ip-address1 172.16.239.205;
peer-type ipspSe;
network-appearance unused;
8 Configure the RNC Peer Mapping – Multiple.

set mme-sgsn interface iu dest-peer-map <destination point code> <iu-peer name>
Syntax:
user@host% set mme-sgsn interface iu dest-peer-map <destination point code> <peer name>
user@host% set mme-sgsn interface iu dest-peer-map 3.15.1 RNC277
user@host% show mme-sgsn interface iu dest-peer-map

3.15.1 RNC277;
5.1.6.2 Gb – GPRS/2G Access
The Gb interface to the GPRS radio access equipment (BSS, i.e. PCU then BTS) supports IP
(Internet Protocol) or FR (Frame Relay) transport, known as Gb/IP and Gb/FR respectively. Either
Gb/IP or Gb/FR transport is specified when an NSE is provisioned. The maximum number of NSE’s
per SGSN is 600.
For Gb/IP, an NSE may be configured in dynamic mode or static mode, the former being preferable.
For Gb/FR, external equipment for E1/T1 Frame Relay conversion to Ethernet is provided by a
DragonWave Pseudowire Multi-Service Packet Node (PMSPN) Fusion A20.
To support Gb NSE redundancy, an “nsvl-group” is created with two “nsvl” instances, where each
“nsvl” instance is linked to a unique DATA VM. There may be multiple “nsvl-group” instances
depending on the number of NSEs that the SGSN needs to support. Up to 100 NSE’s may be linked
to single nsvl-group.

81
SGSN Configuration
The following example creates one Gb “nsvl-group” with two “nsvl-group nsvl” instances, each linked
to a unique DATA VM, for redundancy. This is required to avoid Gb outages during in-service-
patching and upgrade.
Step # Action
1 Add Gb interface (singleton) to the SGSN. If the Gb/FR option is used, then more parameters are
required to specify local VR and IP. Gb/FR and Gb/IP NSEs can be supported concurrently on an
SGSN, but must use unique IP addresses. The version must be 9 or greater for an S4-SGSN.
short form for Gb IP only system:
user@host% set mme-sgsn interface gb gb-if fr-local-ip-address 0.0.0.0 payload-compression-
override disable rim-addr-err-pdu-status-cause invalid-mandatory-information ms-flow-control-th-
timer disable cancel-th-on-ms-move-to-standby disable alternative-bmax 0 version 9 dscp-mark de
user@host% show mme-sgsn interface gb gb-if
fr-local-ip-address 0.0.0.0;
payload-compression-override disable;
rim-addr-err-pdu-status-cause invalid-mandatory-information;
ms-flow-control-th-timer disable;
cancel-th-on-ms-move-to-standby disable;
alternative-bmax 0;
version 9;
dscp-mark de;
2 Create redundant Gb “nsvl-group” instances for each pair of DATA VM’s – Repeat as needed.
ALERT: For Gb/IP and depending upon PCU implementation, preferably all ‘nsvl-group nsvl’ IP/Port
addresses must be provisioned at each PCU to support ‘dynamic configuration’ of the Gb interface.
However, at minimum one ‘nsvl-group nsvl’ IP/Port address must be provisioned at each PCU.
For Gb/IP, the SGSN also supports ‘static configuration’ over the Gb interface, although ‘dynamic
configuration’ is preferred.
If only Gb/FR is to be provisioned, then routing-instance, ip-address, and port is optional and should not
be specified; if both Gb/FR and Gb/IP is to be provisioned on the service-units then vr-id, ip-address,
and port must be configured.
Create “nsvl-group x nsvl 0” and associate it with a DATA VM:
user@host% set mme-sgsn interface gb nsvl-group <#> nsvl 0 unit-id <#> local-ip-address <ip
address> local-port <#> routing-instance <string>
Create “nsvl-group x nsvl 1” and associate it with its redundant DATA VM:
user@host% set mme-sgsn interface gb nsvl-group <#> nsvl 1 unit-id <#> local-ip-address <ip
address> local-port <#> routing-instance <string>
3 Create a NSE (Network Service Entity) and link it to an “nsvl-group”. The NSE will be redundant since it
will exist on the two DATA VM’s that are associated with “nsvl-group <#> nsvl 0” and “nsvl-group <#>
nsvl 1” above. Repeat as needed.
Syntax:
user@host% set mme-sgsn interface gb nse <nse-id> nsvl-group <#> transport-type <transport-type>
port <local-udp-port>
for IP based PCU:
user@host% set mme-sgsn interface gb nse 12 nsvl-group <#> transport-type ip port 701
for FR based PCU:

user@host% set mme-sgsn interface gb nse 12 nsvl-group <#> transport-type fr port 701

82
SGSN Configuration
Step # Action
4 Setting: Display the default BSSGP configuration and modify if desired.
The default values are shown below.
user@host% set mme-sgsn interface gb bssgp inter-nse-rerouting enable current-bucket-level enable

gigabit-interface enable bvc-reset-timer 60 bvc-reset-retry 3 bvc-blocked-timer 10 bvc-bmax-timer
10 bvc-leak-rate-timer 10 bvc-blocked-alarm-threshold 10 bvc-blocked-clear-threshold 5
user@host% show mme-sgsn interface gb bssgp
inter-nse-rerouting enable;
current-bucket-level enable;
gigabit-interface enable;
bvc-reset-timer 60;
bvc-reset-retry 3;
bvc-blocked-timer 10;
bvc-bmax-timer 10;
bvc-leak-rate-timer 10;
bvc-blocked-alarm-threshold 10;
bvc-blocked-clear-threshold 5;
5.1.6.3 GbIP Specific
The following steps only apply to Gb/IP configurations.
Step # Action
1 Optional GbIP only: Add static NSE config if PCU does not support dynamic mode.
Syntax:
user@host% set mme-sgsn interface gb static-nse-remote-endpoint <remote-ip-address> port <port>
nse-id <nse-id> signaling-weight <signaling-weight>
2 Optional GbIP only: Display the NS (Network Service) layer of the Gb Network Service default values
and adjust if desired.
user@host% set mme-sgsn interface gb ns sns-config-retry 3 sns-delete-retry 3 sns-guard-timer 3
ns-test-timer 30 ns-alive-timer 3 ns-alive-retry 10
user@host% show mme-sgsn interface gb ns
sns-config-retry 3;
sns-delete-retry 3;
sns-guard-timer 3;
ns-test-timer 30;
ns-alive-timer 3;
ns-alive-retry 10;
5.1.6.4 GbFR Specific
The following steps only apply to Gb/FR configurations.
Step # Action
1 Create a frame relay tunnel.
Repeat the command below to create as many fr-tunnels as needed to the applicable remote
DragonWave PMSPN TLC IO cards.

83
SGSN Configuration
Step # Action
Syntax:
user@host% set mme-sgsn interface gb fr-tunnel <name> remote-ip-address <remote-ip-address>
2 Repeat the command below to create as many Gb/FR NSVCs as needed for the NSE(s) created in the
previous steps. Gb/FR NSVCs must be administratively assigned to a particular “nsvl-group nsvl”
instance associated with the NSE, and they must be split (e.g. if an Gb/FR NSE has four NSVCs, then
two NSVCs should be assigned to “nsvl-group x nsvl 0”, and 2 NSVCs should be assigned to “nsvl-
group x nsvl 1”).
Syntax:
user@host% set mme-sgsn interface gb nsvc-fr <nse-id> nsvc-id <nsvc-id> dlci <dlci> fr-tunnel
<fr-tunnel> remote-port <remote-port> nsvl-group <x> nsvl <0 or 1>
user@host% set mme-sgsn interface gb nsvc-fr 200 nsvc-id 2000 dlci 20 fr-tunnel fr1 remote-port
2500 nsvl-group <x> nsvl <0 or 1>
3 Configure the DragonWave box.

Refer to the vendor documentation, and specific notes for SGSN dependencies.
4 Configure the PCU.
Make the corresponding nse, nsvc, and frame relay related configuration changes on the PCU side.
5.1.6.5 Routing Area Configuration
Step # Action
1 Configure the routing areas and how they map to access nodes.
If the rnc list or nse list is empty use ‘none’.
Syntax:
user@host% set mme-sgsn service-area routing-area <plmn> <lac> <rac> rncid-list <rncid-list>
nseid-list <nseid-list> timezone <system timezone>
umts example:
user@host% set mme-sgsn service-area routing-area 50502 0x2280 0x25 nseid-list none rnc-id list
602 timezone <system timezone>
combined umts/gprs example:

user@host% set mme-sgsn service-area routing-area 50502 0x2280 0x25 nseid-list 300 rnc-id list
602 timezone <system timezone>

84
SGSN Configuration
5.2 SGSN Optional Configuration
5.2.1 S16 GTP Mobility

See GTP Feature Overview.
5.2.2 Gf/S13 EIR Interface

The interface to the EIR (Equipment Identity Register) is optional for an SGSN in general. For a
standalone Gn-SGSN, it must be configured using the Gf interface. For an S4-SGSN or combo node
it may be configured for Gf or S13, but if you configure both, S13 will supersede Gf and only S13 will
be used.
5.2.2.1 Gf over SIGTRAN
This presumes that the Gr interface is already configured and that the SCTP and M3UA layers are
reused for Gf.
Step # Action
1 Add the Gf Interface. A loopback interface is required for the Gf ASP IP address.
user@host% set mme-sgsn interface gf gf-if check-imei-retry 0 check-imei-timer 4 eir-address

e.4691129999 include-imsi enable
user@host% show mme-sgsn interface gf gf-if

eir-address 4691129999;
check-imei-timer 4;
check-imei-retry 0;
include-imsi enable;
2 If the SGSN will connect directly to the EIR, add the Peer Configuration.
Syntax:
user@host% set mme-sgsn interface ss7 remote-destination destination-point-code <destination
point code> xudt-option <xudt-option> ludt-option <ludt-option> remote-subsystems <remote
subsystem number (SSN)>
user@host% show mme-sgsn interface ss7 remote-destination destination-point-code 100.91.200
100.91.200 xudt-option disable ludt-option disable remote-subsystems 9;
user@host% set mme-sgsn interface ss7 peer <g-peer name> app-server-name <app-server name> peer-
type ipspSe association-creation initiate ip-address1 172.16.241.190 ip-address2 0.0.0.0 port
<Peer Port> compat-mode standard network-appearance 0
user@host% show mme-sgsn interface ss7 peer g-peer-name EIR01

EIR01 {
ip-address1 172.16.241.190;
peer-type ipspSe;
port 57315;

85
SGSN Configuration
Step # Action
}
ALERT: For Gf the SGSN is the SCTP Client. Set the association-creation to initiate.
(the default).
Syntax:
user@host% set mme-sgsn interface ss7 dest-peer-map <destination point code> <g-peer name>

100.91.200 g-peer-name EIR01;
3 Add the SS7 GTT Result for EIR e.164.

Syntax:
point code> routing-indicator <route-on-gt/route-on-ssn> use-original-gtai enable global-title-
indicator subsystem <SSN of GTT result> <gti0/gti1/gti2/gti3/gti4> translation-type <translation
type> numbering-plan <numbering plan> nature-of-addr-indicator <nature of address indicator>
global-title-addr-info <global title address info>
The minimum result is two. One for outbound traffic and one for inbound traffic.
GTT Result for EIR01:
indicator route-on-gt use-original-gtai enable global-title-indicator gti2 translation-type 10
numbering-plan 1 nature-of-addr-indicator 4 global-title-addr-info 4691129999

10 {
subsystem 9;
numbering-plan 1;
}

Syntax:
user@host% set mme-sgsn interface ss7 gtt-entry <instance> lower-gtai <lower global title address
info> upper-gtai <upper global title address info> primary-result <primary result> secondary-
result <secondary result> global-title-indicator <gti0/gti1/gti2/gti3/gti4> translation-type
<translation type> numbering-plan <numbering plan> nature-of-addr-indicator <nature of address
indicator>
EIR Outbound GTT e.164:

user@host% show mme-sgsn interface ss7 gtt-entry instance 10
10 {
lower-gtai 4691129999;
upper-gtai 0;
primary-result 10;
secondary-result 10;
numbering-plan 1;
}

86
SGSN Configuration
Step # Action
5 Enable Identity Checking.

Syntax:
user@host% set mme-sgsn feature equip-identity-check allow-gray-mobile <allow-gray-mobile> log-
black-gray-mobile <log-black-gray-mobile> imei-check-lifetime <imei-check-lifetime> imei-check-
during-internode <imei-check-during-internode>
user@host% set mme-sgsn feature equip-identity-check allow-gray-mobile enable log-black-gray-

mobile disable imei-check-lifetime disable imei-check-during-internode on
user@host% show mme-sgsn feature equip-identity-check

allow-grey-mobile enable;
log-black-grey-mobile disable;
imei-check-lifetime disable;
imei-check-during-internode on;
[ok][2015-01-21 10:12:48]
user@host% set mme-sgsn feature control equip-id-check status on
user@host% show mme-sgsn feature control equip-id-check

status on;
5.2.2.2 S13 over DIAMETER
Please refer to the S13 configuration section under MME, as it is common to MME and SGSN. If S13
is configured and Gf if configured, an S4-SGSN will only use S13.
5.2.3 Ge - SCP (CAMEL)

The CAMEL (Customized Application for Mobile Network Enhancement) Phase 3 SGSN
Enhancements is an optional feature which requires configuring the Ge interface to an SCP (Service
Control Point) node. It is only applicable for Gr based UEs (e.g. subscribers that retrieve their
subscription information from the HLR) with PDP Context activated over the Gn interface towards a
GGSN. It is typically used for handling of pre-paid users and enforcement of data-volume or time-
based limits. This feature enables extra data in the S-CDR billing records when applicable.
Step # Action
1 Enable the ‘ge’ feature.
user@host% set mme-sgsn feature control ge status on
1a Add the Ge Interface. A loopback interface is required for the Ge ASP IP address.
user@host% set mme-sgsn interface ge ge-if max-camel-dialogues 5000 charging-guard-timer 3 ssf-

timer 3 charging-guard-retry 0 subscriber-service all version 10.0.0
user@host% show mme-sgsn interface ge ge-if
max-camel-dialogues 5000;
ssf-timer 3;
charging-guard-timer 3;
charging-guard-retry 0;
subscriber-service all;
version 10.0.0;

87
SGSN Configuration
Step # Action
2 Configure TCAP engineering parameters.
user@host% set mme-sgsn interface ss7 tcap max-cap-transactions 2000

user@host% set mme-sgsn interface ss7 tcap max-cap-invokes 3000
3 Configure the SS7 remote-destination.
user@host% set mme-sgsn interface ss7 remote-destination destination-point-code 100.94.200 ludt-

option disable xudt-option disable remote-subsystems 8
4 Configure the SIGTRAN peer and mapping based on point code.
user@host% set mme-sgsn interface ss7 peer g-peer-name PP2 app-server-name default ip-address1
172.16.241.148 peer-type ipspSe association-creation initiate ip-address2 0.0.0.0 port 41730
compat-mode standard network-appearance 0
Alert: For SIGTRAN m3ua ss7 peer configuration attribute 'association-creation' should always remain as
'initiate' (the default).
user@host% set mme-sgsn interface ss7 dest-peer-map <destination-point-code> 100.94.200 <g-peer-
name> PP2
5 Configure the global title translation.

indicator route-on-gt use-original-gtai enable subsystem unused-or-default global-title-indicator
gti2 translation-type 10 numbering-plan 1 nature-of-addr-indicator 4 global-title-addr-info
4694119999
user@host% set mme-sgsn interface ss7 gtt-result 2 subsystem unused-or-default
user@host% set mme-sgsn interface ss7 gtt-entry 7 lower-gtai 4694 upper-gtai 0 primary-result 6
secondary-result 6 global-title-indicator gti2 translation-type 10 numbering-plan 1 nature-of-
addr-indicator 4
5.2.4 Gd - SMS
Add one or more of the following:
user@host% set mme-sgsn interface gd sms-trusted-operator e.<node-address> <number-of-

digits>
The following may have been added earlier (see Gr section above):
user@host% set mme-sgsn interface ss7 gtt-result <instance> destination-point-code

<destination point code> routing-indicator <route-on-gt/route-on-ssn> use-original-gtai
enable subsystem <SSN of GTT result> global-title-indictor <gti0/gti1/gti2/gti3/gti4>
translation-type <translation type> numbering-plan <numbering plan> nature-of-addr-
indicator <nature of address indicator> global-title-addr-info <global title address
info>
user@host% set mme-sgsn interface ss7 gtt-entry <instance> lower-gtai <lower global title

88
SGSN Configuration
address info> upper-gtai <upper global title address info> primary-result <primary
result> secondary-result <secondary result> global-title-indicator
<gti0/gti1/gti2/gti3/gti4> translation-type <translation type> numbering-plan <numbering
plan> nature-of-addr-indicator <nature of address indicator>
Step # Action
1 Add Gd Interface and configure CP Response Retries. A loopback interface is required for the Gd ASP
IP address.
user@host% set mme-sgsn interface gd gd-if cp-response-retry 1
2 Configure SMS-C.
user@host% set mme-sgsn node-name> interface gd sms-trusted-operator e.<node-address> <number-of-

digits>
3 If the SGSN will connect directly to the SMS-C, add the Peer Configuration.
Syntax:
user@host% set mme-sgsn interface ss7 remote-destination <destination point code> ludt-option
disable xudt-option disable remote-subsystems <remote subsystem number (SSN)>
user@host% show mme-sgsn interface ss7 remote-destination

100.93.200 xudt-option disable ludt-option disable remote-subsystems 8;
Syntax:
user@host% set mme-sgsn interface ss7 peer <g-peer name> app-server-name <app-server name> peer-
type ipspSe association-creation initiate ip-address1 172.16.241.190 <ip-address2> 0.0.0.0 port
<Peer Port> compat-mode standard network-appearance 0
user@host% show mme-sgsn interface ss7 peer SMSC01

ip-address1 172.16.241.190;
peer-type ipspSe;
port 57315;
ALERT: For Gd the SGSN is the SCTP Client. Set the association-creation to initiate.
(the default).
Syntax:
user@host% set mme-sgsn interface ss7 dest-peer-map add <destination point code> g-peer-name <g-
peer name>

100.93.200 g-peer-name SMSC01;
4 Add the SS7 GTT Result for SMS e.164.

Syntax:
point code> routing-indicator <route-on-gt/route-on-ssn> use-original-gtai enable subsystem <SSN
of GTT result> global-title-indicator <gti0/gti1/gti2/gti3/gti4> translation-type <translation
type> numbering-plan <numbering plan> nature-of-addr-indictor <nature of address indicator>

89
SGSN Configuration
Step # Action
GTT Result:
gti2 translation-type 10 numbering-plan 1 nature-of-addr-indicator 4 global-title-addr-info
4691139999
user@host% show mme-sgsn interface ss7 gtt-result
instance 11;
subsystem 8;
numbering-plan 1;

Syntax:
indicator>
Outbound GTT e.164:
user@host% show mme-sgsn interface ss7 gtt-entry instance 11

instance 11;
upper-gtai 0;
primary-result 11;
numbering-plan 1
5.2.5 Gs – VLR (MSC)

Note: This section for Gs interface setup includes the steps to map a location-area (LAC) to a VLR,
but not to ensure a location-area contains routing-area(s) that are tied to the access network. It is a
pre-requisite that the applicable location-area area is already configured under mme-sgsn service-
area routing-area as shown in section 5.1.6.5.
Step # Action
1 Enable the feature and add the Gs Interface. A loopback interface is required for the Gs ASP IP
address.
user@host% set mme-sgsn feature control gs status on

90
SGSN Configuration
Step # Action
Syntax:
user@host% set mme-sgsn interface gs gs-if global-title <global-title> cgpa-routing-indicator
<cgpa-routing-indicator> nature-of-address <nature-of-address> return-option <return-option>
xudt-option <xudt-option> registration-request-timer <registration-request-timer> loc-upd-on-lai-
mismatch <loc-upd-on-lai-mismatch> loc-upd-timer <loc-upd-timer> explicit-gprs-detach-timer
<explicit-gprs-detach-timer> explicit-gprs-detach-retry <explicit-gprs-detach-retry> explicit-
imsi-detach-timer <explicit-imsi-detach-timer> explicit-imsi-detach-retry <explicit-imsi-detach-
retry> implicit-imsi-detach-timer <implicit-imsi-detach-timer> implicit-imsi-detach-retry
<implicit-imsi-detach-retry> reset-timer <reset-timer> version <version>
user@host% set mme-sgsn interface gs gs-if 802991012001 cgpa-routing-indicator global-title

nature-of-address international-number return-option ret-undeliverable xudt-option enable
registration-request-timer 5 loc-upd-on-lai-mismatch disable loc-upd-timer 10 explicit-gprs-
detach-timer 4 explicit-gprs-detach-retry 2 explicit-imsi-detach-timer 4 explicit-imsi-detach-
retry 2 implicit-imsi-detach-timer 4 implicit-imsi-detach-retry 2 reset-timer 4 reset-retry 2
version 10.7.0
user@host% show mme-sgsn interface gs gs-if

global-title 802991012001;
cgpa-routing-indicator global-title;
nature-of-address international-number;
return-option ret-undeliverable;
xudt-option enable;
registration-request-timer 5;
loc-upd-on-lai-mismatch disable;
loc-upd-timer 10;
explicit-gprs-detach-timer 4;
explicit-gprs-detach-retry 2;
explicit-imsi-detach-timer 4;
explicit-imsi-detach-retry 2;
implicit-imsi-detach-timer 4;
implicit-imsi-detach-retry 2;
reset-timer 4;
reset-retry 2;
version 10.7.0;
2 Configure the VLR – Multiple if needed.

NOTE: The length of the name is limited to 255 characters so that it matches the name configured
under vlr-pool in the next step. Although the standards recommend an FQDN for the name, it actually is
not sent in any message for MME/SGSN and only has internal significance to link these two tables
together.
Syntax:
user@host% set mme-sgsn service-area vlr <vlr name> vlr-type gs vlr-number <sgs-ip-address1; sgs-
ip-address2> callp-service-id <id>
user@host% show mme-sgsn service-area vlr gs

vlr-type gs;
vlr-number 4693119999;
callp-service-id 0;
3 Configure the VLR Pool.

Syntax:

91
SGSN Configuration
Step # Action
user@host% set mme-sgsn service-area vlr-pool <vlr-pool name> vlr-selection-digits <vlr-
selection-digits> vlr-name <vlr name>
user@host% show mme-sgsn service-area vlr-pool

default vlr-selection-digits default vlr-name gs;
4 If the SGSN will connect directly to the VLR, add the Peer Configuration.
Syntax:
user@host% set mme-sgsn interface ss7 remote-destination <destination point code> xudt-option
disable ludt-option disable remote-subsystems <remote subsystem number (SSN)>
user@host% show mme-sgsn interface ss7 remote-destination 100.92.200

xudt-option disable ludt-option disable remote-subsystems 7;
Syntax:
user@host% set mme-sgsn interface ss7 peer VLR01 app-server-name default ip-address1 <Peer IP
Address 1> peer-type ipspSe association-creation initiate ip-address2 0.0.0.0 port <Peer Port>
compat-mode standard network-appearance 0
user@host% show mme-sgsn interface ss7 peer SMSC01

VLR01 {
ip-address1 172.16.241.191;
peer-type ipspSe;
port 57315;
ALERT: For Gs, the SGSN is the SCTP Client. Set the association-creation to initiate.
(the default).
Syntax:
user@host% set mme-sgsn interface ss7 dest-peer-map <destination point code> g-peer-name <g-peer
name>
100.92.200 g-peer-name VLR01;
5 Add the SS7 GTT Result for VLR e.164.

Syntax:
point code> routing-indicator <route-on-gt/route-on-ssn> use-original-gtai enable subsystem <SSN
of GTT result> global-title-indicator <gti0/gti1/gti2/gti3/gti4> translation-type <translation
type> numbering-plan <numbering plan> nature-of-addr-indicator <nature of address indicator>
GTT Result for VLR01:
gti2 translation-type 10 numbering-plan 1 nature-of-addr-info 4 global-title-addr-info 4691139999
user@host% show mme-sgsn interface ss7 gtt-result

92
SGSN Configuration
Step # Action
12 {
subsystem 7;
numbering-plan 1;
}

Syntax:
indicator>
EIR Outbound GTT e.164:

12 {
upper-gtai 0;
primary-result 12;
numbering-plan 1;
7 Define the VLR to Location Area/TAC Map.

Syntax:
user@host% set mme-sgsn service-area location-area <plmn-id> <lac> vlr-pool-name <vlr pool name>
user@host% show mme-sgsn service-area location-area

plmn 50502;
lac 0x4630;
vlr-pool-name default-pool;
5.2.6 Ga – CGF (Accounting)

The SGSN supports generation of SGSN (S-CDR) and Mobility (M-CDR) records as well as SMO
(SMS mobile originated) and SMT (SMS mobile terminated) records for account purposes. The output
may be streamed to a CGF (Charging Gateway Function) by GTP protocol over the Ga interface, or it
may be transferred by SFTP pull as initiated by an external server; however these two transfer
functions are mutually exclusive.
Step # Action
1 Configure SGSN accounting parameters (Ga profile).
user@host% set mme-sgsn interface ga sgsn-ga-profile cdr-capture sgsn,mobility

93
SGSN Configuration
Step # Action
user@host% set mme-sgsn interface ga sgsn-ga-profile version <9.6.1/10.12.0>
user@host% show mme-sgsn interface ga sgsn-ga-profile

cdr-capture sgsn,mobility;
collection-time 03:50,04:50;
encoding-scheme ber;
version 9.6.1;
partial-cdr-type full;
roamer-capture all;
tariff-time-change-trigger enable;
Modify CDR generation parameters as needed.

2 Configure Charging Characteristics.
user@host% set mme-sgsn interface ga charging-characteristics data-volume-limit 128 location-

based-billing enable mcdr-max-containers 1 mcdr-partial-record-initial 0 scdr-max-containers 5
scdr-partial-record-interval 0
user@host% show mme-sgsn interface ga charging-characteristics

scdr-partial-record-interval 0;
data-volume-limit 128;
scdr-max-containers 5;
mcdr-partial-record-interval 0;
mcdr-max-containers 1;
location-based-billing enable;
3 Create the Ga Interface. A loopback interface is required for the Ga interface IP address.
user@host% set mme-sgsn interface ga ga-if drt-response-timer 5 drt-retry 1 echo-request-interval

1 ip-address 172.18.249.29 routing-instance EPCCore01
user@host% show mme-sgsn interface ga ga-if

ip-address 172.18.249.29;
echo-request-interval 1;
drt-response-timer 5;
drt-retry 1;
5.2.6.1 Transfer by GTP
This method is mutually exclusive of the SFTP Pull method.
Step # Action
1 Define the CGF Server (Primary/Secondary).
Syntax:
user@host% set mme-sgsn interface ga cgf <CGF IP Address> port <CGF Port> configured-role
<primary/secondary>
user@host% show mme-sgsn interface ga cgf

172.16.241.143 port 3387 {
configured-role primary;
}

94
SGSN Configuration
5.2.6.2 Transfer by SFTP Pull
The following procedure describes how to pull billing records (CDRs) that have been stored to disk in
3GPP TS 32.297 compliant format from the SGSN.
Note that only SFTP Pull is supported. FTP is not supported.
Do not pull the files from the SGSN’s disk if a CGF is provisioned on the SGSN. In that case, the files
are automatically read from the disk and sent to the CGF without any operator intervention required. If
files are pulled in this case, it could lead to duplicate records and unexpected behavior on the SGSN.
This procedure only applies to the case when a CGF is not provisioned on the SGSN. In that case,
the files are written to disk, but the operator must periodically SFTP the files off of the SGSN to
ensure the disk partition does not become full.
The frequency with which the files should be pulled is dependent on the amount of traffic and
accounting provisioning. A Disk High Usage alarm (GaBilling1300) is generated when the billing
partition reaches specific thresholds (Minor: 30%, Major: 50%, Critical: 90%, and Clear: 25%). Use
this alarm as a guide to when the files should be pulled, but do not wait for the disk to become full
since CDRs will be discarded if that occurs.
Verify that a CGF is not provisioned:
Step # Action
1 Check the current CGF provisioning.

172.16.241.143 port 3387 {
configured-role primary;
}
2 Remove any CGF entries.
user@host% delete mme-sgsn interface ga cgf 172.16.241.143 port 3387
Periodic pull procedure:
Step # Action
1 SFTP to the SGSN (non-gui sftp client is shown but any sftp client should work).
sftp sftpuser@vmme20
2 Change to the directory that contains the files to pull.
sftp> cd /usr/local/epc/accounting/closed
3 List the files in the closed directory.
sftp> ls -l
-rw-r--r-- 1 root root 61365 Mar 14 17:45 vmme20_-_1.20120314_-
_1745+0000.mcdr_v36_ber.closed

95
SGSN Configuration
Step # Action
_1745+0000.scdr_v36_ber.closed
4 Make a new directory to move the files to pull into (a name besides ‘pull’ can be used).
sftp> mkdir pull
5 Move (rename) the ‘.closed’ files into the new ‘pull’ directory.
sftp> rename vmme20_-_1.20120314_-_1745+0000.mcdr_v36_ber.closed pull/vmme20_-_1.20120314_-

ALERT: Use the above command for each file to be pulled. A graphical sftp client will make this much easier since
multiple files can be highlighted and dropped into the ‘pull’ folder.
ALERT: A new directory is created because the SGSN may still be writing new files to disk while the files are being
pulled. This allows for an easy way to tell which files should be deleted after the pulling is complete. Some graphical
clients allow you to ‘move’ files (copy and then delete) directly from remote to local and thus the need to move them to
a temporary directory is no longer necessary.
6 Pull the files from the ‘pull’ directory.
sftp> cd pull
sftp> get *
Fetching /usr/local/epc/accounting/closed/pull/vmme20_-_1.20120314_-_1745+0000.mcdr_v36_ber.closed
to vmme20_-_1.20120314_-_1745+0000.mcdr_v36_ber.closed
/usr/local/epc/accounting/closed/pull 100% 60KB 59.9KB/s 00:00
Fetching /usr/local/epc/accounting/closed/pull/ vmme20_-_2.20120314_-
_1745+0000.scdr_v36_ber.closed to vmme20_-_2.20120314_-_1745+0000.scdr_v36_ber.closed
/usr/local/epc/accounting/closed/pull 100% 1024KB 1.0MB/s 00:00
7 Check that the files are in the destination directory.
sftp> lls -l
ALERT: The command is ‘lls’ not ‘ls’. ‘lls’ is for ‘local ls’.
ALERT: It is probably better to check the destination directory using a local file manager or local terminal.
8 Clean up.
sftp> rm *
sftp> cd ..
sftp> rmdir pull
5.2.7 Gn S4 Selection
This feature enhances the S4-SGSN node to provide the following functionality for UEs in Iu mode:

96
SGSN Configuration
 gateway interface selection based on configurable options (Gn, S4 preferred or Gn/S4 using EPC
capability)
 deactivation of existing S4 sessions upon receipt of CAMEL subscription information over Gr

interface
 SGW allocation (when applicable) during mobility from Gn-SGSN to S4-SGSN
Step # Action
1 Verify the S4-SGSN feature is enabled.
[edit]
user@host% show mme-sgsn feature control | tab
NAME STATUS
--------------------------
direct-tunnel off
equip-id-check off
fxa off
gs on
hspa-plus on
ims-emergency on
lawful-intercept on
s101 off
s102 on
s4-sgsn on
sbc off
sgs on
trace on
ue-purge off
[ok][2014-09-03 10:55:37]
Use the set command (set mme-sgsn feature control s4-sgsn status on) if the feature is off.
2 Set the dns-preference attribute to the preferred value. In order to support both DNS s-naptr and classic
query procedures, the value unknown should be configured.
[edit]
user@host% set mme-sgsn subscriber subscriber-plmn 31298 dns-preference unknown
[ok][2014-09-03 10:55:37]
3 Set the Gn/S4 gateway selection.

• If gn is configured, the S4-SGSN activates a UE’s sessions over the Gn interface.
• If s4-preferred is configured, the S4-SGSN gives preference to activating a UE’s sessions over the
S4 interface.
• If ue-epc-capability is configured, the S4-SGSN gives preference to activating an EPC-capable UE’s
sessions over the S4 interface. A non EPC-capable UE’s sessions are activated over the Gn
interface.
[edit]
user@host% set mme-sgsn subscriber subscriber-class default gateway-interface-sel ue-epc-
capability
[ok][2014-09-03 10:55:37

97
SGSN Configuration
5.2.8 S4 Interface Optional Features
Step # Action
1 Add the S4 interface table to control any optional features for that interface, or to point to a unique gtp-
profile for this particular interface when required.
The uli-inclusion parameter controls if the SGSN will send ULI in the below GTPv2 messages if it is set to the enum
value 'force-in-all':
• Create Session Request(HO/TAU)
• Modify Bearer Request
• Delete Session Request
• Delete Bearer Command
The ue-timezone-inclusion parameter controls if the SGSN will send UE-Timezone in GTPv2 messages.
In this example, a separate gtp profile is used for the s4 interface.
user@host% set mme-sgsn interface s4-if gtp-profile s4 ue-timezone-inclusion standard uli-

inclusion force-in-all

s4-if {
gtp-profile s4;
uli-inclusion force-in-all;
ue-timezone-inclusion standard;
}
[ok][2015-01-21 10:20:38]
5.2.9 Iu Flex and Gb Flex

Iu and Gb Flex allow for resource pooling and geographical redundancy. Refer to the vMME Product
Overview document, for more details.
Step # Action
1 Create an SGSN pool.
user@host% set mme-sgsn service-area sgsn-pool <pool-name> nri-bit-length 0 load-balancing enable

non-broadcast-rai none cn-id 1
user@host% show mme-sgsn service-area sgsn-pool default
nri-bit-length 0;
load-balancing enable;
non-broadcast-rai none;
cn-id 1;
2 Set the NRI values.

Syntax:
user@host% set mme-sgsn service-area sgsn-nri <nri number> <sgsn pool name> nri-type <local-
nri/pool-nri> ip-address-list <IP Address List>

98
SGSN Configuration
5.2.10 Traffic Shaping

This feature implements the traffic shaping functionality on the MME. This component represents the
differentiated service (QOS) on the Serving GPRS Support Node (SGSN) that governs the behavior
of packets and contexts that pass through this node. If this component is not provisioned, the data
rate for every context will be best effort.
Step # Action
1 Enable the Traffic Shaping feature.
When enabled, the SGSN will use the allocation and retention priority and traffic class from the QoS of a mobile to
retrieve the DSCP Mark for inclusion in data packets that pass through this node.
user@host% set mme-sgsn feature control traffic-shaping status on
2 Modify the Differentiated Service (DS) Code Point (DSCP) value for signalling traffic and the allocation
and retention priority assigned to a mobile that is a roamer.
user@host% set mme-sgsn feature traffic-shaping control signaling-dscp-mark af11 default-roamer-

ar 2
user@host% show mme-sgsn feature traffic-shaping control

control {
signaling-dscp-mark af11;
default-roamer-ar 2;
}
3 Modify the TrafficClass (Tc) and/or Traffic Handling Priority (THP) provisioning data of the SGSN.
user@host% set mme-sgsn feature traffic-shaping profile priority 1 traffic-class conversational

data-dscp-mark cs5 preemption-capability enabled preemption-vulnerable disabled qa enabled
user@host% set mme-sgsn feature traffic-shaping profile priority 1 traffic-class conversational

data-dscp-mark af11 preemption-capability enabled preemption-vulnerable disabled qa enabled
user@host% set mme-sgsn feature traffic-shaping profile priority 2 traffic-class background

preemption-capability disabled data-dscp-mark af12 preemption-vulnerable auto-configure qa
disabled
user@host% set mme-sgsn feature traffic-shaping profile priority 3 traffic-class streaming data-
dscp-mark af13 preemption-capability auto-configure preemption-vulnerable enabled qa auto-
configure
user@host% set mme-sgsn feature traffic-shaping profile priority 1 traffic-class interactive-thp1

data-dscp-mark af21 preemption-capability auto-configure preemption-vulnerable enabled qa auto-
configure

data-dscp-mark af22 preemption-capability enabled preemption-vulnerable disabled qa enabled

data-dscp-mark af23 preemption-capability disabled preemption-vulnerable auto-configure qa
disabled
user@host% show mme-sgsn feature traffic-shaping profile

1 traffic-class conversational {
data-dscp-mark af11;
preemption-capability enabled;
preemption-vulnerable disabled;
queuing-allowed enabled;
}

99
SGSN Configuration
Step # Action
2 traffic-class background {
preemption-capability disabled;
preemption-vulnerable auto-configure;
queuing-allowed disabled;
}
3 traffic-class streaming {
preemption-capability auto-configure;
preemption-vulnerable enabled;
queuing-allowed auto-configure;
}
1 traffic-class interactive-thp1 {
preemption-capability auto-configure;
preemption-vulnerable enabled;
queuing-allowed auto-configure;
}
preemption-capability enabled;
preemption-vulnerable disabled;
queuing-allowed enabled;
}
preemption-capability disabled;
preemption-vulnerable auto-configure;
queuing-allowed disabled;
}
5.2.11 RAN Information Management
Step # Action
1 Activate the RAN information management feature.
user@host% set mme-sgsn feature control ran-info-management status on
5.2.12 RAN Admission Control
Step # Action
1 Activate the RAN admission control feature.
user@host% set mme-sgsn feature control ran-admission-control status on
5.2.13 Sessionless Subscriber Detach

The SGSN Sessionless Subscriber Detach feature will detach the 2G/3G oldest sessionless
subscribers when overload level of the system reaches the critical stage. The feature is ‘Off’ by
default and is controlled via OAM. A new entity named ‘sgsn-sessionless-sub-detach’ is created for
this feature. Cause value which will be sent in the detach request by this feature can also be

100
SGSN Configuration
configured and default value being ‘no-detach-msg’. Operators can also configure a list of a
maximum of 40 APN-NI`s, which will exclude the subscribers having those APN-NI from getting
detached and default being ‘none’.
Step # Action
1 Turn-On the feature.
user@host% set mme-sgsn feature control sgsn-sessionless-sub-detach status on
The feature entity ‘sgsn-sessionless-sub-detach’ is populated with default values of each attribute only after the
feature is turned on. Initially, it will be empty with no values.
2 Check the default values in sgsn-sessionless-sub-detach feature entity.
user@host% set mme-sgsn feature sgsn-sessionless-sub-detach cause-code no-detach-msg apn-ni-list

none
user@host% show mme-sgsn feature sgsn-sessionless-sub-detach
cause-code no-detach-msg;
apn-ni-list none;
5.2.14 Packet Flow Context (PFC)
Step # Action
1 Activate Packet-Flow-Control Feature.
Syntax:
user@host% set mme-sgsn interface gb packet-flow-management packet-flow-context <packet-flow-
context> pfc-flow-control <pfc-flow-control> pfc-flow-control-tf-timer <pfc-flow-control-tf-
timer> average-pfcs-per-mobile <average-pfcs-per-mobile> t7-timer <t7-timer> t7-retries <t7-
retries> packet-flow-timer <packet-flow-timer>
user@host% show mme-sgsn interface gb packet-flow-management

packet-flow-context = disable
pfc-flow-control = disable
pfc-flow-control-tf-timer = 5
average-pfcs-per-mobile = 10
t7-timer = 5
t7-retries = 3
packet-flow-timer = 40
ALERT: Default entries for the attributes are shown above. All the attributes can be configured as per their need.
5.2.15 IMEI Forwarding During IRAU

IMEI forwarding allows operators to check the status of the equipment (mobile), [whether the mobile
is theft or not]. Based on the response (white-listed, black-listed or gray-listed) it processes the mobile
for further IRAU requests. Refer to the vMME Product Overview document for more details.
Step # Action
1 Set the imei check lifetime and imei-check-during-internode.
user@host% set mme-sgsn feature control equip-id-check status off

101
SGSN Configuration
Step # Action
user@host% set mme-sgsn feature equip-identity-check allow-gray-mobile enable log-black-grey-
mobile disable imei-check-lifetime enable imei-check-during-internode off
5.2.16 Dataplane Options

The SGSN dataplane resides in the DATA VM, and supports GPRS and UMTS concurrently. It is
configured with default values to allow basic service. The following sections indicate options that can
be configured for data plane.
5.2.16.1 PDU Buffering on Old (source) SGSN
During IRAU, packets need to be buffered and then sent to the new SGSN when it is ready to service
the mobile. If the old SGSN is a 2G node, IRAU buffering always takes place on the SGSN. For 3G,
this buffering normally takes place on the RNC; however, if the RNC does not support buffering or if
the operator wants buffering to take place on the SGSN as an optimization, the following attribute can
be set.
Step # Action
1 Enable buffering on the old 3G SGSN.
user@host% set mme-sgsn interface sm old-sgsn-buffering enable
Note that provisionable parameters for IRAU buffering (irau-buff-max-bytes-per-session) are for
buffering on the new SGSN. For IRAU buffering on the old SGSN, provisionable parameters for
downlink buffering are used (dl-buff-max-bytes-per-session; again).
5.2.16.2 GPRS Compression in SNDCP Layer
The SGSN supports RFC1144 IP header compression and V.42 bis user data compression over the
Gb interface. These can be used to decrease overhead and optimize radio resource usage efficiency
for 2G networks.
The header compression parameters have the following meanings:
 allowable-compression-alg: header compression algorithm to propose during XID negotiation

for PDP context activation
 max-header-compression-entities: the number of sessions that can run header compression

simultaneously as a percentage of sd-capacity subs-per-su
 rfc1144-slots: the number of state slots that can be used by the RFC1144 algorithm
The data compression parameters have the following meanings:
 max-v42bis-entities: the number of sessions that can run data compression simultaneously as a
percentage of sd-capacity subs-per-su

102
SGSN Configuration
 v42bis-compression-direction: which data to compress – data from the mobile, data to the
mobile, or both
 v42bis-dictionary: the maximum number of V.42 bis codewords
 v42bis-max-string-size: the maximum number of characters in a string associated with a

codeword
The common (header and data) compression parameter has the following meaning.
 compression-algorithms-in-irau: algorithm(s) to propose during XID negotiation for IRAU. Note

that if rfc1144 is listed, it will only be proposed if it is enabled (by setting allowable-compression-
alg to rfc1144) and a header compression entity is available. Similarly, if v42bis is listed, it will
only be proposed if it is enabled (by setting max-v42bis-entities to a non-zero value) and a V.42
bis entity is available.
Step # Action
1 Configure IP header compression as per engineering requirements.
Syntax:
user@host% set mme-sgsn interface gb sndcp allowable-compression-alg <none | rfc1144> max-header-
compression-entities <value> rfc1144-slots <value>
2 Configure user data compression as per engineering requirements.

Syntax:
user@host% set mme-sgsn interface gb sndcp max-v42bis-entities <value> v42bis-compression-
direction <from-ms | to-ms | both> v42bis-dictionary <512 | 2024 | 2048 | 4096> v42bis-max-
string-size <value>
3 Configure compression negotiation during IRAU.

Syntax:
user@host% set mme-sgsn interface gb sndcp compression-algorithms-in-irau <none | rfc1144 |
v42bis | rfc1144,v42bis>
5.2.16.3 PDU Buffering
PDU buffering is used to improve network performance by temporarily storing packets that cannot be
immediately transmitted. For 2G systems, this can be because the BSS has initiated flow control, LLC
is suspended, or the old SGSN is waiting for a context acknowledgement from the new SGSN during
IRAU. Packets are also buffered if LLC is operating in acknowledged mode. For 3G systems,
buffering occurs during paging and, if enabled, on the old SGSN during IRAU. Buffering for each of
these conditions is configured with the dl (downlink) buffer parameters shown below. In contrast, the
irau buffer parameters are used for buffering on the new SGSN during IRAU following the context
acknowledgement but before the lower layers are available.
The buffering parameters have the following meanings:
 <dl | irau>-buff-total-bytes-reserved: The maximum number of bytes that can be used for
buffering.

103
SGSN Configuration
 <dl | irau>-percent-buffered-sessions: The number of sessions that can use buffering

resources, defined as a percentage of the maximum number of sessions supported.
 <dl | irau>-buff-max-pdu-per-session: The maximum number of PDUs that can be buffered per
session.
 <dl | irau>-buff-max-bytes-per-session: The maximum number of bytes that can be buffered

per session.
 buff-check-interval: The periodic time interval (in 10ths of a second) after which the SGSN
attempts to transmit buffered PDUs.
 pdu-lifetime-in-buff: The maximum amount of time (in seconds) that a single PDU can be
buffered.
 percent-umts-buff: The percentage of buffering resources available for 3G data; the rest are
available for 2G data.
Step # Action
1 Set downlink buffering parameters as per engineering requirements.
Syntax:
user@host% set mme-sgsn engineering sd-engineering dl-percent-buffered-sessions <value> dl-buff-
max-pdu-per-session <value> dl-buff-max-bytes-per-session <value> dl-buff-total-bytes-reserved
<value>
2 Set IRAU buffering parameters as per engineering requirements.

Syntax:
user@host% set mme-sgsn engineering sd-engineering irau-buff-max-pdu-per-session <value> irau-
buff-max-bytes-per-session <value> irau-buff-total-bytes-reserved <value>
3 Set downlink/IRAU common parameters as per engineering requirements.

Syntax:
user@host% set mme-sgsn engineering sd-engineering buff-check-interval <value> pdu-lifetime-in-
buff <value> percent-umts-buff <value>
5.2.16.4 LLC (Logical Link Control)
The LLC layer of the GPRS dataplane configures with usable default values. The following examples
show the default values and the method to adjust if desired, but these steps are optional.
Step # Action
1 Optional: Display the LLC default configuration and modify if desired.
user@host% show mme-sgsn interface gb llc

abm-mode-lle-to-mobile-ratio 15;
flush-logical-link-timer 5;
xid-during-irau-adm-mode during-irau;
alternate-llc-xid-negotiation disable;

104
SGSN Configuration
Step # Action
user@host% set mme-sgsn interface gb llc abm-mode-lle-to-mobile-ratio <new value>
2 Optional: Display the LLC SAPI default configuration and modify if desired.
user@host% show mme-sgsn interface gb llc-sapi

1 {
t200-retransmit-timer 50;
n200-max-retransmits 3;
n201-max-uinfo-field-length 400;
}
3 {
n201-max-iinfo-field-length 1503;
k-window-size-downlink 16;
k-window-size-uplink 16;
pdu-unconfirmed-info-lifetime 50;
}
5 {
n201-max-iinfo-field-length 1503;
k-window-size-downlink 8;
k-window-size-uplink 8;
pdu-unconfirmed-info-lifetime 100;
}
user@host% set mme-sgsn interface gb llc-sapi 1 n200-max-retransmits <new value>
5.2.17 Periodic Paging Resumption

This feature allows the continuation of paging attempts to a mobile after the Paging Proceed Flag has
been cleared on the SGSN, if downlink PDU’s are received. The attempts will continue until the expiry
of mobile reachable timer, assuming the network is unable to contact the mobile. By default, the
feature is disabled.
Activation of this feature may impact messaging and RF paging resources due to the fact that the PS
paging is delivered to all the cells in the RAI. Therefore, an engineering exercise is advised to
properly set the provisioning attribute.
Step # Action
1 Enable the Periodic Paging Resumption Feature.
user@host% set mme-sgsn interface nas nas-common ppf-reset-timer 70

ppf-reset-timer 70;
reset-timer 60;
version 9.5.0;

105
SGSN Configuration
5.2.18 QoS Negotiation

This attribute comes under SM entity. It specifies whether the Serving GPRS Support Node (SGSN)
supports the negotiation of the Quality of Service (QoS) with the RNC and GGSN. By default it is
‘disabled’.
Step # Action
1 Enabling the qos-negotiation attribute.
user@host% set mme-sgsn interface nas sm qos-negotiation enable
By default the qos negotiation is disabled.
5.2.19 QoS Conversion
Step # Action
1 Modify and display the default QOS conversion details.
user@host% set mme-sgsn subscriber qos-conversion background arp-high 6
user@host% show mme-sgsn subscriber qos-conversion background

max-sdu-size 1500;
residual-ber residualber-4thousandth;
delivery-of-erroneous-sdus err-sdus-not-delivered;
arp-high 6;
arp-medium 10;
user@host% show mme-sgsn subscriber qos-conversion conversational

max-sdu-size 1500;
residual-ber residualber-5hundredth;
arp-high 6;
arp-medium 10;
user@host% show mme-sgsn subscriber qos-conversion interactive-thp1

max-sdu-size 1500;
arp-high 5;
arp-medium 10;

max-sdu-size 1500;
arp-high 5;
arp-medium 10;

max-sdu-size 1500;
arp-high 5;
arp-medium 10;

106
SGSN Configuration
Step # Action
user@host% show mme-sgsn subscriber qos-conversion streaming
max-sdu-size 1500;
residual-ber residualber-5hundredth;
arp-high 5;
arp-medium 10;
5.2.20 Second Authentication

Second Authentication is optionally triggered if first authentication attempt fails due to expected
response mismatch. Refer to the MME/SGSN Product Overview document, for more details.
Step # Action
1 Enable the Second authentication attempts.
user@host% set mme-sgsn interface nas gmm second-auth-attempts enable
5.2.21 GMM Cause Code Mapping

This component is used to map GMM cause codes with respect to different error description
scenarios.
Step # Action
1 Setting of GMM cause code.
user@host% set mme-sgsn interface nas gmm-cause-mapping access-restriction-data cause-code no-
suitable-cell-in-la-15 application-unsupported cause-code no-suitable-cells-in-ra-15 command-
unsupported cause-code no-suitable-cells-in-ra-15 out-of-space cause-code congestion-22 too-busy
cause-code congestion-22 unable to comply cause-code no-suitable-cells-in-ra-15 unknown-serving-
node cause-code imsi-unknown-in-hss-2 roaming-restricted-in-mme-due-to-unsupported-feature cause-
code no-suitable-cells-in-la-15
user@host% show mme-sgsn interface nas gmm-cause-mapping access-restriction-data

access-restriction-data cause-code no-suitable-cell-in-la-15;
In the preceding command, the error description should be chosen from the listed string values and
cause code can be any of the listed strings or a numeric value in the range of 1-255.
5.2.22 Capacity and engineering

This section is covered in more detail in the LTE MME and SGSN Engineering Guide. These
commands are optional, as the system provides reasonable defaults at install time.
Step # Action
1 Configure the capacity limit for each SC service unit.
This configures the maximum number of subscribers supported per SC application in this CALLP VM in
units of thousands.
Syntax:

107
SGSN Configuration
Step # Action
user@host% mme-sgsn engineering sc-capacity <callp-service-id> subs-per-su <subs-per-su>
user@host% show mme-sgsn engineering sc-capacity

1 subs-per-su 400;
0 subs-per-su 400;
2 Display the SC engineering configuration details.

ALERT: Only apn-average is applicable for SGSN and others are applicable for MME.
Syntax:
user@host% set mme-sgsn engineering sc-engineering pdn-average <value> dedicated-bearer-average
<value> apn-average <value> csg-average <value>
user@host% show mme-sgsn engineering sc-engineering
pdn-average 105;
dedicated-bearer-average 200;
apn-average 200;
csg-average 200;
3 Configure the capacity limit for each SD service unit in thousands of subscribers.
user@host% set mme-sgsn engineering sd-capacity 416
user@host% show mme-sgsn engineering sd-capacity

subs-per-su 416;
The SD capacity is based on the sizing of the system, how many data processors are present. Please refer to the
LTE MME and SGSN Engineering Guide, for details on how to configure the SD capacity for a given system. The
range is 64K to 1664K subs.
4 Modify and display the SD engineering configuration.
user@host% show mme-sgsn engineering sd-engineering

dl-percent-buffered-sessions 10;
dl-buff-max-pdu-per-session 12;
dl-buff-max-bytes-per-session 10240;
dl-buff-total-bytes-reserved 545259520;
irau-percent-buffered-sessions 5;
irau-buff-max-pdu-per-session 12;
irau-buff-max-bytes-per-session 10240;
irau-buff-total-bytes-reserved 54525952;
buff-check-interval 10;
pdu-lifetime-in-buff 5;
percent-umts-buff 80;
lle-to-mobile-ratio 15;
Optionally adjust as desired:

user@host% set mme-sgsn engineering sd-engineering pdu-lifetime-in-buff <some new value>
5 Modify and display IU congestion control configuration details.

This configures the congestion levels of a particular RNC process.
user@host% show mme-sgsn engineering iu-congestion-control

minor-onset 70;
minor-abate 65;
minor-action ignore;
major-onset 80;
major-abate 75;
major-action ignore;
critical-onset 90;
critical-abate 85;

108
SGSN Configuration
Step # Action
critical-action ignore;
Optionally adjust as desired:

user@host% set mme-sgsn engineering iu-congestion-control minor-onset 75
5.2.23 Sigtran Enhancements

Enhancements made to SIGTRAN are:
 The SS7 congestion control is enhanced under current system overload control architecture. With
this feature, the local SCTP buffer usages of ASP instances are also included in calculating the
congestion level of the system, and the external SCON messages are process as part of
congestion control of the system.
 The capability to specify the subsystem numbers for each 3GPP subsystems configured on the
SGSN.
 The SIGTRAN process (ASP) sheds traffic based on the local subsystems and the configured
importance levels in case of congestion/overload.
 An option is provided to configure/control the reconnect timer for ASP to establish the association
with applicable peers.
Note:
Multi-homing is not supported on the SIGTRAN interfaces (Gfreds and Iu).
The following table shows the configuration tables associated with these enhancements.
Step # Action
1 Display the reconnect timer and adjust if need be.
user@host% show mme-sgsn interface m3ua m3uaSigtran

multiple-network-appearances enable;
fsm-timeout 2000;

109
SGSN Configuration
Step # Action
reconnect-timer 10;
user@host% show mme-sgsn interface m3ua m3uaIu

multiple-network-appearances disable;
fsm-timeout 2000;
reconnect-timer 10;
2 Display/adjust the message priority levels and subsystem numbers.
user@host% show mme-sgsn interface ss7 ss7

sgsn-number 802001002001;
signaling-variant itu;
map-cgpa-routing-indicator global-title;
version 9.4.0;
dscp-mark de;
map-importance-level auto-configure;
bssap-importance-level auto-configure;
cap-importance-level auto-configure;
map-subsystem-number standard;
bssap-subsystem-number unused;
cap-subsystem-number unused;
cap-cgpa-routing-indicator global-title;
Importance levels can be one of 1 2 3 4 5 6, auto-configure; Importance level messages (1::6 for ITU, 1::3 for ANSI);
default for all is auto-configure.
Subsystem numbers can be 2..255, standard, unused. The default for map is standard. The default for bssap and cap
is unused.

110
6 Optional Common Application Setup
6.1 NAS Common

By default, a number of the NAS Common parameters will function as is. To properly configure the
MME, the parameters need to be modified for the specific network operation. For an S4-SGSN,
‘version’ must be set to 9.5.0 or greater.
Step # Action
1 Set the NAS common parameters.
user@host% set mme-sgsn interface nas nas-common reset-timer 30

reset-timer 30;
version 9.5.0;
6.2 LI – Lawful Intercept
Attention:
ALL LI configuration must be done via the lea user account or a user with lea
permissions.
Enabling the LI feature must be done via the admin user account or a user with
admin permissions.

111
Optional Common Application Setup
Step # Action
1 From the admin user account (or a user with admin permissions), enable the feature.
admin@host % set mme-sgsn feature control lawful-intercept status on
2 From the lea user account (or a user with lea permissions (see Adding a User), add the local LI
Interface. A loopback interface is required for the LI interface IP address.
lea@host % set mme-sgsn interface x x-if routing-instance <routing-instance> ip-address <LI IP

Address> max-active-targets <max-active-targets> version <version> dscp-mark <dscp-mark>
lea@host % set mme-sgsn interface x x-if routing-instance EPCLi01 ip-address 172.16.52.32 max-
active-targets 1000 version 10.4.0 dscp-mark de
ALERT: This presumes that the IP appearance on a virtual router is already done in the prior steps.
3 Add entry for LIG (via the lea user account or a user with lea permissions).
lea@host % set mme-sgsn interface x lig <LIG IP Address> <LIG Port>
6.2.1 HI2 Protocol Support

As shown in the following figure, HI2 protocol support involves two interfaces:
 OAM interface where command access is only available to LEA users over an SSH interface
 Delivery of IRI messaging over X2 via the HI2 protocol

112
Figure 1. LI HI Reference Model
Follow the steps in this procedure to:
 activate this feature and regulate this features behavior,
 define the nodes that receive IRI messages for activated targets
 configure targets to be monitored,
 observe feature behavior
Step # Action
1 Generate a TCP profile, if desired, to configure the socket used for LI delivery of IRI messages.
As an ‘admin’ or ‘lea’ user in config mode:
lea@host% set mme-sgsn interface tcp li_df2_profile keep-alive-timer 600 keep-alive-interval 75
keep-alive-probe 10
2 Configure the behavior to use for the LI interface.

As a ‘lea’ user in config mode:
lea@host% set mme-sgsn interface x x-if routing-instance EPCCore01 ip-address 192.168.41.26
version 10.4.0 dscp-mark de max-active-targets 1000
ALERT: This presumes that the IP appearance on a virtual router is already performed in a prior step.
lea@host% set mme-sgsn interface x x2-if keep-alive-timer 300 reconnect-timer 15 tcp-profile
li_df2_profile
lea@host% set mme-sgsn interface x x2-if df md_node1 ip-address 192.168.10.1 port 102
lea@host% set mme-sgsn interface x x2-if df md_node2 ip-address 192.168.10.2 port 102

As an ‘admin’ user in config mode:
admin@host% set mme-sgsn feature control lawful-intercept status on
4 Add a target.

113
Step # Action
As a ‘lea’ user in operational mode:
lea@host> request mme-sgsn interface x x1 target add imsi 12345678901 lawful-intercept-identifier
“case 123” primary-delivery-connection md_node1 secondary-delivery-connection md_node2
lea@host> request mme-sgsn interface x x1 target add imei 123456789012345 lawful-intercept-

identifier “warrant 42” primary-delivery-connection md_node1 location-report enable
lea@host> request mme-sgsn interface x x1 target add msisdn 2223334444 lawful-intercept-

identifier “HS 03/03/2014 #12345” primary-delivery-connection md_node2 location-report enable
5 Remove a target.
lea@host> request mme-sgsn interface x x1 target delete imei 123456789012345 lawful-intercept-
identifier “warrant 42”
5a Clear all targets.

lea@host> request mme-sgsn interface x x1 target clear
This request will result in the deletion of all targets from the database. Proceed? [no,yes]
Success : Targets clear
6 Display all targets.

lea@host> show mme-sgsn interface x x1 target
7 Display a particular target.

lea@host> show mme-sgsn interface x x1 target imsi 12345678901 lawful-intercept-identifier “case
123”
8 Enable PM statistics for the x2 interface.

As a ‘lea’ user in config mode:
lea@host% set mme-sgsn interface x x-if collected-stats enable
9 Display statistics / counters for the x2 interface.

If an ‘admin’ user in operational mode and PM statistics are enabled:
admin@host> show mme-sgsn statistics x x2
If a ‘lea’ user in operational mode and the PM statistics are disabled:
lea@host> show mme-sgsn interface x x2
lea@host> show mme-sgsn interface x x2 df
6.3 Roamer Classification

The MME/SGSN provides for optional configuration to allow classification of subscribers as roamers
based on IMSI mask, which is typically fixed per roaming partner.

114
Step # Action
1 Add a new subscriber-class record to be used for classifying a specific set of roamers (up to 16 are
allowed).
ALERT: The imsi mask is a prefix match, so a 4 digit mask implies a match on the first 4 digits, for
example.
user@host% set mme-sgsn subscriber imsi-range <IMSI-RANGE> service-area global subscriber-class

partnerx
user@host% set mme-sgsn subscriber subscriber-class partnerx subscriber-type roamer csfb true
user@host% show mme-sgsn subscriber subscriber-class partnerx

subscriber-type roamer;
rfsp-index use-subscribed-value;
csfb true;
snr-apn-operator-id default.apnoi.gprs;
snr-reject-cause-code undefined-gmm-cause-0;
snr-emm-reject-cause-code undefined-emm-cause-0;
local-qos-pdn-access-type hplmn;
charging-char-for-gateway-sel disable;
2 Set the protocol type for PLMN (where PLMN-ID is MCC and MNC, 5 or 6 digits total).
Chose gtp or pmip for protocol type (latter for CDMA networks typically) and enable/disable the sending
of NOR messages from MME to HSS.
user@host% set mme-sgsn subscriber subscriber-plmn <PLMN-ID> protocol-type gtp suppress-hss-

notify disable
3 Add naptr-record (only for MME) and a-record to resolve the APNs for the roamers. Refer to the DNS
Service section.
6.4 SNR (Seamless National Roaming)

Step # Action
1 Enable the feature and add a subscriber-class.
user@host% set mme-sgsn feature control seamless-national-roaming status on

Add a subscriber-class with the desired snr-apn-operator-id and snr-reject-cause-code.
Syntax:
user@host% set mme-sgsn subscriber subscriber-class <subscriber-class name> forbidden-ta-list
<forbidden ta list> eq-plmn-list <eq plmn list> forbidden-apn-list <forbidden apn
list>subscriber-type snr-roamer rfsp-index use-subscribed-value local-qos-profile <local-qos-
profile> csfb <csfb> voice-domain-profile <voice-domain-profile> local-eps-qos-entry <local-eps-
qos-entry> local-qos-pdn-access-type <local-qos-pdn-access-type> snr-apn-operator-id <snr-apn-
operator-id> charging-char-for-gateway-sel <charging-char-for-gateway-sel> snr-reject-cause-code
<snr-reject-cause-code>
user@host% show mme-sgsn subscriber subscriber-class snr1

subscriber-type snr-roamer;
rfsp-index use-subscribed-value;
csfb true;
snr-apn-operator-id default.apnoi.gprs;
snr-reject-cause-code eps-service-not-allowed-7;
snr-emm-reject-cause-code network-failure-17;
local-qos-pdn-access-type hplmn;

115
Step # Action
charging-char-for-gateway-sel disable;
2 Add the service-area.

Add the service areas (PLMN/LAC/RAC) serviced by the SGSN.
Syntax:
user@host% set mme-sgsn service-area routing-area <plmn> <lac> <rac> rncid-list <rncid-list>
nseid-list <nseid-list> timezone <system timezone>
3 Add the imsi-range.

Add the range of IMSIs (range) desired to be given a specific treatment defined by the subscriber-class and classified
based on the service areas.
Syntax:
user@host% set mme-sgsn subscriber imsi-range <range> service-area rai:<RAI> subscriber-class
<name>
user@host% set mme-sgsn subscriber imsi-range 05234 service-area plmn:<plmn-id> subscriber-class

snr1
6.4.1 Roamer Control

Roamer control enables network operators the ability to regulate access for subscribers of partner
operators where the network is shared. The type of access is based upon roaming service
agreements with the network operator. The MME/SGSN allows network operators to define local
policies to restrict access or control the type of access for specific groups of roamers. Operator
Determined Barring (ODB) of roamers based on HSS/HLR subscription data is supported. Network
operators are also able to define local EPS Quality of Service (QoS) policies to
enforce/downgrade/negotiate the QoS for roamers and IMS subscribers.
Step # Action
1 Turn on the Seamless National Roaming feature in the feature-control table.
user@host% set mme-sgsn feature control seamless-national-roaming status on
2 Configure subscriber class to restrict roamer access.
user@host% set mme-sgsn subscriber subscriber-class roam-restrict subscriber-type roamer snr-emm-

reject-cause-code 13 snr-emm-reject-cause-code 13
3 Configure the IMSI range for roamers with restricted access.
user@host% set mme-sgsn =subscriber imsi-range 31278 service-area global subscriber-class roam-
restrict
4 Configure subscriber class to treat roamers as homers.
user@host% set mme-sgsn subscriber subscriber-class roam-as-home subscriber-type snr-roamer

local-qos-pdn-access-type hplmn handover-restriction none
5 Configure the IMSI range for roamers treated as homers.

116
Step # Action
user@host% set mme-sgsn subscriber imsi-range 41323 service-area global subscriber-class roam-as-
home
6 Configure the subscriber PLMN with local-breakout.
user@host% set mme-sgsn subscriber subscriber-plmn 33123 local-breakout allow

user@host% set mme-sgsn subscriber subscriber-plmn 33123 local-breakout-apn-list apn1
user@host% set mme-sgsn subscriber subscriber-plmn 33123 local-breakout-apn-list apn2
7 Turn on ODB of Packet Oriented Services feature support for s6-if.
user@host% set mme-sgsn interface s6 s6-if odb-ps enable
8 Turn on ODB of Packet Oriented Services feature support for gr-if.
user@host% set mme-sgsn interface gr gr-if odb-ps enable
9 Turn on the Local EPS QoS Control feature in the feature-control table.
user@host% set mme-sgsn feature control local-eps-qos-control status on
10 Configure the QoS Profile for IMS default bearers.
user@host% set mme-sgsn subscriber bearer-limits-profile ims-default qos-class-identifier qci5

11 Configure the QoS Profile for IMS dedicated bearers.
user@host% set mme-sgsn subscriber bearer-limits-profile ims-dedicated qos-class-identifier qci1

12 Configure Local EPS QoS entry for IMS APN.
user@host% set mme-sgsn subscriber local-eps-qos-entry ims default-bearer-limits-profile ims-

default dedicated-bearer-limits-profile ims-dedicated local-qos-action negotiate
Following is example configuration of IMS QoS Profile not allowing QCI 5 for default bearer and not
allowing QCI 1 for dedicated bearers:

user@host% set mme-sgsn subscriber local-eps-qos-entry ims default-bearer-limits-profile ims-
default dedicated-bearer-limits-profile ims-dedicated local-qos-action negotiate

117
6.5 PLMN Based Admission Controls and Alarms

This PLMN based admission control feature provides the operator the ability to control attaches, Inter
MME TAU, and dedicated bearer setup of their roaming partner subscribers. This includes control
over both the rate and maximums for a particular PLMN; e.g. the operator can control rate at which a
partners mobiles can attach to the MME and SGSN, as well the maximum number of subscriber and
bearer supported for that partner operator.
Step # Action
1 Turn the feature on in the feature-control table.
user@host% set mme-sgsn feature control plmn-based-reporting-and-control status on
2 Add a PLMN entry in the plmn-load-control entity and adjust settings per PLMN as desired.
user@host% set mme-sgsn subscriber plmn-load-control 31298 ms-att-reqs-threshold 10000 load-

control enable
user@host% show mme-sgsn subscriber plmn-load-control

31298 {
ms-att-reqs-threshold 10000;
ms-irau-reqs-threshold 0;
ms-pdpc-act-attempts-threshold 0;
ms-itau-reqs-threshold 0;
ms-dedbearer-reqs-threshold 0;
current-attach-subs-threshold 0;
current-pdp-context-threshold 0;
current-act-bearer-threshold 0;
load-control enable;
}
3 Add a load-control profile in the load-control-profile entity and modify as desired.

Syntax:
user@host% set mme-sgsn subscriber load-control-profile alarm-update-interval <alarm-update-
interval> attach-reject-cause <attach-reject-cause> irau-reject-cause <irau-reject-cause> itau-
reject-cause <itau-reject-cause> ms-act-reject-cause <ms-act-reject-cause>
Example: adjusting the alarm update interval in minutes
user@host% set mme-sgsn subscriber load-control-profile alarm-update-interval 10
user@host% show mme-sgsn subscriber load-control-profile

alarm-update-interval 10;
attach-reject-cause 0;
irau-reject-cause 0;
ms-act-reject-cause 0;
itau-reject-cause 0;
4 Enable load control on a per PLMN basis when it is ready.
user@host% set mme-sgsn subscriber plmn-load-control 31298 load-control enable
5 Watch for PLMN based rate (MmeSc 1317) and level (MmeSc 1318) alarms.
user@host> show log epc | match MmeSc | match 1317

user@host> show log epc | match MmeSc | match 1318
6 Watch performance measurements.

118
Step # Action
user@host> show mme-sgsn statistics sc loadControl
6.6 Load Rebalancing

This feature provides the ability to gracefully offload subscribers from MME/SGSN on a per-MPU or
per node basis. It can be configured to be passive or take a varying level of action to move the users
to another node or blade.
Step # Action
1 Configure the behavior to use for service shutdown commands.
user@host% show mme-sgsn subscriber service-shutdown

connected-subs-action offload-all;
idle-subs-action offload-with-paging;
duration 20;
Default values are shown above.

If you wish to change one of them, use the modify command:
user@host% set mme-sgsn subscriber service-shutdown connected-subs-action detach
2 Initiate shutdown using CLI commands (blocking) per VM.

Example of VM shutdown, 1 VM at a time:
user@host> request mme-sgsn system callp shutdown unit-id <unit-id>
Example of offload one particular SU passively:

user@host> request mme-sgsn subscriber offload start service name SC51 connected-mode-action
passive idle-mode-action passive finish-in 40 hold-duration 1440
Example offload all SU with more aggressive action:

user@host> request mme-sgsn subscriber offload start all connected-mode-action offload-all idle-
mode-action offload-after-tau-or-sr finish-in 60 hold-duration 2000
6.7 Directional Offload

This feature enhances the existing offload mechanism by providing additional cli options to let the
operator direct a specified single UE or a specified number of UEs to a specified single target
MME/SGSN in the same pool.
This enhancement provides the following maintenance actions to the operator:
 Perform offline software update of a node by moving all the UEs off of one MME/SGSN and to
other MME/SGSN in the same pool
 Allows for targeted testing of new nodes, configuration, or functionality in the network by moving a
specified number of UEs without impact to the rest of the subscribers

119
 Move a single UE from one MME/SGSN to a specified MME/SGSN
The verb ‘move’ under ‘request mme-sgsn subscriber’ enables the operator to move a particular IMSI
from the source node (SGSN/MME) to the target node (SGSN/MME).
Sample command for 4G subscriber:
user@host>request mme-sgsn subscriber move imsi 312980911000699 target-mme-ip-address

192.24.25.178
Sample command for 3G subscriber:
user@host> request mme-sgsn subscriber move imsi 452980911000719 target-sgsn-ip-address

192.24.25.214
Sample show command for “show offload” with detail display:
user@host> show mme-sgsn subscriber offload detail

mme-sgsn subscriber offload
service callp0-0
location vsim041
connected-mode-action passive
idle-mode-action passive
finish-in 20
hold-duration 1440
current-active-subscribers 0
current-idle-subscribers 0
finish-in-remaining 19
hold-duration-remaining 1439
offload-type "NO OFFLOAD IN PROGRESS"
target-mme-ip-address 123.12.12.1
target-sgsn-ip-address 134.45.34.2
ue-qty 1000
ue-state connected
6.8 UE Purge
The optional UE purge feature is used by the MME to inform the HSS that it has deleted the
subscription and MM context of a detached UE.
The Operator can select MME’s behavior after the completion of the Detach procedure.
Purge can be initiated for different Detach and Subscriber types.
The Purge function can be triggered immediately or after a configured time period.
UE detach types are as follows:
Detach type Explanation
all All Detach types

120
Detach type Explanation
explicit MME or UE initiated procedure
implicit MME implicitly detaches the UE
oam-forced Operator initiated detach using the CLI
Subscriber types are as follows:
Subscriber Type Explanation
homer Only Subscribers who are homed on this network
roamer Only Subscribers who are roaming on this network
All All Subscribers types
For each detach type and Subscriber type combination, an inactive age needs to be set. A purge for
an inactive UE meeting both the detach and UE type constraints of the UE purge setting will occur
only after its inactivity period exceeds the inactive age of the setting.
Setting the inactive age to immediate or a very low value (like less than a day) will increase signaling
to/from the HSS in the case where UEs reattach shortly after being purged. A low value is only to be
used if the node is operating close to a UE context limit and requires contexts to be freed quickly for
use by other active UEs.
A value of 24 hours is useful to clean up contexts from inactive UEs such as roamers. If context
resources are not a concern but signaling traffic to the HSS is a concern, a high value of upto 31 days
can be set.
MME provides the following PMs to track messaging for purge activity.
GroupSet Group Name Register Name Description
s6 sc SUB.PuaRecv The number of Purge UE answer messages received

s6 sc SUB.PurFail The number of Purge UE request messages failed
s6 sc SUB.PurSent The number of Purge UE request messages sent
Use this procedure to activate and define UE purge.
Step # Action
1 Activate the feature.
user@host% set mme-sgsn feature control ue-purge status on
2 Define the purge triggers.
user@host% set mme-sgsn feature purge-trigger <detach type> all ue-type all inactive-age
immediate

121
Step # Action
user@host% show mme-sgsn feature purge-trigger <all/explicit/implicit/oam-forced/ue-type>
all ue-type all inactive-age immediate;
user@host% set mme-sgsn feature purge-trigger explicit ue-type all inactive-age 5

user@host% set mme-sgsn feature purge-trigger oam-forced roamer inactive-age immediate
user@host% show mme-sgsn feature purge-trigger

explicit ue-type all inactive-age 5;
oam-forced ue-type roamer inactive-age immediate;
6.9 Overload Controls

Use this procedure to configure overload controls.
Step # Action
1 Display the default subscriber overload configuration.
user@host% show mme-sgsn engineering subscriber-overload

minor-onset 70;
minor-abate 65;
minor-action reject-roamer-itau-irau;
minor-ovld enable;
major-onset 80;
major-abate 75;
major-action reject-all-itau-irau;
major-ovld enable;
critical-onset 90;
critical-abate 85;
critical-action reject-all-s1-iu-inc-ho;
2 Modify and display subscriber overload parameters.

user@host% set mme-sgsn engineering subscriber-overload minor-action reject-roamer-attach
user@host% show mme-sgsn engineering subscriber-overload
minor-onset 70;
minor-abate 65;
minor-action reject-roamer-attach;
minor-ovld enable;
major-onset 80;
major-abate 75;
major-ovld enable;
critical-onset 90;
critical-abate 85;
critical-action reject-all-s1-iu-inc-ho;
3 Display default configuration for bearer overload.
user@host% show mme-sgsn engineering bearer-overload

minor-onset 70;
minor-abate 65;
minor-ovld disable;
major-onset 80;

122
Step # Action
major-abate 75;
major-ovld disable;
critical-onset 90;
critical-abate 85;
critical-action reject-bearer-setup;
critical-ovld disable;
4 Modify and display configuration for bearer overload.
user@host% set mme-sgsn engineering bearer-overload minor-onset 70
user@host% show mme-sgsn engineering bearer-overload

minor-onset 70;
minor-abate 65;
minor-ovld disable;
major-onset 80;
major-abate 75;
major-ovld disable;
critical-onset 90;
critical-abate 85;
critical-action reject-bearer-setup;
5 Display the default configuration for congestion overload.
user@host% show mme-sgsn engineering congestion-overload

minor-onset 75;
minor-abate 65;
minor-action ignore-attach;
minor-ovld enable;
major-onset 80;
major-abate 75;
major-action ignore-itau-irau;
major-ovld enable;
critical-onset 90;
critical-abate 85;
critical-action reject-roamer-s1-inc-ho;
6 Modify and display the configuration for congestion overload.
user@host% set mme-sgsn engineering congestion-overload minor-onset 70
user@host% show mme-sgsn engineering congestion-overload

minor-onset 70;
minor-abate 65;
minor-action ignore-attach;
minor-ovld enable;
major-onset 80;
major-abate 75;
major-action ignore-itau-irau;
major-ovld enable;
critical-onset 90;
critical-abate 85;
critical-action reject-roamer-s1-inc-ho;

123
6.10 Femto Cell Support

This feature enables support for interconnecting the MME and SGSN to an HeNB GW or HNB GW
respectively with the purpose of supporting HeNBs and HNBs. The H(e)NB GW is generically referred
to as the Femto Gateway (FGW). The MME/SGSN is updated to support the functionality associated
with the H(e)NBs which includes Closed Subscriber Groups (CSG) and Local IP Access (LIPA). Note
that HeNBs can be directly connected to the MME, but they will be treated the same as a macro
eNBs; HNBs cannot be directly connected to the SGSN since HNBs use the Iuh protocol instead of
the Iu protocol. Perform the following actions to configure support for FGW.
Step # Action
1 Ensure that all the interfaces are provisioned for version 10.
Common:
user@host% set mme-sgsn interface nas nas-common version 10.10.0
MME/Combo:
SGSN/Combo:
user@host% set mme-sgsn interface iu iu-if version 10.9.0
user@host% set mme-sgsn interface ss7 ss7 version 10.8.0
Optional: If CAMEL is configured, modify the version to 10.

user@host% set mme-sgsn interface ge ge-if ge version 10.1.0
Optional: If Billing is configured, modify the version to 10.

user@host% set mme-sgsn services accounting sgsn-ga-profile version 10.12.0
2 Enable the Femto Cell Support feature.

user@host% set mme-sgsn feature control femto-cell-support status on
3 Configure a new sctp-profile for FGW and link it to the s1 s1-if fgw-sctp-profile.
Add a new sctp-profile for FGWs. Use higher values for rx-buffer-size and tx-buffer-size than are used for the default
s1 sctp-profile (ALERT: the values below are just examples):
user@host% set mme-sgsn interface sctp fgwdefaultsctp rto-initial 500 rto-min 100 rto-max 1000
association-init-max-transmit 2 association-max-retrans 2 path-max-retrans 2 no-delay true max-
in-stream 10 max-out-stream 10 hb-interval 30 rx-buffer-size 1000000 tx-buffer-size 2000000 sack-
delay 200 sack-frequency 2
Link the new fgwdefaultsctp profile to s1 s1-if fgw-sctp-profile:

user@host% set mme-sgsn interface s1 s1-if fgw-sctp-profile fgwdefaultsctp
4 Configure fgw-rnc (UMTS) or fgw-enb (LTE).

Configuring fgw-rnc:

124
Step # Action
If spare capacity does not exist on the system then existing rnc entities must be removed to make space for the fgw-
rnc entries. The following action is not required on systems with spare capacity.
user@host% delete mme-sgsn interface iu rnc 123
Add fgw-rnc entry:
user@host% set mme-sgsn interface iu fgw-rnc 123 destination-point-code 2.42.3 callp-service-id 5
direct-tunnel enable max-iu-connections 1000
user@host% show mme-sgsn interface iu fgw-rnc
123 {
callp-service-id 5;
direct-tunnel enable;
max-iu-connections 1000;
}
Configuring fgw-enb:
If spare capacity does not exist on the system then existing s1 entities must be removed to make space for the fgw-
enb entities.
Add s1 fgw-enb entries for each FGW:
user@host% set mme-sgsn interface s1 fgw-enb 11111 enodeb-id 1234 ip-address1 172.16.241.148 ip-
address2 0.0.0.0 unit 4
user@host% show mme-sgsn interface s1 fgw-enb

11111 enodeb-id 1234 {
ip-address1 172.16.241.148;
unit 4;
}
6.11 VoLTE Support

IP Multimedia Subsystem (IMS) is a standardized architecture for telecom operators that want to
provide mobile and fixed multimedia services. It uses a Voice-over-IP (VoIP) implementation based
on a 3GPP standardized implementation of Session Initiation Protocol (SIP), and runs over the
standard Internet Protocol (IP). Follow these steps to provision support for VoLTE.
Step # Action
1 Provision or ims-voice-sgsn for the nodal control for an MME or S4-SGSN.
user@host% set mme-sgsn interface nas gmm ims-voice-sgsn enable
2 Provision per-PLMN IMS supportability for the PLMNs with roaming.
user@host% set mme-sgsn subscriber subscriber-plmn 50631 ims-support enable
3 Provision to allow T-ADS retrieval from the HSS.
user@host% set mme-sgsn interface s6 s6-if t-ads-retrieval enable
4 Provision single QCI=1 bearer restriction.
user@host% set mme-sgsn subscriber nodal-qos single-qci1-bearer enable

125
Step # Action
5 Provision the voice paging related parameters.
user@host% set mme-sgsn interface nas emm voice-paging-t3413 3

user@host% set mme-sgsn interface nas emm voice-paging-retry-n3413 0
6 Enable s5-gtp selection for VoLTE.
user@host% set mme-sgsn feature control s5-gtp-volte-enforce status on
6.12 Local EPS QoS Control

This feature adds support for Local EPS QoS Control in the MME and S4-SGSN. Local EPS QoS
Control allows the operator to define Local EPS Qos profiles which are used to downgrade/enforce
the QoS parameters that are received from HSS and enforce the QoS parameters that’s received
from the S-GW.
MME:
Local EPS Qos Control is performed during Attach, PDN Connectivity, UE/GW Initiated Activation,
UE/GW/HSS Initiated Modification, Inter MME/Inter RAT Tracking Area Update and Inter MME/Inter
RAT S1 Handover procedures.
S4-SGSN:
Local EPS Qos Control is performed during the Session Management procedures of PDP Context
Activation, PDP Context Modification, HSS Initiated Modification, Inter-SGSN Routing Area Update,
and Inter-SGSN SRNS Handover (for 3G mobiles).
Follow these steps to provision Local EPS QoS Control.
Step # Action
1 Configure a bearer-limits-profile for Local EPS Control default bearers (Note: Provision QCIs in the
range of 5-9).
user@host% set mme-sgsn subscriber bearer-limits-profile local-qos-default1 qos-class-identifier
qci5 arp-priority 1 pvi disable pci enable max-bitrate-uplink 0 max-bitrate-downlink 0
guaranteed-bitrate-uplink 0 guaranteed-bitrate-downlink 0

qci6 arp-priority 2 pci enable pvi disable max-bitrate-uplink 0 max-bitrate-downlink 0

qci7 arp-priority 3 pci disable pvi enable max-bitrate-uplink 0 max-bitrate-downlink 0

qci9 arp-priority 4 max-bitrate-uplink 0 max-bitrate-downlink 0 guaranteed-bitrate-uplink 0
guaranteed-bitrate-downlink 0

126
Step # Action
user@host% show mme-sgsn subscriber bearer-limits-profile local-qos-default1 qos-class-identifier
qci5
arp-priority 1;
max-bitrate-uplink 0;
max-bitrate-downlink 0;
guaranteed-bitrate-uplink 0;
guaranteed-bitrate-downlink 0;
pci enable;
pvi disable;

qci6
arp-priority 2;
pci enable;
pvi disable;

qci7
arp-priority 2;
pci disable;
pvi enable;
user@host% show mme-sgsn subscriber bearer-limits-profile

local-qos-default2 qos-class-identifier qci9
arp-priority 4;
pci disable;
pvi enable;
2 Configure a bearer-limits-profile for Local EPS dedicated bearers (Note: Provision QCIs in the range of
1-9).
user@host% set mme-sgsn subscriber bearer-limits-profile local-eps-dedicated1 qos-class-

identifier qci1 arp-priority 1 pci enable pvi disable max-bitrate-uplink 100000 max-bitrate-
downlink 100000 guaranteed-bitrate-uplink 100000 guaranteed-bitrate-downlink 100000

identifier qci3 arp-priority 2 pci enable pvi disable max-bitrate-uplink 200000 max-bitrate-

identifier qci2 arp-priority 3 pci disable pvi enable max-bitrate-uplink 294868 max-bitrate-
user@host% show mme-sgsn subscriber bearer-limits-profile local-eps-dedicated1 qos-class-

identifier qci1
arp-priority 1;
pci enable;
pvi disable;

127
Step # Action
local-eps-dedicated2 qos-class-identifier qci3
arp-priority 2;
pci enable;
pvi disable;

local-eps-dedicated3 qos-class-identifier qci2
arp-priority 3;
pci disable;
pvi enable;
3 Configure Local EPS QOS entries.
user@host% set mme-sgsn subscriber local-eps-qos-entry local-eps-qos1 default-bearer-limits-

profile local-eps-default1 dedicated-bearer-limits-profile local-eps-dedicated1 apn-ambr-downlink
1000 apn-ambr-uplink 1000 ue-ambr-downlink 1000 ue-ambr-uplink 1000 local-qos-action downgrade

profile local-eps-default1

profile local-eps-default2 dedicated-bearer-limits-profile local-eps-dedicated1
4 Link the subscriber-class to the Local EPS QoS entries.
user@host% set mme-sgsn subscriber subscriber-class subscriber-class1 local-eps-qos-entry local-

eps-qos1
user@host% set mme-sgsn subscriber subscriber-class subscriber-class2 local-eps-qos-entry local-

eps-qos2
user@host% set mme-sgsn subscriber subscriber-class subscriber-class1 local-qos-pdn-access-type

hplmn
6.13 PCC Based NPLI

The IMS network can request for NPLI (Network Provided Location Information) from the Policy and
Charging Rules Function (PCRF). The request for NPLI from PCRF is forwarded to the MME/SGSN
via the SGW.
When the feature is enabled, the following are the NPLI sent by the MME/SGSN to the SGW:
 E-UTRAN-Cell-Global-Identity (ECGI) – only in 4G

128
 Cell-Global-Identity (CGI) - only in 2G
 Service-Area-Identity (SAI) – only in 3G
 UE TimeZone – Included only when there is change in UE time zone
 Closed Subscriber Group ID (CSG-ID)
 User CSG Information (UCI)
Follow these steps to enable PCC based NPLI.
Step # Action
1 Verify/set the gtp tunnel version for gtpv2 to Rel 10.
user@host% set mme-sgsn feature control pcc-npli status on
6.14 Flexible Gateway Selection

This feature allows the operator to configure a secondary Access Point Name (APN) source for the
cases where the MME/SGSN could not identify the APN to be used for the activation.
The cases where the MME/SGSN fails to select APN as per APN selection described in 3GPP TS
23.060 ANNEX A areas under:
 APN requested, APN(R), by the User Equipment (UE), does not match any APN configuration in
the subscription and there is no wild card (WC) in the subscription
 APN(R), does not match any APN configuration in the subscription but there is a wild card and
hence the APN(R) is used with the wild card but the DNS query fails
 No APN(R) and there is more than one APN configuration in the subscription
This feature allows the operator to configure a choice for the APN selection in the above cases. The
operator could select an APN from the subscription if available, or configure to use a locally
configured APN.
Step # Action
1 Check the apn-selection-profile linked to the subscriber class for which the feature is to be turned on.
user@host% show mme-sgsn subscriber subscriber-class

default {
local-qos-profile profile0;
voice-domain-profile default;
}
roam {
subscriber-type roamer;

129
apn-selection-profile exampleapnselection;
}
2 Check the “secondary-apn-source” for the “apn-selection-profile” linked
user@host% show mme-sgsn subscriber apn-selection-profile exampleapnselection | display

annotations
##
## local-config-default-pdn-type: PDN type to be used if locally configured APN is used Default
ipv4
##
## default: ipv4
##
## secondary-apn-source-gprs: Secondary-apn-source to select APN when regular selection fails for
GPRS based subscriptions Default off
## default: off
## package: affirmedcta-mmecheck
##
secondary-apn-source-gprs first-subscription-or-local;
##
## secondary-apn-source-epc: Secondary-apn-source to select APN when regular selection fails for
EPC based subscriptions Default off
##
## default: off
##
## local-config-apn: Replacement APN-NI in case the secondary-apn-source is local-config or the
default APN-NI Default default.apnni.com
## range: 1 .. 63
## default: default.apnni.com
## match: Valid values are: case-sensitive alphabetical characters, digits, . and -
## match (regex): ^[A-Za-z0-9]([.-]|[A-Za-z0-9])*$
## package: affirmedcta-mmecheck
##
local-config-apn newapn.com;
##
## wildcard-dns-fail-override: Is APN-selection after the DNS with APN (Req) and wild card
subscription fails allowed Default disable
##
## default: disable
With the default settings the feature is in disabled state. If the operator wants to turn the feature “on” and intends to
select the first subscription and if not present then fall back to the locally configured APN-NI “newapn.com” then the
following should be modified:
user@host% set mme-sgsn subscriber apn-selection-profile exampleapnselection secondary-apn-
source-gprs first-subscription-or-local local-config-apn newapn.com
user@host% show mme-sgsn subscriber apn-selection-profile exampleapnselection
secondary-apn-source-gprs first-subscription-or-local;
local-config-apn newapn.com;
6.15 UPM Enhancements

During periods of high UE traffic spikes that exceed 80% of capacity, the UPM within the MME can
experience overload conditions. When a UPM is overloaded, UEs might experience slower response
time or might be rejected. This feature provides additional UPM load balancing functionality to
alleviate UPM congestion issues that may occur during infrequent cases like:
 a large number of UEs with similar cellular activity patterns, for instance UE activation during
morning and evening commutes. (Predictable)

130
 a large number of UEs initiating access to the network due to specific events such as New Year’s
Eve. (Predictable)
 a large number of UEs moving from one MME to another MME due to planned or unplanned
MME outage. (Both)
 a large number of UEs initiating access to the network due to a natural event. (Unpredictable)
UPM load balancing functionality consists of UPM congestion monitoring and load balancing
management procedures. UPM congestion monitoring includes a new alarm that is raised and
cleared based on configurable thresholds, and CLI display enhancements.
Step # Action
1 Configure UPM TPS Alarm Congestion Threshold.
user@host% set mme-sgsn engineering upm-tps-congestion minor-ovld enable
user@host% set mme-sgsn engineering upm-tps-congestion minor-onset 4000
user@host% show mme-sgsn engineering upm-tps-congestion

minor-onset 4000;
minor-abate 3500;
minor-ovld enable;
major-onset 4500;
major-abate 4100;
major-ovld enable;
critical-onset 5000;
critical-abate 4600;
2 Show UPM status information.
user@host> show mme-sgsn status upm

UNIT PENDING
LOCATION SERVICE ID PATHS WEIGHT TPS TRANS
--------------------------------------------------------
vse05-vm03 sig 0 4 1048 0 0
vse06-vm03 sig 1 2 1002 0 0
[ok][2015-01-21 10:34:20]
6.16 eNB Relocation

The Directed eNB Move feature provides the operator with the ability to manually move or relocate an
Evolved Node B (eNB) from one signaling Virtual Machine (VM) to another. The relocation of an eNB
is performed in-service, meaning there is no impact to the users connected to the MME from the eNB.
Operators can relocate both home and Macro eNBs. This includes Home eNB gateways, which are
classified as macro eNBs.
In previous functionality the MME load balanced the eNBs across the VMs when they initially
connected to it. This distribution of eNBs across VMs only changed if there was a VM SHUTDOWN, a
VM reboot or if the eNB re-connected. This prevented the MME from taking advantage of a newly

131
added capacity. The new eNB relocation functionality allows operators to move eNBs to a newly
added VM, or any other VM, without requiring the eNB to re-connect and thus allowing operators a
chance to manipulate the eNB distribution across the VMs.
The steps presented here are an example of how to use this feature to move eNB from one VM to
another.
Step # Action
1 Find where the eNB is currently located if the Global eNB id of the eNB to be relocated is known:
user@host> show mme-sgsn interface s1 enb plmn-id 504321

PLMN ENODEB ENODEB IP ENODEB
ID ID TYPE IP ADDRESS1 ADDRESS2 NAME SERVICE
-------------------------------------------------------------------
504321 4032 macro 172.16.236.27 - eNB01 sig-1
504321 4034 macro 172.16.236.27 - eNB02 sig-0
504321 4036 macro 172.16.236.26 - eNB03 sig-0
504321 4038 macro 172.16.236.27 - eNB04 sig-0
504321 5039 macro 172.16.236.26 - HeNB01 sig-0
504321 7033 macro 172.16.241.185 - eNB03 sig-0
[ok][2015-01-21 08:32:11]
If the global enb id is not known then one of the below can be used as key:
• [enodeb-name <name>] or
• [ip-address1 <address> [ip-address2 <address>]])
If none of the above key(s) are known then the following command can be used to show all the eNBs connected to
the MME
user@host> show mme-sgsn interface s1 enb
PLMN ENODEB ENODEB IP ENODEB
ID ID TYPE IP ADDRESS1 ADDRESS2 NAME SERVICE
-------------------------------------------------------------------
504321 4032 macro 172.16.236.27 - eNB01 sig-1
504321 4034 macro 172.16.236.27 - eNB02 sig-0
504321 4036 macro 172.16.236.26 - eNB03 sig-0
504321 4038 macro 172.16.236.27 - eNB04 sig-0
504321 5039 macro 172.16.236.26 - HeNB01 sig-0
504321 7033 macro 172.16.241.185 - eNB03 sig-0
[ok][2015-01-21 08:34:47]
2 To display the load status of the target or all the SIG VMs use the following command:
user@host> show mme-sgsn statistics s1 general

REF REF
ENTITY SUBENTITY REGISTER
SERVICE TYPE REF ENTITY TAG INFO REGISTER NAME VALUE
--------------------------------------------------------------------------------
sig-0 s1-if service=sig/unit=0 - S1.NbrEnbConnections 5
sig-1 s1-if service=sig/unit=1 - S1.NbrEnbConnections 1
Note here that the attribute register-value indicates the number of eNBs connected on a particular VM.
3 To check the CPU load on the SIG VMs, use the following command:
user@host> show mme-sgsn statistics platform resource

REF REF
ENTITY SUBENTITY REGISTER
SERVICE TYPE REF ENTITY TAG INFO REGISTER NAME VALUE
---------------------------------------------------------------------------------
callp0-0 system service=callp0/unit=0 - CpuUtilization 8
callp0-0 system service=callp0/unit=0 - MemoryUtilization 7

132
Step # Action
callp0-1 system service=callp0/unit=1 - CpuUtilization 7
callp0-1 system service=callp0/unit=1 - MemoryUtilization 7
data-0 system service=data/unit=0 - CpuUtilization 1
data-0 system service=data/unit=0 - MemoryUtilization 5
data-1 system service=data/unit=1 - CpuUtilization 0
data-1 system service=data/unit=1 - MemoryUtilization 2
mgmt-0 system service=mgmt/unit=0 - CpuUtilization 1
mgmt-0 system service=mgmt/unit=0 - MemoryUtilization 4
mgmt-1 system service=mgmt/unit=1 - CpuUtilization 1
mgmt-1 system service=mgmt/unit=1 - MemoryUtilization 3
rm-0 system service=rm/unit=0 - CpuUtilization 1
rm-0 system service=rm/unit=0 - MemoryUtilization 4
rm-1 system service=rm/unit=1 - CpuUtilization 1
rm-1 system service=rm/unit=1 - MemoryUtilization 4
sig-0 system service=sig/unit=0 - CpuUtilization 1
sig-0 system service=sig/unit=0 - MemoryUtilization 4
sig-1 system service=sig/unit=1 - CpuUtilization 1
sig-1 system service=sig/unit=1 - MemoryUtilization 4
[ok][2015-01-21 08:43:44]
4 To learn the s1-capacity of each of the signaling VM, use the following command:
user@host> show configuration mme-sgsn engineering s1-capacity

max-enodebs 32;
[ok][2015-01-21 08:47:32]
Once we learn:
• The identity of the eNB, in terms of Global eNB ID, that we want to move
• The load on all the signaling VMs so that we could make sure that the target has space
• The capacity of each of the signaling VM to find where all the capacity to serve this eNB remains
• Or checking which VM has more free CPU
The following step would be used to move the eNB.
5 To move the eNB execute the following command:
Syntax:
user@host> request mme-sgsn interface s1 enb relocate plmn-id <plmn-id> enodeb-id <enodeb-id>
enodeb-type <enodeb-type> service <vm-instance>
assuming that in our example the Global eNB id of the eNB is:
plmn-id : 50631
enodeb-id : 2213
enodeb-type : macro
and we want to move the eNB from sig-2 to sig-1 the command would be:
user@host> request mme-sgsn interface s1 enb relocate plmn-id 50631 enodeb-id 2213 enodeb-type
macro service sig-1
6.17 TAC Level Control

This feature enables per Tracking Area Level Control and multi-timezone support on the MME/SGSN.
The MME/SGSN TAC Level Control provides the capability to configure whether IMS voice is
supported for a UE as a function of service-area and the UE service agreement. Service control is
available at three configuration levels:

133
 Per TAC
 Per PLMN
 Per IMSI range
TAC Level Control affects the following:
 IMS Voice
 emergency support
 timezone
 VLR/E-SMLC host lookup
6.17.1 IMS Voice over PS and IMS Emergency
Step # Action
1 Provision the IMS Emergency feature to on for the MME:
user@host% set mme-sgsn feature control ims-emergency status on
2 Provision location area(s) and associated VLR pool name(s) for the MME or S4-SGSN:
Syntax:
user@host% set mme-sgsn service-area location-area <plmn-id> <lac> vlr-pool-name <vlr pool name>
user@host% set mme-sgsn service-area location-area 50631 0x2280 vlr-pool-name vlrPool1
user@host% set mme-sgsn service-area location-area 50502 0x40ff vlr-pool-name vlrPool2
3 Provision per-node support for:

• IMS Voice over PS / IMS Emergency (MME), or
• IMS Voice over PS (S4-SGSN) :
user@host% set mme-sgsn service-area tracking-area 000000 0x0000 lac 0x333 ims-support enable
emergency-support enable e-smlc-pool-name pool1
OR
user@host% set mme-sgsn interface nas gmm default ims-voice-sgsn on
4 Provision per-TAC support for IMS Voice over PS / IMS Emergency (MME):
user@host% set mme-sgsn service-area tracking-area 50631 0x1001 lac 0x333 ims-support disable
emergency-support disable
user@host% set mme-sgsn service-area tracking-area 50502 0x1001 lac 0x333 ims-support enable
emergency-support disable
5 Provision per-PLMN support for IMS Voice over PS for those PLMNs with roaming:
user@host% set mme-sgsn subscriber subscriber-plmn 50631 ims-support enable
Optionally, for VPLMN resource utilization:

134
Step # Action
user@host% set mme-sgsn subscriber subscriber-plmn 50631 ims-local-breakout allow
6 Provision per-subscriber class support for IMS Voice over PS:
user@host% set mme-sgsn subscriber subscriber-class roamer-profile ims-vops-agreement enable

user@host% set mme-sgsn subscriber imsi-range 777 service-area global subscriber-class roamer-
profile
6.17.2 Timezone
Timezone provisioning may be performed independently of or in conjunction with the IMS Voice of
PS/IMS Emergency provisioning.
Step # Action
1 Provision the default timezone (MME):
user@host% set mme-sgsn service-area tracking-area 000000 0x0000 timezone America/Chicago
2 Provision per-TAC support for timezone (MME):
user@host% set mme-sgsn service-area tracking-area 50631 0x1001 timezone America/Indianapolis
3 Provision per-TAC support for timezone (SGSN):
user@host% set mme-sgsn service-area routing-area 50631 0x1022 0x44 timezone America/Indianapolis
6.17.3 MME Location Service

The E-SMLC pool name to service area mapping may be performed independently of or in
conjunction with the IMS Voice over PS/IMS Emergency provisioning. See section Location Service
for configuration details.

135
7 Bring Application into Service
7.1 Bring MME into Service

The following is an example of the CLI commands to start the MME applications. It is a simplified
example for a simplex system.
Step # Action
1 Unlock the different VMs to bring up the system.
user@host> request mme-sgsn system mgmt unlock unit-id 0

user@host> request mme-sgsn system callp unlock unit-id 0
user@host> request mme-sgsn system sig unlock unit-id 0
2 Verify the status of the VMs and ensure that they are all unlocked, the default state for the VM.
user@host> show mme-sgsn status system

UNIT
LOCATION SERVICE ID ADMIN OPER STANDBY CPU MEMORY SYNC
------------------------------------------------------------------------------------
vse05-vm01 mgmt 0 unlocked enabled providing service 1 4 -
vse06-vm01 mgmt 1 unlocked enabled hot standby 1 3 -
vse05-vm04 callp0 0 unlocked enabled providing service 8 7 100
vse06-vm04 callp0 1 unlocked enabled hot standby 6 7 -
vse05-vm05 data 0 unlocked enabled providing service 1 5 -
vse06-vm05 data 1 locked enabled not set 1 2 -
vse05-vm02 rm 0 unlocked enabled providing service 1 4 100
vse06-vm02 rm 1 unlocked enabled hot standby 1 4 -
vse05-vm03 sig 0 unlocked enabled providing service 1 4 -
[ok][2015-01-21 08:50:28]
7.2 Bring SGSN into Service

The following is an example of the CLI commands to start the SGSN applications. It is a simplified
example for a simplex system.
Step # Action
1 Unlock the different VMs to bring up the system.

user@host> request mme-sgsn system sig unlock unit-id 0
user@host> request mme-sgsn system data unlock unit-id 0
2 Verify the status of the VMs and ensure that they are all unlocked, the default state for the VM.

136
Bring Application into Service
Step # Action
user@host> show mme-sgsn status system

UNIT
------------------------------------------------------------------------------------
vse05-vm01 mgmt 0 unlocked enabled providing service 1 4 -
vse06-vm01 mgmt 1 unlocked enabled hot standby 1 3 -
vse06-vm04 callp0 1 unlocked enabled hot standby 6 7 -
vse05-vm05 data 0 unlocked enabled providing service 1 5 -
vse06-vm05 data 1 locked enabled not set 1 2 -
vse05-vm02 rm 0 unlocked enabled providing service 1 4 100
vse06-vm02 rm 1 unlocked enabled hot standby 1 4 -
[ok][2015-01-21 08:50:28]

137
8 Combined Node Variations
The MME/SGSN may operate as standalone MME, standalone S4-SGSN, standalone Gn-SGSN, or
a combined MME/SGSN. A combined node brings network level efficiency by reducing the number of
inter-nodal messages required to support the inter-RAT (Radio Access Technology) mobility events
when the UE moves between access technologies. And it brings nodal level efficiency by sharing
control plane resources between all three access technologies.
A GPRS/UMTS operator may choose to add LTE, and that can be done while the node is in-service
depending on the extent of re-engineering required. Or an LTE operator may want to add UMTS
support, which can be done while the node is in-service depending on the extent of re-engineering,
required. Before starting a procedure to add a new technology support to an existing node, consult
the engineering guidelines to ensure the proper number of VMs are added, and that the optimal
service topology is selected.
8.1 Add MME to an SGSN
8.1.1 Overview
When adding MME function to an SGSN, there should already be compute nodes and VMs
configured for bearer path. However, the number may need to be adjusted if more control plane
capability is needed. If more VMs are needed for control plane, the existing DATA VMs should be
removed such that CALLP VMs can be configured. On the existing CALLP VMs, the subscriber
capacity and RNC fanout capacity may need to be reduced to leave room to introduce eNB fanout. In
the SGSN case, some impact to the UE may be required. The majority of the UEs can be migrated in-
service to other SGSNs in the same SGSN pool. This is done using the same CLI command
mentioned in the MME case (request mme-sgsn subscriber offload). If DATA VMs need to
be reconfigured for control plane, then some UEs will be required to re-activate their PDP contexts.
If a combined node is deployed from scratch, then the following interfaces should be deployed:
 S1 interface
 S11 interface
 S6/S13 interface
 S4 interface
 S3/S16 interface
 Gb interface
 Iu interface, at least one of the Gb or Iu shall be deployed

138
Combined Node Variations
Other interfaces can be optionally deployed based on the need, these include:
 Gs interface (if combined Attach and RAU is required)
 Gd interface (if SMS over Gd is required)
 Gr interface (for roamer from non-EPS capable networks, the UE can only acquire service on the
SGSN side)
 Gn interface (if not already configured on the MME and mobility to legacy SGSN or session
management to legacy GGSN is required)
 Ga interface (if billing function on the SGSN is required)
 Gf interface (if S13 is not configured when the EIR only supports Gf)
 X interface (if legal intercept is required)
 SGs interface (if Circuit Switched Fallback is required for the MME)
 SBc interface (if ETWS function is required for the MME)
 S101 interface (if mobility between eHRPD network is required for the MME)
 S102 interface (if CSFB for 1xRTT is required for the MME)
Before the software components are installed, an engineering exercise should determine the number
of compute nodes and VMs for the control plane and data plane. The data plane related VMs should
be configured on the data plane compute nodes whereas the control plane related VMs should be
configured on the control plane compute nodes.
Minimal Steps:
1. Add/modify S6 interface per the MME section of this document

a. Optionally enable dual-vector-type and g-u-vector limit under s6-if
b. Select S6 on a per UE basis instead of Gr by configuring hss-hlr-routing for IMSI ranges
2. Add S11 per MME section of this document
a. Already Covered by tunnel profile entry under gtp-profile
b. But need to ensure DNS is configured appropriately.
3. Add S1 per MME section of this document
4. Optionally add SGs interface if circuit switched fallback is desired
5. Add mme-pool entries and consider expanding to more than one mme-code per pool to reduce
PTMSI/TLLI collisions
6. Add mme-pool to existing plmn which already has sgsn-pool
a. Only need to lock all SC if deleting existing sgsn-pool from PLMN, or modify the NRI values
to align to the MME code.

139
8.2 Add SGSN to an MME
8.2.1 Overview
If the node is currently configured as a standalone MME node, then the following interfaces needs to
be configured to enable the S4-SGSN function:
 S4 (control and bearer)
 S3/S16 for SGSN to SGSN/MME mobility management (may include DNS setup)
 At least one of:
→ Gb interface to GPRS access
→ Iu interface to UMTS access
Additionally, the following interfaces can be optionally configured depending on specific needs:
 Gs interface (if combined Attach and RAU is required)
 Gd interface (if SMS over Gd is required)
 Gr interface (for roamer from non-EPS capable networks, the UE can only acquire service on the
SGSN side)
 Gn interface (if not already configured on the MME and mobility to legacy SGSN or session
management to legacy GGSN is required)
 Gf interface (if S13 is not already configured on the MME and the EIR only supports Gf)
When adding SGSN function to an MME, a given set of compute nodes and VMs should be reserved
for SGSN bearer path usage. If there are already MME specific VMs configured on these compute
nodes, they should be removed first. Further, on the remaining compute nodes(the control plane
compute nodes) the subscriber capacity and/or eNodeB fan out capacity may need to be reduced to
leave room to introduce RNC fanout capabilities. To ensure that there is no impact to the subscribers,
it is recommended that the graceful offload function be performed to migrate the subscribers from the
compute nodes to be reconfigured. For example, the following CLI command can be issued to
‘migrate’ the subscribers:
user@host> request mme-sgsn subscriber offload start service <service name>

140
8.3 PLMN Configuration
8.3.1 Overview
This section outlines the recommendations for PLMN and pool configuration on the MME/SGSN to
minimize the GUTI/PTMSI collisions. As per 3GPP specification 23.003 Section 2.8.2, when
GUTI/PTMSI conversion are done during inter RAT mobility, the bit 23 to bit 16 of the MTMSI,
corresponding to the NRI byte in PTMSI, are not copied. For example, during GUTI to PTMSI
conversion, this byte within the MTMSI (23rd to 16th) is not copied onto PTMSI, and instead is
replaced with the MME code value from the GUTI. This necessitates a Combo MME/SGSN to have a
uniform allocation schema for GUTI/PTMSI so as to avoid collisions.
The configuration of sgsn-pool is optional for a combined MME/SGSN. If the sgsn-pool is not
configured, all the PLMNs configured on the combo node support all the access types, 2G, 3G, and
4G. When the “default” sgsn-pool is configured, a PLMN must be explicitly configured with sgsn-pool
as “default” to support 2G/3G. If a PLMN is configured with both mme-pool and sgsn-pool, it supports
all the access types (2G/3G/4G). If there is also a PLMN with only sgsn-pool configured as “default”
(mme-pool is “none”), then the PLMN supports only 2G/3G. Since there are two different PLMNs
which is going to use same set of NRI values, there is potential for PTMSI collisions.
Combo/SGSN supports only one SGSN-pool “default” and all the PLMNs configured with this sgsn-
pool uses the same set of NRI values for PTMSI allocation. Therefore, if “default” sgsn-pool is added
to PLMNs having different mme-pool configuration, the PTMSI allocations could potentially collide. In
order to avoid such collisions, the “default” sgsn-pool is recommended to be configured only with one
PLMN or PLMNs with the same mme-pool configuration. Additionally, the mme-codes configured
under the mme-pool should be unique across all the pools.
8.3.2 Example
8.3.2.1 Combo MME/SGSN with PLMN supporting 2G/3G and 4G
Example 1
user@host% show mme-sgsn service-area plmn

10067 mme-pool pool1 sgsn-pool default;
50603 mme-pool pool2 sgsn-pool none;
ALERT: PLMNs ‘10067’ and ‘50502’ supports 2G/3G/4G. PLMN ‘50603’ and ‘50631’ are 4G only and
does not support 2G/3G.
Example 2:

141

ALERT: Both PLMNs having mme-pool 'pool1' supports 2G/3G/4G. PLMNs having 'pool2' does not
support 2G/3G.Removing sgsn-pool from PLMN '10067' converts both the PLMNs in pool to 4G only.
Example 3

ALERT: PLMN ‘10067’ does not support 4G. PLMNs having ‘pool2’ support 4G/3G/2G. However
there is high possibility of GUTI/PTMSI collisions for UEs served by PLMN ‘10067’ and ‘50603’ as
they share same sgsn-pool. Hence this configuration is not recommended.
8.3.2.2 Combo MME/SGSN without combo PLMNs
Example 4

10067 mme-pool none sgsn-pool default;
ALERT: PLMN '10067' supports 2G/3G. PLMNs under mme-pool 'pool1' and 'pool2' are 4G only
8.3.2.3 Combo MME/SGSN without ‘default’ sgsn-pool configured
Example 5

ALERT: If node is COMBO and 'default' sgsn-pool is not configured, then all PLMNs support
2G/3G/4G. There is higher possibility of GUTI/PTMSI collisions for UEs served by PLMN having
pool1 and pool2 and hence this configuration is not recommended. If node is COMBO and ‘default’
sgsn-pool is configured, then all above PLMNs will support only 4G.
To facilitate this, it is recommended to have multiple MME codes configured per MME pool, so that
the combo node uses the same in a round robin fashion.

142
9 FGW Configuration
9.1 FGW Platform Configuration

Start the FGW configuration using all the processes and procedures located in Hardware Description
and Setup. Then proceed to the Common Setup section and perform only these processes and
procedures:
 OAM Mandatory
The following table illustrates the FGW application software functionality to virtual machine mapping.
Table 6. VM Type to FGW Application Mapping
Virtual Machine Type FGW Application

MGMT RM, PWS, Trace
CALLP SC, S1ENB, S1MME
9.2 FGW Mandatory Configuration
9.2.1 Enable Virtual Machines
Step # Action
1 Define the MGMT VMs for RM, PWS and Trace
user@host> request fgw system mgmt unlock unit-id 0

user@host> request fgw system mgmt unlock unit-id 1
2 Define the CALLP VMs for the FGW SC, S1ENB and S1MME applications
Each of the 3 applications, is 1+1 spared and runs on each CALLP VM with a spare.
user@host> request fgw system callp 0 unlock unit-id 0

user@host> request fgw system callp 0 unlock unit-id 1
3 Define FGW SC capacity
user@host% set fgw <fgw-name> engineering sc-capacity fgwSc connections-per-su 455

143
FGW Configuration
9.2.2 Activate PLMNs supported by FGW
Step # Action
1 Configure MME Pool. Group id, code, relative capacity configured.
user@host% set fgw service-area mme-area 1 name vsim2Area
user@host% set fgw service-area mme-area 1 tac-range-list
0145,1001,1002,51A2,3012,1003,1004,2001,2002,61A2,3014,1004
user@host% set fgw service-area mme-area 1 plmn-list 50631,50502,45005
2 Configure PLMN
user@host% set fgw service-area plmn 50631 mme-pool pool1

9.2.3 Activate S1 ENB Interface

FGW requires configuration of one S1 ENB interface per CALLP VM and link it to an SCTP profile.
Each FGW S1 ENB supports 10K HeNBs and the operator can add additional CALLP VMs for scaling
the HeNBs up to 100K.
Step # Action
user@host% set fgw interface sctp s1EnbSctp rto-initial 500

user@host% set fgw interface sctp s1EnbSctp rto-min 250
user@host% set fgw interface sctp s1EnbSctp rto-max 2000
user@host% set fgw interface sctp s1EnbSctp path-max-retrans 5
user@host% set fgw interface sctp s1EnbSctp association-init-max-transmit 3
user@host% set fgw interface sctp s1EnbSctp association-max-retrans 6
user@host% set fgw interface sctp s1EnbSctp no-delay true
user@host% set fgw interface sctp s1EnbSctp max-out-stream 11
user@host% set fgw interface sctp s1EnbSctp max-in-stream 11
user@host% set fgw interface sctp s1EnbSctp hb-interval 30
2 Define S1 Interface Profile.
user@host% set fgw interface s1 profile sctp-profile s1EnbSctp
3 Define S1 Interface (One per FGW CALLP). A loopback interface is required for the S1 interface IP
address.
user@host% set fgw interface s1 s1-if callp0 routing-instance1 EPCAccess01

user@host% set fgw interface s1 s1-if callp0 ip-address1-v4 172.18.248.51
user@host% set fgw interface s1 s1-if callp0 port 36412
4 Define the Max ENBs for each CALLP.
user@host% set fgw engineering s1-capacity callp0 max-num-enodeb 8

144
FGW Configuration
9.2.4 Activate S1 MME Interface

FGW requires configuration of one S1 MME interface and link it to an SCTP profile.
Step # Action
1 Configure the SCTP layer, and set the rx and tx buffer values to larger than normal SCTP defaults.
user@host% set fgw interface sctp s1MmeSctp rto-initial 500

user@host% set fgw interface sctp s1MmeSctp rto-min 250
user@host% set fgw interface sctp s1MmeSctp rto-max 2000
user@host% set fgw interface sctp s1MmeSctp path-max-retrans 5
user@host% set fgw interface sctp s1MmeSctp association-init-max-transmit 3
user@host% set fgw interface sctp s1MmeSctp association-max-retrans 6
user@host% set fgw interface sctp s1MmeSctp no-delay true
user@host% set fgw interface sctp s1MmeSctp max-out-stream 9
user@host% set fgw interface sctp s1MmeSctp max-in-stream 9
user@host% set fgw interface sctp s1MmeSctp hb-interval 30
2 Define S1 MME Interface. A loopback interface is required for the S1 MME interface IP address.
user@host% set fgw interface s1 s1-mme-if routing-instance1 EPCAccess01

user@host% set fgw interface s1 s1-mme-if sctp-profile s1MmeSctp
user@host% set fgw interface s1 s1-mme-if ip-address1 137.168.69.180
9.2.5 Define MME Peer

FGW supports multiple SCTP associations towards MME Peers. Each Association has to be
associated with an MME, MME Profile and MME Area.
Step # Action
1 Configure the MME Area.
user@host% set fgw service-area mme-area 1 name vsim2Area

user@host% set fgw service-area mme-area 1 tac-range-list
0145,1001,1002,51A2,3012,1003,1004,2001,2002,61A2,3014,1004
user@host% set fgw service-area mme-area 1 plmn-list 50631,50502,45005
2 Define MME Peer.
user@host% set fgw interface s1 s1-mme-peer 1 sg-name callp-service-id 0

user@host% set fgw interface s1 s1-mme-peer 1 ip-address1 172.18.248.49
user@host% set fgw interface s1 s1-mme-peer 1 remote-port 36412
3 Define MME Association Profile.

user@host% set fgw interface s1 s1-mme-association-profile 1 plmn-id 45005
user@host% set fgw interface s1 s1-mme-association-profile 1 enodeb-id 99
user@host% set fgw interface s1 s1-mme-association-profile 1 enodeb-name vmme-fgw01-099
4 Define MME Association.

user@host% set fgw interface s1 s1-mme-association 1 s1-mme-peer-index 1
user@host% set fgw interface s1 s1-mme-association 1 s1-mme-assoc-profile-index 1

145
FGW Configuration
Step # Action
user@host% set fgw interface s1 s1-mme-association 1 mme-area-index 1

user@host% set fgw interface s1 s1-mme-association 1 local-port 33825
9.3 FGW Optional Configuration
9.3.1 FGW Engineering
Step # Action
1 Display the default UE Connection Overload configuration.
user@host% show fgw engineering fgw-ue-connection-overload

minor-ovld enable;
minor-onset 70;
minor-abate 65;
minor-action ignore-mo-normal-priority;
major-ovld enable;
major-onset 80;
major-abate 75;
major-action ignore-mo-normal-priority;
critical-onset 90;
critical-abate 85;
critical-action ignore-mo-normal-priority;
2 Display the default Congestion Overload configuration.
user@host% show fgw engineering fgw-congestion-overload

minor-ovld enable;
minor-onset 70;
minor-abate 65;
minor-action ignore-mo-normal-priority;
major-ovld enable;
major-onset 80;
major-abate 75;
major-action ignore-mo-normal-priority;
critical-onset 90;
critical-abate 85;
critical-action ignore-mo-normal-priority;
3 Display the default S1 Overload configuration.
user@host% show fgw engineering fgw-s1-overload

ovld-start-minor-cause reject-delay-tolerant;
ovld-start-major-cause permit-hpriority-mt-only;
ovld-start-critical-cause permit-emg-mt-only;
4 Display the default FGW SC configuration.
user@host% show fgw engineering fgw-sc-engineering

bearer-average 300

146
FGW Configuration
9.3.2 FGW Optional Features
Step # Action
1 Display the default FGW Feature Control configuration.
user@host% show fgw feature control
trace status on;
2 Activate Cell Traffic Tracing for HeNB by specifying the HeNB PLMN, HeNB ENB ID, Trace Reference
ID, Trace targets, Trace interfaces and Trace control entity IP.
Trace feature is enabled by default. Operators can active Cell Traffic tracing for 10 HeNBs.
Syntax:
user@host% set fgw trace session <enodeb-plmn-id> enodeb-id <enodeb-id> session-id <session-id>
fgw-s1-interface-mask <fgw-s1-interface-mask> trace-depth <trace-depth> nms-ip <nms-ip>
9.3.3 FGW Status Profile
Step # Action
1 Display the default FGW Health Profile.
user@host% show fgw status profile

update-period 3;
window 15;
connection-major-threshold 90;
connection-minor-threshold 95;
connection-clear-threshold 98;
9.3.4 FGW Multimedia Priority Service

The FGW allows UE’s S1-AP connection classification as priority connections based on Allocation
Retention Priority (ARP) of bearers. Priority connections are exempt from Connection release
abatement actions during overload conditions. Operators can adjust the ARP limit to classify priority
connections.
Step # Action
1 Display MPS ARP limit (default – 1).
user@host% show fgw nodal-qos

mps-arp-limit 1;
single-qci1-bearer disable;

147
FGW Configuration
9.4 Bring FGW into Service
9.4.1 Activate the Virtual Machines
Step # Action
1 Unlock the different VMs to bring up the system
user@host> request fgw mgmt unlock unit-id 0

user@host> request fgw mgmt unlock unit-id 1
user@host> request fgw callp unlock unit-id 0
user@host> request fgw callp unlock unit-id 1
2 Verify the status of the VMs and ensure they are all unlocked, the default state for the VM.
user@host> show fgw status system

UNIT
-------------------------------------------------------------------------------------------------
vse01-vm01 mgmt 0 unlocked enabled providing service 1 2 0
vse02-vm01 mgmt 1 locked enabled hot standby 1 1 -
vse02-vm02 callp0 1 locked enabled hot standby 0 1 -

148
10 Maintenance
10.1 System Maintenance Commands

The applications are initialized and managed through the CLI (or NETCONF) on the active MGMT
VM. Using these APIs and the data model, craftsperson and applications have the ability to provision
and manage virtual machines of either MGMT, RM, LB, CALLP, SIG or DATA types.
The following commands are used to manage the VMs. Note that the <vmtype> is one of ‘mgmt’, 'rm',
‘sig’, 'lb', or ‘data’, and if the VM type is ‘callp’, an extra argument, “<service-id>” is required.
 Show system status across all VMs:
→ show mme-sgsn status system
 Lock VM (RM/LB/MGMT/DATA/SIG):
→ request mme-sgsn system <vmtype> lock unit-id <VM unit identifier> [force]
Example: request mme-sgsn system mgmt lock unit-id 0 force
 Lock VM (CALLP)
 request mme-sgsn system callp lock <service-id> unit-id <VM unit identifier>
[force]
Example: request mme-sgsn system callp lock 0 unit-id 0 force
 Unlock VM (RM/LB/MGMT/DATA/SIG)
→ request mme-sgsn system <vmtype> unlock unit-id <VM unit identifier>
Example: request mme-sgsn system mgmt unlock unit-id 0
 Unlock VM (CALLP)
→ request mme-sgsn system callp unlock unit-id <VM unit identifier>
Example: request mme-sgsn system callp unlock unit-id 0
 Switchover (CALLP)
 request mme-sgsn system callp <service-id> switchover
Example: request mme-sgsn system callp 0 switchover
 Shutdown (MGMT/DATA/SIG)
→ request mme-sgsn system <vmtype> shutdown unit-id <VM unit identifier> [force]
Example: request mme-sgsn system mgmt shutdown unit-id 0 force
 Shutdown (CALLP)

149
Maintenance
→ request mme-sgsn system callp shutdown <service-id> unit-id <VM unit id> [force]
Example: request mme-sgsn system callp shutdown 0 unit-id 0 force
10.1.1 Partial Nodal Reset for GTP

If GTP configuration calls for a partial nodal reset to take effect, use this section.
Warning:
The order in which a partial nodal reset is performed is critical.
Lock the following VMs in this order:
1. All DATA VMs
2. All SIG VMs
3. All CALLP VM pairs with standby first and active second
4. The standby RM VM
5. The active RM VM
The following is an example:
user@host% request mme-sgsn system data lock unit-id <n> force

user@host% request mme-sgsn system sig lock unit-id <m> force
user@host% request mme-sgsn system callp <x> lock unit-id <z>
user@host% request mme-sgsn system callp <x> lock unit-id <y> force
user@host% request mme-sgsn system rm lock unit-id <b>
user@host% request mme-sgsn system rm lock unit-id <a> force
Unlock the following VMs in this order:
1. The RM VM pair
2. The CALLP VM pairs
3. The SIG VMs
4. The DATA VMs
The following is an example:

150
Maintenance
user@host% request mme-sgsn system rm unlock unit-id <a>

user@host% request mme-sgsn system rm unlock unit-id <b>
user@host% request mme-sgsn system callp <x> unlock unit-id <y>
user@host% request mme-sgsn system callp <x> unlock unit-id <z>
user@host% request mme-sgsn system sig unlock unit-id <m>
user@host% request mme-sgsn system data unlock unit-id <n>
10.2 System Health Check

System health checks indicate how the system is performing and whether any VMs or applications
require attention.
The following commands provide general system health information:
 System storage information:
→ user@host> show mme-sgsn status storage
 Per VM information, and relevant high-level OSI administrative and system usage information:
→ user@host> show mme-sgsn status system
 VM storage information:
→ user@host> show mme-sgsn status storage
The following commands provide application level health information:
 LTE performance indicators:
→ user@host> show mme-sgsn status lte
 UMTS performance indicators:
→ user@host> show mme-sgsn status umts
 GPRS performance indicators:
→ user@host> show mme-sgsn status gprs
 Combo performance indicators:
→ user@host> show mme-sgsn status combo
 Check the ENB information:
→ user@host> show mme-sgsn interface s1 enb
 Check Diameter peer status:
→ user@host> show mme-sgsn interface diameter peer
 Check SGS VLR status:

151
Maintenance
→ user@host> show mme-sgsn interface sgs vlr
 Per group-set/group/register level performance indicators:
→ user@host> show mme-sgsn statistics <group-set> <group>
 Enb counts:
→ user@host> show mme-sgsn statistics nodal s1
Most of these commands are incorporated into a “status” script that can be invoked from the CLI. Use
“describe status” to see the location of the script for customization.
10.3 Software Update

See the Software Update section in the Operator Guide specific to the solution in place, either:
 vMME Operator Guide for the Contrail Solution
 vMME Operator Guide for the VMWare Solution
10.4 Backup/Restore
The following procedures describe backup/restore for configuration data of the MME/SGSN VNF. For
software restore, simply reinstall the selected VM images. There are two techniques for doing
configuration backup restore, but in MME8.1, the binary method is the only one that restores the user
accounts completely and LEA config. The XML method is quick for lab settings if user accounts do
not need to be fully restored (i.e. linux layer user setup), and LEA config is not a concern.
10.4.1 Binary File Method

The binary backup file system retains up to the last ten files on the node in /usr/local/epc/backups.
Older files are removed as newer ones are created to maintain the limit of ten or fewer.
10.4.1.1 Backup
user@host> request system recovery backup
Success : Backup request processed. Backup file vmcg40-Apr_23_01:34:47-backup-8.0-23.tar
present at /usr/local/epc/backups
[ok][2015-04-23 01:34:47]

152
Maintenance
10.4.1.2 Restore
Warning:
A reboot occurs automatically after the restore command is invoked.
user@host> file list /usr/local/epc/backups

user@host> request system recovery restore fileName vmcg40-Apr_23_01:34:47-backup-8.0-23.tar
Connection to host closed.
10.4.2 XML File Method

The limitations of this method are: 1) linux layer setups for users are not retained, 2) LEA interface
config is not retained. If LEA backup is required, that should be done separately by a LEA group user,
with a different XML file just for LEA.
10.4.2.1 Backup
Login as an admin class user.
user@host> save <backup-name> xml
ftp from /home/<userid>/<backup-name> to an off-board location
10.4.2.2 Restore
Login as an admin class user.
ftp the backup file to /home/<userid>/<backup-name>

user@host> load override <backup-name>
user@host> commit
10.5 Security
10.5.1 Login Classes

There are four authorization groups (privilege class levels):

153
Maintenance
 admin – Can view (show) and change (request/set) all configuration except for lea.
 operator – Can view (show) and change (request/set) all configuration except for lea and
aaa/nacm.
 lea (law enforcement agency) – Can only view (show) and change (request/set) lea related
configuration.
 viewer – Can view all configuration and operational data except for lea and aaa/nacm. This level
can perform show commands, but not request commands.
All the sub-commands associated with Lawful Intercept require a privilege class of lea.
10.5.2 Password Complexity Rules

Currently password complexity rules are not enforced. Enforcement will be in a future release.
10.5.3 Add a User

From the ‘admin’ account, follow these commands:
admin@host> configure
[ok][2014-05-08 23:53:52]
[edit]
admin@host% user ?
Possible completions:
add - Add user account
del - Delete user account
mod - Modify user password
show - Show configured user accounts
admin@host% user add
All changes will be committed at the end of this command. Do you want to continue?
[YES,no]
Enter user name: bob
Enter password:
Confirm password:
Choose a group for the user.
Available groups are: admin lea operator viewer
Enter group for user: operator
Adding user `bob' ...
Adding new user `bob' (1007) with group `operator' ...
Creating home directory `/home/bob' ...
Copying files from `/etc/skel' ...
Adding user 'bob' to the 'operator' group.
User info was successfully added - committing changes.
Commit complete.
[ok][2014-05-08 23:54:36]
[edit]
admin@host% user show

154
Maintenance
SSH
NAME UID GID PASSWORD KEYDIR HOMEDIR
----------------------------------------------------------------------------------
admin 1001 1001 $1$eVbSG..J$8EKIv9N5l4/OSETuMZNU40 /home/admin
bob 1007 1003 $1$7avF083L$Q0/xOjaEdmH2hZqN2z6GT. /home/bob
lea 1002 1002 $1$3b0jvqhP$TgsMGFgQOA38DX1kNlO170 /home/lea
operator 1003 1003 $1$603BmPyE$ij7cItjw5rScGAa519IXt/ /home/operator
viewer 1004 1004 $1$wY9m84vW$l1VEE9qxWTAZ6QgJPx/FA0 /home/viewer
[ok][2014-05-08 23:54:53]
[edit]
admin@host%
10.5.4 Delete a User

admin@host> configure
[ok][2014-05-09 06:05:06]
[edit]
admin@host% user del
[YES,no]
Enter user name: bob
gid 1003
Deleting user
Deleting user from the operator group.
Looking for files to backup/remove ...
Removing files ...
Removing user `bob' ...
Warning: group `operator' has no more members.
Done.
User info was successfully deleted - committing changes.
Commit complete.
[ok][2014-05-09 06:05:11]
[edit]
admin@host%
10.5.5 Modify a User

admin@host% user mod

[YES,no]
Enter user name: admin
Enter password:
Confirm password:
Linus password was reset.
AAA password was reset - committing changes.
Commit complete.

155
Maintenance
[ok][2014-05-09 06:05:52]
[edit]
admin@host%
10.5.6 View Security Logs

admin@host> show log security
<INFO> 21-Jan-2015::06:19:59.915 vse05-vm01 confd[12931]: audit user: admin/318 assigned
to groups: admin,operator
<INFO> 21-Jan-2015::06:20:04.000 vse05-vm01 confd[12931]: audit user: admin/319 assigned
to groups: admin,operator
<INFO> 21-Jan-2015::06:20:05.041 vse05-vm01 confd[12931]: audit user: admin/318 CLI
'operational top set complete-on-space false'
<INFO> 21-Jan-2015::06:20:05.041 vse05-vm01 confd[12931]: audit user: admin/318 CLI done
'operational top set complete-on-space false'
<INFO> 21-Jan-2015::06:20:07.653 vse05-vm01 confd[12931]: audit user: admin/318 CLI done
'operational top request mme-sgsn interface gtp path relocate ip-address 172.16.236.45
location vse05-vm03'
aborted
'operational top show mme-sgsn interface gtp path'
[snip]
Note: only admin group users have permission to see the contents of this file
10.5.7 View Active Sessions

admin@host> show user
SID USER CTX FROM PROTO LOGIN CONFIG MODE
*35 admin cli 172.16.245.121 ssh 06:05:01
[ok][2014-05-09 06:06:50]
admin@host>

156
11 Glossary
User is referred to the vMME Overview document for the Glossary.

157
Appendix A - Default Logins
A.1 System Default Login Information
The following table provides a list of the default system username and passwords for a newly
installed system. Remote access (telnet/ssh) cannot be performed via the root account. It is
recommended to change these passwords for a commercially deployed system.
Mode Default User Default Password

CLI admin admin
CLI operator operator
CLI lea lea
CLI viewer viewer
Unix root li69nux
Unix mtc mtc

158

Networks vMME Operator Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Networks vMME Operator Guide

Uploaded by

Copyright:

Available Formats

vMME

Affirmed Networks vMME Operator Guide

Part Number: 550-00328

AFFIRMED & DESIGN®, AN3000®, ACUITAS SERVICE MANAGEMENT SYSTEM®, AFFIRMED

Ref. # Part Number Document Name

Affirmed Networks vMME Operator Guide

2 New in this Release ............................................................................................................................. 3

3 Common Setup .................................................................................................................................... 4

4 MME Configuration ............................................................................................................................ 23

Affirmed Networks vMME Operator Guide

5 SGSN Configuration .......................................................................................................................... 68

Affirmed Networks vMME Operator Guide

6 Optional Common Application Setup .............................................................................................. 111

Affirmed Networks vMME Operator Guide

7 Bring Application into Service .......................................................................................................... 136

8 Combined Node Variations.............................................................................................................. 138

9 FGW Configuration .......................................................................................................................... 143

10 Maintenance .................................................................................................................................. 149

Affirmed Networks vMME Operator Guide

Appendix A - Default Logins ............................................................................................................... 158

Affirmed Networks vMME Operator Guide

Affirmed Networks vMME Operator Guide

Table 2. MME-SGSN TACACS+ client configuration example ......................................................... 13

Table 3. Attribute Combinations ........................................................................................................ 22

Table 4. VM Type to MME Application Mapping ............................................................................... 23

Table 5. VM Type to SGSN Application Mapping ............................................................................. 68

Table 6. VM Type to FGW Application Mapping ............................................................................. 143

Affirmed Networks vMME Operator Guide

1.1 Purpose of the Document

This document provides:

 Procedures for maintenance of the MME and SGSN functions.

 Hardware commissioning completed and the Contrail hypervisor is installed.

 Engineering and planning completed as described in the following document:

→ vMME and SGSN Engineering Guide

What this document does not cover:

 Platform/solution based installation content. This information is now housed in separate

→ vMME CM Reference Guide

→ vMME CLI Commands

→ vMME Fault Management Reference Guide

→ vMME Performance Management Reference Guide

→ vMME CSL Reference Guide

Relationship of the documents:

 The CM/CLI/FM/PM/CSL reference guides are word format references.

Affirmed Networks vMME Operator Guide

Affirmed Networks vMME Operator Guide

 AGW-24211 LI HI2 Protocol Support – New section HI2 Protocol Support

 AGW-24606 TACACS+ for AAA – New section TACACS+ for AAA

2.1 Documentation changes

Affirmed Networks vMME Operator Guide

3.1 Mandatory Common Setup

3.1.1 Platform Mandatory

3.1.1.1 Set System Timezone

The following configuration allows the timezone to be established.

user@host% set system timezone America/Chicago

3.1.1.2 Set System Contact and Location Information (Optional)

user@host % set system contact "Bob Smith x214 555-5555"

3.1.1.3 NTP Setup for Time Sync to External Server

An operator can setup NTP for up to three external servers.

user@host% set ntp server nist.time.nosc.us ip-address 96.226.242.9

Affirmed Networks vMME Operator Guide

3.1.2 OAM Mandatory

3.1.2.1 PM Collection Format and Timing

user@host% show mme-sgsn statistics

3.1.2.2 OAM IP Configuration