BSC6900V900R011 GO Installation and Upgrade of BSC6900 Software ISSUE1.0

www.huawei.com

Security Level: Internal Use

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential

Installation and Upgrade of

BSC6900 Software

ISSUE1.0

2009-08

TSD Wireless Product Service Department—GBSS Product Team

HUAWEI TECHNOLOGIES Co., Ltd. Page 2HUAWEI Confidential

Software Structure of BSC6900

Installation of Linux

Installation and Upgrade of BSC6900 Software

Introduction of OMU Installation Directory

Routine Maintenance of OMU


Familiar with the software structure of BSC6900

Familiar with the installation process of Linux

Familiar with the installation and upgrade processes of

BSC6900 software

Familiar with the routine maintenance of OMU


BSC6900 OMU Administration Guide

BSC6900 V900R011C00 Upgrade Guide


Chapter 1 Software Structure ofChapter 1 Software Structure of BSC6900BSC6900

Chapter 2 Installation of Linux

Chapter 3 Installation and Upgrade of BSC6900

Software

Chapter 4 Routine Maintenance of OMU


Position of the BSC6900

Network architecture



Host software

OMU software

LMT software

GOMU

Software structure of the BSC6000

OMU

Software structure of the BSC6900

OMU software

Host software



OMU software

The OMU software runs on the OMUa/OMUb board and handles the O&M functions of the

BSC6900. It consists of the operating system and the OMU applications. Operating system: For the newly delivered product, the Dopra Linux operating system is used.

For the inventory sites where the upgrade is required, both Suse Linux and Windows are

supported. OMU application: The OMU application runs above the underlying operating system. It

provides various processes such as LMT process, fault diagnosis process, authentication

process, and so on.

The Web LMT is a part of the OMU applications. With the GUI-based Web LMT, users can

operate and maintain the BSC by running MML commands. The functions such as alarm

query, message tracing, performance monitoring, and device maintenance can be performed.

The LMT is totally web-based, which means no installation is required. You can use a web

browser directly to log in to the Web LMT.



The biggest difference between the BSC6900 and BSC6000 is that in BSC6900 one

process is changed to multiple processed, thus improving performance and reliability.

BSC6900 BSC6000

OMU applications

The OM processes of the BSC6900 are different from the BSC6000. The BSC6900 OM processes include host_gate, ems_gate, authority, configure, maintain, stat, alarm, software, ftp_server, sntp, btsom, ems_agent, omu_manager, and Weblmt. Each process can run independently and perform the functions such as BSC/BTS configuration, maintenance, software management, and NMS interfacing. Each service board also has a maintenance software module, which works together with the OM processes in the OMU to maintain the objects related to the service board.

The OM processes of the BSC6000 include Omulocal and Omucore.Omucore is responsible for alarm handling, configuration and maintenance handling, Bin interfacing, event management, and so on.Omulocal is responsible for the OM of the BTS. It performs the functions such as BTS routine maintenance, BTS software loading, BTS alarm conversion, and BTS test. The LMT communicates with the GBAM/GOMU based on TCP/IP and FTP, and with the M2000 based on UDP.



The management of the OMU is achieved through the coordination of the service processes within the OMU.

The service processes of the OMU are shown in the figure.



Apply for and download the released software package based on the site requirements:

Software Center > Version Software > Wireless Product Line > Single RAN > MBSC > BSC6900

V900R011 > BSC6900 V900R011C00SPC300

Software Name Description

BSC6900V900R011C00SPC300 Dopra Linux_VERTool for creating the USB installation disk for Dopra Linux

BSC6900V900R011C00SPC300 OMU drivers_VER OMU hardware driver and Ethernet card driver

BSC6900V900R011C00SPC300 Offline Tool_VER

1. License offline tools: License parsing tool and ESN generation tool2. Web LMT offline tool: LMT, FTP client, FTP server, alarm forwarding system, performance browser tool, trace viewer, and so on.

BSC6900V900R011C00SPC300 linux_VER Upgrade files of Linux operating system

