MIB Browser
The MIB module for representing multiple physical
entities supported by a single SNMP agent. The MIB
is based on the standard RFC-2737 entity-mib.
Organization
PacketLight Networks Ltd.
Root OID
1.3.6.1.4.1.4515.1.3.6
Last updated
Objects
28
Source
Show full MIB
snmptranslate -m SL-ENTITY-MIB -Tp
snmpwalk -v2c -c <community> -m SL-ENTITY-MIB <host> 1.3.6.1.4.1.4515.1.3.6

Imports

IF-MIBInterfaceIndex
SL-MAIN-MIBslMain
SNMP-FRAMEWORK-MIBSnmpAdminString
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP
SNMPv2-SMIBits, Integer32, IpAddress, MODULE-IDENTITY, MibIdentifier, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, TimeTicks, Unsigned32, iso, mib-2
SNMPv2-TCAutonomousType, DisplayString, PhysAddress, RowStatus, TAddress, TDomain, TEXTUAL-CONVENTION, TimeStamp, TruthValue

OID tree

NameOIDTypeAccessStatusExample
IslmEntity1.3.6.1.4.1.4515.1.3.6
NslEntityPhysical1.3.6.1.4.1.4515.1.3.6.1
TslEntPhysicalTable1.3.6.1.4.1.4515.1.3.6.1.1NA
RslEntPhysicalEntry1.3.6.1.4.1.4515.1.3.6.1.1.1NA
CslEntPhysicalIndex1.3.6.1.4.1.4515.1.3.6.1.1.1.1InterfaceIndexRO
CslEntPhysicalDescr1.3.6.1.4.1.4515.1.3.6.1.1.1.2SnmpAdminStringROPL-1000E
CslEntPhysicalClass1.3.6.1.4.1.4515.1.3.6.1.1.1.3PhysicalClassRO
CslEntPhysicalHardwareRev1.3.6.1.4.1.4515.1.3.6.1.1.1.4SnmpAdminStringRO02-02
CslEntPhysicalFirmwareRev1.3.6.1.4.1.4515.1.3.6.1.1.1.5SnmpAdminStringRO3.4.20-A5-A016-2409
CslEntPhysicalSoftwareRev1.3.6.1.4.1.4515.1.3.6.1.1.1.6SnmpAdminStringRO
CslEntPhysicalSerialNum1.3.6.1.4.1.4515.1.3.6.1.1.1.7SnmpAdminString (SIZE (0..32))RO100800446
CslEntPhysicalProtectionEntity1.3.6.1.4.1.4515.1.3.6.1.1.1.8PhysicalIndexRO
CslEntPhysicalProtectState1.3.6.1.4.1.4515.1.3.6.1.1.1.9INTEGERRO
CslEntPhysicalProtectMode1.3.6.1.4.1.4515.1.3.6.1.1.1.14INTEGERRW
CslEntPhysicalStatus1.3.6.1.4.1.4515.1.3.6.1.1.1.15INTEGER (0..1023)RO
CslEntPhysicalFailureDescription1.3.6.1.4.1.4515.1.3.6.1.1.1.16SnmpAdminStringRO
CslEntPhysicalAdminStatus1.3.6.1.4.1.4515.1.3.6.1.1.1.17INTEGERRW
CslEntPhysicalOperStatus1.3.6.1.4.1.4515.1.3.6.1.1.1.18INTEGERRO
CslEntPhysicalSysUptime1.3.6.1.4.1.4515.1.3.6.1.1.1.19TimeTicksRO
CslEntPhysicalType1.3.6.1.4.1.4515.1.3.6.1.1.1.20PhysicalTypeRO
CslEntPhysicalCleiCode1.3.6.1.4.1.4515.1.3.6.1.1.1.21CleiCodeRO
CslEntPhysicalPartNumber1.3.6.1.4.1.4515.1.3.6.1.1.1.22SnmpAdminString (SIZE (0..12))RO
CslEntPhysicalOemSerialNum1.3.6.1.4.1.4515.1.3.6.1.1.1.23SnmpAdminString (SIZE (0..32))RO
CslEntPhysicalProductionDate1.3.6.1.4.1.4515.1.3.6.1.1.1.24SnmpAdminStringRW
CslEntPhysicalSysTemp1.3.6.1.4.1.4515.1.3.6.1.1.1.25INTEGERRO
CslEntPhysicalSysAlias1.3.6.1.4.1.4515.1.3.6.1.1.1.26SnmpAdminStringRW
CslEntPhysicalSysSubType1.3.6.1.4.1.4515.1.3.6.1.1.1.27INTEGERRO
NslEntityNotification1.3.6.1.4.1.4515.1.3.6.2

