02 Open MGW Platform Introduction

Open MGW Introduction Ui5.
0
Open MGW Platform
Nokia Siemens Networks
Objectives
At the end of this module the participant will be able to
Describe High Availability Services model in Open MGW
List the Functional Units in Open MGW and explain their main
function.
Describe the Redundancy Models supported by HAS in the

Open MGW
Hardware Description
Open MGW Platform
Open MGW nodes and main interfaces
One Cabinet Configuration

create_mgw_1shelf.sh
First carrier pair in the shelf is equipped to slots 7 and 10

Second carrier pair in the shelf is equipped to slots 11 and 12
Open MGW Functional Architecture

Interface functions
ADSP1-A
Switching functions
AMC Carrier
TCU/ADSP1-B
DSP
DSP
DSP
Control functions
DSP
IPNI1/MPPAM-B
IP UP 1*10Gbps
IPNIU
Signal Processing
LMP
Ethernet
DSPM
Functional Unit
ACPI4
ISU/ACPI4-A
HCLB
TDM AMC
IPNI10/MPPAM-C
SGU
FI
BI
SISU
IP UP 4*Gbps
IPNIU
Ethernet
IP
O&M
ACPI4
Disk
Disk
CLA/ACPI4-A
HCLB
SGU
SISU
OMU
TDM AMC
TDMSNIU/SCNAM-B
CM
TDMSNIU
T
M
ADDF
TDM UP &
Signaling
TDM E1/T1
Sync. Clock
IP Signaling
R
T
M
AHUB3
HUB
TDM STM-1/OC3
High Availability Services model in Open MGW
High Availability Services model in Open MGW

Cluster :
The cluster is the topmost managed object in the system model.
The cluster consists of nodes and recovery groups. It is the network
element, in this case Open MGW.
Node :
is a term for a single FRU dedicated to specific logical function. Node
typically includes multiple Recovery Units.
Recovery Group (RG) :

is a group of identical recovery units and the redundancy models they
follow. In other words, the recovery group consists of a number of recovery
units controlling similar resources.
Recovery Unit (RU) :

is a collection of SW processes and functions. Recovery Unit is similar to
IPA2800 and DX200 Functional Unit concept but its more independent of
the underlying hardware. Redundancy model of SW processes and
functions must be identical within a RU.
Process:
in the HAS context, the term process means a process started by the HAS
or implementing a HAS service.
9
Example : HAS model in Open MGW

root@CLA-0 [ATCA] > show has bare
[OX] dn
- Print a list of MO names and distinguished names
<mo-type>: - MOType
[X]
cluster - Cluster
[X]
logical - All logical groups
[X]
node - All nodes
[X]
process - All processes
[X]
proxied - All proxied components
[X]
proxy - All proxy processes
[X]
rg
- All RGs
[X]
ru
- All Rus
root@CLA-0 [ATCA] > show has bare cluster

>>Executing a command CLA-0@ATCA [2013-02-04 11:37:06 +0100]
/
10

root@CLA-0 [ATCA] > show has bare node
/CLA-0
/IPNI1P-0
/TCU-0
/CLA-1
/IPNI1P-1
/TCU-1
/IPNI10P-2
/TCU-2
/IPNI10P-3
/TCU-3
/TDMNIP-4
/TCU-4
/TDMNIP-5
/TCU-5
/TDMNIP-6
/TCU-6
/TDMNIP-7
/TCU-7
/TCU-8
/TCU-9
root@CLA-0 [ATCA] >
11

root@CLA-0 [ATCA] > show has bare rg
/MGW_HCLBRG-0
/MGW_SGUNNSFRG-0
/MGW_SAGURG-0
/MGW_IPNIURG-0
/MGW_SISURG-0
/MGW_HCLBRG-1
/MGW_SGUNNSFRG-1
/MGW_SAGURG-1
/MGW_IPNIURG-1
/MGW_SISURG-1
/MGW_DSPMRGTCU1
/MGW_TDMSNIUPRG-2
/MGW_SISURG-2
/MGW_DSPMRGTCU2
/MGW_TDMSNIUPRG-3
/MGW_SISURG-3
/MGW_DSPMRGTCU3
/MGW_DSPMRGTCU4
/MGW_DSPMRGTCU5
/MGW_DSPMRGTCU6
/MGW_DSPMRGTCU7
--More-12

