Ultima Fort Required Data Inputs for Ericsson Infrastructure

March 08 Proprietary and Confidential 1 of 19

Schema






Ultima Fort

Required Data Inputs for Ericsson
Infrastructure
(for Version 4.0 and above)



Copyright Notice
Due to a policy of continuous product development and refinement, Schema reserves the right to alter the
specifications and descriptions outlined in this publication without giving prior notice of any kind. In addition,
no part of this publication, taken as a whole or separately, shall be deemed to be part of any contract for
equipment or services.
Schema retains the sole proprietary rights to all information contained in this document. No part of this
publication may be reproduced, stored in a retrieval system, transmitted in any form or by any means,
including but not limited to: electronic, mechanical, magnetic, photocopy, recording, or otherwise, in use now
or in the future, without prior written consent from Schema.
Copyright 2008 Schema
Ultima Fort Required Data Inputs for Ericsson Infrastructure

March 08 Proprietary and Confidential 2 of 19
Schema


Table of Contents
1 Introduction.............................................................................................. 3
2 Required Information and Data................................................................. 4
2.1 Optimization Area...........................................................................................4
2.2 Network Data.................................................................................................4
2.2.1 Ericsson BSS Network Configuration........................................................4
2.2.2 Ericsson BSS Network Configuration - R12: NEW CNAI...............................6
2.2.3 Sector Coordinates File..........................................................................6
2.3 Mobile Measurements Data Collection................................................................6
2.3.1 Binary Format Files ...............................................................................7
2.3.2 Text Format Files................................................................................ 12
2.3.3 Handover Statistics ............................................................................. 13
2.4 Network Performance Statistics ...................................................................... 13
2.4.1 Network Performance Evaluation........................................................... 14
2.4.2 Radio Network Performance KPI Calculation............................................ 15
2.4.3 Additional KPIs for Network Performance Evaluation ............................... 15
3 Data Collection Checklist......................................................................... 17
4 Appendix: Troubleshooting ..................................................................... 18
4.1.1 The removeFile Parameter for BARFIL and MRR File Deletion..................... 18
4.1.2 Additional Ericsson Information............................................................. 19
4.1.3 Parameter Database (PDB) Maps .......................................................... 19


Ultima Fort Required Data Inputs for Ericsson Infrastructure

March 08 Proprietary and Confidential 3 of 19
Schema

1 Int r oduct i on
This document contains a list of the information and data to be collected for Ericsson GSM
infrastructures in order to perform an optimization cycle using Ultima Fort.
The following information is required:
Optimization area and optimization goals
Ericsson BSS network configuration data
Sector coordinate data
Mobile measurement recordings
Performance reports
This document not only identifies the required sources of data, but also explains how to obtain
the data.



Ultima Fort Required Data Inputs for Ericsson Infrastructure

March 08 Proprietary and Confidential 4 of 19
Schema

2 Requi r ed Inf or mat i on and Dat a
2.1 Opt i mi zat i on Ar ea
The following information is required to analyze a network:
List of cells in the optimization and surrounding areas (optimization set and guard zone)
Available spectrum for all bands
List of frequencies to be used as BCCH channels
List of frequencies to be used as TCH channels
Current frequency planning strategy (BB,1:1, 1:2, , per site, per cell, ad-hoc, )
Desired optimization strategy (BB, 1:1, 1:2, , per site, per cell, ad-hoc, )
2.2 Net wor k Dat a
2.2.1 Er i csson BSS Net wor k Conf i gur at i on

Retrieve the required BSS network configuration file from the Ericsson OSS, using the Cellular
Network Administrator (CNA), by running the following commands:
Overall Network configuration:
cna_export NW = all, MSC = all, MSC_REF = none, BSC = all, BSC_REF = all, SITE = all,
SITE_REF = none, CELL = all, CELL_REF = all, OUTPUT=AllParameters_YYYYMMDD.txt
Foreign cells:
cna_export NW = all, FCELL = all, FCELL_REF = all, OUTPUT=foreign_HO_YYYYMMDD.txt
(where: YYYY year, MM month, DD day)
Ultima Fort Required Data Inputs for Ericsson Infrastructure

