check cv

>cvcu
----------------------------------------------------------------------delete cv
>cvrm cvname
----------------------------------------------------------------------new cv
>cvms cvname
RetDeviceSet_RetFailure:
A faulty RETU
The RETU arm is unable to move for environmental reasons, for example, antenna icin
g
Antenna and RETU not installed
RBS:
moshell Uxxxx *log onto the node
lt all *load all Managed Objects
alt *show current alarms and confirm what sector is affected
lpr SectorAntenna=x,AuxPlugInUnit=x
get xxx *using the proxy number from the above command will show the state of th
e RetDeviceSet
acl xxx *check what action you can perform on the proxy number
acc xxx restartAuxUnit *try restart the RET using the proxy number
If a restart does not clear the alarm an RE will need to go to site and check/re
place the RET unit.
================================================================================
===================
Faulty RU
moshell Uxxxx *log onto the node
lt all *load all Managed Objects
alt *show current alarms
lga | grep RbsSubrack=RU1,RbsSlot=x *see if the RU has been inter-failing
cabx *LED status will indicate what board is faulty
mom AuxPlugInUnit led *description of LED status
st plug *get the proxy number of the faulty unit
acl xxx *check what action you can perform on the proxy number
acc xxx restartAuxUnit *try restart the RU
================================================================================
=======================
Power
>get . power
change power on confoutputpower
> set SectorEquipmentFunction=S1 confoutputpower 40
================================================================================
=======================
How to check eNB parameters
You need to dump the kget file from eNB
> l+ filenam
> kget all
>lKget file will be stored in the location of current directory
Compare two eNB parameters
Take kget dump from eNB1, call it kget_eNB1.log
Moshell into eNB2
Do: diff . Kget_eNB1.log

================================================================================
======================================================
RNC
UtranCell_NbapReconfigurationFailure:
RNC Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms ->U
tranCell_NbapReconfigurationFailure
RBS does not provide the configured output power due to some internal hardware p
roblems. Check the RBS for any HW faults, generally with the MCPA units.
RNC:
moshell XXRNCX *log onto the RNC
lt all *load all Managed Objects
alt *show current alarms
lst .xxxx *show status of channels
get cell=xxxx maximumTransmissionPower *this is a set value on the RNC
RNC will internally set a reference value representing the previously configured
maximumTransmissionPower in the cell.
An alarm will be issued if the RBS reports a degradation of itsmaxPowerCapDl bel
ow 2dB.
RBS:moshell Uxxxx *log onto the node
lt all *load all Managed Objects
alt *show current alarms and confirm what sector is affected
cabx *will show you what MCPA is faulty if you check the LED status
get cell maxDlPowerCapability *the sector with the faulty MCPA will have a lower
value
st plug *get the proxy number of the MCPA to be restarted
lpr McpaSubrack=x,RbsSlot=x,AuxPlugInUnit=1 *also used to get the proxy number o
r the MCPA
acl xxx *check what action you can perform on the proxy number
acc xxx restartAuxUnit *try restart the MCPA
get cell maxDlPowerCapability *confirm the value has changed
this value is calcula
ted by the RBS
If the alarm does not clear the RE will need to go to site and change the faulty
MCPA.
================================================================================
============================================================
no traffic
power failure
transmission
check temperature
>cab
RRU fan failure wilL heat RRU and shuts down RRU
block RRU
>st ru
>lbl <ru proxy>
restart ru
>acl <proxy>
>acc <proxy> <action>
unblock ru
>st ru
>debl <proxy>
================================================================================

===============================================================
RNC
UtranCell_NbapReconfigurationFailure:
RNC Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms ->U
tranCell_NbapReconfigurationFailure
RBS does not provide the configured output power due to some internal hardware p
roblems. Check the RBS for any HW faults, generally with the MCPA units.
RNC:
moshell XXRNCX *log onto the RNC
lt all *load all Managed Objects
alt *show current alarms
lst .xxxx *show status of channels
get cell=xxxx maximumTransmissionPower *this is a set value on the RNC
RNC will internally set a reference value representing the previously configured
maximumTransmissionPower in the cell.
An alarm will be issued if the RBS reports a degradation of itsmaxPowerCapDl bel
ow 2dB.
RBS:moshell Uxxxx *log onto the node
lt all *load all Managed Objects
alt *show current alarms and confirm what sector is affected
cabx *will show you what MCPA is faulty if you check the LED status
get cell f *the sector with the faulty MCPA will have a lower value
st plug *get the proxy number of the MCPA to be restarted
lpr McpaSubrack=x,RbsSlot=x,AuxPlugInUnit=1 *also used to get the proxy number o
r the MCPA
acl xxx *check what action you can perform on the proxy number
acc xxx restartAuxUnit *try restart the MCPA
get cell maxDlPowerCapability *confirm the value has changed
this value is calcula
ted by the RBS
If the alarm does not clear the RE will need to go to site and change the faulty
MCPA.
================================================================================
=========================
RaxDeviceGroup_GeneralSwError:
RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms ->
GeneralSwError
This alarm can be sent from all Device Groups, all Device Sets, and all Devices.
The RBS EM identifie
swhich Managed Object (MO) is issuing the alarm. The likely causes of this alarm
are the following:
A software fault
An incorrect version of the software
A faulty configuration, depending on a software error (only when RruDeviceGroup iss
ues thealarm)In this case it is the RAX board that has the problem.
RBS:
moshell Uxxxx *log onto the node
lt all *load all Managed Objects
alt *show current alarms
cab *confirm the RAX boards on the site
st plug *check the state of the RAX boards
acl xxx *check what action you can perform on the board using the proxy number
acc xxx manualRestart *try restart the board