LLDP-EXT-MED-MIB: View SNMP OID List / Download MIB

The LLDP Management Information Base extension module for TIA-TR41.4 media endpoint discovery information. In order to assure the uniqueness of the LLDP-MIB, lldpXMedMIB is branched from lldpExtensions using the TIA OUI value as the node. An OUI/'company_id' is a 24 bit globally unique assigned number referenced by various standards. Copyright (C) TIA (2005). This version of this MIB module is published as Section 13.3 of ANSI/TIA-1057. See the standard itself for full legal notices.

A notification generated by the local device sensing a change in the topology that indicates that a new remote device attached to a local port, or a remote device disconnected or moved from one port to another.

Local Device Class.

A table that controls selection of LLDP TLVs to be transmitted on individual ports.

LLDP configuration information that controls the transmission of the MED organizationally defined TLVs on LLDP transmission capable ports. This configuration object augments the lldpPortConfigEntry of the LLDP-MIB, therefore it is only present along with the port configuration defined by the associated lldpPortConfigEntry entry. Each active lldpXMedPortConfigEntry must be stored and retrieved from non-volatile storage (along with the corresponding lldpPortConfigEntry) after a re-initialization of the management system.

The bitmap includes the MED organizationally defined set of LLDP TLVs whose transmission is possible for the respective port on the LLDP agent of the device. Each bit in the bitmap corresponds to an LLDP-MED subtype associated with a specific TIA TR41.4 MED optional TLV. If the bit is set, the agent supports the corresponding TLV.

The lldpXMedPortConfigTLVsTxEnable, defined as a bitmap, includes the MED organizationally defined set of LLDP TLVs whose transmission is allowed on the local LLDP agent by the network management. Each bit in the bitmap corresponds to an LLDP-MED subtype associated with a specific TIA TR41.4 MED optional TLV. If the bit is set, the agent will send the corresponding TLV if the respective capability is supported per port. Setting a bit with in this object for a non-supported capability shall have no functional effect and will result in an inconsistent value error returned to the management application. There are other rules and restrictions that prevent arbitrary combinations of TLVs to be enabled on LLDP-MED devices according to the device classes. These rules are defined in Section 10.2.1, Tables 5 - 9 of ANSI/TIA-1057. In case a management application attempts to set this object to a value that does not follow the rules, the set operation shall have and will result in an inconsistent value error returned to the management application. Setting this object to an empty set is valid and effectively disables LLDP-MED on a per-port basis by disabling transmission of all MED organizational TLVs. In this case the remote tables objects in the LLDP-MED MIB corresponding to the respective port will not be populated. The default value for lldpXMedPortConfigTLVsTxEnable object is an empty set, which means no enumerated values are set. The value of this object must be restored from non-volatile storage after a re-initialization of the management system.

A value of 'true(1)' enables sending the topology change traps on this port. A value of 'false(2)' disables sending the topology change traps on this port.

The number of times the fast start LLDPDU are being sent during the activation of the fast start mechanism defined by LLDP-MED.

This table contains one row per policy type per port of media policy information (as a part of the MED organizational extension) on the local system known to this agent.

Information about a particular policy on a specific port component.

The media type that defines the primary function of the application for the policy advertised by an endpoint.

An extension of the VLAN Identifier for the port, as defined in IEEE 802.1P-1998. A value of 1 through 4094 is used to define a valid PVID. A value of 0 shall be used if the device is using priority tagged frames, meaning that only the 802.1p priority level is significant and the default VID of the ingress port is being used instead. A value of 4095 is reserved for implementation use.

This object contains the value of the 802.1p priority which is associated with the given port on the local system.

This object contains the value of the Differentiated Service Code Point (DSCP) as defined in IETF RFC 2474 and RFC 2475 which is associated with the given port on the local system.

A value of 'true' indicates that the network policy for the specified application type is currently unknown. In this case, the VLAN ID, the layer 2 priority and the DSCP value fields are ignored. A value of 'false' indicates that this network policy is defined

A value of 'true' indicates that the application is using a tagged VLAN. A value of 'false' indicates that for the specific application the device either is using an untagged VLAN or does not support port based VLAN operation. In this case, both the VLAN ID and the Layer 2 priority fields are ignored and only the DSCP value has relevance

The vendor-specific hardware revision string as advertised by the endpoint.

The vendor-specific firmware revision string as advertised by the endpoint.

The vendor-specific software revision string as advertised by the endpoint.

The vendor-specific serial number as advertised by the endpoint.

The vendor-specific manufacturer name as advertised by the endpoint.

The vendor-specific model name as advertised by the endpoint.

The vendor-specific asset tracking identifier as advertised by the endpoint.

This table contains Location information as advertised by the local system. The information may be configured per port by a Location Information Server (LIS) or other management application. Multiple Location TLVs of different subtypes may be transmitted in the same PDU. The information in this table MUST be stored in non-volatile-memory and persist over restart/reboot sequences.

