3g alarm handling guide_moshell commands

Alarm Handling Guideline

MTN

Alarm Handling Guideline

Using Moshell Commands

VSWR COMMAND FOR 3000SR ================Lh asc dbg vswr 0 get k

VSWR COMMAND FOR 6000SR==================Lh ru fui get vswr

ContentsINTRODUCTION:3ANTENNA/ASC/RET:3AuxPlugInUnit_CommunicationLostWithAsc:3AuxPlugInUnit_CommunicationLostWithRet:3TmaDevice_LnaDegraded:3TmaDevice_LnaFailure:3RetDeviceSet_RetFailure:3RetDevice_RetFailure:3RetDevice_ElectricalAntennaTiltOutOfRange:3AscDeviceGroup_GeneralHWError:3AntennaBranch_AntennaProblemInBranchA:3AntennaBranch_AntennaProblemInBranchB:3AntennaBranch_FeederCurrentTooLowInBranchA3AntennaBranch_FeederCurrentTooLowInBranchB3AntennaBranch_FeederCurrentTooHighInBranchA3AntennaBranch_FeederCurrentTooHighInBranchB3PLUG IN UNIT:3FcuDeviceGroup_NumberOfHwEntitiesMismatch:3FanDeviceGroup_LeftFanSpeedTooLow:3AuxPlugInUnit_PiuConnectionLost:3TpaDevice_AmplificationError3RuDeviceGroup_GammaUplinkFailure:3Plug-In Unit General Problem3RaxDeviceGroup_GeneralSwError:3TxDeviceGroup_GeneralSwError:3RaxDeviceGroup_GeneralHwError:3LICENSE ISSUES:3License Key File Fault:3NodeBFunction_16QamLicenseNotValid:3Password File Fault:3UpLinkBaseBandPool_ULHWLessThanULCapacity:3DownLinkBaseBandPool_DLHWLessThanDLCapacity:3NodeBFunction_DlHwUsageExceedsDlLicenseLevel:3NodeBFunction_UlHwUsageExceedsUlLicenseLevel:3TRANSMISSION:3Loss of Tracking:3Loss of Synch Reference Redundancy:3PDH Loss of Signal:3PDH Loss of Frame:3Loss of Cell Delineation on IMA Link:3Remote Defect Indication on IMA Link:3IMA Link Reception Unusable at Far End:3IMA Link Reception Misconnected:3IMA Group Insufficient Links:3IMA Group Insufficient Links at Far End:3Heartbeat Failure:3MISCELLANEOUS:3Carrier_RejectSignalFromHardware3NbapCommon_Layer3SetupFailure:3RNC:3UtranCell_NbapReconfigurationFailure:3NbapDedicated_RncRbsControlLinkDown:3UtranCell_ServiceUnavailable:3UtranCell_ExternalResourceUnavailable:3UtranCell_NbapMessageFailure:3EXTRA NOTES:3MTN Configuration Types3RBS 32023SMOKE Text Analysis3Node B Restart Procedure3License Issues on Node B3USEFUL Commands:3Checking Performance:3Locking and Unlocking site on RNC:3Miscellaneous:3

INTRODUCTION:

This alarm guide is to help assist in clearing alarms on the RNC and RBS using MOSHELL commands. Not all cases will be the same. A few things to note for all alarms are as follows:

1) Ensure that there are no existing REFS open for the site either with SMC or BSS.

2) Refer to the ALEX Documentation. This will give you a full and clear understanding of the alarm you are dealing with.

3) Acknowledge the alarm in the OSS Alarm List Viewer.

4) Check all associated alarms on RNC and RBS. Check the history of the alarm taking note if it is a re-occurring alarm. (lga | grep )

5) Use the guidelines below to clear the alarm.

6) Once alarm has been cleared confirm the site is carrying traffic as normal.

ANTENNA/ASC/RET:AuxPlugInUnit_CommunicationLostWithAsc:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> CommunicationLostWithAsc

This alarm will generally require an RE to go to site. Communication with the ASC/RET is lost. The consequence of this alarm is that planning/optimisation will be unable to make a tilt change to the affected sector. Connection with the ASC will need to be restored on site or a replacement ASC will be needed.

If the alarm is inter-failing or re-occurring, the best solution is to swap out the ASC.

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarmslga | grep AuxPlugInUnit_CommunicationLostWithAsc *show history of current alarmget radio no *confirm if node is carrying trafficst plug *print state of all plug in unitsget xxx *do a get on the disabled proxy numberacl xxx *check what action you can perform on the proxy numberacc xxx restartAuxUnit *try restart the ASC/RET using the proxy number

RNC:moshell XXRNCX *log onto the RNClt all *load all Managed Objectsalt *show current alarmslst .xxxx *show status of channels

AuxPlugInUnit_CommunicationLostWithRet:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> CommunicationLostWithRet

This alarm will generally require an RE to go to site. Communication with the ASC/RET is lost. The consequence of this alarm is that planning/optimisation will be unable to make a tilt change to the affected sector. Connection with the RET will need to be restored on site or a replacement ASC will be needed.

If the alarm is inter-failing or re-occurring, the best solution is to swap out the RET.

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarmslga | grep AuxPlugInUnit_CommunicationLostWithRet *show history of current alarmget radio no *confirm if node is carrying trafficst plug *print state of all plug in unitsget xxx *do a get on the disabled proxy numberacl xxx *check what action you can perform on the proxy numberacc xxx restartAuxUnit *try restart the ASC/RET using the proxy number

RNC:moshell XXRNCX *log onto the RNClt all *load all Managed Objectsalt *show current alarmslst .xxxx *show status of channelsTmaDevice_LnaDegraded:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> LnaDegraded

This alarm is issued by the TmaDevice Managed Object (MO) when one of the two transistors amplifying the RF signals in the Antenna System Controller (ASC) or the AISG/3GPP Tower Mounted Amplifier (ATMA) fails. It indicates that the LNA gain in one of the branches on the ASC has degraded. The UL signal will pass, but with decreased level.

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms and confirm what sector is affectedst plug *print state of all plug in unitslpr SectorAntenna=x,AuxPlugInUnit=x *shows associated equipment with the ASCacl xxx *check what action you can perform on the ASCacc xxx restartAuxUnit *try restart the ASC/RET using the proxy number

If the alarm does not clear after restarting the ASC an RE will be required to visit the site and replace the ASC.TmaDevice_LnaFailure:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> LnaFailure

The fault is located in the Low Noise Amplifier (LNA), which amplifies the RF signals in the receiver (RX) chain. When the transistors in one branch have failed, the cell is able to carry traffic as long as the other branch works, but the RX chain performance is degraded. The LNA gain in one of the branches in the ASC is lost.

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms and confirm what sector is affectedst plug *print state of all plug in unitslpr SectorAntenna=x,AuxPlugInUnit=x *shows associated equipment with the ASCget xxx *use this to show more information about the plug in unitacl xxx *check what action you can perform on the ASCacc xxx restartAuxUnit *try restart the ASC/RET using the proxy number

If the alarm does not clear after restarting the ASC an RE will be required to visit the site and replace the ASC.

RetDeviceSet_RetFailure:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> RetFailureThis alarm is issued by the RetDevice or RetDeviceSet Managed Objects (MO) when the Remote Electrical Tilt Unit (RETU) malfunctions. The RETU is used to tilt the antenna according to the specified antenna tilt configuration parameters in the RET profile. The causes of the alarm are: A faulty RETU The RETU arm is unable to move for environmental reasons, for example, antenna icing Antenna and RETU not installed

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms and confirm what sector is affectedlpr SectorAntenna=x,AuxPlugInUnit=2 get xxx *using the proxy number from the above command will show the state of the RetDeviceSetacl xxx *check what action you can perform on the proxy numberacc 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/replace the RET unit.

RetDevice_RetFailure:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> RetFailureThis alarm is issued by the RetDevice or RetDeviceSet Managed Objects (MO) when the Remote Electrical Tilt Unit (RETU) malfunctions. The RETU is used to tilt the antenna according to the specified antenna tilt configuration parameters in the RET profile. The causes of the alarm are: A faulty RETU The RETU arm is unable to move for environmental reasons, for example, antenna icing Antenna and RETU not installed

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms and confirm what sector is affectedlpr SectorAntenna=x,AuxPlugInUnit=2 get xxx *using the proxy number from the above command will show the state of the RetDeviceSetacl xxx *check what action you can perform on the proxy numberacc 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/replace the RET unit.RetDevice_ElectricalAntennaTiltOutOfRange:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> ElectricalAntennaTiltOutOfRangeThis alarm is issued by the RetDevice Managed Object when the electrical antenna tilt is out of range. The electrical tilt on the site is set to a value that the RET and antenna does not support.RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms and confirm what sector is affectedget ret elec *shows the current electrical tilt settings on the sectorsget retdevice tilt *shows the max and min tilt supported by the ret devicelpr SectorAntenna=x,AuxPlugInUnit=2 get xxx *using the proxy number from the above command will show the state of the RetDeviceSetacl xxx *check what action you can perform on the proxy numberacc xxx restartAuxUnit *try restart the RET using the proxy number

If restarting the RET does not clear the alarm confirm with Planning/Optimisation that the Antenna Type is correct:get sector antennatype *shows the antenna type for each sectorIf the alarm still persists an RE will need to go to site and check/replace the RET Unit.AscDeviceGroup_GeneralHWError:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> GeneralHWError

