Professional Documents
Culture Documents
Huawei 2G Fault Guide 04022013CM 1
Huawei 2G Fault Guide 04022013CM 1
This alarm is reported when the maintenance link between the BBU and the RF unit malfunctions
Resolution:
Replace RFU
Check optical interconnections, clean if necessary
Confirm the RF plumbing is as per the RF schematics
Confirm all connections are tight
Sweep antenna
Check connectors/tails externally
Resolution:
Confirm the RF plumbing is as per the RF schematics
Confirm all connections are tight
Confirm all hardware used on site meets the frequency used.
Replace RFU
Sweep antenna
Check connectors/tails externally
The R13 introduces a new user/password level of System User which prompts for login each time the software is run.
See the below embedded screen log ins compiled by Peter Fraser
Cause:
The fault is caused by Jitter and Wander in the transmission network and is usually poor synchronization of the E1 connected to the site (8 KHz
frame).
There will usually be no transmission alarms or errors, only a SDH/PDH and Jitter/Wander Test Set can be used to test for the fault, but in most
cases this is not needed.
All that is usually needed is to provide the incoming E1 with a better synchronization source.
The reason why there will be no alarms on the E1 is because as far as the E1 in concerned its synch is great, but unfortunately the synch
requirement of a BTS are far higher. E1 <50 PPM, BTS approx <1 PPM requirement
These faults can take months to fix but are usually fixed after transmission finally accept that the E1 has a problem.
Action:
Even though it is 99% sure an E1 Jitter and Wander problem, it does have the chance of being the oscillator in the GTMU, especially when we
don’t know the quirks in Huawei (Oscillator problems maybe common), you can replace the GTMU so that there is no doubt that it is the
transmission, if transmission refuse to accept this then escalate.
Note: we have already fixed a few dozen of these in the Huawei gear, all so far have been transmission synch. Some we have managed to fix
remotely because it was a DXX synchronization fault and others were fixed externally.