Atca MGW Workshop

ATCA MGW Workshop, Jodhpur
VF India
By
Rahul Vashisht
Agenda
 Atca Mgw General Overview
 Atca Mgw HW Architecture
 Atca Mgw SW Architecture
 Atca Mgw Commissioning
 Troubleshooting Commissioning and Post Config
 eSW upgrade Procedures in Atca MGW
 IP Integration
 ATCA MGW Integration with MSS
 LK loading
 Announcement Loading
 External Synchronisation and NTP connectivity
 Measurements in Atca MGW
 OSS Integration
 Backup Handling
 CD Upgrade via SCLI
 Webui Functionality
 O&M Maintenance
ATCA MGW Architecture
Introduction of the Mobile MGW Ui5.0
 The Middleware is based on FlexiPlatform (FP5-Lynx) with
integrated IPA Light middleware
 The application software is based on IPA MGW U5.0. In general
feature parity with U5.0 is assumed.
 Main functional characteristics
 Provide feature parity with U5.0 release
 ATM interface not supported
 Same compatibility matrix as in U5.0 release
 MML interface is replaced by Command Line Interface and
WebUI
Benefits of the new product branch
 Wide range in flexibility and scalability (1-100k Erl)

 medium and high end configuration via 16-slot shelf in a
multi-shelf configuration
 small configuration via 2-slot shelf (not realized in Ui5.0)
 Significantly better total cost of ownership
 Planning, installation, configuring, daily operations
 Space, energy consumption
 Very modular architecture, architecture supports easy
introduction of new technologies
 Long-term competitiveness
 Successor for IPA Platform
 NSN long-term platform based on industry standards
 Common development - Co-existence & maintenance of IPA
MGW & ngMGW
MGW Main Functions
 The Multimedia Gateway product can be used for transmitting and converting the user
plane traffic in both bearer independent Circuit-Switched core network (MSC server
environment) and IP based networks (IMS and converged network environments).
 Between different kind of networks the MGW acts as a border element whose main
functions are:
User plane transport;
• Under control of MSC Server (via H.248 protocol), MGW terminates the user plane
from different kind of interfaces, performs conversion between TDM and IP
transmission techologies and connects the user plane between access/core networks.
Media Processing;
 MGW provides needed media processing functions, e.g., Transcoding, Echo
Cancelling, Speech enhancements, Tones and Announcements, as well as
Conference Call functionality.
Signaling Transport;
 MGW adapts the conventional signalling (control plane) between MSC Server and
different network interfaces by changing the signalling transport layer (without
affecting the signalling application layers).
O&M interfaces in MGW
 NE3S interface to NetAct (NSN network management system)

 Element level management
 Web UI over HTTPS
 Structured Command Line Interface (SCLI) over SSH
 Bulk data interface (SFTP)
ATCA MGW HW Architecture
.
Ui5.0 MGW System Architecture in 16-slot shelf
Interface functions AMC carrier

ADSP
ADSP
Switching functions ADSP1-B PACAM
MPPAM IP User
Control functions
plane
Signal Processing
BI FI
RR CLA
ACPI-4 TDM User
Disk TT
Disk TDM AMC
(Control & TDM plane
MM O&M) (SCNAM -B)
linecard
TDM
Signalling
Clock R AHUB3
SFU IP Signalling
T
M
MGW components
 16-slot ATCA shelf with power supplies, shelf manager
 ACPI4 x86 CPU blade

 Intel Nehalem-EP 4-core (8 hardware threads), 2.1 GHz
 Memory up to 24 GB (typical 6GB)
 CPRT4 RTM with disk for permanent storage
 One mid-height AMC slot
 Used for element centralised tasks, media gateway application and signalling
gateway application
 AHUB3 switch blade

 Internal switching for Base Interface (1GE) and Fabric Interface (10GE), all
blades and AMCs have connection to both sides of BI and FI
 Inter-shelf connections
 External connections for signalling over SCTP
 HBRT3 RTM for additional connectivity and clock interface
 ADSP1 DSP blade

 Media processing with TI DSPs, running DSP application and DSP platform SW
 Same DSP devices as in CDSP-DT
 Direct connectivity to FI and BI from DSP devices
 PQ Local management processor
MGW components
 ACAR AMC carrier blade

 4 mid-size AMC slots, PQIII LMP
 Connectivity per AMC slot:
 4 x GE FI connections
 1 x GE BI connections
 Update channel
 SCNAM STM-1 AMC
 TDM linecard AMC with STM-1 interfaces
 MPPAM MIPS packet processing AMC
 Cavium Octeon 56xx series MIPS CPU (12 core, 600MHz) for
packet processing and IP linecard tasks
 Octeon cores running FlexiPlatform with SMP on N cores and
Simple Executive on M cores
 Variants with 4 x GE and 1 x 10GE external interfaces
Cabinet CPU DSP Hub AMC (Advanced Mezzanine Card)
blade blade blade
• AMC carrier
• AMC module AMC
carrier
AMC
interface
module
Shelf
RTM (Rear Transition Module)
Shelf
interconnecting
cables and
transceiver
modules
Hub blade: AHUB3-A
• Hub blade is the main Ethernet switch used for internal traffic between
nodes in the network element, and by employing its Layer 3 capability, it
is also used for routing traffic to/from external networks
• The hub blade provides connections for two types of networks:
• Base interface (BI) switch for the network elements internal traffic (for
communication between computer nodes)
• 14* GbE to interconnect Hub and other HW nodes within the shelf (via
backplane)
• 4* GbE + 1* 10GbE to interconnect shelves (from face plate)
• Fabric interface (FI) switch for communicating with external networks as
well as for the network element’s internal user plane traffic (for example, user
plane traffic transmitted through AMC modules)
• 14* 10GbE to interconnect Hub and other HW nodes within the shelf (via
backplane)
• 4* 10GbE to interconnect shelves (via face plate)
• Hub blade includes a master clock generator (MCG) for distributing a
reference clock signal to other blades and shelves.
• HW redundancy: 2N
• Number of HW nodes (min/max): 1pair / 3pairs
RTM for Hub: HBRT3-A
• The HBRT3-A provides IP signaling uplink and synchronization

connectivity for the hub blades (AHUB3-A). Signaling uplink is provided
by 10GbE/1GbE Ethernet ports, which can be connected to external
networks by using the L3 routing and forwarding capability in the hub.
• Two SSU/BITS ports can be used for connecting the respective hub
blade into a network element timing and synchronization chain.
• HW redundancy: 2N
• Number of HW nodes (min/max): 1pair / 3pairs
Interfaces for external networks:
HW HW HW name Tranceiver Fiber/cable ports

Network Interface Interface type Connector
Node type (FRU) type requirements /FRU
multi mode
IP Ethernet RTM for 10GBase-SR/SW
RTM HBRT3-A SFP+ Duplex LC λ = 850/ nm 1
- ControlPlane Hub 1000BaseLX/SX range = 300m
Min. 1 twisted pair
RTM for 120 ± 15Ω for E1
Telecom sync. RTM HBRT3-A SSU/ BITS - RJ-45 2
Hub and 100 ± 15Ω for
T1
CPU blade: ACPI4-A
 ACPI4-A is a multi-core central processing unit (CPU)
 CPU is in charge of all the processing needed for the call management, signaling
and operation and maintenance tasks
 HW redundancy: 2N
 Number of HW nodes (min/max): 1 pair / 4 pairs
HW Unit HW Logical functions:

ISU node SGU
name nodes CLA node SGU
OM
(FRU): where U SISU SISU
CM
ACPI4-A used: HCLB HCLB
CLA and
ISU

O&M interface
electrical
(electrical) CLA/
CPU ACPI4-A 1000Base-T - RJ-45 S-FTP 2
- Local/remote O&M ISU
CAT 5e
- NetAct
RTM for CPU: CPRT4-A
 The CPRT4-A is a single-width rear transition module which can be equipped

into any RTM slot where the CPU blade is located
 The CPRT4-A provides storage and additional connectivity for the ACPI4-A
CPU blade.
 HW redundancy: 2N disk

