RFC 4133: Entity MIB (Version 3) (original) (raw)

                     Entity MIB (Version 3)
 If no additional identification information is known about the
 physical entity or supported, the object is not instantiated.
 a single logical entity, or multiple logical entities within a
 single naming scope, then implementation of this table may be
 omitted by the agent.
                 Andy Bierman
                 ietf@andybierman.com

                 Keith McCloghrie
                 Cisco Systems Inc.
                 170 West Tasman Drive
                 San Jose, CA 95134
                 +1 408-526-5260
                 kzm@cisco.com"

DESCRIPTION
        "The MIB module for representing multiple logical
        entities supported by a single SNMP agent.

        Copyright (C) The Internet Society (2005).  This
        version of this MIB module is part of [RFC 4133](./rfc4133); see
        the RFC itself for full legal notices."

REVISION        "200508100000Z"
DESCRIPTION
        "Initial Version of Entity MIB (Version 3).
         This revision obsoletes [RFC 2737](./rfc2737).
         Additions:
           - cpu(12) enumeration added to PhysicalClass TC
           - DISPLAY-HINT clause to PhysicalIndex TC
           - PhysicalIndexOrZero TC
           - entPhysicalMfgDate object
           - entPhysicalUris object
         Changes:
           - entPhysicalContainedIn SYNTAX changed from
             INTEGER to PhysicalIndexOrZero

         This version published as [RFC 4133](./rfc4133)."

REVISION        "199912070000Z"
DESCRIPTION
        "Initial Version of Entity MIB (Version 2).
         This revision obsoletes [RFC 2037](./rfc2037).
         This version published as [RFC 2737](./rfc2737)."

REVISION        "199610310000Z"
DESCRIPTION
        "Initial version (version 1), published as
         [RFC 2037](./rfc2037)."
::= { mib-2 47 }
        The enumeration 'other' is applicable if the physical entity
        class is known, but does not match any of the supported
        values.

        The enumeration 'unknown' is applicable if the physical
        entity class is unknown to the agent.

        The enumeration 'chassis' is applicable if the physical
        entity class is an overall container for networking
        equipment.  Any class of physical entity, except a stack,
        may be contained within a chassis; and a chassis may only
        be contained within a stack.
        The enumeration 'backplane' is applicable if the physical
        entity class is some sort of device for aggregating and
        forwarding networking traffic, such as a shared backplane in
        a modular ethernet switch.  Note that an agent may model a
        backplane as a single physical entity, which is actually
        implemented as multiple discrete physical components (within
        a chassis or stack).

        The enumeration 'container' is applicable if the physical
        entity class is capable of containing one or more removable
        physical entities, possibly of different types.  For
        example, each (empty or full) slot in a chassis will be
        modeled as a container.  Note that all removable physical
        entities should be modeled within a container entity, such
        as field-replaceable modules, fans, or power supplies.  Note
        that all known containers should be modeled by the agent,
        including empty containers.

        The enumeration 'powerSupply' is applicable if the physical
        entity class is a power-supplying component.

        The enumeration 'fan' is applicable if the physical entity
        class is a fan or other heat-reduction component.

        The enumeration 'sensor' is applicable if the physical
        entity class is some sort of sensor, such as a temperature
        sensor within a router chassis.

        The enumeration 'module' is applicable if the physical
        entity class is some sort of self-contained sub-system.  If
        the enumeration 'module' is removable, then it should be
        modeled within a container entity, otherwise it should be
        modeled directly within another physical entity (e.g., a
        chassis or another module).

        The enumeration 'port' is applicable if the physical entity
        class is some sort of networking port, capable of receiving
        and/or transmitting networking traffic.

        The enumeration 'stack' is applicable if the physical entity
        class is some sort of super-container (possibly virtual),
        intended to group together multiple chassis entities.  A
        stack may be realized by a 'virtual' cable, a real
        interconnect cable, attached to multiple chassis, or may in
        fact be comprised of multiple interconnect cables.  A stack
        should not be modeled within any other physical entities,
        but a stack may be contained within another stack.  Only
        chassis entities should be contained within a stack.
        The enumeration 'cpu' is applicable if the physical entity
        class is some sort of central processing unit."
SYNTAX      INTEGER  {
   other(1),
   unknown(2),
   chassis(3),
   backplane(4),
   container(5),     -- e.g., chassis slot or daughter-card holder
   powerSupply(6),
   fan(7),
   sensor(8),
   module(9),        -- e.g., plug-in card or daughter-card
   port(10),
   stack(11),        -- e.g., stack of multiple chassis entities
   cpu(12)
}
        If an instance of an object of SYNTAX SnmpEngineIdOrNone has
        a non-zero length, then the object encoding and semantics
        are defined by the SnmpEngineID textual convention (see STD
        62, [RFC 3411](./rfc3411) [[RFC3411](./rfc3411 ""An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks"")]).

        If an instance of an object of SYNTAX SnmpEngineIdOrNone
        contains a zero-length string, then no appropriate
        SnmpEngineID is associated with the logical entity (i.e.,
        SNMPv3 is not supported)."
SYNTAX OCTET STRING (SIZE(0..32)) -- empty string or SnmpEngineID
STATUS      current
DESCRIPTION
        "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
        (entPhysicalContainedIn and entPhysicalParentRelPos) to help
        an NMS relate the particular entry to other entries in this
        table."
INDEX   { entPhysicalIndex }
::= { entPhysicalTable 1 }
        "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 physical
        entity."
::= { entPhysicalEntry 2 }
        An agent should set this object to an enterprise-specific
        registration identifier value indicating the specific
        equipment type in detail.  The associated instance of
        entPhysicalClass is used to indicate the general type of
        hardware device.

        If no vendor-specific registration identifier exists for
        this physical entity, or the value is unknown by this agent,
        then the value { 0 0 } is returned."
::= { entPhysicalEntry 3 }
        In the event that a physical entity is contained by more
        than one physical entity (e.g., double-wide modules), this
        object should identify the containing entity with the lowest
        value of entPhysicalIndex."
::= { entPhysicalEntry 4 }
STATUS      current
DESCRIPTION
        "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, or the primary class if there is more
        than one entity.

        If no appropriate standard registration identifier exists
        for this physical entity, then the value 'other(1)' is
        returned.  If the value is unknown by this agent, then the
        value 'unknown(2)' is returned."