March 08 Proprietary and Confidential 5 of 19
Schema

Notes:

Foreign cell data must be exported only when the BSS network configuration data for the
surrounding networks (including other Ericsson OSS, the network configurations of other
vendors, or UMTS networks) has been provided. Ultima Fort will not create neighbor
relations with other networks if this file is not provided.
Daily CNA adjustment jobs should be scheduled for each BSC to ensure that the network
configuration is updated in the OSS.
It is recommended that the BSS network configuration file be retrieved for each day of mobile
measurement recordings. However, it is mandatory that this file be retrieved if any
BCCH/BSIC changes were made between two days of recordings.
The BSS network configuration file should be generated just before initiating the BAR and
MRR recording sessions.
The BSS network configuration should be retrieved for each OSS that is relevant to the
optimization and surrounding areas in the network.
BSC data is optional beginning from Release R12.

In the beginning and end of the data collection process, the following optional data should be
retrieved for all BSCs, and included in the Ultima Fort network environment:

Data Description
RLCRP:CELL=ALL,DETAIL;
Cell Resources
Details
RXMOP:MOTY=RXOTG;
Managed Object
Data
RAEPP:ID=ALL;
BSC Exchange
Properties

Data retrieval should be performed via the BSC command line interface.
The output of the command printout should be stored in text files. The command name (RLCRP,
RXMOP, RAEPP) of each output type should be at the beginning of the file name, e.g.,
RLCRP_BSC1.txt.

Ultima Fort Required Data Inputs for Ericsson Infrastructure

March 08 Proprietary and Confidential 6 of 19
Schema

2.2.2 Er i csson BSS Net wor k Conf i gur at i on - R12: NEW CNAI
Release R12 supports the New CNAI (CNA Import) alternative format for network configuration
files.
The required BSS network configuration file can be retrieved from the Cellular Network
Administrator (CNA) of the Ericsson OSS with the following command: CNAI export valid i >
AllParameters_YYYYMMDD.txt.

2.2.3 Sect or Coor di nat es Fi l e
The sector coordinates file should be in tab-delimited text file format, and should include
geographical information for all of the network sectors, including the following columns:
Sector
Latitude
Longitude
Azimuth
LAC (optional)
CI (optional)
Keywords (optional)
The latitude and longitude values should be expressed in decimal-degree format, with up to six
digits following the decimal point.
2.3 Mobi l e Measur ement s Dat a Col l ect i on
The following network activities should stop during the time that data is recorded:
BSC split
Site re-homing (BSC/site relations change)
Changes of LAC and CI
Sector mechanical changes, such as tilt, azimuth, and antenna changes
Ultima Fort Required Data Inputs for Ericsson Infrastructure

March 08 Proprietary and Confidential 7 of 19
Schema

The following changes should be performed only during maintenance (not during recording):
TRX additions
Frequency changes (TCH)
Frequency changes (BCCH and BSIC)
Neighbor additions or deletions
Site additions
No other parameters should be changed.
Note (1): The BSC and OSS must be Version R8 or later versions.

The Mobile Measurements files can be extracted, as explained below, from the Ericsson OSS and
used by Ultima Fort either in binary format (Section 2.3.1) or in text format (Section 2.3.2).

2.3.1 Bi nar y For mat Fi l es
Binary format files contain C/I measurements.

2.3.1.1 BA list recordings (BAR) Recordings
BAR recordings should be performed during three to five consecutive working days.
The BAR recording is activated by the:
RNO interface (if available)
BSC command interface
To perform BAR recordings using the RNO interface:
1. Log in to OSS.
2. Start RNO.
3. Go to FileNew RecordingNCS.
4. Name the recording session.
5. Set the Relative SS Threshold to -12db.
6. Set the Absolute SS Threshold to -80dbm.
7. Set the BA List Change interval to 15 minutes.
Ultima Fort Required Data Inputs for Ericsson Infrastructure

March 08 Proprietary and Confidential 8 of 19
Schema

