M-MGW Overview Presentation for CNCS5.

0
NIV at GSDC Australia

[Link]

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 1 (65) EPA/SR/G/C/2 Peter Wu

Contents

1. Definition of a Media Gateway

2. Positioning the M-MGw in the Network
3. M-MGw Interfaces
4. Product Packages
5. Licensing
6. Features
7. Hardware Structure
8. System Architecture
9. Operation & Maintenance

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 2 (65) EPA/SR/G/C/2 Peter Wu

1. Definition of a Media Gateway

A node that works as a facilitating adapter for the user plane

between different networks, in a layered network architecture

• Connects the Mobile Core Network with other networks,

e.g. Radio Access (WCDMA, GSM), PSTN
• Bridges different transmission technologies
• Manipulates the connectivity layer, adding services to end-
user connections

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 3 (65) EPA/SR/G/C/2 Peter Wu

2. Positioning the M-MGw in the Network

• Layered Network Architecture

• M-MGw Interfaces
• Example: UMTS Call to PSTN
• Example: Local Switching

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 4 (65) EPA/SR/G/C/2 Peter Wu

 Positioning the M-MGw in the
Network

Layered Network Architecture

Control Layer

HLR
Signaling
Payload MSC
TSC
Server
Server GMSC
Server

WCDMA MGw/
MGw/ WCDMA
WCDMA MGw/
MGw/ MGw/
MGw/ WCDMA
SGw
SGw
SGw
SGw SGw
SGw

GSM Backbone network GSM

GSM MGw/
MGw/ TDM, ATM, IP MGw/
MGw/ GSM
SGw
SGw SGw
SGw
MGw/
MGw/ MGw/
MGw/
ISDN/PSTN
PSTN ISDN/PSTN
PSTN
ISDN/PSTN SGw
SGw MGw/
MGw/ SGw
SGw ISDN/PSTN
SGw
SGw

Connectivity Layer

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 5 (65) EPA/SR/G/C/2 Peter Wu

 Positioning the M-MGw in the
Network

M-MGw Interfaces
RANAP, 3GPP 24.008 BICC

BSSAP MSC/TSC ISUP

Server

(GPS)
O&M Synch
GCP (Mc)
HTTP, FTP, ATM, IP
S-FTP,
- IIOP
IP

MGW IP (NbUP, RTP)

ATM (IuUP, AAL2) M-MGw

RNC ATM (NbUP, [Link], AAL2)

Q.AAL2 M-MGw Q.AAL2

TDM (A) TDM PSTN
BSC
other networks

Note: Other interfaces like Iur, IuPS, Gn, Mur and Mub can be connected
via the M-MGw using permanent or AAL2 switched connections

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 6 (65) EPA/SR/G/C/2 Peter Wu

4. Product Packages

• GMP V2.0 Base Configurations

– XC/SGw ATM Cross Connect + Signaling Gateway

No media stream processing capabilities

– Base Configuration 201 Media Gateway with co-located XC+SGw

(HS3)

– Base Configuration 202 Media Gateway with co-located XC+SGw

(HS3i) Support for IP transport for CS payload

– Base Configuration 203 Media Gateway with co-located XC+SGw

(HS6)
10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 8 (65) EPA/SR/G/C/2 Peter Wu
 Product Packages

GMP V2.0 Base Configurations – Number of Links

Base 155 Mbps 1,5/2 Mbps 155 Mbps Signaling capacity

configuration ATM ATM/TDM ATM/TDM Broadband Narrowband MSU/s
links links protected (ATM) (TDM)
(ET-M4) (ET-MC1) link pairs signaling signaling
(ET-MC41) links links

XC / SGw 16 16 1 80 256 6500

201 (HS3) 16 16 2 80 256 6500
202 (HS3i) 16+6 16 2 80 256 6500
203 (HS6) 16 16 3 80 256 6500
Note: All capacity figures are given as maximum numbers calculated based
on the Ericsson Standard Traffic Profile. Depending on the traffic profile,
configuration and/or licensing, the actual numbers may vary.

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 9 (65) EPA/SR/G/C/2 Peter Wu

 Product Packages

