entPhysicalAlias    OBJECT-TYPE    SYNTAX      SnmpAdminString (SIZE (0..32))    MAX-ACCESS  read-write    STATUS      current    DESCRIPTION            "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 an physical entity, the value            of entPhysicalAlias associated with that entity is set to            the zero-length string.  However, 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,McCloghrie & Bierman        Standards Track                    [Page 23]RFC 2737                 Entity MIB (Version 2)            December 1999            including those which result in a change of the physical            entity's entPhysicalIndex value."    ::= { entPhysicalEntry 14 }entPhysicalAssetID OBJECT-TYPE    SYNTAX      SnmpAdminString (SIZE (0..32))    MAX-ACCESS  read-write    STATUS      current    DESCRIPTION            "This object is a user-assigned asset tracking identifier            for the physical entity as specified by a network manager,            and provides non-volatile storage of this information.            On the first instantiation of an physical entity, the value            of entPhysicalAssetID associated with that entity is set to            the zero-length string.            Not every physical component will have a 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 which result 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 }entPhysicalIsFRU OBJECT-TYPE    SYNTAX      TruthValue    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "This object indicates whether or not this physical entity            is considered a 'field replaceable unit' by the vendor.  IfMcCloghrie & Bierman        Standards Track                    [Page 24]RFC 2737                 Entity MIB (Version 2)            December 1999            this object contains the value 'true(1)' then this            entPhysicalEntry identifies a field replaceable unit.  For            all entPhysicalEntries which represent components that are            permanently contained within a field replaceable unit, the            value 'false(2)' should be returned for this object."    ::= { entPhysicalEntry 16 }--           The Logical Entity TableentLogicalTable OBJECT-TYPE    SYNTAX      SEQUENCE OF EntLogicalEntry    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION            "This table contains one row per logical entity.  For agents            which implement more than one naming scope, at least one            entry must exist. Agents which instantiate all MIB objects            within a single naming scope are not required to implement            this table."    ::= { entityLogical 1 }entLogicalEntry       OBJECT-TYPE    SYNTAX      EntLogicalEntry    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION            "Information about a particular logical entity.  Entities            may be managed by this agent or other SNMP agents (possibly)            in the same chassis."    INDEX       { entLogicalIndex }    ::= { entLogicalTable 1 }EntLogicalEntry ::= SEQUENCE {      entLogicalIndex            INTEGER,      entLogicalDescr            SnmpAdminString,      entLogicalType             AutonomousType,      entLogicalCommunity        OCTET STRING,      entLogicalTAddress         TAddress,      entLogicalTDomain          TDomain,      entLogicalContextEngineID  SnmpEngineIdOrNone,      entLogicalContextName      SnmpAdminString}entLogicalIndex OBJECT-TYPE    SYNTAX      INTEGER (1..2147483647)    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTIONMcCloghrie & Bierman        Standards Track                    [Page 25]RFC 2737                 Entity MIB (Version 2)            December 1999            "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 are not            necessarily contiguous."    ::= { entLogicalEntry 1 }entLogicalDescr OBJECT-TYPE    SYNTAX      SnmpAdminString    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "A textual description of the logical entity.  This object            should contain a string which identifies the manufacturer's            name for the logical entity, and should be set to a distinct            value for each version of the logical entity. "    ::= { entLogicalEntry 2 }entLogicalType OBJECT-TYPE    SYNTAX      AutonomousType    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "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 which represents the major MIB            module, or the majority of the MIB modules, supported by the            logical entity.  For example:               a logical entity of a regular host/router -> mib-2               a logical entity of a 802.1d bridge -> dot1dBridge               a logical entity of a 802.3 repeater -> snmpDot3RptrMgmt            If an appropriate node in the SMI's naming hierarchy cannot            be identified, the value 'mib-2' should be used."    ::= { entLogicalEntry 3 }entLogicalCommunity OBJECT-TYPE    SYNTAX      OCTET STRING (SIZE (0..255))    MAX-ACCESS  read-only    STATUS      deprecated    DESCRIPTION            "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 managed            objects) and may also return a community string based on the            privileges of the request used to read this object.  Note            that an agent may return a community string with read-only            privileges, even if this object is accessed with a read-            write community string. However, the agent must take careMcCloghrie & Bierman        Standards Track                    [Page 26]RFC 2737                 Entity MIB (Version 2)            December 1999            not to return a community string which 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 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 }entLogicalTAddress OBJECT-TYPE    SYNTAX      TAddress    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "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 octets long, the initial            4 octets containing the IP-address in network-byte order and            the last 2 containing the UDP port in network-byte order.            Consult 'Transport Mappings for Version 2 of the Simple            Network Management Protocol' (RFC 1906 [RFC1906]) for            further information on snmpUDPDomain."McCloghrie & Bierman        Standards Track                    [Page 27]RFC 2737                 Entity MIB (Version 2)            December 1999    ::= { entLogicalEntry 5 }entLogicalTDomain OBJECT-TYPE    SYNTAX      TDomain    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "Indicates the kind of transport service by which the            logical entity receives network management traffic.            Possible values for this object are presently found in the            Transport Mappings for SNMPv2 document (RFC 1906            [RFC1906])."    ::= { entLogicalEntry 6 }entLogicalContextEngineID    OBJECT-TYPE    SYNTAX      SnmpEngineIdOrNone    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "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.            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 }entLogicalContextName    OBJECT-TYPE    SYNTAX      SnmpAdminString    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "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 object, together with the associated            entLogicalContextEngineID object, defines the context            associated with a particular logical entity, and allowsMcCloghrie & Bierman        Standards Track                    [Page 28]RFC 2737                 Entity MIB (Version 2)            December 1999            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 th