network object management

EzNetSoft 031-422-4220 1

OM2000 OM2000 ArchitectureArchitecture

NETWORK OBJECT MANAGEMENT

Trigon Technology Group /EzNetSoft, Inc. Confidential

CORBA For Network Management

General Advantages: Widely used middle ware Standard mappings to

programming languages Uses Internet Inter ORB Protocol

over TCP/IP (short stack) Availability of small foot print

implementations on embedded systems.

Data Modeling Advantages: OMG UML provides a powerful

data modeling framework over CORBA

Standard translation algorithms to translate GDMO & SNMP to IDL.

IIOP

Physical Layer

Link Layer

IP

TCP


CORBA Services

Naming Service : Provides a facility for registering and the location of the objects

Life Cycle Service: Provides a facility for creating, copying and moving objects

Notification Service: Provides a facility for sending events to the subscriber for the events

Log Service: Provides a facility for logging events Query Service: Provides a facility for Query Operation for a

collection of objects Persistent Object Service: Provides a facility for storing

objects


CORBA Based Network Management Architecture

NETWORK ELEMENT

PERF.MGMT

CONF.MGMT

FAULTMGMT

MANAGED RESOURCE INTERFACE

APPLICATION MODULES

CORBA AGENT

FACILITIES

CORBA

DATA BASE INTERFACE

DATABASE

MANAGER SERVER

CORBA MANAGER

PERF.MGMT

CONF.MGMT

FAULTMGMT

MANAGEMENT APPLICATIONS

USER INTERFACE

MANAGEMENT STATION

DATA BASE INTERFACE

ACCT.MGMT

SEC.MGMT

DATABASE

CORBA INTERFACE

• UNIX, NT Work Stations• Management Applications• User Interfaces• Remote Login

• Embedded Realtime Kernels• Interacts both with database & facilities.• Multitasking, prioritization, DB sync.


Network Management CORBA IDL

CORBA IDL for Network Management has the following operations: Create : This operation is used to create an object in the agent. Delete : This operation is used to delete an object. Set : This operation is used to modify the attributes of a given

object or group of objects in the agent. Get : This operations is used to retrieve the attributes of a given

object or group of objects in the agent. Action : This operations is used to perform object specific

operation on a given object or a group of objects in the agent. Notification : This operation is used by the agent to inform the

manager of an alarm condition, state change or other events in the agent.


OM2000 Design Goals

Small agent application code size Limited runtime memory utilization. Optimization of CPU Usage

efficient conversion between protocol representation and internal representation, if possible use same representation

Multiple threads Minimize incoming and outgoing traffic

Scoping and Filtering System Management Functions

Powerful data model to represent complex information in the agent Efficient data storage and retrieval from persistent storage

avoid conversion between encoded formats to in-memory formats Redundant processor & database Secure access to agent database Support for legacy and craft interface development


OM2000 Design Goals ..contd

Efficient implementation of scoping, filtering and system management functions

Consistent data representation Agent and other modules use same data types

Easy access to data base by other modules Avoid need to generate CORBA requests internally to get to agent

data Efficient application development:

API easy to use and debug Incremental development Powerful configuration (number of tasks, semaphores, etc.) Performance collection for fine tuning Flexible tracing and logging to identify problems in the field Testing during development


3 Dimensions of Network Management Applications

Based on the design goals discussed: network management application

development is a three dimensional problem

need to satisfy all the dimensions (interface, database and application)

Interface: data model data access by external systems external traffic management (flow control

etc.) System Management Functions

Database: efficient storage, retrieval, transaction reporting, redundancy, consistency checks

etc. Application:

efficient application development easy access to database multi-threading, priorities, memory

management, tracing, performance collection, testing etc.

Inte

rfac

e

Database

Application


Objects in OM2000

Objects in OM2000 can be divided into three logical categories: Interface objects : interface

with external systems. Database objects : represent

the MIB in the database. Application objects :

implement the behavior associated with the MIB.

The database & application objects are combined together.

Different kinds of interface objects are possible. (influence the flexibility, size and performance of the agent)

EMS

FACILITIES

DB

INTERFACE OBJECTS

DATABASE OBJECTS

APPLICATION OBJECTS

CORBA AGENT


Information Modeling in OM2000

GDMOMODEL

GDMO/SNMPCOMPILER

SNMPMIB

CORBAIDL

DEFINITIONS

CORBAIDL

IMPLEMENTATIONS

UMLMODEL

UML TEXT COMPILER

UMLCASETOOL

CORBAIDL

DEFINITIONS

CORBAPLATFORM

REALTIME KERNEL

MISC. S/WC++ etc.

CORBAAGENT

CUSTOMIZATION

CORBA AGENTAPPLICATION

CLASSES

CORBA AGENTAPPLICATION

CLASSES

CORBAAGENT

OM2000CORE

UMLTEXTUAL

REPRESENTATION

OM2000 Provided/Generated

OM2000 User Provided/Developed

Third Party Software

JIDM/OM2000INTERACTION

TRANSLATION IDL


OM2000 Agent Components

Database

COMPILERS

Th

ird P

arty DB

En

gine

COREAPI

DatabaseI/F

Scope Proc.

Filter Proc.

DataValid/Manip

Mgmt Info Rep.

Trace/MonFacility

CORBAI/F

MemoryMgmt

RequestHandling

ThreadMgmt

MIT

ObjectFactory

AGENTTESTER

TCL

MetaData

SMF : Alarm LOG EFD

SNMPI/F

RULESGDMOASN.1 UML

CORBAIDL

DBSCHEMA

C++IMPL

SERVERC++

APPLC++


OM2000 Compiler

objcom