GMP V2.0 Base Configurations - Capacity

Capacity in Erlangs per configuration type

Base WCDMA WCDMA +

configuration GSM
No EC, No VQE Voice Quality
no VQE Enhancements used
201 (HS3) 4000 3400 2600 1900
202 (HS3i) 3800 3400 2600 1900
203 (HS6) 6000 6000 5200 N/A

Note: All capacity figures are given as maximum numbers calculated based
on the Ericsson Standard Traffic Profile. Depending on the traffic profile,
configuration and/or licensing, the actual numbers may vary.

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 10 (65) EPA/SR/G/C/2 Peter Wu

5. Licensing

Licensing = Setting the right to use features and capacity

• M-MGw Licensing Mechanism

• Feature Licensing
• Capacity Licensing
• Emergency State
• SW Licensing – Supply Aspects

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 11 (65) EPA/SR/G/C/2 Peter Wu

 Licensing

M-MGw Licensing Mechanism

A
pplic
atio
n

• Licensing is used for F

eatu
rec
ontr
olle
rs
C
apa
cityc
ontr
olle
r

– Enabling / disabling features

– Capacity limitations on the node
• One licence key per licensed A
PI
capacity parameter / feature
• License key = a node specific Lic
enc
eMa
nag
er

encrypted string
• All license keys for a specific node are delivered together
as a license key file

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 12 (65) EPA/SR/G/C/2 Peter Wu

 Licensing

Feature Licensing

• Gives possibility to have common SW regardless of which

features a customer has bought
• Optional commercial features are under licence control
• Status either enabled or disabled
• A new feature can be taken into use by updating the
license file

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 13 (65) EPA/SR/G/C/2 Peter Wu

 Licensing

Capacity Licensing

• License parameters
– Simultaneous Call Capacity (SCC )
– Number of CSD modems
– Number of Inmarsat speech coders
• Notification is given when 80% of licensed level reached
• When 100% is reached another notification is given, and
new traffic is not accepted

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 14 (65) EPA/SR/G/C/2 Peter Wu

 Features

Media Gateway Basic Features

• ATM Switch • SS7 Signaling Gateway and

• Element Manager Signaling Transfer Point
• TTC / ETSI / ANSI • SS7 Signaling over TDM
Interfaces • SS7 Signaling over ATM
• Datacom Base • Gateway Control Protocol (GCP)
• Media Stream Function
• ATM Transport
• TDM Transport

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 15 (65) EPA/SR/G/C/2 Peter Wu

 Features

Media Gateway Optional Features

• Lawful Interception • SS7 Signaling over IP

• UMTS Iu Interface • SCCP Accounting
• GSM A-Interface • SCCP Policing
• GSM High Speed Datacom • SCCP Relay
Service • Global Text Telephony
• IP Transport (GTT)
• Voice Quality Enhancement
(VQE)

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 16 (65) EPA/SR/G/C/2 Peter Wu

 Features

Physical Interfaces

• TTC • ANSI
– STM-1 – OC-3
– NTT Megalink (scalable STM-1) – Channelized STS-3
– T1
• ETSI
– STM-1
– Channelized STM-1
– E1

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 17 (65) EPA/SR/G/C/2 Peter Wu

 Features

Datacom Base

• Support for circuit-switched data in both WCDMA and GSM

• Protocol converter enabling connection to PSTN services
• Modem, UDI / RDI
• Applications (for example): MSC Server MSC Server
– WAP WCDMA
/GSM

– Internet access
M-MGw PSTN
– remote LAN access IWF
RNC
RNC
– multimedia ACCESS
ACCESS
SERVER
SERVER
BSC
RNC (optional)

Internet

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 18 (65) EPA/SR/G/C/2 Peter Wu

 Features

SS7 Signaling Gateway and Signaling Transfer

