HandsOnTCM_PA2

Rev. PA2 M-MGw hands-on training EMC2007-07-10 1 (73)

Ericsson Media Gateway for Mobile Networks

M-MGw hands-on training EMC for TCM


ContentDay 1• General Information ~60 min• Software Structure ~30 min• CPPemu ~ 5 min• Exercises ~75 minDay 2• MO scripts ~20 min• Upgrades ~10 min• ATM basics ~20 min• Exercises ~90 minDay 3• Basic Troubleshooting ~40 min• MGW Sanity Check ~20 min • Exercises ~100 min


Typical Testplant Network

T1/E1

ATM

IP

RNC

RNC231

M- MGw1M-MGw3RNC

RNC241

M- MGw2M-MGw6

RNC

BSC3A

RNC

BSC6A

MSC/TSCServer

MSC600Server

MSCServer

MSC300Server


GENERAL MGW INFO


• The MOM organizes the MO classes in a containment hierarchy (e.g: Subrack – Slot – Plug-in Unit)

• Every instantiated MO is given a unique identity relative to its parent (Relative Distinguished Name, RDN)

• A Local Distinguished Name (LDN) is a sequence of RDNs forming a unique name within the nodeExample: ManagedElement=1,Equipment=1,Subrack=2,Slot=15

• Each MO has also a (re)configurable userLabel that can be used to specify descriptive names for MOs (e.g. give destination information for link MOs)

Managed Objects


Relationship between objects

• Parent – child relationshipParent object needs to be defined before child object can be defined.

For example, you need to define the physical fiber port (Os155SpiTtp) before defining the Aal2Path (Aal2PathVccTp).

• Reserved objectsA resource used by one or more other objects.

For example, the SCTP object is defined to represent an SCTP termination on an IP port of a GPB board. The M3uAssociation objects reserve the SCTP object to use it’s IP port to communicate to other nodes.

In the attached document, the solid line represent a parent-child relationship and the dotted line represents a reserved object relationship. This document is not official and should only be used as a guideline.

Microsoft Word Document


CPP and MGW Managed Object Models (MOM)

• The MOMs are used as a reference to define Objects in the CPP nodes. All the parameters are listed in these documents.

• There is one document for CPP and a document for MGW. The MGW MOM contains the parameters that are specific to the MGW. For example, TdmTermGrp, Vmgw, etc.

• Performance counters for each object are also listed in this document.

• This document changes with every release and also during the development of a release. They are stored in http://cdmweb.ericsson.se.

• Also available on the webpage: http://quickplace.ericsson.se/quickplace/lmf-m-mgw-r5-shipment/PageLibraryC125720C00285E3E.nsf/h_Toc/44C9FF004135C414C125720C002A8410/?OpenDocument


Configuration reference documents

• Remote device allocation spreadsheet is updated before making any changes in the network. It can be found in the vob: lmc_gsm_view\CN_60_NIV\TCM\LOCAL_NWPL

• ATM Network Configuration is a diagram that shows the ATM network connections. It is currently kept in the RDAS.

Microsoft Excel Worksheet


Use Case Scenarios

• UCS are used to determine how the MGW handles specific call scenarios. Can be found in CDM web.

For R5:

http://cdmweb.ericsson.se:7045/TeamCenter/controller/home

Search for “*155 56-AXM101 01/6”

Can be used to determine how, when and which devices are seized during specific call scenarios.

Adobe Acrobat 7.0 Document


Board types

• General Processor Board (GPB)– Main processor– Flash disk– Ethernet (10/100 base-T) and serial (RS-232) ports

• Switch Core Board (SCB)– ATM switch core– 4 Inter Switch-Module Links (ISL)– Distribution of system clock


Board types (continue…)

• Switch Extension Board (SXB)– 4 Inter Switch-Module 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.)



• 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



• ET-MC41– STM-1 / OC-3 interface, 155 Mbps (63 E1 or 84 T1 logical

channels)– TDM / ATM– 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