root@CLA-0 [ATCA] > show has bare ru
/CLA-0/MGW_HCLBFU-0
/CLA-0/MGW_SGUNNSFFU-0
/CLA-0/MGW_SGUILSAGFU-0
/CLA-0/MGW_CMFU-0
/CLA-0/MGW_SCLIUFU-0
/CLA-0/MGW_OMUFU-0
/CLA-0/MGW_SISUFU-0
/CLA-0/MGW_HCLBFU-2
/CLA-0/MGW_SGUILSAGFU-2
/CLA-0/MGW_SISUFU-2
/CLA-0/MGW_SISUFU-4
/CLA-0/MGW_SISUFU-6
/CLA-0/FSPM9Server
/CLA-0/FSNodeHAServer
/CLA-0/FSClusterHAServer
/CLA-0/FSBFDServer
/CLA-0/FSDHCPDServer
/CLA-0/FSPM9FuseServer
/CLA-0/FSClusterStateServer
/CLA-0/FSTracingServer
--More
13

root@CLA-0 [ATCA] > show has bare process
/CLA-0/MGW_HCLBFU-0/IL_LastProc12
/CLA-0/MGW_HCLBFU-0/IL_Naseva
/CLA-0/MGW_HCLBFU-0/IL_Mm5prb
/CLA-0/MGW_HCLBFU-0/MGW_htaprb
/CLA-0/MGW_HCLBFU-0/MGW_hcdprb
/CLA-0/MGW_HCLBFU-0/IL_Mfsprb
/CLA-0/MGW_HCLBFU-0/MGW_sdzprb
/CLA-0/MGW_HCLBFU-0/IL_UpgradeMgmtNoWarming
/CLA-0/MGW_HCLBFU-0/IL_Wupman
/CLA-0/MGW_HCLBFU-0/IL_Riesen
/CLA-0/MGW_HCLBFU-0/IL_Thermo
/CLA-0/MGW_HCLBFU-0/IL_Tisero
/CLA-0/MGW_HCLBFU-0/IL_Starter
/CLA-0/MGW_HCLBFU-0/IL_Cpmonitor
/CLA-0/MGW_HCLBFU-0/LinkStateDetectorProcess
/CLA-0/MGW_HCLBFU-0/IL_UnitStateAgent
/CLA-0/MGW_SGUNNSFFU-0/IL_LastProc12
--More-14

root@CLA-0 [ATCA]
> show functional-unit unit-info show-mode simple

UNIT INFORMATION
UNIT_NAME
OMU-0
OMU-1
CM-0
CM-1
SS7UP-0
SS7UP-1
SS7UP-2
SS7UP-3
SISU-0
SISU-1
SISU-2
SISU-3
SISU-4
SISU-5
SISU-6
SISU-7
HCLB-0
HCLB-1
HCLB-2
HCLB-3
IPNIU-0
15
LOG_ADDR
0x4002
0x4002
0x4005
0x4005
0x4AA6
0x4AA6
0x4AA7
0x4AA7
0x4AAE
0x4AAE
0x4AAF
0x4AAF
0x4AB0
0x4AB0
0x4AB1
0x4AB1
0x4ABF
0x4ABF
0x4AC0
0x4AC0
0x4AC9
PHYS_ADDR
0x0200
0x0201
0x0700
0x0701
0x0800
0x0801
0x0900
0x0901
0x0300
0x0301
0x0400
0x0401
0x0500
0x0501
0x0600
0x0601
0x0000
0x0001
0x0100
0x0101
0x0006
STATE
WO-EX
SP-EX
WO-EX
SP-EX
WO-EX
SP-EX
SP-EX
WO-EX
WO-EX
SP-EX
SP-EX
WO-EX
WO-EX
SP-EX
SP-EX
WO-EX
WO-EX
SP-EX
SP-EX
WO-EX
WO-EX
REDUNDANCY
2N
2N
2N
2N
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M

root@CLA-0 [ATCA]
> show functional-unit unit-info show-mode normal

