Exert user guide

30
Ericssonwide Internal USER GUIDE 1 (30) Prepared (also subject responsible if other) No. ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference 2004-11-03 EXERT Limited Ericsson Internal User Guide Note: Due to continuing work within the development organization, changes may be implemented without prior notice.

description

good doc

Transcript of Exert user guide

Page 1: Exert user guide

Ericssonwide Internal

USER GUIDE 1 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

EXERT Limited Ericsson Internal

User Guide

Note: Due to continuing work within the development organization, changes

may be implemented without prior notice.

Page 2: Exert user guide

Ericssonwide Internal

USER GUIDE 2 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

TABLE OF CONTENTS

1 INTRODUCTION .............................................................................................................................................3

2 REVISION HISTORY......................................................................................................................................3

3 GETTING HELP ..............................................................................................................................................3

4 INSTALLATION ..............................................................................................................................................3

5 USER GUIDE ..................................................................................................................................................12 5.1 WORKFLOW ...............................................................................................................................................12 5.2 EXERT MENU...........................................................................................................................................12

5.2.1 AXE Data Handling Menu.................................................................................................................13 5.2.1.1 Create Command Files ..................................................................................................................13 5.2.1.2 Process Exchange Printouts...........................................................................................................13

5.2.1.2.1 AXE Printouts .........................................................................................................................13 5.2.1.2.2 Exchange ID............................................................................................................................13

5.2.2 Tools Menu .......................................................................................................................................14 5.2.2.1 Options ..........................................................................................................................................15

6 TOOL FEATURES .........................................................................................................................................17 6.1 GENERAL FEATURES..................................................................................................................................17 6.2 CELL DESIGN DATA CONSISTENCY CHECKS.............................................................................................19 6.3 MANAGED OBJECT DATA CONSISTENCY CHECKS ....................................................................................23 6.4 INTER-EXCHANGE DATA CONSISTENCY CHECKS .....................................................................................23

7 SUMMARY OF OUTPUT FILES .................................................................................................................25

8 DESTINATION PAGES OF PRINTOUTS..................................................................................................28 8.1 BSC AND CELL PRINTOUTS.......................................................................................................................28 8.2 BSC MANAGED OBJECT PRINTOUTS.........................................................................................................29 8.3 MSC PRINTOUTS .......................................................................................................................................30

Page 3: Exert user guide

Ericssonwide Internal

USER GUIDE 3 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

1 INTRODUCTION

Exert has been updated to cater requirements for GSM Systems R9 and R10. In this new revision, Exert comes with a configuration file. It has been re-designed and re-developed to be more flexible and can be customized to support new printouts with the same format as those currently supported without changing the core application.

Exert is intended to facilitate off-site data processing and analysis. It should not be relied on as substitute for the more powerful OSS tools for data consistency checking.

2 REVISION HISTORY RELEASE REVISED BY REMARKS EXERT 4.x Joel Philamer Quinez Majority of AXE printouts (up to

BSS R9) are supported.

EXERT 5.x Joel Philamer Quinez Majority of AXE printouts (up to BSS R10) are supported.

Table 1. Revision Information

3 GETTING HELP

Support will be provided on best effort basis by the developer. To get support please mailto: [email protected]. All requests will be entertained as much as possible.

4 INSTALLATION

With the installation archive, uncompress the archive in your My Documents folder. The unzipped archive should contain the mandatory files and may contain the optional files:

File Name Category Remarks

SETUP.EXE Mandatory Executable file to

run the installation.

SETUP.LST Mandatory Contains the installation configuration.

EXERT.CAB Mandatory Contains the files to be installed.

PLEASE.READ.ME.FIRST.TXT Optional Contains important

Page 4: Exert user guide

Ericssonwide Internal

USER GUIDE 4 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

instructions, information and may also contain release notes.

EXERT USER GUIDE.DOC/PDF

Optional This document.

Table 2: Installation Files

Note: The archive may be unzipped in other folder than My

Documents. However, please refrain from having the installation files located deeply in your directory structure.