• ET-C41/4– 4 STM-1 / OC-3 interface, 155 Mbps (63 E1 or 84 T1 logical

channels)– TDM– MSP 1+1 (Multiplex Section Protection)

• paired with stand-by ET-C41/4• includes also Equipment Protection

• ET-MFG (Multi Function Gbit ET)– 2 1000BaseT Gbit electrical interface for IP traffic

(optional; 2 1000BaseSX 1Gbit optical interface)– Link redundancy


Naming convention

• The fibers use the following naming convention: <subrack><board><port>. For example, port number 2 of ET-M4 in slot 9 of ATM subrack is called: 2092

• The T1s can either be on board ET-MC1, ET-MC41 or ET-C41/4 via an ET4-1. They are noted differently in the remote device allocation spreadsheet. The ET-MC1 are noted with Slot and Port. For example Slot25 Port4 is connected to the ET-MC1 in Slot 25 and Port4 of the 8 ports. For ET-MC41 and ET-C41/4, we need to identify the fiber (see above) and the DIP (1-84). Look at the attached document to see where that DIP is located.

• VMGWs are named according to the string. For example, VMGW1 in string 300 is connected to MSC300. VMGW2 is connected to MSC 600. It is opposite in string 600. VMGW1 is connected to MSC600 and VMGW2 is connected to MSC300.

ET4-1


Naming convention (continue…)

• StsT1Ttp,Vt15Ttp is a scaled down version of the K.L.M. notation. This is a way to represent the T1s that are multiplexed on a fiber. The T1s are divided in 3 StsT1Ttp and each StsT1Ttp has 28 Vt15Ttp, for a total of 84 T1s. The range of values for K is 1-3, L is 1-7 and M is 1-4. For example, DIP 36 has a K.L.M. notation of 2.2.4. The MGW concatenates the last two digits into one, which gives a notation of 2,8. This notation is also used in ETSI but for 63 E1s.

• The Link<xy> is the cable that runs from the ET4-1 to the Dsx Panel. The link number is shown on the patch panel.


Shello

• Command Line interface to access the MGWs. Has more features and flexibility than the standard OSE interface used when you use ‘telnet’ or ‘ssh’ to access the node.

• You can access all sorts of information regarding shello via this web page: http://eed.ericsson.se/services/eed-x-s/o/soe/cello/shello/index.html

• To get information regarding the commands in shello, type ‘?’ or ‘help’.

• In the EMC environment, shello is located in:/project/cnicmtl/mgw/tools/shello3And is started using the command ‘shello3 <mgw id>’.

• MO commands are used to access the Managed Objects.– moget– molist– mostatus– …


Moshell

• Also a command line interface used to get information from the MGWs.

• A little bit better to retrieve performance statistics. • The only tool that can retrieve information about scanners.• You can get all sorts of information regarding moshell on the

following web page:

http://utran01.epa.ericsson.se/moshell• In the EMC environment, Moshell is located in:

/project/cnicmtl/mgw/tools/moshell


Configuration Version (CV)

• The CV is a backup of the configuration of the MGW.• You can have a maximum of 50 CVs at one time on the node.• The CV does not backup the software. In case of major crash,

you would need to retransfer the software and a valid CV using XFTP (a version of xftp compiled for OSE can be found in the MGW tools directory). Make that CV active and restart the node.

• Files included in a CV:– ARMAMENT– LLP.LMID– attribute– db.dat– md5checksums– ok


CV commands

• cv ls – will list all the CVs on the node• cv mk – will make a new CV• cv set – will make a CV active. Will use this CV at next restart.• cv rm – will remove a CV. This CV can not be assigned.• cv rbrm – will remove a CV from the rollback list.• cv cu – displays current configuration


CV naming convention

• There is currently no naming convention. It is very difficult to come up with one.

• It should always start with the MGW CM version.• When a CV is made, a TESUP entry is created stating the

previous CV, the new one and the reason for the new one.


Walk in the lab

