bcf software handling.pdf

8/15/2019 bcf software handling.pdf

1/36

Nokia Siemens Networks

GSM/EDGE BSS, rel.

RG10(BSS), operatingdocumentation, issue 05

Administer

BCF Software Handling

DN98633622

Issue 8-2Approval Date 2010-06-03


2/36

2 DN98633622

Issue 8-2


Id:0900d8058077eaf6

The information in this document is subject to change without notice and describes only the

product defined in the introduction of this documentation. This documentation is intended for the

use of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted

in any form or means without the prior written permission of Nokia Siemens Networks. The

documentation has been prepared to be used by professional and properly trained personnel,

and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes

customer comments as part of the process of continuous development and improvement of the

documentation.

The information or statements given in this documentation concerning the suitability, capacity,

or performance of the mentioned hardware or software products are given "as is" and all liability

arising in connection with such hardware or software products shall be defined conclusively and

finally in a separate agreement between Nokia Siemens Networks and the customer. However,

Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions

contained in the document are adequate and free of material errors and omissions. Nokia

Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which

may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO

EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-

TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-

RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED

TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY

OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION

IN IT.

This documentation and the product it describes are considered protected by copyrights and

other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark

of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2010. All rights reserved

f Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment.

Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal

injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected

has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-

nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-

zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die

Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene

Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.


3/36

DN98633622

Issue 8-2

3


Id:0900d8058077eaf6

Table of ContentsThis document has 36 pages.

1 Summary of changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 Overview of BCF software handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.1 BCF Software Handling (command group EW). . . . . . . . . . . . . . . . . . . . 8

2.2 Creation of BCF software build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.3 Software build attachment to BCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.4 Activation of BCF software build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.5 Status change of two BCF software builds . . . . . . . . . . . . . . . . . . . . . . 14

2.6 Detachment of software build from BCF . . . . . . . . . . . . . . . . . . . . . . . . 15

2.7 Deleting of BCF software build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.8 Setting of initial software build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.9 Information listing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.10 Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.11 Handling firmware build in BTSplus BCF. . . . . . . . . . . . . . . . . . . . . . . . 19

3 Bringing a new BCF software build into use . . . . . . . . . . . . . . . . . . . . . 21

3.1 Transferring a BCF software build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.2 Creating a BCF software build. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.3 Attaching a BCF software build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.4 Activating a BCF software build. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.5 Changing BCF software build statuses . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.6 Detaching a BCF software build from the BCF . . . . . . . . . . . . . . . . . . . 29

3.7 Deleting a BCF software build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4 Setting and removing an initial BCF software build . . . . . . . . . . . . . . . . 31

4.1 Setting an initial BCF software build . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4.2 Removing an initial BCF software build. . . . . . . . . . . . . . . . . . . . . . . . . 31

5 Listing BCF software information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

5.1 Listing the existing software builds . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

5.2 Listing the contents of the BCF software builds. . . . . . . . . . . . . . . . . . . 33

5.3 Listing the software configuration of the BCF . . . . . . . . . . . . . . . . . . . . 33

5.4 Listing the BCF software handling system activities . . . . . . . . . . . . . . . 33

6 Returning to the old software build in fault conditions . . . . . . . . . . . . . . 35

6.1 Returning to the old software build when the BU build is faulty. . . . . . . 35

6.2 Returning to the old software build when the NW build is faulty . . . . . . 35


4/36

4 DN98633622

Issue 8-2


Id:0900d8058077eaf6

List of FiguresFigure 1 Transferring a BCF software build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Figure 2 Creating a BCF software build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Figure 3 Attaching a BCF software build. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Figure 4 Activating a BCF software build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Figure 5 Changing BU and FB statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Figure 6 Changing NW and BU statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Figure 7 Detaching a BCF software build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Figure 8 Deleting a BCF software build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17


5/36

DN98633622

Issue 8-2

5


Id:0900d8058077eaf6

List of TablesTable 1 Software build types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Table 2 Software build statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Table 3 Initial software builds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17


6/36

6 DN98633622

Issue 8-2


Id:0900d8058077eaf6


7/36

DN98633622

Issue 8-2

7

BCF Software Handling Summary of changes

Id:0900d8058077ead5

1 Summary of changesChanges between document issues are cumulative. Therefore, the latest document

issue contains all changes made to previous issues.

Changes made between issues 8-2 and 8-1

Information on Flexi Multiradio BTS has been added.

The new build M has been added to the tables Software build types and Initial software

builds.

Changes amade between issues 8-1 and 8-0

A new section Firmware software handling in case of BTSplus site types has been

added.

The new builds XE, XM and XB have been added to the tables Software build types and

Initial software builds.


The software build creation examples changed.


Information on PrimeSite BTSs and 2nd generation BTSs has been removed.


8/36

8 DN98633622

Issue 8-2


Id:0900d8058077eaef

Overview of BCF software handling

2 Overview of BCF software handlingThe base station system (BSS) consists of base transceiver station (BTS) sites and at

least one BSC. A BTS site can be considered as the O&M functionality of a physical BTS

site.

A base transceiver station is referred to as a sector of the base station in radio network

maintenance. A sectorised BTS site can, therefore, consist of several logical BTSs. Both

types of the BTS (sectorised and unsectorised) are covered by one BCF. In Nokia

Siemens Networks's implementation of the BSS, a BTS site can consist of several

logical BTSs. One entity takes care of all the common functions of the BTSs on one BTS

site. This entity is called a base control function (BCF), which can be seen as the

common brain of several BTSs. Its main tasks are base station operation and mainte-

nance functions, that is, software loading, unit configuration, and alarm handling. The

BCF communicates with the BSC via the Abis O&M interface. The term BCF is used

here for the functional entity that offers the O&M functions of the BTS network element.