8. Set the number of test frequencies to add to each interval to 10.
9. Enter a start date.
10. Enter a repeat value (set to daily) and a number of repetitions (set to 5).
11. Enter a date type, working days only (Monday to Friday five consecutive working days,
for example).
12. Enter an hour range (Four hours should be defined to include the network busy hour).
13. Select the cell set or BSC (including every cell in the entire network).
14. Set the Cell Filter to a desired (available) frequency band (The recorded cell set should be
limited to a specified frequency band.)
15. Select Frequencies. Create a Frequency Set for BAR recordings, including all frequencies
used for BCCH in the desired band for the entire network.
16. Save and schedule the recording.
Note:
In a dual band network, recordings should be made separately, based on the cell band. However,
in order to provide full functionality of handover optimization, inter-band recordings should be
performed. Each band cell set should record a frequency set with the BCCH frequencies for both
bands.
While BAR files can also be generated with the Frequency Allocation Support (FAS), the
Neighboring Cell Support (NCS) should be used if possible.
If an operator has not purchased the RNO application to activate BAR recordings through NCS,
the BAR recordings can be activated by using the BSC command line interface, as follows:
1. RABRE:RID=RARID00; Terminate an NCS recording.
2. RABIE:RID=BARID00; Delete a recording.
3. RABII; Initiate a new recording.
4. RABRP:RID=BARID00; Print a BAR recording status (optional).
5. RABDC:RID=BARID00, CELL=ALL; All cells of a BSC are recorded.
6. RABDC:RID=BARID00,TMBCCHNO=50&&124; Frequencies to measure 50 to 124.*
7. RABDC:RID=BARID00,NUMFREQ=10; The number of test frequencies at each interval.
8. RABDC:RID=BARID00,SEGTIME=15; The recording segment time in minutes.
9. RABDC:RID=BARID00,RELSSN=12; Negative signal strength thresholds.
10. RABDC:RID=BARID00,RELSS2P=0; Positive signal strength thresholds.
Ultima Fort Required Data Inputs for Ericsson Infrastructure

March 08 Proprietary and Confidential 9 of 19
Schema

11. RABDC:RID=BARID00, ABSS=80; Absolute signal strength (means negative dBm).
12. RABDP:RID=BARID00; View recording properties.
13. RABRI:RID=BARID00,DTIME=120; Recording period time in minutes; recording starts as
soon as this command is entered!
14. RABTI:RID=BARID00,IO=FILE; After recording is complete, this command should be run
to create the output binary file in the OSS.
15. RABTI:RID=BARID00, IO=AT-##; Substitute at-## with the number of the AT device
seen when connecting to this BSC. The text output will be produced at AT-## device**.
* - The relevant frequency set should be used for each specific case.
** - If, for some reason, a binary file cannot be created, the BAR text output can be
generated at the BSC command terminal, with the generated printout being stored as a
text file.
Once recording is finished, store the BARFILs files for each BSC on FTP. If this is not done within
48 hours after the recording, it will be deleted from the system.
Binary BARFILs files are located in the following OSS directories:
R8:
o /var/opt/ehpt/eac/data/fs/BSC_NAME/

R9/R10 and later with IOG20:
o /root/var/opt/ericsson/nms_eam_eac/data/fs/BSC_NAME/

R9/R10 and later with APG40:
o /root/var/opt/ericsson/brf/data/db/tmpfileStore/BSC_NAME/
Note:
When BARFILs are transferred from UNIX to Windows via FTP, the binary transfer method should
be used. All BARFILs recorded on the same day should be stored in the same directory.
The Appendix contains instructions on troubleshooting situations in which BAR files are not
created.

2.3.1.2 MRR Recordings
Measurements Results Recordings (MRR) Recordings files contain RxLevel, Rxqual, and traffic
data.
Ultima Fort Required Data Inputs for Ericsson Infrastructure

March 08 Proprietary and Confidential 10 of 19
Schema