• Take a walk in the lab to show MGWs, patch panels, LAN switches and ET4-1.


Software Structure


MGw Software Structure

Cello

STCCONFMGR

MESC

CH

UPCF

MSP

Voice Processing

O&M - UPCF

O & M

O&M - MSP

DB

MSB

Data Processing

CRH

MFP


UPCF – User Plane Control Function

• ConfMgr– Co-ordination and configuration of UPCF. Agregates the interfaces

towards O&M.

• UPCF database - DB – The UPCF databases (DB) main purpose in M-MGw is to keep the

dynamic GCP view consistent with MGC. DB provides its services for MESCs, CH and configuration manager.

• Signalling Transport Converter - STC– Make GCP independent of bearer– STC communicates only with Controller Handler (CH) and MTP3b

service from CPP – STC might be a bottleneck in M-MGw as all commands go through it

• Controller Handler - CH– Decodes GCP messages and forwards them to MeSC (round robin)– Encodes GCP messages and sends them to STC– Responsible for GCP protocol termination


UPCF (continue…)

• Media Stream Control - MeSC– Manages contexts and terminations– Manages and connects stream connection segments– Every MeSC has a specific Context IDs and Non-TDM termination IDs

range. Termination IDs are unique inside MGW and context IDs are unique inside VMGW.

– MeSCs can communicate between themselves for moving terminations from Contexts from one MeSC to another MeSC.

– VMw functionality is distributed to all of the MeSC processes. – Each MeSC can process requests from any VMGws (up to 32).


MSP Media Stream Processing

• MSB Media Stream Board– It’s executing on Board Processor (BP) and on DSP processors in MSB. MPP

provides support for the applications from MSP system area running on the MSB. The support includes services for communication distribution, driver handling, device loading etc.

• Voice Processing– provides the basic functions needed to support the circuit-switched speech

services in WCDMA and GSM. It enables speech coding, echo cancellation, interactive messaging, tone sending/reception and multi-party calls.

• Data Processiong– CSD Digital– CSD GSM MFH– CSD Modem

• MFP Media Frame Processing– User Plane Media Frame Handler (UP_MFH) converts different framing

formats, e.g. AAL2 to AAL1 conversion. – be able to utilise IP transmission in the backbone, the traffic needs to be

converted from either TDM or ATM into IP.


MSP (continue…)

Common Resource Handling - CRH• Resource Access Adapter (RAA)

– It keeps track of a number of distributed resource handlers - GRA.– RAA has the overview of existing resources in the MGw.– There can be several RAA per node, one per VMGw.

• Media Stream Manager (MSM)– It handles the device configuration interface towards O&M, keeps track

of the state of various resources and informs the RAA of their location. There is only one MsManager per node.

• Resource Access (GRA and IM_RA) – RA performs resource handling in the CRH system and keeps track of

device information. IM_RA is controlling the IM devices, GRA is controlling any other device type. Devices will be created on these GRA in such a way as to get approximately the same number of devices per GRA inside every subrack.


MGw software communication

CH1 CH2

STC

MSC1 MSC3

MeSC1 MeSC2 MeSC3 MeSC4

GRA1 GRA2 GRA3 GRA4

DSP POOL


CH Commands

Controller handler (CH) implements the GCP interface towards MGC meaning that CH is responsible for GCP protocol termination. The task of the CH is to decode the GCP messages from MTP3b messages, extract the commands and forward them to the MESC where the commands are processed. It has been configured to have one instanciation per VMGW.

• ch_counters_command– Prints the statistics of how many commands of a particular type

have been executed, the number of rejects per command and the number of pendings per command type.


MeSC Commands

Media Stream Control (MESC) has two main tasks: to manage contexts and terminations, and to manage and connect stream connection segments. MESC has both GCP and User Plane views. GCP view has contexts and terminations, which are logical entities. The GCP view is then mapped by MESC to User Plane view, which has the actual devices and Connection End-Points (CEPs).

• mesc_counters_gcp– List and amounts of sent and received GCP commands, list and