BCF software is handled in software builds, which are combinations of software entities

that provide the defined hardware with the functions required for it. The builds are

referred to as BCF software builds. A BCF software build includes the software of the

whole base station site. In the case of Flexi Multiradio BTS, Radio Module's software in

BTS can be shared with 3G or LTE

One of the advantages of a computer controlled network element is that new telecom-

munications functionalities can be introduced into existing network elements by replac-

ing and modifying the software. In the BSC, new BCF software is handled in software

builds. Software is loaded to the BCF when new BCF software is released, when a new

BTS site is brought into use, or when the BCF is restarted.

Related topics

• Bringing a new BCF software build into use

• Setting and removing an initial BCF software build

• Listing BCF software information

• Returning to the old software build in fault conditions

2.1 BCF Software Handling (command group EW)

BCF software is handled in the BSC with the commands of the commands group EW

(BCF Software Handling MML).

With the EW commands you can create and delete BCF software builds on the BSC'sdisk. You can attach the created software to a desired status in the BCF and to detach

the attached software build. A software build that is attached to the BCF can be acti-

vated. You can also change the statuses of two software builds with the status NEW,

BACKUP or FALLBACK, so that the attachment of the first status will change to the

second status and vice versa. You can set an initial build for and remove it from a BTS

site type. In addition, there are output commands that list information on the software

builds created in the BSC, the contents of the software build, and the software configu-

ration of the BCFs. You can also list ongoing build management operations. A more

thorough introduction of the EW commands is given in the following sections. Those

sections also give important information that should be taken into consideration when

using the commands. Figures are used to illustrate how the main commands of the EW

command group function.

http://dn9813293.pdf/http://dn9813293.pdf/


9/36

DN98633622

Issue 8-2

9

BCF Software Handling Overview of BCF software handling

Id:0900d8058077eaef

The most central BCF software handling actions are transferring the software build to

the BSC's disks and bringing the software build into use in the BCFs. Software is brought

into use by creating a new software build, attaching it to the desired status in the BCF

and activating the software build. When the new software build is stable, its status is

changed to BACKUP. After this the old software build can be detached from the BCF

and deleted from the software management file and from the BSC's disks.

All BCF software handling functions discussed here can be done by using local MML

commands at the BSC site or with remote MML commands from the NetAct. A new BCF

software build can be transferred into the BSC on a floppy disk on site or through the

operation and maintenance network by means of file transfer services.

Figure 1 Transferring a BCF software build

Transferring software from the NetAct is practical for mass downloads. During a down-

load, software is transferred from a higher level network element to a lower level networkelement. The transfer is carried out file by file so that the master file and all application


10/36

10 DN98633622

Issue 8-2


Id:0900d8058077eaef


files of the software are transferred. Downloading and activation can be timed so that

the system can carry out the operation when the BCFs have the least amount of traffic.

With the NetAct applications you can also have all the software builds in one controlled

place.

2.2 Creation of BCF software build

With the EWC command you create a new BCF software build into the BCF Software

Build Management File (BTMFIL).

Figure 2 Creating a BCF software build

The creation operation reads the master file and checks that all the application files

specified in the master file are in the same subdirectory. A master file contains informa-

tion on all the application files of the software build, together with their version data. A

software build is also accompanied by a master file and the master file is located in the

same subdirectory as the software build. An application file is a load unit that contains

the code and standard data of one software module, or one file block. The application

files are the smallest parts of a software build that can be separately introduced into the

BSC.

The creation operation also checks that the versions of the application files are the same

as specified in the master file. The BSC also checks that the sizes of all build files are

the same that are mentioned in the master file.

BCF PACK :

ID:MF:

EXT:SDIR:

CBTS_S300033

PACK_2

BCF PACK :

ID:MF:

EXT:SDIR:

B

BTS_S300032PACK_1

BCF PACK :

ID:MF:

EXT:SDIR:

ABTS_S300

031PACK_0

BCF-SW :

-

B

A

BSC

B I

BTS

-

A I

B

SW

SW

SW

SW

DB

RAM

DB

FLASH

DEFBU

NW

FB

Command syntax:

EWC:

Example:

MF=,EXT=,SDIR=;

EWC:C:MF=BTS_S300,EXT=033,SDIR=PACK_2;

:



11/36

DN98633622

Issue 8-2

11


Id:0900d8058077eaef

The build ID is the identity string that is used for identifying unambiguously the different

BCF software builds on the BSC's disk. The same build ID can be used in different BSCs

at the same time.

The build type is determined during creation. The BSC checks the file format of themaster file and decides the type of the build. The alternatives are DF, C, I, P, CX, E, XM,

XE, XB and M.

2.3 Software build attachment to BCF

With the EWA command you attach the software build to the desired status in the BCF

specified in the command. The BCF builds in the BSC can be attached to the BCF with

three different statuses. A build status is the activity status of a software build that is

located on a disk and is created with management commands. When the software build

is attached to the BCF, it has an activity state known as its status.

These statuses are NEW (NW), BACKUP (BU) and FALLBACK (FB).

Build type Description

DF The software build used in the Talk-family base sta-

tions.

C The software build used in the MetroSite base stations.

I The software build used in the InSite base stations.

P The software build used in the UltraSite base stations.

CX The software build used in the MetroSite and UltraSitebase stations.

E The software build used in the FlexiEDGE base sta-

tions.

XM The software build used in the BTSplus Mainline base

stations.

XE The software build used in the BTSplus eMicro base

stations.

XB The software build used in the BTSplus Basic base

stations.

M The software build used in the Flexi Multiradio base

stations.

Table 1 Software build types

Status Status description

New (NW) NEW is the status of a new software build when it is

first introduced in the BCF, after which it will be brought

into use.

Backup (BU) BACKUP is the status of a software build that is usually