Before installation, close currently working applications especially Microsoft Excel.

If you have an older version of Exert 5.0.x, please uninstall the older version before installing the newer version.

Note: If you have a previously registered EXERT.LOCK file, you may

not need to register your new copy unless otherwise requested or specified in the release note. Before uninstalling the previous version, copy your EXERT.LOCK file into your My Documents folder to be available for later use or after the installation of the newer version.

Page 5: Exert user guide

Ericssonwide Internal

USER GUIDE 5 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

To uninstall the previous version of Exert 5.0.x, please follow these steps:

Click Start menu | Settings | Control Panel (Figure1) Select Add/Remove Programs (Figure2) Choose Exert and uninstall

Figure 1: Accessing the Control Panel

Page 6: Exert user guide

Ericssonwide Internal

USER GUIDE 6 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

Figure 2: Add/Remove Programs

Before installation, close currently working applications especially Microsoft Excel.

With the available files in Table1, perform the following steps: Double-click setup.exe to run the installation program Follow the instructions of the installation program. For

convenience, follow the default installation directory.

Note: For you to be able to install Exert properly, you need to have administrative rights in the target PC.

Page 7: Exert user guide

Ericssonwide Internal

USER GUIDE 7 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

Optionally after installation, you may want to check the installation directory if you have the following files:

File Name Category Remarks

EXERT.DLL Mandatory Server application.

The main functions and routines reside in this file.

EXERT.XLS Mandatory Client application. This file provides user interface.

EXERT PROPERTY FILE.XLS Mandatory Contains configuration data in handling different types of processing.

GSM BTS FAULT CODES.XLS

Optional Contains the fault classes and fault codes and corresponding interpretations for RXELP printouts.

EXERT USER GUIDE.DOC/PDF

Optional This document.

Table 2: Installed Files

Note: For the tool to work properly, do not rename the files and the

worksheets of the Excel files.

Page 8: Exert user guide

Ericssonwide Internal

USER GUIDE 8 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

You may now proceed to check if the installation was successful. For later versions of Microsoft Excel, the default security level is High. There is a need to set the security level to Medium as shown in Figure 3 to be able to run Macros.

Figure 3. Security Dialog for Microsoft Excel

Page 9: Exert user guide

Ericssonwide Internal

USER GUIDE 9 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

To change the security level, select Tools | Macro | Security … as shown in Figure 4.

Figure 4. Accessing the Security Dialog

After setting the security level to Medium, close Microsoft Excel application.

Page 10: Exert user guide

Ericssonwide Internal

USER GUIDE 10 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

Launch Exert – Start | Program Files | Exert and select EXERT.XLS.

When Microsoft Excel opens, it should prompt you to disable or enable macros. Select Enable Macros.

Figure 5. Disable/Enable Macros Dialog

When Microsoft Excel opens, it should prompt you to disable or enable macros. Select Enable Macros. The client application will create the EXERT menu as shown in Figure 6.

Figure 6. Exert Menu

Page 11: Exert user guide

Ericssonwide Internal

USER GUIDE 11 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

If your copy is not yet registered, you are requested to register your copy. Create EXERT.LOCK and send mail to the person responsible below. Click the ‘To: ‘ list to launch your e-mail application (Figure 7).

If available, you may re-use your currently registered EXERT.LOCK provided it is not expired and it is compatible with the newly installed version.

Figure 7. Registration Dialog

Note: The EXERT.LOCK resides in the installation directory. Providing the license file is subject to evaluation.

Page 12: Exert user guide

Ericssonwide Internal

USER GUIDE 12 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

5 USER GUIDE

5.1 Workflow

Analyses, Verifications

Change implementation

work orders

EXERT

AXE Printouts

AXE NE

Figure 8. Basic Workflow

Figure 8 presents the basic workflow where Exert may be used. The process may be started by creating a scheduled AXE printout generation daily, weekly or on-demand. This can be performed using Activity Manager of Command Handling in OSS. However, to set-up the Activity Manager is not within the scope of this document. Note: Daily generation of AXE printouts can be performed automatically with

