Owl000104 Imanager m2000 v2 Server o&m Issue 2.1

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved

www.huawei.com

Internal

OWL000104 iManager M2000 V2 Server Operation

and Maintenance

ISSUE 2.1

HUAWEI TECHNOLOGIES CO., LTD. Page 2All rights reserved

iManager M2000 Mobile Element Mana

gement System (M2000) is the centraliz

ed management platform for Huawei mo

bile network

iManager M2000 includes client and ser

ver.


Upon completion of this course, you will be

able to:

Know the software structure of iManager

M2000 V2

Know the functions of each process

Perform O&M of M2000 V2 server


Documentation

HUAWEI M2000 System Administrator Guide


Chapter 1 Chapter 1 System OverviewSystem Overview

Chapter 2 Chapter 2 Software ArchitectureSoftware Architecture

Chapter 3 Chapter 3 System AdministrationSystem Administration

Chapter 4 Chapter 4 Main Processing FlowMain Processing Flow


M2000 System Overview

Network Element Management System (EMS) for Huawei WC

DMA O&M Solution

Adopt CORBA system architecture

Full distributed system with modular design

Open system architecture provide easy integration with 3rd par

ty system


M2000 System Overview

Supported operating system: Solaris

Supported hardware platform: Sun Server / HP Server

Supported database management system: Sybase / Oracle







Software Architecture

GUI

CORBA Software Bus

EMPartition Manager

SM NB AgentFM

SAC

TM CM PMGUI

GUI

NEEngine

MediatorMO Manager

MO ManagerMO Manager


M2000 Process View

CORBA Software Bus

System DaemonSystem Daemon

System MonitorSystem Monitor

Service AgentService AgentService AgentService AgentService AgentService Agent

Service Instance

Service Instance

Service Instance

Service Instance

Service Instance

Service Instance

Naming ServiceNaming Service

Notification Service

Notification Service



Distributed Partitions

Partition ManagerPartition Manager

Host1Host1MO ManagerMO Manager

MediatorMediatorNEEngineNEEngine





NEsNEs NEsNEs NEsNEs



System Components

Service

A software module providing specified features for the system

− Security Management

− Topology Management

− Fault Management

− Configuration Management

− Performance Management


System Components

TM – Topology Management

Provide topology management for all NEs of the entire net

work

CM – Configuration Management

Provide centralized configuration management for all NEs

of the entire network


System Components

SM – Security Management

Provide user authority management for the system

PM – Performance Management

Provide network performance data collection and analyse f

eature


System Components

FM – Fault Management

Provide centralized fault management for all NEs of the ent

ire network

NB Agent – Northbound Agent

Provide northbound interface for Network Management Sy

stem (NMS)


System Components

Mediator – Network Element Mediator

Distributed NE Engine management

The NE Engines realize communications between M2000

system and various network devices

MO Manager

Distributed object-oriented data management

MO – Managed Object, a consistent object with CORBA

interfaces for data access and feature providing


System Components

Partition Manager

PartitionService divides the managed objects into partitions.

Different partitions are managed by different processes.

EM – Event Manager

Exchanges messages between services. It can also broadc

ast and filter messages.


System Components

SAC – System Administration and Control

management process to monitor service status

System Daemon

Manage all services on a host； Provide central configurati

on feature； One system daemon per host


System Components

System Monitor

A management process to monitor service status

Service Agent

Provide process host to service,

One service agent can contain several services,

More than one service agent per host







System Administration

Overview

Introduce O&M for M2000 Server

Include: files & directory, often used commands, main proce

sses, log, and how to start or stop the server etc.


System Administration -M2000 V2

Directory

M2000 installation directory : /opt/OMC

Sybase installation directory : /opt/sybase

Sybase database file directory: /data



Directory inside M2000

/opt/OMC/etc : system configuration files and scripts

/opt/OMC/bin : binary files and scripts

/opt/OMC/var : system runtime log files

/opt/OMC/model : data model files



System users

dbuser : user for SYBASE database management system

omcuser: user for M2000 application program

ftpuser : user for M2000 ftp service



Database for M2000

omcdb : contain NE information, system security informatio

n, audit records, common data for system components

fmdb : contain alarm data

pmdb : contain performance data

sysmdb : contain NE software management data


# . /opt/OMC/svc_profile.sh


Working environment for M2000

Run the environment setting scripts manually

Add the commands to user’s “.profile” file located in the use

r’s home directory


# start_svc# stop_svc# kill_svc


Work with M2000

To start / stop M2000 server

Note: 1. Only user “root” can start or stop the M2000 server 2. Ensuring the sybase server running normally before starting or stopping the M2000 server.


# svc_adm -cmd statusNumber of hosts: 1Host: DEFAULTSYSAGENT SystemConfigurator: running

Service Agent: sac_agent [4 service(s)] pid: 14012

ScheduleManager [running ] SysBackupMgr [running ] LicenseMgr [not running ] LogServer [running ]

...


Work with M2000

To check services status


