4 About Cartridge Modeling

This chapter provides information on modeling the Network Integrity Cisco Router and Switch SNMP cartridge.

Cisco Router and Switch SNMP Cartridge UML Representation

Figure 4-1 displays a unified modeling language (UML) diagram depicting the object relationship being rendered.

Figure 4-1 Cisco Router and Switch SNMP Cartridge UML Representation

Illustrates SNMP cartridge UML representation

Hierarchy Mapping

The data sourced from RFC1213-MIB.mgmt.mib-2.system tables establishes and seeds the logical device object.

The media interface encapsulates the common information about an interface as a device is discovered. The device interface configuration captures the media type information that decorates the interface with media-specific parameters. These media-specific parameters define the behavior of the interface (Generic, ATM, Frame Relay, or VLAN).

The media interfaces are established and seeded with data sourced from the following:

  • RFC1213-MIB.mgmt.mib-2.system

  • RFC1213-MIB.mgmt.mib-2.interfaces.ifTable

  • IF-MIB.mgmt.mib-2.ifMIB.ifMIBObjects.ifXTable.ifXEntry

  • IP-MIB.mgmt.mib-2.ip.ipAddressTable.ipAddressEntry

IF-MIB.mgmt.mib-2.ifMIB.ifMIBObjects.ifStackTable.ifStackEntry.ifStackStatus establishes the interface hierarchy.

The generic media device interface configuration is established and seeded with data sourced from the following:

  • RFC1213-MIB.mgmt.mib-2.ip.ipAddrTable.ipAddrEntry

  • IP-MIB.mgmt.mib-2.ip.ipAddressTable.ipAddressEntry

The ATM media device interface configuration is established and seeded with data sourced from the ATM-MIB. See "About Poll Lists".

The Frame Relay device interface configuration is established and seeded with data sourced from the CISCO-FRAME-RELAY-MIB and RFC1315-MIB. See "About Poll Lists".

The VLAN device interface configuration is established and seeded with data sourced from the VLAN-CISCO-IFTABLE-RELATIONSHIP-MIB. See "About Poll Lists".

Oracle Communications Information Model Information

All entities shown in Figure 4-1 (for example, physical device, logical device, media interface, and so on) are Oracle Communications Information Model 1.0-compliant for static fields. The dynamic fields (sometimes referred to as characteristics) are application-specific. You can customize application specific data with the device interface configuration mechanism.

The Cisco Router and Switch SNMP cartridge supports the following configurations:

  • Generic Media

  • AtmMedia

  • FrameRelayMedia

  • VLAN Membership

For a listing of the Information Model fields, see "Logical Mapping" and "Physical Mapping".

Specifications

This section lists the specifications included in the UIM Sample Technology Pack for Cisco Devices.

Specification Naming

The specifications with the name pattern cevXXXX are Cisco product names derived from the CISCO_ENTITY_VENDORTYPE-OID-MIB file.

The specifications with the name pattern artificialXXXX are Network Integrity application specific and are used to compensate a hierarchy when the discovered device renders a non Information Model compliant tree. See Oracle Communications Network Integrity Cisco Router and Switch UIM Integration Cartridge Guide for information about model correction.

PhysicalDevice

This specification models a physical device entity.

Table 4-1 shows the specifications for physical Device.

Table 4-1 Physical Device Specifications

Specification Intended Usage/ Notes

cisco3640

Models a subset of 3640 devices.

cat6509

Models a subset of 6509 devices.

cisco7206VXR

Models a subset of 7206 devices.

Table 4-2 shows the characteristics applied to the physical device specifications. See Network Integrity Cisco Router and Switch UIM Integration Cartridge Guide for information about how these fields relate to the Information Model and how they are populated.

Table 4-2 Physical Device Characteristics

Characteristics Field Type Field Content

mgmtIpAddress

String

Text

modelName

String

Text

discoveredModelNumber

String

Text

discoveredPartNumber

String

Text

discoveredVendorName

String

Text

serialNumber

String

Text

physicalLocation

String

Text

hardwareRev

String

Text

softwareRev

String

Text

nativeEmsName

String

Text

See Network Integrity Cisco Router and Switch UIM Integration Cartridge Guide for information about these fields.

Equipment

