RFC 2737 Implementation Report for Cisco Systems
by Andy Bierman
March 1, 2003

Agent Implementation Checklist

This report is for several cisco platforms that
implement portions of the Entity MIB.  A partial list
of platforms includes these products:

c10000
c3640
c4000
c6000
c3660
c2600
c800
c827
c951
c12000
C10720
uBR7100 family (uBR7111, uBR7114, uBR7111E & uBR7114E)
uBR7200 family (uBR7223, uBR7246, uBR7246-VXR)
uBR10k (uBR710012)
uBR900 family
all DSLAM platforms, i.e. 6160, 6260 and 6015.

   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 commercial code developed by cisco

   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. Works with several cisco NMS applications, such as
an EMS product called UGM managing AS5x00 series; used
to retrieve entPhysical group objects

   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.

   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/N) Supports PhysicalIndex TC.

yes

   (Y/N) Supports updated PhysicalClass TC.

yes

   (Y/N)        Uses new "stack(11)" enumeration.

yes

   (List)       Please list the PhysicalClass values suported by your
                implementation:

most, if not all. Not all platforms support all enumerations. 
Not sure if 'stack' or 'fan' is supported.

   (Y/N) Supports new SNMPEngineIDorNone TC.

no. This TC is not used in Entity MIB at all.

   (Y/N)        Does your agent support SNMPv3?

yes, on most IOS platforms

   Does your Entity MIB agent implement the following groups and
   objects?  Indicate yes or no (Y or N) for each group and object:

   (Y/N) entityPhysical Group
   (Y/N)        entPhysicalIndex
   (Y/N)        entPhysicalDescr
   (Y/N)        entPhysicalVendorType
   (Y/N)        entPhysicalContainedIn
   (Y/N)        entPhysicalClass
   (Y/N)        entPhysicalParentRelPos
   (Y/N)        entPhysicalName
   (Y/N)        entPhysicalHardwareRev
   (Y/N)        entPhysicalFirmwareRev
   (Y/N)        entPhysicalSoftwareRev
   (Y/N)        entPhysicalSerialNum
   (Y/N)        entPhysicalMfgName
   (Y/N)        entPhysicalModelName
   (Y/N)        entPhysicalAlias
   (Y/N)        entPhysicalAssetID
   (Y/N)        entPhysicalIsFRU

all platforms implement these objects

   (Y/N) entityLogical Group
   (Y/N)        entLogicalIndex
   (Y/N)        entLogicalDescr
   (Y/N)        entLogicalType
   (Y/N)        entLogicalTAddress
   (Y/N)        entLogicalTDomain
   (Y/N)        entLogicalContextEngineID
   (Y/N)        entLogicalContextName

2 platforms implement these objects for the default entry,
as described in the RFC. 2 more platforms implement these
objects to model VLANs as logical entities.

   (Y/N) entityMapping Group
   (Y/N)        entLPPhysicalIndex

no

   (Y/N)        entAliasLogicalIndexOrZero

yes, on some platforms

   (Y/N)        entAliasMappingIdentifier

yes, on some platforms

   (Y/N) entityGeneral Group
   (Y/N)        entPhysicalChildIndex

yes, on some platforms

   Does your implementation allow managers to write to the following
   read-write objects?  Indicate yes or no (Y or N) for each object:

   (Y/N) entPhysicalSerialNum
   (Y/N) entPhysicalAlias
   (Y/N) entPhysicalAssetID

yes, these objects are writable on some platforms

   Does your implementation include each of the following
   notifications?  Indicate yes or no (Y or N) for each notification:

   (Y/N) entConfigChange

yes

   Does your agent implement MODULE-COMPLIANCE? (Y/N)  If so, does it
   provide compliance information for the Entity MIB?

Most platforms conform to the entity2Compliance, as modified
by the GROUP clauses for a single naming scope.