MSOFTX3000 ATCA Platform CGP and OMU Principle-20090622-B-1.0

Security Level: INTERNAL
MSOFTX3000 ATCA platform

CGP and OMU principle
ISSUE1.0 CGP Cao Yuning
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential

The training slides aim to provide basic
knowledge on the OMU (including the
client) for technical support engineers.
Contents in the slides are applicable to

CGP V100R003.
HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 2

Training Guide
 OMU Installation Guide
 CGP System Principle

References
 Documents on
http://support.huawei.com/support/
 Reference manuals on the info-server

After learning the course, you will:
 Know functions of the client (LMT and Web
UI).
 Know the modules of the OMU server.
 Know the functions of the OMU server.

Comparison Between the CPCI and ATCA Hardware
Platforms
For the compact peripheral component interconnect (CPCI) hardware
platform, the BAM acts as the software platform.
BAM iLMT iLMT

SQL Server 2000 Server
Windows 2000/2003 Windows XP

Server/CPCI PC
For the advanced telecom computing architecture (ATCA) hardware

platform, CGP acts as the software platform.
CGP.OMU
iMAP Oracle LMT
ACE 11g
SuSE 10 Windows XP
Server/ATCA PC

ATCA Hardware Platform
For the ATCA, CGP acts as the software platform.
Softswitch products IMS products … Product service layer
OMU Host platform CGP platform layer
Oracle Memory database Databases
SuSE Linux Compact Linux Operating systems
ATCA boards Boards

1. Introduction to the OMU Client (LMT
and Web UI)
2. Introduction to the OMU Server

1. Introduction to the OMU Client
1.1 LMT
1.2 Web UI

Client Functions
 The OMU client software is classified into the LMT software and Web
UI software.
 The OMU client and OMU server work in client/server mode.
 The LMT provides the following operation and maintenance options

based on the MML and GUI: service maintenance system, alarm
subsystem, trace management, and monitoring management.
 The OMU client supports management of multiple managed entities
(MEs).
 The Web UI enables you to perform performance measurement, use
the KVM over IP and upgrade tool, and download the JWS client
through a web browser, without installation of a client. The functions of
the Web UI are detailed in the subsequent slides.

LMT Operations
 The LMT is an ME-based system. For example, the MML command
interface, device panel, monitoring management, trace management,
and alarm management are based on MEs.
 MML command interfaces are classified into MML command
interfaces of the platform and MML command interfaces of products.
Platform MML commands can be run only on the MML command
interfaces of the platform, and product MML commands can be run
only on the MML command interfaces of products.
 The platform MML commands are shared by many products, for
example, the commands for managing hardware. The product MML
commands are specific to a product.

LMT Login Interface
 The user name and password are required for logging in to the LMT. The default user
name is admin, and the password is lem.
 The user type can be Local or EMS.

LMT Login Interface (Offline)

The Interface Displayed After You Log In to the
LMT (Online)
 The ME nodes are displayed in the navigation tree.
 Right-click an ME, and choose an appropriate option from the shortcut menu to perform
operations on the ME. The operations include running MML commands, launching
monitoring and tracing, browsing alarms, and managing processes.

MML Command Interface (Querying ME
Information)

Trace Interface (Creating a Trace Task)

Message Tracing Interface

Monitoring Interface (Creating a Task)

Monitoring Interface (Displaying Results in
Charts)

Device Panel Interface

Process Management Interface

Alarm Browsing Interface
 Open the Browse Alarms interface, and select an ME in the navigation tree. The alarms
of the ME are displayed in the right pane. To display the alarms about all the MEs, select
the root node in the navigation tree.

FTP Function of the LMT
 You can start the FTP tool by using the following methods:
1. Start the LMT, and choose Maintenance > File Transfer Service from the
main menu to open the FTP interface.
2. Choose Start > HUAWEI Operation and Maintenance System > FTPS
Client to start the FTP tool. You can also use an independent tool package.
You only need to decompress the package. When prompted, enter the IP
address of the FTP server, and the user name and password.
 The differences between the two methods are as follows:
For the first method, you need not enter the user name and password. The
LMT automatically checks the user name and password. In addition, the LMT
automatically checks whether the type of the package to be uploaded is correct
and selects an upload directory based on the package type.
For the second method, you must enter the password of the root user and the
IP address of a board. Besides this, the package type is not checked and all
the packages are uploaded to the /opt/ directory.
 The LMT R3 supports the resumable download function.

FTP Function of the LMT
 Right-click a file, and choose upload or Download. The upload or download progress is
displayed in the upper pane.

LMT Functions
 Object navigation tree: The nodes in the object navigation tree are logical functions.
 MML navigation tree: The MML navigation tree displays basic MML commands classified
on the basis of logical MEs.
 Tracing management: Tracing management provides the functions such as connection
tracing, signaling tracing, interface tracing, and message interpretation.
 Monitoring management: With this function, the board-specific and process-specific CPU
usage, memory usage, memory dumping, and memory contents can be displayed
dynamically.
 Device panel: By observing the device panel, you can be aware of the running status of
