HP-ENTITY-MIB

        The MIB module for representing multiple logical
entities supported by a single SNMP agent.
        
This is an exact copy of draft 7 of the IETF
Entity MIB.  The only changes are to actually
assign an OID to it, and add hp to the beginning
of all the labels.  This was done only because
a product that uses this MIB is scheduled to ship
before the IETF MIB will be published as an RFC,
and we needed to give it an OID.
        
It is expected that this MIB module will only be
supported until the IETF actually publishes the
official version as an RFC.  At that time, we will
support the IETF version of this MIB.

Imported Objects

icfHP-ICF-OID
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUPSNMPv2-CONF
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPESNMPv2-SMI
TDomain, TAddress, DisplayString, TEXTUAL-CONVENTION, AutonomousType, RowPointer, TimeStampSNMPv2-TC

Type Definitions (2)

Name Base Type Values/Constraints
PhysicalClassother(1), unknown(2), chassis(3), backplane(4), container(5), powerSupply(6), fan(7), sensor(8), module(9), port(10)
PhysicalIndexrange: 1..2147483647

Objects

hpEntityMIB .1.3.6.1.4.1.11.2.14.9
hpEntityMIBObjects .1.3.6.1.4.1.11.2.14.9.1
hpEntityPhysical .1.3.6.1.4.1.11.2.14.9.1.1
hpEntPhysicalTable .1.3.6.1.4.1.11.2.14.9.1.1.1
hpEntPhysicalEntry .1.3.6.1.4.1.11.2.14.9.1.1.1.1
hpEntPhysicalIndex .1.3.6.1.4.1.11.2.14.9.1.1.1.1.1
hpEntPhysicalDescr
.1.3.6.1.4.1.11.2.14.9.1.1.1.1.2
hpEntPhysicalVendorType
.1.3.6.1.4.1.11.2.14.9.1.1.1.1.3
hpEntPhysicalContainedIn .1.3.6.1.4.1.11.2.14.9.1.1.1.1.4
hpEntPhysicalClass .1.3.6.1.4.1.11.2.14.9.1.1.1.1.5
hpEntPhysicalParentRelPos .1.3.6.1.4.1.11.2.14.9.1.1.1.1.6
hpEntPhysicalName
.1.3.6.1.4.1.11.2.14.9.1.1.1.1.7
hpEntityLogical .1.3.6.1.4.1.11.2.14.9.1.2
hpEntLogicalTable .1.3.6.1.4.1.11.2.14.9.1.2.1
hpEntLogicalEntry .1.3.6.1.4.1.11.2.14.9.1.2.1.1
hpEntLogicalIndex .1.3.6.1.4.1.11.2.14.9.1.2.1.1.1
hpEntLogicalDescr
.1.3.6.1.4.1.11.2.14.9.1.2.1.1.2
hpEntLogicalType
.1.3.6.1.4.1.11.2.14.9.1.2.1.1.3
hpEntLogicalCommunity .1.3.6.1.4.1.11.2.14.9.1.2.1.1.4
hpEntLogicalTAddress
.1.3.6.1.4.1.11.2.14.9.1.2.1.1.5
hpEntLogicalTDomain
.1.3.6.1.4.1.11.2.14.9.1.2.1.1.6
hpEntityMapping .1.3.6.1.4.1.11.2.14.9.1.3
hpEntLPMappingTable .1.3.6.1.4.1.11.2.14.9.1.3.1
hpEntLPMappingEntry .1.3.6.1.4.1.11.2.14.9.1.3.1.1
hpEntLPPhysicalIndex .1.3.6.1.4.1.11.2.14.9.1.3.1.1.1
hpEntAliasMappingTable .1.3.6.1.4.1.11.2.14.9.1.3.2
hpEntAliasMappingEntry .1.3.6.1.4.1.11.2.14.9.1.3.2.1
hpEntAliasLogicalIndexOrZero .1.3.6.1.4.1.11.2.14.9.1.3.2.1.1
hpEntAliasMappingIdentifier
.1.3.6.1.4.1.11.2.14.9.1.3.2.1.2
hpEntPhysicalContainsTable .1.3.6.1.4.1.11.2.14.9.1.3.3
hpEntPhysicalContainsEntry .1.3.6.1.4.1.11.2.14.9.1.3.3.1
hpEntPhysicalChildIndex .1.3.6.1.4.1.11.2.14.9.1.3.3.1.1
hpEntityGeneral .1.3.6.1.4.1.11.2.14.9.1.4
hpEntLastChangeTime
.1.3.6.1.4.1.11.2.14.9.1.4.1
hpEntityMIBTraps .1.3.6.1.4.1.11.2.14.9.2
hpEntityMIBTrapPrefix .1.3.6.1.4.1.11.2.14.9.2.0
hpEntityConformance .1.3.6.1.4.1.11.2.14.9.3
hpEntityCompliances .1.3.6.1.4.1.11.2.14.9.3.1
hpEntityGroups .1.3.6.1.4.1.11.2.14.9.3.2

Notifications/Traps

NameOIDDescription
hpEntConfigChange.1.3.6.1.4.1.11.2.14.9.2.0.1
An hpEntConfigChange trap is sent when the value of
hpEntLastChangeTime changes. It can be utilized by an NMS to
trigger logical/physical entity table maintenance polls.
          
An agent must not generate more than one hpEntConfigChange
'trap-event' in a five second period, where a 'trap-event'
is the transmission of a single trap PDU to a list of trap
destinations.  If additional configuration changes occur
within the five second 'throttling' period, then these
trap-events should be suppressed by the agent. An NMS should
periodically check the value of hpEntLastChangeTime to detect
any missed hpEntConfigChange trap-events, e.g. due to
throttling or transmission loss.