This alarm is issued by the ASC. It indicates that the ASC is faulty and needs to be restarted or replaced.

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms and confirm what sector is affectedlpr SectorAntenna=x,AuxPlugInUnit=1 acl xxx *check what action you can perform on the proxy numberacc xxx restartAuxUnit *try restart the ASC using the proxy number

If the alarm does not clear after restarting the ASC an RE will need to go to site and investigate/replace the ASC.AntennaBranch_AntennaProblemInBranchA:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> AntennaProblemInBranchA

This alarm is issued by the AntennaBranch Managed Object (MO) when one of the following units is faulty or a cable is faulty or disconnected: ASC Antenna Jumper Cable

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms and confirm what sector is affectedlga | grep AntennaBranch_AntennaProblemInBranchA *shows history of alarmst plug *check the current status of the ASC/RETlst ret *check the current status of the ASC/RETlst asc *check the current status of the ASC/RETacl xxx *check what action you can perform on the ASC using the proxy numberacc xxx restartAuxUnit *try restart the ASC/RET

NOTE:Equipment=1,SectorAntenna=x,AuxPlugInUnit=1 *ASCEquipment=1,SectorAntenna=x,AuxPlugInUnit=2 *RET

cabx *get the port number of the ASC for the affected sector

===============================================================================================SMN APN PORT BOARD GREEN YELLOW RED PRODUCT NR =============================================================================================== 0 12 port_0_dev_4 RU21 steady 16hz off KRC 118 16/1 0 12 port_0_dev_4 FU12 ON 16Hz OFF KRC 118 17/1 0 12 port_1_dev_10 ASC steady 16hz off KRY 112 42/3 0 12 port_4_dev_5 RU21 steady 16hz off KRC 118 16/1 0 12 port_4_dev_5 FU12 ON 16Hz OFF KRC 118 17/1 0 12 port_5_dev_12 ASC steady 16hz off KRY 112 42/3 0 12 port_8_dev_6 RU21 steady 16hz off KRC 118 16/1 0 12 port_8_dev_6 FU12 ON 16Hz OFF KRC 118 17/1 0 12 port_9_dev_14 ASC steady 16hz off KRY 112 42/3 -----------------------------------------------------------------------------------------------

lhsh 001200/port_1_dev_10 asc vswr *prints the VSWR value for the Antenna Branchlh asc asc vswr *command to show VSWR for all sectors

If the above commands dont work try:lh asc dbg vswr 0 get -k

This command gives you the return loss value which can be converted to the desired VSWR value using the following link:http://www.soontai.com/cal_rtvswr.html

Acceptable value for VSWR should be < 1.5. If the value is higher than this an RE will need to go to site and investigate/sweep the affected Antenna Branch.AntennaBranch_AntennaProblemInBranchB:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> AntennaProblemInBranchB

This alarm is issued by the AntennaBranch Managed Object (MO) when one of the following units is faulty or a cable is faulty or disconnected: ASC Antenna Jumper Cable

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms and confirm what sector is affectedlga | grep AntennaBranch_AntennaProblemInBranchA *shows history of alarmst plug *check the current status of the ASC/RETlst ret *check the current status of the ASC/RETlst asc *check the current status of the ASC/RETacl xxx *check what action you can perform on the ASC using the proxy numberacc xxx restartAuxUnit *try restart the ASC/RET

NOTE:Equipment=1,SectorAntenna=x,AuxPlugInUnit=1 *ASCEquipment=1,SectorAntenna=x,AuxPlugInUnit=2 *RET

cabx *get the port number of the ASC for the affected sector

===============================================================================================SMN APN PORT BOARD GREEN YELLOW RED PRODUCT NR =============================================================================================== 0 12 port_0_dev_4 RU21 steady 16hz off KRC 118 16/1 0 12 port_0_dev_4 FU12 ON 16Hz OFF KRC 118 17/1 0 12 port_1_dev_10 ASC steady 16hz off KRY 112 42/3 0 12 port_4_dev_5 RU21 steady 16hz off KRC 118 16/1 0 12 port_4_dev_5 FU12 ON 16Hz OFF KRC 118 17/1 0 12 port_5_dev_12 ASC steady 16hz off KRY 112 42/3 0 12 port_8_dev_6 RU21 steady 16hz off KRC 118 16/1 0 12 port_8_dev_6 FU12 ON 16Hz OFF KRC 118 17/1 0 12 port_9_dev_14 ASC steady 16hz off KRY 112 42/3 -----------------------------------------------------------------------------------------------

lhsh 001200/port_1_dev_10 asc vswr *prints the VSWR value for the Antenna Branchlh asc asc vswr *command to show VSWR for all sectors

If the above commands dont work try:lh asc dbg vswr 0 get -k

This command gives you the return loss value which can be converted to the desired VSWR value using the following link:http://www.soontai.com/cal_rtvswr.html

Acceptable value for VSWR should be < 1.5. If the value is higher than this an RE will need to go to site and investigate/sweep the affected Antenna Branch.AntennaBranch_FeederCurrentTooLowInBranchARBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> FeederCurrentTooLowInBranchAThis alarm is issued by the AntennaBranch Managed Object (MO) when one of the following units is faulty or a cable is faulty or disconnected: ASC RET Antenna Jumper Cable

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms and confirm what sector is affectedlga | grep AntennaBranch_FeederCurrentTooLowInBranchA *shows history of alarmst plug *check the current status of the ASClst ret *check the current status of the ASC/RETlst asc *check the current status of the ASC/RET if disabled RE will need to attendacl xxx *check what action you can perform on the ASC using the proxy numberacc xxx restartAuxUnit *try restart the ASC

If no issues are seen with the ASC and the alarm still persists an RE will need to go to site and investigate any loose feeder connections.

NOTE:Some other parameters to checkget antennabranch supervision *Value of 0 implies no Antenna Supervision.mom . antennaSupervisionThreshold *description of parameterAntennaBranch_FeederCurrentTooLowInBranchBRBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> FeederCurrentTooLowInBranchBThis alarm is issued by the AntennaBranch Managed Object (MO) when one of the following units is faulty or a cable is faulty or disconnected: ASC RET Antenna Jumper Cable



NOTE:Some other parameters to checkget antennabranch supervision *Value of 0 implies no Antenna Supervision.mom . antennaSupervisionThreshold *description of parameterAntennaBranch_FeederCurrentTooHighInBranchARBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> FeederCurrentTooHighInBranchAThis alarm is issued by the AntennaBranch Managed Object (MO) when one of the following units is faulty or a cable is faulty or disconnected: ASC RET Antenna Jumper Cable



NOTE:Some other parameters to checkget antennabranch supervision *Value of 0 implies no Antenna Supervision.mom . antennaSupervisionThreshold *description of parameterAntennaBranch_FeederCurrentTooHighInBranchBRBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> FeederCurrentTooHighInBranchBThis alarm is issued by the AntennaBranch Managed Object (MO) when one of the following units is faulty or a cable is faulty or disconnected: ASC RET Antenna Jumper Cable



NOTE:Some other parameters to checkget antennabranch supervision *Value of 0 implies no Antenna Supervision.mom . antennaSupervisionThreshold *description of parameter

PLUG IN UNIT:FcuDeviceGroup_NumberOfHwEntitiesMismatch:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> NumberOfHwEntitiesMismatch

This alarm is issued by the FcuDeciceGroup MO when there are too few fans in operation. It could be the cause of a faulty or disconnected fan unit cable or too few fans installed on site.

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarmslpr AuxPlugInUnit=2,FcuDeviceGroup=1get xxx *using proxy number from above command will show the number of Fans defined on the site get . numberoffangroups

An RE will need to go to site and confirm that the number of Fans installed on site matches what is configured. Fan unit cables will also need to be checked.

FcuDeviceGroup_FanFailure:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> FanFailure

This alarm is issued by the FcuDevice Managed Object when there is a problem with one or more of the fans controlled by the Fan Control Unit

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarmspr AuxPlugInUnit=2acl xxx *shows what action you can perform on the Fan Control Unit (FCU)acc xxx restartAuxUnit *restarts the FCUalt *confirm the alarm has cleared

If the alarm does not clear after restarting the FCU and RE will need to attend on site.FanDeviceGroup_LeftFanSpeedTooLow:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> LeftFanSpeedTooLowThe LeftFanSpeedTooLow alarm indicates that there are faults in one or more of following units: BaseBand (BB) Subrack Fan Unit Radio Frequency (RF) Subrack Fan Unit Multi-Carrier Power Assembly (MCPA) Subrack Fan Unit Power Subrack (PS) Fan Unit RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarmslga | grep FanDeviceGroup_LeftFanSpeedTooLow *show history of current alarmlpr Subrack=2,AuxPlugInUnit=1st plug *print state of all plug in unitsget xxx *using proxy number from above command will show the status of the FANcabx *shows the led status of the fan unitmom AuxPlugInUnit led *description of LED statusacl xxx *check what action you can perform on the proxy numberacc xxx restartAuxUnit *try restart the plug in unit

A red LED showing a steady light indicates a faulty FAN. If the alarm does not clear after restarting the unit an RE is required to attend the site and replace the Fan UnitAuxPlugInUnit_PiuConnectionLost:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> PiuConnectionLost