a device and the boards.
 Alarm management: Alarm management involves real-time alarm reporting and history
alarm management.
 Performance management: Performance management allows you to manage
performance through the Web UI.

1. Introduction to the OMU
Client
1.1 LMT Functions
1.2 Web UI

Web UI
 Open the Microsoft Internet Explorer, and enter http://IP address of the web
server/ in the address bar to log in to the web server.
 On the login interface, enter the user name and password, and select a user
type, which can be Local or EMS.
 After login to the web server, four buttons are displayed: Performance
Management System, KVM over IP, Upgrade Tool, and Downloads. Click a
button, and the corresponding interface is displayed.
 Performance Management System: Provides the performance
measurement function.
 KVM over IP: Enables you to log in to the OS of a board through the web
client and run system commands.
 Upgrade Tool: Enables you to upgrade the platform and MEs.
 Downloads: Enables you to download the JWS client. The downloaded
JWS client can be used directly without being installed. It provides the
same functions as the LMT client.

Login Interface of the Web UI Client

The Interface Displayed After You Log In to the
Web UI Client

Upgrade Tool Interface

Upgrade Process
 Click Upgrade in the navigation tree. The MEs that can be upgraded are displayed in
the right pane.
 Select the required ME and the target version.
 Click Upgrade on the menu bar. The upgrade starts, and a progress bar is displayed to
indicate the upgrade progress.
 During the upgrade, you can click View Report in the navigation tree to view the
upgrade details.
 If an error occurs during the upgrade, you can click Rollback in the navigation tree to
roll back the upgrade.
 After the upgrade, the ME can run for seven days for trial. If the ME runs normally during
the trial period, the backup workspace will be deleted. Once the backup workspace is
deleted, the ME cannot be rolled back.
 For details about the upgrade process, see the Upgrade Guide.

KVM Over IP Interface
 Note: There is training on KVM over IP.

KVM Over IP Interface
 Select a subrack, and click OK. The board list of the subrack is displayed in the right
pane. Click a board. The login interface of the board is displayed.

Download Interface

The Interface Displayed After You Click Install
 After you click Install, the JWS download program is started and the system prompts
you to create a shortcut.

The Interface Displayed After You Click Install
 The following interface shows the download progress. After the download is complete,
the login interface is displayed.

Web UI Performance Client Interface

Menus of the Web UI Performance Client
The menus of the Web UI performance client includes Measurement, Query,
Export, Monitor, and Threshold Setting, Customized Entity, and Sample
Statistics Data.

Performance Measurement Task Management
Interface

Querying Performance Measurement Results

Performance Measurement Result List

Exporting Performance Measurement Results

Creating a One-Minute Monitoring Task

Setting Thresholds

Customizing Performance Entities

Sampling Statistics Data Interface

1. Introduction to the OMU Client (LMT and
Web UI)

1.1 OMU Logical Structure
1.2 OMU HA System
1.3 OMU Functions

OMU Logical Structure
 The CGP software is classified into the host software and the background software.
 The background software consists of the OMU, LMT and Web UI.
 The OMU is the OMU server software. It is installed on boards. The following figure
shows the upper-layer and lower-layer software structures of the OMU software.
 The LMT and Web UI are installed on a PC. They are the O&M client software and
implement the functions such as man-machine interaction and device management.
Softswitch products IMS products … Product service layer
OMU Host platform CGP platform layer
Oracle Memory database Database
SuSE Linux Compact Linux Operating system

Part Process Process Name Description
OMU Configuration CM Provides the configuration management function

management
Fault management FM Provides the fault management function
Performance PM Provides the performance management function

management
Maintenance MM Provides the maintenance management function
management
Security management SM Provides the security management function
Management information MIT Provides the management of object classes and object
tree instances
Tracing management TM Provides the tracing of signaling and interfaces
Real-time monitoring RMM Provides the real-time monitoring of system performance

entities
Communication DCM Provides the management of device communication
management
Log management DEVLOG Provides the log management function
Loading management LOAD Provides the host software loading function
Backup management BKM Provides the management of the system backup
Report management RSM Provides the report management function
Resource monitoring MIRROR Provides the active/standby OMU arbitration and resource
monitoring functions
MIRROR monitoring OMUMONITOR Monitors the status of the Mirror process
Listening management XM and xsman Monitors two managed modules

Part Process Process Name Description
MIU SOAP interface SOAP-AGT Provides the SOAP management interface
MML command MMLSERVER Provides the MML management interface

interface
GUI client interface LMTSERVER Provides the local operation and maintenance
interface
SNMP interface SNMP-AGT Provides the SNMP management interface
DIU SNMP interface SNMP-MGR An interface between MEs
Binary interface BIN-MGR A binary interface between MEs
CSU FTP service FTPS-SVC Provides the services of the FTP server
NTPS service NTPS-SVC Provides the services of the NTP server
NTPC service NTPC-SVC Provides the services of the NTP client
User agent UA Automatically manages tasks on behalf of operators