UNIT INFORMATION
UNIT_NAME
OMU-0
OMU-1
CM-0
CM-1
SS7UP-0
SS7UP-1
SS7UP-2
SS7UP-3
SISU-0
SISU-1
SISU-2
SISU-3
SISU-4
SISU-5
SISU-6
SISU-7
HCLB-0
HCLB-1
HCLB-2
HCLB-3
IPNIU-0
16
LOG_ADDR
0x4002
0x4002
0x4005
0x4005
0x4AA6
0x4AA6
0x4AA7
0x4AA7
0x4AAE
0x4AAE
0x4AAF
0x4AAF
0x4AB0
0x4AB0
0x4AB1
0x4AB1
0x4ABF
0x4ABF
0x4AC0
0x4AC0
0x4AC9
PHYS_ADDR
0x0200
0x0201
0x0700
0x0701
0x0800
0x0801
0x0900
0x0901
0x0300
0x0301
0x0400
0x0401
0x0500
0x0501
0x0600
0x0601
0x0000
0x0001
0x0100
0x0101
0x0006
STATE
WO-EX
SP-EX
WO-EX
SP-EX
WO-EX
SP-EX
SP-EX
WO-EX
WO-EX
SP-EX
SP-EX
WO-EX
WO-EX
SP-EX
SP-EX
WO-EX
WO-EX
SP-EX
SP-EX
WO-EX
WO-EX
REDUNDANCY
2N
2N
2N
2N
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
RU_MONAME
/CLA-0/MGW_OMUFU-0
/CLA-1/MGW_OMUFU-1
/CLA-0/MGW_CMFU-0
/CLA-1/MGW_CMFU-1
/CLA-0/MGW_SISUFU-0
/CLA-1/MGW_SISUFU-1
/CLA-0/MGW_SISUFU-2
/CLA-1/MGW_SISUFU-3
/CLA-0/MGW_SISUFU-4
/CLA-1/MGW_SISUFU-5
/CLA-0/MGW_SISUFU-6
/CLA-1/MGW_SISUFU-7
/CLA-0/MGW_HCLBFU-0
/CLA-1/MGW_HCLBFU-1
/CLA-0/MGW_HCLBFU-2
/CLA-1/MGW_HCLBFU-3
/IPNI1P-0/MGW_IPNIUFU-0

root@CLA-0 [ATCA]
> show functional-unit unit-info show-mode verbose

UNIT INFORMATION
UNIT_NAME
OMU-0
OMU-1
CM-0
CM-1
SS7UP-0
SS7UP-1
SS7UP-2
SS7UP-3
SISU-0
SISU-1
SISU-2
SISU-3
SISU-4
SISU-5
SISU-6
SISU-7
HCLB-0
HCLB-1
HCLB-2
HCLB-3
IPNIU-0
17
LOG_ADDR
0x4002
0x4002
0x4005
0x4005
0x4AA6
0x4AA6
0x4AA7
0x4AA7
0x4AAE
0x4AAE
0x4AAF
0x4AAF
0x4AB0
0x4AB0
0x4AB1
0x4AB1
0x4ABF
0x4ABF
0x4AC0
0x4AC0
0x4AC9
PHYS_ADDR
0x0200
0x0201
0x0700
0x0701
0x0800
0x0801
0x0900
0x0901
0x0300
0x0301
0x0400
0x0401
0x0500
0x0501
0x0600
0x0601
0x0000
0x0001
0x0100
0x0101
0x0006
STATE
WO-EX
SP-EX
WO-EX
SP-EX
WO-EX
SP-EX
SP-EX
WO-EX
WO-EX
SP-EX
SP-EX
WO-EX
WO-EX
SP-EX
SP-EX
WO-EX
WO-EX
SP-EX
SP-EX
WO-EX
WO-EX
REDUNDANCY
2N
2N
2N
2N
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
2N*M
RU_MONAME
/CLA-0/MGW_OMUFU-0
/CLA-1/MGW_OMUFU-1
/CLA-0/MGW_CMFU-0
/CLA-1/MGW_CMFU-1
/CLA-0/MGW_SISUFU-0
/CLA-1/MGW_SISUFU-1
/CLA-0/MGW_SISUFU-2
/CLA-1/MGW_SISUFU-3
/CLA-0/MGW_SISUFU-4
/CLA-1/MGW_SISUFU-5
/CLA-0/MGW_SISUFU-6
/CLA-1/MGW_SISUFU-7
/CLA-0/MGW_HCLBFU-0
/CLA-1/MGW_HCLBFU-1
/CLA-0/MGW_HCLBFU-2
/CLA-1/MGW_HCLBFU-3
/IPNI1P-0/MGW_IPNIUFU-0
RG_MONAME
/MGW_OMURG
/MGW_OMURG
/MGW_CMRG
/MGW_CMRG
/MGW_SGUNNSFRG-0
/MGW_SGUNNSFRG-0
/MGW_SGUNNSFRG-1
/MGW_SGUNNSFRG-1
/MGW_SISURG-0
/MGW_SISURG-0
/MGW_SISURG-1
/MGW_SISURG-1
/MGW_SISURG-2
/MGW_SISURG-2
/MGW_SISURG-3
/MGW_SISURG-3
/MGW_HCLBRG-0
/MGW_HCLBRG-0
/MGW_HCLBRG-1
/MGW_HCLBRG-1
/MGW_IPNIURG-0
Functional Units in ATCA MGW