System Administration -M2000 V2 System Processes 1 sac_agent

ScheduleService BackupService LicenseService LogService

em_agent EventService.

monitor_agent MonitorService

partition_agent PartitionService

audit_agent AuditService


System Administration -M2000 V2 System Processes 2 mo_agent

LockService RelationService MOService MOProxyService

sm_agent SecurityService.

med_agent MediationService

ts_agent TopoService.

ifms_agent FaultService

manager_agent SystemService



System Processes 3 pm_agent

PMService cmserver_agent

CMServer swm_agent

SWMService fmnotify_agent

FMNotify proxy_agent

ProxyServer notify_agent

RemoteNotifyService tad_agent

TadService


1. Log in to the Client.2. Select [Tools/System Backup/Manual Backup].

System will do auto-backup every night.Manual backup is a method for emergencies


Work with M2000

Full system backup (By client)

Directory

− /export/home/backup/omc/


1. stop services1. stop services # stop_svc

2. Check the backup log 2. Check the backup log # more /export/home/backup/omc backup.log# more /export/home/backup/omc backup.log

3. Execute the restoration command3. Execute the restoration command# svc_backuprestore -cmd restore# svc_backuprestore -cmd restore

4. restart services4. restart services# start_svc# start_svc


Work with M2000

Full system restore


1. Check disk space usage and ensure all partitions have at lease 10% disk space left# df –k

2. Check if SYBASE servers are running properly


Work with M2000

If services fail to start


3. Restart M2000 server application program

4. Repairing the file system, then reboot the system

5. Call support engineer


Work with M2000

If services fail to start


1. Check if network connection between client and server broken by ping M2000 server from client

2. Check if all services running properly

3. Ensure the client version match the server version

4. Call support engineer


Work with M2000

If client cannot login successfully


# . /opt/sybase/SYBASE.sh# . /opt/sybase/OCS-12_0/OCS-12_0.sh# . /opt/sybase/ASE-12_0/ASE-12_0.sh

System Administration -SYBASE

Working environment for SYBASE

Run the environment setting scripts manually

Add the commands to user’s “.profile” file located in the use

r’s home directory


# su - dbuser $ showserver… /opt/sybase/ASE-12_0/bin/backupserver -SSYB_back …… /opt/sybase/ASE-12_0/bin/dataserver -sSYB …

Or# ps -ef|grep syb


Work with SYBASE

To check SYBASE processes



Work with SYBASE

Start SYBASE server

# cd /opt/sybase/ASE-12_0/install # ./startserver -f ./RUN_SYB# ./startserver -f ./RUN_SYB_back

or# cd /etc/rc2.d# ./S98sybase start


$ isql -Uusername -Ppassword -Sdataservername1>command2>go….1>quit$


Work with SYBASE

Use isql command tool


1>sp_helpserver

2>go


Work with SYBASE

Check server status


1>sp_helpdb

2>go


Work with SYBASE

Check database status


1>use omcdb2>go1>sp_spaceused2>go……. display data device usage …………1>sp_spaceused syslogs2>go ….. display transaction log device usage ………………


Work with SYBASE

Check database usage



Work with SYBASE

Shutdown server

1>shutdown SYB_BACKUP2>go1>shutdown 2>go

or# cd /etc/rc2.d# ./S98sybase stop


1>dump database omcdb to “/data/backupfile.dat”2>go1>dump database omcdb to “/dev/rmt/0”2>go


Work with SYBASE

Backup database


1>load database omcdb from “/data/backupfile.dat”2>go1>online database omcdb2>go


Work with SYBASE

Restore database


1. User log & NE logThe user/NE log is stored in the DB.Query or displace its information through M2000 Client.

2. System log/export/home/omc/var/syslog

3. Trace log/export/home/omc/var/logs

System Administration -Logs

Logs in M2000 V2 Server


4. SYBASE log

/opt/sybase/ASE-12_0/install/SYB.log

/opt/sybase/ASE-12_0/install/SYB_back.log

5. Solaris Error Log

/var/adm/messages

/var/log/syslog

System Administration -Logs

Logs in M2000 V2 Server







NE Data Synchronization

NE

MO Manager

MOCM

GUI

MediatorNE Engine

Auto Report

Manual Synch

Main Processing Flow


Alarm ReportMain Processing Flow

Status Update

DBNE

Alarm Query

Alarm Record

Status Notify

Alarm ReportUniAlarm

Alarm Notify

GUI

TM

EMMediator

NE Engine

FM


Performance Data Report


DB

Mediator

NEEngine

Validate

Extract

CachePM

PM Report

Calculate

Alarm

Notify

Threshold Alarm

Result Notify

GUIGUI

EM

NE


Remote Patch Installation

NE

FTP Server

GUI

3. Activate

1. Upload

to Server

Mediator

NE EngineSoftware Manager

Local File

2. Download

to NE


www.huawei.com

Thank You

Documents

Owl000104 Imanager m2000 v2 Server o&m Issue 2.1