1.

Network Availability Rate:

Network Availability Rate /NAR/ is a calculated value of a cell availability per 24Hrs or one
day., Shortly, NAR calculation bases on a serving RRUS operational or not-operational states of
a cell up to TRX-level. For RRUS operational but partial TRX level we used TCH Availability
cell calculation which is covered latter on 2G Partially down part. Gap on TCH channel level
activities results poor 2G NAR performance.
Consider, a faulty DUG connected 3 RRUS’s results 3X times unavailability than a single faulty
RRUS serving a cell. Currently in our region most of sites got DUG spare issue need as much as
possible a DUG delivery. Faulty DUG is one of the amongst factors that are affecting highly
NAR 2G.
Even if NAR’s highly depends on type of power solution given to that site, Most AC only sites has
a poor NAR performance due to EEU service interruption. Take Group-01 where engagement to
EEU can be taken as good example to other groups. AC only site is available keeping NAR good.
By doing EEU engagement NAR improvement can be achieved.
Still we’re not able to get the minimum targeted values for others ET power solution type used
sites. i.e. AC+DG, Solar and DG+BB. Single site power factors affecting NAR related with DG
Maintenance, DG Fuel and Battery Maintenance more weighted than RAN factors affecting NAR
values.
But here our concern is as a RAN team try to cover factors that are affecting NAR that can be
solved by O&M RAN Team either remote or with site intervention. And methods used to trace
such faults on daily based by using OSS especially on 2G and 3G services.
2. 2G Site Intervention:
2G faults related like OML and Local faults that needs field team interventions. Such faults
raised due to several reason: Probable reason are DUG hardware failure, DUG input power
loss or CF lost its configuration file.
DUGs or RRUSs are sometimes hang means their operating software not ready for operation
instead ready for only maintenance purpose. This happen most of the time during power went
off. After power recovered the DUG/RRUS still stand under maintenance mode instead of being
operational state. In such case a site intervenor needs on site for changing over state from local
to remote state operation by allowing able to communicate the remote network elements.
DUGs with alarm slogan OML indicates when supply input voltage disconnected. In short when
DUG powered off. This may be done by the site intervenors when fault record seen on DUG by
disconnecting supplying voltage cable from PDU or when RBS lost its supply voltage due to site
power lost. All DUG present raise OML Fault. Automatic recovery of RBS supply voltage ceases
OML fault.
.
Following shots took from all alarm fetched in BSC 10 log file. shown DUG failure on BSC side
under Alarm Slogan OML FAULT.

A1/APT "EBS10SH_G17Q3" 158 200407 1513

RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT
MO SCGR SC RSITE ALARM SLOGAN
RXOCF-443 SH_222616 OML FAULT

On intervention at 222616, the DUG serves 1800-Sec3 was interchanged over with G444 DUG
recorded faulty. By considering better coverage and cell availability rate /NAR Correction/.
DUG interchanging made at 222616.
DUG with alarm slogan Local Mode: DUG Hardware failure read from belonging BSC side at
222608 no. 2X DUGs.

A1/APT "EBS09SH_G17.Q3" 232 200416 1606

RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT
MO SCGR SC RSITE ALARM SLOGAN
RXOCF-566 SH_222608 LOCAL MODE
A1/APT "EBS09SH_G17.Q3" 233 200416 1606
RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT
MO SCGR SC RSITE ALARM SLOGAN
RXOCF-567 SH_222608 LOCAL MODE

Depending the given traffic priority: high traffic city site should serve first!! Propose solution by
migrate from other not high traffic sites taking into consideration, 360-degree coverage at least
in either 900 or 1800 band frequency. During my stay G-08 DUG migrates to 222182 (i.e. Site
with high traffic) from 222472 totally down for a long period of time.
By login OMT locally monitor alarm raised and health state check on a Master DUG on a GSM
Node. All fault generated from Antenna Branch A&B, Jumper cable VSWR value greater than
the threshold set point given in OMT for VSWR Limit Class 1 and VSWR Limit Class 2, RRUS
related alarm raised in TRX level and MCTR power, CPRI, SFP, GPS Sync, Idle cable used DU
to DU communication and environmental or climate system of fan groups used in RBS.
Followed vendor, Ericsson recommendation on VSWR monitoring during Mixed Mode sites.
Both 2G and 3G in the same band 900.VSWR related fault finding from 3G DUW is very
recommended and reliable than using 2G DUG.
DUG Health state checking during site intervention, Monitoring fault alarm in DUG’s that might
not directly affect the service. Such faults are mostly raised in IDB inconsistency just for
information only. Whenever need to clear such alarm permanently re-installation in IDB used.
Mostly, those alarms ignored as it is because of service served by the DUG affected during new
IDB re -installation period of time.
Last but not least, perform RBS preventive maintenance/PM/ whenever on-site intervention for
corrective maintenance/CM/. Strictly followed PM Backlog GAP report in my belonging group.
Plan as much as possible both jobs to be done at a time. On 222599 and 222636, Both CM + PM
done in the same day.