defined as active and in use, and is therefore normally

loaded during initial loading when the BCF is restarted.

The BACKUP build cannot be removed with the BCF

build management commands.

Table 2 Software build statuses



12/36

12 DN98633622

Issue 8-2


Id:0900d8058077eaef


Figure 3 Attaching a BCF software build

The system automatically checks that the site type and the build type are compatible.

The attachment operation then reads the master file and checks that all the application

files specified in the master file are in the same subdirectory. It also checks that theversions of the application files are the same as specified in the master file. The BSC

also checks that the sizes of all build files are the same that are mentioned in the master

file.

If possible, the attachment operation downloads the software build to the BCF as a back-

ground operation without disturbing ongoing calls, and stores it to the BCF's non-volatile

memory by replacing the oldest build in that memory. The BCF's memory consists partly

of a non-volatile memory, which is not erased if the power supplies fail. It is possible to

save information into the non-volatile memory by a program. The BCF hardware

database and the BCF's software have been saved into the non-volatile memory. The

non-volatile memory is often called a FLASH memory.

The BCF software management system checks the load rate of the BCSU beforestarting the background downloading of the software build. If the load rate is high

Fallback (FB) FALL-BACK is the status of a software build that is

usually older than the BACKUP build, and which

usually functions as the online backup copy of the BCFsoftware build. If necessary, the FALL-BACK build can

be loaded to the BCF with the MML commands.

Status Status description

Table 2 Software build statuses (Cont.)

BCF PACK :

ID:MF:EXT:

SDIR:

CBTS_S300033

PACK_2

BCF PACK :

ID:MF:

EXT:SDIR:

B

BTS_S300032PACK_1

BCF PACK :

ID:MF:EXT:SDIR:

ABTS_S300031

PACK_0

BCF-SW :

C

B

A

BSC

B I

BTS

C

C I

B

SW

SW

SW

SW

DB

RAM

DB

FLASH

DEFBU

NW

FB

Command syntax:

Example:

EWA::;

EWA:1:NW:C;

:


13/36

DN98633622

Issue 8-2

13


Id:0900d8058077eaef

enough to possibly prevent the call setup, the downloading will be put in a queue until

the load rate decreases enough and the downloading can be started.

You can check the state of the download operation with the EWI command.

You can also monitor various phases of BCF operations on the display of the serviceterminal with the BCF Reset Phase Monitoring service terminal extension. For more

information, see BCF Reset Phase Monitoring.

2.4 Activation of BCF software build

With the EWV command you activate the attached software build and restart the BCF

with it. If necessary, the build will be loaded from the BSC's disks to the BCF.

Figure 4 Activating a BCF software build

The BCF builds in the BSC can be attached to the BCF with three different statuses.

These statuses are NEW (NW), BACKUP (BU) and FALLBACK (FB). Refer to table

Software build statuses for a description of the statuses. Each of these builds can be

activated.

The activation command changes the default build of the BCF and it stays as the default

until another build is activated. The default build is the build that is primarily used for the

initial loading of the BCF and must have the status BU, NW, or FALLBACK. Initial

loading is the loading of the computer unit's or system's load modules from disk or from

the non-volatile memory into the random access memory (RAM) for execution. There

can only be one default build at a time. Build activation normally causes a BCF restart

with the activated software. There are some cases where the BCF restart does not

begin, but the activated build is only set as a default build. These are:

BCF PACK :ID:MF:

EXT:SDIR:

CBTS_S300033PACK_2

BCF PACK :

ID:MF:

EXT:SDIR:

B

BTS_S300032PACK_1

BCF PACK :ID:MF:

EXT:SDIR:

ABTS_S300031

PACK_0

BCF-SW :

C

B

A

BSC

C I

BTS

C I

B

SW

SW

SW

SW

DB

RAM

DB

FLASH

DEF

BU

NW

FB

Command syntax:

Example:

EWV:;

EWV:1:NW;

:

http://dn9813293.pdf/http://dn9812991.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9812991.pdf/http://dn9813293.pdf/


14/36

14 DN98633622

Issue 8-2


Id:0900d8058077eaef


• the administrative state of the BCF is LOCKED

• the O&M link of the BCF is out of order

• the BCF does not respond to the reset request sent by the BSC

The activation command is rejected by the system if the software attachment procedureis still in progress. In that case the activated build is not changed to the default build and

the activation command must be given again later.

The BCF restart initiates the loading of the software build from the BSC to the BCF if the

build is not found in the BCF's non-volatile memory.

2.5 Status change of two BCF software builds

With the EWH command you change the statuses of two software builds. If the other

status is empty, the attached status will be copied to the empty one, but the empty status

cannot be copied to the attached status.

Figure 5 Changing BU and FB statuses

BCF PACK :

ID:MF:EXT:SDIR:

CBTS_S300033PACK_2

BCF PACK :

ID:MF:

EXT:SDIR:

B

BTS_S300

032PACK_1

BCF PACK :

ID:MF:EXT:SDIR:

ABTS_S300031

PACK_0

BCF-SW :

C

A

B

BSC

C I

BTS

C I

B

SW

SW

SW

SW

DB

RAM

DB

FLASH

DEF

BU

NW

FB

Command syntax:

Example:

EWH:ST1=,

EWH:1:ST1=BU,ST2=FB;

:

ST2=;

-



15/36

DN98633622

Issue 8-2

15


Id:0900d8058077eaef

Figure 6 Changing NW and BU statuses

If either one of the builds is the default build, it remains as the default after the status

has been changed.

If one status is BU and empty, and the default build has the other (NW) status, the

change command copies the NW build to the BU status and changes the build with the

BU status into the default build.

2.6 Detachment of software build from BCF

With the EWE command you remove the build attachment of the BCF.

BCF PACK :

