Moshell Helpful
Moshell Helpful
Moshell Helpful
scripts
# Please feel free to add your tips if you don't find it here already.
# Please add comments to help clarify a procedure if you feel it is needed.
# Please add at the end of the file.
# Using Filters !
lst =ms,slot=16,.*ttp=pp(1|2|3),.*ttp enabled
#The meaning being LDN state any string including =ms,slot=16,<.* = any
character>,<.* = any character>ttp=1 or 2 or 3,
<.* = any character>ttp #where the state is = enabled
# If you have IMA / iworx problems - negative ACK fault while integrating a new
RBS.
# It is not necessary to restart the ETM4 board, simply lock the working board and
force it over to the standby board:
CRTNTXLYRXI004> lt all
# First you should check the state of all ImaGroups on the affected board.
CRTNTXLYRXI004> st ImaGroup=MS-12 0
# Then switch the boards (which will cause traffic to drop AFAIK) and check
afterwards.
example:
bl 001200 # block MS,Slot=12 - ETMC41 board
deb 001200 # unlock MS,SLOT=12 - ETMC41 board
# ima release !
# new moshell !
u+ dxu1060ima
rdel ImaGroup=MS-8-1-ima7
u-
# antenna issues !
from moshell rbs
lhsh 001200 ps | grep Fu
or cabx to get port
050812-02:48:48
port_0_dev_5/FuCbcSe ph CXC1323891%1_R22 0 - (lmbpp)
port_8_dev_7/FuCbcSe ph CXC1323891%1_R22 0 - (lmbpp)
port_4_dev_6/FuCbcSe ph CXC1323891%1_R22 0 - (lmbpp)
===================================================================================
=========================
Id MO
accessclassnbarred Result
===================================================================================
=========================
14725 UtranCell=DXU3404X 65535
>>> Set.
14742 UtranCell=DXU3404Y 65535
>>> Set.
14756 UtranCell=DXU3404Z 65535
>>> Set.
===================================================================================
=========================
Total: 3 MOs attempted, 3 MOs set
Open a terminal in oss, type ls (you can see a folder called Ericsson).
Close all Netscape windows then type rm -rf Ericsson.
Now you can open the OSS and try again.
# General traces !
mon-
monr # restart monitor !
ps -ef | grep monitor
acc 021500 restart
lh mod11 te e bus_send bus_receive NBAP_ASN
lh mod11 te e bus_send bus_receive RANAP_ASN
lh mod11 te e bus_send bus_receive RRC_ASN
lh mod11 te s aal2
lh mod11 te s aal2*
lh mod6 te e bus_send bus_receive Ans_aal2ap_proc
lh mod6 te e trace1 UEH_EXCEPTION
lh mod6 te filter set ([1]<>8) NBAP_ASN
lh mod6 te e trace9 Ans_aal2ncc2_proc
cntl c # kill !
cntl s # pause !
cntl q # start !
# restart mod !
str # find mod # or wh
bo
or lh mod7 readclock
acc 021500 restart
RXI
# mom paremeters !
MO parameter
mom rbslocal ocnsCorrelationTime
# get rbstype !
get 0
ulFeederAttenuationBranchB = ulAttenuation
$var = 39
set antf dlAttenuation $var $var $var $var $var $var $var $var $var $var $var $var
set antf ulAttenuation $var $var $var $var $var $var $var $var $var $var $var $var
ulFeederDelayBranchA = electricalDlDelay
set antf electricalDlDelay 1685 1685 1685 1685 1685 1685 1685 1685 1685 1685 1685
1685
set antf electricalUlDelay 1685 1685 1685 1685 1685 1685 1685 1685 1685 1685 1685
1685
$var = 1685
set antf electricalDlDelay $var $var $var $var $var $var $var $var $var $var $var
$var
set antf electricalUlDelay $var $var $var $var $var $var $var $var $var $var $var
$var
Restart RU's
st aux
acc restart proxy's ....
acc 36 restartAuxUnit
# get iub for link #
lk l=dxu1234
RBS:
lt RbsLocalCell
pr RbsLocalCell localCellId
set XX localCellId YYY7 # XX is the proxy for X sector from above print / YYYY
is the new ID !
set XX localCellId YYY8 # XX is the proxy for Y sector from above print / YYYY
is the new ID !
set XX localCellId YYY9 # XX is the proxy for Z sector from above print / YYYY
is the new ID !
RNC:
!!!! As example, with C1P4500, the bandwidth would be: 4500 atm-cell/sec * 47
kbyte/atm-cell * 8 (byte/bit) = 1692.0 kbit/s
!Spreadng factor
get UeRcPhyChUl spreadingFactor
!Same for DL running:
get UeRcPhyChDl spreadingFactor
!Or you can get UL and DL at the same time with:
get UeRcPhyCh spreadingFactor
!To know the correspondence of each value to the SF check the MoM or run:
mom UeRcPhyChUl spreadingfactor
mom UeRcPhyChDl spreadingfactor
!To know the correspondence of each "UeRc" to each RAB use:
get UeRc= userlabel
============================
SF (DL)
========
8 - 384kb/s
16 - 128kb/s
32 - 64kb/s
128 - 128kb/s
4 - HS
SF (UL)
=========
4UL - 384 (HS)
8UL - 144 (128kb/s)
16UL - 64kb/s
64UL - 12.2 (AMR)
============================
lt all
get dxu0075 local
set dxu0075X localCellId YYY7
set dxu0075Y localCellId YYY8
set dxu0075Z localCellId YYY9
# to get T1 from rxi and you know RBS !
get vcltp=vc303 # rbs 303 !
or for orange
get =bXXX # XXX is rbs !
lkk "proxy for vcXX "
get AtmPort=MS-18-1-3-9
lst ......T1Ttp
RNC :
TpaDevice_AmplificationError # ? !
TpaDevice_AmplificationError equipment_malfunction
RbsSubrack=RU1,RbsSlot=4,AuxPlugInUnit=1,RuDeviceGroup=1,TpaDeviceSet=1,TpaDevice=1
print antennab
set antennathreshold 0.....
# ExternalTma_LnaFailureBranchA !
lt systemc
pr systemc
If single band(current=100 not 200(dual)), const should be default so you can
delete what is there
deleteconst X(proxy) # acc ? !
304 through 300 ...
DXU0002> get systemc
===============================================================================
1180 NodeBFunction=1,SystemConstants=1
===============================================================================
SystemConstantsId 1
sysConstants 300:00001,301:135,302:270,303:135,304:270
===============================================================================
Total: 1 MOs
================================================================================
Proxy MO Action Nr of Params
================================================================================
1180 SystemConstants=1 deleteConst 1
1180 SystemConstants=1 writeConst 2
================================================================================
===============================================================================
Proxy MO Action Nr of Params
===============================================================================
1180 SystemConstants=1 deleteConst 1
1. OCNS is active in RBS. Use moshell and check RBSlocalCell MO, parameter
ocnsisactive
OCNS being active is not bad but in combination with point 2. causes the
fault
Most RBS can support about 42-45 dbm (420-450) but due to feeder losses,
the maxcapability
goes down. So if you see a low maxdlpowercapability (< 390) do the
following:
To check the RRC success rate from MoShell use the "pmr" command. e.g. for the last
5 hours run "pmr -m 5" then from the menu choose "6 | sort +1nr" to sort by number
of RRC connection requests, e.g.:
Kind regards,
David Smith
pmxd
Subrack=MS,Slot=8,PlugInUnit=1,Etmc41=1,Os155SpiTtp=pp1,Sts1SpeTtp=3,Vt15Ttp=(15|
16) . -m 5
# To define TMA
Make cv
# Removing TMA's !
pr tma
del XXX # mo from above print !
acc 1191 initSector
### Parameter 1 of 1, numberOfTxBranches (long): 1
deb RU's
# CREATE CV WITH OUT TMA !!!!
cd /d/configuration/cv
cv set <cv_name>
acc 0 restart
2) NbapDedicated/NbapCommon did not come up due to ETM4 did not stablize. Make
sure the CVs have "autoConfigurationAllowed" is set to true.
get 1
set 1 autoConfigurationAllowed true
3) The deleted script should included the blocking of Aal2PathVccTp. If not block
it before running the script.
4) Make sure you have RNC's RBS toy cell script that aligned with the RXI, SCXC or
not configuration. It you don't have the proper script, one can generate it from
the undo mo of the test RNC, thanks Ping.
u+ toycell_utrancell
rdel utrancell=toycell
u- toycell_utrancell
u+ toycell_iub
rdel Iublink=toycell
u- toycell_iub
Run the moshell script on the live CVs. In this case, don't delete VPI MO after
you remove the conflicting utrancell.
If it works in the toy rnc, it ought to work on the live CV.
5) Nortel issues:
Links did not come up: misconfiguration of ip in the MGW, database issue, bad
cable. We will see "MTP3b Link
Out of Service" alarm on the RNC also you will see lots of ERROR code 11095(link
of service) and 11096(link in
service) on board 000800.
All links are up, but RANAP=cs disabled: did not know how they resolved, but
their GTAC knows of the issue. We
will see "SCCP Remote Subsystem Unavailable" alarm on the RNC.
FYI...
All the link issues we have seen so far have always been Nortel/Cingular issue.
And for your information two links
did not come up on RNC3 because Nortel did not configure the ATM crossconnect for
this link.
###############################################################
# Name: How to use CLI "pm_" commands in P7 #
# Software version: RNC P7GA #
# Author: Kingston ([email protected]) #
# Version: A, (5th,Jun 2009) #
###############################################################
###################################################################
PART-1: ABSTRACT OF CLI.
###################################################################
//$ pm_lminfo
- list "Install Handle" for every LM on this board.
//$ pm_pginfo
- list "prog_pid" for every Program on this board.
###################################################################
PART-2: Example case -how to do same operation like "pgkill JVM" ?
###################################################################
Example case:
step-1: in moshell, find all LMs with product name contain "jvm"
===================================================================================
==============================
MO Attribute
Value
===================================================================================
==============================
LoadModule=CXC1726723_R71T01 productData
Struct{5}
>>> 1.productNumber = CXC1726723
>>> 2.productRevision = R71T01
>>> 3.productName = jdbc_jvm_lm
>>> 4.productInfo =
>>> 5.productionDate = 20080626
LoadModule=CXC1320784_R61GH01 productData
Struct{5}
>>> 1.productNumber = CXC1320784
>>> 2.productRevision = R61GH01
>>> 3.productName = jvm
>>> 4.productInfo =
>>> 5.productionDate = 20081030
LoadModule=CXC1320784_R71BC08 productData
Struct{5}
>>> 1.productNumber = CXC1320784
>>> 2.productRevision = R71BC08
>>> 3.productName = jvm
>>> 4.productInfo =
>>> 5.productionDate = 20090317
LoadModule=CXC1725791_R71T04 productData
Struct{5}
>>> 1.productNumber = CXC1725791
>>> 2.productRevision = R71T04
>>> 3.productName = jvm_supp_lm
>>> 4.productInfo =
>>> 5.productionDate = 20081125
LoadModule=CXC1320784_R71BC07 productData
Struct{5}
>>> 1.productNumber = CXC1320784
>>> 2.productRevision = R71BC07
>>> 3.productName = jvm
>>> 4.productInfo =
>>> 5.productionDate = 20081128
===================================================================================
==============================
Total: 5 MOs
Step-2: From so many LM, select the correct LM who are running JVM. The corrent
LM must has related "program" MO.
RNC5> pr CXC1726723_R71T01
===================================================================================
Proxy MO
===================================================================================
2981 SwManagement=1,LoadModule=CXC1726723_R71T01
===================================================================================
Total: 1 MOs
RNC5> pr CXC1320784_R61GH01
===================================================================================
Proxy MO
===================================================================================
3025 SwManagement=1,LoadModule=CXC1320784_R61GH01
===================================================================================
Total: 1 MOs
RNC5> pr CXC1320784_R71BC0
===================================================================================
Proxy MO
===================================================================================
2343
Equipment=1,Subrack=MS,Slot=13,PlugInUnit=1,Program=CXC1320784_R71BC08
2759
Equipment=1,Subrack=MS,Slot=12,PlugInUnit=1,Program=CXC1320784_R71BC08
3588 SwManagement=1,LoadModule=CXC1320784_R71BC08
4213 SwManagement=1,LoadModule=CXC1320784_R71BC07
===================================================================================
Total: 4 MOs
RNC5> pr CXC1725791_R71T04
===================================================================================
Proxy MO
===================================================================================
4093 SwManagement=1,LoadModule=CXC1725791_R71T04
===================================================================================
Total: 1 MOs
RNC5> pr CXC1320784_R71BC07
===================================================================================
Proxy MO
===================================================================================
4213 SwManagement=1,LoadModule=CXC1320784_R71BC07
===================================================================================
Total: 1 MOs
Step-3: Find out "<prog_pig>" of JVM on board 001200 via the correct LM's name.
Notice: after kill the JVM, new JVM program will start automaticall with random
"<prog_pig>", this is quite different from P6.
###################################################################
PART-3: detail usage and example output for each command.
###################################################################
===================================================================================
==============
// pm_lminfo Print information for a/all load module image(s).
===================================================================================
==============
$ help pm_lminfo
NAME
pm_lminfo - Print information for a/all load module image(s).
SYNOPSIS
pm_lminfo [-a] [-i <install_handle>]
$ pm_lminfo
core_module
CXC1725465_R71BC08
CXC1725558_R71BC07
CXC1725310_R71BC08
CXC1725489_R71BC08
......
$ pm_lminfo -a
Install Handle : core_module
File name : core_module
File format : core_module
Persistent : No
Absolute : Yes
Kernel module : No
Entrypoint : 0x00000000
Text_Base : 0x00700000
Text_Size : 0x001d2000
Data_Base : 0x00400000
Data_Size : 0x0006c000
No_Of_Instances: 1
Install Handle : CXC1725465_R71BC08
File name : /mole/ffs/CXC1725465_R71BC08.CBL
File format : ELF
Persistent : Yes
Absolute : No
Kernel module : Yes
Entrypoint : 0x851f0000
Text_Base : 0x851f0000
Text_Size : 0x0000c000
Data_Base : 0x85200000
Data_Size : 0x00001000
No_Of_Instances: 1
Install Handle : CXC1725558_R71BC07
File name : /mole/ffs/CXC1725558_R71BC07.CBL
File format : ELF
Persistent : Yes
Absolute : No
Kernel module : Yes
Entrypoint : 0x85210000
Text_Base : 0x85210000
Text_Size : 0x00022000
Data_Base : 0x85240000
Data_Size : 0x00001000
No_Of_Instances: 1
......
$ pm_lminfo -a -i CXC1725465_R71BC08
Install Handle : CXC1725465_R71BC08
File name : /mole/ffs/CXC1725465_R71BC08.CBL
File format : ELF
Persistent : Yes
Absolute : No
Kernel module : Yes
Entrypoint : 0x851f0000
Text_Base : 0x851f0000
Text_Size : 0x0000c000
Data_Base : 0x85200000
Data_Size : 0x00001000
No_Of_Instances: 1
$
===================================================================================
==============
//pm_lmconf - Print configuration for a load module image.
===================================================================================
==============
$ help pm_lmconf
NAME
pm_lmconf - Print configuration for a load module image.
SYNOPSIS
pm_lmconf <install_handle>
$ pm_lmconf CXC1725465_R71BC08
OSE_LM_POOL_SIZE=0
OSE_LM_SUPERVISOR_MODE=YES
OSE_LM_SIGNAL_SIZES=31,63,127,255,1023,4095,16383,65535
OSE_LM_STACK_SIZES=256,512,1024,2048,4096,8192,16384,65535
OSE_LM_MAIN_NAME=i2cpqii_lm
OSE_LM_MAIN_PRIORITY=16
OSE_LM_PROGRAM_TYPE=SYS_RAM
OSE_LM_DATA_INIT=YES
OSE_LM_MAIN_STACK_SIZE=4000
OSE_LM_EXEC_MODEL=PRIVATE
HEAP_SMALL_BUF_INIT_SIZE=3728
OSE_LM_BSS_INIT=YES
OSE_LM_IDENTITY=CXC1725465_R71BC08
LM_PATH=@(#)/vobs/cello/babs/control_dm/i2c_pqii_mp_lm/.lmopt/lm i2cpqii.ppc750
ppc750 cppswdi_lmbuild_i2cpqiimp_cpp7_26.13seasx041
LM_VERS=@(#)CXC1725465 R71BC08 2009-03-16 10:29:48 GMT
LM_CMINFO=@(#)134.138.134.41 cppswdi_lmbuild_i2cpqiimp_cpp7_26.13seasx041 27877
CELLO_LOAD_CLASS=65
RTL_PHYS_MEM_TEXT=RAM
$
===================================================================================
==============
//pm_pginfo - Print information for a/all program(s).
===================================================================================
==============
$ help pm_pginfo
NAME
pm_pginfo - Print information for a/all program(s).
SYNOPSIS
pm_pginfo [-a] [-p <prog_pid>] [-i <install_handle>]
$ pm_pginfo
0x302f3
0x102ee
0x102dd
0x102d1
0x102c7
......
$
$ pm_pginfo -a
Install handle : CXC1720483_R71BC07
Program pid : 0x000302f3
Domain : 0x0000002f
Segment pid : 0x000102f5
Main block : 0x000302f3
Main process : 0x000102f7
Stk poolid : 0x000102f6
Stk pool base : 0x9c241000
Stk pool size : 0x000493e0
Sig poolid : 0x000102f6
Sig pool base : 0x9c241000
Sig pool size : 0x000493e0
UID : 0x00000000
Heap ref : 0x00a0e800
State : started
Install handle : CXC1322418%12_R71BC06
Program pid : 0x000102ee
Domain : 0x0000002e
Segment pid : 0x000102ef
Main block : 0x000102ee
Main process : 0x000102f1
Stk poolid : 0x000102f0
Stk pool base : 0x9d426000
Stk pool size : 0x0007a120
Sig poolid : 0x000102f0
Sig pool base : 0x9d426000
Sig pool size : 0x0007a120
UID : 0x00000000
Heap ref : 0x00a00820
State : started
......
$ pm_pginfo -a -i CXC1720483_R71BC07
Install handle : CXC1720483_R71BC07
Program pid : 0x000302f3
Domain : 0x0000002f
Segment pid : 0x000102f5
Main block : 0x000302f3
Main process : 0x000102f7
Stk poolid : 0x000102f6
Stk pool base : 0x9c241000
Stk pool size : 0x000493e0
Sig poolid : 0x000102f6
Sig pool base : 0x9c241000
Sig pool size : 0x000493e0
UID : 0x00000000
Heap ref : 0x00a0e800
State : started
$
$ pm_pginfo -a -p 0x000302f3
Install handle : CXC1720483_R71BC07
Program pid : 0x000302f3
Domain : 0x0000002f
Segment pid : 0x000102f5
Main block : 0x000302f3
Main process : 0x000102f7
Stk poolid : 0x000102f6
Stk pool base : 0x9c241000
Stk pool size : 0x000493e0
Sig poolid : 0x000102f6
Sig pool base : 0x9c241000
Sig pool size : 0x000493e0
UID : 0x00000000
Heap ref : 0x00a0e800
State : started
$
===================================================================================
==============
//pm_pgconf - Print configuration for a program.
===================================================================================
==============
$ help pm_pgconf
NAME
pm_pgconf - Print configuration for a program.
SYNOPSIS
pm_pgconf <prog pid>
$ pm_pgconf 0x10091
HEAP_LARGE_BUF_THRESHOLD=64512
heap_ref=9249184 (0x8d21a0)
ose_rtl_elf_chunk_size=0x40000
OS_MODE=BASIC
MAX_TRACE_SIZE=508
MAX_MONITOR_SIZE=508
HEAP_MALLOC_ERROR_ON_NULL=TRUE
OSE_LM_IDENTITY=CXC1725444_R71BC08
LM_PATH=@(#)/vobs/cello/bcs/control_dm/bc_redundancy_mp_lm/.lmopt/lm redundancy.ppc
ppc cppswdi_lmbuild_bcredundancymp_cpp7_26.13seasx041
LM_VERS=@(#)CXC1725444 R71BC08 2009-03-16 10:15:40 GMT
EFS_DEFAULT_STDIO=/tty
CMD_PREFIX=ose_cmd_
CMD_STACK=10000
CS_CONFDIR=/d/configuration/
CS_LMDIR=/d/loadmodules/
CS_GLOBAL_CONFDIR=/c/configuration/
OSE_LM_POOL_SIZE=0
OSE_LM_SUPERVISOR_MODE=YES
OSE_LM_SIGNAL_SIZES=31,63,127,255,1023,4095,16383,65535
OSE_LM_STACK_SIZES=256,512,1024,2048,4096,8192,16384,65535
OSE_LM_MAIN_NAME=redundancy_lm
OSE_LM_MAIN_PRIORITY=16
OSE_LM_PROGRAM_TYPE=SYS_RAM
OSE_LM_DATA_INIT=YES
OSE_LM_MAIN_STACK_SIZE=4000
OSE_LM_EXEC_MODEL=PRIVATE
HEAP_SMALL_BUF_INIT_SIZE=3728
OSE_LM_BSS_INIT=YES
LM_CMINFO=@(#)134.138.134.41 cppswdi_lmbuild_bcredundancymp_cpp7_26.13seasx041
11697
CELLO_LOAD_CLASS=67
RTL_PHYS_MEM_TEXT=RAM
EFS_SHMEM=0
$
===================================================================================
==============
//pm_kill - Kill program
===================================================================================
==============
$ help pm_kill
NAME
pm_kill - Kill program
SYNOPSIS
pm_kill <prog_pid>
===================================================================================
==============
//pm_install - Install a load module
===================================================================================
==============
$ help pm_install
NAME
pm_install - Install a load module
SYNOPSIS
pm_install [-a] [-p] [-k] [-c <conf>] [-f <file_format>] <install_handle>
<file_name>
-a : Install absolute, i.e. do not relocate.
-p : Install persistent.
-k : Install as a kernel module
===================================================================================
==============
//pm_uninstall - Uninstall a load module image
===================================================================================
==============
$ help pm_uninstall
NAME
pm_uninstall - Uninstall a load module image
SYNOPSIS
pm_uninstall <install_handle>
===================================================================================
==============
$ help pm_create
===================================================================================
==============
NAME
pm_create - Create a program.
SYNOPSIS
pm_create [-s] [-c <conf>] <install_handle>
===================================================================================
==============
//pm_start - Start a program.
===================================================================================
==============
$ help pm_start
NAME
pm_start - Start a program.
SYNOPSIS
pm_start <prog_pid>
===================================================================================
==============
********************health check************************************
dcgm
hc
**********************Configuration Settings************************
*****************************PM scanners*********************************
*****************************Troubleshooting*****************************
te log read � reads the trace and error log, and dumps to
the shell --> Check it there is any ERROR event in the log
bs �g �c "llog"
bs �g �c "te log read" | grep ERROR - Read log ERROR/INFO in the active all
boards --> Check it there is any ERROR event in the log
bs -g -c "vii" - Check Led on Boards --> All the boards must
have only the Green �ON�
bs -g -c "spaspccinfo" - Check plane change control info in all boards
--> Check Plane A and Plane B status
sma -n (-all) - Check the state of the Loadmodule in the GPB boards
- Check if the state is active
- Check if the mode is A_w_S (active working standby passive)
- Check the PeerSmnApn (standby board)
- Connect to standby and check if the same loadmodule are passive
ss - Check the maximum stack usage since system start for all
processes on a board
listloaded
cv cu
- Current Configuration Version --> Check that's its
the startable version
all err - Look for errors in the Trace & Error logs
from all boards.
hget aal2pathv state - Prints the operational state for the AAL2
paths.
get aal5tpvcctp state - Prints the operational state of the AAL5 VCC.
The following PM's should be checked to get some basic node statistics.
> pget vmgw
> hpget tdmterm
> pget mtp3b
If Sigtran/IP is used:
lt Mtp3bSpItu
lt/st/get m3uassociation enabled/disabled
lt/st/get mtp3bap
lt/st/get mtp3bsls
lt/st/get mtp3bsrs
lt/st/get mtp3bsr
getAttrObj subrack 1 - To read the serial number of the
backplane
all pglist | grep -i upcf - how to know which ones are mesc and /
or find out different types of boards in the MGw
***************************************sgw
mapping******************************************
Vmgw Used to terminate the signalling from the MSC to the M-MGw,
allowing the MSC to request and release resources from the M-MGw
VclTp Specifies the VCI for an ATM connection and also terminates
the VCI
ET-MF4/1 The unit is a line terminal board with four STM-1 or OC-3c
interfaces for ATM transport.
Element Management
Gateway Control Protocol (GCP)
Media Stream Function
ATM Transport
Virtual Media Gateway
O&M Access Control
TTC Interfaces
ETSI Interfaces
ANSI interfaces
SS7 Signaling Gateway and Signaling Transfer Point
Multi-Function Device
Audit Trail
ATM switch
Datacom Base
SS7 Signaling over TDM
SS7 Signaling over ATM
TDM Transport
New and Enhanced Optional Features
GSM A-interface
GSM High Speed Datacom Service
SCCP Accounting
SCCP Policing
SCCP Relay
*************************************Board Access**********************************
lhsh 730200
02 = Board Number
UPCF DB
lhsh 730200 mesc_info_tdm -group_total 0 - Displays TDM state, group and internal
data
lhsh 730200 mesc_info_vmgw 0 - Displays status of Vmgws
lhsh 730200 mesc_info_ctx <options> - Displays debug & CtxState information
lhsh 730200 mesc_info_ctx -alive 15000
Block MESC : mesc_command_block
pglist
Restart Program : pgkill 12
UPCF O&M
lt/get/pget mgwa
lt/get/pget mesc
lt/get/pget gcp
lt/get/pget/st tdmterm
pget tdmterm pmNrofTdmTermsRej
lt vmgw
get vmgw profile
MTP3B
lt mtp3b
pr/st/get mtp3bsls
MTP3UA
lt m3ua
AAL2
lt aal2
pr/get/st aal2pathvcctp
Gigabit Interface
lt/pr/st/get/pget gig
IP
lt ip
pr/get ipint
*********************************Trace
Handling*********************************************
lhsh xxxxx te status - Displays the current settings of the
traces in a board.
M-MGw R4
sql select name from tables; - List of all the tables in SQLC
sql select * from oammesctable_r401; - Get a list of all the MSB boards
id
1- sql select pno, prev, piuinstanceid from cspgmresource_02 where pno='CXC 132
2250'; <-- Get the PIU instance ID for this loadmodule
2- sql select * from cspiuresource_01 where id=15; <-- Lets take PIU
Instance ID 15 and retrieve the slot id
3- sql select * from csslotresource_01 where id=28; <-- Retrieve with the
slot instance Id, which subrack (srid) and slot (apn)
4- sql select * from cssrresource where id = 1; <-- Real subrack address
6. Before logging the GCP messages to file verify with vols-command that there is
enough disk space:
001300> vols
volume total used free
/p001300 781M 4M 0% 776M 99%
7. If you had enough disk space, you can write the GCP messages from memory to file
with following command:
001300> stc_gcp_buffer -log /p001300/gcp.log
8. Then fetch this file with FTP from node for decoding.
9. Delete the log file from the node:
001300> rm /p001300/gcp.log
10. The GCP Buffer can be cleared with following command:
001300> stc_gcp_buffer �clear
Caution: Make sure always before logging the GCP Buffer to a file, that you have
enough space on the file system (see step 6). Also remove the file
log file always afterwards from the M-MGw file system (see step 9.).
Check the GCP context ID by call path trace command in MSC-S then search all GCP
messages with the GCP context ID in decoded file.
Example: CTRAI:MSISDN=8613826341042;
#########################MGW#######################################################
######
ID: SCS705060
Domain: primus_owner
Solution Class: 4.X
Fix
SOLUTION:
CONDITIONS:
PROCEDURE:
1. Status Check
1. In the Element Manager SS7 view, expand the folder MTP3b Signaling Points.
The current Signalling Points are displayed.
2. Expand the relevant folder MTP3b Signalling Point.
3. Click on the folder MTP3b Signalling Link Sets.
The Status of all Link sets can be seen here.
4. Select the Attribute folder and click on Refresh to verify the present states of
MTP3b Signalling Links.
In Element Manager, select TDM Termination Groups view from drop-down list and
verify that no TDM Termination is in disabled state.
$ vii
$ fan_vii
$ readclock
$ mirror stat
This command goes to GPB 000200, so if status here shows Passive, it means that GPB
000200 is passive. So Other GPB 000300 should be active. Alternatively that can be
checked using:
$ lhsh 000300
000300>mirror stat
$ sma �all
$ llog
$ llog -l
Look for any recent board restarts or corresponding errors.
1.12 Keep a printout of trace and error log
$ te log read
Look for errors in trace and error logs from all boards:
all te log read | grep �i error
$ capi tot
Check all GPB board /c/ and /d/ free space with command:
$ vols
Free space for d/ partition should be at least 30%.
Access MESC controlling GPB board. For example, in GMPV3 GPB board position 010200
and 010300 are controlling GPBs.
$ lhsh 010200
On the following prompt, give command
010200>mesc_counters_gcp �all
These counters a accumulative, so taking this command twice and looking at the
difference in values of the latest printout from previous one, exact cause of
problem in GVP can be found.
Access MESC controlling GPB board. For example, in GMPV3 GPB board position 010200
and 010300 are controlling GPBs.
$ lhsh 010200
On the following prompt, give command
010200> mesc_info_ctx -alive 7200 �defer
010200> mesc_info_ctx �errors
This will list all contexts active for more than 2 hours. Check the same in board
010300 / 650200 /650300 as well.
$ st Vmgw
$ get Vmgw profile ! Check if correct profile is loaded !
$ lhsh 001000 ch_info_vmgw
$ lhsh 001100 ch_info_vmgw
VMGw associated with CH0 will be visible in 001000 & VMGw associated with CH1 will
be visible in 001100 .
Access MESC controlling GPB board. For example, in GMPV3 GPB board position 010200
and 010300 are controlling GPBs.
$ lhsh 010200
On the following prompt, give command
010200> mesc_counters_device 0
010200> mesc_counters_device �all
Look for rejections for any particular device ( if any ). Reasons of rejections can
be found in GCP counters as described in section 2.12 of this document.
Check the same in board 010300 / 650200 /650300 as well.
Access MESC controlling GPB board. For example, in GMPV3 GPB board position 010200
and 010300 are controlling GPBs.
$ lhsh 010200
On the following prompt, give command
010200> mesc_info_tdm -group_total �all
$ lhsh 000600
000600> rof_congestion_info
$ lhsh 000800
000800> rof_congestion_info
Output may be available on one board only. It depends on no. of SS7 stacks loaded
in the system and on which board the stack is running.
Fix
SOLUTION:
CONDITION:
PROCEDURE:
Here,
C = Critical Alarms
M = Major Alarms
m = Minor Alarms
w = Warnings
ALA
UL
where,
lgaevsur yyyy-mm-dd
This command can be used to save the complete healthcheck of the MGw in one file.
Pget MgwApplication
If any of the MSBs show "not loaded", then there is a problem with the MSB.
Take above 2 prints again after a gap of 1-2 minutes to find out error counters
that are increasing.
> cd /c/license
cat licensekeys.xml
Status column should contain �rcv(any)�. If status is other than this, there is a
fault in the board.
Command needs to be given again and output compared with previous output to get
actual present status.
#################################################################################
P7FP Troubleshooting Improvements
#################################################################################
Abstract/Description Contents:
-----------
- Selective Ue Tracing in RBS
- UeCtxt Event History Buffer
- PLM Diagnostic Improvements
$ uetrace status
Uetrace is not enabled.
$ uetrace status
Type of trace selection = NBAP, max = 1
CRNC ccid |NodeB ccid |RLS-type |RLS |RL id |Cell |ubch |
dbch |hsdbch |urnti |crnc |RM |uec |uesl
$ uetrace max 5
$ uetrace status
Type of trace selection = NBAP, max = 5
CRNC ccid |NodeB ccid |RLS-type |RLS |RL id |Cell |ubch |
dbch |hsdbch |urnti |crnc |RM |uec |uesl
Enable bus_send UEH_EXCEPTION and use Decoder (3.0s or later) to see the UE_History
in ASCII format.
Enable bus_send UEH_EXCEPTION and use Decoder (3.0s or later) to see the UE_History
in ascii format.
-> map UeCtxt's between DRNC and SRNC : ueregprint <sRnc sRnti>
################FINGERPRINT##########################
So if you have an Omnisite then you are correct and the node ID will change thus
making the license key invalid.
Interestingly there is a coli command that can change the node ID. We have tried it
and it works....
example
lhsh 000100/port_0_dev_7 nodeid read
lhsh 000100/port_1_dev_8 nodeid read
lhsh 000100/port_2_dev_9 nodeid read
lhsh 000100/port_0_dev_7 nodeid write 32 38 35 37 30 39 5f 35 32 37 37 34 37
lhsh 000100/port_1_dev_8 nodeid write 32 38 35 37 30 39 5f 35 32 37 37 34 37
lhsh 000100/port_2_dev_9 nodeid write 32 38 35 37 30 39 5f 35 32 37 37 34 37
REMEDY:
CONDITIONS:
1. IP-based Iub
2. Node B has no subrack serial number
3. Node B has been recommissioned from scratch with a Basic Package
4. Fingerprint of Node B changed after recommissioning
!PRIMUS
PROCEDURE:
1. The safest way forward to generate new fingerprints is to remove following files
(when present):
/c/node_id/bpNodeId.txt
/c/node_id/Node_identity.txt
/c/node_id/genNodeId.txt
SOLUTION:
CONDITIONS: