HTTP/2 302
date: Mon, 14 Jul 2025 09:12:52 GMT
content-type: text/html
content-length: 143
location: https://get.ietf.org/implementation-report/report-entmib-v3.html
cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
expires: Thu, 01 Jan 1970 00:00:01 GMT
vary: Accept-Encoding
server: cloudflare
cf-ray: 95efe69dc89ddfa6-BLR
alt-svc: h3=":443"; ma=86400
HTTP/2 200
date: Mon, 14 Jul 2025 09:12:52 GMT
content-type: text/html
vary: Accept-Encoding
server: cloudflare
cf-ray: 95efe69dff99b080-BLR
content-encoding: gzip
alt-svc: h3=":443"; ma=86400
Entity MIB Implementation Report
Entity MIB Implementation Report
September 2003
|
1.0 Introduction
|
This report documents implementation experience with the
Entity MIB, most recently published as draft-ietf-entmib-v3-03.txt.
This report consists of three parts: this
summary page,
MIB walks
that demonstrate the
compliance of each implementation, and
vendor
reports
that describe the state of each vendor’s implementation.
.
|
2.0 Implementation Summary
|
Three implementations are described in this report:
-
Cisco’s
implementation – Complete implementation
-
Nortel’s
implementation – Implementation of the Entity MIB Physical Table and
related objects
-
Wind
River’s implementation – Implementation of the Entity MIB Logical Table
and related objects
Between them, these three implementations represent two
independent, interoperable implementations of each Entity MIB object.
The following table summarizes the Entity MIB objects
supported by each implementation:
Entity MIB Objects
|
Cisco
|
Nortel
|
Wind River
|
entityPhysical Group
|
Y
|
Y
|
N
|
entPhysicalIndex
|
Y
|
Y
|
N
|
entPhysicalDescr
|
Y
|
Y
|
N
|
entPhysicalVendorType
|
Y
|
Y
|
N
|
entPhysicalContainedIn
|
Y
|
Y
|
N
|
entPhysicalClass
|
Y
|
Y
|
N
|
entPhysicalParentRelPos
|
Y
|
Y
|
N
|
endPhysicalName
|
Y
|
Y
|
N
|
entPhysicalHardwareRev
|
Y
|
Y
|
N
|
entPhysicalFirmwareRev
|
Y
|
Y
|
N
|
entPhysicalSoftwareRev
|
Y
|
Y
|
N
|
entPhysicalSerialNum
|
Y
|
Y
|
N
|
entPhysicalMfgName
|
Y
|
Y
|
N
|
entPhysicalModeName
|
Y
|
Y
|
N
|
entPhysicalAlias
|
Y
|
Y
|
N
|
entPhysicalAssetID
|
Y
|
Y
|
N
|
entPhysicalIsFRU
|
Y
|
Y
|
N
|
entityLogicalGroup
|
Y
|
N
|
Y
|
entLogicalIndex
|
Y
|
N
|
Y
|
entLogicalDescr
|
Y
|
N
|
Y
|
entLogicalType
|
Y
|
N
|
Y
|
entLogicalTAddress
|
Y
|
N
|
Y
|
entLogicalTDomain
|
Y
|
N
|
Y
|
entLogicalContextEngineID
|
Y
|
N
|
Y
|
entLogicalContextName
|
Y
|
N
|
Y
|
entPhysicalContainsTable
|
Y
|
Y
|
N
|
entPhysicalChildIndex
|
Y
|
Y
|
N
|
entityGeneralGroup
|
Y
|
Y
|
Y
|
entLastChangeTime
|
Y
|
Y
|
Y
|
Notifications
|
Y
|
Y
|
N
|
entConfigChange
|
Y
|
Y
|
N
|
There were logical-to-physical and alias mapping tables
included in earlier versions of the Entity MIB that were not implemented by
multiple vendors.
Those tables have
been deprecated to allow the Entity MIB to progress to Draft Standard.
|