OMU (Operation and Maintenance Unit)
Recovery group: MGW_OMURG
Recovery unit name: MGW_OMUFU
OMU recovery unit implements the operation and maintenance functionality. It has access to permanent
data storage .OMU recovery unit is located in the CLA node.
CM (Central Functions Unit)

Recovery group: MGW_CMRG
Recovery unit name: MGW_CMFU
This recovery unit contains central MGW specific functionalities that have highest real-time dependency.
These functionalities include Signalling gateway centralised functions. CM is located in the CLA node.
HCLB ( H.248 and IWF control and H.248 load balancing)

DRecovery group: MGW_HCLBRG
Recovery unit name: MGW_HCLBFU
HCLB recovery unit implements H.248 link handling, H.248 signaling on Message and TransAction level,
and manages non-call-related H.248 procedures and load balancing among SISUs for call-related H.248
procedures.
One HCLB can contain multiple Virtual Media Gateways (VMGW). HCLB also implements the control
interface towards Circuit Swiched Data server. HCLB recovery units are located in both the ISU and the
CLA nodes.
18

SISU (Slave Interface and Signaling Unit)
Recovery group: MGW_SISURG
Recovery unit name: MGW_SISUFU
SISU recovery unit implements H.248 call-specific procedures and bearer control, and call-related
resource handling. SISU contains an in-memory database for storing H.248 context and termination
relations. SISU recovery units are located in both the ISU and the CLA nodes.
SCLIU (O&M front-end pseudo unit)

Recovery group: MGW_SCLIURG
Recovery unit name: MGW_SCLIUFU
SCLIU recovery unit provides an IPA Light computer address fro SCLI plugin libraries and NE3S extension
libraries to enable DMX messaging. SCLIU recovery unit is located in the CLA node.
SS7SGU (Signaling Gateway Unit)

Recovery group: SS7SGU
Recovery unit name: FSSS7SGUServer
SS7SGU signaling gateway unit manages the Signaling transport between IP-based SIGTRAN and TDMbased SS7 interfaces on M3UA/MTP3 (NIF) layer. SS7SGU recovery units are located in both the ISU and
the CLA nodes.
DSPM (DSP Manager)

Recovery group: MGW_DSPMRG
Recovery unit name: MGW_DSPMFU
DSPM recovery unit contains blade-specific DSP configuration management, bladespecific DSP resource
management and media processing on DSP. DSPM recovery unit is located in the TCU node.
19

DSPOAM (DSP Operation and Announcement Management Unit)
Recovery group: MGW_DSPOAMRG
Recovery unit name: MGW_DSPOAMFU
DSPOAM recovery unit implements the non-call related announcement configuration management and
DSP application configuration file management. DSPOAM recovery unit is located in the TCU node.
SGUNNSF (NAS Node Selection Function Unit)

Recovery group: MGW_SGUNNSFRG
Recovery unit name: MGW_SGUNNSFFU
This signalling gateway unit contains the local SCCP user, i.e. the NAS Node Selection Function and
IPAlight signaling adaptation layer for handling SCCP connection part and handling connection less
message part. SGUNNSF recovery units are located in both the ISU and the CLA nodes.
SGUILSAG (IPAlight SCCP Adaptation Layer Unit)

Recovery group: MGW_SGUILSAGRG
Recovery unit name: MGW_SGUILSAGFU
This signalling gateway unit contains the SCCP layer with Global Title Translation and IPAlight signalling
adaptation and distribution layer between on the one hand the (also distributed) SGUSS7 and the SCCP
user itself, and on the other hand for maintenance handling the SGUSS7 and the centralized SCCP and
SCCP user part. SGUILSAG recovery units are located in both the ISU and the CLA nodes.
DSPTraceProxy (DSP Trace Proxy Unit)

Recovery group: MGW_DSPTraceProxyRG
Recovery unit name: MGW_DSPTraceProxyRU
DSPTraceProxy recovery unit implements the proxying of DSP trace information from DSP devices to the
Nokia Siemens Networks middleware trace framework. DSPTraceProxy recovery unit is
located in the TCU node.
20

