Troubleshooting with the help of alarm tables Purpose ‘The fault reason can be used for troubleshooting, The faults and instructions on how to correct the faults are presented in table format (see example of alarm table below): ‘Table: Description of the fields in the alarm table 1234 ALARM NAME. Severity: Object Object state: Unit: affected: ‘Shows the alarm ‘The logical ‘The state of the affected ‘The alarm origin(s). The severity as displayed at object affected object at the time the alarm unit is given an acronym, the BSC or by the fault, isissued. The options are: for example: NMS/NetAct. The The options loptions are: are: + Enabled BOI, RT xx, TSxx, BB2x + Disabled + *=minor BCE, BTS, + **=major —/TRX, TRE, +"? scritical RTS + User definition Fault reason: Instruction: ‘Alarm cancelling: ‘This field describes the |This field gives instructions for the operator |This field describes how ‘cause of the alarm, for (at the NMS/NetAct or at the BSC) how to the alarm is cancelled. The example: ‘correct the fault reason causing the alarm, options are: for example: ‘Power unit temperature + Automatic is dangerously high. 1. Ensure that the ambient temperature | | Manual of the base station is within specified limits Check the cabinet fans Replace the faulty power unit(s). Note When baseband hopping is used, alarms do not cancel automatically when a fault is corrected. Sector reset from Nokia BTS Manager or BTS lock/unlock from the BSC is required to clear the active alarms,[> | Note go Note If the fault reason cannot be found in the Fault reason field, the instructions given for Other faults apply for the current fault. For instructions on how to replace units, refer to the latest Nokia UltraSite EDGE BTS Product Documentation set. Steps > Expand/collapse all 1, Check the alarm number and alarm name and refer to Alarms list for Nokia UltraSite EDGE BTS to find the correct alarm description table. 2. > Find the fault reason in the Fault reason field in the alarm description table. 3. > Follow the instructions in the proposed order given in the Instruction field. 4, If the fault reason cannot be found in the Fault reason field, follow the instructions given for Other faults. 5. IF there is no fault reason text with the alarm (see 1, in Figure ‘Examples of active alarms 4as seen at the BSC), refer to the correct alarm description table and follow the possible instructions given in the Instruction fie. 7745 CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD Meaning The rate of calls terminating in failure on a channel is above the threshold value set by the operator. The alarm is used to supervise the functioning of traffic and signaling channels, and to detect the possible faulty channele Supplementary information fields 1 indicates if the alarm is on the TCH or on the SDCCH channel a ‘TCH o ‘SDCCH 2 indicates if the channel failure rate is above the defined threshold in time slot 000: belove threshold (no alarm) 01: above threshold (alarm) 3 indicates if the channel failure rate is above the defined threshold in time slot 1 00: belove threshold (no alarm) 0 above threshold (alarr) 4 indicates if the channel failure rate is above the defined threshold in tine slot 2 a belove threshold (no alarm) 01: above threshold (alarn) 5 indicates if the channel failure rate is above the defined threshold in tine slot 3 00: belove threshold (no alarm) 01: above threshold (alarm) 6 indicates if the channel failure rate is above the defined threshold in time slot 4 00: belove threshold (no alarm a above threshold (alarm) 7 indicates ig the channel failure rate is ebove the defined threshold in tine slot 5 a belove threshold (no alarm 01: above threshold (alarm) 8 indicates if the channel failure rate is above the defined threshold in time slot 6 00: belove threshold (no alarm) 0 above threshold (alarm) 9 indicates if the channel failure rate is above the defined threshold in tine slot 7 a belove threshold (no alarm) 0 above threshold (alarm) 10 time slot with the highest failure rate 11 subchannel identification TCH: 0 ‘TCH/# ~subchannel 0 ‘CH/4 ~eubehannel 1 02: TCH/F ~subchannel subchannel identification SDCCH: 00 ~ 07: ‘SDCCH ~subchannel 0 - 7 12. proportion of TCH or SDCCH subchannel releases due to failure in all channel releases on a given channel during the measurenent period Instructions Find out the reason for the alarm on the basis of the release causesin channel release messages. Restore the channel by first locking it out of use and then unlocking it with the M. command BRS. ZERS?, ,tL7 lock ZERS:, ,:U; unlock Check that the paraneters affecting the alarm are reasonable. MuL conmand EEO outputs the radio network supervision parameter values, FEN comand modifies the parameter values Parameters, with their default values, affecting the alarm: ZEEN:TCHFR ~ TCH failure rate (20 SCHER = SDCCH failure rate (20 8) PROCER = length of supervision period (60 min) (CS = channel seizure threshold value (20 SMEND = supervision start time (08-00) EMEN? = supervieion end time (18-00) Cancelling If the alarm requires no user actions, you can cancel it with the ML command EOR ‘The system cancels the alarm automatically in connection with the user's locking and unlocking commands, or, if the situation is solved without user actions, after the current measurenent period. 7743 MEAN HOLDING TIME BELOW DEFINED THRESHOLD Meaning Mean holding time on a channel is below the operator-defined minimum Guring the measurenent period. The alarm is used to supervise the functioning of traffic channels and to detect the poseible faulty channels. Supplementary information fields 1 indicates if the mean holding time is below the defined threshold in time slot 0 00: above threshold (no alarm) 01: below threshold (alarn) 2 indicates if the mean holding time is below the defined threshold in time slot 1 00: above threshold (no alarm) a below threshold (alarm) 3 indicates if the mean holding time is below the defined thresholdin time elot 2 00: above threshold (no alarm) 0 below threshold (alarm) 4 indicates if the mean holding time is below the defined threshold in time elot 3 00: above threshold (no alarm) 01: below threshold (alarm) 5 indicates if the mean holding time is below the defined threshold in time elot 4 a above threshold (no alarm) 01: below threshold (alarm) 6 indicates if the mean holding time is below the defined threshold in time slot 5 00: above threshold (no alarm) a below threshold (alarm) 7 indicates if the mean holding time 1s below the defined threshold in time slot 6 a ‘above threshold (no alarm) 01: below threshold (alarm) 8 indicates if the mean holding time is below the defined threshold in time slot 7 a above threshold (no alarm) @ below threshold (alarm) 9 identifies the time slot where the mean holding time is shortest 10 identifies the subchannel in the time slot with the shortest mean holding time 00: TCH/H subchannel 0 TCH/H subchannel 1 TCH/F subchannel 11 shortest mean holding time in seconds during the measurement period (TCH) Instructions Find out the reason for the fault by examining the release causes in channel release messages. Restore the channel by first locking it out of use and thon unlocking it with the WM command ERS. ZERS:,,:L; lock ZERS:,,:U; unlock Check that the paraneters affecting the alarm are reasonable ‘The WML command EEO outputs the radio network supervision parameter values and the EEN conmand modifies the parameter values. Parameters, with their default values, affecting the alarm:ZEEN:MINHTT = minimum mean holding time for a TCH {10 9) PROMET = length of TCH supervision measurement (120 min} jannel seizure threshold value 420) Cancelling If the alarm requires no user Mu conmand EOR. ions, you can cancel it with the The systen cancels the alarm automatically in connection with the user's locking and unlocking commands, or, if the situation is solved without user actions, after the current measurenent period. 7741 MEAN HOLDING TIME ABOVE DEFINED THRESHOLD Meaning The mean holding time on the channel specified exceeds the operator-defined threshold during the measurement period. The alarm is used to supervise the functioning of the traffic and signalling channels. It reveals unreleased calls. Supplementary information fields 2 subchannel identigication 00 - 01: ‘TCH/ eubchannel FO ‘TCH/F subchannel co - cr SDCCH subchannel 2 mean holding time on the channel during the meacurenent period in minutes 3 number of seizures on the channel during the measurement period 4 shortest seizure on the channel during the measurement period in seconde Instructions Find out whether the channel seizure that caused the alarm is a real call or an unreleased channel. Use the service terminal conmand S:4ltsbts_idagts,cltstrx idegts, Byeitrstatus = 20gt7; RRMPRS states are on CH STA column: OsDISC —1DIDLE 20=BUSY FF=CECH ABIPRE ctates are on the laet column of the output row:= blocked = free = signalling conversation = cece! Compare the channel state in RRM end ABI to determine whether the channel i unused but unreleased. In the case of an unreleased channel, if it is a traffic channel, restore the channel by first locking it out of use and then unlocking it (CH lock/unlock). Use the MML command ERS and give the TRX and the channel as parancters. 2ERS*, CTRX>,tL; lock ZERS:, ,:U; unlock If it is a signalling channel, restore the channel by locking and then unlocking the whole TRX (TEx lock/unlock). Use the MZ command ERS and give the TRX as a parameter. Check that the parameters affecting the alarm are reasonable. MUL conmand EEO outputs the radio network supervision parameter values, FEN command modifies the parameter values. Parameters, with their default values, affecting the alarm: ZEEN:MAXETT= maximum mean holding time for TCH (220 min} MAXHTS= maximum mean holding time for SDCCH (30 min} PROMET= length of TCH supervision measurement (240 min} PROM: = length of SDCCH supervision measurement (60 min} Cancelling Tf the alarm does not require user actions, you can cancel it with ‘the MML connand BOR. The system cancels the alarm when you lock and unlock the object in question, or, if the alarm requires no user actions, after the Current measurement period. 7738 BTS WITH NO TRANSACTIONS Meaning The BTS has had no successfully terminated calle, SoCcH GPRS TEF releases during the supervision period. The alarm is used for supervising the BTS traffic capacity and to indicate a sudden loss of service on BTS level. aneactions of Supplementary information fields1 reason for the alarm (hex) 1 = no successful SDCCH seizures 2 = no successful TCH seizures 3 = no successful SDCCH nor TCH seizures 10 = no successful GPRS transactions 11 = no eucceseful SDCCH seizures and no cucceeful GPRS transactions 12 = no euccessful TCH seizures and no succesful GPRS transactions 13 = no successful SDCCH nor TCH seizures nor GPRS transactions Instructions Find out the reason for the loss of BIS traffic capacity and bring the BTS back to use. This may reqiro for example locking, resetting and unlocking the BTS or BCF object. Note that these actions cause both CS and PS traffic to drop within the entity that has been reset. To restore the GPRS service in a BTS, disabling and enabling GPRS (GENA-N, GENASY) in the alarmed ATS may be sufficient. Check that the parameters in connection with the alarm are reasonable. Too short a supervision period may cause false alarms. ‘The MML comand EEO outputs the radio network supervision parameter values, and the EEN conmand modifies the parameter values. Parameters, with their default values, affecting the alarm: ZEN: SMBNT- supervision start tine (08-00) EMBNT= supervision end tine (28-00) PROBNT= length of supervision period (120 min) Cancelling ‘The system cancels the alarm once it detects the BTS traffic capacity has been restored, that is, when @ normal channel release of the type that was faulty occurs or, in case of a GPRS related cause, when fa successful TBF release occurs in the BTS. Note that if the alarm was originally raised with both CS and PS reasons (16..19), and the service occures either to FS or to CS domain, the alarm may remain for the other domain. ‘The user can also cancel the alarm with the EOR comand after correcting the fault as presented in the INSTRUCTIONS. ALL supplementary alarm fields are est to zero irrespective of wheter the alarm is cancelled manually or by the aysten. 7622 CABINET OPEN Meaning Supplementary information fields166 3 XK HK HK HK 123456 1) rack (cabinet) nutber 4) type of unit 2) shelf nunber 5) unit number 3) slot, 6) cubunit nunbor See instructions on Alarm Structure Instructions If the cover is attached, ensure it is secured properly. If there is no cover, attach it during normal service operations. Cancelling This is a start/cai 1 type alarm. The alarm is cancelled automatically. 7616 OSCILLATOR ADJUSTING TEMPORARILY INTERRUPTED Meaning ‘The Abis frequency is too high or too low, or it fluctuates so much that the master clock tune ie unreliable and tends to oscillate too much, Ancther reason for thie alarm can be that the oven adjustment enario has tuned the oven too near the edge. When the tune is stopped, the master clock can go by itself out of specification and therefore calls may drop after several hours or days. ‘hie ie 2 non-fatal alarm but it indicates decreased traffic capacity in the base station. Supplementary information fields 1-6 2X XK 10 2 2K 20 123456 1) rack (cabinet) number 4) type of unit 2) shelf number 5) unit numb 3) slot 6) subunit number For more information, see Alarm Structure Instructions METROSITE and CONNECTSITE 11 Fault reason : Oven oscillator adjustment function interrupted. Instructions: 1. Check the Abis connection 2. If the Abis connection is OK, replace the faulty VIFA unit.ULTRASITE and CONNECTSITE 100; Fault reason : Oven oscillator adjustment function interrupted. Instructions: 1. Check the Abis connection 21 If the Abie connection is OK, replace the BOI. Cancelling Do not cancel the alarm, The system cancels the alarm automatically then the fault has been corrected 607 TRX OPERATION DEGRADED Meaning Ceitical fault has occurred in a 7RX, The fault reason can be read from the supplementary text field of the alarm. Supplementary information fields 166 3K HK 123456 1) rack (cabinet) number 4) type of unit 2) shelf number 5) unit number 3) slot 6) subunit number For more information, see Alarm Structure Instructions METROSITE and CORNECTSITE 10: All fault reasons Inetructione: See the Alarm Descriptions docunent included in the BTS sw release binder of the alarming base station type. ULTRASITE and CONNECTSITE 100: Fault reason : The reflected power of renote tune combiner is too high. Instructions: 1. Check the antenna connection to the renote tune combiner. 2. If the antenna connection is OK, replace the remote tune combiner. Diversity branch is still working and calls are getting through. Fault reason : Fault in the chain between power unit and MHA, Instructions: 1. Check the chain between the power unit and the MHA. 2] If the chain is ox, replace the NHA.Fault reason : Fault in VSWR antenna monitoring. Instructions: 1. Check the antenna and cabling. If either the antenna or cabling are faulty, replace the faulty units and reset sector to cancel the alam. 2, If the antonna and cabling are OK, the TSxx is faulty. Replace the faulty TSkx. Diversity RX branch is still working and calls are getting through. Fault reason Instructions: 1. Check the BTS configuration and install the Dvux if it ie missing. No connection to dual variable gain duplex unit. Fault reason Instructions: 1. Check the configuration of TRKa- 2. Upgrade the TSxx/B52x unite to EDGE capability. RK is unable to implement EDGE services. Fault reason : IDD main/auxiliary TRX frequency band mismatch. Instructions: Note: IDD auxiliary TAX. 1. Check the IDD configuration of the BCP. 2. Check the configuration of the TRX. 3. Replace the IDD auxiliary TSxx with one of the same frequency as the IDD main TSxx unit. The TSxx unite used for an IDD pair must be of the same type. Fault reason Instructions: Note: IDD auxiliary TRX. 1, Delete the IDD auxiliary TRX from the BSC configuration. 2] Reset the IDD main TRX. IDD auxiliary TRKs are not to be defined at the ASC Mismatch between BSC/MMI configuration and/or IDD TRX. Fault reason : Non EDGE PRX device type used accidentally in IDD mode. Instructions: Note: IDD auxiliary TAX. 1, Check the IDD configuration of the BcF. 2. Check the configuration of the TRX. 3. Replace tho IDD auxiliary TSxx with an EDGE capable unit. IDD TRXe must be EDGE capable. Other fault reasons Instructions: See the Alarm Descriptions document included in the BTS sW release binder of the alarming base station type. Cancelling Do not cancel the alarm. The system canceis the alarm automatically then the fault has been corrected.7601 BCF OPERATION DEGRADED Table: BCF OPERATION DEGRADED 7601 BCF OPERATION DEGRADED ‘Seve (Object affected: Object state: Unit: ew BCE Enabled 'BB2x, BOL, DVxx, MNxx, PWSx, RTxx, SISU, TSxx Fault reason: Instruction: ‘Alarm cancelling: Power unit output | 1. Replace all faulty power units. ‘Automatic. Woltage fault. Power unit input | 1. Ensure that the input voltage is correct. ‘Automatic voltage fault 2. Replace all faulty power units. Noconnection to | 1, Replace all faulty power units. ‘Automatic. power unit, Power unit 1. Ensure that the ambient temperature of the base Automatic. temperature is station is within specified ls dangerously high. | 2, Check the cabinet fans. 3. Replace the faulty power unit(s). \Note: An alarm is activated when the PWSx internal temperature exceeds +85°C. (Transmission unit | 1. Ensure that the ambient temperature of the base (Automatic. temperature is station is within specified limits. dangerously high. | 2. Check the cabinet fans. 3. Replace the faulty transmission unit, \Note: An alarm is activated when the transmission unit {internal temperature exceeds +85°C. Difference 1. Check the network synchronisation between the [Automatic. between PCM and BSC and the base station. bbase station 2. Check the transmission synchronisation settings on frequency the transmission car reference. 3. Check the transmission cabling atthe site 4. Replace the BOL 'Note: After corrective actions, it may take several hours to adjust the clock and the alarm to disappear.7601 BCF OPERATION DEGRADED \Note: With BTS SW CXS and the implementation of the [Fast Tune feature, you may set the DAC clock control word via BIS Manager. This will initiate a Fast Tune procedure, in which the 26 MHz oven oscillator is quickly (within minutes) set very close to the correct frequency. Flash operation 1. Replace the BOL. ‘Automatic. failed in BOI or ‘TRX. BOI detected that | 1. Check the SISU cabinet and the connections. ‘Automatic. the site support is ‘dumb. IRx levels differ too much between ‘main and diversity antennas. 1. Check the RSSI measurements by BTS Manager. Automatic. Note: When the alarm is active, open the RSSI Comparison Values dialog box or Site Information dialog box to pinpoint the alarming RSSI value and antenna. Note: There is a hysteresis of 2 4B in the cancellation of the alarm. The alarm is cancelled when the RSSI measurement result is less than RXDL-2 4B, 2. Check and measure the antenna lines. Check the BTS RF cables and connections. 4, Replace the combiner unit. Check that the RXDL- parameter at the BSC is set to a reasonable value, taking into account the site conditions to prevent unnecessary alarms, 5. Replace the TSxx unit. Note: With BTS SW CX4.1 to CX4.1 CD2.0, the alarm may be generated unnecessarily when the Relative Difference is less than the set difference from the BSC. Check the alarm reason from the RSSI measurements by BTS Manager. If the reason, is Relative Difference, increase the RSSI alarm threshold value at the BSC. (Other Faults. 1. Check whether one or several of the following Automatic, alarms are active: 7606 TRX FAULTY7601 BCF OPERATION DEGRADED 7603 BTS FAULTY 7607 TRX OPERATION DEGRADED 7604 BTS OPERATION DEGRADED 7602 BCF NOTIFICATION and follow the instructions given for the active alarm). UltraSite EDGE BTS and Troubleshooting with the help of alarm 7600 BCF FAULTY ‘Table: 7600 BCF FAULTY following alarms is active: 7606 TRX FAULTY 7603 BTS FAULTY 7600 BCF FAULTY [Severity (Object affected: [Object ste: [Unit fees BCF Disabled 'BB2x, BOL, DV xx, PWSx, RT xx, TSxx, MNxx Fault reason: Instruction: ‘Alarm cancelling: (Oven oscillator is 1, Replace the BOL. ‘Automatic. broken. ‘Base station 1, Check that the synchronisation Automatic. synchronisation failed. source is up and alive. 2. Check that the transmission settings are OK. 3. Check the synchronisation cabling. 4, IFthe cabling is OK, replace the BOL (Other faults. 1. Check whether either of the |Automatic.