the use of Activity Manager of Command Handling (CHA) in OSS. The tool has a built-in function to generate the command files required to collect printouts.

To generate the printouts, command files are required when defining an activity in the Activity Manager. The command files can be generated from Exert and shall be explained in detail later how to generate these command files.

The daily printouts can then be collected when needed. This need may depend on the discipline involved and the type of requirement (e.g. radio network optimization, transmission, network data audit, etc.).

5.2 EXERT Menu

The EXERT main menu can be found as shown earlier in Figure 6. It has the following sub menu:

AXE Data Handling

Page 13: Exert user guide

Ericssonwide Internal

USER GUIDE 13 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

Tools …

5.2.1 AXE Data Handling Menu

The AXE Data Handling Menu is a group of functions related to AXE data processing.

5.2.1.1 Create Command Files

This is used to generate the command files to collect (MSC and BSC) exchange level and cell level parameters and BSC managed object parameters. The generated command files may include the following:

COMMAND FILES REMARKS

CDD.TXT Contains the print commands to collect exchange level and cell level parameters in the BSC.

MO.TXT Contains the print commands to collect managed object parameters in the BSC.

MSC.TXT Contains the print commands to collect data from the MSC.

MFCHECK.TXT Contains the recommended print command to collect data from BSC to check consistency of BCCH allocation (BA) list.

Table 3. Command Files

5.2.1.2 Process Exchange Printouts

This is used to process AXE printout files either taken from AT terminal or OSS terminal. This is only available in registered version of the tool.

5.2.1.2.1 AXE Printouts

Exert qualifies a valid printout when it finds at least one (1) command line, that is, the line is terminated by a semi colon like the following example: RLDEP:CELL=ALL;. After passing this check it then converts the input file to the desired format for data extraction. Note: Without the command lines included in the printout, the data will not

be processed.

5.2.1.2.2 Exchange ID

The exchange identity is derived based on the following order of priority from the printout file as follows:

Page 14: Exert user guide

Ericssonwide Internal

USER GUIDE 14 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

*** Connected to EXCHID ***.

ES Name: EXCHID

** COMMAND FILE: /home/npi_1/CDD.TXT to ES: EXCHID

CONNECTION ESTABLISHED WITH E.S.: EXCHID

From the IOEXP printout

From the filename Note: The exchange ID is only checked once for each file. Hence, combining

data from different exchanges is not recommended when Exert is used to process the data.

5.2.2 Tools Menu

Tools … has the following sub menu:

About …

Options …

Page 15: Exert user guide

Ericssonwide Internal

USER GUIDE 15 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

5.2.2.1 Options

This function emulates the options dialog as shown in Figure 9. You may select or unselect your desired settings based on your processing requirement. Your setting will be saved in UserOptions.txt file located in the installation directory when you click Save or when you Close the dialog.

Figure 9. Options Dialog

Page 16: Exert user guide
Page 17: Exert user guide

Ericssonwide Internal

USER GUIDE 17 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

6 TOOL FEATURES

6.1 General Features

The following are the general tool features. These are created in the destination workbooks.

Item Supporting Printouts Description Overview of cell parameter settings Available cell level printouts Presents a summary of settings used in each cell or subcell.

This is created in the destination workbook.

Summary of active or inactive features in the BSC

DBTSP:TAB=AXEPARS; RAEPP:ID=ALL; And other available BSC and cell parameter printouts

Presents radio network feature summary. This is created in the destination workbook.

ARFCN usage distribution per channel group

RLDEP:CELL=ALL; RLCFP:CELL=ALL;

Displays in a chart the ARFCN usage distribution for each channel type and channel group. This is created in the destination workbook.

Overview of managed object data Available managed object data print outs

Create summary of settings used in each managed object, dip. This is created in the destination workbook.

Configuration summary of managed objects RXMOP:MOTY=RXOTG; RXMOP:MOTY=RXOTRX; (TRU DEF) RXMOP:MOTY=RXOTRX; (TRU OPER) RXMFP:MOTY=RXOCF; (CDU, PSU, DXU)