Information about Location information for the local device.

The location subtype advertised by the local device.

The location information. Parsing of this information is dependent upon the location subtype, as defined by the value of the lldpXMedLocLocationSubtype object.

Defines the type of Power-via-MDI (Power over Ethernet) advertised by the local device. A value pseDevice(2) indicates that the device is advertised as a Power Sourcing Entity (PSE). A value pdDevice(3) indicates that the device is advertised as a Powered Device (PD). A value of none(4) indicates that the device does not support PoE. Enumeration: 'unknown': 1, 'pdDevice': 3, 'pseDevice': 2, 'none': 4.

This table contains one row per port of PSE PoE information on the local system known to this agent.

Information about a particular port PoE information.

This object contains the value of the power available from the PSE via this port expressed in units of 0.1 watts.

Reflects the PD power priority that is being advertised on this PSE port. If both locally configure priority and ldpXMedRemXPoEPDPowerPriority are available on this port, it is a matter of local policy which one takes precedence. This object reflects the active value on this port. If the priority is not configured or known by the PD, the value unknown(1) will be returned. A value critical(2) indicates that the device advertises its power Priority as critical, as per RFC 3621. A value high(3) indicates that the device advertises its power Priority as high, as per RFC 3621. A value low(4) indicates that the device advertises its power Priority as low, as per RFC 3621. Enumeration: 'high': 3, 'unknown': 1, 'critical': 2, 'low': 4.

Defines the type of PSE Power Source advertised by the local device. A value primary(2) indicates that the device advertises its power source as primary. A value backup(3) indicates that the device advertises its power Source as backup. Enumeration: 'unknown': 1, 'backup': 3, 'primary': 2.

This object contains the value of the power required by a PD expressed in units of 0.1 watts.

Defines the type of Power Source advertised as being used by the local device. A value fromPSE(2) indicates that the device advertises its power source as received from a PSE. A value local(3) indicates that the device advertises its power source as local. A value localAndPSE(4) indicates that the device advertises its power source as using both local and PSE power. Enumeration: 'unknown': 1, 'fromPSE': 2, 'local': 3, 'localAndPSE': 4.

Defines the priority advertised as being required by this PD. A value critical(2) indicates that the device advertises its power Priority as critical, as per RFC 3621. A value high(3) indicates that the device advertises its power Priority as high, as per RFC 3621. A value low(4) indicates that the device advertises its power Priority as low, as per RFC 3621. Enumeration: 'high': 3, 'unknown': 1, 'critical': 2, 'low': 4.

A table that displays LLDP-MED capabilities of remote devices connected to individual ports.

LLDP-MED capabilities of remote devices connected to the device ports and communicating via LLDP-MED. The remote tables in the LLDP-MED MIB excepting this table may be sparsely populate. An entry in one of these table is meaningful and shall be populated by the agent only if the corresponding bits for the respective function are set in the objects in this table.

The bitmap includes the MED organizationally defined set of LLDP TLVs whose transmission is possible on the LLDP agent of the remote device connected to this port. Each bit in the bitmap corresponds to an LLDP-MED subtype associated with a specific TIA TR41.4 MED optional TLV. If the bit is set, the agent has the capability to support the corresponding TLV.

The bitmap includes the MED organizationally defined set of LLDP TLVs whose transmission is possible on the LLDP agent of the remote device connected to this port. Each bit in the bitmap corresponds to an LLDP-MED subtype associated with a specific TIA TR41.4 MED optional TLV. If the bit is set, the agent currently supports the corresponding TLV.

Device Class as advertised by the device remotely connected to the port.

This table contains media policy information as advertised by the remote system. This table may be sparsely populated. Entries in this table are relevant only if the networkPolicy(0) bits in the lldpXMedRemCapSupported and lldpXMedRemCapCurrent objects of the corresponding ports are set.

Information about the per port per policy type policy information for a particular physical network connection.

The media type that defines the primary function of the application for the policy advertised by the endpoint connected remotely to this port.

An extension of the VLAN Identifier for the remote system connected to this port, as defined in IEEE 802.1P-1998. A value of 1 through 4094 is used to define a valid PVID. A value of 0 shall be used if the device is using priority tagged frames, meaning that only the 802.1p priority level is significant and the default VID of the ingress port is being used instead. A value of 4095 is reserved for implementation use.

This object contains the value of the 802.1p priority which is associated with the remote system connected at given port.

This object contains the value of the Differentiated Service Code Point (DSCP) as defined in IETF RFC 2474 and RFC 2475 which is associated with remote system connected at the port.

A value of 'true' indicates that the network policy for the specified application type is currently unknown. In this case, the VLAN ID, the layer 2 priority and the DSCP value fields are ignored. A value of 'false' indicates that this network policy is defined.

A value of 'true' indicates that the application is using a tagged VLAN. A value of 'false' indicates that for the specific application the device either is using an untagged VLAN or does not support port based VLAN operation. In this case, both the VLAN ID and the Layer 2 priority fields are ignored and only the DSCP value has relevance

