ENTITY-MIB

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

Imported Objects

IANAPhysicalClassIANA-ENTITY-MIB
SnmpAdminStringSNMP-FRAMEWORK-MIB
NOTIFICATION-GROUP, OBJECT-GROUP, MODULE-COMPLIANCESNMPv2-CONF
OBJECT-TYPE, Integer32, NOTIFICATION-TYPE, mib-2, MODULE-IDENTITYSNMPv2-SMI
TAddress, TEXTUAL-CONVENTION, AutonomousType, RowPointer, TimeStamp, TruthValue, DateAndTime, TDomainSNMPv2-TC
UUIDorZeroUUID-TC-MIB

Type Definitions (4)

Name Base Type Values/Constraints
PhysicalClassEnumerationother(1), unknown(2), chassis(3), backplane(4), container(5), powerSupply(6), fan(7), sensor(8), module(9), port(10), stack(11), cpu(12)
PhysicalIndexInteger32range: 1..2147483647
PhysicalIndexOrZeroInteger32range: 0..2147483647
SnmpEngineIdOrNoneOctetStringrange: 0..32

Objects

entityMIB .1.3.6.1.2.1.47
entityMIBObjects .1.3.6.1.2.1.47.1
entityPhysical .1.3.6.1.2.1.47.1.1
entPhysicalTable .1.3.6.1.2.1.47.1.1.1
entPhysicalEntry .1.3.6.1.2.1.47.1.1.1.1
entPhysicalIndex .1.3.6.1.2.1.47.1.1.1.1.1
entPhysicalSoftwareRev
.1.3.6.1.2.1.47.1.1.1.1.10
entPhysicalSerialNum .1.3.6.1.2.1.47.1.1.1.1.11
entPhysicalMfgName
.1.3.6.1.2.1.47.1.1.1.1.12
entPhysicalModelName
.1.3.6.1.2.1.47.1.1.1.1.13
entPhysicalAlias .1.3.6.1.2.1.47.1.1.1.1.14
entPhysicalAssetID .1.3.6.1.2.1.47.1.1.1.1.15
entPhysicalIsFRU
.1.3.6.1.2.1.47.1.1.1.1.16
entPhysicalMfgDate
.1.3.6.1.2.1.47.1.1.1.1.17
entPhysicalUris .1.3.6.1.2.1.47.1.1.1.1.18
entPhysicalUUID
.1.3.6.1.2.1.47.1.1.1.1.19
entPhysicalDescr
.1.3.6.1.2.1.47.1.1.1.1.2
entPhysicalVendorType
.1.3.6.1.2.1.47.1.1.1.1.3
entPhysicalContainedIn .1.3.6.1.2.1.47.1.1.1.1.4
entPhysicalClass
.1.3.6.1.2.1.47.1.1.1.1.5
entPhysicalParentRelPos .1.3.6.1.2.1.47.1.1.1.1.6
entPhysicalName
.1.3.6.1.2.1.47.1.1.1.1.7
entPhysicalHardwareRev
.1.3.6.1.2.1.47.1.1.1.1.8
entPhysicalFirmwareRev
.1.3.6.1.2.1.47.1.1.1.1.9
entityLogical .1.3.6.1.2.1.47.1.2
entLogicalTable .1.3.6.1.2.1.47.1.2.1
entLogicalEntry .1.3.6.1.2.1.47.1.2.1.1
entLogicalIndex .1.3.6.1.2.1.47.1.2.1.1.1
entLogicalDescr
.1.3.6.1.2.1.47.1.2.1.1.2
entLogicalType
.1.3.6.1.2.1.47.1.2.1.1.3
entLogicalCommunity deprecated .1.3.6.1.2.1.47.1.2.1.1.4
entLogicalTAddress
.1.3.6.1.2.1.47.1.2.1.1.5
entLogicalTDomain
.1.3.6.1.2.1.47.1.2.1.1.6
entLogicalContextEngineID .1.3.6.1.2.1.47.1.2.1.1.7
entLogicalContextName
.1.3.6.1.2.1.47.1.2.1.1.8
entityMapping .1.3.6.1.2.1.47.1.3
entLPMappingTable .1.3.6.1.2.1.47.1.3.1
entLPMappingEntry .1.3.6.1.2.1.47.1.3.1.1
entLPPhysicalIndex .1.3.6.1.2.1.47.1.3.1.1.1
entAliasMappingTable .1.3.6.1.2.1.47.1.3.2
entAliasMappingEntry .1.3.6.1.2.1.47.1.3.2.1
entAliasLogicalIndexOrZero .1.3.6.1.2.1.47.1.3.2.1.1
entAliasMappingIdentifier
.1.3.6.1.2.1.47.1.3.2.1.2
entPhysicalContainsTable .1.3.6.1.2.1.47.1.3.3
entPhysicalContainsEntry .1.3.6.1.2.1.47.1.3.3.1
entPhysicalChildIndex .1.3.6.1.2.1.47.1.3.3.1.1
entityGeneral .1.3.6.1.2.1.47.1.4
entLastChangeTime
.1.3.6.1.2.1.47.1.4.1
entityMIBTraps .1.3.6.1.2.1.47.2
entityMIBTrapPrefix .1.3.6.1.2.1.47.2.0
entityConformance .1.3.6.1.2.1.47.3
entityCompliances .1.3.6.1.2.1.47.3.1
entityGroups .1.3.6.1.2.1.47.3.2

Notifications/Traps

NameOIDDescription
entConfigChange.1.3.6.1.2.1.47.2.0.1
igChange 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.