Displays equipment configuration summary per RSITE. This is created in the destination workbook.

Page 18: Exert user guide

Ericssonwide Internal

USER GUIDE 18 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03 Interpretation of RXELP fault codes RXELP:MOTY=RXOCF;

RXELP:MOTY=RXOTF; RXELP:MOTY=RXOCON; RXELP:MOTY=RX

Requires GSM BTS Fault Code reference. The interpreted codes are written in the BTS Error page in the destination workbook.

Abis timeslot allocation table in the BSC RXMOP:MOTY=RXOTG; RXAPP:MOTY=RXOTG; NTCOP:SNT=ALL;

Displays the mapping of devices on timeslot level on the A-bis interface. This is created in SNT Data page of the destination workbook.

Table 4: General Tool Features

Page 19: Exert user guide

Ericssonwide Internal

USER GUIDE 19 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

6.2 Cell Design Data Consistency Checks

Cell design data consistency checks are done per BSC. The result of each check is stored in a process log located in the same target directory.

Item Supporting Printouts Description HALTED CELLS CHECK RLSTP:CELL=ALL; Checks for halted cells.

SUBCELLS UL/OL OF SAME TSC CHECK

RLDTP:CELL=ALL; Checks for same TSC in UL/OL.

BSPWRB <> BSPWRT CHECK RLCPP:CELL=ALL; Check for unequal power setting in BCCH and non-BCCH carriers.

BSPWR <> BSTXPWR CHECK RLLOC:CELL=ALL; Checks for unequal locating settings for BCCH and non-BCCH carriers.

BSPWRB-BSPWRT <> BSPWR-BSTXPWR CHECK

RLCPP:CELL=ALL; RLLOC:CELL=ALL;

Checks for unequal difference of BCCH and non-BCCH carriers in power configuration and locating data.

LINK IMBALANCE > x dB RLLOP:CELL=ALL; Checks for the absolute difference of uplink and downlink sufficient receive levels and minimum receive thresholds in locating.

INTERNAL RELATION SINGLE DIRECTION CHECK

RLNRP:CELL=ALL; Checks for non-mutual internal relations.

CELLS WITH NO NEIGHBOR CHECK

RLNRP:CELL=ALL; Checks for cells with no defined neighbor.

CELL NOT DEFINED AS A CELLR CHECK RLNRP:CELL=ALL; RLDEP:CELL=ALL; RLDEP:CELL=ALL,EXT;

Checks for cells not used as a neighbor. An external cell not used as a neighbor is a candidate for deletion and usually encountered after migration of sites from one BSC to another.

Page 20: Exert user guide

Ericssonwide Internal

USER GUIDE 20 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03 MISSING NCELL NCC IN SERVING CELL NCCPERM CHECK

RLSSP:CELL=ALL; RLNRP:CELL=ALL; RLDEP:CELL=ALL; RLDEP:CELL=ALL,EXT;

Checks for missing NCC(part of BSIC) by comparing the NCC of the neighbor cells with the serving cell NCCPERM. Data transcript is included to fix the missing NCC in NCCPERM.

CELL AND CELLR OF SAME BCCHNO CHECK

RLDEP:CELL=ALL; RLDEP:CELL=ALL,EXT; RLNRP:CELL=ALL; RLMFP:CELL=ALL;

Checks for co-BCCH serving cell and neighbor cell.

CELLR OF SAME BCCHNO AND OF SAME BSIC CHECK

RLDEP:CELL=ALL; RLDEP:CELL=ALL,EXT; RLNRP:CELL=ALL; RLMFP:CELL=ALL;

Checks for co-BCCH and co-BSIC neighbors of a serving cell.

EXTRA MBCCHNO IN IDLE BA LIST CHECK

RLDEP:CELL=ALL; RLDEP:CELL=ALL,EXT; RLNRP:CELL=ALL; RLMFP:CELL=ALL;

Checks for extra MBCCHNO defined in the cell. The extra MBCCHNO does not belong to any neighbor of the serving cell. The extra MBCCHNO is a candidate for deletion. Data transcript is included to remove the extra MBCCHNO in idle BA list.