This alarm is issued by the AuxPlugInUnit Managed Object (MO) when communication between one of the Auxiliary Units (AU) and its device is lost.Use ALEX to check what actions to perform on the various types of Plug In Units.

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarmslga | grep AuxPlugInUnit_PiuConnectionLost *show the history of the current alarmst plug *print state of all plug in unitslpr AuxPlugInUnit=x *shows associated equipment with plug in unitget xxx *use this to show more information about the plug in unitacl xxx *check what action you can perform on the proxy numberacc xxx restartAuxUnit *try restart the plug in unit

If the alarm does not clear an RE will be required to visit the site.TpaDevice_AmplificationErrorRBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> AmplificationError

This alarm is issued by the TpaDevice Managed Object (MO) when there is a fault affecting the Transmit Power Amplifier (TPA) in a Multicarrier Power Amplifier (MCPA) or a Radio Unit (RU).RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms and confirm what sector is affectedcabx *will show you what MCPA is faulty if you check the LED statusget cell maxDlPowerCapability *the sector with the faulty MCPA will have a lower valuest plug *get the proxy number of the MCPA to be restartedlpr McpaSubrack=x,RbsSlot=x,AuxPlugInUnit=1 *also used to get the proxy number or the MCPAacl xxx *check what action you can perform on the proxy numberacc xxx restartAuxUnit *try restart the MCPAget cell maxDlPowerCapability *confirm the value has changed this value is calculated by the RBS

RNC:moshell XXRNCX *log onto the RNClt all *load all Managed Objectsalt *show current alarmslst .xxxx *show status of channelsget cell=xxxx maximumTransmissionPower *this is a set value on the RNCThis alarm is also associated with the following alarm on the RNC:UtranCell_NbapReconfigurationFailure

If the alarm does not clear the RE will need to go to site and change the faulty MCPA.RuDeviceGroup_GammaUplinkFailure:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> GammaUplinkFailure

This alarm is issued by the Managed Object RuDeviceGroup. The alarm indicates a failure in one or more of the units in the gamma uplink path. Cables carry the gamma link between the following: the Baseband Interface (BBIF) and Radio Frequency Interface (RFIF) boards; the Optical Baseband Interface (OBIF) board and the RRU; the Radio Unit Interface (RUIF) and the Radio Unit (RU). Between all other boards, the physical connections are made through the backplane of the boards.

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarmslga | grep RbsSubrack=RU1,RbsSlot=x *see if the RU has been inter-failingcabx *LED status will indicate what board is faultymom AuxPlugInUnit led *description of LED statusst plug *get the proxy number of the faulty unitacl xxx *check what action you can perform on the proxy numberacc xxx restartAuxUnit *try restart the RU

If the alarm is still present after restarting the unit lock the sector on the RNC until the RE can attend and replace the RU.

NOTE: Identifying the affected sector:RbsSubrack=RU1/FU1,RbsSlot=2 A sectorRbsSubrack=RU1/FU1,RbsSlot=4 B sectorRbsSubrack=RU1/FU1,RbsSlot=6 C sector

If the Radio Unit is faulty the following alarm will be present on the RNC for the disabled sectorUtranCell_NbapMessageFailure call_establishment_error UtranCell=xxxx

RNC:moshell XXRNCX *log onto the RNClt all *load all Managed Objectsalt *show current alarmslst .xxxx *show status of channelslbl cell=xxxxA1 *lock the sector affected by the faulty RUldeb cell=xxxxA1 *once the RU has been replaced unlock the sector Plug-In Unit General ProblemRBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> Plug-In Unit General Problem

The alarm is issued when all defined recovery attempts are performed for the PIU or contact with the PIU is lost for at least five minutes.

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms lga | grep Subrack=1,Slot=8,PlugInUnit=1 *check the history of the alarmcab *confirm if there is contact or not with the PIUst plug *check the state of PIUacl xxx *check what action you can perform on the PIU using the proxy numberacc xxx manualRestart *try restart the PIU

If theres no contact with the board and the alarm does not clear an RE will be required to go to site and do a hard reset or replace the board.RaxDeviceGroup_GeneralSwError:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> GeneralSwErrorThis alarm can be sent from all Device Groups, all Device Sets, and all Devices. The RBSEM identifies which 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 issues the alarm)In this case it is the RAX board that has the problem.RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms cab *confirm the RAX boards on the sitest plug *check the state of the RAX boardsacl xxx *check what action you can perform on the board using the proxy numberacc xxx manualRestart *try restart the board

Check that the alarm has cleared. If the alarm is still present an RE will need to go to site and do a hard reset or change the RAX board. Confirm the site is carrying traffic.TxDeviceGroup_GeneralSwError:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> GeneralSwErrorThis alarm can be sent from all Device Groups, all Device Sets, and all Devices. The RBSEM identifies which 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 issues the alarm)In this case it is the TX board that has the problem. As a consequence the capacity of the site is decreased.RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms cab *confirm the TX boards on the sitest plug *check the state of the TX boardsacl xxx *check what action you can perform on the board using the proxy numberacc xxx manualRestart *try restart the board

Check that the alarm has cleared. If the alarm is still present an RE will need to go to site and do a hard reset or change the TX board. Confirm the site is carrying traffic.RaxDeviceGroup_GeneralHwError:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> GeneralHwErrorThis alarm can be sent from all Device Groups, all Device Sets, and all Devices. The RBSEM identifies which Managed Object (MO) is issuing the alarm. This alarm indicates that the component is faulty and my need to be replaced. The following alarm UplinkBaseBandPool_UlHwLessThanUlCapacity will also be present on the RBS. This indicates that there is less hardware on the site than is licensed for as a result of the faulty RAX board.In this case it is the RAX board that has the problem.RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms cab *confirm the RAX boards on the sitest plug *check the state of the RAX boardsacl xxx *check what action you can perform on the board using the proxy numberacc xxx manualRestart *try restart the board

Check that the alarm has cleared. If the alarm is still present an RE will need to go to site and do a hard reset or change the RAX board. Confirm the site is carrying traffic.

LICENSE ISSUES:License Key File Fault:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> License Key file Fault

This alarm is triggered when no valid License Key file (LKF) is found on the node. The LKF may be corrupt or have been deleted.

When investigating this alarm please ensure that there are no open refs (with BSS) for the site. The site could be in integration and the license may not be loaded yet.

CASE 1:BSS are working on the site and license has not been loaded yet.

CASE 2:No contact with the Node. Check for alarms on transmission. If alarms are present escalate to either Transmission department or Telkom as necessary.CASE 3:Escalate to BSS to install License Key File.NOTE: For extra notes on installing a LKF see document License Issues on Node B. NodeBFunction_16QamLicenseNotValid:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> 16QamLicenseNotValidThis alarm is triggered either when the 16QAM modulation license has expired or the 16QAM modulation license has been removed. RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarmsget . license *confirm the license installed on the nodeget . 16qam *shows the feature and license state on the nodemom . featureState16Qam *gives an explanation of the featurest pp *checks the number of E1s on the site

NOTE: Check the MTN Configuration document to confirm what license should be installed on the site based on the number of E1s/Hardware. Also confirm with Optimisation what license should be installed on the Node.

If the featurestate16Qam is ACTIVATED and the license state is DISABLED it will result in the alarm. To clear the alarm set the featurestate16Qam to DEACTIVATED.

set NodeBFunction featureState16Qam 0 *Sets the feature to DISABLED since no license is installed on the sitePassword File Fault:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> Password File Fault

The alarm indicates that the password required at Security Level 1 and 2, for user access via Telnet, SSH, FTP, SFTP or a serial port, was never set or that the locally stored passwd file has been found to be corrupt.

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarmspasswd; rbs ; rbs *resets the password on the Node Balt *confirm the alarm has clearedUpLinkBaseBandPool_ULHWLessThanULCapacity:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> ULHWLessThanULCapacityThis alarm is triggered when the installed license key file defines a capacity that is greater than the available capacity for DCH given by the installed Random Access and Receiver (RAX) boards. It can also be triggered due to a HW failure on one of the RAX boards which decreases the available capacity below the capacity defined by the license key.A faulty RAX board (see alarm: RaxDeviceGroup_GeneralSwError/ RaxDeviceGroup_GeneralHwError) is the general cause of this alarm however if all RAX boards are operational and showing no errors this alarm will need to be escalated to Planning/Optimisation to consider increasing the UL capacity on the site.RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms get . license *shows the licensed capacity for Channel Elements in the Uplinkget nodebfunction ava *shows the available Channel Elements in the Uplink based on the available RAX boardscab *confirm the RAX boards on the sitest plug *check the state of the RAX boards

NOTE:Use the Product Number (from the cab printout) to search the ALEX document (Product Overview -> Compatibilities for Hardware and Software) to confirm the number of Channel Elements supported by the RAX board.

acl xxx *check what action you can perform on the board using the proxy numberacc xxx manualRestart *try restart the board

If the RAX board restarts without any more alarms confirm that the ULHWLessThanULCapacity alarm has also cleared.

alt *confirm alarm has clearedget nodebfunction ava *the available Channel Elements should now match the licensed capacity

