7602 BCF Notification

Severity:

Object affected:

Object state:

Module/Unit:

Minor

BCF

Enabled

ESEA, ESMx, EOCA.

Fault reason:

Instruction:

BSS synchronisation failed.

ESMx System Module has lost synchronisation signal at synchronisation input (SIN) port. 1. If LMU provides the synchronisation, check if alarm 8202 is active and resolve it. 2. If another BTS is the synchronisation master, check if that it is up and alive. 3. Check that the synchronisation cabling is correctly mated between the units. If LMU is used, check also Q1 cabling and power supply to the LMU unit. 4. Replace ESMx.

BTS Trace Collection Ongoing.

User initiated BTS trace collection from BTS Manager. No repair actions required, alarm is cancelled when BTS trace collection is stopped by the user.

Commissioned RF cabling does not match BTS configuration.

Manually defined RF cabling in SCF is incorrect as verified against BTS Configuration received from BSC. It may result in degraded BTS performance. 1. Revise manually defined RF cabling in SCF against the actual configuration. 2. Check that RXDIV=N for sector is using only one antenna. 3. Enable RF cable autodetection (RFCAD) through commissioning wizard. Note 1: Rack field contains information check for cable present (1 = TX, 2=RX main, 3=RX Div, 4=both RX paths from same Ant connection). Note 2: Shelf filed contains the TRX number which contains Faulty RF cables. Note 3: Also, there may be more RF cabling errors introduced during commissioning, but only one of those is reported. Note 4. Refer to latest Flexi EDGE BTS Commissioning document for RF cable autodetection limitations. 1. Rack field contains information check for cable present (1 = TX, 2=RX main, 3=RX Div, 4=both RX paths from same Ant connection). 2. Shelf field contains the TRX number which contains faulty RF cables. 3. Also, there may be more RF cabling errors introduced during commissioning, but only one of those is reported.

Difference between current and last stable DAC words

DAC word has been changed more than 408 steps from original DAC word (is usually within 2048 +/- 20) 1. Check at NetAct if there are any active core network synchronisation related alarms starting with code 1xxx and/or 2xxx, due to which the incoming sync reference PCM clock is drifted and causes OCXO oven oscillator to tune incorrectly out of correct frequency and (if fault persists) will eventually cause handover failures for CS calls. 2. Correct the synchronization problem in the upper part of network.

ECxx RTC module connected to wrong port.

ECxx RTC module is not connected to port 1/2/3 of ESMx System Module. 1. Connect ECxx to ESMx port 1,2 or 3 and issue a BCF reset.

EOCA Optical module connected to wrong port.

EOCA Optical module is not connected to ESMA System Extension module. 1. Connect Local and Remote EOCA to ESEA.

ESEA System Extension module connected to wrong port.

ESEA System Extension module is not connected to port 6 of ESMA System Module. 1. Connect ESEA to port 6 of ESMA, and issue a BCF reset.

ESEA System Extension module temperature high.

Internal temperature of ESEA System Extension module has exceeded +85C/+185F. 1. Ensure that the ambient temperature of the base station is below +50C/+122F. 2. If the fault persists, replace ESEA. Note that this alarm remains active if the temperature still increases and the "temperature dangerously high" alarm is activated.

ESMx System Module cooling fan speed has increased from the set speed.

The cooling fan speed of System Module has increased substantially from the commanded fan speed. 1. Check the ESMx operational voltage as an increased ESMx voltage could lead to overspeeding of the fans. 2. Replace the fan unit. 3. Replace ESMx.

ESMx System Module cooling fan speed has reduced from the set speed.

The cooling fan speed has reduced substantially from the commanded fan speed. 1. Check that nothing obstructs the fan(s) from rotating. 2. Clean the fan unit of dust and/or dirt. 3. Replace the fan unit. 4. Replace ESMx. Note: If "Temperature high/ dangerously high" and/or 7621 alarm(s) are also active, perform these actions as soon as possible.

ESMx System Module temperature high.

ESMx System Module has detected that its internal temperature has exceeded +90C/+194F. 1. Ensure that the ambient temperature of the base station is below +50C/+122F. 2. Check if any fan alarms are also active. If active, refer to fan alarm instructions to resolve. 3. Replace the ESMx. Note that this alarm remains active if the temperature still increases and the "temperature dangerously high" alarm is activated.

ESMx System Module unable to read internal temperature sensors.

There is no temperature measurement in the ESMx System Module. All temperature sensors inside the module are broken. Fans are rotating at maximum speed. 1. Replace the ESMx. Note: If fan alarm(s) are active at ESMx, perform this action as soon as possible.

External synchronisation signals disabled.

LMU has operated without GPS signal over specified time and is turning its FCLK output off. 1. Check the GPS antenna fix status is OK with LMUManager. Adjust the GPS antenna so that satellites become visible. 2. Check that the GPS cable is correctly mated to LMU. 3. Check that the latest LMU SW is being used. Download newer SW if necessary. 4. Replace LMU.

EXxx TRX module connected to wrong port.

EXxx TRX Module is not connected to ESEA System Extension module. 1. Connect EXxx module to ESEA.

Incoming reference clock has started to deviate rapidly

The DAC word has been changed more than 408 steps rapidly from the original DAC word (is usually within 2048 +/- 20), due to which the incoming synchronisation reference PCM clock has drifted and causes OCXO oven oscillator to tune out of correct frequency and (if fault persists) will eventually cause handover failures. 1. Check at NetAct if there are any active core network synchronisation related alarms starting with code 1xxx and/or 2xxx. 2. Correct the synchronisation problem in the upper part of the network.

Supply voltage to ESEA near low/high limit

The input voltage to the power supply of ESEA is less than 40VDC or more than 58VDC. 1. Check that the input voltage range of System Extension module is within specified range. 2. Replace ESEA.

Supply voltage to ESMx near low/high limit

The input voltage to the power supply of ESMx is less than 40VDC or more than 58VDC. 1. Check that the input voltage range of System module is within specified range. 2. Replace ESMx.

Certificate Revocation List retrieval failure from Certificate Repository

Either Certificate Repository is not reachable or invalid Certificate Revocation List at Certificate Repository or Certificate Revocation List Size too Big. 1. Check Certificate Repository IP address in SCF at BTS 2. Check BTS cable connectivity with Certificate Repository

Certificate Authority certificate retrieval failure

Either Certificate Repository is not reachable or invalid certificate of Certificate Authority at Certificate Repository 1. Check Certificate Repository IP address in SCF at BTS. 2. Check BTS cable connectivity with Certificate Repository. 3. Verify that requested valid certificate exist in Certificate Repository.

BTS security certificate retrieval failure from Certificate Authority

Either Certificate Authority is not reachable or invalid certificate at Certificate Authority 1. Check Certificate Authority IP address is correct via SCF from BTS Manager. 2. Check BTS cable connectivity with Certificate Authority. 3. Verify that valid BTS Certificate exist in Certificate Authority.

Unknown module connected to ESxx System (Extension) module.

ESMA System Module does not recognise the module connected to this port. SW release incompatibility with the connected HW. 1. Check the HW \ SW compatibility from the SW release binder a. If the module is compatible with the current SW running in the BTS, replace the module. b. If the module is not compatible with the current SW running in the BTS, check which SW version supports the module. Upgrade the BTS SW to the version that supports the module. 2. Remove the unknown module.