02 Open MGW Platform Introduction

Open MGW Introduction Ui5.0Open MGW Platform

1 Nokia Siemens Networks

Open MGW Platform

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 DescriptionOpen MGW Platform


Open MGW Platform

Open MGW nodes and main interfaces


One Cabinet Configurationcreate_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


One Cabinet Configuration


Open MGW Functional Architecture

AMC Carrier

ACPI4

BI FI

ISU/ACPI4-ASGU

SISU

HCLB

ADSP1-ATCU/ADSP1-B DSPDSPDSPDSP

LMP DSPM

Interface functions

Switching functions

Control functions

Signal Processing

IPNI1/MPPAM-B

IPNIU

TDM AMCIPNI10/MPPAM-CIPNIU

IP UP 4*Gbps Ethernet

IP UP 1*10Gbps Ethernet

Functional Unit


HUB

Disk

BI FI

AHUB3

SISU IPNIU

Sync. Clock

Ethernet

IP Signaling

ACPI4CLA/ACPI4-A

SGU

SISU

HCLB

OMU

CMRTM

Disk

IP O&M

RTM

TDM AMCTDMSNIU/SCNAM-BTDMSNIUTDMSNIU TDM UP &

SignalingADDF

TDM E1/T1

TDM STM-1/OC3

High Availability Services model in Open MGW


High Availability Services model in Open MGWCluster :

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


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.

Example : HAS model in Open MGWroot@CLA-0 [ATCA] > show has bare

[OX] dn - Print a list of MO names and distinguished names: - 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] 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]/

Example : HAS model in Open MGWroot@CLA-0 [ATCA] > show has bare node>>Executing a command CLA-0@ATCA [2013-02-04 11:37:12 +0100]/CLA-0/IPNI1P-0/TCU-0/CLA-1/IPNI1P-1/TCU-1/IPNI10P-2/TCU-2/IPNI10P-3/TCU-3


/TCU-3/TDMNIP-4/TCU-4/TDMNIP-5/TCU-5/TDMNIP-6/TCU-6/TDMNIP-7/TCU-7/TCU-8/TCU-9root@CLA-0 [ATCA] >

Example : HAS model in Open MGWroot@CLA-0 [ATCA] > show has bare rg>>Executing a command CLA-0@ATCA [2013-02-04 11:41:03 +0100]/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_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--

Example : HAS model in Open MGWroot@CLA-0 [ATCA] > show has bare ru>>Executing a command CLA-0@ATCA [2013-02-04 11:42:49 +0100]/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_SGUNNSFFU-2/CLA-0/MGW_SGUILSAGFU-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

Example : HAS model in Open MGWroot@CLA-0 [ATCA] > show has bare process>>Executing a command CLA-0@ATCA [2013-02-04 11:44:21 +0100]/CLA-0/MGW_HCLBFU-0/IL_LastProc12/CLA-0/MGW_HCLBFU-0/IL_LastProc22/CLA-0/MGW_HCLBFU-0/IL_LastProc32/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_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/CLA-0/MGW_SGUNNSFFU-0/IL_LastProc22/CLA-0/MGW_SGUNNSFFU-0/IL_LastProc32--More--

Example : HAS model in Open MGWroot@CLA-0 [ATCA] > show functional-unit unit-info show-mode simple>>Executing a command CLA-0@ATCA [2013-02-04 12:10:42 +0100]

UNIT INFORMATION

UNIT_NAME LOG_ADDR PHYS_ADDR STATE REDUNDANCYOMU-0 0x4002 0x0200 WO-EX 2NOMU-1 0x4002 0x0201 SP-EX 2NCM-0 0x4005 0x0700 WO-EX 2NCM-1 0x4005 0x0701 SP-EX 2NSS7UP-0 0x4AA6 0x0800 WO-EX 2N*MSS7UP-1 0x4AA6 0x0801 SP-EX 2N*MSS7UP-2 0x4AA7 0x0900 SP-EX 2N*MSS7UP-3 0x4AA7 0x0901 WO-EX 2N*MSISU-0 0x4AAE 0x0300 WO-EX 2N*M


