HP-ENTITY-MIB Table View

Table-centric layout grouping table, row, and column objects.

Standard view Table view
Tables
5
Rows
5
Columns
17

hpEntPhysicalTable

table obsolete
.1.3.6.1.4.1.11.2.14.9.1.1.1 · 1 row entry · 7 columns
Open in standard view 
This table contains one row per physical entity.  There is
always at least one row for an 'overall' physical entity.
hpEntPhysicalEntry entry .1.3.6.1.4.1.11.2.14.9.1.1.1.1
Information about a particular physical entity.

Each entry provides objects (hpEntPhysicalDescr,
hpEntPhysicalVendorType, and hpEntPhysicalClass) to help an NMS
identify and characterize the entry, and obje…
Indexes
hpEntPhysicalIndex
Column Syntax OID
hpEntPhysicalIndex obsolete
The index for this entry.
PhysicalIndex
Textual Convention: PhysicalIndex Integer32
Type Constraints:
range: 1..2147483647
 .1.3.6.1.4.1.11.2.14.9.1.1.1.1.1
hpEntPhysicalDescr obsolete
A textual description of physical entity. This object
should contain a string which identifies the manufacturer's
name for the physical entity, and should be set to a
distinct value for each version or model of the phy…
SNMPv2-TCDisplayString
Textual Convention: SNMPv2-TCDisplayString OctetString
Type Constraints:
range: 0..255
 .1.3.6.1.4.1.11.2.14.9.1.1.1.1.2
hpEntPhysicalVendorType obsolete
An indication of the vendor-specific hardware type of the
physical entity. Note that this is different from the
definition of MIB-II's sysObjectID.

An agent should set this object to a enterprise-specific…
SNMPv2-TCAutonomousType
Textual Convention: SNMPv2-TCAutonomousType ObjectIdentifier
 .1.3.6.1.4.1.11.2.14.9.1.1.1.1.3
hpEntPhysicalContainedIn obsolete
The value of hpEntPhysicalIndex for the physical entity which
'contains' this physical entity. A value of zero indicates
this physical entity is not contained in any other physical
entity. Note that the set of 'contai…
Integer32
Constraints:
range: 0-2147483647
 .1.3.6.1.4.1.11.2.14.9.1.1.1.1.4
hpEntPhysicalClass obsolete
An indication of the general hardware type of the physical
entity.

An agent should set this object to the standard enumeration
value which most accurately indicates the general class of
the physical entit…
PhysicalClass
Textual Convention: PhysicalClass Enumeration
Type Values:
1other
2unknown
3chassis
4backplane
5container
6powerSupply
7fan
8sensor
9module
10port
 .1.3.6.1.4.1.11.2.14.9.1.1.1.1.5
hpEntPhysicalParentRelPos obsolete
An indication of the relative position of this 'child'
component among all its 'sibling' components. Sibling
components are defined as hpEntPhysicalEntries which share the
same instance values of each of the hpEntPhysic…
Integer32
Constraints:
range: -1-2147483647
 .1.3.6.1.4.1.11.2.14.9.1.1.1.1.6
hpEntPhysicalName obsolete
The textual name of the physical entity. The value of this
object should be the name of the component as assigned by
the local device and should be suitable for use in commands
entered at the device's `console'. This …
SNMPv2-TCDisplayString
Textual Convention: SNMPv2-TCDisplayString OctetString
Type Constraints:
range: 0..255
 .1.3.6.1.4.1.11.2.14.9.1.1.1.1.7

hpEntLogicalTable

table obsolete
.1.3.6.1.4.1.11.2.14.9.1.2.1 · 1 row entry · 6 columns
Open in standard view 
This table contains one row per logical entity.  At least
one entry must exist.
hpEntLogicalEntry entry .1.3.6.1.4.1.11.2.14.9.1.2.1.1
Information about a particular logical entity. Entities
may be managed by this agent or other SNMP agents (possibly)
in the same chassis.
Indexes
hpEntLogicalIndex
Column Syntax OID
hpEntLogicalIndex obsolete
The value of this object uniquely identifies the logical
entity. The value is a small positive integer; index values
for different logical entities are are not necessarily
contiguous.
Integer32
Constraints:
range: 1-2147483647
 .1.3.6.1.4.1.11.2.14.9.1.2.1.1.1
hpEntLogicalDescr obsolete
A textual description of the logical entity. This object
should contain a string which identifies the manufacturer's
name for the logical entity, and should be set to a distinct
value for each version of the logical en…
SNMPv2-TCDisplayString
Textual Convention: SNMPv2-TCDisplayString OctetString
Type Constraints:
range: 0..255
 .1.3.6.1.4.1.11.2.14.9.1.2.1.1.2
hpEntLogicalType obsolete
An indication of the type of logical entity. This will
typically be the OBJECT IDENTIFIER name of the node in the
SMI's naming hierarchy which represents the major MIB
module, or the majority of the MIB modules, suppor…
SNMPv2-TCAutonomousType
Textual Convention: SNMPv2-TCAutonomousType ObjectIdentifier
 .1.3.6.1.4.1.11.2.14.9.1.2.1.1.3
