Вы находитесь на странице: 1из 300

RNC & NodeB Health Check for NEV 4.

2- How To
Document number:
Document issue:
Document status:
Date:

UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006

Confidential document - Not to be circulated outside Nortel

Copyright 2006 Nortel Networks, All Rights Reserved


Printed in France
NORTEL CONFIDENTIAL
The information contained in this document is the property of Nortel Networks. Except as specifically authorized in
writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential
and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for
evaluation, operation and maintenance purposes only.
The content of this document is provided for information purposes only and is subject to modification. It does not
constitute any representation or warranty from Nortel Networks as to the content or accuracy of the information
contained herein, including but not limited to the suitability and performances of the product or its intended
application.
This is the Way. This is Nortel, Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks. All
other trademarks are the property of their owners.

RNC & NodeB Health Check for NEV 4.2- How To

PUBLICATION HISTORY
19/MAY/2006
Issue 03.01 / EN, STANDARD.
Update of the Document Issue 02.02 to adapt it to the V4.2 version
New HSDPA, ALCAP and RANAP Chapters
OAM Basic checks added

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 2/300

RNC & NodeB Health Check for NEV 4.2- How To

CONTENTS
1 INTRODUCTION.......................................................................................................... 8
2 RNC1500 OVERVIEW ................................................................................................. 9
2.1. Hardware changes.................................................................................................... 9
2.2. OMU and TMU: new PMC (ap) roles, with deterministic assignments.................. 9
2.3. RNCIN object evolution oam OMU addresses................................................... 12
2.4. Central OMU Troubleshooting Tools (COTT) (RNC1500-RNC1000) ................ 14
2.4.1 COTT for RNC1000 ........................................................................................ 14
2.4.1.1 How to launch the tool.............................................................................. 14
2.4.1.2 Main Menu................................................................................................ 14
2.4.1.3 Mib Patch tool sub menu .......................................................................... 15
2.4.1.4 Sm_launcher sub menu ............................................................................. 15
2.4.1.5 Snapshot sub menu ................................................................................... 16
2.4.2 COTT for RNC1500 ........................................................................................ 16
2.4.2.1 How to launch the tool.............................................................................. 16
2.4.2.2 Menus........................................................................................................ 17
2.5. Connection to OMU and TMU .............................................................................. 17
2.5.1 Cott tool ........................................................................................................... 17
2.5.2 Telci connection from the passport:................................................................. 18
2.6. CollectCRLog Tool for RNC1500......................................................................... 19
2.7. File System overview for RNC1500...................................................................... 21
2.7.1 New partitions.................................................................................................. 21
2.7.2 Partitions use................................................................................................... 22
2.7.3 OMU local-share directories............................................................................ 22
2.7.4 Navigation on the File System:........................................................................ 23
2.8. How to retrieve OMU and TMU sessions ............................................................. 25
2.9. MIB directories for RNC1500 ............................................................................... 27
2.9.1. Overview......................................................................................................... 27
2.9.2. MIB proto........................................................................................................ 28
2.9.3. MIB Patch file................................................................................................. 28
3 CONTROL NODE OPERATIONAL STATE.......................................................... 29
3.1. Find out if an OMU is active ................................................................................. 29
3.2. Identify the boards in the CN................................................................................. 30
3.3. Check that the boards software is up to date ........................................................ 31
3.4. Read the manufacturer and applicative data on a Control Node board ................. 32
3.5. Check the Control Node led status......................................................................... 34
3.6. Led status from the Control Node consultation ..................................................... 36
3.7. Check if the boards are started, and PEC codes..................................................... 38
3.8. Get OMU/TMU FT processes status: ftViCpTable ............................................... 39
3.9. Get OMU/TMU/CC1 non FT processes status...................................................... 42
3.10. Find out if spares TMU are present ..................................................................... 45
3.11. OMU-TMU board address according to the Module Absolute Position ............. 45
3.12. File system check................................................................................................. 50
3.12.1. OMU disks status.......................................................................................... 51
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 3/300

RNC & NodeB Health Check for NEV 4.2- How To

3.12.2. Shared MMS mirroring check up ................................................................. 52


3.12.3. MMS integrity check (number of bad sectors) ............................................. 53
3.13. MIB Verification.................................................................................................. 54
3.13.1. Confirmation that the MIB is built................................................................ 54
3.13.2. Mib customization ........................................................................................ 57
3.14. RNC1000 RNC1500 : telci commands changed .............................................. 59
3.15 ATM check-up on CC1 and TM boards ............................................................... 59
3.15.1. S/UNI state.................................................................................................... 60
3.15.2. ATM planes state .......................................................................................... 60
3.15.2.1. CC1 verifications ................................................................................... 60
3.15.2.2. Verifications of the plane on TM (OMU/TMU) boards ....................... 61
4 INTERFACE NODE OPERATIONAL STATE ...................................................... 63
4.1. Control and Function processors LEDs ................................................................. 63
4.2. Ensure I-Node startup is successful ....................................................................... 63
4.3. File System check up for RNC1500 ...................................................................... 64
4.4. Determine if Base OS has completed initialization ............................................... 64
4.5. Determine if the applications have completed initialization.................................. 65
4.6. Determine if ATM connectivity is available ......................................................... 66
4.7. Determine if the AAL2 ATM Interface is available.............................................. 69
4.8. Determine if the atmmpe layer is available. .......................................................... 71
4.9. Check PMC-M fully redundant ............................................................................. 71
4.9.1 How to find the PMC Master and serving ....................................................... 71
4.9.2 Connection to a PMC....................................................................................... 73
4.9.3 CID use redundancy......................................................................................... 73
5 NODEB ......................................................................................................................... 78
5.1. How to connect and navigate on a NodeB............................................................. 78
5.2. HW, SW and radio check....................................................................................... 79
5.3. Check that the BTS is radiating and the common channels SCCPCH (PCH, FACH)
are up and running. ....................................................................................................... 81
5.4. Iub status ................................................................................................................ 82
5.5. iBTS alarm history check....................................................................................... 82
5.6. Activ FFS ............................................................................................................... 83
5.7. iBTS active SW version......................................................................................... 84
5.8. iBTS built? Configuration file ............................................................................... 85
5.9. iBTS Commissionning Data Check ....................................................................... 86
5.10. iBTS Config Data (DLU file) check.................................................................... 88
5.11. To retrieve VCC for OAM, NCP, CCP , DS and NDS ....................................... 93
5.12. CS & PS Call check ............................................................................................. 93
5.13. Connection to other boards .................................................................................. 96
5.14. PCM & SYNCHRO check................................................................................... 96
6 OAM BASIC CHECKS............................................................................................. 102
6.1 Check status of all groups ..................................................................................... 102
6.2 Check status of specific group .............................................................................. 102
6.3 Restart one application in the group ..................................................................... 103
6.4 Restart one group .................................................................................................. 103
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 4/300

RNC & NodeB Health Check for NEV 4.2- How To

6.5 Restart all groups .................................................................................................. 104


6.6 SMC alarms check ................................................................................................ 105
7 HOW TO................................................................................................................. 108
7.1. How To Wicl.................................................................................................... 108
7.2. How To retrieve the IP address of the nodes ................................................... 110
7.2.1. Control Node Addresses ............................................................................... 110
7.2.2. Interface Node addresses .............................................................................. 110
7.3. CallTrace AccessSession creation for an IMSI through WICL (OMC V5.0) ..... 110
7.3.1. Creation at the OMC..................................................................................... 111
7.3.2. Calltrace creation check on the RNC............................................................ 113
7.3.3. Deletion at the OMC..................................................................................... 115
7.3.4. Calltrace storage............................................................................................ 116
7.4. To retrieve NodeB and Cell information ............................................................. 117
7.5. OAM-RNC link check up. ................................................................................... 124
7.5.1. Control from the Control Node..................................................................... 124
7.5.2. Control from the IN / AN.............................................................................. 125
7.5.3. Verification on the OMC side....................................................................... 125
7.6. Consistency of the SW between RNC and OAM ................................................ 127
7.6.1 RNC Delivery Naming .................................................................................. 127
7.6.1.1. Versions and Deliveries correspondence ............................................... 127
7.6.1.2. RNC delivery naming convention ......................................................... 128
7.6.1.3. Finding the SRS descriptions on the OMC............................................ 129
7.6.2 OMC Versions ............................................................................................... 130
7.6.2.1. Control Node SW from the OMC point of view.................................... 130
7.6.2.2. Interface Node SW from the OMC point of view.................................. 131
7.6.3 CN / IN versions ........................................................................................... 133
7.6.3.1. Control Node SW - OMU check............................................................ 133
7.6.3.2. Interface Node SW - CP check .............................................................. 133
7.7. Check CN-IN link ................................................................................................ 135
7.8. Call check............................................................................................................. 153
7.8.1. RDT Ressource Debug Toolkit..................................................................... 153
7.8.2. TMU.............................................................................................................. 157
7.8.3. RBSet & AsConf Id ...................................................................................... 170
7.8.4. Establishment cause (REC 25.331 R99)....................................................... 172
7.9. IN Counters on User Plane .................................................................................. 173
7.10. IU/IUR links check ............................................................................................ 179
7.11. OMU and TMU VCC info................................................................................. 189
7.12. How To debug SS7 on the RNC-Interface Node........................................... 190
7.13. Observations storage.......................................................................................... 190
7.14. HSDPA How To ........................................................................................... 195
7.14.1. Principle ...................................................................................................... 195
7.14.2. How to .. Check configuration.................................................................... 195
7.14.2.1 Basic configuration ................................................................................... 195
7.14.3. How to .. Check and Troubleshoot HSDPA services on the RNC ............. 200
7.14.4. How to .. Check and Troubleshoot HSDPA services on the BTS .............. 209
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 5/300

RNC & NodeB Health Check for NEV 4.2- How To

7.15. ALCAP/RANAP How To ............................................................................. 220


7.15.1. How to .. Check and Troubleshoot ALCAP services ................................. 220
7.15.2. How to .. Check and Troubleshoot RANAP services................................. 227
8 TOOLS........................................................................................................................ 231
8.1. UMTS Log Collection Engine ............................................................................. 231
8.1.1. Documentation/tool....................................................................................... 231
8.1.2. Purpose.......................................................................................................... 231
8.1.3. Quick start..................................................................................................... 231
8.1.4. Screenshots of OAM V4.x............................................................................ 232
8.1.5. Screenshots For OAM V5.x.......................................................................... 233
8.2. RNC traffic check and cell diagnose tool ............................................................ 235
8.2.1. Documentation.............................................................................................. 235
8.2.2. Tools and logs location .............................................................................. 235
8.2.3. Overview of RNC Traffic Check.................................................................. 235
8.2.3.1 Purpose.................................................................................................... 235
8.2.3.2 How to launch the tool Example.......................................................... 236
8.2.4. Overview of Cell Diagnose........................................................................... 240
8.2.4.1. Purpose................................................................................................... 240
8.2.4.2 How to launch the tool Example.......................................................... 240
8.3. WinRNCSpy (IpSpy, AtmSpy)............................................................................ 249
8.3.1. Documentation/Tool ..................................................................................... 249
8.3.2. AtmSpy overview ......................................................................................... 249
8.3.2.1. Tool presentation ................................................................................... 249
8.3.2.2. Passport configuration ........................................................................... 250
8.3.2.3. Definition of the Vcc Capture settings................................................... 250
8.3.2.4. Capture mode ......................................................................................... 251
8.3.2.5. Ftp mode ................................................................................................ 254
8.3.2.6. Convert mode (optional) ........................................................................ 255
8.3.2.7. Decode mode ......................................................................................... 256
8.3.2.8. Manual launch........................................................................................ 257
8.3.3.. Overview of IPSpy....................................................................................... 258
8.3.3.1. Usage...................................................................................................... 258
8.3.3.2. Manual commands ................................................................................. 265
8.4. CTBL ................................................................................................................... 266
8.4.1 CTBL traces through CallTrace wizard......................................................... 266
8.4.2. Manual CTBL traces on a cell. ..................................................................... 266
8.4.2.1. How to retrieve a cell tracekey .............................................................. 266
8.4.2.2. CTBL traces setup on a cell. .................................................................. 269
8.4.2.3. Traces collection .................................................................................... 270
8.4.2.4. Traces decoding ..................................................................................... 270
8.5. Cott....................................................................................................................... 271
9 ANNEXE A : RNC 1500 COMMANDS .................................................................. 272

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 6/300

RNC & NodeB Health Check for NEV 4.2- How To

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 7/300

RNC & NodeB Health Check for NEV 4.2- How To

1 INTRODUCTION
OBJECT/ SCOPE OF THIS DOCUMENT
Basic health checks on RNC1000/ RNC1500/ iBTS /OAM equipments.
Applicable to versions UA V4.2
AUDIENCE FOR THIS DOCUMENT
GPS, TAS, ER and other operational teams
CONVENTIONS
The commands to type are in bold and blue.
The results to take care of are in red.
The commands preceded by:
CLASSIC

apply for RNC1000.


The commands preceded by:
COMPACT

apply for RNC1500.


As the commands only may differ, refer to the classic part for more
detailed explainations of the expected results.
Commands impact:
Control Node commands are unsafe on TMU and ci_mgr, they
can be very impacting on a loaded RNC if misused.
Passports displays are safe but connections on PMC for unsafe
commands have to be carefully used.
iBTS commands provided are not disruptive (except for III 8.)

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 8/300

RNC & NodeB Health Check for NEV 4.2- How To

2 RNC1500 OVERVIEW
Purpose: short presentation of the RNC1500.
2.1. Hardware changes
The RNC 1500 consists only in one shelf.
The INode shelf will now concentrate both INode and CNode applications.
Modifications performed:
9 Removal of the C-Node HW (CC1, TMU-R, OMU, MMS) from the RNC
platform.
9 Porting of TMU s/w to the PSFP
9 Porting of OMU s/w to the PSFP, with some s/w adaptation due to CP3 Disk.
9 Use of a single 20 Gbyte disk for file management
A previous RNC1000 dual-shelf may contain now two PP 15K shelves (i.e. two
RNC1500).
2.2. OMU and TMU: new PMC (ap) roles, with deterministic assignments.
The OMU and TMU are now only logical entities spread over the PMC.
PMC-M (master), RAB (radio access bearer), PC (protocol converter) and NI (in charge
of ss7 stacks) already running on the PMC are now completed by OMU and TMU AP.
Below an example truncated:

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 9/300

RNC & NodeB Health Check for NEV 4.2- How To

11> d lp/* ap/* rnc processorRole


Lp/* Ap/* RncAp
+==+==+-------+---------------------------------------|Lp|Ap| role |Response
+==+==+-------+---------------------------------------| 2| 0|aMaste |
| 2| 1|tmu
|
| 2| 2|rab
|
| 2| 3|rab
|
| 2| 4|pc
|
| 2| 5|rab
|
| 3| 0|sMaste |
| 3| 1|tmu
|
| 3| 2|rab
|
| 3| 3|rab
|
| 3| 4|pc
|
| 3| 5|rab
|
| 4| 0|rab
|
| 4| 1|tmu
|
| 4| 2|aNi
|
| 4| 3|rab
|
| 4| 4|pc
|
| 4| 5|aOmu
|
| 5| 0|rab
|
| 5| 1|tmu
|
| 5| 2|sNi
|
| 5| 3|rab
|
| 5| 4|pc
|
| 5| 5|sOmu
|
ok
2006-05-11 13:51:42.42

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 10/300

RNC & NodeB Health Check for NEV 4.2- How To

The repartition of OMU/TMU across the PSFP is deterministic.


The same pattern is always used, according to the number of PSFP.
AP role and repartitions according to the number of PSFP
1 PSFP
1 PSFP

AP0

Slot 2 (10) PMCM

AP1

AP2

AP3

AP4

AP5

TMU

NI

RAB

PC

OMU

2 PSFP
2 PSFP

AP0

AP1

AP2

AP3

AP4

AP5

Slot 2 (10) PMCM

TMU

NI

RAB

PC

OMU

Slot 3 (11) PMCM

TMU

NI

RAB

PC

OMU

3 PSFP
3 PSFP

AP0

AP1

AP2

AP3

AP4

AP5

Slot 2 (10) PMCM

TMU

RAB

RAB

PC

RAB

Slot 3 (11) PMCM

TMU

NI

RAB

PC

OMU

Slot 4 (12) RAB

TMU

NI

RAB

PC

OMU

From 4 to 12 PSFP
slot Card type
0
0
CP
1
CP
2
PSFP PMC-M
3
PSFP PMC-M
4
PSFP
RAB
5
PSFP
RAB
6
PSFP
RAB
7
PSFP
RAB
8
OC3
9
OC3
10
PSFP
RAB
11
PSFP
RAB
12
PSFP
RAB
13
PSFP
RAB
14
PSFP
RAB
15
PSFP
RAB

TMU
TMU
TMU
TMU
TMU
TMU

RAB
RAB
NI
NI
RAB
RAB

RAB
RAB
RAB
RAB
RAB
RAB

PC
PC
PC
PC
PC
PC

RAB
RAB
OMU
OMU
RAB
RAB

TMU
TMU
TMU
TMU
TMU
TMU

RAB
RAB
RAB
RAB
RAB
RAB

RAB
RAB
RAB
RAB
RAB
RAB

PC
PC
PC
PC
PC
PC

RAB
RAB
TMU
TMU
RAB
RAB

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 11/300

RNC & NodeB Health Check for NEV 4.2- How To

2.3. RNCIN object evolution oam OMU addresses


d p rncin
Perform this command on passport shelf to determine:
the IP addresses provisioned for the OMU
the mode of the passport shelf.
The mode must be rnc for an RNC1500 (inode for RNC1000).
21> d -p rncIn
RncIn
primaryOmuIpAddress = 0.0.0.0
secondaryOmuIpAddress = 0.0.0.0
oamPrimaryOmuIpAddress = 47.164.76.82
oamSecondaryOmuIpAddress = 47.164.76.83
oamOmcIpAddresses
= 47.164.77.116
rncInfo
= ""
protocolConverterResources = 17 %
mode
= rnc
ok
2005-07-20 18:02:13.40

OMU EXTERNAL ADDRESS


OMU EXTERNAL ADDRESS
OMC SERVER ADDRESS

The oamxxxOmuIpAddresses are a mandatory for the link between the RNC and the
OMC server.
If these addresses are badly defined, no oam operation (such as build, upgrades,) is
possible.
They must be the same on the RNC and the OMC.
To check their definition on the OMC server, use wicl.
In our case, the RNC is RNC_1209.
saba:/home/nortel <113> (nortel) % /opt/nortel/shell/wicl/wiclsh
--------------------------------------------------------Starting Wireless Internet Command Language
--------------------------------------------------------Command mode launched
login : nortel
password : nortel
....wait please
Wireless Internet Command Language (WICL)
>: utran list rnc
{RNC RNC333} {RNC RNC00} {RNC RNC_1210} {RNC RNC_1209} {RNC RNC_1202} {RNC
RNC_1205} {RNC RNC_1206} {RNC RNC1407} {RNC RNC_1201}
>: RNC RNC_1209 list children
CallTrace CsCoreNetworkAccess GSMNeighbour LocationServices MtpSignPoint
NeighbouringRNC NodeB ObjectTrace PerfScanner PsCoreNetworkAccess RNCEquipment
RadioAccessService RncMIB RouteSet SasAccess
>: RNC RNC_1209 list RNCEquipment
{RNC RNC_1209 RNCEquipment 0}

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 12/300

RNC & NodeB Health Check for NEV 4.2- How To

>: RNC RNC_1209 RNCEquipment 0 list children


ANode CNode INode
>: RNC RNC_1209 RNCEquipment 0 list CNode
{RNC RNC_1209 RNCEquipment 0 CNode 0}
>: RNC RNC_1209 RNCEquipment 0 CNode 0 dis
activeIPAddress
47.164.76.82
availabilityStatus
{ }
class
CNode
dn
(RNC,259)(RNCEquipment,0)(CNode,0)
ipAddress
47.164.76.82
mibSynchronization
on
neId
47.164.76.82
operationalState
enabled
operatorId
0
passiveSystemRelease
04_02_00
secondaryIPAddress
47.164.76.83
siteName
Site/SITE_RNC_1209
systemRelease
04_02_00
unknownStatus
unknownstatusfalse
upgradeStatus
IDLE
userSpecificInfo
NONE

You may also ping the OMC from the RNC to check the link RNC OMC.
85> ping -ip(47.164.77.116) vr/0 ip icmp
Vr/0 Ip Icmp
IpPing: Rx reply of 64 bytes from 47.164.77.116: icmpSeq=2, time=2ms
ok
2005-08-03 12:04:29.02

vr/0 was used because the protocol port OAMENET0 is under this virtual router:
83> d vr/* pp/*
Vr/* Pp/*
Use -noTabular to see hidden attributes: atmAddress.
+================+====================+------+-----+----+-----+----|
Vr
|
Pp
|snmpOp|osiAd|osiO|osiUs|ifInd
|
|
|erStat| min |per | age | ex
|
|
| us |
|
|
|
+================+====================+------+-----+----+-----+----|0
|NODEBSOAM0
|up
|unlck|ena |activ|
3
|0
|OAMENET0
|up
|unlck|ena |activ|
7
[]
ok
2005-08-03 12:04:01.61

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 13/300

RNC & NodeB Health Check for NEV 4.2- How To

2.4. Central OMU Troubleshooting Tools (COTT) (RNC1500-RNC1000)


COTT is a tool running on the OMU for RNC1000 and on the OMC Main Server for
RNC1500.
It gathers the following troubleshooting tools and commands:
getCellInfo
collectCRLog
MIB patch tool
Core Process table display
IN_Access table display
OMU state
Messaging full mesh, LWG, routing table
List of process launched by SM launcher
Access to Telci commands (RNC1500 only)
CNode Snapshot (RNC1000 only)

2.4.1 COTT for RNC1000


2.4.1.1 How to launch the tool
Open a telnet session on the active OMU (some tools are only available on the active
omu) and enter cott.
2.4.1.2 Main Menu
===================================================
Central OMU Troubleshooting Tools
===================================================
Please select the following tools:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
L.
Q.

collectCRlog
IN_Acc_List_All_Tables
ftViCpTable
getCellInfo
mib_patch_tool
sm_launcher
snapshot
msgViLwgTable
msgViFullMeshTbl
msgViRoutingTable
msgViOmuState
Enable log.
Quit menu.

Your choice:

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 14/300

RNC & NodeB Health Check for NEV 4.2- How To

Note
All the results can be logged on the OMU under the /tmp/COTTlog directory
except for collectCRlog (under /tmp)
The IN_Acc_List_All_Tables command result will be logged in the blogio.tmp
file.
2.4.1.3 Mib Patch tool sub menu
Be careful to type the MIB path before: MIB=/OMU/share/rw_data/MibRunning/DB_TEST.do
===================================================
MIB Patch Tool (mib_patch_tool.exe)
Note; to use running MIB, type;
MIB=/OMU/share/rw_data/MibRunning/DB_TEST.do
MIB=
(Type MIB=Value to set value)
format=
(Type format=Value to set value)
===================================================
Please select the following options:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
H.
L.
Q.

Read field(s)
Write fields(s)
Display field(s) type
Display field(s) range
Display field(s) size
Display field(s) offset
List the MIB tables
Compare MIB with Reference MIB
Show patch information stored in the MIB
Remove the patch information stored in the MIB.
Validate the MIB to check for corruption.
Help.
Disable log.
Quit menu.

Your choice:

2.4.1.4 Sm_launcher sub menu


SM Launcher
===========
Operating on local board: [Platform: CONTROL NODE; Instance: 0; Sub equip.: SBC;
Shelf: 1; Slot: 9]
Command
------create
modify
delete
get_create_data
ps
pgs

Description
----------Create a process group
Modify a process group
Delete a process group
Get process group create data
Process status
Process group status
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 15/300

RNC & NodeB Health Check for NEV 4.2- How To


bs
board
board-shutdown
oam-shutdown
quit

Board status
Set board position
Board shutdown
OAM shutdown
Quit

Command:

Note
In case no board position is previously set, it will automatically display the
processes associated with the current board (active OMU)
To display processes on a specific board, set the board position first and choose
the ps command
2.4.1.5 Snapshot sub menu
===================================================
Emergency Recovery Procedure Tools
===================================================

Please select the following procedures:


1.
2.
3.
4.
L.
Q.

Save the CNode software & the CNode configuration


Save the CNode configuration
Restore the CNode software and config
Restore the CNode config
Disable log.
Quit menu.

Your choice:

2.4.2 COTT for RNC1500


2.4.2.1 How to launch the tool
COTT has to be launched from the OMC server.
The tool is delivered as a part of the RNC load (under the passport cnp software).
Each time a new RNC SRS is downloaded on the OMC server, COTT is automatically
installed under:
/opt/nortel/data/srs/DELIVERY/PASSPORT/software/cnp/<RI42xxxxxxxxx>/external

with RI41xxxxxxxxx, the software name of the RNC1500.


To launch the tool :
./cott c <CP_IP_ADDRESS>

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 16/300

RNC & NodeB Health Check for NEV 4.2- How To

The login and password are those used for a telnet on the CP.
Logging Path: all the results can be logged on the OAM server under the /tmp/COTT
directory (example: log Dir: /tmp/COTT/47_164_52_232_20060516T092354).
The logging is activated/deactivated by the choice L: Enable log / Disable log.
Example for a RI42111061220 load:
bernard:/home/nortel <114> (nortel) % cd
/opt/nortel/data/srs/DELIVERY/PASSPORT/software/cnp/RI42111061220/external/
bernard:/opt/nortel/data/srs/DELIVERY/PASSPORT/software/cnp/RI42111061220/exter
nal <115> (nortel) % ./cott -c 47.164.52.232
Which OMU do you want to logon(0-act/1-sby):0
login name: debug
login used to connect onto the CP
debug's password: debug
=========================================================
Central OMU Troubleshooting Tools
=========================================================
Please select the following tools:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
L.
T.
Q.

Collect CR Log
INACC_CA display_dd_ctx
cpTable
getCellInfo
mib
sm launcher
msg lwg
msg fullmesh
INACC_LA inacc_disp_table_ctx
msg omu
Enable log
telnet CI
Quit menu

Your choice:

2.4.2.2 Menus
The choices are the same as for RNC1000, except for certain commands naming,
slightly different.
Note: the getCellInfo command will provide a different output when running from the
COTT menu (see chapter 7.4 for details)
2.5. Connection to OMU and TMU

2.5.1 Cott tool


The Cott Tool allows a direct connection on the active OMU (T. telnet CI)
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 17/300

RNC & NodeB Health Check for NEV 4.2- How To

2.5.2 Telci connection from the passport:


Towards a RAB:
telci rab(instance) rnc
Towards a PMC-NI:
telci pmcni(instance) rnc
Towards a PMC:
telci pmcm(instance) rnc
Towards a TMU:
telci tmu(instance) rnc
Towards an OMU
telci omu(instance) rnc

instance=x
instance=0,1
instance=0,1
instance=0.1
instance=0,1

To leave the connection menu, enter Q.


To link an instance and its lp ap numbers display the attributes instances and roles of lp
ap rnc objects:
3> d lp/* ap/* rnc role,instance
Lp/* Ap/* RncAp
+==+==+-------+----------+---------------------------------------|Lp|Ap| role | instance |Response
+==+==+-------+----------+---------------------------------------| 2| 0|aMaste |
0|
| 2| 1|tmu
|
0|
| 2| 2|rab
|
0|
| 2| 3|rab
|
1|
| 2| 4|pc
|
0|
| 2| 5|rab
|
2|
| 3| 0|sMaste |
1|
| 3| 1|tmu
|
1|
| 3| 2|rab
|
3|
| 3| 3|rab
|
4|
| 3| 4|pc
|
1|
| 3| 5|rab
|
5|
| 4| 0|rab
|
6|
| 4| 1|tmu
|
2|
| 4| 2|aNi
|
0|
| 4| 3|rab
|
7|
| 4| 4|pc
|
2|
| 4| 5|aOmu
|
0|
| 5| 0|rab
|
8|
| 5| 1|tmu
|
3|
| 5| 2|sNi
|
1|
| 5| 3|rab
|
9|
| 5| 4|pc
|
3|
| 5| 5|sOmu
|
1|
ok
2006-05-11 14:01:21.90

In this example, the active OMU is lp/4 ap/5, with the instance 0.
To connect it, use telci and then type enter to display the menus (result truncated below),

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 18/300

RNC & NodeB Health Check for NEV 4.2- How To


5> telci -omu(0) rnc
Trying 127.1.4.7...
Connected to 127.1.4.7.
Escape character is '^]'
Telnet CI commands:
Q - quit telci
G - redirect global output.
telci(omu)>

2.6. CollectCRLog Tool for RNC1500


The Collect CR Log tool is the first option offered by COTT.
The files collected are tarred and zipped in a single archive on the OMC server under the
directory
/tmp/COTT
Example for a collect beginning the 10th of May 2006:
=========================================================
Central OMU Troubleshooting Tools
=========================================================
Please select the following tools:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
L.
T.
Q.

Collect CR Log
INACC_CA display_dd_ctx
cpTable
getCellInfo
mib
sm launcher
msg lwg
msg fullmesh
INACC_LA inacc_disp_table_ctx
msg omu
Enable log
telnet CI
Quit menu

Your choice: 1

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 19/300

RNC & NodeB Health Check for NEV 4.2- How To

From which date do you want collect log (YYYYMMDD): 20060510


Please enter command file (optional):
___________________________________________________________
___________________________________________________________
%
COLLECT CR LOG SCRIPT FOR RNC1500
%
%
Script started.
%
%
Please be patient, as the script might
%
take several minutes to run to completion.
%
%__________________________________________________________
Creating temporary directory structure...
Getting info from RNC via TELNET session...
[]
Bundling files...
Deleting temporary directory structure...
___________________________________________________________
%
SCRIPT RUN TO COMPLETION
%
%
Start time T155722
%
End
time T161003
%
Size before bundling: 476016 Kb
%
Output directory: /tmp/COTT/47_164_52_232_20060511T155647
%
Output filename: collectCRlog_47_164_52_232_20060510.tar.gz
%__________________________________________________________
%__________________________________________________________

The following files are retrieved:


Content of the sessions for OMU 0 and 1 stored under:
/CP0/OMU0/local/log/bos/sc/<date>
/CP1/OMU0/local/log/bos/sc/<date>

/CP0/OMU1/local/log/bos/sc/<date>
/CP1/OMU1/local/log/bos/sc/<date>
TMU trace files:
/CP0/TMU/local/log/bos/sc/<date>
/CP1/TMU/local/log/bos/sc/<date>
Fault files:
/sfs2/share/fault/<date>
Histo files
/sfs2/share/log/historisation/*SBC.hst
INode alarms:
/spooled/closed/alarm/<date>
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 20/300

RNC & NodeB Health Check for NEV 4.2- How To

INode Field traces:


/spooled/closed/debug/<date>
INode postmortem:
/spooled/closed/appl/cdcsLp*/*<date>*
The textual results of the following commands run on CP and OMU:
o d -p vr /* on CP
o d lp/* ap/* r on CP (roles and location of PMCs)
o d sw avl on CP (software version)
o d sw patchlist on CP (patchlist)
o d fs part/* on CP (disk size and usage)
o d lp/0 on CP (uptime)
o msg omu on OMU0/1 (Is omu simplex/duplex active/passive)
o msg fullmesh on OMU0/1 (list all tcp connections with the boards)
o cpTable on OMU0/1 (list all the call processes)
o os2 routeShow on OMU0/1 (display host and network routing tables)
Textual results of any additional commands specified in a given command file.

2.7. File System overview for RNC1500

2.7.1 New partitions


Compared to an Inode for RNC1000, two new partitions are added.
12> list fs part/*
Fs Part/0
Fs Part/1
Fs Part/2
ok
2005-08-08 15:28:11.55
13> list fs disk/*
Fs Disk/0
Fs Disk/1
ok
2005-08-08 15:28:16.17
11> d fs part/*
Fs Part/*
+====+----------+----------+-----+------+-----+----+----|Part| capacity |freeSpace |usage| mode |osiAd|osiO|osiUs
|
|
Gbyte|
Gbyte|
%|
| min |per | age
+====+----------+----------+-----+------+-----+----+----|
0| 4.294770| 1.122697|
73|shadow|unlck|ena |activ
|
1| 7.837175| 7.407804|
5|shadow|unlck|ena |activ
|
2| 7.837175| 7.386066|
5|notSha|unlck|ena |activ
ok
2005-08-08 15:08:21.55

The first disk partition is untouched for backward compatibility.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 21/300

RNC & NodeB Health Check for NEV 4.2- How To

These partitions are spread over the two disks of each CP:
29> d fs disk/* part/*
Fs Disk/* Part/*
+====+====+----------+----------+----------+-----+----+----|Disk|Part| capacity |freeSpace |badBlocksP|osiAd|osiO|osiUs
|
|
|
Gbyte|
Gbyte|ercentage | min |per | age
|
|
|
|
|
%|
|
|
+====+====+----------+----------+----------+-----+----+----|
0|
0| 4.294770| 1.122697|
0|unlck|ena |activ
|
0|
1| 7.837175| 7.408001|
0|unlck|ena |activ
|
0|
2| 7.837175| 7.371448|
0|unlck|ena |activ
|
1|
0| 4.294770| 1.122697|
0|unlck|ena |activ
|
1|
1| 7.837175| 7.407804|
0|unlck|ena |activ
|
1|
2| 7.837175| 7.385219|
0|unlck|ena |activ
ok
2005-08-08 15:36:32.28

2.7.2 Partitions use


Partition

Size (GB)
4

Known as
/sfs
(shadowed)

Use
Passport system use download, provisioning, DCS. All
the DCS logs like alarms, debug etc are located under
/sfs.

/local

Active CPs view of the disk.

/remote

Standby CPs view of the disk.

/sfs/sfs2
(shadowed)

New shadowed partition for use by compact. Including


logs for calltrace, counters, fault, and historization are
located under this directory.

/local2

Active CPs view of the above.

/remote2

Standby CPs view of the above.

/sfs/CP0

New non-shadowed partition on the CP in slot 0 for


Compact use.
New non-shadowed partition on the CP in slot 1 for
Compact use.

/sfs/CP1

2.7.3 OMU local-share directories


sfs2 is chiefly dedicated to the mib and the files shared by the OMUs (/OMU/share from
a classical OMU prospective).
The partition 2 is dedicated to the OMU and TMU (previously /OMU/local/)
/CPx/OMU0/
/CPx/OMU1/
/CPx/TMU/
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 22/300

RNC & NodeB Health Check for NEV 4.2- How To

Cp view

External view

OMU0 view OMU1 view

/sfs2/share

/OMU/share

/OMU/share

/sfs/CP0/OMU0/local

/CP0/OMU0/local

/OMU/local

----------------

/sfs/CP0/OMU1/local

/CP0/OMU1/local

---------------- /OMU/local

/sfs2/share

/OMU/share

/OMU/share

/sfs/CP1/OMU0/local

/CP1/OMU0/local

/OMU/local

----------------

/sfs/CP1/OMU1/local

/CP1/OMU1/local

---------------- /OMU/local

CP0 /sfs/sfs2/share

CP1 /sfs/sfs2/share

2.7.4 Navigation on the File System:


ls fs
cd path(path) fs
pwd fs

lists the files


to change the directory
Path of the working dir.

Example:
67> cd -path("/sfs2/share") fs
Fs
ok
2005-08-05 14:43:56.17
68> ls fs
Fs
Type Prot
dir no
dir no
dir no
dir no
dir no
dir no
dir no
ok
69> pwd fs
Fs
/share
ok

Size
Date
Time
0
2001-06-14 02:59:40
0
1980-01-01 00:00:00
0
2001-06-14 02:59:40
0
2001-09-02 01:23:42
0
2001-09-02 01:23:42
0
2001-09-02 01:23:42
0
2001-09-02 01:23:44
2005-08-05 14:44:00.51

Name
.
..
rw_data
config
fault
log
usr

2005-08-05 14:44:03.25

70> cd -path("/") fs
Fs
ok
2005-08-05 14:48:12.41

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 23/300

RNC & NodeB Health Check for NEV 4.2- How To


71> ls fs
Fs
Type Prot
dir no
dir no
dir no
dir no
dir no
dir no
dir no
ok

Size
Date
Time
0
1980-01-01 00:00:00
0
1980-01-01 00:00:00
0
1980-01-01 00:00:00
0
1980-01-01 00:00:00
0
1980-01-01 00:00:00
0
1980-01-01 00:00:00
0
2001-06-14 02:59:40
2005-08-05 14:48:15.90

Name
tmp
bvw
provisioning
system
spooled
software
debugTrace

It is much easier to use a client for ftp browsing.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 24/300

RNC & NodeB Health Check for NEV 4.2- How To

2.8. How to retrieve OMU and TMU sessions


To retrieve the logs of the active OMU and the TMU
1. Determine the active CP (os pcsShowCards) => CPi with i = 0 or 1
2. Determine the instance of the active omu (d lp/* ap/* rnc role,instance) =>
OMUj
j = 0 or 1
3. Open an FTP connection onto the CP, the paths are
/CPi/OMUj/local/log/bos/sc
/CPi/TMU/local/log/bos/sc
Example:
10> d lp/* ap/* rnc role,instance
Lp/* Ap/* RncAp
+==+==+-------+----------+---------------------------------------|Lp|Ap| role | instance |Response
+==+==+-------+----------+---------------------------------------[]
| 5| 5|aOmu
|
1|
[]

11> os pcsShowCards
CARD
---0
1
[]

TYPE
---------CPeE
CPeE

FSM STATE
----------------RunningAsStandby
RunningAsActive

VISIBILITY
---------OnLine
OnLine

LP
-0
0

INSTANCE
-------Standby
Active

The instance of the active OMU is 1, the CP 1 is active, the log files for the active OMU
and for the TMU must be retrieved under:
/CP1/OMU1/local/log/bos/sc
/CP1/TMU/local/log/bos/sc
The files can be viewed using the Passport Text viewer:
How to use it:
1) Log onto CP
2) Enter OS unsafe mode, change to the directory where the file exists and list the file
name
3) Launch the tool
16> os
Debug tracing directed to this OS shell.
<Welcome to DebugShell:VxWorks Version 5.3.1>
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 25/300

RNC & NodeB Health Check for NEV 4.2- How To

WARNING: Commands available at this interface may be service


impacting. This interface is for debugging only.
Do not proceed without proper authority and training.
Do you wish to proceed? [Yes/No]: yes
OS>
OS> set unsafe
WARNING: Entering unsafe mode. Commands available from this interface are not
supported for field use without specific direction from Nortel
Networks.
OS>
OS> set promote
OS>
OS> cd /sfs/CPi/OMUj/local/log/bos/sc
OS> pwd
/sfs/CP0/OMU1/local/log/bos/sc
OS>
OS> ls
.
..
blogOMU1.20060511T170251.ini
CmdServer_1.log
blogOMU1.01.trc
blogOMU1.20060512T015332.tmp
OS> tv blogOMU1.20060511T170251.ini
------------------------------------------------------------------------------11/05/2006 17:01:22.107 num:00000000 vxw_io_driver.cc.708 [0xff3f000]
tCnStarte
r @ OMU_1(Lp/5,Ap/5) (PERM): STDOUT/SRDERR traces
"cn_start_bos: vxw_io_initialize -> OK
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
C-Node software Startup Info for OMU_1(Lp/5,Ap/5):
Cn software Start Time = 2006-05-11 17:01:18.72320000
Cn Started after 17080 ticks (ms) since PMC reset
Environment variables used to configure BaseOS and cNode App:
(global environment)
0: BTHD_MAX_NUMBER_OF_THREADS=200
1: BTHD_MAX_NUMBER_OF_KEYS=50
2: DYM_MAX_NUMBER_OF_PARTITIONS=40
3: TRANSIENT_MEM_ENGINEERING=3
4: MP_BSEM_MAX_NUMBER_OF_SEMAPHORES=120
5: MTX_MAX_NUMBER_OF_MUTEXES=130
6: BJOB_MAX_NUMBER_OF_QUEUES=10
7: MP_VAR_SEGMENT_SIZE=8192
8: DLY_MAX_NUMBER_OF_DELAYS=5000
9: OSIROOT=/Osiroot
10: OSIPIPE=/Osipipe
11: APPTR_VERSION=2
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
[]

.
4) Use 1 mode if required

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 26/300

RNC & NodeB Health Check for NEV 4.2- How To

View commands:
Command
Ctrl-f<enter>
Ctrl-b<enter>
k<enter>
j<enter>
/str<enter>
/<enter>
?str<enter>
?<enter>
:0<enter>
G<enter>
h<enter>
<enter>
q<enter>

Operation
Page Down
Page up
Scroll Up
Scroll down
Forward Search
Next forward Search
Backward Search
Next backward Search
Top of the file
Bottom of the file
Display help information
Refresh current screen
Quit

Note:
Search command does not support pattern search
During tv active session, alarm messages may insert into the tv screen output.
User could use <enter> key to refresh the current page. If alarms are too
disruptive, user could use the CAS command to restrain alarm by issuing the
following command:
To find your telnet session
d nmis tel sess/*
d nmis local sess/*
To restrain alarm for session 2:
set nmis tel sess/2 data ~alarm
set nmis local sess/2 data ~alarm
2.9. MIB directories for RNC1500

2.9.1. Overview
2 directories are dedicated to the MIB in the new mounting point sfs2:
/sfs2/share/rw_data/Mib1
/sfs2/share/rw_data/Mib2
One contains the running MIB, whilst the second is used for the new MIB built online or
during upgrades with changes.
The file /sfs2/share/rw_data/mibDirLinks.txt assigns the role of each directory:
its first line defines the MibRunning
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 27/300

RNC & NodeB Health Check for NEV 4.2- How To

its second line, the MibNew

Each MIB directory contains, like for the classic:


DB_TEST.do
the MIB itself
SAVE_DB_TEST.do backup in case of write failure on DB_TEST.do
mibNominal.txt
points out the sane MIB file.

2.9.2. MIB proto


Directory :
/sfs/software/cRNCApc/obj/ppc/
The proto MIB is compressed
Example :
/sfs/software/cRNCApc/obj/ppc/DB_TEST_RI41119052630.do.gz

2.9.3. MIB Patch file


The file /sfs2/share/rw_data/mibPatch_Rxxxxxxx.txt (with xxx: the software version),
is used to patch the MIB.
This file is optional and is taken into account only if the version xxxx in the file name
is the running version.
It automatically patches the MIB.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 28/300

RNC & NodeB Health Check for NEV 4.2- How To

3 CONTROL NODE OPERATIONAL STATE


Purpose: check that omu are duplex, tmu started, and CP balanced.
3.1. Find out if an OMU is active

CLASSIC
Check that the OMU is ACTIVE (or passive) DUPLEX
RNC1204_OMU2:/OMU/local/usr/bin (omu) $ msgViOmuState
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=OMU is MSG_MODULE_ACTIVE
OMU is duplex
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

COMPACT
On OMU telci
telci(omu)>
msg omu
@ - Result of: msg omu
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=OMU is MSG_MODULE_ACTIVE
OMU is duplex
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

telci(omu)>
msg omu
@ - Result of: msg omu
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=OMU is MSG_MODULE_PASSIVE
OMU is duplex
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 29/300

RNC & NodeB Health Check for NEV 4.2- How To

3.2. Identify the boards in the CN


CLASSIC

RNC1204_OMU2:/OMU/local/usr/bin (omu) $ rbckp listeqp


Equipment
equipment[0]
equipment[1]
equipment[2]
equipment[3]
equipment[4]
equipment[5]
equipment[6]
equipment[7]
equipment[8]
equipment[9]
equipment[10]
equipment[11]
equipment[12]
equipment[13]

absPos
0xE5
0xE9
0xC5
0xC6
0xC9
0xCA
0xE7
0xE8
0xEB
0xEC
0xED
0xEE
0xCF
0xEF

Shelf
1
1
0
0
0
0
1
1
1
1
1
1
0
1

Slot

Type

5
9
5
6
9
10
7
8
11
12
13
14
15
15

OMU
OMU
OMUMMS
MMS
MMS
OMUMMS
CC1
CC1
TMU
TMU
TMU
TMU
SIM
SIM

COMPACT
There are no more OMU-TMU boards in a compact, as these functions are supported by
the AP.
Yet, a similar command would be:
On OMU telci
TELNET_CI> convertAbsPos
@ - Result of: convertAbsPos table
AbsPos(dec) AbsPos(hex) Instance# LP# AP#
===============================================
TMU
193
0xc1
0
2
1
TMU
195
0xc3
1
3
1
TMU
196
0xc4
2
4
1
TMU
203
0xcb
3
5
1
TMU
204
0xcc
4
6
1
TMU
205
0xcd
5
7
1
TMU
206
0xce
6
10
1
TMU
225
0xe1
7
11
1
TMU
227
0xe3
8
12
1
TMU
228
0xe4
9
12
5
TMU
235
0xeb
10
13
1
TMU
236
0xec
11
13
5
TMU
237
0xed
12
14
1
TMU
238
0xee
13
15
1
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 30/300

RNC & NodeB Health Check for NEV 4.2- How To


OMU
OMU

229
233

0xe5
0xe9

0
1

4
5

5
5

3.3. Check that the boards software is up to date


CLASSIC
According to the position of the board (shelf and slot) , the bupslice
allows to check a module software.

test

command

For example for the TMU whose position has been retrieved previously (rbckp
shelf 1 slot 11, the board is up to date.

listeqp),

RNC1204_OMU2:/OMU/local/usr/bin (omu) $ bupslice test 1 11


+----- Factory ------+- TM
: bs is up to date (cn.tmu.tm.flash.bs.H0 2.5.0.0).
+- SBC
: devb is up to date (cn.tmu.sbc.flash.firm.H1 1.4.0.0).
+
bs is up to date (cn.tmu.sbc.flash.bs.H1 2.1.3.0).
+----- Normal -------+- TM
: normal is up to date (cn.tmu.tm.flash.norm 2.9.16.0).
+- SBC
: normal is up to date (cn.tmu.sbc.flash.norm.H1 2.2.14.0).
+----- Alternate ----+- TM
: alternate is up to date (cn.tmu.tm.flash.alt 2.9.16.0).
+- SBC
: alternate is up to date (cn.tmu.sbc.flash.alt.H1 2.2.14.0).
==== The module is up to date ====

The factory parts corresponds to the boot firmware of the board. In the case it wouldnt
be up to date, it can be without impact for the TMU behaviour.
But normal and alternate modules must be up to date. If not the applications wont be
launched on the TMU perceived in a BIST failed state by the Control Node.

COMPACT
On CP (master is by default)
8> d sw avl
Sw
avList = atmNetworking_RI42065,
fabric_RI42065,
iRNC_RI42065,
ipsec_RI42065,
ss7_RI42065,
wirelessCommon_RI42065,

base_RI42065,
genericUtilities_RI42065,
ip_RI42065,
networking_RI42065,
wanDte_RI42065,
RNCCiph_RI42065055010,

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 31/300

RNC & NodeB Health Check for NEV 4.2- How To

ok

apcBase_RI42065055010,
baseExt_RI42065055010,
cRNCApc_RI42065055010,
cnp_RI42065055010,
iRNCApc_RI42065055010,
ss7Apc_RI42065055010
2006-04-07 10:21:16.02

3.4. Read the manufacturer and applicative data on a Control Node board

CLASSIC
rbckp <TM IP address> getmandata <Shelf> <Slot>
rbckp <TM IP address> getappdata <Shelf> <Slot>

For the TM IP address, use the address of the TM board of the active OMU.
Its easier to use omu_9_tm or omu_5_tm as these names will be resolved with etc/hosts
Example:
OMU 9 is active (msgViOmuState),
In shelf 1, slot 12 rbckp listeqp highlights a TMU.
RNC1204_OMUbis:/OMU/local/usr/bin (omu) $ rbckp omu_9_tm
Reading Manufacture data information for module (1,12)
PEC code:
NTQE56AA

Product release:
D04
Date of manufacture:
FEB19/2002
Serial number:
NNTM10178YJ5
RNC1204_OMUbis:/OMU/local/usr/bin (omu) $
rbckp omu_9_tm
Reading Application configuration data for module (1,12)
Format release: 02
Insertion Date: Oct15/2003 14:43:37
Site:
PLATEFORME-BSC3G
Unit:
00
Floor:
00
Row Position:
ARCY
Bay Identifier: CN:UNKNO
Shelf:
01
Slot:
12
BIST result:

getmandata 1 12

getappdata 1 12

COMPACT

95> d shelf card/1


Shelf Card/1
adminState = unlocked
operationalState = enabled
usageState
= active
availabilityStatus =
proceduralStatus
=
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 32/300

RNC & NodeB Health Check for NEV 4.2- How To


controlStatus
=
alarmStatus
=
standbyStatus
= providingService
unknownStatus
= false
currentLP
= Lp/0
failureCause
= none
selfTestFault
= none
sparingConnectionStatus = notApplicable
hardwareAlarm
= none
insertedCardType
= CPeE
productCode
= NTHW08CA-03
pmRevisionCode
= NTHW17B2-09
imRevisionCode
= N/A
serialNumber
= NNTM036046FA
activeFirmwareVersion
= RI42065
inactiveFirmwareVersion = RI41401
memoryCapacity
=
fastRam :
0 kbyte
normalRam : 262144 kbyte
sharedRam :
0 kbyte
sharedMsgBlockCapacity = 6011 kbyte
localMsgBlockCapacity
= 800 kbyte
timeInterval
= 11 minutes
cpuUtil
= 8 %
cpuUtilAvg
= 3 %
cpuUtilAvgMin
= 3 %
cpuUtilAvgMax
= 3 %
memoryUsage
=
fastRam :
0 kbyte
normalRam : 93544 kbyte
sharedRam :
0 kbyte
memoryUsageAvg
=
fastRam :
0 kbyte
normalRam : 93508 kbyte
sharedRam :
0 kbyte
memoryUsageAvgMin
=
fastRam :
0 kbyte
normalRam : 93504 kbyte
sharedRam :
0 kbyte
memoryUsageAvgMax
=
fastRam :
0 kbyte
normalRam : 93533 kbyte
sharedRam :
0 kbyte
sharedMsgBlockUsage
= 0 kbyte
sharedMsgBlockUsageAvg = 0 kbyte
sharedMsgBlockUsageAvgMin = 0 kbyte
sharedMsgBlockUsageAvgMax = 0 kbyte
localMsgBlockUsage
= 4 kbyte
localMsgBlockUsageAvg
= 3 kbyte
localMsgBlockUsageMin
= 3 kbyte
localMsgBlockUsageMax
= 9 kbyte
ok
2006-04-10 13:56:42.00

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 33/300

RNC & NodeB Health Check for NEV 4.2- How To

3.5. Check the Control Node led status


CLASSIC

Two leds are visible on the control node boards.


Initially three leds were used (rond amber led above the triangle), hidden now, it may still
be lid (just after having plugged a board, or during MMS disk accesses).
These indications are to be considered with care: the implementation can vary from one
load to the other.
Green and red leds behaviour
OMU/CC1/TMU
Red Led

Green Led

Status

Module not powered. Bist terminated successfully


The Bist is running or is terminated
unsuccessfully
Passive Module
Active Module
Alarm state
Path finding: the module can be removed

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 34/300

RNC & NodeB Health Check for NEV 4.2- How To

MMS
Red Led

Green Led

Status

The MMS module is not powered.


The disk is not managed or created.
The MMS is not operational (disk is updating or
stopping).
The disk is operational and updated
Alarm state
Path finding: the MMS can be removed

and

indicate that the leds are blinking.

COMPACT

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 35/300

RNC & NodeB Health Check for NEV 4.2- How To

Blinking orange LED indicate card is booting.


Red led indicate issue with the board
Green led indicate board is enable active

3.6. Led status from the Control Node consultation

CLASSIC
To read the led status remotely for the CN, use the command:
rbckp <TM IP address> getled <Shelf> <Slot>

For the TM IP address, use the address of the TM board of the active OMU.
Its easier to use omu_9_tm or omu_5_tm as these names will be resolved with etc/hosts.
rbckp listeqp gives you the shelf and the slot of a board.
RNC1204_OMUbis:/OMU (omu) $ rbckp omu_9_tm getled 1 12
module (1,12) : Led status = 4 => : GREEN :

The led status must be converted to a binary on 4 digits and interpreted as follow:
Digit 3

Digit 2

Digit 1

Digit 0
Amber Led
(hidden)

Red Led
Green Led

If the digit is set to 1 the led is ON.


If the digit is set to 0 the led is OFF.
In the example given: 4 => 0100 => Green Led is on.
If the result was 6 => 0110 => Green and Red leds are on.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 36/300

RNC & NodeB Health Check for NEV 4.2- How To

COMPACT
You cannot have the Led status on compact but you can use :
d shelf card/*
Shelf Card/*
Use -noTabular to see the many hidden attributes.
+====+-----+----+-----+---------------------+-------+-----+------+-----|Card|osiAd|osiO|osiUs|
currentLP
|failure|selfT|scstat|hwAlar
|
| min |per | age |
| Cause |estFa|
| m
|
|
|
|
|
|
| ult |
|
+====+-----+----+-----+---------------------+-------+-----+------+-----|
0|unlck|ena |activ|Lp/0
|none
|none |notApp|none
|
1|unlck|ena |activ|Lp/0
|none
|none |notApp|none
|
2|unlck|ena |activ|Lp/2
|none
|none |notApp|none
|
3|unlck|ena |activ|Lp/3
|none
|none |notApp|none
|
4|unlck|ena |activ|Lp/4
|none
|none |notApp|none
|
5|unlck|ena |activ|Lp/5
|none
|none |notApp|none
|
6|unlck|dis |idle |
|none
|none |notApp|none
|
|Component is disabled.
|
7|unlck|dis |idle |
|none
|none |notApp|none
|
|Component is disabled.
|
8|unlck|ena |activ|Lp/8
|none
|none |notApp|none
|
9|unlck|dis |idle |
|none
|none |notApp|none
|
|Component is disabled.
| 10|unlck|dis |idle |
|none
|none |notApp|none
|
|Component is disabled.
| 11|unlck|dis |idle |
|none
|none |notApp|none
|
|Component is disabled.
| 12|unlck|dis |idle |
|none
|none |notApp|none
|
|Component is disabled.
| 13|unlck|dis |idle |
|none
|none |notApp|none
|
|Component is disabled.
| 14|unlck|dis |idle |
|none
|none |notApp|none
|
|Component is disabled.
| 15|unlck|dis |idle |
|none
|none |notApp|none
|
|Component is disabled.
9 component(s) reported errors.

Component is disable would say that the card is not present in the config. (shelf empty)

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 37/300

RNC & NodeB Health Check for NEV 4.2- How To

3.7. Check if the boards are started, and PEC codes


sm_ext_supervision.exe gives SM (Software Management) status for all C-Node modules
and most of all their status, PEC code, bist
For TMU, OMU and CC1, the status should be operational. For other boards (SIM, MMS)
the status will be unknown.
If a board is starting, it means it has just reset.
Below is an example for few cards (result truncated on purpose).
Ctrl-c to exit the tool
RNC1204_OMU2:/OMU/local/usr/bin (omu) $ sm_ext_supervision.exe
+++ Initialized
+++ Sent CN supervision start request.
+++ Started - Waiting for supervision information...
+++ Received supervision start response at 2005/02/08 14:37:20.644
Response RC: Ok
+++ Received supervision report at 2005/02/08 14:37:20.646
Hardware configuration ID = 8
Number of modules present: 14

Position: [Platform: CONTROL NODE; Instance: 0; Sub equip.: MODULE_CA; Shelf: 1;


Slot: 5]
Hardware Data:
Absolute Position
: 0xe5
Resource Module type : OMU
Hw Release
: 1
Hw State
: BIST OK
Serial Number
:
NNTM10178NWM
PEC Code
:
NTQE03AB
Product Release
:
01
Software Data:
Status
: Operational
Managed by OMC
: Yes

Position: [Platform: CONTROL NODE; Instance: 0; Sub equip.: MODULE_CA; Shelf: 1;


Slot: 11]
Hardware Data:
Absolute Position
: 0xeb
Resource Module type : TMU
Hw Release
: 1
Hw State
: BIST OK
Serial Number
:
NNTM10178X3T
PEC Code
:
NTQE56AA
Product Release
: D02
Software Data:
Status
: Operational
Managed by OMC
: Yes

Position: [Platform: CONTROL NODE; Instance: 0; Sub equip.: MODULE_CA; Shelf: 1;


Slot: 15]
Hardware Data:
Absolute Position
: 0xef
Resource Module type : SIM
Hw Release
: 1
Hw State
: BIST non significant
Serial Number
: ??
PEC Code
: ??
Product Release
: ??
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 38/300

RNC & NodeB Health Check for NEV 4.2- How To


Software Data:
Status
Managed by OMC

: Unknown
: Yes

If a board is not correctly starting (for example TMU), you may use netstat
active OMU to check that IP packets are sent to it.
Editing /etc/hosts file allows determining the kind of board.

-r

on the

COMPACT
Same than for the RNC1000, except that the CC1 doesnt exist anymore.
On OMU telci
TELNET_CI>

sm sm_ext_sup

3.8. Get OMU/TMU FT processes status: ftViCpTable


CLASSIC
This command prints the fault tolerant (FT) processes (Core Process or CP) running
among OMU and TMU.
Here is a result (truncated on purpose), listing the core processes localized on OMU and
TMU.
RNC1204_OMU2:/OMU/local/usr/bin (omu) $ ftViCpTable
@all CI> CI TTY redirected to: me
@all CI> FT_LB_creator[20940] @RNC1204_OMU2 - Result of: cpTable vi
*** Printing Core Process Table (22 cp, 14 cg)
Omu 0
(cpId = 0,AbsPos=229, omu, boardNum=0, act.=Act., FtState = Active
1]),
(cpId = 1,AbsPos=229, omu, boardNum=0, act.=Act., FtState = Active
1]),
(cpId = 2,AbsPos=229, omu, boardNum=0, act.=Act., FtState = Active
1]),
(cpId = 3,AbsPos=229, omu, boardNum=0, act.=Act., FtState = Active
1]),
(cpId = 4,AbsPos=229, omu, boardNum=0, act.=Act., FtState = Active
1]),
(cpId = 5,AbsPos=229, omu, boardNum=0, act.=Act., FtState = Active
1]),
(cpId = 6,AbsPos=229, omu, boardNum=0, act.=Act., FtState = Active
1]),
(cpId = 7,AbsPos=229, omu, boardNum=0, act.=Act., FtState = Active
1]),

, FT/LB [Oc: 0 Rk:


, CM_CA [Oc: 0 Rk:
, SupCN [Oc: 0 Rk:
, OAM_CA [Oc: 0 Rk:
, Umts_CP1 [Oc: 0 Rk:
, Umts_CP2 [Oc: 0 Rk:
, Umts_CP3 [Oc: 0 Rk:
, Umts_CP4 [Oc: 0 Rk:

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 39/300

RNC & NodeB Health Check for NEV 4.2- How To


Tmu 0
(cpId = 16,AbsPos=235, tmu, boardNum = 0, act.=Act., FtState = Active , Umts_Ue [Oc: 0
Rk: 1]),
(cpId = 19,AbsPos=235, tmu, boardNum = 0, act.=Act., FtState = Active , Umts_Nodeb [Oc:
0 Rk: 1]),
Tmu 1
(cpId = 17,AbsPos=236, tmu, boardNum = 1, act.= Act., FtState = Active , Umts_Ue [Oc: 1
Rk: 1]),
(cpId = 20,AbsPos=236, tmu, boardNum = 1, act.= Act., FtState = Active , Umts_Nodeb [Oc:
1 Rk: 1]),
Tmu 2
(cpId = 18,AbsPos=237, tmu, boardNum = 2, act.= Act., FtState = Active , Umts_Ue [Oc: 2 Rk: 1]),
(cpId = 21,AbsPos=237, tmu, boardNum = 2, act.= Act., FtState = Active , Umts_Nodeb [Oc: 2 Rk: 1]),

2 CP per TMU and 8 CP per OMU must be present.


The rank indicates the number of creation of the CP, and therefore can indicate the number of
restart of a board.

Check that one OMU is holding only active CP and that the other is holding the same CP
but in a passive state.
Field descriptions:
Field

Meaning

cpId

Core process identity


Module absolute position, refer to the
following

AbsPos
Module type
act
FtState
Unknown
New
Idle
IdlePassive
IdleActive
Active
Passive
CpType
occ
rank

OMU or TMU
FT status
Current FT Status of the CP, see below
the CP has been spawned
The CP is registered to messaging
In start-up phase, the CP has loaded its
DP (Permanent Data) from MIB
The CP has flushed its DD (Dynamic Data)
The CP has been swacted active/passive
CP active
CP Passive
Name of the Core Process
Occurrence of the process
Rank

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 40/300

RNC & NodeB Health Check for NEV 4.2- How To

COMPACT
cpTable used with convertAbsPos.
N.B. In V4.2, a new CP (UMTS_CacheMgr) appears on some TMU.
telci(omu)> cpTable
Result of: cpTable vi
*** Printing Core Process Table (24 cp, 16 cg)
Omu 0
(cpId = 0,AbsPos = 233, omu, boardNum = 0, act.= Act., FtState =
(cpId = 1,AbsPos = 233, omu, boardNum = 0, act.= Act., FtState =
(cpId = 2,AbsPos = 233, omu, boardNum = 0, act.= Act., FtState =
(cpId = 3,AbsPos = 233, omu, boardNum = 0, act.= Act., FtState =
(cpId = 4,AbsPos = 233, omu, boardNum = 0, act.= Act., FtState =
(cpId = 5,AbsPos = 233, omu, boardNum = 0, act.= Act., FtState =
(cpId = 6,AbsPos = 233, omu, boardNum = 0, act.= Act., FtState =
(cpId = 7,AbsPos = 233, omu, boardNum = 0, act.= Act., FtState =
Omu 1
(cpId = 8,AbsPos = 229, omu, boardNum = 1, act.= Pas., FtState =
(cpId = 9,AbsPos = 229, omu, boardNum = 1, act.= Pas., FtState =
(cpId = 10,AbsPos = 229, omu, boardNum = 1, act.= Pas., FtState =
(cpId = 11,AbsPos = 229, omu, boardNum = 1, act.= Pas., FtState =
(cpId = 12,AbsPos = 229, omu, boardNum = 1, act.= Pas., FtState =
(cpId = 13,AbsPos = 229, omu, boardNum = 1, act.= Pas., FtState =
(cpId = 14,AbsPos = 229, omu, boardNum = 1, act.= Pas., FtState =
(cpId = 15,AbsPos = 229, omu, boardNum = 1, act.= Pas., FtState =
Tmu 0
(cpId = 16,AbsPos = 193, tmu, boardNum = 0, act.= Act., FtState =
(cpId = 19,AbsPos = 193, tmu, boardNum = 0, act.= Act., FtState =
Tmu 1
(cpId = 17,AbsPos = 196, tmu, boardNum = 1, act.= Act., FtState =
(cpId = 20,AbsPos = 196, tmu, boardNum = 1, act.= Act., FtState =
Tmu 2
(cpId = 18,AbsPos = 203, tmu, boardNum = 2, act.= Act., FtState =
(cpId = 21,AbsPos = 203, tmu, boardNum = 2, act.= Act., FtState =
Tmu 3
(cpId = 22,AbsPos = 195, tmu, boardNum = 3, act.= Act., FtState =
(cpId = 23,AbsPos = 195, tmu, boardNum = 3, act.= Act., FtState =

Active
Active
Active
Active
Active
Active
Active
Active

,
,
,
,
,
,
,
,

FT/LB [Oc: 0 Rk: 1]),


CM_CA [Oc: 0 Rk: 1]),
SupCN [Oc: 0 Rk: 1]),
OAM_CA [Oc: 0 Rk: 1]),
Umts_CP1 [Oc: 0 Rk: 1]),
Umts_CP2 [Oc: 0 Rk: 1]),
Umts_CP3 [Oc: 0 Rk: 1]),
Umts_CP4 [Oc: 0 Rk: 1]),

Passive , FT/LB [Oc: 0 Rk: 2]),


Passive , CM_CA [Oc: 0 Rk: 2]),
Passive , SupCN [Oc: 0 Rk: 2]),
Passive , OAM_CA [Oc: 0 Rk: 2]),
Passive , Umts_CP1 [Oc: 0 Rk: 2]),
Passive , Umts_CP2 [Oc: 0 Rk: 2]),
Passive , Umts_CP3 [Oc: 0 Rk: 2]),
Passive , Umts_CP4 [Oc: 0 Rk: 2]),
Active
Active

, Umts_Nodeb [Oc: 0 Rk: 1]),


, Umts_Ue [Oc: 0 Rk: 1]),

Active
Active

, Umts_Nodeb [Oc: 1 Rk: 1]),


, Umts_Ue [Oc: 1 Rk: 1]),

Active
Active

, Umts_Nodeb [Oc: 2 Rk: 1]),


, Umts_Ue [Oc: 2 Rk: 1]),

Active
Active

, Umts_Ue [Oc: 3 Rk: 1]),


, Umts_CacheMgr [Oc: 0 Rk: 1]),

WARNING: the boardNumber attribute should not be confused with the instance number.
The table below provides that conversion
AbsPos(dec) AbsPos(hex) Instance# LP# AP#
===============================================
TMU
193
0xc1
0
2
1
TMU
195
0xc3
1
3
1
TMU
196
0xc4
2
4
1
TMU
203
0xcb
3
5
1
TMU
204
0xcc
4
TMU
205
0xcd
5
TMU
206
0xce
6
TMU
225
0xe1
7
TMU
227
0xe3
8
TMU
228
0xe4
9
TMU
235
0xeb
10
TMU
236
0xec
11
TMU
237
0xed
12
TMU
238
0xee
13
OMU
229
0xe5
0
4
5
OMU
233
0xe9
1
5
5

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 41/300

RNC & NodeB Health Check for NEV 4.2- How To

3.9. Get OMU/TMU/CC1 non FT processes status


CLASSIC
sm_launcher.exe board <board_absolute_position> ps
This command gives the status of non FT processes groups and processes.
See chapter 3.11. OMU and TMU board address according to the Module Absolute
Position to identify a board absolute position.
All processes groups should be executing, all the processes should be started or
finished.
Example for OMU 9 / abs pos 489 / fully started (truncated result on purpose)
RNC1204_OMU2:/OMU/local/usr/bin (omu) $ sm_launcher.exe board 489 ps
Board position set to: [Platform: CONTROL NODE; Instance: 0; Sub equip.: SBC;
Shelf: 1; Slot: 9]

RC: Ok
Report: Size: 3921 [octets]. Text follows.
Process Group
State
Time Launched
Activity_Election_Platform
Executing
2005/02/09 16:43:27.331
Minimal_FT_Platform_1
Executing
2005/02/09 16:44:00.495
Minimal_Non_FT_Platform
Executing
2005/02/09 16:43:43.427
Oam_Minimal_Platform
Executing
2005/02/09 16:43:26.038
UMTS_FT_Platform
Executing
2005/02/09 16:45:31.330
UMTS_Non_FT_Platform
Executing
2005/02/09 16:45:35.626

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 42/300

RNC & NodeB Health Check for NEV 4.2- How To

PID
5162
2916
15998
11926
15762
14218
18602
18864
12690
16564
12962
18362
18098
19350
19608
19866
20382
20640
20898
19110
17896
21416
20148
21672
21930
22966
13970
5764
23248
22714
17326
13700
22220
23478
23736
23994
24252
24510
24768
25026
25284

Application Name
FM
SWB
ACTIVITY_MNGT
OAM_HM
APE
ATM_OMU_Selection
CM_LA
DAS
FAS
FT_LA
FmBosEvent
Histo
OamOvCa
SCI_CA
SCI_LA
TEST_DIAG_CN_MGNT
TEST_DIAG_SERVER
UpgradeCn
UpgradeLmt
CREATOR_CMCA
FT_LB_creator
OAM_CA
OamCn_Creator
OamSmCn_crtr
SwbCreator
ATMM_CA_CRE
CPM_CREATOR
CREATOR_CMCA_H
DDR_CREATOR
IN_CREATOR
IUXADM_CREATOR
IU_CREATOR
PFCA_CREATOR
TR_CA_CREATOR
FMGSC_CA
FMGSC_MA
IN_Access_LA
IN_PROXIES
PFPROXY
RNCUPGSUP
TR_PROXY

State
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started
Started

Instance
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 43/300

RNC & NodeB Health Check for NEV 4.2- How To

COMPACT
The menu is the same as for an RNC1000.
On OMU telci
TELNET_CI>sm sm_launcher
@ - Result of: sm sm_launcher
SM Launcher
===========
Operating on local board: [Platform: CONTROL NODE; Instance: 0; Sub equip.: SBC;
Shelf: 1; Slot: 9]
Command
------create
modify
delete
get_create_data
ps
pgs
bs
board
board-shutdown
oam-shutdown
quit

Description
----------Create a process group
Modify a process group
Delete a process group
Get process group create data
Process status
Process group status
Board status
Set board position
Board shutdown
OAM shutdown
Quit

Command:

The menu offers the same facilities than for the classic.
ps dumps the process status on the OMU, to check that all the processes are launched and
running.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 44/300

RNC & NodeB Health Check for NEV 4.2- How To

3.10. Find out if spares TMU are present


CLASSIC

rbckp listeqp will list all the plugged TMU in the Control Node
sm_ext_supervision.exe allows the starting or the operational state of the
boards plugged.
the spare TMU wont be listed in ftViCpTable: they wont hold any Core
Process.

For a fully fitted Control Node (14 tmu plugged) 2 TMU are spare.
For a 4 TMU configuration one TMU should be spare.

COMPACT
Not applicable.
3.11. OMU-TMU board address according to the Module Absolute Position

CLASSIC
Be sure to differentiate module absolute position and board absolute position
You can either
translate its absolute position in hex, refer to rbckp listeqp result (see chapter 2.
How to identify the boards in the CN) and use /etc/hosts to identify the board
name resolution
calculate directly its ip address,
First way
For example, for TMU 0 in ftViCpTable result, its absolute position is 235
1. 235 converted in hexa is 0xEB
2. rbckp listeqp result was :
Equipment

equipment[8]

absPos
0xEB

Shelf
1

Slot

Type

11

TMU

3. The tmu can be reached by opening a telnet command interpreter session on the
board:
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 45/300

RNC & NodeB Health Check for NEV 4.2- How To


telci tmu_1_11_sbc
telci tmu_1_11_tm

for the sbc board


for the tm board

The name resolution is assumed by /etc/hosts


Or 2nd way
1. Convert the AbsPos in hex
2. Mask it with 0x2F (AbsPos AND 0x2F)
3. Convert it in decimal
4. The IP addresses are:
TMU-TM:
172.decimalvalue.2.1
TMU-SBC: 172.decimalvalue.2.2
Example Absolute position 235
235 0xEB
0xEB AND 0x2F = 0x2B
0x2B 43
TMU-TM: 172.43.2.1
TMU-SBC: 172.43.2.2

The C-Node boards internal IP addresses, names and absolute positions can also be
find in the file /etc/hosts.
TMU internal boards names, internal boards addresses, absolute boards positions
and absolute modules positions:

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 46/300

RNC & NodeB Health Check for NEV 4.2- How To

Shelf 1
Slot 1

Slot 3

Slot 4

Slot 11

Slot 12

Slot 13

Slot 14

0xed (237)

0xee (238)

Module absolute position


0xe1 (225)

0xe3 (227)

0xe4 (228)

0xeb (235)

0xec (236)

TMU TM (name of the board, IP address, board absolute position)


tmu_1_1_tm

tmu_1_3_tm

tmu_1_4_tm

tmu_1_11_tm

tmu_1_12_tm

tmu_1_13_tm

tmu_1_14_tm

172.33.2.1

172.35.2.1

172.36.2.1

172.43.2.1

172.44.2.1

172.45.2.1

172.46.2.1

0x2e1 (737)

0x2e3 (739)

0x2e4 (740)

0x2eb (747)

0x2ec (748)

0x2ed (749)

0x2ee (750)

TMU SBC (name of the board, IP address, board absolute position)


tmu_1_1_sbc

tmu_1_3_sbc

tmu_1_4_sbc

tmu_1_11_sbc

tmu_1_12_sbc

tmu_1_13_sbc

tmu_1_14_sbc

172.33.2.2

172.35.2.2

172.36.2.2

172.43.2.2

172.44.2.2

172.45.2.2

172.46.2.2

0x1e1 (481)

0x1e3 (483)

0x1e4 (484)

0x1eb (491)

0x1ec (492)

0x1ed (493)

0x1ee (494)

Slot 1

Slot 3

Slot 4

Slot 11

Slot 12

Slot 13

Slot 14

0xcd (205)

0xce (206)

Shelf 0
Module absolute position
0xc1 (193)

0xc3 (195)

0xc4 (196)

0xcb (203)

0xcc (204)

TMU TM (name of the board, IP address, board absolute position)


tmu_0_1_tm

tmu_0_3_tm

tmu_0_4_tm

tmu_0_11_tm

tmu_0_12_tm

tmu_0_13_tm

tmu_0_14_tm

172.1.2.1

172.3.2.1

172.4.2.1

172.11.2.1

172.12.2.1

172.13.2.1

172.14.2.1

0x2c1 (705)

0x2c3 (707)

0x2c4 (708)

0x2cb (715)

0x2cc (716)

0x2cd (717)

0x2ce (718)

TMU SBC (name of the board, IP address, board absolute position)


tmu_0_1_sbc

tmu_0_3_sbc

tmu_0_4_sbc

tmu_0_11_sbc

tmu_0_12_sbc

tmu_0_13_sbc

tmu_0_14_sbc

172.1.2.2

172.3.2.2

172.4.2.2

172.11.2.2

172.12.2.2

172.13.2.2

172.14.2.2

0x1c1 (449)

0x1c3 (451)

0x1c4 (452)

0x1cb (459)

0x1cc (460)

0x1cd (461)

0x1ce (462)

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 47/300

RNC & NodeB Health Check for NEV 4.2- How To

Slot 5

Slot 6

Slot 7

Slot 8

Slot 9

Slot 10

Module absolute position


0xe5 (229)

0xe7 (231)

0xe8 (232)

0xe9 (233)

TM (name of the board, IP address, board absolute position)


omu_5_tm

omu_9_tm

172.37.2.1

172.41.2.1

0x3e5 (997)

0x3e9 (1001)

PMC (name of the board, IP address, board absolute position)


omu_5_pmc1

omu_9_pmc1

172.33.3.2

172.41.3.2

0x3e5 (997)

0x3e9 (1001)

SBC (name of the board, IP address, board absolute position)


omu_5_sbc
172.37.2.2
0x1e5 (485)

cc1_7_sbc

cc1_8_sbc

172.253.1.39 172.253.1.40
0x1e7 (487)

0x1e8 (488)

omu_9_sbc
172.41.2.2
0x1e9 (489)

To check messaging traffic between all SBC boards

msgFullMeshTable
On an OMU-SBC board, traffic should be opened towards :
its OMU-TM board
both CC1-SBC boards
all the TMU-SBC boards.
RNC1204_OMU2:/OMU/local/usr/bin (omu) $ msgViFullMeshTbl
[0] <Present> <ip@farend: 172.41.2.2> <TRAFFIC OPENED>
[1] <Present> <ip@farend: 172.37.2.1> <TRAFFIC OPENED>
[2] <Present> <ip@farend: 172.253.1.40> <TRAFFIC OPENED>
[3] <Present> <ip@farend: 172.253.1.39> <TRAFFIC OPENED>
[4] <Present> <ip@farend: 172.43.2.2> <TRAFFIC OPENED>
[5] <Present> <ip@farend: 172.46.2.2> <TRAFFIC OPENED>
[6] <Present> <ip@farend: 172.45.2.2> <TRAFFIC OPENED>
[7] <Present> <ip@farend: 172.44.2.2> <TRAFFIC OPENED>

omu_3 cnbos
This command checks:
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 48/300

RNC & NodeB Health Check for NEV 4.2- How To

the IP/ATM connection between OMU-SBC and each card (TM,SBC)


that the minimal software is started on SBC boards.
The result must be ok.
RNC1204_OMU2:/OMU/local/usr/bin (omu) $ omu_diag 3 cnbos
++ cnnet
-

ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping
ping

++

172.253.1.37--172.37.2.2----172.253.1.41--172.41.2.2----172.253.1.39--172.253.1.40--172.253.1.43--172.43.2.2----172.253.1.44--172.44.2.2----172.253.1.45--172.45.2.2----172.253.1.46--172.46.2.2-----

++ cnbos
-

Control-Node IP Access ++++++++++++++++++++++++++

access
access
access
access
access
access

++
to
to
to
to
to
to

bos
bos
bos
bos
bos
bos

1
1
1
1
1
1
1
1
1
1
1
1
1
1

55997811
11
12
12
13
13
14
14

OMUOMUOMUOMUCC1CC1TMUTMUTMUTMUTMUTMUTMUTMU-

TM.................
SBC................
TM.................
SBC................
SBC................
SBC................
TM.................
SBC................
TM.................
SBC................
TM.................
SBC................
TM.................
SBC................

ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok
ok

Control-Node BaseOS Access ++++++++++++++++++++++

on
on
on
on
on
on

1
1
1
1
1
1

7811
12
13
14

CC1CC1TMUTMUTMUTMU-

SBC....................
SBC....................
SBC....................
SBC....................
SBC....................
SBC....................

ok
ok
ok
ok
ok
ok

# passed : 20
# failed : 0

COMPACT
convertAbsPos and msg fullmesh give the same information.
There is no equivalent command for omu_diag.
TELNET_CI> convertAbsPos
@ - Result of: convertAbsPos table
AbsPos(dec) AbsPos(hex) Instance# LP# AP#
===============================================
TMU
193
0xc1
0
2
1
TMU
195
0xc3
1
3
1
TMU
196
0xc4
2
4
1
[]

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 49/300

RNC & NodeB Health Check for NEV 4.2- How To


TELNET_CI> msg fullmesh
@ - Result of: msg fullmesh
Messaging fullmesh table :
[00] <Present><ip: 127.2.1.33><TRAFFIC
[01] <Present><ip: 127.2.1.37><TRAFFIC
[03] <Present><ip: 127.2.1.38><TRAFFIC
[04] <Present><ip: 127.2.1.39><TRAFFIC
[05] <Present><ip: 127.2.1.40><TRAFFIC
[06] <Present><ip: 127.2.1.41><TRAFFIC
[07] <Present><ip: 127.2.1.42><TRAFFIC
[08] <Present><ip: 127.2.1.43><TRAFFIC
[09] <Present><ip: 127.2.1.44><TRAFFIC
[11] <Present><ip: 127.2.1.45><TRAFFIC
[12] <Present><ip: 127.2.1.46><TRAFFIC
[13] <Present><ip: 127.2.1.47><TRAFFIC
[14] <Present><ip: 127.2.1.48><TRAFFIC
[15] <Present><ip: 127.2.1.49><TRAFFIC
[16] <Present><ip: 127.2.1.50><TRAFFIC
[00]
[01]
[03]
[04]
[05]
[06]
[07]
[08]
[09]
[11]
[12]
[13]
[14]
[15]
[16]

127.2.1.33
127.2.1.37
127.2.1.38
127.2.1.39
127.2.1.40
127.2.1.41
127.2.1.42
127.2.1.43
127.2.1.44
127.2.1.45
127.2.1.46
127.2.1.47
127.2.1.48
127.2.1.49
127.2.1.50

OPEN
OPEN
OPEN
OPEN
OPEN
OPEN
OPEN
OPEN
OPEN
OPEN
OPEN
OPEN
OPEN
OPEN
OPEN

id
id
id
id
id
id
id
id
id
id
id
id
id
id
id

=
=
=
=
=
=
=
=
=
=
=
=
=
=
=

26
38
34
39
37
35
36
40
46
44
43
42
41
45
33

OPENED>
OPENED>
OPENED>
OPENED>
OPENED>
OPENED>
OPENED>
OPENED>
OPENED>
OPENED>
OPENED>
OPENED>
OPENED>
OPENED>
OPENED>

[0/0/0/0:19/8/15/2] [0:46/0/0] [1] [3694:654 KB <=> 3505:766 KB] idle for 57 s


[0/0/0/0:8/4/4/1] [0:33/0/0] [0] [2030:526 KB <=> 1704:569 KB] idle for 20 s
[0/0/0/0:14/4/4/1] [0:33/0/0] [0] [2055:532 KB <=> 1787:585 KB] idle for 21 s
[0/0/0/0:8/6/4/1] [0:31/0/0] [0] [2033:526 KB <=> 1706:569 KB] idle for 20 s
[0/0/0/0:8/4/3/1] [0:32/0/0] [0] [2037:529 KB <=> 1713:570 KB] idle for 20 s
[0/0/0/0:12/4/10/1] [0:34/0/0] [0] [2056:533 KB <=> 1744:576 KB] idle for 20 s
[0/0/0/0:9/4/4/1] [0:31/0/0] [0] [2053:532 KB <=> 1739:575 KB] idle for 20 s
[0/0/0/0:12/4/4/1] [0:33/0/0] [0] [2028:526 KB <=> 1692:567 KB] idle for 39 s
[0/0/0/0:8/4/4/1] [0:31/0/0] [0] [2025:525 KB <=> 1662:563 KB] idle for 20 s
[0/0/0/0:8/4/4/1] [0:31/0/0] [0] [2024:525 KB <=> 1676:565 KB] idle for 20 s
[0/0/0/0:11/4/4/1] [0:32/0/0] [0] [2028:529 KB <=> 1690:609 KB] idle for 20 s
[0/0/0/0:8/4/4/1] [0:32/0/0] [0] [1958:515 KB <=> 1611:526 KB] idle for 20 s
[0/0/0/0:8/4/4/1] [0:32/0/0] [0] [2027:525 KB <=> 1684:566 KB] idle for 20 s
[0/0/0/0:8/4/3/1] [0:33/0/0] [0] [2027:525 KB <=> 1677:565 KB] idle for 19 s
[0/0/0/0:10/4/4/1] [0:31/0/0] [0] [2013:522 KB <=> 1693:537 KB] idle for 19 s

The OMU/TMU work on another addressing plan (127.2.x.x).


16 entries for TCP/IP traffic must be present, in a full configuration: 14 TMU and 2
OMU.
3.12. File system check

CLASSIC
Each OMU active should see at least its private MMS (Memory Mass Storage board,
containing hard drive).
4 MMS are present in the Control Node.
Each OMU has its own MMS (private MMS).
2 MMS are used for mirroring the private MMS. They will be mounted for the active
OMU only.
COMPACT
Not applicable.
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 50/300

RNC & NodeB Health Check for NEV 4.2- How To

3.12.1. OMU disks status


CLASSIC
Df
displays number of free disk blocks and files.
Check that no file system is around 100%.
On the active OMU, check also that the shared MMS are mounted (file systems
/dev/std_mirvg_LV0 to LV3)
RNC1204_OMU2:/OMU (omu) $ df -k
Filesystem
1024-blocks
Free %Used
/dev/hd4
114688
48212
58%
/dev/hd2
393216
119432
70%
/dev/hd9var
229376
215916
6%
/dev/hd3
622592
600728
4%
/dev/hd1
32768
20708
37%
/dev/lv00
1048576
804620
24%
/dev/lv01
212992
205976
4%
/dev/lv02
1048576
714980
32%
/dev/lv03
1048576
725360
31%
/dev/lv04
114688
111052
4%
/dev/std_mirvg_LV0
2736128
1838748
/dev/std_mirvg_LV1
1949696
1807020
/dev/std_mirvg_LV2
1949696
1659828
/dev/std_mirvg_LV3
720896
178152

Iused %Iused Mounted on


1322
3% /
17253
18% /usr
224
1% /var
22
1% /tmp
39
1% /home
450
1% /OMU_STORAGE/log/local
23
1% /OMU_STORAGE/rw_data/local
433
1% /OMU_STORAGE/TREE1/local/usr
430
1% /OMU_STORAGE/TREE2/local/usr
17
1% /OMU_STORAGE/tmp
33%
323
1% /OMU_STORAGE/SHARE
8%
55
1% /OMU_STORAGE/log/share
15%
485
1% /OMU_STORAGE/fault/share
76%
688
1% /OMU_STORAGE/rw_data/share

On the passive OMU, private disk only is seen.


RNC1204_OMUbis:/OMU (omu) $ df -k
Filesystem
/dev/hd4
/dev/hd2
/dev/hd9var
/dev/hd3
/dev/hd1
/dev/lv00
/dev/lv01
/dev/lv02
/dev/lv03
/dev/lv04

1024-blocks
114688
393216
229376
622592
32768
1048576
212992
1048576
1048576
114688

Free %Used
41684
64%
119980
70%
216164
6%
602960
4%
20708
37%
959084
9%
205976
4%
717332
32%
725376
31%
111052
4%

Iused %Iused Mounted on


1249
3% /
17190
18% /usr
223
1% /var
19
1% /tmp
39
1% /home
437
1% /OMU_STORAGE/log/local
23
1% /OMU_STORAGE/rw_data/local
432
1% /OMU_STORAGE/TREE1/local/usr
426
1% /OMU_STORAGE/TREE2/local/usr
17
1% /OMU_STORAGE/tmp

lspv
This command lists the physical volumes seen by an OMU.
For the active OMU, one private MMS (rootvg = root volume group) and two shared
MMS (std_mirvg) must be seen
RNC1204_OMU2:/OMU (omu) $ lspv
hdisk0
0049e9f663c6a36b
hdisk1
004f4da54efffe00
hdisk2
0052f3262b389790

rootvg
std_mirvg
std_mirvg

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 51/300

RNC & NodeB Health Check for NEV 4.2- How To

The passive OMU only sees its private disk


RNC1204_OMUbis:/OMU (omu) $ lspv
hdisk3
004854fecb28b380

rootvg

COMPACT
For file system on passport see paragraph 2.7 File System overview for RNC1500.
29> d fs disk/* part/*
Fs Disk/* Part/*
+====+====+----------+----------+----------+-----+----+----|Disk|Part| capacity |freeSpace |badBlocksP|osiAd|osiO|osiUs
|
|
|
Gbyte|
Gbyte|ercentage | min |per | age
|
|
|
|
|
%|
|
|
+====+====+----------+----------+----------+-----+----+----|
0|
0| 4.294770| 1.122697|
0|unlck|ena |activ
|
0|
1| 7.837175| 7.408001|
0|unlck|ena |activ
|
0|
2| 7.837175| 7.371448|
0|unlck|ena |activ
|
1|
0| 4.294770| 1.122697|
0|unlck|ena |activ
|
1|
1| 7.837175| 7.407804|
0|unlck|ena |activ
|
1|
2| 7.837175| 7.385219|
0|unlck|ena |activ
ok
2005-08-08 15:36:32.28

3.12.2. Shared MMS mirroring check up

CLASSIC
lsvg -p std_mirvg
gives the mirroring status for the 2 shared MMS, the status should be active.
Under the active OMU
RNC1204_OMU2:/OMU
std_mirvg:
PV_NAME
hdisk1
hdisk2

(omu) $ lsvg -p std_mirvg


PV STATE
active
active

TOTAL PPs
546
546

FREE PPs
96
96

FREE DISTRIBUTION
66..00..00..00..30
66..00..00..00..30

lsvg -l std_mirvg
gives the synchronization state of the shared MMS, the state should be open/syncd

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 52/300

RNC & NodeB Health Check for NEV 4.2- How To

Under the active OMU


RNC1204_OMU2:/OMU (omu) $ lsvg -l std_mirvg
std_mirvg:
LV NAME
std_mirvglvlog
std_mirvg_LV0
std_mirvg_LV1
std_mirvg_LV2
std_mirvg_LV3

TYPE
jfslog
jfs
jfs
jfs
jfs

LPs
1
167
119
119
44

PPs
2
334
238
238
88

PVs
2
2
2
2
2

LV STATE
open/syncd
open/syncd
open/syncd
open/syncd
open/syncd

MOUNT POINT
N/A
/OMU_STORAGE/SHARE
/OMU_STORAGE/log/share
/OMU_STORAGE/fault/share
/OMU_STORAGE/rw_data/share

COMPACT
Not applicable.

3.12.3. MMS integrity check (number of bad sectors)


CLASSIC
blvm_readPv -B <name_of_the_disk>
This command checks the integrity of the disks.
The number of bad blocks (number of entries) should be 0.
The name of the disk is obtained with lspv
RNC1204_OMU2:/OMU/local/usr/bin (omu) $

run_root blvm_readPv -B hdisk1

<START - BAD BLOCK DIRECTORY>


Identifier
: DEFECT
Number of entries : 0
<END - BAD BLOCK DIRECTORY>
Identifier
:
Number of entries : 0
Directory end mark error

omu_diag 3 lvm
(result truncated)
RNC1202_titi-1:/OMU (omu) $ omu_diag 3 lvm
++ omulvm
++ OMU Local Logical Volume Management +++++++++++++
- there is 3/3 scsi adapters (lscfg|fgrep scsi)..... ok

- hdisk3 : Number of bad blocks = 0................. ok


++ mirlvm
++ Mirrored File Systems +++++++++++++++++++++++++++

- hdisk0 : Number of bad blocks = 0................. ok


- hdisk1 : Number of bad blocks = 0................. ok

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 53/300

RNC & NodeB Health Check for NEV 4.2- How To

COMPACT
Not applicable.
3.13. MIB Verification
CLASSIC
Confirm that mib is built/Mib customization is correct/Paths
The Management Information Base (MIB) that will be built, or customized by the
operator is localized in /OMU/share/rw_data/MibRunning, the database is DB_TEST.do.
Once built the MIB is nominal (reduced or minimal is for a MIB not built).
This folder is only reachable from the active OMU, once the shared MMS are mounted.
/OMU/share/rw_data/MibRunning is a logical link to /OMU/share/rw_data/Mib1 or
/OMU/share/rw_data/Mib2.
The original MIB delivered with an RNC version is stored in /OMU/share/local/usr/data.
This one is not supposed to be customized.
MIB_PATCH_TOOL
mib_patch_tool.exe is used to read or modify the mib,
mib_patch_tool.exe help command sums up the facilities provided by this tool.
COMPACT
See paragraph 2.9 MIB directories for RNC1500 for more details.
MIB_PATCH_TOOL
The menu mib on the OMU allows to read the content of a table.
mib help to display the possible commands,
mib read to read a table.

3.13.1. Confirmation that the MIB is built


CLASSIC
Two ways can be used:
either a reading of the MIB itself,
or the consultation of the APE process with ci_mgr.
RNC1204_OMU2:/OMU/share/rw_data/MibRunning (omu) $ mib_patch_tool.exe --mib
DB_TEST.do --read cmmib
cmmib[0].id_inst.inst[0] 0
cmmib[0].id_inst.inst[1] 0
cmmib[0].id_inst.inst[2] 0
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 54/300

RNC & NodeB Health Check for NEV 4.2- How To


cmmib[0].id_inst.inst[3] 0
cmmib[0].data.create_state 1
cmmib[0].data.mibBuildNumber 1107773253
cmmib[0].data.mibActivationType 1
cmmib[0].data.mibVersionNumber 0
cmmib[0].data.create_state

should be 1.

2nd Way,
Consultation of the MIB state according to APE
Find its pid and open a ci_mgr session.
The MIB state must be nominal (i.e. built) and not reduced nor minimal (not built).
Example:
RNC1204_OMUbis:/OMU/local/usr/bin (omu) $ psg -i ape
root 16706 5186
0
Feb 11
- 4:04 APE --uniqueid 4 --instance 0
RNC1204_OMUbis:/OMU/local/usr/bin (omu) $ ci_mgr -noxterm

@all CI> tty me


CI TTY redirected to: me
@all CI> 16706=

16706 CI> ape admin


APE[16706] @RNC1204_OMUbis - Result of: ape admin
--------------------------------------OMU ACTIVITY
--------------------------------------Previous Omu Activty = eOmuActivityState_Unknown
Omu Activty
= eOmuActivityState_Active
--------------------------------------MIB STATE
--------------------------------------Previous Mib State
= MibState_Unknown
Mib State
= MibState_Nominal
--------------------------------------VARIABLE CONTEXT
--------------------------------------Class Initialisation is done
The trsp disconnexion is not requested
The trsp connexion is authorized
Prefix, occurence and Rank of messaging name for message to Update Assoc
:
CM_CA 0 1
Prefix, occurence and Rank of messaging name for message to Init&Transac Assoc :
CM_CA 0 1
Automaton state
: APE_ADMIN_DATA_CNF_COMPLETED
Automaton last event : APE_ADMIN_LOAD_DISPATCH_MSG

Other tips:
When a mib is built, its status should be nominal and no longer reduced in the
/OMU_STORAGE/log/local/bos/sc/blogio.tmp file.
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 55/300

RNC & NodeB Health Check for NEV 4.2- How To

The core processes should also be distributed on TMU and OMU.

COMPACT
Just like for the RNC1000,
cmmib[0].data.create_state (through mib cmmib) must be 1
or the mib state must be nominal (through ape admin).
TELNET_CI> mib read cmmib
@ - Result of: mib read cmmib
cmmib[0].id_inst.inst[0] 0
cmmib[0].id_inst.inst[1] 0
cmmib[0].id_inst.inst[2] 0
cmmib[0].id_inst.inst[3] 0
cmmib[0].data.create_state 1
cmmib[0].data.mibBuildNumber 1123510305
cmmib[0].data.mibActivationType 0
cmmib[0].data.mibVersionNumber 0

Or second way :
TELNET_CI> ape admin
@ - Result of: ape admin
--------------------------------------OMU ACTIVITY
--------------------------------------Previous Omu Activty = eOmuActivityState_Unknown
Omu Activty
= eOmuActivityState_Active
--------------------------------------MIB STATE
--------------------------------------Previous Mib State
= MibState_Unknown
Mib State
= MibState_Nominal
--------------------------------------VARIABLE CONTEXT
--------------------------------------Class Initialisation is done
The trsp disconnexion is not requested
The trsp connexion is authorized
Prefix, occurence and Rank of messaging name for message to Update Assoc
:
CM_CA 0 1
Prefix, occurence and Rank of messaging name for message to Init&Transac Assoc :
CM_CA 0 1
Automaton state
: APE_ADMIN_DATA_CNF_COMPLETED
Automaton last event : APE_ADMIN_READREP

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 56/300

RNC & NodeB Health Check for NEV 4.2- How To

Note
For a Compact RNC, the MIB is built on the OMC first and then sent (FTP) to the RNC.
Therefore, the traces of the build will be located on the OMC under the following
directory: /opt/nortel/data/access/tmp/RncProxy/
More information on this process can be found under the following url:
http://eurlivelink.europe.nortel.com/livelink/livelink.exe/15529462/V4.1_RNC1500_OAM_aspects_presentation_01.01.ppt?fun
c=doc.Fetch&nodeid=15529462

3.13.2. Mib customization


CLASSIC
The TML is used for the customization of the RNC.
It will generate the file of its customization and stored under
/OMU/share/rw_data/MibRunning/MibDataCustomization/BSC_CUSTOMIZATION_D
ATA
When the customization is done and the RNC restarted, then the MIB will be customized
according to the customization file.
Thats why its important to check first that a correct customization is made and then that
the MIB is customized.
BSC_CUSTOMISATION_DATA check up
This may also be used to check the customization:
RNC1204_OMUbis:/OMU/local/usr/bin (omu) $ DASPrintf -str <
/OMU/share/rw_data/MibRunning/MibDataCustomization/BSC_CUSTOMIZATION_DATA
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.numberOfPcmInTable
6
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[0].lsaNumber
0
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[0].pcmNumber
0
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[1].lsaNumber
0
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[1].pcmNumber
2
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[2].lsaNumber
0
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[2].pcmNumber
4
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[3].lsaNumber
0
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[3].pcmNumber
1
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[4].lsaNumber
0
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[4].pcmNumber
3
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[5].lsaNumber
0
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[5].pcmNumber
5
BSC_CUSTOMIZATION_DATA.configuration.crcOption
0
BSC_CUSTOMIZATION_DATA.configuration.omcAccessType
1
BSC_CUSTOMIZATION_DATA.configuration.lineEncoding
-1
BSC_CUSTOMIZATION_DATA.configuration.lineBuildOut
4294967295
BSC_CUSTOMIZATION_DATA.configuration.gatewayIpAddress
"47.164.52.1"
BSC_CUSTOMIZATION_DATA.configuration.atmCaINode.bscIpAddress
"172.253.204.0"
BSC_CUSTOMIZATION_DATA.configuration.atmCaINode.bscMaskIpAddress
"255.255.255.0"
BSC_CUSTOMIZATION_DATA.configuration.atmCaINode.bscHostName
"UNKNOWN"
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 57/300

RNC & NodeB Health Check for NEV 4.2- How To


BSC_CUSTOMIZATION_DATA.location.bscLocation.site
"PLATEFORME-BSC3G"
BSC_CUSTOMIZATION_DATA.location.bscLocation.unit
"00"
BSC_CUSTOMIZATION_DATA.location.bscLocation.floor
"00"
BSC_CUSTOMIZATION_DATA.location.bscLocation.rowPosition
"ARCY"
BSC_CUSTOMIZATION_DATA.location.bscLocation.bayIdentifier
"CN:UNKNO"
BSC_CUSTOMIZATION_DATA.cc1Config
0
BSC_CUSTOMIZATION_DATA.cc1SdhSonetConfig
0

MIB customization check up


RNC1204_OMU2:/OMU/share/rw_data/MibRunning (omu) $ mib_patch_tool.exe --mib
DB_TEST.do --arraysofunsignedchar=str --read BSC_CUSTOMIZATION_DATA
BSC_CUSTOMIZATION_DATA.customizationDone BOOL_TRUE
BSC_CUSTOMIZATION_DATA.configuration.bscNumber 799290472
BSC_CUSTOMIZATION_DATA.configuration.bscIpOmu0.bscIpAddress 47.164.52.104
BSC_CUSTOMIZATION_DATA.configuration.bscIpOmu0.bscMaskIpAddress 255.255.255.0
BSC_CUSTOMIZATION_DATA.configuration.bscIpOmu0.bscHostName RNC1204_OMU2
BSC_CUSTOMIZATION_DATA.configuration.bscIpOmu1.bscIpAddress 47.164.52.204
BSC_CUSTOMIZATION_DATA.configuration.bscIpOmu1.bscMaskIpAddress 255.255.255.0
BSC_CUSTOMIZATION_DATA.configuration.bscIpOmu1.bscHostName RNC1204_OMUbis
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.numberOfPcmInTable 6
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[0].lsaNumber
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[0].pcmNumber
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[1].lsaNumber
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[1].pcmNumber
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[2].lsaNumber
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[2].pcmNumber
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[3].lsaNumber
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[3].pcmNumber
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[4].lsaNumber
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[4].pcmNumber
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[5].lsaNumber
BSC_CUSTOMIZATION_DATA.configuration.pcmConfigTable.pcmConfigData[5].pcmNumber
BSC_CUSTOMIZATION_DATA.configuration.crcOption ADM_OPTION_NO_CRC
BSC_CUSTOMIZATION_DATA.configuration.omcAccessType ADM_OMC_ACCESS_IP
BSC_CUSTOMIZATION_DATA.configuration.lineEncoding -1
BSC_CUSTOMIZATION_DATA.configuration.lineBuildOut 4294967295
BSC_CUSTOMIZATION_DATA.configuration.gatewayIpAddress 47.164.52.1
BSC_CUSTOMIZATION_DATA.configuration.atmCaINode.bscIpAddress 172.253.204.0
BSC_CUSTOMIZATION_DATA.configuration.atmCaINode.bscMaskIpAddress 255.255.255.0
BSC_CUSTOMIZATION_DATA.configuration.atmCaINode.bscHostName UNKNOWN
BSC_CUSTOMIZATION_DATA.location.bscLocation.site PLATEFORME-BSC3G
BSC_CUSTOMIZATION_DATA.location.bscLocation.unit 00
BSC_CUSTOMIZATION_DATA.location.bscLocation.floor 00
BSC_CUSTOMIZATION_DATA.location.bscLocation.rowPosition ARCY
BSC_CUSTOMIZATION_DATA.location.bscLocation.bayIdentifier CN:UNKNO
BSC_CUSTOMIZATION_DATA.cc1Config ADM_CC1_CONFIG_STATIC_AT_CC1_START_UP
BSC_CUSTOMIZATION_DATA.cc1SdhSonetConfig ADM_CC1_DRIVER_CONFIG_SDH

0
0
0
2
0
4
0
1
0
3
0
5

Revelant information is in bold and red.


Check that IP addresses, subnets are correct.
COMPACT
Use the following command on CP for checking IP addresses :
3> d -p rncin
RncIn
primaryOmuIpAddress = 0.0.0.0
secondaryOmuIpAddress = 0.0.0.0
oamPrimaryOmuIpAddress = 47.164.52.235
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 58/300

RNC & NodeB Health Check for NEV 4.2- How To


oamSecondaryOmuIpAddress = 47.164.52.236
oamOmcIpAddresses
= 47.164.36.176
rncInfo
= ""
protocolConverterResources = 17 %
mode
= rnc
ok
2006-04-10 16:03:05.80

3.14. RNC1000 RNC1500 : telci commands changed


Here is a table (not exhaustive) of equivalences for omu commands:

RNC1000 (Classic)

RNC1500 (Compact)

telci

telci omu(instance) rnc or telci


tmu(instance) rnc

collectCrLog

use cott

cott
ftViCpTable

cott
cpTable

getCellInfo
msgViRoutingTable

use cott
msg lwp

msgViLwgTable
msgViFullMeshTbl

msg lwg
msg fullmesh

msgViOmuState
msgTrafficTool

msg omu
msgTrafficTool

mib_patch_tool.exe
rbckp listeqp

mib
convertAbsPos

swbDebugMenu.exe
sm_ext_supervision.exe

swbDeb
sm sm_ext_sup

sm_launcher.exe
TR_LAUNCHER.exe

sm sm_launcher
trca

3.15 ATM check-up on CC1 and TM boards

COMPACT
Not applicable for RNC1500.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 59/300

RNC & NodeB Health Check for NEV 4.2- How To

CLASSIC
The CC1 module is the ATM switch that implements the ATM network (AAL5) used as
the Control Node backplane, and that provides an OC-3 connectivity towards the
Interface Node.

3.15.1. S/UNI state


The S/UNI (Saturn User Network Interface) is the chip in charge of the OC-3 stream on
the CC1.
The stream, therefore, the physical layer generated by the optical interface can be
checked on each CC1.
Connect onto the cc1 from an OMU (telci cc1_7_sbc or telci cc1_8_sbc)
Run suni getState, the expected state is OK, and not defect.
TELNET_CI>
suni getState
cc1 @cc1_1_7_sbc - Result of: suni getState
S/UNI is in OK state

3.15.2. ATM planes state


The transmission through the Control Nodes backplane is based on two ATM planes: a
hardware duplication of all the paths between CC1, TMU and OMU.
3.15.2.1. CC1 verifications
Testing frames are transmitted from/to the CC1 to check that planes or boards are up
from an ATM point of view.
V4.2
aal5 testStats
aal5Test tml

overview of the physical planes for the CC1


overview of the physical planes towards each
TMU/OMU board

On each CC1, check that for each plane (0 and 1) the counters are almost identical for the
testing frames.
The reception counters must be equal or slightly below the transmission counter.
Both planes must respond correctly.
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 60/300

RNC & NodeB Health Check for NEV 4.2- How To

The rate of errors must be low.


TELNET_CI> aal5 testStats
cc1 @cc1_1_7_sbc - Result of: aal5 testStats
Traffic counters :
aal5TestTxCpt = 120402
aal5TestPlane0RxCpt = 120394
aal5TestPlane1RxCpt = 120394

Transmission counter
Reception counter for plane 0
Reception counter for plane 1
Error counters must remain low

Errors counters :
aal5TestOutOfDelayRxCpt = 14
aal5TestNoReplyCpt = 8
aal5TestBadDataCpt = 0
aal5TestExtraRxCpt = 14

In V4.2 where the ratio is directly provided for each plane (P0 and P1).
TELNET_CI>
aal5Test tml
cc1 @cc1_1_8_sbc - Result of: aal5Test tml
+----------------------------------------------------------------------------------+
| SHLF | SLOT | STATE | PHY | TX CELLS | % P0 | % P1 | Status P0 | Status P1
|
+----------------------------------------------------------------------------------+
| 0
| 1
|
| BAD | 218215
| 0
| 0
|
ERROR
|
ERROR
|
| 0
| 11
|
| GOOD| 218215
| 99
| 99
|
OK
|
OK
|
| 1
| 5
|
| GOOD| 218215
| 99
| 99
|
OK
|
OK
|
| 1
| 7
|
| GOOD| 218215
| 99
| 99
|
OK
|
OK
|
| 1
| 9
|
| GOOD| 218195
| 99
| 99
|
OK
|
OK
|
| 1
| 11
|
| GOOD| 218215
| 99
| 99
|
OK
|
OK
|
| 1
| 12
|
| GOOD| 218215
| 99
| 99
|
OK
|
OK
|
| 1
| 13
|
| GOOD| 218215
| 99
| 99
|
OK
|
OK
|
+----------------------------------------------------------------------------------+

3.15.2.2. Verifications of the plane on TM (OMU/TMU) boards


From the TMU-TM or the OMU-TM, the plane in can be checked and eventually
switched.
telci tmu_shlef_slot_tm or telci omu_5_tm or telci tmu omu_9_tm
netclk data
displays the plane used and the latest events
netclk switch
to switch the plane manually.
Example below
RNC1206_OMU1:/OMU (omu) $ telci omu_5_tm
Trying...
Connected to omu_5_tm.
Escape character is '^]'.
TELNET_CI>
netclk dynData
tm @omu_1_5_tm - Result of: netclk dynData
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 61/300

RNC & NodeB Health Check for NEV 4.2- How To


Netclock dynamic data :
netclock_activePlane = atm_planeId0
Plane 0 is in use
39 plane switch(s) occured, latest are :
Switched to plane 1 (cause=MCA1_TASK) at : FRI SEP 09 09:38:33 2005 197 ms
Switched to plane 0 (cause=MCA1_TASK) at : FRI SEP 09 09:38:43 2005 197 ms
Switched to plane 1 (cause=MCA1_TASK) at : FRI SEP 09 09:38:53 2005 197 ms
[]
Plane switches by cause :
1 switches due to SW_INIT
1 switches due to MCA1_IRQ
37 switches due to MCA1_TASK
TELNET_CI> netclk switch
tm @omu_1_5_tm - Result of: netclk switch
New active plane = 1. Done.
TELNET_CI> netclk dynData
tm @omu_1_5_tm - Result of: netclk dynData
Netclock dynamic data :
netclock_activePlane = atm_planeId1
Plane 1 is now in use
Latest events
40 plane switch(s) occured, latest are :
Switched to plane 0 (cause=MCA1_TASK) at : FRI SEP 09 09:38:43 2005 197 ms
Switched to plane 1 (cause=MCA1_TASK) at : FRI SEP 09 09:38:53 2005 197 ms
Switched to plane 0 (cause=MCA1_TASK) at : FRI SEP 09 09:39:03 2005 197 ms
Switched to plane 1 (cause=MCA1_TASK) at : FRI SEP 09 09:39:13 2005 197 ms
Switched to plane 0 (cause=MCA1_TASK) at : FRI SEP 09 09:39:23 2005 172 ms
Switched to plane 1 (cause=MCA1_TASK) at : FRI SEP 09 09:39:33 2005 172 ms
Switched to plane 0 (cause=MCA1_TASK) at : FRI SEP 09 09:39:43 2005 172 ms
Switched to plane 1 (cause=MCA1_TASK) at : FRI SEP 09 09:39:53 2005 172 ms
Switched to plane 0 (cause=MCA1_TASK) at : FRI SEP 09 09:40:03 2005 172 ms
Switched to plane 1 (cause=CI_USER) at : FRI SEP 16 13:11:39 2005 251 ms
Plane switches by cause :
1 switches due to SW_INIT
1 switches due to MCA1_IRQ
37 switches due to MCA1_TASK
1 switches due to CI_USER
Manual switch performed

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 62/300

RNC & NodeB Health Check for NEV 4.2- How To

4 INTERFACE NODE OPERATIONAL STATE

4.1. Control and Function processors LEDs


Status Indicator

Description

No colour

Card is unpowered

Solid Red

Card is powered on and performing tests, or


after 30s is faulty.

Slow pulsing red

Card is waiting to load its software

Fast pulsing red

Card is loading its software

Slow pulsing green

Card is loaded but not activated

Fast pulsing green

Card is operational and spare

Solid green

Card is active and in full service

Solid amber

Card is not faulty, but cannot operate (does not


fit the configuration)

4.2. Ensure I-Node startup is successful


1. Software has loaded onto the cards in the I-Node :
During the software loading process, the appropriate PMC base and application binaries
download to the PDC.
The binaries then initialize, the base first, the application second.
Check that all active cards have loaded correctly and show a RunningAsActive state.
6> os pcsShowCards
CARD
TYPE
------------0
CPeE
1
CPeE
2
6mPktServSP
3
6mPktServSP
4
6mPktServSP
5
6mPktServSP
8
16pOC3SmIrAtm
9
16pOC3SmIrAtm

FSM STATE
----------------RunningAsActive
RunningAsStandby
RunningAsActive
RunningAsActive
RunningAsActive
RunningAsActive
RunningAsActive
RunningAsActive

VISIBILITY
---------OnLine
OnLine
OnLine
OnLine
OnLine
OnLine
OnLine
OnLine

LP
-0
0
2
3
4
5
8
9

INSTANCE
-------Active
Standby
Active
Active
Active
Active
Active
Active

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 63/300

RNC & NodeB Health Check for NEV 4.2- How To

7> d lp/*
Lp/*
+==+-----+----+-----+--------------------+------+------+------|Lp|osiAd|osiO|osiUs|
activeCard
|mainCa|spareC|restart
| | min |per | age |
|rdStat|ardSta|OnCpSwi
| |
|
|
|
| us | tus | tch
+==+-----+----+-----+--------------------+------+------+------| 0|unlck|ena |activ|Shelf Card/0
|active|availa|false
| 2|unlck|ena |activ|Shelf Card/2
|active|notPro|false
| 3|unlck|ena |activ|Shelf Card/3
|active|notPro|false
| 4|unlck|ena |activ|Shelf Card/4
|active|notPro|false
| 5|unlck|ena |activ|Shelf Card/5
|active|notPro|false
| 8|unlck|ena |activ|Shelf Card/8
|active|notPro|false
| 9|unlck|ena |activ|Shelf Card/9
|active|notPro|false
ok
2005-02-15 19:10:19.05

4.3. File System check up for RNC1500


Refer to paragraph 2.7 File System overview for RNC1500.
4.4. Determine if Base OS has completed initialization
All APC (lp/* ap/*) must show:
o An admin state unlocked
o An operational state enabled
o An usage state active

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 64/300

RNC & NodeB Health Check for NEV 4.2- How To

9> d lp/* ap/*


Lp/* Ap/*
+==+==+-----+----+-----+--------+---------------+----------+---------|Lp|Ap|osiAd|osiO|osiUs| apType |
ipAddr
|memoryCapa|sharedMsgB
| | | min |per | age |
|
|
city
|lockCapaci
| | |
|
|
|
|
|
kbyte|
ty
| | |
|
|
|
|
|
|
kbyte
+==+==+-----+----+-----+--------+---------------+----------+---------| 2| 0|unlck|ena |activ|FCI11502|172.253.204.79 |
234346|
16384
| 2| 1|unlck|ena |activ|FCI11502|172.253.204.80 |
234346|
16384
| 2| 2|unlck|ena |activ|FCI11502|172.253.204.81 |
234346|
16384
| 2| 3|unlck|ena |activ|FCI11502|172.253.204.82 |
234346|
16384
| 2| 4|unlck|ena |activ|FCI11502|172.253.204.83 |
234346|
16384
| 2| 5|unlck|ena |activ|FCI11502|172.253.204.84 |
234346|
16384
| 3| 0|unlck|ena |activ|FCI11302|172.253.204.73 |
234346|
16384
| 3| 1|unlck|ena |activ|FCI11302|172.253.204.74 |
234346|
16384
| 3| 2|unlck|ena |activ|FCI11302|172.253.204.75 |
234346|
16384
| 3| 3|unlck|ena |activ|FCI11302|172.253.204.76 |
234346|
16384
| 3| 4|unlck|ena |activ|FCI11302|172.253.204.77 |
234346|
16384
| 3| 5|unlck|ena |activ|FCI11302|172.253.204.78 |
234346|
16384
| 4| 0|unlck|ena |activ|FCI11302|172.253.204.67 |
234346|
16384
| 4| 1|unlck|ena |activ|FCI11302|172.253.204.68 |
234346|
16384
| 4| 2|unlck|ena |activ|FCI11302|172.253.204.69 |
234346|
16384
| 4| 3|unlck|ena |activ|FCI11302|172.253.204.70 |
234346|
16384
| 4| 4|unlck|ena |activ|FCI11302|172.253.204.71 |
234346|
16384
| 4| 5|unlck|ena |activ|FCI11302|172.253.204.72 |
234346|
16384
| 5| 0|unlck|ena |activ|FCI11302|172.253.204.61 |
234346|
16384
| 5| 1|unlck|ena |activ|FCI11302|172.253.204.62 |
234346|
16384
| 5| 2|unlck|ena |activ|FCI11302|172.253.204.63 |
234346|
16384
| 5| 3|unlck|ena |activ|FCI11302|172.253.204.64 |
234346|
16384
| 5| 4|unlck|ena |activ|FCI11302|172.253.204.65 |
234346|
16384
| 5| 5|unlck|ena |activ|FCI11302|172.253.204.66 |
234346|
16384

4.5. Determine if the applications have completed initialization


CLASSIC
During the initialization of the applications, roles are assigned to each of the APC on the
PSFPs.
No role should be none.
Below is a correct initialization, all the APC are used as Master, rab, pc (or Ni with v4
versions).

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 65/300

RNC & NodeB Health Check for NEV 4.2- How To

12> d lp/* ap/* rnc


Lp/* Ap/* RncAp
+==+==+-------+----------+----------+----------+----------+---------|Lp|Ap| role |sparedCell|unSparedCe| numCall |sparedPath|unsparedPa
| | |
|
|
ll
|
|
|
th
+==+==+-------+----------+----------+----------+----------+---------| 2| 0|aMaste |
0|
0|
0|
0|
0
| 2| 1|rab
|
0|
0|
0|
0|
0
| 2| 2|rab
|
0|
0|
0|
0|
0
| 2| 3|rab
|
0|
0|
0|
0|
0
| 2| 4|pc
|
0|
0|
0|
3|
0
| 2| 5|rab
|
0|
0|
0|
0|
0
| 3| 0|sMaste |
0|
0|
0|
0|
0
| 3| 1|rab
|
0|
0|
0|
0|
0
| 3| 2|rab
|
0|
0|
0|
0|
0
| 3| 3|rab
|
0|
0|
0|
0|
0
| 3| 4|pc
|
0|
0|
0|
3|
0
| 3| 5|rab
|
0|
0|
0|
0|
0
| 4| 0|rab
|
0|
0|
0|
0|
0
| 4| 1|rab
|
0|
0|
0|
0|
0
| 4| 2|rab
|
0|
0|
0|
0|
0
| 4| 3|rab
|
0|
0|
0|
0|
0
| 4| 4|pc
|
0|
0|
0|
2|
0
| 4| 5|rab
|
0|
0|
0|
0|
0
| 5| 0|rab
|
1|
0|
0|
0|
0
| 5| 1|rab
|
0|
0|
0|
0|
0
| 5| 2|rab
|
0|
0|
0|
0|
0
| 5| 3|rab
|
0|
0|
0|
0|
0
| 5| 4|pc
|
0|
0|
0|
3|
0
| 5| 5|rab
|
0|
0|
0|
0|
0

COMPACT
The same command must also return active, serving Ni, active/serving OMU and TMU
ap roles.
See paragraph 2.2. OMU and TMU: new PMC (ap) roles, with deterministic assignments.
4.6. Determine if ATM connectivity is available
The status of the atm links across the 16port OC-3 cards is essential for the
communication to the external entities (Control Node, Node B, core network).
Check that Atm/vcc entries are
o Administrative state: unlocked
o Operational state: enabled
o Usage : busy
To determine what is connected (not the purpose here), you can rely on the tags of the
virtual channel descriptors, if they have been provisioned (d p atmif/* vcc/* vcd).
By convention:
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 66/300

RNC & NodeB Health Check for NEV 4.2- How To

Atmif/800 to AtmIf/807
Atmif/808
Atmif/814 and AtmIf/815

Iub
Control Node
Iu

(for RNC1000 only)

Example (results truncated)


27> d atmif/* vcc/*
AtmIf/* Vcc/*
Use -noTabular to see the many hidden attributes.
+=====+==========+-----+----+-----+------+-------+----------+------+-----|AtmIf|
Vcc
|osiAd|osiO|osiUs| cpt |distrbt|
nlvs
| cdir |opStat
|
|
| min |per | age |
|
|
|
|
+=====+==========+-----+----+-----+------+-------+----------+------+-----| 800|0.33
|unlck|ena |busy |connec|pointT |
0|notApp|unknow
| 800|0.34
|unlck|ena |busy |connec|pointT |
0|notApp|unknow
| 800|0.42
|unlck|ena |busy |connec|pointT |
0|notApp|unknow
[]

The SDH must also be up, enable, busy.


In the following example, fibers seem to be connected for the 16port OC3 card inserted in
slot 8 (lp/8) only in port 0, 8 and 15
33> d lp/* sdh/*
Lp/* Sdh/*
+==+===+------+-----+----+-----+---+---+---+---+----+---+---+---------|Lp|Sdh|snmpOp|osiAd|osiO|osiUs|los|lof|ais|rfi|utcr|txA|txR|
time
| |
|erStat| min |per | age |
|
|
|
|
|is |di |
| |
| us |
|
|
|
|
|
|
|
|
|
|
+==+===+------+-----+----+-----+---+---+---+---+----+---+---+---------| 8| 0|up
|unlck|ena |busy |off|off|off|off|off |off|off|
449056
| 8| 1|down |unlck|dis |idle |on |off|off|off|off |off|on |
449058
| 8| 2|down |unlck|dis |idle |on |off|off|off|off |off|on |
449058
| 8| 6|down |unlck|dis |idle |on |off|off|off|off |off|on |
449058
| 8| 7|down |unlck|dis |idle |on |off|off|off|off |off|on |
449058
| 8| 8|up
|unlck|ena |busy |off|off|off|off|off |off|off|
449058
| 8| 15|up
|unlck|ena |busy |off|off|off|off|off |off|off|
449058
| 9| 0|down |unlck|dis |idle |on |off|off|off|off |off|on |
449061
| 9| 1|down |unlck|dis |idle |on |off|off|off|off |off|on |
449060
| 9| 2|down |unlck|dis |idle |on |off|off|off|off |off|on |
449060
| 9| 6|down |unlck|dis |idle |on |off|off|off|off |off|on |
449061
| 9| 7|down |unlck|dis |idle |on |off|off|off|off |off|on |
449061
| 9| 8|down |unlck|dis |idle |on |off|off|off|off |off|on |
449061
| 9| 15|down |unlck|dis |idle |on |off|off|off|off |off|on |
449061
ok
2005-02-15 19:57:02.37

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 67/300

RNC & NodeB Health Check for NEV 4.2- How To

For a specific vcc it can be interesting to check that the amount of received and
transmitted atm cells is increasing.
d atmif/atmif_number vcc/vcc_number rxcell,txcell
Example:
To see if cells are sent and received to and from a NodeB CP
13> d -p atmif/800 vcc/0.50 vcd tag
AtmIf/800 Vcc/0.50 Vcd
correlationTag = NB+nCP+00+BTS_RED205
ok
2006-04-18 11:14:56.59
14> d atmif/800 vcc/0.50 rxcell,txcell
AtmIf/800 Vcc/0.50
rxCell = 216304
txCell = 182227
ok
2006-04-18 11:15:23.69
15> d atmif/800 vcc/0.50 rxcell,txcell
AtmIf/800 Vcc/0.50
rxCell = 216312
txCell = 182235
ok
2006-04-18 11:15:39.04

To see what vcc are used on atmif/800:


19> d atmif/800 vcc/* vcd tag
AtmIf/800 Vcc/* Vcd
+==========+--------------------+---------------------------------------|
Vcc
|
tag
|Response
+==========+--------------------+---------------------------------------|0.33
|NB+OAM+00+BTS_193983|
|0.34
|NB+DSS+00+BTS_193983|
|0.42
|NB+NDS+01+BTS_193983|
|0.50
|NB+nCP+00+BTS_193983|
|0.51
|NB+CCP+00+BTS_193983|
|0.58
|NB+DSS+00+BTS_193914|
|
| _LAV
|
|0.66
|NB+NDS+01+BTS_193914|
|
| _LAV
|
|0.74
|NB+nCP+00+BTS_193914|
|
| _LAV
|
|0.75
|NB+CCP+00+BTS_193914|
|
| _LAV
|
|0.81
|NB+OAM+00+BTS_194014|
|0.82
|NB+DSS+00+BTS_194014|
|0.90
|NB+NDS+01+BTS_194014|
|0.98
|NB+nCP+00+BTS_194014|
|0.99
|NB+CCP+00+BTS_194014|

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 68/300

RNC & NodeB Health Check for NEV 4.2- How To

4.7. Determine if the AAL2 ATM Interface is available.


An Iuxif path (now called Aal2If path in V4.2) through an ATM Nep (Nailed up End
Point) Vcc, is responsible for handing AAL2 ATM traffic from/to physical interface and
route it to/from AAL2-IP/AAL5 PCs (Protocol Converters) embedded in the same
Passport Shelf.
CLASSIC/COMPACT
Check that All Aal2 path are:
o Administrative state: unlocked
o Operational state: enabled
o Usage : active
o Remotely status : unblocked
o Locally status : unblocked
15> d aal2/* path/*
Aal2If/* Path/*
+======+=====+-----+----+-----+--------+-------|Aal2If|Path |osiAd|osiO|osiUs|remoteBl|localBlo
|
|
| min |per | age |ockingSt|ckingSta
|
|
|
|
|
| atus | tus
+======+=====+-----+----+-----+--------+-------|
1|
8|unlck|ena |activ|unbloc |unbloc
|
1|
16|unlck|ena |activ|unbloc |unbloc
|
300|
48|unlck|ena |activ|unbloc |unbloc
ok
2006-04-18 12:09:12.59

Each Aal2if path is linked to an Atmif VCC through an ATM Nep d p aal2/* path/* .

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 69/300

RNC & NodeB Health Check for NEV 4.2- How To

21> d -p aal2/* path/*


Aal2If/* Path/*
+======+=====+--------------------+---+----|Aal2If|Path |
atmConnection
|qos|pathO
|
|
|
|
|wner
+======+=====+--------------------+---+----|
1|
8|AtmIf/800 Vcc/0.42 | 1|yes
|
|
| Nep
|
|
|
1|
16|AtmIf/800 Vcc/0.34 | 0|yes
|
|
| Nep
|
|
|
300|
48|AtmIf/815 Vcc/1.48 | 0|yes
|
|
| Nep
|
|
ok
2006-04-28 15:49:18.05

To see which Iux the Aal2If links to


22> d -p aal2/* umtsInterfaceList
Aal2If/*
+======+---------------------+---------------------------------------|Aal2If| umtsInterfaceList |Response
+======+---------------------+---------------------------------------|
1|Iub/1 IuUplane
|
|
| Aal2Lk/1
|
|
300|Iucs/1 IuUplane
|
|
| Aal2Lk/1
|
ok
2006-04-28 16:13:58.81

To see the number of the paths to be spared or unspared in each PMC-PC


23> d lp/* ap/4 rnc role, numOfsparedPaths, numOfUnSparedPaths
Lp/* Ap/4 RncAp
+==+-------+----------+----------+---------------------------------------|Lp| role |sparedPath|unsparedPa|Response
| |
|
|
th
|
+==+-------+----------+----------+---------------------------------------| 2|pc
|
0|
0|
| 3|pc
|
1|
0| The path for Iucs Aal2If 300/path 48
| 4|pc
|
0|
0| (you can see these by showPCsPaths())
| 5|pc
|
2|
0| The 2 paths for Iub Aal2If 1/Path 8 and 16
ok
2006-04-28 16:25:08.08

The tbmHelp shows you more commands about AAL2.


Please see UMTS RNC-IN AAL2 Debug Guidefor more details. Also you can find all
the commands in the Annexe A.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 70/300

RNC & NodeB Health Check for NEV 4.2- How To

4.8. Determine if the atmmpe layer is available.


The atm encapsulation layer sends and receives packets between the Atmif and the virtual
router
The expected state is unlocked, enabled, active.
50> d atmmpe/* ac/*
AtmMpe/* Ac/*
Use -noTabular to see hidden attributes: inErrors, inUnknownProtos, inOctets
and inPackets.
+======+===+-----+----+-----+----------+----------+----------+---------|AtmMpe|Ac |osiAd|osiO|osiUs| speed
|outPackets|outOctets |outDiscard
|
|
| min |per | age |
bit/s|
|
|
s
+======+===+-----+----+-----+----------+----------+----------+---------| 1000| 1|unlck|ena |activ|
0|
18530|
1099320|
1
| 1000| 3|unlck|ena |activ|
0|
51|
2996|
0
| 1020| 48|unlck|ena |activ|
0|
2|
56|
2
| 1020| 49|unlck|ena |activ| 22348192|
128|
3584|
0
| 1020| 50|unlck|ena |activ|
0|
127|
3556|
1
| 1020| 51|unlck|ena |activ|
999792|
127|
3556|
1
| 1023| 52|unlck|ena |activ|
0|
509|
14252|
3
| 1023| 60|unlck|ena |activ|
1919872|
526|
15328|
3
| 1023| 61|unlck|ena |activ|
1919872|
588|
19496|
3
| 1023| 62|unlck|ena |activ|
1919872|
414457| 25680376|
4
| 1023| 63|unlck|ena |activ|
1919872|
106955|
6613380|
4
| 1023| 64|unlck|ena |activ|
1919872|
18776|
1155496|
4
ok
2005-02-15 20:11:15.77

4.9. Check PMC-M fully redundant

4.9.1 How to find the PMC Master and serving


d lp/* ap/* rnc role
d lp/* ap/* ip
Open a telnet session on the CP of the Interface Node.
Identify the lp/ ap/ whose role is active Master (amaster) and retrieve its ip address.
The active Master (amaster) is lp/2 ap/0 in this case, its ip address is 172.253.204.79.
The slave Master (smaster) is lp/3 ap/0 (ip address 172.253.204.73).

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 71/300

RNC & NodeB Health Check for NEV 4.2- How To


10> d lp/* ap/* rnc role
Lp/* Ap/* RncAp
+==+==+-------+---------------------------------------|Lp|Ap| role |Response
+==+==+-------+---------------------------------------| 2| 0|aMaste |
| 2| 1|rab
|
| 2| 2|rab
|
| 2| 3|rab
|
| 2| 4|pc
|
| 2| 5|rab
|
| 3| 0|sMaste |
| 3| 1|rab
|
| 3| 2|rab
|
| 3| 3|rab
|
| 3| 4|pc
|
| 3| 5|rab
|
| 4| 0|rab
|
| 4| 1|rab
|
| 4| 2|rab
|
| 4| 3|rab
|
| 4| 4|pc
|
| 4| 5|rab
|
| 5| 0|rab
|
| 5| 1|rab
|
| 5| 2|rab
|
| 5| 3|rab
|
| 5| 4|pc
|
| 5| 5|rab
|
ok
2005-02-14 17:56:28.67
10> d lp/* ap/* ip
Lp/* Ap/*
+==+==+---------------+---------------------------------------|Lp|Ap|
ipAddr
|Response
+==+==+---------------+---------------------------------------| 2| 0|172.253.204.79 |
| 2| 1|172.253.204.80 |
| 2| 2|172.253.204.81 |
| 2| 3|172.253.204.82 |
| 2| 4|172.253.204.83 |
| 2| 5|172.253.204.84 |
| 3| 0|172.253.204.73 |
| 3| 1|172.253.204.74 |
| 3| 2|172.253.204.75 |
| 3| 3|172.253.204.76 |
| 3| 4|172.253.204.77 |
| 3| 5|172.253.204.78 |
| 4| 0|172.253.204.67 |
| 4| 1|172.253.204.68 |
| 4| 2|172.253.204.69 |
| 4| 3|172.253.204.70 |
| 4| 4|172.253.204.71 |
| 4| 5|172.253.204.72 |
| 5| 0|172.253.204.61 |
| 5| 1|172.253.204.62 |
| 5| 2|172.253.204.63 |
| 5| 3|172.253.204.64 |
| 5| 4|172.253.204.65 |
| 5| 5|172.253.204.66 |
ok
2005-02-14 18:03:43.13
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 72/300

RNC & NodeB Health Check for NEV 4.2- How To

4.9.2 Connection to a PMC


Identify the Virtual Router bearing the LocalMedia
then open a telnet session on the concerned board.
telnet ip(@IPaddress) vr/x
Example:
5> d vr/* pp/*
Vr/* Pp/*
Use -noTabular to see hidden attributes: atmAddress.
+========+====================+------+-----+----+-----+----|
Vr
|
Pp
|snmpOp|osiAd|osiO|osiUs|ifInd
|
|
|erStat| min |per | age | ex
|
|
| us |
|
|
|
+========+====================+------+-----+----+-----+----|0
|NODEBSOAM0
|up
|unlck|ena |activ|
23
|0
|OAMENET0
|up
|unlck|ena |activ|
15
|1
|INCNEXCHANGES
|up
|unlck|ena |activ|
25
|1
|IUPS0
|up
|unlck|ena |activ|
26
|1
|LOCALMEDIA
|up
|unlck|ena |activ|
28
ok
2005-02-15 12:44:28.27

the protocol port Local Media is supported by virtual router vr/1


to open a telnet session on the PMC-M active :
telnet ip(172.253.209.79) vr/1

4.9.3 CID use redundancy


Open a telnet session on both PMC master (active and slave) and compare the results of
the following commands
showTbmAllAllocCid()
it shows the list of all allocated and committed CID.
In the example given cid 8, 9 and 10 are used on the pathGroup 4.
rmanCaCallDbInfo
gives the detail of the cell(s) up or the calls established.
The results should be the same on PMC master active and slave.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 73/300

RNC & NodeB Health Check for NEV 4.2- How To

-> showTbmAllAllocCid
"showTbmAllAllocCid" is overloaded - Please select:
1: showTbmAllAllocCid(int)
2: showTbmAllAllocCid(void)
Enter <number> to select, anything else to stop: 2
Apr 19 2006
17:54:24.951
-------------------------------------------------------| Cid State for PG = 0x8 aal2If = 2 Path = 0x20
| nextIdleCidIndex = 12, CidId[20]
-------------------------------------------------------[8], [9], [10], [11], [12], [13], [14], [15],
-------------------------------------------------------| Cid State for PG = 0x4 aal2If = 1 Path = 0x10
| nextIdleCidIndex = 12, CidId[20]
-------------------------------------------------------[8], [9], [10], [11], [12], [13], [14], [15], [16], [17], [18], [19],
value = 0 = 0x0

NB: If the ShowTbmAllAllocCid doesnt show you the allocated cids on the PMC slave,
you can use showTbmPgAllocCid, or showTbmAal2AllocCid, etc, these commands can
give you the corresponding cids on the PMC slave. The ShowTbmAllAllocCid will be
replaced by ShowTbmAal2AllocCid from V4.2.4.
-> showTbmAllAllocCid
"showTbmAllAllocCid" is overloaded - Please select:
1: showTbmAllAllocCid(int)
2: showTbmAllAllocCid(void)
Enter <number> to select, anything else to stop: 2
Apr 19 2006
17:41:42.390
value = 0 = 0x0
-> showTbmAal2AllocCid(2)
Apr 19 2006
17:54:41.662
-------------------------------------------------------| Cid State for aal2If = 2 Path = 0x18
--------------------------------------------------------------------------------------------------------------| Cid State for aal2If = 2 Path = 0x20
-------------------------------------------------------[8], [9], [10], [11], [12], [13], [14], [15],
value = 0 = 0x0
-> showTbmAal2AllocCid(1)
Apr 19 2006
17:54:58.638
-------------------------------------------------------| Cid State for aal2If = 1 Path = 0x8
--------------------------------------------------------------------------------------------------------------| Cid State for aal2If = 1 Path = 0x10
-------------------------------------------------------[8], [9], [10], [11], [12], [13], [14], [15], [16], [17], [18], [19],
value = 0 = 0x0

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 74/300

RNC & NodeB Health Check for NEV 4.2- How To

rmanCaCallDbInfo (result truncated)


Displays the callDatabase detailed info.
In this example, there are two cells up.
The notion of call is used for a CELL or an UE call.
This cell (CallId = 56) is identified through its lg/cg (logical group / callgroup) 25 / 28.
A logical group is a group of application (Cell/UE) resources in one PMC.
Here 4 TLR (transport layers) are used, declined through 4 different CID 11,10,9 and 8
(certainly for PCH, FACH_0, FACH_1, and RACH ).
This command is quite useful to distinguish the cells from the calls compared to
showTbmAllAllocCid() or showTbmAal2AllocCid().
-> rmanCaCallDbInfo
May 10 2006
18:22:14.084
--- Begin to list the call DB info--CallId = 56
rpmId.lg:25/entityId:1
CELL Call
Call state: stable
This call is not pending for audit
This call has AppAct flag unset
Lg=25
Cg=28
This call has 4 TLRs, and they are:
TLR no. 1 is
aal2PathGroupId
= 4
cid
= 11
a2p
= 16
ownerAccessHandle = 28
ownerContextId
= 589839
TLR no. 2 is
aal2PathGroupId
= 4
cid
= 10
a2p
= 16
ownerAccessHandle = 28
ownerContextId
= 393230
TLR no. 3 is
aal2PathGroupId
= 4
cid
= 9
a2p
= 16
ownerAccessHandle = 28
ownerContextId
= 327693
TLR no. 4 is
aal2PathGroupId
= 4
cid
= 8
a2p
= 16
ownerAccessHandle = 28
ownerContextId
= 524300

To check the CID allocation redundancy, the results provided must be the same on PMCMaster active and slave.
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 75/300

RNC & NodeB Health Check for NEV 4.2- How To

rmanCaLgDbInfo
lists all created Lgs
can be used to find which PMC is bearing a spare LG.
The hwid (hardware id) will identify this PMC.
If the hwid is LAA, the PMC will be lp/L ap/(AA-2)
Example (result truncated):
In the previous result, the cells LG was 25.
-> rmanCaLgDbInfo

There are 2 Lg in spareActiveCellLgList, they are:


Active ->The invoked LG info:-> id=25
active
hasMate
lgCaLgStateReady_c
...its spared LG is in PMC 402 .The invoked LG info:-> id=25
inactive
hasMate
lgCaLgStateReady_c

The spare LG is on PMC 402 => lp/4 ap/0


rmanCaPmcRabList
To list the PMC rab Ip address.
-> rmanCaPmcRabList
May 10 2006
18:42:05.638
===The following Pmc-rabs are ready for call creation:===
--> HwId =0x204 and its private Ip addr: 172.253.208.81
--> HwId =0x205 and its private Ip addr: 172.253.208.82
--> HwId =0x207 and its private Ip addr: 172.253.208.84
--> HwId =0x304 and its private Ip addr: 172.253.208.75
--> HwId =0x305 and its private Ip addr: 172.253.208.76
--> HwId =0x307 and its private Ip addr: 172.253.208.78
--> HwId =0x402 and its private Ip addr: 172.253.208.67
--> HwId =0x405 and its private Ip addr: 172.253.208.70
--> HwId =0x502 and its private Ip addr: 172.253.208.61
--> HwId =0x505 and its private Ip addr: 172.253.208.64
---Totally there are 10 avaliable Pmc-rab!--value = 46 = 0x2e = '.'

For more commands with rmanCa (resource manager central agent), you can type
rmanCaHelp.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 76/300

RNC & NodeB Health Check for NEV 4.2- How To


-> rmanCaHelp
** Attention: This PMC is running as active PMC-m! **
************************************************************************
Welcome to RmanCa/Bienvenue a RmanCa.
This debug tool is designed for field support and rman module designer.
The following tools are available for PMC-m!
rmanCaPmcStatus
- display PMC-m and PMC-rab's status
DisplayPmcDownList- list all down in progress PMC-rab's HwId
rmanCaPmcRabList - list all avaliable PMC-rab's HwId
rmanCaLgInfo
- display all active Lgs info by Pmc-rab
rmanCaLgInfoPerPmc(pmcHwId) - display all active Lgs info in specified Pmc-rab
rmanCaLgDbInfo
- display the lgDatabase info(detailed)
rmanCaLgList
- list all created Lgs
DisplayResetLgList- list all Lgs in reset state
rmanCaShowSwactLists - displays the Lgs waiting to swact
rmanCaCallInfo
- display all created Calls info by Pmc-rab and its Lgs
rmanCaCallInfoPerPmc(pmcHwId) - display all created Calls info in specified
Pmc-rab and its Lgs
rmanCaCallDbInfo - display the callDatabase info(detailed)
rmanCaCallList
- list all created calls
rmanStats (RabId) - list the stats for the specified Rab
rmanCaDumpTraceKeys
- display all traceKeys info
rmanCaDumpTraceKeysPerPmc(pmcHwId) - display all traceKeys info for a
specified pmc-rab
rmanCaCallCid(traceKey) - display all the allocated Cids info for a specified
call
rmanCaCellAuditStatus
rmanCaTurnOffCellAudit
rmanCaTurnOnCellAudit

- display current cell audit status


- turn off cell audit
- turn on cell audit

startBackgroundCellAuditNow - immediately start background cell audit


rebalanceAllCellandUeLgs

- rebalance all cell and ue LGs in the system

ActiveRmanCaInvokeAudit

- Invoke RmanCa audit

rmanCaTool

- display all the above info

rmanCaNextRabCell
- display the Rab Id of the next Cell call
rmanCaSetRabUe(n,RabId)
- Set a Rab to take n number of Ue calls
rmanCaSetRabCell(n,RabId) - Set a Rab to take n number of Cell calls
rmanCaSetRabNoCall(Int16 RabId, bool acceptCall = false, bool CellCall = false)
- Set a Rab to reject/accept calls
rmanCaSetRabSparedCell(n,RabId,CardId) - Set a Rab to take n number of
rmanCaSetMaxResetIndvCall - Set the maxnum outgoing reset Individual call
request to CNode between 0 to 255.
rmanLbCaSetMaxnum_In_Lg(Maxnum_in_lg) - Set UE calls/Rab to 128/256
display_callResetWaitingQueue - Display the content in callResetWaitingQueue.
rmanHelp
- rman tools help
printLbCacTables
- displays eagerness values of the PMCs and the last
chosen PMC
rmanSwactMgrState
- display rman swact manager's state.
getRmanCaCellInfo
- display cell related data in RmanCa
************************************************************************
value = 73 = 0x49 = 'I'
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 77/300

RNC & NodeB Health Check for NEV 4.2- How To

5 NODEB
5.1. How to connect and navigate on a NodeB
telnet @bts_ip_address
If you dont know the IP address of a bts, you can get it with wicl and connect it via the
omc.
>: utran list children
RNC BTSEquipment NodeB Site ATMProfile TraceSession TraceRecord TraceFilter
Trac
eSessionTemplate Operator externalAlarmMappingTable POC Cluster PMCluster
>: utran list BTSEquipment
To be used if the list of BTSEquipment is not too big
[]
{BTSEquipment BTS_193983} {BTSEquipment BTS_276862} {BTSEquipment BTS_194
014}
[]
>: rnc RNC_1202 list NodeB
To be used when the name of the RNC is known
{RNC RNC_1202 NodeB BTS_194014} {RNC RNC_1202 NodeB BTS_RED205}
>: BTSEquipment BTS_194014 get ipAddress
10.50.2.90

The connection will be by default into the CCM board.


Menus available:
Enter $$$ to get the menu > $$$
$$$ close a dialogue
RTC user waiting input
EMO user waiting input
COR user waiting input
New in V4.2
SEP user waiting input

III user waiting input New in V4.2


CAP
IUB
RIB
IMT

user
user
user
user

waiting
waiting
waiting
waiting

input
input
input
input

To come back at the root prompt and in order to change menu type : $$$
In a menu, to go up in a directory : top (if the top command doesnt work, type h to see
available commands that will allow navigation).
To list the commands of a menu: help or h
CCM-EMOAM>help
========= EMOAM DEBUG MENU =========
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 78/300

RNC & NodeB Health Check for NEV 4.2- How To


Alarm

BOard Info

Alarm sub-menu

Board Information

New in V4.2

Bts
Bts Config summary
CompileInfo
Compile Information
Data
Data sub-menu
Debug
Debug sub-menu
DELay
Delay Propagation summary
Drivers
Drivers sub-menu
Flr
FLR messages sub-menu
Help
List of commands
Ima
IMA sub-menu
LCell
Local Cell summary

Passive
Radio
Slave

StatusBts
TimeStamp
Verbose

Passive sub-menu

New in V4.2

Radio sub-menu
Slave sub-menu

Status BTS sub-menu


Time Stamp sub-menu

New in V4.2
New in V4.2

Save Verbose File

5.2. HW, SW and radio check


Enter the EMO menu.
Enter $$$ to get the menu > EMO
ICCM-EMOAM> bts
--------------------------------------------- Packaging ------------------------------------------------iBTS : Indoor (600mm)
|
|
|
|
|
|
|
|
|
|
|
|
|
Logical slot
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
Physical slot
| _ | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | __ | 10 |
|
|
|
|
|
|
|
|
|
|
|
|
|
------------------------------------------- Configuration ----------------------------------------------Radio Mode ............................ OTSR-1
NODEBCP ASU ........................... Connected
NCP connected
Connected to the OMC
OMCB ................................. Connected
BTS built
MIBState .............................. Build
CheckDLU .............................. OK
Flip-Flop ............................. Not actif
Version ............................... UNB04D21230
Software version
TRM Master
DDM master ............................ TRM 3
---------------------------------------- Hardware Snapshot ---------------------------------------------Slot | Type
| HwRel |
Serial Number
|
PEC
|
Module Name
5 |
iCCM |
D1 |
NNTM7504DL6U |
NTUM25CM |
MOD:ICCM2BOARD
--------------------------------------------------------------------------------------------------------3 |
TRM |
D9 |
NNTM7503BYGV |
NTUM10AA |
MOD:TRM2100
7 |
CEM |
E8 |
NNTM7503D8PB |
NTUM00AA |
MOD:CEMALPHA
8 | iCEM128 |
P01 |
CDN200441004 |
NTUM00DB |
MOD:ICEM2128
--------------------------------------------------------------------------------------------------------12 |
GPSAM |
D4 |
NNTM7503F6XA |
NTUM24AA |
MOD:GPSAM
--------------------------------------------------------------------------------------------------------0 |
DDM |
D2 |
PALD01400554 |
NTUM40AA |
MOD:DDM2100UMTS
1 |
DDM |
D7 |
FORM01350613 |
NTUM40AA |
MOD:DDM2100UMTS
2 |
DDM |
D5 |
FORM01286701 |
NTUM40AA |
MOD:DDM2100UMTS
0 |
PA |
01 |
ANDWCS00GPRN |
NTUM30CA |
PA:MCPA21003045WUMTS
1 |
SPLIT |
D02 |
ANENCF000057 |
NTUM50AA |
MOD:TXSPLITTER2100UMTS
------------------------------------ Slaves State management -------------------------------------------Slot | Type
| Soft
|
Hard
|
Admin
| ConfStat | OpState |
UTime
| L3 Connected
3 |
TRM | Soft ok |
Enable | Unlocked | Config ok | Enable | XXXXXXXXX |
L3 complete
7 |
CEM | Soft ok |
Enable | Unlocked | Config ok | Enable |
Synchro |
L3 complete
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 79/300

RNC & NodeB Health Check for NEV 4.2- How To


8 | iCEM128 | Soft ok |
Enable | Unlocked | Config ok | Enable |
Synchro |
L3 complete
--------------------------------- OAM CallP and ATM Configuration
CP status
Slot | Type
| Declared To Callp |
CCP AAL5
|
AAL2 (0)
|
AAL2 (1)
|
AtmHandle
3 |
TRM |
Declared |
None
|
None
|
None
|
0x101b
7 |
CEM |
Declared |
0x1020
|
0x101e
|
0x101f
|
0x101c
8 | iCEM128 |
Declared |
0x1023
|
0x1021
|
0x1022
|
0x101d
---------------------------------------- RF LINK Configuration -----------------------------------------Slot | Type
|
LHP reserve
|
FwdCemToAdder
|
FwdAdderToTrm
|
RvCemToTrm
3 |
TRM |
YES | XXXXXXXXXXXXXXXXXXXXXXX |
YES |
YES
7 |
CEM |
YES |
YES | XXXXXXXXXXXXXXXXXXXXX |
YES
8 | iCEM128 |
YES |
YES | XXXXXXXXXXXXXXXXXXXXX |
YES
------------------------------------------- CCP informations
CCP status
Slot | Type
|
CCP Allocated
|
CCP State
|
CCP Status
7 |
CEM |
1 |
Enable |
Used
8 | iCEM128 |
2 |
Enable |
Used
------------------------------------------- CEM BBUs Load Configuration New in V4.2
Slot | Type
|
BBU0
|
BBU1
|
|
requested
|
current
|
requested
|
current
7 |
CEM |
DCH |
DCH |
DCH |
DCH
8 | iCEM128 |
HSDPA |
HSDPA |
DCH |
DCH
--------------------------------------------------------------------------------------------------------Tx Logical Cell | Physical objects mapping
/| Enable
/ | TRM 3
12054 |
\ | PA 0
\| DDM 0

/|
/ |
0 |
\ |
\|

Disable
TRM 0
PA 0
DDM 0

/|
/ |
0 |
\ |
\|

Disable
TRM 0
PA 0
DDM 0

/|
/ |
0 |
\ |
\|

Disable
TRM 0
PA 0
DDM 0

/|
/ |
0 |
\ |
\|

Disable
TRM 0
PA 0
DDM 0

/|
/ |
0 |
\ |
\|

Disable
TRM 0
PA 0
DDM 0

RF Cabling :
___________________
TRM |___________________|3
|
|
|
_|_
PA
\ /0
V
|
___|_________________
|
TX SPLITTER
|0
|_____________________|
|
|
|
_|_
_|_
_|_
DDM |
|0 |
|1 |
|2
|___| |___| |___|
+-------------------------------------------------------------------------------+
|
Tx Propagation Delay
|
+-------------------------------------------------------------------------------+
| Local Cell Id | Ccm | Trm | Pa | Tx Splitter | Ddm | RFoutput to Antenna |
+-------------------------------------------------------------------------------+
|
12054 | 902 | 1929 |
10 |
1 |
3 |
14 |
+-------------------------------------------------------------------------------+
|
Rx Propagation Delay
|
+-------------------------------------------------------------------------------+
| Local Cell Id |
Ccm
|
Trm
|
Ddm
|
Antenna To RFinput
|
+-------------------------------------------------------------------------------+
|
12054 |
932 |
860 |
4 |
20 |
+-------------------------------------------------------------------------------+
|
Tx and Rx Total Propagation Delay
|
+-------------------------------------------------------------------------------+
| Local Cell Id |
Dl Main
|
Dl Div | Ul Main/Div |
Local Cell State |
+-------------------------------------------------------------------------------+
|
12054 |
2859 |
0 |
1816 |
Enable |
+-------------------------------------------------------------------------------+
|
Cell Delay Propagation Send to Cem State
|
+-------------------------------------------------------------------------------+
|
Cem Slot
|
Local Cell Id
|
CellDelaySentToCem
|
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 80/300

RNC & NodeB Health Check for NEV 4.2- How To


+-------------------------------------------------------------------------------+
|
7 |
12054 |
CELL DELAY OK |
|
8 |
12054 |
CELL DELAY OK |
+-------------------------------------------------------------------------------+
ICCM-EMOAM>

5.3. Check that the BTS is radiating and the common channels SCCPCH
(PCH, FACH) are up and running.
Shows radio operational state, channel state, NodeBCP and CCP states.
EMO /rad/op
Displays the Radio Object Operational State.
CAP/ctx/ctch
Displays Information on Common Transport Channels
To go back to the root menu $$$, or top to go up in the directory (as many times as
needed).
CCM-EMOAM>$$$
End of dispatcher session
Enter $$$ to get the menu > EMO
CCM-EMOAM>rad
ICCM-EMOAM/RAD>ops
========= Radio Operational State =========
========= Local Cell OpState =========
==========================
localCellId : 12050
Cell OpState : Disable
Issue on this cell (wont go up)
==========================
localCellId : 12054
Local Cell Id 12054
Cell OpState : Enable
Cell operational
========= NodeBCP OpState =========
OpState
: STATE_OK
NCP operational
========= CCP OpState =========
CCP 1 operational
CcpId
: 1
CCP OpState : STATE_OK
CcpId
: 2
CCP 2 operational
CCP OpState : STATE_OK
Enter $$$ to get the menu > cap
ICCM-Callp/ctx> ctch
ICCM-Callp/ctx/ctch> d
physical channel id:
physical channel type:
slot format:
rncuc id:
carrier id:
rach id:
rach pathid:

16
PRACH
3
0
2054
10
32

PRACH is operational
Cell Id 2054

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 81/300

RNC & NodeB Health Check for NEV 4.2- How To


RACH CID

rach ext CID:

11

physical channel id:


physical channel type:
slot format:
rncuc id:
carrier id:
fach id:
fach pathid:
fach ext CID:
fach id:
fach pathid:
fach ext CID:
pch id:
pch pathid:
pch ext CID:

20
SCCPCH
8
0
2054
2
32
9
3
32
10
1
32
8

SCCPCH is operational

FACH CID
FACH CID
PCH CID

In the above case, the cell 2054 is operational and is radiating.


In case the cell is locked from the OMC, no information will be displayed in the
command cap/ctx/ctch/detail
5.4. Iub status
Enter $$$ to get the menu > III
ICCM-IubManager>iub_state
IUB Manager state = CONNECTED to the RNC

5.5. iBTS alarm history check


RTC /flr/display
In the FLR (flight recorder service) menu under rtc, first display the FLR configuration,
then dump the number of the last alarms you are interested in.
Enter $$$ to get the menu > rtc
CCM-RTC_TOOLS>flr
CCM-RTC_TOOLS/FLR>config
Flight recorder configuration
----------------------------id
Name
RAMsize EECsize
Address
Ram
Term
Flash
-------------------------------------------------------------------------0:S:
SwLogs
40000
5000
706088c
Yes
No
No
1:S:
SwErrs
40000
5000
706a4cc
Yes
Yes
No
2:S:
Alarms
10000
2000
707410c
Yes
No
No
3:S: HwError
0
0
fff80000
No
No
Yes
4:S:
Init
40000
10000
707681c
Yes
No
No
-----------------------------------------------------------------------

The id of the alarms is 2. They are only dumpled to ram (Ram Yes) and not displayed
(Terminal No) and this id will be used to display them:
d 2 5 = display the last 5 alarms.
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 82/300

RNC & NodeB Health Check for NEV 4.2- How To

CCM-RTC_TOOLS/FLR>d 2 5
Display last 5 records from Ram buffer
Alarms
-------------------------------------------------------CCM_EMOAM_ALARM_MGT> F5_Alarm_Indication_Signal

49

CLEARED at 2005-02-22 11:34:58

CCM_EMOAM_ALARM_MGT> F5_Alarm_Indication_Signal

35

CLEARED at 2005-02-22 11:34:58

CCM_EMOAM_ALARM_MGT> PCM_FAILURE_CRITICAL_FAULT

RAISED at 2005-02-22 11:17:13

CCM_EMOAM_ALARM_MGT> PCM_FAILURE_CRITICAL_FAULT

RAISED at 2005-02-22 11:17:13

CCM_EMOAM_ALARM_MGT> PCM_FAILURE_CRITICAL_FAULT

RAISED at 2005-02-22 11:17:13

CCM_EMOAM_ALARM_MGT> PCM_FAILURE_CRITICAL_FAULT

RAISED at 2005-02-22 11:17:13

5.6. Activ FFS


RTC /FFS/ls
FFS stands for flash file system.
2 out of 3 of the FFS present on the CCM boards will be used to store 2 different
software. The FFS will hold the active or passiv partition.
RTC /FM/print
Displays the partitions state
Enter $$$ to get the menu > rtc
CCM-RTC_TOOLS>fm
CCM-RTC_TOOLS/FM>pr
Flash File System State ...
Flash 0 (/ffs0)
Valid
: YES
Current
: YES
Probed
: YES
Next To Boot: YES
FlashType
: UMTS
File System : FFS
Flash 1 (/ffs1)
Valid
: YES
Current
: NO
Probed
: YES
Next To Boot: NO
FlashType
: UMTS
File System : FFS
Flash 2 (/ffs2)
Valid
: NO
Current
: NO
Probed
: NO
Next To Boot: NO
FlashType
: INVALID
File System : FFS
Flash 3 (/data)
Valid
: NO
Current
: NO

FFS0 is the active partition.


Will be the next partition used for
the next boot.

FFS1 is the passiv partition.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 83/300

RNC & NodeB Health Check for NEV 4.2- How To


Probed
:
Next To Boot:
FlashType
:
File System :

NO
NO
INVALID
FFS

FFS0 is therefore the active partition.


5.7. iBTS active SW version
Refer to 2. HW,SW and Radio check, the software version is displayed through /EMO/bts
For a much more difficult way but allowing to check the other versions installed:
RTC /FFS/ls
List files
Once the activ FFS determined, find out the software release, you may also check the
passiv partition if needed.
Reminder: the active FFS is 0 in this example.
The software may also be retrieved through EMO /bts .
Enter $$$ to get the menu > rtc
CCM-RTC_TOOLS>ffs
CCM-RTC_TOOLS/FFS>ls
Handle of FFS0
: 0
Handle of FFS1
: 1
Handle of FFS2 (CCM only) : 2
Handle of data flash
: 3
Handle of ram disk
: 4
Choice ? > 0
--- Root Directory Contents --InodeId Type Size
Filename
------- ---- -------- -------0 dir
8192 .
1
35956 bootl2ccm.fbin
2
2124014 bootl3ccm0d.fbin.zl
3
1682 emoamCommandFile
4
463475 uc_ccmOam.fbin.zl
5
29050 uc_ccmPm.fbin.zl
6
105967 uc_ccmSepe.fbin.zl
7
14670 uc_ccmTs.fbin.zl
8
611067 uc_ccmCallp.fbin.zl
9
1049819 TilApplet.jar
10
991815 AXEFpgaLoad.fbin.zl
11
98407 GPSAMFpgaLoad150.fbin.zl
12
108251 GPSAMFpgaLoad200.fbin.zl
13
14057 FILE0_UNB04D21240
Total Files:
14
CCM-RTC_TOOLS/FFS>ls
Handle of FFS0
: 0
Handle of FFS1
: 1
Handle of FFS2 (CCM only) : 2
Handle of data flash
: 3
Handle of ram disk
: 4

FFS0 is indeed the active partition.

Software in use.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 84/300

RNC & NodeB Health Check for NEV 4.2- How To


Choice ? > 1
--- Root Directory Contents --InodeId Type Size
Filename
------- ---- -------- -------0 dir
8192 .
1
35168 bootl2ccm.fbin
2
2150693 bootl3ccm0d.fbin.zl
3
444947 uc_ccmOam.fbin.zl
4
29048 uc_ccmPm.fbin.zl
5
101202 uc_ccmSepe.fbin.zl
6
14478 uc_ccmTs.fbin.zl
7
596132 uc_ccmCallp.fbin.zl
8
1046788 TilApplet.jar
9
14057 FILE0_UNB04D21240
10
1560 emoamCommandFile
11
991815 AXEFpgaLoad.fbin.zl
12
98407 GPSAMFpgaLoad150.fbin.zl
13
108251 GPSAMFpgaLoad200.fbin.zl
Total Files:
14

5.8. iBTS built? Configuration file


See 2. (/EMO/bts) to check if the BTS is built.
RTC /FFS/ls, RTC /MIM/lfid, RTC /MIM/mfr
A DLUxxxx.txt file stands for the configuration file perceived as the MIB for the NodeB.
Reminder: FFS0 holds the activ partition in our example.
Enter $$$ to get the menu > rtc
CCM-RTC_TOOLS>ffs
CCM-RTC_TOOLS/FFS>ms
>>>-dialog->>> command not found (ms)
CCM-RTC_TOOLS/FFS>ls
Handle of FFS0
: 0
Handle of FFS1
: 1
Handle of FFS2 (CCM only) : 2
Handle of data flash
: 3
Handle of ram disk
: 4
Choice ? > 3
--- Root Directory Contents --InodeId Type Size
Filename
------- ---- -------- -------0 dir
8192 .
1
218 uccm_logcmdfile
2
744 certificate.der
3
30 root_cmdfile.log
4
54 IC_FILE.TXT
5
107 LogFile
6
6350 FILE0_P
7
1536 IC_APPROVED_FILE
8
1536 IC_MIRROR_FILE
9
6310 DLU_40E1405E.TXT
10
6310 DLU_42039E89.TXT
11
6310 EOAM_CONF_M.TXT
12
6310 EOAM_CONF_B.TXT
13
6657 FILE0_A
14
6310 DLU_41AC9476.TXT
15
387 FLR_Trace
Total Files:
16
CCM-RTC_TOOLS/FFS>rtc

3 DLU files are present


The aim is to find which one is the
current configuration file

to go up

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 85/300

RNC & NodeB Health Check for NEV 4.2- How To


Management Information Module
lists the field id

CCM-RTC_TOOLS>mim
CCM-RTC_TOOLS/MIM>lfid
+---------------------+-----------+
| Field Name
| ID
|
+---------------------+-----------+
| HW REF
| 0x0001
|
| Next To Boot
| 0x0002
|
| Current To Boot
| 0x0003
|
| Plug & Play
| 0x0004
|
| FFS0 SW REF
| 0x0005
|
| FFS1 SW REF
| 0x0006
|
| FFS2 SW REF
| 0x0007
|
| FFS0 Conf REF
| 0x0008
|
| FFS1 Conf REF
| 0x0009
|
| FFS2 Conf REF
| 0x000a
|
| Upgrade Reguest
| 0x000b
|
+---------------------+-----------+
CCM-RTC_TOOLS/MIM>mfr 0x0008

Identifier of FFS0 (activ partition)

Read the field of FFS0


Gives the DLU file.

Field Value : 0x42039E89

The retrieved value allows to identify the correct DLU file.


The BTS is built and its configuration file is DLU_42039E89.TXT.
5.9. iBTS Commissionning Data Check
Enter $$$ to get the menu > emo
CCM-EMOAM/DAT>top
CCM-EMOAM>$$$
End of dispatcher session
Enter $$$ to get the menu > emo
CCM-EMOAM>dat
CCM-EMOAM/DAT>i2m
CCM-EMOAM/DAT/I2M>sim
|------------------------------------------------------------|
|
DUMP SPECIFIC "SIM" PARAMETERS FOR I2M APPLI
|
|------------------------------------------------------------|
SIM_DALLAS_PARAM ------------------------------------------ Dallas Serial Number
:0x680000001008C323
- Dallas Position In the RU
:0x1
- Number of dallas in the RU :0x1
- PIO A description
:0xFF
- PIO B description
:0xFF
SIM_INVENTORY_PARAM --------------------------------------- Appli Type SubType
:0x030110
- Ru Name
:"CAB: INDOOR PRECAB 600
"
- Prod Enginerring Code (PEC) :" NTBY70AA
"
- Serialisation Nb
:"
SNMN75006THN"
- Manuf Date
:"0902"
SIM_RELEASE_PARAM ----------------------------------------- Hardware release
:"E5 "
SIM_DATE_PARAM -------------------------------------------- Last In Service
:0x30303030
SIM_UPDT_RELEASE_PARAM ------------------------------------ Hardware release
:0x1
SIM_DELIV_CABINET_PARAM ----------------------------------- Serial Number
:"193983
"
- Manufacture Date
:"0802"
SIM_SITE_LOCATION_PARAM -----------------------------------

PEC Code
Useful !

BTS serial number

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 86/300

RNC & NodeB Health Check for NEV 4.2- How To


- Site Location
:"B2SUD
"
- Unit
:" "
- Floor
:" "
- Row
:"
"
SIM_UMTS_BTS_INFO_PARAM ----------------------------------- MCC
:"
"
- MNC
:" "
- Network element Id
:"GPS 10.20.80.10
SIM_GSM_BTS_INFO_PARAM ----------------------------------- MCC
:""
- MNC
:""
- Network element Id
:""

"

or (result truncated)
CCM-EMOAM/DAT/I2M>all
|------------------------------------------------------------|
|
DUMP ALL I&C PARAMETERS FOR I2M APPLI
|
|------------------------------------------------------------|
IC1 PARAMETERS----------------IC1_DALLAS_PARAM ------------------------------------------ Dallas Serial Number
:0x6600000010216023
- Dallas Position In the RU
:0x1
- Number of dallas in the RU :0x1
- PIO A description
:0xFF
- PIO B description
:0xFF
IC1_SHORT_INVENTORY_PARAM --------------------------------- Appli Type Subtype
:0x030120
IC1_UPDATE_RELEASE_PARAM --------------------------------- Update Release rec Length
:0x4
IC1_BTS_PARAM ---------------------------------------------- Functional mode
:0x1 (0:GSM 1:UMTS 2:DUAL 3:SPLIT)
- Type of bts
:0x2 (0:INDOOR700 1:OUTDOOR700 2:INDOOR600 3:COMPACT
4:STREET 5:INDOOR2 6:OUTDOOR2 7:MONO ...)
IC1_GSM_PARAM ---------------------------------------------- Bts identificator
:0x0
- Type of Abis interface
:0x0 (0:STD ABIS)
IC1_BACKHAUL_PARAM ----------------------------------------- Type of incoming link
:0x0 (0:PCM 1:STM1)
IC1_GPS_SYNCHRO_PARAM -------------------------------------- Number of GPS sources
:0x0
- Use of fallback sync on pcm :0x1 (0:NO 1:YES)
- Synchronization mode
:0x0 (0:FRAME 1:BURST)
- Synchronization delay
:0x0
IC1_SPLIT_MODE_PARAM --------------------------------------- Functional mode of ccm 0
:0x0
- Functional mode of ccm 1
:0x1
- Mask of slot of the digital shelf used by ccm 0:0x1C0
- Mask of slot of the digital shelf used by ccm 1:0xF
- Mask of pcm used by ccm 0
:0xF
- Mask of pcm used by ccm 1
:0xF0
IC1_PCM_PARAM ---------------------------------------------...
IC1_ADDRESS_PARAM ------------------------------------------ Existence of server DHCP
:0x0 (0:NO 1:YES)

- IP address of the bts


:0x0A14500A

- IP address of the OMC-B


:0x2FA44D86
- Port of the OMC-B
:0x189D
- Virtual path of the OMC-B
:0x0

- Virtual channel of the OMC :0x20


- Mask of sub-network
:0xFFFF0000

DHCP not used


0A.14.50.0A = 10.20.80.10
2F.A4.4D.86 = 47.164.77.134
OAM VP 0x0h = 0
OAM VC 0x20h = 32

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 87/300

RNC & NodeB Health Check for NEV 4.2- How To


-

Port of bts dhcp client


Service Category VC OMC-B
Rx PCR VC OMC-B
Rx CDVT PCR VC OMC-B
Rx SCR VC OMC-B
Rx CDVT SCR VC OMC-B
Rx MBS VC OMC-B
Tx PCR VC OMC-B
Tx CDVT PCR VC OMC-B
Tx SCR VC OMC-B
Tx CDVT SCR VC OMC-B
Tx MBS VC OMC-B

:0x189D
:0x3
:0x1D8
:0x000000
:0x1D8
:0x000000
:0x0F4240
:0xEC
:0x000000
:0xEC
:0x000000
:0x0186A0

5.10. iBTS Config Data (DLU file) check


Enter $$$ to get the menu > emo
ICCM-EMOAM>data
ICCM-EMOAM/DAT>cf
========= Dump the ConfigFile parameters =========
Config File version
: V 4.2
========= Bts Equipment parameters =========
BTS serial number length
: 25
BTS SerialNumber
: 999999
BTS Equipment Instance
: 0
Test Frequency
: 10638
SupervisedExternalAlarmMask : 0xffff
SupervisedUserAlarmMask
: 0x00
RakeMode
: 4
IubLossTimeout
: 20
CallPCommissioningMode
: Mode=0, CEM Slot=0
TraceMode
: 0
FrequencyBand
: 1
AntennaThreshold
: 20
antennaPowerMinSamples
: 1000
antennaFaultMaxCounter
: 100
antennaFaultDetecActivation : 0
bbVersion
: 65535
rmVersion
: 0
rxDemodulation
: 0
CCLTimeout
: 3
nbOmcbCnx
: 0
securityMode
: 0x00
timerCellImpactNoCcp
: 35
timerNodeBCPCellValidity
: 0
timerCommonNbap
: 40
repetitionCommonNbap
: 3
hsdpaMaxNumberUser
: 20
New in V4.2 (cf HSDPA chapter)
hsdpaResourceMaxCapacity
: 100

========= VCC parameters


VCC number
VCC VccId
[00]
VCC AdminState
[00]
VCC Vp
[00]
VCC Vc
[00]

=========
: 5
: 0
: 1
: 1
: 34

Gives the VCC configurations


NodeB CP (VCCId 0 is NCP)
VCC = 1.34
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 88/300

RNC & NodeB Health Check for NEV 4.2- How To


VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC
VCC

ExternalPortID
InterfaceType
Serv.Cat. Field
PCR
CDV PCR
SCR
CDV SCR
MBS
VccId
AdminState
Vp
Vc
ExternalPortID
InterfaceType
Serv.Cat. Field
PCR
CDV PCR
SCR
CDV SCR
MBS
VccId
AdminState
Vp
Vc
ExternalPortID
InterfaceType
Serv.Cat. Field
PCR
CDV PCR
SCR
CDV SCR
MBS
VccId
AdminState
Vp
Vc
ExternalPortID
InterfaceType
Serv.Cat. Field
PCR
CDV PCR
SCR
CDV SCR
MBS
VccId
AdminState
Vp
Vc
ExternalPortID
InterfaceType
Serv.Cat. Field
PCR
CDV PCR
SCR
CDV SCR
MBS

[00]
[00]
[00]
[00]
[00]
[00]
[00]
[00]
[01]
[01]
[01]
[01]
[01]
[01]
[01]
[01]
[01]
[01]
[01]
[01]
[02]
[02]
[02]
[02]
[02]
[02]
[02]
[02]
[02]
[02]
[02]
[02]
[03]
[03]
[03]
[03]
[03]
[03]
[03]
[03]
[03]
[03]
[03]
[03]
[04]
[04]
[04]
[04]
[04]
[04]
[04]
[04]
[04]
[04]
[04]
[04]

:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:

1
0
VBRrt, prio=0 (field value: 0x1)
4528
0
227
0
16
1
CCP1 (VCCid 1 is CCP)
1
1
35
VCC = 1.35
1
0
VBRrt, prio=0 (field value: 0x1)
4528
0
227
0
16
2
CCP1 (VCCid 1 is CCP)
1
1
36
VCC = 1.36
1
0
VBRrt, prio=0 (field value: 0x1)
4528
0
227
0
16
3
VCC = 1.41
1
VBRrt (realtime) = DS path
1
41
1
0
VBRrt, prio=0 (field value: 0x1)
4528
0
1115
0
192
4
VCC = 1.49
1
VBRnrt (nonrealtime)=NDS path
1
49
1
0
VBRnrt, prio=1 (field value: 0x2)
4528
0
2424
0
64

========= NodeBCP parameters =========


NodeBCP Instance
: 0
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 89/300

RNC & NodeB Health Check for NEV 4.2- How To


NodeBCP LossTempo
NodeBCP VccId

: 30
: 0

========= CCP parameters =========


CCP number
: 2
CCP Instance
[0] : 0
CCP Id
[0] : 1
CCP LossTempo
[0] : 30
CCP VccId
[0] : 1
CCP Instance
[1] : 1
CCP Id
[1] : 2
CCP LossTempo
[1] : 30
CCP VccId
[1] : 2
========= AAL2Bearer parameters
AAL2 Port Number
AAL2 Port[0] Instance
AAL2 Port[0] PathId
AAL2 Port[0] VccId
AAL2 Port[1] Instance
AAL2 Port[1] PathId
AAL2 Port[1] VccId

=========
: 2
: 0
: 32
: 3
: 1
: 24
: 4

Path Id used on the interface node


(d aal2If/* path/*)

========= Cell parameters =========


Cellule number
: 1
BtsCellInstance
[0]
: 0
LocalCellId
[0]
: 12054
LocalCellGroupId
[0]
: 0
PaRatio
[0]
: 100
CellSize
[0]
: 1
CellProfile
[0]
: 0
pmmThresholdHigh
[0]
: 10
pmmThresholdLow
[0]
: -5
pmmPowerControlWindow
[0]
: 2
pmmActivation
[0]
: 0
HsdpaResActiv
[0]
: 1
New in V4.2 (HSDPA)
nbHsdpaConf
[0]
: 1
hsdpaResourceId
[0]
: 0
HsdpaHsscchPcConfig
[0]
: 0 0 0 0 0 0 0 -30 -30 -50 -50 -50 -80 -80 -80 -80 -80 80 -80 -80 -80 -80 -80 -80 -80 -80 -80 -80 -80 -80
HsdpaHarqType
[0]
: 1
HsdpaMaxNbRetrans
[0]
: 7
HsdpaHsdschInterval
[0]
: 50
HsdpaMaxRateGrowth
[0]
: 8
HsdpaDchPowerMargin
[0]
: 20
AntennaConnection number [0]
: 3
Antenna Connection
[0]
: 1
Antenna Connection
[0]
: 2
Antenna Connection
[0]
: 3
MaxPowerAmplification
[0]
: 45
========= AntennaAccess parameters =========
AntennaAccess number
: 3
AntennaAccessInstance
[0]
: 0
Antenna Connection
[0]
: 1
ExternalAttenuationMainDl[0]
: 0
ExternalAttenuationMainUl[0]
: 0
ExternalAttenuationDivDl [0]
: 0
ExternalAttenuationDivUl [0]
: 0
TMA Access Type
[0]
: 0
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 90/300

RNC & NodeB Health Check for NEV 4.2- How To


External Uplink Delay
[0]
External Downlink Delay [0]
RxCabling
[0]
AntennaAccessInstance
[1]
Antenna Connection
[1]
ExternalAttenuationMainDl[1]
ExternalAttenuationMainUl[1]
ExternalAttenuationDivDl [1]
ExternalAttenuationDivUl [1]
TMA Access Type
[1]
External Uplink Delay
[1]
External Downlink Delay [1]
RxCabling
[1]
AntennaAccessInstance
[2]
Antenna Connection
[2]
ExternalAttenuationMainDl[2]
ExternalAttenuationMainUl[2]
ExternalAttenuationDivDl [2]
ExternalAttenuationDivUl [2]
TMA Access Type
[2]
External Uplink Delay
[2]
External Downlink Delay [2]
RxCabling
[2]

:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:

20
14
3
1
2
0
0
0
0
0
20
14
3
2
3
0
0
0
0
0
20
14
3

========= PCM parameters =========


PCM number
: 1
PCM Nb
[0]
: 0
AdministrativeState [0]
: 1
========= LocalCellGroup parameters =========
Local Cell Group number
: 1
LocalCellGroupInstance [0]
: 0
LocalCellGroupId
[0]
: 0
FrequencyGroupId
[0]
: 0
Priority
[0]
: 1
========= Backhaul Protocol Type =========
backhaulProtocolType
: 0 (PCM)
========= IMA Group parameters =========
(unsignificant value)
========= IP Interface parameters =========
IP Interface number
: 1
adminState
: 1
ipInterfaceInstance
: 0
ipInterfaceType
: 0
IfRole
: 0
IfId
: 0
========= Site LAN parameters =========
siteLanInstance
: 0
subNetworkAddress
: 0x0a029000
subNetworkMask
: 0xfffffff8
nbDevices
: 2
deviceType
[0]
: Reta
deviceIpAddress
[0]
: 0x0a029002
managerSpec
[0]
: 0
dnsServer
[0]
: 0x00000000
managerFQDN
[0]
:
managerAddress
[0]
: 0x00000000
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 91/300

RNC & NodeB Health Check for NEV 4.2- How To


deviceType
deviceIpAddress
managerSpec
dnsServer
managerFQDN
managerAddress

[1]
[1]
[1]
[1]
[1]
[1]

:
:
:
:
:
:

Laptop
0x0a029003
0
0x00000000
0x00000000

========= Cooling System Instance =========


coolingSystemInstance
: 0
========= Power System Instance =========
powerSystemInstance
: 0
========= Route CES =========
Route CES number

: 0

========= Counter Family =========


Counter Family number
: 0
========= RT OBS Session =========
NO RT OBS Session
========= COMPONENT
cabinet
shelf
slot
adminState
type
serialNumber
cabinet
shelf
slot
adminState
type
serialNumber
cabinet
shelf
slot
adminState
type
serialNumber
cabinet
shelf
slot
adminState
type
serialNumber
cabinet
shelf
slot
adminState
type
serialNumber
cabinet
shelf
slot
adminState
type
serialNumber
cabinet
shelf

parameters =========
[03]
: 0
[03]
: 0
[03]
: 3
[03]
: 1
[03]
: TRM 2100
[03]
:
[05]
: 0
[05]
: 0
[05]
: 65
[05]
: 1
[05]
: iCCM
[05]
:
[07]
: 0
[07]
: 0
[07]
: 7
[07]
: 1
[07]
: CEM
[07]
:
[08]
: 0
[08]
: 0
[08]
: 8
[08]
: 1
[08]
: iCEM 128
[08]
:
[12]
: 0
[12]
: 0
[12]
: 10
[12]
: 1
[12]
: GPSAM
[12]
:
[13]
: 0
[13]
: 1
[13]
: 1
[13]
: 1
[13]
: PA
[13]
:
[14]
: 0
[14]
: 1

NNTM7503BYGV

NNTM7504DL6U

NNTM7503D8PB

CDN200441004

NNTM7503F6XA

ANDWCS00GPRN

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 92/300

RNC & NodeB Health Check for NEV 4.2- How To


slot
adminState
type
serialNumber
cabinet
shelf
slot
adminState
type
serialNumber
cabinet
shelf
slot
adminState
type
serialNumber
cabinet
shelf
slot
adminState
type
serialNumber

[14]
[14]
[14]
[14]
[19]
[19]
[19]
[19]
[19]
[19]
[20]
[20]
[20]
[20]
[20]
[20]
[21]
[21]
[21]
[21]
[21]
[21]

:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:

2
1
TX SPLITTER
ANENCF000057
0
2
1
1
DDM
PALD01400554
0
2
2
1
DDM
FORM01350613
0
2
3
1
DDM
FORM01286701

5.11. To retrieve VCC for OAM, NCP, CCP , DS and NDS


The OAM VCC is configured in the I&C parameters, CCM-EMOAM/DAT/I2M>all gives the
OAM VCC (iBTS Commissioning Data Check).
The other VCC are found in the DLU file (see iBTS Config Data (DLU File) check).

5.12. CS & PS Call check


Two menus can be used to see the context of the cell and the established calls.
Enter $$$ to get the menu > cap
CCM-Callp>ctx
CCM-Callp/ctx>h
>> >> >> CCM Objects Contexts Show << << <<
------------------------------------------------Cell
Cell Context Show
CTCH
CTCH Context Show
Help
List of Commands
Ima
AvailableBandWith
ImaDebug
IMA Debug
OAM
OAM Context Show
Top
Return to CallP menu
UE
UE Context Show

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 93/300

RNC & NodeB Health Check for NEV 4.2- How To

Two cells are now up in our case, cell command gives the scrambling code,
frequencies,
Enter $$$ to get the menu >cap
ICCM-Callp>ctx
ICCM-Callp/ctx>cell
ICCM-Callp/ctx/cell>d
Rncuc Id
:
Cell Carrier Id
:
Local Cell Id
:
TCell
:
UL Frequency
:
DL Frequency
:
Max Transmission Power
:
Primary DL Scrambling Code:
Primary SCH Power
:
Secondary SCH Power
:
Primary CCPCH Power
:
BCH Id
:
Primary CPICH Power
:
Nb of physical channels
:
HSDPA service ACTIVATED :
maxTransmissionPowerHsdpa :
nbOfHSPDSCHCodes
:
startCodeNumber
:
nbOfHSSCCHCodes
:

0
2054
12054
0
9837
10787
420
90
-50
-50
-20
5
320
2

Must be divided by 10
The NodeB transmits at 42.0dBm
out of 45W allowed by the RNC
(see 9. MaxPowerAmplification)

397
10
6
2

A Channel IDentifier (CID) is associated to each logical channel (RACH, FACH, PCH)
into the delay sensitive (DS) path.
For each cell, there are 2 physical channels : PRACH (for RACH) and SCCPCH (for
FACH and PCH).
One CID is used per common channel, for one cell at least 3 CID are allocated (1 PCH, 1
RACH, 1 FACH) or why 4 if the cell uses a multi-fach configuration (1 PCH, 1 RACH, 2
FACH)
ctch command gives the configuration of the common channel.
Example:
for the cell 2042, 3 CID are used on the IuB, PathId 16:
o CID 9 FACH
o CID 10 RACH
o CID 11 PCH
For the cell 2041, 4 CID are used on the PathId 16 and 15:
o CID 8 PathId 15 PCH
o CID 8 PathId 16 FACH
o CID 9 PathId 16 FACH
o CID 10 PathId 16 RACH

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 94/300

RNC & NodeB Health Check for NEV 4.2- How To


Enter $$$ to get the menu >cap
ICCM-Callp>ctx
ICCM-Callp/ctx>ctch
ICCM-Callp/ctx/ctch>d
physical channel id:
physical channel type:
slot format:
rncuc id:
carrier id:
rach id:
rach pathid:
rach ext CID:

16
PRACH
3
0
2054
10
32
11

physical channel id:


physical channel type:
slot format:
rncuc id:
carrier id:
fach id:
fach pathid:
fach ext CID:
fach id:
fach pathid:
fach ext CID:
pch id:
pch pathid:
pch ext CID:

20
SCCPCH
8
0
2054
2
32
9
3
32
10
1
32
8

Physical Channel

Cell Id
Internal CID used for the NodeB
DS Path Id
CID used on the IuB

For signalling traffic (CS, PS), other CIDs are allocated on DS and NDS paths.
The ue command details the cid used for the calls established.
If no calls are established, this command wont dump any result.
CS call example:
CCM-Callp/ctx>ue
nodeBComCtxId: 17
crncComCtxId: 17
CCP Id:
1
nb DCH Groups: 2
Group_1 pathid=15 extCID=11 vpi=33 vci=8227 cid=11 1 signalling channel
DCH_1: id=5
Group_2 pathid=16 extCID=12 vpi=33 vci=8227 cid=12 1 traffic channel
DCH_1: id=1
with 3 transport channels
DCH_2: id=2
as expected for a call CS
DCH_3: id=3

PS call example:
CCM-Callp/ctx>ue
nodeBComCtxId: 18
crncComCtxId: 18
CCP Id:
2
nb DCH Groups: 2
Group_1 pathid=15 extCID=11 vpi=33 vci=8739 cid=13 1 signalling channel
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 95/300

RNC & NodeB Health Check for NEV 4.2- How To


DCH_1: id=5
Group_2 pathid=7 extCID=8 vpi=33 vci=8739 cid=12
DCH_1: id=4

1 NDS call

In case of a multiservice call, only the first established signalling channel will be
displayed.
5.13. Connection to other boards
EMO /bts
RTC /IP/connect boardnumber
To connect a board, first consult the hardware snapshot dumped by EMO /bts command,
CCM-EMOAM>bts

---------------------------------------- Hardware Snapshot ---------------------------------------------Slot | Type


| HwRel |
Serial Number
|
PEC
|
Module Name
3 |
TRM |
D9 |
NNTM7503CKYU |
NTUM10AA |
MOD:TRM2100
4 |
TRM |
E2 |
NNTM7503DCNI |
NTUM10AA |
MOD:TRM2100
5 |
CCM |
12 |
NNTM53306DKC |
NTGY25AA |
MOD:CCM
7 |
CEM |
E8 |
NNTM7503D8PB |
NTUM00AA |
MOD:CEMALPHA
8 | iCEM128 |
D2 |
CDN200321014 |
NTUM00DA |
MOD:ICEM128
12 |
GPSAM |
D4 |
NNTM7503CBQZ |
NTUM24AA |
MOD:GPSAM
280 |
DDM |
D5 |
FORM01279225 |
NTUM40AA |
MOD:DDM2100UMTS
281 |
DDM |
D5 |
FORM01280401 |
NTUM40AA |
MOD:DDM2100UMTS
282 |
DDM |
D5 |
FORM01280588 |
NTUM40AA |
MOD:DDM2100UMTS
256 |
PA |
D4 |
PWWT03D3J48C |
NTUM30AA |
PA:MCPA21003045WUMTS
258 |
PA |
D4 |
PWWT03D3J4KC |
NTUM30AA |
PA:MCPA21003045WUMTS
260 |
PA |
01 |
PWWT03D0GCFC |
NTUM30AA |
PA:MCPA21003045WUMTS
------------------------------------ Slaves State management -------------------------------------------

Example of a connection into the TRM in slot 3:


Enter $$$ to get the menu > rtc
CCM-RTC_TOOLS>ip
CCM-RTC_TOOLS/IP>connect 3

Then as for the CCM, $$$, help and top allow to navigate in the menus.
To disconnect: RTC /IP/disc
Enter $$$ to get the menu > rtc
DTRX-RTC_TOOLS>ip
DTRX-RTC_TOOLS/IP>disc

5.14. PCM & SYNCHRO check


The synchronisation alarms must be checked on the OMC.
To retrieve information about the synchronization (syn driver), and clock status:
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 96/300

RNC & NodeB Health Check for NEV 4.2- How To

Enter $$$ to get the menu > rtc


ICCM-RTC_TOOLS>syn
ICCM-RTC_TOOLS/SYN>info
+-----------------------------------+
|
SYN Information
|
+----------------------+------------+
| Algo version
|
10
|
| Interface version
|
1
|
| Debug mode
|
OFF
|
| DAC value
|
0x083D
|
| Clock source
|
E1/T1/0 |
| Holdover mode
|
OFF
|
| Activity board
|
ON
|
| Synchro
|
Locked
|
| Status
| 0x00000008 |
+----------------------+------------+

This status means that synchronization is operating


correctly

ICCM-RTC_TOOLS/SYN> sta
+--------------------------+
| SYN Status 0x00000008
|
+--------------------------+
| No alarm / No warning
|
+--------------------------+

To retrieve information on PCM configuration:


Enter $$$ to get the menu > rtc
ICCM-RTC_TOOLS/>pcm
ICCM-RTC_TOOLS/PCM>pcmp
PCM#A 0..7 ? 0
PCM#B 0..7 ? 1
PCM#C 0..7 ? 2
PCM#D 0..7 ? 3
+-----------+- PCM0 -+- PCM1 -+- PCM2 -+- PCM3 -+
| OperMode | 0x01 | 0x00 | 0x00 | 0x00 |
| MngtState | 0x01 | 0x00 | 0x00 | 0x00 |
| OperState | 0x01 | 0xfe | 0xfe | 0xfe |
| AvailStat | 0x00 | 0xaa | 0xaa | 0xaa |
| TestType | 0xff | 0xff | 0xff | 0xff |
+-----------+--------+--------+--------+--------+
| IntAIS
| 0x00 | 0x01 | 0x01 | 0x01 |
| ExtRAI
| 0x00 | 0x00 | 0x00 | 0x00 |
| ExtAIS
| 0x00 | 0x00 | 0x00 | 0x00 |
| TimeRef |06:29:30|00:00:00|00:00:00|00:00:00|
+-----------+--------+--------+--------+--------+
+-----------+ LOS + AIS + LFA + FE + CRC + RAI +
|
PCM0
|
|
|
|
|
|
|
|
PCM1
|
|
|
|
|
|
|
|
PCM2
|
|
|
|
|
|
|
|
PCM3
|
|
|
|
|
|
|
+-----------+-----+-----+-----+-----+-----+-----+

00..04:E1 05..07:T1
00:oos 01:is
01:ena FE:dis
00:on 55:tst AA:off FF:err
01..0E:test
FF:none
00:off 01:on
00:off 01:on< 02:on>
00:off 01:on

realtime

+-----------+RSLP+RSLN+TSLP+TSLN+TSHO+TRIS+dCRC+----+REXZ+RPDV+
|
PCM0
|
|
|
|
|
|
|
|
|
|
|
|
PCM1
|
|
|
|
|
|
|
|
|
|
|
|
PCM2
|
|
|
|
|
|
|
|
|
|
|
|
PCM3
|
|
|
|
|
|
|
|
|
|
|
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 97/300

RNC & NodeB Health Check for NEV 4.2- How To

To get statistical information on PCM alarms:


MALA indicates that statistics will come up on a minute basis. It is also possible to get it hourly.
Enter $$$ to get the menu > rtc
ICCM-RTC_TOOLS/>pcm
ICCM-RTC_TOOLS/PCM>pcms
PCM 0..7
? 0
Statistics ? mala
*** ALARMS STATISTICS 60min - Time

6:29:44 ***

MIN
60
59
58
57
56
55
54
53
52
51

LOS
0
0
0
0
0
0
0
0
0
0

AIS
0
0
0
0
0
0
0
0
0
0

LFA
0
0
0
0
0
0
0
0
0
0

FE
0
0
0
0
0
0
0
0
0
0

CRC
0
0
0
0
0
0
0
0
0
0

RAI
0
0
0
0
0
0
0
0
0
0

MIN
50
49
48
47
46
45
44
43
42
41

LOS
0
0
0
0
0
0
0
0
0
0

AIS
0
0
0
0
0
0
0
0
0
0

LFA
0
0
0
0
0
0
0
0
0
0

FE
0
0
0
0
0
0
0
0
0
0

CRC
0
0
0
0
0
0
0
0
0
0

RAI
0
0
0
0
0
0
0
0
0
0

FE
0
0
0
0
0
0
0
0
0
0

CRC
0
0
0
0
0
0
0
0
0
0

RAI
0
0
0
0
0
0
0
0
0
0

MIN
LOS AIS LFA
40
0
0
0
39
0
0
0
38
0
0
0
37
0
0
0
36
0
0
0
35
0
0
0
34
0
0
0
33
0
0
0
32
0
0
0
31
0
0
0
[]
ICCM-RTC_TOOLS/PCM> h

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 98/300

RNC & NodeB Health Check for NEV 4.2- How To

To get ATM statistics (number of cells sent or received) on the external ATM interfaces :
ICCM-RTC_TOOLS>
ICCM-RTC_TOOLS>connmanager
ICCM-RTC_TOOLS/ConnManager>flowcount
ICCM-RTC_TOOLS/ConnManager/FlowCounter>external
What kind of AAL external bearers counters do you want to display? ( 0 : AAL2, 1 : AAL5,
default: all ) 0
Do you want to display AtmConn external channels errors ? ( YES/NO )

yes

+------------------------------------------------------------------------------------------------------------------------------------+
+
External AAL5 counters Overview
+
+------------------------------------------------------------------------------------------------------------------------------------+
+
Identification
|
Counters
+
+
|
IUB Interface
|
End Point Interface
+
+ Handle | LogicalID | Ext Hdl|
VP
|
VC
|PortID| Cells Rcv | Cells Sent | Cells
Rcv | Cells Sent | Frames Rcv | Frames Sent+
+ 0x1017 | 0x6dfc0000 | 0x2000 | 0x0000 | 0x0020 | O L |
0x0f34
|
0x09bf
|
0x0f34
|
0x09bf
|
0x0573
|
0x0342
+
+ 0x1018 | 0x4d7c0000 | 0x2001 | 0x0001 | 0x0022 | O L |
0x33ee
|
0x38bc
|
0x33ee
|
0x38bc
|
0x33dc
|
0x38b7
+
+ 0x1020 | 0x53fc0000 | 0x2004 | 0x0001 | 0x0023 | 7 P |
0x3300
|
0x3300
|
0x32ff
|
0x32ff
|
0x32ff
|
0x32ff
+
+ 0x1023 | 0x547c0000 | 0x2005 | 0x0001 | 0x0024 | 8 P |
0x3300
|
0x3300
|
0x32ff
|
0x32ff
|
0x32ff
|
0x32ff
+
+------------------------------------------------------------------------------------------------------------------------------------+
+------------------------------------------------------------+
+
External AAL5 errors counters Overview
+
+------------------------------------------------------------+
+Handle | Abort Err |
Bad Lg
|
Bad Crc | Bad Size +
+ 0x1017 |
0x0000
|
0x0000
|
0x0000
|
0x0000
+
+ 0x1018 |
0x0000
|
0x0000
|
0x0000
|
0x0000
+
+ 0x1020 |
0x0000
|
0x0000
|
0x0000
|
0x0000
+
+ 0x1023 |
0x0000
|
0x0000
|
0x0000
|
0x0000
+
+------------------------------------------------------------+
+------------------------------------------------------------------------------------------------------------------------------------+
+
External AAL2 counters Overview
+
+------------------------------------------------------------------------------------------------------------------------------------+
+
Identification
|
Counters
+
+
|
IUB Interface
|
End Point Interface
+
+ Handle | LogicalID | Ext Hdl|VP
|
VC
|PortID| Cells Rcv | Cells Sent | Cells Rcv |
Cells Sent |
Cps Rcv | Cps Sent +
+ 0x1019 |
AAL2
| 0x2002 | 0x0001 | 0x0029 | 1 L |
0x09c0
|
0x09e0
|
|
|
|
0x1d00
+
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 99/300

RNC & NodeB Health Check for NEV 4.2- How To


+ 0x101a |
AAL2
| 0x2003 | 0x0001 | 0x0031 | 1 L |
0x0000
|
0x0000
|
|
|
|
0x0000
+
+------------------------------------------------------------------------------------------------------------------------------------+
+---------------------------------------------------------------------------------------------------------------+
+
External AAL2 errors counters Overview
+
+---------------------------------------------------------------------------------------------------------------+
+ Handle | Lost Cps | Stf Parity | Bad Sqc Nb |
Bad Hec | Bad Cps Lg | Lg Mismatch|
Bad Cid |
Osf>47
+
+---------------------------------------------------------------------------------------------------------------*

To get information on IMA configuration:


Enter $$$ to get the menu > rtc
ICCM-EMOAM>ima
ICCM-EMOAM/IMA>info
===============
IMA Emoam Info
===============
BTS is running in IMA mode:
IMA Defence is ACTIVATED
IMA Defence Delay:
0
IMA Internal Defence Timer is: NOT active
--------------Optional Emoam Ima Info:
IMA negotiated version: V1.1
Links (PCMs) configured in the IMA group:
Link 0 (PCM 1): ACTIVE
Link 1 (PCM 2): NOT active
Link 2 (PCM 3): NOT active
Link 3 (PCM 4): NOT active
Link 4 (PCM 5): NOT active
Link 5 (PCM 6): NOT active
IMA I&C parameters:
IMA Version:
V1.1
Frame Length:
128
Max Differential Delay:
2
Min Nr. of Active Links in Group: 1
Test Pattern Activation:
0
Alpha Parameter:
2
Beta Parameter:
2
Gamma Parameter:
1
===============
ICCM-EMOAM/IMA>

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 100/300

RNC & NodeB Health Check for NEV 4.2- How To

Enter $$$ to get the menu > rtc


ICCM-RTC_TOOLS>ima
ICCM-RTC_TOOLS/IMA>pgroup 0
|================================================================|
|
IMA group context
|
| Group index
0
|
| Remote IMA id
0
|
| near end state
Operational
|
| far end state
Operational
|
| group traffic state
UP
|
| group activated
Yes
|
| group failure status No failure
|
| near end version
version 1.1
|
| far end version
version 1.1
|
| near end M value
128
|
| far end M value
128
|
| number of configured links 6
|
| minimum
active links
1
|
| number of active links
1
|
|
link 0
Active
|
|
link 1
Not active
|
|
link 2
Not active
|
|
link 3
Not active
|
|
link 4
Not active
|
|
link 5
Not active
|
| near end TRL link 0
|
| far end TRL link 0
|
| LASR
link
255
|
| faster link
0
|
| slower link
0
|
| maximum differential delay 2
ms
|
| config abort timer
1
s
|
| start up ack timer
1
s
|
| LSM transition timer
1
s
|
| failure confirmation timer 3
s
|
| failure confirmation exit
10
s
|
| LASR retry timer
5
s
|
| LASR suspension timer
30
s
|
|================================================================|

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 101/300

RNC & NodeB Health Check for NEV 4.2- How To

6 OAM BASIC CHECKS


Here are some elementary checks if OAM application doesnt work properly.
6.1 Check status of all groups

% /opt/nortel/shell/sysmgt/wam_checkall.sh
Started groups:
ptf_oss
cem_primary
core_primary
ptf_hfb
ptf_infra
ptf_services
ptf_adaptor
ptf_trouble_ticket
utran
utran_3GPPbulkCM
utran_3GPPpmIRP
ptf_mdm
Nb started groups
: 12
Nb stopped groups
: 0
Nb undefined state groups: 0
The OMC is running

Number of stopped groups and number of undefined groups should be 0. The


number of started groups could be different to 12. Its depends on your configuration.
6.2 Check status of specific group
If some groups are partially started, for example:
Groups not started nor stopped:
ptf_services

Check in details which application is stopped in this group:


% /opt/nortel/shell/sysmgt/wam_checkgroup.sh <GroupName>

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 102/300

RNC & NodeB Health Check for NEV 4.2- How To

Check the number of application down. %Apps OK should be 100. Check that there are
not applications start or stop in progress.
% /opt/nortel/shell/sysmgt/wam_checkgroup.sh <GroupName> ptf_mdm
Nb supervised apps: 15
Nb apps down: 1
%Apps OK: 93
Automatic restart: on
Manual stop requested: yes
No start or stop in progress
ss_sysmgt_healthInfoServer/00113 22911 0.1 0.7 nortel/100 nortel/100
bubb/00100 22485 0.0 0.4 nortel/100 nortel/100
tumsbb/10207 23962 0.0 0.0 root/0 other/1
fmbb/10203 24269 0.0 0.0 root/0 other/1
sumbb/10205 25279 0.0 0.0 root/0 other/1
nt_albb/10201 26127 0.0 0.0 root/0 other/1
ccbb/10202 26128 0.0 0.0 root/0 other/1
cli_controller.x/00102 23529 0.0 0.4 nortel/100 nortel/100
cli_profilemanager.x/00103 23055 0.0 0.3 nortel/100 nortel/100
cli_jobScheduler.x/00104 24106 0.0 0.2 nortel/100 nortel/100
fmk_dfssrv.x/00106 23097 0.0 0.2 nortel/100 nortel/100
fmk_tlssrv.x/00107 24117 0.1 0.2 nortel/100 nortel/100
int_xdrf/00110 23142 0.1 1.2 nortel/100 nortel/100
int_mdm_pp_prov.x/00109 23726 0.0 0.3 root/0 nortel/100
int_mdm_med/00108 Stopped 0.0 0.0 none none

6.3 Restart one application in the group


If one or several applications are stopped and not start in progress, you can try to restart
them.
% /opt/nortel/shell/sysmgt/wam_startoneapp.sh
<appType>/<appInstance>

% /opt/nortel/shell/sysmgt/wam_startoneapp.sh

<groupName>

ptf_services int_mdm_med/00108

Check that the application was started correctly.


6.4 Restart one group
You can also restart all entire group. You need to stop the group if not all applications are
stopped. To find groupName you can run /opt/nortel/shell/sysmgt/wam_checkall.sh
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 103/300

RNC & NodeB Health Check for NEV 4.2- How To


% /opt/nortel/shell/sysmgt/wam_stopgroup.sh

<groupName>

% /opt/nortel/shell/sysmgt/wam_startgroup.sh

<groupName>

6.5 Restart all groups


Sometimes it could be nessecary to stop all groups and restart all groups.
% /opt/nortel/shell/sysmgt/wam_stopall.sh

% /opt/nortel/shell/sysmgt/wam_startall.sh

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 104/300

RNC & NodeB Health Check for NEV 4.2- How To

6.6 SMC alarms check


Check in the NSP if you have any critical alarms in SMC (Sun Management Center. The
number of critical alarms is indicated at the left bottom of the NSP main window. Here in
the example there are two critical alarms.

If you need to have more information on these alarms, you should start SMC either from
the NSP (double click on the left bottom) either from the command line:
set your display
% setenv DISPLAY xx.xx.xx.xx:0.0
start SMC
% /opt/SUNWsymon/sbin/es-start -c

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 105/300

RNC & NodeB Health Check for NEV 4.2- How To

Login with the same user as in the NSP and give the server name. Select impacted server
icon and double click.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 106/300

RNC & NodeB Health Check for NEV 4.2- How To

Select Alarms menu to check alarms.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 107/300

RNC & NodeB Health Check for NEV 4.2- How To

7 HOW TO
7.1. How To Wicl
Find the class under an object with wicl
For example: find the software of an IN or CN
Magic command: list chidren.
To launch wiclsh (on line shell)
On the omc server :
/opt/nortel/shell/wicl/wiclsh

login / password to use: the same used to open a GUI session.


To have the list of the RNC connected to an OMC
utran list rnc

You have to use the exact name given by the list (case sensitive) to invoke its sub-objects.
The helpful commands are :
Display (or dis) displays the attributes of an object
list
list children
to list the subobjects of an object
get
gets the value of an attribute.

Example given here to retrieve the CNODE software.


1. connection to wicl
2. rnc identification
3. search for the CNode Software object
4. get the value of the software
bonaire:/opt/nortel/shell/wicl <33> (nortel) % wiclsh
--------------------------------------------------------Starting Wireless Internet Command Language
--------------------------------------------------------Command mode launched
login : admin
password : admin
....wait please
Wireless Internet Command Language (WICL)
>: utran list rnc
{RNC RNC507} {RNC RNC_1201} {RNC RNC_1205} {RNC RNC502} {RNC RNC_1207}
>: RNC RNC_1207 list children
CallTrace GSMNeighbour PsCoreNetworkAccess RNCEquipment NodeB
RadioAccessService CsCoreNetworkAccess NeighbouringRNC MtpSignPoint PerfScanner
RncMIB RouteSet ObjectTrace
>: RNC RNC_1207 list RNCEquipment
{RNC RNC_1207 RNCEquipment 0}
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 108/300

RNC & NodeB Health Check for NEV 4.2- How To

>: RNC RNC_1207 RNCEquipment 0 dis


class
dn
OAMlinkAdministrativeState
operatorId
unknownStatus
upgradeStatus

RNCEquipment
(RNC,258)(RNCEquipment,0)
unlocked
0
unknownstatusfalse
IDLE

>: RNC RNC_1207 RNCEquipment 0 list children


CNode ANode INode
>: RNC RNC_1207 RNCEquipment 0 list CNode
{RNC RNC_1207 RNCEquipment 0 CNode 0}
>: RNC RNC_1207 RNCEquipment 0 CNode 0 dis
activeIPAddress
10.20.2.10
availabilityStatus
{ degraded }
class
CNode
dn
(RNC,258)(RNCEquipment,0)(CNode,0)
ipAddress
10.20.2.10
mibSynchronization
on
neId
10.20.2.10
operationalState
enabled
operatorId
0
secondaryIPAddress
10.20.2.11
siteName
SITE_RNC_1207
systemRelease
03_00_01
unknownStatus
unknownstatusfalse
upgradeStatus
IDLE
userSpecificInfo
Default_CNode

>: RNC RNC_1207 RNCEquipment 0 CNode 0 list children


OMU MMS TMU CC1 CNodeSoftware
>: RNC RNC_1207 RNCEquipment 0 CNode 0 list CNodeSoftware
{RNC RNC_1207 RNCEquipment 0 CNode 0 CNodeSoftware 0}
>: RNC RNC_1207 RNCEquipment 0 CNode 0 CNodeSoftware 0 dis
class
CNodeSoftware
dn
(RNC,258)(RNCEquipment,0)(CNode,0)(CNodeSoftware,0)
fallbackSoftwareVersion
unknown
fallbackSoftwareVersionDeliveryName
unknown
operatorId
0
runningSoftwareVersion
RC31c52043600
runningSoftwareVersionDeliveryName
RC31c52043600

>: RNC RNC_1207 RNCEquipment 0 CNode 0 CNodeSoftware 0 get


runningSoftwareVersion
RC31c52043600

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 109/300

RNC & NodeB Health Check for NEV 4.2- How To

7.2. How To retrieve the IP address of the nodes

7.2.1. Control Node Addresses


Open a Wicl session on the OMC
/opt/nortel/shell/wicl/wiclsh

login / password : the same used for the GUI session


Retrieve the RNC name and display the active ip address (example : RNC 1207)
>: utran list rnc
{RNC RNC507} {RNC RNC_1201} {RNC RNC_1205} {RNC RNC502} {RNC RNC_1207}
>: RNC RNC_1207 RNCEquipment 0 CNode 0 get activeIPAddress
10.20.2.10

For the RNC1500 see also paragraph 2.3. RNCIN object evolution oam OMU addresses.
7.2.2. Interface Node addresses
To retrieve a passport IP address, the presides configuration file can help:
saba:/opt/nortel <105> (nortel) % more /opt/MagellanNMS/cfg/HGDS.cfg
[]
FMember: IN_1209
IPAddress: 47.164.76.81
[]
FGroup: SURV
[]
Member: IN_1209

7.3. CallTrace AccessSession creation for an IMSI through WICL (OMC V5.0)
Be aware that the CallTrace created as described below wont be managed through
the CallTrace Wizard.
Therefore its deletion should also be made with wicl.
Purpose of this chapter:
create a calltrace with wicl
check its creation on the RNC
delete a calltrace with wicl
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 110/300

RNC & NodeB Health Check for NEV 4.2- How To

retrieve the result of the calltrace (xml files).

7.3.1. Creation at the OMC


1. Launch wicl on line.
wiclsh under /opt/nortel/shell/wicl on the OMC server

login / password : the same used for the GUI session (by default: admin / admin, nortel /
nortel may also work)
2. Retrieve the CallTrace instance created
>: RNC RNC_1207 list Calltrace
{RNC RNC_1207 CallTrace 0}

3. Check if any AccessSession is created under this object


If no AccessSession has been previously created, the result will be blank
>: RNC RNC_1207 CallTrace 0 list AccessSession

>:

If an AccessSession number n already exists be sure to create AccessSession number n+1


(here AccessSession 1 should be created)
>: RNC RNC_1207 CallTrace 0 list AccessSession
{RNC RNC_1207 CallTrace 0 AccessSession 0}

4. CallTrace creation
>: RNC RNC_1207 CallTrace 0 AccessSession 0 create tracedUeIdentification
123456789012345 externalSessionId 2 tracedUeIdType imsi templateName
TraceSessionTemplate/TroubleShooting

In this case the IMSI 123456789012345 will be traced.


The externalSessionId is the identifier of a callTrace for the RNC. Keep it in mind
for the controls on the RNC.
Be sure no to choose a number already used.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 111/300

RNC & NodeB Health Check for NEV 4.2- How To

5. Check the CallTrace creation


>: RNC RNC_1207 CallTrace 0 AccessSession 0 dis
administrativeState
unlocked
class
AccessSession
dataFileUploadPeriod
15
datafileUploadSize
512
dn
(RNC,258)(CallTrace,0)(AccessSession,0)
duration
0
externalSessionId
2
operatorId
0
startTime
0
templateName
TroubleShooting
tracedUeIdentification
123456789012345
tracedUeIdType
imsi

6. CallTrace Activation on the RNC


>: RNC RNC_1207 CallTrace 0 synchronize
{
Performing SemanticCheck
Performing SynchroCheck
Performing Set Off Line on
(RNC.userLabel,RNC_1204)(CallTrace,0)(AccessSession,0) admState attribute
Sending CREATE actions on MO
Sending UNLOCK actions} {} {}
{
Performing Set Off Line on (RNC,258)(CallTrace,0)(AccessSession,0) admState
attribute
Sending CREATE actions on MO
Sending UNLOCK actions} {} {}

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 112/300

RNC & NodeB Health Check for NEV 4.2- How To

7.3.2. Calltrace creation check on the RNC

CLASSIC
In V4.2
Open a telnet session on the active OMU
1. Look for the PID process of TR_CA_CREATOR
RNC1202_titi-1:/OMU (omu) $ psg TR_CA_CREATOR
root 27348 8316
0
May 10
- 2:50 TR_CA_CREATOR --uniqueid 37 -instance 0
27348

is here the pid of TR_CA_CREATOR.

2. Launch ci_mgr on this process and use trca commands


Open a command interpreter manager session and redirect all the traces to your xterm
(and not to blogio)
RNC1202_titi-1:/OMU (omu) $ ci_mgr noxterm
@all CI> tty me

Address your commands to TR_CA_CREATOR


@all CI> 27348=
TR_CA_CREATOR[27348] @RNC1202_titi-1 - CI warningCI warning... List of matching
prefixes:
cidbg: debug commands
bexc: Bexception
bsnap: BaseOS snapshot
wdog: BaseOS watchdog
mtx: Mutexes
bostr: BaseOS basic tracing
pml: Pmlog
bmw: BaseOS memory wrapper
rid: Resource Id
shm: Shared memory
bsem: Shared semaphores
var: Multi Process variables
bthread: BaseOS Threads
prcm: Process
dym: Dynmem
bjob: bjob
ipc: unix_ipc
chro: Chrono
dly: Delay
fms: File Management System
fcirc: Circular files management
bckp: Backplane
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 113/300

RNC & NodeB Health Check for NEV 4.2- How To


bsm:
btpt:
apptr:
bmon:
trca:
tmr:

System and BaseOS monitoring


BaseOS transport
Application tracing
System and BaseOS monitoring
Call Trace Central Agent
TMR Services

Commands to be used:
27348 CI> trca getallsessions
TR_CA_CREATOR[27348] @RNC1202_titi-1 - Result of: trca getallsessions
getallsessions Success
(internal sessionId, type, external sessionId, state)
(1 CTa 0 STARTED)
(3 CTg 23 STARTED)
sessionId = 3
27348 CI> trca getsession 3
TR_CA_CREATOR[27348] @RNC1202_titi-1 - Result of: trca getsession 3
getsession Success 3 omc
-usertype omc
-tracetype CTg
-external session Id 23
-session tag 4000000
-start delay 0
-duration 0
-upldperiod 15
-upldsize 512
-session state: STARTED
-session ov suspension level: 1
-filter (ID in Hex) 30001
BSS Record Type, ID = 3
Mode (Hex) 7
Functional domain list (Hex): 10001 10002 10003 10004 20001 20002 30001
30002 30003 40001 40002 40003 40004 40005 60001 60002 60003 90001 90002 90003
90004 90005 90006 80001 80002 80003 80004 80005 80006 80007 80008 80009 8000A
8000B 8000C 8000D 8000E 8000F 80010 3EA0001 3EA0002 3EA0003 A0001 A0002 A0003
A0004 A0005 A0006 3E90001 3E90002 70001 70002 70003 70004 70005 B0001
Cell ID list (Hex): 207E8
TraceKey of the Cell (hex)
End of Filter object
27348 CI> quit

to leave ci_mgr.

COMPACT
Open a telnet session on the active OMU
6> telci -omu(1) rnc
Trying 127.1.5.7...
Connected to 127.1.5.7.
Escape character is '^]'
Telnet CI commands:
Q - quit telci
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 114/300

RNC & NodeB Health Check for NEV 4.2- How To


G - redirect global output.
telci(omu)> trca getallsessions
telci(omu)> trca getsession <sessionId

>

7.3.3. Deletion at the OMC


1. Delete command
Through wicl, delete the AccessSession created previously.
For instance, if AccessSession 0 was created, delete it and check that the object no longer
exists.
>: RNC RNC_1207 CallTrace 0 AccessSession 0 delete
>: RNC RNC_1207 CallTrace 0 AccessSession 0 dis
Object not found in the ROC or constraint

is incorrect (or time out on request)

>:

2. Apply calltrace deletion to the RNC


>: RNC RNC_1207 CallTrace 0 synchronize
{
Performing SemanticCheck
Performing SynchroCheck
Sending LOCK actions
Sending DELETE actions on MO} {} {}

3. You may check the CallTrace deletion on the RNC


Refer to CallTrace creation check on the RNC

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 115/300

RNC & NodeB Health Check for NEV 4.2- How To

7.3.4. Calltrace storage


The Calltrace will be kept on the OMU before being sent to the OMC.
1. On the active OMU
CLASSIC
Each time a call is ended, or if the calltrace file has reached a determined size, the .xdr
file stored under /OMU/share/log/CNCT is retrieved by the OMC and processed by the
perfServer.
COMPACT
The directory is /sfs2/share/log/CNCT.
See paragraph 2.7.3 OMU local-share directories for more details.
2. On the perfserver
The callTrace directory is
/opt/nortel/data/access/callTrace/onOAMdemand/sessionId/yyyymmdd
With sessionId : the calltrace identifier used for its creation
yyyymmdd: date with the year the month and the day

The folder will contain directories beginning with IMSI-xxxx.


Subdirectories will contain the xml files for IN and CN.
To list all the calltraces linked to one sessionId, use ls */*/*xml.
Here is an example for the sessionId 15, for the 12th of May 2006, on the RNC1211, imsi
number 450001111111544:
bianca:/opt/nortel/data/access/callTrace/onOAMdemand/15/20060512 <131> (nortel)
% ls */*/*xml
IMSI-450001111111544/1211--2080368878/RNC-RNC_1211_CN.161542+0200.xml
IMSI-450001111111544/1211--2080368878/RNC-RNC_1211_IN.161542+0200.xml
IMSI-450001111111544/1211--2080368878/RNC-RNC_1211_IN.161837+0200.xml
IMSI-450001111111544/1211--2080368926/RNC-RNC_1211_CN.173345+0200.xml
IMSI-450001111111544/1211--2080368926/RNC-RNC_1211_IN.173345+0200.xml
IMSI-450001111111544/1211--2080369038/RNC-RNC_1211_CN.121930+0200.xml
IMSI-450001111111544/1211--2080369038/RNC-RNC_1211_IN.121930+0200.xml
IMSI-450001111111544/1211--2080369038/RNC-RNC_1211_IN.122223+0200.xml
IMSI-450001111111544/1211--2080369166/RNC-RNC_1211_CN.120558+0200.xml
IMSI-450001111111544/1211--2080369166/RNC-RNC_1211_IN.120558+0200.xml

For a call, the IN and CN Calltraces are located in the same subdirectory name (here for
example 1211--2080368926).

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 116/300

RNC & NodeB Health Check for NEV 4.2- How To

3. To decode calltraces without the perfserver


RFO (http://navigate.us.nortel.com/imds?pg=/eng/wne/core/tool/adm/umts/rfo) or
Boris tool(http://eur-livelink.europe.nortel.com/livelink/livelink.exe?func=ll&objId=20470315&objAction=browse&sort=name).
7.4. To retrieve NodeB and Cell information
Purpose of this chapter:
To check the general information relative to a cell (cp, ccp states, cell state,)
To retrieve the cp and ccp vcc for a nodeb.

CLASSIC
1. Open a telnet session on the active OMU
Telnet @IP
User / password : omu/omu
2. CP, CCP states , cell states and information with getcellinfo
cd /OMU/local/usr/bin
getcellinfo
Choose menu 1 to retrieve the information of a cell.
In the following example, information is requested for cell 2041
RNC1202_toto-0:/OMU/local/usr/bin (omu) $ getCellInfo
------------------------------------------------------------------------------------CELL INFORMATION TOOL
(matching between different Cell Id, handled TMU and NodeB CP, cell state, call
status)
------------------------------------------------------------------------------------1. By external cell id
2. By external nodeB id
3. Cell IDs handle by TMU
4. Dump all cell IDs and their handled TMU in a file
5. Quit
Your choice : 1
Enter the external Cell ID : 2021

Ext Cell Id
| Ext NodeB Id | Int Cell Id
| Int NodeB Id | Local Cell Id
| NodeB CP
| TMU shelf,slot| PathGroupId
----------------------------------------------------------------------------------------------------------------------------2021
|
257
|
0
|
0
| 12021 |
1
|
0,11
|
4

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 117/300

RNC & NodeB Health Check for NEV 4.2- How To

General information is provided about the cell:


External cell id,
external nodeB id,
Internal cell id,
Internal nodeB id,
Local cell id,
NodeB core process
Tmu shelf and slot,
PathGroup id
Answer y to the following question for the state of the cell, the control port (CP) and
communication control port (CCP) status and state are displayed :
Do you want to check the state of this cell ? (y or n) y
NodeB Control Port State :
Control_port[0]:
admin state : CREATED
nodeBControlPortType : NODEB_CONTROL_PORT
availability status: ONLINE
operationalState: ENABLED
Control_port[1]:
admin state : CREATED
nodeBControlPortType : NODEB_COMMUNICATION_CONTROL_PORT
availability status: ONLINE
operationalState: ENABLED

The cell state, cid numbers are provided.


Check also that no NOBCCH_SETUP_NBAPFAILURE is encountered.
Cell State :
OSI state: Q3_OPER_ST_ENABLED - Q3_AV_ST_ONLINE
Channel Id: 20
Channel Id: 21
NOBCCH_SETUP_SUCCESS
Channel Id: 22
NOBCCH_SETUP_SUCCESS
Channel Id: 23
NOBCCH_SETUP_SUCCESS
current
root_idle
current
connected
current
= wait_change
current
operational

- pchNbapState:
- fachNbapState:

NOBCCH_NBAP_CONFIG
NOBCCH_NBAP_CONFIG - status:

- fachNbapState:

NOBCCH_NBAP_CONFIG - status:

- prachNbapState: NOBCCH_NBAP_CONFIG - status:

NOB CCH setup info : automaton =

nobcch_setup_setup --- state

NOB info

: automaton =

nob_nobroot --- state =

NOB RRC info

: automaton =

nobrrc_sysinfocell --- state

NOB CELL info

: automaton =

nobcell_cellMgt --- state =

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 118/300

RNC & NodeB Health Check for NEV 4.2- How To

Answer n to the two following questions.


Do you want to display historic information ? (y or n) n
Do you want to check the call state of this cell ? (y or n) n

COMPACT
COTT offers the getCellInfo tool,
The analysis is quite the same as for RNC1000 with a different output:
=========================================================
Get Cell Information
=========================================================
Please select the following options:
1.
2.
3.
4.
L.
T.
Q.

By external cell ID
By external Node B ID
By TMU
All cells
Enable log
telnet CI
Quit menu

Your choice: 1
Enter external cell ID: 2081
Include cell state info (y/n): y
Include Call state info (y/n): y
Is history info required (y/n): n
*********************************************************************
* GET CELL INFO SCRIPT STARTED
*
* Please be patient, as the script might take
* several minutes to run to completion.
*
*********************************************************************
*********************************************************************
* GET CELL INFO SCRIPT OUTPUT
*********************************************************************
INFO FOR CELL 2081:
Ext Cell Id
| Ext NodeB Id | Int Cell Id
| Int NodeB Id | Local Cell Id
| NodeB CP
| TMU lp,ap
| PathGroupId
----------------------------------------------------------------------------------------------------------------------------2081
|
257
|
0
|
0
|
12081
|
0
|
2,1
|
4
------------------------------CELL STATE INFO FOR ALL CELLS:
---------------------------------------------------Cell 2081 state:
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 119/300

RNC & NodeB Health Check for NEV 4.2- How To


---------------------nob cpctx 0 0
Result of: nob cpctx 0 0
*** Dump Control port Ctx ***
iCpRef : 0
control_port[0] :
operationalState: ENABLED
availability status: ONLINE
appUserId_Data : 0
PconnId_Data : 0
UconnId_Data : 189
iCpRef : 1
control_port[1] :
operationalState: ENABLED
availability status: ONLINE
appUserId_Data : 0
PconnId_Data : 257
UconnId_Data : 190
telci(tmu)>
nob cpdp 0 0
Result of: nob cpdp 0 0
*** Dump Cp DP ***
control_port[0] :
admin state : CREATED
nodeBControlPortType : NODEB_CONTROL_PORT
controlPortId : 0
control_port[1] :
admin state : CREATED
nodeBControlPortType : NODEB_COMMUNICATION_CONTROL_PORT
controlPortId : 1
telci(tmu)>
nobcch setupctx 0 0
Result of: nobcch setupctx 0 0
*** Dump Setup automaton context ***
updown : NOBCCH_UPLINK
prachInstance: 0
ctxCch:
pich[0]:
pichInstance: 0
codeNumber: 3
sccpch[0]:
sccpchInstance: 0
[]
aal2Ted : CN_IN_AAL2_TED_DISABLED
suConnId: 262199
spConnId: 165
transportLayerAddress[]: 187 187 187 187 187 187 187
187 187 187 187 187 187 187 187 187 187 187 187 187
bindingId[]: 187 187 187 187
bearerId: 0
codeNumber: 2
rachNbapState: NOBCCH_NBAP_CONFIG
status: NOBCCH_SETUP_SUCCESS
pathgroupId: 4
failure: NO_FAILURE
rpmDd:
inode_ctx: ctxInode:
dphAddress: 150999490
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 120/300

RNC & NodeB Health Check for NEV 4.2- How To


rpmAddress: 150995265
[]
telci(tmu)>
nobcch setupaut 0 0
Result of: nobcch setupaut 0 0
===================================================================
*** Display information for setup automaton ***
===================================================================
Current cp: 0
iCellRefPerNodebCP: 0
History Entry #1
Time: 2006/05/11 17:39:28.641
Sequence #18
Automaton: nobcch_setup_setup
State: root_idle
Logical event: setup_start
Next state: wait_qaal2_est_end
[]
------------------------------CALL STATE INFO FOR ALL CELLS:
---------------------------------------------------Cell 2081 call state:
---------------------No Calls found for this cell
*********************************************************************
* END OF GET CELL INFO SCRIPT OUTPUT
*********************************************************************
*********************************************************************
* GET CELL INFO SCRIPT END
*********************************************************************
Press Enter key to back to menu.....

3. Cellsavailability for one TMU: nobcell listcellsbystate command


nobcell listcellsbystate coreProcess
gives the state of the cells managed by a NodeB cp on a TMU.
The TMU and the translations internal cell id cell number are performed thanks to
getCellInfo.
rrmcell list can also be used
The NodeB cp must be known (cp consistency).
The cells must be ENABLED ONLINE.
Below an example
TELNET_CI> rrmcell list
sbc @tmu_0_11_sbc - Result of: rrmcell list
*** List of the managed cells ***
Cell 2021 is Managed and Unlocked
Cell 2022 is Managed and Unlocked
Cell 2023 is Managed and Unlocked
There is 3 cells managed
There is 0 cells managed Locked
There is 3 cells managed Unlocked
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 121/300

RNC & NodeB Health Check for NEV 4.2- How To

TELNET_CI> cp consistency
sbc @tmu_0_11_sbc - Result of: cp consistency
Umts_Nodeb [Oc: 1 Rk: 1]
Active Occurrence 1 for Core process NodeB
Umts_Ue [Oc: 1 Rk: 1]
Active
TELNET_CI> nobcell listcellsbystate 1
sbc @tmu_0_11_sbc - Result of: nobcell listcellsbystate 1
===================================================================
*** List the operational state and availability status for each cell ***
===================================================================
Current cp: 1
iCellRef
operationalState
availabilityStatus
0
Q3_OPER_ST_ENABLED
Q3_AV_ST_ONLINE
Enabled/Online
1
Q3_OPER_ST_ENABLED
Q3_AV_ST_ONLINE
2
Q3_OPER_ST_ENABLED
Q3_AV_ST_ONLINE

In case the cell is locked, the result for this cell would be:
iCellRef
0

operationalState
Q3_OPER_ST_DISABLED

availabilityStatus
Q3_AV_ST_DEPENDENCY

Disabled

4. Retrieve the vcc CP/CCP used for the NodeB


Wicl can be used to retrieve the NodeBs CP and CCP vcc used for the Control Node.
List the rnc on the OMC
List the NodeB below the RNC
Display the control ports information.
>: utran list RNC
{RNC RNC_1202} {RNC RNC518} {RNC RNC_1203} {RNC RNC_1206} {RNC RNC_1204} {RNC
RNC_1205}
>: RNC RNC_1202 list NodeB
{RNC RNC_1202 NodeB BTS_194014} {RNC RNC_1202 NodeB BTS_RED205}
>: RNC RNC_1202 NodeB BTS_RED205 list ControlPort
{RNC RNC_1202 NodeB BTS_RED205 ControlPort 0} {RNC RNC_1202 NodeB BTS_RED205
ControlPort 1}
>: RNC RNC_1202 NodeB BTS_RED205 ControlPort 0 dis
availabilityStatus
{ }
class
ControlPort
controlPortId
0
controlPortType
nodeBCP
dn
(RNC,260)(NodeB,1)(ControlPort,0)
operationalState
enabled
operatorId
0
userSpecificInfo
NONE
vc
100
vp
0
>: RNC RNC_1202 NodeB BTS_RED205 ControlPort 1 dis
availabilityStatus
{ }
class
ControlPort
controlPortId
1
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 122/300

RNC & NodeB Health Check for NEV 4.2- How To


controlPortType
dn
operationalState
operatorId
userSpecificInfo
vc
vp

CCP
(RNC,260)(NodeB,1)(ControlPort,1)
enabled
0
NONE
355
0

5. To retrieve the cp/ccp vcc from the Inode


Open a wicl session
Retrieve the Inode name
Finally, retrieve the associated vcc
The aal2if number is linked to the Path Group retrieved with getCellinfo (aal2if =
PatchGroup Id / 4).
In the previous example, the Path Group Id was 4 => the aal2If at stake will be one.
>: utran list rnc
{RNC RNC_1202} {RNC RNC518} {RNC RNC_1203} {RNC RNC_1206} {RNC RNC_1204} {RNC
RNC_1205}
>: RNC RNC_1202 list children
CallTrace CsCoreNetworkAccess GSMNeighbour LocationServices MtpSignPoint
NeighbouringRNC NodeB ObjectTrace PerfScanner PsCoreNetworkAccess RNCEquipment
RadioAccessService RncMIB SasAccess
>: RNC RNC_1202 list RNCEquipment
{RNC RNC_1202 RNCEquipment 0}
>: RNC RNC_1202 RNCEquipment 0 list children
ANode CNode INode

>: RNC RNC_1202 RNCEquipment 0 list INode


{RNC RNC_1202 RNCEquipment 0 INode IN_1202}
>: INode IN_1202 aal2if/1 path/* atmconnection dis
Aal2If/1 Path/8
atmConnection
AtmIf/800 Vcc/0.42 Nep
Aal2If/1 Path/16
atmConnection
AtmIf/800 Vcc/0.34 Nep

6. To retrieve the OAM VCC


Rely on provisioned tags of
d -p atmif/* vcc/* vcd

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 123/300

RNC & NodeB Health Check for NEV 4.2- How To

Example :
3> d -p atmif/* vcc/* vcd
AtmIf/* Vcc/* Vcd
+=====+==========+------+------+------+------+-------------------|AtmIf|
Vcc
|segLkL|segSwL|eeLbk |connTy|
tag
|
|
| bk | bk |
| pe |
+=====+==========+------+------+------+------+-------------------
| 800|0.33
|sameAs|sameAs|sameAs|ptp
|NB+OAM+00+BTS_RED205
| 800|0.34
|sameAs|sameAs|sameAs|ptp
|NB+DSS+00+BTS_RED205
| 800|0.42
|sameAs|sameAs|sameAs|ptp
|NB+NDS+01+BTS_RED205
| 800|0.50
|sameAs|sameAs|sameAs|ptp
|NB+nCP+00+BTS_RED205
| 800|0.51
|sameAs|sameAs|sameAs|ptp
|NB+CCP+00+BTS_RED205

7.5. OAM-RNC link check up.


Control from the Control Node,
Control from the IN and AN,
Control from the OMC.
7.5.1. Control from the Control Node.
CLASSIC
Under the blogio.* files in /OMU_STORAGE/log/local/bos/sc check the correct
initialization of APE and that the OMC is seen connected.
In the example given, APE is started and we see that the link to the OMC came up, then
went down and came back.
RNC1204_OMU2:/OMU_STORAGE/log/local/bos/sc (omu) $ grep APE blogio*
blogio.ini:[15228] prcm_create(APE) synchro ok <2s - protected.
blogio.ini:24/02/2005 11:29:01 num:00000003 [18358/1] @ omu_5_sbc $$$$ <APE_PE> <0x0000> APE : End
of initialisation
blogio.ini:24/02/2005 11:29:03 num:00000005 [18358/1] @ omu_5_sbc $$$$ <APE_PE> <0x0000> APE :
Software ready
RNC1204_OMU2:/OMU_STORAGE/log/local/bos/sc (omu) $ more blogio* |grep "OMC Line"
24/02/2005 15:05:39 num:0000000b [16522/1] @ omu_5_sbc (PERM): ActMngt : Reception of STATE
MESSAGE from OSI Watch => OMC Line CONNECTED.
25/02/2005 08:17:24 num:0000000c [16522/1] @ omu_5_sbc (PERM): ActMngt : Reception of STATE
MESSAGE from OSI Watch => OMC Line NOT CONNECTED !!!!!!!!!!!.
25/02/2005 08:21:49 num:0000000d [16522/1] @ omu_5_sbc (PERM): ActMngt : Reception of STATE
MESSAGE from OSI Watch => OMC Line CONNECTED.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 124/300

RNC & NodeB Health Check for NEV 4.2- How To

COMPACT
To check if the connection is established with the OMC, the blogio.tmp file can be
retrieved from the passport to check the OMC Line CONNECTED message, as for a
RNC1000.
Other check possible (result truncated):
TELNET_CI> ape trsp
CONFIGURATION CONNEXIONS TRANSPORT
[]
Automaton state
: APE_TRSP_CNX_ETABLIE
Automaton last event : APE_TRSP_T_RDY_ID
[]

Telci on OMU
Connection established

7.5.2. Control from the IN / AN


CLASSIC/COMPACT
A session must be opened on the IN and AN by the perf server, that will support
MDM/Preside, in charge of managing the passports.
Check that NMIS (Network Management Interface System) fmip sessions are present.
There should be at least (and only) one session created under the userid MDMADMIN.
The IP address must be the OMC server address.
3> d nmis fmip session/*
Nmis Fmip Session/*
Use -noTabular to see hidden attributes: loginTime.
+=======+--------+--------------------+---------+---------------+-----+----|Session| userid |
role
|dataStrea|
address
|port |width
|
|
|
|
ms
|
|
|
|
|
|
|a d l s r|
|
|
|
|
|
|l e o c t|
|
|
|
|
|
|a b g n s|
|
|
+=======+--------+--------------------+---------+---------------+-----+----|
1|MDMADMIN|""
|* . . * .|47.164.44.107 |42978|
79

7.5.3. Verification on the OMC side.


The status can be checked:
through the netstat command,
Or thanks to wicl.
First way:
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 125/300

RNC & NodeB Health Check for NEV 4.2- How To

saba:/home/nortel <101> (nortel) % netstat -a|grep -i iso


*.iso-tsap
*.*
0
0 24576
0 LISTEN
fmbb.58451 47.164.52.235.iso-tsap 8176
0 24820
0 ESTABLISHED
fmbb.42861 47.164.52.201.iso-tsap 16060
0 24820
0 ESTABLISHED
fmbb.35357 10.20.2.10.iso-tsap 16384
0 25088
0 ESTABLISHED
fmbb.58494 47.164.76.83.iso-tsap 8174
0 24820
0 ESTABLISHED
fmbb.58495 47.164.74.116.iso-tsap 16060
0 24820
0 ESTABLISHED
fmbb.58622 47.164.52.123.iso-tsap 16060
0 24820
0 ESTABLISHED

The connection must be established with one of the OMU addresses (provisioned under
rncin for the compact).
Or second way:
Check under the GUI that the objects are correctly created and their administrative states
unlocked.
With wicl, get the status of the Cnode, Inode, Anode objects perceived by the OMC
database. unknownstatus must be false (i.e. equipment connected to OMC).
Passport declaration is under /opt/MagellanNMS/cfg/HGDS.cfg for MDM.
Launch wicl on the OMC server (/opt/nortel/shell/wicl/wiclsh)
bonaire:/home/nortel <105> (nortel) % /opt/nortel/shell/wicl/wiclsh
--------------------------------------------------------Starting Wireless Internet Command Language
--------------------------------------------------------Command mode launched
login : nortel
password : nortel
....wait please
Wireless Internet Command Language (WICL)

>: utran list rnc


{RNC RNC507} {RNC RNC_1201} {RNC RNC_1205} {RNC RNC502} {RNC RNC_1207} {RNC
DIDI
ER_31}

>: RNC RNC_1201 RNCEquipment 0 get unknownStatus


unknownstatusfalse
>: RNC RNC_1201 list children
CallTrace GSMNeighbour PsCoreNetworkAccess RNCEquipment NodeB
RadioAccessService CsCoreNetworkAccess NeighbouringRNC MtpSignPoint PerfScanner
RncMIB RouteSet ObjectTrace
>: RNC RNC_1201 list RNCEquipment
{RNC RNC_1201 RNCEquipment 0}
>: RNC RNC_1201 RNCEquipment 0 list children
CNode ANode INode
>: RNC RNC_1201 RNCEquipment 0 Cnode 0 get unknownStatus
unknownstatusfalse
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 126/300

RNC & NodeB Health Check for NEV 4.2- How To

>: RNC RNC_1201 RNCEquipment 0 list Inode


{RNC RNC_1201 RNCEquipment 0 INode IN_1201}
>: RNC RNC_1201 RNCEquipment 0 INode IN_1201 get unknownStatus
unknownstatusfalse
>: RNC RNC_1201 RNCEquipment 0 list Anode
{RNC RNC_1201 RNCEquipment 0 ANode AN_1}
>: RNC RNC_1201 RNCEquipment 0 ANode AN_1 get unknownStatus
unknownstatusfalse

7.6. Consistency of the SW between RNC and OAM


Purpose of this chapter:
Remind the naming conventions for RNC.
Retrieve the Control Node and Interface Node software linked to a delivery.
Check the software that should be running according to the OMC.
Check the software on the RNC equipment (Control Node, Interface Node)
RNC42100c61201

will be the delivery example used.

7.6.1 RNC Delivery Naming


7.6.1.1. Versions and Deliveries correspondence
To link an RNC version with its delivery name go to
http://gato.europe.nortel.com/gpstools/patchs/index.php?line=UMTS
Example:
V4.2.2EP1
The RNC load sub-components are:
Equipment

Software version
Ciphered Load: RNC42100c61201 including:
C Node: RC42162061200
I Node: RI42111c
RI42111c61220

RNC1000

Non-ciphered load: RNC42100061201 including:


C Node: RC42162061200
I Node: RI42111c
RI42111061220

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 127/300

RNC & NodeB Health Check for NEV 4.2- How To

Ciphered Load: RNC42100c61201 including:


I Node: RI42111c
RI42111c61220
RNC1500

Non-ciphered load: RNC42100061201 including:


I Node: RI42111c
RI42111061220
MSS7K06W09A_CF01S1E: PCR6.1.1 Patch Baseline
for 7K
Access Node

AV Patch bundle
base7R1416A_CF01S1E
base7T1396A_CF01S1E

7.6.1.2. RNC delivery naming convention


[ RNCVVVTTXYwwee ]
eg: RNC42100061201
RNC42100c61201
The naming consists of:
RNC - stands for RNC
VVV - stands for the current UMTS release (420 for V4.2, 421 for V4.2 CuR+1)
RNC425 is a V4.2 CUR+5 load.
TT - always 00 (including both RNC 1000 and RNC 1500)
X
= 0 (digit zero) for No ciphering
= c (minus letter) for Ciphering
Y: The last digit of the year
2006
ww: identify the week that the load is generated
week 12
ee: identify the number of builds in the same week
first build of this week
For more details for the CN and IN loads naming, see UMT/RNC/INF/6420 RNC
Naming convention
(http://eurlivelink.europe.nortel.com/livelink/livelink.exe/fetch/2000/16011614/2907303/2969832/5841134/5895418/
5906627/24098488/umtrncinf6420-0301e_RNC_Naming_Convention.pdf?nodeid=24098489&vernum=0).

Internal and external UA4.2 naming conventions will be different till CuR+3
There are different naming conventions used for the successive UA4.2 corrective loads.
Particular care must be taken when communicating externally: for communication to our
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 128/300

RNC & NodeB Health Check for NEV 4.2- How To

customers (in case notes or in any external documents), only the external naming
convention (UA4.2.1 or UA4.2.2 or UA4.2.3) shall be used.
Below is a table summarizing the different conventions:
Corrective load
CL1
CL2
CL3

Customer
Delivery
Wk09
Wk13
Wk17

Internal naming convention


UA4.2.1.1 or UA4.2.1 CuR + 1
UA4.2.1.2 or UA4.2.1 CuR + 2
UA4.2.1.3 or UA4.2.1 CuR + 3

Customer naming
convention
UA4.2.1
UA4.2.2
UA4.2.3

Note : Both UA4.2xx or V4.2xx names can be found

Please find below the correspondence Table:


External
RNC Load (with ciphering)
Release
Stream Objective CNode Load
INode Load
V4.2
V4.2K
CuR
05wk50 RC42062K54900 RI42061K54910c AVL #23210 : RNC4200cK54900
V4.2.0
V4.2K

CuR
CuR+1

06wk03
06wk03

AVL #23517 :
RNC42000C60202
RC42062060201 RI42066c60220
RC42062K60301 RI42065K60320c AVL #23627 : RNC4200cK60301

V4.2.1
V4.2.1
EP1
V4.2K
V4.2.2
V4.2.2
EP1
V4.2.3
V4.2.3
EP1

CuR+1

06wk09

RC42162060900

CuR+1
CuR+2
CuR+2

06wk10
06wk08
06wk12

RC42162061000 RI42108c61030
AVL #24097 : RNC42100c61000
RC42162K20801 RI42106K20820c AVL #23936 : RNC4210cK20801
RC42162061100 RI42110c61120
AVL #24201 : RNC42100c61100

CuR+2
CuR+3

06wk13
06wk17

RC42162061200
RC42162061700

RI42111c61220
RI42112c61671

AVL #24258 : RNC42100c61201


AVL #24548 :RNC42100c61700

CuR+3

06wk18

RC42162061800

RI42112c61673

AVL #24625 : RNC42100c61800

RI42107c60950

AVL #23992 :
RNC42100c60900

Any update on this Table can be found under:


http://eurlivelink.europe.nortel.com/livelink/livelink.exe/20542897/RNC_ExternalLoads_Snapshot.xls?func=doc.Fet
ch&nodeid=20542897

7.6.1.3. Finding the SRS descriptions on the OMC


On the OMC
In the file /opt/nortel/data/srs/DESCRIPTION/RNC/RNCxxxx-RNCxxc00cxxxxx.xml
(choose the version supposed to be installed)
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 129/300

RNC & NodeB Health Check for NEV 4.2- How To


grep soft_vers_name

Example:
bernard:/opt/nortel/data/srs/DESCRIPTION/RNC <106> (nortel) % grep
soft_vers_name RNC1000-RNC42100c61201.xml
comp_soft_vers_name="RNC100042100c61201"
subcomp_soft_vers_name="RC42162061200"
subcomp_soft_vers_name="RACF01S1Ec"
subcomp_soft_vers_name="RI42111c61220"

The load names linked to this RNC delivery name are:


RC42162061200 for the Control Node (RC identifies the family: RNC-CN)
RI42111c61220 for the Interface Node (RI identifies the family: RNC-IN)
RACF01S1Ec for the AN
In case of an RNC1500, only the RI42111c61220 name is used
7.6.2 OMC Versions
7.6.2.1. Control Node SW from the OMC point of view
Open a Wicl session on the OMC
/opt/nortel/shell/wicl/wiclsh

login / password : the same used for the GUI session (example: admin / admin or nortel /
nortel )
For example for the RNC_1202
>: RNC RNC_1202 RNCEquipment 0 CNode 0 list CNodeSoftware
{RNC RNC_1202 RNCEquipment 0 CNode 0 CNodeSoftware 0}
>: RNC RNC_1202 RNCEquipment 0 CNode 0 CNodeSoftware 0 display
class
CNodeSoftware
dn
(RNC,260)(RNCEquipment,0)(CNode,0)(CNodeSoftware,0)
fallbackSoftwareVersion
unknown
fallbackSoftwareVersionDeliveryName
RC41361054801
operatorId
0
runningSoftwareVersion
RC42162061300
runningSoftwareVersionDeliveryName
RC42162061300

How To reach CNodeSoftware under wicl


If you dont know the names of the Control Node and the Interface Node, the path to the
CnodeSoftware can be found through few commands using list and list children.
Retrieve the sub-objects of an object with list children, point out an instance with list
sub-object and display the attributes of the searched object.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 130/300

RNC & NodeB Health Check for NEV 4.2- How To

>: utran list rnc


{RNC RNC_1205} {RNC RNC_1208} {RNC RNC_1211} {RNC RNC_1206} {RNC RNC_1204} {RNC
RNC_1202} {RNC RNC507} {RNC RNC518} {RNC RNC502} {RNC RNC_1201}
>: RNC RNC_1202 list children
CallTrace CsCoreNetworkAccess GSMNeighbour LocationServices MtpSignPoint
NeighbouringRNC NodeB ObjectTrace PerfScanner PsCoreNetworkAccess RNCEquipment
RadioAccessService RncMIB SasAccess
>: RNC RNC_1202 list RNCEquipment
{RNC RNC_1202 RNCEquipment 0}
>: RNC RNC_1202 RNCEquipment 0 list children
CNode ANode INode
>: RNC RNC_1202 RNCEquipment 0 list CNode
{RNC RNC_1202 RNCEquipment 0 CNode 0}
>: RNC RNC_1202 RNCEquipment 0 CNode 0 list children
CC1 CNodeSoftware MMS OMU TMU
>: RNC RNC_1202 RNCEquipment 0 CNode 0 list CNodeSoftware
{RNC RNC_1202 RNCEquipment 0 CNode 0 CNodeSoftware 0}
>: RNC RNC_1202 RNCEquipment 0 CNode 0 CNodeSoftware 0 dis
class
CNodeSoftware
dn
(RNC,260)(RNCEquipment,0)(CNode,0)(CNodeSoftware,0)
fallbackSoftwareVersion
unknown
fallbackSoftwareVersionDeliveryName
RC41361054801
operatorId
0
runningSoftwareVersion
RC42162061300
runningSoftwareVersionDeliveryName
RC42162061300

7.6.2.2. Interface Node SW from the OMC point of view


Open a Wicl session on the OMC
/opt/nortel/shell/wicl/wiclsh

login / password : the same used for the GUI session (example: admin / admin or nortel /
nortel )
For example for the RNC_1202, IN_1202
>: RNC RNC_1202 RNCEquipment 0 INode IN_1202 INodeSoftware 0 dis
class
INodeSoftware
dn
(RNC,260)(RNCEquipment,0)(INode,0)(INodeSoftware,0)
fallbackSoftwareVersion
fallbackSoftwareVersionDeliveryName
operatorId
0
runningSoftwareVersion
RI42112061320
runningSoftwareVersionDeliveryName
RI42112061320

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 131/300

RNC & NodeB Health Check for NEV 4.2- How To

How To reach InodeSoftware under wicl


If you dont know the names of the Control Node and the Interface Node, the path to the
InodeSoftware can be found through few commands using list and list children.
Retrieve the sub-objects of an object with list children, point out an instance with list
sub-object and display the attributes of the searched object.
>: utran list rnc
{RNC RNC_1205} {RNC RNC_1208} {RNC RNC_1211} {RNC RNC_1206} {RNC RNC_1204} {RNC
RNC_1202} {RNC RNC507} {RNC RNC518} {RNC RNC502} {RNC RNC_1201}
>: RNC RNC_1202 list children
CallTrace CsCoreNetworkAccess GSMNeighbour LocationServices MtpSignPoint
NeighbouringRNC NodeB ObjectTrace PerfScanner PsCoreNetworkAccess RNCEquipment
RadioAccessService RncMIB SasAccess
>: RNC RNC_1202 list RNCEquipment
{RNC RNC_1202 RNCEquipment 0}
>: RNC RNC_1202 RNCEquipment 0 list children
CNode ANode INode
>: RNC RNC_1202 RNCEquipment 0 list INode
{RNC RNC_1202 RNCEquipment 0 INode IN_1202}
>: RNC RNC_1202 RNCEquipment 0 INode IN_1202 list children
INodeSoftware
>: RNC RNC_1202 RNCEquipment 0 INode IN_1202 list INodeSoftware
{RNC RNC_1202 RNCEquipment 0 INode IN_1202 INodeSoftware 0}
>: RNC RNC_1202 RNCEquipment 0 INode IN_1202 INodeSoftware 0 dis
class
INodeSoftware
dn
(RNC,260)(RNCEquipment,0)(INode,0)(INodeSoftware,0)
fallbackSoftwareVersion
fallbackSoftwareVersionDeliveryName
operatorId
0
runningSoftwareVersion
RI42112061320
runningSoftwareVersionDeliveryName
RI42112061320

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 132/300

RNC & NodeB Health Check for NEV 4.2- How To

7.6.3 CN / IN versions
7.6.3.1. Control Node SW - OMU check
CLASSIC
Under a telnet session on the active OMU
CN_1202_0-0:/OMU (omu) $ cd /OMU/delivery/B3G/running/BCN
CN_1202_0-0:/OMU/delivery/B3G/running/BCN (omu) $ ls *.version
RC42162061300.version

or
You can also check the version seen by the Control Node at its startup
CN_1202_0-0:/OMU (omu) $ grep "Detected RNC software
/OMU_STORAGE/log/local/bos/sc/blogio.*
/OMU_STORAGE/log/local/bos/sc/blogio.ini:20/04/2006 13:12:34 num:00000015
[21930/1] @ omu_9_sbc (PERM): CM_CA : Detected RNC software id: RC42162061300,
interface version: 42

COMPACT
Not applicable.
7.6.3.2. Interface Node SW - CP check
CLASSIC
Under a telnet session on the Interface Node
1> d sw avl
Sw
avList = atmNetworking_RI42112,
base_RI42112,
fabric_RI42112,
genericUtilities_RI42112,
iRNC_RI42112,
ip_RI42112,
networking_RI42112,
ss7_RI42112,
wanDte_RI42112,
wirelessCommon_RI42112,
apcBase_RI42112061320,
baseExt_RI42112061320,
iRNCApc_RI42112061320,
ss7Apc_RI42112061320
ok
2006-04-28 16:51:21.72

or
using the CAS commands with wicl,

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 133/300

RNC & NodeB Health Check for NEV 4.2- How To

>:

RNC RNC_1202 RNCEquipment 0 INode IN_1202 sw avl dis


avList
atmNetworking_RI42112,
base_RI42112,
fabric_RI42112,
genericUtilities_RI42112,
iRNC_RI42112,
ip_RI42112,
networking_RI42112,
ss7_RI42112,
wanDte_RI42112,
wirelessCommon_RI42112,
apcBase_RI42112061320,
baseExt_RI42112061320,
iRNCApc_RI42112061320,
ss7Apc_RI42112061320

COMPACT
Idem
N.B: Additional packages are revelant of an RNC1500 load: cRncApc_xxx and
cnp_xxx
Example below:
13> d sw avl
Sw
avList = atmNetworking_RI42111,
base_RI42111,
fabric_RI42111,
genericUtilities_RI42111,
iRNC_RI42111,
ip_RI42111,
ipsec_RI42111,
networking_RI42111,
ss7_RI42111,
wanDte_RI42111,
wirelessCommon_RI42111, RNCCiph_RI42111061220,
apcBase_RI42111061220,
baseExt_RI42111061220,
cRNCApc_RI42111061220,
cnp_RI42111061220,
iRNCApc_RI42111061220,
ss7Apc_RI42111061220
ok
2006-04-28 17:11:09.75

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 134/300

RNC & NodeB Health Check for NEV 4.2- How To

7.7. Check CN-IN link

0. First of all, check the IP traffic between CN and IN


1. Then, check that the IN is seen connected to the Control Node thanks to the dumps
generated by software bus debug menu (/OMU/local/usr/bin /swbDebugMenu.exe)
2. Other possible step: check that the CN-IN link is opened from an IN perspective
3. Then check the IRT/ORT tables on CN and IN to ensure the application and addressing
mapping is correct between IN UMTS applications (callgroups) and CN UMTS
applications (core processes).
CLASSIC
IP traffic checks.
First, check that sockets are created towards the PMC Master activ and passiv, by
checking that IP packets are exchanged.
On the active and passiv OMU
RNC1201_OMU1-0:/OMU (omu) $ netstat -a | grep 1500
tcp4
0
0 omu_5_sbc.15000
172.253.201.73.1034
tcp4
0
0 omu_5_sbc.15000
172.253.201.63.1034
tcp4
0
0 omu_5_sbc.15000
172.253.201.69.1034
tcp4
0
0 omu_5_sbc.15000
172.253.201.79.1056
tcp4
0
0 *.15000
*.*

ESTABLISHED
ESTABLISHED
ESTABLISHED
ESTABLISHED
LISTEN

RNC1201_OMU2-1:/OMU (omu) $ netstat -a | grep 1500


tcp4
0
0 omu_9_sbc.15000
172.253.201.79.1133
tcp4
0
0 omu_9_sbc.15000
172.253.201.63.1101
tcp4
0
0 omu_9_sbc.15000
172.253.201.69.1101
tcp4
0
0 omu_9_sbc.15000
172.253.201.73.1146
tcp4
0
0 *.15000
*.*

ESTABLISHED
ESTABLISHED
ESTABLISHED
ESTABLISHED
LISTEN

NB:
The signification of the IP addresses are provided by d
role on the IN.

lp/* ap/* ip

/d

lp/* ap/* rnc

In our case 172.253.201.79 is the active PMC-M, 172.253.201.73 is the passive PMC-M,
172.253.201.63 is the passive Ni, 172.253.201.69 is the active Ni.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 135/300

RNC & NodeB Health Check for NEV 4.2- How To

On Control Node and Interface Node side ORT (Outgoing Routing Table) and IRT
(Incoming Routing Table) must be symetrical.
CLASSIC/COMPACT
Interface Node checks
Telnet to the active PMC-M (see the 4.9.2 to know how to connect to the active PMCM).
-- > showCnAccCaInitTraces
First of all, the initialization of CnAccCa (control node access central agent) can be
checked on the PMC Master.
Under the PMC Master, check that CNODE GAIN NOTFICATION HAS BEEN SENT
OUT (result truncated).
To see the list of the commands.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 136/300

RNC & NodeB Health Check for NEV 4.2- How To

-> helpCnAccCa
---------------------------------------------------------------------CnAccess CA Display Tools
---------------------------------------------------------------------showCnAccCaMeshLink
(formerly ShowCnAccCaTbl(1))
showCnAccCaInBoard
(formerly ShowCnAccCaTbl(2))
showCnAccCaCnBoard
(formerly ShowCnAccCaTbl(3))
showCnAccCaIrtPmc
(formerly ShowCnAccCaTbl(4))
showCnAccCaIrtLg
(formerly ShowCnAccCaTbl(5))
showCnAccCaOrtCg
(formerly ShowCnAccCaTbl(6))
showCnAccCaIrtPmcChurn
(formerly ShowCnAccCaTbl(7))
showCnAccCaInitTraces
(formerly ShowCnAccCaTbl(9))
showCnAccCaCnodeGainRegApps (formerly ShowCnAccCaTbl(10))
checkCnAccCaInit
checkCnAccRoutingInfo
dumpCnAccCa
---------------------------------------------------------------------CnAccess CA Command Tools
---------------------------------------------------------------------CnAccCaManualCmd
toggleResetINodeFlag
value = 1 = 0x1
-> helpCnAccLa
---------------------------------------------------------------------CnAccess LA Tools
---------------------------------------------------------------------showCnAccLaIrt(lgId)
showCnAccLaIrtDeregList
showCnAccLaPrt(mgId)
showCnAccLaLrt
showCnAccLaLrtEntry(lgId)
showCnAccLaOrt
showCnAccLaOrtEntry(cgId)
showPagingOvCounters
showNonPagingOvCounters
showTcpLink
showCnAccLaInitTraces
dumpCnAccLa
tcpOvTest(int times, int data_len)
showTcpLinkState(cgId)
value = 1 = 0x1

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 137/300

RNC & NodeB Health Check for NEV 4.2- How To

-> showCnAccCaInitTraces
Apr 18 2006
18:10:06.427
CnAccCa: Init Traces
---------------------------------------------------------------------1 14:22:12.323 : initialize - State is initialized to REG_TO_LA_st
2 14:22:12.323 : initialize - Running as Active Master
3 14:22:12.324 : initialize - Started LA registration timer
4 14:22:12.324 : addrBookConfirmMsg - Received addressBookAddSuccess_c
5 14:22:12.325 : RegToLa_Hdlr - Registration to local LA has been sent
6 14:22:12.325 : RegToLaRsp_Hdlr - State change: REG_TO_LA_st -> REG_TO_OAM_st
[]
47 14:26:07.052 : CnAddAddrRsp_Hdlr==>startAuditTimer() State:auditStart
48 14:26:07.064 : CnAddressSync_Hdlr - CNODE GAIN NOTFICATION HAS BEEN SENT OUT

ShowCnAccCaOrtCg
Dumps the Call group table in Ort_Ca table
The callgroups (IN UMTS applications) are linked to tasks running on the active OMU
and the TMU bearing Core Processes (nobadm, inacc_ca, iuded_adm).
Below 66 Call groups are pointing to the active OMU SBC (172.41.2.2) and the four
TMU SBC ( 172.43.2.2 172.44.2.2 172.45.2.2 172.11.2.2 ) holding core processes.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 138/300

RNC & NodeB Health Check for NEV 4.2- How To

-> showCnAccCaOrtCg
Apr 18 2006
18:35:08.996
CnAccCa: Call Group Info Table
---------------------------------------------------------------------Number of Entries: 66
Call Group

IP

1
2
3
4
5
6
7
9
10
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54

172.41.2.2
172.41.2.2
172.41.2.2
172.41.2.2
172.41.2.2
172.41.2.2
172.41.2.2
172.41.2.2
172.41.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.11.2.2
172.11.2.2
172.11.2.2
172.11.2.2
172.11.2.2
172.11.2.2
172.11.2.2
172.11.2.2
172.11.2.2
172.11.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 139/300

RNC & NodeB Health Check for NEV 4.2- How To

55
172.44.2.2
56
172.44.2.2
57
172.44.2.2
58
172.45.2.2
59
172.45.2.2
60
172.45.2.2
61
172.45.2.2
62
172.45.2.2
63
172.11.2.2
64
172.11.2.2
65
172.11.2.2
66
172.11.2.2
67
172.11.2.2
68
172.43.2.2
69
172.43.2.2
70
172.44.2.2
71
172.44.2.2
value = 4096 = 0x1000

Reminder to display the type of the PMC and their ip addresses:


d lp/* ap/* rnc role and d lp/* ap/* ip
On our example configuration :
24> d lp/* ap/* ip

25> d lp/* ap/*

rnc role

Lp/* Ap/*
+==+==+---------------+--------------|Lp|Ap|
ipAddr
|Response
+==+==+---------------+--------------| 2| 0|172.253.202.79 |
| 2| 1|172.253.202.80 |
| 2| 2|172.253.202.81 |
| 2| 3|172.253.202.82 |
| 2| 4|172.253.202.83 |
| 2| 5|172.253.202.84 |
| 3| 0|172.253.202.73 |
| 3| 1|172.253.202.74 |
| 3| 2|172.253.202.75 |
| 3| 3|172.253.202.76 |
| 3| 4|172.253.202.77 |
| 3| 5|172.253.202.78 |
| 4| 0|172.253.202.67 |
| 4| 1|172.253.202.68 |
| 4| 2|172.253.202.69 |
| 4| 3|172.253.202.70 |
| 4| 4|172.253.202.71 |
| 4| 5|172.253.202.72 |
| 5| 0|172.253.202.61 |
| 5| 1|172.253.202.62 |
| 5| 2|172.253.202.63 |
| 5| 3|172.253.202.64 |
| 5| 4|172.253.202.65 |
| 5| 5|172.253.202.66 |

+==+==+-------+---------------------|Lp|Ap| role |Response


+==+==+-------+---------------------| 2| 0|aMaste |
| 2| 1|rab
|
| 2| 2|rab
|
| 2| 3|rab
|
| 2| 4|pc
|
| 2| 5|rab
|
| 3| 0|sMaste |
| 3| 1|rab
|
| 3| 2|rab
|
| 3| 3|rab
|
| 3| 4|pc
|
| 3| 5|rab
|
| 4| 0|rab
|
| 4| 1|rab
|
| 4| 2|aNi
|
| 4| 3|rab
|
| 4| 4|pc
|
| 4| 5|rab
|
| 5| 0|rab
|
| 5| 1|rab
|
| 5| 2|sNi
|
| 5| 3|rab
|
| 5| 4|pc
|
| 5| 5|rab
|

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 140/300

RNC & NodeB Health Check for NEV 4.2- How To

OMU checks (RNC1000 RNC1500)


CLASSIC/COMPACT
By consulting IN_ACC_CA (Interface Node Access Central Agent) under the active
OMU, ORT and IRT can be dumped from a Control Node perspective.
On the active OMU (RNC1000):
Retrieve IN_CREATOR pid,
open a ci manager session (ci_mgr noxterm),
type tty me to redirect all the results in your session and not to blogio.tmp
dump INACC
The CI commands are the same for RNC1000/RNC1500:
RNC1202_titi-1:/OMU (omu) $ psg IN_CREATOR
root 24768 10568
0
Apr 14
- 0:40 IN_CREATOR --uniqueid 34 -instance 0
RNC1202_titi-1:/OMU (omu) $ ci_mgr noxterm
@all CI> 24768=
24768 CI> tty me
CI TTY redirected to: me

24768 CI> INACC_CA


IN_CREATOR[24768] @RNC1202_titi-1 - CI warning... Ambiguous command: INACC_CA
INACC_CA help
: Display the help of inacc_ca utilities
INACC_CA display_cd_ctx : Dump the MIB cd context
INACC_CA display_dd_ctx : Dump the dd context
INACC_CA display_his_log : Dump ca history log
INACC_CA check_routing_info: Check IRT, ORT and Meshlink tables
INACC_CA display_demar
: Dump the grf context for demar23994

INACC_CA

display_dd_ctx allows to check the IRT/ORT tables.

INACC_CA IRT TABLE details to which task on OMU and TMU the 66 callgroups seen
previously on the IN are linked to.
INACC_CA ORT TABLE depaints the vision of the LG (logical groups) repartition on
RABs and PMC.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 141/300

RNC & NodeB Health Check for NEV 4.2- How To

24768 CI> INACC_CA display_dd_ctx


IN_CREATOR[24768] @RNC1202_titi-1 - Result of: INACC_CA display_dd_ctx
-------------------| INACC_CA IRT TABLE |
-------------------Nb of Elements : 66
----------------------------------------------------------------------------------------------------------| RncHandle | User Prefix | Famille | Class Id |
register type | IP Address | Status |
----------------------------------------------------------------------------------------------------------|
1|
|
0|
0|
UNSPECIFIED(0) | 172.41.2.2 | PRESENT(1) |
|
2|
CPM_ADM | 151 | 132 |
UNSPECIFIED(0) | 172.41.2.2 | PRESENT(1) |
|
3|
PFPROXY | 165 | 141 |
UNSPECIFIED(0) | 172.41.2.2 | PRESENT(1) |
|
4|
TR_PROXY | 155 | 65535 |
UNSPECIFIED(0) | 172.41.2.2 | PRESENT(1) |
|
5 | STACK_ADM_CA | 151 |
0|
UNSPECIFIED(0) | 172.41.2.2 | PRESENT(1) |
|
6|
RNCUPGSUP | 170 | 203 |
UNSPECIFIED(0) | 172.41.2.2 | PRESENT(1) |
|
7|
OV_PROXY | 177 | 162 |
UNSPECIFIED(0) | 172.41.2.2 | PRESENT(1) |
|
9 | STACK_ADM_CA | 151 | 65535 |
MTP3_ACCESS(2) | 172.41.2.2 | PRESENT(1) |
|
10 | STACK_ADM_CA | 151 | 65535 |
SCCP_ACCESS(1) | 172.41.2.2 | PRESENT(1) |
|
15 |
IUDED_ADM | 151 | 201 |
SCCP_ACCESS(1) | 172.43.2.2 | PRESENT(1) |
|
16 |
IUCOM_ADM | 151 | 202 |
SCCP_ACCESS(1) | 172.43.2.2 | PRESENT(1) |
|
17 | IURCOM_ADM | 151 | 204 |
SCCP_ACCESS(1) | 172.43.2.2 | PRESENT(1) |
|
18 |
IUDED_ADM | 151 | 201 |
SCCP_ACCESS(1) | 172.44.2.2 | PRESENT(1) |
|
19 |
IUCOM_ADM | 151 | 202 |
SCCP_ACCESS(1) | 172.44.2.2 | PRESENT(1) |
|
20 | IURCOM_ADM | 151 | 204 |
SCCP_ACCESS(1) | 172.44.2.2 | PRESENT(1) |
|
21 |
NOBADM | 151 | 105 |
UNSPECIFIED(0) | 172.45.2.2 | PRESENT(1) |
|
22 |
NOBADM | 151 | 117 |
UNSPECIFIED(0) | 172.45.2.2 | PRESENT(1) |
|
23 | NOBCALL_ADM | 151 | 106 |
UNSPECIFIED(0) | 172.45.2.2 | PRESENT(1) |
|
24 |
UE_ADM | 151 | 126 |
UNSPECIFIED(0) | 172.45.2.2 | PRESENT(1) |
|
25 |
IUDED_ADM | 151 | 201 |
UNSPECIFIED(0) | 172.45.2.2 | PRESENT(1) |
|
26 | IURCALL_ADM | 151 | 147 |
UNSPECIFIED(0) | 172.45.2.2 | PRESENT(1) |
|
27 | IURCALL_ADM | 151 | 148 |
UNSPECIFIED(0) | 172.45.2.2 | PRESENT(1) |
|
28 |
UE_ADM | 151 | 127 |
UNSPECIFIED(0) | 172.45.2.2 | PRESENT(1) |
|
29 |
RNC_ADM | 151 | 109 |
UNSPECIFIED(0) | 172.45.2.2 | PRESENT(1) |
|
30 | RNCCOM_ADM | 151 | 110 |
UNSPECIFIED(0) | 172.45.2.2 | PRESENT(1) |
|
31 |
NOBADM | 151 | 105 |
UNSPECIFIED(0) | 172.11.2.2 | PRESENT(1) |
|
32 |
NOBADM | 151 | 117 |
UNSPECIFIED(0) | 172.11.2.2 | PRESENT(1) |
|
33 | NOBCALL_ADM | 151 | 106 |
UNSPECIFIED(0) | 172.11.2.2 | PRESENT(1) |
|
34 |
UE_ADM | 151 | 126 |
UNSPECIFIED(0) | 172.11.2.2 | PRESENT(1) |
|
35 |
IUDED_ADM | 151 | 201 |
UNSPECIFIED(0) | 172.11.2.2 | PRESENT(1) |
|
36 | IURCALL_ADM | 151 | 147 |
UNSPECIFIED(0) | 172.11.2.2 | PRESENT(1) |
|
37 | IURCALL_ADM | 151 | 148 |
UNSPECIFIED(0) | 172.11.2.2 | PRESENT(1) |
|
38 |
UE_ADM | 151 | 127 |
UNSPECIFIED(0) | 172.11.2.2 | PRESENT(1) |
|
39 |
RNC_ADM | 151 | 109 |
UNSPECIFIED(0) | 172.11.2.2 | PRESENT(1) |

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 142/300

RNC & NodeB Health Check for NEV 4.2- How To

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|

40 | RNCCOM_ADM | 151 | 110 |


UNSPECIFIED(0) | 172.11.2.2 | PRESENT(1) |
41 |
NOBADM | 151 | 105 |
UNSPECIFIED(0) | 172.43.2.2 | PRESENT(1) |
42 |
NOBADM | 151 | 117 |
UNSPECIFIED(0) | 172.43.2.2 | PRESENT(1) |
43 | NOBCALL_ADM | 151 | 106 |
UNSPECIFIED(0) | 172.43.2.2 | PRESENT(1) |
44 |
UE_ADM | 151 | 126 |
UNSPECIFIED(0) | 172.43.2.2 | PRESENT(1) |
45 |
IUDED_ADM | 151 | 201 |
UNSPECIFIED(0) | 172.43.2.2 | PRESENT(1) |
46 | IURCALL_ADM | 151 | 147 |
UNSPECIFIED(0) | 172.43.2.2 | PRESENT(1) |
47 | IURCALL_ADM | 151 | 148 |
UNSPECIFIED(0) | 172.43.2.2 | PRESENT(1) |
48 |
UE_ADM | 151 | 127 |
UNSPECIFIED(0) | 172.43.2.2 | PRESENT(1) |
49 |
RNC_ADM | 151 | 109 |
UNSPECIFIED(0) | 172.43.2.2 | PRESENT(1) |
50 | RNCCOM_ADM | 151 | 110 |
UNSPECIFIED(0) | 172.43.2.2 | PRESENT(1) |
51 |
UE_ADM | 151 | 126 |
UNSPECIFIED(0) | 172.44.2.2 | PRESENT(1) |
52 |
IUDED_ADM | 151 | 201 |
UNSPECIFIED(0) | 172.44.2.2 | PRESENT(1) |
53 | IURCALL_ADM | 151 | 147 |
UNSPECIFIED(0) | 172.44.2.2 | PRESENT(1) |
54 | IURCALL_ADM | 151 | 148 |
UNSPECIFIED(0) | 172.44.2.2 | PRESENT(1) |
55 |
UE_ADM | 151 | 127 |
UNSPECIFIED(0) | 172.44.2.2 | PRESENT(1) |
56 |
RNC_ADM | 151 | 109 |
UNSPECIFIED(0) | 172.44.2.2 | PRESENT(1) |
57 | RNCCOM_ADM | 151 | 110 |
UNSPECIFIED(0) | 172.44.2.2 | PRESENT(1) |
58 |
IUDED_ADM | 151 | 201 |
SCCP_ACCESS(1) | 172.45.2.2 | PRESENT(1) |
59 | IURCALL_ADM | 151 | 147 |
SCCP_ACCESS(1) | 172.45.2.2 | PRESENT(1) |
60 | IURCALL_ADM | 151 | 148 |
SCCP_ACCESS(1) | 172.45.2.2 | PRESENT(1) |
61 |
IUCOM_ADM | 151 | 202 |
SCCP_ACCESS(1) | 172.45.2.2 | PRESENT(1) |
62 | IURCOM_ADM | 151 | 204 |
SCCP_ACCESS(1) | 172.45.2.2 | PRESENT(1) |
63 |
IUDED_ADM | 151 | 201 |
SCCP_ACCESS(1) | 172.11.2.2 | PRESENT(1) |
64 | IURCALL_ADM | 151 | 147 |
SCCP_ACCESS(1) | 172.11.2.2 | PRESENT(1) |
65 | IURCALL_ADM | 151 | 148 |
SCCP_ACCESS(1) | 172.11.2.2 | PRESENT(1) |
66 |
IUCOM_ADM | 151 | 202 |
SCCP_ACCESS(1) | 172.11.2.2 | PRESENT(1) |
67 | IURCOM_ADM | 151 | 204 |
SCCP_ACCESS(1) | 172.11.2.2 | PRESENT(1) |
68 | IURCALL_ADM | 151 | 147 |
SCCP_ACCESS(1) | 172.43.2.2 | PRESENT(1) |
69 | IURCALL_ADM | 151 | 148 |
SCCP_ACCESS(1) | 172.43.2.2 | PRESENT(1) |
70 | IURCALL_ADM | 151 | 147 |
SCCP_ACCESS(1) | 172.44.2.2 | PRESENT(1) |
71 | IURCALL_ADM | 151 | 148 |
SCCP_ACCESS(1) | 172.44.2.2 | PRESENT(1) |
------------------------------------------------------------------------------------------------------

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 143/300

RNC & NodeB Health Check for NEV 4.2- How To


-------------------| INACC_CA ORT TABLE |
---------------------------------------------| LogAddr |
IP Address |
--------------------------|
1 |
172.253.202.79 |
|
2 |
172.253.202.79 |
|
3 |
172.253.202.79 |
|
4 |
172.253.202.79 |
|
5 |
172.253.202.79 |
|
7 |
172.253.202.79 |
|
8 |
172.253.202.79 |
|
9 |
172.253.202.79 |
|
10 |
172.253.202.79 |
|
12 |
172.253.202.69 |
|
16 |
172.253.202.80 |
|
17 |
172.253.202.80 |
|
18 |
172.253.202.74 |
|
19 |
172.253.202.74 |
|
20 |
172.253.202.75 |
|
21 |
172.253.202.75 |
|
22 |
172.253.202.82 |
|
23 |
172.253.202.82 |
|
24 |
172.253.202.81 |
|
25 |
172.253.202.81 |
|
26 |
172.253.202.84 |
|
27 |
172.253.202.84 |
|
28 |
172.253.202.78 |
|
29 |
172.253.202.78 |
|
30 |
172.253.202.76 |
|
31 |
172.253.202.76 |
|
32 |
172.253.202.64 |
|
33 |
172.253.202.80 |
|
34 |
172.253.202.64 |
|
35 |
172.253.202.72 |
|
36 |
172.253.202.74 |
|
37 |
172.253.202.72 |
|
38 |
172.253.202.64 |
|
39 |
172.253.202.72 |
|
40 |
172.253.202.61 |
|
41 |
172.253.202.82 |
|
42 |
172.253.202.61 |
|
43 |
172.253.202.62 |
|
44 |
172.253.202.81 |
|
45 |
172.253.202.62 |
|
46 |
172.253.202.70 |
|
47 |
172.253.202.75 |
|
48 |
172.253.202.70 |
|
49 |
172.253.202.61 |
|
50 |
172.253.202.70 |
|
51 |
172.253.202.66 |
|
52 |
172.253.202.84 |
|
53 |
172.253.202.66 |
|
54 |
172.253.202.68 |
|
55 |
172.253.202.78 |
|
56 |
172.253.202.68 |
|
57 |
172.253.202.62 |
|
58 |
172.253.202.68 |
|
59 |
172.253.202.67 |
|
60 |
172.253.202.76 |
|
61 |
172.253.202.67 |
|
62 |
172.253.202.66 |
|
63 |
172.253.202.67 |
--------------------------- --------------------

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 144/300

RNC & NodeB Health Check for NEV 4.2- How To

INACC_CA REGISTER-LA TABLE shows the repartition of the local agents on the
other boards (none stands for non started or non plugged boards).
IP address(es) in TMU table lists the addresses of the IN boards seen by the TMU.
The TMU must see all RAB and PMC M.
---------------------------| INACC_CA REGISTER-LA TABLE |
---------------------------Number of boards to connect to OMUs : 0
Number of boards to connect to TMUs : 20
---------------------------------------------------------------------------------------| Idx | InaccLa Prefix | Occ. | BrdType | IP Address | Elem Present | Elem Status |
---------------------------------------------------------------------------------------|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|

0|
INACC_LA | 37 | OMU | 172.37.2.2 | PRESENT | NORMAL(0) |
1|
INACC_LA | 11 | TMU | 172.11.2.2 | PRESENT | NORMAL(0) |
2|
INACC_LA | 41 | OMU | 172.41.2.2 | PRESENT | NORMAL(0) |
3|
INACC_LA | 45 | TMU | 172.45.2.2 | PRESENT | NORMAL(0) |
4|
INACC_LA | 43 | TMU | 172.43.2.2 | PRESENT | NORMAL(0) |
5|
INACC_LA | 44 | TMU | 172.44.2.2 | PRESENT | NORMAL(0) |
6|
None | None | None |
None |
None |
None |
7|
None | None | None |
None |
None |
None |
8|
None | None | None |
None |
None |
None |
9|
None | None | None |
None |
None |
None |
10 |
None | None | None |
None |
None |
None |
11 |
None | None | None |
None |
None |
None |
12 |
None | None | None |
None |
None |
None |
13 |
None | None | None |
None |
None |
None |
14 |
None | None | None |
None |
None |
None |
15 |
None | None | None |
None |
None |
None |
----------------------------------------------------------------------------------------

----------------------------| IP Address(es) in TMU Table |


----------------------------172.253.202.79 |
172.253.202.73 |
172.253.202.61 |
172.253.202.67 |
172.253.202.69 |
172.253.202.63 |
172.253.202.80 |
172.253.202.74 |
172.253.202.75 |
172.253.202.82 |
172.253.202.81 |
172.253.202.84 |
172.253.202.78 |
172.253.202.76 |
172.253.202.64 |
172.253.202.72 |
172.253.202.62 |
172.253.202.70 |
172.253.202.66 |
172.253.202.68 |

Finally the last table gives the link state for all the INACC_LA.
All the boards of the CN on which an IN access local agent is present must see the PMC
present with a link up.
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 145/300

RNC & NodeB Health Check for NEV 4.2- How To

This table is not easy to read but the first 20 addresses are PMC master and PMC rab
addresses, connected to the OMU passive, then 20 addresses are PMC master and PMC
rab addresses, connected to one TMU, then the 4 addresses of PMC master and PMC Ni
are connected to the OMU active, then 60 following addresses and states are for the 3
last TMU.
The order may as in INACC REGISTER-LA TABLE.
----------------------------------| INACC_CA MESH LINK TABLE (per La) |
---------------------------------------------------------------------------------------------| PmcPresent |
xMU IP |
PMCx IP | LinkState |
-----------------------------------------------------------|
1
|
172.37.2.2 | 172.253.202.79 |
UP |

|
1
|
172.37.2.2 | 172.253.202.73 |
UP |
|
1
|
172.37.2.2 | 172.253.202.61 | WAIT FOR CONNECT
|
1
|
172.37.2.2 | 172.253.202.67 | WAIT FOR CONNECT
|
1
|
172.37.2.2 | 172.253.202.63 |
UP |
|
1
|
172.37.2.2 | 172.253.202.69 |
UP |
|
1
|
172.37.2.2 | 172.253.202.81 | WAIT FOR CONNECT
|
1
|
172.37.2.2 | 172.253.202.80 | WAIT FOR CONNECT
|
1
|
172.37.2.2 | 172.253.202.82 | WAIT FOR CONNECT
|
1
|
172.37.2.2 | 172.253.202.76 | WAIT FOR CONNECT
|
1
|
172.37.2.2 | 172.253.202.74 | WAIT FOR CONNECT
|
1
|
172.37.2.2 | 172.253.202.75 | WAIT FOR CONNECT
|
1
|
172.37.2.2 | 172.253.202.84 | WAIT FOR CONNECT
|
1
|
172.37.2.2 | 172.253.202.78 | WAIT FOR CONNECT
|
1
|
172.37.2.2 | 172.253.202.66 | WAIT FOR CONNECT
|
1
|
172.37.2.2 | 172.253.202.64 | WAIT FOR CONNECT
|
1
|
172.37.2.2 | 172.253.202.70 | WAIT FOR CONNECT
|
1
|
172.37.2.2 | 172.253.202.72 | WAIT FOR CONNECT
|
1
|
172.37.2.2 | 172.253.202.62 | WAIT FOR CONNECT
|
1
|
172.37.2.2 | 172.253.202.68 | WAIT FOR CONNECT
|
1
|
172.11.2.2 | 172.253.202.79 |
UP |

|
1
|
172.11.2.2 | 172.253.202.73 |
UP |
|
1
|
172.11.2.2 | 172.253.202.61 |
UP |
|
1
|
172.11.2.2 | 172.253.202.67 |
UP |
|
1
|
172.11.2.2 | 172.253.202.63 |
UP |
|
1
|
172.11.2.2 | 172.253.202.69 |
UP |
|
1
|
172.11.2.2 | 172.253.202.81 |
UP |
|
1
|
172.11.2.2 | 172.253.202.80 |
UP |
|
1
|
172.11.2.2 | 172.253.202.82 |
UP |
|
1
|
172.11.2.2 | 172.253.202.76 |
UP |
|
1
|
172.11.2.2 | 172.253.202.74 |
UP |
|
1
|
172.11.2.2 | 172.253.202.75 |
UP |
|
1
|
172.11.2.2 | 172.253.202.84 |
UP |
|
1
|
172.11.2.2 | 172.253.202.78 |
UP |
|
1
|
172.11.2.2 | 172.253.202.66 |
UP |
|
1
|
172.11.2.2 | 172.253.202.64 |
UP |
|
1
|
172.11.2.2 | 172.253.202.70 |
UP |
|
1
|
172.11.2.2 | 172.253.202.72 |
UP |
|
1
|
172.11.2.2 | 172.253.202.62 |
UP |
|
1
|
172.11.2.2 | 172.253.202.68 |
UP |
|
1
|
172.41.2.2 | 172.253.202.79 |
UP |

|
1
|
172.41.2.2 | 172.253.202.73 |
UP |
|
1
|
172.41.2.2 | 172.253.202.63 |
UP |
|
1
|
172.41.2.2 | 172.253.202.69 |
UP |
|
1
|
172.45.2.2 | 172.253.202.79 |
UP |

|
1
|
172.45.2.2 | 172.253.202.73 |
UP |
|
1
|
172.45.2.2 | 172.253.202.61 |
UP |
|
1
|
172.45.2.2 | 172.253.202.67 |
UP |
|
1
|
172.45.2.2 | 172.253.202.63 |
UP |
|
1
|
172.45.2.2 | 172.253.202.69 |
UP |
|
1
|
172.45.2.2 | 172.253.202.81 |
UP |

OMU_1_5 (Slave)
|
|

|
|
|
|
|
|
|
|
|
|
|
|
|
|

TMU_0_11

OMU_1_9(active)

TMU_1_13

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 146/300

RNC & NodeB Health Check for NEV 4.2- How To


|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|

1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|

172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.45.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.43.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2
172.44.2.2

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|

172.253.202.80
172.253.202.82
172.253.202.76
172.253.202.74
172.253.202.75
172.253.202.84
172.253.202.78
172.253.202.66
172.253.202.64
172.253.202.70
172.253.202.72
172.253.202.62
172.253.202.68
172.253.202.79
172.253.202.73
172.253.202.61
172.253.202.67
172.253.202.63
172.253.202.69
172.253.202.81
172.253.202.80
172.253.202.82
172.253.202.76
172.253.202.74
172.253.202.75
172.253.202.84
172.253.202.78
172.253.202.66
172.253.202.64
172.253.202.70
172.253.202.72
172.253.202.62
172.253.202.68
172.253.202.79
172.253.202.73
172.253.202.61
172.253.202.67
172.253.202.63
172.253.202.69
172.253.202.81
172.253.202.80
172.253.202.82
172.253.202.76
172.253.202.74
172.253.202.75
172.253.202.84
172.253.202.78
172.253.202.66
172.253.202.64
172.253.202.70
172.253.202.72
172.253.202.62
172.253.202.68

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|

UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP
UP

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|

TMU_1_11

TMU_1_12

------------------------------------------------------------

Use the command dumpCnAccLa on the PMC-M or a PMC-Rab or a PMC-Ni to check


CN-IN link, this example is done on a RNC having 4 TMUs.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 147/300

RNC & NodeB Health Check for NEV 4.2- How To

CLASSIC/COMPACT

-> dumpCnAccLa
CnAccLa: Dump
---------------------------------------------------------------------General
Flags
LinkReqFinishFlag: 2
CnAccLa: Init Traces
---------------------------------------------------------------------1 09:35:59.972 : Init Started: Waiting for CnAccCa registration
2 09:35:59.981 : Registration : Pid=RncInMtc Fn=20
3 09:35:59.982 : Registration : Pid=CnAccCa Fn=9
4 09:35:59.983 : Registration : Pid=OvInCa Fn=6
5 09:35:59.984 : Registration : Pid=WomCa Fn=8
6 09:36:00.204 : Registration : Pid=TrBrMgr Fn=12
7 09:36:00.204 : Registered with CnAccCa
Should be Registered
8 09:36:00.204 : Registration : Pid=RmanCa Fn=8
9 09:36:03.206 : Registration : Pid=InTrCa Fn=7

with CnAccCA

CnAccLa: Incoming Route Table


---------------------------------------------------------------------Total number of registered addresses is: 7
Displaying information for all Lgs...
LG

AI

RAND

1
2
4
5
7
8
9

1
2
4
5
7
8
9

0
0
0
0
0
0
0

BITM
0
0
0
0
0
0
0

HANDLE
400000
800000
1000000
1400000
1c00000
2000000
2400000

PROC_NAME

FUN_NUM

CnAccCa
RmanCa
WomCa
InTrCa
TrBrMgr
RncInMtc
OvInCa

1
1
4
1
13
18
12

CnAccLa: Outgoing Route Table


---------------------------------------------------------------------Number of Entries: 65
Call Group

IP

1
2
3
4
5
7
9
10
24
25
26
27
28
29
30
31

172.253.208.72
172.253.208.72
172.253.208.72
172.253.208.72
172.253.208.72
172.253.208.72
172.253.208.72
172.253.208.72
172.253.208.62
172.253.208.62
172.253.208.62
172.253.208.62
172.253.208.62
172.253.208.62
172.253.208.62
172.253.208.62

OMU active

The first Tmu

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 148/300

RNC & NodeB Health Check for NEV 4.2- How To


32
33
34
35
36
37
38
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143

172.253.208.62
172.253.208.62
172.253.208.62
172.253.208.62
172.253.208.62
172.253.208.62
172.253.208.62
172.253.208.74
172.253.208.74
172.253.208.74
172.253.208.74
172.253.208.74
172.253.208.74
172.253.208.74
172.253.208.74
172.253.208.74
172.253.208.74
172.253.208.74
172.253.208.74
172.253.208.74
172.253.208.74
172.253.208.74
172.253.208.80
172.253.208.80
172.253.208.80
172.253.208.80
172.253.208.80
172.253.208.80
172.253.208.80
172.253.208.80
172.253.208.80
172.253.208.80
172.253.208.80
172.253.208.80
172.253.208.80
172.253.208.80
172.253.208.80
172.253.208.68
172.253.208.68
172.253.208.68
172.253.208.68
172.253.208.68
172.253.208.68
172.253.208.68
172.253.208.68
172.253.208.68
172.253.208.68
172.253.208.68
172.253.208.68

The second TMU

The third TMU

The fourth TMU

CnAccLa: Page Route Table (mgId=0)


---------------------------------------------------------------------MgId
Addresses

CnAccLa: Lg Route Table


---------------------------------------------------------------------Number of Entries: 29
LG

PID

Num of the lgId(s) in the table is: 29


0
1
2
3
4

00010204021e000b
00010204021e000b
00010205021e000b
00010205021e000b
00010505021e000b

02 : Lp/2 05 : ap/3
021e: pdi or proc number
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 149/300

RNC & NodeB Health Check for NEV 4.2- How To


5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

00010204021e000b
00010207021e000b
00010207021e000b
00010502021e000b
00010502021e000b
00010405021e000b
00010405021e000b
00010405021e000b
00010402021e000b
00010502021e000b
00010402021e000b
00010304021e000b
00010204021e000b
00010304021e000b
00010405021e000b
00010304021e000b
00010307021e000b
00010205021e000b
00010307021e000b
00010402021e000b
00010307021e000b
00010305021e000b
00010305021e000b
00010505021e000b

000b: function number

CnAccLa: Paging Msg Overload Stats OV INFO: OPID = c


Ov_Uplane_Paging
====================================================================================
TOTAL: RX = 0; OV = 0
====================================================================================
|
|
NOMINAL | LOW_FILTER | MED_FILTER | HIGH_FILTEG|
SUSPEND |
BLOCK |
-----------------------------------------------------------------------------------| RX |
0 |
0 |
0 |
0 |
0 |
0 |
-----------------------------------------------------------------------------------| OV |
0 |
0 |
0 |
0 |
0 |
0 |
------------------------------------------------------------------------------------

CnAccLa: Non-Paging Overload Counters (nTcpLink = 6)


---------------------------------------------------------------------Link State
= 2
Link IP Address
= 172.253.208.72
The OMU active
TCP Connection Failure Count
= 0
TcpLink: Paging Msg Overload Stats OV INFO: OPID = 12
Ov_Uplane_Paging
====================================================================================
TOTAL: RX = 0; OV = 0
====================================================================================
|
|
NOMINAL | LOW_FILTER | MED_FILTER | HIGH_FILTEG|
SUSPEND |
BLOCK |
-----------------------------------------------------------------------------------| RX |
0 |
0 |
0 |
0 |
0 |
0 |
-----------------------------------------------------------------------------------| OV |
0 |
0 |
0 |
0 |
0 |
0 |
------------------------------------------------------------------------------------

TcpLink: Non-Paging Msg Overload Stats OV INFO: OPID = 2


Ov_Cn_Msg_Filtering
====================================================================================
TOTAL: RX = 0; OV = 0
====================================================================================
|
|
NOMINAL | LOW_FILTER | MED_FILTER | HIGH_FILTEG|
SUSPEND |
BLOCK |
-----------------------------------------------------------------------------------| RX |
0 |
0 |
0 |
0 |
0 |
0 |
-----------------------------------------------------------------------------------| OV |
0 |
0 |
0 |
0 |
0 |
0 |
------------------------------------------------------------------------------------

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 150/300

RNC & NodeB Health Check for NEV 4.2- How To


Link State
= 2
Link IP Address
= 172.253.208.66
The OMU standby
TCP Connection Failure Count
= 0
TcpLink: Paging Msg Overload Stats OV INFO: OPID = 12
Ov_Uplane_Paging
====================================================================================
TOTAL: RX = 0; OV = 0
====================================================================================
|
|
NOMINAL | LOW_FILTER | MED_FILTER | HIGH_FILTEG|
SUSPEND |
BLOCK |
-----------------------------------------------------------------------------------| RX |
0 |
0 |
0 |
0 |
0 |
0 |
-----------------------------------------------------------------------------------| OV |
0 |
0 |
0 |
0 |
0 |
0 |
------------------------------------------------------------------------------------

TcpLink: Non-Paging Msg Overload Stats OV INFO: OPID = 2


Ov_Cn_Msg_Filtering
====================================================================================
TOTAL: RX = 0; OV = 0
====================================================================================
|
|
NOMINAL | LOW_FILTER | MED_FILTER | HIGH_FILTEG|
SUSPEND |
BLOCK |
-----------------------------------------------------------------------------------| RX |
0 |
0 |
0 |
0 |
0 |
0 |
-----------------------------------------------------------------------------------| OV |
0 |
0 |
0 |
0 |
0 |
0 |
-----------------------------------------------------------------------------------Link State
Link IP Address
TCP Connection Failure Count

= 2
= 172.253.208.80
= 0

The first TMU

TcpLink: Paging Msg Overload Stats OV INFO: OPID = 12


Ov_Uplane_Paging
====================================================================================
TOTAL: RX = 0; OV = 0
====================================================================================
|
|
NOMINAL | LOW_FILTER | MED_FILTER | HIGH_FILTEG|
SUSPEND |
BLOCK |
-----------------------------------------------------------------------------------| RX |
0 |
0 |
0 |
0 |
0 |
0 |
-----------------------------------------------------------------------------------| OV |
0 |
0 |
0 |
0 |
0 |
0 |
------------------------------------------------------------------------------------

TcpLink: Non-Paging Msg Overload Stats OV INFO: OPID = 2


Ov_Cn_Msg_Filtering
====================================================================================
TOTAL: RX = 3670; OV = 0
====================================================================================
|
|
NOMINAL | LOW_FILTER | MED_FILTER | HIGH_FILTEG|
SUSPEND |
BLOCK |
-----------------------------------------------------------------------------------| RX |
3670 |
0 |
0 |
0 |
0 |
0 |
-----------------------------------------------------------------------------------| OV |
0 |
0 |
0 |
0 |
0 |
0 |
-----------------------------------------------------------------------------------Link State
= 2
Link IP Address
= 172.253.208.62
The second TMU
TCP Connection Failure Count
= 0
TcpLink: Paging Msg Overload Stats OV INFO: OPID = 12
Ov_Uplane_Paging
====================================================================================
TOTAL: RX = 0; OV = 0
====================================================================================
|
|
NOMINAL | LOW_FILTER | MED_FILTER | HIGH_FILTEG|
SUSPEND |
BLOCK |
-----------------------------------------------------------------------------------| RX |
0 |
0 |
0 |
0 |
0 |
0 |

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 151/300

RNC & NodeB Health Check for NEV 4.2- How To


-----------------------------------------------------------------------------------| OV |
0 |
0 |
0 |
0 |
0 |
0 |
------------------------------------------------------------------------------------

TcpLink: Non-Paging Msg Overload Stats OV INFO: OPID = 2


Ov_Cn_Msg_Filtering
====================================================================================
TOTAL: RX = 5; OV = 0
====================================================================================
|
|
NOMINAL | LOW_FILTER | MED_FILTER | HIGH_FILTEG|
SUSPEND |
BLOCK |
-----------------------------------------------------------------------------------| RX |
5 |
0 |
0 |
0 |
0 |
0 |
-----------------------------------------------------------------------------------| OV |
0 |
0 |
0 |
0 |
0 |
0 |
-----------------------------------------------------------------------------------Link State
Link IP Address
TCP Connection Failure Count

= 2
= 172.253.208.74
= 0

The third TMU

TcpLink: Paging Msg Overload Stats OV INFO: OPID = 12


Ov_Uplane_Paging
====================================================================================
TOTAL: RX = 0; OV = 0
====================================================================================
|
|
NOMINAL | LOW_FILTER | MED_FILTER | HIGH_FILTEG|
SUSPEND |
BLOCK |
-----------------------------------------------------------------------------------| RX |
0 |
0 |
0 |
0 |
0 |
0 |
-----------------------------------------------------------------------------------| OV |
0 |
0 |
0 |
0 |
0 |
0 |
------------------------------------------------------------------------------------

TcpLink: Non-Paging Msg Overload Stats OV INFO: OPID = 2


Ov_Cn_Msg_Filtering
====================================================================================
TOTAL: RX = 5; OV = 0
====================================================================================
|
|
NOMINAL | LOW_FILTER | MED_FILTER | HIGH_FILTEG|
SUSPEND |
BLOCK |
-----------------------------------------------------------------------------------| RX |
5 |
0 |
0 |
0 |
0 |
0 |
-----------------------------------------------------------------------------------| OV |
0 |
0 |
0 |
0 |
0 |
0 |
-----------------------------------------------------------------------------------Link State
= 2
Link IP Address
= 172.253.208.68
The fourth TMU
TCP Connection Failure Count
= 0
TcpLink: Paging Msg Overload Stats OV INFO: OPID = 12
Ov_Uplane_Paging
====================================================================================
TOTAL: RX = 0; OV = 0
====================================================================================
|
|
NOMINAL | LOW_FILTER | MED_FILTER | HIGH_FILTEG|
SUSPEND |
BLOCK |
-----------------------------------------------------------------------------------| RX |
0 |
0 |
0 |
0 |
0 |
0 |
-----------------------------------------------------------------------------------| OV |
0 |
0 |
0 |
0 |
0 |
0 |
------------------------------------------------------------------------------------

TcpLink: Non-Paging Msg Overload Stats OV INFO: OPID = 2


Ov_Cn_Msg_Filtering
====================================================================================
TOTAL: RX = 3; OV = 0
====================================================================================
|
|
NOMINAL | LOW_FILTER | MED_FILTER | HIGH_FILTEG|
SUSPEND |
BLOCK |
-----------------------------------------------------------------------------------Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 152/300

RNC & NodeB Health Check for NEV 4.2- How To


| RX |
3 |
0 |
0 |
0 |
0 |
0 |
-----------------------------------------------------------------------------------| OV |
0 |
0 |
0 |
0 |
0 |
0 |
------------------------------------------------------------------------------------

CnAccLa: TCP Link Table


Total Number of Link: 6
Pid_Index
IP_Address
sockId sockQSize LinkState
MsgSent
MsgRecv
LinkFailure
---------------------------------------------------------------------------------------------------571
172.253.208.72 (aOMU)119
500
LINK_ON
0
0
0
572
172.253.208.66 (sOMU)140
500
LINK_ON
0
0
0
580
172.253.208.80 (TMU1)131
500
LINK_ON
0
0
0
576
172.253.208.62 (TMU2)123
500
LINK_ON
0
0
0
577
172.253.208.74 (TMU3)127
500
LINK_ON
0
0
0
581
172.253.208.68 (TMU4)133
500
LINK_ON
0
0
0
Handle
AppName FunctionNum
De-regTime
-------------------------------------------------value = 51 = 0x33 = '3'

Those counters (OV) indicate the number of calls rejected due to reach the overload
situation.To get more informations about Overload type OvLaHelp.
7.8. Call check

7.8.1. RDT Ressource Debug Toolkit


CLASSIC
RDT at this time isnt ready for compact.
RDT is able to :
List all the callp contexts and statistics
List Inode contexts
Dump the cpu & memory consumption (CN & IN)
Dump the overload level on each CN board
Dump the mailboxes level on each CN board
Dump the cell status
Find buffers not released on TMUs

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 153/300

RNC & NodeB Health Check for NEV 4.2- How To

---------------------------------------------------------------------------------------------------------------------RESOURCE DEBUG TOOLKIT aka RDT (UA4.2)


---------------------------------------------------------------------------------------------------------------------CallP Contexts
CallP Statistics
Misc
Inode
---------------------------------------------------------------------------------------------------------------------1. uerrc
10. uerrc
20. cpu/memory Cnode
30. rmanCaCallList
2. uecall
11. uecall
21. cpu/memory Inode
31. rmanCaLgDbInfo
3. nobcall
12. nob[cell,cch]
22. RNC overload levels
32. rmanCaPmcStatus
4. rnccall
13. nobcall
23. Cnode mailboxes load
33. Dump all
5. iucall
14. rnccall
24. InAccCa Tables
6. iurcallinit
15. rnccom
25. cell state
7. iurcallterm
16. iucall
26. rrmcell list
8. Dump all
17. iurcallinit
27. TMU memory leak
18. iurcallterm
19. Dump all
--------------------------40. Dump CallP Contexts & Statistics + rmanCaCallList + pu/mem/mailboxes/overload
---------------------------------------------------------------------------------------------------------------------Options :
A. TMU selected : 0_12 / 0_13
B. Log to file
: yes (in omu_9:/OMU/local/log/bos/sc/RDT_log_RNC_GLB2-1_RC42162060301_Jan_27_2006_15H48m.txt)
C. List all CallP Ctx : yes
D. Inode address : 47.164.74.108
E. IN login/pwd
: debug/capacity
Q. Quit
Your choice :

7.8.1.1 how to install and launch it


FTP the script on the OMU on folder /OMU/local/usr/bin
cd /OMU/local/usr/bin
./rdt
> If needed, execute :
run_root chown omu:omu rdt
run_root chmod 775 rdt
Log are by default set to no, dont forget to change it to yes.
Logs are stored in /OMU/local/log/bos/sc (alias cdcore) of the active OMU in order to
save it in the archived sc_xxx sessions
7.8.1.2 cell infos
launch option 26
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 154/300

RNC & NodeB Health Check for NEV 4.2- How To

###################### TMU 0_11 - rrmcell list - 17_May_13h04m25s


######################
*** List of the managed cells ***
Cell 1009 is Managed and Unlocked
Cell 1019 is Managed and Unlocked
Cell 1029 is Managed and Locked
There is 3 cells managed
There is 1 cells managed Locked
There is 2 cells managed Unlocked

###################### TMU 1_11 - rrmcell list - 17_May_13h04m26s


######################
*** List of the managed cells ***
Cell
Cell
Cell
Cell

6220
6221
6222
7220

is
is
is
is

Managed
Managed
Managed
Managed

and
and
and
and

Unlocked
Locked
Locked
Unlocked

There is 4 cells managed


There is 2 cells managed Locked
There is 2 cells managed Unlocked

7.8.1.3 Memory leak


If no memory leak are find RDT say on each tmu :
###################### TMU 0_11
######################

- Memory Leak - 16_May_11h19m42s

No memory leak found

Else it was say:


###################### TMU 0_11
######################

- Memory Leak - 21_11_10h:49m:06s

TID_Creator : Iuxadm_LA
TID_Current : SIG_ALU
TID_Previous :
Age : 592987 seconds
famcop = 9F0C
sbc @tmu_0_11_sbc - Result of: dym dblock -body 0xDDFF9D4
The block 0xDDFF9D4 belongs to the partition 0x1004
Header
Address : 0x0DDFF994 (
232782228)
Size :0x00000040
(
64)

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 155/300

RNC & NodeB Health Check for NEV 4.2- How To

Msg Info Address : 0x0DDFF9B4 (


232782260)
32)
Block Address
: 0x0DDFF9D4 (
232782292)
Block OS type.........
Address previous block
Address next block....
Base OS block size....
Requested block size..
Tid Creator...........
Date..................
Pre-allocated Pool....

MM_USER
0x0DDFF754
0x0DDFFBD4
0x00000200
0x00000082
Iuxadm_LA
0x000001BF
0x00000000

Size :0x00000020

(0x2D2D2D2D)
(
232781652)
(
232782804)
(
512)
(
130)
(
226996224)
(
447)
(
0)

Type of block...... 0x7FFFFFFF ( 2147483647)


Message Size Sent.. 0x00000000 (
0)
Tid Current........ SIG_ALU
(
183341056)
Tid Previous....... ( 4294967294)
Part ID of block... 0x00001004 (
4100)
Info............... 0x40000000
0DDFF9D4: 7A 7B 7C 7D 00 00 00 82 00 00 00 20 00
0DDFF9E4: 83 00 06 30 83 00 06 30 00 24 00 24 00
0DDFF9F4: 00 00 00 00 00 12 11 57 00 00 00 00 00
0DDFFA04: FF FF 00 00 00 00 00 00 53 49 47 5F 41

00
00
00
4C

00
00
00
55

00
00
00
00

7.8.1.4 number of call running on the RNC


set option C to No
launch option 2 (uecall) would say on each tmu
###################### TMU 0_11 - ue_call lscallctxid - 16_May_14h01m25s
######################
Number of ue_call contexts : 8

7.8.1.5 Overload status


launch option 22
###################### RNC Overload Level - 16_May_15h09m06s
######################
OMU_9 => ovLevel=0
OMU_5 => ovLevel=0
TMU_0_11 => ovLevel=0
TMU_1_11 => ovLevel=0
TMU_1_12 => ovLevel=0
TMU_1_13 => ovLevel=0
CN OvLevel = 0 ( max module Ovlevel )
IN OvLevel = 0
BSC OvLevel = 0 ( max CN IN Ovlevel )
QOS Alarm OFF

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 156/300

RNC & NodeB Health Check for NEV 4.2- How To

ovLevel are from 0 to 5, 0 is ok.


You can also use other options for specific issues.

7.8.2. TMU
CLASSIC/COMPACT
Calls established (or establishing) can be seen from TMU and PMC Master.
From the TMU, the ue_call menu will be mainly used.
From the PMC Master, rmanCaCallList lists the calls.
For near all component, you might set at first the CP where use ci manager by using
<component> lscp
telci(tmu)> rrmcell listCP
Result of: rrmcell listCP
*** Following Core Process Numbers are created: ***
cpNumber 4
*** Created Core Process Numbers end of list. ***

<component> setcp
telci(tmu)> rrmcell setcp 4
Result of: rrmcell setcp 4
Old cp: 0
New cp: 4

Example:
Through getCellInfo, determine which TMU is managing the cell you are interested in.
Open a telci session, then use :
rrmcell list
Eventually you may check if your cell is managed by the TMU you are logged onto:
TELNET_CI> rrmcell list
sbc @tmu_1_12_sbc - Result of: rrmcell list
*** List of the managed cells ***
Cell 2041 is Managed and Unlocked
Cell 1195 is Managed and Unlocked
Cell 2043 is Managed and Locked
Cell 2044 is Managed and Locked
Cell 2045 is Managed and Locked
There is 5 cells managed
There is 3 cells managed Locked
There is 2 cells managed Unlocked
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 157/300

RNC & NodeB Health Check for NEV 4.2- How To

rrmcell info internalCellId


To display additional information on a specific cell according to its cellid (2041 here):
scrambling code, uplink and downlink frequencies, diversity information
telci(tmu)> rrmcell info 1195
Result of: rrmcell info 1195
*** Display miscellaneous info for Cell 1195 ***
scrambling code = 118
uarfcnForNu = 9787
uarfcnForNd = 10637
isTxDiversityIndicator = 1
txDiversityIndicator = 0
3G to 2G Redirection for Emergency Calls NOT Allowed
iCellRef (iNodebCoreProcessRef = 4, iCellRefPerNodebCP = 77)
isCdma1xMobilityInfo = FALSE
HSDPA Configuration is present
==============================
HS-PDSCH codes (SF 16, level 2): first code number 11, number of codes 5
HS-SCCH codes (SF 128, level 5): list of codes 87 , number of codes 1
HSDPA codes are allocated.
hsdpaMaxPower = 9.33 Watt (39.70 dBm)
Max number of HSDPA users in a cell is 20
Current number of HSDPA users is 0
The global HSDPA flag isHsdpaConfigured is TRUE.
isUlCapacityThreshold = 0
ulCapacityThreshold = 255
currentULLoad = 0

ue_call lscallctxid
To list all the call established on one TMU :
telci(tmu)> ue_call lscallctxid
Result of: ue_call lscallctxid
===================================================================
=== Lists ue_call ctxId, traceKey, IMSI and H-RNTI of all established calls ===
===================================================================
Dump of each ueCallCtxtId (tracekey, start date):
------------------------------------------------> 7803 (0x80005e7b, 2006/04/13 16:53:41.175):
IMSI: 0x2 0 8 1 1 0 0 0 0 0 2 1 6 4 3
H-RNTI: 0x284b
HS-PDSCH RL id: 0
Total: 1

Here, a call with the IMSI 0x208110000021643 and tracekey 0x80005e7b is established.
The ueCallCtxtId will identify the call for the other commands (10 in this example)
related to ue_call menu, but most of all, the tracekey is the unique identifier of the call
within RNC applications (CN & IN).
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 158/300

RNC & NodeB Health Check for NEV 4.2- How To

ue_call callstatus ueCallCtxtId


To identify the type of call: CS and/or PS, and the type of the cell (capacity/coverage)
===================================================================
===
Displays the status of a call
===
===================================================================
UeCall context Id : 5145
IMSI : 0x2 0 8 1 1 0 0 0 0 0 2 0 4 3 9
rrcStateIndic
: CELL FACH
establishmentCause : ORG_BACK_CALL
error : NO ERROR
isL1DchSetup
: FALSE
isL1FachSetup
: TRUE
isDBearerSetup
: TRUE
isHsdpaSupported
: TRUE
iuState
: SIG RAB PS
rrcState
: RRC CONNECTED
nbUeCleanIndToReceive : 0
scope: COVERAGE SCOPE
Power Balancing not activated
is Ue Irm Preemption Timer activated ? TRUE
raPingPongTimer is running: FALSE

The call is a PS call.


ue_call listactivset ueCallCtxtId
To display the active set list for a call
telci(tmu)> ue_call listactivset
Result of: ue_call listactivset

576
576

===================================================================
===
Displays active set cells of a call
===
===================================================================
UeCall context Id: 576
rlId: 5
intraFreqCellId : 8 primaryScramblingCode : 105
cellId : 184

ue_call rabinfo ueCallCtxtId


Lists the radio bearers used by a ue, from the TMU perspective.
telci(tmu)> ue_call rabinfo 576
Result of: ue_call rabinfo 576
===================================================================
=== Displays rab info - id, integrity, ciphering, ...- of a call ===
===================================================================

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 159/300

RNC & NodeB Health Check for NEV 4.2- How To


UeCall context Id: 576
Signalling
---------integrity status : STARTED
nr Of Signal Rb : 4
signal rbId : 1 ulRlcMode :
signal rbId : 2 ulRlcMode :
signal rbId : 3 ulRlcMode :
signal rbId : 4 ulRlcMode :
Latest configured CN domain

UM dlRlcMode
AM dlRlcMode
AM dlRlcMode
AM dlRlcMode
: PS DOMAIN

:
:
:
:

UM
AM
AM
AM

CS Domain
--------start value CS : 0
ciphering state CS : FALSE
nr Of Cs Rab: 0
No Rab With Flow
PS Domain
--------start value PS : 0
ciphering state PS : FALSE
nr Of Ps Rab: 1
Rab Without Flow
rabIdType : GSM MAP rabId : 5
UL rb set id : 0
DL rb set id : 6
rbId : 5 ulRlcMode : AM dlRlcMode : AM
nb HS-DSCH mac-d flows : 0
isHarqInfo : FALSE
Dl transport channel : 0

In this case, one rab is established:


UL RB_SET at 0 : PS 64
DL RB_SET at 6 : PS 128 PS call 64/128.
The mobile is performing a PS call (64/128).
See RBSet & AsConf Id for the RBsetId and AsConf description.
ue_call histocall ueCallCtxtId
Use to display a call history, example of a call is detailed below:
The call was first established in PS (PS Domain) then the radio bearer was resized to
allow both CS and PS calls.
See the comments in log .

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 160/300

RNC & NodeB Health Check for NEV 4.2- How To

Example:
TELNET_CI> ue_call histocall
10
sbc @tmu_1_12_sbc - Result of: ue_call histocall
==========================================
===
Displays History
===
UeCall context Id: 10

10

UECALL: INITIALACCESSREQ,scramblingCode: 30,uEIdType: TMSI LAI GSM,establishmentCause: ORG_BACK_CALL


RRC_CNX_REQ: ulAsConfId=2, dlAsConfId=3, establishmentCause=3
UECALL: RRC_ESTAB
UE_CAPABILITIES_ANALYSIS_FOR_INTERRAT: newGsmCModeState=2, supportOfGsm=1, measSupportOnGsm=1
UE_CAPABILITIES_ANALYSIS_FOR_INTERFREQ: newFddCModeState=1, measSupportOnInterFreq=0
MEAS_CTRL_SETUP: nrOfMeas=1, isFachTVMConfigured=0
UECALL: INITIALDIRECTTRANSFERT, cnDomainInd
: PS DOMAIN
UECALL: IUD_ESTAB
UECALL: COMMONID
UECALL: RABASSREQ, cnDomainInd
: PS DOMAIN, nrOfRabsToSetup
: 1, nrOfRabsToRelease : 0
RAB_ASSIGN: rabId=5, CnDomain=1, maxBitRate[0]=384000
RB_SET_MATCHING: ulRbSetId=0, dlRbSetId=7
IRM_CAC: ARPriority=1, refDlRbSetId/OutputDlRbSetId=7/7, radioLinkColor/cellColor=1/0
UL_AS_CONF_MATCHING: ulAsConfId=0
DL_AS_CONF_MATCHING: dlAsConfId=7
COMPRESS_MODE_CONFIGURATION: Activation deltaCfn=152, Sho deltaCfn=100, nbCModeGapPatterns=2
UECALL: RECONF
UECALL: INITIALDIRECTTRANSFERT, cnDomainInd
: CS DOMAIN
UECALL: IUD_ESTAB
UECALL: COMMONID
UECALL: RABASSREQ, cnDomainInd
: CS DOMAIN, nrOfRabsToSetup
: 1, nrOfRabsToRelease : 0
RAB_ASSIGN: rabId=1, CnDomain=0, maxBitRate[0]=12200
RB_SET_MATCHING: ulRbSetId=5, dlRbSetId=5
IRM_CAC: ARPriority=1, refDlRbSetId/OutputDlRbSetId=7/9, radioLinkColor/cellColor=2/0
UL_AS_CONF_MATCHING: ulAsConfId=8
DL_AS_CONF_MATCHING_FAILURE: dlRbSetId_1=-1, dlRbSetId_2=9, dlRbSetId_3=1
DL_RB_SET_RESIZING: refDlRbSetId=7, curDlRbSetId=3, newDlRbSetId=255
DL_AS_CONF_MATCHING: dlAsConfId=10
UECALL: RECONF

Few highlights :
UECALL: INITIALACCESSREQ, scramblingCode: 30, uEIdType: TMSI LAI GSM ,
establishmentCause: ORG_BACK_CALL

Call being established on the scrambling code 30.


The establishment cause is originating background call => PS call.
RRC_CNX_REQ: ulAsConfId=2, dlAsConfId=3, establishmentCause=3
UECALL: RRC_ESTAB

A RRC Connection Request is sent by the mobile ulAsConfId/dlAsConfId 3/2 the


message is sent on SRB 3.4 channels, establishment cause: originating background call.
UE_CAPABILITIES_ANALYSIS_FOR_INTERRAT: newGsmCModeState=2, supportOfGsm=1,
measSupportOnGsm=1

In the RRC connection setup complete, the mobile informs the Core Network about its
capabilities.
InterRAT (Rat for Radio Access Technology) describes the ability of the mobile to
switch to other technologies (for example: GSM).
Here GSM is supported and measurements on GSM bearers also.
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 161/300

RNC & NodeB Health Check for NEV 4.2- How To

UE_CAPABILITIES_ANALYSIS_FOR_INTERFREQ: newFddCModeState=1, measSupportOnInterFreq=0

Regarding interfreq, no measurement on other frequencies blind ho will be performed.


MEAS_CTRL_SETUP: nrOfMeas=1, isFachTVMConfigured=0
UECALL: INITIALDIRECTTRANSFERT, cnDomainInd
UECALL: IUD_ESTAB
UECALL: COMMONID

: PS DOMAIN

An RRC Initial Direct transfer message is sent, the domain is PS beginning


negociation of the PS call between the RNC and the Core Network.
UECALL: RABASSREQ
nrOfRabsToRelease

, cnDomainInd

: PS DOMAIN, nrOfRabsToSetup

: 1,

: 0

A RAB assignment request is received by the RNC from the Control Node, to setup one
RAB.
RAB_ASSIGN: rabId=5, CnDomain=1, maxBitRate[0]=384000
RB_SET_MATCHING: ulRbSetId=0, dlRbSetId=7

The core network is asking for dlRbSetId/ulRbSetId 7/0 (PS 384/64) in the rab
assignment request.
IRM_CAC: ARPriority=1, refDlRbSetId/OutputDlRbSetId=7/7, radioLinkColor/cellColor=1/0

Before being granted the RAB is first validated by the RNC through IRM CAC, to
eventually resize the RAB according to the colours of the radio link and the cell.
RadiolinkColor: 0= good 1=bad here the radiolink is good.
Cellcolor: 0=green, 1=yellow, 2=red the cell is green.
As the cell is not loaded, the OutputDlRbSetId that will be effectively allocated by the
RNC will suit the demand of the Core Network: 7
ARPriority stands for allocation retention priority.
UL_AS_CONF_MATCHING: ulAsConfId=0
DL_AS_CONF_MATCHING: dlAsConfId=7

The RAB is setup by the RNC ul/dlAsConfId 0/7 SRB + PS384 / SRB + PS 64
COMPRESS_MODE_CONFIGURATION: Activation deltaCfn=152, Sho deltaCfn=100,
nbCModeGapPatterns=2

Compress mode parameters.


UECALL: RECONF
UECALL: INITIALDIRECTTRANSFERT, cnDomainInd

: CS DOMAIN

A new RRC initial Direct Transfer is sent by the mobile to the CS domain (beginning of
the CS call).
UECALL: IUD_ESTAB
UECALL: COMMONID

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 162/300

RNC & NodeB Health Check for NEV 4.2- How To


UECALL: RABASSREQ
nrOfRabsToRelease

, cnDomainInd

: CS DOMAIN, nrOfRabsToSetup

: 1,

: 0

A new rab assignement request is sent by the core


RAB_ASSIGN: rabId=1, CnDomain=0, maxBitRate[0]=12200
RB_SET_MATCHING: ulRbSetId=5, dlRbSetId=5

u/dlRbSetId 5/5 requested : CS 12.2 VBR / CS 12.2 VBR.


In V3.1, the rab ps is downsized as CS + PS @ 384 calls are not supported in this release.
The rate will be downsized below, which makes this example quite singular.
The PS call is still going on, but its parameters still have to go through IRM_CAC for the
DL as this call is no longer PS only.
IRM_CAC: ARPriority=1, refDlRbSetId/OutputDlRbSetId=7/9, radioLinkColor/cellColor=2/0
UL_AS_CONF_MATCHING: ulAsConfId=8

The Ul As Conf Id is fixed at 8 SRB + CS 12.2 (DTX) + PS 64


DL_AS_CONF_MATCHING_FAILURE: dlRbSetId_1=-1, dlRbSetId_2=9, dlRbSetId_3=1
DL_RB_SET_RESIZING: refDlRbSetId=7, curDlRbSetId=3, newDlRbSetId=255
DL_AS_CONF_MATCHING: dlAsConfId=10

The DL is resized to match a supported value: 10 SRB + CS 12.2 (DTX) + PS 64


UECALL: RECONF

The call was first PS 384/64 kbit/s then PS 64/64 + CS.


If a call is already ended, its history is saved temporarily.
ue_call lsoldhistocall
Lists of history from last ended call saved
Example:
telci(tmu)> ue_call listoldhistocall 5145
Result of: ue_call listoldhistocall 5145
===================================================================
===
Displays the list of old calls traceKeys
===
===================================================================
TraceKey : 0x8000400a
TraceKey : 0x80004087
TraceKey : 0x80005bcb

ue_call oldhistocall traceKey


Displays the history of an already ended call.
The analysis is the same as for ue_call histocall.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 163/300

RNC & NodeB Health Check for NEV 4.2- How To

Example (truncated):
TELNET_CI> ue_call oldhistocall 0x8000400a
sbc @tmu_1_12_sbc - Result of: ue_call oldhistocall 0x8000400a
===================================================================
===
Displays all History
===
TraceKey : 0x8000400a
IRM_CAC: ARPriority=1, refDlRbSetId/OutputDlRbSetId=7/9,
radioLinkColor/cellColor=2/0
UL_AS_CONF_MATCHING: ulAsConfId=0
DL_AS_CONF_MATCHING: dlAsConfId=11
RAB_RELEASE: rabId=1, CnDomain=0
CN_DOMAIN_RELEASE: domain=0
UECALL: RECONF
UECALL: IUDCLEANIND
UECALL: RABASSREQ
, cnDomainInd
: PS DOMAIN,
nrOfRabsToSetup
: 0, nrOfRabsToRelease : 1
UL_AS_CONF_MATCHING: ulAsConfId=2
DL_AS_CONF_MATCHING: dlAsConfId=3
RAB_RELEASE: rabId=5, CnDomain=1
UECALL: RECONF
UECALL: RELEASECMD
, cnDomainInd
: PS DOMAIN

Ue_call measstate ueCallCtxtId


List status of measurements for a call
TELNET_CI> ue_call measstate
10
sbc @tmu_1_12_sbc - Result of: ue_call measstate

10

===================================================================
===
Displays uecall Meas State
===
UeCall context Id: 10
IntraFreqMeas available
Report Mode : Periodical
rlId: 0
intraFreqCellId : 0
primaryScramblingCode : 30
intraFreqCellId : 1
primaryScramblingCode : 0
intraFreqCellId : 2
primaryScramblingCode : 5
intraFreqCellId : 3
primaryScramblingCode : 10

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 164/300

RNC & NodeB Health Check for NEV 4.2- How To

ue_call rateadaptationinfo ueCallCtxtId


telci(tmu)> ue_call rateadaptationinfo 5145
Result of: ue_call rateadaptationinfo 5145
===================================================================
===
Displays rate adaptation information of a call
===
===================================================================
rabIdType : GSM MAP rabId : 5
cnDomainInd : PS DOMAIN
alwaysOnState : DOWNGRADED
irmSchedulingState : INITIAL
irmPreemptionState : ELIGIBLE
dlRbAdaptationState : NOT ELIGIBLE
ulRbAdaptationState : NOT ELIGIBLE
measId : 1 measState : NOT ACTIVATED
measId : 2 measState : ACTIVATED
measId : 3 measState : NOT ACTIVATED
measId : 4 measState : NOT ACTIVATED
measId : 5 measState : NOT ACTIVATED
measId : 6 measState : NOT ACTIVATED
dlAsConfId : 19
dchFpId : 6
dchFpId : 9

ulAsConfId : 15

rabIndex : 0
rabId : none

isDlDpchSlotFormatInfo: 0

ulRbSetId : 11 dlRbSetId : 13
ulRbSetId : 9 dlRbSetId : 11

ue_call rlinfo ueCallCtxtId


telci(tmu)> ue_call rlinfo 576
Result of: ue_call rlinfo 576
===================================================================
===
Displays rl informations of a call
===
===================================================================
UeCall context Id: 576
Primary RL informations
scrambling code : 104
uarfcn for Nu : 9787
uarfcn for Nd : 10637
cellIdRef
: UcId (RncId, Cid): (20,174)
plmnId : 2 248 17
is Gsm Meas activation allowed : FALSE
is InterFreq Meas activation allowed : FALSE
isInterFreqHHO allowed : FALSE
nb periodic report before switch to event : 5
RL informations
rlId : 4
UcId (RncId, Cid): (20,174)
frame offset : 251
chip offset : 38123
max Allowed Ul Tx power : 24
rl auto state :

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 165/300

RNC & NodeB Health Check for NEV 4.2- How To

ue_call available commands and displays.


TELNET_CI> ue_call
sbc @tmu_1_12_sbc - CI warning... Ambiguous command: ue_call
ue_call clads
: Dumps ue_call static data
ue_call cladp
: Dumps ue_call permanent data
ue_call lscp
: Lists the core process created on a TMU
ue_call setcp
: Sets the current core process
ue_call clactx
: Dumps ue_call class context
ue_call printctxstat
: Displays statistic information about pools and
contexts
ue_call lscallctxid
: Lists ue_call ctxId, traceKey, IMSI and H-RNTI of all
established calls
ue_call cnaut
: Displays ue_call cnaut transition of a call
ue_call callstatus
: Displays the status of a call
ue_call listcndomain
: Displays the established domains of a call
ue_call rabinfo
: Displays rab informations (id, integrity,
ciphering, ...) of a call
ue_call rlinfo
: Displays rl informations of a call
ue_call locationinfo
: Displays location informations of a call
ue_call listactivset
: Displays active set cells of a call
ue_call measstate
: Displays measurement states of a call
ue_call uecapabilities : Displays UE capabilities of a call
ue_call cmodestate
: Displays compressed mode states of a call
ue_call rateadaptationinfo: Displays rate adaptation information (alwaysOn, irm
scheduling, ...) of a call
ue_call irmschedupg
: Displays irm scheduling upgrade information of a call
ue_call internal_counters: Display Call Internal Counters
ue_call irmscheddowng
: Displays irm scheduling donwgrade information of a
call
ue_call histoCall
: Displays historic of a call
ue_call listoldhistocall: Displays the list of old calls traceKeys
ue_call oldhistocall
: Displays historic of a old call (referenced by a
traceKey)
ue_call lastdec
: Displays the last decisions taken
ue_call help
: Displays information about all the commands available
in ue_call
ue_call listalluectxinfo: Display relevant call context information for all
calls of a CP_UE
ue_call srlrDeltaMsgSize: Displays info about srlr size msg (differences and
static datas)
ue_call resetSrlrSize
ue_call rlRecoved

: reset fields ueCallSrlrDeltaSize of ue_call class ctx


: Display the number of Rl been recovered after RlFailed

rrmded gethisto
Prints the last events decided by uerrm.
rrmded clrhisto may be useful first, as all the last events of the mobiles managed by the
tmu will be dumped.
Not to be used in case of heavy traffic, but more in a lab configuration.
The messages can be linked to the tracekey referenced (below the messages concern
0x80004009 and 0x8000400a).

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 166/300

RNC & NodeB Health Check for NEV 4.2- How To


TELNET_CI> rrmded gethisto
sbc @tmu_1_12_sbc - Result of: rrmded gethisto
10:27:55
0 80004009 RRC_CNX_REQ: ulAsConfId=2, dlAsConfId=3,
establishmentCause=3
10:27:55
1 80004009 UE_CAPABILITIES_ANALYSIS_FOR_INTERRAT:
newGsmCModeState=2, supportOfGsm=1, measSupportOnGsm=1
10:27:55
2 80004009 UE_CAPABILITIES_ANALYSIS_FOR_INTERFREQ:
newFddCModeState=1, measSupportOnInterFreq=0
10:27:55
3 80004009 MEAS_CTRL_SETUP: nrOfMeas=1, isFachTVMConfigured=0
10:28:24
4 8000400a RRC_CNX_REQ: ulAsConfId=2, dlAsConfId=3,
establishmentCause=3
10:28:25
5 8000400a UE_CAPABILITIES_ANALYSIS_FOR_INTERRAT:
newGsmCModeState=2, supportOfGsm=1, measSupportOnGsm=1
10:28:25
6 8000400a UE_CAPABILITIES_ANALYSIS_FOR_INTERFREQ:
newFddCModeState=1, measSupportOnInterFreq=0
10:28:25
7 8000400a MEAS_CTRL_SETUP: nrOfMeas=1, isFachTVMConfigured=0
10:28:26
8 8000400a RAB_ASSIGN: rabId=5, CnDomain=1, maxBitRate[0]=384000
10:28:26
9 8000400a RB_SET_MATCHING: ulRbSetId=0, dlRbSetId=7

Number of calls established on a cell ?


Rrmcell ucode cellIdentifier
get number of codes used for a cell
TELNET_CI> rrmcell ucode 2041
sbc @tmu_1_12_sbc - Result of: rrmcell ucode 2041
*** Display used codes for Cell 2041 ***
There is 0 used codes for SF 4 in cell 2041
There is 0 used codes for SF 8 in cell 2041
There is 0 used codes for SF 16 in cell 2041
There is 0 used codes for SF 32 in cell 2041
There is 1 used codes for SF 64 in cell 2041
There is 0 used codes for SF 128 in cell 2041
There is 4 used codes for SF 256 in cell 2041
signalling
There is 5 used codes for cell 2041 on the whole

used for RAB assignment


used for

SF 64 and 256 are reserved for rab assignment and SRB.


In theory:
DL SF =128 DL data rate = 8 kbit/s
CS
DL SF = 32 DL data rate = 64 kbit/s
PS 64 kbit/s
DL SF = 16 DL data rate = 128 kbit/s
PS 128 kbit/s
DL SF = 8
DL data rate = 384 kbit/s
PS 384 kbit/s
DL SF = 4
DL data rate = 2 Mbit/s
PS 2 Mbit/s

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 167/300

RNC & NodeB Health Check for NEV 4.2- How To

Examples:
One CS call established:
TELNET_CI> rrmcell ucode 2041
sbc @tmu_1_12_sbc - Result of: rrmcell ucode 2041
*** Display used codes for Cell 2041 ***
There is 0 used codes for SF 4 in cell 2041
There is 0 used codes for SF 8 in cell 2041
There is 0 used codes for SF 16 in cell 2041
There is 0 used codes for SF 32 in cell 2041
There is 1 used codes for SF 64 in cell 2041
There is 1 used codes for SF 128 in cell 2041
There is 4 used codes for SF 256 in cell 2041
There is 6 used codes for cell 2041 on the whole

One PS call established:


TELNET_CI> rrmcell ucode 2041
sbc @tmu_1_12_sbc - Result of: rrmcell ucode 2041
*** Display used codes for Cell 2041 ***
There is 0 used codes for SF 4 in cell 2041
There is 1 used codes for SF 8 in cell 2041
There is 0 used codes for SF 16 in cell 2041
There is 0 used codes for SF 32 in cell 2041
There is 1 used codes for SF 64 in cell 2041
There is 0 used codes for SF 128 in cell 2041
There is 4 used codes for SF 256 in cell 2041
There is 6 used codes for cell 2041 on the whole

rrmcellavailable commands and displays.


telci(tmu)> rrmcell
CI warning... Ambiguous
rrmcell help
rrmcell setcp
rrmcell list
rrmcell neigh
rrmcell info
rrmcell fcode
rrmcell fSF
SF level for a cell
rrmcell rcode
rrmcell ucode
rrmcell icode
rrmcell stcode
rrmcell power
rrmcell dlPowerAlloc
rrmcell cellfachusers
CellFach state
rrmcell gethisto
global history
rrmcell acthisto
rrmcell deshisto
rrmcell clrhisto
rrmcell dispglobalhisto
rrmcell selglobalhisto
rrmcell dispcellhisto

command: rrmcell
: Help about RRM_CELL CI Manager
: Set the current core process
: get the list of cells managed by RRM_CELL
: get the list of neighbouring cells for a cell
: get miscellaneous informations for a cell
: get number of free codes for a cell
: get number of free codes(variable _freeCodes[]) per
:
:
:
:
:
:
:

get
get
get
get
get
get
get

number of reserved codes for a cell


number of used codes for a cell
number of inherited codes for a cell
state of each code of the tree for a cell
info on power for a cell
info on DL power allocation for a cell
the max/current number of Mac-C users for a

: get the history and print the last elements of the


:
:
:
:
:
:

activate Cellrrm decision history service


de-activate Cellrrm decision history service
clear the Cellrrm decision history buffers
display global Cellrrm decision history
select Cellrrm decision history for a cell
display the history contained in a cell context
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 168/300

RNC & NodeB Health Check for NEV 4.2- How To


rrmcell cellColor
: get the cellColor information for a cell
rrmcell cellColorThreshold: get the cellColorThreshold and irmIubLoadQos
information for a cell
rrmcell listNodebPerCP : for the present NodebCP, lists the created nodeBs
rrmcell cnaut
: display nobrrm automaton history
rrmcell cellIrmPreemptionColor: get the irm preemption cellColor information
for a cell
rrmcell cellIrmPreemptionColorThreshold: get the irm preemption
cellColorThreshold and irmPreemptionIubLoadQos information for a cell
rrmcell sib11.intraFreqMeasQuantity: display sib11.intraFreqMeasQuantity for a
FDDCell
rrmcell sib11.reportingInfoForCellDchState: display
sib11.reportingInfoForCellDchState for a FDDCell
rrmcell sib11.all
: display sib11.all for a FDDCell
rrmcell listCP
: display list of created CP numbers
rrmcell getHsdpaClassConfRef: display HSDPA configuration for the cell
rrmcell getCurrentNumberOfHsdpaUsers: get the current number of HSDPA users in
the cell
rrmcell getCurrentUlAsconfWeights: get the current UL Asconf weight
rrmcell setNewAsconfWeight: set a new asconf weight

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 169/300

RNC & NodeB Health Check for NEV 4.2- How To

7.8.3. RBSet & AsConf Id


V4.2
DL
AsConfId
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29

SRB
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB FACH
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB FACH
SRB 13.6
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4

Traffic 1
CSD 64
CS 12.2 (CBR)
PS I/B 64
PS I/B 8
CS 12.2 (VBR)
PS I/B 128
PS I/B 384
CS STR 14.4
CS 12.2 (CBR)
CS 12.2 (VBR)
PS I/B 32
PS I/B 256

Traffic 2

PS I/B 64
PS I/B 64

CS STR 57.6
CS 12.2 (CBR)
PS I/B 8
CS 12.2 (VBR)
PS I/B 8
CS 12.2 (CBR)
PS I/B 128
CS 12.2 (VBR)
PS I/B 128
PS I/B FACH
Only supported on DRNC
CSD 64
PS I/B 64
CS 12.2 (VBR)
PS I/B 384
PS STR 64
PS STR 64
PS I/B 8
PS I/B 64 (Mux)
CS 12.2 (VBR)
PS I/B 64 (Mux)
PS HS-DSCH
NOT USED
CSD 64
PS I/B 8

UL
AsConfId
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

SRB
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB RACH
SRB 3.4
SRB 3.4
SRB 3.4
SRB RACH
SRB 13.6
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4
SRB 3.4

Traffic1
PS I/B 64
CS 12.2 (CBR)

CS (STR) 57.6
CS 12.2 (CBR) PS I/B 8
CS 12.2 (VBR) PS I/B 8
PS I/B Rach
Only supported on DRNC
CSD 64
PS I/B 64
PS STR 16
PS STR 16
PS I/B 8
PS I/B 64 Mux
CS 12.2 (VBR) PS I/B 64 Mux
PS I/B 384

SRB 3.4

CSD 64

PS I/B 32
CSD 64
CS 12.2 (VBR)
CS STR 14.4
CS 12.2 (CBR)
CS 12.2 (VBR)
PS I/B 8
PS I/B 128

Traffic2

PS I/B 64
PS I/B 64

PS I/B 8

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 170/300

RNC & NodeB Health Check for NEV 4.2- How To

DL Rbset
Id
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

Dom
CS
N/A
CS
PS
PS
CS
PS
PS
CS
PS
PS
N/A
CS
PS
N/A
PS
PS
PS

Type
Data
SRB
Speech
I/B
I/B
Speech
I/B
I/B
Stream
I/B
I/B
SRB
Stream
I/B
SRB
Stream
I/B Mux
I/B

UL Rbset
Id
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

Rate
64
3.4
12.2 CBR
64
8
12.2 VBR
128
384
14.4
32
256
FACH
57.6
FACH
13.6
64
64
HS-DSCH

Dom
PS
N/A
CS
PS
CS
CS
CS
PS
PS
N/A
CS
PS
N/A
PS
PS
PS

Type
I/B
SRB
Speech
I/B
Data
Speech
Stream
I/B
I/B
SRB
Stream
I/B
SRB
Stream
I/B Mux
I/B

Rate
64
3.4
12.2 CBR
32
64
12.2 VBR
14.4
8
128
RACH
57.6
RACH
13.6
16
64
384

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 171/300

RNC & NodeB Health Check for NEV 4.2- How To

7.8.4. Establishment cause (REC 25.331 R99).


Cause for an RRC connection establishment request.
Establishment cause

0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

Originating Conversational Call


Originating Streaming Call
Originating Interactive Call
Originating Background Call
Originating Subscribed traffic Call
Terminating Conversational Call
Terminating Streaming Call
Terminating Interactive Call
Terminating Background Call
Emergency Call
Inter-RAT cell re-selection
Inter-RAT cell change order
Registration

Detach
Originating High Priority Signalling
Originating Low Priority Signalling
Call re-establishment
Terminating High Priority Signalling
Terminating Low Priority Signalling

Terminating cause unknown

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 172/300

RNC & NodeB Health Check for NEV 4.2- How To

7.9. IN Counters on User Plane


Counters on the IN for a given call (tracekey) are useful in case of dropped frames,
unexpected CFN, synchronization issues, crc errors, to determine the quality of the
user plane.
For Iub
dumpIubOamCounter(tracekey)
For Iu
dumpIuOamCounter(tracekey)
For TTI
dumpTtiOamCounter(tracekey)
For Gtpu
dumpGtpuOamCounter(tracekey)
0. Identify the TMU in charge of the NodeB.
getCellInfo
1. The tracekey of the call is found on the TMU,
ue_call lscallctxid
2. The PMC-M provides the PMC id of the RAB in charge of the call,
rmanCaDumpTracekeys
3. Connect onto the RAB, and dump the counters
Examples for a PS / CS calls:
First example: PS call
The TMU 1 11 was identified thanks to getCellInfo.
The IMSI we are interested in is 450001111111521
RNC1206_OMU2:/OMU (omu) $ telci tmu_1_11_sbc
Trying...
Connected to tmu_1_11_sbc.
TELNET_CI> ue_call lscallctxid
sbc @tmu_1_11_sbc - Result of: ue_call lscallctxid

===================================================================
=== Lists ue_call ctxId, traceKey, IMSI and H-RNTI of all established calls
===
===================================================================
Dump of each ueCallCtxtId (tracekey, start date):
------------------------------------------------> 1200 (0x800004b0, 2006/05/02 08:29:06.456):

0x800004b0
2147484848 in decimal

IMSI: 0x4 5 0 0 0 1 1 1 1 1 1 1 5 2 1
Neither HS-PDSCH RL nor H-RNTI allocated

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 173/300

RNC & NodeB Health Check for NEV 4.2- How To


number of call contexts: 1

On the interface node identify the active PMC-M and retrieve the HW id of the RAB.
1> d lp/* ap/* rnc role
Lp/* Ap/* RncAp
+==+==+-------+---------------------------------------|Lp|Ap| role |Response
+==+==+-------+---------------------------------------| 2| 0|aMaste |
[]
2> d lp/2 ap/0 ip
Lp/2 Ap/0
ipAddress = 172.253.202.79
3> telnet -ip(172.253.202.79) vr/1
Trying 172.253.203.79...
Connected to 172.253.203.79.
Escape character is '^]'
-> rmanCaDumpTraceKeys
May 02 2006
10:48:54.556
******Begin to list all traceKeys******
-TraceKey-PmcId(Hex)- CallId--------------------------------------- 133097 - 0x304 - - 2 - 133094 - 0x305 - - 4 - 133095 - 0x303 - - 5 - 133096 - 0x307 - - 46 - 133093 - 0x203 - - 50 - 2147484848 - 0x407 - - 180 PMC Id: 407 lp/4 (4) ap/5 (7-2)
******end to list all traceKeys******

Note: the lp and ap numbers are be derived from the PMC id


the first digit provides the lp number
the two last digits provide the ap number + 2
0xa07 lp/10 ap/5
0xa05 lp/10 ap/3
0x403 lp/4 ap/1
0x407 lp/4 ap/5
Identify the RAB ip address and dump the counters
13> d lp/4 ap/5 ip
Lp/4 Ap/5
ipAddress = 172.253.202.72
ok
2006-05-02 10:56:21.81
14> telnet -ip(172.253.202.72) vr/1
-> dumpGtpuOamCounter(2147484848)
May 02 2006
10:58:01.598
GTP-U Local trLayerRef = (0x407,0,0x78)
GTP-U Local curVsockId_m
= 120

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 174/300

RNC & NodeB Health Check for NEV 4.2- How To


GTP-U Local IPAddr
GTP-U Local TeId
GTP-U Distant IPAddr
GTP-U Distant TeId
TotalFramesReceived
TotalFramesSent
= 26
TotalFramesDiscarded
TotalErrorIndicationReceived
value = 33 = 0x21 = '!'

=
=
=
=
=

0xacfdca48
120
0xa00a222
1762665115
588

Check that the frames discarded


and in error remain few during the call

= 0
= 0

Other example on a CS call


The identification of the RAB is the same.
-> dumpIuOamCounter(2147484864)
May 02 2006
11:15:35.243
===IuFpSmp::dumpOamCounter: ===
RabId:
1
VSockId:
106
totalDlDataFrames:
1568
totalHCrcErrors:
0
totalPCrcErrors:
0
totalDlFqcErrors:
0
totalUnexpectedFrameNum:
1342
totalUnexpectedPduType:
0
totalUnexpectedProcedure:
0
totalUnexpectedRfci:
0
totalUnknownPduType:
0
IuInitFailedOnRepeatedNack: 0
IuInitFailedOnTimeOut:
0
IuUpVersionNotSupport:
0
totalUnknownProcedure:
0
totalFrameTooShort:
0
totalFrameTooLong:
0
totalFrameLoss:
0
totalTARequest:
1
totalTAAckRcv:
0
taNotSupported:
1
totalTANotPossible:
0
totalHoldFramesDiscarded:
0
totalHoldPeriods:
0
totalFramesShedDueToBuffOverflow:
totalTATimeout:
0
totalDroppedInit:
0
totalDroppedRateControl:
0
totalTimeAlignNack:
0

10

CSV specific for delayered processing:


**************************************
totalDLFrameRcvd_delayer:
1580
totalDLDataFrameRcvd_delayer:
1578
totalDLCtrlFrameRcvd_delayer:
2
totalDLDataFrameSent_delayer:
1568
totalDLEmptyFrameSent_delayer:
9233
**************************************
CSD specific counters:
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 175/300

RNC & NodeB Health Check for NEV 4.2- How To

********UL counters:********
totalUlDataFrames:
0
totalUlFqcErrors:
0
totalUlFramesRcvByNrTBs[0 TBs]:
totalUlFramesRcvByNrTBs[1 TBs]:
totalUlFramesRcvByNrTBs[2 TBs]:
totalUlFramesRcvByNrTBs[3 TBs]:
totalUlFramesRcvByNrTBs[4 TBs]:
TotalUlFramesFromMAC:
0
TotalUlTBsFromMAC:
0
********DL counters:********
totalDlFramesRcvByNrTBs[0 TBs]:
totalDlFramesRcvByNrTBs[1 TBs]:
totalDlFramesRcvByNrTBs[2 TBs]:
totalDlFramesRcvByNrTBs[3 TBs]:
totalDlFramesRcvByNrTBs[4 TBs]:
TotalDlFramesToMAC:
0
TotalDlTBsToMAC:
0
value = 25 = 0x19

0
0
0
0
0

0
0
0
0
0

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 176/300

RNC & NodeB Health Check for NEV 4.2- How To


-> dumpIubOamCounter(2147484864)
May 02 2006
11:19:06.920
===Iub OAM Counter Dump: dchSetId=265 on UPLINK===
SRB UL
FpMode = SILENT, theHHOState=0
SILENT = when there is no data to

transmit, no frame are transmitted


IUB RL Manager
Printing IubDchRlMgr
====================
Number Of RL added = 0
addedRl =
Number Of RL active = 1
activeRl = 0x4f428bc
Number Of RL deleted = 0
deletedRl =
Printing IUB RL (non free entries)
m_iubRl[0] Addr(0x 4f428bc) => IubDchRl { Status(15), Tlr(a2p(32), GrpId(8),
cid(65)), CombRlGrpId(0), Socket(105) }
TotalUlDataFramesReceived=889
Check that this counter is incremented
TotalUlDataFrames=886
TotalUlDataFramesToMac=886
ErrorUlDataFrames=0
TotalUlOuterLoopPwrCtrlFrames=0
TotalUlFramesDiscardedInOv=0
===Iub OAM Counter Dump: dchSetId=265 on DOWNLINK=== SRB DL
FpMode = SILENT
NoTrafficMode is false
TopLayers=
IUB RL Manager
Printing IubDchRlMgr
====================
Number Of RL added = 0
addedRl =
Number Of RL active = 1
activeRl = 0x4f3bb8c
Number Of RL deleted = 0
deletedRl =
Printing IUB RL (non free entries)
m_iubRl[0] Addr(0x 4f3bb8c) => IubDchRl { Status(15), Tlr(a2p(32), GrpId(8),
cid(65)), CombRlGrpId(0), Socket(105) }
TotalDlDataFrames=29
TotalDlFillerDataFrames=10
ErrorDlDataFrames=0
TotalDlTrChSyncFrames=44
if these counters increment, synchro
TotalUlTrChSyncFrames=44
should be ok
TotalUlTimingAdjustmentFrames=0
ErrorUlCtrlFrames=0
totalDchXoffFrameRecieved=0
totalDchXoffFrameDropped=0
===Iub OAM Counter Dump: dchSetId=1 on UPLINK===
FpMode = NORMAL, theHHOState=0

TRB UL

IUB RL Manager
Printing IubDchRlMgr
====================
Number Of RL added = 0
addedRl =
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 177/300

RNC & NodeB Health Check for NEV 4.2- How To


Number Of RL active = 1
activeRl = 0x4f2962c
Number Of RL deleted = 0
deletedRl =
Printing IUB RL (non free entries)
m_iubRl[0] Addr(0x 4f2962c) => IubDchRl { Status(15), Tlr(a2p(32), GrpId(8),
cid(66)), CombRlGrpId(0), Socket(107) }
TotalUlDataFramesReceived=21382
TotalUlDataFrames=21382
TotalUlDataFramesToMac=0
ErrorUlDataFrames=0
TotalUlOuterLoopPwrCtrlFrames=240
TotalUlFramesDiscardedInOv=0
-----------DE Layering Counters --------------------TotalULFrameRcvd_delayer : 2737
TotalULFrameSentbyIub_delayer : 2737
TotalULDhoFrame_delayer : 21382
TotalUlFqcErrors : 0
-----------DE Layering Counters --------------------===Iub OAM Counter Dump: dchSetId=1 on DOWNLINK===
TRB DL
FpMode = SILENT
NoTrafficMode is false
TopLayers=0x4f1f6a4
IUB RL Manager
Printing IubDchRlMgr
====================
Number Of RL added = 0
addedRl =
Number Of RL active = 1
activeRl = 0x4f2109c
Number Of RL deleted = 0
deletedRl =
Printing IUB RL (non free entries)
m_iubRl[0] Addr(0x 4f2109c) => IubDchRl { Status(15), Tlr(a2p(32), GrpId(8),
cid(66)), CombRlGrpId(0), Socket(107) }
TotalDlDataFrames=0
TotalDlFillerDataFrames=45
ErrorDlDataFrames=0
TotalDlTrChSyncFrames=43
TotalUlTrChSyncFrames=43
TotalUlTimingAdjustmentFrames=0
ErrorUlCtrlFrames=0
totalDchXoffFrameRecieved=0
totalDchXoffFrameDropped=0
value = 27 = 0x1b

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 178/300

RNC & NodeB Health Check for NEV 4.2- How To

7.10. IU/IUR links check

CLASSIC
V4. 2 version
From V4.0, the SS7 and MTP layers are now managed at the IN level.
Commands are the same on the IN for RNC classic and compact.
Check first that IU ranap cs, IU ranap ps and alcap are ready to ensure traffic.
Check the provisioning of ss7
4> d -p ss7 *
Ss7 Sccp/*
+====+------+-----+----+---+----+---+-----|Sccp| maxC |class|tCon|tIa|tIar|tRe|tRepea
|
|
|OfSer|nEst| s |seco| l | tRel
|
|
| v |seco|sec| nds|sec|second
|
|
|0 2 | nds|ond|
|ond|
s
|
|
|
|
| s|
| s|
+====+------+-----+----+---+----+---+-----|
1| 16000|* * | 60|300| 660| 10|
10
Ss7 Mtp3/*
Use -noTabular to see hidden attributes: tQ707T2, tQ707T1, t23, t22 and t17.
+====+-----+---------------+----+----+----+----+----+----+---+----+----+--|Mtp3|mtpTy|
opc
| t1 | t2 | t3 | t4 | t5 | t6 |t10|t12 |t13 |t14
|
| pe |
|msec|msec|msec|msec|msec|msec|sec|msec|msec|sec
|
|
|
|
|
|
|
|
|
|ond|
|
|ond
|
|
|
|
|
|
|
|
|
| s|
|
| s
+====+-----+---------------+----+----+----+----+----+----+---+----+----+--|
1|mtp3b|4
| 500| 700| 500| 500| 500| 800| 30| 800| 800| 2
Ss7 SaalNni/*
+====+--------------------+----+----+----+----+----+-----+-----+-------+--+--|Saal|
link
|maxP| cc |maxC|tKee|noRe|pollT|idleT|proving|t1|t2
|Nni |
|dus |msec| c |pAl | sp |imer |imer | Mode |se|sec
|
|
|
|
|
|msec|msec| msec| msec|
|co|ond
|
|
|
|
|
|
|
|
|
|
|nd| s
|
|
|
|
|
|
|
|
|
|
| s|
+====+--------------------+----+----+----+----+----+-----+-----+-------+--+--|
1|Ss7 Mtp3/1 Ls/0 Lk/0| 500| 200|
4| 100|1500| 100| 100|neutra | 5| 30
| 17|Ss7 Mtp3/1 Ls/1 Lk/0| 500| 200|
4| 100|1500| 100| 100|neutra | 5| 30
| 33|Ss7 Mtp3/1 Ls/2 Lk/0| 500| 200|
4| 100|1500| 100| 100|neutra | 5| 30
ok
2006-05-02 11:39:54.67

Three linksets are provisioned on ss7 saalnni/1, 17 and 33.


Check that sccp, mtp3 and saalnni are all enable and active

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 179/300

RNC & NodeB Health Check for NEV 4.2- How To

3> d ss7 *
Ss7 Sccp/*
Use -noTabular to see the many hidden attributes.
+====+-----+----+-----+----------+----------+----------+----------+------|Sccp|osiAd|osiO|osiUs|tConnEstTo| tIarTo | tRelTo | repRelTo |actConn
|
| min |per | age |
|
|
|
|
+====+-----+----+-----+----------+----------+----------+----------+------|
1|unlck|ena |activ|
0|
0|
0|
0|
1
Ss7 Mtp3/*
Use -noTabular to see hidden attributes: customCntr3 and customCntr2.
+====+-----+----+-----+----------+----------+----------+----------+---------|Mtp3|osiAd|osiO|osiUs| t2Tmouts | t4Tmouts | t5Tmouts |t13Tmouts |customCntr
|
| min |per | age |
|
|
|
|
1
+====+-----+----+-----+----------+----------+----------+----------+---------|
1|unlck|ena |activ|
0|
0|
0|
0|
n/a
Ss7 SaalNni/*
Use -noTabular to see hidden attributes: customCntr3, customCntr2,
customCntr1, insvFail, pduOctRx, pduOctTx, pduRx, pduTx and noRespTo.
+====+-----+----+-----+----+------+----------+----------+----------+---------|Saal|osiAd|osiO|osiUs|card|state |
n1
|
c1
| inSrvDur | maxCcR
|Nni | min |per | age |
|
|
|
|
seconds|
+====+-----+----+-----+----+------+----------+----------+----------+---------|
1|unlck|ena |activ|
2|comple|
0|
0|
0|
0
| 17|unlck|ena |activ|
3|comple|
0|
0|
0|
0
| 33|unlck|dis |idle |
2|notSta|
1000|
0|
0|
0
ok
2006-05-02 11:43:49.36

To see on which PSFP are the saalnni:


25> os
Debug tracing directed to this OS shell.
<Welcome to DebugShell:VxWorks Version 5.3.1>
WARNING: Commands available at this interface may be service
impacting. This interface is for debugging only.
Do not proceed without proper authority and training.
Do you wish to proceed? [Yes/No]: y
OS> set unsafe
WARNING: Entering unsafe mode. Commands available from this interface are not
supported for field use without specific direction from Nortel
Networks.
OS> showSaalNniProxyInfo
ProvChanged is False
Total PSFP cards: 4
Number of SaalNni cards on A side: 1
Number of SaalNni cards on B side: 1
SaalNni proxies on two NI cards:
Pid: 4/1/2/32713
Card#: 4
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 180/300

RNC & NodeB Health Check for NEV 4.2- How To


Pid: 5/0/2/11209
Card#: 5
SaalNni proxies on A side:
[0] Pid: 2/0/2/28361
Card#: 2
provReqReceived_m = 1
hadProvData_m
= 1
# of SaalNnis: 2
SaalNni list:
saalnni/1 --> mtp3/1 ls/0 link/0
saalnni/33 --> mtp3/1 ls/2 link/0
SaalNni proxies on B side:
[0] Pid: 3/1/2/31689
Card#: 3
provReqReceived_m = 1
hadProvData_m
= 1
# of SaalNnis: 1
SaalNni list:
saalnni/17 --> mtp3/1 ls/1 link/0

To see which atmif/ vcc/ is linked to ranap cs and ranap ps.


Engineering rules define the use of the first 16 vcc (maximum) of a link for Ranap CS,
then 16 following (maximum) are for Ranap PS and the 16 following (max) are dedicated
to Alcap.
The provisioning of the SaalNni should also follow this rule, then
SaalNni 1 to 16 should be dedicated to CS, Alcap is mapped over CS.
SaalNni 17 to 32 should be dedicated to PS.
Also keep in mind that atmif/815 is used for iu link and atmif/807 for iur links.
To find the provisioned vcc:
38> d -p ss7 saalnni/*

nap

Ss7 SaalNni/* Nap


+=======+--------------------+---------------------------------------|SaalNni|
atmConn
|Response
+=======+--------------------+---------------------------------------|
1|AtmIf/815 Vcc/1.32 |
|
| Nep
|
|
17|AtmIf/815 Vcc/2.32 |
|
| Nep
|
|
33|AtmIf/807 Vcc/3.32 |
|
| Nep
|
ok
2006-05-02 13:48:54.24

Here on the AtmIf/815 (IU link) vcc/1.32 is used for signaling CS and vcc/2.32 for
signaling PS.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 181/300

RNC & NodeB Health Check for NEV 4.2- How To

In case of problem, check that atm cells are sent and received on these vcc and that its
increasing.
d atmif/xx vcc/yy txcell,rxcell
If the tags are provisioned, d p atmif/815 vcc/* vcd tag can give indications on the use
of the VCC.
Below, 1.32 is used for signaling CS (as we saw before), 1.48 is the user plane CS, 2.32
is the signaling for the PS, 2.48, 2.49, 2.50 and 2.51 are the four VCC used for the PS
user plane (these VCC will be used according to the IpQos requested).
39>

d -p atmif/815 vcc/* vcd tag

AtmIf/815 Vcc/* Vcd


+==========+--------------------+---------------------------------------|
Vcc
|
tag
|Response
+==========+--------------------+---------------------------------------|1.32
|CP+CS+0+2_0
|
|1.48
|UP+CS+48+2_300
|
|2.32
|PS+CCP+00+2_1
|
|2.48
|PS+TPS+00+2_147
|
|2.49
|PS+TPS+01+2_147
|
|2.50
|PS+TPS+02+2_147
|
|2.51
|PS+TPS+03+2_147
|
ok
2006-05-02 13:56:36.65

To find IUR links, the atmif used must be 807.


One vcc must be provisioned for RNSAP (that will also bear alcap) and at least two vcc
for aal2 iur fp (DS and NDS) pipes.
7> d -p atmif/807 vcc/* vcd
AtmIf/807 Vcc/* Vcd
+==========+--------------------+---------------------------------------|
Vcc
|
tag
|Response
+==========+--------------------+---------------------------------------|3.32
|IR+SCS+00+1
|
|3.48
|IR+TCS+00+1
|
|3.50
|IR+TCS+01+1
|
ok
2006-05-02 14:02:18.54

ON OMU SIDE
On the active OMU ci_mgr commands can be dumped for the processes
STACKADM_CREATOR and CPM_CREATOR.
RNC1202_toto-0:/OMU (omu) $ psg STACKADM
root 25562 10914
0
Feb 10
- 1:16 STACKADM_CREATOR --uniqueid 36 -instance 0
RNC1202_toto-0:/OMU (omu) $ ci_mgr noxterm
@all CI> 25562=
25562 CI> tty me

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 182/300

RNC & NodeB Health Check for NEV 4.2- How To


CI TTY redirected to: me
25562 CI> stkadmca lsctx
Prints all the configuration
STACKADM_CREATOR[25562] @RNC1202_toto-0 - Result of: stkadmca lsctx
CsCoreNetworkAccess # 0:
CS Domain
CS Core Network Access:
1 CS network created / enabled
- id
: 0
- type
: Cs Core Network Access
- create state : 1
- admin state
: non significant(4294967295)
- plmnid
: plmnid[0]: 84 plmnid[1]: 240 plmnid[2]: 0
- CN_RESET_DOMAIN
: CN_RESET_END(1)
- fm Status
: enabled no value
- sccpDestinationPointCode: 2
- sccpNetworkIndicator
: 3
- ssn status
: available
- iucsIfId
: 1
- iucsIfIdState : 3
- dpcInfoForAccess:
- dpcInfoForAccess[0]:
distantEntityAddr.pointCode = 2
distantEntityAddr.networkIndicator = 3
state = 1
- dpcInfoForAccess[1]:
distantEntityAddr.pointCode = 650990
distantEntityAddr.networkIndicator = 0
state = -1
CsCoreNetworkAccess # 1:
Non created CS network
CS Core Network Access:
- id
: 1
- type
: Cs Core Network Access
- create state : 0
- admin state
: non significant(4294967295)
- plmnid
: plmnid[0]: 255 plmnid[1]: 255 plmnid[2]: 255
- CN_RESET_DOMAIN
: CN_RESET_UNKNOWN(2)
- fm Status
: Undefined FM State
- sccpDestinationPointCode: -1
- sccpNetworkIndicator
: 255
- ssn status
: undefined
- iucsIfId
: 65535
- iucsIfIdState : 5
- dpcInfoForAccess:
- dpcInfoForAccess[0]:
distantEntityAddr.pointCode = -1
distantEntityAddr.networkIndicator = 255
state = -1
- dpcInfoForAccess[1]:
distantEntityAddr.pointCode = -1
distantEntityAddr.networkIndicator = 255
state = -1

PsCoreNetworkAccess # 0:
PS Core Network Access:
- id
: 0
- type
: Ps Core Network Access
- create state: 1
- admin state : non significant(4294967295)

PS Domain
1 PS network created /enabled

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 183/300

RNC & NodeB Health Check for NEV 4.2- How To


-

plmnid
: plmnid[0]: 84 plmnid[1]: 240 plmnid[2]: 0
CN_RESET_DOMAIN
: CN_RESET_END(1)
fm Status
: enabled no value
sccpDestinationPointCode : 6
sccpNetworkIndicator
:
ssn status : 0

PsCoreNetworkAccess # 1:
PS Core Network Access:
- id
: 1
- type
: Ps Core Network Access
- create state: 0
- admin state : non significant(4294967295)
- plmnid
: plmnid[0]: 255 plmnid[1]: 255 plmnid[2]: 255
- CN_RESET_DOMAIN
: CN_RESET_UNKNOWN(2)
- fm Status
: Undefined FM State
- sccpDestinationPointCode : 4294967295
- sccpNetworkIndicator
:
- ssn status : -1

NeighbouringRnc # 0:
IUR status (only one neighbour declared)
Neighbouring Rnc:
- id
: 0
- type
: Neighbouring Rnc
- create state : 1
- admin state
: unlocked(1)
- fm Status
: disabled dependency
- sccpDestinationPointCode
: 14
- sccpNetworkIndicator
: 3
- ssn status
: 1
- iurIfId
: 1
- iurIfIdState : 0
- dpcInfoForAccess:
- dpcInfoForAccess[0]:
distantEntityAddr.pointCode = 54
distantEntityAddr.networkIndicator = 202
state = 55
- dpcInfoForAccess[1]:
distantEntityAddr.pointCode = -1392653740
distantEntityAddr.networkIndicator = 0
state = -1392653749
- dpcInfoForAccess[2]:
distantEntityAddr.pointCode = 57
distantEntityAddr.networkIndicator = 202
state = 58
- dpcInfoForAccess[3]:
distantEntityAddr.pointCode = -1392653749
distantEntityAddr.networkIndicator = 0
state = -1392653746
- dpcInfoForAccess[4]:
distantEntityAddr.pointCode = 60
distantEntityAddr.networkIndicator = 202
state = 61
- dpcInfoForAccess[5]:
distantEntityAddr.pointCode = -1392653746
distantEntityAddr.networkIndicator = 0
state = -1392653756
- dpcInfoForAccess[6]:
distantEntityAddr.pointCode = 63

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 184/300

RNC & NodeB Health Check for NEV 4.2- How To


distantEntityAddr.networkIndicator = 202
state = 25007632
- dpcInfoForAccess[7]:
distantEntityAddr.pointCode = 26742256
distantEntityAddr.networkIndicator = 238
state = -286331154
- dpcInfoForAccess[8]:
distantEntityAddr.pointCode = 0
distantEntityAddr.networkIndicator = 0
state = -286331154
- dpcInfoForAccess[9]:
distantEntityAddr.pointCode = -286331154
distantEntityAddr.networkIndicator = 22
state = 373817838
NeighbouringRnc # 1:
Neighbouring Rnc:
- id
: 1
- type
: Neighbouring Rnc
- create state : 0
- admin state
: non significant(4294967295)
- fm Status
: Undefined FM State
- sccpDestinationPointCode
: 4294967295
- sccpNetworkIndicator
: 255
- ssn status
: -1
- iurIfId
: 65535
- iurIfIdState : 5
- dpcInfoForAccess:
- dpcInfoForAccess[0]:
distantEntityAddr.pointCode = -1
distantEntityAddr.networkIndicator = 255
state = -1
- dpcInfoForAccess[1]:
distantEntityAddr.pointCode = -1
distantEntityAddr.networkIndicator = 255
state = -1

Instead of dumping all the contexts, other menus are available:


stkadmca cs cs_core_access_instance
prints cs core network access
stkadmca ps cs_core_access_instance
prints ps core network access
stkadmca neighb
prints neighbouring rnc
Syntax examples:
25562
25562
25562
25562

CI>
CI>
CI>
CI>

stkadmca
stkadmca
stkadmca
stkadmca

cs 0
cs 1
ps 0
neighb

The results will be the same as detailled before for stkadmca


Also usefull:

lsctx.

25562 CI> stkadmca tmu


STACKADM_CREATOR[26588] @RNC1202_titi-1 - Result of: stkadmca tmu

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 185/300

RNC & NodeB Health Check for NEV 4.2- How To


TMU states as seen by Stack Adm Ca:
- abspos: 0x1
- shelf : 0, slot: 1
- state : Cn Module State : USABLE

Ranap reset check


Callp manager (CPM) can also dump the states of the CS/PS domains.
Search for CPM_CREATOR pid, the ci_mgr commands are :
cpm_iu data cs index
displays CS Domain info
cpm_iu data ps index
displays PS Domain info
For the reset status, CN_RESET_END means that a Ranap Reset Acknowledge was
received from the core network.
RNC1202_toto-0:/OMU (omu) $ psg -i cpm
root 23996 10914
0
Feb 10
- 0:49 CPM_CREATOR --uniqueid 31 -instance 0
RNC1202_toto-0:/OMU (omu) $ ci_mgr -noxterm
@all CI> 23996 =
23996 CI> tty me
23996 CI> cpm_iu data cs 0
CPM_CREATOR[25284] @RNC1202_titi-1 - Result of: cpm_iu data cs 0

*** Print CS Domain Context Infos ***


CS Domain Index: 0
- cnDomainInd
: CS_DOMAIN(0)
+ CS Permanent Data
:
- create_state
: ADM_AO_CREATED(1)
Object created
- NbResetRepetitions: 5
- TcnResetAck
: 120000
- plmnId
: plmnid[0]: 84 plmnid[1]: 240 plmnid[2]: 0
-

domainInstance
:
isSccpAvailable
:
proceedSccpAvailable:
resetStatus
:
transacId
:
isUpdateDdOK
:
isResetSyncNeeded
:

IU_CS(0)
true(1)
false(0)
CN_RESET_END(1)
151
false(0)
true(1)

Ranap Reset Ack received for CS.

23996 CI> cpm_iu data cs 1


CPM_CREATOR[25284] @RNC1202_titi-1 - Result of: cpm_iu data

cs 1

*** Print CS Domain Context Infos ***


CS Domain Index: 1
- cnDomainInd
: CS_DOMAIN(0)
+ CS Permanent Data
:

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 186/300

RNC & NodeB Health Check for NEV 4.2- How To


-

create_state
:
NbResetRepetitions:
TcnResetAck
:
plmnId
:

domainInstance
:
isSccpAvailable
:
proceedSccpAvailable:
resetStatus
:
transacId
:
isUpdateDdOK
:
isResetSyncNeeded
:

ADM_AO_NOT_CREATED(0)
0
0
plmnid[0]: 255 plmnid[1]: 255 plmnid[2]: 255
IU_CS(0)
false(0)
false(0)
CN_RESET_BEGIN(0)
0
false(0)
true(1)

No Ranap Reset Ack received

23996 CI> cpm_iu data ps 0


CPM_CREATOR[25284] @RNC1202_titi-1 - Result of: cpm_iu data

ps 0

*** Print PS Domain Context Infos ***


PS Domain Index: 0
- cnDomainInd
: PS_DOMAIN(1)
+ PS Permanent Data
:
- create_state
: ADM_AO_CREATED(1)
- NbResetRepetitions: 5
- TcnResetAck
: 120000
- plmnId
: plmnid[0]: 84 plmnid[1]: 240 plmnid[2]: 0
-

domainInstance
:
isSccpAvailable
:
proceedSccpAvailable:
resetStatus
:
transacId
:
isUpdateDdOK
:
isResetSyncNeeded
:

IU_PS(1)
true(1)
false(0)
CN_RESET_END(1)
152
false(0)
true(1)

The status can also be retrieved on a TMU through iu_call:


Log onto any TMU (except the Spare one)
Retrieve IUDED_ADM tid (os i)
Attach the decimal value to iu_call (iu_call tid iuded_adm_decimal_tid)
Display the reset status (iu_call reset)

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 187/300

RNC & NodeB Health Check for NEV 4.2- How To

Example:
IUDED_ADM is 128606208 (7aa6000 in hex.)
TELNET_CI> os i
@ - Result of: os i
NAME
ENTRY
TID
PRI
STATUS
PC
SP
ERRNO DELAY
---------- ------------ -------- --- ---------- -------- -------- ------- ----[]
IUDED_ADM 19c775c
7aa6000 200 PEND+T
42f860 7aa4a40
3c
234996
[]
TELNET_CI> iu_call tid 128606208
@ - Result of: iu_call tid 128606208
CI Manager has been sucessfully attached to tid: 128606208

Expected case: reset statuses are (0x0) RANAP RESET ACK message ok.
TELNET_CI> iu_call reset
@ - Result of: iu_call reset
*** Display result of: reset(14) ***

Ranap Reset Ack received

- resetStatus[0]
: (0x0)
[]
- swbResetStatus[0]: (0x0)
[]

If not, the domain still not reset is pointed out:


TELNET_CI> iu_call reset
@ - Result of: iu_call reset
*** Display result of: reset(14) ***
- resetStatus[0]

: RESET_DOMAIN_CS (0x2)

RESET_DOMAIN_PS (0x2)

Ranap Reset Ack not received for CS


and PS
[]
- swbResetStatus[0]: RESET_DOMAIN_CS (0x2)

RESET_DOMAIN_PS (0x2)

Ranap Reset Ack not received for CS


and PS
[]

COMPACT
Refer to the Classic part in version V4.
The IN part is the same (ss7 object).
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 188/300

RNC & NodeB Health Check for NEV 4.2- How To

The ci commands are the same on the omu (stkadmca, cpm_iu).


Those ci commands have to be run from the active OMU (telci).
To get the TID, run the iu_call_lstid command.
7.11. OMU and TMU VCC info
Following VCC are used for connections towards OMU and TMU:
Shelf/Slot
0/1
00/3
0/4
0/11
0/12
0/13
0/14
1/1
1/3
1/4
1/5
1/7
1/8
1/9
1/11
1/12
1/13
1/14

ATM port
number
1
2
3
4
5
6
8
9
10
11
12
0
7
13
14
15
16
17

RM Type

IP Address

CN-IN PVC

TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
TMU
OMU
CC1
CC1
OMU
TMU
TMU
TMU
TMU

172.1.2.2
172.3.2.2
172.4.2.2
172.11.2.2
172.12.2.2
172.13.2.2
172.14.2.2
172.33.2.2
172.35.2.2
172.36.2.2
172.37.2.2
172.41.2.2
172.43.2.2
172.44.2.2
172.45.2.2
172.46.2.2

0.49
0.50
0.51
0.52
0.53
0.54
0.56
0.57
0.58
0.59
0.60
0.61
0.62
0.63
0.64
0.65

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 189/300

RNC & NodeB Health Check for NEV 4.2- How To

7.12. How To debug SS7 on the RNC-Interface Node


CLASSIC/COMPACT
(1) Check that the SAAL-NNI is receiving and transmitting messages:
9> d ss7 saalnni/* pdusTx,pduOctetsTx,pdusRx,pduOctetsRx
Ss7 SaalNni/*
+=======+----------+----------+----------+---------|SaalNni| pduTx
| pduOctTx | pduRx
| pduOctRx
+=======+----------+----------+----------+---------|
1|
34045|
348933|
34047|
349184
|
17|
34476|
430276|
34471|
361943
ok
2006-04-19 11:03:32.65
10> d ss7 saalnni/* pdusTx,pduOctetsTx,pdusRx,pduOctetsRx
Ss7 SaalNni/*
+=======+----------+----------+----------+---------|SaalNni| pduTx
| pduOctTx | pduRx
| pduOctRx
+=======+----------+----------+----------+---------|
1|
34047|
348953|
34049|
349204
|
17|
34477|
430286|
34472|
361953
ok
2006-04-19 11:03:43.79

=>Should be increased

Please see the 7.10 IU/IUR links check for the checks on SS7.
For more informations, an user guide for debugging the SS7 stacks migrated onto the IN
for versions V3.2, V4.0, V4.1 and V4.2 is available in
UMTS_RNC_IN_SS7_Debug_Guide (UMT/RNC/APP/014269) under
http://eur-livelink.europe.nortel.com/livelink/livelink.exe?func=ll&objId=15531104&objAction=browse&sort=name

7.13. Observations storage


On the RNC:
CLASSIC
The counters collected by PF_CA (performance central agent) through the PF_LA (local
agents) on the different boards are stored on the active OMU under xdr files in
/OMU/share/log/PF_GPO
They are collected by the OMC if the NE link is opened at the end of the granularity
period.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 190/300

RNC & NodeB Health Check for NEV 4.2- How To

COMPACT
The counters are stored under
/sfs2/share/log/PF_GPO
Perfserver:
Mediation file
/opt/nortel/config/access/pm_current_cntlst.cfg
Mediation file allow linking the counter number used by the RNC to its name as
defined for the clients.
Storage
/opt/nortel/data/access/observation/date/equipment_name contains xml files of the
retrieved counters.
Example for the IN of the RNC 1202, May 3, 2006:
bianca:/opt/nortel/data/access/observation/20060503/RNC-RNC_1202_IN <118> (nortel) % ls
A20060503.0000+0200-0015+0200_RNC-RNC_1202_IN.gz
Counters from 0:00 to 0:15am
A20060503.0015+0200-0030+0200_RNC-RNC_1202_IN.gz
A20060503.0030+0200-0045+0200_RNC-RNC_1202_IN.gz
A20060503.0045+0200-0100+0200_RNC-RNC_1202_IN.gz
A20060503.0100+0200-0115+0200_RNC-RNC_1202_IN.gz
A20060503.0000+0200-0100+0200_RNC-RNC_1202_IN.gz
Counters from 0:00 to 1am

These are xml files that need to be converted.


Counters in real-time:
Sometimes, it could be useful to check the counter on the RNC itself while it is
incremented.
In order to do it, perform as follows:
telci on the TMU
Usage
TELNET_CI> pfla_callp lscounterValue -CTR <CounterId> [-NBR NeighbRNCId] [-NDB
NodebId] [-CEL CellId]
sbc @tmu_1_12_sbc - Result of: pfla_callp lscounterValue -CTR 631

===================================================================
===
Displays Counter Value
===
Query for Counter Id 631
Data for Cell Nodeb 0 Cell 0
CtrId Screening Cumulative
----- --------- ---------0631
0
0
0631
1
0
0631
2
0
0631
3
0
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 191/300

RNC & NodeB Health Check for NEV 4.2- How To


0631
0631
0631
0631
0631
0631
0631
0631
0631
0631
0631

4
5
6
7
8
9
10
11
12
13
14

0
0
0
0
0
0
0
0
0
0
0

Please find below a table of the most useful counters

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 192/300

RNC & NodeB Health Check for NEV 4.2- How To


Counter
ID

Counter Name

#409

RRC.AttConnEstab.<screening>

#403

RRC.SuccConnEstab.<screening>

#621

VS.RabEstablishmentRequestsPerRabType.<rab>

#622

VS.RabEstablishmentSuccessPerRequestedRabType.<rab>

#701

VS.SmcSuccess.WithCoreNetwork<Cs/Ps>

#702

VS.RejectedSmc.WithCoreNetwork<Cs/Ps>

#703

VS.FailedRrcSmc.WithCoreNetwork<Cs/Ps>

#957

VS.HsdpaCACSuccess

#958

VS.HsdpaCACUnccessful

Description

#542

VS.IuAbnormRelReqCs.<screening>

#546

VS.IuAbnormRelReqCs.DlAccessStratumConf=<ID>

#543

VS.IuAbnormRelReqPs.<screening>

Location

Triggering event

FDDCell

Reception RRC/RRC_CONNECTION_REQUEST

FDDCell

Reception RRC_CONNECTION_SETUP_COMPLETE ok

RNC

RANAP/RAB assignment request message

RNC

RANAP/RAB assignment response message

RNC

SMC Response of success

RNC

SMC Reject before sending SMC RRC command to UE

RNC

SMC Response of failure (due to failure of RRC command)

Number of HSDPA CAC

FDDCell
(reference)

Successful access to the cell for an HSDPA call during mobility or


establishment procedure

Number of HSDPA CAC

FDDCell
(reference)

Unsuccessful access to the cell for an HSDPA call during mobility


or establishment procedure

FDDCell
(reference)

Sending of a RANAP/IU Release Request message in order to


release the IU connection of a
CS call (call in CS TRB) abnormally terminated

FDDCell
(reference)

Whenever RNC requests Iu CS release due to abnormal conditions

FDDCell
(reference)

Sending of a RANAP/IU Release Request message in order to


release the IU connection of a PS call (call in PS TRB) abnormally
terminated

This is incremented for any


rrc connection request
received
Number of rrc connection
successfull
Number of RAB
establishment attempts
Number of successful
RAB establishment per
requested RAB type
Number of successful
Security Mode Commands
at Iu interface
Number of Security Mode
Commands at Iu interface
rejected as unsupported /
allowed
Number of Security Mode
Commands that fail
because the corresponding
RRC command fails

Number of Iu release
request sent for CS calls
abnormally terminated,
when the reference fddcell
of
these calls is located on the
serving RNC
Number of Iu CS release
requests due to abnormal
conditions
Number of Iu release
request sent for PS calls
abnormally terminated,
when the reference fddcell
of these calls is located on
the serving RNC

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 193/300

RNC & NodeB Health Check for NEV 4.2- How To

Counter
ID

Counter Name

Description

Location

Triggering event

#547

VS.IuAbnormRelReqPs.DlAccessStratumConf=<ID>

Number of Iu PS release
requests due to abnormal
conditions

FDDCell
(reference)

Whenever RNC requests Iu PS release due to abnormal conditions


(i.e. excludes Always On and if last remaining RAB was released
by Core Network)

#631

#625

VS.RadioBearerEstablishmentUnsuccess.<screening>

VS.RadioBearerSetupRequest.< DlAsConfId>

Number of radio bearer


setup not successfully
established, with no
RADIO_BEARER_SETU
P_REQUEST sent.(based
on procedure count, not
RBs). Incremented based
on reference
Cell (a)
Number of Radio Bearer
setup decisions (leading or
not to a RB Setup, ie.
incremented even if CAC
rejects the setup)

FDDCell
(reference)

FDDCell
(reference)

Any event that prevents to setup the RB successfully before to


sent the
RADIO_BEARER_SETUP_REQUEST (b).

Reception of RAB Assignment Request (addition Only)

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 194/300

RNC & NodeB Health Check for NEV 4.2- How To

7.14. HSDPA How To

7.14.1. Principle
3GPP has standardized HSDPA in Release 5 in order to increase maximum user
throughput for downlink packet data (streaming, interactive and background traffic
classes) and decrease downlink packet transmission delay. This Release 5 is fully
compatible with the previous Release 99 (R99).
In R99, data are transmitted on a dedicated channel with a given user throughput and a
downlink transmitted power controlled according to the radio conditions.
In HSDPA, data are transmitted on a shared channel by using all the available power and
by controlling the downlink user throughput according to the radio conditions. Typically,
a user in good radio conditions will receive his data with a high bit rate whereas a user in
bad radio conditions will receive his data with a lower bit rate.

7.14.2. How to .. Check configuration


The following chapter will present the main parameters to be checked regarding the
activation of the HSDPA Feature. For more details information on the HSDPA
configuration, please refer to the documentation UMT/IRC/APP/014654 HSDPA
Engineering Guide.
To check the configuration on the OMC server, use wicl.
In our case, the RNC is RNC_1202 (classic)
7.14.2.1 Basic configuration
RadioAccessService configuration Impact:
A new instance of DlRbSetConf (DlRbSetConf/HSDSCH) has been created under
RadioAccessService to take into account HSDPA services (instance 17 in the traces)
Check that this new Radio Bearer is eligible for the RAB Matching Algorithm:
bernard:/opt/nortel/shell/wicl <104> (nortel) % ./wiclsh
--------------------------------------------------------Starting Wireless Internet Command Language
--------------------------------------------------------Command mode launched
login : nortel
password :
password = same as GUI
....wait please
Wireless Internet Command Language (WICL)
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 195/300

RNC & NodeB Health Check for NEV 4.2- How To

>: RNC RNC_1202 RadioAccessService 0 DlRbSetConf HSDSCH dis


allowedDlRbSetForMatching
NONE
class
DlRbSetConf
dlBlerQuality
-1.7
dlOutOfOrderSduDeliveryMethod
InSequence
dlRbRateAdaptationDownsizeThreshold
NONE
dlRbRateAdaptationUpsizeThreshold
NONE
dlRlcQueueSize
64
dlSrbErrorMatching
0.7
dlSyncRetryPeriod
100
dn
(RNC,260)(RadioAccessService,0)(DlRbSetConf,17)
New instance of DlRbSetConf
enabledForRABMatching
true
Eligible for RAB Matching
endPoint
5
[]

A new instance of RlcConfClass (RlcConfClass/ TRBHSDPAAM) has been created


under RadioAccessService to take into account HSDPA service (instance 16 in the traces)
>: RNC RNC_1202 RadioAccessService 0 RlcConfClass TRBHSDPAAM DlRlcAckMode 0 dis
class
DlRlcAckMode
dn
(RNC,260)(RadioAccessService,0)(RlcConfClass,16)(DlRlcAckMode,0)
epcTimer
NONE
lastRetransPuPoll
true
lastTransPuPoll
true
maxDat
10
maxNbrOfResetRetrans
6
misPuIndic
true
nbrOfPuBetweenPolling
128
nbrOfSduBetweenPolling
NONE
operatorId
0
pollingTimer
450
pollwindow
pollWindow80
prohibitedPollingTimer
70
prohibitedStatusTimer
300
receptionWindowSize
2047 To be checked
resetTimer
500
timerPollPeriod
NONE
timerStatPeriod
NONE
transmissionWindowSize
2047
userSpecificInfo
NONE

A new object HsdpaRncConf has been created under RadioAccessService


Check the following:
>: RNC RNC_1202 RadioAccessService 0 HsdpaRncConf 0
SourceConformanceInformation 0 dis
class
SourceConformanceInformation
dn
(RNC,260)(RadioAccessService,0)(HsdpaRncConf,0)(SourceConformanceInformation,0)
maximumBucketSize
250000
It will handle the throughput
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 196/300

RNC & NodeB Health Check for NEV 4.2- How To


difference between Iu and IuB interfaces
maximumTokenGenerationRate
operatorId
sourceConformanceStatus
userSpecificInfo

2000000
0
Off
NONE

A new object HsdpaCellClass has been created under RadioAccessService


Check the following:
>: RNC RNC_1202 RadioAccessService 0 HsdpaCellClass 0 dis
class
HsdpaCellClass
dn
(RNC,260)(RadioAccessService,0)(HsdpaCellClass,0)
maximumNumberOfUsers
20
minimumPowerForHsdpa
3.0
numberOfHsPdschCodes
10
Number of OVSF codes for HS-DSCH

Data channels
Number of OVSF codes for HS-SCCH
Signalling channel

numberOfHsScchCodes

operatorId
userSpecificInfo

0
NONE

A new object HsdpaUserService has been created under RadioAccessService


Check the following:
>: RNC RNC_1206 RadioAccessService 0 HsdpaUserService 0 dis
ackNackRepetitionFactor
1
ackPowerOffset
6
class
HsdpaUserService
cqiFeedbackCycleK
2
cqiPowerOffset
6
cqiRepetitionFactor
1
discardTimer
500
dn
(RNC,259)(RadioAccessService,0)(HsdpaUserService,0)
hsScchPowerOffset
NONE
macHsWindowSize
32
measurementPowerOffset
15
Offset to the P-CPICH used by the UE

for CQI estimation (0.5dB)


nackPowerOffset
operatorId
timerT1
userSpecificInfo

7
0
100
NONE

Feature Activation
>: RNC RNC_1202 RadioAccessService 0 dis
[]
isDlRbRateAdaptationAllowed
false
isGsmMeasActivationAllowed
true
isHsdpaAllowed
true Feature activation at RNC Level
isInterFreqHHOAllowed
false

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 197/300

RNC & NodeB Health Check for NEV 4.2- How To


isInterFreqIntraRncHHOWithCModeAllowed false
isInterFreqMeasActivationAllowed
false
isIntraFreqInterRncHHOAllowed
false
[]
isUeCapabilitiesInRabMatchingAllowed
false
isUeCapabilitiesInRabMatchingAllowedForPhyAndRlctrue
isUlRbRateAdaptationAllowed
true Uplink Rate Adaptation activated
levelLimit
2
locUpdatePeriod
0

Note
The Feature Uplink Rate adaptation has also to be activated since some troubles may
appear on the HSDPA Throughput if the uplink rate is not correctly adapted for the
acknowledgement process.

FDDCell configuration Impact:


>:

RNC RNC_1202 list NodeB

{RNC RNC_1202 NodeB BTS_194014} {RNC RNC_1202 NodeB BTS_RED205}


>: RNC RNC_1202 NodeB BTS_194014 list FDDCell
{RNC RNC_1202 NodeB BTS_194014 FDDCell BTS_194014_0} {RNC RNC_1202 NodeB
BTS_194014 FDDCell BTS_194014_1} {RNC RNC_1202 NodeB BTS_194014 FDDCell
BTS_194014_2}
>: RNC RNC_1202 NodeB BTS_194014 FDDCell BTS_194014_0 dis
[]
HoConfClass/1
hsdpaActivation
true Feature activation at FDDCell Level
intraFreqCellReselectInd
allowed
is3Gto2GRedirectForEmergencyAllowed
false

Note
hsdpaActivation set to true means that the BTS will have to handle the Physical Shared
Channel Reconf Procedure (procedure on the IuB interface to implement the new
Transport Channels which are dedicated to HSDPA)
BTS Configuration Impact:
>: BTSEquipment BTS_194014 dis
[]
dn
frequencyBand
globalHardwareRef
hsdpaMaxNumberUser
hsdpaMaxNumberUserPerNodeB
hsdpaResourceMaxCapacity
inVccGroup

(BTSEquipment,67)
umtsBand
0
0
0
100
2
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 198/300

RNC & NodeB Health Check for NEV 4.2- How To


[]
>: BTSEquipment BTS_194014 list BTSCell
{BTSEquipment BTS_194014 BTSCell 0} {BTSEquipment BTS_194014 BTSCell 1}
{BTSEquipment BTS_194014 BTSCell 2}
>: BTSEquipment BTS_194014 BTSCell 0 dis
[]
cellSize
from0to5
class
BTSCell
dn
(BTSEquipment,67)(BTSCell,0)
hsdpaResourceActivation
true Feature activation at BTSCell Level
localCellGroupId
0
localCellId
12024
maximumPowerAmplification
30
operatorId
0
paRatio
100
pmmActivation
false
pmmPowerControlWindow
2
pmmThresholdHigh
1.0
pmmThresholdLow
-0.5
userSpecificInfo
Default_BTSCell

Note
The first three parameters are manufacturer, that is to say they are hidden from the OMC
GUI and the command setOnLine on those parameters will not be possible.
hsdpaMaxNumberUser: defines the maximum number of HSDPA users allowed
by software per H-BBU. The recommended value 0 means that the maximum
users are supported per H-BBU
hsdpaMaxNumberUserPerNodeB: defines the maximum number of HSDPA
users allowed per NodeB. The recommended value 0 means that the maximum
user allowed by software and Hardware are supported per NodeB
hsdpaResourceMaxCapacity: defines the maximum resources in term of software
Capacity. Recommended value = 100
>: BTSEquipment BTS_194014 BTSCell 0 list children
HsdpaConf
>: BTSEquipment BTS_194014 BTSCell 0 HsdpaConf 0 dis
class
HsdpaConf
dchPowerMargin
20
dn
(BTSEquipment,67)(BTSCell,0)(HsdpaConf,0)
harqNbMaxRetransmissions
15
harqType
mirType
hsdpaResourceId
0
if value is 0 on all BTSCells, its a

mono-H-BBU configuration
hsdschInterval
100
hsscchPcOffset
{ 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
0.0 }
maxRateGrowth
8
operatorId
0
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 199/300

RNC & NodeB Health Check for NEV 4.2- How To


userSpecificInfo

NONE

Note
Mono H-BBU configuration: all cells are handled by only one H-BBU Entity
In case there is no limitation on the H-BBU Hardware (iCEM Boards), the
hsdpaResourceId parameter could take different values on each BTSCell (value 0, 1 and
2 respectively for BTSCell0, 1 and 2)

7.14.3. How to .. Check and Troubleshoot HSDPA services on the RNC


Call Flow

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 200/300

RNC & NodeB Health Check for NEV 4.2- How To


UE

Node B

RNC

SGSN

The UE is authenticated by the SGSN


GMM/ Authentication and Ciphering Request
GMM/ Authentication and Ciphering Response
The ciphering and integrity procedures are activated by the MSC
The RNS supports the following algorithms:

UIA1 for integrity

UEA1 for ciphering


RANAP/ Security Mode Command (UIAx, UEAy)

RRC/ FACH / Security Mode Command

"Common Id" is used to provide the RNC with the user IMSI
RANAP/ Common Id (IMSI)
RRC/ RACH / Security Mode Complete

RANAP/ Security Mode Complete


The Radio Access Bearer assignment procedure
RANAP/ RAB Assignment Request (RAB param, binding Id)

NBAP/ Radio Link Setup Request (DCH Radio Link,


HS-DSCH Radio Link)

New Radio links are created to support the


DCCH and DTCH configuration. A HS-DSCH
Radio Link is created as well as the associated
DCH

NBAP/ Radio Link Setup response (HS-SCCH codes allocated)


AAL2/ ERQ
The FP for the DCH transport channel is setup

AAL2/ ECF
FP/ DL Synchronisation (CFN)

The DCH is synchronised


FP/ UL Synchronisation (ToA)
AAL2/ ERQ

The FP for the HS-DSCH transport channel is


setup

AAL2/ ECF
The UE is provided with the new radio link configuration.
A new RAB (corresponding to the new DTCH) is added to
the current configuration
RRC/ FACH / RB Setup (DCCH + DTCH,
RRC state = CELL_DCH,
HS-SCCH information)
RRC/ DCH / RB Setup Complete

The measurement for CELL_DCH state are


configured once the mobile is in CELL_DCH

RRC/ Measurement Control

RANAP/ RAB Assignment Response


The RAB is now established. the mobile is now waiting for end-to-end
service accept.
SM/ Activate PDP Context Accept
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 201/300

RNC & NodeB Health Check for NEV 4.2- How To

CLASSIC/COMPACT
Pre-requisites
One the IuB Interface, an HSDPA dedicated VCC needs to be configured per BTS with qosId=2
and serviceCategory UBR.
If more than one E1 are configured per BTS, IMA is mandatory.

OMU/TMU Side
The example below has been captured on a Classic RNC but the commands are also
relevant for the Compact RNCs.
Telci on the TMU
To retrieve information on the cell itself:
TELNET_CI> rrmcell info 6544
Cell ID
sbc @tmu_1_13_sbc - Result of: rrmcell info 6544
*** Display miscellaneous info for Cell 6544 ***
scrambling code = 208
uarfcnForNu = 9887
uarfcnForNd = 10837
isTxDiversityIndicator = 1
txDiversityIndicator = 0
3G to 2G Redirection for Emergency Calls Allowed
WaitTime for 3G to 2G Redirection Failure = 1
iCellRef (iNodebCoreProcessRef = 2, iCellRefPerNodebCP = 4)
HSDPA Configuration is present
==============================
HS-PDSCH codes (SF 16, level 2): first code number 6, number of codes 10
HS-SCCH codes (SF 128, level 5): list of codes 46 47 , number of codes 2
HSDPA codes are allocated.
hsdpaMaxPower = 11.75 Watt (40.70 dBm)
Max number of HSDPA users in a cell is 32
Current number of HSDPA users is 2
The global HSDPA flag isHsdpaConfigured is TRUE.
Allocated H-RNTI : 0x7310
Allocated H-RNTI : 0x8711
isUlCapacityThreshold = 1
ulCapacityThreshold = 143
currentULLoad = 0

To retrieve information on the active HSDPA calls :


Telci on the TMU
TELNET_CI> ue_call lscallctxid
sbc @tmu_1_13_sbc - Result of: ue_call lscallctxid
===================================================================
=== Lists ue_call ctxId, traceKey, IMSI and H-RNTI of all established
calls ===
===================================================================
Dump of each ueCallCtxtId (tracekey, start date):
------------------------------------------------> 12574 (0x8000b11e, 2006/05/19 11:06:26.231):
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 202/300

RNC & NodeB Health Check for NEV 4.2- How To


IMSI: 0x5 4 0 0 0 0 0 0 0 0 0 0 0 3 9
H-RNTI: 0x62fb
HS-PDSCH RL id: 0
-> 287 (0x8000811f, 2006/05/19 11:12:41.276):
IMSI: 0x5 4 0 0 0 0 0 0 0 0 0 0 0 3 3
H-RNTI: 0x7310
HS-PDSCH RL id: 0
-> 12638 (0x8000b15e, 2006/05/19 11:14:40.583):
IMSI: 0x5 4 0 0 0 0 0 0 0 0 0 0 0 1 9
Neither HS-PDSCH RL nor H-RNTI allocated
-> 175 (0x840080af, 2006/05/19 11:15:36.167):
IMSI: 0x5 4 0 0 0 0 0 0 0 0 0 0 0 8 3
H-RNTI: 0x8711
HS-PDSCH RL id: 0
-> 991 (0x800083df, 2006/05/19 11:15:56.807):
IMSI: 0x5 4 0 0 0 0 0 0 0 0 0 0 0 1 7
H-RNTI: 0xa017
HS-PDSCH RL id: 0
-> 1039 (0x8000840f, 2006/05/19 11:16:02.787):
IMSI: 0x5 4 0 0 0 0 0 0 0 0 0 0 0 4 6
Neither HS-PDSCH RL nor H-RNTI allocated
number of call contexts: 6
TELNET_CI> rnccall uectxid 0x2703
sbc @tmu_1_13_sbc - Result of: rnccall uectxid 0x2703
===================================================================
===
Dumps the UeCtxId
===
===================================================================
[]
HSDPA info:
isHsdpaRlId: TRUE
isHsdpaInfo: TRUE
estabHsPdschRlId: 0
estabHsDschInfo:
macDFlowInfo:
nbHsDschMacDFlowSpecInfo: 1
hsDschMacDFlowSpecInfo[0]
hsdschMacDFlowId: 0
allocRetentPriority:
priorityLevel: 3
preemptionCap: 0
preemptionVul: 0
aal2Information:
transpQosId: 2
cacAal2Info:
qaal2DlEquivalentBitRate: 0
qaal2DlMaximumBitRate: 6375
qaal2DlMaximumSSARSDULength: 510
qaal2DlEquivalentSSARSDULength: 1
qaal2UlEquivalentBitRate: 0
qaal2UlMaximumBitRate: 0
qaal2UlMaximumSSARSDULength: 1
qaal2UlEquivalentSSARSDULength: 1
nbPrioQueueInfo: 1
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 203/300

RNC & NodeB Health Check for NEV 4.2- How To


prioQueueInfo[0]
priorityQueueId: 0
assocHsdschMacDFlow: 0
schedulingPriorityIndicator: 0
T1: 100
isDiscardTimer: TRUE
discardTimer: 500
macHsWindowSize: 32
nbMacDPduSizeIndex: 1
macDPduSizeIndex[0]
sid: 0
macDPduSize: 336
rlcMode: 0
ueCapaInfo:
hsDschPhyLayerCat: 12
macHsReorderBufSizeForRlcUm: 0
cqiFeedbackCycleK: 2
isCqiRepetitionFactor: TRUE
cqiRepetitionFactor: 1
ackNackRepetitionFactor: 1
cqiPowerOffset: 6
ackPowerOffset: 6
nackPowerOffset: 7
isHsScchPowerOffset: FALSE
isMeasurementPowerOffset: TRUE
measurementPowerOffset: 15
===================================================================
TELNET_CI> rrmded hsdpaconf
sbc @tmu_1_13_sbc - Result of: rrmded hsdpaconf
HSDPA Configuration
===================
isHsdpaAllowed
= TRUE
deltaCfnForHsdpaRLCReconfiguration
=0
isRLCReconfigurationForChannelTypeSwitching =TRUE
HSDPA User Service Configuration:
--------------------------------create_state
timerT1
isDiscardTimer
discardTimer
macHsWindowSize
cqiFeedbackCycleK
isCqiRepetitionFactor
cqiRepetitionFactor
cqiPowerOffset
ackNackRepetitionFactor
ackPowerOffset
nackPowerOffset
isHsScchPowerOffset
hsScchPowerOffset
measurementPowerOffset
HSDPA RNC Configuration:
---------------------------------create_state
hsDschFlowInformation:
.minTimeBetweenRequest
.maxNumberOfRetryRequest

=
=
=
=
=
=
=
=
=
=
=
=
=
=
=

1
64
TRUE
1f4
20
2
TRUE
1
6
1
6
7
FALSE
ffff
f

= 1
= 1f4
= 14

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 204/300

RNC & NodeB Health Check for NEV 4.2- How To


isSourceConformanceActivated
sourceConformanceInformation:
.ifNonCompDrop
.tokenGenerationRate
.bucketSize
numberOfSPIConfiguration
spiConfiguration[0].priorityLevel
spiConfiguration[0].streamingSpi
spiConfiguration[0].interactiveSpi
spiConfiguration[0].backgroundSpi
spiConfiguration[1].priorityLevel
spiConfiguration[1].streamingSpi
spiConfiguration[1].interactiveSpi
spiConfiguration[1].backgroundSpi
spiConfiguration[2].priorityLevel
spiConfiguration[2].streamingSpi
spiConfiguration[2].interactiveSpi
spiConfiguration[2].backgroundSpi
suspendTimeOffset
maxIubHsDschFrameSize
deltaCfnForHsdpaMobility
deltaCfnForHsdpaChannelTypeSwitching

= FALSE
= FALSE
= 7a120
= 3d090
= 3
= 1
= 0
= 0
= 0
= 2
= 0
= 0
= 0
= 3
= 0
= 0
= 0
= 1e
= 5c8
= 2d
= 50

=== End of HSDPA configuration ===


===================================================================

INode Side
Check the VCCs configuration:
2> d -p atmif/800 vcc/* vcd
AtmIf/800 Vcc/* Vcd
+==========+------+------+------+------+-------------------|
Vcc
|segLkL|segSwL|eeLbk |connTy|
tag
|
| bk | bk |
| pe |
+==========+------+------+------+------+-------------------|0.33
|sameAs|sameAs|sameAs|ptp
|NB+OAM+00+BTS_193895
|0.34
|sameAs|sameAs|sameAs|ptp
|NB+DSS+00+BTS_193895
|0.35
|sameAs|sameAs|sameAs|ptp
|NB+DSS+02+BTS_193895
|0.36
|sameAs|sameAs|sameAs|ptp
|NB+DSS+04+BTS_193895
|0.42
|sameAs|sameAs|sameAs|ptp
|NB+NDS+01+BTS_193895
|0.43
|sameAs|sameAs|sameAs|ptp
|NB+NDS+03+BTS_193895
|0.44
|sameAs|sameAs|sameAs|ptp
|NB+HSD+05+BTS_193895VCC for HSDPA traffic
|0.50
|sameAs|sameAs|sameAs|ptp
|NB+nCP+00+BTS_193895
|0.51
|sameAs|sameAs|sameAs|ptp
|NB+CCP+00+BTS_193895
|0.52
|sameAs|sameAs|sameAs|ptp
|NB+CCP+01+BTS_193895
|0.57
|sameAs|sameAs|sameAs|ptp
|NB+OAM+00+BTS_127544
|0.58
|sameAs|sameAs|sameAs|ptp
|NB+DSS+00+BTS_127544
|0.59
|sameAs|sameAs|sameAs|ptp
|NB+DSS+03+BTS_127544
|0.66
|sameAs|sameAs|sameAs|ptp
|NB+NDS+01+BTS_127544
|0.67
|sameAs|sameAs|sameAs|ptp
|NB+NDS+04+BTS_127544
|0.72
|sameAs|sameAs|sameAs|ptp
|NB+HSD+05+BTS_127544VCC for HSDPA traffic
|0.73
|sameAs|sameAs|sameAs|ptp
|NB+HSD+02+BTS_127544VCC for HSDPA traffic
|0.74
|sameAs|sameAs|sameAs|ptp
|NB+nCP+00+BTS_127544
|0.75
|sameAs|sameAs|sameAs|ptp
|NB+CCP+00+BTS_127544
|0.76
|sameAs|sameAs|sameAs|ptp
|NB+CCP+01+BTS_127544
ok
2006-05-18 14:16:19.08

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 205/300

RNC & NodeB Health Check for NEV 4.2- How To

5> d -p atmif/800 vcc/0.72 vcd tm


AtmIf/800 Vcc/0.72 Vcd Tm
txTrafficDescType = 6
txTrafficDescParm = 1 : 17960
2 : 2800
3 :
28
4 :
0
5 :
0
txQueueLimit
= sameAsCa
holdingPriority
= 2
rxTrafficDescType = 6
rxTrafficDescParm = 1 : 17960
2 : 2800
3 :
28
4 :
0
5 :
0
atmServiceCategory = unspecifiedBitRate
trafficShaping
= sameAsCa
unshapedTransmitQueueing = sameAsCa
weight
= sameAsCa
[]
txWredThreshold
= 25 %
rxPacketWiseDiscard
= disabled
abrConnectionType
= sameAsCa
ok
2006-05-18 14:19:28.00

UBR

6> d -p aal2/*
Aal2If/*
Use -noTabular to see hidden attributes: aal2RouteList and umtsInterface
List.
+======+----+--------------------+---+------+----+-----+-----+-----+----|Aal2If|cid |
commentText
|ecr| cacm |lbm |q0bwr|q1bwr|q2bwr|q3bwr
|
|
|
|Ob |
|
|
%|
%|
%|
%
|
|
|
| %|
|
|
|
|
|
+======+----+--------------------+---+------+----+-----+-----+-----+----|
1|
0|NodeB/BTS_193895
|100|aal2if|pc |
0|
0|
0|
0
|
2|
0|NodeB/BTS_127544
|100|aal2if|link|
0|
0|
0|
0
|
10|
0|NodeB/BTS_6_GPS1
|100|aal2if|pc |
0|
0|
0|
0
|
11|
0|NodeB/BTS_6_GPS2
|100|aal2if|pc |
0|
0|
0|
0
|
12|
0|NodeB/BTS_6_GPS3
|100|aal2if|pc |
0|
0|
0|
0
|
13|
0|NodeB/BTS_6_GPS4
|100|aal2if|pc |
0|
0|
0|
0

7> d -p aal2/2 pa/*


Aal2If/2 Path/*
+=====+--------------------+---+-----+---------------------------------------|Path |
atmConnection
|qos|pathO|Response
|
|
|
|wner |
+=====+--------------------+---+-----+---------------------------------------|
20|AtmIf/800 Vcc/0.72 | 2|yes |
|
| Nep
|
|
|
|
21|AtmIf/800 Vcc/0.67 | 1|yes |
|
| Nep
|
|
|
|
22|AtmIf/800 Vcc/0.59 | 0|yes |
|
| Nep
|
|
|
|
23|AtmIf/800 Vcc/0.73 | 2|yes |

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 206/300

RNC & NodeB Health Check for NEV 4.2- How To


|
|
|
|
|
ok

| Nep
|
|
|
24|AtmIf/800 Vcc/0.66 | 1|yes |
| Nep
|
|
|
32|AtmIf/800 Vcc/0.58 | 0|yes |
| Nep
|
|
|
2006-05-18 14:30:43.73

In case the HSDPA Thoughput is not correct, it could be a problem of VCCs


configuration, so it is better to check those VCCs from an End to End point of view (on
all the Passports within the IuB Interface: INode and ANode)
In particular, on the ANode the following component:

2> d -p atmif/* vcc/* vcd


AtmIf/* Vcc/* Vcd
+=====+==========+------+------+------+------+-------------------|AtmIf|
Vcc
|segLkL|segSwL|eeLbk |connTy|
tag
|
|
| bk | bk |
| pe |
+=====+==========+------+------+------+------+-------------------|
10|0.33
|sameAs|sameAs|sameAs|ptp
|NB+OAM+00+BTS_193983
|
10|0.34
|sameAs|sameAs|sameAs|ptp
|NB+DSS+00+BTS_193983
[]
| 903|0.32
|sameAs|sameAs|sameAs|ptp
|NB+OAM+00+BTS_127544
| 903|1.34
|sameAs|sameAs|sameAs|ptp
|NB+nCP+00+BTS_127544
| 903|1.35
|sameAs|sameAs|sameAs|ptp
|NB+CCP+00+BTS_127544
| 903|1.36
|sameAs|sameAs|sameAs|ptp
|NB+CCP+00+BTS_127544
| 903|1.41
|sameAs|sameAs|sameAs|ptp
|""
| 903|1.49
|sameAs|sameAs|sameAs|ptp
|""
| 903|1.57
|sameAs|sameAs|sameAs|ptp
|NB+HSDPA+00+BTS_127544
| 903|1.65
|sameAs|sameAs|sameAs|ptp
|NB+DSS+00+BTS_127544
| 903|1.73
|sameAs|sameAs|sameAs|ptp
|NB+NDS+00+BTS_127544
| 903|1.81
|sameAs|sameAs|sameAs|ptp
|NB+HSDPA+00+BTS_127544
[]

3> d atmif/903 vcc/1.57


AtmIf/903 Vcc/1.57
adminState = unlocked
operationalState = enabled
usageState
= busy
connectionPointType = segmentEndPoint
distributionType
= pointToPoint
numLeaves
= 0
callDirection
= notApplicable
operStatus
= unknown
localFailureCause
= noFailure
troubled
= no
segLinkSideLoopbackState = unknown
segSwitchSideLoopbackState = unknown
endToEndLoopbackState
= notApplicable
rxOamCellCongestionState
= good
aisState
= notApplicable
rdiState
= notApplicable
txCell
= 557334
txCellClp
= 0
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 207/300

RNC & NodeB Health Check for NEV 4.2- How To


txCellDiscard

= 1740

txCellDiscardClp
txFrameDiscard
txFrameDiscardClp
rxCell
rxCellClp

=
=
=
=
=

Not good, it should be equal to 0, it means either


the number of PCMs is not enough or the VCC
configuration is not correct (txQueueLimit)

0
0
0
12817
0

4> d -p atmif/903 vcc/1.57 vcd tm


AtmIf/903 Vcc/1.57 Vcd Tm
txTrafficDescType = 6
txTrafficDescParm = 1 : 17960
2 : 2800
3 :
28
4 :
0
5 :
0
txQueueLimit
= sameAsCa

Need to be modified in case the number of PCMs


on the BTS is not high enough

holdingPriority
= 2
rxTrafficDescType = 6
rxTrafficDescParm = 1 : 17960
2 : 2800
3 :
28
4 :
0
5 :
0
atmServiceCategory = unspecifiedBitRate
trafficShaping
= sameAsCa
unshapedTransmitQueueing = sameAsCa
weight
= 1
forceTagging
= sameAsCa
usageParameterControl
= sameAsCa
fwdQosClass
= 0
fwdQosParameters
= cdv : 16777215
ctd : 16777215
clr :
255
bwdQosClass
= sameAsFwd
bwdQosParameters
= cdv : 16777215
clr :
255
bearerClassBbc
= derivedFromServiceCategory
transferCapabilityBbc
= derivedFromServiceCategory
clippingBbc
= no
bestEffort
= derivedFromServiceCategory
txPacketWiseDiscard
= disabled
txWredMode
= disabled
txWredThreshold
= 25 %
rxPacketWiseDiscard
= disabled
abrConnectionType
= sameAsCa
ok
2006-05-18 16:35:28.92

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 208/300

RNC & NodeB Health Check for NEV 4.2- How To

7.14.4. How to .. Check and Troubleshoot HSDPA services on the BTS


BTS Minimal Configuration For HSDPA
In order to activate HSDPA on a BTS configuration, CEM MINIMAL requirements are:

One CEM alpha, or one iCEM (-1 / -2) 64, or one half of iCEM (-1 / -2) 128 for
NON HSDPA resources

AND
One iCEM (-1 / -2) 64 or half or iCEM (-1 / -2) 128 for HSDPA
Restrictions
HSDPA is only supported on STSR-1 and STSR-2 (HSDPA can be deployed on one
frequency only).
H-BBU is only supported on iCEM (but mixity with alpha modules is supported).
One, two or three H-BBU can be deployed by Node B.
A given HSDPA Cell is managed by one single H-BBU and cannot be split between
several H-BBU
BBU Allocations
Note: H-BBU corresponds to the same hardware than a normal BBU but running a
different software.
CEM Type
CEM Alpha
iCEM64

iCEM128

BBU 1
D-BBU
D-BBU
H-BBU
D-BBU
D-BBU
H-BBU
H-BBU

BBU 2
D-BBU

Comments
Only D-BBU for CEM
Each BBU (iBBU) of iCEM
can be allocated
independently with D-BBU
or H-BBU.
Up to 1 HBBU for iCEM64
Up to 2 HBBU for iCEM128

D-BBU
H-BBU
D-BBU
H-BBU

D-BBU: BBU managing dedicated services


H-BBU: BBU managing HSDPA
The number of H-BBUs to allocate in the BTS is determined by the number of cells
which have different hsdpaResourceId values but ignoring the ones for which
hsdpaResourceActivation is false. It is not possible to have more than 3 H-BBUs.
All BBUs on CEM alpha are considered as D-BBUs. On iCEM, H-BBUs are allocated in
priority compared to D-BBUs, knowing that if there are only iCEM in the BTS, the first
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 209/300

RNC & NodeB Health Check for NEV 4.2- How To

BBU is a D-BBU (for common channels). The remaining BBUs are D-BBUs. This
allocation is done when BTS starts up or when a new CEM board is plugged in. HBBUs
are not reallocated when a CEM hosting an H-BBU fails.
The mapping of cells on H-BBUs is determined by the value of hsdpaResourceId: it
gives directly number of the H-BBU on which the cell has to be mapped. In case of
failure of this H-BBU, it is not possible to remap the impacted cells on other H-BBUs.
If it is not possible to map on an H-BBU a cell for which HSDPA has been configured
(hsdpaResourceActivation is true), an alarm is generated by the BTS on this BtsCell (eg :
only CEM alpha in the BTS).
Resource Allocation
The H-BBU processing resources are dynamically shared over carrier/sectors (cells) as a
function of the cell traffic load. In tri-sector configuration, all 3 HSDPA cells can be
mapped on same H-BBU (selected by OMC-B configuration: hsdpaResourceId). A new
dynamic stage handles the sharing of CPU processing resources between the cells every
TTI. Three schedulers (one per cell) run in parallel and remain independent: they dont
share power nor OVSF codes or UE data. They take the new processing capabilities as an
input.
The principle of the sharing stage is:

A cell is considered active when at least one UE is configured in HSDPA in this cell
and is active, AND if the available power for HSDPA is higher than the minimum
power manageable on the H-BBU.
A UE is considered as active if some data is present in RNC buffers, in Node B
buffers or in HARQ buffers (unacknowledged data).
The minimum manageable power corresponds to the minimum power needed to
schedule one UE (HS-SCCH + HS-PDSCH), that is to say Pmin = PHS-SCCH min +
PHS-PDSCH min
Where
PHS-SCCH min = PCPICH + min(HS-SCCH Power Offset)
PHS-PDSCH min = Pmax 39dB

The Resource Management function then counts the number of active cells and
equally shares the CPU processing resources among these. No resource is allocated
to a non-active cell.

This allocation is updated as soon as the active cell status changes (a UE becomes
active in an inactive cell or the last UE of an active cell is deleted or becomes
inactive).

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 210/300

RNC & NodeB Health Check for NEV 4.2- How To

In UA4.2, iCEM forecast capability is:


Number of cell per BBU

MAC-hs data rate per cell

1 cell / BBU

10.8 Mbps / cell

2 cells / BBU

5.4 Mbps / cell

3 cells / BBU

3.6 Mbps /cell

Check on Cells
In order to check the status of each BTS Cell, perform as follows:
Enter $$$ to get the menu > cap
CCM-Callp>lbg
CCM-Callp/lbg>ctx
___________________________________________________________________________
| Index | MessageType |
Id
| CEMType | Slot | BBU/Codec | DSP/Modem |
|-------+-------------+------------+---------+------+-----------+-----------|
|
0 | Cell
|
2011 | iCEM64 |
9 | Codec0
| Modem0
|
|
1 | Cell
|
2012 | iCEM64 |
9 | Codec0
| Modem2
|
|
2 | Cell
|
2014 | iCEM64 |
9 | Codec0
| Modem1
|
|
| Cell (hsdpa)|
2014 | iCEM64 |
7 | Codec0 |
|
|
3 | Cell
|
2015 | iCEM64 |
9 | Codec0
| Modem1
|
|
| Cell (hsdpa)|
2015 | iCEM64 |
7 | Codec0 |
|
|
4 | CTCH
|
1312731 | iCEM64 |
9 | Codec0
| Modem0
|
|
5 | CTCH
|
1312732 | iCEM64 |
9 | Codec0
| Modem2
|
|
6 | CTCH
|
1312734 | iCEM64 |
9 | Codec0
| Modem1
|
|
7 | CTCH
|
1312735 | iCEM64 |
9 | Codec0
| Modem1
|
|
8 | CTCH
|
1050587 | iCEM64 |
9 | Codec0
| Modem0
|
|
9 | CTCH
|
1050588 | iCEM64 |
9 | Codec0
| Modem2
|
|
10 | CTCH
|
1050590 | iCEM64 |
9 | Codec0
| Modem1
|
|
11 | CTCH
|
1050591 | iCEM64 |
9 | Codec0
| Modem1
|
|
12 | RadioLink
|
1264 | iCEM64 |
9 | Codec0
| Modem2
|
1264 | iCEM64 |
7 | Codec0 | Modem0
|
|
| RL
(hsdpa)|
|_______|_____________|____________|_________|______|___________|___________|
CCM-Callp/lbg>

The above BTS has got an STSR-2 configuration (2 frequencies).


From the screen above, the following information can be retrieved:
cells 2011, 2012 are not HSDPA cells
cells 2014 and 2015 have been configured in HSDPA (R5)
CTCH: Common Transport Channel
An HSDPA call is running on the BTS : this call is made of a DCH part (uplink)
and an HSDPA part (downlink)
HSDPA services are handle by the iCEM64 in slot 7 (1 H-BBU)
Indeed, for an HSDPA call, the DCH channel in uplink will be supported by a D-BBU
(iCEM slot 9 in our case) and the HSDPA services in downlink will be supported by an
H-BBU (iCEM slot7 in our case).
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 211/300

RNC & NodeB Health Check for NEV 4.2- How To

An HSDPA call will always be set up on the same iCEM board than the one that handles
the cell.
Enter $$$ to get the menu > cap
CCM-Callp>lbg
CCM-Callp/lbg>nodeb
lbg>NodeB Capacities
lbg>|-------------------------+---------------+---------------|
lbg>|
Parameters
| Current Value |
Ref Value
|
lbg>|-------------------------+---------------+---------------|
lbg>| NodeB Hsdpa Max User Nb +
19
+
20
|
lbg>|-------------------------+---------------+---------------|
CCM-Callp/lbg>

The above command will provide the number of HSDPA calls running on the BTS.
Value 19 means that 1 HSDPA call is active on the BTS (= 20 -1)
In case the cell doesnt come up with HSDPA services when it has been configured so on
the OMC, the power parameters and the NBAP cell setup Procedure need to be checked
as follows:
Enter $$$ to get the menu >
CCM-Callp>ctx
CCM-Callp/ctx>cell
CCM-Callp/ctx/cell>
CCM-Callp/ctx/cell>display
[]
Rncuc Id
:
Cell Carrier Id
:
Local Cell Id
:
TCell
:
UL Frequency
:
DL Frequency
:
Max Transmission Power
:
Primary DL Scrambling Code:
Primary SCH Power
:
Secondary SCH Power
:
Primary CCPCH Power
:
BCH Id
:
Primary CPICH Power
:
Nb of physical channels
:
HSDPA service ACTIVATED :
maxTransmissionPowerHsdpa :
nbOfHSPDSCHCodes
:
startCodeNumber
:
nbOfHSSCCHCodes
:

cap

0
2062
12062
3
9837
10787
420
170
-50
-50
-20
5
320
2
397
10
6
2

Pmax = 42dBm

Pcpich = 32dBm
The Cell is HSDPA: No issue
max Power available for HSDPA

For any reason like OCNS Feature activation, it could happen that the available power on
the BTS is not enough to setup the HSDPA service that is to say an HSDPA call (Pmin =
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 212/300

RNC & NodeB Health Check for NEV 4.2- How To

PHS-SCCH min + PHS-PDSCH min where PHS-SCCH min = PCPICH + min(HS-SCCH Power
Offset) and PHS-PDSCH min = Pmax 39dB) in dB
The above parameters can be found in the configuration:
>: RNC RNC_1206 NodeB BTS_193895 FDDCell BTS_193895_0 dis
[]
localCellId
12061
locationAreaCode
1206
maxCellRadius
2200
maxTxPower
42.0 Pmax
measurementConfClassRef
(RNC,259)(RadioAccessService,0)(DedicatedConf,0)(MeasurementConfClass,0)
measurementConfId
RadioAccessService/0 DedicatedConf/0
MeasurementConfClass/0
minCellRadius
10
mobileCountryCode
450
mobileNetworkCode
00
nbReportsBeforeSwitchingToEventMode
5
nInSyncInd
1
nmo
nmoValue1
nOutSyncInd
256
OCNSActivation
false
OCNSPower
0
OCNSSpreadingFactor
spreadingFactor8
operationalState
disabled
operatorId
0
pcpichPower
32.0 Pcpich
plmnValueTag
0
plmnValueTagMethodUsed
lacRac
powerConfClassRef
(RNC,259)(RadioAccessService,0)(DedicatedConf,0)(PowerConfClass,0)
powerConfId
RadioAccessService/0 DedicatedConf/0
PowerConfClass/0
powerCtrlConfClassRef

>: BTSEquipment BTS_193895 BTSCell 0 HsdpaConf 0 dis


class
HsdpaConf
dchPowerMargin
20
dn
(BTSEquipment,66)(BTSCell,0)(HsdpaConf,0)
harqNbMaxRetransmissions
7
harqType
mirType
hsdpaResourceId
0
hsdschInterval
50
hsscchPcOffset
{ 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 3.0 -3.0 -5.0 -5.0 -8.0 -8.0 -8.0 -8.0 -8.0 -8.0 -8.0 -8.0 -8.0 -8.0 -8.0 -8.0
-8.0 -8.0 -8.0 -8.0 -8.0 }
HS-SCCH Power Offset
maxRateGrowth
8
operatorId
0
userSpecificInfo
NONE

A new procedure applies on the IUB Interface regarding the HSDPA services:
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 213/300

RNC & NodeB Health Check for NEV 4.2- How To

BTS

CRNC
Cell Setup Request
Cell Setup Response

Common Transport Channel Setup Request


Common Transport Channel Setup Response
Physical Shared Channel Reconfiguration Request (HSDPA configuration)
Physical Shared Channel Reconfiguration Response
System Information Update Request
System Information Update Response

In the above DFD, a new Physical Shared Channel Reconfiguration Procedure will apply
in case the cell has been configured with HSDPA service at the OMC. This procedure is
used to setup the new HSDPA Transport Channels (HS-DSCH channels for Data
transmission and HS-SCCH Channels for signaling transmission)
To monitor these messages on the BTS, perform as follows:
NBAP Traces
Telnet on the iCCM:
Enter $$$ to get the menu > rtc
CCM-RTC_TOOLS>trace
CCM-RTC_TOOLS/TRACES>ut 14 0
Traces 0 of function 14 desactivated
CCM-RTC_TOOLS/TRACES>ut 14 1
Traces 1 of function 14 desactivated
CCM-RTC_TOOLS/TRACES>ut 14 2
Traces 2 of function 14 desactivated
CCM-RTC_TOOLS/TRACES>ut 14 3
Traces 3 of function 14 desactivated
CCM-RTC_TOOLS/TRACES>ut 14 4
Traces 4 of function 14 desactivated
CCM-RTC_TOOLS/TRACES>act 14
Trace INPUT OUTPUT ERROR PASSAGE activated for function 14
CCM-RTC_TOOLS/TRACES>act 13
Trace INPUT OUTPUT ERROR PASSAGE activated for function 13

Telnet on the iCEM:

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 214/300

RNC & NodeB Health Check for NEV 4.2- How To


Enter $$$ to get the menu > rtc
ICEM-RTC_TOOLS>flr
ICEM-RTC_TOOLS/FLR>o 0 3
ICEM-RTC_TOOLS/FLR>rtc
ICEM-RTC_TOOLS>trace
ICEM-RTC_TOOLS/TRACES>act 13
Trace INPUT OUTPUT ERROR PASSAGE activated for function 13

Be careful, to display the traces on the Terminal, verify the following configuration:
Parameter Term = yes in RTC>FLR>CONF
Traces on an HSDPA call using DSPTool
Telnet on the iCEM which supported the HSDPA call (H-BBU)
Perform as follows:
First
Enter $$$ to get the menu > rtc
ICEM-RTC_TOOLS> dsptool
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SetFunctionalMode 1
ICEM-RTC_TOOLS/ICEM_DSPTOOL> Setdumpmode 0
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SetOutput_DspTrace 0
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SetOutput_DspPrintf 0
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SetBufferMode 0 one shot (1 = circular)

Then activate the DSP Traces


There are two ways to do it
1) Manually
ICEM-RTC_TOOLS/ICEM_DSPTOOL>Activate_DspTrace w x x1 y z a b c for each trace Id
[]
ICEM-RTC_TOOLS/ICEM_DSPTOOL> Ref
To refresh the buffer
ICEM-RTC_TOOLS/ICEM_DSPTOOL> stop
To stop traces
ICEM-RTC_TOOLS/ICEM_DSPTOOL> resume
To resume traces

Where:
w = codecId(HEX), x=traceId(HEX), x1=periodicity, y=BurstSize, z=number of
mobiles to be traced, a,b,c=mobile Ids
ICEM-RTC_TOOLS/ICEM_DSPTOOL> listDSP
---------------------------| DSP
| DSP Number |
---------------------------| MBBC_MDM0 |
0x0000
|
---------------------------| MBBC_MDM1 |
0x0001
|
----------------------------

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 215/300

RNC & NodeB Health Check for NEV 4.2- How To


| MBBC_MDM2 |
0x0002
|
---------------------------| MBBC_CDC
|
0x0004
|
----------------------------

to obtain w

ICEM-RTC_TOOLS/ICEM_DSPTOOL> List_DspTrace
| Help CDC Traces:
|
| trace tag
Trace Num(HEX)|
|----------------------------------------------|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|

CDC_TRACE_GLO
CDC_TRACE_UE
CDC_TRACE_UE_TEST
CDC_TRACE_DL_ATM_CELL
CDC_TRACE_UL_ATM_CELL
CDC_TRACE_CAPA_CDC
CDC_TRACE_KER_STATS
CDC_TRACE_DL_CODED_TRCH
CDC_TRACE_ATM_STATS
CDC_TRACE_CAPA_MDM
CDC_TRACE_ATM_FP_INFO
CDC_TRACE_DL_STAT_FP
CDC_TRACE_COD_DL_FP
CDC_TRACE_DL_INFO_TRCH0
CDC_TRACE_KPI_UL
CDC_TRACE_ATM_FP_COUNT
CDC_TRACE_DEC_CODEBLOCK
CDC_TRACE_RACH_ACK
CDC_TRACE_RACH_NACK
CDC_TRACE_DL_ATM_CTRL_CELL
CDC_TRACE_UL_ATM_CTRL_CELL
CDC_TRACE_SHIFTED_RL_PARAMS
CDC_TRACE_RACH_PREAMBLE

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|

B5
B6
B7
B8
B9
BA
BB
BC
BD
BE
BF
C0
C1
C2
C3
C4
C5
C6
C7
C8
C9
CA
CB

| Help MDM Traces:


|
|
|
|
|
|
|
|
|
|
|

to obtain x

MDM_TRACE_UE_UL
MDM_TRACE_EXTND_IMP_RESP
MDM_TRACE_FINGER
MDM_TRACE_IMP_RESP
MDM_TRACE_GLO
MDM_TRACE_KER_STATS
MDM_TRACE_DL_UE
MDM_TRACE_DL_CRCP_UE
MDM_TRACE_PW_CTRL
MDM_TRACE_CM_UL
MDM_TRACE_SHIFTED_RL_PARAMS

HSDPA TRACES:
| HCDC_TRACE_NOT_SCHED
| HCDC_TRACE_GLO
| HCDC_TRACE_UE_STAT
| HCDC_TRACE_QID_STAT
| HCDC_TRACE_FLW_CTRL_STAT
| HCDC_TRACE_OVSF_POWER_STAT
| HCDC_TRACE_UE_SCD_STAT
| HCDC_TRACE_HS_SCCH
| HCDC_TRACE_CQI_STAT
| HCDC_TRACE_PDSCH_USAGE
| HCDC_TRACE_SCHED
| HCDC_TRACE_DPCCH_INFO

D5
D6
D7
D8
D9
DA
DB
DC
DD
DE
DF

|
|
|
|
|
|
|
|
|
|
|

E1
E2
E3
E4
E5
E6
E7
E8
E9
EA
EB
EC

|
|
|
|
|
|
|
|
|
|
|
|

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 216/300

RNC & NodeB Health Check for NEV 4.2- How To


|
|
|
|
|
|
|
|
|

HCDC_TRACE_SCD_UNDER_RUN
HCDC_TRACE_SCD_QID_SELECT
HCDC_TRACE_FLW_ATM_STATS
HCDC_TRACE_OVSF_CODE_STAT
HCDC_TRACE_COD_USER_PLANE
HCDC_TRACE_SCHED_RESULTS
HCDC_TRACE_CAPA_ALLOC
HCDC_TRACE_PDU_DISCARDED
HCDC_TRACE_SCD_STAT

ED
EE
EF
F0
F1
F2
F3
F4
F5

|
|
|
|
|
|
|
|
|

| Help HMDM Traces:


|
| HMDM_TRACE_UE_UL
F6
|
| HMDM_TRACE_DL_UE
F7
|
| HMDM_TRACE_ACK_TIMING
F8
|
| HMDM_TRACE_CQI_STAT
F9
|
| HMDM_TRACE_ACK_TIMING_COUNTER
FA
|
|----------------------------------------------|

The most useful ones are in bold in the above table


Periodicity = 1
BurstSize = 0

means that traces will be collected every TTI (2ms)


indicates the number of times that trace will be displayed

(0 = infinite)
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SendGloContextReq w

a, b, c (gives information

on calls and cells Ids)


2) Automatically
Enter $$$ to get the menu > rtc
ICEM-RTC_TOOLS> dsptool
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SetFunctionalMode 1
ICEM-RTC_TOOLS/ICEM_DSPTOOL> Setdumpmode 0
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SetOutput_DspTrace 0
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SetOutput_DspPrintf 0
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SetBufferMode 0
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SendMmg <script.MMG>

Example:
Enter $$$ to get the menu > rtc
ICEM-RTC_TOOLS> dsptool
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SetFunctionalMode 1
ICEM-RTC_TOOLS/ICEM_DSPTOOL> Setdumpmode 0
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SetOutput_DspTrace 0
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SetOutput_DspPrintf 0
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SetBufferMode 0
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SendMmg TRACE_ON.MMG
ICEM-RTC_TOOLS/ICEM_DSPTOOL> ref
ICEM-RTC_TOOLS/ICEM_DSPTOOL> stop
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SendMmg TRACE_OFF.MMG

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 217/300

RNC & NodeB Health Check for NEV 4.2- How To

The script Files should be present in the following directory of the iCCM board
(/SLAVE/SLAVE0x/data) where x = slot number of the iCEM.
Traces Collection
Once the test has been performed, collect the logs in the following directory of the iCCM
board: SLAVE/SLAVE0x/dsptlog/ (perform a ftp connection on the iCCM and get the
file DSPToolTrace.log)
Traces Decoding
Traces decoding via the NodeBL1Logger Application

Enter the DSP log File in the first input Field (DSPToolTrace.log) then the Obsb3u.h
File (located in the NodeBL1Logger installation directory) and the target directory.
Then, press the START button.
When the START button comes back again, it means the decoding has been done.

Result Analysis via the Pre Denis Macro

1) Start the Pre Denis Application


2) Choose the Enable Macro Option
3) Choose Charts and Stats = FullStats
Press the Launch NodeB Macro Button and fill in with the directory that has been
generated by the NodeBL1Logger Application.
It will generate automatically some result Tabs for each mobile.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 218/300

RNC & NodeB Health Check for NEV 4.2- How To

In order to download the Tools or for any other specific information, please refer to the
following useful Link: http://umts-eye/

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 219/300

RNC & NodeB Health Check for NEV 4.2- How To

7.15. ALCAP/RANAP How To

7.15.1. How to .. Check and Troubleshoot ALCAP services


CLASSIC/COMPACT
Definition & Stack
The ALCAP services (Specification Q2630) are used to initiate CS calls towards the Core
Network (Iu/IuR Interfaces). It is needed to set up the transport bearers (Data Bearer) for
the User Plane and it belongs to the Transport Network Control Plane
The establishment and release of User Plane Transport bearers for the IuCS interface are
initiated by the RNC using ALCAP messages, typically in response to the RANAP RAB
assignment procedures. Aal2 connections are identified by means of a CID and a
PATHID. The CID identifies an Aal2 connection, whereas the PATHID identifies an aal2
Path. There are up to 248 Aal2 connections within each Aal2 Path. The remote aal2 node
is identified by means of A2EA addresses.
The A2EA, PATHID and CID are carried in ALCAP ERQ messages for establishing the
Aal2 connections. ALCAP identifiers are used only in the Transport Network Control
plane:
- On the IU interface, the RNC is in charge of allocating a CID.
- On the IuR interface, the SRNC is in charge of allocating a CID.
ALCAP
Q2150.1
MTP3B
SSCF-NNI
SSCOP
AAL5
ATM
PHY

The PSFP PDC board will handle the saalNni and the SSCOP layers
The PMC-NI APs will handle the MTP3 layer
The PMC-M board will handle the ALCAP for IuCS and IuR interfaces.
Call Flow

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 220/300

RNC & NodeB Health Check for NEV 4.2- How To

RNC-IN

RNC-CN

MGw

MGC

RANAP/ RAB Assignment Request


TransportLayerAddress:A2EA
CID allocationRequest
CID allocationResponse

Alcap/ ERQ
- AEA
- PatchId
- CID

Alcap/ ECF

RANAP/ RAB Assignment Response

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 221/300

RNC & NodeB Health Check for NEV 4.2- How To

Configuration
In V4.2, this protocol is only supported on the Iu/IuR interfaces.
In order to check the ALCAP configuration, the following commands have to be
performed:
There are two possibilities in the configuration, either the ALCAP signaling is carried
over the same RouteSet as the SCCP signaling or it can use a separate RouteSet.
In the example below, the commands have been performed on a classic RNC with an
Associated Mode Configuration.
Check configuration of CS User Plane:
9> d -p

Iucs/* IuUplane Aal2Lk/*

Iucs/* IuUplane Aal2Lk/*


+======+--------------------+---------------------------------------|Aal2Lk|
aal2If
|Response
+======+--------------------+---------------------------------------|
1|Aal2If/300
|
Aal2 Interface for IuCS services
ok
2006-05-22 18:06:29.30
14> d aal2if/300
Aal2If/300
adminState = unlocked
operationalState = enabled
usageState
= active
ok
2006-05-22 18:09:18.42
33> d -p Aal2If/300 Alcap AlcapConn
Aal2If/300 Alcap AlcapConn
destPointCode = 2
Point Code of the Distant Equipment that will handle the

ALCAP Procedure
networkIndicator = nationalSpare Network Indicator
ok
2006-05-22 18:20:00.63
15> d -p Aal2If/300
Aal2If/300
customerIdentifier = 0
commentText
= CS
ecrOverBook
= 100 %
cacMethod
= aal2if
loadBalancingMethod = pc
qos0BwReservation
= 0 %
qos1BwReservation
= 0 %
qos2BwReservation
= 0 %
qos3BwReservation
= 0 %
umtsInterfaceList
= Iucs/1 IuUplane Aal2Lk/1
aal2RouteList
= RncIn Qaal2P Aal2EndPoint/1 Route/1
ok
2006-05-22 18:10:03.08
17> d -p RncIn Qaal2P
RncIn Qaal2P
originatingA2ea = 470000999999999999999960400020480d032f00 should equal the

rncNSAPAddress
(see below)
timerErq

= 5 seconds
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 222/300

RNC & NodeB Health Check for NEV 4.2- How To


timerRel
= 2 seconds
timerRes
= 10 seconds
timerBlo
= 5 seconds
timerUbl
= 5 seconds
timerMod
= 2 seconds
resetRetries
= 3
ok
2006-05-23 14:13:08.02
14> d -p RncIn Qaal2P Aal2EndPoint/1
RncIn Qaal2P Aal2EndPoint/1
address = 470000999999999999999940200020480d222200 Distant A2EA @ (sent in the

ERQ message)
ok

2006-05-23 14:02:04.10

17> d Aal2If/300 Path/*


Aal2If/300 Path/*
+=====+-----+----+-----+--------+-------|Path |osiAd|osiO|osiUs|remoteBl|localBlo
|
| min |per | age |ockingSt|ckingSta
|
|
|
|
| atus | tus
+=====+-----+----+-----+--------+-------|
48|unlck|ena |activ|unbloc |unbloc
ok
2006-05-22 18:11:37.88

path Id (sent in the ERQ message)

18> d -p Aal2If/300 Path/*


Aal2If/300 Path/*
+=====+--------------------+---+-----+---------------------------------------|Path |
atmConnection
|qos|pathO|Response
|
|
|
|wner |
+=====+--------------------+---+-----+---------------------------------------|
48|AtmIf/815 Vcc/1.48 | 0|yes |
|
| Nep
|
|
|
ok
2006-05-22 18:12:48.08

28> d AtmIf/815 Vcc/1.48 rxcell,txcell


AtmIf/815 Vcc/1.48
rxCell = 10
it should increase
txCell = 0
it should increase
ok
2006-05-22 18:13:40.11

How to check the rncNSAPAddress using wicl:


>: rnc RNC_1202 dis
accessRestrictionList
class
clusterId
cnodeCapacity
dn
frequencyBand
inAccessOperationalState
isSysInfoChangeNotifMobilesFach
isSysInfoChangeNotifMobilesIdle
mobileCountryCode
mobileNetworkCode
modelName
operationalState

{ NONE }
RNC
Cluster/UMAINSERV1
29
(RNC,260)
umtsBand
enabled
true
true
450
00
2
enabled
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 223/300

RNC & NodeB Health Check for NEV 4.2- How To


operatorId
outageGranularity
passiveSystemRelease
perfServerId
pmClusterId
provisionedSystemRelease
rncArchitecture
rncFamily
rncId
rncNSAPAddress
runningSoftwareVersion
stateChangeNotificationDelay
systemRelease
upgradeStatus
userLabel
userSpecificInfo

0
30
04_01_00
UPERFSERV1
PMCluster/UPERFSERV1
04_02_00
rnc1000
rnc1000
2
470000999999999999999960400020480d032f00
RC42162061300
0
04_02_00
IDLE
RNC_1202
Default_RNC

Check configuration of CS Transport Control Plane (ALCAP):


38> d -p

ss7 mtp3/* ls/*

Ss7 Mtp3/* Ls/*


+====+==+---------------+------+---------------------------------------|Mtp3|Ls|
apc
|netInd|Response
+====+==+---------------+------+---------------------------------------|
1| 0|2
|nation|
|
1| 1|6
|nation|
|
1| 2|14
|nation|
ok
2006-05-22 18:30:17.44
40> d -p

ss7 mtp3/1 ls/0 lk/*

Ss7 Mtp3/1 Ls/0 Lk/*


+==+--------------------+---------------------------------------|Lk|
saalNni
|Response
+==+--------------------+---------------------------------------| 0|Ss7 SaalNni/1
|
ok
2006-05-22 18:31:57.45
30> d Ss7 SaalNni/*
Ss7 SaalNni/*
Use -noTabular to see hidden attributes: customCntr3, customCntr2,
customCntr1, insvFail, pduOctRx, pduOctTx, pduRx, pduTx, noRespTo and
maxCcR.
+=======+-----+----+-----+----+------+----------+----------+---------|SaalNni|osiAd|osiO|osiUs|card|state |
n1
|
c1
| inSrvDur
|
| min |per | age |
|
|
|
|
seconds
+=======+-----+----+-----+----+------+----------+----------+---------|
1|unlck|ena |activ|
2|comple|
0|
0|
0
|
17|unlck|ena |activ|
3|comple|
1000|
0|
0
|
33|unlck|dis |idle |
2|notSta|
1000|
0|
0
ok
2006-05-23 15:45:35.27

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 224/300

RNC & NodeB Health Check for NEV 4.2- How To


44> d -p Ss7 SaalNni/1 nap
Ss7 SaalNni/1 Nap
atmConnection = AtmIf/815 Vcc/1.32 Nep ALCAP signaling is carried over this VCC
ok
2006-05-22 18:33:11.74

45> d AtmIf/815 Vcc/1.32


AtmIf/815 Vcc/1.32
adminState = unlocked
operationalState = enabled
usageState
= busy
connectionPointType = connectionEndPoint
distributionType
= pointToPoint
numLeaves
= 0
callDirection
= notApplicable
operStatus
= unknown
localFailureCause
= noFailure
troubled
= no
segLinkSideLoopbackState = unknown
segSwitchSideLoopbackState = notApplicable
endToEndLoopbackState
= unknown
rxOamCellCongestionState
= good
aisState
= good
rdiState
= good
txCell
= 39885 Check that it is increasing
txCellDiscard
= 0
txFrameDiscard
= 0
txFrameDiscardClp
= 0
rxCell
= 39881 Check that it is increasing
rxCellDiscard
= 0
rxCellDiscardClp
= 0
rxFrameDiscard
= 0
rxFrameDiscardClp
= 0
rxAal5FrameError
= 0
rxAal5FrameAbort
= 0
lastMinimumCtd
= noMeasurement
lastMaximumCtd
= noMeasurement
lastAverageCtd
= noMeasurement
currentCtd
= noMeasurement
lastCtdSampleSize
= 0
ok
2006-05-22 18:34:34.53

To see on which PSFP are the saalnni:


25> os
Debug tracing directed to this OS shell.
<Welcome to DebugShell:VxWorks Version 5.3.1>
WARNING: Commands available at this interface may be service
impacting. This interface is for debugging only.
Do not proceed without proper authority and training.
Do you wish to proceed? [Yes/No]: y
OS> set unsafe
WARNING: Entering unsafe mode. Commands available from this interface are not
supported for field use without specific direction from Nortel
Networks.
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 225/300

RNC & NodeB Health Check for NEV 4.2- How To


OS> set promote
OS>
OS> showSaalNniProxyInfo
ProvChanged is False
Total PSFP cards: 4
Number of SaalNni cards on A side: 1
Number of SaalNni cards on B side: 1
SaalNni proxies on two NI cards:
Pid: 5/1/2/13000
Card#: 5
Pid: 4/1/2/20680
Card#: 4
SaalNni proxies on A side:
[0] Pid: 2/1/2/26312
Card#: 2
PSFP card #2 is used for SaalNni
provReqReceived_m = 1
hadProvData_m
= 1
# of SaalNnis: 2
SaalNni list:
saalnni/1 --> mtp3/1 ls/0 link/0
saalnni/33 --> mtp3/1 ls/2 link/0
SaalNni proxies on B side:
[0] Pid: 3/1/2/28616
Card#: 3
provReqReceived_m = 1
hadProvData_m
= 1
# of SaalNnis: 1
SaalNni list:
saalnni/17 --> mtp3/1 ls/1 link/0

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 226/300

RNC & NodeB Health Check for NEV 4.2- How To

7.15.2. How to .. Check and Troubleshoot RANAP services


CLASSIC/COMPACT
Definition & Stack
Whereas ALCAP is used for the Transport Control Plane (Transport Signalling) for
IuCS, the RANAP protocol is identified as the Control Plane (Radio Network Signalling)
on the IuCS and IuPS Interfaces.
The UMTS Iu CP traffic (RANAP) uses the services from SCCP/MTP3B/
SaalNNI/AAL5/ATM.
RANAP messages are exchanged between the RNC and the MGC/SGSN.

RANAP
SCCP
MTP3B
SSCF-NNI
SSCOP
AAL5
ATM
PHY

The PSFP PDC board will handle the saalNni and the SSCOP layers
The PMC-NI APs will handle the SCCP and MTP3 layer
The TMU board will handle the RANAP Protocol.
Configuration
How to check the DPCs (destination Point Code) for the RANAP Protocol using wicl :
>: rnc RNC_1202 CsCoreNetworkAccess 0 dis
administrativeState
unlocked
availabilityStatus
{ }
ciphering
cipheringDisabledIgnore
class
CsCoreNetworkAccess
dn
(RNC,260)(CsCoreNetworkAccess,0)
iucsIfId
1
mobileCountryCode
450
mobileNetworkCode
00
nbResetRepetitions
5
operationalState
enabled
operatorId
0
qosIdList
{ 0 }
relocationCiphering
cipheringEnabled
sccpDestinationPointCode
2
Destination Point Code for CS Domain
sccpNetworkIndicator
sccpNetworkNationalReservedUse
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 227/300

RNC & NodeB Health Check for NEV 4.2- How To


NetworkIndicator for CS
securityControl
tcnResetAck
userSpecificInfo

integrityActivated
120000
NONE

>: rnc RNC_1202 PsCoreNetworkAccess 0 dis


administrativeState
unlocked
availabilityStatus
{ }
ciphering
cipheringDisabledIgnore
class
PsCoreNetworkAccess
dn
(RNC,260)(PsCoreNetworkAccess,0)
isRabRelMgtAllowed
false
mobileCountryCode
450
mobileNetworkCode
00
nbResetRepetitions
5
operationalState
enabled
operatorId
0
relocationCiphering
cipheringEnabled
sccpDestinationPointCode
6
Destination Point Code for PS Domain
sccpNetworkIndicator
sccpNetworkNationalReservedUse

NetworkIndicator for PS
securityControl
tcnResetAck
userSpecificInfo

integrityActivated
120000
Default_PsCoreNetworkAccess

RNC-IN Configuration
27> d -p

ss7 mtp3/* ls/*

Ss7 Mtp3/* Ls/*


+====+==+---------------+------+---------------------------------------|Mtp3|Ls|
apc
|netInd|Response
+====+==+---------------+------+---------------------------------------|
1| 0|2
|nation| CS SCCP RouteSet (apc=dpc of CS as listed above)
|
1| 1|6
|nation| PS SCCP RouteSet (apc=dpc of PS as listed above)
|
1| 2|14
|nation|
ok
2006-05-23 15:44:00.91
28> d -p

ss7 mtp3/1 ls/0 lk/*

Ss7 Mtp3/1 Ls/0 Lk/*


+==+--------------------+---------------------------------------|Lk|
saalNni
|Response
+==+--------------------+---------------------------------------| 0|Ss7 SaalNni/1
| SaalNni for CS
ok
2006-05-23 15:44:37.01
29> d -p

ss7 mtp3/1 ls/1 lk/*

Ss7 Mtp3/1 Ls/1 Lk/*


+==+--------------------+---------------------------------------|Lk|
saalNni
|Response
+==+--------------------+---------------------------------------| 0|Ss7 SaalNni/17
| SaalNni for PS
ok
2006-05-23 15:45:00.57

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 228/300

RNC & NodeB Health Check for NEV 4.2- How To

30> d Ss7 SaalNni/*


Ss7 SaalNni/*
Use -noTabular to see hidden attributes: customCntr3, customCntr2,
customCntr1, insvFail, pduOctRx, pduOctTx, pduRx, pduTx, noRespTo and
maxCcR.
+=======+-----+----+-----+----+------+----------+----------+---------|SaalNni|osiAd|osiO|osiUs|card|state |
n1
|
c1
| inSrvDur
|
| min |per | age |
|
|
|
|
seconds
+=======+-----+----+-----+----+------+----------+----------+---------|
1|unlck|ena |activ|
2|comple|
0|
0|
0
|
17|unlck|ena |activ|
3|comple|
1000|
0|
0
|
33|unlck|dis |idle |
2|notSta|
1000|
0|
0
ok
2006-05-23 15:45:35.27
32> d -p Ss7 SaalNni/* nap
Ss7 SaalNni/* Nap
+=======+--------------------+---------------------------------------|SaalNni|
atmConn
|Response
+=======+--------------------+---------------------------------------|
1|AtmIf/815 Vcc/1.32 | signaling Vcc for CS
|
| Nep
|
|
17|AtmIf/815 Vcc/2.32 | signaling Vcc for PS
|
| Nep
|
|
33|AtmIf/807 Vcc/3.32 |
|
| Nep
|
ok
2006-05-23 15:54:54.52
33> d AtmIf/815 Vcc/2.32 check Vcc state for PS
AtmIf/815 Vcc/2.32
adminState = unlocked
operationalState = enabled
usageState
= busy
connectionPointType = connectionEndPoint
distributionType
= pointToPoint
numLeaves
= 0
callDirection
= notApplicable
operStatus
= unknown
localFailureCause
= noFailure
troubled
= no
segLinkSideLoopbackState = unknown
segSwitchSideLoopbackState = notApplicable
endToEndLoopbackState
= unknown
rxOamCellCongestionState
= good
aisState
= good
rdiState
= good
txCell
= 1607715
Check that it is increasing
txCellDiscard
= 0
txFrameDiscard
= 0
txFrameDiscardClp
= 0
rxCell
= 1606853
Check that it is increasing
rxCellDiscard
= 0
rxCellDiscardClp
= 0
rxFrameDiscard
= 0
rxFrameDiscardClp
= 0
rxAal5FrameError
= 0
rxAal5FrameAbort
= 0
lastMinimumCtd
= noMeasurement

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 229/300

RNC & NodeB Health Check for NEV 4.2- How To


lastMaximumCtd
= noMeasurement
lastAverageCtd
= noMeasurement
currentCtd
= noMeasurement
lastCtdSampleSize
= 0
ok
2006-05-23 15:57:39.85

RNC-CN Configuration
See paragraph 7.10 IU/IUR links check(OMU/TMU Side) for the RANAP reset procedure
to be checked on the CNode.
Troubleshooting
For investigation and before any restart of the RNC, please follow the Technical Card
available at the url:
http://eurlivelink.europe.nortel.com/livelink/livelink.exe/23627527/SS7_instability.doc?func=doc.Fetch&nodeid=23627527

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 230/300

RNC & NodeB Health Check for NEV 4.2- How To

8 TOOLS
8.1. UMTS Log Collection Engine
Applicable for RNC classic in V4.2

8.1.1. Documentation/tool
For more details refer to the UMTS GPS tools web site:
http://eurlivelink.europe.nortel.com/livelink/livelink.exe?func=ll&objId=17471511&objAction=browse&sort=nameHYPERLINK%20%22

for:

The specifications,
The user guide.

8.1.2. Purpose
The Log Collect Engine tool allows to collect automatically:
A set of logs for a RNC
A set of observation files for a RNC
A set of logs for CallP issue.
Remarks:
These logs are a mandatory for each RNC case.
The tool has to be executed for each end of outage.

8.1.3. Quick start


Mandatory information
Interface Node CP address, login and password
Control Node OMU addresses, logins and passwords.
Tools location
OAM V4.x
/opt/nortel/shell/access/UtranLogCollector.sh
RNC logs collected storage
/opt/nortel/data/support/UtranLogCollection.tra
Tools log files
/opt/nortel/logs/access
Usage
./UtranLogCollector.sh (-DEBUG option traces all the commands executed if needed).
Time/space cost
For a classic RNC with 120 NodeB under a loaded context:
a package of 13Mo is generated
time of execution: almost 55 minutes.
OAM V5.x
/opt/nortel/shell/support_tools/LogCollection/UtranLogCollector.sh
RNC logs collected storage
/opt/nortel/logs/support_tools/LogCollection/UtranLogCollection.tra
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 231/300

RNC & NodeB Health Check for NEV 4.2- How To

Tools log files


/opt/nortel/logs/support_tools
Usage
It is the same as OAM V4.x, please see the usage of OAM V4.x above.

8.1.4. Screenshots of OAM V4.x


+-------------------------------------------------|
UTRAN LOG COLLECTION TOOL
+-------------------------------------------------|
|---RNC
|
|--- 1 Collect RNC logs
|
|--- 2 Collect RNC observations files
|
|--- 3 Collect CallP logs
|
|-------------------------------------------------|---> q : quit the tool
+-------------------------------------------------Please enter your choice:

For example the menu 1:


RNC label (under wicl), password for the connection to wicl, logins/passwords for the
(telnet) connection to the Control Node and Interface Node and a date will be required
+-------------------------------------------------|
UTRAN LOG COLLECTION TOOL
+-------------------------------------------------|
|---RNC
|
|--- Collect RNC logs
|
|
|
|
|
|-------------------------------------------------|---> q : quit the tool
|---> b : back to the previous menu
+-------------------------------------------------RNC user Label: "RNC_1209"
NSP nortel password: "xxxxx"
User to use to log to the CNode:"omu"
CNode omu password:"xxxxx"
User to use to log to the IN:"debug"
Password for user "debug" to log to the IN: "debug"
Data collected between: "20040707" and "20040714"
All information OK (yes/no) ?:yes

The data collected are stored under /opt/nortel/data/support

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 232/300

RNC & NodeB Health Check for NEV 4.2- How To

saba:/opt/nortel/data/support <130> (nortel) % ll -tr


total 234536
[]
UtranLogCollection.20050823.RNC1205.tar
-rw-rw-rw1 nortel
nortel
13976390 Aug 23 10:20 UtranLogCollection.20050823.RNC1201.tar.gz
-rw-rw-rw1 nortel
nortel
118 Aug 23 11:18 RncCallPCollection.20050823.RNC1209.tar.gz
-rw-rw-rw1 nortel
nortel
1536 Aug 23 11:29 RncCallPCollection.20050823.RNC1209.1.tar
-rw-rw-rw1 nortel
nortel
96828 Aug 23 11:54 UtranLogCollection.20050823.RNC1209.tar.gz
saba:/opt/nortel/data/support <131> (nortel) %

The file needs to be gunzipped and untarred.

8.1.5. Screenshots For OAM V5.x


+-------------------------------------------------|
UTRAN LOG COLLECTION TOOL
+-------------------------------------------------|
|---RNC
|
|--- 1 Collect RNC logs
|
|--- 2 Collect RNC observations files
|
|--- 3 Collect CallP logs
|
|--- 4 Collect RNC Emergency logs
|
|---BTS
|
|--- 5 Collect NodeB logs
|
|-------------------------------------------------|---> q : quit the tool
+-------------------------------------------------Please enter your choice:

For example the menu 1:


RNC label (under wicl), password for the connection to wicl, logins/passwords for the
(telnet) connection to the Control Node and Interface Node and a date will be required

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 233/300

RNC & NodeB Health Check for NEV 4.2- How To

+-------------------------------------------------|
UTRAN LOG COLLECTION TOOL
+-------------------------------------------------|
|---RNC
|
|--- Collect RNC logs
|
|
|
|
|
|-------------------------------------------------|---> q : quit the tool
|---> b : back to the previous menu
+-------------------------------------------------RNC user Label: "RNC_1202"
User to use to log to Wicl:"nortel"
NSP nortel password: "nortelGPS"
User to use to log to the CNode:"omu"
CNode omu password:"omu"
User to use to log to the IN:"debug"
Password for user "debug" to log to the IN: "debug"
Number of days for data collection : "1"
Data collected between: "20060516" and "20060517"
All information OK (yes/no) ?:yes

... RNC Ip Address found


Checking OMUs Activity
+-------------------------------------------------|
LOG COLLECTION TOOL
+-------------------------------------------------|
|---CLASSIC RNC LOG COLLECTION
|
|--- 1 Collect CN logs
|
|--- 2 Collect IN logs
|
|--- 3 Collect All logs
|
|-------------------------------------------------|---> q : quit the tool
+-------------------------------------------------Please enter your choice: 1
Gathering OAM data for RNC "RNC_1202"
... OAM data for RNC "RNC_1202" collected

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 234/300

RNC & NodeB Health Check for NEV 4.2- How To

The data collected are stored under /opt/nortel/data/support_tools/LogCollection/


bernard:/opt/nortel/data/support_tools/LogCollection <112> (nortel) % ls -lrt | grep RNC1202
-rw-rw-rw1 nortel
nortel
3479811 May 18 13:28 UtranLogCollection.20060518.RNC1202.tar.gz
bernard:/opt/nortel/data/support_tools/LogCollection <113> (nortel) %

The file needs to be gunzipped and untarred.


8.2. RNC traffic check and cell diagnose tool
This tool is implemented for V4.1 (or higher) versions only.

8.2.1. Documentation
For a full documentation on this tool refer to:
RNC Traffic Check and Cell Diagnose Tool (Q00867258) User Guide. It can be
found under: http://eurlivelink.europe.nortel.com/livelink/livelink.exe?func=ll&objId=12278784&objAction=
browse&sort=name

Q00867258 RNC Traffic Check and Cell Diagnose Tool Feature HLD/DD
UMTS/RNC/DD/01200

8.2.2. Tools and logs location

There are a part of the RNC IN delivery (for RNC1000 and RNC1500) and
launched from the OAM server under
/opt/nortel/data/srs/DELIVERY/PASSPORT/software/cnp/Rxxxxxxxxxxxx/external
with Rxxxxxxxxxxxx the version used (passport version RI41083052310 in our case).

The results are stored under:


o /tmp/traffic_check_result or /tmp/cell_diag_result for the last displayed
result only.
o /tmp/cpAddress_dateThour

8.2.3. Overview of RNC Traffic Check


8.2.3.1 Purpose
The RNC Traffic Check tool provides the capability to verify the call processing activity
and the status of resources through a single command:
Number and states of cells for each TMU
Number of CS and PS calls for each TMU
SS7 links, linksets and route status
RANAP and RNSAP SCCP status.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 235/300

RNC & NodeB Health Check for NEV 4.2- How To

8.2.3.2 How to launch the tool Example


1st step: to launch the tool.
The rncconfig file can be customized
Example of rncconfig file:
RNC_NAME
RNC_1209
RNC_1205

OAM_IP
47.164.76.81
47.164.52.125

OAM_USER
debug
debug

OMU5_IP
47.164.52.123

OMU9_IP
47.164.52.124

OMU_USER
omu

Then launch ./trafficCheck.exp <RNC_NAME>, the - fields will be requested by the


tool.
Or simply launch ./trafficCheck.exp
saba:/opt/nortel/data/srs/DELIVERY/PASSPORT/software/cnp/RI41083052310/external
<208> (nortel) % ./trafficCheck.exp

2nd step: results provided / logs.


The result is displayed in one shot on the users screen.
The example below is truncated and segmented on purpose.
Lauching ./trafficCheck.exp the IP address and the login/password to connect onto the
CP and the OMU will be requested.
CLASSIC
OMU addresses will also be requested:
saba:/opt/nortel/data/srs/DELIVERY/PASSPORT/software/cnp/RI41083052310/external <208>
(nortel) % ./trafficCheck.exp
[]
============================================================================
RNC Traffic Check Starting
============================================================================
Enter
Enter
Enter
Enter
Enter
Enter
Enter

IN address
login / password to connect the CP

OAM(CP) IP address: 47.164.52.125


OAM(CP) user: debug
OAM(CP) password for user debug:
OMU_5 IP address: 47.164.52.123
OMU user: omu
OMU password for user omu: omu
OMU_9 IP address: 47.164.52.124

first OMU address


login / password to connect the OMU
second OMU address

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 236/300

RNC & NodeB Health Check for NEV 4.2- How To

COMPACT

saba:/opt/nortel/data/srs/DELIVERY/PASSPORT/software/cnp/RI41083052310/external <208>
(nortel) % ./trafficCheck.exp
[]
============================================================================
RNC Traffic Check Starting
============================================================================
Enter OAM(CP) IP address: 47.164.76.81
Passport CP address
Enter OAM(CP) user: debug
login / password to connect the CP.
Enter OAM(CP) password for user debug: debug
Logging this session in logfile:
/tmp/47.164.76.81_20050823T155745/logtrafficCheck.exp_no_rnc_specified.tmp
The result will be saved to /tmp/traffic_check_result

Two logs are generated:

The .tmp file gathers all the commands and results to build up the report

/tmp/traffic_check_result contains the last summary provided by the tool.


=======================================
Cell State Information Per TMU
=======================================
Cell State Information for TMU Inst. 6
---------------------------------------------Operational State
Availability State
Number of Cells
[]
Cell State Information for TMU Inst. 13
---------------------------------------------Operational State
ENABLED
DISABLED

Availability State
ONLINE
FAILED

Number of Cells
6
30

The TMU with instance 6 has no cell.


The TMU with the instance 13 holds 6 cells ENABLED ONLINE.
And 30 cells DISABLED FAILED in this case actions might be taken to fix it
No cell must be in a DISABLED FAILED state.
=============================
Number of CS/PS Calls per TMU
=============================
Num of CS Calls
Num of PS Calls

TMU
[]
TMU Inst.

66

162

TMU Inst.

71

150

[]
TMU Inst. 13

=====================================
UE Call Type Distribution Per TMU
=====================================
Call Type Distribution for

TMU Inst.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 237/300

RNC & NodeB Health Check for NEV 4.2- How To


-------------------------------------------No UE calls running on the TMU
[]

ulAsConf
0
2
5
0
11
15
0

Call Type Distribution for TMU Inst. 3


-------------------------------------------dlAsConf
number_of_calls
call_type
2
5
PS64K x PS64K
3
4
DCCH_SRB x DCCH_SRB
5
66
CS12.2K x CS12.2K
6
39
PS64K x PS128K
13
4
CELL_FACH_SRB x CELL_FACH_SRB
19
78
CELL_FACH_TRB x CELL_FACH_TRB
27
40
PS64K x PS0K_HS_DSCH

[]

refer to paragraph 7.8.3. RBSet & AsConf Id to see calltype AsConf.

===================
RANAP SCCP Status
===================
SCCP
1

LOC
142

SCCP
1

LOC
143

Admin State
Oper State
unlocked
enabled
===================
RNSAP SCCP Status
===================
Admin State
Oper State
unlocked
enabled

Usage State
active

Usage State
active

===================
SS7 Route Set Status
===================
N/A
===================
SS7 Route Status
===================
N/A
===================
SS7 Link Set Status
===================
+====+==+-----+----+-----+-------+-------+----------+----------+---------|Mtp3|Ls|osiAd|osiO|osiUs|osiAvai|osiProc|customCntr|customCntr|customCntr
|
| | min |per | age |
l
|
|
1
|
2
|
3
+====+==+-----+----+-----+-------+-------+----------+----------+---------|
1| 0|unlck|ena |activ|
|
|
n/a|
n/a|
n/a
|
1| 1|unlck|ena |activ|
|
|
n/a|
n/a|
n/a
|
1| 2|unlck|ena |activ|
|
|
n/a|
n/a|
n/a
ok
===================
SS7 Link Status
===================
+====+==+==+-----+----+-----+----------+----------+----------+---------|Mtp3|Ls|Lk|osiAd|osiO|osiUs| pdusRx | plPdusRx | pdusTx | plPdusTx
|
| | | min |per | age |
|
|
|
+====+==+==+-----+----+-----+----------+----------+----------+---------|
1| 0| 0|unlck|ena |activ|
87630|
1155|
87867|
1041
|
1| 1| 0|unlck|ena |activ|
87146|
848|
87173|
861
|
1| 2| 0|unlck|ena |activ|
87565|
1246|
88095|
1753
ok

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 238/300

RNC & NodeB Health Check for NEV 4.2- How To

===================
IU Domain Data
===================
CS Domain Index: 0
------------------- cnDomainInd
:
+ CS Permanent Data
:
- create_state
:
- NbResetRepetitions:
- TcnResetAck
:
- plmnId
:
-

domainInstance
:
isSccpAvailable
:
proceedSccpAvailable:
resetStatus
:
transacId
:
isUpdateDdOK
:
isResetSyncNeeded

CS_DOMAIN(0)
ADM_AO_CREATED(1)
Object created
5
120000
plmnid[0]: 84 plmnid[1]: 240 plmnid[2]: 0
IU_CS(0)
true(1)
false(0)
CN_RESET_END(1)
0
true(1)

Ranap Reset Ack received for CS.

CS Domain Index: 1
------------------- cnDomainInd
:
+ CS Permanent Data
:
- create_state
:
- NbResetRepetitions:
- TcnResetAck
:
- plmnId
:

CS_DOMAIN(0)

IU_CS(0)
false(0)
false(0)
CN_RESET_BEGIN(0)
0
false(0)

domainInstance
:
isSccpAvailable
:
proceedSccpAvailable:
resetStatus
:
transacId
:
isUpdateDdOK
:
isResetSyncNeeded

ADM_AO_NOT_CREATED(0)
0
0
plmnid[0]: 255 plmnid[1]: 255 plmnid[2]: 255

PS Domain Index: 0
------------------- cnDomainInd
:
+ PS Permanent Data
:
- create_state
:
- NbResetRepetitions:
- TcnResetAck
:
- plmnId
:

PS_DOMAIN(1)

IU_PS(1)
true(1)
false(0)
CN_RESET_END(1)
1
true(1)

domainInstance
:
isSccpAvailable
:
proceedSccpAvailable:
resetStatus
:
transacId
:
isUpdateDdOK
:
isResetSyncNeeded

ADM_AO_CREATED(1)
5
120000
plmnid[0]: 84 plmnid[1]: 240 plmnid[2]: 0

Ranap Reset Ack received for PS.

PS Domain Index: 1
------------------- cnDomainInd
:
+ PS Permanent Data
:
- create_state
:
- NbResetRepetitions:
- TcnResetAck
:

PS_DOMAIN(1)
ADM_AO_NOT_CREATED(0)
0
0

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 239/300

RNC & NodeB Health Check for NEV 4.2- How To


- plmnId
-

: plmnid[0]: 255 plmnid[1]: 255 plmnid[2]: 255

domainInstance
:
isSccpAvailable
:
proceedSccpAvailable:
resetStatus
:
transacId
:
isUpdateDdOK
:
isResetSyncNeeded

IU_PS(1)
false(0)
false(0)
CN_RESET_BEGIN(0)
0
false(0)

Status are also provided for Ranap and Rnsap sccp, and the ss7 link sets.
They all must be enabled active.
Regarding the domains, the create states must be ADM_AO_CREATED and the reset
status CN_RESET_END (i.e. Ranap reset ack received).
See paragraphs 7.10. IU/IUR links check and 7.12. How To debug SS7 on the RNCInterface Node for more details.

8.2.4. Overview of Cell Diagnose


8.2.4.1. Purpose
Cell Diagnose is dedicated to the trouble shooting of sleepy cells.
Two modes are available:
the simple display of information
or a diagnostic algorithm to point out an abnormal condition.
8.2.4.2 How to launch the tool Example
To launch the tool
./cellDiagnose.exp <RNC_NAME> if the rncconfig file is defined.
or ./cellDiagnose.exp .
Example of the display option (for the diagnose option, refer to the User guide).
The data on cell 2092, on a compact RNC have been retrieved.
3 parts can be outlined:
The NBAP view from the CNode
The CID states
The automaton states.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 240/300

RNC & NodeB Health Check for NEV 4.2- How To

saba:/opt/nortel/data/srs/DELIVERY/PASSPORT/software/cnp/RI41083052310/external <246>
(nortel) % ./cellDiagnose.exp
[]
============================================================================
Cell Diagnose Tool Starting
============================================================================
Please choose option:
Available Options:
1. Cell Information Display
2. Cell Diagnose
3. Quit
Your Option is: 1
1
===========================================================================
Cell Information Display
===========================================================================
Please choose option:
Available Options:
1. Display information for one cell
2. Display information for all cells under a nodeB
3. Quit
Your Option is: 1
1
Enter OAM(CP) IP address: 47.164.76.81
CP address
login/password for the
Enter OAM(CP) user: debug
Enter OAM(CP) password for user debug: debug
Logging this session in logfile:
/tmp/47.164.76.81_20050823T185024/logcellDiagnose.exp_no_rnc_specified.tmp

CP

logfile
Input External Cell ID 2092
======================================================================
Display All Cells Information For External Cell ID = 2092
======================================================================

Do you want to display the output on the screen, y or n y


The result will be saved to /tmp/cell_diag_result
logfile of the last result.
Do you want to display historic information for cell automatons? y or n yes
External Cell ID : 2092 cell id
nodeb id
External NodeB ID : 257
Local Cell ID
: 12092
NodeB CP
: 0
Internal NodeB Id : 0
Internal_Cell_Id : 1
Cell Trace Key
: 0x82d0000
cell tracekey
TMU in charge of the cell.
TMU Instance
: 13
NodeB Info :
==========

The Control port state must be


ENABLED /ONLINE

NodeB Control Port State :

Control_port[0]:
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 241/300

RNC & NodeB Health Check for NEV 4.2- How To


Admin state:
NodeB Control Port Type:
Availability Status:
Operational State:
Iub Access Res Ctx St:
PconnId:
UconnId:
Control_port[1]:
Admin state:
NodeB Control Port Type:
Availability Status:
Operational State:
Iub Access Res Ctx St:
PconnId:
UconnId:

CREATED
NODEB_CONTROL_PORT
ONLINE
ENABLED
WAIT_CPNODEB_DISC_REQ
0
0
CREATED
NODEB_COMMUNICATION_CONTROL_PORT
ONLINE
ENABLED
WAIT_CPNODEB_DISC_REQ
257
1

Control_port[2]:
Admin state:
NodeB Control Port Type:
Availability Status:
Operational State:
Iub Access Res Ctx St:
PconnId:
UconnId:

CREATED
NODEB_COMMUNICATION_CONTROL_PORT
ONLINE
ENABLED
WAIT_CPNODEB_DISC_REQ
514
2

Current NOB Automaton State : connected


Cell State Info : (Obtainted from TMU)
===============
Cell Admin State:
Cell Operational State:
Cell Availablity State:

The Cell must be ENABLED/ONLINE

UNLOCKED
ENABLED
ONLINE

Current NOB Cell Automaton State


nobcell_cell_Mgt
:
operational
Current NOB RRC Automaton State
nobrrc_sysinfocell :
wait_change

Common channels configuration

Common Channels Info


====================
NOB

Common Channel State :

PCH
:
FACH_0:
FACH_1:
RACH :

NOBCCH_NBAP_CONFIG
NOBCCH_NBAP_CONFIG
NOBCCH_NBAP_CONFIG
NOBCCH_NBAP_CONFIG

SCCPCH:
PRACH:

NOBCCH_SETUP_SUCCESS
NOBCCH_SETUP_SUCCESS

No NBAPFAILURE must be present

Current NOB CCH Automaton State


nobcch_rootaut
:
cch_configured
nobcch_setupaut
:
root_idle
nobcch_qaal2aut
:
qaal2_established

QAAL2 must be established.

CID for Each Common Channel

CID dedicated to PCH-FACH-RACH

PCH
:
FACH_0:
FACH_1:
RACH :

Pathgroup:
Pathgroup:
Pathgroup:
Pathgroup:

4
4
4
4

Path:
Path:
Path:
Path:

16
16
16
16

Cid:
Cid:
Cid:
Cid:

11
12
13
27

Logical Address
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 242/300

RNC & NodeB Health Check for NEV 4.2- How To

NOB
NOB
NOB
NOB

CCH
RRC
RPM
DPH

RNC User Address:


RNC User Address:
Logical Handle:
Logical Handle:

Rman Cell RPM Related Info


==========================
RPM Logical Group:
260
Rman Call ID:
369
RAB PMC for the Active Cell RPM:
RAB PMC for the Spare Cell RPM:

221
221
0x41001e41
0x41000c42

Provides the active RAB


in charge of the cell: lp/11 ap/2.
Location: LP: 11 AP: 2 IP: 172.253.209.27
Location: LP: 14 AP: 3 IP: 172.253.209.10

Rman TLR Info


TLR_1: Pathgroup: 4 Path: 16

Cid: 11

TLR_2: Pathgroup: 4 Path: 16

Cid: 12

TLR_3: Pathgroup: 4 Path: 16

Cid: 13

TLR_4: Pathgroup: 4 Path: 16

Cid: 27

TBM AAL2 CID and Path Related Info (Obtained from PMC-M)
=======================================================

Status for each CID from the PMC-M


perspective.
TLR_1: IuxIf ID: 1 Pathgroup: 4 Path: 16

Cid: 11

The CID 11 on IuxIf 1, Pathgroup 4,


path 16 used for PCH is:
CID State in TBM:
Q.AAL2 State
: ESTABLISHED
Callp State
: COMMITTED_s
CallP Audit Flag Set: No
Quick Audit Flag Set: No
Trace Key
: 3221226850

Commited is the normal state

Path State

Path Status in TBM:


Admin State:

UNLOCKED

Operatioinal State: ENABLED


Usage State:
ACTIVE
Active QAAL2:
No
Local Block State: UNBLOCKED_s
Remote Block State: UNBLOCKED_s
localUnblkEnabled State: ENABLED
ResetInProgress:
No

Both blocks (local,remote) must be


unblocked

Path Binding State:


Double Bound
Active PC:
Location: FP: 4 AP: 4
Standby PC: Location: FP: 15 AP: 4

lp/4 ap/4 is the active PC (AAL2<-> AAL5)

Path Status in Aal2If:


Admin State:
Operational State:
Usage State:
Remote Block State:

unlocked
enabled
active
unblocked

According to the choice performed at the beginning, the automaton states are displayed.
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 243/300

RNC & NodeB Health Check for NEV 4.2- How To

As a reminder, one cell only was chosen.


All the last events relative to the NodeB and cell setup can be founds in this log (qaal2
establishment, audit response, cell setup response, common channels setup response).
Automaton History Info
===
===================================================================
iNodeBRefPerNodebCP: 0
current cp: 0
History Entry #1
[]
History Entry #6
Time: 1970/01/02 02:27:48.995000
Sequence #5
Automaton: nob_nobroot
State: connecting_wait_audit_response
Logical event: nbap_audit_required_indication
Result: Treated
Next state: connecting_wait_audit_response

Last events between NodeB and TMU:


NBAP Audit Required / Audit Response

History Entry #7
Time: 1970/01/02 02:27:49.017000
Sequence #6
Automaton: nob_nobroot
State: connecting_wait_audit_response
Logical event: nbap_audit_response
Result: Treated
Next state: connected

Current automaton: nob_nobroot


Current state: connected
No saved events available.
===================================================================
TELNET_CI>
nobcell cellaut 0 1
@ - Result of: nobcell cellaut 0 1
===================================================================
*** Display information for CellMgt automaton ***
===================================================================
Current cp: 0
iCellRefPerNodebCP: 1
History Entry #1
[]
History Entry #6
Time: 1970/01/02 02:27:49.020000
Sequence #5
Automaton: nobcell_setup
State: wfath_new_cell_setup
Logical event: inodeb_nobcell_setup_request
Result: Treated
Next state: wait_cell_setup_response
History Entry #7
Time: 1970/01/02 02:27:50.845000
Sequence #6
Automaton: nobcell_setup
State: wait_cell_setup_response
Logical event: nbap_cell_setup_response
Result: Treated
Next state: wfath_new_cell_setup
History Entry #8
Time: 1970/01/02 02:27:50.845000

Cell Setup Request

Cell Setup Response on NBAP

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 244/300

RNC & NodeB Health Check for NEV 4.2- How To


Sequence #7
Automaton: nobcell_cellMgt
State: wson_cell_setup_response
Logical event: inodeb_cellsetup_response
Result: Treated
Next state: wait_nobrrc_sysinfo_update
History Entry #9
Time: 1970/01/02 02:27:56.462000
Sequence #8
Automaton: nobcell_cellMgt
State: wait_nobrrc_sysinfo_update
Logical event: inodeb_sysinfo_update
Result: Treated
Next state: wait_nbap_sysinfo_update_resp

Sys info update

History Entry #10


Time: 1970/01/02 02:27:56.510000
Sequence #9
Automaton: nobcell_cellMgt
State: wait_nbap_sysinfo_update_resp
Logical event: nbap_sys_info_update_response
Result: Treated
Next state: operational

Sys info Response

Current automaton: nobcell_cellMgt


Current state: operational
No saved events available.
===================================================================
TELNET_CI>
nobrrc sysinfoaut 0 1
@ - Result of: nobrrc sysinfoaut 0 1
===================================================================
*** Display information for sysinfo automaton ***
===================================================================
Current cp : 0
iCellRefPerNodebCP : 1
History Entry #1
Time: 1970/01/02 02:27:43.013000
Sequence #0
Automaton: nobrrc_sysinfocell
State: root_idle
Logical event: swact
Result: Treated
Next state: wait_sysinfo
History Entry #2
Time: 1970/01/02 02:27:43.030000
Sequence #1
Automaton: nobrrc_sysinfocell
State: wait_sysinfo
Logical event: rnccom_available
Result: Treated
Next state: wait_sysinfo
History Entry #3
Time: 1970/01/02 02:27:50.845000
Sequence #2
Automaton: nobrrc_sysinfocell
State: wait_sysinfo
Logical event: inodeb_cell_sysinfo
Result: Treated
Next state: wait_sysinfo
History Entry #4
Time: 1970/01/02 02:27:56.461000
Sequence #3
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 245/300

RNC & NodeB Health Check for NEV 4.2- How To


Automaton: nobrrc_sysinfocell
State: wait_sysinfo
Logical event: inodeb_cch_info
Result: Treated
Next state: wait_change
Current automaton: nobrrc_sysinfocell
Current state: wait_change
No saved events available.
===================================================================
TELNET_CI>
nobcch rootaut 0 1
@ - Result of: nobcch rootaut 0 1
===================================================================
*** Display information for Root automaton ***
===================================================================
Current cp: 0
iCellRefPerNodebCP: 1
History Entry #1
[]
History Entry #30
Time: 1970/01/16 02:29:09.405000
Sequence #119
Automaton: nobcch_root
State: cch_configured
Logical event: rpm_alive_ind
Result: Treated
Next state: cch_configured
Current automaton: nobcch_root
Current state: cch_configured
No saved events available.
===================================================================
TELNET_CI>
nobcch setupaut 0 1
@ - Result of: nobcch setupaut 0 1
===================================================================
*** Display information for setup automaton ***
===================================================================
Current cp: 0
iCellRefPerNodebCP: 1
History Entry #1
[]
History Entry #8
Time: 1970/01/02 02:27:56.312000
Sequence #8
Automaton: nobcch_setup_setup
State: root_idle
Logical event: setup_start
Result: Treated
Next state: wait_qaal2_est_end
History Entry #9
Time: 1970/01/02 02:27:56.313000
Sequence #9
Automaton: nobcch_setup_setup
State: wait_qaal2_est_end
Logical event: qaal2_est_end
Result: Treated
Next state: wait_nbap_setup_response
History Entry #10
Time: 1970/01/02 02:27:56.450000
Sequence #10
Automaton: nobcch_setup_setup
State: wait_nbap_setup_response

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 246/300

RNC & NodeB Health Check for NEV 4.2- How To


Logical event: nbap_cch_setup_response
Result: Treated
Next state: root_idle
Current automaton: nobcch_setup_setup
Current state: root_idle
No saved events available.
===================================================================
TELNET_CI>
nobcch qaal2aut 0 1
@ - Result of: nobcch qaal2aut 0 1
===================================================================
*** Display information for qaal2 automaton ***
===================================================================
Current cp: 0
iCellRefPerNodebCP: 1
infos for PRACH:
PRACH OK at a QAAL2 level
History Entry #1
Time: 1970/01/02 02:27:56.312000
Sequence #0
Automaton: nobcch_Qaal2_Qaal2
State: root_idle
Logical event: qaal2_est_start
Result: Treated
Next state: wait_qaal2_est_rsp
History Entry #2
Time: 1970/01/02 02:27:56.313000
Sequence #1
Automaton: nobcch_Qaal2_Qaal2
State: wait_qaal2_est_rsp
Logical event: qaal2_est_cfm
QAAL2 establishment confirm
Result: Treated
Next state: qaal2_established
Current automaton: nobcch_Qaal2_Qaal2
Current state: qaal2_established
No saved events available.

FACH OK at a QAAL2 level

infos for for FACH[0]:


History Entry #1
Time: 1970/01/02 02:27:50.846000
Sequence #0
Automaton: nobcch_Qaal2_Qaal2
State: root_idle
Logical event: qaal2_est_start
Result: Treated
Next state: wait_qaal2_est_rsp
History Entry #2
Time: 1970/01/02 02:27:50.848000
Sequence #1
Automaton: nobcch_Qaal2_Qaal2
State: wait_qaal2_est_rsp
Logical event: qaal2_est_cfm
Result: Treated
Next state: qaal2_established

QAAL2 establishment confirm

Current automaton: nobcch_Qaal2_Qaal2


Current state: qaal2_established
No saved events available.
infos for for FACH[1]:
[]
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 247/300

RNC & NodeB Health Check for NEV 4.2- How To


Current automaton: nobcch_Qaal2_Qaal2
Current state: qaal2_established
No saved events available.
infos for for FACH[2]:
[]
Current automaton: nobcch_Qaal2_Qaal2
Current state: qaal2_established
No saved events available.

PCH OK at a QAAL2 level

infos for PCH


History Entry #1
Time: 1970/01/02 02:27:50.846000
Sequence #0
Automaton: nobcch_Qaal2_Qaal2
State: root_idle
Logical event: qaal2_est_start
Result: Treated
Next state: wait_qaal2_est_rsp
History Entry #2
Time: 1970/01/02 02:27:50.848000
Sequence #1
Automaton: nobcch_Qaal2_Qaal2
State: wait_qaal2_est_rsp
Logical event: qaal2_est_cfm
Result: Treated
Next state: qaal2_established
Current automaton: nobcch_Qaal2_Qaal2
Current state: qaal2_established
No saved events available.
TELNET_CI>

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 248/300

RNC & NodeB Health Check for NEV 4.2- How To

8.3. WinRNCSpy (IpSpy, AtmSpy)


WinRNCSPYs usage may be disruptive on a loaded RNC, to be used with care.

8.3.1. Documentation/Tool
The tool for Windows and the Win ATMSPY user guide can be found under:
http://eur-livelink.europe.nortel.com/livelink/livelink.exe?func=ll&objId=4605421
Two functionalities are offered:
The monitoring and decoding of ATM messages within the RNC,
The monitoring and decoding of IP messages between the PSFP and PMC.

8.3.2. AtmSpy overview


8.3.2.1. Tool presentation

Four modes are available


Capture to connect and setup atm traces on the Interface Node
Ftp to retrieve the logs from the Interface Node CP3 card to the users computer.
The file has a .spy extension.
Convert to generate .nor files for post processing by Dune (V3.x only) or Gida.
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 249/300

RNC & NodeB Health Check for NEV 4.2- How To

Decode

8.3.2.2. Passport configuration


Refer to the user guide: a specific provisioning on lp/8 eng ds/appl is a mandatory to run
the tool.
8.3.2.3. Definition of the Vcc Capture settings
The menu Options then VCC Setup must be detailed according to the VCC configuration:
the port id corresponds to the sdh port. Atmif 80x uses the OC3 port x.
the vpi/vci
the protocol that can be associated:
o CnIn for exchanges between the Control Node and the Interface Node
(Classic only)
o NBAP or NBAP 3GPP
o Iub user for the Iub user plane
o RANAP for Iu CS or PS signalization
o Iu CS user or Iu PS user for Iu user plane
o RNSAP for Iur signalisation
o Iur user for Iur user plane
o Alcap
o PCAP
o IP
Below is an example for a compact RNC.
6> d -p atmif/* vcc/* vcd tag
AtmIf/* Vcc/* Vcd
+=====+==========+--------------------+
|AtmIf|
Vcc
|
tag
|
+=====+==========+--------------------+
| 800|0.33
|NB+OAM+00+BTS_277090|
| 800|0.34
|NB+DSS+00+BTS_277090|
| 800|0.42
|NB+NDS+01+BTS_277090|
| 800|0.50
|NB+nCP+00+BTS_277090|
| 800|0.51
|NB+CCP+00+BTS_277090|
| 800|0.52
|NB+CCP+01+BTS_277090|
| 806|5.32
|IR+SCS+00+6
|
| 806|5.48
|IR+TCS+0+6_DS
|
| 806|5.50
|IR+TCS+1+6_NDS
|
| 815|1.32
|CS+SCS+00+9_0
|
| 815|1.48
|CS+TCS+0+9_1209
|
| 815|2.32
|PS+CCP+00+9_1
|
| 815|2.48
|PS+TPS+00+9_1209
|
| 815|2.49
|PS+TPS+01+9_1209
|
| 815|2.50
|PS+TPS+02+9_1209
|
| 815|2.51
|PS+TPS+03+9_1209
|

Iub User
Iub User
NBAP (3GPP)
NBAP (3GPP)
NBAP (3GPP)
RNSAP
Iur user
Iur user
RANAP
Iu CS user
RANAP
Iu PS user
Iu PS user
Iu PS user
Iu PS user

port 0 vcc 0.34


port 0 vcc 0.42
port 0 vcc 0.50
port 0 vcc 0.51
port 0 vcc 0.52
port 6 vcc 5.32
port 6 vcc 5.48
port 6 vcc 5.50
port 15 vcc 1.32
port 15 vcc 1.48
port 15 vcc 2.32
port 15 vcc 2.48
port 15 vcc 2.49
port 15 vcc 2.50
port 15 vcc 2.51

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 250/300

RNC & NodeB Health Check for NEV 4.2- How To


ok

2005-08-25 12:11:19.11

For a RNC1000, the connections to the Control Node must be associated to the protocol
CnIn. Spying the connections to the TMU is highly recommended.
See paragraph 7.11. OMU and TMU VCC info to retrieve the vcc towards TMU and
OMU.
Corresponding setup:

8.3.2.4. Capture mode


To capture traces:
By clicking Connect the passports address, login and password are requested
Command lines need to be sent to the passport, the results and new queries are displayed
in the lower frame.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 251/300

RNC & NodeB Health Check for NEV 4.2- How To

AtmSpy Config button becomes available and leads to the VPI,VCI to spy. For
example to monitor the NBAP layer during a lock/unlock of a cell, select the
NBAP connections:

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 252/300

RNC & NodeB Health Check for NEV 4.2- How To

A command interface becomes available. Always interact with the main lower
window if additional commands are needed (for example yes is required for set
unsafe).

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 253/300

RNC & NodeB Health Check for NEV 4.2- How To

VCC to spy will be setup, then be sure to perform your test between the
atmSpyStart(Stop)Capture steps.

Once all the steps have been performed, end the telnet session with the
Disconnect button in the Capture mode.

8.3.2.5. Ftp mode


Connect onto the passport and retrieve the latest atmspy.xxxxx file.
These files are present under the spyCardx directory (/spooled/closed/appl/spyCardx/ in
fact); x=providing service OC3 card
Download the file to your computer.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 254/300

RNC & NodeB Health Check for NEV 4.2- How To

8.3.2.6. Convert mode (optional)


Generates .nor files that can be post processed by 3Gida (see
http://gato.europe.nortel.com/index.php) Dune.
Browse the .spy file to convert,
the vcc protocol should suit,
convert to the target file

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 255/300

RNC & NodeB Health Check for NEV 4.2- How To

8.3.2.7. Decode mode


Select the .spy file to decode, the level of detail and the correct version
The VCC should be automatically recognized, if not they can be manually modified.
The principle of use is the same that for AtmSpy.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 256/300

RNC & NodeB Health Check for NEV 4.2- How To

8.3.2.8. Manual launch


If a connection through AtmSpy is not possible, the manual commands are:
connection to an OC3
allowing debug mode

os rlogin card8
set unsafe
set promote
atmSpySetMaxVcc 3
atmSpyInstall 40000
atmSpySetBufType 1
atmSpyAddVcc 0 0 50 0 0

3 VCC to be captured
40000 entries in the capture buffer
VCC added
Port 0
VCC 0 50
0 : both directions
0 : raw atm cell

atmSpyAddVcc 0 0 51 0 0
atmSpyAddVcc 0 0 52 0 0
atmSpyShowSettings
atmSpyShowVccs

displays the VCC spied

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 257/300

RNC & NodeB Health Check for NEV 4.2- How To


capture start/stop

atmSpyStartCapture
atmSpyStopCapture
atmSpySaveBuf
atmSpyUninstall
exit

saves the logs


to leave the board.

For more help type atmSpyHelp


The files are logged under /spooled/closed/appl/spyCardx/ (x= service providing OC3
card)
8.3.3.. Overview of IPSpy
8.3.3.1. Usage
The point is to spy the IP traffic between two PMC.
Allowing, for example a trace equivalent to a CnIn trace on the classic.
Example for PMC-RAB / PMC-TMU connection
Mandatory information:
PMC (RAB, TMU) AP
Slot card of the PSFP in charge of the PMC-RAB
PMC-RAB ip address
PMC-TMU ip address
Local and remote tcp ports.
The CellDiagnose tool provides the PMC-RAB address and the TMU instance:
[]
TMU Instance
: 0
[]
Rman Cell RPM Related Info
==========================
[]
RAB PMC for the Active Cell RPM:

Location: LP: 3 AP: 5 IP: 172.253.208.78

The TMU address can be retrieved from its instance,

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 258/300

RNC & NodeB Health Check for NEV 4.2- How To

18> d lp/* ap/* rnc role,instance


Lp/* Ap/* RncAp
+==+==+-------+----------+---------------------------------------|Lp|Ap| role | instance |Response
+==+==+-------+----------+---------------------------------------[]
|2| 1|tmu
|
0|
[]
ok
2005-08-25 19:44:31.41
25> d lp/2 ap/1 ip
Lp/2 Ap/1
ipAddress = 172.253.208.80
ok
2006-05-03 17:34:22.33

The ports are identified by the command vsockShow on the PMC-RAB, by looking for
the socket created for the TMU:
26> telnet -ip(172.253.208.78) vr/1
Trying 172.253.209.6...
Connected to 172.253.209.6.
Escape character is '^]'
-> vsockShow
vsockMGR...
[]
| 0x13756c0 | 118 | fd:14
[]
->

local:172.253.208.78:1025

remote:172.253.208.80:15000

Summary of the pertinent information for IPspy


PMC-RAB (local monitor)
Card / AP
lp/3 ( card 3) AP/5
@ip :
172.253.208.78
port:
1025
protocol:
TCP
PMC-TMU (remote monitor)
Card / AP
lp/2 ( card 2) AP/1
@ip :
172.253.208.80
port :
15000
protocol :
TCP
Card # :
Slot of the PSFP bearing the PMC-RAB 3.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 259/300

RNC & NodeB Health Check for NEV 4.2- How To

To add the remote and local monitors click on Add Monitor and Add FE Monitor.
Use the card number of the local monitor for Card#.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 260/300

RNC & NodeB Health Check for NEV 4.2- How To

Then leave the Capture mode and retrieve the IpSpy file.
The files can be found under the spyCardxx directory, xx corresponding to the Card #
previously used.
The PMC-RAB was on a PSFP in slot 3

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 261/300

RNC & NodeB Health Check for NEV 4.2- How To

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 262/300

RNC & NodeB Health Check for NEV 4.2- How To

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 263/300

RNC & NodeB Health Check for NEV 4.2- How To

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 264/300

RNC & NodeB Health Check for NEV 4.2- How To

8.3.3.2. Manual commands


If a connection through the tool is not possible, the manual commands are:
connection to the PSFP bearing
the RAB PMC

os rlogin card3
yes
set unsafe
set promote
ipspySetMode 1
ipspyInstall
ipspyAdd 5 172.253.208.78 1025 6

allowing debug mode

mode circular
resources allocation for the tool
local port definition
AP 5
IP 172.253.208.78
Port 1025
6 TCP (17 for UDP)
ipspyAddFE 5 172.253.208.78 172.253.208.80 15000 6
remote port definition
Local AP 5
Local IP 172.253.208.78
Remote IP 172.253.208.80
Port 15000
6 TCP (17 for UDP)
ipspyDump
settings summary
ipspyStart
capture start/stop

ipspyStop
ipspyUninstall
exit

to leave the board

For more details type ipspyHelp.


The logs generated are under /spooled/closed/appl/spyCardxx (with xx the card number
of the PSFP in charge of the local PMC).

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 265/300

RNC & NodeB Health Check for NEV 4.2- How To

8.4. CTBL
CTBL traces may be required for specific investigations.
Bulletins already exist to enable them through the OAM CallTrace wizard in the same
time than a call trace activation (on a cell or IMSI).
The second paragraph explains how to setup these traces manually for a cell.
CTBL traces can be disruptive according to the RNC load and the set of traces used.

8.4.1 CTBL traces through CallTrace wizard


Refer to GPS bulletins to activate CTBL traces through the CallTrace Wizard on the
OMC.
RNC V4.2 / OAM V5.0
http://eurlivelink.europe.nortel.com/livelink/livelink.exe/14845541/Bulletin_CTBL_Tracing_via_CTb_RNCV4.0_OAMV4.1.doc?func=
doc.Fetch&nodeid=14845541

8.4.2. Manual CTBL traces on a cell.


A maximum of 9 calls established on a cell can be monitored thanks to CTBL.
8.4.2.1. How to retrieve a cell tracekey
Launch getCellInfo (on the active OMU or through Cott for a compact RNC).
Retrieve the TMU and the internal cell id with getCellInfo.
On the TMU
cp consistency provides the
dump nobcch setupctx cp InternalCellId
On the PMC-Master run
rmanCaCallDbInfo to find the call id
rmanCaDumpTraceKey to find the associated tracekey.
Our example is for cell 2024 on a v4.2 classic RNC.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 266/300

RNC & NodeB Health Check for NEV 4.2- How To


-------------------------------------------------------------------------------------CELL INFORMATION TOOL
(matching between different Cell Id, handled TMU and NodeB CP, cell state, call status)
-------------------------------------------------------------------------------------1. By external cell id
2. By external nodeB id
3. Cell IDs handle by TMU
4. Dump all cell IDs and their handled TMU in a file
5. Quit
Your choice : 1
Enter the external Cell ID : 2024

Ext Cell Id
| Ext NodeB Id | Int Cell Id
| Int NodeB Id | Local Cell Id | NodeB CP
| TMU
shelf,slot| PathGroupId
----------------------------------------------------------------------------------------------------------------------------2024
|
258
|
0
|
0
| 12024 |
0
|
1,12
|
8

TMU is 1 12, and internal cell id 0.


RNC1202_titi-1:/OMU/local/usr/bin (omu) $ telci tmu_1_12_sbc
Trying...
Connected to tmu_1_12_sbc.
Escape character is '^]'.
Telnet CI commands:
Q - quit telci
G - redirect global output.
TELNET_CI> cp con
sbc @tmu_1_12_sbc - Result of: cp consistency
Umts_Nodeb [Oc: 0 Rk: 1]
Active
Umts_Ue [Oc: 0 Rk: 1]
Active
TELNET_CI> nobcch setupctx 0 0
sbc @tmu_1_12_sbc - Result of: nobcch setupctx 0 0
*** Dump Setup automaton context ***
updown : NOBCCH_UPLINK
prachInstance: 0
ctxCch:
pich[0]:
pichInstance: 0
codeNumber: 3
sccpch[0]:
sccpchInstance: 0
pch[0]:
pchInstance: 0
InAal2ReqId: 255
tlr:
aal2PathGroupId: 8
cid: 8
a2p: 32
ownerAccessHandle: 49
ownerContextId: 196698
[]

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 267/300

RNC & NodeB Health Check for NEV 4.2- How To

The ownerContextId is found in the result of rmanCaCallDbInfo on the PMC-M.


PathGroupId, a2p, owneraccessHandles must match.
2> d lp/* ap/* rnc role
Lp/* Ap/* RncAp
+==+==+-------+---------------------------------------|Lp|Ap| role |Response
+==+==+-------+---------------------------------------| 2| 0|aMaste |
[]
3> d lp/2 ap/0 ip
Lp/2 Ap/0
ipAddress = 172.253.202.79
ok
2006-05-16 14:18:20.83
4> telnet -ip(172.253.202.79) vr/1
Trying 172.253.202.79...
Connected to 172.253.202.79.
Escape character is '^]'
->rmanCaCallDbInfo
[]
CallId = 40
rpmId.lg:58/entityId:7
CELL Call
Call state: stable
This call is not pending for audit
This call has AppAct flag unset
Lg=58
Cg=49
This call has 4 TLRs, and they are:
[]
TLR no. 4 is
aal2PathGroupId
= 8
cid
= 8
a2p
= 32
ownerAccessHandle = 49
ownerContextId
= 196698
[]

The callId is 40.


Then RmanCaDumpTracekeys gives the tracekey.
-> rmanCaDumpTraceKeys
May 16 2006
14:23:03.059
******Begin to list all traceKeys******
-TraceKey-PmcId(Hex)- CallId--------------------------------------- 133096 - 0x307 - - 40 []

Tracekey is 133096.
Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 268/300

RNC & NodeB Health Check for NEV 4.2- How To

8.4.2.2. CTBL traces setup on a cell.


Connection on the active PMC-M must be established.
CtblHelp and CtblHelpConcepts can be useful.
Applications and categories must be specified
Applications choice
The SW entities roles (DPH, MAC, DHO,) on the Interface Node must be known.
Below a brief description of the CTBL application constants (ac)
CtblGetApps to view all the available applications.
Constant
CountC_ac
DHO_ac
DPH_ac
GTPu_ac
IUBcch_ac
IUBdch_ac
Iu_ac
MAC_ac
PGS_ac
RLC_ac
Rpm_ac
Rrc_ac
TTI_ac
IURcch_ac
CTBL_ac

Description
Ciphering
Diversity handoff
Datapath handler
GPRS tunneling protocol UL and DL
IUB common channels UL and DL
UB dedicated channels UL and DL
Headers and payload UL and DL
Media access control protocol UL and DL
Paging
Radio link control protocol UL and DL
Radio protocol manager
Radio resource control
Transmission timer interval
IUR common channels UL and DL
CTBL Itself

Categories settings
To focus on a specific theme (mobility, measurement,...) amongst the traces set on the
applications.
CtblShowCats lists the different categories.
Categories
CTBL_UPTC_CONFIG
CTBL_UPTC_CFGDUMP
CTBL_UPTC_UPLINK
CTBL_UPTC_DOWNLINK
CTBL_UPTC_MOBILITY
CTBL_UPTC_MEASUREMENT
CTBL_UPTC_DUMP
CTBL_UPTC_PERTTI_DBGXTRA

Description
Call configuration: setup, modifiation, teardown
Configuration message dumping
Uplink Datapath
Downlink DataPath
Cell and SRNC relocation
Traffic measurement
Payload dumping
Per TTI debug extra

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 269/300

RNC & NodeB Health Check for NEV 4.2- How To

Example
Removes and turns off any
previous CTBL logging.

CtblIdle

CtblSetApps "IUBdch_ac DPH_ac TTI_ac DHO_ac RLC_ac MAC_ac Rrc_ac


Rpm_ac CountC_ac"
Applications to spy are set
CtblSetCatsAll
All categories are set
CtblRemoveCats "CTBL_UPTC_PERTTI_DBGXTRA"
This category is removed (too
much traces consuming)
Turns CTBL traces on
To disable any automatic
stop logging
Logs the CellTracekey (133)
with a maximum of 9 mobiles.
To check the configuration

CtblFilterOn
CtblRemoveStopTrigger
CtblLogCellWithTaggedUes(133096,9)
CtblShowStatus

Turns CTBL traces off


Removes and turns off any
previous CTBL logging.

CtblFilterOff
CtblIdle

8.4.2.3. Traces collection


Once closed, the files are located under
/spooled/closed/appl/rncInCTBinaryLogging
8.4.2.4. Traces decoding
In order to decode the generated CTBL Files, get the relevant parser from the site
http://rncin.ca.nortel.com/, that is to say the one corresponding to the INode version.
On an UNIX station
Perform the following command on the CTBL File:
Unix> parser f < (CtblFileName) > (CtblFile_name_result)
Example:
Unix> parser f < CtblLog.0002.20060328T042936.027.0147 >
CtblLog.0002.20060328T042936.027.0147_decoded

Then, perform a vi on the resulting File.

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 270/300

RNC & NodeB Health Check for NEV 4.2- How To

8.5. Cott
Refer to chapter 2.4 Central OMU TroubleShooting Tools (COTT) (RNC1500RNC1000) .

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 271/300

RNC & NodeB Health Check for NEV 4.2- How To

9 ANNEXE A : RNC 1500 COMMANDS

TelCI Support

TMU

PC

RAB

NI

OMU

PMCM

Component

CP

Tool

Safe

These commands are specific to V4.2 RNC1500.


To be run with extra-care, some of them are disruptive if misused.

showTbmNumbers

Tbm

showTbmAal2

Tbm

showTbmIub

Tbm

showTbmIur

Tbm

showTbmIucs

Tbm

showTbmAal2IfStatusInfo

Tbm

showTbmAal2Path

Tbm

showTbmLpsList

Tbm

showTbmLps

Tbm

showTbmPcList

Tbm

showTbmPc

Tbm

showPcs

Tbm

showPcTab

Tbm

showTbmCidState

Tbm

showTbmAal2PathCidsState Tbm

Description

Dumps out the total number of


paths, pathgroups, logical path
sets and protocol convertors
within TBM.
Dumps out all attributes of a
particular AAL2IF
Dumps out all attributes of a
particular IubIF
Dumps out all attributes of a
particular IurIF
Dump out all attributes of a
particular IucsIF
Dumps out the status
(availability) of all pathgroups
within a particular AAL2IF
Dumps out all the attributes of
a particular path (with
AAL2IFID)
Dumps all the LPS (84)
attributes on the RNC
Dumps all the attributes of a
particular LPS
Dumps all the PC attributes on
the RNC
Dumps attributes of a particular
PC
Dumps all the PC attributes on
the RNC
Dumps a brief summary (table)
of attributes for all paths
provisioned on the RNC
Dumps all attributes of a
particular CID for a given
pathgroup, path and cid
number
Dump the states (I,A,C) of all
CIDs belonging to a particular
aal2If, path pair

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 272/300

TelCI Support

TMU

PC

RAB

NI

OMU

PMCM

Component

CP

Tool

Safe

RNC & NodeB Health Check for NEV 4.2- How To

showTbmAal2CidsState

Tbm

showTbmAal2AllocCid

Tbm

showTbmAal2PathAllocCid Tbm

showCidsBrief

Qaal2

showCid

Qaal2

showCidHistoryBrief

Qaal2

showCidHistoryLong

Qaal2

showCidHistoryLong Different params

Qaal2

showCidHistoryEvents

Qaal2

dumpAllSom

JFK

dumpSom_v

JFK

dumpSo_v

JFK

dumpAllSOs

JFK

dumpJfkSomEventList

JFK

dumpJfkMgrEventList

JFK

InTrCa_printStatus

Call Trace

InTrXdrInfo 1

Call Trace

itfmStatus

Call Trace

Description

Dump the states (I,A,C) of all


CIDs belonging to a particular
aal2If
Dumps all the allocated (or
committed) CIDs on a particular
aal2If
Dumps all the allocated (or
committed) CIDs on a particular
aal2If, path pair
Dumps a summary of all CIDs on
the RNC from the perspective of
QAAL2
Dumps the attributes of a
particular CID based on connId
Dumps a summary of the cid
history for a particular connId
Dumps a detailed record of cid
history based on a particular
connId
Dumps a detailed record of the
cid history based on pathgroup,
path and cidnum
Dumps all the cid history events
supported by the RNC
Dumps out information about all
SOMs on the PMC, RAB, or NI.
Dumps information related to the
SOM specified
Dumps information related to the
SO specified
Dumps out information about all
SOs in the specified SOM
Dumps out the last 60 SOM
events, for the specified SOM
Dumps out the last 15 JFK
Manager events
Displays the status of INode Call
Trace Central Agent
Displays the status of
XDRLayer process in INode Call
Trace
Displays the status of file
manager in INode Call Trace
Central Agent

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 273/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

InTrLa_printStatus

Call Trace

InTrLaOvStatus

Call Trace

talShow

IuPc

talProvShow

IuPc

mtp3TestCase

SS7

sccpTestCase

SS7

WomHelp

WOM

WomShowStatus
WomFilterOff

WOM
WOM

N
N

N
N

Y
Y

N
N

Y
Y

Y
Y

N
N

N
N

Y
Y

WomSetPmcs

WOM

WomSetPmcsAll

WOM

Displays the status of INode Call


Trace Local Agent
Displays the overload status
of INode Call Trace Local
Agent
Displays internal SAS IP
addresses
Displays state information for
TAL process
Provides debugging utilities for
the mtp3b layer on the active
PMCNI
Provides debugging utilities for
the sccp layer on the active
PMCNI
Lists function names with a brief
description of each
Shows the list of reported and
filtered PMC IDs and cell IDs.
Stops reporting of all WOMs.
Replaces the current list of
reported PMC IDs with the valid
values specified in pmcList
Enables WOM reporting on all
availbale PMC IDs.

Adds the list of valid PMC IDs


specified in pmcList to the PMC
IDs already listed as reported

Tool

WomAddPmcs

WOM

WomRemovePmcs
WomRemovePmcsAll

WOM
WOM

N
N

N
N

Y
Y

N
N

Y
Y

Y
Y

N
N

N
N

Y
Y

WomSetCells

WOM

WomSetCellsAll

WOM

WomAddCells

WOM

WomRemoveCells

WOM

WomRemoveCellsAll

WOM

Description

Removes the list of valid PMC


IDs specified in pmcList from the
PMC IDs listed as reported
Removes the list of all PMC IDs
Replaces the current list of
reported cell IDs with the valid
values specified in cellList
Enables WOM reporting on all
avilable cell IDs
Adds the list of valid cell IDs
specified in cellList to the cell
IDs already listed as reported
Removes the list of valid cell IDs
specified in cellList from the cell
IDs listed as reported
Stops reporting WOMs on all cell
IDs

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 274/300

TelCI Support

TMU

PC

RAB

NI

OMU

PMCM

Component

CP

Tool

Safe

RNC & NodeB Health Check for NEV 4.2- How To

WomIdle

WOM

WomCaPrintInfo

WOM

WomChangeReportInterval

WOM

WomReportRequest

WOM

WomSetXdrDecode

WOM

WomGpoRequest

WOM

WomSetCounterSanityChecking WOM

WomPrintInfo

WOM

dumpDphOamCounter

Uplane

dumpIubOamCounter

UPlane

umpTtiOamCounter

UPlane

dumpIurOamCounter
dumpTtiMgr

UPlane
UPlane

N
N

N
N

N
N

N
N

N
N

Y
Y

N
N

N
N

Y
Y

dumpGtpuOamCounter

RAB

dumpIuOamCounter

RAB

dumpDhoOamCounter

UPlane

rmanCaPmcStatus

RMAN CA

rmanCaLgDbInfo

RMAN CA

Description

Releases WOM CLI for


reuse in case previous
request was not properly
terminated
Prints all information
relative to the WomCa
configuration
Changes current WOM
report interval
Requests that an
immediate WOM report be
generated.
Enables/disables XDR
decoding of GPOs before
sent toPFProxy
Requests GPOs currently
configured within specified
time
Enables/disables counter
sanity checking when
"WomApi::Increment" is
called.
Prints all information
relative to the Correlation
group internal to the WOM
Framework
Dumps the status of DPH
and RlcRrcInterface
Dumps the status of Iub
object
Dumps the status of Tti
object
Dumps the status of Iur
object
Dumps the status of TtiMgr
Dumps the status of Iub
object
Dumps the status of Iub
object
Dumps the status of
DhoClass
Displays RMAN status for
all PMC RABs
Displays the lgDatabase
info(detailed)

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 275/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

rmanCaShowSwactLists

RMAN CA

rmanCaCallDbInfo

RMAN CA

rmanCaCallList

RMAN CA

rmanCaCallCid
getRmanCaCellInfo

RMAN CA
RMAN CA

Y
N

N
N

Y
Y

N
N

N
N

N
N

N
N

N
N

Y
Y

rmanLaDumpTraceKeys

RMAN LA

printRmanLa_Table - New
RMAN LA
ActiveRmanCaInvokeAudit RMAN CA
New
startBackgroundCellAuditNow
- New
RMAN CA

rmanCaSetRabUe - New

RMAN CA

rmanCaSetRabCell - New

RMAN CA

rmanCaSetRabNoCall - New
rmanLbCaSetMaxnum_In_Lg
- New
displayOvLa - New
displayOvTable - New

RMAN CA

Invokes RmanCa audit


Immediately starts a
background cell audit
Sets a Rab to take n number
of Ue calls
Sets a Rab to take n number
of Cell calls
Sets a Rab to reject/accept
calls

RMAN CA
N
OVERLOAD Y
OVERLOAD Y

N
N
N

Y
Y
Y

N
N
N

N
Y
Y

N
Y
Y

N
N
N

N
N
N

Y
Y
Y

Sets UE calls/Rab to 128/256


Displays overload LA
Displays overload Table

displayOvAlgorithm - New
displayOvMeastypeVsOpId
New

OVERLOAD Y

OVERLOAD Y

displayOvCtrlValue - New

OVERLOAD Y

Displays overload algorithm


Displays measurement type
vs. Op ID
Displays overload control
value

Tool

Description

Displays the Lgs waiting to


swact
Displays the callDatabase
info(detailed)
Displays RMAN database call
list
Displays CID for specific call
ID
Large output (Per Cell)
Displays all traceKeys
allocated in this PMC
Displays RMAN LA call
database

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 276/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

stkadmca help
stkadmca all
stkadmca lsctx

stkadmca
stkadmca
stkadmca

Y
Y
Y

N
N
N

N
N
N

Y
Y
Y

N
N
N

N
N
N

N
N
N

N
N
N

?
?
?

stkadmca cs

stkadmca

stkadmca ps

stkadmca

stkadmca neigh

stkadmca

stkadmca tmu

stkadmca

stkadmca stacks

stkadmca

stkadmla help
stkadmla all
stkadmla lsctx

stkadmla
stkadmla
stkadmla

Y
Y
Y

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

stkadmla stacks

stkadmla

stkadmla state

stkadmla

stkadmla kill_stkadm_la
INACC_CA help
INACC_CA
display_cd_ctx
INACC_CA
display_dd_ctx
INACC_CA
display_his_log
INACC_CA
display_demar
INACC_CA
check_routing_info
INACC_LA help
INACC_LA
inacc_disp_table_ctx
INACC_LA
inacc_disp_history_log

stkadmla
INACC_CA

N
?

N
N

N
N

N
Y

N
N

N
N

N
N

Y
N

?
?

Prints helps about available


command
Prints all information
Prints all Configuration Data
Prints all CS Core Network Access
or only a given on
Prints all PS Core Network Access
or only a given on
Prints all Neighbouring Rnc or
only a given one
Prints TMU states as seen by
StackAdmC
Prints Stacks Configuration
parameters
Prints helps about available
commands
Prints all information
Prints all Configuration Data
Prints Stacks Configuration
parameters
Prints Finite State Machines current
states
Kill the stkadmla process (for
design test only)
Display the help of inacc_ca utilities

INACC_CA

Dump the MIB cd context

INACC_CA

Dump the dd contex

INACC_CA

Dump ca history log

INACC_CA

INACC_CA
INACC_LA

?
?

N
N

N
N

Y
Y

N
N

N
N

N
N

N
Y

?
?

INACC_LA

Dump the grf context for demar


Check IRT, ORT and Meshlink
tables
Display the help of inacc utilities
Dump the inacc_la tables
(ORT/IRT)

INACC_LA

Dump the inacc_la history buffer)

Tool

Description

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 277/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

INACC_LA

INACC_LA

Dump the CELL_ACCESS user


information
Check IRT, ORT and Meshlink
tables

INACC_LA

Show Inacc_La overload counter

INACC_LA

INACC_LA

Reset Inacc_La overload counter


Set Inacc_La tx queue overload
params

INACC_LA

inacclaStat help
inacclaStat Summary

inacclaStat
inacclaStat

?
?

N
N

N
N

Y
Y

N
N

N
N

N
N

Y
Y

?
?

inacclaStat All

inacclaStat

inacclaStat Addr
cmla_cd DAS
cmla_cd FAS
cmla_cd ALL
cmla_cd DEBUG
cmla_cd NON_DEBUG
DAS

inacclaStat
cmla_cd
cmla_cd
cmla_cd
cmla_cd
cmla_cd
DAS

?
Y
Y
Y
Y
Y
N

N
N
N
N
N
N
N

N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N

N
N
N
N
N
N
N

N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
N

?
?
?
?
?
?
?

oamFmCi DisableReset

oamFmCi

oamFmCi EnableReset

oamFmCi

oamFmCi
GetResetState
oamFmCi Version
oamFmCi Critical
oamFmLa Timer

oamFmCi
oamFmCi
oamFmCi
oamFmLa

Y
Y
N
Y

N
N
N
N

N
N
N
N

Y
Y
Y
Y

N
N
N
N

N
N
N
N

N
N
N
N

Y
Y
Y
Y

?
?
?
?

oamFmLa ListSize
oamFmLa Stats
oamFmLa Version
oamFmMa Timer

oamFmLa
oamFmLa
oamFmLa
oamFmMa

Y
Y
Y
Y

N
N
N
N

N
N
N
N

Y
Y
Y
Y

N
N
N
N

N
N
N
N

N
N
N
N

Y
Y
Y
Y

?
?
?
?

Tool

INACC_LA
inacc_disp_celluser_info
INACC_LA
check_routing_info
INACC_LA
show_ov_counter
INACC_LA
reset_ov_counter
INACC_LA
set_txq_ov_param
INACC_LA
set_slctServTaskDelay

Description

Set task delay ticks for selectLoop


Help about InAccess Stat CI
Manager
Statistics summary
Statistics on all InAccess La
sockets
Show a single InAccess La socket's
statistics
Dump DAS context of CMLA
Dump FAS context of CMLA
Dump DAS / FAS context of CMLA
Start CMLA debug mode
Stop CMLA debug mode
Dump statistics of DAS
disable a reset due to a critical
error processing alarm
enable a reset due to a critical error
processing alarm
show if the reset due to a critical
error processing alarm is enabled
or disabled
show Faultmngt delivery label
set minor or major alarms to critical
set/get timer value
set/get MSSP list max size in
percent of msg pool
display statistics
display delivery label
set/get a timer value

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 278/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

oamFmMa
SweCounter

oamFmMa

oamFmMa ListSize

oamFmMa

oamFmMa ResetMgt
oamFmMa
UseStchList
oamFmMa Stats
oamFmMa Version
tmr pools
tmr timer
tmr version

oamFmMa

oamFmMa
oamFmMa
oamFmMa
tmr
tmr
tmr

Y
Y
Y
Y
Y
Y

N
N
N
N
N
N

N
N
N
N
N
N

Y
Y
Y
Y
Y
Y

N
N
N
N
N
N

N
N
N
N
N
N

N
N
N
N
N
N

Y
Y
Y
Y
Y
Y

?
?
?
?
?
?

fmgscCa
fmgscCa

Y
Y

N
N

N
N

Y
Y

N
N

N
N

N
N

N
N

?
?

use/not use STCH list.


display statistics
display delivery lavel
Information about TMR external bind.
Information about timer selected.
TMR label version.
display help text for the given
command
get FSM state of FmgscCa

fmgscCa

display FmgscMa internal state

fmgscCa

display buffer parameters

fmgscCa

fmgscCa terminate

fmgscCa

fmgscCa set_state
fmgscCa
set_ma_state
fmgscCa
set_buf_parms

fmgscCa

fmgscCa

fmgscCa

fmgscMa
fmgscMa

Y
Y

N
N

N
N

Y
Y

N
N

N
N

N
N

Y
Y

?
?

display buffer entry/entries


terminate FmgscCa (WARNING:
DESTRUCTIVE!)
set state of FmgscCa (WARNING!
DANGEROUS!)
set MA internal state (WARNING!
DANGEROUS!)
set buffer parameters (WARNING!
DANGEROUS!)
display help text for the given
command
get FSM state of FmgscMa

Tool

fmgscCa help
fmgscCa get_state
fmgscCa
get_ma_state
fmgscCa
get_buf_parms
fmgscCa
get_buf_entry

Description

set/get a swe counter


set/get mssp/stch list max size in
percent of msg pool
use/not use reset for total CN
severity overweight.

fmgscMa help
fmgscMa get_state
fmgscMa
get_buf_parms
fmgscMa
get_buf_entry

fmgscMa

display buffer parameters

fmgscMa

fmgscMa terminate

fmgscMa

fmgscMa set_state
fmgscMa
set_buf_parms

fmgscMa

fmgscMa

display buffer entry/entries


terminate FmgscMa (WARNING:
DESTRUCTIVE!)
set state of FmgscMa (WARNING!
DANGEROUS!)
set buffer parameters (WARNING!
DANGEROUS!)

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 279/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

pfca help

pfca

pfca lsconfigData
pfca
nbofPFLAPFPROXY

pfca

pfca

pfca nbofTMU

pfca

pfca PermTraceOn
pfca xdrDecode
pfca xdrDisplay
pfca xdrRm

pfca
pfca
pfca
pfca

Y
Y
Y
Y

N
N
N
N

N
N
N
N

Y
Y
Y
Y

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

?
?
?
?

pfca PermTraceOff
pfla_callp help

pfca
pfla_callp

Y
N

N
N

N
N

Y
N

N
N

N
N

N
N

N
Y

?
?

pfla_callp assert
pfla_callp lscounterId

pfla_callp
pfla_callp

N
N

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

pfla_callp cnaut
pfla_callp
lscounterValue
pfla_callp peg
pfla_callp
resetSleepyCell
pfla_callp addCell
pfla_callp addCtr
pfla_callp delCtr
gob all
gob list
gob genera
gob data
gob method
gob swb
mib help

pfla_callp

Display number of PFLA/PFPROXY


registered
Display Configuration
Data(granularityPeriod,
admin_state..)
Display number of PFLA/PFPROXY
registered
Display info(prefix and AbsPos) of
TMU seen in PFCA
Turn on Perm trace for polling
request and respons
Decode xdr file
Display decoded xdr file
Remove decoded xdr file
Turn off Perm trace for polling
request and response
Displays available commands
Test Pf Callp snapshot when assert
happens
Dump pflactrlist_i100 information
Displays pflacallp Current Cnaut
status

pfla_callp
pfla_callp

N
N

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

Display Counter Value


Increment Counter

pfla_callp
pfla_callp
pfla_callp
pfla_callp
gob
gob
gob
gob
gob
gob
mib

N
N
N
N
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
N
N
N
N
N
N
N

?
?
?
?
?
?
?
?
?
?
?

mib config

mib

mib read

mib

Reset Sleepy Cell


Add Cell to list of cells
Add Counter to list of counters
Delete Counter from list of counters
all information of the gob objects
list of the gob objects
general information
internal data information
methods information
SoftWare Bus information
Help with the MIB Patch Tool.
Shows current MIB Patch Tool
configuration.
Read a table, sub-field or field in the
MIB.

Tool

Description

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 280/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

mib write
mib list
mib patchinfo

mib
mib
mib

N
Y
Y

N
N
N

N
N
N

Y
Y
Y

N
N
N

N
N
N

N
N
N

N
N
N

?
?
?

mib typ

mib

mib size

mib

mib offset

mib

mib padding

mib

mib tablediff

mib

mib mib

mib

mib refmib

mib

mib logfile

mib

mib more
mib recurse
mib nrecurse
mib
showfieldnames=always

mib
mib
mib

Y
Y
Y

N
N
N

N
N
N

Y
Y
Y

N
N
N

N
N
N

N
N
N

N
N
N

?
?
?

Write to a field in the MIB.


List tables in the MIB.
Show MIB patch information.
Show types of a given table, subfield or field in the MIB.
Show the size of a given table,
sub-field or field in the MIB
Show offsets for a given table,
sub-field or field in the MIB
Shows padding for a given table,
sub-field or field in the MIB
Show the differences in tables
between two MIBs
Change the MIB file used for
reading/writing.
Change the reference MIB file
used for comparisons.
Change the log file used to log
changes made to the MIB.
Change the number of lines output
before asking for more.
Read MIB tables recusively.
Do not read MIB tables recusively

mib

Always show field names.

mib
showfieldnames=recurse mib

mib arraysofchar=str

mib

mib arraysofchar=int
mib
arraysofsignedchar=str
mib
arraysofsignedchar=int
mib
arraysofunsignedchar=st

mib

mib

mib

mib

mib enumvalues=str

mib

Only show field names when


reading MIB tables recusively
Format arrays of characters as
strings.
Format arrays of characters as
integers.
Format arrays of signed characters
as strings.
Format arrays of signed characters
as integers.
Format arrays of unsigned
characters as strings.
Format enumerated values as
strings

mib enumvalues=int

mib

Format enumerated values as


integers.

mib stringvalues=raw

mib

Display strings in raw format.

Tool

Description

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 281/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

mib stringvalues=cooked
mib endofstring=null
mib endofstring=none
mib debug

mib
mib
mib
mib

Y
N
N
Y

N
N
N
N

N
N
N
N

Y
Y
Y
Y

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

?
?
?
?

mib range
mib
arraysofunsignedchar=int
ape assoc
ape rout
ape trsp
ape fich
ape admin
hstca version

mib

mib
ape
ape
ape
ape
ape
hstca

N
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N

N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N

N
N
N
N
N
N
N

N
N
N
N
N
N
N

N
N
N
N
N
N
N

?
?
?
?
?
?
?

hstca info

hstca

hstca list

hstca

hstca file

hstca

hstca resize

hstca

hstca recreate_one
hstca recreate_all
hstca unsuspend
hstca context
hstcom

hstca
hstca
hstca
hstca
hstcom

N
N
Y
Y
Y

N
N
N
N
N

N
N
N
N
N

Y
Y
Y
Y
Y

N
N
N
N
N

N
N
N
N
N

N
N
N
N
N

N
N
N
N
Y

?
?
?
?
?

hstla dump
hstla clear
hstla collect
hstla format
msg version
msg lwp
msg lwg
msg fullmesh
msg supervision
msg counters
msg omu
msg sciihm

hstla
hstla
hstla
hstla
msg
msg
msg
msg
msg
msg
msg
msg

Y
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
N

N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N

?
?
?
?
?
?
?
?
?
?
?
?

Tool

Description

Display strings in cooked format.


Use null for end of string.
Do not use null for end of string
Toggle debug mode.
Show value ranges for a given
table, sub-field or field in the MIB.
Format arrays of unsigned
characters as integers.
Disp Assoc class
Display Rout class
Display Trsp clas
Display Fich class
Display admn class
Give the current software version.
Return the state of Histo CA and
the files size
List all non-empty files and their
occupation rat
Return the occupation rate for the
specified fil
Change files size. Warning: the
files are deleted
Delete and recreate a specified
file.
Delete and recreate all files
Unsuspend all suspended files
Dump the internal contexts
Dump hstcom name
Dump PMDZ
{[All/Header/Data]/[Raw]
{[bank]/[offset size]}}
Clear PMDZ {bank}
Print collection
Print formated record [bank]
Show messaging version
Dump the Messaging LWP table
Dump the Messaging LWG table
Dump the fullmesh table
Show Messaging tasks status
Dump Messaging counters
Show OMU state
Msg SCI IHM

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 282/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

msg traffic
msgadm
cp consistency
cp info

msg
msgadm
cp
cp

N
Y
Y
Y

N
N
N
N

N
N
N
N

Y
Y
Y
Y

N
N
N
N

N
N
N
N

N
N
N
N

N
N
Y
Y

?
?
?
?

cpTable
ddrca help
ddrca displayhistory

cpTable
ddrca
ddrca

Y
Y
Y

N
N
N

N
N
N

Y
Y
Y

N
N
N

N
N
N

N
N
N

N
N
N

?
?
?

ddrca displayarb

ddrca

Tool

swbDeb
ft admin
ft mib
ft lwg
ft action
lb admin
lb pde
lb ctx
lb swb
lb tmu
lb omu
lb duplex

swbDeb
ft
ft
ft
ft
lb
lb
lb
lb
lb
lb
lb

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N

?
?
?
?
?
?
?
?
?
?
?
?

sm_external_supervision sm

sm sm_launcher
swb_ca serverstate

sm
swb_ca

N
Y

N
N

N
N

Y
Y

N
N

N
N

N
N

N
N

?
?

swb_ca context
swb_ca ftinfo
swb_ca handlelist

swb_ca
swb_ca
swb_ca

Y
Y
Y

N
N
N

N
N
N

Y
Y
Y

N
N
N

N
N
N

N
N
N

N
N
N

?
?
?

swb_ca sampling
swb_la
swb_ma serverstate

swb_ca
swb_la
swb_ma

Y
Y
Y

N
N
N

N
N
N

Y
Y
Y

N
N
N

N
N
N

N
N
N

N
Y
Y

?
?
?

swb_ma debuginfo
swb_ma msgidmap

swb_ma
swb_ma

Y
Y

N
N

N
N

Y
Y

N
N

N
N

N
N

Y
Y

?
?

Description

Traffic tool IHM


Show msgadm boardtb
display CP Consistency data
display CP/LWP/Creator data
Display state of all the
CoreProcesses running in the
system (CPs running on both
OMUs and all active TMUs)
Help about DDR_CA CI Manage
Displays the history even
Displays the Agent Registration
Bas
Display information about the
software bus subjects and clients
registered with software bus.
display ftcaAdmin data
display ftcaMib data
display ftcaLwgEntry data
display ftcaConsistency dat
display lbAdmin data
display PDE data
display execution context data
display lbSwb data
display lbTmuState data
display lbOmuState data
display lbDuplexBind data
Display information about the
modules present in the Cnode
(OMUs and TMUs)
Manipulation of SM process
groups.
print the state of swbserver
print the state of swbCa context
map
print the FT info of swbCa
print the clients hdl list of swbCa
print the global state of ctxt (20
sec sampling
swb_la debug info
print the state of swbserver
print the specific swb_ma debug
info
print the swb ma message id map

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 283/300

Tool

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

cpm_global help
cpm_global fsmState
cpm_global fsmHisto
cpm_global
fsmSavedEvents
cpm_global dump
cpm_global in
cpm_global reset
cpm_global duplex
cpm_global mib
cpm_global history
cpm_global statistics
cpm_iu help
cpm_iu dump
cpm_iu class
cpm_iu duplex
cpm_iu data
cpm_iu fsmState
cpm_iu fsmHisto
cpm_iu
fsmSavedEvents
cpm_iu globalHistory
cpm_iu history

cpm_global
cpm_global
cpm_global

?
?
?

N
N
N

N
N
N

Y
Y
Y

N
N
N

N
N
N

N
N
N

N
N
N

?
?
?

Help about cpm_global


Display current state
Display historic of states

cpm_global
cpm_global
cpm_global
cpm_global
cpm_global
cpm_global
cpm_global
cpm_global
cpm_iu
cpm_iu
cpm_iu
cpm_iu
cpm_iu
cpm_iu
cpm_iu

?
?
?
?
?
?
?
?
?
?
?
?
?
?
?

N
N
N
N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N
N
N
N

?
?
?
?
?
?
?
?
?
?
?
?
?
?
?

Display event save


Dump Global Context
Dump IN Context
Dump Reset Context
Dump OMU Duplex Context
Display mib info
Dump event history
Display statistics
Help about cpm_iu CI Manager
Dump Domain Context in hex
Print Class Context infos
Dump OMU Duplex Context
Print Domain Context infos
Display current state
Display historic of states

cpm_iu
cpm_iu
cpm_iu

?
?
?

N
N
N

N
N
N

Y
Y
Y

N
N
N

N
N
N

N
N
N

N
N
N

?
?
?

bsm mon
bsm om
bsm ov

bsm
bsm
bsm

Y
Y
Y

N
N
N

N
N
N

Y
Y
Y

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

bsm cpu

bsm

bsm mem
bsnap info
bsnap run
bsnap runonly

bsm
bsanp
bsanp
bsanp

N
Y
Y
Y

N
N
N
N

N
N
N
N

Y
Y
Y
Y

N
N
N
N

N
N
N
N

N
N
N
N

Y
Y
Y
Y

?
?
?
?

bsnap runsuffix
bsnap settimeout
bsnap loadbuildref
bsnap
EnableAppSnap
bos_suicide
bsem dump
bsem date

bsanp
bsanp
bsanp

Y
Y
Y

N
N
N

N
N
N

Y
Y
Y

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

bsanp
bos_suicide
bsem
bsem

Y
N
Y
Y

N
N
N
N

N
N
N
N

Y
Y
Y
Y

N
N
N
N

N
N
N
N

N
N
N
N

Y
Y
Y
Y

?
?
?
?

Display event save


Display the global history
Display domain history
Dump current values of monitored
resources
Dump Operations Measures
Dump overload information
Load the CPU with the given %
[0;100]
Load the MEM with the given %
[0;100]
Display info
Run a snapshot
Run a snapshot for only the trigger
Run a snapshot with trigger & file
extension
Set the defense timeout value
Set the loadbuildref informations
Enable/Disable App generated
Snapshot
Reset AP
Dump the table
Set on/off the date mode

Description

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 284/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

bsem validate
dly table
dly armed
dly om
dly ovl
dly info
dly valid
dly time
ipc dump
ipc all
ipc list

bsem
dly
dly
dly
dly
dly
dly
dly
ipc
ipc
ipc

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

?
?
?
?
?
?
?
?
?
?
?

ipc sor
ipc ov
ipc dbl
ipc trigger
ipc count
ipc info

ipc
ipc
ipc
ipc
ipc
ipc

Y
Y
Y
Y
Y
Y

N
N
N
N
N
N

N
N
N
N
N
N

Y
Y
Y
Y
Y
Y

N
N
N
N
N
N

N
N
N
N
N
N

N
N
N
N
N
N

Y
Y
Y
Y
Y
Y

?
?
?
?
?
?

ipc bsnapconfig
mtx dump
mtx date
mtx validate
bmon start
bmon stop
bmon last
bmon h1

ipc
mtx
mtx
mtx
bmon
bmon
bmon
bmon

Y
Y
Y
Y
N
N
N
N

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y

?
?
?
?
?
?
?
?

bmon h2
bexc list
bexc which

bmon
bexc
bexc

N
Y
Y

N
N
N

N
N
N

Y
Y
Y

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

bexc dump

bexc

bexc clear

bexc

bexc freeze
bjob dump
bjob jobs
bjob validate
bostr events

bexc
bjob
bjob
bjob
bostr

N
Y
Y
Y
N

N
N
N
N
N

N
N
N
N
N

Y
Y
Y
Y
Y

N
N
N
N
N

N
N
N
N
N

N
N
N
N
N

Y
Y
Y
Y
Y

?
?
?
?
?

bostr call

bostr

Tool

Description

Validate the internal data


Dump specified or all delays
Dump the armed delays
Dump Operations Measures
Dump delays consumption
Dump delay characteristics
Validate the table
Absolute time
Dump given msgQueue (sem: -s)
Dump all msgQueues (sem: -s)
List all messages in a msgQueue
List all msgQueues sorted by msg nb
or size
Overload/histo/trash information
Overload double list
Set/Display user actions
Clear debug counters
Internal information
Set up bsnap to dump top loaded
msgQ
Dump the table
Set on/off the date mode
Validate the internal data
Start the monitoring
Stop the monitoring
Dump information on last second
Dump global information on last minute
Dump detailed information on last
minute
List the unfreezable tasks
Give the task which freezed the board
Display the exception parameters if
any
Clear the dedicated to exceptions
PMDZ
Freeze the board. nosnapshot to avoid
a snapshot
Dump the table of queues
Dump the jobs of a queue
Validate the internal data
Show/Set/Add(-a)/Delete(-d) events
Set Number [nb] of stack calls,
0=>none

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 285/300

CP

PMCM

OMU

NI

RAB

PC

bostr data
bostr verbose
bostr start
bostr stop
bostr clear
bostr report
bostr info
bostr backup
bostr load
bostr example
bostr calibrate
bthread dump
bthread purge
bthread specific
bthread validate
btpt
chro
debtr dump
debtr clear
dym dblock
dym lpart
dym lblock
dym om
dym validate
dym snapmsg_set

bostr
bostr
bostr
bostr
bostr
bostr
bostr
bostr
bostr
bostr
bostr
bthread
bthread
bthread
bthread
btpt
chro
debtr
debtr
dym
dym
dym
dym
dym
dym

N
N
N
N
N
Y
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
?
Y
N
Y
Y
Y
Y
Y
N

N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?

dym snapmsg_reset
dym load_part
ov board
ov thresh
ov module
pml archi
pml dump
pml clear
pml info
prcm dump
prcm validate

dym
dym
ov
ov
ov
pml
pml
pml
pml
prcm
prcm

N
N
Y
Y
Y
Y
Y
N
Y
Y
Y

N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

?
?
?
?
?
?
?
?
?
?
?

rid dump

rid

rid display
shm

rid
shm

Y
?

N
N

N
N

Y
Y

N
N

N
N

N
N

Y
Y

?
?

Tool

TMU

Component

Safe

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

Description

Set size [sz] of data dumps, 0=>none


Set size [sz] of data dumps, 0=>none
Start tracing [size] bytes (-s => stop)
Stop tracing
Clear all resources
Stop and Print the report ([nb] lines)
Print some info
Stop and Backup the report [file]
Load a report from [file]
A little example of use
Calibation test
Dump the thread table
Garbage collect of the TCB table
Dump the specific key table
Validate the thread data structures
Dump btpt info
Dump chro info
Display DEBTR pmdz data, if any
Clear the DEBTR pmdz
Dump a block
List all the partitions
List a set of blocks
Display OM for one or all partitions
Check partitions'coherency
Set a full snapshot of the messages
Reset the full snapshot of the
messages
Stop/Start/Change load value
Print local board's OvLevel
Print local board threshold levels
Print local module's OvLevel
Display the PMDZ architecture
Dump the specified PMDZ
Clear the specified PMDZ
Dump pmlog internal characteristics
Dump the table
Validate the table
Dump sw sub-system, sw elt and idx
for one rid value
Display rid for idx=0 and idx=10 of
every sw elt
Dump shm

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 286/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

var dump
var validate
wdog info
wdog disable
wdog enable
apptr getlevel
apptr getstate
apptr reset
apptr setlevel

var
var
wdog
wdog
wdog
apptr
apptr
apptr
apptr

?
?
Y
N
N
Y
Y
N
N

N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y

?
?
?
?
?
?
?
?
?

apptr showcode

apptr

apptr showname
apptr showlevel
apptr showstate
apptr enablecomment
apptr disablecomment
apptr
getcommentstate
apptr showverbosity
apptr getverbosity

apptr
apptr
apptr
apptr
apptr

Y
Y
Y
N
N

N
N
N
N
N

N
N
N
N
N

Y
Y
Y
Y
Y

N
N
N
N
N

N
N
N
N
N

N
N
N
N
N

Y
Y
Y
Y
Y

?
?
?
?
?

apptr
apptr
apptr

Y
Y
Y

N
N
N

N
N
N

Y
Y
Y

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

apptr getdeffmt
apptr setverbosity
apptr setdeffmt

apptr
apptr
apptr

N
N
N

N
N
N

N
N
N

Y
Y
Y

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

apptr showdeffmt
apptr gettracetotal
apptr resettracetotal
apptr
gettracetimezone
apptr
settracetimezone
apptr settraceprio

apptr
apptr
apptr

Y
Y
N

N
N
N

N
N
N

Y
Y
Y

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

apptr

apptr
apptr

N
N

N
N

N
N

Y
Y

N
N

N
N

N
N

Y
Y

?
?

fcirc getWBT
fcirc setWBT
fcirc dump
fms clear
fms display
vxwio
os unprotect
os e

fcirc
fcirc
fcirc
fms
fms
vxwio
os
os

Y
N
Y
Y
Y
?
N
N

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y

?
?
?
?
?
?
?
?

Tool

Description

Dump the table


Validate the table
Display info
Disable watchdog expiration
Enable watchdog expiration
show current trace level
show current trace redirection
reset trace parameters to default
change trace level
show sub-system / software element
codes
show sub-system / software element
names
show possible level values
show possible state values
turn on the comment sending by level
turn off the comment sending by level
show current comment state
show possible verbosity values
show current trace verbosity
show current default format for
display
change trace verbosity
change default format for display
show allowed default format for
display
show current processed trace number
reset the processed trace number
show the timezone of the traces
set the timezone of the traces LOCAL
or UTC
set the Priority of the local trace Task
show current White Box Test flag
value
change White Box Test flag value
dump file descriptor table
Clear metrology
Display metrology
BaseOS VxWorks IO
Enables the unprotect mode
Event breakpoint

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 287/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

os i
os ti
os tt
os checkStac
os b
os bh
os bd
os bdall

os
os
os
os
os
os
os
os

Y
Y
N
Y
N
N
N
N

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y

?
?
?
?
?
?
?
?

os memShow

os

os semShow

os

os show
os version

os
os

Y
Y

N
N

N
N

Y
Y

N
N

N
N

N
N

Y
Y

?
?

os taskName
os d
os m
os c
os cret
os s
os so
os sp
os td
os ts
os tr
os taskSpawn
os l
os printErrno
os moduleShow
os envShow
os putenv

os
os
os
os
os
os
os
os
os
os
os
os
os
os
os
os
os

Y
Y
N
N
N
N
N
N
N
N
N
N
N
Y
Y
Y
N

N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?

os2 routeShow

os2

os2 ifShow
os2 iosDevShow

os2
os2

Y
Y

N
N

N
N

Y
Y

N
N

N
N

N
N

Y
Y

?
?

os2 iosFdShow
os2 ioGlobalStdSet
os2 ioGlobalStdGet

os2
os2
os2

Y
N
Y

N
N
N

N
N
N

Y
Y
Y

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

Tool

Description

Summary of tasks' TCBs


Complete info on TCB for task
Do stack trace on task
Print task's stack usage
Display/Set breakpoint(s)
Set hardware breakpoint
Delete breakpoint
Delete all breakpoints
Show system memory partition
blocks
Show information about a
semaphore
Show information on a specified
object
Print VxWorks version information
Get the name associated with a
task ID
Display memory
Modify memory
Continue from breakpoint
Continue to subroutine return
Single step
Single step/step over subroutine
Spawn a task with default param.
Delete a task
Suspend a task
Resume a task
Spawn a task
Disassemble instructions
Print the name of an error status
Show dynamically loaded modules
Show global environment variables
Set a global environment variable
Display host and network routing
tables
Display the attached network
interfaces
Display list of devices in the system
Display file descriptor names in the
system
Set the file descriptor for std i/o/err
Get the file descriptor for std i/o/err

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 288/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

os2 logFdSet

os2

os2 ping
os2 hostShow
os2
netStackDataPoolShow
os2
netStackSysPoolShow
os2 inetstatShow
os2 tcpstatShow
os2 udpstatShow
os2 ipstatShow
os2 icmpstatShow
os2 arptabShow
os2 mbufShow

os2
os2

Y
Y

N
N

N
N

Y
Y

N
N

N
N

N
N

Y
Y

?
?

os2

os2
os2
os2
os2
os2
os2
os2
os2

Y
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y

?
?
?
?
?
?
?
?

os2 mRouteShow

os2

cnode_assert help
cnode_assert show
cnode_assert precond
cnode_assert postcond
cnode_assert ptrcheck

cnode_assert
cnode_assert
cnode_assert
cnode_assert
cnode_assert

N
N
N
N
N

N
N
N
N
N

N
N
N
N
N

Y
Y
Y
Y
Y

N
N
N
N
N

N
N
N
N
N

N
N
N
N
N

Y
Y
Y
Y
Y

?
?
?
?
?

cnode_assert help
cnode_assert show
cnode_assert precond
cnode_assert postcond
cnode_assert ptrcheck

cnode_assert
cnode_assert
cnode_assert
cnode_assert
cnode_assert

N
N
N
N
N

N
N
N
N
N

N
N
N
N
N

Y
Y
Y
Y
Y

N
N
N
N
N

N
N
N
N
N

N
N
N
N
N

Y
Y
Y
Y
Y

?
?
?
?
?

lcsproxy help
lcsproxy lsctx
ConfAlarm Help
ConfAlarm Text
ConfAlarm Credit
ConfAlarm Test
ConfAlarm Show
sig_adm help

lcsproxy
lcsproxy
ConfAlarm
ConfAlarm
ConfAlarm
ConfAlarm
ConfAlarm
sig_adm

Y
Y
Y
Y
Y
N
N
?

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y

?
?
?
?
?
?
?
?

sig_adm iubasu

sig_adm

sig_adm iubsscop

sig_adm

Tool

Description

Set the logging facility output file


descriptor
Test that a remote host is
reachable
Display the host table
Print the state of network data pool
Print the state of network system
pool
Show all Internet protocol sockets
Show statistics for TCP
Show statistics for UDP
Show statistics for IP
Show statistics for ICMP
Show a list of known ARP entries
Show mbuf statistics
Display host and network multicast
routing tables
Help about cnode_assert
commands
Display current assert settings
Sets pre-condition asserts
Sets post-condition asserts
Sets pointer checking asserts
Help about cnode_assert
commands
Display current assert settings
Sets pre-condition asserts
Sets post-condition asserts
Sets pointer checking asserts
Prints help about available
commands
Prints LCSProxy context
Help about ConfAlarm
Set the Alarm text String
Set the Alarm Limit Count
Send an Alarm
Display settings/stats
Display the help of sig_adm utilities
Query information on Iub ASU
interface
Query SSCOP links on Iub
Interface

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 289/300

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

sig_adm
iubsscopstat
sig_adm
iubsscopdebug
sig_adm iubping
sig_adm
trillium_mem
sig_adm mgt

sig_adm

sig_adm
sig_adm

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

sig_adm
sig_adm

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

sig_adm sigconf

sig_adm

sig_adm sapconf

sig_adm

sig_adm speconf

sig_adm

sig_adm cntrlconf

sig_adm

sig_adm initconf
iu_cnxless help
iu_cnxless fsmState
iu_cnxless fsmHisto
iu_cnxless
fsmSavedEvents
iu_cnxless param
iu_cnxless mib
iu_cnxless dump
iu_cnxless history
iu_cnxless statistics
cn_register
rnccom help
rnccom cladp
rnccom clads
rnccom celldpref
rnccom celliref

sig_adm
iu_cnxless
iu_cnxless
iu_cnxless

?
?
?
?

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

Y
Y
Y
Y

?
?
?
?

iu_cnxless
iu_cnxless
iu_cnxless
iu_cnxless
iu_cnxless
iu_cnxless
cn_register
rnccom
rnccom
rnccom
rnccom
rnccom

?
?
?
?
?
?
?
?
?
?
?
?

N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

?
?
?
?
?
?
?
?
?
?
?
?

rnccom celldp
rnccom
neighfdddpref

rnccom

rnccom

rnccom neighfdddp
rnccom
neighgsmdpref

rnccom

Lists internal neighfdd references


Dumps one instance of table
rnc_com_i200

rnccom

Lists internal rnc references

Tool

Component

Description

Query statistics information on a


SSCOP link
Activate/Desactivate Trillium debug
trace on SSCOP
Host Testing: IUB Signaling
Query Trillium memory usage
Host Testing: Management of sig_adm
Host Testing: General configuration of
signalling stack
Host Testing: Configuration of SAP in
signalling stack
Host Testing: Configuration of protocolspecific object in signalling stack
Host Testing: Configuration for
Controls & actions
Host Testing: Initializations of the
ASU/ALU interface
Help about iu_cnxless CI Manager
Display current FSM state
Display historic of FSM states
Display FSM saved events
Display General Parameters Info
Display mib info
Dump iu_cnxless context in hex
Display global history events
Display statistics
Displays available commands
Dumps class dp information
Dumps class ds information
Lists internal references
Retrieves the internal cell references
Dumps one instance of table
rnc_com_i100

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 290/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

rnccom neighrncdp
rnccom listucid
rnccom getlocinfo
rnccom
readiurcellinfo
rnccom
readneighfdd
rnccom
readrrmparam

rnccom
rnccom
rnccom

?
?
?

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

rnccom

rnccom

rnccom

rnccom readiurobs

rnccom

Tool

rnccom
iurfddcellmap

rnccom

rnccom

rnccom

rnccom size
rnccom
initrnccomaut

rnccom

rnccom

rnccom statistics

rnccom

rnccom bsnapshot
upos help

rnccom
upos

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

upos debug
upos status
upos start
upos stop

upos
upos
upos
upos

?
?
?
?

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

Y
Y
Y
Y

?
?
?
?

upos annotate
upos client
upos procedures

upos
upos
upos

?
?
?

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

upos map
upos filters
upos create_filter

upos
upos
upos

?
?
?

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

upos replace_filter

upos

rnccom
iurgsmcellmap
rnccom
readneighgsm

Description

Dumps one instance of table


rnc_com_i500
Lists managed Utran Cell Id
Retrieves location information
Retrieves information on a FDD cell
Retrieves information on a neigh FDD
cell
Retrieves RMM information on a FDD
cell
Retrieves information used by IUR for
OBS counters
Dumps the dynamic map {UcID}->{contextId,activeCtr,neighbourCtr} for
IUR FDD cells
Dumps the dynamic map {cgi}->{contextId,neighbourCtr} for IUR GSM
cells
Retrieves GSM neighbourhood
information of a FDD cell
Gives the memory allocated for Rnccom
process
Displays init rnccom automaton
Context Manager and CNU Static Map
statistics, GCPP timer statistics
Causes rnccom to perform bsnapshot
context dump
Help with the UPOS Trace Tool
Debugging information for the UPOS
Trace Tool
Current status
Start/activate UPOS Tracing
Stop/deactivate UPOS Tracing
Add an annotation (free text) to the trace
file
Configure UPOS client
Lists available UPOS Trace procedure
Shows the filter and output selector
mapped to each procedure
Lists available UPOS Trace filters
Create a new filter
Replace all references to a filter with
another

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 291/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

upos destroy_filters

upos

upos config_filter

upos

upos use_filter

upos

upos associate_imsi
upos is
upos create_is

upos
upos
upos

?
?
?

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

upos replace_is

upos

upos destroy_is

upos

upos config_is

upos

upos use_is
upos os
upos create_os

upos
upos
upos

?
?
?

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

upos replace_os

upos

upos destroy_os

upos

upos config_os

upos

upos use_os
iupccom help
iupccom autState
iupccom autHisto
iupccom autSavEvt
iupccom mib
iupccom pcap
iupccom timers
iupccom histo
rrmded help
rrmded estab

upos
iupccom
iupccom
iupccom
iupccom
iupccom
iupccom
iupccom
iupccom
rrmded
rrmded

?
?
?
?
?
?
?
?
?
?
?

N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

?
?
?
?
?
?
?
?
?
?
?

rrmded ulas
rrmded dlas

rrmded
rrmded

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

rrmded ulrbset

rrmded

Tool

Description

Destroys filters created with the


create_filter command
Configure or re-configure an existing
filter
Use a filter for the procedures
specified
Associate an IMSI with the trace key
specified
Lists available input selectors
Create a new input selector
Replace all references to an input
selector with another
Destroy input selectors created with
the create_is command
Configure or re-configure an existing
input selector
Use an input selector for the
procedures specified
Lists available output selectors
Create a new output selector
Replace all references to an output
selector with another
Destroy output selectors created with
the create_os command
Configure or re-configure an existing
output selector
Use an output selector for the
procedures specified
Help about iupccom CI Manager
Display automaton current state
Display automaton state history
Display automaton saved events
Display mib info
Display pcap context info
Display timers info
Display events history
Help about RRM_DED CI Manager
get the list of Establishment cause
get UpLink Access Stratum
information
get DownLink Access Stratum info.
get UpLink RbSet Configuration
information

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 292/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

rrmded dlrbset

rrmded

rrmded ulscn

rrmded

rrmded ispanaue

rrmded

rrmded measconf
rrmded mobconf
rrmded mobcounters

rrmded
rrmded
rrmded

?
?
?

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

rrmded resetmobcounter

rrmded

rrmded alwayson

rrmded

rrmded cmode

rrmded

rrmded checkcmode

rrmded

rrmded difStag

rrmded

rrmded listLwp
rrmded IRM

rrmded
rrmded

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

rrmded relocation

rrmded

rrmded gethisto
rrmded disphisto
rrmded selhisto

rrmded
rrmded
rrmded

?
?
?

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

rrmded acthisto

rrmded

rrmded deshisto

rrmded

rrmded clrhisto

rrmded

rrmded getrncrrmhisto

rrmded

rrmded disprncrrmhisto

rrmded

rrmded actrncrrmhisto

rrmded

rrmded desrncrrmhisto

rrmded

rrmded clrrncrrmhisto

rrmded

Tool

Description

get DownLink RbSet


configuration information
get the min/current/max
values of the Uplink
Scrambling Code number
get the value of the flag
isPanasonicUe
get the measurement
configurations
get the Mobility configuration
get the Mobility counters
reset the Mobility counters
get the always on
configuration
get the compressed mode
configuration
check the compressed mode
configuration
get the Diff Serv Tag
parameters
list the ue_call core process
(used in rncrrm)
list the IRM parameters
list the parameters for
incoming relocation
get Uerrm decision history
and print the last elements
display Uerrm decision history
select Uerrm decision history
activate Uerrm decision
history service
de-activate Uerrm decision
history service
clear the Uerrm decision
history buffers
get Rncrrm decision history
and print the last elements
display Rncrrm decision
history
activate Rncrrm decision
history service
de-activate Rncrrm decision
history service
clear the Rncrrm decision
history buffers

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 293/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

rrmded cacconf

rrmded

rrmded rncrrmov

rrmded

rrmded agpsconf

rrmded

rrmded agpsstatic

rrmded

rrmded lcsconf
rrmded doffrecord

rrmded
rrmded

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

rrmded powerbalancing

rrmded

rrmded irmsched

rrmded

rrmded rrccnxsetupconf

rrmded

rrmded uecapachkinrabmatch rrmded

rrmded rbadapt

rrmded

rrmded Aal2BearerReneg

rrmded

rrmded
CModeActOverMultiVendorIur rrmded
rrmded hsdpaconf
rrmded

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

rrmded radioaccessservice
rrmded event1AWparam
rrmded event1AHyst
ue_rrc clads

rrmded
rrmded
rrmded
ue_rrc

?
?
?
?

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

Y
Y
Y
Y

?
?
?
?

ue_rrc cladp

ue_rrc

ue_rrc lscp
ue_rrc setcp
ue_rrc clactx

ue_rrc
ue_rrc
ue_rrc

?
?
?

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

ue_rrc lscallctxid

ue_rrc

ue_rrc printctxstat

ue_rrc

ue_rrc cnaut
ue_rrc instctx

ue_rrc
ue_rrc

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

Tool

Description

get the CAC configurations


get the RncRrm Context for
overload Cac
get the AGPS configuration
parameters
get the AGPS static
configuration
display the LCS
configurations
display DOFF record
display the Power Balancing
configurations
display the IRM Scheduling
configurations
display the Extended Rrc Cnx
Setup Params
display the Flags for the Ue
Capa Checks in Rab
Matching
display the Rb Adaptation
configuration
get parameter for
Aal2BearerRenegotiation
get parameter for
CModeActOverMultiVendorIur
display HSDPA config
display radio access service
parameters
set wParam of event 1A
set hysteresis of event 1A
Dumps ue_rrc static data
Dumps ue_rrc permanent
data
Lists the core process created
on a TMU
Sets the current core process
Dumps ue_rrc class context
Lists ue_rrc ctxId and
traceKey of all established
calls
Displays statistic information
about pools and contexts
Displays ue_rrc cnaut
transition of a call
Dumps ue_rrc inst ctx

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 294/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

ue_rrc integrityinfo

ue_rrc

ue_rrc help
ue_call clads
ue_call cladp

ue_rrc
ue_call
ue_call

?
?
?

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

ue_call lscp
ue_call setcp
ue_call clactx

ue_call
ue_call
ue_call

?
?
?

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

ue_call printctxstat

ue_call

ue_call lscallctxid

ue_call

ue_call cnaut
ue_call callstatus

ue_call
ue_call

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

ue_call listcndomain

ue_call

ue_call rabinfo
ue_call rlinfo

ue_call
ue_call

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

ue_call locationinfo
ue_call listactivset

ue_call
ue_call

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

ue_call measstate
ue_call uecapabilities

ue_call
ue_call

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

ue_call cmodestate

ue_call

ue_call
rateadaptationinfo

ue_call

ue_call

ue_call

ue_call

ue_call
ue_call

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

ue_call

Tool

ue_call irmschedupg
ue_call
internal_counters
ue_call
irmscheddowng
ue_call
dlAsConfIdInstr
ue_call histoCall
ue_call listoldhistocall

Description

Displays integrity information of a call


Displays information about all the
commands available in ue_rrc
Dumps ue_call static data
Dumps ue_call permanent data
Lists the core process created on a
TMU
Sets the current core process
Dumps ue_call class context
Displays statistic information about
pools and contexts
Lists ue_call ctxId, traceKey and
IMSI of all established calls
Displays ue_call cnaut transition of a
call
Displays the status of a call
Displays the established domains of
a call
Displays rab informations (id,
integrity, ciphering, ...) of a call
Displays rl informations of a call
Displays location informations of a
call
Displays active set cells of a call
Displays measurement states of a
call
Displays UE capabilities of a call
Displays compressed mode states of
a call
Displays rate adaptation information
(alwaysOn, irm scheduling, ...) of a
call
Displays irm scheduling upgrade
information of a call
Display Call Internal Counters
Displays irm scheduling donwgrade
information of a call
Displays dlAsConfId Q01100563
instrumentation for all or given call(s)
Displays historic of a call
Displays the list of old calls
traceKeys

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 295/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

ue_call oldhistocall
ue_call lastdec

ue_call
ue_call

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

ue_call help

ue_call

ue_call listalluectxinfo
ue_call
srlrDeltaMsgSize

ue_call

ue_call

ue_call resetSrlrSize

ue_call

ue_call rlRecoved
callcleanup help
callcleanup
SetshortSanityTrigger
callcleanup
SetlongSanityTrigger
callcleanup
SetoverallTrigger

ue_call
callcleanup

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

callcleanup

callcleanup

callcleanup

Tool

callcleanup
DisplaySanityCounter
callcleanup
DisplaySanityTrigger
iu_call help
iu_call tid
iu_call mib
iu_call param
iu_call reset
iu_call inacc
iu_call qaal2
iu_call fsmState
iu_call fsmHisto
iu_call
fsmSavedEvents
iu_call lscallctxid
iu_call callctxid
iu_call callctx
iu_call lsrabctxid
iu_call rabctx

Description

Displays historic of a old call


(referenced by a traceKey)
Displays the last decisions taken
Displays information about all the
commands available in ue_call
Display relevant call context
information for all calls of a CP_UE
Displays info about srlr size msg
(differences and static datas)
reset fields ueCallSrlrDeltaSize of
ue_call class ctx
Display the number of Rl been
recovered after RlFailed
Displays available commands
Set the limit number of call cleanup
allowed in short period
Set the limit number of call cleanup
allowed in long period
Set the overal max number of call
cleanup

callcleanup

callcleanup
iu_call
iu_call
iu_call
iu_call
iu_call
iu_call
iu_call
iu_call
iu_call

?
?
?
?
?
?
?
?
?
?

N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N

N
N
N
N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y
Y
Y
Y

?
?
?
?
?
?
?
?
?
?

Display shortSanityCounter,
longSanityCounter and
overallCounter of call cleanup
Display shortSanityTrigger,
longSanityTrigger and overallTrigger
of call cleanup
Help about iu_call CI Manager
Sets iu_call Task Id/Process Id
Display mib info
Display General Parameters Info
Display Reset Info
Display IN Access Info
Display QAAL2 Info
Display Current State
Display States History

iu_call
iu_call
iu_call
iu_call
iu_call
iu_call

?
?
?
?
?
?

N
N
N
N
N
N

N
N
N
N
N
N

N
N
N
N
N
N

N
N
N
N
N
N

N
N
N
N
N
N

N
N
N
N
N
N

Y
Y
Y
Y
Y
Y

?
?
?
?
?
?

Display Saved Events


Display CtxId & TraceKey List
Display CtxId for TraceKey
Display Context Info
Display RAB CtxId list
Display IuRab Context Info

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 296/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

iu_call dump
iu_call globalHistory
iu_call history
iu_call statistics
iu_call lstid
iurcallinit help

iu_call
iu_call
iu_call
iu_call
iu_call
iurcallinit

?
?
?
?
?
?

N
N
N
N
N
N

N
N
N
N
N
N

N
N
N
N
N
N

N
N
N
N
N
N

N
N
N
N
N
N

N
N
N
N
N
N

Y
Y
Y
Y
Y
Y

?
?
?
?
?
?

iurcallinit lscp
iurcallinit setcp
iurcallinit clads
iurcallinit cladp
iurcallinit neighdp
iurcallinit neighrncinfo
iurcallinit clactx

iurcallinit
iurcallinit
iurcallinit
iurcallinit
iurcallinit
iurcallinit
iurcallinit

?
?
?
?
?
?
?

N
N
N
N
N
N
N

N
N
N
N
N
N
N

N
N
N
N
N
N
N

N
N
N
N
N
N
N

N
N
N
N
N
N
N

N
N
N
N
N
N
N

Y
Y
Y
Y
Y
Y
Y

?
?
?
?
?
?
?

iurcallinit listcallctx
iurcallinit callkey
iurcallinit callid
iurcallinit ciaut

iurcallinit
iurcallinit
iurcallinit
iurcallinit

?
?
?
?

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

Y
Y
Y
Y

?
?
?
?

iurcallinit histocall

iurcallinit

iurcallinit histoglobal

iurcallinit

iurcallinit

iurcallinit

iurcallinit

iurcallinit
iurcallinit
iurcallinit
iurcallterm

?
?
?
?

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

Y
Y
Y
Y

?
?
?
?

iurcallterm
iurcallterm
iurcallterm
iurcallterm
iurcallterm

?
?
?
?
?

N
N
N
N
N

N
N
N
N
N

N
N
N
N
N

N
N
N
N
N

N
N
N
N
N

N
N
N
N
N

Y
Y
Y
Y
Y

?
?
?
?
?

Dumps the history of the core class


Dumps pools informations
display iurcall context size
Displays available commands
Lists the core processes created on a
TMU
Sets the current core process
Dumps class ds information
Dumps class dp information
Dumps class dp information

iurcallterm

Dumps neighbouring rnc information

Tool

iurcallinit
histoglobalcall
iurcallinit
histoglobalneighrnc
iurcallinit
histoneighrnc
iurcallinit
histocoreclass
iurcallinit poolstatistic
iurcallinit contextsize
iurcallterm help
iurcallterm lscp
iurcallterm setcp
iurcallterm clads
iurcallterm cladp
iurcallterm neighdp
iurcallterm
neighrncinfo

Description

Display context in hexdecimal


Display global history events
Display call history events
Display statistics
Lists iu_call Task Id(s)
Displays available commands
Lists the core processes created on a
TMU
Sets the current core process
Dumps class ds information
Dumps class dp information
Dumps class dp information
Dumps neighbouring rnc information
Dumps the ClassCtx
Lists CallCtxId and TraceKey of all
established calls
Dumps the CallCtx
Dumps the CallCtx
Displays iurCall_Init automaton
Dumps the history of the call related
to the given traceKey
Dumps the history of the call set
managed by class context
Dumps the history of the call related
to the given tracekey from class
context
Dumps the history of TEA and REA
messages for any RNC
Dumps the history of TEA and REA
messages for a given RNC

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 297/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

iurcallterm clactx

iurcallterm

iurcallterm listcallctx
iurcallterm callkey
iurcallterm callid
iurcallterm callrrm
iurcallterm ciaut

iurcallterm
iurcallterm
iurcallterm
iurcallterm
iurcallterm

?
?
?
?
?

N
N
N
N
N

N
N
N
N
N

N
N
N
N
N

N
N
N
N
N

N
N
N
N
N

N
N
N
N
N

Y
Y
Y
Y
Y

?
?
?
?
?

iurcallterm histocall

iurcallterm

iurcallterm histoglobal

iurcallterm

iurcallterm

iurcallterm

iurcallterm

iurcallterm
iurcallterm

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

iurcallterm
ddrla
ddrla
ddrla

?
Y
Y
Y

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

Y
Y
Y
Y

?
?
?
?

ddrla displayqueue
ddrla displayallimsi
ddrla displaysingleimsi
ddrla displayallcelldata
ddrla
displaysinglecelldata
cmgr help
cmgr lLwps
cmgr LwpInfo

ddrla
ddrla
ddrla
ddrla

Y
Y
Y
Y

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

Y
Y
Y
Y

?
?
?
?

ddrla
cmgr
cmgr
cmgr

Y
?
?
?

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

Y
Y
Y
Y

?
?
?
?

cmgr LwpDdSize
cmgr LwpDdDump
cmgr lLwpDP
cmgr lDpTables
cmgr DpTables
cmgr DpTable

cmgr
cmgr
cmgr
cmgr
cmgr
cmgr

?
?
?
?
?
?

N
N
N
N
N
N

N
N
N
N
N
N

N
N
N
N
N
N

N
N
N
N
N
N

N
N
N
N
N
N

N
N
N
N
N
N

Y
Y
Y
Y
Y
Y

?
?
?
?
?
?

Tool

iurcallterm
histoglobalcall
iurcallterm
histoglobalneighrnc
iurcallterm
histoneighrnc
iurcallterm
histocoreclass
iurcallterm poolstatistic
iurcallterm
sccprejected
ddrla help
ddrla displayhistory
ddrla displaydrb

Description

Dumps the ClassCtx


Lists CallCtxId and TraceKey of all
established calls
Dumps the CallCtx
Dumps the CallCtx
Dumps the CallCtx rrm params
Displays iurCall_Term automaton
Dumps the history of the call related
to the given traceKey
Dumps the history of the call set
managed by class context
Dumps the history of the call related
to the given tracekey from class
context
Dumps the history of TEA and REA
messages for any RNC
Dumps the history of TEA and REA
messages for a given RNC
Dumps the history of the core class
Dumps pools informations
Dumps total number of rejected sccp
connections
Help about DDR_LA CI Manager
Displays the history event
Displays the Data Registration Base
Displays information on update
queues
Displays all IMSI information
Displays single IMSI information
Displays all cell data information
Displays single cell data information
Help about CacheMgr CI Manager
Get the list for all LWP
Display all CacheMgr Data for Lwp
Display the Size of DD for a given
Lwp
Display the DD for a given Lwp
List DP Table names for Lwp
List all DP Tables names
Dump all DP Table
Dump info and data for DP Table

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 298/300

PMCM

OMU

NI

RAB

cmgr
cmgr
cmgr
rnccall

?
?
?
?

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

Y
Y
Y
Y

?
?
?
?

rnccall lscp
rnccall setcp
rnccall clads
rnccall cladp

rnccall
rnccall
rnccall
rnccall

?
?
?
?

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

Y
Y
Y
Y

?
?
?
?

rnccall celldpref

rnccall

rnccall celldp
rnccall neighrncdpref

rnccall
rnccall

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

rnccall neighrncdp
rnccall classcoreaut
rnccall cellaut
rnccall size

rnccall
rnccall
rnccall
rnccall

?
?
?
?

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

N
N
N
N

Y
Y
Y
Y

?
?
?
?

rnccall lsuectxid

rnccall

rnccall tracekey
rnccall uectxid
rnccall rnccallaut

rnccall
rnccall
rnccall

?
?
?

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

N
N
N

Y
Y
Y

?
?
?

rnccall lsuefachctxid

rnccall

rnccall fachtracekey
rnccall uefachctxid
rnccall
rnccallFachaut

rnccall
rnccall

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

rnccall

rnccall statistics

rnccall

rnccall histocelldch

rnccall

rnccall histocellfach

rnccall

rnccall histotracekey
rnccall bsnapshot
rnccall
bsnapshotuedch

rnccall
rnccall

?
?

N
N

N
N

N
N

N
N

N
N

N
N

Y
Y

?
?

rnccall

TMU

CP

cmgr DpSize
cmgr DpWrite
cmgr DpStat
rnccall help

Tool

PC

Component

Safe

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

Description

Dump info and data for DP Table


Dump DP Table to /tmp directory
Display the status of DP Loading
Displays available commands
Lists the core processes created on a
TMU
Sets the current core process
Dumps class ds information
Dumps class dp information
Lists internal cell references of all
created instances
Dumps one instance of table
rnc_call_i100
Lists internal neighfdd references
Dumps one instance of table
rnc_call_i200
Displays rnccall classcore automaton
Displays rnccall cell automaton
Displays contexts sizes and constants
Lists the UeCtxId and TraceKey of all
established calls
Retrieves UeCtxId of a given
TraceKey
Dumps the UeCtxId
Displays rnccall core automaton
Lists the UeFachCtxId and TraceKey
of all established calls
Retrieves UeFachCtxId of a given
TraceKey
Dumps the UeFachCtxId
Displays rnccall cell_fach automaton
Context Manager and CNU Static
Map statistics, GCPP timer statistics
Displays cell_dch global history for all
calls or for a given call
Displays cell_fach global history for
all calls or for a given call
Displays global history for the call
given by the traceKey
Performs bsnapshot context dump
Performs bsnapshot context dump for
the given UeCtxId

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 299/300

Component

Safe

CP

PMCM

OMU

NI

RAB

PC

TMU

TelCI Support

RNC & NodeB Health Check for NEV 4.2- How To

rnccall
bsnapshotuefach

rnccall

showPathTab

Tbm

showPcsPaths

Tbm

showPaths

Tbm

tbmHelp

Tbm

helpCnAccCa

Cnacc

helpCnAccLa

cnacc

Tool

Description

Performs bsnapshot context dump for


the given UeFachCtxId
Dumps out the informations about a
Path for every Path
Dumps out all the Paths on every PC
Dumps out the informations about a
Path for every Path
Dump out all the commands of Tbm
Dump out all the commands of
CnAccCa
Dump out all the commands of
CnAccLa

Z END OF DOCUMENT Y

Nortel confidential

UMT/UMT/APP/015074

03.01 / EN

Standard

19/May/2006

Page 300/300

Вам также может понравиться