
LLDP-EXT-MED-MIB
File:
LLDP-EXT-MED-MIB.mib (61520 bytes)
Imported modules
Imported symbols
Defined Objects
| lldpXMedMIB |
1.0.8802.1.1.2.1.5.4795 |
| 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. |
| MODULE-IDENTITY |
|
|
|
| lldpXMedPortConfigEntry |
1.0.8802.1.1.2.1.5.4795.1.1.2.1 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
LldpXMedPortConfigEntry |
|
|
| lldpXMedPortCapSupported |
1.0.8802.1.1.2.1.5.4795.1.1.2.1.1 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
LldpXMedCapabilities |
|
|
| lldpXMedPortConfigTLVsTxEnable |
1.0.8802.1.1.2.1.5.4795.1.1.2.1.2 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
LldpXMedCapabilities |
|
|
| lldpXMedLocLocationTable |
1.0.8802.1.1.2.1.5.4795.1.2.9 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
LldpXMedLocLocationEntry |
|
| lldpXMedLocLocationEntry |
1.0.8802.1.1.2.1.5.4795.1.2.9.1 |
| Information about Location information for the local device. |
| OBJECT-TYPE |
|
|
|
| |
LldpXMedLocLocationEntry |
|
|
| lldpXMedLocLocationInfo |
1.0.8802.1.1.2.1.5.4795.1.2.9.1.2 |
| The location information. Parsing of this information is dependent upon the location subtype, as defined by the value of the lldpXMedLocLocationSubtype object. |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
SIZE(0..256) |
|
| lldpXMedLocXPoEDeviceType |
1.0.8802.1.1.2.1.5.4795.1.2.10 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
unknown(1), pseDevice(2), pdDevice(3), none(4) |
|
| lldpXMedLocXPoEPSEPortEntry |
1.0.8802.1.1.2.1.5.4795.1.2.11.1 |
| Information about a particular port PoE information. |
| OBJECT-TYPE |
|
|
|
| |
LldpXMedLocXPoEPSEPortEntry |
|
|
| lldpXMedLocXPoEPSEPortPDPriority |
1.0.8802.1.1.2.1.5.4795.1.2.11.1.2 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
unknown(1), critical(2), high(3), low(4) |
|
| lldpXMedLocXPoEPSEPowerSource |
1.0.8802.1.1.2.1.5.4795.1.2.12 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
unknown(1), primary(2), backup(3) |
|
| lldpXMedLocXPoEPDPowerSource |
1.0.8802.1.1.2.1.5.4795.1.2.14 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
unknown(1), fromPSE(2), local(3), localAndPSE(4) |
|
| lldpXMedLocXPoEPDPowerPriority |
1.0.8802.1.1.2.1.5.4795.1.2.15 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
unknown(1), critical(2), high(3), low(4) |
|
| lldpXMedRemCapabilitiesEntry |
1.0.8802.1.1.2.1.5.4795.1.3.1.1 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
LldpXMedRemCapabilitiesEntry |
|
|
| lldpXMedRemCapSupported |
1.0.8802.1.1.2.1.5.4795.1.3.1.1.1 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
LldpXMedCapabilities |
|
|
| lldpXMedRemCapCurrent |
1.0.8802.1.1.2.1.5.4795.1.3.1.1.2 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
LldpXMedCapabilities |
|
|
| lldpXMedRemInventoryTable |
1.0.8802.1.1.2.1.5.4795.1.3.3 |
| 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 |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
LldpXMedRemInventoryEntry |
|
| lldpXMedRemInventoryEntry |
1.0.8802.1.1.2.1.5.4795.1.3.3.1 |
| Information about inventory information for the remote devices connected to the ports. |
| OBJECT-TYPE |
|
|
|
| |
LldpXMedRemInventoryEntry |
|
|
| lldpXMedRemLocationTable |
1.0.8802.1.1.2.1.5.4795.1.3.4 |
| 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 |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
LldpXMedRemLocationEntry |
|
| lldpXMedRemLocationEntry |
1.0.8802.1.1.2.1.5.4795.1.3.4.1 |
| Information about Location information for the remote devices connected to the ports. |
| OBJECT-TYPE |
|
|
|
| |
LldpXMedRemLocationEntry |
|
|
| lldpXMedRemLocationInfo |
1.0.8802.1.1.2.1.5.4795.1.3.4.1.2 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
SIZE(0..256) |
|
| lldpXMedRemXPoEEntry |
1.0.8802.1.1.2.1.5.4795.1.3.5.1 |
| Information about PoE type of the remote devices connected to the ports. |
| OBJECT-TYPE |
|
|
|
| |
LldpXMedRemXPoEEntry |
|
|
| lldpXMedRemXPoEDeviceType |
1.0.8802.1.1.2.1.5.4795.1.3.5.1.1 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
unknown(1), pseDevice(2), pdDevice(3), none(4) |
|
| lldpXMedRemXPoEPSETable |
1.0.8802.1.1.2.1.5.4795.1.3.6 |
| 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 |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
LldpXMedRemXPoEPSEEntry |
|
| lldpXMedRemXPoEPSEEntry |
1.0.8802.1.1.2.1.5.4795.1.3.6.1 |
| Information about Extended PoE PSE information for the remote devices connected to the ports. |
| OBJECT-TYPE |
|
|
|
| |
LldpXMedRemXPoEPSEEntry |
|
|
| lldpXMedRemXPoEPSEPowerAv |
1.0.8802.1.1.2.1.5.4795.1.3.6.1.1 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
Gauge32 |
0..1023 |
|
| lldpXMedRemXPoEPSEPowerSource |
1.0.8802.1.1.2.1.5.4795.1.3.6.1.2 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
unknown(1), primary(2), backup(3) |
|
| lldpXMedRemXPoEPSEPowerPriority |
1.0.8802.1.1.2.1.5.4795.1.3.6.1.3 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
unknown(1), critical(2), high(3), low(4) |
|
| lldpXMedRemXPoEPDTable |
1.0.8802.1.1.2.1.5.4795.1.3.7 |
| 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 |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
LldpXMedRemXPoEPDEntry |
|
| lldpXMedRemXPoEPDEntry |
1.0.8802.1.1.2.1.5.4795.1.3.7.1 |
| Information about XPoEPD information for the remote devices connected to the ports. |
| OBJECT-TYPE |
|
|
|
| |
LldpXMedRemXPoEPDEntry |
|
|
| lldpXMedRemXPoEPDPowerSource |
1.0.8802.1.1.2.1.5.4795.1.3.7.1.2 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
unknown(1), fromPSE(2), local(3), localAndPSE(4) |
|
| lldpXMedRemXPoEPDPowerPriority |
1.0.8802.1.1.2.1.5.4795.1.3.7.1.3 |
| 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. |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
unknown(1), critical(2), high(3), low(4) |
|
| lldpXMedConfigGroup |
1.0.8802.1.1.2.1.5.4795.2.2.1 |
| The collection of objects which are used to configure or describe the configuration or behavior of the LLDP-MED organizational extension implementation. |
| OBJECT-GROUP |
|
|
|
| lldpXMedOptLocationGroup |
1.0.8802.1.1.2.1.5.4795.2.2.4 |
| The collection of objects which are used to represent LLDP MED organizational extension for Location Information. |
| OBJECT-GROUP |
|
|
|
| lldpXMedOptPoEPSEGroup |
1.0.8802.1.1.2.1.5.4795.2.2.5 |
| The collection of objects which are used to represent LLDP MED organizational extensions for PoE PSE Information. |
| OBJECT-GROUP |
|
|
|
| lldpXMedOptPoEPDGroup |
1.0.8802.1.1.2.1.5.4795.2.2.6 |
| The collection of objects which are used to represent LLDP MED organizational extensions for PoE PD Information. |
| OBJECT-GROUP |
|
|
|
| lldpXMedRemSysGroup |
1.0.8802.1.1.2.1.5.4795.2.2.7 |
| The collection of objects which are used to represent LLDP- MED organizational extension Remote Device Information. |
| OBJECT-GROUP |
|
|
|
Defined Objects
| LldpXMedDeviceClass |
|
| Device Class to which the device is a member. A value of notDefined(0) indicates that the device has capabilities not covered by any of the LLDP-MED classes. A value of endpointClass1(1) indicates that the device has endpoint class 1 capabilities. A value of endpointClass2(2) indicates that the device has endpoint class 2 capabilities. A value of endpointClass3(3) indicates that the device has endpoint class 3 capabilities. A value of networkConnectivity(4) indicates that the device has network connectivity device capabilities. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
notDefined(0), endpointClass1(1), endpointClass2(2), endpointClass3(3), networkConnectivity(4) |
|
| LldpXMedCapabilities |
|
| Bitmap that includes the MED organizationally defined set of LLDP TLVs the device is capable of and whose transmission is allowed on the local LLDP agent by network management. Each bit in the bitmap corresponds to an LLDP-MED subtype associated with a specific TIA TR41.4 MED TLV. Having the bit 'capabilities(0)' set indicates that the LLDP agent refers to the Capabilities TLVs. Having the bit 'networkPolicy(1)' set indicates that the LLDP agent refers to the Network Policy TLVs. Having the bit 'location(2)' set indicates that the LLDP agent refers to the Emergency Communications System Location TLVs. Having the bit 'extendedPSE(3)' set indicates that the LLDP agent refers to the Extended PoE TLVs with PSE capabilities. Having the bit 'extendedPD(4)' set indicates that the LLDP agent refers to the Extended PoE TLVs with PD capabilities. Having the bit 'inventory(5)' set indicates that the LLDP agent refers to the Hardware Revision, Firmware Revision, Software Revision, Serial Number, Manufacturer Name, Model Name, and Asset ID TLVs. |
| TEXTUAL-CONVENTION |
|
|
|
| |
BITS |
capabilities(0), networkPolicy(1), location(2), extendedPSE(3), extendedPD(4), inventory(5) |
|
| LocationSubtype |
|
| The location subtype advertised by the remote endpoint. A value coordinateBased(2) indicates that the location subtype advertised by the endpoint is defined to use the relevant sub- fields of the DHCP option for Coordinate LCI as specified in ANSI/TIA-1057, Section 10.2.4.3.1. A value civicAddress(3) indicates that the location subtype advertised by the endpoint is defined to use the relevant sub- fields of the DHCP option for Civic Address as specified in ANSI/TIA-1057, Section 10.2.4.3.2. A value elin(4) indicates that the location subtype advertised by the endpoint is defined to use the Emergency Location Information Number (ELIN) as specified in ANSI/TIA-1057, Section 10.2.4.3.3. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
unknown(1), coordinateBased(2), civicAddress(3), elin(4) |
|
| PolicyAppType |
|
| The media type that defines the primary function of the application for the policy advertised by an endpoint. Having the bit voice(1) set indicates that the media type defining a primary function of the application for the policy advertised on the local port is voice. Having the bit voiceSignaling(3) set indicates that the media type defining a primary function of the application for the policy advertised on the local port is voice signaling. Having the bit guestVoice(4) set indicates that the media type Defining a primary function of the application for the policy advertised on the local port is guest voice. Having the bit guestVoiceSignaling(5) set indicates that the media type defining a primary function of the application for the policy advertised on the local port is guest voice signaling. Having the bit softPhoneVoice(6) set indicates that the media type Defining a primary function of the application for the policy advertised on the local port is softphone voice. Having the bit videoConferencing(7) set indicates that the media type defining a primary function of the application for the policy advertised on the local port is voice. Having the bit streamingVideo(8) set indicates that the media type defining a primary function of the application for the policy advertised on the local port is streaming video. Having the bit videoSignaling(2) set indicates that the media type defining a primary function of the application for the policy advertised on the local port is video signaling. |
| TEXTUAL-CONVENTION |
|
|
|
| |
BITS |
unknown(0), voice(1), voiceSignaling(2), guestVoice(3), guestVoiceSignaling(4), softPhoneVoice(5), videoconferencing(6), streamingVideo(7), videoSignaling(8) |
|
| LldpXMedPortConfigEntry |
|
| SEQUENCE |
|
|
|
| |
LldpXMedCapabilities as lldpXMedPortCapSupported |
|
|
| |
LldpXMedCapabilities as lldpXMedPortConfigTLVsTxEnable |
|
|
| |
TruthValue as lldpXMedPortConfigNotifEnable |
|
|
| LldpXMedLocLocationEntry |
|
| SEQUENCE |
|
|
|
| |
LocationSubtype as lldpXMedLocLocationSubtype |
|
|
| |
OCTET STRING as lldpXMedLocLocationInfo |
|
|
| LldpXMedLocXPoEPSEPortEntry |
|
| SEQUENCE |
|
|
|
| |
Gauge32 as lldpXMedLocXPoEPSEPortPowerAv |
|
|
| |
INTEGER as lldpXMedLocXPoEPSEPortPDPriority |
|
|
| LldpXMedRemCapabilitiesEntry |
|
| SEQUENCE |
|
|
|
| |
LldpXMedCapabilities as lldpXMedRemCapSupported |
|
|
| |
LldpXMedCapabilities as lldpXMedRemCapCurrent |
|
|
| |
LldpXMedDeviceClass as lldpXMedRemDeviceClass |
|
|
| LldpXMedRemInventoryEntry |
|
| SEQUENCE |
|
|
|
| |
SnmpAdminString as lldpXMedRemHardwareRev |
|
|
| |
SnmpAdminString as lldpXMedRemFirmwareRev |
|
|
| |
SnmpAdminString as lldpXMedRemSoftwareRev |
|
|
| |
SnmpAdminString as lldpXMedRemSerialNum |
|
|
| |
SnmpAdminString as lldpXMedRemMfgName |
|
|
| |
SnmpAdminString as lldpXMedRemModelName |
|
|
| |
SnmpAdminString as lldpXMedRemAssetID |
|
|
| LldpXMedRemLocationEntry |
|
| SEQUENCE |
|
|
|
| |
LocationSubtype as lldpXMedRemLocationSubtype |
|
|
| |
OCTET STRING as lldpXMedRemLocationInfo |
|
|
| LldpXMedRemXPoEEntry |
|
| SEQUENCE |
|
|
|
| |
INTEGER as lldpXMedRemXPoEDeviceType |
|
|
| LldpXMedRemXPoEPSEEntry |
|
| SEQUENCE |
|
|
|
| |
Gauge32 as lldpXMedRemXPoEPSEPowerAv |
|
|
| |
INTEGER as lldpXMedRemXPoEPSEPowerSource |
|
|
| |
INTEGER as lldpXMedRemXPoEPSEPowerPriority |
|
|
| LldpXMedRemXPoEPDEntry |
|
| SEQUENCE |
|
|
|
| |
Gauge32 as lldpXMedRemXPoEPDPowerReq |
|
|
| |
INTEGER as lldpXMedRemXPoEPDPowerSource |
|
|
| |
INTEGER as lldpXMedRemXPoEPDPowerPriority |
|
|