BSC 3000 disk configuration

The BSC 3000 houses two types of SCSI hard disks:

• the private disks

• the shared disks

Private disks Two private or local disks are used in a BSC 3000. Each of them is associated with one OMU module:

The partitions in each private disk are split up as follows:

• The root partition "/" contains the root directory, and AIX root file.

• The "/usr", "/var", "/tmp", "home" partitions contain the AIX running software. The sizes are derived from the AIX software needs.

• The "/tmp" file system partition is used also during upgrade to store the copy of the package.

• The "/OMU_STORAGE" directory contains the applicative files stored on the OMU local and shared disk. Therw_ datadirectory is a

"read/write" directory, used for important, long life applicative data. The log directory is used for short life data, which is temporarily stored on the disk before being either sent to the OMC or erased by newer data.

In case of disk space shortage on the log directory,the rw_data directory is not affected because they are on different partitions.

• The LOCAL_LOG "/OMU_STORAGE/log/local" partition contains the dump of the AIX board, because the OMU may not have access to the shared disk when restarting.

• The LOCAL_LOG "/OMU_STORAGE/rw_data/local" partition does not contain anything.

• The LOCAL_LOG "/OMU_STORAGE/TREEn/local/usr" partition contains OAM platform and BaseOS application and tools.

Shared disks Two shared disks are used in a BSC 3000. Each of them is managed in a mirroring way for both OMU modules:

The partitions in each shared disk is split up as follows:

• Partition /OMU_STORAGE/rw_data/share, this partition contains files that are of long duration, compulsory, and whose size does not depend on the traffic or network configuration.

• Partition /OMU_STORAGE/SHARE, this partition contains the SW (switch) needed by the BSS, which includes all the former partitions (transited into directory only).

1.10.3.5 Downloading management

This function is used to download new BSS software versions to the BSC 3000 disks from the executableSoftware created and validated on the OMC-R agent disks.

User command TheDownloadcommand is available for all created software objects.

Downloading consists of copying a BSS software version from the OMC-R agent disks to the BSC 3000 disk related to the selected BSS object.

The user enters the executableSoftware name.

executableSoftware and associated DLU files are stored in dedicated directory(ies). The directory and subdirectories are identified from the information supplied by the executableSoftware.

Requirements The main requirements for the BSC 3000 are:

• No change software version command is executing on the selected BSC 3000.

• No create or download new DLU file command is being processed for the concerned executableSoftware.

• Up to five download commands that involve BSC 3000 can be executed at the same time by system users. After that, the OMC-R refuses the commands.

The STF service provided by the OMC-R agent and the MTF service on the BSC 3000 manages the download command routine.

Two download commands can be launched on BSC 3000 at the same time.

BSC 3000 software downloading The BSS software (BSC 3000, TCU 3000 and BTS) is downloaded by the BSC 3000 from the OMC-R. For each version and edition, the complete BSS software is delivered on a CD-ROM.

It is sufficient for all upgrades from any authorized version (typically N-2 and N-1 versions).

It is compressed and divided into several files in order to download only the modified files between two versions and to reduce as much as possible the duration of downloading.

The BSC 3000 stores two versions of the BSS software and the new version can be downloaded in the background without impacting BSC 3000 service.

Both the BSS software and the BSC 3000 OS can be downloaded in the background task, or installed locally from the TML through the Ethernet link.

There is no PROM memory on the BSC 3000 & TCU 3000 hardware module, with the exception of the ATM_SW module (ATM switch).

All firmware is in flash EPROM and can be modified and downloaded remotely by the system.

The complete BSS software (BSC 3000, TCU 3000 and BTS) is downloaded from the OMC-R to the BSC 3000 through FTAM.

The OMC-R and BSC 3000 are connected through Ethernet and IP protocols. The throughput is up to 10/100 Mbit/s (Ethernet standard) if the OMC is locally connected to the BSC 3000.

When the BSC 3000 is remote, a minimum throughput of 128 kbps is necessary for the efficiency of OMC-R / BSC 3000 communication.

BTS and TCU 3000 software downloading by the BSC 3000

BTS software downloading The BSC 3000 can download ten BTS/TRXs simultaneously per TMU module. With ten "active" TMU modules, 100 BTSs can be downloaded simultaneously.

TCU 3000 software downloading TCU 3000 software is downloaded by the BSC 3000. It is compressed and divided into several files, in order to download only the modified files between two versions and to reduce the downloading duration as much as possible.

The BSC 3000 stores two versions of TCU 3000 software.

The new version can be downloaded as a background task, without impacting TCU 3000 service.

The TCU 3000 software can also be installed locally from the TML.

A set of LAPD connections is used for TCU 3000 management in normal operation. These connections pre-empt (or wait for) time-slots used for communications. Two LAPD channels are managed per LSA module.

Download of a set of files (size of about 20 Mbytes per TCU 3000) lasts:

• with four LAPDs: about 20 minutes (requires a minimum of 2 LSAs)

• with eight LAPDs: about 10 minutes (requires a minimum of 3 LSAs)

Consequences

• BSC 3000 software:

— If the sWVersionNew or sWVersionFallback parameter was defined before downloading, the reference to the associated software version is deleted.

— The sWVersionNew parameter is defined with the newly loaded software version.

— The sWVersionRunning is not changed.

— The sWVersionFallback is not defined.

• BCF, TRX/DRX, and TCU 3000 software:

— If the sWVersionNew parameter was defined before downloading, the reference to the associated software version is deleted.

— The sWVersionNew parameter is defined with the newly loaded software version.

— The sWVersionRunning and sWVersionFallback parameters are not changed.

DRX automatic downloading See Section 1.10.7 "Automatic downloading of DRX software" (page 125).

1.10.3.6 BTS software background downloading