| Oracle® Communications Network Integrity Optical UIM Integration Cartridge Guide Release 7.2.2 Part Number E35809-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Communications Network Integrity Optical UIM Integration Cartridge Guide Release 7.2.2 Part Number E35809-01 |
|
|
PDF · Mobi · ePub |
This chapter describes the components of Oracle Communications Network Integrity Optical UIM Integration cartridge.
The Optical UIM Integration cartridge is composed of the following actions, each containing several processors:
This discovery action extends the Discover Huawei U2000 action that the Optical TMF814 CORBA cartridge contains. The extended discovery action uses the results of a TMF814 discovery scan and then remodels the logical device hierarchy into a Network Device model hierarchy. The 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.
In addition to the processors inherited from the Discover Huawei U2000 action, this action contains the following processors:
Figure 2-1 shows the processor workflow of the Discover Enhanced Huawei U2000 action.
This processor remodels the TMF814 discovery results into logical device hierarchies.
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
}
}
}
}
This discovery action extends the Discover TMF814 action that the Optical TMF814 CORBA cartridge contains. The intent of this action is to discover logical device hierarchies. The extended discovery 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.
In addition to the processors inherited from the Discover TMF814 action, this action contains the following processors:
Figure 2-2 shows the processor workflow of the Discover Enhanced TMF814 action.
This processor sets the modeler processors to only model the logical device tree, and not to model the physical device tree.
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 and then remaps specifications and attributes. This processor also corrects VC3/VC12 layers.
This discrepancy detection action extends the Abstract Detect UIM Discrepancies action that is included in the UIM Integration cartridge. The discrepancy detection action filters and removes unused attributes and characteristics from the logical device and physical device models.
This action applies the following filters:
Ignore missing equipment holder
Ignore missing physical port
Ignore missing physical device that has TMF814 specifications
Ignore missing equipment card that has TMF814 specifications
This action inherits all the processors from the Abstract Detect UIM Discrepancies action that is part of the UIM Integration cartridge. For information about the inherited processors in this action, see Network Integrity UIM Integration Cartridge Guide.
This discrepancy detection action extends the Abstract Detect UIM Discrepancies action that is included in the UIM Integration cartridge. The discrepancy detection action filters and removes unused attributes and characteristics from the Logical Device model.
This action applies the following filters in addition to the filters which are inherited from the Abstract Detect UIM Discrepancies action:
Ignore missing device interface that has TMF814 specifications
TMF814 discovery creates all CTP interfaces as media interface. The processor ignores any media interface specific attributes when comparing for CTPs. For PTP interfaces, it compares as a media interface.
This action inherits all the processors from the Abstract Detect UIM Discrepancies action that is part of the UIM Integration cartridge. For information about the inherited processors in this action, see Network Integrity UIM Integration Cartridge Guide.
This import action extends the Abstract Import from UIM action that is included in the UIM Integration cartridge. The import action provides extensibility for any features specific to SDH that you want to add. This action contains the same UI scan parameters as the Import from UIM action, which is included in the UIM Integration cartridge. You run this action to import both physical devices and logical devices from UIM.
This action inherits all the processors from the Abstract Import from UIM action that is part of the UIM Integration cartridge. For information about the scan parameters and the inherited processors in this action, see Network Integrity UIM Integration Cartridge Guide.
This import action extends the Abstract Import from UIM action that is included in the UIM Integration cartridge. This import action provides extensibility for features specific to SDH that you want to add and to also limit the UI scan parameters to those that are relevant to logical import only.
The UI scan parameters in this action have the following fields available:
Name
Inventory State
Network Location/Entity Code
Table 2-1 lists the values that are used when configuring the filters in the base class.
| Filter | Value |
|---|---|
|
Query Physical Devices |
False |
|
Import Related Physical or Logical Device |
False |
|
Logical Device Specification |
Network Device |
This action inherits processors from the Abstract Import from UIM action that is part of the UIM Integration cartridge.
For information about the inherited processors in this action, see Network Integrity UIM Integration Cartridge Guide.
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.
This action inherits all the processors from the Abstract Resolve in UIM action that is part of the UIM Integration cartridge. For information about the inherited processors in this action, see Network Integrity UIM Integration Cartridge Guide.
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 managed element.
EMS_Name is the name of the EMS.
Domain_Home is the directory in which the WebLogic domain is configured.
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 WeLogic_Domain_Home/config/corbaConfig/ directory. Recording Mode can be enabled or disabled by an administrator without needing any server or application restart. The recording processor reads this file each time it is run.
|
 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