O&M interface
multi mode
(optical) RTM for
RTM CPRT4-A 1000Base-LX/SX SFP Duplex LC λ = 850/ nm 2
- Local/remote O&M CPU
range = 300m
- NetAct
DSP blade: ADSP1-A
 DSP blade provides DSP HW for media processing

 TCU node implements DSP configuration management, DSP resource
management and media processing
 HW redundancy: N+1 (within shelf)

 Number of HW nodes (min/max): 2 / 34
HW Unit HW Logical functions:

name nodes TCU node
(FRU): where DSPM
ADSP1-A used:
TCU

- none
AMC Carrier: ACAR1-B
 ACAR1-B is a carrier blade (bay) for AMC modules

 Single ACAR1-B blade can house up to four AMC modules.
 An integrated Ethernet switch on ACAR1-B provides Base and Fabric
Interface connectivity from the AMC modules to the blade backplane.
IP GbE AMC module: MPPAM-C
 MPPAM-C provides four GbE interfaces for IP userplane

 Up to two MPPAM-C modules can be equipped on a single ACAR1-B
carrier blade

multi mode
IP Ethernet
IPNI1 AMC MPPAM-C 1000BASE-LX/SX SFP Duplex LC λ = 850/ nm 4
- UserPlane range = 300m
TDM STM-1/OC3 AMC module: SCNAM-B
 SCNAM-B provides four STM-1/OC3 interfaces for TDM userplane

 Up to four SCNAM-B modules can be equipped on a single ACAR1-B
carrier blade

TDM STM-1/OC3 single mode

- TDM userplane TDMNI AMC SCNAM-B ITU-T G.957 S-1.1 SFP Duplex LC λ = 1310/ nm 4
- TDM signaling range = 15km
MGW shelf layout – mandatory HW units
AMC Carrier - bay for AMC

interface modules
• Mandatory in 1. shelf
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Hub
CLA node (1.st shelf) TCU node
Packet switching and
Signaling, Control and O&M Media processing
routing
• Mandatory in 1. shelf • 2 - 12 / shelf • One pair / shelf
• Mandatory 2 / shelf
ISU node (2. & 3. shelf) • Number of nodes depend on traffic
Signaling volumes, traffic profile and voice
• Mandatory one pair / 2.&3 shelf enhancement features
MGW shelf layout – full configuration (example)
AMC Modules:
4x TDM STM-1 /SFP
4x GbE /SFP
1x 10GbE /SFP+
AMC Carrier
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
AMC bay for AMC
interface modules
CPU Blade TCU Hub AMC Modules

Signaling, Control and Media processing Packet switching for external interfaces
O&M and routing
Atca Mgw Software architecture
Ui5.0 MGW SW architecture compared to U5.0
DSP DSP
applicati Other applications applicati
on MGW target >70% MGW on
Appl Common SW Appl
DSP
IPA 2800 platform
DSP IPA light incl. TNSDL
SW Platform
platform FlexiPlatform
Linux DMX & Chorus
NSN ATCA HW Platform IPA 2800 HW

- AB platform includes HW & embedded SW
Platform
Ui5.0 U5.0
Ui5.0 MGW software architecture deployment
ADSP
ADSP
TCU(ADSP)
DSP
DSP
LMP
DSPM
IP User
AMC carrier plane
CLA
ISU(ACPI4) PACAM
IPNI(MPP
IP O&M SISU AM)
HCLB
BI FI
SGU IPNIU
CLA
CLA/ACPI4
Disk RR SISU TDM User
Disk SCNAM
TDM plane
TT
HCLB
SGU
M linecard
TDMNIU
M OMU CM
TDM
signalling
R AHUB3
Clock SFU IP Signalling
T
M
MGW specific recovery units in 16-slot configuration
CLA-0 CLA-1 TCU-0 TCU-1 TCU-2 ISU-0 ISU-1 IPN-0 IPN-1

OMU OMU DSPM DSPM HCLB HCLB IPNIU IPNIU
CM CM DSPM DSPM SISU SISU
HCLB HCLB SGU/ SGU/

SCCP/ SCCP/
ILSAC/ ILSAC/
NNSF NNSF
SISU SISU
NNSF & SCCP
SGU/
SCCP/
SGU/
SCCP/
TDMSN-2 TDMSN-3
SGU SGU ILSAC/ ILSAC/
NNSF NNSF
TDMSNIU TDMSNIU
SCLI SCLI
SGU SS7 & SGU
SS7 SIGTRAN SS7
SGU SGU
IUA/ISDN
ISDN ISND
RU Active, no
RU active RU Hot Standby RG FP Node
redundancy
REDUNDANCY MODEL
Node Recovery
redunda Group (RG)
ncy Recovery redundancy
Node model Units (RUs) model Description of RG redundancy
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
OMU and Active –Hot initiate switchover to Standby RU (no service
CLA 2N CM Standby impact).
No
CLA 2N SCLIU redundancy Service is provided by both RUs.
Capacity and services are provided by the Active

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

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 due
CLA ISU 2N SS7SGU Active-Active the MTP3 signaling traffic re-routing mechanics.
Capacity and services are provided by two Active

RU. Active RUs locates in different FRUs and their
AHUB CONFIGURATION
BASE configuration(BI):-
This base interface is used for internal messaging/communication and
management traffic.
Ports 3/5 and 3/6 are the external BI Ports connecting Base Traffic from Shelf-
to-shelf.
FABRIC configuration(FI):-
This fabric interface is used for user payload (signaling data)/control plane
traffic.
Ports 3/1 to 3/4 are the external FI ports used for shelf-to-shelf and peer
Network connectivity.
Interconnection cables between shelves (Hub+RTM)
NOTE! Picture presents Front Rear
cabling for Active- side Shelf 1 IP Ethernet – Layer 2/3
only. Cabling for 1/1 3/1
(i.e H.248, M3UA, etc..)
Redundant Hub+RTM is 1/2
FI FI 3/2
identical with Active. 1/3
3/3
Hub 0
& 3/4
1/5 RTM
Hub 1
Optional cable set 3 1/6
1/7
3/5
BI BI  Ext. Sync
(link aggregation) 1/8
1/9
3/6
Shelf 2
cable set 1
Legend
10GbE / XFPMM-A, P02035 / LC 1/1 3/1
1/2
10GbE/ SFPPMM, P02045 / LC 1/3
FI FI 3/2
3/3
GbE / SFPF2L, P02028 / LC Hub 2
& 3/4
RTM
SSU / BITS / RJ-45/ 1/5 Hub 3
3/5
1/6
1/7
1/8
BI BI 3/6 cable set 2
fiber multimode FI
1/9
fiber multimode BI
fiber multimode FI / Aggregation
Shelf 3
Internal cable: copper cable
1/1 3/1
1/2
External cable: fiber multimode FI FI 3/2
1/3
3/3
External cable: copper cable Hub 4
3/4
& RTM
Port is not used by Ui5.0 SW Hub 5
1/5
3/5
1/6
Port is disabled by HW 1/7 BI BI 3/6
1/8
1/9
Diagnosis HW,SW and System Internal Connectivity
Diagnosing in Open Mgw is quite less painful and just a pre-installed script
needs to be executed in CLA,which gives a detailed report of Diagnosis.
# fstestcli--- This provides the status of Blades physically present in the

Cluster and the Status of Services which all are there in the Cluster..
Cluster status check:

*********************
/ Cluster OK
*********************
Node status check:
******************
/CLA-0 Node OK
/IPNI1P-0 Node OK
/TCU-0 Node OK
/CLA-1 Node NOK **!!!**
/IPNI1P-1 Node NOK **!!!**
/IPNI10P-2 Node OK
/IPNI10P-3 Node OK
/TDMNIP-4 Node OK
/TDMNIP-5 Node OK
******************
If any Service is Found NOK in fstestcli it is mandatory that all the related child
Units are Up and Running.
show has children managed-object /XXX" to check the children services CLI
command 'hwcli -q -e "^[^d]"' to list all installed HW nodes.
# hw_diagnostic --- If we get node status as OK in fstestcli we can go further for
Internal Health Check of the System by the Pre-installed hw_diagnostic
script.We can take Basic data or Full data Collection as per the need by
selecting below Options:-
[root@CLA-0(ATMGW01) /opt/nokiasiemens/SS_MGWSSD/bin]
# ./mgwssd.py
--------------------------------------------------------------------------------
Welcome to MGWSSD
(c) NSN 2011 $Revision: 190 $
Select action:
( ) 1. Basic Data Collection.
( ) 2. Full Data Collection.
( ) 3. Message Monitoring and logs (Includes Basic Data Collection).
( ) 4. Take a 'snapshot' of MGW's status.
( ) 5. Show userplane context-topology for max. 10 contexts.
( ) 6. IP Connectivity Check.
e. Execute.
t. TransferFiles. (Data NOT Collected)
h. Help.
q. Quit.
Result diagnosis files can be taken from /var/log/mgwssd directory

