To configure the NI_UIM webservice:

1. Go to the domain path <domain>/UIM/app/7_5_1.
2. Download custom.ear from https://edelivery.oracle.com
3. Update custom.ear with the latest NI_Uim.war file.
4. Login to the console and update custom.ear.

For this action, the result category is Services and type is Abstract.

For this action, the result category is Services and type is Main.

For this action, the result category is Discover WDM Services (Services) and type is Normal.

For this action, the lable is Reconcile WDM Services to UIM, result source is Discover WDM Services (Services) and type is Normal.

Grooming a DWDM connectivity is changing the design path of a connectivity by either changing segment's channel within a facility or to a channel from different facility. For example, when you groom a ODU4 connectivity, you change the OTU channel within same OTU facility or to a OTU channel from different OTU facility.

The groom feature can also be used for:

• Reallocating bandwidth to ensure optimal usage
• Consolidating traffic to make better use of high-capacity links
• Upgrading equipment with newer, more capable devices

Grooming frequently happens due to network modifications that introduce new routes or render existing ones less effective. For example, the addition of new devices to a network might cause existing routes to have unacceptable number of hops. Planning and management procedures identify such scenarios and recommend more efficient routing adjustments through grooming. For more information, see "Maintaining Channelized Connectivity and Network Resources" in UIM Concepts Guide.

UIM exposes a Groom API via the REST protocol. Network Integrity identifies design path discrepancies for each connectivity rider, triggering a groom request and calling UIM's Groom endpoint. Upon receiving the groom request, UIM promptly acknowledges it with a 202 response and processes it in the background. Network Integrity then regularly checks UIM for a Groom response and addresses the discrepancies accordingly.

For more information on how to invoke Groom REST APIs, see REST API for Unified Inventory Management.

A default API is introduced within the DiscrepancyHandler interface of the UIM_Integration_Cartridge, which takes collections of discrepancies (such as attribute mismatches, missing or extra pipe segments) and the reference pipe entity (either trails or tunnels) as inputs, as shown below. You can use reconciliation handler classes to override this API.

Groom can be used by modifying the necessary segments, or changing channel(s) within existing segments.

public default void handleDiscrepancyGroom(Collection<DisDiscrepancy> missingEntity, Collection<DisDiscrepancy>
        extrEntity, Collection<DisDiscrepancy> attributeMismatch, Pipe pipe) {
   }

The input to the API is passed from the oracle.communications.integrity.uim.resolutionprocessors.base.BaseResolutionElement class within the UIM_Integration_Cartridge. This class has the logic to group discrepancies respective to the attribute mismatches, missing or extra entities, and reference root entities for each result group.

The oracle.communications.integrity.dwdm.logical.assimilation.service.handler.DWDMLogicalEntityPipeDiscrepancyHandler OOB reconciliation handler has the logic to groom DWDM layers.

When you rehome a connectivity, you alter one of its endpoints. This action may be necessary for load balancing purposes or due to the removal or replacement of devices and interfaces. For more information, see "Maintaining Channelized Connectivity and Network Resources" in UIM Concepts Guide.

The rehome feature can also be used for:

• Moving customer connections to different network nodes to improve service quality
• Physical moving network devices to different location
• Switching network services from one provider to another
• Shifting network resources, such as IP addresses or bandwidth, to different parts of the network.

Rehoming a facility requires changes to the termination of the facility itself and to any channels it provides. Channels are re-terminated on sub-device interfaces provided by the new device interface on which the facility is terminated.

UIM exposes a Rehome API over REST protocol. Network Integrity detects such port change discrepancies for each connectivity facility and generates a Rehome request and invokes Rehome endpoint of UIM. Upon receiving the rehome request, UIM immediately acknowledges with a 202 response and processes it in the background. Network Integrity then regularly checks UIM for a Rehome response and addresses the discrepancies accordingly.

For more information on how to invoke Rehome REST APIs, see REST API for Unified Inventory Management.

A default API is introduced within the DiscrepancyHandler interface of the UIM_Integration_Cartridge, which takes a collection of discrepancies (such as missing or extra pipe or PTP entities) as input, as shown below. The design path can be modified by making device changes or termination point changes on one side.

public default void handleDiscrepancyRehome(DisDiscrepancy missingEntity, DisDiscrepancy extrEntity) { 
}

The input to the API is passed from the oracle.communications.integrity.uim.resolutionprocessors.base.BaseResolutionElement class within the UIM_Integration_Cartridge. This class has the logic to group discrepancies respective to the missing or extra entities for each result group.

The oracle.communications.integrity.dwdm.logical.assimilation.service.handler.PipeTerminationPointHandler OOB reconciliation handler has the logic to rehome DWDM layers.

To configure Import System in NI:

1. Open Manage Import System in NI.
2. Under Import System Details, enter the following:
   1. Enter Name as Import.
   2. Enter the required address.
   3. Enter your User Name and Password.