IPNIU (IP Network Interface Unit, IP line card)
Recovery group: MGW_IPNIURG
Recovery unit name: MGW_IPNIUFU
IPNIU recovery unit implements IP user plane termination and transferring user plane traffic via Fabric
Interface (FI) to ADSP. IPNIU recovery units are located in the IPNI1P and IPNI10P nodes.
TDMSNIUP (TDM Network Interface Unit)

Recovery group: MGW_TDMSNIUPRG
Recovery unit name: MGW_TDMSNIUPFU
TDMSNIUP recovery unit implements STM-1/OC3 TDM termination and forwards TDM channels over FI
to DSP for further processing. TDMSNIUP is located in the TDMNIP Node.
TDMMGU (TDM Management Unit)

Recovery group: MGW_TDMMGURG
Recovery unit name: MGW_TDMMGUFU
TDMMGU recovery unit implements SDH/SONET management functionality. It provides the services for
TDM circuit configuration, SDH supervision, configuration of the framer, alerting application of important
events that are happening on the line and controlling the overhead functions of the circuits. It provides line
interface protection (MSP1+1) in the TDMNIP node. TDMMGU is located in the TDMNIP node.
21
FU to RG and RU mapping in Open MGW 1/2
22
FU to RG and RU mapping in Open MGW 2/2
23
HAS Supports 3 Redundancy Models

As far as the software is concerned, redundancy for a service is achieved by
deploying standby service instances (recovery units) to the appropriate nodes.
The number of redundant recovery units (RUs) and their deployment methods
depend on the redundancy model :
Hot active/standby redundancy

Cold active/standby redundancy
No redundancy
24
Hot Active Standby Redundancy Model
A hot active/standby pair consists of two RUs offering the same services.
Processes in both the active and standby RUs are running
E.G. in Open MGW SISUs are in hot active/stanby pairs.
During switchover, the roles of the RUs are swapped and the formerly active
process gives the data to the newly active one. This increases the availability of the
services and makes it possible to preserve data during the switchover.
Node-1
Node-2
Recovery Unit
(Active)
Active
Process
Process
Providing
Service
Recovery Unit
(Standby)
Application
itself
synchronizes
state or relies
on DB
Replication
Recovery Group
25
Standby process
Running but NOT
Providing Service
Cold Active Standby Redundancy Model

A cold active/standby pair also consists of two RUs offering the same services.
Processesin the active RU are running and offering service. The redundant
processes in the cold standby RU, however, are not running.
E.G. in Open MGW, DSP manager (DSPM) recovery units are in cold
active/stanby pairs.
During switchover, the roles of the RUs are swapped. The processes running in
the active RU are terminated and the unit becomes the standby unit. The
processes in the former standby RU are started, making it the new active RU.
Node-1
Node-2
Recovery Unit
(Active)
Recovery Unit
(Standby)
Standby
Processes
Active
Process
Process
Providing
Service
Not Even Running
Recovery Group
26
No Redundancy Model
Recovery groups of the no redundancy type provide node-local services for which
active/standby redundancy would make no sense.
In the case of no redundancy, the HAS can attempt to restart either individual
processes or the whole recovery unit.
E.G. in Open MGW, signaling gateway units between IP-based SIGTRAN and
TDM-based SS7 interfaces (SGUSS7) are recovery groups of the no redundancy
type.
Node-1
Recovery Unit
A (Active)
Process
Node-2
Recovery Unit
B (Active)
Process
Recovery Group
27
Node-3
Recovery Unit
C (Active)
Process
Node and Recovery Group Redundancy 1/2

Node
Node
Redundancy
model / FRU State
Recovery
Unit
(RUs)
Recovery
Group
(RG)
Redundancy
model
Description of RG Redundancy
CLA
2N
Active-Active
OMU
and CM
Active-Hot
Standby
Capacity and services are provided by the Active RU.

Active RU can be either side of the FRU pair (Standby RU
another side). Fault in Active RU initiate switchover to
Standby RU (no service impact).
CLA
2N
Active-Active
SCLIU
No Redundancy
Service is provided by both RUs.
CLA,
ISU
2N
Active-Active
HCLB, SISU
and
SGUISDN
Active-Hot
Standby
Capacity and services are provided by the Active RU.

Active RU can be either side of the FRU pair (Standby RU
another side). Fault in Active RU initiate switchover to
Standby RU (no service impact).
CLA,
ISU
2N
Active-Active
SS7SGU
Active-Active
Capacity and services are provided by both Active RUs.

