Module 3

EMS GUI Configuration

Objectives
Upon completion, you will be able to:
• Perform the Platform Configurations
• Perform the Interface Configurations
• Configure the IPSM local setting
• Configure the OMA setting
• Configure the RepoData Profile Server
• Configure the MAP settings
• Configure the RepoData
• Configure the Routing interworking
scenarios
• Configure the Routing details to SMSC
How System Starts Up
• ADM Boots Up with Local OS
• Various Services like dhcpd, named, mountd, NTP etc
• Uses Local HD (68G)
• RM – Resource manager
• Gets a DHCP IP from ADM
• Downloads OS related files and mOne binaries followed by configuration
• SI Blade
• Gets DHCP IP from ADM and downloads OS, software and configuration
• Uses RAM (1G) to store abovementioned
• Spare 2G RAM for operations
• Hard Disk only for logs and core-files etc (68 G)
Site Integration
Platform Management:
• Configure Shelf and Components
• Configure External IPs
• Setup Routes
• Setup NAT/Firewall Rules on RM
• Assign FQDNs
• Backup
• Alarms
CIQ Sample
• Mavenir Provides:
• System Specifications (Equipment list and so on)
• Site Requirements (Power, IPs, Configuration and so on)
• And more…
• Customer to provide:
• Administrative Information
• Cabling Matrix (Power, External IP)
• IP/FQDN Addresses
• Network Diagram
• And more…
EMS - Element Management System
Configuration
Configuration Management tab has 3 layers: Platform, Interface and RMS Application
configuration
Platform Terms
• Component
• A single physical blade
• Identified by physical location Shelf-Slot
• For example 0-9 is ADM-A Component
• Protection Group
• Also known as “Node”
• Combination of components existing of:
• Active Side
• Standby Side
• Identified by PG<ID> e.g. Node 1 = pg01
• pg01-active
• pg01-standby
Platform - Configuring Shelves
• Login to the CM GUI  Configuration  Platform Management  mOne  System Configuration 
Platform  Servers  Shelves

It indicates the assigned number of shelves

A unique IP address associated

with a selected shelf.
Platform - Configuring Component
• Login to the CM GUI  Configuration  Platform Management  mOne  System Configuration  Platform
 Servers  Component
Platform – IP Configuration
• Login to the RMS GUI  Configuration  Platform Management  mOne  System Configuration 
Platform  IP Configuration External IP Interface

Used to provision an interface to an external IP address.

Platform – IP Configuration
• Login to the RMS GUI  Configuration  Platform Management  mOne  System Configuration 
Platform  IP Configuration External IP Address

A separate unique external IP address is defined to communicate with

each external component
Platform – External Routes
• Login to the RMS GUI  Configuration  Platform Management  mOne  System Configuration 
Platform  IP Configuration External Routes
• Assign routes to components or Protection groups.

This is used to define the external routers (gateway) IP address.

Platform – FQDN Rules
• Login to the RMS GUI  Configuration  Platform Management  mOne  System Configuration 
Platform  IP Configuration Local FQDN
• Create FQDN and Assign to Local IPs

Used to define the domain name of the application servers.

Platform – NAT Services
• Login to the RMS GUI  Configuration  Platform Management  mOne
 System Configuration  Platform  IP Configuration NAT Services  • The NAT parameter group is
NAT used to define the NAT rules.
• Configure NAT/Firewall rules for RM • The Resource Manager (RM)
module acts as a firewall
towards the signalling
networks.
• Any Ingress or Egress
communication with external
network is allowed under the
NAT services.
• Any traffic that doesn't match
one of the NAT entries is
dropped.
• A NAT rule can be assigned
to a Service Pool, Protection
Group or a Component.
Platform – Service Pool
• Login to the CM GUI  Configuration  System Configuration  Platform  IP • A service pool
Configuration  NAT Services provides a pool of
IP addresses
within which a RM
can perform
internal load
balancing on
Ingress traffic.

• It is applicable to
UDP ingress
traffic or TCP
traffic where the
client is external
to mOne.
Configuring RMS Local – Remote Server
Platform – Backup & Restore
• Login to the CM GUI  Configuration  Platform Management  System Management  Backup
Interface Configuration
• IPSMGW to HSS

• IPSMGW to I/S-CSCF

• IPSMGW to STP/HLR

• IPSMGW to STP/MSC

• IPSMGW to STP/SMSC

• IPSMGW to DNS

• IPSMGW to NTP
Interface Configuration - IPSMGW to HSS
• Login to the EMS GUI  Configuration  Interface  Diameter
Interface Configuration - IPSMGW to I/S-CSCF
• Login to the EMS GUI  Configuration  Converged Messaging  Converged Configuration  Remote
Server
Interface Configuration - IPSMGW to STP/HLR
• Login to the EMS GUI  Configuration  Interface  Signaling Interface  SS7 Interface  SIGTRAN
Interface Configuration - IPSMGW to STP/MSC
• Login to the EMS GUI  Configuration  Interface  Signalling Interface  SS7 Interface  SIGTRAN