BSC6900V900R011C00SPC300 windows_VER Upgrade files of Windows operating system. They can be used for the installation of OMU software on the PC.

iManagerM2000_BSC6900GSM_MATCH_CHS_V200R009C00SPC003_VER

M2000 adaption layer of GSM Only

iManagerM2000_BSC6900GU_MATCH_CHS_V200R009C00SPC003_VER

M2000 adaption layer of GSM/UMTS

iManagerM2000_BSC6900UMTS_MATCH_CHS_V200R009C00SPC003_VER

M2000 adaption layer of UMTS Only



Installation and upgrade scenarios: 1. New site

If the delivered OMU has the OMU operating system and OMU applications, you can use the upgrade tool to

upgrade the OMU applications and host software after completing the IP settings.

Documents: OMU Administration Guide > Installing the OMU Applications in Field Commissioning, Upgrade

Guide, Commissioning Guide 2. Troubleshooting in maintenance scenarios

If the OMU operating system or OMU applications need to be reinstalled on the site, there is no need to

change the host software.

Document: OMU Administration Guide > Reinstalling Software on Site 3. Upgrade

It involves version upgrade, patch upgrade, and version plus patch upgrade.

If the target version is V900R011C00SPCX00, the version upgrade needs to be performed; if the target

version is V900R011C00SPCXY0, you should determine whether the baseline version is the same as the

current version. If the baseline version is the same as the current version, a patch needs to be installed.

Otherwise, the current version needs to be upgraded to the baseline version and a patch needs to be

installed. (X indicates the baseline version, and Y indicates a cold patch.)

Document: Upgrade Guide


Software Structure of BSC6900 OMU IP addresses

You can set the OMU IP addresses by logging in to the OMU locally or by creating

the USB installation disk. Document: OMU Administration Guide > Working Principles of the OMU

Note: bond1 and bond1:0, vlan1 and vlan1:0, or fixed IP address and virtual IP

address are not fixedly matched.

IP Address MeaningConfiguration

SuggestionExample

Internal fixed IP address

Used for the communication between the active OMU and the standby OMU in the internal network segment. It is configured when the OMU operating system is installed.

No modification is required for single OMU

ifconfig vlan1

External fixed IP address

Used for the communication between the active OMU and the standby OMU in the external network segment. It is configured when the OMU operating system is installed and floats between the two external Ethernet adapters of the OMU board.

Network planning ifconfig bond1

Internal virtual IP address

Used for the communication between the active OMU and the BSC6900 host boards. It exists on the internal Ethernet adapter team and is added automatically when the OMU applications are started. Not modified generally ifconfig vlan1:0 　

External virtual IP address

Used for the communication between the OMU and the LMT/M2000. It is set during the installation of the OMU applications. For active/standby OMU networking, the external virtual IP address floats between the four Ethernet adapters of the active and standby OMUs.

Network planning ifconfig bond1:0

Backup channel IP address of the active and standby OMUs

Used for the communication between the active OMU and the standby OMU in the backup channel network segment. It is configured when the OMU operating system is installed. No modification is

required for single OMUifconfig bond3

Debugging IP address

IP address used for the local O&M of the OMU operating system. You can not visit the OMU applications by using this IP address. The default value is 192.168.6.50.

Default value generally ifconfig bond2

GatewayGateway to which the external Ethernet adapter of the OMU belongs. It is the route and must on the same network segment as external network IP

Network planning route


Chapter 1 Software Structure of BSC6900

Chapter 2Chapter 2 Installation of LinuxInstallation of Linux


Software



Creating USB Installation Disk

Scenarios of using the USB disk: The initial network configuration is performed on the OMU.

The OMU operating system crashes or the OMU board is replaced.

The Suse Linux or Windows operating system is switched to Dopra Linux.

Preparations before the installation The OMUa/OMUb board, laptop, and BSC6900 software package should be

prepared before the installation on the site.

Creating the USB installation disk For details, see BSC6900 OMU Administration Guide.


Installing LinuxOperation steps:

