Skip Headers
Oracle® Communications Network Integrity Optical UIM Integration Cartridge Guide
Release 7.2.2

Part Number E35809-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 About the Cartridge Components

This chapter provides information about the components of the Oracle Communications Network Integrity Optical UIM Integration cartridge.

The Optical UIM Integration cartridge contains the following actions:

Discover Enhanced Huawei U2000 Action

The Discover Enhanced Huawei U2000 action extends the Discover Huawei U2000 action (from the Optical TMF814 CORBA cartridge) to remodel the discovered logical device hierarchy into a Network Device model hierarchy. This action also remodels the physical device hierarchy into a Huawei OptiX OSN 3500 physical device hierarchy by changing the specification on the equipment objects from TMF814 specifications to Huawei OptiX OSN specifications. When a Huawei specification is not found during remodeling, the original specification is retained.

This discovery action inherits all the processors from the Discover Huawei U2000 action that is included in the Optical TMF814 CORBA cartridge. For information about the inherited processors in this action, see Network Integrity Optical TMF814 CORBA Cartridge Guide.

The Discover Enhanced Huawei U2000 action contains the following processors run in the following order:

  1. CORBA Property Initializer (inherited)

  2. TMF814 CORBA Property Initializer (inherited)

  3. CORBA Connection Manager (inherited)

  4. TMF814 Property Initializer (inherited)

  5. TMF814 Property Customizer (inherited)

  6. Huawei Customizer (inherited)

  7. TMF814 Session Manager (inherited)

  8. TMF814 Device Recorder Initializer (inherited)

  9. TMF814 ME Collector (inherited)

  10. TMF814 Device Modeler (inherited)

  11. TMF814 Equipment Collector (inherited)

  12. TMF814 Equipment Modeler (inherited)

  13. TMF814 PTP Collector (inherited)

  14. TMF814 PTP Modeler (inherited)

  15. TMF814 CPT Discoverer for PTP (inherited)

  16. Huawei MSTP EndPoint Collector (inherited)

  17. Huawei MSTP EndPoint Modeler (inherited)

  18. TMF814 FTP Collector (inherited)

  19. TMF814 FTP Modeler (inherited)

  20. TMF814 CTP Discoverer for FTP (inherited)

  21. Huawei Logical Device Remodeler Processor

  22. Huawei Physical Device Remodeler Processor

  23. TMF814 Device Persister (inherited)

  24. TMF814 Device Recorder Persister (inherited)

  25. TMF814 Cross-Connect Discoverer (inherited)

  26. TMF814 Cross-Connect Modeler (inherited)

  27. TMF814 Topological Link Modeler (inherited)

  28. TMF814 Pipe Persister (inherited)

Figure 2-1 illustrates the processor workflow of the Discover Enhanced Huawei U2000 action.

Figure 2-1 Discover Enhanced Huawei U2000 Action Processor Workflow

Description of Figure 2-1 follows
Description of "Figure 2-1 Discover Enhanced Huawei U2000 Action Processor Workflow"

Huawei Logical Device Remodeler Processor

This processor remodels the TMF814 discovery results into logical device hierarchies.

Huawei Physical Device Remodeler Processor

This processor remodels the physical device hierarchy into a Huawei OptiX OSN 3500 physical device model.

This processor performs the following tasks:

  • If the device model is an OptiX OSN 3500 device, this processor calls the HuaweiOptiXOSN3500Remodeler class.

  • If the device model is not an OptiX OSN 3500 device, this processor does not remodel the physical device hierarchy.

You can easily add other Huawei device remodeler classes into the remodeler when the remodel class is specific to the device.

The following example shows the changes that are made when the HuaweiOptiXOSN3500Remodeler class is called. This flow is used to remodel the physical devices returned by the TMF814 discovery processors.

For each shelf {
  replace specification
  For each slot {
    replace specification
    For each card {
      replace specification
      For each port {
        replace specification
      }
    }
  }
}

Discover Enhanced TMF814 Action

The Discover Enhanced TMF814 action extends the Discover TMF814 action (from the Optical TMF814 CORBA cartridge). This action discovers logical device hierarchies. This action uses the results of a TMF814 discovery scan and then remodels the logical device hierarchy into a Network Device model hierarchy. When a scan is created, configure the scan parameter to not collect equipment.

This discovery action inherits all the processors from the Discover TMF814 action that is included in the Optical TMF814 CORBA cartridge. For information about the inherited processors in this action, see Network Integrity Optical TMF814 CORBA Cartridge Guide.

