Fault Management &

Troubleshooting By WinFiol

Q. What is NOC and Why need NOC?

A. Network operations center (NOC) is a place which administrators supervise, monitor and maintain a
telecommunications network and the Assessment provided a 360 analysis and recommendations of forward based on
Ericssons NOC best practices and the Ericsson organization and competence readiness portfolio in a multi-vendor
environment.
The network operations center is the focal point for network troubleshooting, software distribution and updating, router and
domain name management, performance monitoring, and coordination with affiliated networks.
The customer will be going through a complete transformation that will enable them to provide new services to other
government institutions and agencies. This NOC consists of a multi-vendor environment with Transport and
Transmission equipment from different vendors (Ericsson and Huawei) with various sets of hardware and software for
monitoring and supervising network operations and Key Performances Indicators (KPI).

Table of CONTENTS
Description of the FAULTS finding
Non service affecting Fault <<..>> page no: 4
A-bis Path Unavailable <<.>>Page no: 5
Fault find out <<.>> Page No:6
TS Sync Fault <<.>>Page No:7
Permanent Fault <<.>> Page NO:8
BTS Internal Affected/Unaffected<<>>Page No:9-10
Local Mode <<.>>Page No:11-12
TF NOT SYNCRONIZED<..>>Page No:13
Others:

None Service affecting FAULT:

We have to find out the alarm by using this command in BSE: allip:alcat=ext;

External/ Internal faults can be identified on the basis of affecting the service in the
network.
There are lot of external/ Internal alarm in the network but which is not traffic
hampering.
1. Environment alarm like as BATT_FIRE
2. Environment alarm like as Water leakage alarm and so on:

ABIS PATH UNAVAILABLE

How can we find out the connection between the BTS and the BSC?

: There are no transmission device exists between the Base Station Controller (BSC) and the Base Transceiver
Station (BTS)
There are sufficient devices defined on TG and then number of TRUs/CONFACT defined on TG
There are 64K devices reserved on Abis for EGPRS not equal to NUMREQEGPRSBPC defined on cell
How to restored the ABIS path:
We have to Add sufficient devices on TG w.r.t to no. of TRUs/CONFACT defined on TG
The availability of the free devices on Abis must be taken care before addition/activation of a new TRU in a

cell

There are number of 64K devices reserved on Abis for EGPRS should be equal to NUMREQEGPRSBPC defined

on cell if ABISALLOC is FIXED

The following Commands need to used to resolve Abis path Unavailable problem.
First need to check the configuration of the cabinet by using this command:

[RXCDP:MO=RXOTG-<TG>;] TG= TG no
// check configuration.
RXMOP:MO=RXOTG-<TG>;
// check confect of the TG
RLBDP:CELL=<CELL ID>;
// check NUMREQEGPRSBPC
RXAPP:MO=RXOTG-<TG>;
// check devices on ABIS
RXAPE:MO=RXOTG-<TG>,DCP=<DCP VALUE>;
// Delete devices from Abis
RXAPI:MO=RXOTG-<TG>,DCP=<DCP VALUE>,DEV=<DEV NAME>;
//Define devices on TG
RXAPI:MO=RXOTG-<TG>,DCP=<DCP VALUE>,DEV=<DEV NAME>,RES64K;
//Reserve 64k devices
on TG

Fault find out by using TG:

RXTCP:MOTY=RXOTG,CELL=<CELL ID>;
RXASP:MO=RXOTG-<TG>;
RXMFP:MO=RXOTRX-<TG>-<TRX>;

// Find the TG value

// Check the Fault on MO
// Check Fault Code No.

Check the Fault Code from FAULT CODE LIST & take the corrective actions
accordingly.
If no fault found in RXASP..
Check RXCDP:MO=RXOTG-<TG>;
Also check RXMSP:MO=RXOTG-<TG>, Subord;

// Check MO Config. Data

// Check MO Status