Insert the USB installation disk to any USB port on the panel of the OMUa board.

Press RESET on the panel of the OMUa board to reset the OMUa board.

Wait 5 to 10 minutes and view the status of the indicators on the panel of the OMUa board.

Item Description

RUN indicator flashes

ALM indicator flashes

ACT indicator flashes

OFFLINE indicator turns off

Installation process

RUN indicator flashes

ALM indicator turns off

ACT indicator turns off

OFFLINE indicator flashes

The installation of the operating system succeeds.

RUN indicator turns off

ALM indicator flashes

ACT indicator turns off

OFFLINE indicator flashes

The installation of the operating system fails.

If failed, check that the first boot sequence of the OMU is USB.

Check that the configuration files and the installation scripts of the

operating system obtained during the creation of the UBS installation

disk are correct. If not, recreate the USB installation disk.


Policy of Using the OMU Operating System

Policy of using the OMU operating system Inventory upgrade: The upgrade can be performed by directly using the

early operating system. For the upgrade from BSC6810 to BSC6900, the original Windows operating

system can be used.

For the upgrade from BSC6000 to BSC6900, the original SUSE Linux operating

system can be used.

Note: The root directory of Dopra Linux is /mbsc, while that of Suse Linux is

/BSC6000/data/mbsc.

Pay attention when getting the files. Later, such difference will be hidden.

New deployment: For the newly deployed product, Dopra Linux is used.

Dopra Linux is the Linux operating system developed by Huawei. It is characterized

by small footprint, easy and fast installation, and high security.




Chapter 3Chapter 3 Installation and Upgrade of BSC6900 Installation and Upgrade of BSC6900

SoftwareSoftware



Installation and Upgrade of BSC6900 Software OMU networking

ETH0 and ETH1: These two Ethernet

adapters are bound as the external

Ethernet adapter team. They are used for

the communication between the OMU and

LMT/M2000. ETH2: It is the OMU debugging Ethernet

adapter, and it can be connected to the

laptop for OMU debugging if necessary. ETH3-UPDATE: It is the backup Ethernet

adapter of the OMU. It is used as the

dedicated backup channel between the

active OMU and standby OMU when the

BSC6900 is configured with two OMUa

boards. ETH4-SCU7 and ETH5-SCU6: These two

Ethernet adapters are bound as the internal

Ethernet adapter team. They are used for

the communication between the OMU and

BSC6900 host boards. Command of viewing the relation of

Ethernet adapters:

/root/eth_alias_omu.sh


Installation and Upgrade of BSC6900 Software OMU networking

The OMU comprises two OMU boards physically, and the two boards work in active/standby mode.

Each OMU board has 6 Ethernet adapters and 4 network segments. External network: The external network comprises two Ethernet adapters, bound as one Ethernet

adapter team. Default IP configuration: 172.121.139.201 (255.255.255.0), configurable. Internal network: The internal network comprises two Ethernet adapters, bound as one Ethernet

adapter team. Default IP configuration: 80.168.3.50 (255.0.0.0), configurable. Backup channel: One Ethernet adapter. Default IP configuration: 192.168.3.50 (255.255.255.0). Debugging network: One Ethernet adapter. Default IP configuration: 192.168.6.50 (255.255.255.0).

Active BAM

Standby BAM

ActiveStandby ActiveStandby

ActiveStandbyActiveStandby

Backup channelDebugging

Ethernet portDebugging

Ethernet port

External network

Internal network



The internal and external networks are further classified into fixed network and

virtual network. Fixed IP address: It is the network IP address configured for the two OMU boards in a fixed

way. Virtual IP address: It is the network IP address configured for the two OMU boards in a

float way.

ActiveOMU

Internal network

Standby OMU

Physical internal network IP address Physical internal network IP address

Physical external network IP address Physical external network IP address

Virtual internal network IP address

Virtual external network IP address


Installing OMU Software

Flowchart of installing OMU software Upload OMU installation package.

Log in to OMU through Putty, and switch to directory

where the installation package is saved.

