0% found this document useful (0 votes)
231 views

OSS Commands

This document contains commands and explanations for monitoring and adjusting various network parameters in an UMTS network. It includes commands to check the number of HSDPA users and PDSCH codes, view alarms, adjust primary CPICH power, check handovers, and monitor drops and failures. It also provides explanations of abbreviations and counters for troubleshooting issues like RRC failures.

Uploaded by

Hassane Aly
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
231 views

OSS Commands

This document contains commands and explanations for monitoring and adjusting various network parameters in an UMTS network. It includes commands to check the number of HSDPA users and PDSCH codes, view alarms, adjust primary CPICH power, check handovers, and monitor drops and failures. It also provides explanations of abbreviations and counters for troubleshooting issues like RRC failures.

Uploaded by

Hassane Aly
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 7

>> pmr -s 20160615.0500 -e 20160615.

1100
>>,
To check max no. of HSDPA users, EUL users & PDSCH codes
In node RBS
>> hget RbsLocalCell=.*C maxNum

lgn -m 3_extrair logs


alt_ alarms
lget UMPT94 primaryCpichPower
lget utrancell=UMAP646 gsmcellref- Para verificar HO s 3G-2G
lget UtranCell=UMPM05 utrancellref - Para verificar HO s 3G-3G
MPRNC01> alt para ver sites alarmados e fora de servico
get bf ul|dl|elements- get channel elements
get UMPT62 primarycpich
Command to get and adjust Priamry CPICH Power (Default is 320)
================================================================================
=================================
RNRST08> get UMAP53 pri.*
RNRST08> set UMAP681 primaryCpichPower 300
================================================================================
=================================
Command to get and adjust Individualoffset (reccommeded is 0)
================================================================================
=================================
RNRST08> get U08-BKK2874-1A individualoffset.*
RNRST08> set U08-BKK2874-1A individualOffset 30
RNRST08> set U08-BKK2874-1A individualOffset -30
================================================
pr retdevice
get <proxy>
set <proxy> electricalAntennaTilt <value>
get ret electrical
get . fingerprint

set Subrack=1,Slot=1,PlugInUnit=1,PiuDevice=2,TxDeviceGroup=1 numHsCodeResources


2-para aumentar reource device
ala_The list of active alarms can be retrieved with the commands al (to show an
overview) or ala
(the same as al, with more details).
pr-will show for each MO, the LDNand the proxy number.
cedhr -s 20160405.1600 -e 20160406.0700
Ob
nemo
para ler teste scannado

.nmf-results
.mrk-results
.tab-map
update coordenate
ajustar coordenadas
pmxh -s 20140415.0800 -e 20140415.1700 -a utrancell UplinkBaseBandPool pmCapaci
tyAllocRejUlCe|pmCapacityAllocAttUlCe|pmCapacityUlCe|
________________________________________________________________________________
________________________________________________

set 237 electricalAntennaTilt 50


ftp.celfinet.com
user:ftp_mcel
PWD: celfinetmcel
APN:isp.mcel.mz
---------------------------------------------------------------------------------------------------------------------------cedhr -m7
cedhr -s 20141130.1600 -e 20141130.2000
MHRNC03> lget UtranCell=UMAP68 pwroffset
140827-16:40:29 10.201.13.132 10.0j RNC_NODE_MODEL_S_1_1052 stopfile=/tmp/4665
================================================================================
=================================
MO
Attribute
Value
================================================================================
=================================
UtranCell=UMPT941
pwrOffset
5
UtranCell=UMPT942
pwrOffset
5
UtranCell=UMPT943
pwrOffset
5
================================================================================
=================================
Total: 3 MOs
MHRNC03> lget UtranCell=UMPT33 pwrAdm
140827-16:40:34 10.201.13.132 10.0j RNC_NODE_MODEL_S_1_1052 stopfile=/tmp/4665
================================================================================
=================================
MO
Attribute
Value
================================================================================
=================================
UtranCell=UMPT941
pwrAdm
94
UtranCell=UMPT942
pwrAdm
94
UtranCell=UMPT943
pwrAdm
94
================================================================================
=================================

lget UtranCell=UMPT33 dlCodeAdm

rrc rab

pmxh -m 12 -a UMAP07 pmNoRabEstBlockTnSpeech|pmNoRabEstBlockNodeSpeech|pmNoRrcCo


nnReqBlockTnCs
pmNoRrcConnReqBlockTnCs|pmNoRrcConnReqBlockTnPs
pmxhn utrancell -m 24 pmNoFailedRrcConnectReqHw|pmNoFailedAfterAdm|pmNoRrcConnRe
qBlockNodeCs|pmNoRrcConnReqBlockNodePs|pmNoRrcConnReqBlockTnCs|pmNoRrcConnReqBlo
ckTnPs