# sanity_test
Network Element : OMGW-Anna

Time label : 2012-04-29 17:55:51.909271
Log file : /var/log/comm_log/commissioning.log
Selected commissioning items:

- HW Interrogation
- Monitoring System Start-up
- SW Interrogation
- IO System Interrogation
- Reachability Interrogation
- Shelf Manager Interrogation
- Embedded Software Interrogation
- Unit Diagnostic
- Synchronization Interrogation
- Alarm Interrogation
*****************************************************************
Synchronization Interrogation done (00:00:01)
Alarm Interrogation done (00:00:01)
HW Interrogation done (00:00:02)
IO System Interrogation done (00:00:02)
SW Interrogation done (00:00:03)
Total time (hour:min:sec): 00:00:05
IP Integration and Auditing
IP Integration
 BI in AHUB is used for Internal Message Communication

 FI in AHUB is used for Control Plane Connectivity
 In the Current Network Topology O&M has L2 Straight Connectivity with Site
Routers and is Done via RTM’s of CLA
 Control Plane has L3 Connectivity To Site Routers and both AHUB from
BackPlane carries L3 Primary and Secondary CP traffic
 Userplane Connectivity is a port-to-port L3 Connectivity with Site Routers and
Is done between Routers and IPNI1P AMC from Front Plane
L2 O&M Site Connectivity
O&M Plane: in MGW
 2 Straight Lan cables from CLA-0 rtm_sfp1 and rtm_sfp2 to Router-1
and 2 straight Lan Cables from CLA-1 rtm_sfp1 and rtm_sfp2 to Router -2
bond10
type : dedicated
address : 10.84.122.20/29
owner : /SSH
user : /HTTPDPlat
Static route: default Next hop type: normal Rank: 60

Gateway: 10.84.122.17 Preference: not defined
BFD monitoring: disabled BFD tx interval: 1000 BFD rx
interval: 1000 BFD detect multiplier: 4
Sample Command:
add networking bond /CLA-0 algorithm xor-mac iface bond10 slave rtm_sfp1 slave rtm_sfp2
add networking bond /CLA-0 algorithm xor-mac iface bond10 slave rtm_sfp1 slave rtm_sfp2
set routing node CLA-0 static-route default nexthop gateway address 10.150.50.1 on
O&M Plane in Routers
Port Configuration
7609-0#configure terminal
7609-0(config)#interface GigabitEthernet3/10
7609-0(config-if)#description amgwm071_cla0_rtm_sfp1
7609-0(config-if)#switchport
7609-0(config-if)#switchport access vlan 212
7609-0(config-if)#switchport mode access
7609-0(config-if)#no shutdown
7609-0(config-if)#end
7609-0(config)#interface GigabitEthernet3/11
7609-0(config-if)#description amgwm071_cla0_rtm_sfp2
7609-0(config-if)#switchport
7609-0(config-if)#switchport access vlan 212
7609-0(config-if)#switchport mode access
O&M Plane in Routers
Vlan Configuration
7609-0(config)#interface vlan 212
7609-0(config-if)#description amgwm071_oam
7609-0(config-if)#ip address 10.84.122.18 255.255.255.248
7609-0(config-if)#standby 50 preempt
7609-0(config-if)#standby 50 ip 10.84.122.17
7609-0(config-if)#standby 50 priority 110
7609-0(config-if)#standby 50 timers msec 300 msec 1000
L3 Control Plane Site Connectivity
Control Plane: in MGW
fsipaddress dedicated add 10.84.119.42/27 iface fi0 owner /MGW_HCLBRG-0 user
/MGW_HCLBRG-0 user /CLA-1/MGW_HCLBFU-1
/MGW_HCLBRG-2 user /ISU-1/MGW_HCLBFU-5
Sample command:
add networking address dedicated /MGW_HCLBRG-1 iface fi0 ip-address 10.150.51.2/27
Control Plane: in MGW
fsipaddress dedicated add 10.84.119.40/27 iface fi0 owner /CLA-0 user /SS7SGU
fsipaddress dedicated add 10.84.119.34/27 iface fi0 owner /ISU-0 user /SS7SGU
Static route: 10.84.112.128/25 Next hop type: normal Rank: 60

BFD monitoring: disabled BFD tx interval: 1000 BFD rx interval: 1000
BFD detect multiplier: 4
Static route: 10.84.114.128/25 Next hop type: normal Rank: 60

BFD monitoring: disabled BFD tx interval: 1000 BFD rx interval: 1000
BFD detect multiplier: 4
 10.84.112.128 and 10.84.114.128 are the MSS Primary and secondary CP network
IP and 10.84.119.33 and 10.84.120.33 is the Gateway IP.
Control plane in AHUB
Vlan Configuration
vlan database
vlan 100
vlan name 100 "mgw-sctp-prm"
vlan routing 100 3
vlan association subnet 10.68.162.48 255.255.255.240 100
Enable routing and the created VLAN with the ID index 3
Port Configuration
interface 5/3
no shutdown
mtu 9212
routing
ip address 10.68.162.49 255.255.255.240
router rip
router ospf
Assign IP to Virtual Port 5/3 Created

Control plane in AHUB
Add SCTP VLAN to AHUB's port connecting to /MGW_HCLBRG on CLA-0 and CLA-1
AHUB0--Fabric(Config)# interface 0/1

AHUB0--Fabric(Interface 0/1)# vlan participation include 100
AHUB0--Fabric(Interface 0/1)# vlan participation exclude 1
AHUB0--Fabric(Config)# interface 0/2

AHUB0--Fabric(Interface 0/2)# vlan participation include 100
AHUB0--Fabric(Interface 0/2)# vlan participation exclude 1
Give AHUB's uplink connecting to site Routers
AHUB0-Fabric# configure interface 3/1

AHUB0-Fabric(Interface 3/1)# ip address 10.69.45.2 255.255.255.252
AHUB0-Fabric(Interface 3/1)#routing
Add IP route for the SCTP traffic toward MSS
AHUB0-Fabric(Config)# ip route 10.56.201.64 255.255.255.192 10.69.45.1

AHUB0-Fabric(Config)# ip routing
Control Plane in Routers
Port Configuration
interface GigabitEthernet 3/12

description amgwm021-cp-primary
ip address 10.84.121.10 255.255.255.252
no shutdown
Static Routes
ip route 10.84.119.16 255.255.255.240 10.84.121.9 name amgwm021-cp-primary

ip route 10.84.120.16 255.255.255.240 10.84.121.13 name amgwm021-cp-secondary
L3 User Plane in MGW
L3 User Plane in MGW
Assign IP address to all Interfaces of all IPNI1P’s
add networking address dedicated /IPNI1P-0/MGW_IPNIUFU-0 iface eth_sfp1 ipaddress 10.33.112.222/30
Assign Loopback IP to only WO IPNI1P for all Interfaces

add networking address dedicated /MGW_IPNIURG-0 iface lo ip-address 10.33.97.36/29
Assign Static Routes to transport Network’s Gateway configured at Site Router

set routing node IPNI1P-0 static-route default nexthop gateway address 10.33.112.221 bfd-monitoring enabled
bfd-rx-interval 50 bfd-tx-interval 50 bfd-detect-mult 3 on
L3 User Plane in Routers
Create BFD sessions for physical interfaces
7609-0#(config)#interface GigabitEthernet1/16
7609-0#(config-if)#description up-ipn0-eth_sfp1
7609-0#(config-if)#bfd interval 50 min_rx 50 multiplier 3
7609-0#(config-if)#ip address 10.33.112.221 255.255.255.252
L3 User Plane in Routers
ip route static bfd GigabitEthernet1/16 10.33.112.222

