ENTITY-MIB Table View
Table-centric layout grouping table, row, and column objects.
Tables
5
Rows
5
Columns
31
entPhysicalTable
table.1.3.6.1.2.1.47.1.1.1
·
1 row entry
·
19 columns
This table contains one row per physical entity. There is always at least one row for an 'overall' physical entity.
Information about a particular physical entity.
Each entry provides objects (entPhysicalDescr,
entPhysicalVendorType, and entPhysicalClass) to help an NMS
identify and characterize the entry and objects
(en…
Each entry provides objects (entPhysicalDescr,
entPhysicalVendorType, and entPhysicalClass) to help an NMS
identify and characterize the entry and objects
(en…
Indexes
entPhysicalIndex
| Column | Syntax | OID | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
entPhysicalIndex
The index for this entry.
|
PhysicalIndex Textual Convention: PhysicalIndex Integer32Type Constraints: range: 1..2147483647 |
.1.3.6.1.2.1.47.1.1.1.1.1 |
||||||||||||||||||||||||||||||
|
entPhysicalDescr
A textual description of physical entity. This object
should contain a string that identifies the manufacturer's name for the physical entity and should be set to a distinct value for each version or model of the physi… |
SNMP-FRAMEWORK-MIBSnmpAdminString Textual Convention: SNMP-FRAMEWORK-MIBSnmpAdminString OctetStringType Constraints: range: 0..255 |
.1.3.6.1.2.1.47.1.1.1.1.2 |
||||||||||||||||||||||||||||||
|
entPhysicalVendorType
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 an enterprise-specif… |
SNMPv2-TCAutonomousType Textual Convention: SNMPv2-TCAutonomousType ObjectIdentifier |
.1.3.6.1.2.1.47.1.1.1.1.3 |
||||||||||||||||||||||||||||||
|
entPhysicalContainedIn
The value of entPhysicalIndex for the physical entity that
'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 'containme… |
PhysicalIndexOrZero Textual Convention: PhysicalIndexOrZero Integer32Type Constraints: range: 0..2147483647 |
.1.3.6.1.2.1.47.1.1.1.1.4 |
||||||||||||||||||||||||||||||
|
entPhysicalClass
An indication of the general hardware type of the physical
entity. An agent should set this object to the standard enumeration value that most accurately indicates the general class of the physical entity… |
IANA-ENTITY-MIBIANAPhysicalClass Textual Convention: IANA-ENTITY-MIBIANAPhysicalClass EnumerationType Values:
|
.1.3.6.1.2.1.47.1.1.1.1.5 |
||||||||||||||||||||||||||||||
|
entPhysicalParentRelPos
An indication of the relative position of this 'child'
component among all its 'sibling' components. Sibling components are defined as entPhysicalEntries that share the same instance values of each of the entPhysicalCo… |
Integer32 Constraints: range: -1-2147483647 |
.1.3.6.1.2.1.47.1.1.1.1.6 |
||||||||||||||||||||||||||||||
|
entPhysicalName
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 … |
SNMP-FRAMEWORK-MIBSnmpAdminString Textual Convention: SNMP-FRAMEWORK-MIBSnmpAdminString OctetStringType Constraints: range: 0..255 |
.1.3.6.1.2.1.47.1.1.1.1.7 |
||||||||||||||||||||||||||||||
|
entPhysicalHardwareRev
The vendor-specific hardware revision string for the
physical entity. The preferred value is the hardware revision identifier actually printed on the component itself (if present). Note that if revision … |
SNMP-FRAMEWORK-MIBSnmpAdminString Textual Convention: SNMP-FRAMEWORK-MIBSnmpAdminString OctetStringType Constraints: range: 0..255 |
.1.3.6.1.2.1.47.1.1.1.1.8 |
||||||||||||||||||||||||||||||
|
entPhysicalFirmwareRev
The vendor-specific firmware revision string for the
physical entity. Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such info… |
SNMP-FRAMEWORK-MIBSnmpAdminString Textual Convention: SNMP-FRAMEWORK-MIBSnmpAdminString OctetStringType Constraints: range: 0..255 |
.1.3.6.1.2.1.47.1.1.1.1.9 |
||||||||||||||||||||||||||||||
|
entPhysicalSoftwareRev
The vendor-specific software revision string for the
physical entity. Note that if revision information is stored internally in a non-printable (e.g., binary) format, then the agent must convert such info… |
SNMP-FRAMEWORK-MIBSnmpAdminString Textual Convention: SNMP-FRAMEWORK-MIBSnmpAdminString OctetStringType Constraints: range: 0..255 |
.1.3.6.1.2.1.47.1.1.1.1.10 |
||||||||||||||||||||||||||||||
|
entPhysicalSerialNum
The vendor-specific serial number string for the physical
entity. The preferred value is the serial number string actually printed on the component itself (if present). On the first instantiation of a ph… |
OctetStringr/w Constraints: range: 0-32 |
.1.3.6.1.2.1.47.1.1.1.1.11 |
||||||||||||||||||||||||||||||
|
entPhysicalMfgName
The name of the manufacturer of this physical component.
The preferred value is the manufacturer name string actually printed on the component itself (if present). Note that comparisons between instances … |
SNMP-FRAMEWORK-MIBSnmpAdminString Textual Convention: SNMP-FRAMEWORK-MIBSnmpAdminString OctetStringType Constraints: range: 0..255 |
.1.3.6.1.2.1.47.1.1.1.1.12 |
||||||||||||||||||||||||||||||
|
entPhysicalModelName
The vendor-specific model name identifier string associated
with this physical component. The preferred value is the customer-visible part number, which may be printed on the component itself. If the mod… |
SNMP-FRAMEWORK-MIBSnmpAdminString Textual Convention: SNMP-FRAMEWORK-MIBSnmpAdminString OctetStringType Constraints: range: 0..255 |
.1.3.6.1.2.1.47.1.1.1.1.13 |
||||||||||||||||||||||||||||||
|
entPhysicalAlias
This object is an 'alias' name for the physical entity, as
specified by a network manager, and provides a non-volatile 'handle' for the physical entity. On the first instantiation of a physical entity, th… |
OctetStringr/w Constraints: range: 0-32 |
.1.3.6.1.2.1.47.1.1.1.1.14 |
||||||||||||||||||||||||||||||
|
entPhysicalAssetID
This object is a user-assigned asset tracking identifier
(as specified by a network manager) for the physical entity and provides non-volatile storage of this information. On the first instantiation of a … |
OctetStringr/w Constraints: range: 0-32 |
.1.3.6.1.2.1.47.1.1.1.1.15 |
||||||||||||||||||||||||||||||
|
entPhysicalIsFRU
This object indicates whether or not this physical entity
is considered a 'field replaceable unit' by the vendor. If this object contains the value 'true(1)', then this entPhysicalEntry identifies a field replaceable un… |
SNMPv2-TCTruthValue Textual Convention: SNMPv2-TCTruthValue EnumerationType Values:
|
.1.3.6.1.2.1.47.1.1.1.1.16 |
||||||||||||||||||||||||||||||
|
entPhysicalMfgDate
This object contains the date of manufacturing of the
managed entity. If the manufacturing date is unknown or not supported, the object is not instantiated. The special value '0000000000000000'H may also be returned i… |
SNMPv2-TCDateAndTime Textual Convention: SNMPv2-TCDateAndTime OctetStringType Constraints: range: 8range: 11 |
.1.3.6.1.2.1.47.1.1.1.1.17 |
||||||||||||||||||||||||||||||
|
entPhysicalUris
This object contains identification
information about the physical entity. The object contains URIs; therefore, the syntax of this object must conform to RFC 3986, Section 3. Multiple URIs may be present… |
OctetStringr/w | .1.3.6.1.2.1.47.1.1.1.1.18 |
||||||||||||||||||||||||||||||
|
entPhysicalUUID
This object contains identification information
about the physical entity. The object contains a Universally Unique Identifier, the syntax of this object must conform to RFC 4122, Section 4.1. A zero-len… |
UUID-TC-MIBUUIDorZero Textual Convention: UUID-TC-MIBUUIDorZero OctetStringType Constraints: range: 0range: 16 |
.1.3.6.1.2.1.47.1.1.1.1.19 |
entLogicalTable
table.1.3.6.1.2.1.47.1.2.1
·
1 row entry
·
8 columns
This table contains one row per logical entity. For agents that implement more than one naming scope, at least one entry must exist. Agents that instantiate all MIB objects within a single naming scope are not required to implement this table.
Information about a particular logical entity. Entities
may be managed by this agent or other SNMP agents (possibly)
in the same chassis.
may be managed by this agent or other SNMP agents (possibly)
in the same chassis.
Indexes
entLogicalIndex
| Column | Syntax | OID |
|---|---|---|
|
entLogicalIndex
The value of this object uniquely identifies the logical
entity. The value should be a small positive integer; index values for different logical entities are not necessarily contiguous. |
Integer32 Constraints: range: 1-2147483647 |
.1.3.6.1.2.1.47.1.2.1.1.1 |
|
entLogicalDescr
A textual description of the logical entity. This object
should contain a string that identifies the manufacturer's name for the logical entity and should be set to a distinct value for each version of the logical enti… |
SNMP-FRAMEWORK-MIBSnmpAdminString Textual Convention: SNMP-FRAMEWORK-MIBSnmpAdminString OctetStringType Constraints: range: 0..255 |
.1.3.6.1.2.1.47.1.2.1.1.2 |
|
entLogicalType
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 that represents the major MIB module, or the majority of the MIB modules, support… |
SNMPv2-TCAutonomousType Textual Convention: SNMPv2-TCAutonomousType ObjectIdentifier |
.1.3.6.1.2.1.47.1.2.1.1.3 |
|
entLogicalCommunity
deprecated
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: 0-255 |
.1.3.6.1.2.1.47.1.2.1.1.4 |
|
entLogicalTAddress
The transport service address by which the logical entity
receives network management traffic, formatted according to the corresponding value of entLogicalTDomain. For snmpUDPDomain, a TAddress is 6 octet… |
SNMPv2-TCTAddress Textual Convention: SNMPv2-TCTAddress OctetStringType Constraints: range: 1..255 |
.1.3.6.1.2.1.47.1.2.1.1.5 |
|
entLogicalTDomain
Indicates the kind of transport service by which the
logical entity receives network management traffic. Possible values for this object are presently found in RFC 3417. |
SNMPv2-TCTDomain Textual Convention: SNMPv2-TCTDomain ObjectIdentifier |
.1.3.6.1.2.1.47.1.2.1.1.6 |
|
entLogicalContextEngineID
The authoritative contextEngineID that can be used to send
an SNMP message concerning information held by this logical entity to the address specified by the associated 'entLogicalTAddress/entLogicalTDomain' pair. … |
SnmpEngineIdOrNone Textual Convention: SnmpEngineIdOrNone OctetStringType Constraints: range: 0..32 |
.1.3.6.1.2.1.47.1.2.1.1.7 |
|
entLogicalContextName
The contextName that can be used to send an SNMP message
concerning information held by this logical entity to the address specified by the associated 'entLogicalTAddress/entLogicalTDomain' pair. This obj… |
SNMP-FRAMEWORK-MIBSnmpAdminString Textual Convention: SNMP-FRAMEWORK-MIBSnmpAdminString OctetStringType Constraints: range: 0..255 |
.1.3.6.1.2.1.47.1.2.1.1.8 |
entLPMappingTable
table.1.3.6.1.2.1.47.1.3.1
·
1 row entry
·
1 columns
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 that
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 entLPMapping 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 (because
the entPhysicalContainedIn hierarchy can provide the same
information). On the other hand, if more than one bridge
were 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.
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 is expected that sufficient information exists …
equipment association. Note that the nature of the
association is not specifically identified in this entry.
It is expected that sufficient information exists …
Indexes
entLogicalIndex entLPPhysicalIndex
| Column | Syntax | OID |
|---|---|---|
|
entLPPhysicalIndex
The value of this object identifies the index value of a
particular entPhysicalEntry associated with the indicated entLogicalEntity. |
PhysicalIndex Textual Convention: PhysicalIndex Integer32Type Constraints: range: 1..2147483647 |
.1.3.6.1.2.1.47.1.3.1.1.1 |
entAliasMappingTable
table.1.3.6.1.2.1.47.1.3.2
·
1 row entry
·
2 columns
This table contains zero or more rows, representing
mappings of logical entities and physical components 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.
Information about a particular binding between a
logical entity/physical component pair and an external
identifier. Each logical entity/physical component pair
may be associated with one alias mapping.
The logical enti…
logical entity/physical component pair and an external
identifier. Each logical entity/physical component pair
may be associated with one alias mapping.
The logical enti…
Indexes
entPhysicalIndex entAliasLogicalIndexOrZero
| Column | Syntax | OID |
|---|---|---|
|
entAliasLogicalIndexOrZero
The value of this object identifies the logical entity
that defines the naming scope for the associated instance of the entAliasMappingIdentifier object. If this object has a non-zero value, then it ident… |
Integer32 Constraints: range: 0-2147483647 |
.1.3.6.1.2.1.47.1.3.2.1.1 |
|
entAliasMappingIdentifier
The value of this object identifies a particular conceptual
row associated with the indicated entPhysicalIndex and entLogicalIndex pair. Because only physical ports are modeled in this table, only entries… |
SNMPv2-TCRowPointer Textual Convention: SNMPv2-TCRowPointer ObjectIdentifier |
.1.3.6.1.2.1.47.1.3.2.1.2 |
entPhysicalContainsTable
table.1.3.6.1.2.1.47.1.3.3
·
1 row entry
·
1 columns
A table that exposes the container/'containee'
relationships between physical entities. This table
provides all the information found by constructing the
virtual containment tree for a given entPhysicalTable, but
in a more direct format.
In the event a physical entity is contained by more than one
other physical entity (e.g., double-wide modules), this
table should include these additional mappings, which cannot
be represented in the entPhysicalTable virtual containment
tree.
A single container/'containee' relationship.
Indexes
entPhysicalIndex entPhysicalChildIndex
| Column | Syntax | OID |
|---|---|---|
|
entPhysicalChildIndex
The value of entPhysicalIndex for the contained physical
entity. |
PhysicalIndex Textual Convention: PhysicalIndex Integer32Type Constraints: range: 1..2147483647 |
.1.3.6.1.2.1.47.1.3.3.1.1 |