Point
• Routing SS7 messages between signaling links
• Support for different bearer types (ATM, TDM, IP)
• Interworking between MTP3, MTP3b, M3UA

• Note: Signaling over IP is an optional feature

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 19 (65) EPA/SR/G/C/2 Peter Wu

 Features

Gateway Control Protocol (GCP)

• Allows an MSC Server (i.e. MGC) to control resources in

the M-MGw
• Based on ITU-T H.248
• Enabler for the Control Layer
layered architecture BICC
MGC MGC
• ATM or IP bearer H.248/GCP
Call Control
H.248/GCP
• Binary encoded Commands Commands

MGW bearer/connectivity network MGW

Connectivity Layer

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 20 (65) EPA/SR/G/C/2 Peter Wu

 Features

Media Stream Function (1)

• Speech Coder
– Adaptive Multi-Rate (AMR) for UMTS
– Inmarsat speech coders
• Tone Sender
– E.g. call progress tones (alerting, busy, call waiting, …)
• DTMF Sender
– Sends DTMF tones on terminal request
• DTMF Receiver
– Detects DTMF tones from the User Plane, and sends digits
indication towards the MSC Server
• Echo Canceller
10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 21 (65) EPA/SR/G/C/2 Peter Wu
 Features

Media Stream Function (2)

• Interactive Messaging
– Interactive voice response
– Basic, Composite, and Variable messages
• Multi Party Function
– Enables conference calls
– Using Speech Control to limit the number of simultaneous speakers
– Can add Comfort Noise
• Continuity Check
– Testing the integrity of the speech path using an audio tone
• Code Answer
– Used for maintenance purposes
10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 22 (65) EPA/SR/G/C/2 Peter Wu
 Features

Lawful Interception (optional)

• Enables law enforcement agencies to monitor circuit-

switched speech and data
• Monitoring is invisible to the target subscriber and the
operator staff

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 23 (65) EPA/SR/G/C/2 Peter Wu

 Features

UMTS Iu Interface (optional)

• Interface between RNC and Core Network in 3G

• Circuit-switched user plane carried over AAL2, set up
using Q.AAL2 (Q.2630.2) signaling
• Control plane (RANAP) relayed to the MSC Server using
ATM cross-connections or SS7 Signaling Gateway
functionality

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 24 (65) EPA/SR/G/C/2 Peter Wu

 Features

GSM A-interface (optional)

• Interface towards BSS in 2G

• TDM transport
• Call control by MSC Server via the GCP protocol
• Signaling relayed to MSC Server using the SS7 Signaling
Gateway functionality
• Enables integrated transport solutions for 2G and 3G over
a common backbone

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 25 (65) EPA/SR/G/C/2 Peter Wu

 Features

GSM High Speed Datacom Service (optional)

• Speed for circuit-switched data calls can be increased up to

57.6 kbit/s
• Accomplished using:
– High-Speed Circuit-Switched Data, using up to 4 timeslots per call
– 14.4 kbit/s data channel encoding
• Good real-time capabilities: Predictable bandwidth and delay

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 26 (65) EPA/SR/G/C/2 Peter Wu

 Features

Voice Quality Enhancement (VQE) (optional)

• Mobile Cross-Talk Control

– Remove echo originating in mobile terminals
• Noise Reduction
– Reduce background noise when calling from noisy environments
• Network Probe
– Provides information about the network, by measuring speech
levels, delays, etc.
– The collected data can be used to improve settings, and thus also
speech quality
• Fixed Level Control
– Can equalize line level differences on incoming routes
10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 27 (65) EPA/SR/G/C/2 Peter Wu
 Features

SCCP Accounting (optional)

• Signaling accounting between operators: Count and

register SCCP messages meeting specified criteria
• Base for billing
• Data is stored periodically on local persistent media
• Fetched using FTP (e.g. to a billing system)

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 28 (65) EPA/SR/G/C/2 Peter Wu

 Features

SCCP Policing (optional)

• Allows SCCP messages from/to certain destinations to be