TS SYNC FAULT
How to find out the TS SYNC fault?
Mainly this problem has come when we used one TG for two cabinets like as cascading
connection; The Synchronization has been lost on the uplink or downlink Transcoder and Rate
Adaptation Unit (TRAU) channels.
How to resolve the Problem.
First we have to Check Abis path from DCP mapping and the physical connectivity should be
on right position like as port A to C and B to D.
The Devices should be defined on correct DCPs w.r.t the Port A,B,C or D at RBS side.
If 2-DIPs are given & 1-DIP needs to be cascaded between two cabinets, then always define
both DIPs to Master cabinet & then cascade one of them with another cabinet.
In case of MBC site there should not be mismatch in devices and DCPs i.e., fault will occur if
900 Mhz band devices attach on 1800 Mhz band devices.
Commands need to used to resolve TS SYNC fault.
RXAPP:MO=RXOTG-<TG>;
// Check ABIS print & find wrong device
RXMDP:MO=RXOTS-<TG>-<TRX>-<TS>;
// Find wrong Device associated with TS
RXBLI:MO=RXOTS-<TG>-<TRX>-<TS>;
// Block the TS
RXESE:MO=RXOTS-<TG>-<TRX>-<TS>; // Out of Service TS
RXAPE:MO=RXOTG-<TG>,DCP=<dcp>;// Remove the device
RXAPP:MO=RXOTG-<TG>;
// Check ABIS print
RXASP:MO=RXOTG-<TG>;
// Check Alarm Status

PERMANENT FAULT
WHY have we need to declare the permanent fault??
The hardware is classified as being permanently faulty when fault situations have
occurred, and have been cleared, a certain number of times within a certain period
of time. Manual intervention is required to bring such equipment back into
operation.
How to confirm that the Problem is permanent.
Give soft reset (Block/De-block) by using the below command:
RXBLI:MO=RXOTRX-<TG>-<TRX>,SUBORD,FORCE;
// Block MO
RXESE:MO=RXOTRX-<TG>-<TRX>,SUBORD;
// Out of Service MO
RXESI:MO=RXOTRX-<TG>-<TRX>,SUBORD;
// In Service MO
RXBLE:MO=RXOTRX-<TG>-<TRX>,SUBORD;
// De-block MO
RXASP:MO=RXOTG-<TG>;
// Check alarm again
RXMFP:MO=RXOTRX-<TG>-<TRX>;
// Check Fault code
RXMSP:MO=RXOTG-<TG>,SUBORD;
// Check MO state
If alarm not vanished then
Give hard reset
If the alarm still there then we confirm that the fault is permanent fault.
Change the Hardware (H/W Faulty)

BTS INT AFFECTED/UNAFFECTED

Problem find out that the hardware is affected or unaffected?
BTS INT AFFECTED - A fault exists in a piece of equipment internal to the BTS that
leads to that equipment not being able to perform its operational function.
BTS INT UNAFFECTED - A fault exists in a piece of equipment internal to the BTS
that does not directly interfere with its operational function.

The below faults have occurred in RBS.

VSWR LIMIT EXCEEDED

ANTENNA HOPPING FAILURE
TX MAX POWER RESTRICTED
CDU OUTPUT POWER LIMIT EXCEEDED
RX CABLE DISCONNECTED
RF LOOP TEST FAULT
RX PATH IMBALANCE

The below Commands need to use for the fault find out.

RXASP:MO=RXOTG-<TG>;
RXMFP:MO=RXOTRX-<TG>-<TRX>;

// Check the alarm situation

// Check Fault Code on MO

Check the Fault Code from FAULT CODE LIST & take the corrective actions
accordingly.
9

BTS INT AFFECTED/UNAFFECTED

10