If the fault on the RAX board does not clear after a restart an RE will need to go to site and do a hard reset or replace the RAX board. DownLinkBaseBandPool_DLHWLessThanDLCapacity: RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> DLHWLessThanDLCapacityThis alarm is triggered when the installed license key file defines a capacity that is greater than the available capacity for DCH given by the installed Transmitter (TX) boards. It can also be triggered due to a HW failure on one of the TX boards which decreases the available capacity below the capacity defined by the license key.If all TX boards are operational and showing no errors this will need to be escalated to Planning/Optimisation to consider increasing the DL capacity on the site.RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms get . license *shows the licensed capacity for Channel Elements in the Downlinkget nodebfunction ava *shows the available Channel Elements in the downlink based on the available TX boardscab *confirm the TX boards on the sitest plug *check the state of the TX boards

NOTE:Use the Product Number (from the cab printout) to search the ALEX document (Product Overview -> Compatibilities for Hardware and Software) to confirm the number of Channel Elements supported by the TX board. NodeBFunction_DlHwUsageExceedsDlLicenseLevel: RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> DlHwUsageExceedsDlLicenseLevelThis alarm is issued by the NodeBFunction Managed Object (MO) when the licensed limit has been reached in the RBS. The cause of the alarm is that the licensed Channel Element (CE) level is reached in the RBS.

NOTE:When a site uses more Channel Element capacity than is licensed a grace period will be triggered along with this alarm. Once this grace period expires the site will be limited to the licensed capacity and the alarm will be cleared

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms get . license *shows the licensed capacity for Channel Elements get nodeb ava *shows the available Channel Elements in the uplink/downlink based on the installed HWget . grace *shows the grace period left for UL and DLget . limited *shows if the site is limited to the licensed capacityExample 1:In the example below there are 4 days grace period left. Once dlGraceTimeLeft reaches 0 the parameter dlLimitedByLicenseLevel will be set to True. A value of -1 for ulGraceTimeLeft indicates that the grace period has not yet been triggered for the UL.

U2575-Ooseinde_VC> get . grace

100723-12:37:46 10.205.75.161 8.0c RBS_NODE_MODEL_M_1_8 stopfile=/tmp/10008==========================================================================================MO Attribute Value==========================================================================================NodeBFunction=1 dlGraceTimeLeft 4NodeBFunction=1 ulGraceTimeLeft -1==========================================================================================

U2575-Ooseinde_VC> get . limited

100723-12:37:55 10.205.75.161 8.0c RBS_NODE_MODEL_M_1_8 stopfile=/tmp/10008======================================================================================MO Attribute Value======================================================================================NodeBFunction=1 dlLimitedByLicenseLevel falseNodeBFunction=1 ulLimitedByLicenseLevel false======================================================================================

Example 2:In this example the UL and DL grace time has expired (showing a value of 0) and the parameter ulLimitedByLicenseLevel and dlLimitedByLicenseLevel are set to True.

U0595-Umgeni_Heights> get . grace100723-10:50:26 10.209.84.1 8.0c RBS_NODE_MODEL_M_1_8 stopfile=/tmp/25336=======================================================================================MO Attribute Value=======================================================================================NodeBFunction=1 dlGraceTimeLeft 0NodeBFunction=1 ulGraceTimeLeft 0=======================================================================================

U0595-Umgeni_Heights> get . limited

100723-10:50:34 10.209.84.1 8.0c RBS_NODE_MODEL_M_1_8 stopfile=/tmp/25336========================================================================================MO Attribute Value========================================================================================NodeBFunction=1 dlLimitedByLicenseLevel trueNodeBFunction=1 ulLimitedByLicenseLevel true========================================================================================

In order for this alarm to clear you must wait for the grace period to expire. One other way of clearing the alarm is to upgrade the license file to match the available Channel Elements. However this will be up to the planner/optimisation engineer to decide.

In most cases this alarm can be as a result of a spike in CE usage after a site is brought on air. All users will attempt to do a location update and use up all resources causing this spike.

NodeBFunction_UlHwUsageExceedsUlLicenseLevel:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> UlHwUsageExceedsUlLicenseLevelThis alarm is issued by the NodeBFunction Managed Object (MO) when the licensed limit has been reached in the RBS. The cause of the alarm is that the licensed Channel Element (CE) level is reached in the RBS.

NOTE:When a site uses more Channel Element capacity than is licensed a grace period will be triggered along with this alarm. Once this grace period expires the site will be limited to the licensed capacity and the alarm will be cleared

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms get . license *shows the licensed capacity for Channel Elements get nodeb ava *shows the available Channel Elements in the uplink/downlink based on the installed HWget . grace *shows the grace period left for UL and DLget . limited *shows if the site is limited to the licensed capacityExample 1:In the example below there are 2 days grace period left. Once ulGraceTimeLeft reaches 0 the parameter ulLimitedByLicenseLevel will be set to True. A value of -1 for dlGraceTimeLeft indicates that the grace period has not yet been triggered for the DL.

U4574-Elukhanyisweni_High_School> get . grace

100723-11:02:03 10.201.89.97 8.0c RBS_NODE_MODEL_M_1_8 stopfile=/tmp/25511===============================================================================================MO Attribute Value===============================================================================================NodeBFunction=1 dlGraceTimeLeft -1NodeBFunction=1 ulGraceTimeLeft 2===========================================================================================

U4574-Elukhanyisweni_High_School> get . limited

100723-11:02:42 10.201.89.97 8.0c RBS_NODE_MODEL_M_1_8 stopfile=/tmp/25511============================================================================================MO Attribute Value============================================================================================NodeBFunction=1 dlLimitedByLicenseLevel falseNodeBFunction=1 ulLimitedByLicenseLevel false============================================================================================

Example 2:In this example the UL and DL grace time has expired (showing a value of 0) and the parameter ulLimitedByLicenseLevel and dlLimitedByLicenseLevel are set to True.

U0595-Umgeni_Heights> get . grace100723-10:50:26 10.209.84.1 8.0c RBS_NODE_MODEL_M_1_8 stopfile=/tmp/25336=======================================================================================MO Attribute Value=======================================================================================NodeBFunction=1 dlGraceTimeLeft 0NodeBFunction=1 ulGraceTimeLeft 0=======================================================================================

U0595-Umgeni_Heights> get . limited

100723-10:50:34 10.209.84.1 8.0c RBS_NODE_MODEL_M_1_8 stopfile=/tmp/25336========================================================================================MO Attribute Value========================================================================================NodeBFunction=1 dlLimitedByLicenseLevel trueNodeBFunction=1 ulLimitedByLicenseLevel true========================================================================================

In order for this alarm to clear you must wait for the grace period to expire. One other way of clearing the alarm is to upgrade the license file to match the available Channel Elements. However this will be up to the planner/optimisation engineer to decide. In most cases this alarm can be as a result of a spike in CE usage after a site is brought on air. All users will attempt to do a location update and use up all resources causing this spike.

TRANSMISSION:Loss of Tracking:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> Loss of Tracking

The alarm is issued when the system clock enters "loss of tracking" mode. The value of the attribute, syncRefStatus is changed to LOSS_OF_TRACKING.

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms get 10 *prints the synchronization Managed Objectacl 10 *shows what action you can perform on the MOacc 10 resetLossOfTracking *resets loss of tracking

When prompted to Enter mo LDN: Equipment=1,Subrack=1,Slot=2,PlugInUnit=1,ExchangeTerminal=1,E1PhysPathTerm=pp1

NOTE: To see the values for syncRefStatus and syncRefActivity use the below commands:mom refstatemom refactivityLoss of Synch Reference Redundancy:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> Loss of Synch Reference Redundancy

This alarm can be triggered as a consequence of the primary alarm Loss of Tracking. As a consequence of the fault, the number of available synchronization references is reduced and there is only one left. Clearing the Loss of Tracking alarm should clear this alarm.

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms get 10 *prints the synchronization Managed Objectacl 10 *shows what action you can perform on the MOacc 10 resetLossOfTracking *resets loss of trackingWhen prompted to Enter mo LDN: Equipment=1,Subrack=1,Slot=2,PlugInUnit=1,ExchangeTerminal=1,E1PhysPathTerm=pp1

NOTE: To see the values for syncRefStatus and syncRefActivity use the below commands:mom refstatemom refactivity

PDH Loss of Signal:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> PDH Loss of SignalThis alarm is issued by an E1 on the site when the Exchange Terminal (ET) board cannot detect any signal at the input port.

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms this will indicate what E1/IMA Link the alarm has been triggered forst pp *shows the status of the E1s on the sitest ima *shows the status of the IMA linksget ima *shows what IMA Link is associated with a particular E1

E1s that are LOCKED and DISABLED they will most likely not be defined in the IMA Group and are waiting to be integrated.Check on the HS 3G Site planning page to confirm number of links that are actually completed on site.http://10.217.201.232/facts/report/Tx/DXX/8600/Planning/3G+HS+Site+Planning

If any E1/IMA Links are UNLOCKED and DISABLED use the DXX Web Reporter to check for any active alarms.http://10.200.31.30/dll/w3rt.dllLogin: ESAPassword: ESA

NOTE:To check for any errors on the E1 links use the following command:pmx e1 pm m 1

Consult with Transmission department as for the next steps to take.

PDH Loss of Frame:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> PDH Loss of FrameThis alarm is issued by an E1 on the site when the Exchange Terminal (ET) board cannot detect any signal at the input port.