EXTRA MBCCHNO IN ACTIVE BA LIST CHECK

RLDEP:CELL=ALL; RLDEP:CELL=ALL,EXT; RLNRP:CELL=ALL; RLMFP:CELL=ALL;

Checks for extra MBCCHNO defined in the cell. The extra MBCCHNO does not belong to any neighbor of the serving cell. The extra MBCCHNO is candidate for deletion. Data transcript is included to remove the extra MBCCHNO in active BA list. In this version of Exert, only non-BCCH ARFCN of internal and external cells are considered extra in the idle BA-list.

Page 21: Exert user guide

Ericssonwide Internal

USER GUIDE 21 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03 MISSING MBCCHNO IN IDLE BA LIST CHECK

RLDEP:CELL=ALL; RLDEP:CELL=ALL,EXT; RLNRP:CELL=ALL; RLMFP:CELL=ALL;

Checks MBCCHNO that should be included in the cell. The missing MBCCHNO belongs to a neighbor of the serving cell and it is candidate for inclusion. Data transcript is included to define missing MBCCHNO in idle BA list.

MISSING MBCCHNO IN ACTIVE BA LIST CHECK

RLDEP:CELL=ALL; RLDEP:CELL=ALL,EXT; RLNRP:CELL=ALL; RLMFP:CELL=ALL;

Checks MBCCHNO that should be included in the cell. The missing MBCCHNO belongs to a neighbor of the serving cell and it is candidate for inclusion. Data transcript is included to define missing MBCCHNO in active BA list.

CELL RESOURCE SEIZURE SUPERVISION CHECK

RLVLP:CELL=ALL; Checks for cells not included in the cell resource seizure supervision. Checks also if the BSC level supervision is active. Data transcript is included to include missing cells in the supervision and to activate the BSC level supervision (if not active).

CELL RESOURCE AVAILABILITY SUPERVISION CHECK

RLSLP:CELL=ALL; Checks for cells with inactive supervision on unavailable resources. Data transcript is included to activate the cell supervision and to adjust the LVA (limit value adjust) parameter for downgrades and upgrades.

BSC LOAD MISMATCH CHECK PLLDP; Checks for originating calls not equal to fetched originating calls or offered incoming calls not equal to fetched incoming calls. BSC load mismatch is for further investigation.

Page 22: Exert user guide

Ericssonwide Internal

USER GUIDE 22 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03 BCCHNO(BSIC) DUPLICATE-PAIR CHECK (NON-NEIGHBORS INCLUDED)

RLDEP:CELL=ALL; RLDEP:CELL=ALL,EXT;

Checks for duplicate BCCH(BSIC) pairs. These are candidates for further investigation.

Table 5: Cell Design Data Consistency Check

Page 23: Exert user guide

Ericssonwide Internal

USER GUIDE 23 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

6.3 Managed Object Data Consistency Checks

Managed object data checks are done per BSC. The result of each check is stored in a process log that may be located in the same directory as the source file.

Item Supporting Printouts Description CELL AND MO TRX LOGICAL LINK CHECK

RXTCP:MOTY=RXOTG; RXMOP:MOTY=RXOTRX; RXMSP:MOTY=RXOTRX; (Optional)

Checks for TRX and cells connected as CELL=ALL.

CELL AND MO TX LOGICAL LINK CHECK RXTCP:MOTY=RXOTG; RXMOP:MOTY=RXOTX; RXMSP:MOTY=RXOTX (Optional)

Checks for Tx and cells connected as CELL=ALL.

Table 5. Managed Object Data Consistency Checks

6.4 Inter-Exchange Data Consistency Checks

Inter-exchange BSC check, except for the first three items, is done for multiple exchanges. The result of each check is stored in a process log that may be located in the same directory as the input files.

Item Supporting Printouts Description INTERNAL CELLS COMMON IN BSCs CHECK

RLSTP:CELL=ALL; Checks for common internal cells defined in two or more BSCs. The neighbor relations of these cells are candidates for further investigation.