Viewing the Status of OMU Processes on the
Client
 Right-click the CGP node in the object navigation tree, and choose Launch
Monitoring. The monitoring interface is displayed. Double-click OMU Module, and the
OMU module monitoring interface is displayed, as shown in the following figure.

OMU HA System Management
 The OMU high availability (HA) system refers to two OMU boards working in
active/standby mode.
 The OMU HA system is not installed with disk arrays. It supports the dual-board
installation, that is, the primary and secondary boards can be installed at the same time.
 The OMU HA system uses two processes: Mirror and Sync. The Mirror process functions
as the arbitration point of the OMU HA system. It arbitrates the primary and secondary
boards and monitors resources. The Sync process forwards MML commands, and collects
and sends synchronization messages to the Mirror process. The Mirror process performs
the synchronization and processes the MML commands.
 The synchronization scheme of the primary and secondary boards: The database
synchronization is implemented through Oracle Data Guard, and the file synchronization
is implemented through the Mirror process of the OMU.
 The processes running on the secondary board are omumonitor, mirror, and oracle.
 The active/standby switchover policy is configured in the configuration file. For example,
you can configure the policy data so that the active/standby switchover occurs when some
processes are abnormal or after the active board restarts several times. You can even
configure whether the system performs a switchover or restarts when the primary or
secondary board is abnormal.

1.3 OMU Functions

Configuration Management Fault Management
Log Management Performance Management
Loading Management Security Management
Trace Monitoring Software Management
NMS Access Differences Between the OMU and the BAM

OMU Configuration Management
Data backup function:
 You can back up data to a local disk, network server, or network management system (NMS) server.
 You can back up the database and/or configuration files.
 You can back up the database in full backup mode or incremental backup mode.
 The system can run BKP SYS automatically at 3:30 a.m. every day to back up the database. You can
also run BKP SYS to back up the database manually.
 No MML command is available for database restoration, because MML commands can be run only on
the basis of an existing database. You can run
/opt/HUAWEI/cgp/workshop/omu/workspace1/server/bin> cgp_restore.sh to restore the database.
For details, see the Administrator Guide.
 It takes a long time to back up or restore the database. During the backup, a progress bar is displayed
to indicate the backup progress. The progress bar for database restoration is added in the R3 version.
 The backup files generated in the most recent seven days are retained, and the oldest backup file that
is saved for more than seven days is overwritten by the new backup file. The system keeps only one
backup file for each day.
 The files are backed up to the DB and APP folders in \\IP address of the OMU
server\root\opt\HUAWEI\cgp\workshop\omu\share\backup\backup_5_V100R002C02B022\.
 At present, the OMU does not provide the function of clearing data configuration. You can clear the
data configuration quickly by replacing the current database with an empty database.

Data export function:
 You can run EXP MES to export data, run IMP MES (an implicit command) to
implicit data, and run LST EXPINFO to query information about the exported
files.
 The EXP MES command is used to export database tables. You can check the
tables for information required for identifying problems. Exporting tables is
quicker than exporting a database, because the tables are of a much smaller
size than the database. You can export the tables of a specific ME or export all
the tables.
 During the export, a progress bar shows the export progress.
 The data is exported to
\\167.1.3.168\root\opt\HUAWEI\cgp\workshop\omu\share\backup\exp_backup.
 The tables are exported one by one as compressed files.
 You can download the exported files to a local client through SFTP.

 The data management on the OMU is implemented by using the functions similar to those
on the CPCI platform, such as data formatting, online setting, and CRC check.
 The OMU does not provide commands to enable or disable the data formatting function
and online setting function on the CGP platform.
 When the data formatting and online setting functions of all the service MEs are disabled,
the data formatting and online setting functions on the CGP platform are disabled. When
the data formatting and online setting functions of any service ME are enabled, the data
formatting and online setting functions on the CGP platform must be enabled.
 Automatic conversion and setting: When the OMU restarts, the system checks whether
there are unfinished data conversion and setting tasks. If there are unfinished tasks, the
system automatically converts the data and sets the tasks.
 The processing procedure of configuration commands is as follows: Pre-process (check
parameters and check whether the ME is locked) -> Invoke stored procedures to
implement data processing and notification -> Format data -> Perform online setting ->
Return packets.
 You can perform a task of batch data configuration immediately or in a scheduled manner.

Immediate Batch Processing
 In the Immediate Batch Command window, you can save commands or results, perform syntax
analysis, or set whether to display a message when an error occurs. In addition, you can select an
execution type, for which the available options are All, Step by Step, Breakpoint, Range.

Adding a Scheduled Task
 Scheduled tasks are stored on the OMU board and can be run every several months,
weeks, or days. You can set the start date and end date of a scheduled task. You can also
set the number of times a scheduled task runs on a day (the default value is 5) or the
execution period (the number of times a task runs is not limited).
 The following figure shows the interface on which a task is set to run only once:

 The following figure shows the interface on which a task is set to run periodically:

 The following figure shows the list of added tasks:

Querying Results of a Scheduled Task
 Right-click a scheduled task, and choose Query Execution Result. On the displayed
interface, double-click a record to display the task results.

 The following figure shows the statistic results of a scheduled task.

OMU Configuration Rollback
CFM TST CNL TST
STP TST
BGN TRAN CMT TRAN
Normal mode Transaction mode Trial operation mode
RBK TRAN
STP TRAN
 Configuration rollback function: You can run RBK TST to roll back the configuration.
Before configuring data, run BGN TRAN to place the ME in transaction mode. Then, run
commands to add, delete, or modify data. After the configuration, run CMT TRAN to place
the ME in trail operation mode. At this time, if you want to roll back to the transaction
mode to add, delete, or modify the data again, you can run RBK TST. If you want to
check whether the added, deleted, or modified data is correct, you can run CFM TST to
place the ME in normal mode. In trial operation mode, you can run CNL TST or STP TST
to cancel or stop the trial operation and place the ME in normal mode.

OMU Fault Management After receiving the alarm
notification message, the
The FM module generates and alarm subscribers send
sends an alarm notification the notification message
message to the alarm to their own MEs.
subscribers.
DEV OMU MANAGER
MML SERVER LMT SERVER
M2000/N2000
FM DATABASE
After detecting a fault,
the host invokes the LMT
alarm sending Upon receiving the
interface of the alarm alarm, the DCM ALM BOX CTRL
module forwards the
module to send an
alarm to the FM
alarm. module.
The FM module
generates an alarm
and sends the
DEV ALARM MODULE DCM alarm to the alarm
box through the
ALARM BOX alarm box module.
The DCM modules Upon receiving the alarm,

The alarm module sends the response the FM module returns a The FM module invokes the DB2 stored
generates and to the alarm module response to the DCM procedure to analyze the parsed alarm and
sends an alarm to module. saves the alarm in the database. Then, the
of the host.
the OMU. DB2 stored procedure returns to the FM
module an alarm record indicating that the
alarm is successfully stored in the database.

OMU Alarm Management
 Basic concept 1
 Fault alarm: A fault alarm reflects a state. It is generated at a specific time
and is retained until the corresponding clear alarm is generated.
 Event alarm: An event alarm refers to an alarm generated for an event. It is
the alarm information that is displayed at a certain time. An event alarm
reflects only an instant state. No clear alarm is generated for an event alarm.
 Features of a fault alarm:
 Continuity, that is, a fault must exist for a period.
 Clearable: A fault alarm has a corresponding clear alarm.
 Features of an event alarm:
 Unrecoverable: An event alarm has no corresponding clear alarm.
 Clearable: The fault that results in the generation of the alarm is rectified. An
alarm is cleared when the corresponding clear alarm is generated.

 Basic concept 2
 Oscillating alarms: The fault alarms and clear alarms that are generated alternatively
within a short period with the same ME ID, alarm ID, module ID, object instance, and
key parameters. For oscillating alarms, only one pair of fault alarm and clear alarm
(the first fault alarm and the last clear alarm) are retained. Other alarms are filtered.
The filtered alarms are not saved to the database or reported to the NMS.
 Active alarm: An alarm that is not cleared.
 Global alarm: An alarm that is generated on module A of an ME but can be cleared by
module B.
 For a global alarm, the FM need not know the ID of the module on which the alarm is
generated.
 ADAC Fault: The system can automatically detect when an automatically detected
and automatically cleared (ADAC) fault occurs and when the fault is rectified.
 ADMC Fault: The system can automatically detect when an automatically detected
and manually cleared (ADMC) fault occurs, but cannot detect whether the fault is
rectified. When the fault is rectified, you must clear the alarm manually.

The following are alarm related commands:
 LST ALMAF: The command is used to list active alarms.
 LST ALMLOG: The command is used to list history alarms.
 RMV ALMFLT: The command is used to clear alarms manually.
 LST ALMCFG: The command is used to list alarm configuration.
 SET ALMLVL: The command is used to set the alarm severity.
 SET ALMSHLD: The command is used to set the alarm masking flag.
 SET BOXRPT: The command is used to set the report to alarm box flag.
 RST ALMCFG: The command is used to restore the alarm configuration.
 EPT ALMDATA: The command is used to export alarm logs.

The following are alarm box related commands:
 LST BOXLGT: The command is used to query the status of the alarm box.
 LST BOXVER: The alarm is used to query the version of the alarm box.
 SET ALMSCRN: The alarm is used to query the masking level of the alarm box.
 LST ALMSCRN: The command is used to set the masking level of the alarm box.
 CLR BOXLGT: The command is used to turn off the alarm indicators.
 STP BOXSND: The command is used to disable the alarm sound.
 RST ALMBOX: The command is used to reset the alarm box.

Basic alarm data
 For fault alarms, a maximum of 50,000 alarms can be stored and the alarms