Consult with Transmission department as for the next steps to take.

Loss of Cell Delineation on IMA Link:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> Loss of Cell Delineation on IMA LinkThis alarm is triggered when the node cannot extract the ATM cells from the PDH frame. If there are many similar alarms it is likely that common hardware is at fault. However if there is just one alarm, the fault is probably with one IMA link.




NOTE:To check for any errors on the E1 links use the following command:pmx e1 pm m 1 Consult with Transmission department as for the next steps to take.Remote Defect Indication on IMA Link:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms ->Remote Defect Indication on IMA Link

This alarm is triggered when the remote (far end) node has detected a transmission fault on the IMA link. This will also trigger the alarm IMA Link Reception Unusable at Far End indicating that the link at the far end has become unusable.





Consult with Transmission department as for the next steps to take. However in most cases this will need to be escalated to Telkom.

IMA Link Reception Unusable at Far End:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms ->IMA Link Reception Unusable at Far End

This alarm is triggered when the IMA link at the far end becomes unusable. It is likely that you will also see the alarm Remote Defect Indication on IMA Link for the same link indicating that the IMA link is faulty.





Consult with Transmission department as for the next steps to take. However in most cases this will need to be escalated to Telkom.IMA Link Reception Misconnected:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms ->IMA Link Reception Misconnected

This alarm is triggered when there is a configuration mismatch between two nodes. The IMA link in the receive direction is not connected to the same remote (far end) IMA unit as the other reception links in the IMA group. It is likely that you will see one or both of the following alarms: Remote Defect Indication on IMA Link, IMA Link Reception Unusable at Far End.





Consult with Transmission department as for the next steps to take. However in most cases this will need to be escalated to Telkom.

IMA Group Insufficient Links:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms ->IMA Link Insufficient LinksThis alarm is triggered when one or more of the IMA links have failed. This reduces the number of IMA Links in the IMA group and the required number of links is less than defined.RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms this will indicate what E1/IMA Link the alarm has been triggered forst pp *shows the status of the E1s on the sitest ima *shows the status of the IMA linksget ima *shows what IMA Link is associated with a particular E1get ima required *shows the required number of links needed in the IMA group

CASE 1:In the below example there are two UNLOCKED and ENABLED E1 links. However there is only 1 E1 link defined in the IMA group.

U4784-Vredenburg_WPK_Silo> st pp

100730-12:08:56 10.202.83.113 8.0c RBS_NODE_MODEL_M_1_8 stopfile=/tmp/29260===================================================================================Proxy Adm State Op. State MO=================================================================================== 110 1 (UNLOCKED) 1 (ENABLED) Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,ExchangeTerminal=1,E1PhysPathTerm=pp1 111 0 (LOCKED) 0 (DISABLED) Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,ExchangeTerminal=1,E1PhysPathTerm=pp2 114 1 (UNLOCKED) 1 (ENABLED) Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,ExchangeTerminal=1,E1PhysPathTerm=pp3===================================================================================

U4784-Vredenburg_WPK_Silo> st ima

100730-12:09:02 10.202.83.113 8.0c RBS_NODE_MODEL_M_1_8 stopfile=/tmp/29260===================================================================================Proxy Adm State Op. State MO=================================================================================== 17 0 (DISABLED) TransportNetwork=1,AtmPort=1-1-ima1 49 0 (DISABLED) TransportNetwork=1,ImaGroup=1-1-ima1 50 1 (ENABLED) TransportNetwork=1,ImaGroup=1-1-ima1,ImaLink=1===================================================================================

U4784-Vredenburg_WPK_Silo> get ima required

100730-12:22:21 10.202.83.113 8.0c RBS_NODE_MODEL_M_1_8 stopfile=/tmp/29260===================================================================================MO Attribute Value===================================================================================ImaGroup=1-1-ima1 requiredNumberOfLinks 1===================================================================================

Check on the HS 3G Site planning page to confirm the number of links that are actually completed on site.http://10.217.201.232/facts/report/Tx/DXX/8600/Planning/3G+HS+Site+Planning

In the above example BSS will be required to do an IMA upgrade and add the 2nd working link to the IMA group. You might also need to contact Transmission and confirm what the correct configuration is on the DXX.

IMA Group Insufficient Links at Far End:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms ->IMA Group Insufficient Links at Far End

This alarm is triggered when one or more of the IMA links have failed. This reduces the number of IMA Links in the IMA group and the required number of links is less than defined.RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms this will indicate what E1/IMA Link the alarm has been triggered forst pp *shows the status of the E1s on the sitest ima *shows the status of the IMA linksget ima *shows what IMA Link is associated with a particular E1get ima required *shows the required number of links needed in the IMA group

CASE 1:In the below example there are two UNLOCKED and ENABLED E1 links. However there is only 1 E1 link defined in the IMA group.

U4784-Vredenburg_WPK_Silo> st pp

100730-12:08:56 10.202.83.113 8.0c RBS_NODE_MODEL_M_1_8 stopfile=/tmp/29260===================================================================================Proxy Adm State Op. State MO=================================================================================== 110 1 (UNLOCKED) 1 (ENABLED) Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,ExchangeTerminal=1,E1PhysPathTerm=pp1 111 0 (LOCKED) 0 (DISABLED) Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,ExchangeTerminal=1,E1PhysPathTerm=pp2 114 1 (UNLOCKED) 1 (ENABLED) Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,ExchangeTerminal=1,E1PhysPathTerm=pp3===================================================================================

U4784-Vredenburg_WPK_Silo> st ima

100730-12:09:02 10.202.83.113 8.0c RBS_NODE_MODEL_M_1_8 stopfile=/tmp/29260===================================================================================Proxy Adm State Op. State MO=================================================================================== 17 0 (DISABLED) TransportNetwork=1,AtmPort=1-1-ima1 49 0 (DISABLED) TransportNetwork=1,ImaGroup=1-1-ima1 50 1 (ENABLED) TransportNetwork=1,ImaGroup=1-1-ima1,ImaLink=1===================================================================================

U4784-Vredenburg_WPK_Silo> get ima required

100730-12:22:21 10.202.83.113 8.0c RBS_NODE_MODEL_M_1_8 stopfile=/tmp/29260===================================================================================MO Attribute Value===================================================================================ImaGroup=1-1-ima1 requiredNumberOfLinks 1===================================================================================

Check on the HS 3G Site planning page to confirm the number of links that are actually completed on site.http://10.217.201.232/facts/report/Tx/DXX/8600/Planning/3G+HS+Site+Planning

In the above example BSS will be required to do an IMA upgrade and add the 2nd working link to the IMA group. You might also need to contact Transmission and confirm what the correct configuration is on the DXX.Heartbeat Failure:OSS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarm Handling Operational Instruction -> Heartbeat Failure

This alarm can be triggered when connectivity to the OSS is lost or the site has gone down due to transmission.

RBS:moshell Uxxxx *log onto the nodeIf you cannot MOSHELL to the node check for alarms on the RNC

riorda_m@uas3g3> moshell u2652

__ __ ____ _____ /\ | \/ |/ __ \ / ____| / \ | \ / | | | | (___ / /\ \ | |\/| | | | |\___ \ / ____ \| | | | |__| |____) | /_/ \_\_| |_|\____/|_____/ OSS Framework for MoShell-8.0c Checking ip contact...Not OKUnable to connect to 10.209.89.241:23Cannot connect to MO service, exiting...

RNC:moshell XXRNCX *log onto the RNClt all *load all Managed Objectsalt *show current alarmslst .xxxx *show status of channelspmx cell=xxxx pmTotNoRrcC|pmNoSystemRabRe|pmNoRabEstablish|pmNoNormalRabRel|pmNoFailedAfterAdm -m 1 *confirm if the site is carrying traffic

CASE 1 Site is operational and carrying traffic but no connection to the node:If all channels are unlocked and enabled, the site is carrying traffic and no alarms are present on the RNC escalate this fault to Transmission/IP Routing. In this case VC32 and VC33 (used for O&M connectivity) will need to be checked by Transmission. Transmission will possibly need to recreate these VCs as they are hanging.

Use the command traceroute to confirm where the problem is before escalating to Transmission. The traceroute command shows where the IP packet stops in the network, either at the DXX or IP router.

riorda_m@uas3g3> traceroute 10.204.78.145traceroute: Warning: Multiple interfaces found; using 10.217.12.16 @ ce1traceroute to 10.204.78.145 (10.204.78.145), 30 hops max, 40 byte packets 1 10.217.12.252 (10.217.12.252) 0.614 ms 0.349 ms 0.279 ms 2 10.195.17.165 (10.195.17.165) 1.043 ms 0.878 ms 0.901 ms 3 10.195.17.13 (10.195.17.13) 0.952 ms 0.816 ms 0.844 ms 4 10.90.217.5 (10.90.217.5) 1.418 ms 0.991 ms 90.119 ms 5 10.90.250.14 (10.90.250.14) 1.840 ms 6.803 ms 1.097 ms 6 10.90.204.6 (10.90.204.6) 1.317 ms 1.131 ms 0.938 ms 7 10.204.47.252 (10.204.47.252) 0.855 ms 0.859 ms 0.729 ms 8 10.204.47.230 (10.204.47.230) 1.505 ms 1.504 ms 1.940 ms 9 10.204.78.145 (10.204.78.145) 7.887 ms 7.250 ms 8.814 msriorda_m@uas3g3>