SISU-0 0x4AAE 0x0300 WO-EX 2N*MSISU-1 0x4AAE 0x0301 SP-EX 2N*MSISU-2 0x4AAF 0x0400 SP-EX 2N*MSISU-3 0x4AAF 0x0401 WO-EX 2N*MSISU-4 0x4AB0 0x0500 WO-EX 2N*MSISU-5 0x4AB0 0x0501 SP-EX 2N*MSISU-6 0x4AB1 0x0600 SP-EX 2N*MSISU-7 0x4AB1 0x0601 WO-EX 2N*MHCLB-0 0x4ABF 0x0000 WO-EX 2N*MHCLB-1 0x4ABF 0x0001 SP-EX 2N*MHCLB-2 0x4AC0 0x0100 SP-EX 2N*MHCLB-3 0x4AC0 0x0101 WO-EX 2N*MIPNIU-0 0x4AC9 0x0006 WO-EX 2N*M

Example : HAS model in Open MGWroot@CLA-0 [ATCA] > show functional-unit unit-info show-mode normal>>Executing a command CLA-0@ATCA [2013-02-04 12:19:40 +0100]

UNIT INFORMATION

UNIT_NAME LOG_ADDR PHYS_ADDR STATE REDUNDANCY RU_MONAMEOMU-0 0x4002 0x0200 WO-EX 2N /CLA-0/MGW_OMUFU-0OMU-1 0x4002 0x0201 SP-EX 2N /CLA-1/MGW_OMUFU-1CM-0 0x4005 0x0700 WO-EX 2N /CLA-0/MGW_CMFU-0CM-1 0x4005 0x0701 SP-EX 2N /CLA-1/MGW_CMFU-1SS7UP-0 0x4AA6 0x0800 WO-EX 2N*M /CLA-0/MGW_SGUNNSFFU-0SS7UP-1 0x4AA6 0x0801 SP-EX 2N*M /CLA-1/MGW_SGUNNSFFU-1SS7UP-2 0x4AA7 0x0900 SP-EX 2N*M /CLA-0/MGW_SGUNNSFFU-2SS7UP-3 0x4AA7 0x0901 WO-EX 2N*M /CLA-1/MGW_SGUNNSFFU-3SISU-0 0x4AAE 0x0300 WO-EX 2N*M /CLA-0/MGW_SISUFU-0


SISU-0 0x4AAE 0x0300 WO-EX 2N*M /CLA-0/MGW_SISUFU-0SISU-1 0x4AAE 0x0301 SP-EX 2N*M /CLA-1/MGW_SISUFU-1SISU-2 0x4AAF 0x0400 SP-EX 2N*M /CLA-0/MGW_SISUFU-2SISU-3 0x4AAF 0x0401 WO-EX 2N*M /CLA-1/MGW_SISUFU-3SISU-4 0x4AB0 0x0500 WO-EX 2N*M /CLA-0/MGW_SISUFU-4SISU-5 0x4AB0 0x0501 SP-EX 2N*M /CLA-1/MGW_SISUFU-5SISU-6 0x4AB1 0x0600 SP-EX 2N*M /CLA-0/MGW_SISUFU-6SISU-7 0x4AB1 0x0601 WO-EX 2N*M /CLA-1/MGW_SISUFU-7HCLB-0 0x4ABF 0x0000 WO-EX 2N*M /CLA-0/MGW_HCLBFU-0HCLB-1 0x4ABF 0x0001 SP-EX 2N*M /CLA-1/MGW_HCLBFU-1HCLB-2 0x4AC0 0x0100 SP-EX 2N*M /CLA-0/MGW_HCLBFU-2HCLB-3 0x4AC0 0x0101 WO-EX 2N*M /CLA-1/MGW_HCLBFU-3IPNIU-0 0x4AC9 0x0006 WO-EX 2N*M /IPNI1P-0/MGW_IPNIUFU-0

Example : HAS model in Open MGWroot@CLA-0 [ATCA] > show functional-unit unit-info show-mode verbose>>Executing a command CLA-0@ATCA [2013-02-04 12:21:35 +0100]

UNIT INFORMATION