Page 24: Exert user guide

Ericssonwide Internal

USER GUIDE 24 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03 COMMON LAI USED IN BSCs CHECK RLDEP:CELL=ALL; Checks for common LAI used in two or more BSCs. BSCs of

common LAI are for further investigation e.g. paging performance, MSC homing, etc. BSCs using common LAI and served by different MSCs should be strictly avoided.

INNER CELLS DATA CHECK MGCEP:CELL=ALL; RLDEC:CELL=ALL;

Checks for CGI consistency of INTERNAL and INNER cells.

OUTER CELLS DATA CHECK MGOCP:CELL=ALL;MGCEP:CELL=ALL; RLDEC:CELL=ALL;

Checks for CGI or AREAID consistency of OUTER, INTERNAL and INNER cells.

INNER CELLS MISSING CHECK RLDEC:CELL=ALL; MGCEP:CELL=ALL;

Checks for missing INNER cell. Data transcript is included to define missing inner cell in MSC.

EXTERNAL CELL DATA CHECK RLDEP:CELL=ALL; RLCPP:CELL=ALL; RLLOP:CELL=ALL; RLLHP:CELL=ALL; RLDEP:CELL=ALL,EXT; RLCPP:CELL=ALL,EXT; RLLOP:CELL=ALL,EXT; RLLHP:CELL=ALL,EXT;

Checks for inconsistent INTERNAL cell and EXTERNAL cell data. Includes data transcript to fix data inconsistency.

Page 25: Exert user guide

Ericssonwide Internal

USER GUIDE 25 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03 MISSING EXTERNAL RELATION, MISSING OUTER CELL CHECKS

RLDEP:CELL=ALL; RLCPP:CELL=ALL; RLLOP:CELL=ALL; RLLHP:CELL=ALL; RLDEP:CELL=ALL,EXT; RLCPP:CELL=ALL,EXT; RLLOP:CELL=ALL,EXT; RLLHP:CELL=ALL,EXT; RLNRP:CELL=ALL; MGOCP:CELL=ALL; MGCEP:CELL=ALL;

Checks for missing OUTER cell in MSC. Data transcript is included to define the missing outer cell in MSC. Checks for missing relation counterpart in the other BSC. Data transcript is included to define the external cell (if needed) and to create the external relation. Checks for inconsistent relation data e.g. hysteresis and offset. Data transcript is not included for this type of inconsistency.

Table 6. Inter-exchange Data Consistency Checks

7 SUMMARY OF OUTPUT FILES

The following table lists the probable output files. yyyymmdd hhmmss indicates the date and time the file was created. The transcript files are named such that they can be loaded directly into OSS. Warning! Exercise caution when using the data transcript files. The tool is a machine but the author is human.

Output File Remarks MSC yyyymmdd hhmmss.xls This is an Excel file that contains processed MSC data.

BSC CDD yyyymmdd hhmmss.xls This is an Excel file that contains processed cell design data.

BSC MO yyyymmdd hhmmss.xls This is an Excel file that contains processed BSC managed object data.

AXE yyyymmdd hhmmss.LOG This file contains the result of all consistency checks.

Page 26: Exert user guide

Ericssonwide Internal

USER GUIDE 26 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03 BSC_yyyymmdd_SUPERVISION_CHANNEL_SEIZURE_ADJUST.TXT BSC_yyyymmdd_SUPERVISION_CHANNEL_AVAILABILITY_ADJUST.TXT

This is a transcript file that may facilitate you adjust LVA = NCH parameters (RLSLP), activate non-activated resource availability supervision on cell level; include cells not included in resource supervision (RLVLP) or activate non-activated BSC-level cell resource supervision.

BSC_yyyymmdd_MBCCHNO_ACTIVELIST_EXTRA.TXT BSC_yyyymmdd_MBCCHNO_ACTIVELIST_MISSING.TXT BSC_yyyymmdd_MBCCHNO_IDLELIST_EXTRA.TXT BSC_yyyymmdd_MBCCHNO_IDLELIST_MISSING.TXT