CASE 2 Site is DISABLED and there are alarms present on the RNC:If the channels on the RNC are UNLOCKED and DISABLED and there are alarms present on the RNC it is more than likely a problem on the Transmission side and will need to be escalated to TX or Telkom based on the alarms present on the DXX.

Possible RNC Alarms:NbapDedicated_RncRbsControlLinkDown transmission_error IubLink=Iub_U2652-Bay_View_Estates,NbapDedicated=1UtranCell_ServiceUnavailable unavailable UtranCell=2652A1 UtranCell_ServiceUnavailable unavailable UtranCell=2652B1 UtranCell_ServiceUnavailable unavailable UtranCell=2652C1

CASE 3 New SiteCheck in REMEDY if this is a new site. Generally a new site that is not yet fully integrated will display the Heartbeat Failure alarm as it is not yet connected on the OSS.

MISCELLANEOUS:Carrier_RejectSignalFromHardwareRBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> RejectSignalFromHardware

This alarm is triggered by the Carrier Managed Object. This alarm can be issued for the AIU/sAIU, FU, MCPA, RFIF board, RRU, RU, TRX board or the TX board. If none of the boards are faulty it could be related to a frequency configuration issue.

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarmscabx *check the equipment on the site (particularly the RU and FU)get . fqband *check the highedge and lowedge of the Antenna Branch

Contact optimisation/planning to confirm that the UARFCNs and high and low edges are set correctly. If they are set correctly restart the RU relevant to the affected sector.

st plug *shows the plug in units.acl xxx *check what action you can perform on the PIU using the proxy numberacc xxx manualRestart *try restart the PIU

NOTE: Identifying the affected sector:RbsSubrack=RU/FU, RbsSlot=2 A sectorRbsSubrack=RU/FU, RbsSlot=4 B sectorRbsSubrack=RU/FU, RbsSlot=6 C sector

RNC:moshell XXRNCX *log onto the RNClt all *load all Managed Objectsalt *show current alarmslst .xxxx *show status of channels some carriers may be disabledget cell=xxxx uarfcn *displays the DL and UL frequencies set for each carrier

The following alarm may be present on the RNC:UtranCell_NbapMessageFailureNbapCommon_Layer3SetupFailure:RBS Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> Layer3SetupFailureThis alarm is issued by the NbapCommon Managed Object. It is issued for the Node B Application Protocol (NBAP) Common. The likely cause is a communication failure between the RBS and RNC. The following alarm, UtranCell_ExternalResourceUnavailable could also be present on the RNC for the affected cells. RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms

RNC:moshell XXRNCX *log onto the RNClt all *load all Managed Objectsalt *show current alarmslst .xxxx *show status of channels all cells will be DISABLED and also NbapCommom on the IubLink========================================================================================14622 1 (UNLOCKED) 1 (ENABLED) RncFunction=1,IubLink=Iub_U2141-Adgam_Place14624 0 (DISABLED) RncFunction=1,IubLink=Iub_U2141-Adgam_Place,NodeSynch=114625 1 (UNLOCKED) 0 (DISABLED) RncFunction=1,IubLink=Iub_U2141-Adgam_Place,NbapCommon=114626 1 (UNLOCKED) 0 (DISABLED) RncFunction=1,IubLink=Iub_U2141-Adgam_Place,NbapDedicated=122656 1 (UNLOCKED) 0 (DISABLED) RncFunction=1,UtranCell=2141A122669 1 (UNLOCKED) 0 (DISABLED) RncFunction=1,UtranCell=2141A1,Hsdsch=122670 1 (UNLOCKED) 0 (DISABLED) RncFunction=1,UtranCell=2141A1,Hsdsch=1,Eul=122684 1 (UNLOCKED) 0 (DISABLED) RncFunction=1,UtranCell=2141A1,Rach=RACH22685 1 (UNLOCKED) 0 (DISABLED) RncFunction=1,UtranCell=2141A1,Pch=PCH22695 1 (UNLOCKED) 0 (DISABLED) RncFunction=1,UtranCell=2141A1,Fach=1========================================================================================

lbl Iublink_Iub_Uxxxx *block the IubLink

GERNC1> lbl Iublink=Iub_U2141===================================================================================14622 RncFunction=1,IubLink=Iub_U2141-Adgam_Place14625 RncFunction=1,IubLink=Iub_U2141-Adgam_Place,NbapCommon=114626 RncFunction=1,IubLink=Iub_U2141-Adgam_Place,NbapDedicated=1===================================================================================

ldeb Iublink_Iub_Uxxxx *deblock the IubLinklst .xxxx confirm the channels are UNLOCKED and ENABLED

Confirm the alarm has cleared on the RBS. If the alarm is still present escalate to Transmission.

RNC:UtranCell_NbapReconfigurationFailure:RNC Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> UtranCell_NbapReconfigurationFailure

RBS does not provide the configured output power due to some internal hardware problems. Check the RBS for any HW faults, generally with the MCPA units.

RNC:moshell XXRNCX *log onto the RNClt all *load all Managed Objectsalt *show current alarmslst .xxxx *show status of channelsget cell=xxxx maximumTransmissionPower *this is a set value on the RNCRNC 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 its maxPowerCapDl below 2dB.

This alarm can be associated with the following alarm on the RBS:TpaDevice_AmplificationError

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms and confirm what sector is affectedcabx *will show you what MCPA is faulty if you check the LED statusget cell maxDlPowerCapability *the sector with the faulty MCPA will have a lower valuest plug *get the proxy number of the MCPA to be restartedlpr McpaSubrack=x,RbsSlot=x,AuxPlugInUnit=1 *also used to get the proxy number or the MCPAacl xxx *check what action you can perform on the proxy numberacc xxx restartAuxUnit *try restart the MCPAget cell maxDlPowerCapability *confirm the value has changed this value is calculated by the RBS

If the alarm does not clear the RE will need to go to site and change the faulty MCPA.

NbapDedicated_RncRbsControlLinkDown:RNC Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> NbapDedicated_RncRbsControlLinkDown

This alarm is triggered when there is a temporary disturbance or interruption in the Iub link . It is also generally associated with the alarm UtranCell_ServiceUnavailable as all Utrancells will be DISABLED.

RNC:moshell XXRNCX *log onto the RNClt all *load all Managed Objectsalt *show current alarmslst .xxxx *show status of channels cells will be UNLOCKED and DISABLED

This alarms indicates a problem with Transmission. It will need to be either escalated to the Transmission department or Telkom. When this alarm is present you will be unable to Moshell onto the RBS.

Check the DXX web reporter for any current alarms.http://10.200.31.30/dll/w3rt.dllLogin: ESAPassword: ESA

Once the Transmission issue has been cleared, confirm that all cells and channels are UNLOCKED and ENABLED and the site is carrying traffic.

UtranCell_ServiceUnavailable:RNC Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> UtranCell_ServiceUnavailableThis is a secondary alarm and is triggered when there is a problem with the NBAP signalling on the Transmission link. It is associated with the alarm NbapDedicated_RncRbsControlLinkDown

RNC:moshell XXRNCX *log onto the RNClt all *load all Managed Objectsalt *show current alarmslst .xxxx *show status of channels cells will be UNLOCKED and DISABLED

This alarm could indicate a problem with Transmission. It will need to be either escalated to the Transmission department or Telkom.


UtranCell_ExternalResourceUnavailable:RNC Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> UtranCell_ExternalResourceUnavailableThis alarm is triggered by the Utrancell Managed Object. It is issued for the Node B Application Protocol (NBAP) Common. The likely cause is a communication failure between the RBS and RNC. The following alarm, NbapCommon_ Layer3SetupFailure could also be present on the RBS. RNC:moshell XXRNCX *log onto the RNClt all *load all Managed Objectsalt *show current alarmslst .xxxx *show status of channels all cells will be DISABLED

Check the RBS for any alarms.RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms

This alarm could point to a problem with Transmission. It will need to be either escalated to the Transmission department or Telkom.


UtranCell_RBSLocalCellNotAdded:RNC Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> UtranCell_RBSLocalCellNotAdded

This alarm is triggered when the RNC is trying to activate the UTRANCELL but is unable to as there is a mis-configuration with the RBS Local Cell on the RBS. The alarm UtranCell_NbapMessageFailure could also be present for the affected sectors.

RNC:moshell XXRNCX *log onto the RNClt all *load all Managed Objectsalt *show current alarmslst .xxxx *show status of channels cells will be UNLOCKED and DISABLEDget cell=xxxx cid *check the Cell ID on the RNC

RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms and confirm what sector is affectedget rbslocalcell cellid *check the Cell ID on the RBS and confirm the mismatchCheck the FACTs page to confirm the correct Cell ID to be used CI Allocation Lookuphttp://10.217.201.232/facts/report/CI_TRANSLATION/CI_TRANSLATION_LOGIf the RBS that has the incorrect values use the following command to correct it:set rbslocalcell=SXCX localCellId=xxxxx *corrects the Cell ID on the RBSNOTE:S1C1 Sector 1,Carrier1S1C2 Sector1,Carrier2 etc.....

If the RNC has the incorrect value use the following command to correct it:set cell=xxxxA1 cid=xxxxx *corrects the Cell ID on the RNC