Signaling load must be shared 50/50 between both RUs.
In case of HW/SW fault the capacity of affected RU is lost
until the fault is corrected. Signaling link load and CPU
load will increase in the remaining links and CPU due the
MTP3 signaling traffic re-routing mechanics.
CLA,
ISU
2N
Active-Active
SGUNNSF
Crossed ActiveHot Standby
Capacity and services are provided by two Active RU.

Active RUs locates in different FRUs and their Standby
RU on another side. Fault in Active RU initiate switchover
to Standby RU (no service impact to NNSF function)
28
Node and Recovery Group Redundancy 2/2

Node
TCU in
Ui5.0
Node
Redundancy
model / FRU
State
Recovery
Unit
(RUs)
Recovery
Group
(RG)
Redundancy
model
Description of RG Redundancy
DSPM
No Redundancy
Capacity and services are provided by n number of Active

RUs. If one Active RU fails the capacity is lost until the
fault is corrected
TCU in
Ui5.0 EP
N:1
Active-Hot
Standby
DSPM
Active-Cold
Standby
Capacity and services are provided by n number of Active

RUs. If one Active RU fails the Standby RU becomes an
Active RU having configuration and services of failed RU.
No service impact, but some interference on speech path
during switchover.
IPNI1P
IPNI10P
2N
Active-Hot
Standby
IPNIU
Active-Hot
Standby
Capacity is provided by the Active RU. Fault in Active RU

initiate switchover to Hot Standby RU (no service impact).
RU is common for all GbE interfaces within a RG.
TDMNIP
2N
Active-Hot
Standby
TDMSNIU
Active-Hot
Standby
Capacity is provided by the Active RU. Fault in Active RU

initiate switchover to Hot Standby RU (no service impact).
RU is common for all STM-1/OC3 interfaces within a RG.
AMC
Carrier
2N
Active-Hot
Standby
None
None
Capacity is provided by the Active FRU. Fault in Active

FRU initiate switchover to Hot Standby FRU (no service
impact)
2N
Active-Standby
None
None
Capacity is provided by the Active FRU. Fault in Active

FRU initiate switchover to Hot Standby FRU (no service
impact)
HUB
29
States of managed objects

The HAS framework follows a standard state model for managing resources, in
other words managed objects.
The model described in recommendation X.731 ITU-T is used for this purpose
According to this model, the managed objects have three main state attributes:
Administrative state
Operational state
Usage state
The model also includes a set of status attributes that are called
Procedural
Availability
Unknown
Alarm
As an extension to the standard state model, the platform provides three additional
status attributes:
Role
lock timeout
service level
30
States of managed objects

root@CLA-0 [ATCA] > show has state managed-object /CLA-0/MGW_OMUFU-0
/CLA-0/MGW_OMUFU-0:
administrative(UNLOCKED)
operational(ENABLED)
usage(ACTIVE)
procedural()
availability()
unknown(FALSE)
alarm()
role(ACTIVE)
Dynamic attributes:
RESOURCE_STATE = FUNCTIONAL
RESOURCE_LEVEL = 100
root@CLA-0 [ATCA]
31
>
State attributes (Administrative state)

There are three possible values for the administrative state: UNLOCKED,
LOCKED, and SHUTDOWN.
UNLOCKED state
In the UNLOCKED state, the software or hardware entity represented by the
managed object can perform its normal duties.
LOCKED state
the entity is administratively prohibited from performing its normal duties, until
explicitly unlocked by the operator
SHUTDOWN state
the entity should process whatever ongoing services are running, but must not
take on any new work. After the ongoing service requests are finished, the
administrative state automatically changes to LOCKED.
The SHUTDOWN state is an intermediary state that is used for implementing a
graceful shutdown behavior.
32
State attributes (Operational state)

The value of the operational state attribute is either ENABLED or DISABLED.
Unlike the administrative state, the operational state is controlled by the HAS itself.
ENABLED state
the entity represented by the managed object is functioning properly and can
perform its duties normally
DISABLED state
the entity is not functioning properly and cannot perform its duties. In other words,
it is considered faulty in some way
33
State attributes (Usage state)

There are three possible values for the usage state attribute: IDLE, ACTIVE, and
BUSY.
The usage state attribute is controlled by the HAS for all managed objects except
processes.
IDLE state
the entity is not currently processing any service requests.
ACTIVE state
the entity entity is processing service requests and there is still some spare
capacity for new service requests
BUSY state
the entity has no more spare capacity until some of the active service requests
have terminated or more capacity is added
34
Status attributes (Procedural status)