UNIT_NAME LOG_ADDR PHYS_ADDR STATE REDUNDANCY RU_MONAME RG_MONAMEOMU-0 0x4002 0x0200 WO-EX 2N /CLA-0/MGW_OMUFU-0 /MGW_OMURGOMU-1 0x4002 0x0201 SP-EX 2N /CLA-1/MGW_OMUFU-1 /MGW_OMURGCM-0 0x4005 0x0700 WO-EX 2N /CLA-0/MGW_CMFU-0 /MGW_CMRGCM-1 0x4005 0x0701 SP-EX 2N /CLA-1/MGW_CMFU-1 /MGW_CMRGSS7UP-0 0x4AA6 0x0800 WO-EX 2N*M /CLA-0/MGW_SGUNNSFFU-0 /MGW_SGUNNSFRG-0SS7UP-1 0x4AA6 0x0801 SP-EX 2N*M /CLA-1/MGW_SGUNNSFFU-1 /MGW_SGUNNSFRG-0SS7UP-2 0x4AA7 0x0900 SP-EX 2N*M /CLA-0/MGW_SGUNNSFFU-2 /MGW_SGUNNSFRG-1SS7UP-3 0x4AA7 0x0901 WO-EX 2N*M /CLA-1/MGW_SGUNNSFFU-3 /MGW_SGUNNSFRG-1SISU-0 0x4AAE 0x0300 WO-EX 2N*M /CLA-0/MGW_SISUFU-0 /MGW_SISURG-0SISU-1 0x4AAE 0x0301 SP-EX 2N*M /CLA-1/MGW_SISUFU-1 /MGW_SISURG-0SISU-2 0x4AAF 0x0400 SP-EX 2N*M /CLA-0/MGW_SISUFU-2 /MGW_SISURG-1


SISU-3 0x4AAF 0x0401 WO-EX 2N*M /CLA-1/MGW_SISUFU-3 /MGW_SISURG-1SISU-4 0x4AB0 0x0500 WO-EX 2N*M /CLA-0/MGW_SISUFU-4 /MGW_SISURG-2SISU-5 0x4AB0 0x0501 SP-EX 2N*M /CLA-1/MGW_SISUFU-5 /MGW_SISURG-2SISU-6 0x4AB1 0x0600 SP-EX 2N*M /CLA-0/MGW_SISUFU-6 /MGW_SISURG-3SISU-7 0x4AB1 0x0601 WO-EX 2N*M /CLA-1/MGW_SISUFU-7 /MGW_SISURG-3HCLB-0 0x4ABF 0x0000 WO-EX 2N*M /CLA-0/MGW_HCLBFU-0 /MGW_HCLBRG-0HCLB-1 0x4ABF 0x0001 SP-EX 2N*M /CLA-1/MGW_HCLBFU-1 /MGW_HCLBRG-0HCLB-2 0x4AC0 0x0100 SP-EX 2N*M /CLA-0/MGW_HCLBFU-2 /MGW_HCLBRG-1HCLB-3 0x4AC0 0x0101 WO-EX 2N*M /CLA-1/MGW_HCLBFU-3 /MGW_HCLBRG-1IPNIU-0 0x4AC9 0x0006 WO-EX 2N*M /IPNI1P-0/MGW_IPNIUFU-0 /MGW_IPNIURG-0

Functional Units in ATCA MGW OMU (Operation and Maintenance Unit)

Recovery group: MGW_OMURGRecovery unit name: MGW_OMUFUOMU 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_CMRGRecovery unit name: MGW_CMFUThis 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.


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_HCLBRGRecovery unit name: MGW_HCLBFUHCLB 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.

Functional Units in ATCA MGW SISU (Slave Interface and Signaling Unit)

Recovery group: MGW_SISURGRecovery unit name: MGW_SISUFUSISU 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_SCLIURGRecovery unit name: MGW_SCLIUFUSCLIU 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.


libraries to enable DMX messaging. SCLIU recovery unit is located in the CLA node. SS7SGU (Signaling Gateway Unit)

Recovery group: SS7SGURecovery unit name: FSSS7SGUServerSS7SGU signaling gateway unit manages the Signaling transport between IP-based SIGTRAN and TDM-based 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_DSPMRGRecovery unit name: MGW_DSPMFUDSPM recovery unit contains blade-specific DSP configuration management, bladespecific DSP resourcemanagement and media processing on DSP. DSPM recovery unit is located in the TCU node.

Functional Units in ATCA MGW DSPOAM (DSP Operation and Announcement Management Unit)

Recovery group: MGW_DSPOAMRGRecovery unit name: MGW_DSPOAMFUDSPOAM 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_SGUNNSFRGRecovery unit name: MGW_SGUNNSFFUThis 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_SGUILSAGRGRecovery unit name: MGW_SGUILSAGFUThis signalling gateway unit contains the SCCP layer with Global Title Translation and IPAlight signallingadaptation 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_DSPTraceProxyRGRecovery unit name: MGW_DSPTraceProxyRUDSPTraceProxy recovery unit implements the proxying of DSP trace information from DSP devices to the Nokia Siemens Networks middleware trace framework. DSPTraceProxy recovery unit islocated in the TCU node.