Confirm alarm has cleared and the cells are UNLOCKED and ENABLED.Finally be sure to save a CV see Node B Restart Procedure for help on creating a CV.cvlscvms [cvname_date_time][ursername][comment]

UtranCell_NbapMessageFailure:RNC Library in ALEX: Operation and Maintenance -> Fault Management -> Alarms -> UtranCell_NbapMessageFailureThis alarm can be triggered when the RBS cannot fulfil the request to set up a UTRAN Cell issued by the RNC. The RBS will need to be checked for any alarms.RNC:moshell XXRNCX *log onto the RNClt all *load all Managed Objectsalt *show current alarmslst .xxxx *show status of channels all cells will be DISABLED

Check the RBS for any alarms.RBS:moshell Uxxxx *log onto the nodelt all *load all Managed Objectsalt *show current alarms

CASE 1 Hardware Failure on RBS:A faulty TX board on the RBS can cause the untrancells on the RNC to be DISABLED. See alarm Plug-In Unit General Problem.

EXTRA NOTES: MTN Configuration Types

RBS 3202

SMOKE Text Analysis

Node B Restart Procedure

License Issues on Node B

USEFUL Commands:

Checking Performance:

RNC:pmx cell=xxxx pmtotnoutranrejrrcconnreq|pmNoFailedAfterAdm -m 1 *shows rejections and failures for the last hourpmx cell=xx pmTotNoRrcC|pmNoSystemRabRe|pmNoSysRelSpeech|pmNoRabEstablish|pmNoNormalRabRel|pmNoFailedAfterAdm -m 1pmx utrancell=xxxx pmCellDowntime -m 4 *shows downtime for last 4 hourspmr *displays all the predefined performance reports on the RNCpmom . *gives a description of a specific counterpmom . pmCellDowntimeAutomom . *gives a description of a particular parameterpmx plug processorload -m 1 *shows processor load on individual boards

RBS:pmx e1 pm m 1 *shows the errored seconds and severely errored seconds for the E1 links over the last hourpgets e1 *shows the current errors on the E1 linkspmx aal2ap pmunsuc -m 2 *show all unsuccessful attempts across the aal2 paths for all classes pmx edch pmnoallowedeul pgets *shows all active counters on the RBSpmr *displays all the predefined performance reports on the RBSget radio no *shows the current number of active radio links

Locking and Unlocking site on RNC:

RNC:moshell XXRNCX *log onto the RNClt all *load all Managed Objectsalt *show current alarmslst .xxxx *show status of channels confirm if site has one or two carriersbls cell=xxxx *soft blocks the cells takes 5 minuteslbl cell=xxxx *blocks all the channelslst .xxxx *confirm the channels are LOCKED and DISABLEDldeb cell=xxxx *unlock cells and channels one sector at a timelst .xxxx *confirm the channels are UNLOCKED and ENABLED

Miscellaneous:ala *shows current alarms WITH detailsaltk *shows current alarms UNACKNOWLEDGED and ACKNOWLEDGEDget 0 *shows equipment typelicense key *shows licenses installed on the nodecvls *prints configuration version on the node

Change ControlVersionChangesEdited ByDate1.3Removed Config Licences Original Worksheet since it was a WIP and the "Licences" sheet overwrites this now.Added Change Control Sheet to track changesRemoved reference to version # in New MTN Config worksheetBilal Mohamed9th February 20101.4Updated RNC licenses in "Licences" tabLlewellyn King9th February 20101.5Added maxNumEulUsers row, added Notes column clarifying the ability to increase certain values if license capacity exists (whilst checking available DL CE remaining after change)Bilal Mohamed25th March 20101.6Updated Config4 Licensing : Dual stack & Flexible QOSLlewellyn King7th April 20101.7 AmaxNumAdchReservation parameter addedLlewellyn King8th July 20101.7 BNew TAB to assist in configuring non-compliant configurations added. Also TAB added to assist with HS-TX Mapping of HS Code Resources. Highlights removed since are no longer changes to the New MTN Config Tab. Highlight added to sf16admul since issue with it needs to be addressed.Bilal Mohamed20th July 2010

