logstash-input-snmp 0.1.0.beta4 → 0.1.0.beta5

data/lib/mibs/ietf/ENTITY-MIB.dic

@@ -0,0 +1,2235 @@
+# python version 1.0						DO NOT EDIT
+#
+# This python file has been generated by smidump version 0.5.0:
+#
+#   smidump -f python ENTITY-MIB
+
+FILENAME = "./libsmi-0.5.0/mibs/ietf/ENTITY-MIB"
+
+MIB = {
+    "moduleName" : "ENTITY-MIB",
+
+    "ENTITY-MIB" : {
+        "nodetype" : "module",
+        "language" : "SMIv2",
+        "organization" :    
+            """IETF Energy Management Working Group""",
+        "contact" : 
+            """WG Email: eman@ietf.org
+Mailing list subscription info:
+http://www.ietf.org/mailman/listinfo/eman
+
+
+
+
+
+
+
+Andy Bierman
+YumaWorks, Inc.
+274 Redwood Shores Parkway, #133
+Redwood City, CA 94065
+USA
+Phone: +1 408-716-0466
+Email: andy@yumaworks.com
+
+Dan Romascanu
+Avaya
+Park Atidim, Bldg. #3
+Tel Aviv, 61581
+Israel
+Phone: +972-3-6458414
+Email: dromasca@avaya.com
+
+Juergen Quittek
+NEC Europe Ltd.
+Network Research Division
+Kurfuersten-Anlage 36
+Heidelberg  69115
+Germany
+Phone: +49 6221 4342-115
+Email: quittek@neclab.eu
+
+Mouli Chandramouli
+Cisco Systems, Inc.
+Sarjapur Outer Ring Road
+Bangalore 560103
+India
+Phone: +91 80 4429 2409
+Email: moulchan@cisco.com""",
+        "description" :
+            """The MIB module for representing multiple logical
+entities supported by a single SNMP agent.
+
+Copyright (c) 2013 IETF Trust and the persons identified
+as authors of the code.  All rights reserved.
+
+Redistribution and use in source and binary forms, with
+or without modification, is permitted pursuant to, and
+subject to the license terms contained in, the Simplified
+BSD License set forth in Section 4.c of the IETF Trust's
+Legal Provisions Relating to IETF Documents
+(http://trustee.ietf.org/license-info).""",
+        "revisions" : (
+            {
+                "date" : "2013-04-05 00:00",
+                "description" :
+                    """Entity MIB (Version 4).
+This revision obsoletes RFC 4133.
+- Creation of a new MIB module, IANA-ENTITY-MIB, which
+makes the PhysicalIndex TC an IANA-maintained TEXTUAL-
+CONVENTION.  IANAPhysicalClass is now imported
+from the IANA-ENTITY-MIB.
+- Addition of a new MIB object to the entPhysicalTable,
+entPhysicalUUID.  UUIDorZero is imported from the
+UUID-TC-MIB.
+- Addition of two new MODULE-COMPLIANCE modules-
+entity4Compliance and entity4CRCompliance.
+This version is published as RFC 6933.""",
+            },
+            {
+                "date" : "2005-08-10 00:00",
+                "description" :
+                    """Initial Version of Entity MIB (Version 3).
+This revision obsoletes RFC 2737.
+Additions:
+  - cpu(12) enumeration added to IANAPhysicalClass TC
+  - DISPLAY-HINT clause to PhysicalIndex TC
+  - PhysicalIndexOrZero TC
+  - entPhysicalMfgDate object
+  - entPhysicalUris object
+Changes:
+  - entPhysicalContainedIn SYNTAX changed from
+    INTEGER to PhysicalIndexOrZero
+
+This version was published as RFC 4133.""",
+            },
+            {
+                "date" : "1999-12-07 00:00",
+                "description" :
+                    """Initial Version of Entity MIB (Version 2).
+This revision obsoletes RFC 2037.
+This version was published as RFC 2737.""",
+            },
+            {
+                "date" : "1996-10-31 00:00",
+                "description" :
+                    """Initial version (version 1), published as
+RFC 2037.""",
+            },
+        ),
+        "identity node" : "entityMIB",
+    },
+
+    "imports" : (
+        {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
+        {"module" : "SNMPv2-SMI", "name" : "OBJECT-TYPE"},
+        {"module" : "SNMPv2-SMI", "name" : "mib-2"},
+        {"module" : "SNMPv2-SMI", "name" : "NOTIFICATION-TYPE"},
+        {"module" : "SNMPv2-SMI", "name" : "Integer32"},
+        {"module" : "SNMPv2-TC", "name" : "TDomain"},
+        {"module" : "SNMPv2-TC", "name" : "TAddress"},
+        {"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
+        {"module" : "SNMPv2-TC", "name" : "AutonomousType"},
+        {"module" : "SNMPv2-TC", "name" : "RowPointer"},
+        {"module" : "SNMPv2-TC", "name" : "TimeStamp"},
+        {"module" : "SNMPv2-TC", "name" : "TruthValue"},
+        {"module" : "SNMPv2-TC", "name" : "DateAndTime"},
+        {"module" : "SNMPv2-CONF", "name" : "MODULE-COMPLIANCE"},
+        {"module" : "SNMPv2-CONF", "name" : "OBJECT-GROUP"},
+        {"module" : "SNMPv2-CONF", "name" : "NOTIFICATION-GROUP"},
+        {"module" : "SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
+        {"module" : "UUID-TC-MIB", "name" : "UUIDorZero"},
+        {"module" : "IANA-ENTITY-MIB", "name" : "IANAPhysicalClass"},
+    ),
+
+    "typedefs" : {
+        "PhysicalIndex" : {
+            "basetype" : "Integer32",
+            "status" : "current",
+            "ranges" : [
+            {
+                "min" : "1",
+                "max" : "2147483647"
+            },
+            ],
+            "range" : {
+                "min" : "1",
+                "max" : "2147483647"
+            },
+            "format" : "d",
+            "description" :
+                """An arbitrary value that uniquely identifies the physical
+entity.  The value should be a small positive integer.
+Index values for different physical entities are not
+necessarily contiguous.""",
+        },
+        "PhysicalIndexOrZero" : {
+            "basetype" : "Integer32",
+            "status" : "current",
+            "ranges" : [
+            {
+                "min" : "0",
+                "max" : "2147483647"
+            },
+            ],
+            "range" : {
+                "min" : "0",
+                "max" : "2147483647"
+            },
+            "format" : "d",
+            "description" :
+                """This TEXTUAL-CONVENTION is an extension of the
+PhysicalIndex convention, which defines a greater than zero
+value used to identify a physical entity.  This extension
+permits the additional value of zero.  The semantics of the
+value zero are object-specific and must, therefore, be
+defined as part of the description of any object that uses
+this syntax.  Examples of the usage of this extension are
+situations where none or all physical entities need to be
+referenced.""",
+        },
+        "SnmpEngineIdOrNone" : {
+            "basetype" : "OctetString",
+            "status" : "current",
+            "ranges" : [
+            {
+                "min" : "0",
+                "max" : "32"
+            },
+            ],
+            "range" : {
+                "min" : "0",
+                "max" : "32"
+            },
+            "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 STD
+62, RFC 3411).
+
+
+
+
+
+
+
+
+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).""",
+        },
+        "PhysicalClass" : {
+            "basetype" : "Enumeration",
+            "status" : "deprecated",
+            "other" : {
+                "nodetype" : "namednumber",
+                "number" : "1"
+            },
+            "unknown" : {
+                "nodetype" : "namednumber",
+                "number" : "2"
+            },
+            "chassis" : {
+                "nodetype" : "namednumber",
+                "number" : "3"
+            },
+            "backplane" : {
+                "nodetype" : "namednumber",
+                "number" : "4"
+            },
+            "container" : {
+                "nodetype" : "namednumber",
+                "number" : "5"
+            },
+            "powerSupply" : {
+                "nodetype" : "namednumber",
+                "number" : "6"
+            },
+            "fan" : {
+                "nodetype" : "namednumber",
+                "number" : "7"
+            },
+            "sensor" : {
+                "nodetype" : "namednumber",
+                "number" : "8"
+            },
+            "module" : {
+                "nodetype" : "namednumber",
+                "number" : "9"
+            },
+            "port" : {
+                "nodetype" : "namednumber",
+                "number" : "10"
+            },
+            "stack" : {
+                "nodetype" : "namednumber",
+                "number" : "11"
+            },
+            "cpu" : {
+                "nodetype" : "namednumber",
+                "number" : "12"
+            },
+            "description" :
+                """Starting with version 4 of the ENTITY-MIB, this TC is
+deprecated, and the usage of the IANAPhysicalClass TC from
+the IANA-ENTITY-MIB is recommended instead.
+
+An enumerated value that 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; 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.""",
+        },
+    }, # typedefs
+
+    "nodes" : {
+        "entityMIB" : {
+            "nodetype" : "node",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47",
+            "status" : "current",
+        }, # node
+        "entityMIBObjects" : {
+            "nodetype" : "node",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1",
+        }, # node
+        "entityPhysical" : {
+            "nodetype" : "node",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1",
+        }, # node
+        "entPhysicalTable" : {
+            "nodetype" : "table",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1",
+            "status" : "current",
+            "description" :
+                """This table contains one row per physical entity.  There is
+always at least one row for an 'overall' physical entity.""",
+        }, # table
+        "entPhysicalEntry" : {
+            "nodetype" : "row",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1",
+            "status" : "current",
+            "linkage" : [
+                "entPhysicalIndex",
+            ],
+            "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.""",
+        }, # row
+        "entPhysicalIndex" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.1",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"ENTITY-MIB", "name" : "PhysicalIndex"},
+            },
+            "access" : "noaccess",
+            "description" :
+                """The index for this entry.""",
+        }, # column
+        "entPhysicalDescr" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.2",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
+            },
+            "access" : "readonly",
+            "description" :
+                """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.""",
+        }, # column
+        "entPhysicalVendorType" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.3",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "AutonomousType"},
+            },
+            "access" : "readonly",
+            "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 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.""",
+        }, # column
+        "entPhysicalContainedIn" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.4",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"ENTITY-MIB", "name" : "PhysicalIndexOrZero"},
+            },
+            "access" : "readonly",
+            "description" :
+                """The value of entPhysicalIndex for the physical entity that
+'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 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.""",
+        }, # column
+        "entPhysicalClass" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.5",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"IANA-ENTITY-MIB", "name" : "IANAPhysicalClass"},
+            },
+            "access" : "readonly",
+            "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.""",
+        }, # column
+        "entPhysicalParentRelPos" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.6",
+            "status" : "current",
+            "syntax" : {
+                "type" :                 {
+                    "basetype" : "Integer32",
+                    "ranges" : [
+                    {
+                        "min" : "-1",
+                        "max" : "2147483647"
+                    },
+                    ],
+                    "range" : {
+                        "min" : "-1",
+                        "max" : "2147483647"
+                    },
+                },
+            },
+            "access" : "readonly",
+            "description" :
+                """An indication of the relative position of this 'child'
+component among all its 'sibling' components.  Sibling
+components are defined as entPhysicalEntries that 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).
+
+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.""",
+        }, # column
+        "entPhysicalName" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.7",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
+            },
+            "access" : "readonly",
+            "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 (e.g., '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 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.""",
+        }, # column
+        "entPhysicalHardwareRev" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.8",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
+            },
+            "access" : "readonly",
+            "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 if this information is unknown to
+the agent, then this object will contain a zero-length
+string.""",
+        }, # column
+        "entPhysicalFirmwareRev" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.9",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
+            },
+            "access" : "readonly",
+            "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 if this information is unknown to the
+agent, then this object will contain a zero-length string.""",
+        }, # column
+        "entPhysicalSoftwareRev" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.10",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
+            },
+            "access" : "readonly",
+            "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 if this information is unknown to the
+agent, then this object will contain a zero-length string.""",
+        }, # column
+        "entPhysicalSerialNum" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.11",
+            "status" : "current",
+            "syntax" : {
+                "type" :                 {
+                    "basetype" : "OctetString",
+                    "parent module" : {
+                        "name" : "SNMP-FRAMEWORK-MIB",
+                        "type" : "SnmpAdminString",
+                    },
+                    "ranges" : [
+                    {
+                        "min" : "0",
+                        "max" : "32"
+                    },
+                    ],
+                    "range" : {
+                        "min" : "0",
+                        "max" : "32"
+                    },
+                },
+            },
+            "access" : "readwrite",
+            "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 a 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 that 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 numbers.  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.""",
+        }, # column
+        "entPhysicalMfgName" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.12",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
+            },
+            "access" : "readonly",
+            "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.""",
+        }, # column
+        "entPhysicalModelName" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.13",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
+            },
+            "access" : "readonly",
+            "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.""",
+        }, # column
+        "entPhysicalAlias" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.14",
+            "status" : "current",
+            "syntax" : {
+                "type" :                 {
+                    "basetype" : "OctetString",
+                    "parent module" : {
+                        "name" : "SNMP-FRAMEWORK-MIB",
+                        "type" : "SnmpAdminString",
+                    },
+                    "ranges" : [
+                    {
+                        "min" : "0",
+                        "max" : "32"
+                    },
+                    ],
+                    "range" : {
+                        "min" : "0",
+                        "max" : "32"
+                    },
+                },
+            },
+            "access" : "readwrite",
+            "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 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.""",
+        }, # column
+        "entPhysicalAssetID" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.15",
+            "status" : "current",
+            "syntax" : {
+                "type" :                 {
+                    "basetype" : "OctetString",
+                    "parent module" : {
+                        "name" : "SNMP-FRAMEWORK-MIB",
+                        "type" : "SnmpAdminString",
+                    },
+                    "ranges" : [
+                    {
+                        "min" : "0",
+                        "max" : "32"
+                    },
+                    ],
+                    "range" : {
+                        "min" : "0",
+                        "max" : "32"
+                    },
+                },
+            },
+            "access" : "readwrite",
+            "description" :
+                """This object is a user-assigned asset tracking identifier
+(as specified by a network manager) for the physical entity
+and provides non-volatile storage of this information.
+
+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.""",
+        }, # column
+        "entPhysicalIsFRU" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.16",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
+            },
+            "access" : "readonly",
+            "description" :
+                """This object indicates whether or not this physical entity
+is considered a 'field replaceable unit' by the vendor.
+If this object contains the value 'true(1)', then this
+entPhysicalEntry identifies a field replaceable unit.  For
+all entPhysicalEntries that represent components
+permanently contained within a field replaceable unit, the
+value 'false(2)' should be returned for this object.""",
+        }, # column
+        "entPhysicalMfgDate" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.17",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "DateAndTime"},
+            },
+            "access" : "readonly",
+            "description" :
+                """This object contains the date of manufacturing of the
+managed entity.  If the manufacturing date is unknown or
+not supported, the object is not instantiated.  The special
+value '0000000000000000'H may also be returned in this
+case.""",
+        }, # column
+        "entPhysicalUris" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.18",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"", "name" : "OctetString"},
+            },
+            "access" : "readwrite",
+            "description" :
+                """This object contains identification
+information about the physical entity.  The object
+contains URIs; therefore, the syntax of this object
+must conform to RFC 3986, Section 3.
+
+Multiple URIs may be present and are separated by white
+space characters.  Leading and trailing white space
+characters are ignored.
+
+If no URI identification information is known
+about the physical entity, the object is not
+instantiated.  A zero-length octet string may also be
+returned in this case.""",
+            "reference" :
+                """RFC 3986, Uniform Resource Identifiers (URI): Generic
+Syntax, Section 2, August 1998.""",
+        }, # column
+        "entPhysicalUUID" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.1.1.1.19",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"UUID-TC-MIB", "name" : "UUIDorZero"},
+            },
+            "access" : "readonly",
+            "description" :
+                """This object contains identification information
+about the physical entity.  The object contains a
+Universally Unique Identifier, the syntax of this object
+must conform to RFC 4122, Section 4.1.
+
+A zero-length octet string is returned if no UUID
+information is known.""",
+            "reference" :
+                """RFC 4122, A Universally Unique IDentifier (UUID) URN
+Namespace, Section 4.1, July 2005.""",
+        }, # column
+        "entityLogical" : {
+            "nodetype" : "node",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.2",
+        }, # node
+        "entLogicalTable" : {
+            "nodetype" : "table",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.2.1",
+            "status" : "current",
+            "description" :
+                """This table contains one row per logical entity.  For agents
+that implement more than one naming scope, at least one
+entry must exist.  Agents that instantiate all MIB objects
+within a single naming scope are not required to implement
+this table.""",
+        }, # table
+        "entLogicalEntry" : {
+            "nodetype" : "row",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.2.1.1",
+            "status" : "current",
+            "linkage" : [
+                "entLogicalIndex",
+            ],
+            "description" :
+                """Information about a particular logical entity.  Entities
+may be managed by this agent or other SNMP agents (possibly)
+in the same chassis.""",
+        }, # row
+        "entLogicalIndex" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.2.1.1.1",
+            "status" : "current",
+            "syntax" : {
+                "type" :                 {
+                    "basetype" : "Integer32",
+                    "ranges" : [
+                    {
+                        "min" : "1",
+                        "max" : "2147483647"
+                    },
+                    ],
+                    "range" : {
+                        "min" : "1",
+                        "max" : "2147483647"
+                    },
+                },
+            },
+            "access" : "noaccess",
+            "description" :
+                """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.""",
+        }, # column
+        "entLogicalDescr" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.2.1.1.2",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
+            },
+            "access" : "readonly",
+            "description" :
+                """A textual description of the logical entity.  This object
+should contain a string that identifies the manufacturer's
+name for the logical entity and should be set to a distinct
+value for each version of the logical entity.""",
+        }, # column
+        "entLogicalType" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.2.1.1.3",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "AutonomousType"},
+            },
+            "access" : "readonly",
+            "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 that 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.""",
+        }, # column
+        "entLogicalCommunity" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.2.1.1.4",
+            "status" : "deprecated",
+            "syntax" : {
+                "type" :                 {
+                    "basetype" : "OctetString",
+                    "ranges" : [
+                    {
+                        "min" : "0",
+                        "max" : "255"
+                    },
+                    ],
+                    "range" : {
+                        "min" : "0",
+                        "max" : "255"
+                    },
+                },
+            },
+            "access" : "readonly",
+            "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
+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 that 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).""",
+        }, # column
+        "entLogicalTAddress" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.2.1.1.5",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "TAddress"},
+            },
+            "access" : "readonly",
+            "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 contain the IP-address in network-byte order, and
+the last 2 contain the UDP port in network-byte order.
+Consult RFC 3417 for further information on snmpUDPDomain.""",
+            "reference" :
+                """Transport Mappings for the Simple Network Management
+Protocol (SNMP), STD 62, RFC 3417.""",
+        }, # column
+        "entLogicalTDomain" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.2.1.1.6",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "TDomain"},
+            },
+            "access" : "readonly",
+            "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
+RFC 3417.""",
+            "reference" :
+                """Transport Mappings for the Simple Network Management
+Protocol (SNMP), STD 62, RFC 3417.""",
+        }, # column
+        "entLogicalContextEngineID" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.2.1.1.7",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"ENTITY-MIB", "name" : "SnmpEngineIdOrNone"},
+            },
+            "access" : "readonly",
+            "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.""",
+        }, # column
+        "entLogicalContextName" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.2.1.1.8",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
+            },
+            "access" : "readonly",
+            "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 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.""",
+        }, # column
+        "entityMapping" : {
+            "nodetype" : "node",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.3",
+        }, # node
+        "entLPMappingTable" : {
+            "nodetype" : "table",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.3.1",
+            "status" : "current",
+            "description" :
+                """This table contains zero or more rows of logical entity to
+physical equipment associations.  For each logical entity
+known by this agent, there are zero or more mappings to the
+physical resources, which are used to realize that logical
+entity.
+
+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.""",
+        }, # table
+        "entLPMappingEntry" : {
+            "nodetype" : "row",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.3.1.1",
+            "status" : "current",
+            "linkage" : [
+                "entLogicalIndex",
+                "entLPPhysicalIndex",
+            ],
+            "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
+MIB modules used to manage a particular logical entity to
+infer how physical component information is utilized.""",
+        }, # row
+        "entLPPhysicalIndex" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.3.1.1.1",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"ENTITY-MIB", "name" : "PhysicalIndex"},
+            },
+            "access" : "readonly",
+            "description" :
+                """The value of this object identifies the index value of a
+particular entPhysicalEntry associated with the indicated
+entLogicalEntity.""",
+        }, # column
+        "entAliasMappingTable" : {
+            "nodetype" : "table",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.3.2",
+            "status" : "current",
+            "description" :
+                """This table contains zero or more rows, representing
+mappings of logical entities and physical components to
+external MIB identifiers.  Each physical port in the system
+may be associated with a mapping to an external identifier,
+which itself is associated with a particular logical
+
+
+
+
+
+
+entity's naming scope.  A 'wildcard' mechanism is provided
+to indicate that an identifier is associated with more than
+one logical entity.""",
+        }, # table
+        "entAliasMappingEntry" : {
+            "nodetype" : "row",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.3.2.1",
+            "status" : "current",
+            "linkage" : [
+                "entPhysicalIndex",
+                "entAliasLogicalIndexOrZero",
+            ],
+            "description" :
+                """Information about a particular binding between a
+logical entity/physical component pair and an external
+identifier.  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.""",
+        }, # row
+        "entAliasLogicalIndexOrZero" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.3.2.1.1",
+            "status" : "current",
+            "syntax" : {
+                "type" :                 {
+                    "basetype" : "Integer32",
+                    "ranges" : [
+                    {
+                        "min" : "0",
+                        "max" : "2147483647"
+                    },
+                    ],
+                    "range" : {
+                        "min" : "0",
+                        "max" : "2147483647"
+                    },
+                },
+            },
+            "access" : "noaccess",
+            "description" :
+                """The value of this object identifies the logical entity
+that defines the naming scope for the associated instance
+of the entAliasMappingIdentifier object.
+
+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.""",
+        }, # column
+        "entAliasMappingIdentifier" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.3.2.1.2",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "RowPointer"},
+            },
+            "access" : "readonly",
+            "description" :
+                """The value of this object identifies a particular conceptual
+row associated with the indicated entPhysicalIndex and
+entLogicalIndex pair.
+
+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.""",
+        }, # column
+        "entPhysicalContainsTable" : {
+            "nodetype" : "table",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.3.3",
+            "status" : "current",
+            "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.""",
+        }, # table
+        "entPhysicalContainsEntry" : {
+            "nodetype" : "row",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.3.3.1",
+            "status" : "current",
+            "linkage" : [
+                "entPhysicalIndex",
+                "entPhysicalChildIndex",
+            ],
+            "description" :
+                """A single container/'containee' relationship.""",
+        }, # row
+        "entPhysicalChildIndex" : {
+            "nodetype" : "column",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.3.3.1.1",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"ENTITY-MIB", "name" : "PhysicalIndex"},
+            },
+            "access" : "readonly",
+            "description" :
+                """The value of entPhysicalIndex for the contained physical
+entity.""",
+        }, # column
+        "entityGeneral" : {
+            "nodetype" : "node",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.4",
+        }, # node
+        "entLastChangeTime" : {
+            "nodetype" : "scalar",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.1.4.1",
+            "status" : "current",
+            "syntax" : {
+                "type" : { "module" :"SNMPv2-TC", "name" : "TimeStamp"},
+            },
+            "access" : "readonly",
+            "description" :
+                """The value of sysUpTime at the time a conceptual row is
+created, modified, or deleted in any of these tables:
+        - entPhysicalTable
+        - entLogicalTable
+        - entLPMappingTable
+        - entAliasMappingTable
+        - entPhysicalContainsTable""",
+        }, # scalar
+        "entityMIBTraps" : {
+            "nodetype" : "node",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.2",
+        }, # node
+        "entityMIBTrapPrefix" : {
+            "nodetype" : "node",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.2.0",
+        }, # node
+        "entityConformance" : {
+            "nodetype" : "node",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3",
+        }, # node
+        "entityCompliances" : {
+            "nodetype" : "node",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.1",
+        }, # node
+        "entityGroups" : {
+            "nodetype" : "node",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.2",
+        }, # node
+    }, # nodes
+
+    "notifications" : {
+        "entConfigChange" : {
+            "nodetype" : "notification",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.2.0.1",
+            "status" : "current",
+            "objects" : {
+            },
+            "description" :
+                """An entConfigChange notification is generated when the value
+of entLastChangeTime changes.  It can be utilized by an NMS
+to trigger logical/physical entity table maintenance polls.
+
+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.""",
+        }, # notification
+    }, # notifications
+
+    "groups" : {
+        "entityPhysicalGroup" : {
+            "nodetype" : "group",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.2.1",
+            "status" : "current",
+            "members" : {
+                "entPhysicalDescr" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entPhysicalVendorType" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entPhysicalContainedIn" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entPhysicalClass" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entPhysicalParentRelPos" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entPhysicalName" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+            }, # members
+            "description" :
+                """The collection of objects used to represent physical
+system components for which a single agent provides
+management information.""",
+        }, # group
+        "entityLogicalGroup" : {
+            "nodetype" : "group",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.2.2",
+            "status" : "deprecated",
+            "members" : {
+                "entLogicalDescr" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entLogicalType" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entLogicalCommunity" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entLogicalTAddress" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entLogicalTDomain" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+            }, # members
+            "description" :
+                """The collection of objects used to represent the list of
+logical entities for which a single agent provides
+management information.""",
+        }, # group
+        "entityMappingGroup" : {
+            "nodetype" : "group",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.2.3",
+            "status" : "current",
+            "members" : {
+                "entLPPhysicalIndex" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entAliasMappingIdentifier" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entPhysicalChildIndex" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+            }, # members
+            "description" :
+                """The collection of objects used to represent the
+associations between multiple logical entities, physical
+components, interfaces, and port identifiers for which a
+single agent provides management information.""",
+        }, # group
+        "entityGeneralGroup" : {
+            "nodetype" : "group",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.2.4",
+            "status" : "current",
+            "members" : {
+                "entLastChangeTime" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+            }, # members
+            "description" :
+                """The collection of objects used to represent general entity
+information for which a single agent provides management
+information.""",
+        }, # group
+        "entityNotificationsGroup" : {
+            "nodetype" : "group",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.2.5",
+            "status" : "current",
+            "members" : {
+                "entConfigChange" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+            }, # members
+            "description" :
+                """The collection of notifications used to indicate Entity MIB
+data consistency and general status information.""",
+        }, # group
+        "entityPhysical2Group" : {
+            "nodetype" : "group",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.2.6",
+            "status" : "current",
+            "members" : {
+                "entPhysicalHardwareRev" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entPhysicalFirmwareRev" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entPhysicalSoftwareRev" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entPhysicalSerialNum" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entPhysicalMfgName" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entPhysicalModelName" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entPhysicalAlias" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entPhysicalAssetID" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entPhysicalIsFRU" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+            }, # members
+            "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.""",
+        }, # group
+        "entityLogical2Group" : {
+            "nodetype" : "group",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.2.7",
+            "status" : "current",
+            "members" : {
+                "entLogicalDescr" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entLogicalType" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entLogicalTAddress" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entLogicalTDomain" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entLogicalContextEngineID" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entLogicalContextName" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+            }, # members
+            "description" :
+                """The collection of objects used to represent the
+list of logical entities for which a single SNMP entity
+provides management information.""",
+        }, # group
+        "entityPhysical3Group" : {
+            "nodetype" : "group",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.2.8",
+            "status" : "current",
+            "members" : {
+                "entPhysicalMfgDate" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entPhysicalUris" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+            }, # members
+            "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.""",
+        }, # group
+        "entityPhysical4Group" : {
+            "nodetype" : "group",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.2.9",
+            "status" : "current",
+            "members" : {
+                "entPhysicalUUID" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+            }, # members
+            "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 and
+entityPhysicalCRGroup.""",
+        }, # group
+        "entityPhysicalCRGroup" : {
+            "nodetype" : "group",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.2.10",
+            "status" : "current",
+            "members" : {
+                "entPhysicalClass" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+                "entPhysicalName" : {
+                    "nodetype" : "member",
+                    "module" : "ENTITY-MIB"
+                },
+            }, # members
+            "description" :
+                """The collection of objects used to represent physical
+system components for constrained resourced devices,
+for which a single agent provides management
+information.""",
+        }, # group
+    }, # groups
+
+    "compliances" : {
+        "entityCompliance" : {
+            "nodetype" : "compliance",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.1.1",
+            "status" : "deprecated",
+            "description" :
+                """The compliance statement for SNMP entities that implement
+version 1 of the Entity MIB.""",
+            "requires" : {
+                "entityPhysicalGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityLogicalGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityMappingGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityGeneralGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityNotificationsGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+            }, # requires
+        }, # compliance
+        "entity2Compliance" : {
+            "nodetype" : "compliance",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.1.2",
+            "status" : "deprecated",
+            "description" :
+                """The compliance statement for SNMP entities that implement
+version 2 of the Entity MIB.""",
+            "requires" : {
+                "entityPhysicalGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityPhysical2Group" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityGeneralGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityNotificationsGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityLogical2Group" : {
+                    "nodetype" : "optional",
+                    "module" : "ENTITY-MIB",
+                    "description" :
+                        """Implementation of this group is not mandatory for agents
+that model all MIB object instances within a single naming
+scope.""",
+                },
+                "entityMappingGroup" : {
+                    "nodetype" : "optional",
+                    "module" : "ENTITY-MIB",
+                    "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.""",
+                },
+            }, # requires
+            "refinements" : {
+                "entPhysicalSerialNum" : {
+                    "module" : "ENTITY-MIB",
+                    "access" : "noaccess",
+                    "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)'.""",
+                },
+                "entPhysicalAlias" : {
+                    "module" : "ENTITY-MIB",
+                    "access" : "readonly",
+                    "description" :
+                        """Write access is required only if the associated
+entPhysicalClass value is equal to 'chassis(3)'.""",
+                },
+                "entPhysicalAssetID" : {
+                    "module" : "ENTITY-MIB",
+                    "access" : "noaccess",
+                    "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)'.""",
+                },
+                "entPhysicalClass" : {
+                    "module" : "ENTITY-MIB",
+                    "syntax" : {
+                        "type" :                         {
+                            "basetype" : "Enumeration",
+                            "parent module" : {
+                                "name" : "IANA-ENTITY-MIB",
+                                "type" : "IANAPhysicalClass",
+                            },
+                            "other" : {
+                                "nodetype" : "namednumber",
+                                "number" : "1"
+                            },
+                            "unknown" : {
+                                "nodetype" : "namednumber",
+                                "number" : "2"
+                            },
+                            "chassis" : {
+                                "nodetype" : "namednumber",
+                                "number" : "3"
+                            },
+                            "backplane" : {
+                                "nodetype" : "namednumber",
+                                "number" : "4"
+                            },
+                            "container" : {
+                                "nodetype" : "namednumber",
+                                "number" : "5"
+                            },
+                            "powerSupply" : {
+                                "nodetype" : "namednumber",
+                                "number" : "6"
+                            },
+                            "fan" : {
+                                "nodetype" : "namednumber",
+                                "number" : "7"
+                            },
+                            "sensor" : {
+                                "nodetype" : "namednumber",
+                                "number" : "8"
+                            },
+                            "module" : {
+                                "nodetype" : "namednumber",
+                                "number" : "9"
+                            },
+                            "port" : {
+                                "nodetype" : "namednumber",
+                                "number" : "10"
+                            },
+                            "stack" : {
+                                "nodetype" : "namednumber",
+                                "number" : "11"
+                            },
+                        },
+                    }, # syntax
+                    "description" :
+                        """Implementation of the 'cpu(12)' enumeration is not
+required.""",
+                },
+            }, # refinements
+
+        }, # compliance
+        "entity3Compliance" : {
+            "nodetype" : "compliance",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.1.3",
+            "status" : "deprecated",
+            "description" :
+                """The compliance statement for SNMP entities that implement
+version 3 of the Entity MIB.""",
+            "requires" : {
+                "entityPhysicalGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityPhysical2Group" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityPhysical3Group" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityGeneralGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityNotificationsGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityLogical2Group" : {
+                    "nodetype" : "optional",
+                    "module" : "ENTITY-MIB",
+                    "description" :
+                        """Implementation of this group is not mandatory for agents
+that model all MIB object instances within a single naming
+scope.""",
+                },
+                "entityMappingGroup" : {
+                    "nodetype" : "optional",
+                    "module" : "ENTITY-MIB",
+                    "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.""",
+                },
+            }, # requires
+            "refinements" : {
+                "entPhysicalSerialNum" : {
+                    "module" : "ENTITY-MIB",
+                    "access" : "noaccess",
+                    "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)'.""",
+                },
+                "entPhysicalAlias" : {
+                    "module" : "ENTITY-MIB",
+                    "access" : "readonly",
+                    "description" :
+                        """Write access is required only if the associated
+entPhysicalClass value is equal to 'chassis(3)'.""",
+                },
+                "entPhysicalAssetID" : {
+                    "module" : "ENTITY-MIB",
+                    "access" : "noaccess",
+                    "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)'.""",
+                },
+            }, # refinements
+
+        }, # compliance
+        "entity4Compliance" : {
+            "nodetype" : "compliance",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.1.4",
+            "status" : "current",
+            "description" :
+                """The compliance statement for SNMP entities that implement
+the full version 4 (full compliance) of the Entity MIB.""",
+            "requires" : {
+                "entityPhysicalGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityPhysical2Group" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityPhysical3Group" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityGeneralGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityNotificationsGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityPhysical4Group" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityLogical2Group" : {
+                    "nodetype" : "optional",
+                    "module" : "ENTITY-MIB",
+                    "description" :
+                        """Implementation of this group is not mandatory for agents
+that model all MIB object instances within a single naming
+scope.""",
+                },
+                "entityMappingGroup" : {
+                    "nodetype" : "optional",
+                    "module" : "ENTITY-MIB",
+                    "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.""",
+                },
+            }, # requires
+            "refinements" : {
+                "entPhysicalSerialNum" : {
+                    "module" : "ENTITY-MIB",
+                    "access" : "noaccess",
+                    "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)'.""",
+                },
+                "entPhysicalAlias" : {
+                    "module" : "ENTITY-MIB",
+                    "access" : "readonly",
+                    "description" :
+                        """Write access is required only if the associated
+entPhysicalClass value is equal to 'chassis(3)'.""",
+                },
+                "entPhysicalAssetID" : {
+                    "module" : "ENTITY-MIB",
+                    "access" : "noaccess",
+                    "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)'.""",
+                },
+            }, # refinements
+
+        }, # compliance
+        "entity4CRCompliance" : {
+            "nodetype" : "compliance",
+            "moduleName" : "ENTITY-MIB",
+            "oid" : "1.3.6.1.2.1.47.3.1.5",
+            "status" : "current",
+            "description" :
+                """The compliance statement for SNMP entities that implement
+version 4 of the Entity MIB on devices with constrained
+resources.""",
+            "requires" : {
+                "entityPhysicalCRGroup" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+                "entityPhysical4Group" : {
+                    "nodetype" : "mandatory",
+                    "module" : "ENTITY-MIB"
+                },
+            }, # requires
+        }, # compliance
+    }, # compliances
+
+}