can be retained for up to 90 days. For event alarms, a maximum of 45,000
alarms can be stored and the alarms can be retained for up to 90 days. The
alarms that are generated 90 days ago are exported automatically at wee hours.
You can also manually export these alarms as an xml file.
 Alarms are reported to the NMS through SNMP. Event alarms are not reported
to the NMS.
 There is an alarm acknowledgment mechanism. If the module that sends an
alarm does not receive an acknowledgment message at the specified period,
the module resends the alarm periodically.
 Alarm check: For alarms about host faults, the OMU performs alarm check at
wee hours every day. If the alarms do not exist or the faults are rectified, the
OMU automatically clears the alarms.
 The OMU can process up to 400 alarms per second.

Browsing Alarms

Browsing Alarms

Alarm Related Operations
 1. You can right-click an alarm, and choose the required option to perform the corresponding operation,
as shown in the left figure.
 2. Right-click an alarm, and choose Set Columns. In the displayed Set Columns window, you can set
the columns to be displayed. The sequence of the columns remains unchanged.

Saving Alarms
 1. You can save all the alarms, the selected alarms, or alarms of the specified range.
 2. Alarms can be saved in a TXT file, an HTML file, or a CSV file.
 3. By default, alarm files are saved to the D:\CGP\omu\workspace1\client\output\alarm
path.

Querying Alarm Logs

Alarm Box Related Operations

Setting Local Alarm Sound
 You can set whether to play alarm sound repetitively.
 You can set to play alarm sound for alarms of specific severities.
 You can set the sound duration (in second).

Alarm Customization
 By default, 1,000 fault alarms or 1,000 event alarms are displayed in the alarm browsing
window. Up to 2,000 alarms can be displayed in the alarm browsing window.
 Keep the default alarm color settings.

OMU Log Management
Host logs
 There are two types of host logs: binary logs and text logs.
 For binary logs, a specialized tool is required to view them. For text logs, you can save the
logs in a text file and then view the file. Alternatively, you can choose View > Debug from
the main menu of the OMU client to view the logs directly.
 Log files are stored in the /opt/HUAWEI/cgp/workshop/omu/share/run_log/dev_log>
directory. Different types of logs are stored in different folders in the directory.
 Storage rules: The maximum size of a log file is 20 MB. When a log file reaches 20 MB,
the file is automatically compressed. Up to 30 compressed files can be retained in a folder.
The compressed files are overwritten in round robin manner when more than 30
compressed files exist in a folder.
 Each module of the host can process at least 20 logs per second.

OMU Log Management
1. The running logs of the OMU are text logs.
 The running log files are stored in the
/opt/HUAWEI/cgp/workshop/omu/share/run_log/omu> directory. The log files of each
OMU module are stored in a separate folder.
 Storage rules: The maximum size of a log file is 2 MB. When a log file reaches 2 MB, the
file is compressed automatically. Up to 32 log files can be retained. The oldest log files are
deleted when more than 32 log files are generated in a folder.
2. Operation logs of the OMU: Up to 200,000 logs can be retained in the database. If the
number of logs exceeds 200,000, the logs are dumped. Each 10,000 logs are dumped to
a file. You can query logs in GUI mode or in command line mode (by running the qry log
command).
3. Setting/Querying the log level
 You can run set loglevel to set the log level and run lst loglevel to query the log level.

Querying OMU Operation Logs

OMU Performance Management
 For the softswitch domain, the host registers performance measurement

tasks. For the IMS domain, the host performs performance
measurement by using all measurement entities.
 On the Web UI, tasks are registered by activating the corresponding
task files.
 The performance measurement results on the Web UI are stored in the
database and can be queried through Web UI. The results are also
saved in binary files. The files are transmitted to the NMS through FTP.
 The performance measurement results are retained in the database for
60 days by default. The duration for keeping the results can be
configured. The performance measurement result files are retained for
three days, after which the files are transmitted to the NMS through FTP.
The duration for keeping the files cannot be configured.

Architecture of Performance Solution

Web UI NMS
Task files/Monitoring files Task files
OMU
WEB-AGT SOAP-AGT
PM
RSM
Performance
Performance
measurement
PDS measurement task
database
processing
CM management
Host communication module

DCM
Interface for transmitting Transmitting PCDR through

messages Sliding Window Protocol
Host (MSOFT3000)

OMU Performance Management
 The host generates PDCRs. The PM (PDS) parses the PDCRs and saves the
performance measurement results in the database. The PM also saves the results in files.
 The PM (PDS) can save performance measurement results in binary files or XML files
and in the DB2. Performance measurement result files and performance configuration
files are stored in separate folders in the
\opt\HUAWEI\cgp\workshop\omu\workspace1\perf_data\ directory.
 The Web UI client connects to the RSM (ReportServer) to query the DB2 for performance
measurement results.
 The performance measurement results are stored in the PDS database. After the
database is switched from the DB2 to the Oracle, the PDS database is merged with the
CGP database.
 At present, the PM can process 1300-1600 PDCRs per second.
 The performance measurement tasks are registered by activating corresponding task files.
The task files contain measurement units, measurement entities, measurement period,
and switches.