amounts of error codes.

• mesc_counters_aal– Displays the counters for AAL1/AAL2, number of connection

request, connection reject, Disconnects, etc.


MeSC Commands (continue…)

• mesc_counters_device

– Request, reject and releaseInd counters for all MSP device types. Useful to know if device allocation was rejected while running traffic.

• mesc_info_ctx

– Displays details of busy contexts. Can show hangings in the MGW.

• mesc_info_vmgw

– Displays vmgw related counters, amongst them the number of busy contexts.

• mesc_info_fpif – Displays fpif related counters, amongst them the number of busy

contexts.


CPPemu


CPPemu

• To be used within SEA to simulate CPP nodes• Emulates the hardware. Operating system and software is the

same as a real CPP node

Adobe Acrobat 7.0 Document


Exercices


MO scripts


Writing MO scripts• Scripts are kept in common directory. For example in CN6.0 they

are kept in /project/cnicmtl/CN60/mgw/mo_scripts• Each MGW has a lazy guide which describes the steps used to

configure it from scratch.• CREATE, SET, DELETE, ACTION are commands used in an MO

scriptCREATE( parent "ManagedElement=1,Equipment=1,Subrack=2,Slot=19,PlugInUnit=1,EtMfg=1,GigaBitEthernet=2191" identity "219-3103" moType IpInterface exception none nrOfAttributes 7 userLabel String "219-3103" vid Integer 3103 vLan Boolean true rps Boolean false mtu Integer 1500 networkPrefixLength Integer 24 defaultRouter0 String "10.2.110.1")


MOPP tool

• Tool to help reduce the time to write MO scripts.• Tools can be used in /project/cnicmtl/mgw/tools/mopp

– mopp5

• To get help on the tool, just give the option ‘?’

– :create mtp3bsr sp=2-2310 srs=2-2301 m3ua=MSC3_1 priority=1 // MSC300 GCP– :create mtp3bsr sp=2-2310 srs=2-2301 m3ua=MSC3_2 priority=2 // MSC300 GCP


Information from MGW webpage

• IP address of MGWs• Hardware configuration• License files• Terminal server ports• Version that is currently installed. Needs to be modified after each

MGW upgrade.• FAQ webpage has a lot of TCM information. i.e. how to change the

O&M IP address, change the license file, put a black delivery, etc.


MGW upgrades

• Upgrade package downloaded from MGW TCM at LMF. It is indicated in the NUM where to exactly retrieve it.

• There is one package for GMP V2 and one for GMP V3. It is important to use the correct package.

• Look at the upgrade_control_file.xml to make sure the upgrade path is supported.

• The upgrade can be done using shello, EMAS/Node Manager or OSS-RC. We commonly use EMAS to do the upgrades.

• An FTP ‘server’ needs to be setup before we can proceed with the upgrade.


ATM Basics


ATM Basics

• ATM, Cell Switching concept - 53 bytes long cells (5 byte header, 48 bytes payload)

• ATM, High bandwidth in transport network - One network for all traffic

• Different Adaptation Layers for different type of traffic:– AAL5 – signalling traffic (packet type of traffic)– AAL2 – user payload

• “Bandwidth on demand”


ATM Benefits

• Better network utilization• Same mechanism works for all traffic types• All slots are the same size (53 bytes = 1 ATM cell)• Any user can use any empty slot• No notion of specific slots assigned to specific users• Can do low speed ATM (e.g., 1.5 Mbps)• Can do high speed ATM (e.g., 155 Mbps)


Transmission of Data

OC-3/STM-1 link

ATM VPATM VC (AAL2 path or AAL5)

248 AAL2 connections (a.k.a. CIDs)if VC is AAl2 Path


ATM Adaptation Layers

• AAL1• CBR Ex: Circuit

Emulation• Connection oriented• Timing information exists

• AAL2• CBR Ex: Speech• Connection oriented• Requires timing information

• AAL5• VBR or UBR Ex: Signaling• Connection oriented• No timing information


