MAX-ACCESS  read-only    STATUS      currentMcCloghrie & Bierman        Standards Track                    [Page 17]RFC 2737                 Entity MIB (Version 2)            December 1999    DESCRIPTION            "An indication of the vendor-specific hardware type of the            physical entity.  Note that this is different from the            definition of MIB-II's sysObjectID.            An agent should set this object to a 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 }entPhysicalContainedIn OBJECT-TYPE    SYNTAX      INTEGER (0..2147483647)    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "The value of entPhysicalIndex for the physical entity which            'contains' this physical entity.  A value of zero indicates            this physical entity is not contained in any other physical            entity.  Note that the set of 'containment' relationships            define a strict hierarchy; that is, recursion is not            allowed.            In the event 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 }entPhysicalClass OBJECT-TYPE    SYNTAX      PhysicalClass    MAX-ACCESS  read-only    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 which most accurately indicates the general class of            the physical entity, or the primary class if there is more            than one.            If no appropriate standard registration identifier existsMcCloghrie & Bierman        Standards Track                    [Page 18]RFC 2737                 Entity MIB (Version 2)            December 1999            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 }entPhysicalParentRelPos OBJECT-TYPE    SYNTAX      INTEGER (-1..2147483647)    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "An indication of the relative position of this 'child'            component among all its 'sibling' components. Sibling            components are defined as entPhysicalEntries which share the            same instance values of each of the entPhysicalContainedIn            and entPhysicalClass objects.            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).            This value should match any external labeling of the            physical component if possible. 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 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,McCloghrie & Bierman        Standards Track                    [Page 19]RFC 2737                 Entity MIB (Version 2)            December 1999            then the first sibling should be associated with a            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 }entPhysicalName OBJECT-TYPE    SYNTAX      SnmpAdminString    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "The textual name of the physical entity.  The value of this            object should be the name of the component as assigned by            the local device and should be suitable for use in commands            entered at the device's `console'.  This might be a text            name, such as `console' or a simple component number (e.g.,            port or module number), such as `1', depending on the            physical component naming syntax of the device.            If there is no local name, or 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 }entPhysicalHardwareRev    OBJECT-TYPE    SYNTAX      SnmpAdminString    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "The vendor-specific hardware revision string for the            physical entity.  The preferred value is the hardware            revision identifier actually printed on the component itself            (if present).            Note that if revision information is stored internally in aMcCloghrie & Bierman        Standards Track                    [Page 20]RFC 2737                 Entity MIB (Version 2)            December 1999            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 this information is unknown to            the agent, then this object will contain a zero-length            string."    ::= { entPhysicalEntry 8 }entPhysicalFirmwareRev    OBJECT-TYPE    SYNTAX      SnmpAdminString    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "The vendor-specific firmware revision string for the            physical entity.            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 this information is unknown to the            agent, then this object will contain a zero-length string."    ::= { entPhysicalEntry 9 }entPhysicalSoftwareRev    OBJECT-TYPE    SYNTAX      SnmpAdminString    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "The vendor-specific software revision string for the            physical entity.            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 this information is unknown to the            agent, then this object will contain a zero-length string."    ::= { entPhysicalEntry 10 }entPhysicalSerialNum   OBJECT-TYPE    SYNTAX      SnmpAdminString (SIZE (0..32))McCloghrie & Bierman        Standards Track                    [Page 21]RFC 2737                 Entity MIB (Version 2)            December 1999    MAX-ACCESS  read-write    STATUS      current    DESCRIPTION            "The vendor-specific serial number string for the physical            entity.  The preferred value is the serial number string            actually printed on the component itself (if present).            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 which 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 which result in a change of the physical            entity's entPhysicalIndex value."    ::= { entPhysicalEntry 11 }entPhysicalMfgName   OBJECT-TYPE    SYNTAX      SnmpAdminString    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "The name of the manufacturer of this physical component.            The preferred value is the manufacturer name string actually            printed on the component itself (if present).McCloghrie & Bierman        Standards Track                    [Page 22]RFC 2737                 Entity MIB (Version 2)            December 1999            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 }entPhysicalModelName   OBJECT-TYPE    SYNTAX      SnmpAdminString    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "The vendor-specific model name identifier string associated            with this physical component.  The preferred value is the            customer-visible part number, which may be printed on the            component itself.            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 }