discarded

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 29 (65) EPA/SR/G/C/2 Peter Wu

 Features

SCCP Relay (optional)

• Routing SCCP messages (e.g. MAP, CAP) in the signaling

network based on
– Global Title and/or Sub-System Number
– Destination Point Code and/or Sub-System Number

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 30 (65) EPA/SR/G/C/2 Peter Wu

 Features

Global Text Telephony (GTT) (optional)

• Enables support for transmitting text messages through
ordinary speech traffic channels
• Persons with speech or hearing disabilities can use
teletypewriter (TTY) equipment in fixed and mobile
networks (UMTS, GSM) MSC Server

• Using Cellular Text Modem

M-MGw
(CTM) tones having a high BSS /
UTRAN
CTM

robustness against channel CTM

CTM
CTM
Baudot

errors Baudot
Baudot

• Signal adaptation between

CTM PSTN
capable
Mobile

conventional Baudot tones Baudot

and CTM tones

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 31 (65) EPA/SR/G/C/2 Peter Wu
7. Hardware Structure

• Board types
– General Processor Board (GPB) – Timing Unit Board (TUB)
– Switch Core Board (SCB) – Media Stream Board (MSB)
– Switch Extension Board (SXB) – Exchange Terminals (ET)
• Subracks
– Main subrack
– ATM Extension subrack
– IP Extension Subrack
– Media Stream Extension subrack
• Inter Subrack Links
• Cabinet allocation example
10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 32 (65) EPA/SR/G/C/2 Peter Wu
 Hardware Structure

Board types

• General Processor Board (GPB)

– Main processor
– Flash disk
– Ethernet (10/100) and serial (RS-232) ports
– Interactive Messaging
• Switch Core Board (SCB)
– ATM switch core
– 4 Inter Subrack Links (ISL)
– Distribution of system clock

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 33 (65) EPA/SR/G/C/2 Peter Wu

 Hardware Structure

Board types

• Switch Extension Board (SXB)

– 4 Inter Subrack Links (ISL)
– Used for expansion of the M-MGw
• Timing Unit Board (TUB)
– CPP system clock
– Input of external synchronization (e.g. GPS)
• Media Stream Board (MSB)
– Board processor + 16 digital signal processors (DSP) for media
stream manipulation
– Media Stream Functions (e.g. speech codecs, echo canceller, etc.)
– IP termination

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 34 (65) EPA/SR/G/C/2 Peter Wu

 Hardware Structure

Board types
• ET-MC1
– 8 E1 / T1 interfaces, 2 / 1.5 Mbps
– TDM / ATM
– AAL2 Multiplexing
– AAL1 Circuit Emulation
– Inverse Multiplexing for ATM (IMA)
• max 8 links for one connection between two nodes
• ET-M4
– 2 STM-1 / OC-3 interfaces, 155 Mbps
– ATM
– AAL2 multiplexing

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 35 (65) EPA/SR/G/C/2 Peter Wu

 Hardware Structure

Board types

• ET-MC41
– STM-1 / OC-3 interface, 155 Mbps (63 E1 or 84 T1 logical
channels)
– TDM / ATM
– Multiple external E1/T1 links can be multiplexed (ET4-1) to
channelized STM-1 on this board
– AAL2 Multiplexing
– AAL1 Circuit Emulation
– Inverse Multiplexing for ATM (IMA)
– MSP 1+1 (Multiplex Section Protection)
• paired with stand-by ET-MC41
• includes also Equipment Protection
10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 36 (65) EPA/SR/G/C/2 Peter Wu
 Hardware Structure

Subracks

