Ads Revenue Hits

Tuesday, November 18, 2014

8125 Loss of synchronization signal (s)

8125 Loss of synchronization signal(s)


Severity:
Object affected:
Object state:
Module/Unit:
Critical
TRE
Enabled
FIxx
Fault reason:
Instruction:
Field not  used.
 
All defined synchronisation sources in the synchronisation priority list are invalid or the list is empty. Node is running on its internal clock.
1. Check that synchronisation priority list has Rx clock entries for used interfaces.
2. In case FIFA PIU is used, check that the microwave link is commissioned and operational. Refer to FIFA product documentation for further instructions.
3. If any of the alarms 8050, 8066, 8081, 8099, 8056, 8073, 8277,8278, or 8282 are active, follow the instructions on them..
4. Check that interface cables are correctly mated to FIxx. Check also condition of the connectors.
5. With FIQA or FIYA and using adaptive clock recovery at a PW as synch source, check if packet switched network is of sufficient quality. Refer to documentation about synchronization of BTS with FIQA, FIYA.
6. Replace FIxx.

             

7616 OSCILLATOR ADJUSTMENT TEMPORARILY INTERRUPTED

7616 Oscillator Adjustment Temporarily interrupted


Severity:
Object affected:
Object state:
Module/Unit:
Minor
BCF
Enabled
ESMx
Fault reason:
Instruction:
Clock tuning DAC word reaching min/max limit.
Oven oscillator DAC word is within 5% of the min/max limit. Alarm is activated if the DAC word is between 0-204 or 3891-4095. This alarm can be activated due to incorrect synchronisation settings in transmission network.
1. Check the Abis synchronisation that there are valid Rx clock sources available.
1.1. If the reference clock is ok, tune the ESMx clock to the correct frequency.
1.2. If the reference clock is not ok, check the alarm history for 8xxx alarms for the possible reason for the incorrect reference clock. Follow the instructions on 8xxx alarms. After correcting the reference clock tune ESMx clock to the correct frequency.