This action the following processors run in the following order:

  1. CORBA Property Initializer (inherited)

  2. TMF814 CORBA Property Initializer (inherited)

  3. CORBA Connection Manager (inherited)

  4. TMF814 Property Initializer (inherited)

  5. TMF814 Property Customizer (inherited)

  6. Enhanced TMF814 Property Customizer

  7. TMF814 Session Manager (inherited)

  8. TMF814 Device Recorder Initializer (inherited)

  9. TMF814 ME Collector (inherited)

  10. TMF814 Device Modeler (inherited)

  11. TMF814 Equipment Collector (inherited)

  12. TMF814 Equipment Modeler (inherited)

  13. TMF814 PTP Collector (inherited)

  14. TMF814 PTP Modeler (inherited)

  15. TMF814 CPT Discoverer for PTP (inherited)

  16. TMF814 FTP Collector (inherited)

  17. TMF814 FTP Modeler (inherited)

  18. TMF814 CTP Discoverer for FTP (inherited)

  19. Logical Network Device Remodeler

  20. TMF814 Device Persister (inherited)

  21. TMF814 Device Recorder Persister (inherited)

  22. TMF814 Cross-Connect Discoverer (inherited)

  23. TMF814 Topological Link Collector (inherited)

  24. TMF814 Topological Link Modeler (inherited)

  25. TMF814 Pipe Persister (inherited)

Figure 2-2 illustrates the processor workflow of the Discover Enhanced TMF814 action.

Figure 2-2 Discover Enhanced TMF814 Action Processor Workflow

Discover Enhanced TMF814 Action processors
Description of "Figure 2-2 Discover Enhanced TMF814 Action Processor Workflow"

Enhanced TMF814 Property Customizer

This processor sets the modeler processors to model only the logical device tree and not to model the physical device tree.

Logical Network Device Remodeler

This processor remodels the logical device hierarchies from the TMF814 discovery results. This processor removes the TMF814 TPLayer Generic objects from the logical device tree from each DeviceInterface entity and then remaps specifications and attributes. This processor also corrects VC3/VC12 layers.

UIM Detect Huawei Device Discrepancies Action

The UIM Detect Huawei Device Discrepancies action extends two other actions to provide discrepancy detection and automatic discrepancy resolution.

This action extends the Abstract Detect UIM Discrepancies action (from the Network Integrity UIM Integration cartridge) to detect discrepancies while filtering and removing unused attributes and characteristics from the logical and physical device models.

For information about the processors inherited from the Abstract Detect UIM Discrepancies action, see Network Integrity UIM Integration Cartridge Guide.

This action also extends the Auto Resolve Discrepancies action (from the NetworkIntegritySDK cartridge) to provide automatic discrepancy resolution.

For information about the processors inherited from the Auto Resolve Discrepancies action, see Network Integrity Developer's Guide.

This action contains the following processors run in the following order:

  1. UIM Discrepancies Filter Initializer (inherited)

  2. Optical UIM Huawei DD Filters

  3. Discrepancy Detector (inherited)

  4. Check Auto Resolve Selected (inherited)

  5. UIM Auto Resolve Selected Discrepancies

  6. Identify Auto Resolving Discrepancies (inherited)

  7. Prepare Resolving Discrepancies (inherited)

Figure 2-3 illustrates the processor workflow of the UIM Detect Huawei Device Discrepancies action.

Figure 2-3 UIM Detect Huawei Device Discrepancies Action Processor Workflow

Description of Figure 2-3 follows
Description of "Figure 2-3 UIM Detect Huawei Device Discrepancies Action Processor Workflow"

Optical UIM Huawei DD Filters

This processor applies filters to ignore the following types of discrepancies:

  • Missing equipment holder

  • Missing physical port

  • Missing physical device with a TMF814 specification

  • Missing equipment card with a TMF814 specification

UIM Auto Resolve Selected Discrepancies

This processor contains the Java class for the automatic discrepancy resolution manager. The Java implementation class determines the types of discrepancies to be automatically resolved and the resolution logic.

See Network Integrity Developer's Guide for more information about completing the Java implementation class.

UIM Detect TMF814 Device Discrepancies Action

The UIM Detect TMF814 Discrepancies action extends the Abstract Detect UIM Discrepancies action (from the UIM Integration cartridge) to detect discrepancies while filtering and removing unused attributes and characteristics from the logical and physical device models.

For information about the processors inherited from the Abstract Detect UIM Discrepancies action, see Network Integrity UIM Integration Cartridge Guide.

This action contains the following processors run in the following order:

  1. UIM Discrepancies Filter Initializer (inherited)

  2. Optical UIM TMF DD Filters

  3. Discrepancy Detector (inherited)

Figure 2-4 illustrates the processor workflow of the UIM Detect TMF814 Device Discrepancies action.

Figure 2-4 UIM Detect TMF814 Device Discrepancies Action Processor Workflow