This are transcript files that may facilitate you in defining missing MBCCHNO in each cell for IDLE and ACTIVE BA list. It may also suggest to remove extra MBCCHNO for each cell. The checking of MBCCHNO is based on the BCCHNO of each neighbor of a cell. In this version of EXERT, only non-BCCH ARFCN of internal and external cells are considered extra in the idle BA-list.

BSC_yyyymmdd_NCCPERM_ADJUST.TXT This is a transcript file that may facilitate you include a missing NCC of a neighbor cell in the NCCPERM of a serving cell.

MSC_yyyymmdd_DEFINE_INNER_CELL.TXT This is a transcript file that may facilitate you to define a missing inner cell as detected during inter-exchange data consistency check.

MSC_yyyymmdd_DEFINE_OUTER_CELL.TXT This is a transcript file that may facilitate you to define a missing outer cell as detected during inter-exchange data consistency check. This may indicate a missing external cell relation.

BSC_yyyymmdd_EXTERNAL_DATA_ADJUST.TXT This is a transcript file that may help you correct inconsistent internal and external data of a cell.

Page 27: Exert user guide

Ericssonwide Internal

USER GUIDE 27 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

BSC_yyyymmdd_DEFINE_EXTERNAL_CELL.TXT This is a transcript file and closely associated with file

BSC_yyyymmdd_RELATION_DATA_ADJUST.TXT. It suggests to define an external cell if a missing external cell relation is detected.

BSC_yyyymmdd_RELATION_DATA_ADJUST.TXT This is a transcript file and is closely associated with BSC_yyyymmdd_DEFINE_EXTERNAL_CELL.TXT. You may use this file to define a missing external cell relation that does not exist in the opposite direction.

Table 7. Output Files

Page 28: Exert user guide

Ericssonwide Internal

USER GUIDE 28 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

8 DESTINATION PAGES OF PRINTOUTS

8.1 BSC and Cell Printouts Destination Printouts Remarks ADMIN IOEXP;

CACLP;

SAE1 SAAEP:SAE=ALL; SAE2 SAACP:SAE=ALL; AXEPARS DBTSP:TAB=AXEPARS; BSC RLTYP;

RLLSP; RLOMP; RLCAP; RLCDP:CELL=ALL;

BSCPROP RAEPP:ID=ALL; LOAD PLLDP; STATUS RLSTP:CELL=ALL; INTERNAL RLDEP:CELL=ALL; POWER RLCPP:CELL=ALL; FREQCONTROLCH RLCHP:CELL=ALL;

RLGAP:CELL=ALL; RLCFP:CELL=ALL;

RELATION RLNRP:CELL=ALL; RLGNP:CELL=ALL;

RELATION2 RLNRP:CELL=ALL,UTRAN; MF1 RLMFP:CELL=ALL; MF2 RLUMP:CELL=ALL; LOCATING0 RLLBP; LOCATING1 RLLOP:CELL=ALL;

RLLUP:CELL=ALL; RLDTP:CELL=ALL;

LOCATING2 RLLDP:CELL=ALL; RLLPP:CELL=ALL; RLLFP:CELL=ALL;

CHADMIN1 RLHPP:CELL=ALL; RLCDP:CELL=ALL; RLACP:CELL=ALL; RLDRP:CELL=ALL; RLCRP:CELL=ALL;

CHADMIN2 RLGRP:CELL=ALL; CHADMIN3 RLGSP:CELL=ALL;

RLGQP:CELL=ALL;

CHADMIN4 RLDHP:CELL=ALL; RLDMP:CELL=ALL;

CHADMIN5 RLBDP:CELL=ALL; IHO RLIHP:CELL=ALL; HCS0 RLHBP; HCS1 RLLHP:CELL=ALL;

RLPSP:CELL=ALL;

Page 29: Exert user guide

Ericssonwide Internal

USER GUIDE 29 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

ICM RLIMP:CELL=ALL; CLS RLLCP:CELL=ALL; SYSINFO1 RLSBP:CELL=ALL;