• Main subrack
– Central functions of the node (e.g. signaling, O&M, …)
• ATM Extension subrack
– ETs for handling the traffic
– Available in different versions depending on capacity needs (# ETs)
• IP Extension Subrack
– Device and processor boards for CS traffic handling over IP bearer
– ETs for handling the traffic
• Media Stream Extension subrack
– Device boards for handling payload modifications
– ETs for handling the traffic
10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 37 (65) EPA/SR/G/C/2 Peter Wu
 CU
CU
CU
Fan
Fan
Fan

MACU
ATM
Main

Subrack
Subrack

Subrack

Extension
Extension

Front View
Media Stream

IP

10/0062-2/FCP 101 2915/11 Rev PA1

CCF
Fan

Subrack

Rear View
Extension
Cabinet Layout

16/05/2005
SCB

38 (65)
SCB SCB SCB
Cabinet Allocation Example:

GPB GPB GPB GPB

GPB GPB GPB GPB
ET-M4 TUB GPB ET-M4
ET-M4 TUB GPB ET-M4
ET-M4 GPB GPB ET-M4
ET-M4 GPB MSB MSB
ET-M4 GPB MSB MSB
ET-M4 GPB MSB MSB
ET-M4 GPB MSB Dummy
ET-M4 GPB MSB Dummy
ET-M4 GPB MSB Dummy
ET-M4 GPB MSB Dummy
ET-M4 SXB MSB Dummy
ET-M4 SXB MSB Dummy
ET-M4 SXB MSB Dummy
ET-M4 SXB MSB Dummy
ET-M4 SXB MSB Dummy
Dummy Dummy MSB Dummy
Dummy Dummy MSB Dummy
Dummy MSB Dummy
ET-MC41
Dummy Dummy Dummy
GMP V2.0 Base Configuration 202 (HS3i)

ET-MC41 Dummy Dummy

ET-MC41
GPB Dummy
ET-MC1 GPB Dummy
ET-MC1 ET-MC41
GPB Dummy
Dummy
Subrack Configuration

GPB SXB Dummy

SCB SCB SCB SCB
IP

MS

EPA/SR/G/C/2 Peter Wu
ATM
Main
Hardware Structure
 Operation & Maintenance

Management Applications
• Element Manager (EM)
– Has a CPP part and a M-MGw part
– Thin client (Java applet in web browser) loaded from the node
– Common look-and-feel with other node EMs
– Higher level of abstraction than the MOM view
– Fault, Software, Equipment, Configuration, and Performance Mgmt
• Moshell
– A useful and powerful tool we like to use, specially during
troubleshooting
– Run on Unix or Windows (Cygwin)
– Command line interface
– Details see this webpage
[Link]

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 39 (65) EPA/SR/G/C/2 Peter Wu

 Operation & Maintenance

Performance Management

• Statistical data about M-MGw is collected in MO attributes

called PM counters
– Level counters reflects the status of some resource at a given time
– Peg counters are cumulative, incremented each time an event occurs
• PM counter data is collected by ”scanners” at predefined
intervals (typically every 15 minutes)
• The collected data is stored in XML files on the node
• Management applications can
– retrieve the XML files via FTP
– parse the XML files to read the data
– present the data to a user in some suitable way
10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 40 (65) EPA/SR/G/C/2 Peter Wu
PM Counters
• There is counters in MsDevicePool MO’s and in vMGw
Mo’s.
• All these are described in Managed Object Model
– EG. In device pools:
• pmBusyDevices
• pmNormalRelease
• pmForcedRelease
– EG. In Virtual Media Gateway
• pmGcpNrOfReceivedMessages
• pmGcpNrOfSentMessages
• pmNrOfContextsBusy
• Etc.

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 41 (65) EPA/SR/G/C/2 Peter Wu

 Node status Check

Some things to check to be more sure that Mgw node

is up and running

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 42 (65) EPA/SR/G/C/2 Peter Wu

Using EM for checking status
• It’s handy to use also official tool for node status check
– MS devices
– vMGw status
– Link status
– TDM Groups

• But keep in mind, that there can be also fault in EM..

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 43 (65) EPA/SR/G/C/2 Peter Wu

MS Devices

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 44 (65) EPA/SR/G/C/2 Peter Wu

vMGw status

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 45 (65) EPA/SR/G/C/2 Peter Wu

Link Status

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 46 (65) EPA/SR/G/C/2 Peter Wu

TDM Groups

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 47 (65) EPA/SR/G/C/2 Peter Wu

Ds0Bundles

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 48 (65) EPA/SR/G/C/2 Peter Wu

Alarm

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 49 (65) EPA/SR/G/C/2 Peter Wu

 Node status check (Target: M-MGw R3)
• When
•Node status check has to made really well at least:
• New delivery has been loaded to node.
• New black Loadmodules has been installed
• Some weird problems comes up

• Also quick node status check is good to make after every node restart

• What
• All boards has came up
• Message from serial port
• Sysmgr: All configured PIUs started on node
• Every SR must have at least 1 SCB up
• All loadmodules have successfully started
• MS devices are available
• idle devices available in every device pool
• vMGw’s operational state is ENABLED

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 50 (65) EPA/SR/G/C/2 Peter Wu

 Node status check (Target: M-MGw R3)

Main commands on node terminal

Cello ‘based commands’
• vii : shows boards current led status
• sma -all : shows loadmodules RPU state
• llog (-l) : shows, have there been errors in board
• te log read : print out trace & error log
Helpers to check status of Ms Devices

M-MGw R3 Specific helpers

•gramsb : show msb’s to which GRA has successfully attached
•grapool : show current status if pools in specific device set
•gradsl : list all devices type type and where they are located

• Note !! Status of IM devices are not included here.

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 51 (65) EPA/SR/G/C/2 Peter Wu

 Example of result of vii:
001000> vii
----- VII SERVER INFO -----
registered clients:
client FAULT LOAD_START NO_POWER BOOTTEST MISSING_RESOURCE BOARD_LOCKED BOARD_BUSY SHUTDOWN
---------- ----- ---------- -------- -------- ---------------- ------------ ---------- --------

LED State
GREEN CLS_LEDI_ON
RED CLS_LEDI_OFF
YELLOW CLS_LEDI_OFF

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 52 (65) EPA/SR/G/C/2 Peter Wu

Commands in CH
ch_command_loggcp Log GCP messages.

ch_counters_command [vmgwId] [clear <all>|<vmgwId>] Print or clear command statistics of one

VMGw or all VMGws.

ch_counters_gcp CRI-interface for ChdMessageHandler

ch_info_fault CH fault status

ch_info_loadcontrol CRI-interface for ChdLoadControlC

ch_info_tc [vmgwId] Print out TransactionCoordinator information of

a certain VMGw. If no vmgwId is given, data for
all existing TransactionCoordinators will be
printed.

ch_info_th CRI-interface for

ChdTransactionHandlerFactoryC

ch_info_vmgw [vmgwId] Print out VMGw information. If no vmgwId is

given, data for all existing VMGws will be
printed.

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 53 (65) EPA/SR/G/C/2 Peter Wu

Commads in STC
stc_info [<vmgwId>] Displays information about STC load module

Commads in DB
db_info_license Shows stored sw licensing data
db_info_tdm Shows stored tdmgroup data
db_info_term Shows stored termination data
db_info_vmgw Shows stored vmgw data

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 54 (65) EPA/SR/G/C/2 Peter Wu

Commands in MeSC
mesc_counters <options> Displays MeSC counters and Vmgw states
mesc_counters_aal <options> Displays aal counters
mesc_counters_device <options> Displays device related counters
mesc_counters_gcp <options> Displays information about received and sent
GCP commands and list of errorcodes with amounts
mesc_counters_ip <options> Displays information of IPBCP and BCTP statistics.
mesc_info_csdSsg <options> Displays information about CSD Segments.
mesc_info_csg <options> Displays information of ConnectionSegments.
mesc_info_ctx <options> Displays debug & CtxState information
mesc_info_mescmsghdl <options> Displays Mesc Mesagge Handler's state and internal data.
mesc_info_muxSsg <options> Displays information about MUX Segments.
mesc_info_tdm <options> Displays TDM state, group and internal data
mesc_info_termdeposit <options> Displays Termination Deposit's state and internal data.
mesc_info_vmgw <options> Displays status of Vmgws
mesc_info_voiceSsg <options> Displays information about Voice Segments.

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 55 (65) EPA/SR/G/C/2 Peter Wu

 Tracings – Call path tracing

• CPT in MGw:
- Step 1: CPT in MSC. In the printout you see something
similar:
XSS TRACING
:
TAG IDX MISCDATA
xx y1 CMGWz
xx y2 CMGWz
xx y1 <Context Id>
xx y2 <Context Id>

- Step2: In EMAS go to menu “Utilities” => “Start Call Path

Trace” and type the CtxId from the MSC printout
- Step3: Click on “Print”. With the PDF printer you’ll get a PDF
document containing your CPT results

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 56 (65) EPA/SR/G/C/2 Peter Wu

 Tracings – GCP trace

• Tracing of GCP messages:

- Step1: Specify trace via Shello

lhsh 002600 te e trace5 stcMbaMtp3biClientC*
- Step2: Get TM into operation and switch “Log to file” in xterm
- Step3: After the TC stop logging to file
- Step4: Decode the results with gcpdecoder (e.g. in
/home/eednod/bin)

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 57 (65) EPA/SR/G/C/2 Peter Wu

 Recovery of the node

(how to get it back in shape, how to clear

hangings, how to create work around)

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 58 (65) EPA/SR/G/C/2 Peter Wu

General
• If fault is detected from node, cause of fault should always
be found before using any ‘dirty’ recovery actions.
• Really hard / impossible to describe all possible faults /
recovery actions, because new delivery brings always
some new ‘features’ -> …
• Every fault has identity of it’s own….
• Different Hardware -> different problems
• Different Configuration -> different problems.
• General understanding of system is needed.

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 59 (65) EPA/SR/G/C/2 Peter Wu

Possible problem areas (MGW)
• When executing Node restart all boards are actually not
restarted.
• Hanging devices after MSB/DSP restart.
• TDM Term Group related problems.
• Load modules fails to attach to different interfaces and
services
• Memory leaks
• MSB area problems during traffic

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 60 (65) EPA/SR/G/C/2 Peter Wu

3 Main problem Areas

• Configuration
• Restart
• Traffic, Dimention issues

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 61 (65) EPA/SR/G/C/2 Peter Wu

• ONCE YOU HAVE PROBLEM, HOW TO TROUBLESHOOT IT:

• What are symptoms?

• High load.
• Restart of program, board or even node node.
• Memory leakage. (see appendix 2 “heap memory usage” )
• Some services not available (signaling links up to vmgw’s).
• Some calls are rejected.
• Faulty MsDevices
• Hanging context
• etc.

• Before start troubleshooting, collect some information from node: (Health

Check)
• trace & error logs from all boards (board_status –g –c “te log read”
• pm counters and result of application specific coli commands.
• llog, dump, pmdumps

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 62 (65) EPA/SR/G/C/2 Peter Wu

• What has lead to this problem?
• Configuration has changed.
• What was the actual traffic case.
• Was something done when problem occurred. Is the problem reproducible?

• Start to troubleshoot the actual root cause.

• Think which loadmodules are involved in this case.
• Do you see something unexpected in trace & error logs.
• ERROS
• Unexpected signals
• Rejects
• Timeouts
• etc.
• Dig more deeply. Eg. From where the possible reject is received.
• Trouble shooting is hard work and it needs knowledge of system!

• Node recovery
• How to recover from the fault situation
• eg. Lock and Unlock vmgw or Tdm Term Group.
• program restart, PIU restart….

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 63 (65) EPA/SR/G/C/2 Peter Wu

Reload with a CV (Configuration Version)

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 64 (65) EPA/SR/G/C/2 Peter Wu

Restart M-MGW from EM

10/0062-2/FCP 101 2915/11 Rev PA1 16/05/2005 65 (65) EPA/SR/G/C/2 Peter Wu