This table contains inventory information as advertised by the remote system. This table may be sparsely populated. Entries in this table are relevant only if the inventory(2) bits in the lldpXMedRemCapSupported and lldpXMedRemCapCurrent objects of the corresponding ports are set

Information about inventory information for the remote devices connected to the ports.

The vendor-specific hardware revision string as advertised by the remote endpoint.

The vendor-specific firmware revision string as advertised by the remote endpoint.

The vendor-specific software revision string as advertised by the remote endpoint.

The vendor-specific serial number as advertised by the remote endpoint.

The vendor-specific manufacturer name as advertised by the remote endpoint.

The vendor-specific model name as advertised by the remote endpoint.

The vendor-specific asset tracking identifier as advertised by the remote endpoint.

This table contains Location information as advertised by the remote system. This table may be sparsely populated. Entries in this table are relevant only if the Location(3) bits in the lldpXMedRemCapSupported and lldpXMedRemCapCurrent objects of the corresponding ports are set

Information about Location information for the remote devices connected to the ports.

The location subtype advertised by the remote endpoint.

The location information advertised by the remote endpoint. Parsing of this information is dependent upon the location subtype, as defined by the value of the corresponding lldpXMedRemLocationSubType object.

This table contains information about the PoE device type as advertised by the remote system. This table is densely populated.

Information about PoE type of the remote devices connected to the ports.

Defines the type of Power-via-MDI (Power over Ethernet) advertised by the remote device. A value pseDevice(2) indicates that the device is advertised as a Power Sourcing Entity (PSE). A value pdDevice(3) indicates that the device is advertised as a Powered Device (PD). A value none(4) indicates that the device does not support PoE. Enumeration: 'unknown': 1, 'pdDevice': 3, 'pseDevice': 2, 'none': 4.

This table contains extended PoE information as advertised by the remote devices of PSE type. This table may be sparsely populated. Entries in this table are relevant only if the extendedPSE(4) bits in the lldpXMedRemCapSupported and lldpXMedRemCapCurrent objects of the corresponding ports are set

Information about Extended PoE PSE information for the remote devices connected to the ports.

This object contains the value of the power available from the PSE via this port expressed in units of 0.1 watts on the remote device.

Defines the type of PSE Power Source advertised by the remote device. A value primary(2) indicates that the device advertises its power source as primary. A value backup(3) indicates that the device advertises its power Source as backup. Enumeration: 'unknown': 1, 'backup': 3, 'primary': 2.

This object contains the value of the PSE power priority advertised by the remote device. A value critical(2) indicates that the device advertises its power priority as critical, as per RFC 3621. A value high(3) indicates that the device advertises its power priority as high, as per RFC 3621. A value low(4) indicates that the device advertises its power priority as low, as per RFC 3621. Enumeration: 'high': 3, 'unknown': 1, 'critical': 2, 'low': 4.

This table contains extended PoE information as advertised by the remote devices of PD type. This table may be sparsely populated. Entries in this table are relevant only if the extendedPD(5) bits in the lldpXMedRemCapSupported and lldpXMedRemCapCurrent objects of the corresponding ports are set

Information about XPoEPD information for the remote devices connected to the ports.

This object contains the value of the power required by a PD connected remotely to the port expressed in units of 0.1 watts.

Defines the type of Power Source advertised as being used by the device connected remotely to the port. A value fromPSE(2) indicates that the device advertises its power source as received from a PSE. A value local(3) indicates that the device advertises its power source as local. A value localAndPSE(4) indicates that the device advertises its power source as using both local and PSE power. Enumeration: 'unknown': 1, 'fromPSE': 2, 'local': 3, 'localAndPSE': 4.

Defines the priority advertised as being required by the PD connected remotely to the port. A value critical(2) indicates that the device advertises its power Priority as critical, as per RFC 3621. A value high(3) indicates that the device advertises its power Priority as high, as per RFC 3621. A value low(4) indicates that the device advertises its power Priority as low, as per RFC 3621. Enumeration: 'high': 3, 'unknown': 1, 'critical': 2, 'low': 4.

The compliance statement for SNMP entities which implement the LLDP MED extension MIB.

The collection of objects which are used to configure or describe the configuration or behavior of the LLDP-MED organizational extension implementation.

The collection of objects which are used to represent LLDP MED organizational extensions for Media Policy Information.

The collection of objects which are used to represent LLDP MED organizational extension for inventory Information.

The collection of objects which are used to represent LLDP MED organizational extension for Location Information.

The collection of objects which are used to represent LLDP MED organizational extensions for PoE PSE Information.

The collection of objects which are used to represent LLDP MED organizational extensions for PoE PD Information.

The collection of objects which are used to represent LLDP- MED organizational extension Remote Device Information.

Notifications sent by an LLDP-MED agent.