4 About Cartridge Modeling

This chapter provides information on modeling the Oracle Communications Network Integrity Cisco Router and Switch UIM Integration cartridge.

For information about the following, see Network Integrity Cisco Router and Switch SNMP Cartridge Guide:

  • Cisco UIM Integration cartridge UML Representation

  • Hierarchy Mapping

  • Oracle Communications Information Model Information

  • Field Mapping

  • Logical Mapping

  • Physical Mapping

  • Model Correction

Shared Specifications

You must first model inventory (UIM) specifications in an inventory cartridge using Design Studio, define the cartridge dependency such that the Network Integrity cartridge is dependent on the inventory cartridge, and then use the inventory cartridge specifications in the Network Integrity cartridge model.

Specifications shared with Oracle Communications Unified Inventory Management (UIM) are defined in the ora_ni_uim_device and ora_ni_uim_cisco_device_sample cartridges. These cartridges are used to directly deploy specifications to UIM.Oracle Communications Design Studio features are used to tag certain characteristics as specific to UIM. These characteristics appear on specifications deployed to UIM, but they do not appear on specifications deployed to Network Integrity.This cartridge references ora_ni_uim_device for the shared physicalDeviceGeneric and equipmentGeneric specifications.The following tables identify which characteristics on the shared specifications are specific to UIM.

deviceGeneric Characteristics

Table 4-1 shows deviceGeneric characteristics.

Table 4-1 deviceGeneric Characteristics

Characteristic Name Specific to UIM

mgmtIpAddress

No

sysObjectId

No

nativeEmsAdminServiceState

Yes

nativeEmsServiceState

Yes

nativeEmsName

Yes


interfaceGeneric Characteristics

Table 4-2 shows interfaceGeneric characteristics.

Table 4-2 interfaceGeneric Characteristics

Characteristic Name Specific to UIM

ifAlias

No

ifName

No

ifPromiscuousMode

No

ifType

Yes

minSpeed

Yes

maxSpeed

Yes

nominalSpeed

Yes

physicalAddress

Yes

physicalLocation

Yes

nativeEmsConnectorPresent

Yes

mtuCurrent

Yes

mtuSupported

Yes

nativeEmsAdminServiceState

Yes

nativeEmsServiceState

Yes

nativeEmsName

Yes


physicalDeviceGeneric Characteristics

Table 4-3 shows physicalDeviceGeneric characteristics.

Table 4-3 physicalDeviceGeneric Characteristics

Characteristic Name Specific to UIM

mgmtIpAddress

No

modelName

No

discoveredModelNumber

No

discoveredPartNumber

No

discoveredVendorName

No

hardwareRev

No

softwareRev

No

nativeEmsName

Yes


equipmentGeneric Characteristics

Table 4-4 shows equipmentGeneric characteristics.

Table 4-4 equipmentGeneric Characteristics

Characteristic Name Specific to UIM

modelName

No

discoveredModelNumber

No

discoveredPartNumber

No

discoveredVendorName

No

hardwareRev

No

nativeEmsName

Yes


equipmentHolderGeneric Characteristics

Table 4-5 shows equipmentHolderGeneric characteristics.

Table 4-5 equipmentHolderGeneric Characteristics

Characteristic Name Specific to UIM

modelName

No

discoveredModelNumber

No

discoveredPartNumber

No

discoveredVendorName

No

hardwareRev

No

nativeEmsName

Yes


physicalPortGeneric Characteristics

Table 4-6 shows physicalPortGeneric characteristics.

Table 4-6 physicalPortGeneric Characteristics

Characteristic Name Specific to UIM

modelName

No

discoveredModelNumber

No

discoveredPartNumber

No

discoveredVendorName

No

hardwareRev

No

nativeEmsName

Yes