MRR recordings should be generated with, and for the same cell set as, BAR recordings. No
filtering or thresholds should be applied to MRR recordings.
An MRR recording may be activated via:
RNO interface (if available)
BSC command interface
To make MRR recordings using the RNO interface:
1. Log in to OSS.
2. Start RNO.
3. Go to FileNew RecordingMRR.
4. Name the recording session.
5. Enter a Start date.
6. Enter a repeat value (set to daily) and a number of repetitions (set to 5).
7. Enter a date type, working days only (Monday to Friday five consecutive working days).
8. Enter hour range (Three hours should be defined to include the network busy hour).
9. Select the cell set or BSC (including every cell in the entire network).
10. Set Cell Filter to a desired (available) frequency band (The recorded cell set is limited to a
specified frequency band.)
11. Save and schedule the recording.
If an operator has not purchased the RNO application to activate MRR recordings, the MRR
recordings can be activated by using the BSC command line interface, as follows:
1. RAMRE: RID=MRRID00; Terminate an MRR recording.
2. RAMIE: RID=MRRID00; Delete a recording
3. RAMII; Initialize a new recording
4. RAMRP: RID=MRRID00; Print status (optional).
5. RAMDC: RID=MRRID00, CELL=ALL; All cells of a BSC are recorded.
6. RAMDC: RID=MRRID00, MEASTYPE=NOTYPE; All measurement types are collected.
7. RAMRI: RID=MRRID00, DTIME=120; Recording period time; the recording starts as soon
as this command is entered!
8. RAMRP: RID=MRRID00; Print status (optional).
9. RAMTI: RID=MRRID00; After the recording is finished, this command should be run to
create the output file.
Ultima Fort Required Data Inputs for Ericsson Infrastructure

March 08 Proprietary and Confidential 11 of 19
Schema

When the recording is finished, store the MRRFILs files for each BSC on an FTP. If this is not done
within 48 hours after the recording, it will be deleted from the system.
Binary MRRFILs files are located in the following OSS directories:
R8:
o /var/opt/ehpt/eac/data/fs/BSC_NAME/
R9/R10 and later with IOG20:
o /root/var/opt/ericsson/nms_eam_eac/data/fs/BSC_NAME/
R9/R10 and later with APG40:
o /root/var/opt/ericsson/brf/data/db/tmpfileStore/BSC_NAME/
Notes:
When MRRFILs are transferred from UNIX to Windows via FTP, the binary transfer method
should be used.
All MRRFILs recorded on the same day should be stored in the same directory.
The Appendix contains instructions on troubleshooting situations in which MRR files are not
created.

2.3.1.3 RIR Recordings
The RIR recording files contain uplink interference data.
RIR recordings should only be generated when there is an external interference observed in the
network on the uplink. This type of recording mainly relates to the GSM900 band.
External interference may come from other networks, cordless phones, surveillance systems,
military equipment, and other sources. This external interference may be constant or sporadic.
Constant external interference can be identified with a short RIR recording.
RIR recordings can be activated using the BSC command line interface, as detailed below:
1. RARRE: RID=RIRID00; Terminate an RIR recording.
2. RARIE: RID=RIRID00; End of recording.
3. RARII; Initialize a new recording.
4. RARRP: RID=RIRID00; Print status (optional).
5. RARDC: RID=RIRID00, CELL=ALL, CSYSTYPE=GSM900; All cells in the GSM900 band in a
BSC will be recorded.
6. RARDC: RID=RIRID00, ARFCN=60&&124; Frequencies from 60 to 124 will be recorded.
Ultima Fort Required Data Inputs for Ericsson Infrastructure

March 08 Proprietary and Confidential 12 of 19
Schema

7. RARRI: RID=RIRID00, DTIME=300; Recording period in minutes; the recording starts as
soon as this command is entered!
8. RARRP: RID=RIRID00; Print status (optional).
9. RARTI: RID=RIRID00; After the recording is finished, this command should be run to
create the output file.
When the recording is finished, store the RIRFILs files for each BSC on the FTP. If this is not done
within 48 hours after the recording, it will be deleted from the system.
Binary RIRFILs files are located in the following OSS directories:
R8:
o /var/opt/ehpt/eac/data/fs/BSC_NAME/
R9/R10 and later with IOG20:
o /root/var/opt/ericsson/nms_eam_eac/data/fs/BSC_NAME/
R9/R10 and later with APG40:
o /root/var/opt/ericsson/brf/data/db/tmpfileStore/BSC_NAME/
Note:
When RIRFILs are transferred from UNIX to Windows via FTP, the binary transfer method should
be used. All RIRFILs recorded on the same day should be stored in the same directory.
FAS RIR recordings can only be activated for BSC software R9.1, and later versions, and RBS
software 8.4. RIR recordings should not be initiated for previous versions since they may take
timeslots out of service.