ID:MF:

EXT:SDIR:

CBTS_S300033PACK_2

BCF PACK :

ID:MF:EXT:SDIR:

B

BTS_S300032PACK_1

BCF PACK :ID:MF:

EXT:SDIR:

ABTS_S300031

PACK_0

BCF-SW :

A

C

B

BSC

C I

BTS

C I

B

SW

SW

SW

SW

DB

RAM

DB

FLASH

DEFBU

NW

FB

Command syntax:

Example:

EWH:

ST1=,

EWH:1:ST1=NW,ST2=BU;

:

ST2=;

-



16/36

16 DN98633622

Issue 8-2


Id:0900d8058077eaef


Figure 7 Detaching a BCF software build

The default build or the BU build cannot be detached.

2.7 Deleting of BCF software build

With the EWD command you delete a BCF software build from the BCF software handling

system. If you use the parameter DSK, also the physical build files are removed from the

BSC's disks.

BCF PACK :

ID:MF:

EXT:SDIR:

CBTS_S300033PACK_2

BCF PACK :ID:MF:

EXT:SDIR:

B

BTS_S300032PACK_1

BCF PACK :ID:MF:

EXT:SDIR:

ABTS_S300031

PACK_0

BCF-SW :

C

B

BSC

C I

BTS

C I

B

SW

SW

SW

SW

DB

RAM

DB

FLASH

DEFBU

NW

FB

Command syntax:

Example:

EWE:;

EWE:1:NW;

:

-



17/36

DN98633622

Issue 8-2

17


Id:0900d8058077eaef

Figure 8 Deleting a BCF software build

You cannot delete a BCF software build that still has attachments. You cannot delete aBCF software build that has been set as the initial build.

2.8 Setting of initial software build

When you have created a software build, you can define an initial software build in

advance for each BTS site type with the EWS command.

When a BCF is created, this predefined software build is attached and activated auto-

matically to the new BCF. The initial builds are indicated with the following letters:

BCF PACK :

ID:MF:EXT:SDIR:

CBTS_S300033PACK_2

BCF PACK :

ID:MF:

EXT:SDIR:

B

BTS_S300032PACK_1

BCF PACK :ID:MF:

EXT:SDIR:PACK_0

BCF-SW :

C

B

BSC

C I

BTS

C I

B

SW

SW

SW

SW

DB

RAM

DB

FLASH

DEFBU

NW

FB

Command syntax:

Example:

EWD:

[];

EWD:A:DSK;

:

--

Build Description

D The initial build of the Talk-family base stations.

C The initial build of the MetroSite base stations.

I The initial build of the InSite base stations.

P The initial build of the UltraSite base stations.

C/P The initial build of the MetroSite and UltraSite base

stations.

E The initial build of the FlexiEDGE base stations

XM The initial build of the BTSplus Mainline base stations.

XE The initial build of the BTSplus eMicro base stations.

Table 3 Initial software builds



18/36

18 DN98633622

Issue 8-2


Id:0900d8058077eaef


The build is attached to the BU status. If the O&M link of the BCF is already in the

working state, the system also background downloads the software build into the BCF.

You may thus ignore two standard manual work phases, attaching and activating, in

BTS commissioning.

You can also remove or change the initial build with the EWS command at any time. You

can see the initial BCF software builds with the EWL command.

2.9 Information listingWith the EWI command you can output ongoing BCF software handling system activities

like background downloading or saving software to the BCF's non-volatile memory. The

command also shows operations in the pending state.

You can output all the created software builds on the BSC's disks with the EWL

command. The command shows the following information on each created software

build:

• build ID

• build type

• release version

• initial build of the BTS site type

• master file name

• subdirectory

• connection counter

The connection counter tells how many attachments have been made to the software

build.

You can output the software configuration of the BCF with the EWO command. The

command shows the following information on all attached software builds of the BCF:

• status

• build ID

• release version • subdirectory

• state (“DEFAULT” in this field indicates the default build)

• software master

• in the case of Flexi Multiradio BTS, if the Radio Module is shared and the software

master is WCDMA, then also the file name and the version of the active software in

Radio Module are shown.

You can output build and file information on the application files included in the software

build with the EWP command. The command shows the following information on the BCF

software build:

• build ID

• build type

XB The initial build of the BTSplus Basic base stations.

M The initial build of the Flexi Multiradio base stations.

Build Description

Table 3 Initial software builds (Cont.)

http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/


19/36

DN98633622

Issue 8-2

19


Id:0900d8058077eaef

• release version

• master file name

• master file version

• subdirectoryIn addition, it also shows the following information on the files of the software build: appli-

cation file names, file versions, freezing dates, file types, and unit information which indi-

cates the units in which these files will be run.

2.10 Capacity

The BSC manages BCF software in builds. In the BSC's disks there are 40 subdirecto-

ries for BCF software, each containing one build.

The BCF software builds are located in various disk directories and each software build

is located in its own subdirectory. For more information on the directory structure, refer

to figure BSC directory tree in BCF Hardware Database Handling .

The capacity of the BCF software management files limits the number of BCF software

builds that can be created in one BSC. The BSDATA (BSS Radio Network Configuration

Database) limits the number of the BCFs that can be created in one BSC. The capacity

of the management files is the following:

• the maximum number of BCFs created in a BSC depends on the BSC configuration

(see Product Descriptions Product Description of Base Station Controller BSC2i,

BSCi and Product Description of Base Station Controller BSC3i ).

• the maximum number of software builds created in a BSC is 40

• the possible status of a BCF software build attached to a BCF is NEW (NW),

BACKUP (BU), or FALL-BACK (FB). At any one time there can be only one command managing BCF software handling in

the BSC, but one command can handle several BCFs at the same time.

The maximum number of simultaneous download operations has been restricted to 32.