Check system version and Ethernet adapter

information.

Run chmod +x ./install_bam.sh to obtain the

execution right of install_bam.sh.

Run ./install_bam.sh to start the installation.

For details, see OMU Administration Guide.

Obtain execution right of the commands

Check system version and Ethernet adapter information

Wizard installation

Start

Upload OMU installation package

End


Uploading OMU Installation Package to OMU

Background information The installation package of OMU applications is saved in the directory \Software\setup of the

version software package. It must be uploaded to the directory \mbsc\upgrade of the OMU.

The installation package of OMU applications must be named by version number. That is,

after the installation package of the OMU applications is uploaded to the OMU, the directory

structure should be: \mbsc\upgrade\V900R011C**.

Operation steps: Log in to the OMU using psftp, and switch to the local directory that saves the

version files.

Enter ls /mbsc/upgrade to check whether the installation directory exists in the

OMU. If the directory /mbsc/upgrade does not exist, enter mkdir /mbsc/upgrade

to create the installation directory in the OMU.

Enter cd /mbsc/upgrade to switch to the OMU installation directory.

Enter put -r V900R011C00 to perform the file uploading.


Installing OMU Applications

In Putty, log in to the OMU as user root. Run cat /etc/DL-Release to check the Linux version installed on the OMU. Run /root/eth_alias_omu.sh to check the factory settings of the Ethernet

adapters as follows:Ethernet adapter configuration information (example):

eth0 04,4,0 ETH2

eth1 04,4,1 ETH3-UPDATE

eth2 08,4,0 ETH0

eth3 08,4,1 ETH1

eth4 06,0,0 ETH4-SCU7

eth5 06,0,1 ETH5-SCU6

Run cd /mbsc/upgrade/V900R011C00/install/setup to switch to directory

where the installation package is saved. Run chmod +x ./install_bam.sh to obtain the right of executing

./install_bam.sh.



Enter ./install_bam.sh and press Enter.

Enter the service mode of the product and press Enter to configure the office

information.

Enter the name and press Enter. The GUI is as follows:


Installing OMU Applications Enter the language information and press Enter to configure the internal virtual

IP address.

Enter the internal virtual IP address and press Enter to configure the password

for admin.

Enter the password for admin and press Enter to configure the password for

ftp.



Enter the password for ftp and press Enter.

Select the OMU installation type as planned and press Enter. Enter Y to start the

installation.

When the message “Install OMU succeed!” is displayed, it indicates that the

OMU applications are installed successfully.


Checking the Installation Directory of the OMU Applications Directory structure

If the OMU applications are installed only in the active OMU workspace for the first time, the

directory structure is as shown in Figure 1.

If the OMU applications are installed on both the active workspace and the standby

workspace, the directory structure is as shown in Figure 2. The structures of the version_a

and version_b folders are the same.

Note: “version_a” and “version_b” are the relative folders for saving the data of the active

workspace and standby workspace.


File Folders of the OMU Application Directory


BSC6900 Upgrade Scenarios

Upgrade of BSC6900 software Upgrade methods:

Upgrade tool

M2000: the upgrade tool is activated through the M2000

Upgrade scenarios: upgrade, patch installation, upgrade plus patch installation, upgrade rollback, and

patch rollback

Support for batch upgrade:

In batch upgrade, one client is connected to multiple BSCs at the same time for the upgrade of

multiple BSCs. The client provides the configuration GUI and the GUI of viewing the upgrade progress

for each BSC. The BSC upgrade process in each client does not interfere with each other. In terms of

design, there is no restriction on the maximum number of BSCs during batch upgrade.

The client of the upgrade tool is saved in the directory \remoteclient. The external virtual IP address or

fixed IP address can be used for the upgrade operations. You can perform software uploading, one-key

operations, and troubleshooting easily through the client.

The server of the upgrade tool is saved in the directory upgrade. You can use remoteclient to start the

UpgradeServer.exe process.



Active and standby work areas The active and standby work areas are used for the upgrade and rollback of BSC6900 versions,