2.3.2 Text For mat Fi l es
2.3.2.1 NCS Recordings
NCS Recording files, available in the RNO application window, contain C/I measurements, which
are similar to the information available in the raw binary BAR recordings.
NCS files can be exported from the RNO application window in pairs, one with an .msmt
extension (data) and one with a .conf extension (file configurations and recordings information).

2.3.2.2 MRR Recordings
MRR Recording files contain RxLevel, Rxqual, and traffic data, which can be extracted in either
binary or text formats. Text format can be exported directly form the RNO application window.
Ultima Fort Required Data Inputs for Ericsson Infrastructure

March 08 Proprietary and Confidential 13 of 19
Schema

Text MRR files are extracted in pairs: one with an .msmt extension (data) and one with a .conf
extension (file configurations and recordings).
MRR recordings are exported to ASCII files via the RNO GUI. Both export files (.msmt and .conf)
should be transferred. The data from these files may be used to back up MRRFIL files.

2.3.2.3 FAS Recordings
FAS Recordings files contain uplink interference and can be exported in text format
(corresponding to RIR files) directly from the RNO application window.
FAS recordings should be generated only when external interference is observed on the uplink in
the network. This recording type relates mainly to the GSM900 band.
Text FAS files are extracted in pairs, one with an .msmt extension (data) and one with a .conf
extension (file configuration and recordings).

2.3.3 Handover St at i st i cs
Handover statistics for each cell-to-cell relation should be collected for handover optimization.
This data should be aggregated over one week for each cell-to-cell relation, and provided in a
tab-delimited text file with the following fields:
Serving Sector
Target Sector
Handover Attempts
2.4 Net wor k Per f or mance St at i st i cs
Network performance statistics should be collected for network traffic modeling and post-
optimization network performance benchmarking.
The following network performance statistics should be collected per cell, and calculated hourly
over seven consecutive days:
SDCCH Assignments
CCALLS, CCALLSSUB, CMSESTAB, CMSESTABSUB, CCONGS, CCONGSSUB, CNRELCONG
SDCCH Traffic
CTRALACC, CTRALSUB
SDCCH Performance
CNDROP
Ultima Fort Required Data Inputs for Ericsson Infrastructure

March 08 Proprietary and Confidential 14 of 19
Schema

TCH Assignments. These statistics should include the following counters:
TASSALL, TFCASSALL, THCASSALL, TFNCASSALLSUB, THNCASSALLSUB, TMSESTB, TFMSESTB,
THMSESTB, TFMSESTBSUB, THMSESTBSUB, TFCONGSAS, THCONGSASSUB, TFNRELCONG,
THNRELCONG, TFNRELCONGSUB, THNRELCONGSUB
TCH Traffic (Traffic per Cell, Traffic per OL/UL, Traffic HR/EFR and per OL/UL, Traffic AMR
FR/AMR HR and per OL/UL). These statistics should include the following counters:
TFTRALACC, THTRALACC, TFTRALSUB, THTRALSUB, TSCAN, TFNSCAN, THNSCAN,
TFNSCANSUB, THNSCANSUB, TTCONGS, TFTCONGS, THTCONGS, TFTCONSUB, THTCONSUB
TCH Performance (Drops, Drops per OL/UL, Drops Reason, Drops Reason per OL/UL, Normal
Disconnection, Bad Quality). These statistics should include the following counters:
TFNDROP, THNDROP, TFNDROPSUB, THNDROPSUB, TFDISTA, THDISTA, TFDISTASUB,
THDISTASUB, TFDISSUL, TFDISSSDL, TFDISSSBL, TFDISSSULSUB, TFDISSSDLSUB,
TFDISSSBLSUB, THDISSSUL, THDISSSDL, THDISSSBL, THDISSSULSUB, THDISSSDLSUB,
THDISSSBLSUB, TFDISQAUL, TFDISQADL, TFDISQABL, TFDISQAULSUB, TFDISQADLSUB,
TFDISQABLSUB, THDISQAUL, THDISQADL, THDISQABL, THDISQAULSUB, THDISQADLSUB,
THDISQABLSUB, TFSUDLOS, THSUDLOS, TFSUDLOSSUB, THSUDLOSSUB
The following performance statistics should be collected and calculated daily for each cell relation,
for seven consecutive days:
HO Performance (Cell to Cell Relation, HO Attempts, HO Reversions, HO Lost, Assignment to
Best/Worst due to BQ Uplink & due to BQ Downlink). These statistics should include the
following counters:
HOVERCNT, HOVERSUC, HORTTOCH, HOASBCL, HOASWCL, HOUPLQA, HODWNQA,
HOATTLSS, HOATTHSS
Intra-Cell Performance (Attempts, Reversion, Lost, Reason Uplink/Downlink). These statistics
should include the following counters:
HOINSUC, HOINBOCH, HOINUQA, HOINDQA, HOINBQA