LicencesConfig 1 (Standard Node B)Config 2 (3.6 Capable & Multiple E1s)Config 3 (7.2 & 14.4 Capable or Multi Carrier)Config 4 (21Mbps Capable and IP capable)Notes/CommentsFAJ 121 801, HSDPA MobilityFAJ 121 801, HSDPA MobilityFAJ 121 801, HSDPA MobilityFAJ 121 801, HSDPA MobilityFAJ 121 1023, Enhanced Uplink Start Package :FAJ 121 1023, Enhanced Uplink Start Package :FAJ 121 1023, Enhanced Uplink Start Package :FAJ 121 1023, Enhanced Uplink Start Package : FAJ 121 970 Enhanced Uplink Introduction FAJ 121 970 Enhanced Uplink Introduction FAJ 121 970 Enhanced Uplink Introduction FAJ 121 970 Enhanced Uplink Introduction FAJ 121 990 Enhanced Uplink Interactive RAB, 2xSF4 FAJ 121 990 Enhanced Uplink Interactive RAB, 2xSF4 FAJ 121 990 Enhanced Uplink Interactive RAB, 2xSF4 FAJ 121 990 Enhanced Uplink Interactive RAB, 2xSF4 FAJ 121 1129 Enhanced Uplink users per cell (with 4 users per cell) FAJ 121 1129 Enhanced Uplink users per cell (with 16 users per cell) FAJ 121 1129 Enhanced Uplink users per cell (with 16 users per cell) FAJ 121 1129 Enhanced Uplink users per cell (with 16 users per cell)FAJ 121 1317 R2, Enhanced Uplink 2ms TTIFAJ 121 1334 Improved CE ladder for E-DCH on RAX R2eFAJ 121 1129 32 EUL Users FAJ 121 1050 1.4 Mbps Enhanced Uplink FAJ 121 1050 1.4 Mbps Enhanced Uplink FAJ 121 1050 1.4 Mbps Enhanced Uplink FAJ 121 1050 1.4 Mbps Enhanced Uplink FAJ 121 1050 1.4 Mbps Enhanced Uplink FAJ 121 1050 1.4 Mbps Enhanced Uplink FAJ 121 1050 1.4 Mbps Enhanced Uplink FAJ 121 1050 1.4 Mbps Enhanced Uplink FAJ 121 1050 1.4 Mbps Enhanced Uplink FAJ 121 1054 Enhanced UpLink TN Optimization FAJ 121 1054 Enhanced UpLink TN Optimization FAJ 121 1054 Enhanced UpLink TN Optimization FAJ 121 1054 Enhanced UpLink TN Optimization FAJ 121 1002 Enhanced UL Mobility FAJ 121 1002 Enhanced UL Mobility FAJ 121 1002 Enhanced UL Mobility FAJ 121 1002 Enhanced UL MobilityFAJ 121 1033, HSDPA Introduction Package :FAJ 121 1033, HSDPA Introduction Package :FAJ 121 1033, HSDPA Introduction Package :FAJ 121 1033, HSDPA Introduction Package : FAJ 121 842 R1, HSDPA Introduction FAJ 121 842 R1, HSDPA Introduction FAJ 121 842 R1, HSDPA Introduction FAJ 121 842 R1, HSDPA Introduction FAJ 121 895 R1, HSDPA TN Optimization FAJ 121 895 R1, HSDPA TN Optimization FAJ 121 895 R1, HSDPA TN Optimization FAJ 121 895 R1, HSDPA TN Optimization FAJ 121 927 R1, Admission Control FAJ 121 927 R1, Admission Control FAJ 121 927 R1, Admission Control FAJ 121 927 R1, Admission Control FAJ 121 906, HSDPA Interactive 64/HS RAB FAJ 121 906, HSDPA Interactive 64/HS RAB FAJ 121 906, HSDPA Interactive 64/HS RAB FAJ 121 906, HSDPA Interactive 64/HS RAB FAJ 121 1011, HSDPA users per cell, with up to 64 users per cell FAJ 121 1011, HSDPA users per cell, with up to 16 users per cell FAJ 121 1011, HSDPA users per cell, with up to 32 users per cell FAJ 121 1011, HSDPA users per cell, with up to 32 users per cell FAJ 121 1011, HSDPA users per cell, with up to 32 users per cell FAJ 121 1097, Fast HSDPA Dynamic Power Allocation FAJ 121 1097, Fast HSDPA Dynamic Power Allocation FAJ 121 1097, Fast HSDPA Dynamic Power Allocation FAJ 121 1097, Fast HSDPA Dynamic Power Allocation FAJ 121 1010 R1, HSDPA Cell Carriers, with up to 3 HSDPA cell carriers FAJ 121 1010 R1, HSDPA Cell Carriers, with up to 3 HSDPA cell carriers FAJ 121 1010 R1, HSDPA Cell Carriers, with up to 3 HSDPA cell carriers FAJ 121 1010 R1, HSDPA Cell Carriers, with up to 3 HSDPA cell carriers FAJ 121 0332 R1, HSDPA codes per cell, with up to 5 codes per cell FAJ 121 0332 R1, HSDPA codes per cell, with up to 5 codes per cell FAJ 121 0332 R1, HSDPA codes per cell, with up to 5 codes per cell FAJ 121 0332 R1, HSDPA codes per cell, with up to 5 codes per cellFAJ 121 1004, HSDPA CQI AdjustmentFAJ 121 1004, HSDPA CQI AdjustmentFAJ 121 1004, HSDPA CQI AdjustmentFAJ 121 1004, HSDPA CQI AdjustmentFAJ 121 961, Emergency Unlock ResetFAJ 121 961, Emergency Unlock ResetFAJ 121 961, Emergency Unlock ResetFAJ 121 961, Emergency Unlock ResetFAJ 121 904, HSDPA Proportional Fair schedulingFAJ 121 904, HSDPA Proportional Fair schedulingFAJ 121 904, HSDPA Proportional Fair schedulingFAJ 121 904, HSDPA Proportional Fair schedulingFAJ 121 905, HSDPA Interactive up to 384/HS RABFAJ 121 905, HSDPA Interactive up to 384/HS RABFAJ 121 905, HSDPA Interactive up to 384/HS RABFAJ 121 905, HSDPA Interactive up to 384/HS RABFAJ 121 150, Speech and Packet Data RAB CombinationFAJ 121 150, Speech and Packet Data RAB CombinationFAJ 121 150, Speech and Packet Data RAB CombinationFAJ 121 150, Speech and Packet Data RAB CombinationFAJ 121 147, Conversational RAB for 64 kbps MultimediaFAJ 121 147, Conversational RAB for 64 kbps MultimediaFAJ 121 147, Conversational RAB for 64 kbps MultimediaFAJ 121 147, Conversational RAB for 64 kbps MultimediaFAJ 121 903, HSDPA 16QAMFAJ 121 903, HSDPA 16QAMFAJ 121 903, HSDPA 16QAMFAJ 121 1331 Support for 64 QAMFAJ 121 1328 Enhanced layer 2FAJ 121 0332, High Downlink Bit Rate Support, up to 10 CodesFAJ 121 0332, High Downlink Bit Rate Support, up to 10 CodesFAJ 121 0332, High Downlink Bit Rate Support, up to 10 CodesFAJ 121 987, Very High Downlink Bit Rate Support, up to 15 CodesFAJ 121 987, Very High Downlink Bit Rate Support, up to 15 CodesFAJ 121 369, Inverse Multiplexing over ATM, IMA (All sites with multiple E1s)FAJ 121 369, Inverse Multiplexing over ATM, IMA (All sites with multiple E1s)FAJ 121 369, Inverse Multiplexing over ATM, IMA (All sites with multiple E1s)FAJ 121 1086, IMA Bandwidth Adapation (All sites with multiple E1s)FAJ 121 1086, IMA Bandwidth Adapation (All sites with multiple E1s)FAJ 121 1086, IMA Bandwidth Adapation (All sites with multiple E1s)FAJ 121 969, HSDPA Code Multiplexing and HS-SCCH Power ControlFAJ 121 969, HSDPA Code Multiplexing and HS-SCCH Power ControlFAJ 121 969, HSDPA Code Multiplexing and HS-SCCH Power ControlFAJ 121 860, HSDPA Mobility phase 2FAJ 121 860, HSDPA Mobility phase 2FAJ 121 860, HSDPA Mobility phase 2FAJ 121 860, HSDPA Mobility phase 2FAJ 121 967, HSDPA Dynamic Code AllocationFAJ 121 967, HSDPA Dynamic Code AllocationFAJ 121 967, HSDPA Dynamic Code AllocationFAJ 121 988, Speech 12.2 kbps and HSDPA Interactive 64/HS RAB combinationFAJ 121 988, Speech 12.2 kbps and HSDPA Interactive 64/HS RAB combinationFAJ 121 988, Speech 12.2 kbps and HSDPA Interactive 64/HS RAB combinationFAJ 121 988, Speech 12.2 kbps and HSDPA Interactive 64/HS RAB combinationFAJ 121 968 HSDPA Flexible SchedulerFAJ 121 968 HSDPA Flexible SchedulerFAJ 121 968 HSDPA Flexible SchedulerFAJ 121 148 Interactive RAB for up to 384 kbps Packet DataFAJ 121 148 Interactive RAB for up to 384 kbps Packet DataFAJ 121 148 Interactive RAB for up to 384 kbps Packet DataFAJ 121 148 Interactive RAB for up to 384 kbps Packet DataFAJ 121 146, Conversational RAB for AMR SpeechFAJ 121 146, Conversational RAB for AMR SpeechFAJ 121 146, Conversational RAB for AMR SpeechFAJ 121 146, Conversational RAB for AMR SpeechFAJ 121 985 Conversational RAB for multi mode AMR SpeechFAJ 121 985 Conversational RAB for multi mode AMR SpeechFAJ 121 985 Conversational RAB for multi mode AMR SpeechFAJ 121 985 Conversational RAB for multi mode AMR SpeechRNC FeaturesRNC FeaturesRNC FeaturesRNC FeaturesFAJ 121 154, GSM Handover and Cell ReselectionFAJ 121 154, GSM Handover and Cell ReselectionFAJ 121 154, GSM Handover and Cell ReselectionFAJ 121 154, GSM Handover and Cell ReselectionFAJ 121 405, Inter-frequency HandoverFAJ 121 405, Inter-frequency HandoverFAJ 121 405, Inter-frequency HandoverFAJ 121 405, Inter-frequency HandoverFAJ 121 406, Directed Retry to GSMFAJ 121 406, Directed Retry to GSMFAJ 121 406, Directed Retry to GSMFAJ 121 406, Directed Retry to GSMFAJ 121 435, Inter frequency Load SharingFAJ 121 435, Inter frequency Load SharingFAJ 121 435, Inter frequency Load SharingFAJ 121 435, Inter frequency Load SharingFAJ 121 973, SS7 over IPFAJ 121 973, SS7 over IPFAJ 121 973, SS7 over IPFAJ 121 973, SS7 over IPFAJ 121 972, Support for SGSN in PoolFAJ 121 972, Support for SGSN in PoolFAJ 121 972, Support for SGSN in PoolFAJ 121 972, Support for SGSN in PoolFAJ 121 976, IuPS user plane over IPFAJ 121 976, IuPS user plane over IPFAJ 121 976, IuPS user plane over IPFAJ 121 976, IuPS user plane over IPFAJ 121 1009, Delayed Activation (21 day grace period)FAJ 121 1009, Delayed Activation (21 day grace period)FAJ 121 1009, Delayed Activation (21 day grace period)FAJ 121 1009, Delayed Activation (21 day grace period)Site SpecificSite SpecificSite SpecificSite SpecificFAJ 121 244, Positioning Service, Cell AccuracyFAJ 121 244, Positioning Service, Cell AccuracyFAJ 121 244, Positioning Service, Cell AccuracyFAJ 121 244, Positioning Service, Cell AccuracyIub over IP SupportFAJ 121 964 IP interfaces in WCDMA RANFAJ 121 1132 Iub over IP/Ethernet in RBSFAJ 121 1118 Iub over IP/Ethernet in RNCFAJ 121 1154 Network Synch Server for IP transportNeeded since we are not going for Dual-StackFAJ 121 1155 Network Synch Client for IP transportNeeded since we are not going for Dual-StackFAJ 121 1093 Flexible QoS And Allocation/Retention handlingFAJ 121 1311, ATM & IP dual stack in RBS

MTN Config OldestConfigurationConfig 1Config 2 (Opt 1)Config 2 (Opt2)Config 2 (Opt3)Config 2 (Opt4)Config 3Carrier Configuration3x1, R99+EUL/HS on 1st Carrier3x1, R99+EUL/HS on 1st Carrier, or3x1, R99+EUL/HS on 1st Carrier, or3x1, R99+EUL/HS on 1st Carrier, or3x1, R99+EUL/HS on 1st Carrier3x1, R99+EUL/HS on 1st Carrier, or3x2, R99 on 1st Carrier, EUL/HS on 2nd Carrier3x2, R99 on 1st Carrier, EUL/HS on 2nd Carrier3x2, R99 on 1st Carrier, EUL/HS on 2nd Carrier3x2, R99 on 1st Carrier, EUL/HS on 2nd CarrierNumber of E1's12 or 32 or 32 or 32 or 34, 5, 6Minimum TXB ConfigurationTX6HS-03TX6HS-04 + TXTX6HS-03 + TXTX6HS-04TX6HS-03TX6HS-04 + TXRNC MO - HsdschcodeThresholdPdu656666666numHsPdschCodes555555numHsScchCodes132223RNC MO - UtranCellsf16AdmUl323232323232sf4AdmUl444444hsdpaUsersAdm102020201530RBS MO - RbsLocalCelldynamicHsPdschCodeAdditionOnfalsetruefalsefalsefalsetruemaxNumHsPdschCodes51055515maxNumHsdpaUsers163232321632RBS MO - NodeBFunctionflexibleSchedulerOnfalsetruetruetruetruetruesteeredHsAllocationfalsefalsefalsefalsefalsefalsesupportOf16qamfalsetruetruetruetruetrueRBS MO - CarriercqiAdjustmentOntrue (except IBS)true (except IBS)true (except IBS)true (except IBS)true (except IBS)true (except IBS)hsScchMaxCodePower-20-20-20-20-20-20hsScchMinCodePower-150-150-150-150-150-150queueSe

3g alarm handling guide_moshell commands

Documents