hpEntLogicalCommunity obsolete
An SNMPv1 or SNMPv2C community-string which can be used to
access detailed management information for this logical
entity. The agent should allow read access with this
community string (to an appropriate subset of all …
OctetString
Constraints:
range: 1-255
 .1.3.6.1.4.1.11.2.14.9.1.2.1.1.4
hpEntLogicalTAddress obsolete
The transport service address by which the logical entity
receives network management traffic, formatted according to
the corresponding value of hpEntLogicalTDomain.

For snmpUDPDomain, a TAddress is 6 oct…
SNMPv2-TCTAddress
Textual Convention: SNMPv2-TCTAddress OctetString
Type Constraints:
range: 1..255
 .1.3.6.1.4.1.11.2.14.9.1.2.1.1.5
hpEntLogicalTDomain obsolete
Indicates the kind of transport service by which the
logical entity receives network management traffic.
Possible values for this object are presently found in the
Transport Mappings for SNMPv2 document (RFC 1906 [8]).
SNMPv2-TCTDomain
Textual Convention: SNMPv2-TCTDomain ObjectIdentifier
 .1.3.6.1.4.1.11.2.14.9.1.2.1.1.6

hpEntLPMappingTable

table obsolete
.1.3.6.1.4.1.11.2.14.9.1.3.1 · 1 row entry · 1 columns
Open in standard view 
This table contains zero or more rows of logical entity to
physical equipment associations. For each logical entity
known by this agent, there are zero or more mappings to the
physical resources which are used to realize that logical
entity.
          
An agent should limit the number and nature of entries in
this table such that only meaningful and non-redundant
information is returned. For example, in a system which
contains a single power supply, mappings between logical
entities and the power supply are not useful and should not
be included.
          
Also, only the most appropriate physical component which is
closest to the root of a particular containment tree should
be identified in an hpEntLPMapping entry.
          
For example, suppose a bridge is realized on a particular
module, and all ports on that module are ports on this
bridge. A mapping between the bridge and the module would be
useful, but additional mappings between the bridge and each
of the ports on that module would be redundant (since the
hpEntPhysicalContainedIn hierarchy can provide the same
information). If, on the other hand, more than one bridge
was utilizing ports on this module, then mappings between
each bridge and the ports it used would be appropriate.
          
Also, in the case of a single backplane repeater, a mapping
for the backplane to the single repeater entity is not
necessary.
hpEntLPMappingEntry entry .1.3.6.1.4.1.11.2.14.9.1.3.1.1
Information about a particular logical entity to physical
equipment association. Note that the nature of the
association is not specifically identified in this entry. It



…
Indexes
hpEntLogicalIndex hpEntLPPhysicalIndex
Column Syntax OID
hpEntLPPhysicalIndex obsolete
The value of this object identifies the index value of a
particular hpEntPhysicalEntry associated with the indicated
hpEntLogicalEntity.
PhysicalIndex
Textual Convention: PhysicalIndex Integer32
Type Constraints:
range: 1..2147483647
 .1.3.6.1.4.1.11.2.14.9.1.3.1.1.1

hpEntAliasMappingTable

table obsolete
.1.3.6.1.4.1.11.2.14.9.1.3.2 · 1 row entry · 2 columns
Open in standard view 
This table contains zero or more rows, representing
mappings of logical entity and physical component to
external MIB identifiers.  Each physical port in the system
may be associated with a mapping to an external identifier,
which itself is associated with a particular logical
entity's naming scope. A 'wildcard' mechanism is provided to
indicate that an identifier is associated with more than one
logical entity.
hpEntAliasMappingEntry entry .1.3.6.1.4.1.11.2.14.9.1.3.2.1
Information about a particular physical equipment, logical
entity to external identifier binding. Each logical
entity/physical component pair may be associated with one
alias mapping. The logical entity index may also …
Indexes
hpEntPhysicalIndex hpEntAliasLogicalIndexOrZero
Column Syntax OID
hpEntAliasLogicalIndexOrZero obsolete
The value of this object uniquely identifies the logical










…
Integer32
Constraints:
range: 0-2147483647
 .1.3.6.1.4.1.11.2.14.9.1.3.2.1.1
hpEntAliasMappingIdentifier obsolete
The value of this object identifies a particular conceptual
row associated with the indicated hpEntPhysicalIndex and
hpEntLogicalIndex pair.





…
SNMPv2-TCRowPointer
Textual Convention: SNMPv2-TCRowPointer ObjectIdentifier
 .1.3.6.1.4.1.11.2.14.9.1.3.2.1.2

hpEntPhysicalContainsTable

table obsolete
.1.3.6.1.4.1.11.2.14.9.1.3.3 · 1 row entry · 1 columns
Open in standard view 
A table which exposes the container/containee relationships
between physical entities. This table provides equivalent
information found by constructing the virtual containment
tree for a given hpEntPhysicalTable but in a more direct
format.
hpEntPhysicalContainsEntry entry .1.3.6.1.4.1.11.2.14.9.1.3.3.1
A single container/containee relationship.
Indexes
hpEntPhysicalIndex hpEntPhysicalChildIndex
Column Syntax OID
hpEntPhysicalChildIndex obsolete
The value of hpEntPhysicalIndex for the contained physical
entity.
PhysicalIndex
Textual Convention: PhysicalIndex Integer32
Type Constraints:
range: 1..2147483647
 .1.3.6.1.4.1.11.2.14.9.1.3.3.1.1