::= { entPhysicalEntry 5 }
        An NMS can use this object to identify the relative ordering
        for all sibling components of a particular parent
        (identified by the entPhysicalContainedIn instance in each
        sibling entry).

        If possible, this value should match any external labeling
        of the physical component.  For example, for a container
        (e.g., card slot) labeled as 'slot #3',
        entPhysicalParentRelPos should have the value '3'.  Note
        that the entPhysicalEntry for the module plugged in slot 3
        should have an entPhysicalParentRelPos value of '1'.

        If the physical position of this component does not match
        any external numbering or clearly visible ordering, then
        user documentation or other external reference material
        should be used to determine the parent-relative position.
        If this is not possible, then the agent should assign a
        consistent (but possibly arbitrary) ordering to a given set
        of 'sibling' components, perhaps based on internal
        representation of the components.
        If the agent cannot determine the parent-relative position
        for some reason, or if the associated value of
        entPhysicalContainedIn is '0', then the value '-1' is
        returned.  Otherwise, a non-negative integer is returned,
        indicating the parent-relative position of this physical
        entity.

        Parent-relative ordering normally starts from '1' and
        continues to 'N', where 'N' represents the highest
        positioned child entity.  However, if the physical entities
        (e.g., slots) are labeled from a starting position of zero,
        then the first sibling should be associated with an
        entPhysicalParentRelPos value of '0'.  Note that this
        ordering may be sparse or dense, depending on agent
        implementation.

        The actual values returned are not globally meaningful, as
        each 'parent' component may use different numbering
        algorithms.  The ordering is only meaningful among siblings
        of the same parent component.

        The agent should retain parent-relative position values
        across reboots, either through algorithmic assignment or use
        of non-volatile storage."
::= { entPhysicalEntry 6 }
        If there is no local name, or if this object is otherwise
        not applicable, then this object contains a zero-length
        string.

        Note that the value of entPhysicalName for two physical
        entities will be the same in the event that the console
        interface does not distinguish between them, e.g., slot-1
        and the card in slot-1."
::= { entPhysicalEntry 7 }
        Note that if revision information is stored internally in a
        non-printable (e.g., binary) format, then the agent must
        convert such information to a printable format, in an
        implementation-specific manner.

        If no specific hardware revision string is associated with
        the physical component, or if this information is unknown to
        the agent, then this object will contain a zero-length
        string."
::= { entPhysicalEntry 8 }
        Note that if revision information is stored internally in a
        non-printable (e.g., binary) format, then the agent must
        convert such information to a printable format, in an
        implementation-specific manner.

        If no specific firmware programs are associated with the
        physical component, or if this information is unknown to the
        agent, then this object will contain a zero-length string."
::= { entPhysicalEntry 9 }
        Note that if revision information is stored internally in a
        non-printable (e.g., binary) format, then the agent must
        convert such information to a printable format, in an
        implementation-specific manner.

        If no specific software programs are associated with the
        physical component, or if this information is unknown to the
        agent, then this object will contain a zero-length string."
::= { entPhysicalEntry 10 }
        On the first instantiation of an physical entity, the value
        of entPhysicalSerialNum associated with that entity is set
        to the correct vendor-assigned serial number, if this
        information is available to the agent.  If a serial number
        is unknown or non-existent, the entPhysicalSerialNum will be
        set to a zero-length string instead.

        Note that implementations that can correctly identify the
        serial numbers of all installed physical entities do not
        need to provide write access to the entPhysicalSerialNum
        object.  Agents which cannot provide non-volatile storage
        for the entPhysicalSerialNum strings are not required to
        implement write access for this object.

        Not every physical component will have a serial number, or
        even need one.  Physical entities for which the associated
        value of the entPhysicalIsFRU object is equal to 'false(2)'
        (e.g., the repeater ports within a repeater module), do not
        need their own unique serial number.  An agent does not have
        to provide write access for such entities, and may return a
        zero-length string.

        If write access is implemented for an instance of
        entPhysicalSerialNum, and a value is written into the
        instance, the agent must retain the supplied value in the
        entPhysicalSerialNum instance (associated with the same
        physical entity) for as long as that entity remains
        instantiated.  This includes instantiations across all
        re-initializations/reboots of the network management system,
        including those resulting in a change of the physical
        entity's entPhysicalIndex value."
::= { entPhysicalEntry 11 }
        Note that comparisons between instances of the
        entPhysicalModelName, entPhysicalFirmwareRev,
        entPhysicalSoftwareRev, and the entPhysicalSerialNum
        objects, are only meaningful amongst entPhysicalEntries with
        the same value of entPhysicalMfgName.

        If the manufacturer name string associated with the physical
        component is unknown to the agent, then this object will
        contain a zero-length string."
::= { entPhysicalEntry 12 }
        If the model name string associated with the physical
        component is unknown to the agent, then this object will
        contain a zero-length string."
::= { entPhysicalEntry 13 }
        On the first instantiation of a physical entity, the value
        of entPhysicalAlias associated with that entity is set to
        the zero-length string.  However, the agent may set the
        value to a locally unique default value, instead of a
        zero-length string.

        If write access is implemented for an instance of
        entPhysicalAlias, and a value is written into the instance,
        the agent must retain the supplied value in the
        entPhysicalAlias instance (associated with the same physical
        entity) for as long as that entity remains instantiated.
        This includes instantiations across all
        re-initializations/reboots of the network management system,
        including those resulting in a change of the physical
        entity's entPhysicalIndex value."
::= { entPhysicalEntry 14 }
        On the first instantiation of a physical entity, the value
        of entPhysicalAssetID associated with that entity is set to
        the zero-length string.

        Not every physical component will have an asset tracking
        identifier, or even need one.  Physical entities for which
        the associated value of the entPhysicalIsFRU object is equal
        to 'false(2)' (e.g., the repeater ports within a repeater
        module), do not need their own unique asset tracking
        identifier.  An agent does not have to provide write access
        for such entities, and may instead return a zero-length
        string.

        If write access is implemented for an instance of
        entPhysicalAssetID, and a value is written into the
        instance, the agent must retain the supplied value in the
        entPhysicalAssetID instance (associated with the same
        physical entity) for as long as that entity remains
        instantiated.  This includes instantiations across all
        re-initializations/reboots of the network management system,
        including those resulting in a change of the physical
        entity's entPhysicalIndex value.
        If no asset tracking information is associated with the
        physical component, then this object will contain a
        zero-length string."
::= { entPhysicalEntry 15 }
        Multiple URIs may be present and are separated by white
        space characters.  Leading and trailing white space
        characters are ignored.

        If no additional identification information is known
        about the physical entity or supported, the object is not
        instantiated.  A zero length octet string may also be
        returned in this case."