The following list shows Equipment specifications:

  • artificial6509ContainerGbic

  • artificial6509MSFCCard

  • artificial6509PowerSupplyHolderCard

  • cevBackplaneCat6000

  • cevBackplaneCat6500

  • cevCat6kWsc6000cl

  • cevCat6kWsc6kvtt

  • cevCat6kWsf6kPfc

  • cevCat6kWsx6248Rj45

  • cevCat6kWsx6348Rj45

  • cevCat6kWsxSup1a2ge

  • cevChassis3640

  • cevChassis7206Vxr

  • cevChassisCat6509

  • cevCpu7200Npe300

  • cevCpuCat6kMsfc

  • cevCpuCat6kWsxSup1a2ge

  • cevFanWSC6k9SlotFan

  • cevModuleCat6000Type

  • cevModuleUnknownCard

  • cevModuleVipPortAdapters

  • cevPa8e

  • cevPaAtmdxMmOc3

  • cevPaE3MuxCbr120e1

  • cevPaE3MuxCbr120e1

  • cevPmCpm2e2w

  • cevPmM4t

  • cevPowerSupplyAC1360W

  • cevPowerSupplyC7200AC

  • cevSensorClock

  • cevSensorFanTrayStatus

  • cevSensorModuleDeviceTemp

  • cevSensorModuleOutletTemp

  • cevSensorModulePowerOutputFail

  • cevSensorPSFan

  • cevSensorPSInput

  • cevSensorPSOutput

  • cevSensorVtt

  • cevWicSerial1t

Table 4-3 shows the characteristics applied to the Equipment specifications. See Network Integrity Cisco Router and Switch UIM Integration Cartridge Guide for information about how these field relate to the Information Model and are populated.

Table 4-3 Equipment Characteristics

Characteristics Field Type Field Content

modelName

String

Text

discoveredModelNumber

String

Text

discoveredPartNumber

String

Text

discoveredVendorName

String

Text

serialNumber

String

Text

physicalLocation

String

Text

hardwareRev

String

Text

softwareRev

String

Text

nativeEmsName

String

Text

See Network Integrity Cisco Router and Switch UIM Integration Cartridge Guide to understand how these fields are populated.

Equipment Holder

The following list shows Equipment Holder specifications:

  • artificial6509PowerSupplySlot

  • cevContainerClock

  • cevContainerDaughterCard

  • cevContainerFanTraySlot

  • cevContainerGbic

  • cevContainerPowerSupplyBay

  • cevContainerSlot

  • cevContainerVtt

Table 4-4 shows the characteristics applied to the EquipmentHolder specifications. See Network Integrity Cisco Router and Switch UIM Integration Cartridge Guide for information about how these fields relate to the Information Model and are populated.

Table 4-4 EquipmentHolder Characteristics

Characteristics Field Type Field Content

modelName

String

Text

discoveredModelNumber

String

Text

discoveredPartNumber

String

Text

discoveredVendorName

String

Text

serialNumber

String

Text

physicalLocation

String

Text

hardwareRev

String

Text

softwareRev

String

Text

See Network Integrity Cisco Router and Switch UIM Integration Cartridge Guide to understand how these fields are populated.

Physical Port

The following list shows Physical Port specifications:

  • cevPortAMDP2

  • cevPortDCUATMPort

  • cevPortFe

  • cevPortFEIP

  • cevPortGigBaseLH

  • cevPortMueslix

  • cevPortQuiccSerial

  • cevPortUnknown

Table 4-5 shows the characteristics applied to the PhysicalPort specifications. See Network Integrity Cisco Router and Switch UIM Integration Cartridge Guide for information about how these fields relate to the Information Model and are populated.

Table 4-5 PhysicalPort Characteristics

Characteristics Field Type Field Content

modelName

String

Text

discoveredModelNumber

String

Text

discoveredPartNumber

String

Text

discoveredVendorName

String

Text

serialNumber

String

Text

physicalLocation

String

Text

hardwareRev

String

Text

softwareRev

String

Text

nativeEmsName

String

Text

physicalAddress

String

Text

See Network Integrity Cisco Router and Switch UIM Integration Cartridge Guide to understand how these fields are populated.

Specification Lineages

The UIM Sample Technology Pack for Cisco Devices contains the following specification lineages:

cisco3640

        cisco3640
            cevChassis3640
          cevContainerSlot
                cevPmCpm2e2w
                      cevPortAMDP2
                      cevContainerDaughterCard
                            cevWicSerial1t
                                  cevPortQuiccSerial
                cevPmM4t
                      cevPortMueslix

cisco7206VXR

        cisco7206VXR
            cevChassis7206Vxr
          cevCpu7200Npe300
          cevContainerSlot
                cevModuleUnknownCard
                      cevPortFEIP
                cevPaAtmdxMmOc3
                      cevPortUnknown
                cevModuleVipPortAdapters
                      cevPortMueslix
                cevPaE3MuxCbr120e1
                      cevPortUnknown
                      cevPortDCUATMPort
                cevPowerSupplyC7200AC
                cevPa8e
                      cevPortAMDP2

cat6509

        cat6509
            cevChassisCat6509
          cevBackplaneCat6000
                cevContainerVtt
                      cevCat6kWsc6kvtt
                            cevSensorVtt
                cevSensorVtt
                cevContainerClock
                      cevCat6kWsc6000cl
                            cevSensorClock
                cevSensorClock
          cevBackplaneCat6500
                cevContainerVtt
                      cevCat6kWsc6kvtt
                            cevSensorVtt
                cevSensorVtt
                cevContainerClock
                      cevCat6kWsc6000cl
                            cevSensorClock
                cevSensorClock

          cevContainerFanTraySlot
                cevFanWSC6k9SlotFan
                      cevSensorFanTrayStatus
          cevContainerPowerSupplyBay
                artificial6509PowerSupplyHolderCard
                      artificial6509PowerSupplySlot
                            cevPowerSupplyAC1360W
                                   cevSensorPSFan
                                   cevSensorPSInput
                                   cevSensorPSOutput
          cevContainerSlot
                cevCat6kWsxSup1a2ge
                      cevCpuCat6kWsxSup1a2ge
                      cevSensorModuleOutletTemp
                      cevSensorModulePowerOutputFail
                      cevSensorModuleInletTemp
                      cevSensorModuleDeviceTemp
                      cevContainerDaughterCard
                            cevWicSerial1t
                                   cevPortQuiccSerial
                            cevCat6kWsf6kPfc
                                   cevSensorModuleOutletTemp
                                   cevSensorModuleInletTemp
                            artificial6509MSFCCard
                                   cevModuleCat6000Type
                                         cevSensorModuleOutletTemp
                                         cevSensorModuleInletTemp
                                   cevCpuCat6kMsfc
                      artificial6509ContainerGbic
                            cevPortGigBaseLH
                cevCat6kWsx6248Rj45
                      cevSensorModulePowerOutputFail
                      cevSensorModuleInletTemp
                      cevSensorModuleDeviceTemp
                      cevPortFe
                cevCat6kWsx6348Rj45
                      cevSensorModulePowerOutputFail
                      cevSensorModuleInletTemp
                      cevSensorModuleDeviceTemp
                      cevPortFe

Specification Cardinality

The cardinality of all specification parent-child relationships is included in the software code so that min= 0 and max= n. This approach allows Network Integrity to programmatically instantiate all objects on demand as they are discovered using the web service.

Equipment Visual Specifications

The visual facility on the Equipment specifications is not used. It is left to the customer to decide if they want to enrich the technology pack to provide visual effects to the UIM GUI for a given Equipment entity.

Sample Physical Device Hierarchy

Figure 4-2 shows a physical device hierarchy.

Figure 4-2 Sample Physical Device Hierarchy

Surrounding text describes Figure 4-2 .

Field Mapping

The Cisco Router and Switch SNMP cartridge supports the following field mappings:

  • Text: Implies Text [255]

  • static: Information Model 1.0 defines this field to be static on the entity specification. The specification provides getters and setters for this field.

  • dynamic: This is a dynamic field where the entity specification treats the field as a name and value pair. The specification does not provide getter and setters but generically has get and set characteristics method holding a HashSet of entries.

Logical Mapping

The Cisco Router and Switch SNMP cartridge supports the following logical mappings:

LogicalDevice

Table 4-6 shows characteristics for the LogicalDevice specification.

Table 4-6 LogicalDevice Characteristics

Characteristics (LogicalDevice) Information Model Support MIB Object Field Type Intended Usage/ Notes