enabling fast switch between different versions. The relation of the active and standby work areas is

relative, depending on the current running version. That is, the work area saving the versions files

of the current version is the active work area and the other work area is the standby work area. Pre-upgrade

Before upgrade, the pre-upgrade can be performed. It involves the operations such as checks

before the upgrade and data upgrade.

Data upgrade rule In special data upgrade scenarios, a customized upgrade rule should be defined and configured.

Generally, the default data upgrade rule is used.

The default upgrade rule is identified by the original version number and target version number.

Intermediate version The upgrade can be performed only when there is a corresponding upgrade rule. If an intermediate

version is required, but there is no corresponding upgrade rule, an intermediate version must be

provided. Thus, the old version can be upgraded first to the intermediate versions and then to the

new version. The intermediate version number is in the same format as the old version number.


BSC6900 Upgrade Procedure

NE upgrade

The following upgrade paths are supported now:

Upgrade from BSC6000 R8C01 to BSC6900

Upgrade from BSC6810V2R11 to BSC6900

Upgrade between BSC6900 versions

The upgrade from BSC6000 R8C12 to BSC6900 will

be supported later.

The flowchart at the right is the upgrade procedure. For

details, see BSC6900 Upgrade Guide.At the “Perform upgrade” stage, the active and standby

OMUs should be upgraded together.

1. Install the new version software on the standby work area

of the active and standby OMUs.

2. Switch the active and standby work areas of the active

and standby OMUs by using the upgrade data from the pre-

upgrade stage.

Then, upgrade the host software.

Prepare for upgrade

Add the NEs to be upgraded

Configure basic information about the

upgrade

Perform pre- upgrade

Start

End

Perform upgrade

Verify whether the upgrade is successful

Yes

Perform version rollback

No

Perform post- upgrade processings





Software

Chapter 4Chapter 4 Routine Maintenance of OMURoutine Maintenance of OMU


Introduction to BSC6900 omutool

Method of obtaining the tool After the software version is installed, the omutool is saved in the following

directory: /mbsc/bam/version_a/bin/bam or /mbsc/bam/version_b/bin/bam.

Main functions Setting the working mode of OMU

Start the omutool Putty and log in to OMU. Stop omud and switch the directory to

the one where omutool is saved: cd /mbsc/bam/version_a/bin/bam ./omutool.

Set the working mode of OMU: /omutool dualmode dual

Changing IP address and mask for the OMU Ethernet card Enter the command: /omutool innercard ip mask

Changing password for admin Enter the command: /omutool adminpwd password

For details, see BSC6900 OMU Administration Guide.



Managing the applications of OMU

To operate and maintain the OMU, start a Secure Shell (SSH) terminal (for example,

PuTTY) and log in to the OMU. Query the running status of omud: /etc/rc.d/omud status.

Start omud /etc/rc.d/omud start.

Stop omud /etc/rc.d/omud stop.



Managing the running status of OMU

Log in to the LMT, and then managing the running status of the OMU through MML commands.

Commands of checking the running status of OMU: DSP OMU and DSP OMUMODULE.

Example:



Managing the running status of OMU Command of checking the active/standby area versions of OMU: LST OMUAREA.

Example:



Managing the running status of OMU Commands of querying the hardware information of OMU: DSP OMUHW and DSP

OMUVER.

Example:



Managing the running status of OMU Command of switching over the active and standby OMUs: SWP OMU

Run the command SWP OMUAREA, and set Target OMU to ACTIVE(Active OMU). In

this case, the active and standby working areas on the OMU will be switched over.

Command of resetting OMU: RST OMU Run the command RST OMU to reset the OMU.

If Reset Type is set to SOFT(Soft Reset), only OMU applications are reset, and no

power-off and power-on operations are performed for the OMUa board.

If Reset Type is set to HARD(Hard Reset), power-off and power-on operations are

performed on the OMUa board.


1. Installation scenarios supported by BSC6900

2. BSC6900 OMU networking

3. BSC6900 upgrade procedure

Thank You

www.huawei.com