252N/A MODULE-IDENTITY, OBJECT-TYPE, mib-2, NOTIFICATION-TYPE
252N/A TDomain, TAddress, TEXTUAL-CONVENTION,
252N/A AutonomousType, RowPointer, TimeStamp, TruthValue
252N/A MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
252N/A FROM SNMP-FRAMEWORK-MIB;
252N/AentityMIB MODULE-IDENTITY
252N/A LAST-UPDATED "9912070000Z"
252N/A ORGANIZATION "IETF ENTMIB Working Group"
252N/A " WG E-mail: entmib@cisco.com
252N/A Subscribe: majordomo@cisco.com
252N/A msg body: subscribe entmib
252N/A ENTMIB Working Group Chair
252N/A ENTMIB Working Group Editor
252N/A "The MIB module for representing multiple logical
252N/A entities supported by a single SNMP agent."
252N/A "Initial Version of Entity MIB (Version 2).
252N/A This revision obsoletes RFC 2037.
252N/A This version published as RFC 2737."
252N/A "Initial version (version 1), published as
252N/AentityMIBObjects OBJECT IDENTIFIER ::= { entityMIB 1 }
252N/AentityPhysical OBJECT IDENTIFIER ::= { entityMIBObjects 1 }
252N/AentityLogical OBJECT IDENTIFIER ::= { entityMIBObjects 2 }
252N/AentityMapping OBJECT IDENTIFIER ::= { entityMIBObjects 3 }
252N/AentityGeneral OBJECT IDENTIFIER ::= { entityMIBObjects 4 }
252N/APhysicalIndex ::= TEXTUAL-CONVENTION
252N/A "An arbitrary value which uniquely identifies the physical
252N/A entity. The value should be a small positive integer; index
252N/A values for different physical entities are not necessarily
252N/A SYNTAX INTEGER (1..2147483647)
252N/APhysicalClass ::= TEXTUAL-CONVENTION
252N/A "An enumerated value which provides an indication of the
252N/A general hardware type of a particular physical entity.
252N/A There are no restrictions as to the number of
252N/A entPhysicalEntries of each entPhysicalClass, which must be
252N/A instantiated by an agent.
252N/A The enumeration 'other' is applicable if the physical entity
252N/A class is known, but does not match any of the supported
252N/A The enumeration 'unknown' is applicable if the physical
252N/A entity class is unknown to the agent.
252N/A The enumeration 'chassis' is applicable if the physical
252N/A entity class is an overall container for networking
252N/A equipment. Any class of physical entity except a stack may
252N/A be contained within a chassis, and a chassis may only be
252N/A contained within a stack.
252N/A The enumeration 'backplane' is applicable if the physical
252N/A entity class is some sort of device for aggregating and
252N/A forwarding networking traffic, such as a shared backplane in
252N/A a modular ethernet switch. Note that an agent may model a
252N/A backplane as a single physical entity, which is actually
252N/A implemented as multiple discrete physical components (within
252N/A The enumeration 'container' is applicable if the physical
252N/A entity class is capable of containing one or more removable
252N/A physical entities, possibly of different types. For example,
252N/A each (empty or full) slot in a chassis will be modeled as a
252N/A container. Note that all removable physical entities should
252N/A be modeled within a container entity, such as field-
252N/A replaceable modules, fans, or power supplies. Note that all
252N/A known containers should be modeled by the agent, including
252N/A The enumeration 'powerSupply' is applicable if the physical
252N/A entity class is a power-supplying component.
252N/A The enumeration 'fan' is applicable if the physical entity
252N/A class is a fan or other heat-reduction component.
252N/A The enumeration 'sensor' is applicable if the physical
252N/A entity class is some sort of sensor, such as a temperature
252N/A sensor within a router chassis.
252N/A The enumeration 'module' is applicable if the physical
252N/A entity class is some sort of self-contained sub-system. If
252N/A it is removable, then it should be modeled within a
252N/A container entity, otherwise it should be modeled directly
252N/A within another physical entity (
e.g., a chassis or another
252N/A The enumeration 'port' is applicable if the physical entity
252N/A class is some sort of networking port, capable of receiving
252N/A The enumeration 'stack' is applicable if the physical entity
252N/A class is some sort of super-container (possibly virtual),
252N/A intended to group together multiple chassis entities. A
252N/A stack may be realized by a 'virtual' cable, a real
252N/A interconnect cable, attached to multiple chassis, or may in
252N/A fact be comprised of multiple interconnect cables. A stack
252N/A should not be modeled within any other physical entities,
252N/A but a stack may be contained within another stack. Only
252N/A chassis entities should be contained within a stack."
252N/ASnmpEngineIdOrNone ::= TEXTUAL-CONVENTION
252N/A "A specially formatted SnmpEngineID string for use with the
252N/A If an instance of an object of SYNTAX SnmpEngineIdOrNone has
252N/A a non-zero length, then the object encoding and semantics
252N/A are defined by the SnmpEngineID textual convention (see RFC
252N/A If an instance of an object of SYNTAX SnmpEngineIdOrNone
252N/A contains a zero-length string, then no appropriate
252N/A SnmpEngineID is associated with the logical entity (
i.e.,
252N/A SNMPv3 not supported)."
252N/A SYNTAX OCTET STRING (SIZE(0..32))
252N/AentPhysicalTable OBJECT-TYPE
252N/A SYNTAX SEQUENCE OF EntPhysicalEntry
252N/A MAX-ACCESS not-accessible
252N/A "This table contains one row per physical entity. There is
252N/A always at least one row for an 'overall' physical entity."
252N/A ::= { entityPhysical 1 }
252N/AentPhysicalEntry OBJECT-TYPE
252N/A SYNTAX EntPhysicalEntry
252N/A MAX-ACCESS not-accessible
252N/A "Information about a particular physical entity.
252N/A Each entry provides objects (entPhysicalDescr,
252N/A entPhysicalVendorType, and entPhysicalClass) to help an NMS
252N/A identify and characterize the entry, and objects
252N/A (entPhysicalContainedIn and entPhysicalParentRelPos) to help
252N/A an NMS relate the particular entry to other entries in this
252N/A INDEX { entPhysicalIndex }
252N/A ::= { entPhysicalTable 1 }
252N/AEntPhysicalEntry ::= SEQUENCE {
252N/A entPhysicalIndex PhysicalIndex,
252N/A entPhysicalDescr SnmpAdminString,
252N/A entPhysicalVendorType AutonomousType,
252N/A entPhysicalContainedIn INTEGER,
252N/A entPhysicalClass PhysicalClass,
252N/A entPhysicalParentRelPos INTEGER,
252N/A entPhysicalName SnmpAdminString,
252N/A entPhysicalHardwareRev SnmpAdminString,
252N/A entPhysicalFirmwareRev SnmpAdminString,
252N/A entPhysicalSoftwareRev SnmpAdminString,
252N/A entPhysicalSerialNum SnmpAdminString,
252N/A entPhysicalMfgName SnmpAdminString,
252N/A entPhysicalModelName SnmpAdminString,
252N/A entPhysicalAlias SnmpAdminString,
252N/A entPhysicalAssetID SnmpAdminString,
252N/A entPhysicalIsFRU TruthValue
252N/AentPhysicalIndex OBJECT-TYPE
252N/A MAX-ACCESS not-accessible
252N/A "The index for this entry."
252N/A ::= { entPhysicalEntry 1 }
252N/AentPhysicalDescr OBJECT-TYPE
252N/A "A textual description of physical entity. This object
252N/A should contain a string which identifies the manufacturer's
252N/A name for the physical entity, and should be set to a
252N/A distinct value for each version or model of the physical
252N/A ::= { entPhysicalEntry 2 }
252N/AentPhysicalVendorType OBJECT-TYPE
252N/A "An indication of the vendor-specific hardware type of the
252N/A physical entity. Note that this is different from the
252N/A definition of MIB-II's sysObjectID.
252N/A An agent should set this object to a enterprise-specific
252N/A registration identifier value indicating the specific
252N/A equipment type in detail. The associated instance of
252N/A entPhysicalClass is used to indicate the general type of
252N/A If no vendor-specific registration identifier exists for
252N/A this physical entity, or the value is unknown by this agent,
252N/A then the value { 0 0 } is returned."
252N/A ::= { entPhysicalEntry 3 }
252N/AentPhysicalContainedIn OBJECT-TYPE
252N/A SYNTAX INTEGER (0..2147483647)
252N/A "The value of entPhysicalIndex for the physical entity which
252N/A 'contains' this physical entity. A value of zero indicates
252N/A this physical entity is not contained in any other physical
252N/A entity. Note that the set of 'containment' relationships
252N/A define a strict hierarchy; that is, recursion is not
252N/A In the event a physical entity is contained by more than one
252N/A physical entity (
e.g., double-wide modules), this object
252N/A should identify the containing entity with the lowest value
252N/A ::= { entPhysicalEntry 4 }
252N/AentPhysicalClass OBJECT-TYPE
252N/A "An indication of the general hardware type of the physical
252N/A An agent should set this object to the standard enumeration
252N/A value which most accurately indicates the general class of
252N/A the physical entity, or the primary class if there is more
252N/A If no appropriate standard registration identifier exists
252N/A for this physical entity, then the value 'other(1)' is
252N/A returned. If the value is unknown by this agent, then the
252N/A value 'unknown(2)' is returned."
252N/A ::= { entPhysicalEntry 5 }
252N/AentPhysicalParentRelPos OBJECT-TYPE
252N/A SYNTAX INTEGER (-1..2147483647)
252N/A "An indication of the relative position of this 'child'
252N/A component among all its 'sibling' components. Sibling
252N/A components are defined as entPhysicalEntries which share the
252N/A same instance values of each of the entPhysicalContainedIn
252N/A and entPhysicalClass objects.
252N/A An NMS can use this object to identify the relative ordering
252N/A for all sibling components of a particular parent
252N/A (identified by the entPhysicalContainedIn instance in each
252N/A This value should match any external labeling of the
252N/A physical component if possible. For example, for a container
252N/A entPhysicalParentRelPos should have the value '3'. Note
252N/A that the entPhysicalEntry for the module plugged in slot 3
252N/A should have an entPhysicalParentRelPos value of '1'.
252N/A If the physical position of this component does not match
252N/A any external numbering or clearly visible ordering, then
252N/A user documentation or other external reference material
252N/A should be used to determine the parent-relative position. If
252N/A this is not possible, then the the agent should assign a
252N/A consistent (but possibly arbitrary) ordering to a given set
252N/A of 'sibling' components, perhaps based on internal
252N/A representation of the components.
252N/A If the agent cannot determine the parent-relative position
252N/A for some reason, or if the associated value of
252N/A entPhysicalContainedIn is '0', then the value '-1' is
252N/A returned. Otherwise a non-negative integer is returned,
252N/A indicating the parent-relative position of this physical
252N/A Parent-relative ordering normally starts from '1' and
252N/A continues to 'N', where 'N' represents the highest
252N/A positioned child entity. However, if the physical entities
252N/A (
e.g., slots) are labeled from a starting position of zero,
252N/A then the first sibling should be associated with a
252N/A entPhysicalParentRelPos value of '0'. Note that this
252N/A ordering may be sparse or dense, depending on agent
252N/A The actual values returned are not globally meaningful, as
252N/A each 'parent' component may use different numbering
252N/A algorithms. The ordering is only meaningful among siblings
252N/A of the same parent component.
252N/A The agent should retain parent-relative position values
252N/A across reboots, either through algorithmic assignment or use
252N/A of non-volatile storage."
252N/A ::= { entPhysicalEntry 6 }
252N/AentPhysicalName OBJECT-TYPE
252N/A "The textual name of the physical entity. The value of this
252N/A object should be the name of the component as assigned by
252N/A the local device and should be suitable for use in commands
252N/A entered at the device's `console'. This might be a text
252N/A name, such as `console' or a simple component number (
e.g.,
252N/A port or module number), such as `1', depending on the
252N/A physical component naming syntax of the device.
252N/A If there is no local name, or this object is otherwise not
252N/A applicable, then this object contains a zero-length string.
252N/A Note that the value of entPhysicalName for two physical
252N/A entities will be the same in the event that the console
252N/A interface does not distinguish between them,
e.g., slot-1
252N/A and the card in slot-1."
252N/A ::= { entPhysicalEntry 7 }
252N/AentPhysicalHardwareRev OBJECT-TYPE
252N/A "The vendor-specific hardware revision string for the
252N/A physical entity. The preferred value is the hardware
252N/A revision identifier actually printed on the component itself
252N/A Note that if revision information is stored internally in a
252N/A non-printable (
e.g., binary) format, then the agent must
252N/A convert such information to a printable format, in an
252N/A implementation-specific manner.
252N/A If no specific hardware revision string is associated with
252N/A the physical component, or this information is unknown to
252N/A the agent, then this object will contain a zero-length
252N/A ::= { entPhysicalEntry 8 }
252N/AentPhysicalFirmwareRev OBJECT-TYPE
252N/A "The vendor-specific firmware revision string for the
252N/A Note that if revision information is stored internally in a
252N/A non-printable (
e.g., binary) format, then the agent must
252N/A convert such information to a printable format, in an
252N/A implementation-specific manner.
252N/A If no specific firmware programs are associated with the
252N/A physical component, or this information is unknown to the
252N/A agent, then this object will contain a zero-length string."
252N/A ::= { entPhysicalEntry 9 }
252N/AentPhysicalSoftwareRev OBJECT-TYPE
252N/A "The vendor-specific software revision string for the
252N/A Note that if revision information is stored internally in a
252N/A non-printable (
e.g., binary) format, then the agent must
252N/A convert such information to a printable format, in an
252N/A implementation-specific manner.
252N/A If no specific software programs are associated with the
252N/A physical component, or this information is unknown to the
252N/A agent, then this object will contain a zero-length string."
252N/A ::= { entPhysicalEntry 10 }
252N/AentPhysicalSerialNum OBJECT-TYPE
252N/A SYNTAX SnmpAdminString (SIZE (0..32))
252N/A "The vendor-specific serial number string for the physical
252N/A entity. The preferred value is the serial number string
252N/A actually printed on the component itself (if present).
252N/A On the first instantiation of an physical entity, the value
252N/A of entPhysicalSerialNum associated with that entity is set
252N/A to the correct vendor-assigned serial number, if this
252N/A information is available to the agent. If a serial number
252N/A is unknown or non-existent, the entPhysicalSerialNum will be
252N/A set to a zero-length string instead.
252N/A Note that implementations which can correctly identify the
252N/A serial numbers of all installed physical entities do not
252N/A need to provide write access to the entPhysicalSerialNum
252N/A object. Agents which cannot provide non-volatile storage for
252N/A the entPhysicalSerialNum strings are not required to
252N/A implement write access for this object.
252N/A Not every physical component will have a serial number, or
252N/A even need one. Physical entities for which the associated
252N/A value of the entPhysicalIsFRU object is equal to 'false(2)'
252N/A (
e.g., the repeater ports within a repeater module), do not
252N/A need their own unique serial number. An agent does not have
252N/A to provide write access for such entities, and may return a
252N/A If write access is implemented for an instance of
252N/A entPhysicalSerialNum, and a value is written into the
252N/A instance, the agent must retain the supplied value in the
252N/A entPhysicalSerialNum instance associated with the same
252N/A physical entity for as long as that entity remains
252N/A instantiated. This includes instantiations across all re-
252N/A including those which result in a change of the physical
252N/A entity's entPhysicalIndex value."
252N/A ::= { entPhysicalEntry 11 }
252N/AentPhysicalMfgName OBJECT-TYPE
252N/A "The name of the manufacturer of this physical component.
252N/A The preferred value is the manufacturer name string actually
252N/A printed on the component itself (if present).
252N/A Note that comparisons between instances of the
252N/A entPhysicalModelName, entPhysicalFirmwareRev,
252N/A entPhysicalSoftwareRev, and the entPhysicalSerialNum
252N/A objects, are only meaningful amongst entPhysicalEntries with
252N/A the same value of entPhysicalMfgName.
252N/A If the manufacturer name string associated with the physical
252N/A component is unknown to the agent, then this object will
252N/A contain a zero-length string."
252N/A ::= { entPhysicalEntry 12 }
252N/AentPhysicalModelName OBJECT-TYPE
252N/A "The vendor-specific model name identifier string associated
252N/A with this physical component. The preferred value is the
252N/A customer-visible part number, which may be printed on the
252N/A If the model name string associated with the physical
252N/A component is unknown to the agent, then this object will
252N/A contain a zero-length string."
252N/A ::= { entPhysicalEntry 13 }
252N/AentPhysicalAlias OBJECT-TYPE
252N/A SYNTAX SnmpAdminString (SIZE (0..32))
252N/A "This object is an 'alias' name for the physical entity as
252N/A specified by a network manager, and provides a non-volatile
252N/A 'handle' for the physical entity.
252N/A On the first instantiation of an physical entity, the value
252N/A of entPhysicalAlias associated with that entity is set to
252N/A the zero-length string. However, agent may set the value to
252N/A a locally unique default value, instead of a zero-length
252N/A If write access is implemented for an instance of
252N/A entPhysicalAlias, and a value is written into the instance,
252N/A the agent must retain the supplied value in the
252N/A entPhysicalAlias instance associated with the same physical
252N/A entity for as long as that entity remains instantiated.
252N/A This includes instantiations across all re-
252N/A including those which result in a change of the physical
252N/A entity's entPhysicalIndex value."
252N/A ::= { entPhysicalEntry 14 }
252N/AentPhysicalAssetID OBJECT-TYPE
252N/A SYNTAX SnmpAdminString (SIZE (0..32))
252N/A "This object is a user-assigned asset tracking identifier
252N/A for the physical entity as specified by a network manager,
252N/A and provides non-volatile storage of this information.
252N/A On the first instantiation of an physical entity, the value
252N/A of entPhysicalAssetID associated with that entity is set to
252N/A the zero-length string.
252N/A Not every physical component will have a asset tracking
252N/A identifier, or even need one. Physical entities for which
252N/A the associated value of the entPhysicalIsFRU object is equal
252N/A to 'false(2)' (
e.g., the repeater ports within a repeater
252N/A module), do not need their own unique asset tracking
252N/A identifier. An agent does not have to provide write access
252N/A for such entities, and may instead return a zero-length
252N/A If write access is implemented for an instance of
252N/A entPhysicalAssetID, and a value is written into the
252N/A instance, the agent must retain the supplied value in the
252N/A entPhysicalAssetID instance associated with the same
252N/A physical entity for as long as that entity remains
252N/A instantiated. This includes instantiations across all re-
252N/A including those which result in a change of the physical
252N/A entity's entPhysicalIndex value.
252N/A If no asset tracking information is associated with the
252N/A physical component, then this object will contain a zero-
252N/A ::= { entPhysicalEntry 15 }
252N/AentPhysicalIsFRU OBJECT-TYPE
252N/A "This object indicates whether or not this physical entity
252N/A is considered a 'field replaceable unit' by the vendor. If
252N/A this object contains the value 'true(1)' then this
252N/A entPhysicalEntry identifies a field replaceable unit. For
252N/A all entPhysicalEntries which represent components that are
252N/A permanently contained within a field replaceable unit, the
252N/A value 'false(2)' should be returned for this object."
252N/A ::= { entPhysicalEntry 16 }
252N/AentLogicalTable OBJECT-TYPE
252N/A SYNTAX SEQUENCE OF EntLogicalEntry
252N/A MAX-ACCESS not-accessible
252N/A "This table contains one row per logical entity. For agents
252N/A which implement more than one naming scope, at least one
252N/A entry must exist. Agents which instantiate all MIB objects
252N/A within a single naming scope are not required to implement
252N/A ::= { entityLogical 1 }
252N/AentLogicalEntry OBJECT-TYPE
252N/A MAX-ACCESS not-accessible
252N/A "Information about a particular logical entity. Entities
252N/A may be managed by this agent or other SNMP agents (possibly)
252N/A INDEX { entLogicalIndex }
252N/A ::= { entLogicalTable 1 }
252N/AEntLogicalEntry ::= SEQUENCE {
252N/A entLogicalIndex INTEGER,
252N/A entLogicalDescr SnmpAdminString,
252N/A entLogicalType AutonomousType,
252N/A entLogicalCommunity OCTET STRING,
252N/A entLogicalTAddress TAddress,
252N/A entLogicalTDomain TDomain,
252N/A entLogicalContextEngineID SnmpEngineIdOrNone,
252N/A entLogicalContextName SnmpAdminString
252N/AentLogicalIndex OBJECT-TYPE
252N/A SYNTAX INTEGER (1..2147483647)
252N/A MAX-ACCESS not-accessible
252N/A "The value of this object uniquely identifies the logical
252N/A entity. The value should be a small positive integer; index
252N/A values for different logical entities are are not
252N/A necessarily contiguous."
252N/A ::= { entLogicalEntry 1 }
252N/AentLogicalDescr OBJECT-TYPE
252N/A "A textual description of the logical entity. This object
252N/A should contain a string which identifies the manufacturer's
252N/A name for the logical entity, and should be set to a distinct
252N/A value for each version of the logical entity. "
252N/A ::= { entLogicalEntry 2 }
252N/AentLogicalType OBJECT-TYPE
252N/A "An indication of the type of logical entity. This will
252N/A typically be the OBJECT IDENTIFIER name of the node in the
252N/A SMI's naming hierarchy which represents the major MIB
252N/A module, or the majority of the MIB modules, supported by the
252N/A logical entity. For example:
252N/A a logical entity of a 802.1d bridge -> dot1dBridge
252N/A a logical entity of a 802.3 repeater -> snmpDot3RptrMgmt
252N/A If an appropriate node in the SMI's naming hierarchy cannot
252N/A be identified, the value 'mib-2' should be used."
252N/A ::= { entLogicalEntry 3 }
252N/AentLogicalCommunity OBJECT-TYPE
252N/A SYNTAX OCTET STRING (SIZE (0..255))
252N/A "An SNMPv1 or SNMPv2C community-string which can be used to
252N/A access detailed management information for this logical
252N/A entity. The agent should allow read access with this
252N/A community string (to an appropriate subset of all managed
252N/A objects) and may also return a community string based on the
252N/A privileges of the request used to read this object. Note
252N/A that an agent may return a community string with read-only
252N/A privileges, even if this object is accessed with a read-
252N/A write community string. However, the agent must take care
252N/A not to return a community string which allows more
252N/A privileges than the community string used to access this
252N/A A compliant SNMP agent may wish to conserve naming scopes by
252N/A representing multiple logical entities in a single 'default'
252N/A naming scope. This is possible when the logical entities
252N/A represented by the same value of entLogicalCommunity have no
252N/A object instances in common. For example, 'bridge1' and
252N/A 'repeater1' may be part of the main naming scope, but at
252N/A least one additional community string is needed to represent
252N/A 'bridge2' and 'repeater2'.
252N/A Logical entities 'bridge1' and 'repeater1' would be
252N/A represented by sysOREntries associated with the 'default'
252N/A For agents not accessible via SNMPv1 or SNMPv2C, the value
252N/A of this object is the empty string. This object may also
252N/A contain an empty string if a community string has not yet
252N/A been assigned by the agent, or no community string with
252N/A suitable access rights can be returned for a particular SNMP
252N/A Note that this object is deprecated. Agents which implement
252N/A SNMPv3 access should use the entLogicalContextEngineID and
252N/A entLogicalContextName objects to identify the context
252N/A associated with each logical entity. SNMPv3 agents may
252N/A return a zero-length string for this object, or may continue
252N/A to return a community string (
e.g., tri-lingual agent
252N/A ::= { entLogicalEntry 4 }
252N/AentLogicalTAddress OBJECT-TYPE
252N/A "The transport service address by which the logical entity
252N/A receives network management traffic, formatted according to
252N/A the corresponding value of entLogicalTDomain.
252N/A For snmpUDPDomain, a TAddress is 6 octets long, the initial
252N/A 4 octets containing the IP-address in network-byte order and
252N/A the last 2 containing the UDP port in network-byte order.
252N/A Consult 'Transport Mappings for Version 2 of the Simple
252N/A Network Management Protocol' (RFC 1906 [RFC1906]) for
252N/A further information on snmpUDPDomain."
252N/A ::= { entLogicalEntry 5 }
252N/AentLogicalTDomain OBJECT-TYPE
252N/A "Indicates the kind of transport service by which the
252N/A logical entity receives network management traffic.
252N/A Possible values for this object are presently found in the
252N/A Transport Mappings for SNMPv2 document (RFC 1906
252N/A ::= { entLogicalEntry 6 }
252N/AentLogicalContextEngineID OBJECT-TYPE
252N/A SYNTAX SnmpEngineIdOrNone
252N/A "The authoritative contextEngineID that can be used to send
252N/A an SNMP message concerning information held by this logical
252N/A entity, to the address specified by the associated
252N/A This object, together with the associated
252N/A entLogicalContextName object, defines the context associated
252N/A with a particular logical entity, and allows access to SNMP
252N/A engines identified by a contextEngineId and contextName
252N/A If no value has been configured by the agent, a zero-length
252N/A string is returned, or the agent may choose not to
252N/A instantiate this object at all."
252N/A ::= { entLogicalEntry 7 }
252N/AentLogicalContextName OBJECT-TYPE
252N/A "The contextName that can be used to send an SNMP message
252N/A concerning information held by this logical entity, to the
252N/A address specified by the associated
252N/A This object, together with the associated
252N/A entLogicalContextEngineID object, defines the context
252N/A associated with a particular logical entity, and allows
252N/A access to SNMP engines identified by a contextEngineId and
252N/A If no value has been configured by the agent, a zero-length
252N/A string is returned, or the agent may choose not to
252N/A instantiate this object at all."
252N/A ::= { entLogicalEntry 8 }
252N/AentLPMappingTable OBJECT-TYPE
252N/A SYNTAX SEQUENCE OF EntLPMappingEntry
252N/A MAX-ACCESS not-accessible
252N/A "This table contains zero or more rows of logical entity to
252N/A physical equipment associations. For each logical entity
252N/A known by this agent, there are zero or more mappings to the
252N/A physical resources which are used to realize that logical
252N/A An agent should limit the number and nature of entries in
252N/A this table such that only meaningful and non-redundant
252N/A information is returned. For example, in a system which
252N/A contains a single power supply, mappings between logical
252N/A entities and the power supply are not useful and should not
252N/A Also, only the most appropriate physical component which is
252N/A closest to the root of a particular containment tree should
252N/A be identified in an entLPMapping entry.
252N/A For example, suppose a bridge is realized on a particular
252N/A module, and all ports on that module are ports on this
252N/A bridge. A mapping between the bridge and the module would be
252N/A useful, but additional mappings between the bridge and each
252N/A of the ports on that module would be redundant (since the
252N/A entPhysicalContainedIn hierarchy can provide the same
252N/A information). If, on the other hand, more than one bridge
252N/A was utilizing ports on this module, then mappings between
252N/A each bridge and the ports it used would be appropriate.
252N/A Also, in the case of a single backplane repeater, a mapping
252N/A for the backplane to the single repeater entity is not
252N/A ::= { entityMapping 1 }
252N/AentLPMappingEntry OBJECT-TYPE
252N/A SYNTAX EntLPMappingEntry
252N/A MAX-ACCESS not-accessible
252N/A "Information about a particular logical entity to physical
252N/A equipment association. Note that the nature of the
252N/A association is not specifically identified in this entry.
252N/A It is expected that sufficient information exists in the
252N/A MIBs used to manage a particular logical entity to infer how
252N/A physical component information is utilized."
252N/A INDEX { entLogicalIndex, entLPPhysicalIndex }
252N/A ::= { entLPMappingTable 1 }
252N/AEntLPMappingEntry ::= SEQUENCE {
252N/A entLPPhysicalIndex PhysicalIndex
252N/AentLPPhysicalIndex OBJECT-TYPE
252N/A "The value of this object identifies the index value of a
252N/A particular entPhysicalEntry associated with the indicated
252N/A ::= { entLPMappingEntry 1 }
252N/AentAliasMappingTable OBJECT-TYPE
252N/A SYNTAX SEQUENCE OF EntAliasMappingEntry
252N/A MAX-ACCESS not-accessible
252N/A "This table contains zero or more rows, representing
252N/A mappings of logical entity and physical component to
252N/A external MIB identifiers. Each physical port in the system
252N/A may be associated with a mapping to an external identifier,
252N/A which itself is associated with a particular logical
252N/A entity's naming scope. A 'wildcard' mechanism is provided
252N/A to indicate that an identifier is associated with more than
252N/A ::= { entityMapping 2 }
252N/AentAliasMappingEntry OBJECT-TYPE
252N/A SYNTAX EntAliasMappingEntry
252N/A MAX-ACCESS not-accessible
252N/A "Information about a particular physical equipment, logical
252N/A entity to external identifier binding. Each logical
252N/A alias mapping. The logical entity index may also be used as
252N/A a 'wildcard' (refer to the entAliasLogicalIndexOrZero object
252N/A DESCRIPTION clause for details.)
252N/A Note that only entPhysicalIndex values which represent
252N/A physical ports (
i.e. associated entPhysicalClass value is
252N/A 'port(10)') are permitted to exist in this table."
252N/A INDEX { entPhysicalIndex, entAliasLogicalIndexOrZero }
252N/A ::= { entAliasMappingTable 1 }
252N/AEntAliasMappingEntry ::= SEQUENCE {
252N/A entAliasLogicalIndexOrZero INTEGER,
252N/A entAliasMappingIdentifier RowPointer
252N/AentAliasLogicalIndexOrZero OBJECT-TYPE
252N/A SYNTAX INTEGER (0..2147483647)
252N/A MAX-ACCESS not-accessible
252N/A "The value of this object identifies the logical entity
252N/A which defines the naming scope for the associated instance
252N/A of the 'entAliasMappingIdentifier' object.
252N/A If this object has a non-zero value, then it identifies the
252N/A logical entity named by the same value of entLogicalIndex.
252N/A If this object has a value of zero, then the mapping between
252N/A the physical component and the alias identifier for this
252N/A entAliasMapping entry is associated with all unspecified
252N/A logical entities. That is, a value of zero (the default
252N/A mapping) identifies any logical entity which does not have
252N/A an explicit entry in this table for a particular
252N/A For example, to indicate that a particular interface (
e.g.,
252N/A physical component 33) is identified by the same value of
252N/A ifIndex for all logical entities, the following instance
252N/A entAliasMappingIdentifier.33.0 = ifIndex.5
252N/A In the event an entPhysicalEntry is associated differently
252N/A for some logical entities, additional entAliasMapping
252N/A entAliasMappingIdentifier.33.0 = ifIndex.6
252N/A entAliasMappingIdentifier.33.4 = ifIndex.1
252N/A entAliasMappingIdentifier.33.5 = ifIndex.1
252N/A entAliasMappingIdentifier.33.10 = ifIndex.12
252N/A Note that entries with non-zero entAliasLogicalIndexOrZero
252N/A index values have precedence over any zero-indexed entry. In
252N/A this example, all logical entities except 4, 5, and 10,
252N/A associate physical entity 33 with ifIndex.6."
252N/A ::= { entAliasMappingEntry 1 }
252N/AentAliasMappingIdentifier OBJECT-TYPE
252N/A "The value of this object identifies a particular conceptual
252N/A row associated with the indicated entPhysicalIndex and
252N/A Since only physical ports are modeled in this table, only
252N/A entries which represent interfaces or ports are allowed. If
252N/A an ifEntry exists on behalf of a particular physical port,
252N/A then this object should identify the associated 'ifEntry'.
252N/A For repeater ports, the appropriate row in the
252N/A 'rptrPortGroupTable' should be identified instead.
252N/A For example, suppose a physical port was represented by
252N/A entPhysicalEntry.3, entLogicalEntry.15 existed for a
252N/A repeater, and entLogicalEntry.22 existed for a bridge. Then
252N/A there might be two related instances of
252N/A entAliasMappingIdentifier:
252N/A entAliasMappingIdentifier.3.15 == rptrPortGroupIndex.5.2
252N/A entAliasMappingIdentifier.3.22 == ifIndex.17
252N/A It is possible that other mappings (besides interfaces and
252N/A repeater ports) may be defined in the future, as required.
252N/A Bridge ports are identified by examining the Bridge MIB and
252N/A appropriate ifEntries associated with each 'dot1dBasePort',
252N/A and are thus not represented in this table."
252N/A ::= { entAliasMappingEntry 2 }
252N/AentPhysicalContainsTable OBJECT-TYPE
252N/A SYNTAX SEQUENCE OF EntPhysicalContainsEntry
252N/A MAX-ACCESS not-accessible
252N/A "A table which exposes the container/'containee'
252N/A relationships between physical entities. This table provides
252N/A all the information found by constructing the virtual
252N/A containment tree for a given entPhysicalTable, but in a more
252N/A In the event a physical entity is contained by more than one
252N/A other physical entity (
e.g., double-wide modules), this
252N/A table should include these additional mappings, which cannot
252N/A be represented in the entPhysicalTable virtual containment
252N/A ::= { entityMapping 3 }
252N/AentPhysicalContainsEntry OBJECT-TYPE
252N/A SYNTAX EntPhysicalContainsEntry
252N/A MAX-ACCESS not-accessible
252N/A "A single container/'containee' relationship."
252N/A INDEX { entPhysicalIndex, entPhysicalChildIndex }
252N/A ::= { entPhysicalContainsTable 1 }
252N/AEntPhysicalContainsEntry ::= SEQUENCE {
252N/A entPhysicalChildIndex PhysicalIndex
252N/AentPhysicalChildIndex OBJECT-TYPE
252N/A "The value of entPhysicalIndex for the contained physical
252N/A ::= { entPhysicalContainsEntry 1 }
252N/AentLastChangeTime OBJECT-TYPE
252N/A "The value of sysUpTime at the time a conceptual row is
252N/A created, modified, or deleted in any of these tables:
252N/A - entPhysicalContainsTable
252N/A ::= { entityGeneral 1 }
252N/AentityMIBTraps OBJECT IDENTIFIER ::= { entityMIB 2 }
252N/AentityMIBTrapPrefix OBJECT IDENTIFIER ::= { entityMIBTraps 0 }
252N/AentConfigChange NOTIFICATION-TYPE
252N/A "An entConfigChange notification is generated when the value
252N/A of entLastChangeTime changes. It can be utilized by an NMS
252N/A An agent should not generate more than one entConfigChange
252N/A 'notification-event' in a given time interval (five seconds
252N/A is the suggested default). A 'notification-event' is the
252N/A transmission of a single trap or inform PDU to a list of
252N/A notification destinations.
252N/A If additional configuration changes occur within the
252N/A throttling period, then notification-events for these
252N/A changes should be suppressed by the agent until the current
252N/A throttling period expires. At the end of a throttling
252N/A period, one notification-event should be generated if any
252N/A configuration changes occurred since the start of the
252N/A throttling period. In such a case, another throttling period
252N/A An NMS should periodically check the value of
252N/A entLastChangeTime to detect any missed entConfigChange
252N/A notification-events,
e.g., due to throttling or transmission
252N/A ::= { entityMIBTrapPrefix 1 }
252N/AentityConformance OBJECT IDENTIFIER ::= { entityMIB 3 }
252N/AentityCompliances OBJECT IDENTIFIER ::= { entityConformance 1 }
252N/AentityGroups OBJECT IDENTIFIER ::= { entityConformance 2 }
252N/AentityCompliance MODULE-COMPLIANCE
252N/A "The compliance statement for SNMP entities which implement
252N/A version 1 of the Entity MIB."
252N/A entityNotificationsGroup
252N/A ::= { entityCompliances 1 }
252N/Aentity2Compliance MODULE-COMPLIANCE
252N/A "The compliance statement for SNMP entities which implement
252N/A version 2 of the Entity MIB."
252N/A entityNotificationsGroup
252N/A GROUP entityLogical2Group
252N/A "Implementation of this group is not mandatory for agents
252N/A which model all MIB object instances within a single naming
252N/A GROUP entityMappingGroup
252N/A "Implementation of the entPhysicalContainsTable is mandatory
252N/A for all agents. Implementation of the entLPMappingTable and
252N/A entAliasMappingTables are not mandatory for agents which
252N/A model all MIB object instances within a single naming scope.
252N/A Note that the entAliasMappingTable may be useful for all
252N/A agents, however implementation of the entityLogicalGroup or
252N/A entityLogical2Group is required to support this table."
252N/A OBJECT entPhysicalSerialNum
252N/A MIN-ACCESS not-accessible
252N/A "Read and write access is not required for agents which
252N/A cannot identify serial number information for physical
252N/A entities,
and/or cannot provide non-volatile storage for
252N/A NMS-assigned serial numbers.
252N/A Write access is not required for agents which can identify
252N/A serial number information for physical entities, but cannot
252N/A provide non-volatile storage for NMS-assigned serial
252N/A Write access is not required for physical entities for
252N/A physical entities for which the associated value of the
252N/A entPhysicalIsFRU object is equal to 'false(2)'."
252N/A OBJECT entPhysicalAlias
252N/A "Write access is required only if the associated
252N/A entPhysicalClass value is equal to 'chassis(3)'."
252N/A OBJECT entPhysicalAssetID
252N/A MIN-ACCESS not-accessible
252N/A "Read and write access is not required for agents which
252N/A cannot provide non-volatile storage for NMS-assigned asset
252N/A Write access is not required for physical entities for which
252N/A the associated value of entPhysicalIsFRU is equal to
252N/A ::= { entityCompliances 2 }
252N/AentityPhysicalGroup OBJECT-GROUP
252N/A entPhysicalContainedIn,
252N/A entPhysicalParentRelPos,
252N/A "The collection of objects which are used to represent
252N/A physical system components, for which a single agent
252N/A provides management information."
252N/AentityLogicalGroup OBJECT-GROUP
252N/A "The collection of objects which are used to represent the
252N/A list of logical entities for which a single agent provides
252N/A management information."
252N/AentityMappingGroup OBJECT-GROUP
252N/A entAliasMappingIdentifier,
252N/A "The collection of objects which are used to represent the
252N/A associations between multiple logical entities, physical
252N/A components, interfaces, and port identifiers for which a
252N/A single agent provides management information."
252N/AentityGeneralGroup OBJECT-GROUP
252N/A "The collection of objects which are used to represent
252N/A general entity information for which a single agent provides
252N/A management information."
252N/AentityNotificationsGroup NOTIFICATION-GROUP
252N/A NOTIFICATIONS { entConfigChange }
252N/A "The collection of notifications used to indicate Entity MIB
252N/A data consistency and general status information."
252N/AentityPhysical2Group OBJECT-GROUP
252N/A entPhysicalHardwareRev,
252N/A entPhysicalFirmwareRev,
252N/A entPhysicalSoftwareRev,
252N/A "The collection of objects which are used to represent
252N/A physical system components, for which a single agent
252N/A provides management information. This group augments the
252N/A objects contained in the entityPhysicalGroup."
252N/AentityLogical2Group OBJECT-GROUP
252N/A entLogicalContextEngineID,
252N/A "The collection of objects which are used to represent the
252N/A list of logical entities for which a single SNMP entity
252N/A provides management information."