The interface between the IPSMGW and the MSC is MAP over SIGTRAN. This interface is used for IMS to CS
retry messages.
Interface Configuration - IPSMGW to STP/SMSC
• Login to the EMS GUI  Configuration  Interface  Signalling Interface  SS7 Interface  SIGTRAN

The interface between the IPSMGW and the SMSC is MAP over SIGTRAN. This interface is used for exchange of SRI-
SM query, MO-FSM and MT-FSM.
Interface Configuration - IPSMGW to DNS
• Login to the EMS GUI Configuration  Interface  DNS/ENUM  DNS Server

This interface is used for DNS queries.

Interface Configuration - IPSMGW to NTP
This is configured as below:
• /usr/IMS/exports/blade.cfg
• etc/ntp.conf
Configuring Interface - SCTP
• Login to the CM GUI  Configuration  Interface  Signaling Interface  SCTP Interface SCTP General
Configuring Interface – SS7
• Login to the CM GUI  Configuration  Interface  Signaling Interface  SS7 Interface SS7 Relay
Configuring Interface – SIP Interface
• Login to the CM GUI  Configuration  Interface  Signalling Interface  SIP  SIP Parameters
Configuring
IPSM Local

GUI Configuration
Site Integration
IPSMGW:
• Setup Local Configuration
• Change Local Parameters for each function
• Setup Remote Servers
IPSM Local Configuration
• Login to the CM GUI  Configuration  Converged Messaging  IPSMGW  IPSM Local Setting

Defines a system
wide operator-
specific routing
/interworking
logic.
IPSM Local Configuration - Local Setting details
IPSM Local Configuration - Local Setting details
IPSM Local Configuration - Local Setting details
RepoData Profile Server Configuration
• Login to the CM GUI  Configuration  Converged Messaging  IPSMGW  Local Configuration 
RepoData Profile Configuration

The parameters are fixed at the time of deployment.

OMA Settings
• Login to the CM GUI  Configuration  Converged Messaging  IPSMGW  Local
MAP Settings
• Login to the CM GUI  Configuration  Converged Messaging  IPSMGW  Local Configuration 
MAP Setting
RepoData Configuration
• Login to the CM GUI  Configuration  Converged Messaging  IPSMGW  Local Configuration 
RepoData Configuration
Prepaid Services
• Login to the CM GUI  Configuration  Converged Messaging  IPSMGW  Local Configuration  Prepaid
Server Configuration
Configuring Home Domain Names
• Login to the CM GUI  Configuration  Converged Messaging  IPSMGW  Local Configuration 
Home Domain Names
Configuring Routing Interworking
• Login to the CM GUI  Configuration  Converged Messaging  IPSMGW  Local Configuration 
Routing Interworking
Routing to SMSC
• Login to the CM GUI  Configuration  Converged Messaging  IPSMGW  Local Configuration 
Routing to SMSC
Configuring the Remote Servers
• Login   Configuration Converged Messaging  Converged Configuration  Remote Servers
Transrouting Profile
• Login  Configuration Converged Messaging  Converged Configuration  Service Profiles 
Transrouting
Configuring Service Profiles - Blacklists Configuration
• Login to the CM GUI  Configuration  Converged Messaging  Service Profiles
Configuring Service Profiles - Black List
• A Blacklist profile allows the operator to define a list of addresses for which no service is to be made available.
• It helps to determine whether a given SM is allowed to use the service.
• The Blacklist profile supports:
• configuring business logic
• for instance, rules to bar the originator/recipient from sending/receiving messages.
• allows operator to define a list of addresses which could be either blocked/untrusted.
• screening is applied on the source address received using the system wide default blacklist profile.
• ORGINATOR and RECIPIENT addresses or address prefixes can be configured
• The type of addresses supported by BlackList profiles are:
• IMSI
• MSISDN
• SHORTNUM
• The BlackList profile is configured on per Subscriber basis or as a system wide list.
• If the BlackList profile is not configured in Subscriber profile, default BlackList profile (index 0 in the BlackList
profile table) is used.
Configuring Service Profiles - COS
• The Originating, Terminating Class of
• Login to the CM GUI  Configuration  Converged Messaging  Service (COS) functionality allows the
Service Profiles operator to control the access to the
defined set of the application services for
the SMS subscribers and SMS Address
Groups.
• RMS supports two types of class of
services, as follows:
• Origination Class of Server (COS)
• A service which controls
whether a sending party is
allowed to send message
through LA, identified by LA Id.
• Terminating Class of Service (TCOS)
• A service which controls
whether the receiving
subscriber is able to receive
SM from LA.
• It also defines the traffic
combination type allowed for
terminating subscriber.