OMU Loading Management
Loading types:
 Network loading (OS loading): Network loading refers to the whole process of
downloading, installing, and starting the OS through Preboot Execute
Environment (PXE).
 Initial loading: Initial loading refers to the whole process of downloading,
installing, and starting files through Sliding Window Protocol. The downloaded
files include some kernel files and configuration script files of the OS and files
and programs for CGP MEs.
 Online loading: Online loading refers to the whole process of downloading,
installing, and starting files through CGP communication module. The
downloaded files include files and programs for some CGP MEs and all the
service MEs.

OS loading
 The service board (APP server) is configured to start the OS from the network (or start
the OS from the network after local start attempts fail more than three times). The
service board sends the OMU board a request for installing the OS and database. If the
OMU board has the OS and database, the system automatically installs them on the
service board.
Response
Request
OMU Server APP Server

Online loading
 The host sends a loading request to the OMU.
 The OMU obtains the list of loading files from the database.
 The OMU compares the CRC value received from the host with that
stored in the local disk. If the two CRC values are the same, no
loading is required.
 If the CRC values are different, the host starts loading files from the
OMU through FTP.
 During loading, a progress bar shows the loading progress.

Viewing loading progress
 You can view loading progress by browsing event alarms.
 You can click the Device Panel tab, and select the Board Loading Programs node to
view loading progress in the right pane.

OMU Security Management
OMU security management helps to secure the OMU system. It involves
user management, right management, security policy management, and
log management.
 User management: Classifies and manages various users.
 Right management: Allocates rights to users and prevents unauthorized

operations from being performed on the OMU.
 Security policy management: Prepares security policies, such as the
password strength policy and locking policy, to prevent hacker attacks.
 Log management: Records system operations to indicate the running
status of the OMU.

 You can choose System > Security from the main menu to display the Security Management navigation tree,
consisting of the nodes involving user management, user group management, command group management,
object group management, workstation management, security policy management, online user management,
and log management.
 The administrator can perform all security management operations. Other users can perform authorized
operations. If a user performs an unauthorized operation, the system displays a prompt box for warning.

 User management involves deleting or editing a user, setting user password,
and authorizing MEs and operations. The user admin is the default
administrator who has all rights on the OMU and cannot be deleted.

 User group management involves deleting or editing users, setting the user
passwords, and authorizing MEs, operations, and directories. The default
groups, namely administrator, operator, user, and guest, cannot be deleted.
 By default, the administrator group has all operation rights, the operator group
has authorized operation rights, the user group has query rights, and the guest
group has no right. The rights of the four groups can be modified.

 ME authorization: Authorizes users to operate specified MEs. By default, the
CGP is an authorized ME, and no authorization is required. Service MEs require
authorization.
 Select the User node in the Security Management navigation tree. In the right
pane, right-click a user and choose Authorized ME to allocate MEs to the user.

 Operation authorization: Authorizes users to perform specified operations (command
groups) on specified objects (object groups), involving authorization of ME IDs,
command groups, and object groups. The user rights are the intersection of the
authorization.
 Select the User node in the Security Management navigation tree. In the right pane,
right-click a user and choose Authorized Operation to allocate operation rights to the
user.

 Command group management: Each ME has its own default command group, which can
be edited but cannot be deleted. After an ME is installed, the existing command group is
the default command group.
 You can add a command group. A command can belong to one or more command groups.

 Object group management

Object group management:
 An object group is a set of objects or resources operable to users. An object group
maps an operation domain on the CPCI. Object group management refers to right
management and control of system resources (managed objects) operable to
users.
 If a new object is not configured with the object group parameter, the object does
not belong to any object group.
 If a new object is configured with the object group parameter (that is, the
parameter item in the data profile is set to Yes), you can choose whether to set
the parameter. If you do not set the parameter, the object belongs to the current
object group (the public group by default). The public group is a default group
and cannot be deleted.
 You can run the SET CURMOGRP command to change the current object group.
 An object configured with the object group parameter must belong to an object
group.
 You can create or delete an object group except public.
 An object group belongs to one and only one ME.

 Workstation management involves setting the IP address range within which you can log in to
the OMU. The function is disabled before you select the Enable workstation access control
check box.
 You can set the IP addresses, network segment, and IP addresses and subnet masks to
specify the workstations with which you can log in to the OMU.

 Security policy management provides the account locking policy. You can set
the login attempts, login interval, and account lockout duration for a user.

 Security policy management provides the password policy. You can choose whether to change the
password at the first login and whether to use the history password. You can set the days before which
password expiration is notified and the password strength. At present, however, a password cannot be
retrieved if it is lost.

 Online user management: The OMU provides online user information in GUI
mode. Up to 32 clients are allowed to log in to the OMU at a time.

Log management
 OMU logs are classified into operation logs, security logs, and event
logs.
 Operation logs: Record user operations on the OMU, including
operations performed through the SOAP and SNMP interfaces.
 Security logs: Record operations related to the system security, such as
user login, logout, and authorization.
 Event logs: Record event alarms. The latest alarm definition rules define