RLCXP:CELL=ALL; RLPBP:CELL=ALL; RLSSP:CELL=ALL;

SYSINFO2 RLSUP:CELL=ALL; POWERCONTROL1 RLPCP:CELL=ALL;

RLBCP:CELL=ALL;

POWERCONTROL2 RLAPP:CELL=ALL; SUBCELL RLLLP:CELL=ALL;

RLOLP:CELL=ALL;

MSGDIST RLSMP:CELL=ALL; SMSCB1 RLMTP:ID=ALL,CELL=ALL; SMSCB2 RLMBP:ID=ALL; CODEC RLADP:SET=ALL; EXTERNAL RLDEP:CELL=ALL,EXT;

RLLOP:CELL=ALL,EXT; RLCPP:CELL=ALL,EXT; RLLHP:CELL=ALL,EXT; RLPSP:CELL=ALL,EXT;

Gb RRGBP; SUPERVISION1 RLVLP:CELL=ALL; SUPERVISION2 RLSLP:CELL=ALL; SUPERVISION3 RLVAP;

Table 8. Destination of BSC and Cell Parameter Printouts

8.2 BSC Managed Object Printouts Destination Printouts Remarks TGCELL RXTCP:MOTY=RXOTG; TG RXMOP:MOTY=RXOTG; CF RXMOP:MOTY=RXOCF;

RXMSP:MOTY=RXOCF; RXMDP:MOTY=RXOCF;

TF RXMOP:MOTY=RXOTF; RXMSP:MOTY=RXOTF; RXMDP:MOTY=RXOTF;

TRX RXMOP:MOTY=RXOTRX; RXMSP:MOTY=RXOTRX; RXMDP:MOTY=RXOTRX;

TX RXMOP:MOTY=RXOTX; RXMSP:MOTY=RXOTX;

RX RXMOP:MOTY=RXORX; RXMSP:MOTY=RXORX;

CFDATA RXMFP:MOTY=RXOCF; TRXDATA RXMFP:MOTY=RXOTRX; FAULTS RXMFP:MOTY=RXOCF;

RXMFP:MOTY=RXOTRX; RXMFP:MOTY=RXOTX,FAULTY;

Page 30: Exert user guide

Ericssonwide Internal

USER GUIDE 30 (30)Prepared (also subject responsible if other) No.

ENP/LD Joel Philamer V. Quinez Approved Checked Date Rev Reference

2004-11-03

RXMFP:MOTY=RXORX,FAULTY; RXMFP:MOTY=RXOTS,FAULTY;

TRA RRTPP:TRAPOOL=ALL; RRMSP:TRAPOOL=ALL;

ALARMSITUATIONS RXASP:MOTY=RXOTG; Abis RXAPP:MOTY=RXOTG; SNT1 SNT2 SNT3

NTCOP:SNT=ALL;

ALARMLIST ALLIP; BTSERROR RXELP:MOTY=RXOCF;

RXELP:MOTY=RXOTF; RXELP:MOTY=RXOCON; RXELP:MOTY=RXOTRX; RXELP:MOTY=RXOTX; RXELP:MOTY=RXORX; RXELP:MOTY=RXOTS;

EM EXEMP:RP=ALL,EM=ALL; RP EXRPP:RP=ALL; RPSW EXRUP:RP=ALL;

Table 9. Destination of BSC Managed Object Printouts

8.3 MSC Printouts Destination Printouts RemarksMSCPROP MGEPP:ID=ALL; MSC MGIDP;

MGADP; MGCAP;

N-MSCs MGNMP:MSC=ALL; C-VLRs MGCVP:VLR=ALL; BSCs MGBSP:BSC=ALL; INNER MGCEP:CELL=ALL; OUTER MGOCP:CELL=ALL; LOCNO MGLNP:LOCNO=ALL,ATYPE=ALL,CTYPE=ALL; MSSURVEY MGSVP; AUTHFAILED MGARP:NLOG=ALL; EMLPP MGETP; TSC1 MGTCP:TSC=ALL; ALARMLIST ALLIP;

Table 10. Destination of MSC Printouts