1. OSS-BSS Remote O&M.

G-08 BULE-HORRA O&M OSS-BSS Support:
Used WinFIOL alarm management software as a tool in every daily operation and maintenance
to follow-up site status. Both 2G & 3G technologies and their services. By extracting log file
fetched from WinFIOL in to network overall status.xls file filter site status accordingly Totally
Down, 2G Down, 3G Down, 2G Partial, 3G partial and 2G&3G Partial faults. Edit WinFIOL
command file to export network element status as per the demands.3G Down and 3G partial will
be closed in 3G part.
3.1 Totally Down
SMS or Call for totally down sites and plan accordingly traffic type priority, Uplink Site and
their power solution type used. Office follow-up in case OSS- BSS support needs from site
intervenors. Most of the time unknowingly 2G service needs DUG remote BSS side resetting
after site power maintained.
 SITE ID Boundary Group Traffic Type TOWN Uplink >=4 Priority Site STATUS
222177 DILLA SR-MOB-G08 Not High Traffic Hageremariam Uplink Uplink_Hageremariam_Not High Traffic Totally Down
222467 DILLA SR-MOB-G08 Not High Traffic Uplink Uplink_Not High Traffic Totally Down
222375 DILLA SR-MOB-G08 Not High Traffic Totally Down
222174 DILLA SR-MOB-G08 Not High Traffic Totally Down
222173 DILLA SR-MOB-G08 Not High Traffic Totally Down
222465 DILLA SR-MOB-G08 Not High Traffic Totally Down
222469 DILLA SR-MOB-G08 Not High Traffic Totally Down
222466 DILLA SR-MOB-G08 Not High Traffic Totally Down
222317 DILLA SR-MOB-G08 Not High Traffic Totally Down
222470 DILLA SR-MOB-G08 Not High Traffic Totally Down
222471 DILLA SR-MOB-G08 Not High Traffic Totally Down
Table: Shows G-08 Totally Down Sites 01/22/2020 at 8:45 AM.

3.2 2G Down
Only 2G down while 3G is up occurred in daily operation. This happens unknowingly DUG get
still standing not operational mode/NOOP/ even supplied with optimum voltage that needs after
site power maintenance or power recovered. No longer communicating with TCU results Abis
interface lost to its respecting BSC. Remote BSC resetting DUGs help to get back its Abis
interface.
In some solar sites, During night time battery discharges. Supplied voltage gradually fall. Site
feed from under-voltage batteries during night time. For example, 222322 even during the
day/morning time solar panel charges battery and minimum required voltage meets for DUG
operation, DUG still stand in not operational /NOOP/ Mode and needs remote BSC resetting to
make it Operational mode.
Below table lists of site needs remote or local site intervention. 2G down while its 3G is serving:

SITE ID Boundary Group Traffic Type TOWN Uplink >=4 Priority Site STATUS
222179 DILLA SR-MOB-G08 Not High Traffic Hageremariam Hageremariam_Not High Traffic 2G Down
222340 DILLA SR-MOB-G08 Not High Traffic 2G Down
222183 DILLA SR-MOB-G08 Not High Traffic 2G Down
222376 DILLA SR-MOB-G08 Not High Traffic 2G Down
Table 2: Shows G-08 2G Down Sites 01/22/2020 at 8:45 AM.