LOCAL MODE
Why the hardware goes to local mode?
The MO is in Local Mode or the MO has subsequently changed from Local to
Remote Mode and a fault exists in the communication link between the BSC and the
BTS.
How can we try to resolve the Problem..
Escalate to field engineer & get local mode changed to remote mode.
Hard Reset at BTS site & Reload IDB & then Soft Reset.
If from NOC end TRU is showing in local mode and Field engr. says at his end TRU
is blinking (already in remote mode), then check..
RXMSP:MO=RXOCON-<TG>;
RXMSP:MO=RXOIS-<TG>;
Check DCP1 & DCP2 defined on TRUs are correct using command
RXMOP:MO=RXOTRX-<TG>-<TRX>;
If every parameter is properly defined then escalate to field engineer to recheck
TRUs/DXU & related connection & load IDB again.
Change the Hardware

11

LOCAL MODE

TF not Synchronized
WHY Dip is not working properly?
DIP not working or bad quality
DXU E1 Port Faulty
DXU Faulty

How to Resolve the fault.

Give soft & hard reset to DXU or CF

RXBLI, RXESE, RXESI, RXBLE
Check DIP status & DIP Quality
DTSTP:DIP=<DIP>;
DTQUP:DIP=<DIP>;
Reset DIP if error on DIP & Give soft Reset
DTQSR:DIP=<DIP>,ES,SES,SF;
DTQSR:DIP=<DIP>,DEGR,UNACC;
Ask FM engr. to check E1 port & connector at DXU & Reload IDB
If problem does not resolve change the E1 port A to Port B or C or D & Reload IDB
Lastly change DXU.

13

Q. How can we find out the TG number ?

First we have to access in the BSC(BSE<NO>) by EAW BSE<BSC NO>; and then the below command to get the TG number.

rxtcp:moty=rxotg,cell=Cell number

14

Q. How to find out that site is up/down?

A. One cabinet has one TG at least and find out that site is up/down by this command. The operation state is OPER and
configuration is ENA then we confirm that site is up. If state is NOOP and configuration is ENA/UNCONF then site is down .
rxmsp:mo=rxotg-39,subord;

15

Q. How we confirm the hardware related alarm?

Ans: We would like to find out the alarm status of the cabinet by using this command with TG number.

rxasp:mo=rxotg-39;

Q. How we confirm the Time slot are used for data/Speech/signal?

Ans: We have to find out the time slot that are allocated for data/Speech/signal by using this command with TG number.
rxapp:mo=rxotg-39;

16

Q. How can we find out the TG is block/unblock?

Ans: We can found the TG is block/unblock by using this command.

17

Q. How can we find out the software/Hardware version?

software/Hardware version by using this

command with TG.
RXMOP:MO=rxotg-TG Number

Ans: We can found the

18

TG Block and Deblock

19

Q. How can we find out the dip quality into the Dip?
Ans: We have found the dip quality by using this command, IF we have found error on the dip
then dip quality is not perfect for voice call or other data service.

dtqup:dip=DH0216A;

20

Q. Why the dip need to reset?

Ans: We have to measure dip quality status for voice/data service. For this reason we have
reset the dip and again measure the dip quality if the error status increase frequently then we
will confirm that dip quality is not good.

dtqsr:dip=DH0216A,unacc,degr;

21

Related Commands

RXASP Radio X-ceiver Administration MO Alarm Situation, Print

RXMFP - Radio X-ceiver Administration MO Fault Info, Print
RXMSP - Radio X-ceiver Administration MO Status, Print
RXMOP - Radio X-ceiver Administration MO Data, Print
RXCDP - Radio X-ceiver Administration MO Configuration Data, Print
RXMDP - Radio X-ceiver Administration MO Device Info, Print
RXBLI - Radio X-ceiver Administration Manual Blocking of MO, Initiate
RXBLE - Radio X-ceiver Administration Manual Blocking of MO, End
RXESI - Radio X-ceiver Administration MO in Service, Initiate
RXESE - Radio X-ceiver Administration MO Out of Service, End
RXMOI - Radio X-ceiver Administration MO, Initiate
RXMOC - Radio X-ceiver Administration MO, Change
RXMSC - Radio X-ceiver Administration MO In-Service Data, Change
RXPLI - Radio X-ceiver Administration Function Change & Program Load of MO, Initiate

22

Thank You

23