Alcatel_A956-RNO Acceptance Test

7/28/2019 Alcatel_A956-RNO Acceptance Test

1/40

Alcatel BSS

B7.2 A956-RNO Acceptance Tests

Acceptance Manual

3BK 17416 4035 RJZZA Ed. 02


2/40

Status RELEASED

Short title Acceptance test manual

All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel.

BLANK PAGE BREAK

2 / 40 3BK 17416 4035 RJZZA Ed.02


3/40

Contents

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1 Principles of the Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2 Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.3 Procedure Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.3.1 Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3.2 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3.3 Sequence of Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3.4 Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.3.5 Impact on Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.4 Supplies, Tools and Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.5 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2 PI 01: Check the Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.1 Check Processor(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2 Check Physical Memory Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3 Check Disks Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.4 Check RAID5 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 PI 02: Check Installed Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.1 Check RNO Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2 Check Oracle Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.3 Check Netscape Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.4 Check Acrobat Reader Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.5 Check Microsoft Excel Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.6 Check ARCserve Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.7 Check ARCserve Disaster Recovery Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4 PI 03: Check the Import Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.1 Basic Information about the Import Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224.2 Summary of Actions for Import Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4.2.1 Edit the Crontab File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234.2.2 Check the PRC File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.2.3 Modify the Import Schedule Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

5 PI 04: Create Tuning Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

5.1 Basic Information about the Tuning Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.2 Create a Tuning Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

6 PI 05: Check the Export Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

6.1 Basic Information about the Export Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326.2 Check the Export Process for OMC-R Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

7 PI 06: Creating an Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 PI 07: Check RNO-NPA Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

9 PI 08: Check the Import from RNP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

3BK 17416 4035 RJZZA Ed. 02 3 / 40


4/40

Tables

Tables

Table 1: List of procedures for A956-RNO V3 acceptance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4 / 40 3BK 17416 4035 RJZZA Ed.02


5/40

Preface

Preface

Purpose This document describes the acceptance procedure for the RNO V3 Softwarein order to check that the hardware and software configuration is well done forthe RNO machines and the links with OMC-R host(s) and NPA are reliable.

Audience This document is intended for:

Field service technicians

Project managers

Site administrators

System support engineers (specialists)

Occasional users (e.g. subcontractors).

Assumed Knowledge A good knowledge of the following topics is mandatory:

Windows 2000 Server / Workstation

OMC-R administration

UNIX shell

Practicals in RNO Man-Machine Interface.

3BK 17416 4035 RJZZA Ed. 02 5 / 40


6/40

Preface

6 / 40 3BK 17416 4035 RJZZA Ed.02


7/40

1 General Information


This chapter provides general information about the principle of the operationsand requirements for the procedure.

3BK 17416 4035 RJZZA Ed. 02 7 / 40


8/40


1.1 Principles of the Operation

This document describes the A956 RNO V3.1 acceptance procedure.

The acceptance procedure covers the tests to be performed on the RNO

machine after the installation. The hardware configuration and the software

configuration are both tested.

Performing this procedure ensure that the RNO machine is correctly

installed, configured and running.

Also, the import-export mechanism between RNO and OMC-R host(s), the

interaction RNO - NPA and the import from RNP to RNO are tested.

The tests apply to following cases:

Install of RNO V3.1 Client-Server

Install of RNO V3.1 Standalone.

1.2 Scenario

Only one scenario is described.

The scenario A956-RNO V3.1 Acceptance procedure

This method contains procedures concerning the acceptance of a full A956RNO V3.1 installation.

PI 01: Check the hardware configuration

PI 02: Check the installed software

PI 03: Check the import process

PI 04: Create tuning session

PI 05: Check the export process

PI 06: Creating an optimizer

PI 07: Check the RNO-NPA interaction

PI 08: Check the import from RNP

8 / 40 3BK 17416 4035 RJZZA Ed.02


9/40


1.3 Procedure Information

1.3.1 Pre-requisites

Respect the safety rules.

Inform the operator. Ask for an operators representative to be on site

(unless otherwise specifically agreed in writing).

Installation of the RNO V3.1 has been completely performed (Client-Server,

Standalone).

OMC-R is installed and running in software version compliant with RNO V3.

NPA and RNP machines should be available, it should be installed and

running in software version compliant with RNO V3 (NPA B7).

Connection to OMC-R(s) and NPA machine (if the case) is available.

If RNP machine available, at least one project should exist on this machine;the connection with the RNO should also be available.

1.3.2 Restrictions

None.

1.3.3 Sequence of Operations

PI No. Procedure Name Mandatory/Optional

PI 01 Check the Hardware Configuration Mandatory

PI 02 Check the Installed Software Mandatory

PI 03 Check the Import Process Mandatory

PI 04 Create Tuning Session Mandatory

PI 05 Check the Export Process Mandatory

PI 06 Creating an Optimizer Optional

PI 07 Check the RNO-NPA Interaction Optional

PI 08 Check the Import from RNP Optional

Table 1: List of procedures for A956-RNO V3 acceptance

3BK 17416 4035 RJZZA Ed. 02 9 / 40


10/40


1.3.4 Schedule

PI No. PI Titles Total Time

PI 01 Check the Hardware Configuration 15 min. /machine

PI 02 Check the Installed Software 20 min. /machine

PI 03 Check the Import Process 120 min.

PI 04 Create Tuning Session 25 min. /Client or Standalone

PI 05 Check the Export Process 20 min.

PI 06 Creating an Optimizer 10 min.

PI 07 Check RNO-NPA Interaction 10 min.

PI 08 Check the Import from RNP 15 min.

TOTAL 4 hours (*)

(*) The Total Time depends of the network configuration.

1.3.5 Impact on Service

None.

1.4 Supplies, Tools and Documentation

Supplies None.

Tools None.

ApplicableDocumentation

No. Designation Reference

[1] A956 RNO User Guide 3BK 20586 AAAA PCZZA

[2] A956 RNO Administration Guide 3BK 20588 AAAA PCZZA

[3] A956 RNO Engineering Rules V3.1 / B7.2 3BK 11246 0064 PJZZA

[4] CCL A956-RNO Acceptance Tests 3BK 17416 4035 QZZZA

[5] B7.2 TSI (Technical Status Information) 3BK 17416 0003 PCZZA

[6] B7.2 SPS (Site Preparation Sheet) 3BK 17416 4002 RJZZA

10 / 40 3BK 17416 4035 RJZZA Ed.02


11/40


1.5 Conventions

The following conventions are used in the document:

Keyboard keys are indicated in the text as [ XX ]. For example, Press

[ Enter ] means press the [ Enter ] key.

System messages appear in Courier font:system message

Operator input is shown after a double right-oriented arrow, in Courier font.

The UNIX prompt of the user is also displayed. For root user the prompt is

#, for axadmin user axadmin@host$ and for metrica user host:metrica

where host is the hostname of the machine.

For root user the input looks like the following:# operator_input

For axadmin user the input looks like the following:axadmin@host$ operator_input

For metrica user the input looks like the following:host:metrica operator_input

Software buttons on a terminal screen are also indicated in the text as [ XX ].

For example, click on [ OK ] means move the mouse pointer to the [ OK ]

button on the screen and then click the left mouse button.

To describe a menu path chain, the menu entries are chained with a ->.

Example:Tools -> Options -> Printer -> ...

3BK 17416 4035 RJZZA Ed. 02 11 / 40


12/40


12 / 40 3BK 17416 4035 RJZZA Ed.02


13/40

2 PI 01: Check the Hardware Configuration


This chapter describes the operations to be performed to check the hardwareconfiguration on ALL the RNO machines.

3BK 17416 4035 RJZZA Ed. 02 13 / 40


14/40


2.1 Check Processor(s)

For Processor(s) 1. Open a System Informationwindow by following the menu path:

Start -> Programs -> Accessories -> System Tools -> SystemInformation

2. Select the System Summary from the System Information tree (in theleft side).

3. Search in the right side for the number and value of Processor instance, foreach configuration in turn ( RNO Server, RNO Client or RNO Standalone )refer to the applicable document [3] "A956 RNO Engineering Rules V3.1

/ B7.2" .

4. Update the Completion Check List (CCL).

2.2 Check Physical Memory Size

For RAM 1. In System Information window

2. Search the Total Physical Memory line.

3. For each configuration in turn ( RNO Server, RNO Client or RNOStandalone ) refer to the applicable document [3]"A956 RNO EngineeringRules V3.1 / B7.2" .


2.3 Check Disks Partitions

On all the machines, check the disks partitions by following the sequences:

1. Go on the menu path:

Start -> Programs -> Administrative Tools -> Computer Management

2. Expand the Storage from the left window, then select Disk Management.

3. In the right window, check that Disk 0 has the healthy volumes:

For RNO Server C: to be NTFS with 4 GB size

D: to be NTFS with the remaining disk space.

For RNO Standaloneand RNO Client

C: to be NTFS with 2 GB size.

D: to be NTFS with the remaining disk space.

4. Close Computer Management window.5. Update the Completion Check List (CCL).

14 / 40 3BK 17416 4035 RJZZA Ed.02


15/40


2.4 Check RAID5 Configuration

This paragraph is applicable only for RNO Server.

For RAID5 1. To check the RAID5 configuration, follow the menu path:Start -> Programs -> Compaq System Tools -> Compaq ArrayConfiguration Utility

2. In Compaq Array Configuration Utility window:

inside Drive View sub-window, check [ Logical ] button.

inside Logical Configuration View sub-window, check a line contains

RAID5 must be appear like that:xxxxx Mb, RAID 5, Logical Drive 1

3. Close Compaq Array Configuration Utility window.


3BK 17416 4035 RJZZA Ed. 02 15 / 40


16/40


16 / 40 3BK 17416 4035 RJZZA Ed.02


17/40

3 PI 02: Check Installed Software


This chapter describes the operations to be performed to check all the installedsoftware.

3BK 17416 4035 RJZZA Ed. 02 17 / 40


18/40


3.1 Check RNO Installation

To verify if the required version of RNO has been installed on the RNOmachine, perform the following operations:

For RNO Server 1. Open D:\RnoServer\Version.tag file.

2. Check in Minor and Major section conform with TSI.

For RNO Client 1. Open V:\RnoResourcesForClient.ini file.


For RNO Standalone 1. Open D:\RnoStandalone\Version.tag file.



3.2 Check Oracle Installation

This paragraph is applicable for all the RNO machines.

To verify if the required version of Oracle has been installed on the RNOmachine, perform the following operations:

1. Open Oracle Release Notes window by following the menu path:

Start -> Programs -> Oracle for Windows NT -> Oracle 7 WorkgroupServer Release Notes

2. Check that it is an English version.

3. Look for Oracle release that is conform with TSI.


3.3 Check Netscape Installation

This paragraph is applicable for RNO Client or RNO Standalone.

To verify if the required version of Netscape has been installed on the RNOmachine, perform the following operations:

1. Open Netscape window by following the menu path:

Start -> Programs -> Netscape Communicator -> Netscape Navigator

If the Netscape Navigator is at first running, follow the steps to create a profile.


3. To check the Netscape version, follow the menu path:

Help -> About Communicator...

Read the software version, it should be 4.7 or higher.

4. Close the Netscape window.


18 / 40 3BK 17416 4035 RJZZA Ed.02


19/40


3.4 Check Acrobat Reader Installation


To verify if the required version of Acrobat Reader has been installed on theRNO machine, perform the following operations:

1. Open Acrobat Reader window by following the menu path:

Start -> Programs -> Adobe Acrobat 4.0 -> Adobe Reader 4.0


3. To check the Acrobat Reader version, follow the menu path:

Help -> About Acrobat Reader...

Read the software version, it should be 4.0.

4. Close the Acrobat Reader window.


3.5 Check Microsoft Excel Installation


To verify if the required version of Excel has been installed on the RNOmachine, perform the following operations:

1. Open Microsoft Excelwindow by following the menu path:

Start -> Programs -> Microsoft Excel

2. Check that it is an English version.3. To check the Excel version, follow the menu path:

Help -> About Microsoft Excel

4. Read the first line in the About Microsoft Excel window, it should beMicrosoft Excel 2000 (or Microsoft Excel 97).

5. Close the Microsoft Excel window.


3.6 Check ARCserve Installation

This paragraph is applicable for RNO Server or RNO Standalone.

To verify if the required version of ARCserve has been installed on the RNOmachine, perform the following operations:

1. Open ARCserve Release Noteswindow by following the menu path:

Start -> Programs -> ARCserve -> ARCserve Release Notes


3. Check that ARCserve version is conform with TSI.


3BK 17416 4035 RJZZA Ed. 02 19 / 40


20/40


3.7 Check ARCserve Disaster Recovery Installation

This paragraph is applicable for RNO Server or RNO Standalone.

To verify if the required version of ARCserve Disaster Recovery has beeninstalled on the RNO machine, perform the following operations:

1. Open Disaster Recovery Release Notes window by following the menu path:

Start -> Programs -> ARCserve -> Disaster Recovery Release Notes


3. Check that ARCserve Disaster Recovery version is conform with TSI.


20 / 40 3BK 17416 4035 RJZZA Ed.02


21/40

4 PI 03: Check the Import Process


This chapter describes the operations to be performed to check if the importprocess from the OMC-R hosts to RNO application is correctly configuredand running.

3BK 17416 4035 RJZZA Ed. 02 21 / 40


22/40


4.1 Basic Information about the Import Process

The import process allows the transfer of a file containing the full logicalconfiguration of the running radio network, from the OMC-R hosts to theRNO machine.

This process is performed automatically and it is totally transparent for the user.It is important to present the main steps of this import process for a deeperunderstanding of the check to assure the correct actions to be performed.

The main steps are the following:

On each OMC-R host, at one precise moment (normally once per day), a

script is called to generate a file that contains the full logical configuration of

the radio network, supervised by that OMC-R host.

The RNO machine has also a scheduler that periodically checks if the file

has been generated on each OMC-R host.

If the RNO machine identifies the new generated file on the OMC-R host, itcalls a program that will transfer this file on the RNO machine.

From this moment, the logical configuration of the radio network is available

on the RNO machine, allowing the modification off line for the logical

parameters.

After the logical configuration has been modified, the modifications of the

configuration are saved into a file that will be transferred to the impacted

OMC-R host(s) and activated - this step will be covered in the next chapters.

22 / 40 3BK 17416 4035 RJZZA Ed.02


23/40


4.2 Summary of Actions for Import Process

To verify the automatic import process from the OMC-R hosts, perform thefollowing actions:

1. Edit the crontab file and modify the schedule time for

/alcatel/omc3/omc3rno/script/run_periodicExport script with anappropiate time of the current time (after 5 minutes).

2. Check that NlSCExport.tgz file is present in /alcatel/var/share/AFTR/ACIE/ACIE_NLexport_Dir1 directory.

3. To verify the automatic import process on RNO Server or RNO Standalone,modify the schedule time with an appropiate time of the current time(after 5 minutes).

4. Then look for errors at end of the file:\Programs\ImportOmc\ImpOmc.log for eachOMC-R host, where is the directory for RNO installation.

Initially, it must be note the schedule time of each OMC-R host and alsofor RNO Server or RNO Standalone.

After the verification of the automatic import process, it MUST be restoredthe schedule time, with the initial value, on all OMC-R hosts and, finally,on RNO Server or RNO Standalone.

4.2.1 Edit the Crontab File

This paragraph is applicable on each OMC-R host declared on RNO machine.

1. Log in as axadmin with the password taken from SPS.

2. Assume that the current shell is ksh; to do that, launch:axadmin@host$ echo $SHELL

if not the case, type it:axadmin@host$ ksh

3. Select the default editor (e.g.: dtpad) using to open the crontab file, to dothis - set the EDITOR variable and export it:

axadmin@host$ export EDITOR=/usr/dt/bin/dtpad

4. Now, the crontab file can be opened for edition, type the following command:axadmin@host$ crontab -e

Another window appears with the content of the crontab file.

5. Go to the line that contains the script/alcatel/omc3/omc3rno/script/run_periodicExport.

The schedule time is set as:0 22 * * *

That means in every day this script is called at 22:00.

3BK 17416 4035 RJZZA Ed. 02 23 / 40


24/40


6. Look in advance with 5 minutes at the current time and modify the scheduletime with the new time (e.g.: if the current time is 18:20, the new scheduletime is: 25 18 * * *).

7. Save the crontab file with:

File -> Save (needed)

8. Exit the crontab file with:

File -> Close

9. Close the Terminal window.


4.2.2 Check the PRC File

Perform this paragraph on each OMC-R host declared on RNO machine.

Wait about 1 hour till all the import processes, from OMC-R hosts, are finished(the time to wait depends of the cells number for the given network; for 300cells it takes about 10 minutes).

1. Log in as axadmin with password taken from SPS.

2. Verify if the NlSCExport.tgz file is present in the directory/alcatel/var/share/AFTR/ACIE/ACIE_NLexport_Dir1.

3. Verify if the done file is present in the /alcatel/var/home/rno directory

At this point, it is verified if the file containing the logical configuration of theradio network has been generated.


4.2.3 Modify the Import Schedule Time

Perform this paragraph on RNO Server or RNO Standalone.

1. Check if the Windows 2000 Scheduler is properly configured; to do thatdouble click on the Services icon from the Control Panel -> AdministrativeTools menu.

2. In the Services window, check that the Task Schedule service is started, ifnot the case then perform Action -> Start from panel menu.

The next commands are available for RNO Server. For RNO Standalone useD:\RnoStandalone instead of D:\RnoServer.

3. Go on the menu path: Start->Run

4. Browse to D:\RnoServer\Programs\OmcUpdate\impOmc.exe program,then click on [ OK ] button to launch it.

5. Go on the menu path: File > Open...

6. Reach the D:\RnoServer\Shared\Data\ImportExport\Omc\ImpOmc.cfgfile, then click on [ Open ] button.

7. Look in advance with 10 minutes at the current time and put this timeinstead of 00:00.

24 / 40 3BK 17416 4035 RJZZA Ed.02


25/40


As an example, if the current time is 18:20, replace 00:00 with 18:30in Schedule time section

8. Save the file with: File -> Save...

9. Exit program with: File -> Exit, then answer Yes to save the file again.

10. Activate the scheduler on RNO machine, to start the automatic importprocess; to do this, launch the following commands in a Command Promptwindow:

C:\> D:

D:\> cd D:\RnoServer\Programs\ImportOMC

D:\RnoServer\Programs\ImportOMC\> ImpSch.bat

It will ask to press any key to finish.

11. To verify if the scheduler knows about the import process, in the CommandPrompt window, launch:

D:\> at

Something like the following should appear on the screen:Status ID day Time Command line

0 Each M T W Th F S Su 6:30 PM D:\RnoServer\Programs\ImportOMC\ImpRun.bat

Above, the time to launch ImpRun.bat process is adapted for the appropiatetime, that is 6:30 PM.

12. Wait about 30 minutes for RNO to finish the import process.

13. Open the D:\RnoServer\Programs\ImportOMC\ImpOmc.log file to see ifthe following message is present for all the OMC-R hosts.

FTP Import Procedure SUCCESSFUL ...

14. Close Command Prompt window.


3BK 17416 4035 RJZZA Ed. 02 25 / 40


26/40


26 / 40 3BK 17416 4035 RJZZA Ed.02


27/40

5 PI 04: Create Tuning Session


This chapter describes the creation of a tuning session on the RNO machine.

3BK 17416 4035 RJZZA Ed. 02 27 / 40


28/40


5.1 Basic Information about the Tuning Session

At this time, the situation is as following:

The OMC-R has generated a file (PRC file) which contains the logical

configuration of the real radio network.

This file has been exported on the RNO machine.

The next steps in the acceptance procedure are:

1. Create a tuning session based on the PRC file uploaded from the OMC-Rhosts that have generated this file.

2. Choose at least one OMC-R host for the tuning session (the OMC-Rsoftware version is not important).

3. Modify a logical parameter.

4. Save the new modified session and export it to the impacted OMC-R host(s)from which the configuration was originally uploaded.

The final scope of this operation is to have a new configuration, modifiedusing the RNO software, and to visualize this new configuration onthe impacted OMC-R host(s). In this way, the whole operation chainimport-modification-export has been tested.

Since this new logical configuration has been generated for test purposes only,it will not be applied on the real network.

5.2 Create a Tuning Session

Perform this paragraph on the RNO Client or RNO Standalone.

To perform the operations described as principle previously, follow the stepsbelow:

Edit 1. Launch the RNO application (from the Start menu or by double-click on theRNO icon on the desktop).

2. Log in as Administrator with the password admin.

3. Wait for the Applicationmain window to appear.

4. Create a tuning session using the paragraph "Creating a Tuning Session"

from the applicable document [1]"A956 RNO User Guide".

5. Edit the created tuning session using the paragraph "Edit a Tuning Session"from the applicable document [1]"A956 RNO User Guide".

In the RNO application left window, for the created tuning session, do thefollowing actions:

Population 1. Select the BSS label positioned at the left side.

2. Select the OMC-R host(s) from which the file containing the logical networkconfiguration has been uploaded.

3. Select a BSS for each the OMC-R host(s) selected above.

4. Click on Tuning label.

28 / 40 3BK 17416 4035 RJZZA Ed.02


29/40


5. Select a logical parameter corresponding for the chosen BSS of eachOMC-R host selected before.

It can not provide a very precise parameter for test purpose only. Since this isonly a test, any parameter can be changed. The suggestion is to choose a notrelevant parameter - for example TIMER_T3111, if it exists.

6. Drag & Drop the selected parameter in the window named Tuning OperationManager: (edit),

Where is the given session name.

7. Select the validation box labeled Value, in the Tuning Operation Managerwindow corresponding to the working session.

The validation box labeled Reference is automatically deselected and aselection box with multiple values appears.

8. For the chosen logical parameter, select a value (other than the initial one),and then click on [ Update ] button.

9. Click on [ OK ] button.

10. In the Menu Bar window, click on:

Session -> Save

To save the modification for the running session.

In the RNO application right window, for the created tuning session, do thefollowing actions:

Export 1. In the Menu Bar window, click on:

Session -> Export

In the Save tuning report as window, the is already

introduced, then click on [ Save ] button.2. Wait for the export operation to be completed until a log window named

Tuning Export Log File appears. Here, check the logs for possible errors.

3. Click on [ OK ] to close the window.

When asked:Do you want to export this file to impacted OMC-R(s)

?

Answer Yes.

4. Check the logs for eventual errors in the window named Ftp Export thatcontain the logs for the transfer operation.

5. Click on [ OK ] to close the log window.For each OMC-R Host, a message like that will follow:

Export towards completed with success.

Note one OMC-R Host that was succesfully in export process, because thenext paragraph is applicable for it.

At this time, if no errors have been reported, the modified networkconfiguration file has been downloaded to the impacted OMC-R host(s).


3BK 17416 4035 RJZZA Ed. 02 29 / 40


30/40


30 / 40 3BK 17416 4035 RJZZA Ed.02


31/40

6 PI 05: Check the Export Process


This chapter describes the operations to be performed to check if the exportprocess from RNO machine to the OMC-R hosts is correctly configured andrunning.

Apply this PI on only one OMC-R host.

3BK 17416 4035 RJZZA Ed. 02 31 / 40


32/40


6.1 Basic Information about the Export Process

After the operations performed until now, the current situation is as follows:

The file containing the logical configuration for the real radio network has

been generated and transferred from the OMC-R hosts to the RNO machine.

On the RNO machine, a tuning session has been created using the

uploaded file, and a tuning operation has been performed.

The file containing the new modified logical configuration has been

transferred again to the impacted OMC-R host(s).

This PI describes how to test the export procedure, which will export the newlogical configuration to the impacted OMC-R hosts.

Since there are two types of OMC-R hosts which are concerned (B6 or B7), thenew logical configuration will be exported with respect to the OMC-R host type.

For each impacted host, the new logical configuration is exported into a

directory known for OMC-R, which can be later opened using RNUSM, andeventually applied to the real radio network, which is the final purpose ofthe RNO application.

Because its only a test, the modified radio configuration will not be appliedon the real radio network.BE CAREFUL, DO NOT APPLY THIS TUNING SESSION !

6.2 Check the Export Process for OMC-R Host

Open Tuning Browser 1. Log in as axadmin with the value taken from SPS.

2. Check if the IconBoxwindow is opened; if not, click on the icon at the rightside of the navigation bar to open it.

3. Inside the IconBoxwindow, click on the icon labeled RNO Tuning Browser.

4. Wait a few seconds until the RNO Tuning Browser appears.

Export a tuning session 1. Open the new modified session (with the path given in the notice) usingthe menu path:

File -> Open

The tuning session /alcatel/var/home/rno/.tun will beopened and exported with Tuning Browser.

2. Select the tuning session created in the previous chapter, then click on[ Open ] button.

3. Select the OMC-R where to export this tuning session.

4. Export the modified tuning session using the menu path:

File -> Export to OMC...

5. Choose [ Yes ] when you are ready for export.

6. A window must reports that the export is succesfully. Click on [ OK ] button.

32 / 40 3BK 17416 4035 RJZZA Ed.02


33/40


7. Exit from the tuning browser using the menu path:

File -> Quit

The confirm with click on [ Yes ] button.

Check the Export 1. Verify that .csv files are present in the directory (chosen in theOptions->Path Preferences menu path of Tuning Browser), by default is:/alcatel/var/share/AFTR/ACIE/ACIE_NLimport_Dir1.

2. Start the RNUSM by clicking on its icon from the A1353-RA application.

3. In the RNUSM : SC : Supervised Configuration window, open a new PRCwith the menu path:

Configuration -> Create PRC...

4. In the RNUSM : Create PRCwindow, enter the name of the PRC and clickon [ OK ] button (and wait some minutes).

5. In the RNUSM : PRC : window, import the tuning sessiondata with the menu path:

Population -> Import...

6. In the RNUSM : Import Operationwindow, select the line corresponding tothe Directory number (chosen in the Options->Path Preferences menupath of the Tuning Browser).

7. Click on [ Import ] button.

8. In the RNUSM : Follow up window, check that there is no errors.

9. Close the RNUSM : Import Operation window.

10. In the RNUSM : SC : Supervised Configuration window, select the impactedBSC, right click on it and choose Edit...

11. In the window that appear, check that the parameters modified in the tuning

session has the new value(s), then close this window.Remove PRC and exit

RNUSM1. In the RNUSM : PRC : window, follow the menu path:

Configuration -> Close PRC

2. In the RNUSM : SC : Supervised Configuration window, follow the menu path:

Configuration -> Delete PRC...

3. In the RNUSM : Configuration Selector window, select the PRC that will bedeleted and click on [ OK ] to confirm.

4. Exit from RNUSM.


3BK 17416 4035 RJZZA Ed. 02 33 / 40


34/40


34 / 40 3BK 17416 4035 RJZZA Ed.02


35/40

7 PI 06: Creating an Optimizer


This describes the actions to be performed to create a new user (calledoptimizer) for the RNO application.

3BK 17416 4035 RJZZA Ed. 02 35 / 40


36/40



1. The RNO application provides some administrative features for the user(e.g.: Tuning Session rights).

2. The goal of this PI is to test one of this features, and is optional, relying onthe client demand.

3. The tested feature is to create a new user - called optimizer - in theRNO application.

In RNO V2 (B6.2) each user has tuning session rights, but in RNO V3 (B7.2) isadded a new feature to give (or not) tuning session rights for a user.

4. To create an user called optimizer, with Tuning Session option selected,refer to the applicable document [2] "A956-RNO Administration Guide",

chapter User Manager.5. Update the Completion Check List (CCL).

36 / 40 3BK 17416 4035 RJZZA Ed.02


37/40

8 PI 07: Check RNO-NPA Interaction


This chapter describes the operations to be performed on RNO machineto check the RNO-NPA interaction.

3BK 17416 4035 RJZZA Ed. 02 37 / 40


38/40


This test will be performed on RNO Server or RNO Standalone, ONLY if anNPA machine is available.

At the beginning, assure that RNO-NPA Request Service is started:

1. Double click on Services icon from Control Panel> Administrative Tools.

2. Look if the RNO-NPA Request Service is started, if not the case thenperform Action -> Start from panel menu.

To verify the communication between the RNO machine and the NPAmachine.There are two checks to be performed:

First, verify if the required service is available on the RNO machine.

Second, verify if the RNO-NPA daemon is running on the NPA machine.

To perform this test, please follow the steps described below:

In the case presented below, it is considered that the RNO machine isRNO Server, thats why the path to execute the required script starts withD:\RnoServer. If the test is performed on a RNO Standalone , the path willstart with D:\RnoStandalone.

3. To check if the necessary service is available on the RNO machine, run thefollowing program from the DOS prompt:

D:\> \RnoServer\Programs\Npa\TestConnection -service

4. To check if the RNO-NPA daemon is running on the NPA machine, run thefollowing program from the DOS prompt:

D:\> \RnoServer\Programs\Npa\TestConnection -daemon

Both commands should return the message:Connection accepted !

If the communication between the RNO machine and the NPA machine isworking properly.


38 / 40 3BK 17416 4035 RJZZA Ed.02


39/40

9 PI 08: Check the Import from RNP


This chapter describes the operations to be performed to check the importprocess from the RNP machine to RNO machine.

3BK 17416 4035 RJZZA Ed. 02 39 / 40


40/40


This test will be performed only if an RNP machine is available.

This test has to be performed only if a connection with an RNP machine is

available on site.

The test consists only in making an import of a project (available already on

the RNP machine, as specified in the Prerequisites) to the RNO machine.

To verify the import process from the RNP machine to the RNO machine,perform the steps described below:

1. Launch the RNO Administration Workshop from the RNO group of theWindows 2000 Start menu, with the menu path:

Start -> Programs -> A956-RNO 3.0 -> RNO Administration Workshop

2. Launch the RNP Project Configuration utility.

3. Log in as Administrator with the password admin.

4. Add a new project version.

The project must already be defined on the RNP machine.

5. Import the new project version by clicking on the [ Import ] button - theproject should be imported on the RNO machine and should appear in theRNP Project Configuration main window.


Documents

Alcatel_A956-RNO Acceptance Test