Id

static

N/A

Text

Programmatically generated as MgmtIPAddress::sysName::"LogicalDevice"

Name

static

sysName

Text

N/A

Description

static

sysDescr

Text

N/A

Specification

static

N/A

N/A

Programmatically applies deviceGeneric specification

nativeEmsAdminServiceState

static

N/A

Enum with the following values:

  • UNKNOWN

  • IN_SERVICE

  • OUT_OF_SERVICE

  • TESTING

  • IN_MAINTENANCE

Nothing available to source the field.

nativeEmsName

static

sysName

Text

N/A

nativeEmsServiceState

static

N/A

Enum with the following values:

  • UNKNOWN

  • IN_SERVICE

  • OUT_OF_SERVICE

  • TESTING

  • IN_MAINTENANCE

Nothing available to source the field.

mgmtIpAddress

dynamic

N/A

Text

discoveryAddress

sysObjectId

dynamic

sysObjectId

Text

Support legacy systems

MediaInterface

Table 4-7 shows characteristics for the MediaInterface specification.

Table 4-7 MediaInterface Characteristics

Characteristics (MediaInterface) Information Model Support MIB Object Field Type Intended Usage/ Notes

Id

static

N/A

Text

Programmatically generated as MgmtIPAddress::sysName::ifDescr::"MediaInterface"

Name

static

ifDescr

Text

N/A

Description

static

ifDescr

Text

N/A

Specification

static

N/A

N/A

Programmatically applies interfaceGeneric specification

interfaceNumber

static

N/A

Text

Nothing available to source the field.

customerInterfaceNumber

static

N/A

Text

Nothing available to source the field.

vendorInterfaceNumber

static

ifName

Text

N/A

nativeEmsName

static

ifDescr

Text

The field must be unique. ifDescr guarantees the uniqueness of a device.

nativeEmsAdminServiceState

static

ifAdminStatus

Enum with the following values:

  • UNKNOWN

  • IN_SERVICE

  • OUT_OF_SERVICE

  • TESTING

  • IN_MAINTENANCE

Mapped, see Table 4-17.

nativeEmsServiceState

static

ifOperStatus

Enum with the following values:

  • UNKNOWN

  • IN_SERVICE

  • OUT_OF_SERVICE

  • TESTING

  • IN_MAINTENANCE

Mapped, see Table 4-17.

ifType

dynamic

ifType

Text

Mapped from IANA MIB using the snmpIfTypeMap properties file. Look up returning null results in a value of "n".

mtuSupported

static

N/A

Float

Nothing available to source the field. Defaults to 0.0

mtuCurrent

static

ifMtu

Float

N/A

physicalAddress

static

ifPhysAddress

Text

N/A

physicalLocation

static

sysLocation

Text

N/A

minSpeed

static

N/A

Float

Nothing available to source the field. Defaults to 0.0

maxSpeed

static

N/A

Float

Nothing available to source the field. Default to 0.0

nominalSpeed

static

ifSpeed | ifHighSpeed

Float

ifHighSpeed overrides ifSpeed when ifHighSpeed is available

ifAlias

dynamic

ifAlias

Text

N/A

ifName

dynamic

ifName

Text

Support legacy systems

DeviceInterfaceConfigurationItem Mapping (IPv4)

Table 4-8 shows characteristics for the DeviceInterfaceConfigurationItem (IPv4) specification.

Table 4-8 DeviceInterfaceConfigurationItem (IPv4) Characteristics

Characteristics (Generic Media) Information Model Support MIB Object Field Type Intended Usage/ Notes

ipAddress

dynamic

ipAdEntAddr

Text

N/A

prefix

dynamic

ipAdEntNetMask

Text

N/A

ipVersion

dynamic

ipAddressType

Enum

  • IPV4

  • IPV6

Programmatically set to IPV4.

Specification

static

N/A

N/A

Programmatically applies GenericMedia specification

DeviceInterfaceConfigurationItem Mapping (IPv6)

Table 4-9 shows characteristics for the DeviceInterfaceConfigurationItem (IPv6) specification.

Table 4-9 Characteristics for the DeviceInterfaceConfigurationItem (IPv6) Specification

Characteristics (Generic Media) Information Model Support MIB Object Field Type Intended Usage/ Notes