ATM Service Categories

• Constant Bit Rate (CBR): emulates a copper wire and minimum cell loss and variation in delay. Used for real time audio and video.

• Unspecified Bit Rate (UBR): no guarantee on cell loss and delay variation. Suited for TCP/IP traffic. Perfect to use excess bandwidth.

• Variable Bit Rate (VBR): easy description is in between the previous two service categories. Used for retrieving multimedia e-mails, MPEG and Frame Relay. Can be real-time or not real-time, depending on the application, but not currently supported in MGW.


ALI Traffic Descriptors

• ALI constrains:

– Only Variable Bit Rate (VBR) can be used for signalling and CBR for payload

– Fixed values can only be set on ALI

– Peek Cell Rate (PCR): 440, 660, … 7040, …112640 [for RPB-S]

– Peek Cell Rate (PCR): 440, 660, … 7040, …168960 [for RPB-E]

– Sustainable Cell Rate (SCR): 1, ½, 1/3, ¼, 1/5, 1/6, 1/7, and 1/8 of the PCR

– Minimum Burst Size (MBS) depends on SCR/PCR ratio

– Shaping is done to SCR allowing a burst specified by MBS

RNC

M-MGW

SGwSTP

AAL2

MSC

TSC VLR

G-MSC

ALI

M-MGW

SGwSTP

AAL21-100 1-200

ATM PVC(AAL5)

ALIcharacteristics

CPPcharacteristics


ATM Traffic Descriptors

• CPP:

– Only Unspecified Bit Rate + (UBR+) can be used

– Peek Cell Rate (PCR) – Maximum cell rate allowable on a circuit

– Minimum Cell Rate (MCR) – Minimum cell rate garanteed

– Shaping is done only to PCR in direction MSC

– Sustainable Cell Rate (SCR): Cell rate averaged over a long time interval

– Cell Delay Variation Tolerance (CDVT): variation in cell transmission time

• Problem: Different ATM implementations on ALI and CPP!

• How to align SS7 TD?

– Rule: PCRALI=PCRCPP

– Rule: SCRALI=PCRALI and MCRCPP=PCRCPP-1


ATM

AAL5 (I.363.5)

SSCOP (Q.2110)

Control plane

MTP3B (Q.2210)

ISUP

RANAP

BICC

SSCF-NNI (Q.2140)

MAP

QAAL2

GCP

ATM Signaling Layers


SS7 over ATM- Broadband ATM


SS7 over TDM – Narrowband SS7


SS7 over IP


Exercises


Basic Troubleshooting


Available resources

• All the MGW tools are kept in the following directory: /project/cnicmtl/mgw/tools

• There is a GCP decoder available to decode the GCP commands exchanged between the MGW and the MSC

• There is a source of frequently asked questions. This web page is updated to share information with everyone using the MGW.

http://www.lmc.ericsson.se/~lmcmaab/cnicmtl/mgw/share/web/FAQ_MGW.htm

• It is sometimes difficult to remember which traces should be used in the MGW. Instead of everyone keeping their own list of traces and help files, this web page is shared with everyone. http://www.lmc.ericsson.se/~lmcmaab/cnicmtl/mgw/share/web/TraceCheatSheet.htm

• There is a lazy guide available for Nethawk.http://www.lmc.ericsson.se/~lmcmaab/Testplant.html


Core Network Call Flow

• To make sure the calls are being processed correctly. The Core Network call flows can be used as a reference.

• It is possible to set traces in the MGW to make sure the actual call flow is following accurately the expected call flow.

• The latest documents can be found in the below web page. •

http://switching-products.ericsson.se/SystemManagement/Projects/SL1/Flow_charts/flow_charts_index.htm

Rev PA1 M-MGw & Core Network Presentation2006-11-22 58 (70)

Call Flow – Network Example

MGw 3VMGW300VMGW600

MSC 300

MGw 1VMGW 300

MGw 4VMGW 600

MGw 2VMGW 300

MSC 600

RNC 301