NB: Before rushing to conclude, we can further proceed fault RCA finding by login into DUW
since 3G is reachable for O&M while 2G not. Using alt command current alarm on DUW can be
listed out. If there is alarm says commercial power failure we stop there and communicate power
team for further RCA.
Below sample took from 3G alarm history during site main power unavailable but DUW
operating on battery from 222375.In different severity major and critical. Critical raised after 12
minutes loss in mains alarm activated.
2020-01-10 01:16:44 AL M AuxPlugInUnit_LossOfMains SectorAntenna=3-
1,AuxPlugInUnit=RRUW-1 (commercial_power_failure)
2020-01-10 01:16:44 AL M AuxPlugInUnit_LossOfMains SectorAntenna=2-
1,AuxPlugInUnit=RRUW-1 (commercial_power_failure)
2020-01-10 01:16:44 AL M AuxPlugInUnit_LossOfMains SectorAntenna=1-
1,AuxPlugInUnit=RRUW-1 (commercial_power_failure)
2020-01-10 01:16:58 AL * AuxPlugInUnit_LossOfMains SectorAntenna=3-
1,AuxPlugInUnit=RRUW-1 (commercial_power_failure)
2020-01-10 01:16:58 AL * AuxPlugInUnit_LossOfMains SectorAntenna=1-
1,AuxPlugInUnit=RRUW-1 (commercial_power_failure)

Generally, this is because of cutting time during power failure is different for DUG and DUW.
DUW stays a little bit longer.
3.3 2G Partial
Most abundant type of fault occurred in all SR groups GSM Network. Mostly failure in DUG and
RRUS hardware.
Ignoring such fault as a hardware fault is completely wrong unless the fault alarm raised seen in
OSS BSS side. Here, we’ll see DUGs contained with PERMANENT FAULT and BTS INTERNAL
alarms and their resetting operation being done to make it back to operational.
.3.3.1 PERMANENT FAULT
BSC issues a PERMANENT FAULT alarm and set the DUG state to FAIL. Raised when BSC
considers an issue that prevent the DUG operation permanently.
Such faults exist in every BSCs can occurred anytime unless we follow up those sites and take
action. Controlling this type of fault must consider in the future for every group O&M teams with
their belonging BSCs.

A2/APT "EBS09SH_G17.Q3" 990 200416 1304

RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT
MO SCGR SC RSITE ALARM SLOGAN
RXOTRX-70-11 SH_222092 PERMANENT FAULT
A2/APT "EBS09SH_G17.Q3" 991 200416 1305
RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT
MO SCGR SC RSITE ALARM SLOGAN
RXOTRX-70-9 SH_222092 PERMANENT FAULT
A2/APT "EBS09SH_G17.Q3" 005 200416 1307
RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT
MO SCGR SC RSITE ALARM SLOGAN
RXOTRX-70-8 SH_222092 PERMANENT FAULT
A2/APT "EBS09SH_G17.Q3" 024 200416 1311
RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT
MO SCGR SC RSITE ALARM SLOGAN
RXOTRX-70-10 SH_222092 PERMANENT FAULT

Figure shown alarm log 222092 with permanent fault type.

FIGURE Log Files 222092 TRX Blocked.

FIGURE Log Files 222092 TRX Operational after Resetting operation.
3.3.2 BTS INTERNAL
Fault reported in this class affect DUG functionality. Remote resetting the DUG take to back
normal operation. Operates dilly based on field support office time.
Such faults exist in every BSCs can occurred anytime unless we follow up those sites and take
action. Controlling this type of fault must consider in the future for every group O&M teams with
their belonging BSCs.
A2/APT "EBS10SH_G17Q3" 137 200417 0911
RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT
MO SCGR SC RSITE ALARM SLOGAN
RXOTX-471-2 SH_222525 BTS INTERNAL
A2/APT "EBS10SH_G17Q3" 138 200417 0911
RADIO X-CEIVER ADMINISTRATION
MANAGED OBJECT FAULT
MO SCGR SC RSITE ALARM SLOGAN
RXOTX-471-0 SH_222525 BTS INTERNA

FIGURE Log Files 222525 BTS INTERNAL FUALT.

FIGURE Log Files 222525 TRX Blocked.

FIGURE Log Files 222525 TRX Operational after Resetting operation.

 2. OSS-RNC Remote O&M.