Create IP routes for BFD sessions
ip route 10.33.97.32 255.255.255.224 GigabitEthernet1/16 10.33.112.222 name

mgw-ipn0-sfp1
ip route 10.33.97.40 255.255.255.224 GigabitEthernet 1/1710.33.112.226 name
mgw-ipn0-sfp2
mgw-ipn0-sfp3
mgw-ipn0-sfp4
LSD(Link State Detector) Functionality in Open Mgw
 LSD functionality is used in Open Mgw to ensure that proper Switchover of RU and RG happens
in case of an Interface failure or a Hardware Breakdown.
 To enable LSD for O&M N/W:

Attach /SSH RG to Bond10 Created between both CLA nodes:-
fsclish -c "add networking link-state-detector /SSH iface bond10"
 To enable LSD for CP N/W:

Add all HCLBRG RG’s to both fi0 anf fi1 Interfaces
fsclish -c "add networking link-state-detector /MGW_HCLBRG-0 iface fi0 iface fi1“
 To enable LSD for UP:

Attach all /MGW_IPNIURG to all interfaces of IPNI1P
fsclish -c "add networking link-state-detector /MGW_IPNIURG-0 iface eth_sfp1 iface eth_sfp2 iface
eth_sfp3 iface eth_sfp4"
Troubleshooting Steps
 When Doing O&M connectivity from RTM of CLA ,BIOS setting need to be
changed as below after which CLA needs to be JOJI.After that status of
RTM’s can be checked via linux cmd:
#ethtool rtm_sfp1 | grep Link
Under OEM E-keying Configuration
Management LAN Setting [RTM]

Management LAN State [RTM]
 Sometimes SSH IP is unreachable even after RTM is detected OK..Give

a restart to /SSH RG that time.
hascli –r –F /SSH
 During CP connectivity make Sure IP route is added in the AHUB with

Network IP as default or MSS CP IP is defined. Also Static Routes
needs to be defined in Respective CLA /ISU nodes also to reach peer
end Entity.
 During UP connectivity bfd should be enabled with same Parameters

on Both Router and Mgw end for Proper functioning of User Plane.
Loopback IP’s should be Pingable from Peer end
IP Auditing
 IP Audit Checklist
 Attached Checklist can be referred in case of troubleshooting for

CP,O&M,UP connectivity in Open Mgw.
 It has Router Configuration Logs, AHUB logs, IP Configuration in Mgw
and Post Checks after Implementing the Configuration
Resiliency Checks
 For Testing O&M resiliency:
a) Plug out Both cables from CLA which has active SSH RG one by one. The
SSH login should remain entact in such a case.
 For Testing CP resiliency:

a) Plug out the cable from RTM of Primary AHUB,In that case all M3UA
associations and VMGW’s should be available via Secondary Path.
b) Also same case can be Implemented in mid of a TDM or IP call.The call
should not get Drop in such a case,
c) AHUB HW resiliency can be checked by making AHUB Manually Inactive by
Pulling Hot Swap Button.
 For Testing User plane Resiliency

a) During a Active IP call the Interface from Active IPNI1P card on which call is
made can be made down by pulling out the LAN cable. IP Call should not
get drop.
b) In Mid Of an active call the WO IPNI1P AMC can be made Inactive which will
initiate a SWO to SP AMC without the call being terminated.
Resiliency Checks for various RG and RU in Open Mgw
 Attcahed Excel can be referred to in case Resiliency checks for various RG

an RU needs to performed..
 All the Resiliency cases should be tested During Active Calls by Proper
Removal of HW during HW resiliency testing
Open MGW Integration
IP Implementation
 IP’s can be assigned to Various RG by SCLI commands.
Attached is the Text file for reference
Sigtran Creation with MSS
Following Sequence of Commands to be followed for creating a

Sigtran with MSS/GCS.
 add signaling service-access-point id 1 name test network-appearance 12

network-indicator NA1 network-type itu
 add signaling ss7 local-as id 1 name AMGW routing-context 1 routing-key-dpc
10612 service-access-point-name test traffic-mode loadshare
 add signaling ss7 remote-as id 1 name AMSS pending-timer 3 service-access-
point-name test routing-context 2 routing-key-dpc 11431 traffic-mode loadshare
communication-type sgasp
 add signaling ss7 association id 1 local-ip-addr 10.84.119.42 local-ip-addr
10.84.120.42 local-server-port 2905 role server node /CLA-0 remote-as-name
AMSS remote-ip-addr 10.84.112.33 remote-ip-addr 10.84.114.33 remote-port
1025 exchange-mode single sctp-profile SS7 communication-type sgasp local-
as-name AMGW
 set signaling ss7 association id 1 admin-state enabled“
Sigtran Creation with MSS
To Define MSS SPC as Own Point Code

add signaling ss7 own-point-code name mss service-access-point-name sgwas
Point-code 11431 type primary
Hint: Give a restart to /SS7SGU RG if state of association state remains

connection_down even after enabling.
H.248 Between MGW and MSS
>set mgw common service-endpoint-address e164 911234567891

>add vmgw mgw vmn AMGW rg 1 opip 10.84.119.43 osip 10.84.120.43 opn 8009
>add vmgw controller vmn AMGW hea 3000 hve 2 pip 10.84.112.33 sip 10.84.114.33
>set vmgw registration rega 1 vid 0
Hint: Give a restart to concerned RG if VMGW is not Registered..

hascli –rn /MGW_HCLBRG-1
show vmgw mgw vid 0

>>Executing a command CLA-0@AMGWM071 [2012-01-02 02:00:00 +0530]
VIRTUAL MGW DATA:
virtual media gateway identifier : 0

virtual media gateway name : AMGW
HCLB rg :1
SISU rg(s) : 0, 1, 2, 3, 4, 5, 6, 7, 12, 13, 14, 15
REGISTRATION:
state : registered, normal functionality
registration allowed : registration allowed
COMMAND EXECUTED
BSC Connectivity
 Attached doc can be refferred while Doing BSC connecvtivity
Note: Doc is prepared when SPMC is used in the Network.
Same way ISUP connectivity can also be done just by changing

destination point code as Point Code of TDM MSC.
LSL and HSL Creation
 Below SCLI can be used for LSL Creation
add signaling ss7 link id 1 destination-point-code-name tbsc own-point-code-name MSS07
slc 1 bandwidth narrowband chassis-id 1 link-rate 64 mtp2-link-profile ITU_T mtp2-timer-
profile ITU_T node-name /CLA-0 number-of-time-slots 1 pcm-id 1 spmc-link yes time-slot
16
Hint :
 Make sure if pcm used lies in the chassis which is being used for Link creation
 Spmc-link is set to yes if SPMC functionality is being used
 Correct Link and Timer Profiles are to be Used depending on type of Link to be
created.
 Below SCLI can be used for HSL Creation

add signaling ss7 link id 2 destination-point-code-name STP own-point-code-name MSS07
slc 0 bandwidth HSL chassis-id 2 link-rate 1984 mtp2-link-profile ITU_2_M mtp2-timer-
profile ITU_2_M node-name /ISU-0 number-of-time-slots 31 pcm-id 1346 spmc-link yes
time-slot 1
 Hint: Make Sure bandwidth type is HSL and Link-rate is 1984 Kb/s
 Link and Timer Profile is ITU_2_M as it supports HSL extended frame numbering
 Number of time slots are 31 to utilise all Links for successful 1984 Kb/s Link
Creation
NE ID (Internal and Confidential) and LK Installation
 Below Linux can be used to configure C Number in Mgw

# ilsystemid.sh –w <C Number>
 Below Linux can be used to Interrogate C number in Mgw

# ilsystemid.sh -r
 Change Network Element name

# set config attribute fsClusterId=ClusterRoot attribute-list fsLogicalNetworkElemId
AMGWG041
 C number can also be checked with SCLI:

Show licence target-id
For Installing Licences in Open Mgw Copy all the XML files under path /root using
WinScp. Thereafter execute below SCLI cmds to Activate the Licences and
features.
# cd /root
# add licence file /root/HXXXXXX.xml
# show licence all
# set licence feature-mgmt id 0000000799 feature admin-state on
# show licence feature-mgmt all
Hint: Check C number in XML files and system date and time before installing LK’s
.
Announcement Loading
 To add silence vad files:
# add announcement-and-tone announcement fnbr 01001 ftyp vad

 To Load and add vat files:
# load announcement-and-tone announcement fdir

/var/opt/nokiasiemens/annfile/ORIGINAL fnbr 691-702 ftyp vat
# add announcement-and-tone announcement fnbr 691-702 ftyp vat
To Load and add vad files:
# load announcement-and-tone announcement fdir

/var/opt/nokiasiemens/annfile/ORIGINAL fnbr 6 ftyp vad
 Loading IN Speech Announcements
IN announcement needs to be Constructed with Varpgen Tool which
generates a language file in .L format.Below SCLI cmds are for loading .L
file and other variable Announcements.
load announcement-and-tone announcement ftyp val fnbr 0 fdir

/var/opt/nokiasiemens/annfile/ORIGINAL/
add announcement-and-tone language-tag langid 0 lang EN
add announcement-and-tone announcement varp 0 lang 0
load announcement-and-tone announcement ftyp vad fnbr 6 fdir
/var/opt/nokiasiemens/annfile/ORIGINAL
add announcement-and-tone announcement ftyp vad fnbr 6
 Other easiest way of Announcement loading is to copy Ann. files in.IMG file format
from any U5 IPA Mgw
Just remove the .IMG extension from all those Announcement Files and copy them to
/var/opt/nokiasiemens/annfile/DESTINATION directory in Atca Mgw.
After that just add the Announcement files:

add announcement-and-tone announcement fnbr 691-702 ftyp vat
IN announcement can also be copied in same way from U5 Mgw (vat and vad
files). For Language files:
1.Use VARPGEN tool to generate 0.L from your IPA(U5) file VAXL00GX.IMG
2.Upload(SFTP) this files to /var/opt/nokiasiemens/annfile/ORIGINAL/ Atca Mgw.
3.Use SCLI :
> load announcement-and-tone announcement ftyp val fnbr 0
then VAXL00NG will be generated/refreshed under
/var/opt/nokiasiemens/SS_ILOMU/SS_ILMFS/_active.
Tones and DTMF in Open Mgw
 Tones can be set according to Network Requirement and can be referred
from any Live Mgw.
 To Interrogate national Tones ,SCLI used is:
# show announcement-and-tone tone paratype 0
For Adding National Tones:

# add announcement-and-tone tone toneid 66 int 0 dur 500 fre 480-22,620-22 pau 500
For Deleting National Tone:

# delete announcement-and-tone tone toneid 66 ord 1
For Modifying national Tones:

# set announcement-and-tone tone toneid 250 ord 1-3 int 0 dur 400 fre 500-32,300-32 pau
1000
After changing any parameter in Tones it has to be distributed to all TCU’s in Mgw with
SCLI
# load announcement-and-tone tone-and-dtmf
For More Troubleshooting refer Attached doc.

Synchronisation and Timing
 The timing source for Open MGW can comes from, for example,
PSTN network via AMC module STM-1 or comes from, for example,
GPS/BITS via AHUB3-A RTM external port.
 The input clock reference of Open MGW has following two types
and the maximum number of input clock reference is 6.
1) External timing(via the redundant external synchronization input)

The external timing reference signal can be selected from two possible
inputs:
E1(2.048 MHz) and T1(1.544 MHz).
2) Line timing(via the redundant PDH or SDH/SONET core network
interfaces)
The system clock can be selected from three possible inputs: STM-
1(155.52 MHz),
E1(2.048 Mbps ), and T1(1.544 Mbps ).
Synchronisation and Timing
 For Configuring Input Clock Reference

# add mgw synchronization inputreference port set-0 forceql 2 priority 12
 For Deleting Input Clock Reference

# delete mgw synchronization inputreference port set-0
 For Modifying Input Reference Parameters
# set mgw synchronization inputreference port set-0 forceql 2 priority 12

# show mgw synchronization input-reference
reference mode locked pri force ql line ql ssm ver wtr phy port mcg clk mcg clk
status
--------- ----- ------ --- -------- ------- ------- --- -------- -------- --------------
set-0 stm-1 yes 12 2 9 gen2 5 ok clk3a ok
Priority value is from 0-15 with ascending order.
 For Interrogating General synchronisation Parameters

# show mgw synchronization general
CDS connectivity
 Check the IP addresses configured for the MGW_HCLBRG_x recovery groups.
# fsipaddress get
 Check the SCTP parameter values of an SCTP parameter set named SS7 is same as in
CDS
# show signaling sctp-profile name SS7
 Assign HCLBRG-x own IP to IWF entry. Select the IWF priority list with HCLBrecovery
group index 0 as a cyclic Hunt Method.
# add mgw iwf unit-data rg 0 opip 10.84.119.43 hunt 1
 Add a new IWF/cds priority entry

# add mgw iwf entry rg 0 prio 1 pip 10.84.84.4 pport 8014 sip 10.84.86.4 sport 8014 sctp-set-name
SS7 nename AMGW
 Register the IWF/cds priority entries

# set mgw iwf connection rg 0 prio 1 conn 3
# set mgw iwf connection rg 0 prio 1 conn 0
 Interrogate the IWF priority lists

# show mgw iwf control-data rg 0
CDS connectivity
 Create a special circuit group
# add tdm circuitgroup ncgr IWF1 cgr 2 spe vmgw
 Set the interface type to other

# set tdm circuitgroup cgr 2 inter other
 Add TDM circuits to the CGR

# add tdm crct ncgr IWF1 crct-pcm 2 crct-tsl 1-31
 Unlock the Circuits

# set tdm crct-state admin-state unlocked crct-pcm 2 crct-tsl 1-31
Hint:
 Check proper Reachablility of CDS by Pinging GSW IP from MGW.
 Make Sure at CDS IWF mode is set as ‘SCTP’ and not ‘TCP’
 ‘Nename’ in MGW should be same as the IWF entry name in CDS in ZJGI MML.
 SCTP parameters are same in both CDS amd MGW for the parameter set that is
used.
NTP Server Connectivity
 Check for NTP server IP address and Configure the same IN OMGW. The Server IP
should Ping OK from CLA nodes.
# ping 10.84.108.27
# add networking-service ntp forwarder 10.84.108.27
 Assign an IP from O&M Pool to /ClusterNTP RG

# add networking address dedicated /ClusterNTP iface bond10 ip-address 10.84.122.21/29
 Set system date and time to some other using below cmd and check the date again
after sometime ,NTP should reset the correct Timestamp
# date -s “2 OCT 2009 13:00:00"
# date
Hint: Check state of /ClusterNTP RG and restart if needed.

# hascli –s /ClusterNTP
# hascli –rn /ClusterNTP
User Management
 To create a new User ID and assign necessary access permissions to it.
# add user-management group test

# add user-management group-to-permission gid test permid fsclishAllowAll
# add user-management user dailyuser primary-group test
# set user-management passwd set-user-passwd user dailyuser
For Various different permissions please refer attached excel:

Backup Handling in Open Mgw
 There can be Full Backup and Partial Backup. Partial Backup can be Default or
Selective
 Check for enough space in HDD

# df -h
# free
 FULL BACKUP
>start backup full
>commit backup
 DEFAULT PARTIAL BACKUP

>start backup partial
>commit backup
 SELECTIVE PARTIAL BACKUP

>start backup selective
>add backup delivery current
>commit backup
Check the backup in

# cd /mnt/backup
Backup Handling in Open Mgw
 There can be following further options for selective backup

>add backup state <options>
>add backup filesystem <options>
>add backup plugin <options>
>add backup database <options>
>add backup config <options>
>add backup delivery <options>
Refer attached ppt. for Detailed Backup and Restore Process

USB Mounting
 USB should be Mounted properly for Viewing the contents and should be