RNC 601

RNC 302BSC 301

IPATM (sig)TDMATM

GCP

QAAL2

BICC

BSSAP

RANAP

PSTN

ISUP


IPBCP


Call Flow – Call Scenarios

MGw 3VMGW300VMGW600

MSC 300

MGw 1VMGW 300

MGw 4VMGW 600

MGw 2VMGW 300

MSC 600

RNC 301

RNC 601

RNC 302BSC 301

IPATM (sig)TDMATM

PSTN



Call Flow – Example 2

MGw 3VMGW300VMGW600

MSC 300

MGw 1VMGW 300

MGw 4VMGW 600

MGw 2VMGW 300

MSC 600

RNC 301

RNC 601

RNC 302BSC 301

IPATM (sig)TDMATM

PSTN6.APM (BCUID)

5.ADD REP

4.ADD

3.IAM (forw.)

2.CALL PROCEED

1.SETUP

7.ADD

8.ADD REP

9.RAB ASSIGN (BA MGw 3)

10.ERQ

10.ERQ

11.ECF

11.ECF

12.IUUP init

13.IUUP ack

14.RAB ASSIGN RES

16.ADD

24.APM

23.NOTIFY REP22.NOTIFY

19.ECF

18.ERQ

17.ADD REP25.NOTIFY

31.ACM

29.IAM

28.ADD REP

27.ADD

26.NOTIFY REP 32.MOD

33.MOD REP

34.ACM

35.ALERTING

36.ANM37.MOD

38.MOD REP

39.CONNECT

15.COT

30.COT

20.NbUP init

21.NbUP ack



Call Flow – Example 2

MGw 3VMGW300VMGW600

MSC 300

MGw 1VMGW 300

MGw 4VMGW 600

MGw 2VMGW 300

MSC 600

RNC 301

RNC 601

RNC 302BSC 301

IPATM (sig)TDMATM

PSTN6.APM

5.ADD REP

4.ADD

3.IAM

2.CALL PROCEED

1.SETUP

7.ADD

8.ADD REP

9.RAB ASSIGN

10.ERQ

10.ERQ

11.ECF

11.ECF

12.IUUP init

13.IUUP ack

14.RAB ASSIGN RES

16.ADD

24.APM

23.NOTIFY REP22.NOTIFY

19.ECF

18.ERQ

17.ADD REP25.NOTIFY

31.ACM

29.IAM

28.ADD REP

27.ADD

26.NOTIFY REP 32.MOD

33.MOD REP

34.ACM

35.ALERTING

36.ANM37.MOD

38.MOD REP

39.CONNECT

15.COT

30.COT

20.NbUP init

21.NbUP ack



DSP dumps

• The directory /c/usr/dsp_dump should be monitored for new DSP dumps

• The first two numbers (73-21-xx-xx-first) tell you the MSB (732100). The last number is the DSP (xx-xx-xx-13-first), within that MSB

• To view the details of the DSP dump, you need to connect to the affected MSB and send the command: readlog detail

• Other information required to analyze a DSP dump:– te log read

– rev

– listloaded


Fault Reporting

• All faults are reported using MHS, the TR writing guideline should be used as a reference. The document can be found on the project web page.

• CPP TRs are transferred to DDTS by LMF MHO. From our perspective they are handled exactly the same way.

• Always specify the complete software version (including CPP) in the comment field. The complete software revision can be retrieved from the MGW@EMC webpage /www.lmc.ericsson.se/~lmcmaab/MGW_LMC.html

• Some CPP loadmodules have a revision that can not be found in MHS. In this case use the latest one available in MHS and in the description specify the actual revision.


MGW Sanity Check


MGW Sanity Check

1) Location Update:

MTP3 Troubleshooting

STEP-1:

Identify which GPB is running the process Scc_ansiServer_proc:$ boards all$ all te s | grep -i Scc_ansiServer_proc

000800: 0002021f Scc_ansiServer_proc check error info interface object