As long as the O&M accessible/reachable most configuration, operation and maintenance task
done remote OSS-RNC side.
Generally, 3G issues can be categorize into two parts: 3G Totally Down and 3G Partially
Down.3G totally down site needs site intervention whereas most 3G partial down except
hardware related failure can maintained OSS-RNC side.
2.1 3G Totally Down
Happened when either DUW lost its configuration or DUW hardware failure recorded. 3G
totally down issue raised more than 90% due to configuration lost not in hardware failure.
Whenever configuration lost in DUW, site intervenor should at least formatting DUW and install
scripts (i.e. Cabinet, O&M, Site Equipment and IUB). License Key File /LKF/ installed in office
OSS side up on completion all the basics above on site.
When we see the root causes of script losing in DUW, we can generally divide into two
categories: Environment & climate system and Power System Fluctuation
4.1.2 Environment and Climate System
In RBS 6000 families the environment and climate system controlled by master DUG. Whereas
in only 3G sites DUW take the support system controlling function. Almost all 3G only sites
implemented on 6301 RBS Cabinet type.
Pole mounted cabinet RBS6301 type used in our region. Where controlling environment and
climate system is a little bit difficult comparing to others outdoor and indoor RBS 6000 families.
Cabinet RBS 6301’s very compact in size, PDU, CN, DUG, DUW and TCU all in one compacted
together. No free space for air circulation. By no any means such cabinet will not be
recommended for hot areas like DILLA.

RBS 6301
Dilla town only 3G sites with RBS 6301 Cabinet type used. Sites 222255,222259 and 222262
where I intervenor on formatting and license key installation.
On top of that, Site with only 3G platform, DUW control master operation. So, we have to make
sure the support system control be “TRUE” for all only 3G sites and “FALSE” for other sites.
There’re still 3G Only sites with support system control parameter defined false. Lists will be
given up on your request.
Some of us believed when DUW configured as a master fan rotational speed high and annoying.
Then we convert it as a FALSE instead making it TRUE. Better to go to through it with all teams
and come up with one option.
4.1.2 Power System Fluctuation
Frequent power interruption with zero load batteries sites results in digital unit software
hanging and hardware failure. Example,222042 and 222375 lost scripts and formatted more
than 2 times during in my stay in G_08 BULE HORRA Region.
2.2 3G Partial
3G partial issue raised in my experience may be in one of the fallowing things: RRUS failure,
Layered TMA sites script, RRUS Blocked mode, RRUS CPRI Data 1 & Data 2 cross connection,
Fiber cable damage/cut, SFP, Jumper VSWR loose connection, during site equipment/SE/ script
installation invalid cell ID definition which different from defined RNC side and gap between
NNOC and SR O&M during on band 2100 frequency high and low change.
2.2.1 Layered TMA Site
Site equipment script installed after layered in G_08 BULE HORRA on both city sites 222178
and 222177 <Tmaconfiguration>-<Tmasector> not defined. with a default TMA parameter
values. Our one NAR 3G improvement boost and shown after this troubleshooting made by
coordinating with senior RAN Experts from ERICSSON side. Bule Horra weekly 3G
performance improved from 75 % to 95% and keeps the value till now.

4.2.2 RRUS Blocked mode

On daily based in case such faults raised unless the RRUS hardware failure recorded lock /
unlock or lbl/ldebl resets the RRUS to its operational mode.
Figure below screen shot took during the lock / unlock operation done on OSS-Common explorer
window at 222455.
Fig: Shows 222455 Locked cell

Fig: Shows 222455 Unlocked cell

4.3.3 SFP Modules
Due different type of SFP Module used in Ericsson site performance of SFP different. G-07 Dilla
222236.One of SFP Module on DUW Side was on and off and very hot when we take out. The
SFP module used is not recommended and isn’t a product of Ericsson. The same procedure
works G-08 Bule Horra 222360.

222236> lga

200117-15:33:55 10.207.200.27 17.0g RBS_NODE_MODEL_U_4_343 stopfile=/tmp/13566

Please enter Node Password:

Startdate=19661031.171320, Enddate=20200118.123400

2019-12-31 09:55:20 AL M AuxPlugInUnit_PiuConnectionLost SectorAntenna=2-1,AuxPlugInUnit=RRUW-1

(RRUW)

2019-12-31 09:55:30 AL * AuxPlugInUnit_PiuConnectionLost SectorAntenna=2-1,AuxPlugInUnit=RRUW-1

(RRUW)

2019-12-31 09:55:41 AL M AuxPlugInUnit_PiuConnectionLost SectorAntenna=2-1,AuxPlugInUnit=RRUW-1

