Академический Документы
Профессиональный Документы
Культура Документы
2- How To
Document number:
Document issue:
Document status:
Date:
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
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
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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 4/300
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 5/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 6/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 7/300
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 8/300
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 10/300
AP0
AP1
AP2
AP3
AP4
AP5
TMU
NI
RAB
PC
OMU
2 PSFP
2 PSFP
AP0
AP1
AP2
AP3
AP4
AP5
TMU
NI
RAB
PC
OMU
TMU
NI
RAB
PC
OMU
3 PSFP
3 PSFP
AP0
AP1
AP2
AP3
AP4
AP5
TMU
RAB
RAB
PC
RAB
TMU
NI
RAB
PC
OMU
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
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
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
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
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:
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
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
===================================================
Your choice:
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 16/300
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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 17/300
instance=x
instance=0,1
instance=0,1
instance=0.1
instance=0,1
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
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
/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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 21/300
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
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
/remote
/sfs/sfs2
(shadowed)
/local2
/remote2
/sfs/CP0
/sfs/CP1
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 22/300
Cp view
External 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
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
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 24/300
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
.
4) Use 1 mode if required
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 26/300
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 28/300
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
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
229
233
0xe5
0xe9
0
1
4
5
5
5
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),
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
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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 32/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 33/300
Green Led
Status
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 34/300
MMS
Red Led
Green Led
Status
and
COMPACT
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 35/300
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 36/300
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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 38/300
: 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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 39/300
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
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
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
,
,
,
,
,
,
,
,
Active
Active
Active
Active
Active
Active
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
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
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
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
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
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
Shelf 1
Slot 1
Slot 3
Slot 4
Slot 11
Slot 12
Slot 13
Slot 14
0xed (237)
0xee (238)
0xe3 (227)
0xe4 (228)
0xeb (235)
0xec (236)
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_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_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_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
Slot 5
Slot 6
Slot 7
Slot 8
Slot 9
Slot 10
0xe7 (231)
0xe8 (232)
0xe9 (233)
omu_9_tm
172.37.2.1
172.41.2.1
0x3e5 (997)
0x3e9 (1001)
omu_9_pmc1
172.33.3.2
172.41.3.2
0x3e5 (997)
0x3e9 (1001)
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)
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
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
-
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
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
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>
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
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%
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
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
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
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
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.
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 53/300
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.
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 54/300
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
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
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
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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 57/300
0
0
0
2
0
4
0
1
0
3
0
5
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 58/300
RNC1000 (Classic)
RNC1500 (Compact)
telci
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
COMPACT
Not applicable for RNC1500.
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 59/300
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.
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
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
|
+----------------------------------------------------------------------------------+
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 61/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 62/300
Description
No colour
Card is unpowered
Solid Red
Solid green
Solid amber
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
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 64/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 65/300
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
Atmif/800 to AtmIf/807
Atmif/808
Atmif/814 and AtmIf/815
Iub
Control Node
Iu
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 67/300
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 68/300
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 70/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 71/300
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 72/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 73/300
-> 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
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
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
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
ActiveRmanCaInvokeAudit
rmanCaTool
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
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
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
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
New in V4.2
New in V4.2
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 79/300
/|
/ |
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
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
11
20
SCCPCH
8
0
2054
2
32
9
3
32
10
1
32
8
SCCPCH is operational
FACH CID
FACH CID
PCH CID
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
CCM-RTC_TOOLS/FLR>d 2 5
Display last 5 records from Ram buffer
Alarms
-------------------------------------------------------CCM_EMOAM_ALARM_MGT> F5_Alarm_Indication_Signal
49
CCM_EMOAM_ALARM_MGT> F5_Alarm_Indication_Signal
35
CCM_EMOAM_ALARM_MGT> PCM_FAILURE_CRITICAL_FAULT
CCM_EMOAM_ALARM_MGT> PCM_FAILURE_CRITICAL_FAULT
CCM_EMOAM_ALARM_MGT> PCM_FAILURE_CRITICAL_FAULT
CCM_EMOAM_ALARM_MGT> PCM_FAILURE_CRITICAL_FAULT
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 83/300
NO
NO
INVALID
FFS
Software in use.
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 84/300
to go up
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 85/300
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
PEC Code
Useful !
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 86/300
"
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)
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 87/300
:0x189D
:0x3
:0x1D8
:0x000000
:0x1D8
:0x000000
:0x0F4240
:0xEC
:0x000000
:0xEC
:0x000000
:0x0186A0
=========
: 5
: 0
: 1
: 1
: 34
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 88/300
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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 89/300
: 30
: 0
=========
: 2
: 0
: 32
: 3
: 1
: 24
: 4
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 90/300
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
20
14
3
1
2
0
0
0
0
0
20
14
3
2
3
0
0
0
0
0
20
14
3
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 91/300
[1]
[1]
[1]
[1]
[1]
[1]
:
:
:
:
:
:
Laptop
0x0a029003
0
0x00000000
0x00000000
: 0
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
[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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 93/300
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
16
PRACH
3
0
2054
10
32
11
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
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
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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 96/300
ICCM-RTC_TOOLS/SYN> sta
+--------------------------+
| SYN Status 0x00000008
|
+--------------------------+
| No alarm / No warning
|
+--------------------------+
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
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
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 100/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 101/300
% /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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 102/300
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
% /opt/nortel/shell/sysmgt/wam_startoneapp.sh
<groupName>
ptf_services int_mdm_med/00108
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 103/300
<groupName>
% /opt/nortel/shell/sysmgt/wam_startgroup.sh
<groupName>
% /opt/nortel/shell/sysmgt/wam_startall.sh
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 104/300
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
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 107/300
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
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.
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 108/300
RNCEquipment
(RNC,258)(RNCEquipment,0)
unlocked
0
unknownstatusfalse
IDLE
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 109/300
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
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}
>:
4. CallTrace creation
>: RNC RNC_1207 CallTrace 0 AccessSession 0 create tracedUeIdentification
123456789012345 externalSessionId 2 tracedUeIdType imsi templateName
TraceSessionTemplate/TroubleShooting
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 111/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 112/300
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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 113/300
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
>
>:
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 115/300
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
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
- pchNbapState:
- fachNbapState:
NOBCCH_NBAP_CONFIG
NOBCCH_NBAP_CONFIG - status:
- fachNbapState:
NOBCCH_NBAP_CONFIG - status:
NOB info
: automaton =
: automaton =
: automaton =
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 118/300
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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 120/300
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 121/300
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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 122/300
CCP
(RNC,260)(NodeB,1)(ControlPort,1)
enabled
0
NONE
355
0
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 123/300
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 124/300
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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 125/300
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)
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 126/300
Software version
Ciphered Load: RNC42100c61201 including:
C Node: RC42162061200
I Node: RI42111c
RI42111c61220
RNC1000
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 127/300
AV Patch bundle
base7R1416A_CF01S1E
base7T1396A_CF01S1E
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
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
Customer naming
convention
UA4.2.1
UA4.2.2
UA4.2.3
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
CuR+3
06wk18
RC42162061800
RI42112c61673
RI42107c60950
AVL #23992 :
RNC42100c60900
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 129/300
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"
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 130/300
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 132/300
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
>:
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
ESTABLISHED
ESTABLISHED
ESTABLISHED
ESTABLISHED
LISTEN
ESTABLISHED
ESTABLISHED
ESTABLISHED
ESTABLISHED
LISTEN
NB:
The signification of the IP addresses are provided by d
role on the IN.
lp/* ap/* ip
/d
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
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
-> 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
-> 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
-> 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
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
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 |
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 140/300
INACC_CA
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 142/300
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 143/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 144/300
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 |
----------------------------------------------------------------------------------------
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
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
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
------------------------------------------------------------
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 147/300
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
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
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 148/300
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
PID
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
00010204021e000b
00010207021e000b
00010207021e000b
00010502021e000b
00010502021e000b
00010405021e000b
00010405021e000b
00010405021e000b
00010402021e000b
00010502021e000b
00010402021e000b
00010304021e000b
00010204021e000b
00010304021e000b
00010405021e000b
00010304021e000b
00010307021e000b
00010205021e000b
00010307021e000b
00010402021e000b
00010307021e000b
00010305021e000b
00010305021e000b
00010505021e000b
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 150/300
= 2
= 172.253.208.80
= 0
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 151/300
= 2
= 172.253.208.74
= 0
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 152/300
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 153/300
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 154/300
6220
6221
6222
7220
is
is
is
is
Managed
Managed
Managed
Managed
and
and
and
and
Unlocked
Locked
Locked
Unlocked
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
MM_USER
0x0DDFF754
0x0DDFFBD4
0x00000200
0x00000082
Iuxadm_LA
0x000001BF
0x00000000
Size :0x00000020
(0x2D2D2D2D)
(
232781652)
(
232782804)
(
512)
(
130)
(
226996224)
(
447)
(
0)
00
00
00
4C
00
00
00
55
00
00
00
00
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 156/300
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
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
576
576
===================================================================
===
Displays active set cells of a call
===
===================================================================
UeCall context Id: 576
rlId: 5
intraFreqCellId : 8 primaryScramblingCode : 105
cellId : 184
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 159/300
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 160/300
Example:
TELNET_CI> ue_call histocall
10
sbc @tmu_1_12_sbc - Result of: ue_call histocall
==========================================
===
Displays History
===
UeCall context Id: 10
10
Few highlights :
UECALL: INITIALACCESSREQ, scramblingCode: 30, uEIdType: TMSI LAI GSM ,
establishmentCause: ORG_BACK_CALL
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
: PS DOMAIN
, 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
: 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
, cnDomainInd
: CS DOMAIN, nrOfRabsToSetup
: 1,
: 0
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 163/300
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
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
ulAsConfId : 15
rabIndex : 0
rabId : none
isDlDpchSlotFormatInfo: 0
ulRbSetId : 11 dlRbSetId : 13
ulRbSetId : 9 dlRbSetId : 11
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 165/300
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 167/300
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
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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 168/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 169/300
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
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
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
Detach
Originating High Priority Signalling
Originating Low Priority Signalling
Call re-establishment
Terminating High Priority Signalling
Terminating Low Priority Signalling
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 172/300
===================================================================
=== 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
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******
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 174/300
=
=
=
=
=
0xacfdca48
120
0xa00a222
1762665115
588
= 0
= 0
10
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 175/300
********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
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 178/300
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 179/300
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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 180/300
nap
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
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>
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
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
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
CI>
CI>
CI>
CI>
stkadmca
stkadmca
stkadmca
stkadmca
cs 0
cs 1
ps 0
neighb
lsctx.
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 185/300
domainInstance
:
isSccpAvailable
:
proceedSccpAvailable:
resetStatus
:
transacId
:
isUpdateDdOK
:
isResetSyncNeeded
:
IU_CS(0)
true(1)
false(0)
CN_RESET_END(1)
151
false(0)
true(1)
cs 1
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 186/300
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)
ps 0
domainInstance
:
isSccpAvailable
:
proceedSccpAvailable:
resetStatus
:
transacId
:
isUpdateDdOK
:
isResetSyncNeeded
:
IU_PS(1)
true(1)
false(0)
CN_RESET_END(1)
152
false(0)
true(1)
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 187/300
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) ***
- resetStatus[0]
: (0x0)
[]
- swbResetStatus[0]: (0x0)
[]
: RESET_DOMAIN_CS (0x2)
RESET_DOMAIN_PS (0x2)
RESET_DOMAIN_PS (0x2)
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
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
=>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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 190/300
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
===================================================================
===
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
4
5
6
7
8
9
10
11
12
13
14
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 192/300
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
RNC
RNC
RNC
RNC
FDDCell
(reference)
FDDCell
(reference)
FDDCell
(reference)
FDDCell
(reference)
FDDCell
(reference)
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
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)
#631
#625
VS.RadioBearerEstablishmentUnsuccess.<screening>
VS.RadioBearerSetupRequest.< DlAsConfId>
FDDCell
(reference)
FDDCell
(reference)
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 194/300
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.
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 195/300
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 196/300
2000000
0
Off
NONE
Data channels
Number of OVSF codes for HS-SCCH
Signalling channel
numberOfHsScchCodes
operatorId
userSpecificInfo
0
NONE
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
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.
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
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
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)
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 200/300
Node B
RNC
SGSN
"Common Id" is used to provide the RNC with the user IMSI
RANAP/ Common Id (IMSI)
RRC/ RACH / Security Mode Complete
AAL2/ ECF
FP/ DL Synchronisation (CFN)
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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 201/300
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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 202/300
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 203/300
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
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
= FALSE
= FALSE
= 7a120
= 3d090
= 3
= 1
= 0
= 0
= 0
= 2
= 0
= 0
= 0
= 3
= 0
= 0
= 0
= 1e
= 5c8
= 2d
= 50
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
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 206/300
| 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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 207/300
= 1740
txCellDiscardClp
txFrameDiscard
txFrameDiscardClp
rxCell
rxCellClp
=
=
=
=
=
0
0
0
12817
0
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
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
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 209/300
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
1 cell / BBU
2 cells / BBU
3 cells / BBU
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>
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 211/300
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
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
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
BTS
CRNC
Cell Setup Request
Cell Setup 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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 214/300
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)
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
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
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
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
|
|
|
|
|
|
|
|
|
(0 = infinite)
ICEM-RTC_TOOLS/ICEM_DSPTOOL> SendGloContextReq w
a, b, c (gives information
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
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.
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 218/300
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
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-IN
RNC-CN
MGw
MGC
Alcap/ ERQ
- AEA
- PatchId
- CID
Alcap/ ECF
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 221/300
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
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
ERQ message)
ok
2006-05-23 14:02:04.10
{ 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
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 224/300
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 225/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 226/300
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
integrityActivated
120000
NONE
NetworkIndicator for PS
securityControl
tcnResetAck
userSpecificInfo
integrityActivated
120000
Default_PsCoreNetworkAccess
RNC-IN Configuration
27> d -p
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 228/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 229/300
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
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.
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 231/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 232/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 233/300
+-------------------------------------------------|
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 234/300
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
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).
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 235/300
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
IN address
login / password to connect the CP
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 236/300
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
The .tmp file gathers all the commands and results to build up the report
Availability State
ONLINE
FAILED
Number of Cells
6
30
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
ulAsConf
0
2
5
0
11
15
0
[]
===================
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
===================
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)
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
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
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.
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 240/300
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
======================================================================
Control_port[0]:
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 241/300
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
UNLOCKED
ENABLED
ONLINE
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
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
NOB
NOB
NOB
NOB
CCH
RRC
RPM
DPH
221
221
0x41001e41
0x41000c42
Cid: 11
Cid: 12
Cid: 13
Cid: 27
TBM AAL2 CID and Path Related Info (Obtained from PMC-M)
=======================================================
Cid: 11
Path State
UNLOCKED
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
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 244/300
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 245/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 246/300
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 247/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 248/300
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.
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 249/300
Decode
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 250/300
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:
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 251/300
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
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
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.
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 254/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 255/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 256/300
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 257/300
atmSpyStartCapture
atmSpyStopCapture
atmSpySaveBuf
atmSpyUninstall
exit
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 258/300
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 259/300
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
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 262/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 263/300
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 264/300
os rlogin card3
yes
set unsafe
set promote
ipspySetMode 1
ipspyInstall
ipspyAdd 5 172.253.208.78 1025 6
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 265/300
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.
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 266/300
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
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 267/300
Tracekey is 133096.
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 268/300
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
Example
Removes and turns off any
previous CTBL logging.
CtblIdle
CtblFilterOn
CtblRemoveStopTrigger
CtblLogCellWithTaggedUes(133096,9)
CtblShowStatus
CtblFilterOff
CtblIdle
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 270/300
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
TelCI Support
TMU
PC
RAB
NI
OMU
PMCM
Component
CP
Tool
Safe
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
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
showTbmAal2CidsState
Tbm
showTbmAal2AllocCid
Tbm
showTbmAal2PathAllocCid Tbm
showCidsBrief
Qaal2
showCid
Qaal2
showCidHistoryBrief
Qaal2
showCidHistoryLong
Qaal2
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
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
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
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
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
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
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
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
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
displayOvAlgorithm - New
displayOvMeastypeVsOpId
New
OVERLOAD Y
OVERLOAD Y
displayOvCtrlValue - New
OVERLOAD Y
Tool
Description
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
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
?
?
INACC_CA
INACC_CA
INACC_CA
INACC_CA
INACC_CA
INACC_LA
?
?
N
N
N
N
Y
Y
N
N
N
N
N
N
N
Y
?
?
INACC_LA
INACC_LA
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
INACC_LA
INACC_LA
INACC_LA
INACC_LA
INACC_LA
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
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
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
?
?
fmgscCa
fmgscCa
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
?
?
Tool
fmgscCa help
fmgscCa get_state
fmgscCa
get_ma_state
fmgscCa
get_buf_parms
fmgscCa
get_buf_entry
Description
fmgscMa help
fmgscMa get_state
fmgscMa
get_buf_parms
fmgscMa
get_buf_entry
fmgscMa
fmgscMa
fmgscMa terminate
fmgscMa
fmgscMa set_state
fmgscMa
set_buf_parms
fmgscMa
fmgscMa
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
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
pfla_callp
pfla_callp
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Y
Y
?
?
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
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
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
?
?
?
mib
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
mib enumvalues=int
mib
mib stringvalues=raw
mib
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
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
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
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
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
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
?
?
?
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
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
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
?
?
?
?
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
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
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
Description
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
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
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
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
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
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
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
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
rnccom
Tool
Component
Description
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
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
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
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
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
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
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
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 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
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
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
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
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
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
?
?
?
?
?
?
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
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
?
?
?
?
?
iurcallterm
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
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
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
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
Description
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
rnccall
bsnapshotuefach
rnccall
showPathTab
Tbm
showPcsPaths
Tbm
showPaths
Tbm
tbmHelp
Tbm
helpCnAccCa
Cnacc
helpCnAccLa
cnacc
Tool
Description
Z END OF DOCUMENT Y
Nortel confidential
UMT/UMT/APP/015074
03.01 / EN
Standard
19/May/2006
Page 300/300