If there are no resources left, the BSC puts the extra downloading operations in a queue

until resources are available again. It is possible to load the same build to every BCF or

a different one to each BCF.

2.11 Handling firmware build in BTSplus BCF

In the BTSplus BCF, firmware (FW) build is handled in the BSC with the commands of

the command group EW (BCF Software Handling MML). With the EW command, youcan create firmware build to its own BCF SW management file. You can attach the

firmware build to BTSplus BCFwith the NEW status.

After attaching, BSC starts the background download for the firmware build if O&M link

is in order. BTSplus automatically upgrades firmware build within BTS after background

download. When the firmware build is up and running in BTSplus, detach firmware build

from the BCF with the EW command that the NEW status can be released for the BCF

software build management.

Attach a valid software build with NEW status to BTSplus after firmware build download

so that the software build overwrites the firmware build in the non-volatile memory in

BTSplus. This software build should be the same one which is already running in

BCFand attached in the BACKUP status. After software build background download,

http://dn98799836.pdf/http://dn99558545.pdf/http://dn99558545.pdf/http://dn01149718.pdf/http://dn01149718.pdf/http://dn99558545.pdf/http://dn99558545.pdf/http://dn98799836.pdf/


20/36

20 DN98633622

Issue 8-2


Id:0900d8058077eaef


you shall detach BCF software build from the NEW status that the same software build

is not attached twice to BTSplus in BCF software management.


21/36

DN98633622

Issue 8-2

21

BCF Software Handling Bringing a new BCF software build into use

Id:0900d80580790704

3 Bringing a new BCF software build into useBringing the BCF software build into use can be separated into the phases listed below

as links. The procedures in that list are to carry out in the presented order.

BCF software handling functions discussed in the following sections can also be per-

formed from the NetAct.

Before you start

The following initial conditions should be met before you start to bring a new BCF

software build into use:

• the BSC's OMU is in the normal working state (WO-EX) (the USI command)

• both of the BSC's disks are in the normal working state (WO-BU) (the ISI

command)

The new BCF software build should be tested with one BCF. When its stability has been

proven to be good, the software build can be distributed to the other BCFs.

3.1 Transferring a BCF software build

Before you start

The BCF software builds are located in the subdirectories on the BSC's disks. On the

disk there is a directory named BCF_PACK and subdirectories named PACK_X. The

value of X ranges from 0 to 39. Ensure that the new BCF software build is located on a

floppy disk (the IWX command). Copy the BCF software build files to the first unused

build subdirectory of both disks, for example from a floppy disk.

Steps

Output the existing software builds and their subdirectories (EWL).

With this command you search the first subdirectory that does not include any created

software builds.

ZEWL;

The command has no parameters.

2 Check that the subdirectory is empty on both disks (IWX).

ZIWX::,::,;

3

Delete the extra files from the subdirectory (IWD).

You can delete the extra files from the subdirectory if the subdirectory is not empty but

it contains no files that associated with the created software builds.

ZIWD::,::,,,;

4 Define the source of the software build on the floppy disk (IWY).

ZIWY::DRIVE=;

http://dn987175.pdf/http://dn986043.pdf/http://dn986079.pdf/http://dn9813293.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn9813293.pdf/http://dn986079.pdf/http://dn986043.pdf/http://dn987175.pdf/


22/36

22 DN98633622

Issue 8-2


Id:0900d80580790704

Bringing a new BCF software build into use

5 Define the destination of the software build in unused subdirectories on both

disks (IWY).

ZIWY::PATH=,DRIVE=;

6

Copy the files to the subdirectory (IBC).

ZIBC:,,,,,,;

7

Check that all the files have been copied (IWX).

ZIWX::,::,;

Further information

Example: Outputting the existing software builds and their subdirectories

ZEWL;

Example: Checking that the subdirectory is empty on both disks

ZIWX::WS,NODEF:BCF_PACK,PACK_0:%,%;

ZIWX::WB,NODEF:BCF_PACK,PACK_0:%,%;

Example: Deleting the extra files from the subdirectory

ZIWD::WSB,NODEF:BCF_PACK,PACK_0:%,%,0,CON;

Example: Defining the source of the software build on the floppy disk

ZIWY:S:DRIVE=FDU-N0;

Example: Defining the destination of the software build

ZIWY:D:PATH=/BCF_PACK/PACK_0,DRIVE=WDU-SB;

Example: Copying the files to the subdirectory

ZIBC:FDU,,%,%,,WDU,SB;

Example: Checking that all the files have been copied

ZIWX::WS,NODEF:BCF_PACK,PACK_0:%,%;ZIWX::WB,NODEF:BCF_PACK,PACK_0:%,%;

3.2 Creating a BCF software build

The build ID must be unique in the BSC. You can output the already created BCF

software build names in the BSC with the EWL command.

http://dn986079.pdf/http://dn70541437.pdf/http://dn986079.pdf/http://dn9813293.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn70541437.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn70541437.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn9813293.pdf/http://dn986079.pdf/http://dn70541437.pdf/http://dn986079.pdf/


23/36

DN98633622

Issue 8-2

23


Id:0900d80580790704

Steps

Create a BCF software build (EWC).

ZEWC::MF=,EXT=,SDIR=;

2

Check the error code that the system outputs after the creation.

Check the error code that the system outputs after the creation. The error codes and

their meanings are explained in General Error Messages of System. If the command

execution was not successful, refer to section Unexpected outcome below.

Expected outcome

The creation is successful.

Example: Creating a BCF software build

ZEWC:EP_2_0:MF=BTS_2000,EXT=058,SDIR=PACK_0;

Unexpected outcome

If creating a BCF software build fails an error code appears. If the error code is

a) MASTER FILE NOT FOUND, APPLICATION FILE NOT FOUND, DIRECTORY

