IMPORTS

    MODULE-IDENTITY, OBJECT-TYPE, mib-2, NOTIFICATION-TYPE

        FROM SNMPv2-SMI

    TDomain, TAddress, TEXTUAL-CONVENTION,

    AutonomousType, RowPointer, TimeStamp, TruthValue

        FROM SNMPv2-TC

    MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP

        FROM SNMPv2-CONF

    SnmpAdminString

        FROM SNMP-FRAMEWORK-MIB;

entityMIB MODULE-IDENTITY

    LAST-UPDATED "9912070000Z" 

    ORGANIZATION "IETF ENTMIB Working Group"

    CONTACT-INFO

            "        WG E-mail: [email protected]

                  Subscribe: [email protected]

                         msg body: subscribe entmib

                     Keith McCloghrie

                     ENTMIB Working Group Chair

                     Cisco Systems Inc.

                     170 West Tasman Drive

                     San Jose, CA 95134

                     +1 408-526-5260

                     [email protected]

                     Andy Bierman

                     ENTMIB Working Group Editor

                     Cisco Systems Inc.

                     170 West Tasman Drive

                     San Jose, CA 95134

                     +1 408-527-3711

                     [email protected]"

    DESCRIPTION

            "The MIB module for representing multiple logical

            entities supported by a single SNMP agent."

    REVISION        "9912070000Z"

    DESCRIPTION

            "Initial Version of Entity MIB (Version 2).

             This revision obsoletes RFC 2037.

             This version published as RFC 2737."

    REVISION        "9610310000Z"

    DESCRIPTION

            "Initial version (version 1), published as

             RFC 2037."

    ::= { mib-2 47 }

entityMIBObjects OBJECT IDENTIFIER ::= { entityMIB 1 }

entityPhysical OBJECT IDENTIFIER ::= { entityMIBObjects 1 }

entityLogical  OBJECT IDENTIFIER ::= { entityMIBObjects 2 }

entityMapping  OBJECT IDENTIFIER ::= { entityMIBObjects 3 }

entityGeneral  OBJECT IDENTIFIER ::= { entityMIBObjects 4 }

PhysicalIndex ::= TEXTUAL-CONVENTION

    STATUS            current

    DESCRIPTION

            "An arbitrary value which uniquely identifies the physical

            entity.  The value should be a small positive integer; index

            values for different physical entities are not necessarily

            contiguous."

    SYNTAX INTEGER (1..2147483647)

PhysicalClass ::= TEXTUAL-CONVENTION

    STATUS            current

    DESCRIPTION

            "An enumerated value which provides an indication of the

            general hardware type of a particular physical entity.

            There are no restrictions as to the number of

            entPhysicalEntries of each entPhysicalClass, which must be

            instantiated by an agent.

            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

            it 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."

    SYNTAX      INTEGER  {

       other(1),

       unknown(2),

       chassis(3),

       backplane(4),

       container(5),

       powerSupply(6),

       fan(7),

       sensor(8),

       module(9),        

       port(10),

       stack(11)         

    }

SnmpEngineIdOrNone ::= TEXTUAL-CONVENTION

    STATUS            current

    DESCRIPTION

            "A specially formatted SnmpEngineID string for use with the

            Entity MIB.

            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 RFC

            2571 [RFC2571]).

            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 not supported)."

    SYNTAX OCTET STRING (SIZE(0..32)) 

entPhysicalTable OBJECT-TYPE

    SYNTAX      SEQUENCE OF EntPhysicalEntry

    MAX-ACCESS  not-accessible

    STATUS      current

    DESCRIPTION

            "This table contains one row per physical entity.  There is

            always at least one row for an 'overall' physical entity."

    ::= { entityPhysical 1 }

entPhysicalEntry       OBJECT-TYPE

    SYNTAX      EntPhysicalEntry

    MAX-ACCESS  not-accessible

    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 }

EntPhysicalEntry ::= SEQUENCE {

      entPhysicalIndex          PhysicalIndex,

      entPhysicalDescr          SnmpAdminString,

      entPhysicalVendorType     AutonomousType,

      entPhysicalContainedIn    INTEGER,

      entPhysicalClass          PhysicalClass,

      entPhysicalParentRelPos   INTEGER,

      entPhysicalName           SnmpAdminString,

      entPhysicalHardwareRev    SnmpAdminString,

      entPhysicalFirmwareRev    SnmpAdminString,

      entPhysicalSoftwareRev    SnmpAdminString,

      entPhysicalSerialNum      SnmpAdminString,

      entPhysicalMfgName        SnmpAdminString,

      entPhysicalModelName      SnmpAdminString,

      entPhysicalAlias          SnmpAdminString,

      entPhysicalAssetID        SnmpAdminString,

      entPhysicalIsFRU          TruthValue

}

entPhysicalIndex    OBJECT-TYPE

    SYNTAX      PhysicalIndex

    MAX-ACCESS  not-accessible

    STATUS      current

    DESCRIPTION

            "The index for this entry."

    ::= { entPhysicalEntry 1 }

entPhysicalDescr OBJECT-TYPE

    SYNTAX      SnmpAdminString

    MAX-ACCESS  read-only

    STATUS      current

    DESCRIPTION

            "A textual description of physical entity.  This object

            should contain a string which 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 }

entPhysicalVendorType OBJECT-TYPE

    SYNTAX      AutonomousType

    MAX-ACCESS  read-only

    STATUS      current

    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 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 }

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,

            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 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 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))

    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).

            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 }

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,

            including those which result in a change of the physical

            entity's entPhysicalIndex value."

    ::= { entPhysicalEntry 14 }

entPhysicalAssetID OBJECT-TYPE

    SYNTAX      SnmpAdminString (SIZE (0..32))