SCHEMA

APPLICATIONSPECIFIC

USERIMPLEMENTATION

CORBA IDL IDLSERVER

IMPL

META DATA DEFAULTOBJECT

IMPL

DEFAULTOBJECT

IMPLHEADER

Generated for application use

Generated for OM2000 internal use

User Input data model

User Application Implementation

.CPP .SCM .IDL .CPP .CPP .H

.H.CPP

.ORF .OWS .DRF .DWS


OM2000 Compiler Input Object Rule File (.orf) :

includes all the object specification files for the application (.odl, .mo, .mib)

contains rules for aliasing, fine-graining, etc.

Object Working Set (.ows):

specifies all the objects that are implemented by the application

Data Rule File (.drf):

include all the data type specification files for the application (.ddl, .asn)

contains rules for aliasing, etc.

Data Working Set (.dws):

specifies all the data types that used by the application.


External Interface Types

Object Oriented: Application & Database objects are made visible to external systems. Operations are performed on individual or groups of objects. Management systems have knowledge of objects in the Agent. Support scoping and filtering. Support arbitrary object selection. Support bulk object retrieval.

Service (Function) Oriented: Application & Database objects in the agent are not exposed on the external

interface. Services provided by the agent (or functions that can be performed by a

management system user) are modeled as external interface objects & methods.

Support bulk object retrieval. Hidden support for scoping and filtering, arbitrary object selection.


Fine-Grained Agent Implementation

Application/database objects are exposed to external systems.

Each application/database object has a corresponding interface object.

The interface objects provide methods to access the data and exercise the services offered by the managed object.

Suitable for small scale agent applications.

EMS

FACILITIES

DB

INTERFACE OBJECTS

DATABASE OBJECTS

APPLICATION OBJECTS

CORBA AGENT


Coarse-Grained Agent Implementation

Application/database objects are exposed to external systems.

Only one external interface object which mediates access to individual application objects.

Suitable for large scale agent applications.

EMS

FACILITIES

DB

INTERFACE OBJECTS

DATABASE OBJECTS

APPLICATION OBJECTS

CORBA AGENT


Service Oriented Agent Implementation

Application/database objects are not exposed to external systems.

One or more external interface objects provide access to database/application objects.

Suitable for small scale to medium scale agent applications.

EMS

FACILITIES

DB

INTERFACE OBJECTS

DATABASE OBJECTS

APPLICATION OBJECTS

CORBA AGENT


System Management Functions

Event Forwarding Routing to multiple

destinations Filtering of Events (Future) Filtering of Destinations

(Future) Prioritization of alarms Vs PM

Vs Other (Future) Event Log

Log capacity control Filtering of Events (Future) Prioritization of alarms Vs PM

Vs Other (Future) Automatic persistent storage of

LOGs

EMSs

FACILITIES

DB

INTERFACE OBJECTS

DATABASE OBJECTS

APPLICATION OBJECTS

CORBA AGENT

AlarmEFD

AlarmLOG

PMEFD

PMLOG


Example of OM2000 Usage

Modules other than agent need access to information in the agent database Call processing Update new cards plugged in Local craft interfaces

Database access should not require going through the external

interface should be able to directly get to and use the

database objects should be shielded from external interface

mechanisms and data storage mechanisms should be able to create and manage

collections of frequently accessed objects

bbbb

EMS

FACILITIES

DB

INTERFACE OBJECTS

DATABASE OBJECTS

APPLICATION OBJECTS

CORBA AGENT

CALLPROC.

UPDATECARD

OTHER TASKS/MODULES


Example of OM2000 Usage Con’t

Examples:

Craft Inteface can be used to activate new line cards inserted

in a slot. The activation can trigger an insert operation of an

object in the data base

Call Processing Systems will access some information in the

data base to build Call Detail Record ( CDR)


Agent Testing

Support all interfaces (coarse grain, etc.) Support scripting

construction of requests from scripts looping constructs (e.g, TCL)

Support detailed analysis of responses read individual data elements compare with expected results

Load generation agent tester cannot be the bottle neck

Script generation rule based stress the database stress the different performance

points

CORBA AGENT

NETWORK ELEMENT

OTHERTASKS

AGENTTESTER

IIOP

SCRIPTFILE

SCRIPTFILE

RESULTSFILE


Existing Model Deployment

Vast body of existing models in CMIP & SNMP re-doing will result in lost time & effort investment of new resources & effort to solve it a

second time Translation Algorithms

Joint Inter Domain Management (JIDM) defined translation algorithms to translate CMIP, SNMP -> IDL

Other application requirements discussed so far remain the same.


OM2000 in Element Managers

NETWORK ELEMENT

ELEMENT MANAGER SERVER

CORBA MANAGER

PERF.MGMT

CONF.MGMT

FAULTMGMT

MANAGEMENT APPLICATIONS

USER INTERFACE

FACILITIES

CORBA

ELEMENTMANAGER

DATA BASE INTERFACE

ACCT.MGMT

SEC.MGMT

DATABASE

CORBAAGENT

• Element Manager server has same functionality as an agent.• Only difference being the information content in the Element Management Database.• GUI clients can communicate with the element manager server using CORBA.• A well designed CORBA agent framework can be easily deployed on an element management system with ease.• The stringent requirements of an embedded agent when present in the element manager server will result in faster element management solutions.


OM2000 Supported Platforms

OS ORB Database Status

Windows NT IONA Orbix PsePro Current

Windows NT Visibroker PsePro Current

pSOS HighComm Raima Current

VxWorks HighComm Raima Current

Solaris IONA Orbix PsePro Future

Solaris Visibroker PsePro Future

network object management

Documents