right arrow or Ctrl-f - move forward one character


left arrow or Ctrl-b - move backward one character
up arrow - previous command in history buffer
down arrow - next command in history buffer
backspace - delete one character backward
Ctrl-d or <del> - delete one character forward
Ctrl-a or <home> - go to beginning of line
Ctrl-e or <end> - go to end of line
Ctrl-u - erase all characters backward
Ctrl-k - erase all characters forward
Alt-f - move forward one word
Alt-b - move backward one word
select or select + ctrl-<insert> - copy to clipboard
<insert> or shift-<insert> - paste from clipboard
lpr utrancell=UMPM383- Handovers going out
get utrancell=UMPM38 - Na parte das relacoes de HO, o "reserved by" ilucida as r
elacoes no sentido para a celula em causa.

CFRPHEM
MOD: Module RNC yang menghandle Node-B
IUBLINK : Label IuB interface Node-B
CELL (CFRPHEMX): 1st digit (C) = status cell
3 digit berikutnya (FRP)= status common
channels (fach/rach/pch).
5th digit (H) = status HSDPA channel (h
sdsch).
6th digit (E) = status Enhanced uplink
channel (eul)
ICDS: 1st digit = status Iublink
2nd digit = status nbapCommon
3rd digit = status nbapDedicated
4th digit = status Synchronisasi Node-B

TN: jenis transmisi IuB


I = berbasis IP address
A = ATM
ATMPORTS: hanya untuk yang menggunakan ATM
cth: MS11-2-IMA37-44 : MS11=MainSubrack slot 11, port 2
: IMA37-44=sys 37
s/d 44 (8 E1)
Status: L=Locked, 0=Disabled, and 1=Enabled
Drops de Sincronismo
RNC -> pmx umap07 pmnoSysRelSpeechUlSynch -m 4 -a
drops de congestionamento
MHRNC03-> pmx umap77 pmnoOfTermSpeechCong -m 4 -a
drops de SHO failure
MHRNC03> pmx umap07 pmnoSysRelSpeechSoho -m 4 -a

O maxTotaloutputPower deve ser ajustado nos dois lados: do lado da Node e do lad
o da RNC.
--Do lado da node eh o primeiro parmetro a ser ajustado. Se este parmetro aparecer
-1, quer dizer que a potencia eh menor que 40W (default=20W). No entanto, para
poder ajustar o parametro maximumtransmissionPower(RNC) para 460dBm, eh mandator
io que antes o maxTotaloutputPower (na RBS) esteja em 40.
---------MHRNC03> lget . maximumTransmissionPower ------para RNC
-----MHRNC03> lget utrancell=UMAP32 maximumTransmissionPower --------para NodB
-----UMPT11-MATENDENE> get . maxtotal
--------Para verificar os Ips da nodes na RNC
MHRNC03> get . remoteCpIpAddress1
-------para ver electrical tilt
UMAP42-LAULANE> get ret elec
------comando para ver overshooting
UMPT13_HABEL_JAFAR> pmx . propagationdelay
----para ver o estado das licencas, fingerprinter
UMAP32-EDUCACAO> get 6
------para ver potencia da RBS
SOMMERSCHIELD> get . maxtotal

pmr na node para ver capacidade de CE e quantos estao em usi


17.
DownlinkBaseBandPool=1 AvgCapacityDlCE (capacidade da node)
DownlinkBaseBandPool=1 AvgDlCECapacity (capacidade em uso)
uer dizer que nao esta a ser usado

17.7
0

19.5
0 q

get txdevices - Para ver configuracoes dos Resource ID's na NodeB


-------------Quando temos RRC failure, pode ser por varios motivos:
-MHRNC03> pmxh utrancell=UMAP35 -s 20160526.0400 -e 20160526.1100 pmNoFailedRrcC
onnectReqHw|pmNoFailedAfterAdm|pmNoRrcConnReqBlockNodeCs|pmNoRrcConnReqBlockNode
Ps|pmNoRrcConnReqBlockTnCs|pmNoRrcConnReqBlockTnPs
se temos falha devido a pmNoFailedAfterAdm, corremos o comando que se segue par
a saber as causas:
MVRNC02> pmxh utrancell=UMAP55 -s 20160504.0400 -e 20160504.0900 pmNoRrcReqDenie
dAdmDlHw|pmNoRrcReqDeniedAdmUlHw|pmNoRrcReqDeniedAdmDlPwr|pmNoRrcReqDeniedAdmDlC
hnlCode

da nos todos os contadores nums estacao


