--------------------------------------------------------------------------
Agent Implementation Checklist
This section should be completed by individuals or companies who
have implemented RFC 2737 support in an SNMP agent.
Is your Entity MIB agent an independent implementation? Or is it
based on public domain or commercial code? If it is not
independent, what code base was used?
Independent (though it uses the SNMP Research EMANATE toolkit).
Have you done any interoperability testing with managers that
implement the Entity MIB? If so, which manager implementations have
been used with your agent?
No.
For each manager with which you have interoperated, which of the
following features were tested? Duplicate this section for each
manager, and indicate yes or no (Y/N) for each feature:
Manager Implementation Used: <Name>
Original Manager Code Base (if known): <Name>
(Y/N) Manager implemented independently from your agent?
(Y/N) Read access to Entity MIB variables.
(Y/N) Write access to Entity MIB variables.
(Y/N) Sending and receiving Entity MIB notifications.
(Y/N) Tested using SNMPv1/v2c.
(Y/N) Tested using SNMPv3.
N/A
Are there any unresolved interoperability issues between your Entity
MIB agent and any Entity MIB manager that may indicate problems in
the specification? If so, please provide technical details.
Does your implementation support the following textual conventions,
including the updates and changes since RFC 2037?
Y (Y/N) Supports PhysicalIndex TC.
Y (Y/N) Supports updated PhysicalClass TC.
Y (Y/N) Uses new "stack(11)" enumeration.
(List) Please list the PhysicalClass values suported by your
implementation:
container(5)
powersupply(6)
fan(7)
module(9)
port(10)
stack(11)
N/A (Y/N) Supports new SNMPEngineIDorNone TC.
Y (Y/N) Does your agent support SNMPv3?
Does your Entity MIB agent implement the following groups and
objects? Indicate yes or no (Y or N) for each group and object:
Y (Y/N) 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) entPhysicalName
Y (Y/N) entPhysicalHardwareRev
Y (Y/N) entPhysicalFirmwareRev
Y (Y/N) entPhysicalSoftwareRev
Y (Y/N) entPhysicalSerialNum
Y (Y/N) entPhysicalMfgName
Y (Y/N) entPhysicalModelName
Y (Y/N) entPhysicalAlias
Y (Y/N) entPhysicalAssetID
Y (Y/N) entPhysicalIsFRU
N (Y/N) entityLogical Group
N (Y/N) entLogicalIndex
N (Y/N) entLogicalDescr
N (Y/N) entLogicalType
N (Y/N) entLogicalTAddress
N (Y/N) entLogicalTDomain
N (Y/N) entLogicalContextEngineID
N (Y/N) entLogicalContextName
N (Y/N) entityMapping Group
N (Y/N) entLPPhysicalIndex
N (Y/N) entAliasLogicalIndexOrZero
N (Y/N) entAliasMappingIdentifier
Y (Y/N) entityGeneral Group
Y (Y/N) entPhysicalChildIndex
Does your implementation allow managers to write to the following
read-write objects? Indicate yes or no (Y or N) for each object:
N (Y/N) entPhysicalSerialNum
N (Y/N) entPhysicalAlias
N (Y/N) entPhysicalAssetID
Does your implementation include each of the following
notifications? Indicate yes or no (Y or N) for each notification:
Y (Y/N) entConfigChange
Does your agent implement MODULE-COMPLIANCE? (Y/N) If so, does it
provide compliance information for the Entity MIB?
Not sure what is being asked here. We conform to entity2Compliance, except
that we support everything read-only.
--------------------------------------------------------------------------------
Sharon Chisholm
Preside Management
Nortel Networks
Ottawa, Ontario