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
PDF · Mobi · ePub

8 About Design Studio Extension

This chapter provides examples for extending certain aspects of the Oracle Communications Network Integrity Optical UIM Integration cartridge using Oracle Communications Design Studio.

You can modify any part of the code to customize the cartridge for your business and operational requirements. For more information about cartridge extension, see UIM Developer's Guide.

For guidelines and best practices for extending cartridges, see Network Integrity Concepts.

This chapter describes the following examples:

Using a Different Vendor

This section describes how to use a different vendor using TMF814 discovery for integration with the Optical UIM Integration cartridge.

To use a different vendor:

  1. Extend the Discover TMF814 discovery action to add the following processors. See Design Studio Help for instructions about extending actions in Oracle Communications Design Studio.

    • vendor Logical Device Remodeler, which calls the LogicalNetworkDeviceRemodelerHelper class. Replace vendor with the name of the vendor you want to use.

    • vendor Physical Device Remodeler, which remodels the TMF814 equipment model into your vendor-specific equipment specifications. Replace vendor with the name of the vendor you want to use.

  2. Relate the Optical UIM resolution actions to your new discovery action.

  3. Relate the UIM Detect Huawei Device Discrepancies action to your new discovery action.

Using a Different Discovery Method

This section describes how you can use the Optical UIM Integration cartridge as a reference to using a different discovery method such as the File Transfer and Parsing cartridge or the TL1 cartridge.

To use a different discovery method:

  1. Load the appropriate discovery cartridge into Oracle Communications Design Studio.

  2. Extend the discovery action by remodeling the logical device tree to use the specifications in ora_uim_network_device. See Design Studio Help for instructions on extending actions in Design Studio.

  3. Extend the discovery action by remodeling the physical device tree to use the specifications in the vendor-specific UIM model cartridge that has your equipment model.

  4. Relate the UIM Detect TMF814 Device Discrepancies action to your discovery action. If required, extend this action to perform any filters like the filter used in the UIM Detect Huawei Device Discrepancies action.

  5. Relate the Optical UIM resolution actions to your new discovery actions.

Extending the Cartridge to Support Circuits

This section describes building an SDH circuit integration cartridge for Oracle Communications Unified Inventory Management (UIM). The cartridge uses optical circuit assimilation results. See UIM Developer's Guide to develop a UIM Web service.

To extend the Optical UIM Integration cartridge to support circuits:

  1. Extend the sample UIM Web service to support connectivity entities for the Network Integrity Optical Model.

  2. Create a UIM technology pack with connectivity specifications for the solution.

  3. Extend an import action that is based on existing UIM import actions that also support circuits.

  4. Create discrepancy detection actions.

  5. Extend the discrepancy resolution action based on existing UIM discrepancy resolution actions that also support circuits.

Modeling Considerations

This section describes the modeling considerations for building support for circuits.

Connectivity

Network Integrity and UIM both use a model based on the Oracle Communications Information Model for connectivity. The information model does not contain one-to-one mapping of the UIM model to the Network Integrity model. Follow the UIM connectivity guidelines and best practices within UIM, then perform any required mapping to or from the Network Integrity Optical Model in the Web service layer.

The Network Integrity Optical Model minimizes redundant information in a partitioned result model. As such, it does not make use of signal structure entities, capacity entities, pipe directional entities, or pipe configuration. Capacity, channel information, and directionality are modeled as attributes within Network Integrity. Termination points and trail pipes are referenced directly from a pipe entity, rather than indirectly through pipe configuration.

By default, Network Integrity assumes that the pipes used within the Optical Model terminate on physical ports. The simplest approach is to model objects similarly within UIM. You can also use a logical device interface as the termination point, because it is easily mapped to a physical port.

Because UIM has a unified view of the entire model, pipes directly reference other pipes and termination points. Network Integrity has a partitioned view of the entire model. In Network Integrity, direct references are not typically possible. Network Integrity references a placeholder entity that contains information to identify the actual referenced entity. Examples are device and port identifiers for a termination point.

About Extending the Web Service to Support Circuits

Add appropriate Create, Read, Update, and Delete operations to support pipes and termination points as used in the Optical Model. The existing CRUD operations for physical and logical devices are a good starting point. Mapping between the UIM model and the Network Integrity Optical Model is performed as required.

The Optical Model:

  • Uses the layerRate or rate attributes to specify capacity, but UIM uses signal structure and capacity entities to specify capacity.

  • Uses the directionality attribute instead of the PipeDirectionality entity to specify direction.

  • References the termination port by device and physical port identifier, rather than by a direct relationship.

  • References a channel pipe in a trail path by transport pipe identifier and the channel attribute.