Functional Units in ATCA MGW IPNIU (IP Network Interface Unit, IP line card)

Recovery group: MGW_IPNIURGRecovery unit name: MGW_IPNIUFUIPNIU 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_TDMSNIUPRGRecovery unit name: MGW_TDMSNIUPFUTDMSNIUP 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)


TDMMGU (TDM Management Unit)Recovery group: MGW_TDMMGURGRecovery unit name: MGW_TDMMGUFUTDMMGU 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.

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


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


HAS Supports 3 Redundancy ModelsAs 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


Node-1 Node-2

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.


Application itself

synchronizes state or relies

on DB Replication

ActiveProcessProviding Service

Recovery Unit(Active)

Recovery Group

Recovery Unit(Standby)

ProcessStandby processRunning 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-2Node-1

ActiveProcessProviding Service

Recovery Unit(Active)

Recovery Group

Recovery Unit(Standby)

ProcessStandby ProcessesNot Even Running

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 Node-2

Recovery UnitA (Active)

Recovery UnitB (Active)

Node-3

Recovery UnitC (Active)

Recovery Group

Process ProcessProcess

Node and Recovery Group Redundancy 1/2Node Node

Redundancy model / FRU State

Recovery Unit(RUs)

Recovery Group(RG) Redundancy model

Description of RG Redundancy

CLA 2NActive-Active

OMUand 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 2NActive-Active

SCLIU No Redundancy Service is provided by both RUs.

CLA, 2N HCLB, SISU Active-Hot Capacity and services are provided by the Active RU.


CLA, ISU

2NActive-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

2NActive-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

2NActive-Active

SGUNNSF Crossed Active-Hot 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)

Node and Recovery Group Redundancy 2/2

Node Node Redundancy model / FRU State

Recovery Unit(RUs)

Recovery Group(RG) Redundancy model

Description of RG Redundancy

TCU inUi5.0

N 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:1Active-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


No service impact, but some interference on speech path during switchover.

IPNI1PIPNI10P

2NActive-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 2NActive-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.

AMCCarrier

2NActive-Hot Standby

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

HUB 2NActive-Standby

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

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


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

States of managed objectsroot@CLA-0 [ATCA] > show has state managed-object /CLA-0/MGW_OMUFU-0>>Executing a command CLA-0@ATCA [2013-02-04 18:23:25 +0100]/CLA-0/MGW_OMUFU-0:administrative(UNLOCKED)operational(ENABLED)usage(ACTIVE)procedural()availability()unknown(FALSE)alarm()


role(ACTIVE)Dynamic attributes:RESOURCE_STATE = FUNCTIONALRESOURCE_LEVEL = 100

root@CLA-0 [ATCA] >

State attributes (Administrative state) There are three possible values for the administrative state: UNLOCKED,

LOCKED, and SHUTDOWN.

UNLOCKED stateIn the UNLOCKED state, the software or hardware entity represented by the managed object can perform its normal duties.

LOCKED statethe entity is administratively prohibited from performing its normal duties, until


the entity is administratively prohibited from performing its normal duties, until explicitly unlocked by the operator

SHUTDOWN statethe 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.

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 statethe entity represented by the managed object is functioning properly and can perform its duties normally

DISABLED statethe entity is not functioning properly and cannot perform its duties. In other words,


the entity is not functioning properly and cannot perform its duties. In other words, it is considered faulty in some way

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 statethe entity is not currently processing any service requests.

ACTIVE state


ACTIVE statethe entity entity is processing service requests and there is still some spare capacity for new service requests

BUSY statethe entity has no more spare capacity until some of the active service requests have terminated or more capacity is added

Status attributes (Procedural status) There are three possible values for the procedural status attribute:

INITIALIZING,NOTINITIALIZED and TERMINATING

INITIALIZING stateIf the value of the procedural status attribute is INITIALIZING, the process, node orRU is currently starting

NOTINITIALIZED state


the process, node or RU is not running.

TERMINATING statewhen the process, RU, recovery group (RG) or node (and in a cluster environment also the whole cluster) is currently terminating