ipAddress

dynamic

ipAddressIfIndex

Text

For IPv6 addresses the actual IP is derived from the index since ipAddressAddr is not acceptable.

prefix

dynamic

ipAddressPrefix

Text

N/A

ipVersion

dynamic

ipAddressType

Enum

  • IPV4

  • IPV6

Programmatically set to IPV6.

Specification

static

N/A

N/A

Programmatically applies GenericMedia specification

DeviceInterfaceConfigurationItem Mapping (Frame Relay)

Table 4-10 shows characteristics for the DeviceInterfaceConfigurationItem Mapping (FrameRelayMedia) specification.

Table 4-10 Characteristics for the DeviceInterfaceConfigurationItem (FrameRelayMedia) Specification

Characteristics (FrameRelayMedia) Information Model Support MIB Object Field Type Intended Usage/ Notes

DLCI

dynamic

Table index

Text

Parsed from the table index, which is in the format: <ifindex>.<DLCI>.

Table 4-11 shows characteristics for the DeviceInterfaceConfigurationItem Mapping (FrameRelayData) specification.

Table 4-11 Characteristics for the DeviceInterfaceConfigurationItem (FrameRelayData) Specification

Characteristics (FrameRelayData) Information Model Support MIB Object Field Type

frCircuitIfIndex

dynamic

frCircuitIfIndex

Text

frCircuitDlci

dynamic

frCircuitDlci

Text

frCircuitState

dynamic

frCircuitState

Text

frCircuitCreationTime

dynamic

frCircuitCreationTime

Text

frCircuitLastTimeChange

dynamic

frCircuitLastTimeChange

Text

frCircuitCommittedBurst

dynamic

frCircuitCommittedBurst

Text

frCircuitExcessBurst

dynamic

frCircuitExcessBurst

Text

frCircuitThroughput

dynamic

frCircuitThroughput

Text

Table 4-12 shows characteristics for the DeviceInterfaceConfigurationItem Mapping (FrameRelayExtendedData) specification.

Table 4-12 Characteristics for the DeviceInterfaceConfigurationItem (FrameRelayExtendedData) Specification

Characteristics (FrameRelayExtendedData) Information Model Support MIB Object Field Type

cfrCircuitType

dynamic

cfrCircuitType

Text

cfrExtCircuitSubIfIndex

dynamic

cfrExtCircuitSubifIndex

Text

cfrSvcThroughputIn

dynamic

cfrSvcThroughputIn

Text

cfrSvcCommitBurstIn

dynamic

cfrSvcCommitBurstIn

Text

cfrSvcExcessBurstIn

dynamic

cfrSvcExcessBurstIn

Text

DeviceInterfaceConfigurationItem Mapping (ATM Media)

Table 4-13 shows characteristics for the DeviceInterfaceConfigurationItem mapping (ATM media) specification.

Table 4-13 Characteristics for the DeviceInterfaceConfigurationItem (ATM media) Specification

Characteristics (ATM Media) Information Model Support MIB Object Field Type Intended Usage/ Notes

VPI

dynamic

Table index

Text

Parsed from the table index, which is in the format: <ifIndex>.<VPI>.<VCI>

VCI

dynamic

Table index

Text

Parsed from the table index, which is in the format: <ifIndex>.<VPI>.<VCI>

Table 4-14 shows characteristics for the DeviceInterfaceConfigurationItem Mapping (VirtualChannelLinkData) specification.

Table 4-14 Characteristics for the DeviceInterfaceConfigurationItem (VirtualChannelLinkData) Specification

Characteristics (VirtualChannelLinkData) Information Model Support MIB Object Field Type

atmVccAal5EncapsType

dynamic

atmVccAal5EncapsType

Text

atmVccAalType

dynamic

atmVccAalType

Text

atmVclLastChange

dynamic

atmVclLastChange

Text

atmVclAdminStatus

dynamic

atmVclAdminStatus

Text

atmVclOperStatus

dynamic

atmVclOperStatus

Text

Table 4-15 shows characteristics for the DeviceInterfaceConfigurationItem Mapping (AtmInterfaceConfigurationData) specification.

Table 4-15 Characteristics for the DeviceInterfaceConfigurationItem (AtmInterfaceConfigurationData) Specification