MHRNC03> pmx cell=UGAD24 pmTotNoRrcC|pmNoSystemRabRe|pmNoRabEstablish|pmNoNormal
RabRel|pmNoFailedAfterAdm -m 1

pmx cell=UGAD24 pmCapacityHsDschUsers


1. You should monitor the value of the counter pmCapacityHsDschUsers
################################################################################
####################################################
MO Class Pm Counter Type Flags
################################################################################
####################################################
HsDschResources pmCapacityHsDschUsers sequence:long [21] PDF,ropReset
----------------------------------------------------------------------------------------------------------------------------------The distribution of the number of HS-DSCH users, as percentages of the correspon
ding license limit.
Counter type: PDF
Counter is reset after measurement interval: Yes
Condition: Sampled each second of the granularity period (gives 900 values). HSFACH is not applicable to this counter and HS-FACH transmissions do consequently
not trigg
er the stepping of this counter. The actual measurement is started when the HS-D
SCH resources are setup.
2. It's hard to calculate the average number of codes per user. I advise you to
look at the following counters:
################################################################################

####################################################
MO Class Pm Counter Type Flags
################################################################################
####################################################
HsDschResources pmUsedHsPdschCodes sequence:long [16] PDF,ropReset
----------------------------------------------------------------------------------------------------------------------------------The distribution of the HS-PDSCH code utilization, as the number of HS-PDSCH cod
es used by the scheduler. Also includes codes used for HS-FACH.
Counter type: PDF
Counter is reset after measurement interval: Yes
Condition: Sampled each 100 ms of the granularity period (gives 9000 values). Th
e actual measurement is started when the HS-DSCH resources are setup.
################################################################################
####################################################
MO Class Pm Counter Type Flags
################################################################################
####################################################
HsDschResources pmRemainingResourceCheck sequence:long [3] PDF,ropReset
----------------------------------------------------------------------------------------------------------------------------------The reason why it is not possible to schedule another high-speed user.
Counter type: PDF
Counter is reset after measurement interval: Yes
Condition: There are three resources needed for HSDPA user transmission: HS-SCCH
codes, HS-PDSCH codes and HS-PDSCH power. These are recorded in separate counte
r entries.
For every subframe and after every scheduled user the Remaining Resource Check f
unction is activated. The counter monitors the function and therefore only steps
in activ
e subframes. When it is not possible to schedule another user in the subframe be
cause of resource shortage the counter records the first found reason. As soon a
s one reso
urce is found short checking stops, thus only one resource counter entry can be
incremented per subframe. The function checks the resources in order of counter
entry inde
x starting with the lowest. Note that the counter steps even in case there are n
o more users valid for transmission in current subframe, i.e. even if no user th
at could h
ave used the resources. Resource shortage is considered for both CELL_DCH and HS
-FACH users. A HS-FACH user is a UE which is in RRC state CELL_FACH (on RNC leve
l) and is
using transport channel HS-DSCH and not FACH. The counter reflects the cell pers
pective. The actual measurement is started when the HS-DSCH resources are setup.
PDF ranges:
[0]: HS-SCCH code shortage
[1]: HS-PDSCH code shortage
[2]: HS-PDSCH power shortage
3. It's not so important to know the average power per user. More useful is to f
ind out how ofter Power is the limiting factor for providing HS services. Motino
r pmRemainingResourceCheck (HS-PDSCH power shortage).
4. Here you also need not the average CE consumption per user, but the number of
times when the user was rejected due to CE congestions:
################################################################################
####################################################
MO Class Pm Counter Type Flags

################################################################################
####################################################
DownlinkBaseBandPool pmCapacityAllocRejDlCe long Peg,ropReset
----------------------------------------------------------------------------------------------------------------------------------The number of attempts to allocate DL Channel Elements that are rejected (relate
d to bin [0] of pmCapacityDlCe).
Counter type: Peg
Counter is reset after measurement interval: Yes
Condition: Stepped each time an attempt to allocate a DL CE is rejected. The act
ual measurement is started when the DownlinkBaseBandPool is created.
Undefined value: -1
********************************************************************************
****************************************************
UplinkBaseBandPool pmCapacityAllocRejUlCe long Peg,ropReset
----------------------------------------------------------------------------------------------------------------------------------The number of attempts to allocate UL Channel Elements that are rejected (relate
d to bin [0] of pmCapacityUlCe).
Counter type: Peg
Counter is reset after measurement interval: Yes
Condition: Stepped each time an attempt to allocate an UL CE is rejected. The ac
tual measurement is started when MO UplinkBaseBandPool is created.
Undefined value: -1
********************************************************************************
****************************************************

You might also like