(RRUW)

2019-12-31 09:56:42 AL * AuxPlugInUnit_PiuConnectionLost SectorAntenna=2-1,AuxPlugInUnit=RRUW-1

(RRUW)
2019-12-31 09:56:53 AL M AuxPlugInUnit_PiuConnectionLost SectorAntenna=2-1,AuxPlugInUnit=RRUW-1
(RRUW)

2019-12-31 09:57:05 AL * AuxPlugInUnit_PiuConnectionLost SectorAntenna=2-1,AuxPlugInUnit=RRUW-1

(RRUW)

2019-12-31 09:57:16 AL M AuxPlugInUnit_PiuConnectionLost SectorAntenna=2-1,AuxPlugInUnit=RRUW-1

(RRUW)

Alarm related with SFP Modules on the connected plug in units RRUS or DUW raised with flag
PiuConnectionLost on it. With this alarm replace SFP. I recommend all team with such partial
issue by exporting the history alarm to find degraded SFP module. Because, this alarm might
raise and ceased automatically. For those catching PiuConnectionLost longer needs replacement.
4.3.4 VSWR
VSWR Measurement reading took during troubleshooting Antenna Branch System of 222467.
New RRUS 12 B8 on sector 3 replaced but after a while on 2G out of 5 trx 2 gets blocked and 3G
carriers blocked too. Resetting RRU recovered latter problem arise again after a while. Open
fault not yet traced.
 4.3.5 2100 Frequency Band Change
NNOC made a frequency plan change on both high and low frequency 2100 band. Without
updating SR O&M team by pushing it from RNC side. But the site equipment generator we use
old version and not updated those changes. Resulting 21000 one carrier in each sector unable to
take traffic.
Old fq values:
fqBandHighEdgeBranchA="21300" fqBandLowEdgeBranchA="21100"
updated fq values:
fqBandHighEdgeBranchA="21350" fqBandLowEdgeBranchA="21150"

NB: All teams should update their site equipment script generator. And make sure the generated
site equipment fq parameter values accordingly the new plan.
222182 with old Vs update fq change band plan after formatting DUW hang.
222182> get radio no

200311-16:17:16 10.207.229.115 17.0g RBS_NODE_MODEL_U_4_672 stopfile=/tmp/11840

======================================================================================

MO Attribute Value

======================================================================================

Sector=1,Carrier=1,RadioLinks=1 noOfRadioLinks 16

Sector=2,Carrier=1,RadioLinks=1 noOfRadioLinks 53

Sector=3,Carrier=1,RadioLinks=1 noOfRadioLinks 18

Sector=4,Carrier=1,RadioLinks=1 noOfRadioLinks 0

Sector=4,Carrier=2,RadioLinks=1 noOfRadioLinks 11

Sector=5,Carrier=1,RadioLinks=1 noOfRadioLinks 0

Sector=5,Carrier=2,RadioLinks=1 noOfRadioLinks 10

Sector=6,Carrier=1,RadioLinks=1 noOfRadioLinks 0

Sector=6,Carrier=2,RadioLinks=1 noOfRadioLinks 45

======================================================================================
===========================

222182> get radio no

200311-16:23:21 10.207.229.115 17.0g RBS_NODE_MODEL_U_4_672 stopfile=/tmp/11840

======================================================================================
MO Attribute Value

======================================================================================

Sector=1,Carrier=1,RadioLinks=1 noOfRadioLinks 5

Sector=2,Carrier=1,RadioLinks=1 noOfRadioLinks 40

Sector=3,Carrier=1,RadioLinks=1 noOfRadioLinks 4

Sector=4,Carrier=1,RadioLinks=1 noOfRadioLinks 9

Sector=4,Carrier=2,RadioLinks=1 noOfRadioLinks 15

Sector=5,Carrier=1,RadioLinks=1 noOfRadioLinks 13

Sector=5,Carrier=2,RadioLinks=1 noOfRadioLinks 16

Sector=6,Carrier=1,RadioLinks=1 noOfRadioLinks 42

Sector=6,Carrier=2,RadioLinks=1 noOfRadioLinks 46

======================================================================================
===========================

“Transmission part up on your request”

Trainee new O&M G-08 BULE HORRA staffs:

Microsoft Excel
97-2003 Worksheet