Because the existing filtering is based on the device, and circuits are organized by device in the result group, device-based find operations may be appropriate. For example, finding all topological links modeled on a particular device.

About Importing Circuits

Use the existing Optical UIM Integration import actions as the starting point.

Add additional filter criteria to the scan parameters, if required. For example, you may want to make connectivity import entirely optional, or allow import of topological links, but not transport pipes or circuits.

After retrieving and modeling each device (both logical and physical tree), retrieve and model topological links, transport pipes, and circuits. Use the Web service operations for retrieval. Refer to the Network Integrity MSS Integration cartridge for code examples that model according to the Optical Model.

About Detecting Circuit Discrepancy

Implement appropriate discrepancy detection behavior to compare assimilated circuits with imported SDH circuits. You typically extend the Abstract Optical Circuit Discrepancy Detection action and then add additional filters as needed. The existing MSS Circuit Discrepancy Detection action is a good starting point.

About Resolving Circuit Discrepancies

An existing resolution action in the cartridge is the starting point.

The existing Resolve in MSS action shows how to extend the resolution handler framework to support Optical Model discrepancies. For information about PipeTerminationPointHandler, TrailPathHandler, and EntityCircuitHandler, see Network Integrity MSS Integration Cartridge Guide.

You can choose which discrepancies you want to resolve. You can also choose which discrepancies you want to consider for a manual resolution operation. For example, creating a topological link may involve relationships to network entities that cannot be determined from discovered data. All implemented resolution operations use Web service operations.

Adding Additional Huawei OptiX OSN Cards

This section describes how to add additional Huawei OptiX OSN cards to existing cards.

To add additional Huawei OptiX OSN cards:

  1. Add an equipment (type card) specification.

    If the card has ports, add physical port specifications to the ora_uim_huawei_tdm_network_device cartridge with proper specification relationships between the card and port.

  2. Add new card and port specifications to the Optical UIM model collection.

  3. Add a new card specification to the list in HuaweiOptiXOSN3500EquipSpecHelper.java.

  4. Add a new physical port specification to the list in HuaweiOptiXOSN3500SpecificationMapper.java.

Extending the Cartridge to Support SONET Devices

You can extend the Optical UIM Integration cartridge to support SONET devices.

Table 8-1 shows the specifications that can be added to the cartridge to support SONET devices.

Table 8-1 SONET Specifications

Specification Entity

DS1 Device

DeviceInterface

DS3 Interface

DeviceInterface

OC-3 Interface

DeviceInterface

OC-12 Interface

DeviceInterface

OC-48 Interface

DeviceInterface

OC-192 Interface

DeviceInterface

STS-1 Interface

DeviceInterface

VT1.5 Interface

DeviceInterface


The device interface hierarchy can be added to network device to extend the device to support SONET.

The following example demonstrates the device interface hierarchy:

Network Device
  DS1 Interface
  DS3 Interface
    STS-1 Interface
      VT1.5 Channel Interface
    OC-3 Interface
      STS-1 Interface
        VT1.5 Interface
    OC-12 Interface
      STS-1 Interface
        VT1.5 Interface
    OC-48 Interface
      STS-1 Interface
        VT1.5 Interface
    OC-192 Interface
      STS-1 Interface
        VT1.5 Interface

To extend the Optical UIM Integration cartridge to include SONET devices:

  1. Add the new specifications to the ora_uim_network_device cartridge.

  2. Add new interface specifications to the Optical UIM model collection.

  3. Add new device interface specifications to the list in the replaceSpec method of LogicalNetworkDeviceRemodelerHelper.java.

  4. Add any additional model corrections if required.

Supporting an Extended Subrack

The cartridge can be extended to include support for the Huawei OptiX OSN 3500 extended subrack. This section describes slot distribution for the extended shelf. The subrack is modeled as another shelf under the physical device.

Table 8-2 shows how slots in a Huawei device are distributed.

Table 8-2 Slot Distribution of Huawei OptiX OSN 3500 Extended Subrack

Board Type Distributed Slot Ranges

Service interface boards

69 to 76 and 79 to 86

Service processing boards

51 to 55 and 63 to 66

XCS boards

59 to 60

Power interface boards

77 to 78

Auxiliary interface boards

87

Fans

88-90

Virtual slots

  • 50 (CAU slot)

  • 101 to 102 (COA slots)


Figure 8-1 shows slot distribution for an extended subrack of Huawei OptiX OSN 3500.

Figure 8-1 Extended Subrack of Huawei OptiX OSN 3500

slots in extended Huawei OptiX OSN 3500 subrack