event alarms as event logs. All the event alarms are not reported to the
Browse Alarms window of the OMU client in real time. You can query
event alarms only from event logs.
 The log filtering criteria and log contents vary according to the log types.
For details, see the immediately subsequent figures.

 Operation logs

 Security logs

 Event logs
 Note: Log management is detailed on the fault location slide, which can
be used as a reference.

OMU Trace Management
 The following figure shows interaction between entities for implementing tracing
management.
Create, stop, delete, and
handshake commands
immediate task and Only create, delete, and
scheduled task commands handshake commands
Client TM ME
Messages and command responses Messages and command responses
 Different MEs have different trace tasks. The CGP platform provides the IP, Ping, and
Trace Route trace tasks. The trace tasks of service MEs vary according to services.
 Supporting scheduled trace tasks: Scheduled trace tasks refer to the tasks that are
automatically activated at the preset time. After a scheduled trace task is activated, the
trace results are reported to the connected clients and are saved to the specified file. The
start time and end time of a scheduled trace task are configurable. A scheduled trace task
runs only once.

 The figure on the left shows the menu items that are displayed when you right-click a
node on the Tracing tab page.
 The figure on the right shows the menu items that are displayed when you right-click in
the tracing window.

 Saving trace messages: You can choose to report trace messages to a specified location.
By default, the messages are not saved. You can save the messages to a binary file or a
text file. The default saving path is *\omu\workspace1\client\output\cgp\version
number\ (* indicates the installation path of the OMU client).
 Specification data:
 Up to 80 trace tasks can be activated at a time.
 Up to 64 immediate trace tasks can be activated at a time.
 Up to 16 scheduled trace tasks can be created at a time.
 The MSOFTX3000 does not support periodic trace tasks. It can process 3,000 traces per
second.
 Handshake management: The trace management (TM) module sends a handshake
message to a host (ME) at an interval of one minute. If the TM module does not receive a
response to a task within three minutes, the TM module deletes the task. The TM module
receives a handshake message from the LMT at an interval of five minutes. If the TM
module does not receive any handshake message within 15 minutes, the TM module
deletes the information about the LMT from the buffer.
 Task sharing: The tasks created through different clients are visible on the OMU and can
be activated. The BAM does not have the task sharing function.

OMU Monitoring Management
 You can monitor the CPU usage, memory usage, disk usage, memory dump,
and OMU module.
 The OMU displays the CPU usage, memory usage, and disk usage in charts
and data lists in real time. The data in the charts and data lists refreshes every
five seconds.
 The OMU does not provide the function of saving monitoring data or the monitor
reviewer.
 With the OMU module function, you can monitor the running status of OMU
processes.
 You can run STR DMPMEM to enable the memory dump function and STP
DMPMEM to disable the memory dump function.
 The dumped files can be retained on the OMU board for 1 hour to 168 hours (7
days).
 Files can be dumped at a normal speed or at a high speed. Dump files at a high
speed when the traffic is light.

OMU Monitoring Management
 With the memory dump function, you can dump a maximum of 32 MB data from the
memory to the OMU board. The dumped data is then automatically downloaded to the
specified path on the client. You can set the dump speed (normal speed or high speed)
and the file reservation duration (the default value is 2 days).

OMU Software Management
Installing the OMU through INU4WIN
 Installation procedure:
 1. Install INU4WIN on a PC, and save the installation packages of

the OS, database, and OMU to the specified path.
Unlike the INU board, INU4WIN is installed on a PC with the Windows OS.
 2. Use a network cable to connect the PC to the OMU board.

 3. Start INU4WIN, and perform configuration on the displayed
interface.
 4. Click Install. The installation of the OMU starts.
 Note: The OMU is installed on the board before delivery.

 OMU uninstallation procedure:
 1. Log in to the OS as user root and switch to the opt/HUAWEI/cgp
directory.
 2. Run ./uninstall.
 A dialog box is displayed, asking you whether to uninstall the OMU service.
If you select Yes, the OMU service is stopped and the database is
uninstalled.
 3. A dialog box is displayed, asking you whether to delete OMU users. If
you select Yes, the OMU users are deleted.
 4. A dialog box is displayed, asking you whether to restart the system
immediately. If you select Yes, the system is restarted. If you select No,
the uninstallation is complete.

 Software upgrade and rollback
 1. Log in to the Web UI client and click Upgrade Tool to open the upgrade
interface.
 2. Select the required ME and the target version, and click Upgrade on the
menu bar.
 3. During the upgrade, a progress bar is displayed to indicate the upgrade
progress. You can also click View Report to view the upgrade details.
 4. If an error occurs during the upgrade, you can roll back the upgrade.
 5. After the upgrade, the ME can run for seven days for trial. If the ME runs
normally during the trial period, the backup information is deleted. You
cannot roll back the ME to the original version.

Interconnection Between the OMU and the NMS
 CGP V100R003 supports interconnection with the M2000 and N2000 UMS.
 The performance data, some maintenance commands, security data, and device files are