REFERENCE
        "[RFC 3986](./rfc3986), Uniform Resource Identifiers (URI): Generic
        Syntax, [section 2](#section-2), August 1998."

::= { entPhysicalEntry 18 }
        "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."
::= { entLogicalEntry 1 }
        care not to return a community string that allows more
        privileges than the community string used to access this
        object.

        A compliant SNMP agent may wish to conserve naming scopes by
        representing multiple logical entities in a single 'default'
        naming scope.  This is possible when the logical entities,
        represented by the same value of entLogicalCommunity, have
        no object instances in common.  For example, 'bridge1' and
        'repeater1' may be part of the main naming scope, but at
        least one additional community string is needed to represent
        'bridge2' and 'repeater2'.

        Logical entities 'bridge1' and 'repeater1' would be
        represented by sysOREntries associated with the 'default'
        naming scope.

        For agents not accessible via SNMPv1 or SNMPv2C, the value
        of this object is the empty string.  This object may also
        contain an empty string if a community string has not yet
        been assigned by the agent, or if no community string with
        suitable access rights can be returned for a particular SNMP
        request.

        Note that this object is deprecated.  Agents which implement
        SNMPv3 access should use the entLogicalContextEngineID and
        entLogicalContextName objects to identify the context
        associated with each logical entity.  SNMPv3 agents may
        return a zero-length string for this object, or may continue
        to return a community string (e.g., tri-lingual agent
        support)."
::= { entLogicalEntry 4 }
        For snmpUDPDomain, a TAddress is 6 octets long: the initial
        4 octets contain the IP-address in network-byte order and
        the last 2 contain the UDP port in network-byte order.
        Consult 'Transport Mappings for the Simple Network
        Management Protocol' (STD 62, [RFC 3417](./rfc3417) [[RFC3417](./rfc3417 ""Transport Mappings for the Simple Network Management Protocol (SNMP)"")]) for
        further information on snmpUDPDomain."
::= { entLogicalEntry 5 }
        This object, together with the associated
        entLogicalContextName object, defines the context associated
        with a particular logical entity, and allows access to SNMP
        engines identified by a contextEngineId and contextName
        pair.

        If no value has been configured by the agent, a zero-length
        string is returned, or the agent may choose not to
        instantiate this object at all."
::= { entLogicalEntry 7 }
        This object, together with the associated
        entLogicalContextEngineID object, defines the context
        associated with a particular logical entity, and allows
        access to SNMP engines identified by a contextEngineId and
        contextName pair.

        If no value has been configured by the agent, a zero-length
        string is returned, or the agent may choose not to
        instantiate this object at all."
::= { entLogicalEntry 8 }
        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."
::= { entityMapping 1 }
STATUS      current
DESCRIPTION
        "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 in the
        MIBs used to manage a particular logical entity to infer how
        physical component information is utilized."
INDEX       { entLogicalIndex, entLPPhysicalIndex }
::= { entLPMappingTable 1 }
        entity to external identifier binding.  Each logical
        entity/physical component pair may be associated with one
        alias mapping.  The logical entity index may also be used as
        a 'wildcard' (refer to the entAliasLogicalIndexOrZero object
        DESCRIPTION clause for details.)

        Note that only entPhysicalIndex values that represent
        physical ports (i.e., associated entPhysicalClass value is
        'port(10)') are permitted to exist in this table."
INDEX { entPhysicalIndex, entAliasLogicalIndexOrZero }
::= { entAliasMappingTable 1 }
        If this object has a non-zero value, then it identifies the
        logical entity named by the same value of entLogicalIndex.

        If this object has a value of zero, then the mapping between
        the physical component and the alias identifier for this
        entAliasMapping entry is associated with all unspecified
        logical entities.  That is, a value of zero (the default
        mapping) identifies any logical entity that does not have
        an explicit entry in this table for a particular
        entPhysicalIndex/entAliasMappingIdentifier pair.

        For example, to indicate that a particular interface (e.g.,
        physical component 33) is identified by the same value of
        ifIndex for all logical entities, the following instance
        might exist:

                entAliasMappingIdentifier.33.0 = ifIndex.5

        In the event an entPhysicalEntry is associated differently
        for some logical entities, additional entAliasMapping
        entries may exist, e.g.:
                entAliasMappingIdentifier.33.0 = ifIndex.6
                entAliasMappingIdentifier.33.4 =  ifIndex.1
                entAliasMappingIdentifier.33.5 =  ifIndex.1
                entAliasMappingIdentifier.33.10 = ifIndex.12

        Note that entries with non-zero entAliasLogicalIndexOrZero
        index values have precedence over zero-indexed entries.  In
        this example, all logical entities except 4, 5, and 10,
        associate physical entity 33 with ifIndex.6."
::= { entAliasMappingEntry 1 }
        Because only physical ports are modeled in this table, only
        entries that represent interfaces or ports are allowed.  If
        an ifEntry exists on behalf of a particular physical port,
        then this object should identify the associated 'ifEntry'.
        For repeater ports, the appropriate row in the
        'rptrPortGroupTable' should be identified instead.

        For example, suppose a physical port was represented by
        entPhysicalEntry.3, entLogicalEntry.15 existed for a
        repeater, and entLogicalEntry.22 existed for a bridge.  Then
        there might be two related instances of
        entAliasMappingIdentifier:
           entAliasMappingIdentifier.3.15 == rptrPortGroupIndex.5.2
           entAliasMappingIdentifier.3.22 == ifIndex.17
        It is possible that other mappings (besides interfaces and
        repeater ports) may be defined in the future, as required.

        Bridge ports are identified by examining the Bridge MIB and
        appropriate ifEntries associated with each 'dot1dBasePort',
        and are thus not represented in this table."
::= { entAliasMappingEntry 2 }
DESCRIPTION
        "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."
::= { entityMapping 3 }
                - entPhysicalContainsTable
        "
::= { entityGeneral 1 }
        An agent should not generate more than one entConfigChange
        'notification-event' in a given time interval (five seconds
        is the suggested default).  A 'notification-event' is the
        transmission of a single trap or inform PDU to a list of
        notification destinations.

        If additional configuration changes occur within the
        throttling period, then notification-events for these
        changes should be suppressed by the agent until the current
        throttling period expires.  At the end of a throttling
        period, one notification-event should be generated if any
        configuration changes occurred since the start of the
        throttling period.  In such a case, another throttling
        period is started right away.

        An NMS should periodically check the value of
        entLastChangeTime to detect any missed entConfigChange
        notification-events, e.g., due to throttling or transmission
        loss."
DESCRIPTION
        "The compliance statement for SNMP entities that implement
        version 1 of the Entity MIB."
MODULE  -- this module
    MANDATORY-GROUPS {
                       entityPhysicalGroup,
                       entityLogicalGroup,
                       entityMappingGroup,
                       entityGeneralGroup,
                       entityNotificationsGroup
    }
::= { entityCompliances 1 }
    GROUP entityMappingGroup
    DESCRIPTION
        "Implementation of the entPhysicalContainsTable is mandatory
        for all agents.  Implementation of the entLPMappingTable and
        entAliasMappingTables are not mandatory for agents that
        model all MIB object instances within a single naming scope.

        Note that the entAliasMappingTable may be useful for all
        agents; however, implementation of the entityLogicalGroup or
        entityLogical2Group is required to support this table."

    OBJECT entPhysicalSerialNum
    MIN-ACCESS   not-accessible
    DESCRIPTION
        "Read and write access is not required for agents that
        cannot identify serial number information for physical
        entities, and/or cannot provide non-volatile storage for
        NMS-assigned serial numbers.

        Write access is not required for agents that can identify
        serial number information for physical entities, but cannot
        provide non-volatile storage for NMS-assigned serial
        numbers.

        Write access is not required for physical entities for which
        the associated value of the entPhysicalIsFRU object is equal
        to 'false(2)'."

    OBJECT entPhysicalAlias
    MIN-ACCESS   read-only
    DESCRIPTION
        "Write access is required only if the associated
        entPhysicalClass value is equal to 'chassis(3)'."

    OBJECT entPhysicalAssetID
    MIN-ACCESS   not-accessible
    DESCRIPTION
        "Read and write access is not required for agents that
        cannot provide non-volatile storage for NMS-assigned asset
        identifiers.

        Write access is not required for physical entities for which
        the associated value of the entPhysicalIsFRU object is equal
        to 'false(2)'."

    OBJECT entPhysicalClass
    SYNTAX INTEGER {
        other(1),
        unknown(2),
        chassis(3),
        backplane(4),
        container(5),
        powerSupply(6),
        fan(7),
        sensor(8),
        module(9),
        port(10),
        stack(11)
    }
    DESCRIPTION
        "Implementation of the 'cpu(12)' enumeration is not
        required."

::= { entityCompliances 2 }
    GROUP entityMappingGroup
    DESCRIPTION
        "Implementation of the entPhysicalContainsTable is mandatory
        for all agents.  Implementation of the entLPMappingTable and
        entAliasMappingTables are not mandatory for agents that
        model all MIB object instances within a single naming scope.

        Note that the entAliasMappingTable may be useful for all
        agents; however, implementation of the entityLogicalGroup or
        entityLogical2Group is required to support this table."

    OBJECT entPhysicalSerialNum
    MIN-ACCESS   not-accessible
    DESCRIPTION
        "Read and write access is not required for agents that
        cannot identify serial number information for physical
        entities, and/or cannot provide non-volatile storage for
        NMS-assigned serial numbers.

        Write access is not required for agents that can identify
        serial number information for physical entities, but cannot
        provide non-volatile storage for NMS-assigned serial
        numbers.

        Write access is not required for physical entities for
        which the associated value of the entPhysicalIsFRU object
        is equal to 'false(2)'."

    OBJECT entPhysicalAlias
    MIN-ACCESS   read-only
    DESCRIPTION
        "Write access is required only if the associated
        entPhysicalClass value is equal to 'chassis(3)'."

    OBJECT entPhysicalAssetID
    MIN-ACCESS   not-accessible
    DESCRIPTION
        "Read and write access is not required for agents that
        cannot provide non-volatile storage for NMS-assigned asset
        identifiers.

        Write access is not required for physical entities for which
        the associated value of entPhysicalIsFRU is equal to
        'false(2)'."
::= { entityCompliances 3 }
::= { entityGroups 2 }
DESCRIPTION
        "The collection of objects used to represent physical
        system components, for which a single agent provides
        management information.  This group augments the objects
        contained in the entityPhysicalGroup."
::= { entityGroups 6 }
Physical entities -- entPhysicalTable:
   1 Field-replaceable physical chassis:
     entPhysicalDescr.1 ==             'Acme Chassis Model 100'
     entPhysicalVendorType.1 ==        acmeProducts.chassisTypes.1
     entPhysicalContainedIn.1 ==       0
     entPhysicalClass.1 ==             chassis(3)
     entPhysicalParentRelPos.1 ==      0
     entPhysicalName.1 ==              '100-A'
     entPhysicalHardwareRev.1 ==       'A(1.00.02)'
     entPhysicalSoftwareRev.1 ==       ''
     entPhysicalFirmwareRev.1 ==       ''
     entPhysicalSerialNum.1 ==         'C100076544'
     entPhysicalMfgName.1 ==           'Acme'
     entPhysicalModelName.1 ==         '100'
     entPhysicalAlias.1 ==             'cl-SJ17-3-006:rack1:rtr-U3'
     entPhysicalAssetID.1 ==           '0007372293'
     entPhysicalIsFRU.1 ==             true(1)
     entPhysicalMfgDate.1 ==           '2002-5-26,13:30:30.0,-4:0'
     entPhysicalUris.1 ==              'URN:CLEI:CNME120ARA'
   2 slots within the chassis:
     entPhysicalDescr.2 ==             'Acme Chassis Slot Type AA'
     entPhysicalVendorType.2  ==       acmeProducts.slotTypes.1
     entPhysicalContainedIn.2 ==       1
     entPhysicalClass.2 ==             container(5)
     entPhysicalParentRelPos.2 ==      1
     entPhysicalName.2 ==              'S1'
     entPhysicalHardwareRev.2 ==       'B(1.00.01)'
     entPhysicalSoftwareRev.2 ==       ''
     entPhysicalFirmwareRev.2 ==       ''
     entPhysicalSerialNum.2 ==         ''
     entPhysicalMfgName.2 ==           'Acme'
     entPhysicalModelName.2 ==         'AA'
     entPhysicalAlias.2 ==             ''
     entPhysicalAssetID.2 ==           ''
     entPhysicalIsFRU.2 ==             false(2)
     entPhysicalMfgDate.2 ==           '2002-7-26,12:22:12.0,-4:0'
     entPhysicalUris.2 ==              'URN:CLEI:CNME123ARA'

     entPhysicalDescr.3 ==             'Acme Chassis Slot Type AA'
     entPhysicalVendorType.3 =         acmeProducts.slotTypes.1
     entPhysicalContainedIn.3 ==       1
     entPhysicalClass.3 ==             container(5)
     entPhysicalParentRelPos.3 ==      2
     entPhysicalName.3 ==              'S2'
     entPhysicalHardwareRev.3 ==       '1.00.07'
     entPhysicalSoftwareRev.3 ==       ''
     entPhysicalFirmwareRev.3 ==       ''
     entPhysicalSerialNum.3 ==         ''
     entPhysicalMfgName.3 ==           'Acme'
     entPhysicalModelName.3 ==         'AA'
     entPhysicalAlias.3 ==             ''
     entPhysicalAssetID.3 ==           ''
     entPhysicalIsFRU.3 ==             false(2)
     entPhysicalMfgDate.3 ==           '2002-7-26,12:12:12.0,-4:0'
     entPhysicalUris.3 ==              'URN:CLEI:CNME123ARA'

   2 Field-replaceable modules:
   Slot 1 contains a module with 3 ports:
     entPhysicalDescr.4 ==             'Acme Router-100'
     entPhysicalVendorType.4  ==       acmeProducts.moduleTypes.14
     entPhysicalContainedIn.4 ==       2
     entPhysicalClass.4 ==             module(9)
     entPhysicalParentRelPos.4 ==      1
     entPhysicalName.4 ==              'M1'
     entPhysicalHardwareRev.4 ==       '1.00.07'
     entPhysicalSoftwareRev.4 ==       '1.4.1'
     entPhysicalFirmwareRev.4 ==       'A(1.1)'
     entPhysicalSerialNum.4 ==         'C100087363'
     entPhysicalMfgName.4 ==           'Acme'
     entPhysicalModelName.4 ==         'R100-FE'
     entPhysicalAlias.4 ==             'rtr-U3:m1:SJ17-3-eng'
     entPhysicalAssetID.4 ==           '0007372462'
     entPhysicalIsFRU.4 ==             true(1)
     entPhysicalMfgDate.4 ==           '2003-7-18,13:30:30.0,-4:0'
     entPhysicalUris.4 ==              'URN:CLEI:CNRU123CAA'

     entPhysicalDescr.5 ==             'Acme Ethernet-100 Port'
     entPhysicalVendorType.5  ==       acmeProducts.portTypes.2
     entPhysicalContainedIn.5 ==       4
     entPhysicalClass.5 ==             port(10)
     entPhysicalParentRelPos.5 ==      1
     entPhysicalName.5 ==              'P1'
     entPhysicalHardwareRev.5 ==       'G(1.02)'
     entPhysicalSoftwareRev.5 ==       ''
     entPhysicalFirmwareRev.5 ==       '1.1'
     entPhysicalSerialNum.5 ==         ''
     entPhysicalMfgName.5 ==           'Acme'
     entPhysicalModelName.5 ==         'FE-100'
     entPhysicalAlias.5 ==             ''
     entPhysicalAssetID.5 ==           ''
     entPhysicalIsFRU.5 ==             false(2)
     entPhysicalMfgDate.5 ==           '2003-7-18,14:20:22.0,-4:0'
     entPhysicalUris.5 ==              'URN:CLEI:CNMES23ARA'

     entPhysicalDescr.6 ==             'Acme Ethernet-100 Port'
     entPhysicalVendorType.6  ==       acmeProducts.portTypes.2
     entPhysicalContainedIn.6 ==       4
     entPhysicalClass.6 ==             port(10)
     entPhysicalParentRelPos.6 ==      2
     entPhysicalName.6 ==              'P2'
     entPhysicalHardwareRev.6 ==       'G(1.02)'
     entPhysicalSoftwareRev.6 ==       ''
     entPhysicalFirmwareRev.6 ==       '1.1'
     entPhysicalSerialNum.6 ==         ''
     entPhysicalMfgName.6 ==           'Acme'
     entPhysicalModelName.6 ==         'FE-100'
     entPhysicalAlias.6 ==             ''
     entPhysicalAssetID.6 ==           ''
     entPhysicalIsFRU.6 ==             false(2)
     entPhysicalMfgDate.6 ==           '2003-7-19,10:15:15.0,-4:0'
     entPhysicalUris.6 ==              'URN:CLEI:CNMES23ARA'

     entPhysicalDescr.7 ==             'Acme Router-100 FDDI-Port'
     entPhysicalVendorType.7  ==       acmeProducts.portTypes.3
     entPhysicalContainedIn.7 ==       4
     entPhysicalClass.7 ==             port(10)
     entPhysicalParentRelPos.7 ==      3
     entPhysicalName.7 ==              'P3'
     entPhysicalHardwareRev.7 ==       'B(1.03)'
     entPhysicalSoftwareRev.7 ==       '2.5.1'
     entPhysicalFirmwareRev.7 ==       '2.5F'
     entPhysicalSerialNum.7 ==         ''
     entPhysicalMfgName.7 ==           'Acme'
     entPhysicalModelName.7 ==         'FDDI-100'
     entPhysicalAlias.7 ==             ''
     entPhysicalAssetID.7 ==           ''
     entPhysicalIsFRU.7 ==             false(2)
  Slot 2 contains another 3-port module:
     entPhysicalDescr.8 ==             'Acme Router-100 Comm Module'
     entPhysicalVendorType.8  ==       acmeProducts.moduleTypes.15
     entPhysicalContainedIn.8 ==       3
     entPhysicalClass.8 ==             module(9)
     entPhysicalParentRelPos.8 ==      1
     entPhysicalName.8 ==              'M2'
     entPhysicalHardwareRev.8 ==       '2.01.00'
     entPhysicalSoftwareRev.8 ==       '3.0.7'
     entPhysicalFirmwareRev.8 ==       'A(1.2)'
     entPhysicalSerialNum.8 ==         'C100098732'
     entPhysicalMfgName.8 ==           'Acme'
     entPhysicalModelName.8 ==         'C100'
     entPhysicalAlias.8 ==             'rtr-U3:m2:SJ17-2-eng'
     entPhysicalAssetID.8 ==           '0007373982'
     entPhysicalIsFRU.8 ==             true(1)
     entPhysicalMfgDate.8 ==           '2002-5-26,13:30:15.0,-4:0'
     entPhysicalUris.8 ==              'URN:CLEI:CNRT321MAA'

     entPhysicalDescr.9 ==             'Acme Fddi-100 Port'
     entPhysicalVendorType.9 ==        acmeProducts.portTypes.5
     entPhysicalContainedIn.9 ==       8
     entPhysicalClass.9 ==             port(10)
     entPhysicalParentRelPos.9 ==      1
     entPhysicalName.9 ==              'FDDI Primary'
     entPhysicalHardwareRev.9 ==       'CC(1.07)'
     entPhysicalSoftwareRev.9 ==       '2.0.34'
     entPhysicalFirmwareRev.9 ==       '1.1'
     entPhysicalSerialNum.9 ==         ''
     entPhysicalMfgName.9 ==           'Acme'
     entPhysicalModelName.9 ==         'FDDI-100'
     entPhysicalAlias.9 ==             ''
     entPhysicalAssetID.9 ==           ''
     entPhysicalIsFRU.9 ==             false(2)

     entPhysicalDescr.10 ==            'Acme Ethernet-100 Port'
     entPhysicalVendorType.10 ==       acmeProducts.portTypes.2
     entPhysicalContainedIn.10 ==      8
     entPhysicalClass.10 ==            port(10)
     entPhysicalParentRelPos.10 ==     2
     entPhysicalName.10 ==             'Ethernet A'
     entPhysicalHardwareRev.10 ==      'G(1.04)'
     entPhysicalSoftwareRev.10 ==      ''
     entPhysicalFirmwareRev.10 ==      '1.3'
     entPhysicalSerialNum.10 ==        ''
     entPhysicalMfgName.10 ==          'Acme'
     entPhysicalModelName.10 ==        'FE-100'
     entPhysicalAlias.10 ==            ''
     entPhysicalAssetID.10 ==          ''
     entPhysicalIsFRU.10 ==            false(2)
     entPhysicalMfgDate.10 ==          '2002-7-26,13:30:15.0,-4:0'
     entPhysicalUris.10 ==             'URN:CLEI:CNMES23ARA'

     entPhysicalDescr.11 ==            'Acme Ethernet-100 Port'
     entPhysicalVendorType.11 ==       acmeProducts.portTypes.2
     entPhysicalContainedIn.11 ==      8
     entPhysicalClass.11 ==            port(10)
     entPhysicalParentRelPos.11 ==     3
     entPhysicalName.11 ==             'Ethernet B'
     entPhysicalHardwareRev.11 ==      'G(1.04)'
     entPhysicalSoftwareRev.11 ==      ''
     entPhysicalFirmwareRev.11 ==      '1.3'
     entPhysicalSerialNum.11 ==        ''
     entPhysicalMfgName.11 ==          'Acme'
     entPhysicalModelName.11 ==        'FE-100'
     entPhysicalAlias.11 ==            ''
     entPhysicalAssetID.11 ==          ''
     entPhysicalIsFRU.11 ==            false(2)
     entPhysicalMfgDate.11 ==          '2002-8-16,15:35:15.0,-4:0'
     entPhysicalUris.11 ==             'URN:CLEI:CNMES23ARA'

  Logical entities -- entLogicalTable; no SNMPv3 support
   2 OSPF instances:
     entLogicalDescr.1 ==              'Acme OSPF v1.1'
     entLogicalType.1 ==               ospf
     entLogicalCommunity.1 ==          'public-ospf1'
     entLogicalTAddress.1 ==           192.0.2.1:161
     entLogicalTDomain.1 ==            snmpUDPDomain
     entLogicalContextEngineID.1 ==    ''
     entLogicalContextName.1 ==        ''

     entLogicalDescr.2 ==              'Acme OSPF v1.1'
     entLogicalType.2 ==               ospf
     entLogicalCommunity.2 ==          'public-ospf2'
     entLogicalTAddress.2 ==           192.0.2.1:161
     entLogicalTDomain.2 ==            snmpUDPDomain
     entLogicalContextEngineID.2 ==    ''
     entLogicalContextName.2 ==        ''

   2 logical bridges:
     entLogicalDescr.3 ==              'Acme Bridge v2.1.1'
     entLogicalType.3  ==              dot1dBridge
     entLogicalCommunity.3 ==          'public-bridge1'
     entLogicalTAddress.3 ==           192.0.2.1:161
     entLogicalTDomain.3 ==            snmpUDPDomain
     entLogicalContextEngineID.3 ==    ''
     entLogicalContextName.3 ==        ''

     entLogicalDescr.4 ==              'Acme Bridge v2.1.1'
     entLogicalType.4 ==               dot1dBridge
     entLogicalCommunity.4 ==          'public-bridge2'
     entLogicalTAddress.4 ==           192.0.2.1:161
     entLogicalTDomain.4 ==            snmpUDPDomain
     entLogicalContextEngineID.4 ==    ''
     entLogicalContextName.4 ==        ''
 2nd OSPF instance: uses module 2-port 1
     entLPPhysicalIndex.2.9 ==         9

 1st bridge group: uses module 1, all ports

 [ed. -- Note that these mappings are included in the table because
 another logical entity (1st OSPF) utilizes one of the
 ports.  If this were not the case, then a single mapping
 to the module (e.g., entLPPhysicalIndex.3.4) would be
 present instead.]
     entLPPhysicalIndex.3.5 ==         5
     entLPPhysicalIndex.3.6 ==         6
     entLPPhysicalIndex.3.7 ==         7

 2nd bridge group: uses module 2, all ports
     entLPPhysicalIndex.4.9  ==        9
     entLPPhysicalIndex.4.10 ==        10
     entLPPhysicalIndex.4.11 ==        11
 Example 2: ifIndex values are not shared by all logical entities;
        (Bridge-1 uses ifIndex values 101 - 103 and Bridge-2 uses
        entAliasMappingIdentifier.6.3 ==  ifIndex.102
        entAliasMappingIdentifier.7.0 ==  ifIndex.3
        entAliasMappingIdentifier.7.3 ==  ifIndex.103
        entAliasMappingIdentifier.9.0 ==  ifIndex.4
        entAliasMappingIdentifier.9.4 ==  ifIndex.204
        entAliasMappingIdentifier.10.0 == ifIndex.5
        entAliasMappingIdentifier.10.4 == ifIndex.205
        entAliasMappingIdentifier.11.0 == ifIndex.6
        entAliasMappingIdentifier.11.4 == ifIndex.206
 container 1 has a module:
     entPhysicalChildIndex.2.4 ==      4

 container 2 has a module:
     entPhysicalChildIndex.3.8 ==      8

 module 1 has 3 ports:
     entPhysicalChildIndex.4.5 ==      5
     entPhysicalChildIndex.4.6 ==      6
     entPhysicalChildIndex.4.7 ==      7

 module 2 has 3 ports:
     entPhysicalChildIndex.8.9 ==      9
     entPhysicalChildIndex.8.10 ==     10
     entPhysicalChildIndex.8.11 ==     11
     entPhysicalClass.1 ==       chassis(3)
     entPhysicalParentRelPos.1 ==0
     entPhysicalName.1 ==        '110-B'
     entPhysicalHardwareRev.1 == 'A(1.02.00)'
     entPhysicalSoftwareRev.1 == ''
     entPhysicalFirmwareRev.1 == ''
     entPhysicalSerialNum.1 ==   'C100079294'
     entPhysicalMfgName.1 ==     'Acme'
     entPhysicalModelName.1 ==   '110'
     entPhysicalAlias.1 ==       'bldg09:floor1:rptr18:0067eea0229f'
     entPhysicalAssetID.1 ==     '0007386327'
     entPhysicalIsFRU.1 ==       true(1)

  2 Chassis Ethernet Backplanes:
     entPhysicalDescr.2 ==          'Acme Ethernet Backplane Type A'
     entPhysicalVendorType.2 ==     acmeProducts.backplaneTypes.1
     entPhysicalContainedIn.2 ==    1
     entPhysicalClass.2 ==          backplane(4)
     entPhysicalParentRelPos.2 ==   1
     entPhysicalName.2 ==           'B1'
     entPhysicalHardwareRev.2 ==    'A(2.04.01)'
     entPhysicalSoftwareRev.2 ==    ''
     entPhysicalFirmwareRev.2 ==    ''
     entPhysicalSerialNum.2 ==      ''
     entPhysicalMfgName.2 ==        'Acme'
     entPhysicalModelName.2 ==      'BK-A'
     entPhysicalAlias.2 ==          ''
     entPhysicalAssetID.2 ==        ''
     entPhysicalIsFRU.2 ==          false(2)

     entPhysicalDescr.3 ==          'Acme Ethernet Backplane Type A'
     entPhysicalVendorType.3  ==    acmeProducts.backplaneTypes.1
     entPhysicalContainedIn.3 ==    1
     entPhysicalClass.3 ==          backplane(4)
     entPhysicalParentRelPos.3 ==   2
     entPhysicalName.3 ==           'B2'
     entPhysicalHardwareRev.3 ==    'A(2.04.01)'
     entPhysicalSoftwareRev.3 ==    ''
     entPhysicalFirmwareRev.3 ==    ''
     entPhysicalSerialNum.3 ==      ''
     entPhysicalMfgName.3 ==        'Acme'
     entPhysicalModelName.3 ==      'BK-A'
     entPhysicalAlias.3 ==          ''
     entPhysicalAssetID.3 ==        ''
     entPhysicalIsFRU.3 ==          false(2)
  3 slots within the chassis:
     entPhysicalDescr.4 ==          'Acme Hub Slot Type RB'
     entPhysicalVendorType.4  ==    acmeProducts.slotTypes.5
     entPhysicalContainedIn.4 ==    1
     entPhysicalClass.4 ==          container(5)
     entPhysicalParentRelPos.4 ==   1
     entPhysicalName.4 ==           'Slot 1'
     entPhysicalHardwareRev.4 ==    'B(1.00.03)'
     entPhysicalSoftwareRev.4 ==    ''
     entPhysicalFirmwareRev.4 ==    ''
     entPhysicalSerialNum.4 ==      ''
     entPhysicalMfgName.4 ==        'Acme'
     entPhysicalModelName.4 ==      'RB'
     entPhysicalAlias.4 ==          ''
     entPhysicalAssetID.4 ==        ''
     entPhysicalIsFRU.4 ==          false(2)

     entPhysicalDescr.5 ==          'Acme Hub Slot Type RB'
     entPhysicalVendorType.5  ==    acmeProducts.slotTypes.5
     entPhysicalContainedIn.5 ==    1
     entPhysicalClass.5 ==          container(5)
     entPhysicalParentRelPos.5 ==   2
     entPhysicalName.5 ==           'Slot 2'
     entPhysicalHardwareRev.5 ==    'B(1.00.03)'
     entPhysicalSoftwareRev.5 ==    ''
     entPhysicalFirmwareRev.5 ==    ''
     entPhysicalSerialNum.5 ==      ''
     entPhysicalMfgName.5 ==        'Acme'
     entPhysicalModelName.5 ==      'RB'
     entPhysicalAlias.5 ==          ''
     entPhysicalAssetID.5 ==        ''
     entPhysicalIsFRU.5 ==          false(2)

     entPhysicalDescr.6 ==          'Acme Hub Slot Type RB'
     entPhysicalVendorType.6  ==    acmeProducts.slotTypes.5
     entPhysicalContainedIn.6 ==    1
     entPhysicalClass.6 ==          container(5)
     entPhysicalParentRelPos.6 ==   3
     entPhysicalName.6 ==           'Slot 3'
     entPhysicalHardwareRev.6 ==    'B(1.00.03)'
     entPhysicalSoftwareRev.6 ==    ''
     entPhysicalFirmwareRev.6 ==    ''
     entPhysicalSerialNum.6 ==      ''
     entPhysicalMfgName.6 ==        'Acme'
     entPhysicalModelName.6 ==      'RB'
     entPhysicalAlias.6 ==          ''
     entPhysicalAssetID.6 ==        ''
     entPhysicalIsFRU.6 ==          false(2)
  Slot 1 contains a plug-in module with 4 10-BaseT ports:
     entPhysicalDescr.7  ==         'Acme 10Base-T Module 114'
     entPhysicalVendorType.7 ==     acmeProducts.moduleTypes.32
     entPhysicalContainedIn.7  ==   4
     entPhysicalClass.7 ==          module(9)
     entPhysicalParentRelPos.7 ==   1
     entPhysicalName.7 ==           'M1'
     entPhysicalHardwareRev.7 ==    'A(1.02.01)'
     entPhysicalSoftwareRev.7 ==    '1.7.2'
     entPhysicalFirmwareRev.7 ==    'A(1.5)'
     entPhysicalSerialNum.7 ==      'C100096244'
     entPhysicalMfgName.7 ==        'Acme'
     entPhysicalModelName.7 =       '114'
     entPhysicalAlias.7 ==          'bldg09:floor1:eng'
     entPhysicalAssetID.7 ==        '0007962951'
     entPhysicalIsFRU.7 ==          true(1)

     entPhysicalDescr.8 ==          'Acme 10Base-T Port RB'
     entPhysicalVendorType.8 ==     acmeProducts.portTypes.10
     entPhysicalContainedIn.8  ==   7
     entPhysicalClass.8 ==          port(10)
     entPhysicalParentRelPos.8 ==   1
     entPhysicalName.8 ==           'Ethernet-A'
     entPhysicalHardwareRev.8 ==    'A(1.04F)'
     entPhysicalSoftwareRev.8 ==    ''
     entPhysicalFirmwareRev.8 ==    '1.4'
     entPhysicalSerialNum.8 ==      ''
     entPhysicalMfgName.8 ==        'Acme'
     entPhysicalModelName.8 ==      'RB'
     entPhysicalAlias.8 ==          ''
     entPhysicalAssetID.8 ==        ''
     entPhysicalIsFRU.8 ==          false(2)

     entPhysicalDescr.9  ==         'Acme 10Base-T Port RB'
     entPhysicalVendorType.9 ==     acmeProducts.portTypes.10
     entPhysicalContainedIn.9 ==    7
     entPhysicalClass.9 ==          port(10)
     entPhysicalParentRelPos.9 ==   2
     entPhysicalName.9 ==           'Ethernet-B'
     entPhysicalHardwareRev.9 ==    'A(1.04F)'
     entPhysicalSoftwareRev.9 ==    ''
     entPhysicalFirmwareRev.9 ==    '1.4'
     entPhysicalSerialNum.9 ==      ''
     entPhysicalMfgName.9 ==        'Acme'
     entPhysicalModelName.9 =       'RB'
     entPhysicalAlias.9 ==          ''
     entPhysicalAssetID.9 ==        ''
     entPhysicalIsFRU.9 ==          false(2)
     entPhysicalDescr.10 ==         'Acme 10Base-T Port RB'
     entPhysicalVendorType.10 ==    acmeProducts.portTypes.10
     entPhysicalContainedIn.10 ==   7
     entPhysicalClass.10 ==         port(10)
     entPhysicalParentRelPos.10 ==  3
     entPhysicalName.10 ==          'Ethernet-C'
     entPhysicalHardwareRev.10 ==   'B(1.02.07)'
     entPhysicalSoftwareRev.10 ==   ''
     entPhysicalFirmwareRev.10 ==   '1.4'
     entPhysicalSerialNum.10 ==     ''
     entPhysicalMfgName.10 ==       'Acme'
     entPhysicalModelName.10 ==     'RB'
     entPhysicalAlias.10 ==         ''
     entPhysicalAssetID.10 ==       ''
     entPhysicalIsFRU.10 ==         false(2)

     entPhysicalDescr.11 ==         'Acme 10Base-T Port RB'
     entPhysicalVendorType.11  ==   acmeProducts.portTypes.10
     entPhysicalContainedIn.11 ==   7
     entPhysicalClass.11 ==         port(10)
     entPhysicalParentRelPos.11 ==  4
     entPhysicalName.11 ==          'Ethernet-D'
     entPhysicalHardwareRev.11 ==   'B(1.02.07)'
     entPhysicalSoftwareRev.11 ==   ''
     entPhysicalFirmwareRev.11 ==   '1.4'
     entPhysicalSerialNum.11 ==     ''
     entPhysicalMfgName.11 ==       'Acme'
     entPhysicalModelName.11 ==     'RB'
     entPhysicalAlias.11 ==         ''
     entPhysicalAssetID.11 ==       ''
     entPhysicalIsFRU.11 ==         false(2)

  Slot 2 contains another ethernet module with 2 ports.
     entPhysicalDescr.12 ==         'Acme 10Base-T Module Model 4'
     entPhysicalVendorType.12 ==    acmeProducts.moduleTypes.30
     entPhysicalContainedIn.12 =    5
     entPhysicalClass.12 ==         module(9)
     entPhysicalParentRelPos.12 ==  1
     entPhysicalName.12 ==          'M2'
     entPhysicalHardwareRev.12 ==   'A(1.01.07)'
     entPhysicalSoftwareRev.12 ==   '1.8.4'
     entPhysicalFirmwareRev.12 ==   'A(1.8)'
     entPhysicalSerialNum.12 ==     'C100102384'
     entPhysicalMfgName.12 ==       'Acme'
     entPhysicalModelName.12 ==     '4'
     entPhysicalAlias.12 ==         'bldg09:floor1:devtest'
     entPhysicalAssetID.12 ==       '0007968462'
     entPhysicalIsFRU.12 ==         true(1)
     entPhysicalDescr.13 ==         'Acme 802.3 AUI Port'
     entPhysicalVendorType.13  ==   acmeProducts.portTypes.11
     entPhysicalContainedIn.13 ==   12
     entPhysicalClass.13 ==         port(10)
     entPhysicalParentRelPos.13 ==  1
     entPhysicalName.13 ==          'AUI'
     entPhysicalHardwareRev.13 ==   'A(1.06F)'
     entPhysicalSoftwareRev.13 ==   ''
     entPhysicalFirmwareRev.13 ==   '1.5'
     entPhysicalSerialNum.13 ==     ''
     entPhysicalMfgName.13 ==       'Acme'
     entPhysicalModelName.13 ==     ''
     entPhysicalAlias.13 ==         ''
     entPhysicalAssetID.13 ==       ''
     entPhysicalIsFRU.13 ==         false(2)

     entPhysicalDescr.14 ==         'Acme 10Base-T Port RD'
     entPhysicalVendorType.14  ==   acmeProducts.portTypes.14
     entPhysicalContainedIn.14 ==   12
     entPhysicalClass.14 ==         port(10)
     entPhysicalParentRelPos.14 ==  2
     entPhysicalName.14 ==          'E2'
     entPhysicalHardwareRev.14 ==   'B(1.01.02)'
     entPhysicalSoftwareRev.14 ==   ''
     entPhysicalFirmwareRev.14 ==   '2.1'
     entPhysicalSerialNum.14 ==     ''
     entPhysicalMfgName.14 ==       'Acme'
     entPhysicalModelName.14 ==     ''
     entPhysicalAlias.14 ==         ''
     entPhysicalAssetID.14 ==       ''
     entPhysicalIsFRU.14 ==         false(2)
  Repeater 2--comprised of any ports attached to backplane 2:
     entLogicalDescr.2 ==           'Acme repeater v3.1'
     entLogicalType.2  ==           snmpDot3RptrMgt
     entLogicalCommunity.2 ==       'public-repeater2'
     entLogicalTAddress.2 ==        192.0.2.1:161
     entLogicalTDomain.2 ==         snmpUDPDomain
     entLogicalContextEngineID.2 == '80000777017c7d7e7f'H
     entLogicalContextName.2 ==     'repeater2'
 repeater1 uses backplane 1, slot 1-ports 1 & 2, slot 2-port 1
 [ed. -- Note that a mapping to the module is not included,
  because this example represents a port-switchable hub.
  Even though all ports on the module could belong to the
  same repeater as a matter of configuration, the LP port
  mappings should not be replaced dynamically with a single
  mapping for the module (e.g., entLPPhysicalIndex.1.7).
  If all ports on the module shared a single backplane connection,
  then a single mapping for the module would be more appropriate.]

    entLPPhysicalIndex.1.2 ==       2
    entLPPhysicalIndex.1.8 ==       8
    entLPPhysicalIndex.1.9 ==       9
    entLPPhysicalIndex.1.13 ==      13

 repeater2 uses backplane 2, slot 1-ports 3 & 4, slot 2-port 2
     entLPPhysicalIndex.2.3 ==      3
     entLPPhysicalIndex.2.10 ==     10
     entLPPhysicalIndex.2.11 ==     11
     entLPPhysicalIndex.2.14 ==     14
 container 1 has a module:
     entPhysicalChildIndex.4.7 ==   7

 container 2 has a module
     entPhysicalChildIndex.5.12 ==  12
 [ed. -- in this example, container 3 is empty.]

 module 1 has 4 ports:
     entPhysicalChildIndex.7.8 ==   8
     entPhysicalChildIndex.7.9 ==   9
     entPhysicalChildIndex.7.10 ==  10
     entPhysicalChildIndex.7.11 ==  11

 module 2 has 2 ports:
     entPhysicalChildIndex.12.13 == 13
     entPhysicalChildIndex.12.14 == 14
  These objects expose information about the physical entities
  within a managed system, which may be used to identify the vendor,
  model, and version information of each system component.
  This object can allow asset identifiers for various system
  components to be exposed, in the event this MIB object is actually
  configured by an NMS application.
  These objects expose the type of logical entities present in the
  managed system.
  This object exposes community names associated with particular
  logical entities within the system.
  These objects expose network addresses that can be used to
  communicate with an SNMP agent on behalf of particular logical
  entities within the system.
  These objects identify the authoritative SNMP engine that contains
  information on behalf of particular logical entities within the
  system.
          Descriptor        OBJECT IDENTIFIER value
          ----------        -----------------------
          entityMIB         { mib-2 47 }