Unmount for Safe removal. It should be inserted only when it is required.
# dmesg /df -->>with this command you can see device name granted for USB
memory. For example sdb1.
# mkdir /media/usb ->>Make directory for mounting
# chmod 777 /media/usb ->>Give proper user rights for new directory
# mount /dev/sdb1 /media/usb ->>mount device sdb1 to folder /mnt/usb
# cd /media/usb/ ->>check that mounting was successful
# ls –l ->> check contents of USB
#umount /dev/sdb1 -->>safely remove the USB from CLA node
CD Upgrade via SCLI
ISO upgrade in Mgw is done via FEWS comissioning described earlier and via SCLI
command instructed below:
 Copy ISO image to target Blade HDD (CLA)

# scp R_UI50_3.9.2.1.iso /mnt/backup
 Backup current image

>save snapshot startup config-name XXXX
>start backup full
>commit backup
 Install new R_UI50_3.9.2.1 by SW install SCLI command

>set sw-manage install delivery /mnt/backup/R_UI50_3.9.2.1.iso
 Check installed SW delivery list and activate the SW delivery needed

>show sw-manage list
>set sw-manage activate delivery-label R_UI50_3.9.2.1.WR.64.20110704T143058 all
mode restart
After restart check the installed delivery in all nodes is correct

>show sw-manage current all
Refer attached doc

Webui in Open Mgw
Like SCLI Open MGW also has a Web User Interface for Configuration handling
and Management.
 A super user account is needed to create user accounts for
WebUI. Permission “fsumManageAll” is needed for the super user.
Login as a root user and Use below commands to create a super user:
>add user-management group dailysuper-group

>add user-management user dailysuper1 primary-group dailysuper-group
>add user-management group-to-permission gid dailysuper-group permid fsumManageAll
>set user-management passwd set-user-passwd user dailysuper1
Give Password for Username dailysuper1
fsWebUIAllowAll -> for login WebUI

fsNetworkingManage -> for configuration management
FSHASMANAGE -> for HAS related web page
Webui in Open Mgw
 Add an IP address for the Web UI on the CLA unit.
>add networking address dedicated /SSH user/HTTPDPlat user /Ne3sAgent iface
bond-10 ip-address 10.84.122.20/29
Use same IP for both /SSH ,/HTTPDPlat and /Ne3SAgent RG
 Add a user that can access and use the Web UI with needed permissions after Login as
super user:
>add user-management group dailywebui-group

>add user-management user dailyweb1 primary-group dailywebui-group
>set user-management passwd set-user-passwd user dailyweb1
>add user-management group-to-permission gid dailywebui-group permid fsWebUIAllowAll
>add user-management group-to-permission gid dailywebui-group permid fsNetworkingManage
> add user-management group-to-permission gid dailywebui-group permid FSHASMANAGE
Open Mozilla or Internet Explorer to login using below address

https://10.84.122.20/WebFwCore/web/pages/main.jsp
Inspecting and Upgrading the eSW version of Blades
eSW upgrade of all blades need to be performed if applicable

after loading a new ISO in to the Open Mgw.
You can check the eSW version present in the Node

by executing below SCLI cmd:
show sw-manage embedded-sw version fru-location /chassis-1/slot-1
eSW name installed baseline upgrade/downgrade

version version
IPMC 5.52-058-066 5.52-058-066 not needed
BIOS 3.30 3.30 not needed
FPGA 4.01 4.01 not needed
FRUdata 01-08 01-08 not needed

For Upgrading different blade below SCLI commands can be used
set sw-manage embedded-sw upgrade fru-location /chassis-1/slot-1 all
set sw-manage embedded-sw upgrade fru-location /chassis-1/slot-1/RTM-1 all
set sw-manage embedded-sw upgrade fru-location /chassis-1/shelf-manager-slot-1 all

set sw-manage embedded-sw upgrade fru-location /chassis-1/slot-7/AMC-1 all
Sometimes if SCLI upgrade fails, Manual Upgrade can be done for cards
Below is the procedure for Manual upgrade of cards. And python script for
upgrading SCNAM directly from X-19 to X-30 SW
Troubleshooting SCNAM manual Upgrade
 Attached are few Troubleshooting steps during Manual

Upgrade of SCNAM card.
Measurement Handling
 Performance management (PM) gives the information that can be used to optimize
the utilization of the network element (NE)
Create a measurement job

add stats m-job name CPUReport omes 2002 granularity 3600
Start the Measurement job

set stats m-job id 2002 enabled
Verifying Measurement job

show stats m-job id 4
Create an object list

add stats obj-list name CPUList omes 2002 object FPNODE-CLA-0/FPCPU-CPU0
Verify Existence of Object List

show stats obj-list id 0
 Delete an Object List
# delete stats obj-list id 0
 Delete a Measurement job

# delete stats m-job id 4
 To view the results of the storage usage measurements

# show stats data current omes-id 2002 FPNODE-CLA-0/FPCPU-0
OVERALL_CPU_USG(local_m2002c0001) : 2.70694
CPU_CUM_ELAPSED_TIME(local_m2002c0002) : 2549
MIN_CPU_USAGE(m2002c0003) : 1
MAX_CPU_USAGE(m2002c0004) : 100
AVG_CPU_USAGE(m2002c0005) : 3
CPU_CUM_IDLE_TIME(local_m2002c0006) : 2480
The list of the collected result files in the NE can be found by using
# show stats data reports id 1
 Sometimes current reports cannot be seen and can be made refresh by:
# refresh stats data current omes-id 2002 all-objects
 Measurement .XML files can be Fetched by WinSCP from below Directory:

/var/opt/nokiasiemens/SS_PM9/storage/results
 Measurement .XML files can be read in SCLI prompt by:

# zcat xxxxxx.XML
 XML files can be Uncompressed by:

# gzip –d xxxxxx.XML
OSS integration
NetAct provides Fault Management (FM), Configuration Management (CM) and
Performance Management (PM) for OMGW
 Provide OMGW SSH IP,C Number and Network Element name to OSS team for
Mgw definition in OSS.
 Ensure that the network element is running the correct software version
# show config filter (fsLogicalNetworkElemId=*) fsClusterId=ClusterRoot
>>Executing a command CLA-0@Kosmo [2012-02-09 13:33:31 +0200]
dn: fsClusterId=ClusterRoot
objectClass: FSCluster
objectClass: extensibleObject
fsClusterId: ClusterRoot
fsLayer: FlexiPlatformBase FlexiPlatformFull
IPALightMiddlewareMGW MediaGateway
fsLogicalNetworkElemType: OMGW
fsMOID: 1
fsLogicalNetworkElemId: Naakka
fsStaticDataDelivery: R_UI50_3.9.3.3.WR.64.20120126T120552fsLast
OSS integration
 Assign SSH ip to Ne3SAgent RG and add static routes to both CLA to through the
connectivity with OSS
# add networking address dedicated /SSH ip-address 10.84.122.20/29 iface bond10 user
/Ne3SAgent
# set routing node CLA-0 static-route 10.104.208.0/27 nexthop gateway address
10.84.122.17 on
# set routing node CLA-1 static-route 10.104.208.0/27 nexthop gateway address
10.84.122.17 on
 Check if any firewall is running on Router and Do a ping to OSS IP to check the
connectivity between OMGW and OSS.Give a restart to Ne3SAgent RG in case it is
not pinging.
# hascli –rn /Ne3SAgent
 To create NUPADM user in OMGW
# add user-management group sclimgr
# add user-management group-to-permission gid sclimgr permid fsclishAllowAll
# add user-management user NUPADM primary-group sclimgr
# set user-management passwd set-user-passwd user NUPADM
OSS integration
Enter password, set the NUPAMD’s password. It is must be the same as the
NUPADM’s password in NetAct.
Add OSS IP as DNS in OMGW

# add networking-service dns forwarder 10.104.208.27
Hint:
 Check OSS IP is reachable. Check MTU size if MPLS BB is there in the Network
 Check Ne3SAgent is up and Running in Mgw.
 At OSS end check Ne3SAgent should be successfully Registered in directory,
# /var/opt/nokia/oss/local/common/log/NE3S-Registration
Status: Successful Registration
 Check Measurements and Alarms are coming in OMGW.
 OSS should be able to do SSH Login in OMGW and Alarms and Measurements