Description of Figure 2-4 follows
Description of "Figure 2-4 UIM Detect TMF814 Device Discrepancies Action Processor Workflow"

Optical UIM TMF DD Filters

This processor applies filters to ignore the following types of discrepancies:

  • Missing device interface with a TMF814 specification

  • Media interface specific attributes when comparing for connection termination points. For physical termination point interfaces, it compares as a media interface.

Import Optical from UIM Action

The Import Optical from UIM action extends the Abstract Import from UIM action (from the UIM Integration cartridge). This import action provides extensibility for any features specific to SDH that you want to add. This action imports both physical devices and logical devices from UIM.

For information about the processors inherited from the Abstract Import from UIM action, see Network Integrity UIM Integration Cartridge Guide.

This action contains the following processors run in the following order:

  1. Import UIM Initializer (inherited)

  2. Scan Params Physical Optical UIM Init

  3. Logical Device UIM Finder (inherited)

  4. Physical Device UIM Finder (inherited)

  5. Logical Device UIM Importer (inherited)

  6. Linked Physical Device UIM Importer (inherited)

  7. Logical Device UIM Persister (inherited)

  8. Physical Device UIM Importer (inherited)

  9. Physical Device UIM Persister (inherited)

Figure 2-5 illustrates the processor workflow of the Import Optical from UIM action.

Figure 2-5 Import Optical from UIM Action Processor Workflow

Description of Figure 2-5 follows
Description of "Figure 2-5 Import Optical from UIM Action Processor Workflow"

Scan Params Physical Optical UIM Init

This processor initializes the scan parameters configured by the Network Integrity user in the Network Integrity UI.

Import Logical Optical from UIM Action

The Import Logical Optical from UIM action extends the Abstract Import from UIM action (from the UIM Integration cartridge). This import action provides extensibility for features specific to SDH that you want to add.

Table 2-1 lists the values that are used when configuring the filters in the base class.

Table 2-1 Filter Values

Filter Value

Query Physical Devices

False

Import Related Physical or Logical Device

False

Logical Device Specification

Network Device


For information about the processors inherited from the Abstract Import from UIM action, see Network Integrity UIM Integration Cartridge Guide.

This action contains the following processors run in the following order:

  1. Import UIM Initializer (inherited)

  2. Scan Parameters Optical UIM Initializer

  3. Logical Device UIM Finder (inherited)

  4. Physical Device UIM Finder (inherited)

  5. Logical Device UIM Importer (inherited)

  6. Linked Physical Device UIM Importer (inherited)

  7. Logical Device UIM Persister (inherited)

  8. Physical Device UIM Importer (inherited)

  9. Physical Device UIM Persister (inherited)

Figure 2-6 illustrates the processor workflow of the Import Logical Optical from UIM action.

Figure 2-6 Import Logical Optical from UIM Action Processor Workflow

Description of Figure 2-6 follows
Description of "Figure 2-6 Import Logical Optical from UIM Action Processor Workflow"

Scan Parameters Optical UIM Initializer

This processor initializes the scan parameters configured by the Network Integrity user in the Network Integrity UI.

Resolve Optical in UIM Action

This resolution action extends the Abstract Resolve in UIM action that is included in the UIM Integration cartridge. This action is the basis for discrepancy resolution between discovered data and the data imported from UIM. This action constructs and updates logical device and physical device trees in UIM.

For information about the inherited processors in this action, see Network Integrity UIM Integration Cartridge Guide.

About Recording Mode

The Optical UIM Integration cartridge can be configured to record all discovered MEs, topological links, and cross-connects. The recorded files (ME_Name.me for MEs, EMS_Name.ems for topological links, and EMS_Name.cc for cross-connects) are saved to the Domain_Home/corbaData/Scan_Name/EMS_Name directory, where:

  • ME_Name is the name of the ME.

  • EMS_Name is the name of the EMS.

  • Domain_Home is the Oracle WebLogic Server domain directory in which Network Integrity is installed.

  • Scan_Name is the name of the scan.

If the TMF814 scan action type has been configured to not discover MEs, topological links, or cross-connects, the corresponding file is not generated.

Recording mode is controlled with the tmf814.properties file in the Domain_Home/config/corbaConfig/ directory. Recording mode can be enabled or disabled by an administrator without needing to restart the server or application. The recording processor reads this file each time it is run.

Enabling Recording Mode

To enable recording mode:

  1. Open the Domain_Home/config/corbaConfig/tmf814.properties file.

  2. Search for the line: MODE=NORMAL

  3. Change NORMAL to RECORD.

  4. Set the CHUNK SIZE entry to the number of cross-connects written to EMS_Name.cc at a time.

  5. Save and close the file.