2.4.1 Net wor k Per f or mance Eval uat i on
Each KPI improvement rate will be calculated as:
% 100 _ _

=
before
after before
KPI
KPI KPI
rate t improvemen KPI

For the handover success rate the improvement will be calculated as:
% 100
1
_ _

=
before
before after
KPI
KPI KPI
rate t improvemen Success

Ultima Fort Required Data Inputs for Ericsson Infrastructure

March 08 Proprietary and Confidential 15 of 19
Schema

Each KPI improvement ratio can be calculated separately over a period of five working days
(during each days network busy hour) before and after the optimization cycle.
Any network performance KPIs that are not related to the BSS subsystem should be excluded
from the calculation.

2.4.2 Radi o Net wor k Per f or mance KPI Cal cul at i on
The following calculations provide KPIs to evaluate radio network performance:

+
=
) B CMSESTABSU CMSESTAB (
) CNDROP (
_ _ Rate Drop SDCCH

+ +
+ +
+ + +
=
SUB THNCASSALL SUB TFNCASSALL
THCASSALL TFCASSALL
) THNDROPSUB TFNDROPSUB THNDROP TFNDROP (
_ _ Rate Drop TCH

+ + +
+
=
) THNDROPSUB TFNDROPSUB THNDROP TFNDROP (
360 / ) THTRALACC TFTRALACC (
_ _ _ Drop to Erlang TCH

=
=
=
7
0
7
5
_
_
_ _ _
x
x
x
x
DL RxQual
DL RxQual
DL Quality Bad TCH

=
=
=
7
0
7
5
_
_
_ _ _
x
x
x
x
UL RxQual
UL RxQual
UL Quality Bad TCH

=
) HOVERCNT (
) HOVERSUC (
_ _ _ Rate Success HO Outgoing

Note:
Bad_Quality statistics are retrieved directly from MRR data.

2.4.3 Addi t i onal KPI s f or Net wor k Per f or mance Eval uat i on
The following calculations provide additional KPIs to evaluate network performance:
Ultima Fort Required Data Inputs for Ericsson Infrastructure

March 08 Proprietary and Confidential 16 of 19
Schema

+
+
=
) CCALLSSUB CCALLS (
) B CMSESTABSU CMSESTAB (
_ _ Success Assignment SDCCH

=
) CCALLS (
) CCONGS (
_ Congestion SDCCH

+ +
+ +
=
) TASSALL (
SUB THNCASSALL SUB TFNCASSALL
THCASSALL TFCASSALL
_ _ Success Assign TCH

+
+ + +
=
) TASSALL (
SUB THNRELCONG SUB TFNRELCONG
THNRELCONG TFNRELCONG CNRELCONG
_ Congestion TCH

3600
) CTRALSUB CTRALACC (
_

+
= Traffic SDCCH
360
) THTRALACC TFTRALACC (
_

+
= Traffic TCH

360
) TFTRALACC (
_ _

= FR Traffic TCH

360
) THTRALACC (
_ _

= HR Traffic TCH

=
) HOVERCNT (
) HODWNQA (
_ _ DL BQ HO

=
) HOVERCNT (
) HOUPLQA (
_ _ UL BQ HO


Ultima Fort Required Data Inputs for Ericsson Infrastructure
March 08 Proprietary and Confidential 17 of 19
Schema

3 Data Col l ect i on Checkl i st
Source Comments Check
Network Data
BSS Network
Configuration

Sector Coordinates File
Traffic File
Mobile Measurements Recordings
Day 1 Day 2 Day 3 Day 4 Day 5
BAR Files
MRR Files
RIR Files
BSS Network
Configuration

Network Performance Statistics
SDCCH Assignments Immediate assignments attempts
Immediate assignments failures

SDCCH Traffic SDCCH traffic per cell
SDCCH congestion

SDCCH Performance SDCCH drop
SDCCH drop reason

TCH Assignments TCH assignment attempts
TCH assignment failures

TCH Traffic Traffic per cell
Traffic FR/HR

TCH Performance Drops
Drops per reason

Handover (HO)
Performance per Cell
Relation
HO attempts
HO success
HO reversion
HO drop

Intra-Cell Handover
Performance
HO reasons
HO attempts
HO success


Ultima Fort Required Data Inputs for Ericsson Infrastructure
March 08 Proprietary and Confidential 18 of 19
Schema

4 Appendi x: Tr oubl eshoot i ng
BARFIL and MRRFIL files are transferred from the BSC to the OSS, once the recording has
finished.
4.1.1 The r emoveFi l e Par amet er f or BARFIL and MRR Fi l e Del et i on
To check the setting of the removeFile parameter:
1. Connect to the OSS via an external application, such as Citrix ICA Client.
2. Check the file removing option in OSS, which automatically deletes MS files (perhaps to
avoid hard disk space problems). The possible values for this parameter are:

removeFile Value Result
0
MS files will not be
removed
1
MS files will be
removed


Parameters in OSS are stored in Parameter Database (PDB) maps. The removeFile parameter
belongs to the BRF map.
To determine the value of OSSs parameters, use the cap_pdb_get_para command:
cap_pdb_get_para n brf removeFile
The Ericsson Alex Library has additional details.
1. Change the value of the file removing option from 1 to 0, using the cap_pdb_mu
command (with the correct user privileges). (If the file removing option is set to 1, files
will be deleted.) If the BRF map is edited with an editor such as VI, it may lock the
database, and the cap_pdb_mu command may not work with BRF. A user with Super
User access (and perhaps additional knowledge) may be able to remedy this situation.
2. Activate the NCS recording using the RNO.
3. Look for BARFIL and MRRFIL files after completing the collection process, since these
files must be located in their corresponding directories.
4. Return the file removing option to its original value (1) after completing the MS
collection. If this parameter is not changed back to the original value, hard disk space
and collateral problems may arise.

Ultima Fort Required Data Inputs for Ericsson Infrastructure
March 08 Proprietary and Confidential 19 of 19
Schema

4.1.2 Addi t i onal Er i csson Inf or mat i on
(This material originally appears in official documentation, entitled Operations Support
System ( Oss) Rc 1.1, Cp4).
Files retrieved from APG40 are stored in the <dbPath>/tmpFileStore/<bsc> directory.
File Description
<dbPath> The path is stated by
the dbPath
parameter in BRF
map.
<bsc> The BSC.

The removeFile parameter in the BRF map can be set up to delete files automatically, as
explained in the previous section.
4.1.3 Par amet er Dat abase (PDB) Maps
Each application has its own parameter database map, with parameters relating to the current
installation.
When the appropriate command is entered in the command shell window (man -s7 <map
name>), additional map information is displayed on the main page.
Application Map Name
BRF Brf
FAS Fas
FOX Fox
NCS Ncs
NOX Nox
TET Tet
MRR Mrr

Use cap_pdb_mu to edit the map.
Note:
To edit system parameters, select RNO System Parameters from the Options menu in the
RNO main window.