transmitted between the NMS and the OMU through the SOAP protocol. The alarm data
is transmitted between the NMS and the OMU through the SNMP protocol. The
configuration data is transmitted between the NMS and the OMU through the MML
protocol.
 SOAP service: The OMU provides the SOAP service with the NMS through port 6060.
The SOAP service adopts the SOAP over HTTP (HTTPS) protocol. The NMS functions
as the client, and the soap-agt module of the OMU functions as the server. The SOAP
service is based on the apache service.
 SNMP service: The OMU provides the SNMP service with the NMS through port 8000.
The SNMP service supports SNMP V2/V3. It also supports alarm reporting, alarm
synchronization, and alarm command sending.
 MML protocol: The OMU receives MML commands from the NMS through port 6000. The
MML server module of the OMU processes the MML commands.
 Interconnection with Yiyang NMS: The OMU uses port 6000 to receive MML commands
from the Yiyang NMS and port 6001 to report alarms to the NMS. The performance
interface is not supported.

OMU Related Paths
 Assume that the IP address of the OUM is 167.1.3.105. The OMU
related paths are as follows:
 File uploading path: \\167.1.3.105\opt\pub\software. The
installation package, upgrade package, license file, and patch
package are uploaded to this path on the OMU board.
 Path of the OMU running logs:
\\167.1.3.105\opt\HUAWEI\cgp\workshop\omu\share\run_log\omu.
The running logs of each OMU module are stored in this path.
 Path of the host running logs:
\\167.1.3.105\opt\HUAWEI\cgp\workshop\omu\share\run_log\dev_l
og. The running logs of the host are stored in this path.
 Path of the backup database:
 \\167.1.3.105\opt\HUAWEI\cgp\workshop\omu\share\backup\db_b
ackup

Differences Between the OMU and the BAM
 Differences between the BAM and the OMU are as follows:

 BAM is used to manage a single ME. OMU is used to manage multiple MEs.
 OMU supports inter-operating-system or inter-database transporting.
 All the OMU services are based on description. If an ME is added to the OMU
without adding new features, you need not modify code.
 The O&M capability is integrated into the platform. You need not add codes of new
O&M features such as configuration rollback and alarm configuration restoration.
 OMU supports various northbound interfaces (NBIs) such as the SNMP NBI, SOAP
NBI, MML NBI, Web NBI, and FTP NBI.
 OMU provides a series of auxiliary tools to help maintain consistency between
alarm data, configuration data, performance data, and documents. OMU can
generate 80% of stored procedures; thus, only half of the database maintenance
persons are needed.
 The OMU modules are loosely coupled. If a module is abnormal, other modules are
not affected.

Questions
 What parts does the OMU consist of?
 What parts does the OMU server software consist of?
 What functions does the O&M system of the OMU provide?
 What parts does the security management module of the OMU consist of?
 How to implement the OMU configuration rollback?
 How many ways are there to install the OMU? How to uninstall the OMU?

Answers
 The OMU consists of the OMU server and OMU client (LMT and Web UI).
 The OMU server software includes OMU, MIU, DIU, and CSU.
 The O&M system of the OMU includes the object navigation tree, tracing function, monitoring function,
MML command function, alarm management, and performance management.
 The security management of the OMU involves user group management, command group
management, object group management, and security policy management.
 See slide 64 for details about OMU configuration rollback.
 There are two ways to install the OMU: INU quick installation and manual installation. See slide 112 for
details on how to uninstall the OMU.

Thank You
www.huawei.com

MSOFTX3000 ATCA Platform CGP and OMU Principle-20090622-B-1.0

Uploaded by

Copyright:

Available Formats

MSOFTX3000 ATCA Platform CGP and OMU Principle-20090622-B-1.0

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MSOFTX3000 ATCA Platform CGP and OMU Principle-20090622-B-1.0

Uploaded by

Copyright:

Available Formats

Security Level: INTERNAL

MSOFTX3000 ATCA platform

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential

Contents in the slides are applicable to

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 2

 OMU Installation Guide

 CGP System Principle

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 3

 Reference manuals on the info-server

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 4

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 5

BAM iLMT iLMT

Windows 2000/2003 Windows XP

For the advanced telecom computing architecture (ATCA) hardware

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 6

Softswitch products IMS products … Product service layer

OMU Host platform CGP platform layer

Oracle Memory database Databases

SuSE Linux Compact Linux Operating systems

ATCA boards Boards

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 7

2. Introduction to the OMU Server

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 8

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 9

 The LMT provides the following operation and maintenance options

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 10

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 11

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 12

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 13

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 14

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 15

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 16

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 17

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 18

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 19

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 20

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 21

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 22

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 23

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 24

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 25

1.1 LMT Functions

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 26

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 27

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 28

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 29

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 30

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 31

 Note: There is training on KVM over IP.

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 32

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 33

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 34

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 35

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 36

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 37

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 38

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 39

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 40

HUAWEI TECHNOLOGIES CO., LTD. HUAWEI Confidential Page 41