Status attributes (Availability status) There are four possible values for the availability status attribute: POWEROFF,

FAILED, OFFLINE and OFFDUTY.

POWEROFF statethe node is powered off

FAILED statethe 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


the FAILED value is also shown when the node is not physically present in the cluster.

OFFLINE statethe node is not operational

OFFDUTY statethe 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)

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.


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.


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.

ACTIVEthe managed object is providing normal service.

COLDSTANDBYthe managed object is acting as a backup resource for an active managed object


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

HOTSTANDBYthe 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

Mapping of RU states into IPA2800 FU states

40 Nokia Siemens Networks * Any value

Mapping of RU states into IPA2800 FU statesroot@CLA-0 [ATCA] > show has state managed-object /CLA-0/MGW_OMUFU-0>>Executing a command CLA-0@ATCA [2013-02-04 18:23:25 +0100]/CLA-0/MGW_OMUFU-0:administrative(UNLOCKED)operational(ENABLED)usage(ACTIVE)procedural()availability()unknown(FALSE)alarm()role(ACTIVE)Dynamic attributes:RESOURCE_STATE = FUNCTIONALRESOURCE_LEVEL = 100

root@CLA-0 [ATCA] >


* Any value

root@CLA-0 [ATCA] > show functional-unit unit-info>>Executing a command CLA-0@ATCA [2013-02-04 18:59:10 +0100]

UNIT INFORMATION

UNIT_NAME LOG_ADDR PHYS_ADDR STATE REDUNDANCY RU_MONAMEOMU-0 0x4002 0x0200 WO-EX 2N /CLA-0/MGW_OMUFU-0OMU-1 0x4002 0x0201 SP-EX 2N /CLA-1/MGW_OMUFU-1CM-0 0x4005 0x0700 WO-EX 2N /CLA-0/MGW_CMFU-0CM-1 0x4005 0x0701 SP-EX 2N /CLA-1/MGW_CMFU-1

Mapping of RU states into IPA2800 FU statesroot@CLA-0 [ATCA] > show has state managed-object /CLA-1/MGW_OMUFU-1>>Executing a command CLA-0@ATCA [2013-02-04 19:01:06 +0100]/CLA-1/MGW_OMUFU-1:administrative(UNLOCKED)operational(ENABLED)usage(ACTIVE)procedural()availability()unknown(FALSE)alarm()role(HOTSTANDBY)Dynamic attributes:RESOURCE_STATE = FUNCTIONALRESOURCE_LEVEL = 100

root@CLA-0 [ATCA] >


* Any value

root@CLA-0 [ATCA] > show functional-unit unit-info>>Executing a command CLA-0@ATCA [2013-02-04 18:59:10 +0100]

UNIT INFORMATION

UNIT_NAME LOG_ADDR PHYS_ADDR STATE REDUNDANCY RU_MONAMEOMU-0 0x4002 0x0200 WO-EX 2N /CLA-0/MGW_OMUFU-0OMU-1 0x4002 0x0201 SP-EX 2N /CLA-1/MGW_OMUFU-1CM-0 0x4005 0x0700 WO-EX 2N /CLA-0/MGW_CMFU-0CM-1 0x4005 0x0701 SP-EX 2N /CLA-1/MGW_CMFU-1

ADDF

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


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).


Software Architecture DescriptionOpen MGW Platform


Open MGW Platform

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


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 common control appl.

MGW O&M appl.

SignalingGateway

DSP applicationLine card SW

Resource mgmtMGW adapted control appl.


NSN ATCA HW Platform- AB platform includes HW & embedded SW

Flexi Platform

appl.

Linux (WindRiver PNE 2.0)

IPA light incl. TNSDL DSP platformIPA light IPA light

OSEck

Ui5.0 MGW SW architecture compared to U5.0

Other applications MGWAppl

target >70% Common SW

MGWAppl

DSP applicati

on

DSP

DSP applicati

on


Ui5.0 U5.0

NSN ATCA HW Platform- AB platform includes HW & embedded SW

FlexiPlatform

IPA 2800 HW Platform

IPA 2800SW PlatformIPA light incl. TNSDL

Linux DMX & Chorus

DSP platformDSP

platform

Appendix



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


One Cabinet Configurationcreate_mgw_2shelf_4xISU


02 Open MGW Platform Introduction

Documents

Transcript of 02 Open MGW Platform Introduction