should be visible in OSS
ATCA MGW Commissioning
Presentation / Author / Date

Commissioning Overview
What is Commissioning?
Commissioning is:
 Preparing a certain (eg. create_mgw_3shelf.sh) deployment and SW for installation
 Commissioning is divided into 4 parts
 setting up a commissioning session
 preparation of hard drives (disks)
 transferring the SW and according data to the target (Using FEWS)
 enabling all (or parts) of the components (Post Config) and Synchronise data
between CLA-0 and CLA-1 HDD’s.
Please Follow attached Commissioning Checklist with All Learnings so far and
Attached Commissioning Manual for Detailed reference During Commissioing
Connecting FEWS to ATCA
Connect from FEWS PC ethernet cable to AHUB3-A(left AHUB and port SFP 1/6)
Serial connection at least to Shelf manager and CLA-0 is needed. You can use
also windows laptop to get needed serial connections to CLA and Shelf Manager.
Delivery patch to R_UI50*.iso
 After R_UI50*.iso is copied to FEWS you need to decompressed

R_Ui50*.iso file to img-files:
# export PATH=$PATH:/opt/nokiasiemens/SS_FEWS/bin/
#fsetupcli –-delivery –-patch R_UI50_*.iso

For example:
1. #fsetupcli –-delivery –-patch /root/R_UI50_3.9.3.2.iso
 After delivery patch is done, you can find *.img files from:
#/opt/nokiasiemens/fews/R_Ui50*-directory
Create commissioning session, fsetup*.conf-file in FEWS
The FSetup configuration file is a user-definable commissioning
configuration file. Below is example which can be used. You need to
modify Cluster ID , Time Zone and Delivery Name.
#DELIVERY="R_UI50_3.9.3.2.WR.64.20101027T145713" # commissioning
COMM_DELIVERY_ROOT="/opt/nokiasiemens/fews/deliveries" # commissioning
COMM_SESSION_ROOT="/opt/nokiasiemens/fews/sessions" # commissioning
HW_PLATFORM="ATCA" # system
CLUSTERID="Lion" # system is name of the your ATCA Node
TIMEZONE="Europe/Helsinki" # commissioning
FSVER="FP5LYNX" # system
COMM_IFACE="eth1" # commissioning
This is interface in FEWS where AHUB is connected
#COMM_IPMGMT_EXTERNAL_IP_SCRIPT="/atkis/fews/ipscript_buster.sh" #
commissioning
#COMM_IPMGMT_FI_SUBNET="169.254.128.0/17"
CPU_TYPE="x86_64" # system
#DEPLOYMENT="create_mgw_1shelf_tdm.sh" # commissioning
#COMM_NETWORK="192.168.40.1/24" # commissioning
COMM_NETWORK="192.168.0.1/24" # commissioning
COMM_FEWSIP="192.168.0.199/24" # commissioning
COMM_NODE="CLA" # commissioning
#COMM_IPMGMT_INTERNAL_IFACE=eth0
#COMM_IPMGMT_FI_IFACE=eth2
COMM_KERNEL_VARIANT="wr"
#PASSWORD_root='root'
#PASSWORD__nokfsoperator='root'
#PASSWORD__nokfssysemoperatorfallback='root'
Create commissioning session
FEWS: Commissioinig session creation:
#fsetupcli –-session –-create <session name> fsetup*.conf

For example:
2. #fsetupcli –-session –-create amgw /tmp/fsetup.conf
Choose deployment(create_mgw_1shelf.sh), SW delivery and define

passwords.
 FEWS: After session is created you need to start it:

#fsetupcli –-session –-start <session name>
For example:
3. #fsetupcli –-session –-start amgw
 Session needs to be Reset Sometimes when Commissioning Fails

4. # fsetupcli –-session –-reset amgw
Commissioning
In CLA-1:
Clear the Master Boot Record (MBR) before commissioning in CLA-1 if there is a old SWdd
if=/dev/zero of=/dev/sda count=1 bs=512
#dd if=/dev/zero of=/dev/sda count=1 bs=512
Connect fews to hub (SFP 1/6 interface in ahub3)
In Shelfmanager:Deactivate all plugged boards except CLA-0, AHUB and Shelf Manager. Use
shelf manager(root/shmm4nsn):
5.#clia deactivate board < slot number >
For example:
#clia deactivate board 2 CLA-1
#clia deactivate board 3 DSP-0
#clia deactivate board 4 DSP-1
#clia deactivate board 7 MPPAM-C/SCNAM-B
#clia deactivate board 10 MPPAM-C/SCNAM-B
Commissioning
Shelf manager:Restart CLA-0:
#clia boardreset 1
Boot order in CLA sholud be such that PXE-boot is first and after that Hard drive(SCSI). You
should have serial connection to CLA-0 that you can see that CLA start to boot from
PXE(FEWS). You should press enter beginning that PXE-boot continues.
If boot order is not correct one then during CLA-0 boot press F12 to get boot setup to change
boot priority.
boot: "manual" for manual installation (default) Press enter here
After commissioning is finished you can see commissionig finished OK text on CLA-0. Stop
session in FEWS:
#=============================================#
 # COMMISSIONING: FINISHED OK (0)
 # START DATE: 2010-07-16-181021
 # END DATE: 2010-07-16-183005
 # ELAPSED TIME: 00:09:44
#=============================================#

#fsetupcli --session --stop session_name
For example
#fsetupcli --session --stop amgw
Commissioning
Connect Shelfmanager or serial console in CLA-0 and Restart CLA-0.
For example in shelf manager or in CLA-0 press 0(reboot node):