NOT FOUND, or BUILD DIRECTORY IN USE, check the files and directories of the

new BCF software build by following the steps from 1 to 4.

b) BUILD ID ALREADY EXISTS, check the build identifier by following the steps from

5 to 7.

c) DEVICE NOT IN USE, check the BSC's disks by following the steps 8 and 9.For more information on the parameters, see Disk File and Directory Handling .

To correct the situation follow the steps below.

a) Check that the subdirectory is correct (IWX).

ZIWX::,::,;

b) Check that all the files are in the subdirectory (IWX).

ZIWX::,::,;

c) Check that the version of the software build files are correct (IWX).

ZIWX::,::,;

d) Repeat the creation operation.

e) Check that the given build identifier is correct (EWL).

ZEWL;


f) Check that the identifier is unique in the BSC (EWL).

ZEWL;


g) Repeat the creation operation.

h) Check that both BSC's disks are in working state (ISI).

ZISI::;i) Repeat the creation operation.

http://dn9813293.pdf/http://dn9813293.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn986043.pdf/http://dn986043.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn9813293.pdf/http://dn9813293.pdf/


24/36

24 DN98633622

Issue 8-2


Id:0900d80580790704


Further information

Example: Checking a new BCF software build

ZIWX::WS,NODEF:BCF_PACK,PACK_0:%,%;

Example: Checking the build identifier

ZEWL;

Example: Checking the BSC's disks

ZISI::WDU;

3.3 Attaching a BCF software build

Steps

Check that the BCF object has been created in the BSDATA ( EEI).

ZEEI

2

Check the BCF's NW status (EWO).

ZEWO:;

Check that the BCF's NW status is empty and there are no software builds attached to

the NW status. If there is a build attached to the NW status, check if the build is the

default build or not.

3

Detach the build attached to the NW status if it is not the default build (EWE).

ZEWE::;

If the default build has been attached to the NW status, follow the tasks described in

Changing BCF software build statuses and Detaching a BCF software build from the

BCF.

4

Attach the software build to the NW status of the BCF (EWA).

ZEWA:::;

5 Check the command printout.

If the printout shows something other than the BCF identifier and DOWNLOAD-

STARTED or DOWNLOAD-DENIED (BUILD IN FLASH), refer to section Unexpected

outcome below. DOWNLOAD-DENIED (BUILD IN FLASH) means that the software

build already exists in the BCF's non-volatile memory so there is no need to download

the build again.

Expected outcome

The attachment is successful.

Example: Checking the BCF's NW status

ZEWO:1;



25/36

DN98633622

Issue 8-2

25


Id:0900d80580790704

Example: Detaching a build

ZEWE:1:NW;

Example: Attaching the software build

ZEWA:1:NW:EP_2_0;

Unexpected outcome

a) If the command printout is BCF identifier and DOWNLOAD-PENDING (NO

RESOURCES), the download operation will be in the download queue until the

download resources are again available.

Use the ZEWI command to see when the download has been started.

ZEWI:;

b) If the command printout shows the BCF identifier and DOWNLOAD-PENDING

(LOAD RATE), the download operation will be in the download queue until the load

rate of the BCSU unit decreases. Use the EWI command to see when the download

has been started.

ZEWI:;

c) If the command printout shows the BCF identifier and DOWNLOAD-DENIED (O &

M LINK STATE), follow the steps from 1 to 3.

ZDTI;

ZDTC::,;

d) If the command printout shows the BCF identifier and DOWNLOAD-DENIED

(ONGOING RESET), use the EFO command to see when the BCF restart has been

finished, that is, when the BCF has moved from operational state BL-RST (blocked-

reset) to operational state WO. Then repeat the attachment.

ZEEI:BCF=;

e) If the command printout shows the BCF identifier and DOWNLOAD-DENIED

(PARTLY OK), at least one TRX has started the downloading and at the same time

at least one downloading has failed. Check with the EOL command if alarm 7713

(SOFTWARE BACKGROUND DOWNLOAD TO BCF FAILS) has been set. Follow

the instructions of the alarm to correct the fault. Use the command EWI to see when

the ongoing loading is finished. Then repeat the attachment.

ZEOL:;

ZEWI:;

f) If the command printout shows an error code, check the reason for it in General Error

Messages of System and correct the situation. Then repeat the attachment.

g) If the error code is MASTER FILE NOT FOUND, APPLICATION FILE NOT FOUND,

DIRECTORY NOT FOUND, or BUILD DIRECTORY IN USE, check the files anddirectories of the new BCF software build by following the steps from 4 to 7.

h) If alarm 7713 (SOFTWARE BACKGROUND DOWNLOAD TO BCF FAILS) is set,

follow the instructions of the alarm. Then repeat the attachment.

The alarm 7713 is set if the background downloading of the BCF software build from

the BSC to the BCF has failed. There is a field in the alarm output which gives more

detailed information on the fault phase (QUEUING, DOWNLOADING or SAVING

TO FLASH).

After the cause of the interruption has been repaired, you must detach the software

build from the BCF. You must also check the O&M link state and attach the BCF

software build to the BCF again.

You must cancel the alarm with an MML command.

http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn985765.pdf/http://dn985765.pdf/http://dn9813196.pdf/http://dn9813184.pdf/http://dn9813239.pdf/http://x%3Dd%3Do%3Dc/s-000005.pdfhttp://dn9813293.pdf/http://dn9813239.pdf/http://dn9813293.pdf/http://x%3Dd%3Do%3Dc/s-000005.pdfhttp://x%3Dd%3Do%3Dc/s-000005.pdfhttp://x%3Dd%3Do%3Dc/s-000005.pdfhttp://x%3Dd%3Do%3Dc/s-000005.pdfhttp://dn9813293.pdf/http://dn9813239.pdf/http://dn9813293.pdf/http://x%3Dd%3Do%3Dc/s-000005.pdfhttp://dn9813239.pdf/http://dn9813184.pdf/http://dn9813196.pdf/http://dn985765.pdf/http://dn985765.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/


