• No results found

OMC-R software management

In document Nortel GSM BSS Fundamentals (Page 95-100)

General operating mechanisms

1.9 AMR Overview

1.10.2 BSC 12000HC software management .1 Principles

1.10.2.3 OMC-R software management

Identifying the software deliveries A DVD formatted delivery tape is identified by a delivery name and contains the following two records:

The first record contains two empty files: the name of one of the files is set from the name of the EFT recorded on the DVD and is suffixed

".EFT", the name of the other file is set from the name of the delivery and is suffixed ".LIV".

The second record contains the EFT itself, that is a directory named after the EFT, with the consisting files, and the associated DLU files.

A delivery name does not depend on the version of the software and DLUs stored on the DVD.

Identifying the EFTs An EFT containing BSS software has a standard name that defines the associated software type and version, and is used to create a specific directory on the OMC-R manager and agent disks. The name of an EFT is formatted as follows:

BSC 12000HC software: Format = "BSxabvcdefgh"

Field Meaning Value

BSx Name x = [1 .. .4]

ab Version number [09 ... 32]

v Reserved

cd Sub-version number [01 ... 99]

ef Edition number [01 ... 99]

gh Patch version [01 ... 99]

BTS/TRX/TCU software: Format = "XXXabcdef"

Field Meaning Value

XXX Name CBC (S8000 CBCF)

IBC (S12000)

Identifying the DLUs The name of a DLU configuration file is coded as

"Fabcyyyz", where:

abc is the software version number (ab = [08 to 32], c = [A to H]).

yyy is the hardware configuration index (0 to 9, A to V) of the DLU file for the equipment.

z is the revision factor (0 to 9, A to V).

The DLU name is used to create a special subdirectory under the associated EFT directory on the OMC-R manager and agent disks.

BSS software management by the OMC-R manager User commands are available when using the OMC object:

Read Gigatape

Copy a set of transferable files containing a BSS software version and the associated DLUs supplied on DVD to the OMC-R manager disks..

The DVD must be installed in the drive of the active OMC-R manager server.

The delivery and EFT names supplied on the tape are displayed in session logs when the copy is complete. The EFT name defines the OMC-R manager disk directory where the EFT is stored.

Download EFT to md

Copy an EFT containing a BSS software version and the associated DLUs from OMC-R manager disks onto OMC-R agent disks.

The EFT to download is identified by name. The OMC-R agent disk directory used to store the EFT must be created (see next Paragraph).

Download and validate EFT from Gigatape to md

Copy a set of transferable files containing a BSS software version and the associated DLUs supplied on DVD to the OMC-R manager and agent disks, and validate the EFT and DLU downloading to disk.

This command enables to gather in one command the two previous listed commands and the two creating commands described in the following subparagraph.

Delete EFT

Delete an EFT containing a BSS software version and the associated DLUs from the OMC-R manager disks.

The EFT is identified by name. The disk directory and all the files it contains are deleted.

List EFT

Display the list of EFTs and associated DLUs created on the OMC-R manager disks. The OMC-R manager file manager supplies theinformation.

BSS software management by the OMC-R agent This function performs tasks that may cause the OMC-R operations database (BDE) to be updated.

User commands are available using the md object as follows:

Create EFT dir

Create a directory on the OMC-R agent disks to store an EFT containing a BSS software version and the associated DLUs.

The directory is identified by the name of the EFT due to be downloaded next (see previous Paragraph):

— BSC 12000HC software: The EFT creation is not already validated (see next).

— BCF software: If the EFT creation is already validated, the command can be used to associate more DLU files to the EFT.

— TRX/DRX and TCB software: The EFT creation is not already validated (see next).

Create EFT

Validate an EFT and associated DLU downloading to the OMC-R agent disks (see previous Paragraph) to declare the BSS software version to the OMC-R agent Software Management function.

If the command follows a Create EFT dircommand used to associate more DLU files to the EFT, downloading the EFT to a BSC 12000HC disk is forbidden until the command is complete.

The directories corresponding to an EFT delivery that is not validated are automatically cleared and deleted when they are more than three days old.

Delete EFT

Delete an EFT and the associated DLUs from the OMC-R agent disks.

The disk directory and all the files it contains are deleted.

The command is refused if the software version is referenced by a software object created in the BDE.

List EFT

Display the list of EFTs and associated DLUs created on the OMC-R agent disks. The OMC-R agent file manager supplies the information.

List (object instances referencing an EFT)

Display the list of software objects that reference a named EFT. The BDE supplies the information.

This command is a multiple-type command (scope & filter) and cannot be accessed using a software object. It can be used before deleting an EFT to check whether the EFT is referenced.

EFT loading sequence BSS software loading commands must be entered in the following order to allow the OMC-R Software Management function to organize software versions correctly:

Read GigaTape(omc object)

Create EFT dir(md object)

Download EFT to md (omc object)

Create EFT(md object)

After the system validates the last command, the EFT is effectively accepted by the OMC-R agent Software Management function and can be downloaded to the BSC 12000HC disk.

Use the Download and validate EFT from Gigatape to md command instead of the four separate commands listed above.

Consulting BSS and OMC-R software markers This function identifies the software applications currently running on BSS entities and on OMC-R manager and agent servers.

The marker files are stored in BSC 12000HC and OMC-R server disk directories. A software application marker contains the following information:

type (BSS entity or server) and name of the associated entity

name and number of the application version (a version number is encoded in Vab_cd Enn format)

a variable comments area, depending on the application type (usually the date when the application was generated)

Consulting BSS software markers TheDisplay markerscommand on any created software object provides the following information:

software versions running on a BSC 12000HC, radio site BCF, radio transceiver (TRX/DRX), or remote transcoding unit (TCB)

PROM software versions in the same entities

BSC 12000HC prototype application database (BDA) configuration files

The command run invokes a reference file updated by the BSC 12000HC that contains the list of BSS markers. The BSC 12000HC then sends the information to the OMC-R.

A reference file updating request is sent to the BSC 12000HC and the resulting information is provided to users.

Consulting OMC-R software markers The Display markers

command on the md object identifies the OMC-R agent active and passive server software applications.

The Display server markers and Display workstation markerscommands on the omc object respectively identify the OMC-R manager active and passive server software applications, and the software applications of a given workstation.

The file manager provides information on the application software that is running in the servers and workstations.

In document Nortel GSM BSS Fundamentals (Page 95-100)