This chapter explains how to use the Oracle Communications Network Integrity Incremental TMF814 Discovery cartridge.
The Incremental TMF814 Discovery cartridge allows you to create a Discover TMF814 scan.
To create an Incremental TMF814 Discovery scan:
Create a scan, as explained in the Network Integrity Help.
On the General tab, from the Scan Action list, select Discover Incremental TMF814 to discover only the modified network elements (MEs, SNCs, and TLs) from the network management system.
The Scan Type field displays Discovery.
Under the Scan Action Parameters area, from the Select Parameter Group list, select the following:
Select TMF814Parameters and enter the following TMF14 scan action parameters:
In the Username field, enter the username for the target element or network management system (EMS or NMS).
In the Password field, enter the password for the target EMS or NMS.
In the EMS Naming Service field, enter the EMS session factory CORBA object name.
From the EMS Naming Service Format list, specify whether the EMS session factory CORBA object name uses the Plain, or the Stringified format.
From the Collect Equipment list, specify whether you want to collect equipment holder objects.
From the Collect Termination Points list, specify the type of termination points (TPs) you want to collect. To not collect any TPs, select None.
From the Collect Connection TP list, specify the type of connection TPs you want to collect. To not collect any connection TPs, select None.
(Optional) To set the number of equipment objects to retrieve with each EMS call, enter a value in the Equipment Fetch Size field. Leave this field blank to retrieve all equipment objects in a single EMS call.
(Optional) To set the number of TPs to retrieve with each EMS call, enter a value in the Termination Point Fetch Size field. Leave this field blank to retrieve all TPs in a single EMS call.
(Optional) To set the number of hierarchical child levels to which contained TPs are collected, enter a value in the Contained TP Collection Depth field. Leave this field blank to retrieve all contained TPs.
(Optional) To pass custom object request broker (ORB) properties to the Discover Abstract TMF814 action, enter name value pairs in the ORB Properties field, separated by a semicolon, as in the following example:
Property_1=value_1;Property_2=value_2;Property_n=value_n
(Optional) To pass custom ORB arguments to the Discover Abstract TMF814 action, enter name value pairs in the ORB Arguments field, separated by a semicolon, as in the following example:
Argument_1=value_1;Argument_2=value_2;Argument_n=value_n
(Optional) To filter the discovered managed elements (MEs) by name, enter a name in the Managed Element Name(s) field and set the Managed Element Name Qualifier list.
(Optional) To filter the discovered network elements (NEs) by name, enter a name in the Network Element Name(s) field and set the Network Element Name Qualifier list.
In the Cross Connect Collection Type field, specify how cross-connect objects are collected. Irrespective of whether you select SNC or ME list, only the SNC option is considered for fetching cross-connects. To not collect any cross-connect objects, select None.
In the Topological Link Collection Type field, specify how topological links are collected. To not collect any topological links, select None.
See Table 6-3, "TMF814 Scan Parameters Design Studio Construction" for more information.
(Optional) Select AutoResolutionParameter and then select the Auto Resolve Discrepancies check box to initiate automatic discrepancy resolution at the end of the scan. Automatic discrepancy resolution works only if the Detect Discrepancies option is also selected. See Network Integrity Developer's Guide for more information.
(Optional) Select IncrementalScanParameter and then select the Incremental Scan check box.
On the Scope tab, do one of the following:
Enter the EMS CORBA Loc URL.
Import the IOR file.
Enter the content of the IOR file.
Note:
All entries on the Scope tab must be unique. All entries are validated against the CorbaURLAddressHandler address handler.On the Schedule tab, define a schedule for the scan.
See the Design Studio Modeling Network Integrity Help for more information on defining a scan schedule.
Make any other required configurations.
Click Save and Close.
You may be required to extend the existing Incremental Discovery cartridge (sample NMS listener application) to support different protocols used by vendor-specific EMS and NMS notification services that you may have implemented.
To extend the Incremental Discovery Cartridge to support different protocols used by an EMS or NMS:
Continuously monitor the changes made to the network devices by listening to the notifications of the EMS or NMS.
Enhance the discovery cartridge by adding a new discovery processor that does the following:
Checks the text file generated by the notification listener for the list of devices that are modified after the previous scan by going through the device tracking file
Fetches only the modified devices from the network
Copies the unmodified devices from the previous scan
Removes the unmodified devices from the list of devices to be discovered