26/36

26 DN98633622

Issue 8-2


Id:0900d80580790704



a) Check the O&M link state (DTI).

ZDTI

b) Change the state of the link to WO-EX (DTC).ZDTC

ZDTC::,;

c) Repeat the attachment.

d) Check that the subdirectory is correct (IWX).

ZIWX::,::,;

e) Check that all the files are in the subdirectory (IWX).

ZIWX::,::,;

f) Check that the version of the software build files are correct (IWX).

ZIWX::,::,;

g) Repeat the attachment operation.

Further information

Example: Checking when the download has been started

ZEWI:1;

Example: Checking and changing the O&M link state

ZDTI;

ZDTC:CLS00:,WO;

Example: Checking when the BCF restart is finished

ZEEI:BCF=1;

Example: Checking if the alarm is set and checking when the loading is finished

ZEOL:1;

ZEWI:1;

3.4 Activating a BCF software build

Before you start

Note that activating the BCF software build causes a BCF reset.

Steps

Check that the software build you want to activate has been attached to the BCF

with the required status (EWO).

ZEWO:;

2 Activate the software build.

ZEWV::;

http://dn985765.pdf/http://dn985765.pdf/http://dn985765.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn9813293.pdf/http://dn985765.pdf/http://dn985765.pdf/http://dn9813184.pdf/http://dn9813239.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813239.pdf/http://dn9813184.pdf/http://dn985765.pdf/http://dn985765.pdf/http://dn9813293.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn985765.pdf/http://dn985765.pdf/http://dn985765.pdf/


27/36

DN98633622

Issue 8-2

27


Id:0900d80580790704

3 Check the command printout.

If the printout shows something other than the BCF identifier and RESET-STARTED,

see alarm description of the alarm 7715 below. Otherwise move to the next step.

4

Check the BCF's operational state.

Check that the BCF's operational state receives the value WO.

ZEEI:BCF=;

Expected outcome

The activation is successful.

Example: Checking the software build

ZEWO:1;

Example: Activating the software build

ZEWV:1:NW;

Example: Checking the command printout

ZEEI:BCF=1;

Unexpected outcome

a) If the command printout shows the BCF identifier and RESET DENIED (O & M LINK

STATE), follow the steps from 1 to 3.

b) If the command printout shows the BCF identifier and RESET-DENIED (ADMINIS-

TRATIVE STATE), follow the steps 4 and 5.c) If the command printout shows the BCF identifier and RESET-DENIED (ALL TRXs

NOT RESTARTED), at least one TRX has restarted but at the same time at least

one TRX restart has failed. Follow the steps from 6 to 9.

d) If the command printout shows an error code, check the reason for it in General Error

Messages of System and correct the situation. Then restart the activation.


a) Check the O&M link state (DTI).

ZDTI;

b) Change the O&M link state to WO-EX (DTC).

ZDTC::,;

c) Repeat the activation.

d) Check the BCF's administrative state (EEI).

ZEEI:BCF=;

The state of the BCF must be unlocked.

e) Change the state if necessary (EFS).

ZEFS::;

f) Check the alarm printout (EOL).

ZEOL:;

g) Follow the instructions of the alarm to correct the fault.

h) Check when the ongoing restart has finished (EEI).

That is when the state has changed from BL-RST to WO.ZEEI:BCF=;

http://x%3Dd%3Do%3Dc/s-000005.pdfhttp://dn9813184.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813184.pdf/http://dn985765.pdf/http://dn985765.pdf/http://dn9813184.pdf/http://dn9813196.pdf/http://dn9813239.pdf/http://dn9813184.pdf/http://dn9813184.pdf/http://dn9813239.pdf/http://dn9813196.pdf/http://dn9813184.pdf/http://dn985765.pdf/http://dn985765.pdf/http://dn9813184.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813184.pdf/http://x%3Dd%3Do%3Dc/s-000005.pdf


28/36

28 DN98633622

Issue 8-2


Id:0900d80580790704


i) Repeat the activation.

Further information

Example: Checking and changing the O&M linkZDTI;

ZDTC:CLS00:,WO;

Example: Checking the BCF's administrative state

ZEEI:BCF=1;

ZEFS:1:U;

Example: Checking the alarm printout and whether the restart is finished

ZEOL:1;

ZEEI:BCF=1;

The alarm 7715 is set if the O&M unit of the BCF is caught in a circle of resets. The BCF

or has received at least 3 resets within 30 minutes. When this alarm is set, the BCF is

unable to operate properly.

You must find out the reason why the BCF is receiving continuous resets and correct

the error that causes them. Possible reasons for the error can be, for example, a wrong

hardware database in the BCF, a hardware fault in the BTS, a change of the O&M link

state during the reset, or a corrupted BCF software build.

The system cancels the alarm when 15 minutes have passed after the last reset of the

BCF.

3.5 Changing BCF software build statuses

Steps

Interchange attached builds between the FB and BU statuses (EWH).

ZEWH::ST1=,ST2=;

When the NW build is stable, use the EWH command to interchange attached builds

between the FB and BU statuses.

If the other status is empty, the attached status will be copied to the empty one.

2

Interchange the BU and NW statuses (EWH).

ZEWH::ST1=,ST2=;

Further information

Example: Interchanging attached builds

ZEWH:1:ST1=BU,ST2=FB;

Example: Interchanging the BU and NW statuses

ZEWH:1:ST1=NW,ST2=BU;