There are three possible values for the procedural status attribute:
INITIALIZING,NOTINITIALIZED and TERMINATING
INITIALIZING state
If the value of the procedural status attribute is INITIALIZING, the process, node or
RU is currently starting
NOTINITIALIZED state
the process, node or RU is not running.
TERMINATING state
when the process, RU, recovery group (RG) or node (and in a cluster environment
also the whole cluster) is currently terminating
35
Status attributes (Availability status)

There are four possible values for the availability status attribute: POWEROFF,
FAILED, OFFLINE and OFFDUTY.
POWEROFF state
the node is powered off
FAILED state
the process, RU or node is faulty and waiting for a repair. In a cluster environment,
the FAILED value is also shown when the node is not physically present in the
cluster.
OFFLINE state
the node is not operational
OFFDUTY state
the node, process, RU, RG (or cluster in a case of cluster environment) is not
running an active service (this usually means that the managed object is
LOCKED)
36
Status attributes (Unknown status)

The value of the unknown status attribute can be TRUE only for a node that is
LOCKED and not operational (its operational status is DISABLED).
It can also be TRUE for a short period of time, when the system is starting. In
other cases this value is FALSE.
37
Status attributes (Alarm status)

The possible values for the alarm status attribute are OUTSTANDING and
MAJOR.
The OUTSTANDING value is set for a managed object that has an active alarm
The MAJOR value is set for a managed object that has a major active alarm.
38
Role attributes
The role attribute is used for specifying the role of a recovery unit (RU) in an
active/standby pair of a recovery group (RG). There are three possible values for
the role attribute: ACTIVE, COLDSTANDBY, and HOTSTANDBY.
ACTIVE
the managed object is providing normal service.
COLDSTANDBY
the managed object is acting as a backup resource for an active managed object
in a cold active/standby pair and will be promoted to the active role should the
active object fail
HOTSTANDBY
the managed object is acting as a backup resource for an active managed object
in a hot active/standby pair and will be promoted to the active role should the
active object fail
39
Mapping of RU states into IPA2800 FU states
40
* Any value

/CLA-0/MGW_OMUFU-0:
usage(ACTIVE)
procedural()
availability()
unknown(FALSE)
alarm()
role(ACTIVE)
Dynamic attributes:
root@CLA-0 [ATCA]
>
root@CLA-0 [ATCA] > show functional-unit unit-info

UNIT INFORMATION
UNIT_NAME
OMU-0
OMU-1
CM-0
CM-1
* Any value
41
LOG_ADDR
0x4002
0x4002
0x4005
0x4005
PHYS_ADDR
0x0200
0x0201
0x0700
0x0701
STATE
WO-EX
SP-EX
WO-EX
SP-EX
REDUNDANCY
2N
2N
2N
2N
RU_MONAME
/CLA-0/MGW_OMUFU-0
/CLA-1/MGW_OMUFU-1
/CLA-0/MGW_CMFU-0
/CLA-1/MGW_CMFU-1

/CLA-1/MGW_OMUFU-1:
usage(ACTIVE)
procedural()
availability()
unknown(FALSE)
alarm()
role(HOTSTANDBY)
Dynamic attributes:
root@CLA-0 [ATCA]
>
root@CLA-0 [ATCA] > show functional-unit unit-info

UNIT INFORMATION
UNIT_NAME
OMU-0
OMU-1
CM-0
CM-1
* Any value
42
LOG_ADDR
0x4002
0x4002
0x4005
0x4005
PHYS_ADDR
0x0200
0x0201
0x0700
0x0701
STATE
WO-EX
SP-EX
WO-EX
SP-EX
REDUNDANCY
2N
2N
2N
2N
RU_MONAME
/CLA-0/MGW_OMUFU-0
/CLA-1/MGW_OMUFU-1
/CLA-0/MGW_CMFU-0
/CLA-1/MGW_CMFU-1
ADDF
43
ADDF provides E1/T1 implementation in Ui5.0 Open MGW.

ADDF functionality is provided by Krone ADX201.
Rack-mountable unit that can be integrated in an ATCA rack.
Each ADX201 provides 64 E1 2Mb/s interfaces.
ADX201
Each ADX201 hosts 8 interface cards.
Three different interface types are supported:
E1/RJ-45 (new design, with 4x dual PCM)
T1/RJ-45 (new design, with 4x dual PCM)
E1/mini-coaxial
44
ADC-PDU (Power Supply Unit for ADX201)

