LLDP-EXT-MED-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.
Main OID:
lldpXMedMIB.1.3.6.1.4.1.3320.127.1.5.4795
84
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
84 total| Object Name |
|---|
lldpXMedMIBThe 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 .1.3.6.1.4.1.3320.127.1.5.4795 |
lldpXMedNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.3320.127.1.5.4795.0 |
lldpXMedTopologyChangeDetectedA 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3320.127.1.5.4795.0.1 |
lldpXMedObjects OBJECT IDENTIFIER .1.3.6.1.4.1.3320.127.1.5.4795.1 |
lldpXMedConfig OBJECT IDENTIFIER .1.3.6.1.4.1.3320.127.1.5.4795.1.1 |
lldpXMedLocDeviceClassLocal Device Class.ro LldpXMedDeviceClass .1.3.6.1.4.1.3320.127.1.5.4795.1.1.1 |
lldpXMedPortConfigTableA table that controls selection of LLDP TLVs to be transmitted
on individual ports. SEQUENCE OF LldpXMedPortConfigEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.1.2 |
lldpXMedPortConfigEntryLLDP 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. LldpXMedPortConfigEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.1.2.1 |
lldpXMedPortCapSupportedThe 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.ro LldpXMedCapabilities .1.3.6.1.4.1.3320.127.1.5.4795.1.1.2.1.1 |
lldpXMedPortConfigTLVsTxEnableThe 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.rw LldpXMedCapabilities .1.3.6.1.4.1.3320.127.1.5.4795.1.1.2.1.2 |
lldpXMedPortConfigNotifEnableA 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.4795.1.1.2.1.3 |
lldpXMedFastStartRepeatCountThe number of times the fast start LLDPDU are being sent during the
activation of the fast start mechanism defined by LLDP-MED.rw Unsigned32 .1.3.6.1.4.1.3320.127.1.5.4795.1.1.3 |
lldpXMedLocalData OBJECT IDENTIFIER .1.3.6.1.4.1.3320.127.1.5.4795.1.2 |
lldpXMedLocMediaPolicyTableThis 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. SEQUENCE OF LldpXMedLocMediaPolicyEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.2.1 |
lldpXMedLocMediaPolicyEntryInformation about a particular policy on a specific
port component. LldpXMedLocMediaPolicyEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.2.1.1 |
lldpXMedLocMediaPolicyAppTypeThe media type that defines the primary function of the
application for the policy advertised by an endpoint. PolicyAppType .1.3.6.1.4.1.3320.127.1.5.4795.1.2.1.1.1 |
lldpXMedLocMediaPolicyVlanIDAn 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.ro Integer32 (0|1..4094|4095) .1.3.6.1.4.1.3320.127.1.5.4795.1.2.1.1.2 |
lldpXMedLocMediaPolicyPriorityThis object contains the value of the 802.1p priority
which is associated with the given port on the
local system.ro Integer32 .1.3.6.1.4.1.3320.127.1.5.4795.1.2.1.1.3 |
lldpXMedLocMediaPolicyDscpThis 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.ro Dscp (DIFFSERV-DSCP-TC) .1.3.6.1.4.1.3320.127.1.5.4795.1.2.1.1.4 |
lldpXMedLocMediaPolicyUnknownA 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 definedro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.4795.1.2.1.1.5 |
lldpXMedLocMediaPolicyTaggedA 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 relevancero TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.4795.1.2.1.1.6 |
lldpXMedLocHardwareRevThe vendor-specific hardware revision string
as advertised by the endpoint.ro SnmpAdminString .1.3.6.1.4.1.3320.127.1.5.4795.1.2.2 |
lldpXMedLocFirmwareRevThe vendor-specific firmware revision string
as advertised by the endpoint.ro SnmpAdminString .1.3.6.1.4.1.3320.127.1.5.4795.1.2.3 |
lldpXMedLocSoftwareRevThe vendor-specific software revision string
as advertised by the endpoint.ro SnmpAdminString .1.3.6.1.4.1.3320.127.1.5.4795.1.2.4 |
lldpXMedLocSerialNumThe vendor-specific serial number
as advertised by the endpoint.ro SnmpAdminString .1.3.6.1.4.1.3320.127.1.5.4795.1.2.5 |
lldpXMedLocMfgNameThe vendor-specific manufacturer name
as advertised by the endpoint.ro SnmpAdminString .1.3.6.1.4.1.3320.127.1.5.4795.1.2.6 |
lldpXMedLocModelNameThe vendor-specific model name
as advertised by the endpoint.ro SnmpAdminString .1.3.6.1.4.1.3320.127.1.5.4795.1.2.7 |
lldpXMedLocAssetIDThe vendor-specific asset tracking identifier
as advertised by the endpoint.ro SnmpAdminString .1.3.6.1.4.1.3320.127.1.5.4795.1.2.8 |
lldpXMedLocLocationTableThis 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. SEQUENCE OF LldpXMedLocLocationEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.2.9 |
lldpXMedLocLocationEntryInformation about Location information for the local device. LldpXMedLocLocationEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.2.9.1 |
lldpXMedLocLocationSubtypeThe location subtype advertised by the local device. LocationSubtype .1.3.6.1.4.1.3320.127.1.5.4795.1.2.9.1.1 |
lldpXMedLocLocationInfoThe location information. Parsing of this information is
dependent upon the location subtype, as defined by the value of the
lldpXMedLocLocationSubtype object.rw OCTET STRING .1.3.6.1.4.1.3320.127.1.5.4795.1.2.9.1.2 |
lldpXMedLocXPoEDeviceTypeDefines 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.ro Enumeration .1.3.6.1.4.1.3320.127.1.5.4795.1.2.10 |
lldpXMedLocXPoEPSEPortTableThis table contains one row per port of PSE PoE
information on the local system known to this agent. SEQUENCE OF LldpXMedLocXPoEPSEPortEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.2.11 |
lldpXMedLocXPoEPSEPortEntryInformation about a particular port PoE information. LldpXMedLocXPoEPSEPortEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.2.11.1 |
lldpXMedLocXPoEPSEPortPowerAvThis object contains the value of the power available from the
PSE via this port expressed in units of 0.1 watts.ro Gauge32 .1.3.6.1.4.1.3320.127.1.5.4795.1.2.11.1.1 |
lldpXMedLocXPoEPSEPortPDPriorityReflects 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.ro Enumeration .1.3.6.1.4.1.3320.127.1.5.4795.1.2.11.1.2 |
lldpXMedLocXPoEPSEPowerSourceDefines 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.ro Enumeration .1.3.6.1.4.1.3320.127.1.5.4795.1.2.12 |
lldpXMedLocXPoEPDPowerReqThis object contains the value of the power required by a
PD expressed in units of 0.1 watts.ro Gauge32 .1.3.6.1.4.1.3320.127.1.5.4795.1.2.13 |
lldpXMedLocXPoEPDPowerSourceDefines 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.ro Enumeration .1.3.6.1.4.1.3320.127.1.5.4795.1.2.14 |
lldpXMedLocXPoEPDPowerPriorityDefines 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.ro Enumeration .1.3.6.1.4.1.3320.127.1.5.4795.1.2.15 |
lldpXMedRemoteData OBJECT IDENTIFIER .1.3.6.1.4.1.3320.127.1.5.4795.1.3 |
lldpXMedRemCapabilitiesTableA table that displays LLDP-MED capabilities of remote devices
connected to individual ports. SEQUENCE OF LldpXMedRemCapabilitiesEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.3.1 |
lldpXMedRemCapabilitiesEntryLLDP-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. LldpXMedRemCapabilitiesEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.3.1.1 |
lldpXMedRemCapSupportedThe 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.ro LldpXMedCapabilities .1.3.6.1.4.1.3320.127.1.5.4795.1.3.1.1.1 |
lldpXMedRemCapCurrentThe 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.ro LldpXMedCapabilities .1.3.6.1.4.1.3320.127.1.5.4795.1.3.1.1.2 |
lldpXMedRemDeviceClassDevice Class as advertised by the device remotely connected to the
port.ro LldpXMedDeviceClass .1.3.6.1.4.1.3320.127.1.5.4795.1.3.1.1.3 |
lldpXMedRemMediaPolicyTableThis 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. SEQUENCE OF LldpXMedRemMediaPolicyEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.3.2 |
lldpXMedRemMediaPolicyEntryInformation about the per port per policy type policy
information for a particular physical network connection. LldpXMedRemMediaPolicyEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.3.2.1 |
lldpXMedRemMediaPolicyAppTypeThe media type that defines the primary function of the
application for the policy advertised by the endpoint connected
remotely to this port. PolicyAppType .1.3.6.1.4.1.3320.127.1.5.4795.1.3.2.1.1 |
lldpXMedRemMediaPolicyVlanIDAn 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.ro Integer32 (0|1..4094|4095) .1.3.6.1.4.1.3320.127.1.5.4795.1.3.2.1.2 |
lldpXMedRemMediaPolicyPriorityThis object contains the value of the 802.1p priority
which is associated with the remote system connected at
given port.ro Integer32 .1.3.6.1.4.1.3320.127.1.5.4795.1.3.2.1.3 |
lldpXMedRemMediaPolicyDscpThis 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.ro Dscp (DIFFSERV-DSCP-TC) .1.3.6.1.4.1.3320.127.1.5.4795.1.3.2.1.4 |
lldpXMedRemMediaPolicyUnknownA 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.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.4795.1.3.2.1.5 |
lldpXMedRemMediaPolicyTaggedA 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 relevancero TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3320.127.1.5.4795.1.3.2.1.6 |
lldpXMedRemInventoryTableThis 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 SEQUENCE OF LldpXMedRemInventoryEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.3.3 |
lldpXMedRemInventoryEntryInformation about inventory information for the remote devices
connected to the ports. LldpXMedRemInventoryEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.3.3.1 |
lldpXMedRemHardwareRevThe vendor-specific hardware revision string
as advertised by the remote endpoint.ro SnmpAdminString .1.3.6.1.4.1.3320.127.1.5.4795.1.3.3.1.1 |
lldpXMedRemFirmwareRevThe vendor-specific firmware revision string
as advertised by the remote endpoint.ro SnmpAdminString .1.3.6.1.4.1.3320.127.1.5.4795.1.3.3.1.2 |
lldpXMedRemSoftwareRevThe vendor-specific software revision string
as advertised by the remote endpoint.ro SnmpAdminString .1.3.6.1.4.1.3320.127.1.5.4795.1.3.3.1.3 |
lldpXMedRemSerialNumThe vendor-specific serial number
as advertised by the remote endpoint.ro SnmpAdminString .1.3.6.1.4.1.3320.127.1.5.4795.1.3.3.1.4 |
lldpXMedRemMfgNameThe vendor-specific manufacturer name
as advertised by the remote endpoint.ro SnmpAdminString .1.3.6.1.4.1.3320.127.1.5.4795.1.3.3.1.5 |
lldpXMedRemModelNameThe vendor-specific model name
as advertised by the remote endpoint.ro SnmpAdminString .1.3.6.1.4.1.3320.127.1.5.4795.1.3.3.1.6 |
lldpXMedRemAssetIDThe vendor-specific asset tracking identifier
as advertised by the remote endpoint.ro SnmpAdminString .1.3.6.1.4.1.3320.127.1.5.4795.1.3.3.1.7 |
lldpXMedRemLocationTableThis 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 SEQUENCE OF LldpXMedRemLocationEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.3.4 |
lldpXMedRemLocationEntryInformation about Location information for the remote devices
connected to the ports. LldpXMedRemLocationEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.3.4.1 |
lldpXMedRemLocationSubtypeThe location subtype advertised by the remote endpoint. LocationSubtype .1.3.6.1.4.1.3320.127.1.5.4795.1.3.4.1.1 |
lldpXMedRemLocationInfoThe 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.ro OCTET STRING .1.3.6.1.4.1.3320.127.1.5.4795.1.3.4.1.2 |
lldpXMedRemXPoETableThis table contains information about the PoE device type
as advertised by the remote system.
This table is densely populated. SEQUENCE OF LldpXMedRemXPoEEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.3.5 |
lldpXMedRemXPoEEntryInformation about PoE type of the remote devices
connected to the ports. LldpXMedRemXPoEEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.3.5.1 |
lldpXMedRemXPoEDeviceTypeDefines 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.ro Enumeration .1.3.6.1.4.1.3320.127.1.5.4795.1.3.5.1.1 |
lldpXMedRemXPoEPSETableThis 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 SEQUENCE OF LldpXMedRemXPoEPSEEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.3.6 |
lldpXMedRemXPoEPSEEntryInformation about Extended PoE PSE information for
the remote devices connected to the ports. LldpXMedRemXPoEPSEEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.3.6.1 |
lldpXMedRemXPoEPSEPowerAvThis 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.ro Gauge32 .1.3.6.1.4.1.3320.127.1.5.4795.1.3.6.1.1 |
lldpXMedRemXPoEPSEPowerSourceDefines 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.ro Enumeration .1.3.6.1.4.1.3320.127.1.5.4795.1.3.6.1.2 |
lldpXMedRemXPoEPSEPowerPriorityThis 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.ro Enumeration .1.3.6.1.4.1.3320.127.1.5.4795.1.3.6.1.3 |
lldpXMedRemXPoEPDTableThis 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 SEQUENCE OF LldpXMedRemXPoEPDEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.3.7 |
lldpXMedRemXPoEPDEntryInformation about XPoEPD information for the remote devices
connected to the ports. LldpXMedRemXPoEPDEntry .1.3.6.1.4.1.3320.127.1.5.4795.1.3.7.1 |
lldpXMedRemXPoEPDPowerReqThis object contains the value of the power required by a
PD connected remotely to the port
expressed in units of 0.1 watts.ro Gauge32 .1.3.6.1.4.1.3320.127.1.5.4795.1.3.7.1.1 |
lldpXMedRemXPoEPDPowerSourceDefines 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.ro Enumeration .1.3.6.1.4.1.3320.127.1.5.4795.1.3.7.1.2 |
lldpXMedRemXPoEPDPowerPriorityDefines 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.ro Enumeration .1.3.6.1.4.1.3320.127.1.5.4795.1.3.7.1.3 |
lldpXMedConformance OBJECT IDENTIFIER .1.3.6.1.4.1.3320.127.1.5.4795.2 |
lldpXMedCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.3320.127.1.5.4795.2.1 |
lldpXMedGroups OBJECT IDENTIFIER .1.3.6.1.4.1.3320.127.1.5.4795.2.2 |