Bsc6910 Gsm Omu Administration Guide(v100r015c00_05)(PDF)-En

8/19/2019 Bsc6910 Gsm Omu Administration Guide(v100r015c00_05)(PDF)-En

1/154

BSC6910 GSM

V100R015C00

OMU Administration Guide

Issue 05

Date 2014-03-28

HUAWEI TECHNOLOGIES CO., LTD.


2/154

Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written

consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the

customer. All or part of the products, services and features described in this document may not be within the

purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,

and recommendations in this document are provided "AS IS" without warranties, guarantees or representations

of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 05 (2014-03-28) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com/


3/154

About This Document

Overview

This document describes software structure, working principles, application installation, general

tasks of OMU boards.

NOTE

In this document, OMU board (hardware) indicates the combination of the EOMUa board and its operating

system; OMU (logical concept) indicates the OMU board with product software.

Product Version

The following table lists the product versions related to this document.

Product Name Product Version

BSC6910 V100R015C00

Intended Audience

This document is intended for:

l Field engineers

l Shift operators

Organization

1 Changes in BSC6910 GSM OMU Administration Guide

This document describes the changes in BSC6910 GSM OMU Administration Guide.

2 Introduction to OMU

This chapter describes the following information about the OMU: position in the network,

software structure, working mode, OM methods, and safety instructions.

3 Working Principles of the OMU

BSC6910 GSM

OMU Administration Guide About This Document



ii


4/154

This section has the following topics:

4 Initially Commissioning the OMU

This section describes the procedure for initially commissioning the OMU after delivery.

5 Installing OMU Software

If an OMU board is damaged onsite, replace it. If the operating system fails, reinstall it along

with the product software.

6 Operating and Maintaining the OMU

This section describes how to perform operation and maintenance on the OMU after product

software are installed. To perform this task, log in to the OMU remotely or run MML commands.

7 Appendix: OMU-Related Operations

This section describes basic OMU-related operations, including logging into the OMU, logging

out of the OMU, and starting OMU tools.

8 Appendix: OMU-Related Software

This section describes how to obtain and use the OMU-related software, including the psftp

software and PuTTY software. The OMU-related software is used to install the product software

and perform operation and maintenance on the OMU.

9 Appendix: OMU-Related Information Tables

This section describes the tables in which the OMU information is recorded during routine

operation and maintenance on the OMU.

10 Appendix: Troubleshooting

This chapter describes OMU faults and troubleshooting methods.

11 Appendix: Security FAQ

This section describes how to improve the security of the BSC6910.

12 Appendix: Special OMU Networking Scenarios

This section describes special scenarios associated with connecting the OMU to peripheral

equipment.

Conventions

Symbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.

BSC6910 GSM




iii


5/154

Symbol Description

Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.


avoided, may result in minor or moderate injury.


avoided, could result in equipment damage, data loss,

performance deterioration, or unanticipated results.

NOTICE is used to address practices not related to personal

injury.

Calls attention to important information, best practices and

tips.

NOTE is used to address information not related to personal

injury, equipment damage, and environment deterioration.

General Conventions

The general conventions that may be found in this document are defined as follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in

Courier New.

Command Conventions

The command conventions that may be found in this document are defined as follows.


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.

BSC6910 GSM




iv


6/154