Characteristics (AtmInterfaceConfigurationData) Information Model Support MIB Object Field Type

atmInterfaceMaxVpcs

dynamic

atmInterfaceMaxVpcs

Text

atmInterfaceMaxVccs

dynamic

atmInterfaceMaxVccs

Text

atmInterfaceMaxActiveVpiBits

dynamic

atmInterfaceMaxActiveVpiBits

Text

atmInterfaceMaxActiveVciBits

dynamic

atmInterfaceMaxActiveVciBits

Text

atmInterfaceIlmiVpi

dynamic

atmInterfaceIlmiVpi

Text

atmInterfaceIlmiVci

dynamic

atmInterfaceIlmiVci

Text

atmInterfaceAddressType

dynamic

atmInterfaceAddressType

Text

atmInterfaceAdminAddress

dynamic

atmInterfaceAdminAddress

Text

DeviceInterfaceConfigurationItem Mapping (VLAN)

Table 4-16 shows characteristics for the DeviceInterfaceConfigurationItem mapping (VLAN) specification.

Table 4-16 Characteristics for the DeviceInterfaceConfigurationItem (VLAN) Specification

Characteristics (VLAN ID) Information Model Support MIB Object Field Type

cviRoutedVlanIfIndex

dynamic

cviRoutedVlanIfIndex

Text

Mapping Table

Table 4-17 shows a mapping table.

Table 4-17 Mapping Table

ifOperStatus ifAdminStatus nativeEmsServiceState nativeEmsAdminState

4: unknown, 6: notPresent

N/A

UNKNOWN

1: up

1: up

IN_SERVICE

2: down, 5: dormant, 7: lowerLayerDown

2: down

Programmatically set to OUT_OF_SERVICE.

3: testing

3: testing

TESTING

N/A

N/A

IN_MAINTENANCE

Physical Mapping

This cartridge support the following physical mappings:

Mapping From Cisco to Information Model Nomenclature

Table 4-18 lists the Cisco to Information Model mapping classification of physical components. For example, if an equipment is classified as "Power Supply," this cartridge maps the SNMP data into the Information Model entity type Equipment.

Table 4-18 Cisco to Information Model Physical Nomenclature Mapping

entPhysicalClass Information Model

root

Physical Device

Other (1)

Unsupported

Unknown (2)

Unsupported

Chassis (3)

Equipment-Shelf

Backplane (4)

Equipment-Shelf

Container (5)

Equipment-Holder

Power supply (6)

Equipment

Fan (7)

Equipment

Sensor (8)

Equipment

Module (9)

Equipment-Card

Port (10)

Physical Port

Stack (11)

Unsupported

PhysicalDevice

Table 4-19 shows the characteristics for the PhysicalDevice specification.

Table 4-19 PhysicalDevice Characteristics

Characteristics (Physical Device) Information Model Support MIB Object Field Type Intended Usage/ Notes

Id

static

N/A

Text

Programmatically generated as MgmtIPAddress::sysName::0::"PhysicalDevice".

Name

static

sysName

Text

N/A

Description

static

sysDescr

Text

N/A

Specification

static

N/A

N/A

Programmatically applies physicalDeviceGeneric specification.

discoveredModelNumber

dynamic

sysObjectId

Text

N/A

discoveredVendorName

dynamic

N/A

Text

Mapped using the snmpVendorNameMap which is created by the MIB II Properties Initializer. See "Determining the Value of the discoveredVendorName Field".

serialNumber

static

N/A

Text

N/A

physicalLocation

N/A

location

Text

N/A

discoveredPartNumber

dynamic

N/A

Text

N/A

hardwareRev

dynamic

N/A

Text

N/A

softwareRev

dynamic

N/A

Text

N/A

modelName

dynamic

N/A

Text

Mapped using the ciscoProductsMap, which is created by the Cisco SNMP Properties Initializer. See "Determining the Value of the modelName Field".

mgmtIpAddress

dynamic

N/A

Text

discoveryAddress

nativeEmsName

static

sysName

Text

N/A

Equipment

Table 4-20 shows characteristics for the Equipment specification.

Table 4-20 Equipment Characteristics

Characteristics (Equipment) Information Model Support MIB Object Field Type Intended Usage/ Notes

Id

static

N/A

Text

