1 Overview

This chapter describes the Oracle Communications Network Integrity Incremental TMF814 Discovery cartridge.

About the Incremental TMF814 Discovery Cartridge

The Incremental TMF814 Discovery cartridge is an extension to the existing Network Integrity Optical TMF814 CORBA cartridge. See Network Integrity Optical TMF814 CORBA Cartridge Guide for more information.

The Incremental TMF814 Discovery cartridge is dependent on the Optical TMF814 CORBA cartridge. You must import the Optical TMF814 CORBA cartridge before importing the Incremental TMF814 Discovery cartridge in Oracle Communications Design Studio.

The Incremental TMF814 Discovery cartridge can perform a full scan (same as the Optical TMF814 CORBA cartridge) or an incremental discovery scan. In an incremental scan, the Incremental TMF814 Discovery cartridge discovers only the network elements, such as managed elements (MEs), topological links (TLs), and subnetwork connections (SNCs), that have changed in the network since the last discovery scan; thus avoiding the need to discover the entire network. This cartridge allows you to make faster inventory updates by reducing the time taken for network discovery and reconciliation.

The incremental discovery scan retrieves information using an iterative query approach. Address-based discovery retrieves the complete information in a single communication; as a result, the incremental discovery scan is not applicable in such scenarios.

The Incremental TMF814 Discovery cartridge solution explained in this guide discovers and models physical and logical entities for the following vendors: Huawei and ECI.

The Incremental TMF814 Discovery cartridge consists of the following components:

  • NMS Notification Listener Sample Application: This sample application is connected to multiple element management system (EMS) servers or network management system (NMS) servers to listen to event channels and capture the NMS notifications that are generated when network elements are created, updated, or deleted. See "NMS Notification Listener Sample Application" for more information.

  • NetworkIntegritySDK cartridge: The NetworkIntegritySDK cartridge is enhanced to support incremental discovery. See Network Integrity Developer's Guide for more information.

The Incremental TMF814 Discovery cartridge uses the TMF814 CORBA interface as a discovery protocol to connect to the EMS or NMS servers and retrieve information about network elements from that system.

The Incremental TMF814 Discovery cartridge discovers network elements in the network using a TMF814 common object request broker architecture (CORBA) interface. This cartridge provides discovery actions capable of discovering both physical (equipment) and logical (interface) hierarchy details of MEs.

The Incremental TMF814 Discovery cartridge can be used to discover the following network systems:

  • Synchronous Optical Networking (SONET)

  • Synchronous Digital Hierarchy (SDH)

  • Dense Wavelength Division Multiplexing (DWDM)

  • Asynchronous Transfer Mode (ATM)

  • Ethernet

NMS Notification Listener Sample Application

The NMS Notification Listener Sample Application is connected to multiple EMS and NMS servers to listen to event channels and capture the NMS notifications that are generated when network elements are created, updated, or deleted. The NMS Notification Listener Sample Application is a notification listener based on version 1.0.1 of the Object Management Group (OMG) Notification Service specification. The NMS Notification Listener Sample Application supports all the EMS and NMS notification services that are compliant with version 1.0.1 of the OMG Notification Service specification.

You can extend the NMS Notification Listener Sample Application to support vendor-specific EMS and NMS notification services that you may have implemented.

For information about the OMG Notification Service specification, see the OMG Web site at:

http://www.omg.org/spec/NOT/

The Notification Service specification supports event types defined by the OMG Event Service. The OMG Event Service does the following:

  • Supports asynchronous exchange of notification events between clients.

  • Introduces event channels that communicate notification events between suppliers and consumers by issuing standard CORBA requests.

  • Defines two roles for objects:

    • Suppliers: Event Service clients that produce notification events

    • Consumers: Event Service clients that consume and process notification events

The OMG Notification Service specification defines various types of suppliers and consumers. The NMS Notification Listener Sample Application implements the StructuredPushConsumer interface that listens for the notification events of the NMS server and persists the relevant information (such as native EMS names and last modified date and time of MEs, SNCs, and TLs) in standard file format. These text files act as an input to the Discover Incremental TMF814 scan, which does the following:

  • Identifies and retrieves only those network elements (from NMS Server) that have changed in the network since the last discovery scan and displays them in the scan results

  • Copies the unmodified network elements from the previous successful scan and displays them in the scan results

The NMS Notification Listener Sample Application uses OMG CORBA Notification Service standard APIs to connect to the NMS. You must install and set up the Notification Listener Sample Application to receive notification events from the NMS and to communicate the events to Network Integrity. The Notification Listener Sample Application is packaged separately and is available along with the NetworkIntegritySDK cartridge project. You must change the Notification Listener Sample Application configuration using a Java editor to connect to the NMS server and receive its notification events.

See "NMS Notification Listener Sample Application Reference" for more information about the example code for the NMS Notification Listener Sample Application.

About Cartridge Dependencies

This section provides information about dependencies that the Incremental TMF814 Discovery cartridge has on other entities.

Run-Time Dependencies

There are no run-time dependencies for this cartridge.

Design Studio Dependencies

To load the Incremental TMF814 Discovery cartridge into Oracle Communications Design Studio, the following cartridge projects must be installed:

  • TMF814Discovery_Cartridge

  • Abstract_CORBA_Cartridge

  • NetworkIntegritySDK

  • Address_Handlers

  • ora_uim_model

Opening the Cartridge Files in Design Studio

To review and extend the Incremental TMF814 Discovery cartridge, download the Incremental TMF814 Discovery cartridge ZIP file from the Oracle software delivery Web site:

https://edelivery.oracle.com/

The Incremental TMF814 Discovery cartridge ZIP file has the following structure:

  • \UIM_Cartridge_Projects\TMF814_Model

  • \Network_Integrity_Cartridge_Projects\Incr_TMF814_Disc_Cartridge

The Incr_TMF814_Disc_Cartridge project contains the extendable Design Studio files.

You must open the files in Design Studio before you can review and extend the cartridge.

See Network Integrity Concepts for guidelines and best practices for extending cartridges. See Network Integrity Developer's Guide for information about opening files in Design Studio.

Building and Deploying the Cartridge

See the Design Studio Help for information about building and deploying cartridges.