4 About Cartridge Modeling

This chapter provides information on modeling the Oracle Communications Network Integrity MIB-II UIM Integration cartridge.

For information about the following, see Network Integrity MIB-II SNMP Cartridge Guide:

  • MIB-II UIM Integration Cartridge UML Representation

  • Hierarchy Mapping

  • Oracle Communications Information Model Information

  • Specifications

  • Field Mappings

Specification Support in UIM

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 cartridge. This cartridge is 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.

Network Integrity specifications such as GenericMedia are defined in the MIB-II SNMP cartridge. This cartridge references ora_ni_uim_device for the shared deviceGeneric and interfaceGeneric specifications.

The following tables identify which characteristics on the shared specifications are specific to UIM.

Device Generic Characteristics

Table 4-1 shows Device Generic characteristics.

Table 4-1 Device Generic Characteristics

Characteristic Name Specific to UIM

mgmtIpAddress

No

sysObjectId

No

nativeEmsAdminServiceState

Yes

nativeEmsServiceState

Yes

nativeEmsName

Yes


Interface Generic Characteristics

Table 4-2 shows Interface Generic characteristics.

Table 4-2 Interface Generic 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