[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all

items can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.

GUI Conventions

The GUI conventions that may be found in this document are defined as follows.


Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK .

> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.

Keyboard Operations

The keyboard operations that may be found in this document are defined as follows.

Format Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt

+A means the three keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means

the two keys should be pressed in turn.

Mouse Operations

The mouse operations that may be found in this document are defined as follows.

Action Description

Click Select and release the primary mouse button without moving

the pointer.

BSC6910 GSM




v


7/154

Action Description

Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.

Drag Press and hold the primary mouse button and move the

pointer to a certain position.

BSC6910 GSM




vi


8/154

Contents

About This Document.....................................................................................................................ii

1 Changes in BSC6910 GSM OMU Administration Guide......................................................1

2 Introduction to OMU....................................................................................................................4

2.1 Position of the OMU in the BSC6910............................................................................................................................5

2.2 OMU Components..........................................................................................................................................................5

2.3 OMU Working Mode.....................................................................................................................................................9

2.4 OMU Installation and Maintenance Methods................................................................................................................9

2.5 OMU Saf ety Information..............................................................................................................................................10

3 Working Principles of the OMU..............................................................................................11

3.1 OMU Ethernet Adapter Configuration.........................................................................................................................12

3.2 OMU IP Address Plan..................................................................................................................................................13

3.3 OMU Networking Principle.........................................................................................................................................21

3.4 Heartbeat Detection on Active and Standby OMUs.....................................................................................................26

3.5 Synchronization Between Active and Standby OMUs.................................................................................................26

3.6 Switchover Between Active and Standby OMUs.........................................................................................................27

4 Initially Commissioning the OMU..........................................................................................29

4.1 Setting the Link Mode for External OMU Ethernet Adapters......................................................................................31

4.2 Commissioning the OMU.............................................................................................................................................32

5 Installing OMU Software..........................................................................................................38

5.1 Preparations..................................................................................................................................................................39

5.2 Optional: Installing Product Software by Using a USB Storage Device.....................................................................40

5.3 Optional: Manually Installing the Product Software....................................................................................................43

5.3.1 Obtaining Information About OMU Software Installation.......................................................................................43

5.3.2 Uploading the OMU Application Installation Package to the OMU.........................................................................43

5.3.3 Installing the Product Software in the Active Workspace.........................................................................................46

5.3.4 Checking the Installation Directory of Product Software..........................................................................................49

6 Operating and Maintaining the OMU....................................................................................55

6.1 Querying the Mapping Between Ethernet Adapters.....................................................................................................57

6.2 Querying the Configuration of the OMU Ethernet Adapters.......................................................................................57

6.3 Querying Occupied OMU Ports...................................................................................................................................59

BSC6910 GSM

OMU Administration Guide Contents



vii


9/154

6.4 Querying the Link Mode of the External OMU Network Adapters.............................................................................59

6.5 Checking the Version of the Operating System...........................................................................................................60

6.6 Changing the Administrator Password of the Operating System.................................................................................60

6.7 Setting RAID 1 on OMU Hard Disks...........................................................................................................................61

6.8 Adjusting OMU Slots...................................................................................................................................................64

6.9 Transferring OMU Files to a Local PC........................................................................................................................66

6.10 Managing the Operating Status of the OMU..............................................................................................................69

6.10.1 Querying the OMU Operating Status......................................................................................................................69

6.10.2 Querying the Information About an OMU Board...................................................................................................69

6.10.3 Querying the Version of the Active/Standby OMU Workspaces............................................................................70

6.10.4 Querying the Status of Data Synchronization Between the Active and Standby OMUs........................................71

6.10.5 Checking the Data Consistency Between the Active OMU and the Standby OMU...............................................71

6.10.6 Changing the Time Zone and OMU Time ..............................................................................................................72

6.10.7 Configuring Data Rates of Accessing the OMU Hard Disks..................................................................................72

6.10.8 Forcibly Switching Over the Active and Standby OMUs.......................................................................................73

6.10.9 Resetting the OMU..................................................................................................................................................74

6.11 Managing the Product Software.................................................................................................................................75

6.11.1 Querying Operating Status of the omud..................................................................................................................75

6.11.2 Starting the omud.....................................................................................................................................................75

6.11.3 Stop the omud..........................................................................................................................................................76

6.11.4 Uninstalling the Product Software...........................................................................................................................76

6.12 Backing Up and Restoring Data.................................................................................................................................77

6.12.1 Backing Up System Data.........................................................................................................................................78

6.12.2 Restoring System Data............................................................................................................................................79

6.13 Setting OMU System Parameters...............................................................................................................................81

6.13.1 Setting the OMU Working Mode............................................................................................................................81

6.13.2 Changing IP Addresses and Subnet Masks of OMU Ethernet Adapters.................................................................85

6.13.3 Changing Users' Passwords.....................................................................................................................................88

6.13.4 Changing the Computer Name................................................................................................................................90

7 Appendix: OMU-Related Operations......................................................................................91

7.1 Starting the omu_backup_linker Tool..........................................................................................................................927.2 Starting the omutool.....................................................................................................................................................92

7.3 Logging In to the OMU................................................................................................................................................93

7.4 Logging Out of the OMU.............................................................................................................................................94

8 Appendix: OMU-Related Software..........................................................................................95

8.1 psftp Software...............................................................................................................................................................96

8.2 PuTTY Software...........................................................................................................................................................97

8.3 Dopra_Linux_USB Disk Tool......................................................................................................................................99

9 Appendix: OMU-Related Information Tables.....................................................................119

9.1 Information Records of OMU Software Installation..................................................................................................120

BSC6910 GSM




viii


10/154

9.2 Checklist for the OMU Software Factory Settings.....................................................................................................121

9.3 OMU Directory Operation Rights List.......................................................................................................................123

9.4 OMU Folder Size List................................................................................................................................................124

9.5 Enabled Ports on the OMU.........................................................................................................................................127

10 Appendix: Troubleshooting..................................................................................................128

10.1 Restoring OS by the Using USB Storage Device.....................................................................................................129

11 Appendix: Security FAQ........................................................................................................131

11.1 Disabling root user login with SSH..........................................................................................................................132

11.2 Disabling OMU route forwarding............................................................................................................................135

11.3 Configuring the Function of Recording OMU OS Accessing Information in Real Time........................................137

11.4 Enabling Function of Checking OS File Integrity....................................................................................................138

11.5 Enhancing Security of Time Synchronization with NTP.........................................................................................139

12 Appendix: Special OMU Networking Scenarios.............................................................. 141

12.1 Scenario of Connecting the OMU and VNP............................................................................................................142

BSC6910 GSM




ix


11/154

1 Changes in BSC6910 GSM OMUAdministration Guide

This document describes the changes in BSC6910 GSM OMU Administration Guide.

05 (2014-03-28)

This is the fifth commercial release for V100R015C00.

Compared with 04 (2014-01-20), this issue does not include any new information.

Compared with 04 (2014-01-20), this issue does not incorporate any changes.

Compared with 04 (2014-01-20), this issue excludes the following topics:

Content Description

Active/Standby Workspaces of the OMU

Switching Over the Active/Standby OMU

Workspaces

Deleted this content because this function has

been incorporated into the upgrade tool and

is no longer independently used.

04 (2014-01-20)

This is the fourth commercial release for V100R015C00.


Compared with 03 (2013-11-15), this issue incorporates the following changes.

Content Description

6.13.3 Changing Users' Passwords Changed the background information.

Updated description of changing users'

passwords on both the active and standby

OMUs.

BSC6910 GSM

OMU Administration Guide 1 Changes in BSC6910 GSM OMU Administration Guide



1


12/154

Compared with 03 (2013-11-15), this issue does not exclude any topics.

03 (2013-11-15)

This is the third commercial release for V100R015C00.



Content Description

7.2 Starting the omutool The use right of the omutool is changed.

9.4 OMU Folder Size List The storage specifications of some logs are

changed.


02 (2013-06-25)

This is the second commercial release for V100R015C00.



Content Description

5.3.3 Installing the Product Software in the

Active Workspace

Changed the password information of User

admin and FtpUsr user. The special character

of the password is modified.


01 (2013-05-04)This is the first commercial release for V100R015C00.

Compared with Draft A (2013-02-27), this issue does not include any new information.

Compared with Draft A (2013-02-27), this issue incorporates the following changes.

Content Description

11.5 Enhancing Security of Time

Synchronization with NTP

Changed the background information. When

the OMU works as an NTP server, NTP

packets are transmitted in plaintext on the

intranet.

BSC6910 GSM




2


13/154

Content Description

3.2 OMU IP Address Plan Added description of changing the fixed and

virtual internal IP addresses.

9.4 OMU Folder Size List Changed the OMU folder size list.

4 Initially Commissioning the OMU Added a flowchart for commissioning the

OMU.

4.2 Commissioning the OMU Classified procedures for commissioning the

OMU.

Compared with Draft A (2013-02-27), this issue does not exclude any topics.

Draft A (2013-02-27)

This is the Draft A release of V100R015C00.

BSC6910 GSM




3


14/154

2 Introduction to OMUAbout This Chapter

This chapter describes the following information about the OMU: position in the network,

software structure, working mode, OM methods, and safety instructions.

2.1 Position of the OMU in the BSC6910

This section describes the components of the BSC6910 operation and maintenance (O&M)

network and the position of the OMU in the OM network.

2.2 OMU Components

This section describes the OMU components and dependencies of those components on eachother.

2.3 OMU Working Mode

The OMU works in independent or active/standby mode.

2.4 OMU Installation and Maintenance Methods

This section describes how to perform installation and maintenance on the OMU in different

scenarios.

2.5 OMU Safety Information

This section describes the safety information related to the OMU operation.

BSC6910 GSM

OMU Administration Guide 2 Introduction to OMU



4


15/154

2.1 Position of the OMU in the BSC6910

This section describes the components of the BSC6910 operation and maintenance (O&M)network and the position of the OMU in the OM network.

The BSC6910 O&M network is composed of the O&M terminal (LMT or M2000), OMU, SCU,

and O&M modules on the host boards. The O&M terminal communicates with the BSC6910

host boards by using the OMU.

Figure 2-1 shows the position of the OMU in the BSC6910 O&M network.

Figure 2-1 Position of the OMU in the BSC6910 O&M Network

As shown in Figure 2-1, the external network is the logical network between the OMU and the

O&M terminal (LMT/M2000), and the internal network is the logical network between the OMU

and the BSC6910 host boards.

2.2 OMU Components

This section describes the OMU components and dependencies of those components on each

other.

The OMU consists of the OMU Hardware, OMU operating system and product software, as

shown in Figure 2-2.

l OMU Hardware

The OMU hardware is monitoring its software in real time to avoid suspension of product

software.

BSC6910 GSM




5


16/154

l OMU Operating System

The OMU operating system, installed on the boards, can be the Dopra Linux.

l OMU Application Software

The OMU application software runs on the bottom-level operating system and providesvarious service processes.

Figure 2-2 OMU Components

NOTE

l The yellow blocks in Figure 2-2 indicate OMU service monitoring entities, the blue blocks indicate

OMU service processes, the white blocks indicate OMU peripheral devices.

l The arrows shown in Figure 2-2 indicate communication between modules.

OMU Service Processes

The OMU is managed by OMU services processes. OMU service processes are logically

independent of one another. When one process fails, other processes continue to run properly.

The OMU can detect a process that stops abnormally and restart it quickly.

Table 2-1 shows the OMU service processes and the functions.

BSC6910 GSM




6


17/154

Table 2-1 OMU Service Processes

Service Processes Functions

Communication Module

(ems_gate)

The communication module receives messages from the

Element Management System (EMS) or Local MaintenanceTerminal (LMT), converts the messages into frames for

internal communication in the OMU, and then sends the

messages to the authentication module. Receives messages

from the OMU modules, interprets the messages, and then

sends the messages to the EMS or LMT.

The communication module receives, interprets, and sends

messages between the VNP and maintenance module.

Authentication Module

(authority)

The authentication module performs functions such as

authority management, log management, and command

resolution.

Network Management Agent

Module (ems_agent)

The network management agent module performs functions

such as batch command processing, and scheduled task

management.

Configuration Module

(configure)

The configuration module performs the functions of data

configuration and management for the BSC6910 host, such

as configuring data effective and ineffective modes,

formatting the data files loaded by the host, and checking data

consistency.

Maintenance Module

(maintain)

The maintenance module enables the OMU to query the

operating status of objects such as the BSC6910 hosthardware, physical/logical links, and channels. It also

enables the BAM to test and maintain objects.

Alarm Module (alarm) The alarm module handles alarms. It controls the output

mode and classification of alarms, and shields alarms.

Performance Module (stat) The performance module collects, stores, and computes the

performance measurement data of the host, and then reports

the data to the M2000.

Software Management

Module (software)

The software management module performs functions such

as BOOTP service for the OMU board, OMU softwaremanagement, OMU active/standby workspace management,

file synchronization between the active OMU and the

standby OMU, and version upgrade management.

OMU Management Module

(omu_manager)

The OMU management module monitors the OMU hardware

and software.

BSC6910 GSM




7


18/154

Service Processes Functions

Time Server Module (sntp) The server module performs the functions as follows:

l The time server provides time synchronization for

BSC6900 boards and the base station.l The time client synchronizes with the upper-level time

server and provides the reference time.

FTP Module (ftp_server) The FTP module serves as an FTP server and provides the

file transfer function for the host boards, LMT, and EMS.

Exchange Module

(host_gate)

The exchange module enables the communication between

the OMU processes and the host.

Base Station Maintenance

Module (btsom)

The base station maintenance module performs the functions

of alarm management, performance management, software

management, and routine maintenance for the base station.

Fault Diagnosis Module (cfa) The fault diagnosis module collects end-to-end link fault

information, periodically diagnoses faulty nodes, and

performs self-healing.

OMU Log Management

Module (debug_log)

The OMU log management module records and regularly

cleans up OMU logs.

LMT Module (weblmt) The LMT module performs message tracing, performance

monitoring, and device maintenance. It also provides an

interface for issuing MML commands.

Data Exportation Module(cfg_mirror)

The data exportation module exports the configuration data.

OMU Service Monitoring Entities

The product software perform monitoring at three levels:

l Level 1 is the hardware-level monitoring in which the watchdog monitors the omud.

A watchdog is a timer used to monitor the omud. Once the omud is abnormal and cause

the watchdog timer to overflow, the OMU will be reset automatically.l Level 2 is the system-level monitoring in which the omud monitors the monitor.

As a service entity, the omud is registered in the operating system and automatically starts

when the operating system starts. The monitor is started when the omud starts and the omud

monitors the monitor.

l Level 3 is the application-level monitoring in which the monitor monitors service processes.

The monitor monitors the service processes in real time.

When a service process, the monitor, or the omud is faulty, three-level monitoring mechanism

ensures that the faulty service process, monitor, or omud can be restarted.

BSC6910 GSM




8


19/154

2.3 OMU Working Mode

The OMU works in independent or active/standby mode.

Independent Mode

When the BSC6910 is configured with one OMU board or one GBAM server, the OMU works

in independent mode.

In this mode, if the OMU is faulty, operation and maintenance (OM) cannot be performed on

the BSC6910. This reduces system reliability.

Active/Standby Mode

When the BSC6910 is configured with two OMU boards, the OMU works in active/standbymode.

In this mode, the OMU board working in active mode is called the active OMU board, and the

OMU board working in standby mode is called the standby OMU board. The active and standby

OMU boards must be of the same type. Installing different types of OMU boards is prohibited.

When the BSC6910 is configured in active/standby OMU mode, the OMU can operate properly

with high reliability. Specifically, if a hardware or software fault occurs on the active OMU, the

standby OMU is automatically switched over to the active state and provides services.

NOTE

l The OMU working mode is set during the OMU application installation.

l After the product software are installed, run the MML command DSP OMU to query the OMU working

mode, and check the value for the Operational state parameter in the command output to check the OMU

working mode. If the value is Active normal or Standby normal, the OMU works in active/standby mode.

If the value is Normal, the OMU works in independent mode.

2.4 OMU Installation and Maintenance Methods

This section describes how to perform installation and maintenance on the OMU in different

scenarios.

Scenario: Installing Product Software Before Onsite Commissioning After installing the BSC6910 hardware, install product software before commissioning the

OMU. For details about this scenario, see 4 Initially Commissioning the OMU.

Scenario: Reinstalling the OMU Operating System Onsite

If the operating system crashes onsite, reinstall the OMU operating system as well as product

software, and reconfigure the OMU. For details, see 5.2 Optional: Installing Product Software

by Using a USB Storage Device.

When product software are abnormal and you do not want to change the OMU operating system

configurations, you must manually reinstall the product software. For details about this scenario,

see 5.3 Optional: Manually Installing the Product Software.

BSC6910 GSM




9


20/154

Scenario: Performing Routine OM on the OMU

Query and set some OMU information by using MML commands or operating system command

lines. For details about this scenario, see 6 Operating and Maintaining the OMU.

2.5 OMU Safety Information

This section describes the safety information related to the OMU operation.

l To ensure normal operation of the OMU, do not create or delete directories, change

directory attributes, delete backup files, modify system files, change system file attributes,

disable Ethernet adapters, modify configuration files for Ethernet adapters, or configure

routes.

l Install and run only the operating system software (including necessary drivers and

components) and product software on the OMU.

l The operation information and faults of the BSC6910 are recorded on the OMU. Therefore,to timely and accurately locate and rectify faults, do not delete any log file from the OMU.

BSC6910 GSM




10


21/154

3 Working Principles of the OMUAbout This Chapter

This section has the following topics:

3.1 OMU Ethernet Adapter Configuration

This section describes the configuration of OMU Ethernet adapters.

3.2 OMU IP Address Plan

The OMU Ethernet adapters must follow the IP address planning principles to meet the

communication requirements of the operation and maintenance (O&M) network.

3.3 OMU Networking PrincipleThe internal Ethernet adapters of the OMU are connected to the SCUs in the MPS, and the

external Ethernet adapters of the OMU are connected to the operation and maintenance (O&M)

terminals. In this way, the OMU fulfills the communication between the BSC6910 and the O&M

terminals.

3.4 Heartbeat Detection on Active and Standby OMUs

In active/standby OMU mode, heartbeat detection is performed on active and standby OMUs to

check whether the active and standby OMUs are working properly.

3.5 Synchronization Between Active and Standby OMUs

In active/standby mode, the synchronization between the active and standby OMUs consists of

data synchronization, file synchronization, and time synchronization.

3.6 Switchover Between Active and Standby OMUs

For OMUs working in active/standby mode, there are four types of switchover: manual

switchover, fault-triggered switchover, failover, and self-healing switchover.

BSC6910 GSM

OMU Administration Guide 3 Working Principles of the OMU



11


22/154

3.1 OMU Ethernet Adapter Configuration

This section describes the configuration of OMU Ethernet adapters.

The six Ethernet adapters on an EOMUa board are:

l F_ETH0 and F_ETH1: These two Ethernet adapters are bound as an external Ethernet

adapter team. This Ethernet adapter team is used for communication in the external network.

That is, the communication between the OMU and the LMT/M2000. This external Ethernet

adapter team is also called bond1/bond1:0.

l F_DBG: bond2, a debugging Ethernet adapter, is connected to a portable PC for OMU

debugging if required.

l B_UPDATE: This is a backup channel Ethernet adapter used for the dedicated backup

channel between the active and standby OMUs when the BSC6910 is configured with two

EOMUa boards. This backup Ethernet adapter is also called bond3.l B_ETH0 and B_ETH1: The two Ethernet adapters are bound as an internal Ethernet adapter

team. This Ethernet adapter team is used for communication in the internal network. That

is, the communication between the OMU and BSC6910 host boards. This Ethernet adapter

team is also called bond0 (vlan1/vlan1:0).

Figure 3-1 shows the binding relationship between Ethernet adapters on the EOMUa board.

Figure 3-1 Binding relationship between Ethernet adapters on the EOMUa board

BSC6910 GSM




12


23/154

NOTE

l F_ETH0, F_ETH1, and F_DBG are connected to the external network by using the Ethernet ports on

the panel of the EOMUa board. B_ETH0, B_ETH1, and B_UPDATE are connected to the the external

network by using the Ethernet ports which are on the backplane of the Main Processing Subrack (MPS)

and are invisible on the panel of the EOMUa board.l One of bond1 and bond1:0 is reserved for the fixed external IP address, and the other is reserved for

the virtual external IP address.

l B_ETH0 and B_ETH1 are bound as an internal adapter team. This internal adapter team is also called

bond0. To enable communication between the OMU and the SCU, a VLAN whose ID is 1 needs to be

established on bond0. vlan1 and vlan1:0 are reserved for the internal fixed IP address and the internal

virtual IP address, respectively.

3.2 OMU IP Address Plan

The OMU Ethernet adapters must follow the IP address planning principles to meet the

communication requirements of the operation and maintenance (O&M) network.

Definitions of OMU IP addresses

The OMU IP addresses include fixed internal IP address, fixed external IP address, virtual

internal IP address, virtual external IP address, and commissioning IP address. If the

BSC6910 is configured with two OMU boards, the OMU IP addresses also include the IP address

of the backup channel between the active and standby OMU boards.

Table 3-1 provides definitions of different OMU IP addresses.

Table 3-1 Definitions of OMU IP addresses

IP Address Definition and Function Corresponding EthernetAdapters on theEOMUa Board

Fixed external

IP address

IP address for the communication between peripheral

devices (for example, LMT/M2000) and the OMU. A

user can log in to the LMT and OMU by using the

fixed external IP address.

The fixed external IP address is automatically

configured on the OMU external Ethernet adapter

team when the OMU operating system is being

installed.

If active and standby OMUs are switched over when

a peripheral device communicates with the active

OMU by using the fixed external IP address, the

communication between the peripheral device and the

active OMU will be interrupted.

l F_ETH0

l F_ETH1

BSC6910 GSM




13


24/154


Virtual

external IP

address

IP address for the communication between peripheral

devices (for example, LMT/M2000) and the OMU. A

user can log in to the LMT and OMU by using the

fixed external IP address.

The virtual external IP address is configured on the

Ethernet adapter team of the active OMU when the

product software are installed. It takes effect after the

product software are started.

If active and standby OMUs are switched over when

a peripheral device communicates with the OMUs by

using the virtual external IP address, thecommunication between the peripheral device and the

OMU will be interrupted for a while and then be

recovered. During this process, the virtual external IP

address of the original standby OMU becomes

effective, and the virtual external IP address of the

original active OMU becomes ineffective.

l F_ETH0

l F_ETH1

Fixed internal

IP address

IP address for the communication between the active

and standby OMUs on the internal network segment

(network on which information is exchanged by using

the SCU board).

The fixed internal IP address is automatically

configured on the OMU internal Ethernet adapter team

when the OMU operating system is installed.

The fixed internal IP address is not used for the

communication between the OMU and the BSC6910

host boards.

l B_ETH0

l B_ETH1

Virtual

internal IP

address


OMU and the BSC6910 host boards.

The virtual internal IP address is configured on the

internal Ethernet adapter team of the active OMU. It

takes effect after the product software are started.

The communication between the BSC6910 host

boards and the OMU are not interrupted even during

the switchover of the active and standby OMUs.

l B_ETH0

l B_ETH1

BSC6910 GSM




14


25/154


IP address of

the backup

channel

between active

and standby

OMU boards


and standby OMUs on the backup channel network

segment (network on which information is exchanged

by using an Ethernet cable).

The IP address of the backup channel between the

active and standby OMUs is automatically configured

on the standby OMU Ethernet adapter when the OMU

operating system is being installed.

The active and standby OMUs communicates by using

the backup channel IP address between the active and

standby OMUs. Any fault on a host board does notaffect the communication between the active and

standby OMUs.

l B_UPDATE

Commissionin

g IP address

IP address for operating and maintaining the OMU

when a PC is connected to the commissioning Ethernet

port of the OMU by using an Ethernet cable at the local

end.

The commissioning Ethernet port and the ETH0 or

ETH1 port cannot be simultaneously connected to the

external network. Otherwise, the OMU IP Address

Conflict alarm is generated.

l F_DBG

Definition of Onsite Network

The network connecting the OMU external Ethernet adapters and the LMT or M2000 is defined

as an external network or an onsite network. If the OMU external Ethernet adapters are connected

to the LMT or M2000 routers, then the network connecting the OMU external Ethernet adapters

and the first router (gateway) is defined as an onsite network. Figure 3-2 shows an onsite

network.

lThe network between the OMU internal Ethernet adapters and host boards is defined as aninternal network. The OMU communicates with the base station by using the host boards.

l The network between the OMU external Ethernet adapters and the LMT or M2000 is

defined as an external network. The OMU is connected to the LMT or M2000 either directly

or by using multiple routers (gateways).

BSC6910 GSM




15


26/154

Figure 3-2 Onsite network

Consider the following principles when configuring IP addresses onsite:

l If IP routes configured for the OMU are configured (by running the ADD OMUIPRT

command), ensure that the Forward Route Address and Destination Network Addressto the LMT/M2000 are not located in the same network segment as the virtual internal IP

address, fixed internal IP address, backup channel IP address, and debugging IP address.

IP Addresses to Be Changed Onsite

IP addresses are configured before an OMU is delivered. For more information, see 9.2 Checklist

for the OMU Software Factory Settings. The default IP addresses may fail to meet the

requirements of onsite network planning. Therefore, you are required to reconfigure some of the

OMU IP addresses.

Generally, the fixed and virtual external IP addresses need to be reconfigured according to the

customer network planning. To reconfigure the IP addresses, do as follows:

l If single OMU is configured, one fixed and one virtual external IP addresses of the OMU

must be on the same network segment.

l If active and standby OMUs are configured, the fixed external IP addresses of the active

and standby OMUs, the virtual external IP address of the active and standby OMUs (the

virtual external IP address of the active OMU and that of the standby OMU are the same)

must be configured on the same network segment.

If the fixed and virtual internal IP addresses need to be changed, do as follows:

l If single OMU is configured, one fixed and one virtual internal IP addresses of the OMU

must be on the same network segment. And their subnet masks are fixed to 255.0.0.0.l If active and standby OMUs are configured, the fixed internal IP addresses of the active

and standby OMUs, the virtual internal IP address of the active and standby OMUs (the

virtual internal IP address of the active OMU and that of the standby OMU are the same)

must be configured on the same network segment. The subnet masks of the IP addresses

are fixed to 255.0.0.0.

Table 3-2 describes the planning principles of OMU IP addresses.

BSC6910 GSM




16


27/154


28/154

Table 3-3 Onsite check of OMU IP addresses

IP Address Check Principle

Fixed internal IP

address

The fixed internal IP address of the active OMU must be set to X.168.3.50.

The default IP address is 80.168.3.50 (255.0.0.0).The fixed internal IP address of the standby OMU must be set to X.

168.3.60. The default IP address is 80.168.3.60 (255.0.0.0).

Check principle:

1. The network segment in which the fixed internal IP address is located

cannot conflict with the onsite network segment. If they conflict, you

must change the fixed internal IP address.

2. Only the network segment where the fixed internal IP address is

located can be changed. For example, 80.168.3.50 can be changed to

90.168.3.50.

3. If active and standby OMUs are configured, the fixed internal IPaddresses of the active and standby OMUs must be different and on

the same network segment.

4. If an independent OMU is configured and the network segment where

the fixed internal IP address is located does not conflict with the onsite

network segment, reserve the default fixed internal IP address.

5. The subnet mask of the fixed internal IP address must be 255.0.0.0.

Virtual internal

IP address

1. The virtual internal IP address must be located in the same subnet as

the fixed internal IP addresses of the active and standby OMUs. This

subnet is called the OMU internal network segment. In addition, the

virtual internal IP address cannot be identical with other IP addressesin the subnet and it should be configured as X.168.3.40 in which X

must be the same as the network segment where the fixed internal IP

address is located.

For example, if active and standby OMUs are configured, the fixed

internal IP address of the active OMU is 80.168.3.50, and that of the

standby OMU is 80.168.3.60, the virtual internal IP address can be

configured as 80.168.3.40.

2. For example, if an independent OMU is configured and the fixed

internal IP address of the OMU is 80.168.3.50, the virtual internal IP

address can be configured as 80.168.3.40.

3. The subnet mask of the virtual internal IP address must be 255.0.0.0

BSC6910 GSM




18


29/154


30/154

Table 3-4 Impact of OMU IP address changes

IP Address Change Impact

Fixed external IP

address

After the fixed external IP address is changed, the device connected to the

external Ethernet port can access the OMU only by using the new fixedexternal IP address.

The fixed external IP address can be changed remotely and takes effect

immediately after it is changed.

Virtual external

IP address

After the virtual external IP address is changed, the device connected to

the OMU by using the original IP address can access the OMU only by

using the new virtual external IP address.

The virtual external IP address can be changed remotely and takes effect

immediately after it is changed.

Fixed internal IP

address

The fixed internal IP address and the IP addresses of the BSC6910 host

boards have been planned. Therefore, only the network segment on which

the fixed internal IP address is located can be changed so that the fixed

internal IP address is not identical with the IP addresses of the BSC6910

host boards.

If the network segment where the fixed internal IP address is located is

changed, the BSC6910 subnet number must be changed as well.

Otherwise, the communication between the OMU and the BSC6910 host

boards will be interrupted.

The fixed internal IP address is usually changed when the OMU is

commissioned onsite to avoid negative effects caused by frequent resets

of the BSC6910 during daily maintenance.The fixed internal IP address can be changed remotely. After it is changed,

you must reset the BSC6910 at the local end.

Virtual internal

IP address

The virtual and fixed internal IP addresses must be changed at the same

time.

After the virtual internal IP address is changed, reset the BSC6910 so that

the communication between the OMU and the BSC6910 host boards can

be re-established.

The virtual internal IP address is usually changed when the OMU is

commissioned onsite to avoid negative effects caused by frequent resets

of the BSC6910 during daily maintenance.The virtual internal IP address can be changed remotely. After it is

changed, you must reset the BSC6910 at the local end.

IP address of the

backup channel

between active

and standby

OMU boards

After the IP address of the backup channel between the active and standby

OMUs is changed, reset the OMUs so that the communication between

the active and standby OMUs can be re-established.

The IP address of the backup channel between the active and standby

OMUs can be changed remotely and takes effect immediately after it is

changed.

BSC6910 GSM




20


31/154

IP Address Change Impact

Commissioning

IP address

After the commissioning IP address is changed, the device connected to

the commissioning Ethernet port cannot access the OMU. The OMU can

be accessed only by using the new commissioning IP address.The commissioning IP address must be changed by connecting the

commissioning Ethernet port. The new IP address takes effect

immediately after the change.

NOTE

l The fixed internal and external IP addresses are bound to the active and standby OMUs, and the virtual

internal and external IP addresses are bound to the active OMU. For example, after the switchover of the

active and standby OMUs, the fixed internal and external IP addresses of the original active and standby

OMUs remain the same while the virtual internal and external IP addresses of the original active OMU become the virtual internal and external IP addresses of the original standby OMU. There is no virtual internal

or external IP addresses for the original active OMU.

l Each pair of the following IP addresses must be on the same network segment: fixed and virtual internal IP

addresses, fixed and virtual external IP addresses, IP addresses of the channel between the active and standby

OMUs on the active OMU and standby OMU, commissioning IP address of the active and standby OMU.

The network segments of these pairs of IP addresses cannot conflict with each other. Additionally, the IP

addresses on a network segment cannot conflict, either.

l Record the IP addresses in 9.1 Information Records of OMU Software Installation.

l The next hop IP address of the M2000 route must be the virtual external IP address of the OMU.

l For principles for configuring the BSC local IP address, see Scenario of Connecting the OMU and VNP.

3.3 OMU Networking Principle

The internal Ethernet adapters of the OMU are connected to the SCUs in the MPS, and the

external Ethernet adapters of the OMU are connected to the operation and maintenance (O&M)

terminals. In this way, the OMU fulfills the communication between the BSC6910 and the O&M

terminals.

Independent EOMUa Networking Principle

Figure 3-3, and Figure 3-4 show the networking topology in single-EOMUa mode.

BSC6910 GSM




21


32/154

Figure 3-3 Independent-EOMUa (with a single LAN switch)

BSC6910 GSM




22


33/154

Figure 3-4 Independent EOMUa networking topology (with two LAN switches)

The two internal Ethernet adapters B_ETH0 and B_ETH1 of the EOMUa board are connected

to the active and standby SCUs in the MPS by using the backplane, respectively.

The two external Ethernet adapters F_ETH0 and F_ETH1 of the EOMUa board are connected

to the O&M terminals by using network equipment such as a hub, LAN switch, or router. In this

way, the OMU fulfills the communication between the BSC6910 and the O&M terminals.

As shown in Figure 3-4, the two external Ethernet ports of the EOMUa board are connected to

the two LAN switches, respectively, which improves network reliability. In this network

topology, external Ethernet ports on the OMU, ports on the LAN switches for the connection

with the OMU, and the ports on the LAN switches for the connection between LAN switches

must be in the same local area network (LAN).

BSC6910 GSM




23


34/154

The Ethernet port marked in blue in Figure 3-3 and Figure 3-4 must be enabled with the

Spanning Tree Protocol (STP) function to prevent network storms.

Active/standby EOMUa Networking Principle

Figure 3-5, and Figure 3-6 show the network topology in dual-EOMUa mode.

Figure 3-5 Active/standby EOMUa (with a single LAN switch)

BSC6910 GSM




24


35/154

Figure 3-6 Active/standby EOMUa (with two LAN switches)

The two internal Ethernet adapters B_ETH0 and B_ETH1 of the EOMUa board are connected

to the active and standby SCUs in the MPS by using the backplane, respectively.

The two external Ethernet adapters F_ETH0 and F_ETH1 of the EOMUa board are connected

to the O&M terminals by using network equipment such as a hub, LAN switch, or router. In this

way, the OMU fulfills the communication between the BSC6910 and the O&M terminals.

The B_UPDATE Ethernet adapters of the active and standby EOMUa boards are connected by

using the backplane to fulfill the data synchronization and software update between the active

and standby OMUs.

As shown in Figure 3-6, the two external Ethernet ports of the active and standby OMUs are

connected to the two LAN switches, respectively, which improves network reliability. In this

BSC6910 GSM




25


36/154

network topology, external Ethernet ports on the OMU, ports on the LAN switches for the

connection with the OMU, and the ports on the LAN switches for the connection between LAN

switches must be in the same local area network (LAN).

The Ethernet port marked in blue in Figure 3-5 and Figure 3-6 must be enabled with the

Spanning Tree Protocol (STP) function to prevent network storms.

3.4 Heartbeat Detection on Active and Standby OMUs

In active/standby OMU mode, heartbeat detection is performed on active and standby OMUs to

check whether the active and standby OMUs are working properly.

Heartbeat refers to response messages between active and standby OMUs. In active/standby

OMU mode, active and standby OMUs send heartbeat messages to each other to ensure that they

work properly and the network connection is normal.

The principle of heartbeat detection is: The active and standby OMUs send status messages to

each other and check the messages. Based on the active/standby policy, they determine whether

they are operating as the active or standby OMU. In addition, they decide whether to perform a

switchover after negotiation. If an OMU cannot receive any messages from the other for a period

of time, the unresponsive OMU is considered faulty. If the active OMU is faulty, a switchover

is triggered.

3.5 Synchronization Between Active and Standby OMUs

In active/standby mode, the synchronization between the active and standby OMUs consists of

data synchronization, file synchronization, and time synchronization.

data synchronization

The OMU data is dynamic, which changes when the BSC6910 is working. After the standby

OMU starts, the active OMU data is fully synchronized, and the increments are synchronized.

This ensures that the OMU can work normally after a switchover.

File Synchronization

The synchronization between active and standby OMU files is mainly applicable to dynamic

files. The dynamic files include the license file, board program, BOOTROM file, DSP file, patch

file, and performance statistics file. The software management module on the standby OMU

regularly checks the active OMU files and synchronizes the dynamic files on the standby OMU

with those on the active OMU. This ensures that the files on the active and standby OMUs are

the same.

Time Synchronization

Time synchronization means that the sntp module on the standby OMU regularly synchronizes

the time with the sntp module on the active OMU. This ensures that the time on the active and

standby OMUs is the same.

BSC6910 GSM




26


37/154


38/154

NOTE

If the DSP OMU command output shows that the values for Internal network link state, External network

state, and Backup network link state are all Breakdown, then the active OMU is faulty.

Self-Healing Switchover

Self-healing switchover is a method of self-healing for OMUs.

The active OMU performs a self-healing switchover when any of the following conditions

occurs:

l The hard disk capacity of the active OMU overflows if the remaining space is smaller than

200 MB.

l An abnormality occurred on the active OMU for 10 times within 30 minutes.

l No Ethernet cable is connected to any external Ethernet port on the active OMU.

l The virtual internal or external IP address of the active OMU is lost for more than 3 minutes.

l The standby OMU detects that the active OMU is restarted abnormally three times within

24 hours.

l The connection between the active OMU and SCU is interrupted and the connection

between the standby OMU and SCU is normal.

l A fault occurs in one or both of the internal and external networks of the active OMU while

the internal and external networks of the standby OMU are normal.

BSC6910 GSM




28


39/154

4 Initially Commissioning the OMUAbout This Chapter

This section describes the procedure for initially commissioning the OMU after delivery.

NOTE

Install product software if the version number is not specified in the BSC6910 order.

For the commissioning procedure in the OM phase, see 6.13 Setting OMU System

Parameters.

In the initial commissioning phase, check the installation of product software, and configure the

IP addresses, subnet masks, and OMU name of OMU Ethernet adapters based on the onsite IPaddress plan. For IP addresses and masks to be changed in the initial commissioning phase, see

3.2 OMU IP Address Plan.

Figure 4-1 shows the procedure in the initial commissioning phase.

BSC6910 GSM

OMU Administration Guide 4 Initially Commissioning the OMU



29


40/154

Figure 4-1 Initial commissioning procedure

4.1 Setting the Link Mode for External OMU Ethernet Adapters

This section describes how to set the link mode of the external OMU Ethernet adapters so that

it is the same as that of the LAN switch.

4.2 Commissioning the OMU

Before using the OMU for the first time, commission the OMU onsite to check the installation

status and version of the product software, and configure IP addresses of the OMU.

BSC6910 GSM




30


41/154

4.1 Setting the Link Mode for External OMU Ethernet

AdaptersThis section describes how to set the link mode of the external OMU Ethernet adapters so that

it is the same as that of the LAN switch.

Prerequisites

The link mode, duplex mode, and rate of the LAN switch have been acquired.

Context

If the link mode of the external Ethernet adapters of the OMU is inconsistent with that of the

LAN switch, the network may be interrupted. If the link mode of the LAN switch is specified,the link mode of the external Ethernet adapter of the OMU should also be specified.

There are two link modes of the LAN switch: forced mode and auto-negotiation mode. The link

mode of the OMU external Ethernet adapter must be consistent with that of the LAN switch.

If active and standby OMUs are configured, perform the following steps on both the active and

standby OMUs:

NOTE

l The following procedure assumes that the link mode of the external Ethernet adapter is f orced mode

and the adapter works at 100 Mbit/s in full duplex mode.

l The following procedure assumes that version_a is the active workspace of the OMU.

Procedure

Step 1 Log in to the target OMU by referring to 7.3 Logging In to the OMU.

Step 2 Type the /etc/rc.d/omud stop command and click Enter to stop the omud process

Step 3 Type the cd /mbsc/bam/version_a/bin/bam command and click Enter to navigate to thedirectory that contains omutool

Step 4 Run the ./omutool duplexmode 100 full off command.

NOTE

For details about how to query the link mode of the external OMU Ethernet adapters, see 6.4 Querying

the Link Mode of the External OMU Network Adapters.

The fields in the ./omutool duplexmode 100 full off command are described as follows:

l 100 indicates that the rate of the Ethernet adapter is 100 Mbit/s. The value of this field can be 10, 100,

or 1000. If the Ethernet adapter of the peer switch cannot work at 1000 Mbit/s, the external network

connection of the OMU is interrupted when the rate of the OMU Ethernet adapter is set to 1000 Mbit/

s.

l full indicates that the Ethernet adapter works in full duplex mode. The value of this field can be full

or half.

loff indicates that the link mode of the Ethernet adapter is forced mode. The value of this field can beoff or on. When the value of this field is on, the link mode is auto-negotiation mode.

BSC6910 GSM




31


42/154

Step 5 Enter the /etc/rc.d/omud start command and press Enter to start the omud

----End

4.2 Commissioning the OMU

Before using the OMU for the first time, commission the OMU onsite to check the installation

status and version of the product software, and configure IP addresses of the OMU.

Prerequisites

The OMU is connected to the local PC using the commissioning Ethernet port.

Context

NOTE

If the product software have been installed before delivery, the active workspace of the OMU is version_a.

If the product software have been installed before delivery, refer to 9.2 Checklist for the OMU Software

Factory Settings for the initial parameters of the OMU.

If the product software are not installed before delivery, plan items in 9.1 Information R ecords of OMU

Software Installation, and then install the product software.

Procedure

Step 1 Connect the PC to the OMU board.

1. Connect the PC to the ETH2 commissioning port on the OMU board by using a network

cable.

2. Set the IP addresses of the PC and ETH2 port to be on the same network segment.

The initial IP address of the ETH2 port is 192.168.6.50 (active OMU) or 192.168.6.60

(standby OMU), and the subnet mask is 255.255.255.0.

Step 2 Set the link mode of the external OMU Ethernet adapters.

1. Log in to the OMU by referring to 7.3 Logging In to the OMU in the BSC 6910 GSMOMU

Administration Guide.

2. Check whether the link mode of the external OMU Ethernet adapters is consistent with thatof LAN switches.

For details about how to query the link mode of the external OMU Ethernet adapters, see

Follow-up Procedure of 4.1 Setting the Link Mode for External OMU Ethernet

Adapters in the BSC6910 GSMOMU Administration Guide.

If... Then...

The link mode of the external OMU

Ethernet adapters is consistent with that of

LAN switches

Go to Step 3.

BSC6910 GSM




32


43/154

If... Then...

The link mode of the external OMU

Ethernet adapters is inconsistent with that

of LAN switches

Set the link mode of the external OMU

network adapters to be consistent with that

of LAN switch by referring to operationsin Procedure of 4.1 Setting the Link Mode

for External OMU Ethernet Adapters in

BSC6910 GSMOMU Administration

Guide.

Step 3 Install the product software.

1. Run the /etc/rc.d/omud status command to check the running status of the OMU process.

If... Then...

The information displayed is running 1. Run the /etc/rc.d/omud stop commandto stop the omud process.

2. Go to Step 3.2.

The information displayed is unused Go to Step 3.2.

The information displayed is No such file

or directory

1. Install the product software in the active

workspace by referring to operations in

Procedure of 5.3.3 Installing the

Product Software in the Active

Workspace in the BSC6910

GSMOMU Administration Guide.

2. Go to Step 6.

3. Go to Step 7. The task is complete.

2. Run the cd /mbsc/upgrade command to switch to the OMU installation directory, and then

run the ls command to query the current versions of the product software.

If... Then...

The versions of the product software are

the same as those required by the operator

Go to Step 4.

BSC6910 GSM




33


44/154

If... Then...

The versions of the product software are

different from those required by the

operator

1. Uninstall the product software by

referring to operations in Procedure of

6.11.4 Uninstalling the ProductSoftware in the BSC6910 GSMOMU


2. Upload the OMU application

installation package to the OMU by

referring to operations in Procedure of

Uploading the OMU Application

Installation Package to the OMU in

the BSC6910 GSMOMU


3. Install the product software in the active

workspace by referring to operations inProcedure of 5.3.3 Installing the

Product Software in the Active

Workspace in the BSC6910

GSMOMU Administration Guide.

4. Go to Step 6.

5. Go to Step 7. The task is complete.

Step 4 Modify the OMU IP addresses.

1. Run the cd /mbsc/bam/version_a/bin/bam command to switch to the directory where theomutool program is located.

NOTE

You can run the ./omutool -h command to view the help information of the omutool.

2. Change the fixed external IP address and subnet mask according to the plan of the operator.

Run the ./omutool extercard The external fixed IP address The subnet mask The gateway

IP address (Optional) command to change the fix external IP address and the subnet mask.

For example, you can type the following command and then press Enter.

./omutool extercard 10.161.10.100 255.255.255.0

NOTE

l The following two methods show how to change the fixed external IP address if changing the

gateway IP address is required at the same time.

l Method 1: Type ./omutool extercard The external fixed IP address The subnet mask (The

gateway IP address) and then press Enter to change the fixed external IP address and gateway

IP address at the same time. The following is an example:

./omutool extercard 10.161.10.100 255.255.255.0 10.161.10.1

l Method 2: Type ./omutool gateway The gateway IP address and then press Enter to change

the gateway IP address separately. The following is an exam ple:

./omutool gateway 10.161.10.1

l After the fixed external IP address is changed, the OMU can be connected to the operation and

maintenance (OM) network of the operator by using the ETH0 or ETH1 port. In this case, thecommissioning task can continue remotely.

BSC6910 GSM




34


45/154

3. Change the virtual external IP address and the subnet mask of the active and standby OMUs

according to the plan. Ensure that the virtual external IP address is on the same network

segment as the fixed external IP address.

Run the ./omutool extervip The external virtual IP address The subnet mask command to

change the virtual external IP address and the subnet mask. For example, you can type thefollowing command and then press Enter../omutool extervip 10.161.10.102 255.255.255.0

NOTE

When the fixed or virtual external IP address is being changed, a window is displayed to remind users

to check whether the virtual or fixed external IP address and the gateway IP address need to be

changed. In this way, users can make necessary changes to ensure that the three IP addresses are on

the same network segment.

4. Check whether the fixed internal IP address, virtual internal IP address, backup channel IP

address, and debugging IP address of active and standby OMUs are on the same network

segment as the operator's network.

BSC6910 GSM




35


46/154

If... Then...

All of the preceding IP addresses

are on the same network

segment as the network of theoperator

Change the IP address in conflict.

l Run the ./omutool innercard The internal fixed

IP address command to change the fixed internalIP address and the subnet mask. For example, you

can type the following command and then press

Enter../omutool innercard 80.168.3.60

l Run the ./omutool innervip The internal virtual

IP address command to change the virtual internal

IP address and the subnet mask. For example, you


Enter../omutool innervip 80.168.3.40

NOTEl When the fixed or virtual internal IP address is being

changed, a window is displayed to remind users to

check whether the virtual or fixed internal IP

address needs to be changed. In this way, users can

make necessary changes to ensure that the two IP

addresses are on the same network segment.

l If the network segment of the virtual or fixed

internal IP address is changed, the Subnet No. must

be changed when updating the OMU database. For

details, see Follow-up Procedure in Updating the

OMU Database to ensure that the OMU

communicates properly with the BSC6910 host.

l Change the backup channel IP address and subnet

mask of the active and standby OMUs:

Run the ./omutool backupcard The IP address

command. For example, you can type the

following command and then press Enter../omutool backupcard 192.168.3.60

l Run the ./omutool debugcard The debugging IP

address command to change the debugging IP

address and the subnet mask. For example, you


Enter../omutool debugcard 192.168.6.60

The preceding IP addresses are

not on the same network

segment as the network of the

operator

Change the backup channel IP address of the standby

OMU.

Run the ./omutool backupcard The IP address

command. For example, you can type the following

command and then press Enter../omutool backupcard 192.168.3.60

Step 5 Change the OMU name.

1. Run the ./omutool hostname OMU name command to change the name of the OMU.

BSC6910 GSM




36


47/154

For example, you can type ./omutool hostname omu_123 and then press Enter.

NOTE

The OMU name cannot contain control characters, spaces, or any of the following characters: / \ [ ] ( ) ' :

| < > + = ; , ?, and the length of the OMU name ranges from 1 to 62 characters.

Step 6 Set the working mode of the OMU.

1. Set the OMU backup attribute.

l If only one OMU board is configured, run the ./omutool dualmode single command

to set the OMU to work in independent mode.

l If two OMU boards (active and standby OMU boards) are configured, run the ./omutool

dualmode dual command to set the OMU to work in active/s

Documents

Bsc6910 Gsm Omu Administration Guide(v100r015c00_05)(PDF)-En