WikiStart: lldp-med-mib.txt

File lldp-med-mib.txt, 46.6 kB (added by karlheinzw, 4 years ago)

LLDP-MED MIB

Line 
1LLDP-EXT-MED-MIB DEFINITIONS ::= BEGIN
2IMPORTS
3MODULE-IDENTITY, OBJECT-TYPE, Integer32, Gauge32, Unsigned32,
4NOTIFICATION-TYPE
5FROM SNMPv2-SMI
6TEXTUAL-CONVENTION, TruthValue
7FROM SNMPv2-TC
8MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
9FROM SNMPv2-CONF
10lldpExtensions, lldpLocPortNum,
11lldpRemTimeMark, lldpRemLocalPortNum, lldpRemIndex,
12lldpPortConfigEntry, lldpRemChassisIdSubtype, lldpRemChassisId
13FROM LLDP-MIB
14Dscp
15FROM DIFFSERV-DSCP-TC
16SnmpAdminString
17FROM SNMP-FRAMEWORK-MIB;
18lldpXMedMIB MODULE-IDENTITY
19LAST-UPDATED "200507280000Z" -- July 28th, 2005
20ORGANIZATION "TIA TR41.4 Working Group"
21CONTACT-INFO
22" WG-URL: http://www.tiaonline.org/standards/sfg/scope.cfm#TR-41.4
23WG-EMail: tr41@tiacomm.org
24Contact: Chair, TIA TR-41
25Postal: Telecommunications Industry Association
262500 Wilson Blvd., Suite 300
27Arlington, VA 22201 USA
28Tel: (703) 907-7700
29E-mail: tr41@tiacomm.org"
30DESCRIPTION
31"The LLDP Management Information Base extension module for
32TIA-TR41.4 Media Endpoint Discovery information.
33In order to assure the uniqueness of the LLDP-MIB,
34lldpXMedMIB is branched from lldpExtensions using the TIA OUI
35value as the node. An OUI/'company_id' is a 24 bit globally
36unique assigned number referenced by various standards.
37Copyright (C) TIA (2005). This version of this MIB module
38is published as Section 13.3 of ANSI/TIA-1057.
39See the standard itself for full legal notices."
40REVISION "200507280000Z" -- July 28th, 2005
41DESCRIPTION
42"Published as part of ANSI/TIA-1057."
43-- OUI for TIA TR-41 is 4795 (00-12-BB)
44::= { lldpExtensions 4795 }
45------------------------------------------------------------------------------
46------------------------------------------------------------------------------
47--
48-- LLDP-MED Information
49--
50------------------------------------------------------------------------------
51------------------------------------------------------------------------------
52lldpXMedNotifications OBJECT IDENTIFIER ::= { lldpXMedMIB 0 }
53lldpXMedObjects OBJECT IDENTIFIER ::= { lldpXMedMIB 1 }
54-- LLDP MED Extension Notifications
55-- Transmission of LLDP MED Extension Notification is controlled by the
56-- lldpNotificationInterval object in the LLDP MIB defined in
57-- IEEE 802.1AB-2005
58lldpXMedTopologyChangeDetected NOTIFICATION-TYPE
59OBJECTS { lldpRemChassisIdSubtype,
60lldpRemChassisId,
61lldpXMedRemDeviceClass
62}
63STATUS current
64DESCRIPTION
65"A notification generated by the local device sensing
66a change in the topology that indicates that a new remote
67device attached to a local port, or a remote device disconnected
68or moved from one port to another."
69::= { lldpXMedNotifications 1 }
70-- LLDP MED extension MIB groups
71lldpXMedConfig OBJECT IDENTIFIER ::= { lldpXMedObjects 1 }
72lldpXMedLocalData OBJECT IDENTIFIER ::= { lldpXMedObjects 2 }
73lldpXMedRemoteData OBJECT IDENTIFIER ::= { lldpXMedObjects 3 }
74-- textual conventions
75LldpXMedDeviceClass ::= TEXTUAL-CONVENTION
76STATUS current
77DESCRIPTION
78"Device Class to which the device is a member.
79A value of notDefined(0) indicates that the device
80has capabilities not covered by any of the LLDP-MED classes.
81A value of endpointClass1(1) indicates that the device
82has endpoint class 1 capabilities.
83A value of endpointClass2(2) indicates that the device
84has endpoint class 2 capabilities.
85A value of endpointClass3(3) indicates that the device
86has endpoint class 3 capabilities.
87A value of networkConnectivity(4) indicates that the device
88has network connectivity device capabilities.
89"
90SYNTAX INTEGER {
91notDefined(0),
92endpointClass1(1),
93endpointClass2(2),
94endpointClass3(3),
95networkConnectivity(4)
96}
97-- LLDP-MED Capabilities TC
98LldpXMedCapabilities ::= TEXTUAL-CONVENTION
99STATUS current
100DESCRIPTION
101"Bitmap that includes the MED organizationally defined set of LLDP
102TLVs the device is capable of and whose transmission is allowed on
103the local LLDP agent by network management.
104Each bit in the bitmap corresponds to an LLDP-MED subtype associated
105with a specific TIA TR41.4 MED TLV.
106Having the bit 'capabilities(0)' set indicates that the LLDP
107agent refers to the Capabilities TLVs.
108Having the bit 'networkPolicy(1)' set indicates that the LLDP
109agent refers to the Network Policy TLVs.
110Having the bit 'location(2)' set indicates that
111the LLDP agent refers to the Emergency Communications
112System Location TLVs.
113Having the bit 'extendedPSE(3)' set indicates that
114the LLDP agent refers to the Extended PoE TLVs with PSE
115capabilities.
116Having the bit 'extendedPD(4)' set indicates that
117the LLDP agent refers to the Extended PoE TLVs with PD
118capabilities.
119Having the bit 'inventory(5)' set indicates that
120the LLDP agent refers to the Hardware Revision, Firmware
121Revision, Software Revision, Serial Number, Manufacturer Name,
122Model Name, and Asset ID TLVs."
123SYNTAX BITS {
124capabilities(0),
125networkPolicy(1),
126location(2),
127extendedPSE(3),
128extendedPD(4),
129inventory(5)
130}
131-- Location Subtype Textual Convention
132LocationSubtype ::= TEXTUAL-CONVENTION
133STATUS current
134DESCRIPTION
135"The location subtype advertised by the remote endpoint.
136A value coordinateBased(2) indicates that the location subtype
137advertised by the endpoint is defined to use the relevant subfields
138of the DHCP option for Coordinate LCI as specified in
139ANSI/TIA-1057, Section 10.2.4.3.1.
140A value civicAddress(3) indicates that the location subtype
141advertised by the endpoint is defined to use the relevant subfields
142of the DHCP option for Civic Address as specified in
143ANSI/TIA-1057, Section 10.2.4.3.2.
144A value elin(4) indicates that the location subtype
145advertised by the endpoint is defined to use the Emergency
146Location Information Number (ELIN) as specified in
147ANSI/TIA-1057, Section 10.2.4.3.3."
148SYNTAX INTEGER {
149unknown(1),
150coordinateBased(2),
151civicAddress(3),
152elin(4)
153}
154-- Policy Application Type Textual Convention
155PolicyAppType ::= TEXTUAL-CONVENTION
156STATUS current
157DESCRIPTION
158"The media type that defines the primary function of the
159application for the policy advertised by an endpoint.
160Having the bit voice(1) set indicates that the media type defining
161a primary function of the application for the policy advertised on
162the local port is voice.
163Having the bit voiceSignaling(3) set indicates that the media type
164defining a primary function of the application for the policy
165advertised on the local port is voice signaling.
166Having the bit guestVoice(4) set indicates that the media type
167Defining a primary function of the application for the policy
168advertised on the local port is guest voice.
169Having the bit guestVoiceSignaling(5) set indicates that the media
170type defining a primary function of the application for the policy
171advertised on the local port is guest voice signaling.
172Having the bit softPhoneVoice(6) set indicates that the media type
173Defining a primary function of the application for the policy
174advertised on the local port is softphone voice.
175Having the bit videoConferencing(7) set indicates that the media
176type defining a primary function of the application for the policy
177advertised on the local port is voice.
178Having the bit streamingVideo(8) set indicates that the media type
179defining a primary function of the application for the policy
180advertised on the local port is streaming video.
181Having the bit videoSignaling(2) set indicates that the media type
182defining a primary function of the application for the policy
183advertised on the local port is video signaling."
184SYNTAX BITS {
185unknown(0),
186voice(1),
187voiceSignaling(2),
188guestVoice(3),
189guestVoiceSignaling(4),
190softPhoneVoice(5),
191videoconferencing(6),
192streamingVideo(7),
193videoSignaling(8)
194}
195------------------------------------------------------------------------------
196-- MED - Configuration
197------------------------------------------------------------------------------
198lldpXMedLocDeviceClass OBJECT-TYPE
199SYNTAX LldpXMedDeviceClass
200MAX-ACCESS read-only
201STATUS current
202DESCRIPTION
203"Local Device Class."
204REFERENCE
205" ANSI/TIA-1057, Section 10.2.2.2"
206::= { lldpXMedConfig 1 }
207lldpXMedPortConfigTable OBJECT-TYPE
208SYNTAX SEQUENCE OF LldpXMedPortConfigEntry
209MAX-ACCESS not-accessible
210STATUS current
211DESCRIPTION
212"A table that controls selection of LLDP TLVs to be transmitted
213on individual ports."
214::= { lldpXMedConfig 2 }
215lldpXMedPortConfigEntry OBJECT-TYPE
216SYNTAX LldpXMedPortConfigEntry
217MAX-ACCESS not-accessible
218STATUS current
219DESCRIPTION
220"LLDP configuration information that controls the
221transmission of the MED organizationally defined TLVs on
222LLDP transmission capable ports.
223This configuration object augments the lldpPortConfigEntry of
224the LLDP-MIB, therefore it is only present along with the port
225configuration defined by the associated lldpPortConfigEntry
226entry.
227Each active lldpXMedPortConfigEntry must be stored and
228retrieved from non-volatile storage (along with the
229corresponding lldpPortConfigEntry) after a re-initialization
230of the management system."
231AUGMENTS { lldpPortConfigEntry }
232::= { lldpXMedPortConfigTable 1 }
233LldpXMedPortConfigEntry ::= SEQUENCE {
234lldpXMedPortCapSupported LldpXMedCapabilities,
235lldpXMedPortConfigTLVsTxEnable LldpXMedCapabilities,
236lldpXMedPortConfigNotifEnable TruthValue
237}
238lldpXMedPortCapSupported OBJECT-TYPE
239SYNTAX LldpXMedCapabilities
240MAX-ACCESS read-only
241STATUS current
242DESCRIPTION
243"The bitmap includes the MED organizationally defined set of LLDP
244TLVs whose transmission is possible for the respective port
245on the LLDP agent of the device. Each bit in the bitmap corresponds
246to an LLDP-MED subtype associated with a specific TIA TR41.4 MED
247optional TLV. If the bit is set, the agent supports the
248corresponding TLV."
249REFERENCE
250"ANSI/TIA-1057, Section 10.2.2.3"
251::= { lldpXMedPortConfigEntry 1 }
252lldpXMedPortConfigTLVsTxEnable OBJECT-TYPE
253SYNTAX LldpXMedCapabilities
254MAX-ACCESS read-write
255STATUS current
256DESCRIPTION
257"The lldpXMedPortConfigTLVsTxEnable, defined as a bitmap,
258includes the MED organizationally defined set of LLDP
259TLVs whose transmission is allowed on the local LLDP agent by
260the network management. Each bit in the bitmap corresponds
261to an LLDP-MED subtype associated with a specific TIA TR41.4 MED
262optional TLV. If the bit is set, the agent will send the
263corresponding TLV if the respective capability is supported per
264port.
265Setting a bit with in this object for a non-supported capability
266shall have no functional effect and will result in an inconsistent
267value error returned to the management application.
268There are other rules and restrictions that prevent arbitrary
269combinations of TLVs to be enabled on LLDP-MED devices according to
270the device classes. These rules are defined in Section 10.2.1,
271Tables 5 - 9 of ANSI/TIA-1057. In case a management application
272attempts to set this object to a value that does not follow the rules,
273the set operation shall have and will result in an inconsistent
274value error returned to the management application.
275Setting this object to an empty set is valid and effectively
276disables LLDP-MED on a per-port basis by disabling transmission of
277all MED organizational TLVs. In this case the remote tables objects
278in the LLDP-MED MIB corresponding to the respective port will not
279be populated.
280The default value for lldpXMedPortConfigTLVsTxEnable object
281is an empty set, which means no enumerated values are set.
282The value of this object must be restored from non-volatile
283storage after a re-initialization of the management system."
284REFERENCE
285"ANSI/TIA-1057, Section 10.2.2.3"
286DEFVAL { { } }
287::= { lldpXMedPortConfigEntry 2 }
288lldpXMedPortConfigNotifEnable OBJECT-TYPE
289SYNTAX TruthValue
290MAX-ACCESS read-write
291STATUS current
292DESCRIPTION
293"A value of 'true(1)' enables sending the topology change
294traps on this port.
295A value of 'false(2)' disables sending the topology change
296traps on this port."
297REFERENCE
298" ANSI/TIA-1057, Section 12.3"
299DEFVAL { false }
300::= { lldpXMedPortConfigEntry 3 }
301lldpXMedFastStartRepeatCount OBJECT-TYPE
302SYNTAX Unsigned32 (1..10)
303MAX-ACCESS read-write
304STATUS current
305DESCRIPTION
306"The number of times the fast start LLDPDU are being sent during the
307activation of the fast start mechanism defined by LLDP-MED."
308REFERENCE
309" ANSI/TIA-1057, Section 11.2.1"
310DEFVAL { 3 }
311::= { lldpXMedConfig 3 }
312------------------------------------------------------------------------------
313-- LLDP-MED - Local Device Information
314------------------------------------------------------------------------------
315---
316--- lldpXMedLocMediaPolicyTable: Local Media Policy
317--- Information Table
318---
319---
320lldpXMedLocMediaPolicyTable OBJECT-TYPE
321SYNTAX SEQUENCE OF LldpXMedLocMediaPolicyEntry
322MAX-ACCESS not-accessible
323STATUS current
324DESCRIPTION
325"This table contains one row per policy type per port
326of media policy information (as a part of the MED
327organizational extension) on the local system known
328to this agent."
329::= { lldpXMedLocalData 1 }
330lldpXMedLocMediaPolicyEntry OBJECT-TYPE
331SYNTAX LldpXMedLocMediaPolicyEntry
332MAX-ACCESS not-accessible
333STATUS current
334DESCRIPTION
335"Information about a particular policy on a specific
336port component."
337INDEX { lldpLocPortNum, lldpXMedLocMediaPolicyAppType }
338::= { lldpXMedLocMediaPolicyTable 1 }
339LldpXMedLocMediaPolicyEntry ::= SEQUENCE {
340lldpXMedLocMediaPolicyAppType PolicyAppType,
341lldpXMedLocMediaPolicyVlanID Integer32,
342lldpXMedLocMediaPolicyPriority Integer32,
343lldpXMedLocMediaPolicyDscp Dscp,
344lldpXMedLocMediaPolicyUnknown TruthValue,
345lldpXMedLocMediaPolicyTagged TruthValue
346}
347lldpXMedLocMediaPolicyAppType OBJECT-TYPE
348SYNTAX PolicyAppType
349MAX-ACCESS not-accessible
350STATUS current
351DESCRIPTION
352"The media type that defines the primary function of the
353application for the policy advertised by an endpoint."
354REFERENCE
355"ANSI/TIA-1057, Section 10.2.3.1"
356::= { lldpXMedLocMediaPolicyEntry 1 }
357lldpXMedLocMediaPolicyVlanID OBJECT-TYPE
358SYNTAX Integer32 (0|1..4094|4095)
359MAX-ACCESS read-only
360STATUS current
361DESCRIPTION
362"An extension of the VLAN Identifier for the port,
363as defined in IEEE 802.1P-1998.
364A value of 1 through 4094 is used to define a valid PVID.
365A value of 0 shall be used if the device is using priority tagged
366frames, meaning that only the 802.1p priority level is significant
367and the default VID of the ingress port is being used instead.
368A value of 4095 is reserved for implementation use."
369REFERENCE
370" ANSI/TIA-1057, Section 10.2.3.5"
371::= { lldpXMedLocMediaPolicyEntry 2 }
372lldpXMedLocMediaPolicyPriority OBJECT-TYPE
373SYNTAX Integer32 (0..7)
374MAX-ACCESS read-only
375STATUS current
376DESCRIPTION
377"This object contains the value of the 802.1p priority
378which is associated with the given port on the
379local system."
380REFERENCE
381" ANSI/TIA-1057, Section 10.2.3.6 "
382::= { lldpXMedLocMediaPolicyEntry 3 }
383lldpXMedLocMediaPolicyDscp OBJECT-TYPE
384SYNTAX Dscp
385MAX-ACCESS read-only
386STATUS current
387DESCRIPTION
388"This object contains the value of the Differentiated Service
389Code Point (DSCP) as defined in IETF RFC 2474 and RFC 2475
390which is associated with the given port on the local system."
391REFERENCE
392" ANSI/TIA-1057, Section 10.2.3.7"
393::= { lldpXMedLocMediaPolicyEntry 4 }
394lldpXMedLocMediaPolicyUnknown OBJECT-TYPE
395SYNTAX TruthValue
396MAX-ACCESS read-only
397STATUS current
398DESCRIPTION
399"A value of 'true' indicates that the
400network policy for the specified application type is
401currently unknown. In this case, the VLAN ID, the
402layer 2 priority and the DSCP value fields are ignored.
403A value of 'false' indicates that this network policy
404is defined "
405REFERENCE
406" ANSI/TIA-1057, Section 10.2.3.2"
407::= { lldpXMedLocMediaPolicyEntry 5 }
408lldpXMedLocMediaPolicyTagged OBJECT-TYPE
409SYNTAX TruthValue
410MAX-ACCESS read-only
411STATUS current
412DESCRIPTION
413"A value of 'true' indicates that the application is using a
414tagged VLAN.
415A value of 'false' indicates that for the specific application
416the device either is using an untagged VLAN or does not
417support port based VLAN operation. In this case, both the
418VLAN ID and the Layer 2 priority fields are ignored and
419only the DSCP value has relevance "
420REFERENCE
421" ANSI/TIA-1057, Section 10.2.3.3"
422::= { lldpXMedLocMediaPolicyEntry 6 }
423--- Inventory Information
424--- Local Inventory Information transmitted by an endpoint
425lldpXMedLocHardwareRev OBJECT-TYPE
426SYNTAX SnmpAdminString (SIZE (0..32))
427MAX-ACCESS read-only
428STATUS current
429DESCRIPTION
430"The vendor-specific hardware revision string
431as advertised by the endpoint."
432REFERENCE
433" ANSI/TIA-1057, Section 10.2.6.1"
434::= { lldpXMedLocalData 2 }
435lldpXMedLocFirmwareRev OBJECT-TYPE
436SYNTAX SnmpAdminString (SIZE (0..32))
437MAX-ACCESS read-only
438STATUS current
439DESCRIPTION
440"The vendor-specific firmware revision string
441as advertised by the endpoint."
442REFERENCE
443" ANSI/TIA-1057, Section 10.2.6.2"
444::= { lldpXMedLocalData 3 }
445lldpXMedLocSoftwareRev OBJECT-TYPE
446SYNTAX SnmpAdminString (SIZE (0..32))
447MAX-ACCESS read-only
448STATUS current
449DESCRIPTION
450"The vendor-specific software revision string
451as advertised by the endpoint."
452REFERENCE
453" ANSI/TIA-1057, Section 10.2.6.3"
454::= { lldpXMedLocalData 4 }
455lldpXMedLocSerialNum OBJECT-TYPE
456SYNTAX SnmpAdminString (SIZE (0..32))
457MAX-ACCESS read-only
458STATUS current
459DESCRIPTION
460"The vendor-specific serial number
461as advertised by the endpoint."
462REFERENCE
463" ANSI/TIA-1057, Section 10.2.6.4"
464::= { lldpXMedLocalData 5 }
465lldpXMedLocMfgName OBJECT-TYPE
466SYNTAX SnmpAdminString (SIZE (0..32))
467MAX-ACCESS read-only
468STATUS current
469DESCRIPTION
470"The vendor-specific manufacturer name
471as advertised by the endpoint."
472REFERENCE
473" ANSI/TIA-1057, Section 10.2.6.5"
474::= { lldpXMedLocalData 6 }
475lldpXMedLocModelName OBJECT-TYPE
476SYNTAX SnmpAdminString (SIZE (0..32))
477MAX-ACCESS read-only
478STATUS current
479DESCRIPTION
480"The vendor-specific model name
481as advertised by the endpoint."
482REFERENCE
483" ANSI/TIA-1057, Section 10.2.6.6"
484::= { lldpXMedLocalData 7 }
485lldpXMedLocAssetID OBJECT-TYPE
486SYNTAX SnmpAdminString (SIZE (0..32))
487MAX-ACCESS read-only
488STATUS current
489DESCRIPTION
490"The vendor-specific asset tracking identifier
491as advertised by the endpoint."
492REFERENCE
493" ANSI/TIA-1057, Section 10.2.6.7"
494::= { lldpXMedLocalData 8 }
495--- Location Information
496--- Local Location Information transmitted by an endpoint
497--- lldpXMedLocLocationTable - Location Information
498---
499lldpXMedLocLocationTable OBJECT-TYPE
500SYNTAX SEQUENCE OF LldpXMedLocLocationEntry
501MAX-ACCESS not-accessible
502STATUS current
503DESCRIPTION
504"This table contains Location information as advertised
505by the local system.
506The information may be configured per port by a Location
507Information Server (LIS) or other management application.
508Multiple Location TLVs of different subtypes may be transmitted
509in the same PDU.
510The information in this table MUST be stored in non-volatile-memory
511and persist over restart/reboot sequences."
512::= { lldpXMedLocalData 9 }
513lldpXMedLocLocationEntry OBJECT-TYPE
514SYNTAX LldpXMedLocLocationEntry
515MAX-ACCESS not-accessible
516STATUS current
517DESCRIPTION
518"Information about Location information for the local device."
519INDEX { lldpLocPortNum, lldpXMedLocLocationSubtype}
520::= { lldpXMedLocLocationTable 1 }
521LldpXMedLocLocationEntry ::= SEQUENCE {
522lldpXMedLocLocationSubtype LocationSubtype,
523lldpXMedLocLocationInfo OCTET STRING
524}
525lldpXMedLocLocationSubtype OBJECT-TYPE
526SYNTAX LocationSubtype
527MAX-ACCESS not-accessible
528STATUS current
529DESCRIPTION
530"The location subtype advertised by the local device."
531REFERENCE
532"ANSI/TIA-1057, Section 10.2.4.2"
533::= { lldpXMedLocLocationEntry 1 }
534lldpXMedLocLocationInfo OBJECT-TYPE
535SYNTAX OCTET STRING (SIZE (0..256))
536MAX-ACCESS read-write
537STATUS current
538DESCRIPTION
539"The location information. Parsing of this information is
540dependent upon the location subtype, as defined by the value of the
541lldpXMedLocLocationSubtype object. "
542REFERENCE
543"ANSI/TIA-1057, Section 10.2.4.3"
544DEFVAL { "" }
545::= { lldpXMedLocLocationEntry 2 }
546--- Extended Power over Ethernet objects
547---
548lldpXMedLocXPoEDeviceType OBJECT-TYPE
549SYNTAX INTEGER {
550unknown(1),
551pseDevice(2),
552pdDevice(3),
553none(4)
554}
555MAX-ACCESS read-only
556STATUS current
557DESCRIPTION
558"Defines the type of Power-via-MDI (Power over Ethernet) advertised
559by the local device.
560A value pseDevice(2) indicates that the device is advertised as a
561Power Sourcing Entity (PSE).
562A value pdDevice(3) indicates that the device is advertised as a
563Powered Device (PD).
564A value of none(4) indicates that the device does not support PoE."
565REFERENCE
566"ANSI/TIA-1057, Section 10.2.5.1"
567::= { lldpXMedLocalData 10 }
568--- Extended PoE - PSE objects
569--- PSE Port Table
570lldpXMedLocXPoEPSEPortTable OBJECT-TYPE
571SYNTAX SEQUENCE OF LldpXMedLocXPoEPSEPortEntry
572MAX-ACCESS not-accessible
573STATUS current
574DESCRIPTION
575"This table contains one row per port of PSE PoE
576information on the local system known to this agent."
577::= { lldpXMedLocalData 11 }
578lldpXMedLocXPoEPSEPortEntry OBJECT-TYPE
579SYNTAX LldpXMedLocXPoEPSEPortEntry
580MAX-ACCESS not-accessible
581STATUS current
582DESCRIPTION
583"Information about a particular port PoE information."
584INDEX { lldpLocPortNum }
585::= { lldpXMedLocXPoEPSEPortTable 1 }
586LldpXMedLocXPoEPSEPortEntry ::= SEQUENCE {
587lldpXMedLocXPoEPSEPortPowerAv Gauge32,
588lldpXMedLocXPoEPSEPortPDPriority INTEGER
589}
590lldpXMedLocXPoEPSEPortPowerAv OBJECT-TYPE
591SYNTAX Gauge32 (0..1023)
592UNITS "tenth of watt"
593MAX-ACCESS read-only
594STATUS current
595DESCRIPTION
596"This object contains the value of the power available from the
597PSE via this port expressed in units of 0.1 watts."
598REFERENCE
599" ANSI/TIA-1057, Section 10.2.5.4 "
600::= { lldpXMedLocXPoEPSEPortEntry 1 }
601lldpXMedLocXPoEPSEPortPDPriority OBJECT-TYPE
602SYNTAX INTEGER {
603unknown(1),
604critical(2),
605high(3),
606low(4)
607}
608MAX-ACCESS read-only
609STATUS current
610DESCRIPTION
611"Reflects the PD power priority that is being advertised on this
612PSE port.
613If both locally configure priority and
614ldpXMedRemXPoEPDPowerPriority are available on this port, it is
615a matter of local policy which one takes precedence. This object
616reflects the active value on this port.
617If the priority is not configured or known by the PD, the value
618unknown(1) will be returned.
619A value critical(2) indicates that the device advertises its power
620Priority as critical, as per RFC 3621.
621A value high(3) indicates that the device advertises its power
622Priority as high, as per RFC 3621.
623A value low(4) indicates that the device advertises its power
624Priority as low, as per RFC 3621."
625REFERENCE
626"ANSI/TIA-1057, Section 10.2.5.3"
627::= { lldpXMedLocXPoEPSEPortEntry 2 }
628lldpXMedLocXPoEPSEPowerSource OBJECT-TYPE
629SYNTAX INTEGER {
630unknown(1),
631primary(2),
632backup(3)
633}
634MAX-ACCESS read-only
635STATUS current
636DESCRIPTION
637"Defines the type of PSE Power Source advertised
638by the local device.
639A value primary(2) indicates that the device advertises its power
640source as primary.
641A value backup(3) indicates that the device advertises its power
642Source as backup."
643REFERENCE
644"ANSI/TIA-1057, Section 10.2.5.2"
645::= { lldpXMedLocalData 12 }
646--- Extended PoE - PD objects
647lldpXMedLocXPoEPDPowerReq OBJECT-TYPE
648SYNTAX Gauge32 (0..1023)
649UNITS "tenth of watt"
650MAX-ACCESS read-only
651STATUS current
652DESCRIPTION
653"This object contains the value of the power required by a
654PD expressed in units of 0.1 watts."
655REFERENCE
656" ANSI/TIA-1057, Section 10.2.4.3 "
657::= { lldpXMedLocalData 13 }
658lldpXMedLocXPoEPDPowerSource OBJECT-TYPE
659SYNTAX INTEGER {
660unknown(1),
661fromPSE(2),
662local(3),
663localAndPSE(4)
664}
665MAX-ACCESS read-only
666STATUS current
667DESCRIPTION
668"Defines the type of Power Source advertised as being used
669by the local device.
670A value fromPSE(2) indicates that the device advertises its power
671source as received from a PSE.
672A value local(3) indicates that the device advertises its power
673source as local.
674A value localAndPSE(4) indicates that the device advertises its
675power source as using both local and PSE power."
676REFERENCE
677"ANSI/TIA-1057, Section 10.2.5.2"
678::= { lldpXMedLocalData 14 }
679lldpXMedLocXPoEPDPowerPriority OBJECT-TYPE
680SYNTAX INTEGER {
681unknown(1),
682critical(2),
683high(3),
684low(4)
685}
686MAX-ACCESS read-only
687
688STATUS current
689DESCRIPTION
690"Defines the priority advertised as being required by this PD.
691A value critical(2) indicates that the device advertises its power
692Priority as critical, as per RFC 3621.
693A value high(3) indicates that the device advertises its power
694Priority as high, as per RFC 3621.
695A value low(4) indicates that the device advertises its power
696Priority as low, as per RFC 3621."
697REFERENCE
698"ANSI/TIA-1057, Section 10.2.5.3"
699::= { lldpXMedLocalData 15 }
700------------------------------------------------------------------------------
701-- LLDP-MED - Remote Devices Information
702------------------------------------------------------------------------------
703-- LLdpXMedRemCapabilitiesTable
704-- this table is read by a manager to determine what capabilities
705-- exists and are enabled on the remote system connected to the port
706-- The information in this table is based upon the information advertised
707-- by the remote device and received on each port in the capabilities TLV
708lldpXMedRemCapabilitiesTable OBJECT-TYPE
709SYNTAX SEQUENCE OF LldpXMedRemCapabilitiesEntry
710MAX-ACCESS not-accessible
711STATUS current
712DESCRIPTION
713"A table that displays LLDP-MED capabilities of remote devices
714connected to individual ports."
715::= { lldpXMedRemoteData 1 }
716lldpXMedRemCapabilitiesEntry OBJECT-TYPE
717SYNTAX LldpXMedRemCapabilitiesEntry
718MAX-ACCESS not-accessible
719STATUS current
720DESCRIPTION
721"LLDP-MED capabilities of remote devices connected to the device
722ports and communicating via LLDP-MED.
723The remote tables in the LLDP-MED MIB excepting this table may be
724sparsely populate. An entry in one of these table is meaningful
725and shall be populated by the agent only if the corresponding bits
726for the respective function are set in the objects in this table. "
727INDEX { lldpRemTimeMark,
728lldpRemLocalPortNum,
729lldpRemIndex }
730::= { lldpXMedRemCapabilitiesTable 1 }
731
732LldpXMedRemCapabilitiesEntry ::= SEQUENCE {
733lldpXMedRemCapSupported LldpXMedCapabilities,
734lldpXMedRemCapCurrent LldpXMedCapabilities,
735lldpXMedRemDeviceClass LldpXMedDeviceClass
736}
737lldpXMedRemCapSupported OBJECT-TYPE
738SYNTAX LldpXMedCapabilities
739MAX-ACCESS read-only
740STATUS current
741DESCRIPTION
742"The bitmap includes the MED organizationally defined set of LLDP
743TLVs whose transmission is possible on the LLDP agent of the remote
744device connected to this port. Each bit in the bitmap corresponds
745to an LLDP-MED subtype associated with a specific TIA TR41.4 MED
746optional TLV. If the bit is set, the agent has the capability
747to support the corresponding TLV."
748REFERENCE
749"ANSI/TIA-1057, Sections 10.2.2.1"
750::= { lldpXMedRemCapabilitiesEntry 1 }
751lldpXMedRemCapCurrent OBJECT-TYPE
752SYNTAX LldpXMedCapabilities
753MAX-ACCESS read-only
754STATUS current
755DESCRIPTION
756"The bitmap includes the MED organizationally defined set of LLDP
757TLVs whose transmission is possible on the LLDP agent of the remote
758device connected to this port. Each bit in the bitmap corresponds
759to an LLDP-MED subtype associated with a specific TIA TR41.4 MED
760optional TLV. If the bit is set, the agent currently supports the
761corresponding TLV."
762REFERENCE
763"ANSI/TIA-1057, Sections 10.2.2.1"
764::= { lldpXMedRemCapabilitiesEntry 2 }
765lldpXMedRemDeviceClass OBJECT-TYPE
766SYNTAX LldpXMedDeviceClass
767MAX-ACCESS read-only
768STATUS current
769DESCRIPTION
770"Device Class as advertised by the device remotely connected to the
771port."
772REFERENCE
773" ANSI/TIA-1057, Section 10.2.2.2"
774::= { lldpXMedRemCapabilitiesEntry 3 }
775---
776---
777--- lldpXMedRemMediaPolicyTable: Media Policy Table
778---
779---
780lldpXMedRemMediaPolicyTable OBJECT-TYPE
781SYNTAX SEQUENCE OF LldpXMedRemMediaPolicyEntry
782
783MAX-ACCESS not-accessible
784STATUS current
785DESCRIPTION
786"This table contains media policy information as advertised
787by the remote system.
788This table may be sparsely populated. Entries in this table are
789relevant only if the networkPolicy(0) bits in the
790lldpXMedRemCapSupported and lldpXMedRemCapCurrent objects of the
791corresponding ports are set."
792::= { lldpXMedRemoteData 2 }
793lldpXMedRemMediaPolicyEntry OBJECT-TYPE
794SYNTAX LldpXMedRemMediaPolicyEntry
795MAX-ACCESS not-accessible
796STATUS current
797DESCRIPTION
798"Information about the per port per policy type policy
799information for a particular physical network connection."
800INDEX { lldpRemTimeMark,
801lldpRemLocalPortNum,
802lldpRemIndex,
803lldpXMedRemMediaPolicyAppType }
804::= { lldpXMedRemMediaPolicyTable 1 }
805LldpXMedRemMediaPolicyEntry ::= SEQUENCE {
806lldpXMedRemMediaPolicyAppType PolicyAppType,
807lldpXMedRemMediaPolicyVlanID Integer32,
808lldpXMedRemMediaPolicyPriority Integer32,
809lldpXMedRemMediaPolicyDscp Dscp,
810lldpXMedRemMediaPolicyUnknown TruthValue,
811lldpXMedRemMediaPolicyTagged TruthValue
812}
813lldpXMedRemMediaPolicyAppType OBJECT-TYPE
814SYNTAX PolicyAppType
815MAX-ACCESS not-accessible
816STATUS current
817DESCRIPTION
818"The media type that defines the primary function of the
819application for the policy advertised by the endpoint connected
820remotely to this port."
821REFERENCE
822"ANSI/TIA-1057, Section 10.2.3.1"
823::= { lldpXMedRemMediaPolicyEntry 1 }
824lldpXMedRemMediaPolicyVlanID OBJECT-TYPE
825SYNTAX Integer32 (0|1..4094|4095)
826MAX-ACCESS read-only
827STATUS current
828DESCRIPTION
829"An extension of the VLAN Identifier for the remote system
830connected to this port, as defined in IEEE 802.1P-1998.
831A value of 1 through 4094 is used to define a valid PVID.
832
833A value of 0 shall be used if the device is using priority tagged
834frames, meaning that only the 802.1p priority level is significant
835and the default VID of the ingress port is being used instead.
836A value of 4095 is reserved for implementation use."
837REFERENCE
838" ANSI/TIA-1057, Section 10.2.3.5"
839::= { lldpXMedRemMediaPolicyEntry 2 }
840lldpXMedRemMediaPolicyPriority OBJECT-TYPE
841SYNTAX Integer32 (0..7)
842MAX-ACCESS read-only
843STATUS current
844DESCRIPTION
845"This object contains the value of the 802.1p priority
846which is associated with the remote system connected at
847given port."
848REFERENCE
849" ANSI/TIA-1057, Section 10.2.3.6"
850::= { lldpXMedRemMediaPolicyEntry 3 }
851lldpXMedRemMediaPolicyDscp OBJECT-TYPE
852SYNTAX Dscp
853MAX-ACCESS read-only
854STATUS current
855DESCRIPTION
856"This object contains the value of the Differentiated Service
857Code Point (DSCP) as defined in IETF RFC 2474 and RFC 2475
858which is associated with remote system connected at the port."
859REFERENCE
860" ANSI/TIA-1057, Section 10.2.3.7"
861::= { lldpXMedRemMediaPolicyEntry 4 }
862lldpXMedRemMediaPolicyUnknown OBJECT-TYPE
863SYNTAX TruthValue
864MAX-ACCESS read-only
865STATUS current
866DESCRIPTION
867"A value of 'true' indicates that the
868network policy for the specified application type is
869currently unknown. In this case, the VLAN ID, the
870layer 2 priority and the DSCP value fields are ignored.
871A value of 'false' indicates that this network policy
872is defined."
873REFERENCE
874" ANSI/TIA-1057, Section 10.2.3.2"
875::= { lldpXMedRemMediaPolicyEntry 5 }
876lldpXMedRemMediaPolicyTagged OBJECT-TYPE
877SYNTAX TruthValue
878MAX-ACCESS read-only
879STATUS current
880DESCRIPTION
881"A value of 'true' indicates that the application is using a
882tagged VLAN.
883A value of 'false' indicates that for the specific application
884the device either is using an untagged VLAN or does not
885support port based VLAN operation. In this case, both the
886VLAN ID and the Layer 2 priority fields are ignored and
887only the DSCP value has relevance "
888REFERENCE
889" ANSI/TIA-1057, Section 10.2.3.3"
890::= { lldpXMedRemMediaPolicyEntry 6 }
891--- lldpXMedRemInventoryTable - Remote Inventory Information
892---
893lldpXMedRemInventoryTable OBJECT-TYPE
894SYNTAX SEQUENCE OF LldpXMedRemInventoryEntry
895MAX-ACCESS not-accessible
896STATUS current
897DESCRIPTION
898"This table contains inventory information as advertised
899by the remote system.
900This table may be sparsely populated. Entries in this table are
901relevant only if the inventory(2) bits in the
902lldpXMedRemCapSupported and lldpXMedRemCapCurrent objects of the
903corresponding ports are set "
904::= { lldpXMedRemoteData 3 }
905lldpXMedRemInventoryEntry OBJECT-TYPE
906SYNTAX LldpXMedRemInventoryEntry
907MAX-ACCESS not-accessible
908STATUS current
909DESCRIPTION
910"Information about inventory information for the remote devices
911connected to the ports."
912INDEX { lldpRemTimeMark,
913lldpRemLocalPortNum,
914lldpRemIndex }
915::= { lldpXMedRemInventoryTable 1 }
916LldpXMedRemInventoryEntry ::= SEQUENCE {
917lldpXMedRemHardwareRev SnmpAdminString,
918lldpXMedRemFirmwareRev SnmpAdminString,
919lldpXMedRemSoftwareRev SnmpAdminString,
920lldpXMedRemSerialNum SnmpAdminString,
921lldpXMedRemMfgName SnmpAdminString,
922lldpXMedRemModelName SnmpAdminString,
923lldpXMedRemAssetID SnmpAdminString
924}
925lldpXMedRemHardwareRev OBJECT-TYPE
926SYNTAX SnmpAdminString (SIZE (0..32))
927MAX-ACCESS read-only
928STATUS current
929DESCRIPTION
930"The vendor-specific hardware revision string
931as advertised by the remote endpoint."
932REFERENCE
933" ANSI/TIA-1057, Section 10.2.6.1"
934::= { lldpXMedRemInventoryEntry 1 }
935lldpXMedRemFirmwareRev OBJECT-TYPE
936SYNTAX SnmpAdminString (SIZE (0..32))
937MAX-ACCESS read-only
938STATUS current
939DESCRIPTION
940"The vendor-specific firmware revision string
941as advertised by the remote endpoint."
942REFERENCE
943" ANSI/TIA-1057, Section 10.2.6.2"
944::= { lldpXMedRemInventoryEntry 2 }
945lldpXMedRemSoftwareRev OBJECT-TYPE
946SYNTAX SnmpAdminString (SIZE (0..32))
947MAX-ACCESS read-only
948STATUS current
949DESCRIPTION
950"The vendor-specific software revision string
951as advertised by the remote endpoint."
952REFERENCE
953" ANSI/TIA-1057, Section 10.2.6.3"
954::= { lldpXMedRemInventoryEntry 3 }
955lldpXMedRemSerialNum OBJECT-TYPE
956SYNTAX SnmpAdminString (SIZE (0..32))
957MAX-ACCESS read-only
958STATUS current
959DESCRIPTION
960"The vendor-specific serial number
961as advertised by the remote endpoint."
962REFERENCE
963" ANSI/TIA-1057, Section 10.2.6.4"
964::= { lldpXMedRemInventoryEntry 4 }
965lldpXMedRemMfgName OBJECT-TYPE
966SYNTAX SnmpAdminString (SIZE (0..32))
967MAX-ACCESS read-only
968STATUS current
969DESCRIPTION
970"The vendor-specific manufacturer name
971as advertised by the remote endpoint."
972REFERENCE
973" ANSI/TIA-1057, Section 10.2.6.5"
974::= { lldpXMedRemInventoryEntry 5 }
975lldpXMedRemModelName OBJECT-TYPE
976SYNTAX SnmpAdminString (SIZE (0..32))
977MAX-ACCESS read-only
978STATUS current
979DESCRIPTION
980"The vendor-specific model name
981as advertised by the remote endpoint."
982REFERENCE
983" ANSI/TIA-1057, Section 10.2.6.6"
984::= { lldpXMedRemInventoryEntry 6 }
985lldpXMedRemAssetID OBJECT-TYPE
986SYNTAX SnmpAdminString (SIZE (0..32))
987MAX-ACCESS read-only
988STATUS current
989DESCRIPTION
990"The vendor-specific asset tracking identifier
991as advertised by the remote endpoint."
992REFERENCE
993" ANSI/TIA-1057, Section 10.2.6.7"
994::= { lldpXMedRemInventoryEntry 7 }
995--- lldpXMedRemLocationTable - Remote Location Information
996---
997lldpXMedRemLocationTable OBJECT-TYPE
998SYNTAX SEQUENCE OF LldpXMedRemLocationEntry
999MAX-ACCESS not-accessible
1000STATUS current
1001DESCRIPTION
1002"This table contains Location information as advertised
1003by the remote system.
1004This table may be sparsely populated. Entries in this table are
1005relevant only if the Location(3) bits in the
1006lldpXMedRemCapSupported and lldpXMedRemCapCurrent objects of the
1007corresponding ports are set "
1008::= { lldpXMedRemoteData 4 }
1009lldpXMedRemLocationEntry OBJECT-TYPE
1010SYNTAX LldpXMedRemLocationEntry
1011MAX-ACCESS not-accessible
1012STATUS current
1013DESCRIPTION
1014"Information about Location information for the remote devices
1015connected to the ports."
1016INDEX { lldpRemTimeMark,
1017lldpRemLocalPortNum,
1018lldpRemIndex,
1019lldpXMedRemLocationSubtype}
1020::= { lldpXMedRemLocationTable 1 }
1021LldpXMedRemLocationEntry ::= SEQUENCE {
1022lldpXMedRemLocationSubtype LocationSubtype,
1023lldpXMedRemLocationInfo OCTET STRING
1024}
1025lldpXMedRemLocationSubtype OBJECT-TYPE
1026SYNTAX LocationSubtype
1027MAX-ACCESS not-accessible
1028STATUS current
1029DESCRIPTION
1030"The location subtype advertised by the remote endpoint."
1031REFERENCE
1032"ANSI/TIA-1057, Section 10.2.4.2 "
1033::= { lldpXMedRemLocationEntry 1 }
1034lldpXMedRemLocationInfo OBJECT-TYPE
1035SYNTAX OCTET STRING (SIZE (0..256))
1036MAX-ACCESS read-only
1037STATUS current
1038DESCRIPTION
1039"The location information advertised by the remote endpoint.
1040Parsing of this information is dependent upon the location
1041subtype, as defined by the value of the corresponding
1042lldpXMedRemLocationSubType object. "
1043REFERENCE
1044"ANSI/TIA-1057, Section 10.2.4.3 "
1045::= { lldpXMedRemLocationEntry 2 }
1046--- lldpXMedRemXPoETable - Information about Remote PoE Device Type
1047---
1048lldpXMedRemXPoETable OBJECT-TYPE
1049SYNTAX SEQUENCE OF LldpXMedRemXPoEEntry
1050MAX-ACCESS not-accessible
1051STATUS current
1052DESCRIPTION
1053"This table contains information about the PoE device type
1054as advertised by the remote system.
1055This table is densely populated."
1056::= { lldpXMedRemoteData 5 }
1057lldpXMedRemXPoEEntry OBJECT-TYPE
1058SYNTAX LldpXMedRemXPoEEntry
1059MAX-ACCESS not-accessible
1060STATUS current
1061DESCRIPTION
1062"Information about PoE type of the remote devices
1063connected to the ports."
1064INDEX { lldpRemTimeMark,
1065lldpRemLocalPortNum,
1066lldpRemIndex }
1067::= { lldpXMedRemXPoETable 1 }
1068LldpXMedRemXPoEEntry ::= SEQUENCE {
1069lldpXMedRemXPoEDeviceType INTEGER
1070}
1071lldpXMedRemXPoEDeviceType OBJECT-TYPE
1072SYNTAX INTEGER {
1073unknown(1),
1074pseDevice(2),
1075pdDevice(3),
1076none(4)
1077}
1078MAX-ACCESS read-only
1079STATUS current
1080DESCRIPTION
1081"Defines the type of Power-via-MDI (Power over Ethernet) advertised
1082by the remote device.
1083A value pseDevice(2) indicates that the device is advertised as a
1084Power Sourcing Entity (PSE).
1085A value pdDevice(3) indicates that the device is advertised as a
1086Powered Device (PD).
1087A value none(4) indicates that the device does not support PoE."
1088REFERENCE
1089"ANSI/TIA-1057, Section 10.2.5.1"
1090::= { lldpXMedRemXPoEEntry 1 }
1091--- lldpXMedRemXPoEPDTable - Extended PoE PSE Information from the remote device
1092---
1093lldpXMedRemXPoEPSETable OBJECT-TYPE
1094SYNTAX SEQUENCE OF LldpXMedRemXPoEPSEEntry
1095MAX-ACCESS not-accessible
1096STATUS current
1097DESCRIPTION
1098"This table contains extended PoE information as advertised
1099by the remote devices of PSE type.
1100This table may be sparsely populated. Entries in this table are
1101relevant only if the extendedPSE(4) bits in the
1102lldpXMedRemCapSupported and lldpXMedRemCapCurrent objects of the
1103corresponding ports are set "
1104::= { lldpXMedRemoteData 6 }
1105lldpXMedRemXPoEPSEEntry OBJECT-TYPE
1106SYNTAX LldpXMedRemXPoEPSEEntry
1107MAX-ACCESS not-accessible
1108STATUS current
1109DESCRIPTION
1110"Information about Extended PoE PSE information for
1111the remote devices connected to the ports."
1112INDEX { lldpRemTimeMark,
1113lldpRemLocalPortNum,
1114lldpRemIndex }
1115::= { lldpXMedRemXPoEPSETable 1 }
1116LldpXMedRemXPoEPSEEntry ::= SEQUENCE {
1117lldpXMedRemXPoEPSEPowerAv Gauge32,
1118lldpXMedRemXPoEPSEPowerSource INTEGER,
1119lldpXMedRemXPoEPSEPowerPriority INTEGER
1120}
1121lldpXMedRemXPoEPSEPowerAv OBJECT-TYPE
1122SYNTAX Gauge32 (0..1023)
1123UNITS "tenth of watt"
1124MAX-ACCESS read-only
1125STATUS current
1126DESCRIPTION
1127"This object contains the value of the power available from the
1128PSE via this port expressed in units of 0.1 watts on the remote
1129device."
1130REFERENCE
1131" ANSI/TIA-1057, Section 10.2.5.4"
1132::= { lldpXMedRemXPoEPSEEntry 1 }
1133lldpXMedRemXPoEPSEPowerSource OBJECT-TYPE
1134SYNTAX INTEGER {
1135unknown(1),
1136primary(2),
1137backup(3)
1138}
1139MAX-ACCESS read-only
1140STATUS current
1141DESCRIPTION
1142"Defines the type of PSE Power Source advertised
1143by the remote device.
1144A value primary(2) indicates that the device advertises its power
1145source as primary.
1146A value backup(3) indicates that the device advertises its power
1147Source as backup."
1148REFERENCE
1149"ANSI/TIA-1057, Section 10.2.5.2"
1150::= { lldpXMedRemXPoEPSEEntry 2 }
1151lldpXMedRemXPoEPSEPowerPriority OBJECT-TYPE
1152SYNTAX INTEGER {
1153unknown(1),
1154critical(2),
1155high(3),
1156low(4)
1157}
1158MAX-ACCESS read-only
1159STATUS current
1160DESCRIPTION
1161"This object contains the value of the PSE power priority
1162advertised by the remote device.
1163A value critical(2) indicates that the device advertises its power
1164priority as critical, as per RFC 3621.
1165A value high(3) indicates that the device advertises its power
1166priority as high, as per RFC 3621.
1167A value low(4) indicates that the device advertises its power
1168priority as low, as per RFC 3621."
1169REFERENCE
1170"ANSI/TIA-1057, Section 10.2.5.3"
1171::= { lldpXMedRemXPoEPSEEntry 3 }
1172--- lldpXMedRemXPoEPDTable - Extended PoE PD Information from the remote device
1173---
1174lldpXMedRemXPoEPDTable OBJECT-TYPE
1175SYNTAX SEQUENCE OF LldpXMedRemXPoEPDEntry
1176MAX-ACCESS not-accessible
1177STATUS current
1178DESCRIPTION
1179"This table contains extended PoE information as advertised
1180by the remote devices of PD type.
1181This table may be sparsely populated. Entries in this table are
1182relevant only if the extendedPD(5) bits in the
1183lldpXMedRemCapSupported and lldpXMedRemCapCurrent objects of the
1184corresponding ports are set "
1185::= { lldpXMedRemoteData 7 }
1186lldpXMedRemXPoEPDEntry OBJECT-TYPE
1187SYNTAX LldpXMedRemXPoEPDEntry
1188MAX-ACCESS not-accessible
1189STATUS current
1190DESCRIPTION
1191"Information about XPoEPD information for the remote devices
1192connected to the ports."
1193INDEX { lldpRemTimeMark,
1194lldpRemLocalPortNum,
1195lldpRemIndex }
1196::= { lldpXMedRemXPoEPDTable 1 }
1197LldpXMedRemXPoEPDEntry ::= SEQUENCE {
1198lldpXMedRemXPoEPDPowerReq Gauge32,
1199lldpXMedRemXPoEPDPowerSource INTEGER,
1200lldpXMedRemXPoEPDPowerPriority INTEGER
1201}
1202lldpXMedRemXPoEPDPowerReq OBJECT-TYPE
1203SYNTAX Gauge32 (0..1023)
1204UNITS "tenth of watt"
1205MAX-ACCESS read-only
1206STATUS current
1207DESCRIPTION
1208"This object contains the value of the power required by a
1209PD connected remotely to the port
1210expressed in units of 0.1 watts."
1211REFERENCE
1212" ANSI/TIA-1057, Section 10.2.5.4 "
1213::= { lldpXMedRemXPoEPDEntry 1 }
1214lldpXMedRemXPoEPDPowerSource OBJECT-TYPE
1215SYNTAX INTEGER {
1216unknown(1),
1217fromPSE(2),
1218local(3),
1219localAndPSE(4)
1220}
1221MAX-ACCESS read-only
1222STATUS current
1223DESCRIPTION
1224"Defines the type of Power Source advertised as being used
1225by the device connected remotely to the port.
1226A value fromPSE(2) indicates that the device advertises its power
1227source as received from a PSE.
1228A value local(3) indicates that the device advertises its power
1229source as local.
1230A value localAndPSE(4) indicates that the device advertises its
1231power source as using both local and PSE power."
1232REFERENCE
1233"ANSI/TIA-1057, Section 10.2.5.2"
1234::= { lldpXMedRemXPoEPDEntry 2 }
1235lldpXMedRemXPoEPDPowerPriority OBJECT-TYPE
1236SYNTAX INTEGER {
1237unknown(1),
1238critical(2),
1239high(3),
1240low(4)
1241}
1242MAX-ACCESS read-only
1243STATUS current
1244DESCRIPTION
1245"Defines the priority advertised as being required by the PD
1246connected remotely to the port.
1247A value critical(2) indicates that the device advertises its power
1248Priority as critical, as per RFC 3621.
1249A value high(3) indicates that the device advertises its power
1250Priority as high, as per RFC 3621.
1251A value low(4) indicates that the device advertises its power
1252Priority as low, as per RFC 3621."
1253REFERENCE
1254"ANSI/TIA-1057, Section 10.2.5.3"
1255::= { lldpXMedRemXPoEPDEntry 3 }
1256---
1257-- conformance information
1258lldpXMedConformance OBJECT IDENTIFIER ::= { lldpXMedMIB 2 }
1259lldpXMedCompliances OBJECT IDENTIFIER ::= { lldpXMedConformance 1 }
1260lldpXMedGroups OBJECT IDENTIFIER ::= { lldpXMedConformance 2 }
1261-- compliance statements
1262lldpXMedCompliance MODULE-COMPLIANCE
1263STATUS current
1264DESCRIPTION
1265"The compliance statement for SNMP entities which implement
1266the LLDP MED extension MIB."
1267MODULE -- this module
1268MANDATORY-GROUPS { lldpXMedConfigGroup,
1269lldpXMedRemSysGroup,
1270lldpXMedNotificationsGroup
1271}
1272GROUP lldpXMedOptMediaPolicyGroup
1273DESCRIPTION
1274"This group represents the information associated with
1275the LLDP-MED optional Media Policy TLVs,
1276therefore the agent may not implement them."
1277GROUP lldpXMedOptInventoryGroup
1278DESCRIPTION
1279"This group represents the information associated with
1280the LLDP-MED optional inventory TLVs,
1281therefore the agent may not implement them."
1282GROUP lldpXMedOptLocationGroup
1283DESCRIPTION
1284"This group represents the information associated with
1285the LLDP-MED optional Location TLVs,
1286therefore the agent may not implement them."
1287GROUP lldpXMedOptPoEPSEGroup
1288DESCRIPTION
1289"This group represents the information associated with
1290the LLDP-MED optional extended PoE PolicyTLVs, carrying
1291PSE information, therefore the agent may
1292not implement them."
1293GROUP lldpXMedOptPoEPDGroup
1294DESCRIPTION
1295" This group represents the information associated with
1296the LLDP-MED optional extended PoE Policy TLVs, carrying
1297PD information, therefore the agent may
1298not implement them."
1299::= { lldpXMedCompliances 1 }
1300-- MIB groupings
1301lldpXMedConfigGroup OBJECT-GROUP
1302OBJECTS {
1303lldpXMedPortCapSupported,
1304lldpXMedPortConfigTLVsTxEnable,
1305lldpXMedPortConfigNotifEnable,
1306lldpXMedFastStartRepeatCount,
1307lldpXMedLocXPoEDeviceType,
1308lldpXMedLocDeviceClass
1309}
1310STATUS current
1311DESCRIPTION
1312"The collection of objects which are used to configure or
1313describe the configuration or behavior of the LLDP-MED
1314organizational extension implementation."
1315::= { lldpXMedGroups 1 }
1316lldpXMedOptMediaPolicyGroup OBJECT-GROUP
1317OBJECTS {
1318lldpXMedLocMediaPolicyVlanID,
1319lldpXMedLocMediaPolicyPriority,
1320lldpXMedLocMediaPolicyDscp,
1321lldpXMedLocMediaPolicyUnknown,
1322lldpXMedLocMediaPolicyTagged
1323}
1324STATUS current
1325DESCRIPTION
1326"The collection of objects which are used to represent LLDP
1327MED organizational extensions for Media Policy Information."
1328::= { lldpXMedGroups 2 }
1329lldpXMedOptInventoryGroup OBJECT-GROUP
1330OBJECTS {
1331lldpXMedLocHardwareRev,
1332lldpXMedLocFirmwareRev,
1333lldpXMedLocSoftwareRev,
1334lldpXMedLocSerialNum,
1335lldpXMedLocMfgName,
1336lldpXMedLocModelName,
1337lldpXMedLocAssetID
1338}
1339STATUS current
1340DESCRIPTION
1341"The collection of objects which are used to represent LLDP
1342MED organizational extension for inventory Information."
1343::= { lldpXMedGroups 3 }
1344lldpXMedOptLocationGroup OBJECT-GROUP
1345OBJECTS {
1346lldpXMedLocLocationInfo
1347}
1348STATUS current
1349DESCRIPTION
1350"The collection of objects which are used to represent LLDP
1351MED organizational extension for Location Information."
1352::= { lldpXMedGroups 4 }
1353lldpXMedOptPoEPSEGroup OBJECT-GROUP
1354OBJECTS {
1355lldpXMedLocXPoEPSEPortPowerAv,
1356lldpXMedLocXPoEPSEPortPDPriority,
1357lldpXMedLocXPoEPSEPowerSource
1358}
1359STATUS current
1360DESCRIPTION
1361"The collection of objects which are used to represent LLDP
1362MED organizational extensions for PoE PSE Information."
1363::= { lldpXMedGroups 5 }
1364lldpXMedOptPoEPDGroup OBJECT-GROUP
1365OBJECTS {
1366lldpXMedLocXPoEPDPowerReq,
1367lldpXMedLocXPoEPDPowerSource,
1368lldpXMedLocXPoEPDPowerPriority
1369}
1370STATUS current
1371DESCRIPTION
1372"The collection of objects which are used to represent LLDP
1373MED organizational extensions for PoE PD Information."
1374::= { lldpXMedGroups 6 }
1375lldpXMedRemSysGroup OBJECT-GROUP
1376OBJECTS {
1377lldpXMedRemCapSupported,
1378lldpXMedRemCapCurrent,
1379lldpXMedRemDeviceClass,
1380lldpXMedRemMediaPolicyVlanID,
1381lldpXMedRemMediaPolicyPriority,
1382lldpXMedRemMediaPolicyDscp,
1383lldpXMedRemMediaPolicyUnknown,
1384lldpXMedRemMediaPolicyTagged,
1385lldpXMedRemHardwareRev,
1386lldpXMedRemFirmwareRev,
1387lldpXMedRemSoftwareRev,
1388lldpXMedRemSerialNum,
1389lldpXMedRemMfgName,
1390lldpXMedRemModelName,
1391lldpXMedRemAssetID,
1392lldpXMedRemLocationInfo,
1393lldpXMedRemXPoEDeviceType,
1394lldpXMedRemXPoEPSEPowerAv,
1395lldpXMedRemXPoEPSEPowerSource,
1396lldpXMedRemXPoEPSEPowerPriority,
1397lldpXMedRemXPoEPDPowerReq,
1398lldpXMedRemXPoEPDPowerSource,
1399lldpXMedRemXPoEPDPowerPriority
1400}
1401STATUS current
1402DESCRIPTION
1403"The collection of objects which are used to represent LLDPMED
1404organizational extension Remote Device Information."
1405::= { lldpXMedGroups 7 }
1406lldpXMedNotificationsGroup NOTIFICATION-GROUP
1407NOTIFICATIONS { lldpXMedTopologyChangeDetected }
1408STATUS current
1409DESCRIPTION
1410"Notifications sent by an LLDP-MED agent."
1411::= { lldpXMedGroups 8 }
1412END