The generated printout will show on which board the process is running (000800 in this example). In case of multiple stacks, make sure the correct one (RPU for Mtp3bSpxxx object) and active one (sma –all) is selected.


MGW Sanity Check (continue..)

STEP-2

To view the MTP3 layer signalling messages, the following trace needs to be enabled:

lhsh 000800 te enable trace3 trace4 Scc_ansiServer_proc

Note: When tracing MTP3 for the ITU standard, there is a UNIX tool to decode the Scc_ituServer_proc trace. This tool can be found in /project/cnicmtl/mgw/tools/tv_sr5_itu. Don’t forget to specify the ‘–cello’ option. There is also a Windows tool to decode MTP3 messages for all standards. It is available in /project/cnicmtl/mgw/tools/MGWdecoder/MgwDecoder.



2) Intra-MGW Call:


GCP

For R4 :lhsh 002500 te enable trace5 stcMbaMtp3biClientC*

For R4 with BC3024 hardware :lhsh 001300 te enable trace5 stcMbaMtp3biClientC*

Or command stc_gcp_buffer on board running STC can be used to log the GCP requests.

Note: You can either pipe the output in ‘gcpdecoder’ if you are using shello, or save the output and use ‘gcpdecoder’ to decode it. In the EMC environment, the gcpdecoder can be found in /project/cnicmtl/mgw/tools/mgw_gcpdecoder.



Q.AAL2 Tracing [only calls using ATM]

To set the trace, use the following command:

lhsh 000600 te enable bus_send bus_receive Ans_aal2ap_proc

Note: Once trace log is taken, MGWDecoder can be used to decode this trace.

For more details see Tracing Cheat Sheet


MGW Sanity Check (continue..)Intra-MGW Call (continue)

Iu Init [only for UE calls]

lhsh 73xx00 te e trace2 trace5 DSP*lhsh 73xx00 te log freeze IuInit 20

where 73xx00 is the only MSB that can process AMR calls. All other MSBs are locked.To see all the MSB boards that process AMR calls, go to EMAS and select Device Pools -> MFDPool. The properties of MFDPool will provide information about all the MSB boards.

See example printout below for both successful/failure scenario:############################################################################# IuInit failure ####[2003-08-04 11:54:29.528] DSP1/40 IuControl_Log.c:108 TRACE5:IuInit failed for ClientResourceId 291

(ServerResourceId 0), UserIndex 0, Error cause: Codec mode problem

#### IuInit success ####[2003-08-04 13:28:01.304] DSP1/40 IuControl_Log.c:86 TRACE2:IuInit successful for ClientResourceId

288 (ServerResourceId 0), UserIndex 0##########################################################################


MGW Sanity Check (continue..)3) Inter-MGW Call:

MTP3 Troubleshooting [Both Originating/Terminating]GCPQ.AAL2 Tracing [only for calls using ATM]Iu Init [only for UE calls]

Nb Init

lhsh 73xx00 te e trace2 trace5 DSP*lhsh 73xx00 te log freeze NbInit 20

where xx is the MSB board where UP is running. All other MSBs are locked.To see all the MSB boards where UP is running, go to EMAS and select Device Pools -> IPBPool[in case of IP backbone] or Device Pools -> MFDPool[in case of ATM backbone]. The properties of IPBPool/MFDPool will provide information about respective MSB boards.


MGW Sanity Check (continue..)4) Intra-MGW Handover [Both Originating/Terminating]:


GCP


Iu Init [Call involving UE only]


MGW Sanity Check (continue..)5) Inter-MGW Handover[Both Originating/Terminating]:


GCP


Iu Init [Call involving UE]

Nb Init

Note: For additional information see Tracing Cheat Sheet

[http://www.lmc.ericsson.se/~lmcmaab/cnicmtl/mgw/share/web/TraceCheatSheet.htm]


Exercises

Date post:	12-Dec-2015
Category:	Documents
Upload:	abhinav-garg
View:	214 times
Download:	0 times

HandsOnTCM_PA2

Documents