3. Press Enter from your keyboard.

   The Import System is configured in NI.

4. Verify using the Webservice test URL:

   http://<ip>:<port>/NI_Uim/NI_UimHTTP

To run the DWDM Import scan:

1. Go to the Manage Scan page in NI.
2. Click Create Scan.
3. On the Create Scan page provide following:
   • Name: Name of the scan.
   • Enabled: Select to run the scan.
   • Scan Action: Select Import WDM Services from UIM.
4. Under Scan Action Parameters, select Scan Parameter Group as WDM Service Parameters for WDM Service Parameters and provide the corresponding parameters.
5. Under Scan Action Parameters, select Scan Parameter Group as Parallel Process Parameters for Parallel Process Parameters and provide the corresponding parameters.

   Note:

   By default, Parallel Process is enabled along with the thread count configured at time of NI installation.
6. Click Save and Close.
7. Run the Import scan.

   The scan results appear.

To detect discrepancy between DWDM discovered and imported data:

1. Open Manage Scans.
2. From the list of scans, select the required DWDM Discovery scan.
3. Click Edit.
4. Under the General tab, select Detect Discrepancies.
5. Run the scan.

   The scan results appear.

6. Click Review Discrepancies.

   The Review Discrepancies page appears as shown in the following figures.

Description of the illustration img_reviewdiscrepancies.png

Description of the illustration img_clientlayer_discrepancy.png

Description of the illustration img_ochlayer_discrepancy.png

To resolve discrepancies:

1. Before resolving a discrepancy, ensure that DWDM physical layer data is present in UIM.
2. Usually, the cartridge that discovers and reconciles physical layer data such as device, shelf, card, port, device interface, and so on, already exists. Only then, the logical layer discover and reconciliation happens.

You must perform reconciliation in the following order:

1. OCH layer: The action for OCH layer reconciliation is Reconcile WDM Services.
2. Client layer: The action for client layer reconciliation is Reconcile WDM services

   Note:

   You must perform Client layer reconciliation only after performing OCH layer reconciliation.

   The following figure shows a sample of reconciliation results.

   
   
   
   Description of the illustration img_recon_result.png
   
   
3. Verify the reconciled data in UIM.

To verify the reconciled data between UIM and NI:

1. Go to Manage Scans.
2. Run an Import scan.
3. Verify the scan results.
4. Verify the results for all layers.
5. Verify if the network data and UIM data is in synchronization as follows:
   1. Run a Discovery scan with Detect Discrepancy enabled.
   2. Check the scan results.
6. If the data under Discrepancy Counts columns shows zeros, the discovered data created in UIM is correct as shown in the following sample.

Description of the illustration img_discrepancy_zero_detection.png

The prerequisite for running an incremental import scan is:

• Collect DWDM logical layer notification from NMS/EMS system using NMS listener.

To run an incremental import scan:

1. Go to Manage Scans in NI.
2. Open a required import scan.
3. Click Edit.

   The Edit Scan page appears.

4. Under Scan Action Parameters, select Scan Parameter Group as IncrementalScanParameter.
5. Enter the corresponding parameters for the selected group.
6. Run the scan.

   The scan results appear.

7. Verify if the scan status is changed from INITIAL to IMPORTED.

If UIM has a DWDM hierarchy and it is removed from the network, the corresponding discrepancies appear when you run the Discrepancy Detection Entity.

Perform the tasks in the following order for resolution:

1. Address the entity disparity on the client layer.
2. OCH layer discrepancy is the next resolved entity.

In UIM, the SNC hierarchy is generated in a different sequence than its deletion. When an entity + is created, it is resolved on the OCH layer first, and then it is resolved on the client layer. The top layer is erased first, followed by the child layer, while deleting.

Run the import and discovery scan again after resolving the entity discrepancy.

You can filter DWDM data during discovery and import scans by defining the Nms Notification Vendor and Nms Notification Circle parameters. This ensures that only data matching these criteria will be available in the scan results. When reconciling this data with UIM, the pipe and connectivity will include both vendor and circle as characteristics.

To reconcile DWDM data based on vendor and circle parameters:

1. Create a DWDM import scan with the requisite Nms Notification Vendor and Nms Notification Circle parameter values and run the scan.

2. Create a DWDM discovery scan with the requisite Nms Notification Vendor and Nms Notification Circle parameter values and run the scan with discrepancy detection enabled.

   Note:

   Ensure that the Nms Notification Vendor and Nms Notification Circle parameter values entered in both import and discovery scans are the same.

3. Perform the OCH layer reconciliation first. Then perform the reconciliation of the client group.

4. Verify the reconciled data by using the same Nms Notification Vendor and Nms Notification Circle parameter values. See "Verifying Reconciled Data between UIM and NI" for more information on verifying reconciled data.