NETWORK OBJECT MANAGEMENT

1. NETWORK OBJECT MANAGEMENT

2. 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. CORBA For Network Management IIOP TCP IP Link Layer Physical Layer

3. 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

4. CORBA Based Network Management Architecture • Embedded Realtime Kernels • Interacts both with database & facilities. • Multitasking, prioritization, DB sync. ACCT. MGMT SEC. MGMT FAULT MGMT PERF. MGMT CONF. MGMT NETWORK ELEMENT CORBA AGENT MANAGEMENT APPLICATIONS CORBA INTERFACE CORBA DATA BASE INTERFACE USER INTERFACE DATA BASE DATA BASE INTERFACE DATA BASE CORBA MANAGER MANAGEMENT STATION APPLICATION MODULES MANAGER SERVER FAULT MGMT PERF. MGMT CONF. MGMT • UNIX, NT Work Stations • Management Applications • User Interfaces • Remote Login MANAGED RESOURCE INTERFACE FACILITIES

5. 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.

6. 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

7. 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

8. 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. 3 Dimensions of Network Management Applications Interface Application Database

9. 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) Objects in OM2000 EMS CORBA AGENT INTERFACE OBJECTS DB DATABASE OBJECTS APPLICATION OBJECTS FACILITIES

10. Information Modeling in OM2000 UML MODEL GDMO MODEL SNMP MIB GDMO/SNMP COMPILER UML CASE TOOL JIDM/OM2000 INTERACTION TRANSLATION IDL CORBA IDL DEFINITIONS UML TEXTUAL REPRESENTATION CORBA AGENT APPLICATION CLASSES CORBA IDL IMPLEMENTATIONS UML TEXT COMPILER CORBA IDL DEFINITIONS CORBA AGENT CUSTOMIZATION CORBA AGENT APPLICATION CLASSES CORBA AGENT CORBA PLATFORM OM2000 CORE OM2000 Provided/Generated REALTIME KERNEL MISC. S/W C++ etc. OM2000 User Provided/Developed Third Party Software

11. OM2000 Agent Components Object Factory CORE API Database I/F Request Handling Mgmt Info Rep. Memory Mgmt CORBA I/F Thread Mgmt SNMP I/F MIT TCL GDMO ASN.1 RULES UML SMF : Alarm LOG EFD AGENT TESTER COMPILERS Scope Proc. CORBA IDL C++ IMPL DB SCHEMA Meta Data Filter Proc. Data Valid/Manip APPL C++ SERVER C++ Third Party DB Engine Trace/Mon Facility Database

12. OM2000 Compiler .CPP .CPP .IDL .SCM .CPP .H .CPP .OWS .ORF .DRF .DWS .H objcom META DATA SCHEMA CORBA IDL IDL SERVER IMPL DEFAULT OBJECT IMPL DEFAULT OBJECT IMPL HEADER User Input data model APPLICATIONSPECIFIC USERIMPLEMENTATION Generated for OM2000 internal use Generated for application use User Application Implementation

13. 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.

14. 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.

15. 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. Fine-Grained Agent Implementation EMS CORBA AGENT INTERFACE OBJECTS DB DATABASE OBJECTS APPLICATION OBJECTS FACILITIES

16. 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. Coarse-Grained Agent Implementation EMS CORBA AGENT INTERFACE OBJECTS DB DATABASE OBJECTS APPLICATION OBJECTS FACILITIES

17. 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. Service Oriented Agent Implementation EMS CORBA AGENT INTERFACE OBJECTS DB DATABASE OBJECTS APPLICATION OBJECTS FACILITIES

18. 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 System Management Functions EMSs CORBA AGENT PM EFD Alarm EFD Alarm LOG PM LOG INTERFACE OBJECTS DB DATABASE OBJECTS APPLICATION OBJECTS FACILITIES

19. 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 Example of OM2000 Usage EMS CORBA AGENT INTERFACE OBJECTS DB DATABASE OBJECTS APPLICATION OBJECTS CALLPROC. UPDATE CARD OTHER TASKS/MODULES FACILITIES

20. 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)

21. 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 Agent Testing SCRIPT FILE RESULTS FILE SCRIPT FILE AGENT TESTER IIOP CORBA AGENT OTHERTASKS NETWORK ELEMENT

22. 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.

23. OM2000 in Element Managers ACCT. MGMT SEC. MGMT FAULT MGMT PERF. MGMT CONF. MGMT NETWORK ELEMENT MANAGEMENT APPLICATIONS FACILITIES DATA BASE INTERFACE USER INTERFACE CORBA AGENT DATA BASE CORBA CORBA MANAGER ELEMENT MANAGER ELEMENT MANAGER SERVER • 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.

24. OM2000 Supported Platforms