#clia restart board 1
After CLA-0 is up then activate the all boards except CLA-1 in shelf manager
#clia activate board < slot number >
For example:
#clia activate board 3 DSP-0
#clia activate board 4 DSP-1
#clia activate board 15 MPPAM-C/SCNAM-B
Commissioning
CLA-0: When all blades are up(use fstestcli command to check node status. When nodes are
NOK state, you can proceed then Start post Config right away after cla-1(activate from shelf
manager) start to get up.Also all TCU’s should have red LED on all DSP before p c can start.
In shelf manager:

clia activate board 2 CLA-1 (Wait few seconds…)
In CLA-0:
#fsetupcli post configure

If you have problems, check postconfig failure cases.
Hint: After Commissioning is Over check hwcli whether nodes are

availabe or not. If nodes are not coming available, Power-off-on the
Cluster and again check hwcli. Nodes should be available.Continue
with postconfig thereafter.
Commissioning
 After postconfiguration is finished you can define SSH access
#INFO "postConfig finished successfully"
 Give permission to access ssh with vi-tool in CLA-0. You need to do that
also in
CLA-1 when redundancy is supported
#vi /etc/ssh/sshd_external_config
Change permit_root_login no to yes

Enter insert mode, use i
Exit and save, use esc then wq!
Restart ssh process

#hascli -rn –F /SSH
Troubleshoot: PostConfiguration is failing or CLA Keeps
Restarted
Check Shelf manager have correct IP address in use. Compare in active
shelf manager side that ifconfig is matching IP addresses defined in CLA:
/etc/hosts. If there is address micmatch then check shelf manager eSW and
configuration. If eSW is correct and configuration is OK then restart shelf
or do clia dhcp restart to update IP address from CLA.
# grep SM /etc/hosts
169.254.1.42 SM-1-1.internalnet.localdomain SM-1-1
169.254.1.43 SM-1.internalnet.localdomain SM-1
169.254.1.44 SM-1-2.internalnet.localdomain SM-1-2
[root@CLA-0(Lion) /var/crash]
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:18:49:00:9A:AA
 inet addr:169.254.1.42 Bcast:169.254.127.255 Mask:255.255.128.0
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
 RX packets:10340679 errors:0 dropped:0 overruns:0 frame:0
 TX packets:9140835 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:1000
 RX bytes:803679296 (766.4 MiB) TX bytes:752688308 (717.8 MiB)
 Interrupt:27
eth0:0 Link encap:Ethernet HWaddr 00:18:49:00:9A:AA
 inet addr:169.254.1.43 Bcast:169.254.127.255 Mask:255.255.128.0
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
 Interrupt:27
Troubleshoot: PC Fails because of wrong boot order in CLA-1
Command 'fsconfigure --noask --initialize' failed
# fsetupcli post configure
INFO Checking if this is a single-node host
INFO Detected multi-node host
INFO "Starting postConfig"
INFO PostConfig is not just unlocking MOs
INFO Following cluster manager nodes found:
INFO CLA-0 CLA-1
INFO More than one cluster manager node found
INFO Enabled PXE boot for cluster manager nodes
INFO Checking if CLA-1 node is ready for initialization
INFO CLA-1 node is not yet ready for initialization
INFO CLA-1 node is ready for initialization
INFO Checking if CLA-1 node is up
INFO CLA-1 node is up
INFO Initializing cluster manager node ...
ERROR Command 'fsconfigure --noask --initialize' failed
ERROR
ERROR Check file /tmp/cla-init.log for more details
ERROR 'Failed to initialize disks for CM nodes'
ERROR "postConfig failed”
Check that boot order in CLA-1 is correct:

1st Boot [PXE:IBA GE Slot 0200 v1338]
2nd Boot [SCSI:#0600 ID05 LUN0 FUJITSU MBD]
Troubleshoot :CLA nodes are not found and hwcli-command
doesn’t list any available node
# fsetupcli post configure
INFO Checking if this is a single-node host
INFO Detected multi-node host
INFO "Starting postConfig"
INFO PostConfig is not just unlocking MOs
INFO Following cluster manager nodes found:
INFO
ERROR Unable to list any cluster manager nodes
ERROR "postConfig failed"
[root@CLA-0(Fami) /root]
Check hwcli if all nodes are available or not
Restart flxiuser username in shelf. Before that Take out the Spare Shelf Manager and after that
restart the username and check hwcli.
#clia user passwd 3 flexiu7er
 Power-off and Power-on whole Cluster if required.Nodes should be available in hwcli after that
Troubleshoot :PostConfiguration is failing or CLA is restarted
every now and then
Check that flexiuser user is in shelf manager:

#clia user
If user doesn’t exist then create it:
#clia user add 3 flexiuser 0x60 4 flexiu7er
If user exist then restart it:
#clia user passwd 3 flexiu7er
Does shelf manager has correct shelf address in use:
The ATCA shelf address must be set as follows:
clia shelfaddress "0000FFFFFF01FFFF00.."
and in multi-shelf configuration accordingly for other shelves:
Shelf 2: "0000FFFFFF02FFFF00.."
Shelf 3: "0000FFFFFF03FFFF00.."
Failure case: PostConfiguration is failing, CMF should be
enabled
When the CMF is disabled in CLA-0 when CLA-1 still deactivated state
then CMF should be activated:
#fscmfcli –s /CLA-0 Check the status.
#fscmfcli –f -e /CLA-0 If deactivated then activate CMF
After CLA-0 is serving state CLA-1 can be activated and postConfiguration

can be run:
#fscmfcli --status /CLA-0
CLA-0: CMF-SERVING priority: 5
Bios Settings-ACPI4-A
These Bios Settings in ACPI4-A differs from what are set during FEWS
Comissioning,and are to be reset once FEWS comissioning is over or
SW-upgrade is done on any ACPI4-A blade.
Same Settings can be done for ISU nodes as well except Boot Device
priority which is supposed to be Only ‘PXE Boot’ Always.
QA Log Procedure
 QAL can be collected with the help of mgwssd script located in
# cd /opt/nokiasiemens/SS_MGWSSD/bin
# ./mgwssd.py
Just execute ./mgwssd.py and therefter u can choose from various options
Welcome to MGWSSD
(c) NSN 2011 $Revision: 190 $
Select action:
() 1. Basic Data Collection.

() 2. Full Data Collection.
() 3. Message Monitoring and logs (Includes Basic Data Collection).
() 4. Take a 'snapshot' of MGW's status.
() 5. Show userplane context-topology for max. 10 contexts.
() 6. IP Connectivity Check.
e. Execute.
t. TransferFiles. (Data NOT Collected)
h. Help.
q. Quit.
Output file can be obtained from /var/log/mgwssd

Maintenance of Open Mgw
 Maintenance tasks includes general principles of use as well as daily, weekly
and monthly activities for maintaining the system health.
 Attached Excel can be Maintained in order to Maintain the Atca Mgw on

Daily/Weekly/Monthly basis.
Open Mgw Expansion
 While Doing the Commissioning we create the full deployment of 3-shelf so

that in Future if any expansion is to be done we need not Create the
Deployment again as it will require full Commissioning via FEWS Pc which is
not advisable in a Live Environment.
 We can do Card Expansion without any need to Create the need HW as it will
be already Created in the System.
Attached Doc can be referred for Detailed step by step Procedures to be followed
for Expanding Units in a Live system

Atca MGW Workshop

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Atca MGW Workshop

Încărcat de

Drepturi de autor:

Formate disponibile

ATCA MGW Workshop, Jodhpur

 Wide range in flexibility and scalability (1-100k Erl)

 NE3S interface to NetAct (NSN network management system)

Interface functions AMC carrier

 16-slot ATCA shelf with power supplies, shelf manager

 ACPI4 x86 CPU blade

 AHUB3 switch blade

 ADSP1 DSP blade

 ACAR AMC carrier blade

• The HBRT3-A provides IP signaling uplink and synchronization

Interfaces for external networks:

HW HW HW name Tranceiver Fiber/cable ports

HW Unit HW Logical functions:

HW HW HW name Tranceiver Fiber/cable ports

 The CPRT4-A is a single-width rear transition module which can be equipped

Interfaces for external networks:

 DSP blade provides DSP HW for media processing

 HW redundancy: N+1 (within shelf)

HW Unit HW Logical functions:

(FRU): where DSPM

Interfaces for external networks:

 ACAR1-B is a carrier blade (bay) for AMC modules

 MPPAM-C provides four GbE interfaces for IP userplane

Interfaces for external networks:

 SCNAM-B provides four STM-1/OC3 interfaces for TDM userplane

Interfaces for external networks:

HW HW HW name Tranceiver Fiber/cable ports

TDM STM-1/OC3 single mode

AMC Carrier - bay for AMC

4x TDM STM-1 /SFP

CPU Blade TCU Hub AMC Modules

Linux DMX & Chorus

NSN ATCA HW Platform IPA 2800 HW

CLA-0 CLA-1 TCU-0 TCU-1 TCU-2 ISU-0 ISU-1 IPN-0 IPN-1

CM CM DSPM DSPM SISU SISU

HCLB HCLB SGU/ SGU/

Capacity and services are provided by the Active

Capacity and services are provided by both Active

Capacity and services are provided by two Active

# fstestcli--- This provides the status of Blades physically present in the

Cluster status check:

Result diagnosis files can be taken from /var/log/mgwssd directory

Network Element : OMGW-Anna

Selected commissioning items:

 BI in AHUB is used for Internal Message Communication

Static route: default Next hop type: normal Rank: 60

Static route: 10.84.112.128/25 Next hop type: normal Rank: 60

Static route: 10.84.114.128/25 Next hop type: normal Rank: 60

Enable routing and the created VLAN with the ID index 3

Assign IP to Virtual Port 5/3 Created

AHUB0--Fabric(Config)# interface 0/1

AHUB0--Fabric(Config)# interface 0/2

Give AHUB's uplink connecting to site Routers

AHUB0-Fabric# configure interface 3/1

Add IP route for the SCTP traffic toward MSS

AHUB0-Fabric(Config)# ip route 10.56.201.64 255.255.255.192 10.69.45.1

interface GigabitEthernet 3/12

ip route 10.84.119.16 255.255.255.240 10.84.121.9 name amgwm021-cp-primary

Assign Loopback IP to only WO IPNI1P for all Interfaces

Assign Static Routes to transport Network’s Gateway configured at Site Router

ip route static bfd GigabitEthernet1/16 10.33.112.222

Create IP routes for BFD sessions

ip route 10.33.97.32 255.255.255.224 GigabitEthernet1/16 10.33.112.222 name