Textual conventions

CleiCode DisplayString (SIZE (10))
COMMON LANGUAGE Equipment Code.
The CLEI code contains an intelligent
ten-character code that identifies the
telecommunications equipment.
PhysicalClass INTEGER

backplane(4) chassis(3) container(5) fan(7) module(9) other(1) port(10) powerSupply(6) sensor(8) stack(11) unknown(2)

An enumerated value which provides an indication of the
general hardware type of a particular physical entity.
There are no restrictions as to the number of
slEntPhysicalEntries of each slEntPhysicalClass, which must be
instantiated by an agent.

The enumeration 'other' is applicable if the physical entity
class is known, but does not match any of the supported
values.

The enumeration 'unknown' is applicable if the physical
entity class is unknown to the agent.

The enumeration 'chassis' is applicable if the physical
entity class is an overall container for networking
equipment.  Any class of physical entity except a stack may
be contained within a chassis, and a chassis may only be
contained within a stack.

The enumeration 'backplane' is applicable if the physical
entity class is some sort of device for aggregating and
forwarding networking traffic, such as a shared backplane in
a modular ethernet switch.  Note that an agent may model a
backplane as a single physical entity, which is actually
implemented as multiple discrete physical components (within
a chassis or stack).

The enumeration 'container' is applicable if the physical
entity class is capable of containing one or more removable
physical entities, possibly of different types. For example,
each (empty or full) slot in a chassis will be modeled as a
container. Note that all removable physical entities should
be modeled within a container entity, such as field-
replaceable modules, fans, or power supplies.  Note that all
known containers should be modeled by the agent, including
empty containers.

The enumeration 'powerSupply' is applicable if the physical
entity class is a power-supplying component.

The enumeration 'fan' is applicable if the physical entity
class is a fan or other heat-reduction component.

The enumeration 'sensor' is applicable if the physical
entity class is some sort of sensor, such as a temperature
sensor within a router chassis.

The enumeration 'module' is applicable if the physical
entity class is some sort of self-contained sub-system.  If
it is removable, then it should be modeled within a
container entity, otherwise it should be modeled directly
within another physical entity (e.g., a chassis or another
module).

The enumeration 'port' is applicable if the physical entity
class is some sort of networking port, capable of receiving
and/or transmitting networking traffic.

The enumeration 'stack' is applicable if the physical entity
class is some sort of super-container (possibly virtual),
intended to group together multiple chassis entities.  A
stack may be realized by a 'virtual' cable, a real
interconnect cable, attached to multiple chassis, or may in
fact be comprised of multiple interconnect cables. A stack
should not be modeled within any other physical entities,
but a stack may be contained within another stack.  Only
chassis entities should be contained within a stack.
PhysicalIndex INTEGER (0..255)
An arbitrary value which uniquely identifies the physical
entity.  The value should be a small positive integer; index
values for different physical entities are not necessarily
contiguous.
The index 0 is for the Shelf.
The indices 1..100 are for the Cards.
The indices 101..102 are reserved for the Power-Supply.
The indices 103..110 are reserved for the Fans.
PhysicalType INTEGER

edfaModule(14) fanModule(2) lc400G(21) ocmModule(15) otdrModule(16) powerModule(1) switchModule(3) unknown(100)

An enumerated value which provides an indication of the
general card type of a particular physical entity.
There are no restrictions as to the number of
slEntPhysicalEntries of each PhysicalType, which must be
instantiated by an agent.

Used by