Power supply for ADX201 devices comes from rack-mountable ADC-PDU device,
by ADC Krone.
Two redundant ADC-PDU units can supply up to 18 ADX201 devices.
Equip power modules first, starting from the bottom of the cabinet.
Equip ADX201 modules, from bottom of the cabinet to upwards. Maximum of 6x
ADX201 modules can be equipped to each shelf (3 on front side, 3 on rear side).
45
Software Architecture Description

Open MGW Platform
46
Functional Software Architecture

Open MGW comprises the following architectural components:
Nokia Siemens Networks ATCA hardware platform
Nokia Siemens Networks middleware platform
Open MGW application software
47
Functional Software Architecture

Open MGW comprises the following architectural components:
Nokia Siemens Networks ATCA hardware platform
Nokia Siemens Networks middleware platform
Open MGW application software
MGW O&M
appl.
Signaling Line card MGW adapted Resource mgmt

Gateway
SW
control appl.
DSP application
MGW common control
appl.
IPA light
IPA light
IPA light incl. TNSDL
Flexi Platform
Linux (WindRiver PNE 2.0)
NSN ATCA HW Platform

- AB platform includes HW & embedded SW
48
DSP platform
OSEck
Ui5.0 MGW SW architecture compared to U5.0
DSP
applicati Other applications
on
DSP
platform
IPA light incl. TNSDL
FlexiPlatform
Linux
NSN ATCA HW Platform
- AB platform includes HW & embedded SW
Ui5.0
49
MGW
Appl
target >70%
Common SW
MGW
Appl
IPA 2800
SW Platform
DMX & Chorus

IPA 2800 HW
Platform
U5.0
DSP
applicati
on
DSP
platform
Appendix
50

First carrier pair in the shelf is equipped to slots 7 and 10

Second carrier pair in the shelf is equipped to slots 11 and 12
51

52

53

create_mgw_2shelf_4xISU
54

02 Open MGW Platform Introduction

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

02 Open MGW Platform Introduction

Uploaded by

Copyright:

Available Formats

Open MGW Introduction Ui5.

Nokia Siemens Networks

Describe the Redundancy Models supported by HAS in the

Nokia Siemens Networks

Nokia Siemens Networks

Open MGW nodes and main interfaces

Nokia Siemens Networks

One Cabinet Configuration

First carrier pair in the shelf is equipped to slots 7 and 10

Nokia Siemens Networks

One Cabinet Configuration

Nokia Siemens Networks

Open MGW Functional Architecture

Nokia Siemens Networks

High Availability Services model in Open MGW

Nokia Siemens Networks

High Availability Services model in Open MGW

Recovery Group (RG) :

Recovery Unit (RU) :

Nokia Siemens Networks

Example : HAS model in Open MGW

root@CLA-0 [ATCA] > show has bare cluster

Nokia Siemens Networks

Example : HAS model in Open MGW

Nokia Siemens Networks

Example : HAS model in Open MGW

Nokia Siemens Networks

Example : HAS model in Open MGW

Nokia Siemens Networks

Example : HAS model in Open MGW

Nokia Siemens Networks

Example : HAS model in Open MGW

> show functional-unit unit-info show-mode simple

>>Executing a command CLA-0@ATCA [2013-02-04 12:10:42 +0100]

Nokia Siemens Networks

Example : HAS model in Open MGW

> show functional-unit unit-info show-mode normal

>>Executing a command CLA-0@ATCA [2013-02-04 12:19:40 +0100]

Nokia Siemens Networks

Example : HAS model in Open MGW

> show functional-unit unit-info show-mode verbose

>>Executing a command CLA-0@ATCA [2013-02-04 12:21:35 +0100]

Nokia Siemens Networks

Functional Units in ATCA MGW

CM (Central Functions Unit)

HCLB ( H.248 and IWF control and H.248 load balancing)

Nokia Siemens Networks

Functional Units in ATCA MGW

SCLIU (O&M front-end pseudo unit)

SS7SGU (Signaling Gateway Unit)

DSPM (DSP Manager)

Nokia Siemens Networks

Functional Units in ATCA MGW

SGUNNSF (NAS Node Selection Function Unit)

SGUILSAG (IPAlight SCCP Adaptation Layer Unit)

DSPTraceProxy (DSP Trace Proxy Unit)

Nokia Siemens Networks

Functional Units in ATCA MGW

TDMSNIUP (TDM Network Interface Unit)

TDMMGU (TDM Management Unit)

Nokia Siemens Networks

FU to RG and RU mapping in Open MGW 1/2

Nokia Siemens Networks

FU to RG and RU mapping in Open MGW 2/2