http://dn985765.pdf/http://dn985765.pdf/http://dn9813184.pdf/http://dn9813196.pdf/http://dn9813239.pdf/http://dn9813184.pdf/http://x%3Dd%3Do%3Dc/s-000005.pdfhttp://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://x%3Dd%3Do%3Dc/s-000005.pdfhttp://dn9813184.pdf/http://dn9813239.pdf/http://dn9813196.pdf/http://dn9813184.pdf/http://dn985765.pdf/http://dn985765.pdf/


29/36

DN98633622

Issue 8-2

29


Id:0900d80580790704

3.6 Detaching a BCF software build from the BCF

Steps

Check the BCF software build (EWO).

ZEWO:;

Check that the BCF has a software build that has been attached to the required status

and that it is not the default build or the BU build.

2 Detach the software build from the BCF (EWE).

ZEWE::;

3

Check the command printout.If the system outputs an error code, check it in General Error Messages of System, find

out the reason for it, correct the fault, and try again.

Further information

Example: Checking the BCF software build

ZEWO:1;

Example: Detaching the software build from the BCF

ZEWE:1:NW;

3.7 Deleting a BCF software build

Before you start

The BCF software build files cannot be deleted from the subdirectory where the files for

the created builds are located.

Steps

Check if the software build has any attachments (EWL).

Note also the subdirectory name where the build files are located. If the build has been

attached to the BCF, it must be detached before it can be deleted.ZEWL;


2

Delete the software build using the parameter value DSK (EWD).

ZEWD::;

Further information

If the command execution failed, check the error code from General Error Messages of

System, correct the situation and try again.

http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/


30/36

30 DN98633622

Issue 8-2


Id:0900d80580790704


Example: Checking the software build

ZEWL;

Example: Deleting the software build

ZEWD:EP_1_0:DSK;

If you have problems with deleting the physical software build files with the EWD

command, you have to delete them with the commands of the I/O system. See Disk File

and Directory Handling (command group IW).

The BCF software build files must not be deleted from the subdirectory where the files

for the created builds are located (IWD command).

For an overview, see Overview of BCF software handling.

http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn986079.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/


31/36

DN98633622

Issue 8-2

31

BCF Software Handling Setting and removing an initial BCF software build

Id:0900d80580790752

4 Setting and removing an initial BCF software

build

You must create a BCF software build before you can set it as the initial BCF softwarebuild.

4.1 Setting an initial BCF software build

Steps

Check that the software build has been created (EWL).

ZEWL;


2

Set the initial software build (EWS).

ZEWS::;

3

Check that the software build has been set as the initial build (EWL).

ZEWL;


If the command execution failed, correct the situation and try again.

Further information

Example: Checking that the software build has been created

ZEWL;

Example: Setting the initial software build

ZEWS:E:EP_2_0;

Example: Checking that the software build has been set as the initial build

ZEWL;

4.2 Removing an initial BCF software buildSteps

Check that the initial software build is set for the BTS site type (EWL).

ZEWL;


2

Remove the initial software build (EWS).

ZEWS:;



32/36

32 DN98633622

Issue 8-2


Id:0900d80580790752

Setting and removing an initial BCF software build

3 Check the command printout to see that the command execution was successful.

If the command execution failed, correct the situation and try again.

4

Check that the initial build is removed (EWL).

ZEWL;


Further information

Example: Checking the initial software build

ZEWL;

Example: Removing the initial software build

ZEWS:E;

Example: Checking that the initial build is removed

ZEWL;


http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/


33/36

DN98633622

Issue 8-2

33

BCF Software Handling Listing BCF software information

Id:0900d8058061bb55

5 Listing BCF software information

5.1 Listing the existing software buildsSteps

Output all the created software builds on the BSC's disks (EWL).

ZEWL;


5.2 Listing the contents of the BCF software builds

Steps

Output build and file information on the application files (EWP).

ZEWP:ID=;

ZEWP:MF=,EXT=,SDIR=;

5.3 Listing the software configuration of the BCF

Steps

Output the software build configuration (EWO).

ZEWO:;

5.4 Listing the BCF software handling system activities

Steps

Output the ongoing activities (EWI).

ZEWI:;

Further information

Example: Listing the existing software builds

ZEWL;

Example: Listing the contents of the BCF software builds

ZEWP:ID=EP_2_0;

or

ZEWP:MF=BTS_2000,EXT=058,SDIR=PACK_0;



34/36

34 DN98633622

Issue 8-2


Id:0900d8058061bb55

Listing BCF software information

Example: Listing the software configuration of the BCF

ZEWO:1&5&&10;

Example: Listing the BCF software handling system activities

ZEWI:1&2&5&&10;


http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/


35/36

DN98633622

Issue 8-2

35

BCF Software Handling Returning to the old software build in fault conditions

Id:0900d8058061bb58

6 Returning to the old software build in fault

conditions

6.1 Returning to the old software build when the BU build is

faulty

Steps

Activate the build with the FB status (EWV).

ZEWV::;

2

Interchange the statuses FB and BU (EWH).

ZEWH::ST1=,ST2=;

3

Detach the software build with the FB status (EWE).

ZEWE::;

Further information

Example: Activating the build with the FB status

ZEWV:1:FB;

Example: Interchanging the statuses FB and BU

ZEWH:1:ST1=BU,ST2=FB;

Example: Detaching the software build with the FB status

ZEWE:1:FB;

6.2 Returning to the old software build when the NW build is

faulty

Steps

Activate the software build with the BU status (EWV).

ZEWV::;

2

Detach the software build with NW status (EWE).

ZEWE::;

Further information

Example: Activating the software build with the BU status

ZEWV:1:BU;

http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/http://dn9813293.pdf/


36/36

BCF Software HandlingReturning to the old software build in fault conditions

Example: Detaching the software build with NW status

ZEWE:1:NW;


Documents

bcf software handling.pdf