7600 BCF Faulty

Severity:	Object affected:	Object state:	Module/Unit:
Critical	BCF	Disabled	ESEA, ESMx, FIxx
Fault reason:	Instruction:
Air i/f reference clock 26 MHz  not available.	System module detected that its Oven Controlled Oscillator is not generating the frequency reference. 1. Make sure that ambient temperature of the site is within normal operating temperature range (-35 to +50C/-31 to +122F). 2. Issue a HW reset to ESMx from (remote) BTS Manager. Note that the site's bypass transmission will be cut for 1-2 minutes. 3. Replace ESMx.
BSS synchronisation failed.	ESMx System Module detected no synchronisation signal at synchronisation input (SIN) port at startup. 1. Check that the BCF synchronisation related settings are correct at the BSC via MML command(s) (ZEFO...). 2. If LMU provides the synchronisation, check if alarm 8202 is active and resolve. 3. If another BTS is the synchronisation master, check if that it is up and alive. 4. 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. 5. Replace ESMx.
Critical transmission licence missing at the BSC.	'Abis over IP/Ethernet', 'Additional 2 E1,T1 IF', or 'Packet Abis Security' licence is not installed in the BSC. 1. Check which transmission licence alarm (8273 or 8274) is active and follow the alarm specific instructions given.
ESEA System Extension module reported HW failure.	ESMx System Module detected that a hardware failure has occurred in the ESEA System Extension module. 1. Issue HW reset to ESMx from BTS Manager. 2. If fault persists, replace ESEA and reset the BCF.
ESEA System Extension module SW upgrade failed.	ESMA System Module detected that SW download to ESEA System Extension module failed at startup. 1. Issue a HW reset to ESEA. 2. Issue a HW reset to ESMA. 3. If alarm persists, replace ESEA. 4. Replace ESMA.
ESMx System Module has lost connection to all ECxx RTCs and EXxx TRXs.	None of the BTS modules respond to ESMx polling command. 1. Reset BCF. 2. Check all cable connections between ESMx and ECxx Remote Tune Combiner (ECxx) and EXxx TRX modules. 3. If the fault persists, replace ESMx.
ESMA System Module has lost connection to ESEA System Extension module.	ESEA System Extension module does not respond to polling command from ESMA System Module. 1. Check the power distribution to ESEA. 2. Check that the bus cable is correctly mated between ESMA and ESEA. 3. Replace ESEA. 4. Replace ESMA.
ESMx System Module has lost connection to FIxx transmission submodule.	FIEA/FIPA/FIFA/FIQx/FIYx transport sub-module is not detected. This alarm is reported to the BTS Manager only. 1. Check that the PIU (FIPA/FIEA/FIFA/FIQx/FIYx) is properly inserted into the ESMx. 2. Check the LED status. If LED is not lit (all PIU types) or yellow (for FIPA/FIEA/FIQx/FIYx), check the back connector of the PIU. 3. Replace PIU. 4. Replace ESMx. At the BSC, alarms 7767 BCCH Missing, 7706 BTS O&M link failure may be active for the alarming BCF.
ESMx System Module temperature dangerously high.	Internal temperature of ESMx System Module has exceeded +95C/+203F. 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.
FIxx type mismatch between commissioning file and detected hardware.	FIEA/FIPA/FIFA/FIQx/FIYx transport sub-module is of wrong type. This alarm is reported to the BTS Manager only. 1.1. Replace PIU module with a correct type (as defined in SCF) and issue a HW reset to ESMx. OR 1.2. Set PIU type in SCF according to the actual PIU module type and re-commission the site. 2. Replace the PIU and issue a HW reset to ESMx.
Mismatch between the commissioned configuration and actual configuration.	There is a conflict between the SCF and the actual configuration during commissioning or at start up: 1. SCF contains ESEA, but it is not detected in the actual configuration. 2. SCF does not contain ESEA, but it is detected to port 6 of ESMx. 3. If cabling source is "AUTODECTECTED" in SCF, issue BCF reset with RFCAD. 4. Modify SCF to match the actual configuration or modify the actual configuration to match the SCF. 5. Replace ESEA. 6. Replace ESMA.
BTS has lost CS U-Plane connection to BSC	BTS has detected a U-Plane (CS) Link Failure 1. Check U Plane IP address configurations. 2. Check if there is any filtering/firewall configurations in the network for U-CS traffic.