Programmatically set to MgmtIPAddress::sysName::
[absRelativePosition]::"Equipment.Rack|Shelf|Card". See "About the absRelativePosition Value".

Name

static

entPhysicalDescr

Text

N/A

Description

static

entPhysicalDescr

Text

N/A

Specification

static

N/A

N/A

Programmatically applies equipmentGeneric specification.

discoveredModelNumber

dynamic

entPhysicalVendorType

Text

N/A

discoveredVendorName

dynamic

entPhysicalMfgName

Text

N/A

serialNumber

static

entPhysicalSerialNum

Text

N/A

physicalLocation

static

location

Text

N/A

discoveredPartNumber

dynamic

entPhysicalModelName

Text

N/A

hardwareRev

dynamic

entPhysicalHardwareRev

Text

N/A

softwareRev

dynamic

entPhysicalSoftwareRev

Text

N/A

modelName

dynamic

N/A

Text

Mapped using the ciscoVendorTypesMap, which is created by the Cisco SNMP Properties Initializer. See "Determining the Value of the modelName Field".

nativeEmsName

static

entPhysicalDescr and absRelativePosition

Text

N/A

EquipmentHolder

Table 4-21 shows characteristics for the EquipmentHolder specification.

Table 4-21 EquipmentHolder Characteristics

Characteristics (EquipmentHolder) Information Model Support MIB Object Field Type Intended Usage/ Notes

Id

static

N/A

Text

Programmatically generated as MgmtIPAddress::sysName::[absRelativePosition]::"EquipmentHolder". See "About the absRelativePosition Value".

Name

static

entPhysicalDescr and entPhysicalParentRelPos

Text

Programmatically generated as entPhysicalDescr::entPhysi calParentRelPos.

Description

static

entPhysicalDescr

Text

N/A

Specification

static

N/A

N/A

Programmatically applies equipmentHolderGeneric specification.

discoveredModelNumber

dynamic

entPhysicalVendorType

Text

N/A

discoveredVendorName

dynamic

entPhysicalMfgName

Text

N/A

serialNumber

static

entPhysicalSerialNum

Text

N/A

physicalLocation

static

location

Text

N/A

discoveredPartNumber

dynamic

entPhysicalModelName

Text

N/A

hardwareRev

dynamic

entPhysicalHardwareRev

Text

N/A

softwareRev

dynamic

entPhysicalSoftwareRev

Text

N/A

modelName

dynamic

  

Text

Mapped using the ciscoVendorTypesMap, which is created by the Cisco SNMP Properties Initializer. See "Determining the Value of the modelName Field".

nativeEmsName

static

entPhysicalParentRelPos

Text

N/A

PhysicalPort

Table 4-22 shows characteristics for the PhysicalPort specification.

Table 4-22 PhysicalPort Characteristics

Characteristics (PhysicalPort) Information Model Support MIB Object Field Type Intended Usage/ Notes

Id

static

N/A

Text

Programmatically generated as MgmtIPAddress::sysName::[absRelativePosition]::"PhysicalPort". See "About the absRelativePosition Value".

Name

static

entPhysicalDescr and entPhysicalParentRelPos

Text

Programmatically generated as entPhysicalDescr::entPhysicalParentRelPos.

Description

static

entPhysicalName

Text

N/A

Specification

static

N/A

N/A

Programmatically applies equipmentGeneric specification.

discoveredModelNumber

dynamic

entPhysicalVendorType

Text

N/A

portNumber

static

entPhysicalParentRelPos

Int

N/A

customerPortName

static

entPhysicalParentRelPos

Text

N/A

vendorPortName

static

N/A

Text

N/A

discoveredVendorName

dynamic

entPhysicalMfgName

Text

N/A

serialNumber

static

entPhysicalSerialNum

Text

N/A

physicalLocation

static

location

Text

N/A

discoveredPartNumber

dynamic

entPhysicalModelName

Text

N/A

hardwareRev

dynamic

entPhysicalHardwareRev

Text

N/A

softwareRev

dynamic

entPhysicalSoftwareRev

Text

N/A

modelName

dynamic

N/A

Text

Mapped using the ciscoVendorTypesMap, which is created by the Cisco SNMP Properties Initializer. See "Determining the Value of the modelName Field".

nativeEmsName

static

entPhysicalParentRelPos

Text

N/A