Internet Draft Avi Berger PowerDsine Inc. Dan Romascanu AvayaInc. 19 December 200221 May 2003 Power Ethernet(DTE Power via MDI)MIB<draft-ietf-hubmib-power-ethernet-mib-04.txt><draft-ietf-hubmib-power-ethernet-mib-05.txt> Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." To view the list Internet-Draft Shadow Directories, see http://www.ietf.org/shadow.html. Copyright Notice Copyright (C) The Internet Society(2002).(2003). All Rights Reserved. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. The document proposes an extension to the Ethernet-like Interfaces MIB[RFC2665]with a set of objects for managing apower Ethernet Powered Device (PD) and/orPower Source Equipment (PSE). Distribution of this memo is unlimited. Table of Contents Status of this Memo 1 Abstract 1 1 Introduction 2 2 TheSNMPInternet-Standard Management Framework 2 3 Overview32 4 MIB Structure43 5Evolution of the Document, Limitations and Future Work 4Definitions 3 6Changes log 4Acknowledgements 17 7Definitions 10 8Normative References24 917 8 Informative References25 1018 9 Intellectual Property26 1118 10 Security Considerations27 1218 11 Authors Addresses2720 A Full Copyright Statement2820 B Evolution of the Document, Limitations and Future Work 21 C Changes log 21 1. Introduction This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a set of MIB objects to manage a Power Ethernet(DTE Power via MDI)Powered Device (PD) and/or power[IEEE-802.3af] Source Equipment (PSE). The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in[RFC2863].[RFC2119]. 2. TheSNMP Management Framework The SNMPInternet-Standard Management Frameworkpresently consists of five major components: o An overall architecture, described in RFC 2571 [RFC2571]. o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, called SMIv2, is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [RFC1157]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [RFC1905]. o A setFor a detailed overview offundamental applications described in RFC 2573 [RFC2573] andtheview-based access control mechanism described in RFC 2575 [RFC2575]. A more detailed introduction todocuments that describe the currentSNMPInternet-Standard ManagementFramework can be found inFramework, please refer to section 7 of RFC2570 [RFC2570].3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in theSMI.Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to theSMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translationSMIv2, which ispossible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptionsdescribed inSMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB.STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 3. Overview The emergence of IP telephony as an application that allows for voice applications to be run over the same infrastructure as data applications led to the emergence of Ethernet IP phones, with similar functions and characteristics as the traditional phones. Powering a phone is one of these functions that are being taken as granted. The IEEE 802.3 Working Group initiated a standard work on this subject, currently known as the IEEE 802.3af work [IEEE-802.3af]. The IEEE 802.3af WG will not define a full management interface, but only the hardware registers that will allow for a management interfaces to be built for a powered Ethernet device. The MIB module defined in this document extends the Ethernet-like Interfaces MIB [RFC2665] with the management objects required for the management of the powered Ethernet devices and ports. The following abbreviations are defined in [IEEE-802.3af] and will be used with the same significance in this document: PSE - Power Sourcing Equipment; PD - Powered Device 4. MIB Structure This MIB objects are included infour MIB groups -threeof them includeMIBtables, and the fourth scalar objectsgroups. The pethPsePortTable defines the objects used for the configuration and describing the status of ports on a PSE device. Examples of PSE devices are Ethernet switches that support power Ethernet and mid- span boxes. ThepethPdPortTable defines the objects used for the configuration and describing the status of ports on a PD device. Examples of PD devices are Ethernet phones. ThepethMainPseObjects MIB group defines the management objects for a managed main power source in a PSE device. Ethernet switches are one example of boxes that would support these objects. ThepethTrapsControlTablepethNotificationsControlTable includes objects that control thetransmissionTransmission oftrapsnotifications by the agent to a management application. 5.Evolution of the Document, LimitationsDefinitions POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, mib-2, OBJECT-TYPE, Integer32, Gauge32, Counter32, NOTIFICATION-TYPE FROM SNMPv2-SMI TruthValue FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF; powerEthernetMIB MODULE-IDENTITY LAST-UPDATED "200304250000Z" -- April 25, 2003 ORGANIZATION "IETF Ethernet Interfaces andFuture Work TheHub MIB Working Group" CONTACT-INFO " WG Charter: http://www.ietf.org/html.charters/hubmib-charter.html Mailing lists: General Discussion: hubmib@ietf.org To Subscribe: hubmib-requests@ietf.org In Body: subscribe your_email_address Chair: Dan Romascanu Avaya Tel: +972-3-645-8414 Email: dromasca@avaya.com Editor: Avi Berger PowerDsine Inc. Tel: 972-9-7755100 Ext 307 Fax: 972-9-7755120 E-mail: avib@PowerDsine.com " DESCRIPTION "The MIB module for managing Power Source Equipment (PSE) working according to the IEEE802.3af is at this stage work in progress.802.af Powered Ethernet (DTE Power via MDI) standard. Thescope offollowing terms are used throughout thisdocument is to doMIB module. For complete formal definitions, the IEEE 802.3 standardswork in the IETF in parallel withshould be consulted wherever possible: Group - A recommended, but optional, entity defined by the IEEEstandardization activity,802.3 management standard, in order toallow for the publication ofsupport astandard track document containingmodular numbering scheme. The classical example allows anSNMP MIB simultaneously or closeimplementor tothe date of the publicationrepresent field-replaceable units as groups of ports, with theIEEE revised standard. It is possible that changes may be brought toport numbering matching theIEEE proposal, andmodular hardware implementation. Port - This entity identifies theEthernet MIB Working Group will work in order to ensure consistency betweenport within thetwo standards proposals. 6. Changes Loggroup for which this entry contains information. Thefollowing changes were introduced relative to the first proposalnumbering scheme fora Power Ethernet MIB [PWR-MIB] a. pethPsePortTable has to index pethPsePortGroupIndex & pethPsePortIndex b. pethPsePortIndex INTEGER instead of InterfaceIndex c. Name change pethPsePortStatus instedports is implementation specific. Copyright (c) The Internet Society (2003). This version ofpethPsePortFaultError d. Name change pethPsePortStatusClear insteadthis MIB module is part ofpethPsePortFaultErrorClear e. DESCRIPTION updateRFC yyyy; See the RFC itself forpethPsePortPowerDetectionStatus test(3) f.full legal notices. -- RFC Ed.: replace yyyy with the actual RFC number & remove this notice. " REVISION "200305210000Z" -- May 21, 2003 DESCRIPTIONupdate pethPsePortDetectionOperStatus off(2) g. Adding to pethPsePortStatus one more item both(4) h. Adding pethMainPseTable"Initial version, published as RFC yyyy." -- RFC Ed.: replace yyyy witha pethMainPseGroupIndex i. Deletting to objects pethMainPseMaxVoltageactual RFC number &pethMainPseMinVoltage j. Change SYNTAX of pethMainPseUsagePower form INTEGER to Gauge32 k. Changeremove this notice ::= { mib-2 XXX } -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 0 } pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 } pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 2 } -- PSE Objects pethPsePortTable OBJECT-TYPE SYNTAX SEQUENCE OF PethPsePortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table ofpethMainPseUsageCurrent form INTEGER to Gauge32 l. Adding pethMainPseBackupActivated & pethMainPseBackupPresent m. Adding Traps Control Objects n. Adding Notifications Section (5 notifications ) o. Adding pethTrapsControlGroup to Conformance Section p. Adding pethPsePortPowerClassifications to pethPsePortTable Class 1-5 q. Adding pethPsePortPowerClassifications to pethPsePortGroup r. Changeobjects that display and control the power characteristics power Ethernet ports on a Power Source Entity (PSE) device. This group will be implemented inpethPsePortStatus none(1) to ok(1) s. Changemanaged power Ethernet switches and mid-span devices. Values of all read-write objects in this table are persistent at restart/reboot." ::= { pethObjects 1 } pethPsePortEntry OBJECT-TYPE SYNTAX PethPsePortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set ofpethMainPseUsagePower from mW to Watt t. Change pethMainPseUsagePower to pethMainPseConsumptionPower u. Delete of pethMainPseUsageCurrent The following changes were introduced between draft-ietf-hubmib- power-ethernet-mib-00.txtobjects that display anddraft-ietf-hubmib-power-ethernet- mib-01.txt: 1. change pethMainPowerUsageTrap to pethMainPowerUsageOnTrap 2. add pethMainPowerUsageOffTrap 3. change pethMainPowerTrapGroup 4. change pethPsePorPowerEnable tocontrol the power characteristics of a power Ethernet PSE port." INDEX { pethPsePortGroupIndex , pethPsePortIndex } ::= { pethPsePortTable 1 } PethPsePortEntry ::= SEQUENCE { pethPsePortGroupIndex Integer32, pethPsePortIndex Integer32, pethPsePortAdminEnable5. pethPsePortPowerIdPairsControl toTruthValue, pethPsePortPowerPairsControlAbility6. pethPsePortPowerIdPairs to pethPsePortPowerPairs 7. delete both fromTruthValue, pethPsePortPowerPairsobject 8. change pethPsePortPowerDetectionStatus to pethPsePortPowerDetectionControl 9. delete from pethPsePortPowerDetectionControl off , and change test to 2 10. change pethPsePortDetectionOperStatus to pethPsePortDetectionStatus 11. changeINTEGER, pethPsePortDetectionStatusto: disabled(1), searching(2), detected(3), deliveringPower(4), fault(5), invalidPD(6), test(7), denyLowPriority(8) 12. change description forINTEGER, pethPsePortPowerPriority INTEGER, pethPsePortMPSAbsentCounter Counter32, pethPsePortInvalidSignatureCounter Counter32, pethPsePortPowerDeniedCounter Counter32, pethPsePortOverLoadCounter Counter32, pethPsePortShortCounter Counter32, pethPsePortType INTEGER, pethPsePortPowerClassifications13. change pethPsePortStatusINTEGER } pethPsePortGroupIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This variable uniquely identifies the group containing the port topethPsePortCurrentStatus 14. Update description for pethPsePortCurrentStatus 15. change pethPsePortStatusClear to pethPsePortCurrentStatusClear 16. change pethPdPortDetectionOperStatus to pethPdPortDetectionStatus 17. change in description of pethPdPortPowerPairs 18. changewhich a power Ethernet PSE is connected. Group means box inpethPdPortDetectionStatus description 19. delete pethPdPortPowerClassifications object 20. changethe stack, module inpethPsePortGroup 21. changea rack and the value 1 MUST be used for non-modular devices. Furthermore, the same value MUST be used inpethPdPortGroup 22. change pethPsePortOnOffTrap with pethPsePortDetectionStatus object 23. change pethPsePortStatusTrap to pethPsePortCurrentStatusTrap 24. change pethPsePortTrapGroup The following changes were introduced between draft-ietf-hubmib- power-ethernet-mib-01.txtthis variable, pethMainPseGroupIndex, anddraft-ietf-hubmib-power-ethernet- mib-02.txt: 1. change pethMainPsePower SYNTAX Integer32 (0..65535)pethNotificationControlGroupIndex to(1..65535) 2. change pethTrapsControlGroupIndexrefer to a given box in a stack or module in the rack." ::= { pethPsePortEntry 1 } pethPsePortIndex OBJECT-TYPE SYNTAX Integer32(0..65535) to (1..65535) 3. change int pethMainPseBackUpActivatedTrap pethPsePortGroupIndex to pethMainPseGroupIndex 4. change int pethMainPowerUsageOnTrap pethPsePortGroupIndex to pethMainPseGroupIndex 5. change int pethMainPowerUsageOffTrap(1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This variable uniquely identifies the power Ethernet PSE port within group pethPsePortGroupIndex topethMainPseGroupIndex 6. change pethMainPseGroupIndexwhich the power Ethernet PSE entry is connected." ::= { pethPsePortEntry 2 } pethPsePortAdminEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "true (1) An interface which can provide the PSE functions. false(2) The interface will act as it would if it had no PSE function." REFERENCE "IEEE Draft P802.3af/D4.3 Section 30.9.1.1.2 aPSEAdminState" ::= { pethPsePortEntry 3 } pethPsePortPowerPairsControlAbility OBJECT-TYPE SYNTAX TruthValue MAX-ACCESStoread-onlyupdates from IEEESTATUS current DESCRIPTION "Describes the capability of controlling the power pairs functionality to switch pins for sourcing power. The value true indicate that the device has the capability to control the power pairs. When false the PSE Pinout Alternative used cannot be controlled through the PethPsePortAdminEnabe attribute." REFERENCE "IEEE DraftP802.3af/D3.1, June 5, 2002 7. remove from pethPsePortPowerClassifications class5 8. remove from pethPsePortCurrentStatus both(4) and description 9. add pethPsePortUnderCurrentCounter object 10. add pethPsePortOverCurrentCounter object 11. remove pethPsePortCurrentStatusClear object 12. change pethPsePortType OID to end with 13 13. change pethPsePortPowerClassifications OID to end with 14 14. update pethPsePortGroup OBJECT-GROUP 15. chage reference to new IEEE Draft 16. change pethPdCompliance description. The following changes were introduced between draft-ietf-hubmib- power-ethernet-mib-02.txt and draft-ietf-hubmib-power-ethernet- mib-03.txt: 1. remove pethPsePortGroupIndex and pethPsePortIndex from pethPsePortOnOffTrap and pethPsePortCurrentStatusTrap 2. change pethPsePortGroupIndex and pethPsePortIndex MAX-ACCESS to not-accessible 3. remove pethMainPseGroupIndex from pethMainPseBackUpActivatedTrap 4. replace pethMainPseGroupIndex with pethMainPseConsumptionPower in pethMainPowerUsageOnTrap and pethMainPowerUsageOffTrap 5. change pethMainPseGroupIndex MAX-ACCESS to not-accessible 6. move pethPsePortTrapGroup NOTIFICATION-GROUP and pethMainPowerTrapGroup NOTIFICATION-GROUP to the Conformance Section 7. update the discription of pethPsePortOnOffTrap 8. add pethPsePortPowerDetectionControl to pethPsePortGroup 9. change reference to IEEE Draft P802.3af/D3.3 October 2002 10. delete enumaration pethPsePortDetectionStatus detected(3) and invalidPD(6) 11. change pethPsePortCurrentStatus to pethPsePortPowerMaintenanceStatus 12 . change pethPsePortUnderCurrentCounter to pethPsePortMPSAbsentCounter 13. add pethPdPortAdminEnable object. 14. replace Trap with Notification. 15. update pethPsePortOnOffNotification description. 16. update pethPsePortDetectionStatus description. 17. remove pethPdPortPowerPairs object. 18. remove pethPdPortDetectionStatus object. 19. remove pethPdPortType object. 20. change pethPdPortAdminEnable OID. The following changes were introduced between draft-ietf-hubmib- power-ethernet-mib-03.txt and draft-ietf-hubmib-power-ethernet- mib-04.txt: 1. remove pethMainPseMaximumDcPower object 2. remove pethMainPseBackupPresent object 3. remove pethMainPseBackupActivated object. 4. remove pethMainPseBackUpActivatedNotification 5. change reference from IEEE Draft P802.3af/D3.3, October, 2002 to IEEE Draft P802.3af/D4.0, November, 2002 6. DESCRIPTION "Initial version, published as RFC yyyy." 7. change the syntax of pethPsePortGroupIndex from INTEGER (1..2147483647) to Integer32 (1..2147483647). 8. change the syntax of pethPsePortIndex from INTEGER (1..2147483647) to Integer32 (1..2147483647). 9.change the syntax of pethPdPortIndex from INTEGER (0..65535) to InterfaceIndex. 10.import InterfaceIndex from IF-MIB. 11. change the syntax of pethMainPseGroupIndex from INTEGER (0..65535) to Integer32 (1..2147483647) 12. change the syntax of pethMainPseUsageThreshold from INTEGER (1..99) to Integer32 (1..99). 13. change the syntax of pethNotificationControlGroupIndex from INTEGER (1..65535) to Integer32 (1..2147483647) 14. replace OID: ! pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 0 } ! pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 } ! pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 2 } 15. change the discription of the pethPsePortGroup and pethPdPortGroup 16. pethMainPsePower changed to Gauge32 17. add: REVISION "200212020000Z" -- December 02, 2002 DESCRIPTION "Initial version, published as RFC yyyy." 18 change the MIB registered from { dot3 20 } ::= { mib-2 XXX } -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice 7. Definitions POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, mib-2, OBJECT-TYPE, Integer32, Gauge32, Counter32, NOTIFICATION-TYPE FROM SNMPv2-SMI TruthValue FROM SNMPv2-TC InterfaceIndex FROM IF-MIB MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF; powerEthernetMIB MODULE-IDENTITY LAST-UPDATED "200212020000Z" -- December 02, 2002 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" CONTACT-INFO " Chair: Dan Romascanu Avaya Inc. Tel: +972-3-645-8414 Email: dromasca@avaya.com Editor: Avi Berger PowerDsine Inc. Tel: 972-9-7755100 Ext 307 Fax: 972-9-7755120 E-mail: avib@PowerDsine.com " DESCRIPTION "The MIB module for for managing Powered Devices (PD) or Power Source Equipment (PSE) working according to the IEEE 802.af Powered Ethernet (DTE Power via MDI) standard. The following terms are used throughout this MIB module. For complete formal definitions, the IEEE 802.3 standards should be consulted wherever possible: Group - A recommended, but optional, entity defined by the IEEE 802.3 management standard, in order to support a modular numbering scheme. The classical example allows an implementor to represent field-replaceable units as groups of ports, with the port numbering matching the modular hardware implementation. Port - This entity identifies the port within the group for which this entry contains information. The numbering scheme for ports is implementation specific." REVISION "200212020000Z" -- December 02, 2002 DESCRIPTION "Initial version, published as RFC yyyy." -- RFC Ed.: replace yyyy with actual RFC number & remove this notice ::= { mib-2 XXX } -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 0 } pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 } pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 2 } -- PSE Objects pethPsePortTable OBJECT-TYPE SYNTAX SEQUENCE OF PethPsePortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of objects that display and control the power characteristics power Ethernet ports on a Power Source Entity (PSE) device. This group will be implemented in managed power Ethernet switches and mid-span devices." ::= { pethObjects 1 } pethPsePortEntry OBJECT-TYPE SYNTAX PethPsePortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of objects that display and control the power characteristics of a power Ethernet PSE port." INDEX { pethPsePortGroupIndex , pethPsePortIndex } ::= { pethPsePortTable 1 } PethPsePortEntry ::= SEQUENCE { pethPsePortGroupIndex Integer32, pethPsePortIndex Integer32, pethPsePortAdminEnable INTEGER, pethPsePortPowerPairsControlAbility TruthValue, pethPsePortPowerPairs INTEGER, pethPsePortPowerDetectionControl INTEGER, pethPsePortDetectionStatus INTEGER, pethPsePortPowerPriority INTEGER, pethPsePortPowerMaintenanceStatus INTEGER, pethPsePortMPSAbsentCounter Counter32, pethPsePortOverCurrentCounter Counter32, pethPsePortType INTEGER, pethPsePortPowerClassifications INTEGER } pethPsePortGroupIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This variable uniquely identifies the group containing the port to which a power Ethernet PSE is connected. Group means box in the stack, module in a rack and the value 1 MUST be used for non-modular devices . pethPseMidSpanGroupCapacity is the number of Mid-Span PSE groups that can be contained within the Mid-Span PSE." ::= { pethPsePortEntry 1 } pethPsePortIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This variable uniquely identifies the power Ethernet PSE port within group pethPseGroupIndex to which the power Ethernet PSE entry is connected." ::= { pethPsePortEntry 2 } pethPsePortAdminEnable OBJECT-TYPE SYNTAX INTEGER { enable(1), disable(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Enables power supply on this port. Setting this object at a value enable(1) enables power and detection mechanism for this port. Setting this object at a value disable(2) disables power for this port." ::= { pethPsePortEntry 3 } pethPsePortPowerPairsControlAbility OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "Describes the capability of controlling the power pairs functionality to switch pins for sourcing power. The value true indicate that the device has the capability to control the power pairs"P802.3af/D4.3 Section 30.9.1.1.3 aPSEPowerPairsControlAbility" ::= { pethPsePortEntry 4 } pethPsePortPowerPairs OBJECT-TYPE SYNTAX INTEGER { signal(1), spare(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Describes or controls the pairs in use. If the value of pethPsePortPowerPairsControl is true, this object is writable. A value of signal(1)meansmenas that the signal pairs only are in use. A value of spare(2) means that the spare pairs only are in use." REFERENCE "IEEE Draft P802.3af/D4.3 Section 30.9.1.1.4 aPSEPowerPairs" ::= { pethPsePortEntry 5 }pethPsePortPowerDetectionControl OBJECT-TYPE SYNTAX INTEGER { auto(1), test(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Controls the power detection mechanism of the port. Setting the value auto(1) enables the power detection mechanism of the port. Setting the value test(2) puts the port in a testmode: force continuous discovery without applying power regardless of whether PD detected." ::= { pethPsePortEntry 6 }pethPsePortDetectionStatus OBJECT-TYPE SYNTAX INTEGER { disabled(1), searching(2),deliveringPower(4), fault(5), test(7), denyLowPriority(8)deliveringPower(3), fault(4), test(5), otherFault(6) } MAX-ACCESS read-only STATUS current DESCRIPTION "Describes the operational status of the port PD detection. A value of disabled(1)- indicates that the PSE State diagram is in the stateIDLEDISABLED. A value ofsearching(2)-deliveringPower(3) - indicates that the PSE State diagram is in the stateDETECTION, CLASSIFICATION, SIGNATURE_INVALID or BACKOFF.POWER_ON for a duration greater than tlim max (see IEEE Drafts P802.3af/D4.3 Table 33-5 tlim). A value ofdeliveringPower(4)fault(4) - indicates that the PSE State diagram is in the statePOWER_UP, POWER_ON or POWER_OFF.TEST_ERROR. A value offault(5)test(5) - indicates that the PSE State diagram is in the stateTEST_ERROR or the state IDLE due to the variable error condition. Faults detected are vendor specific.TEST_MODE. A value oftest(7)otherFault(6) - indicates that the PSE State diagram is in the stateTEST_MODE.IDLE due to the variable error_conditions. A value ofdenyLowPriority(8)searching(2)- indicatesthat the port was disabled bythepower management system,PSE State diagram is inorder to keep active higher priority ports. "a state other than those listed above." REFERENCE "IEEE Draft P802.3af/D4.3 Section 30.9.1.1.5 aPSEPowerDetectionStatus" ::= { pethPsePortEntry 7 } pethPsePortPowerPriority OBJECT-TYPE SYNTAX INTEGER { critical(1), high(2), low(3) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object controls the priority of the port from the point of view of a power management algorithm. The priority that is set by this variable could be used by a control mechanism that prevents over current situations by disconnecting first ports with lower power priority. Ports that connect devices critical to the operation of the network - like the E911 telephones ports - should be set to higher priority." ::= { pethPsePortEntry 8 }pethPsePortPowerMaintenanceStatuspethPsePortMPSAbsentCounter OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This counter is incremented when the PSE state diagram transitions directly from the state POWER_ON to the state IDLE due to tmpdo_timer_done being asserted." REFERENCE "IEEE Draft P802.3af/D4.3 Section 30.9.1.1.11 aPSEMPSAbsentCounter" ::= { pethPsePortEntry 11 } pethPsePortType OBJECT-TYPE SYNTAX INTEGER {ok(1), underCurrent(2), mPSAbsent(3)other(1), telephone(2), webcam(3), wireless(4) } MAX-ACCESSread-onlyread-write STATUS current DESCRIPTION"The"A manager will set the valueok(1) indicatesof this variable to indicate thePower Maintenance Signaturetype of powered device that ispresent andconnected to theovercurrent condition has not been detected. The value overCurrent (2) indicates an overcurrent condition has been detected.port." ::= { pethPsePortEntry 13 } pethPsePortPowerClassifications OBJECT-TYPE SYNTAX INTEGER { class0(1), class1(2), class2(3), class3(4), class4(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "Classification is a way to tag different terminals on the Power over LAN network according to their power consumption. Devices such as IP telephones, WLAN access points and others, will be classified according to their power requirements. Thevalue mPSAbsent(3) indicatesmeaning of the classification labels is defined in the IEEE specification. This variable is valid only while a PD is being powered, that is, while thePower Maintenance Signatureattribute pethPsePortDetectionStatus is reporting the enumeration deliveringPower." REFERENCE "IEEE Draft P802.3af/D4.3 Section 30.9.1.1.6 aPSEPowerClassification" ::= { pethPsePortEntry 14 } pethPsePortInvalidSignatureCounter OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This counter is incremented when the PSE state diagram enters the state SIGNATURE_INVALID." REFERENCE "IEEE Draft P802.3af/D4.3 Section 30.9.1.1.7 aPSEInvalidSignatureCounter" ::= { pethPsePortEntry 15 } pethPsePortPowerDeniedCounter OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This counter is incremented when the PSE state diagram enters the state POWER_DENIED." REFERENCE "IEEE Draft P802.3af/D4.3 Section 30.9.1.1.8 aPSEPowerDeniedCounter" ::= { pethPsePortEntry 16 } pethPsePortOverLoadCounter OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "This counter isabsent."incremented when the PSE state diagram enters the state ERROR_DELAY_OVER." REFERENCE"[IEEE"IEEE DraftP802.3af/D4.0, November, 2002, 30.9.1.1.8 aPSEPowerMaintenanceStatus]"P802.3af/D4.3 Section 30.9.1.1.9 aPSEOverLoadCounter" ::= { pethPsePortEntry1017 }pethPsePortMPSAbsentCounterpethPsePortShortCounter OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION"Counts the number of times that"This counter is incremented when thepethPsePortPowerMaintenanceStatus attribute changes from any value toPSE state diagram enters thevalue mPSAbsent(3)."state ERROR_DELAY_SHORT." REFERENCE"[IEEE"IEEE DraftP802.3af/D4.0, November, 2002, object 30.9.1.1.9 aPSEUnderCurrentCounter]"P802.3af/D4.3 Section 30.9.1.1.10 aPSEShortCounter" ::= { pethPsePortEntry1118 }pethPsePortOverCurrentCounter-- Main PSE Objects pethMainPseObjects OBJECT IDENTIFIER ::= { pethObjects 3 } pethMainPseTable OBJECT-TYPE SYNTAXCounter32SEQUENCE OF PethMainPseEntry MAX-ACCESSread-onlynot-accessible STATUS current DESCRIPTION"Counts the number"A table oftimesobjects that display and control attributes of theaPSEPowerCurrentStatus attribute changes from any value to the value overCurrent(2)." REFERENCE "[IEEE Draft P802.3af/D4.0, November, 2002, object 30.9.1.1.1 aPSEOverCurrentCounter]"main power source in a PSE device. Ethernet switches are one example of boxes that would support these objects. Values of all read-write objects in this table are persistent at restart/reboot." ::= {pethPsePortEntry 12pethMainPseObjects 1 }pethPsePortTypepethMainPseEntry OBJECT-TYPE SYNTAXINTEGER { other(1), telephone(2), webcam(3), wireless(4) }PethMainPseEntry MAX-ACCESSread-writenot-accessible STATUS current DESCRIPTION "Amanager willsetthe value of this variable to a value that indicates the typeofthe deviceobjects thatis connected to theport. This value can be the result of the mappingdisplay and control theaddressMain power of a PSE. " INDEX { pethMainPseGroupIndex } ::= { pethMainPseTable 1 } PethMainPseEntry ::= SEQUENCE { pethMainPseGroupIndex Integer32, pethMainPsePower Gauge32 , pethMainPseOperStatus INTEGER, pethMainPseConsumptionPower Gauge32, pethMainPseUsageThreshold Integer32 } pethMainPseGroupIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This variable uniquely identifies thestation connectedgroup to which power Ethernet PSE is connected. Group means (box in theportstack, module in a rack) andofthe valueof1 MUST be used for non-modular devices. Furthermore, thepethPdPortTypesame value MUST be used in this variable, pethPsePortGroupIndex, and pethNotificationControlGroupIndex to refer to a given box in a stack or module in a rack." ::= { pethMainPseEntry 1 } pethMainPsePower OBJECT-TYPE SYNTAX Gauge32 (1..65535) UNITS "Watts" MAX-ACCESS read-only STATUS current DESCRIPTION "The nominal power of therespective PD port."PSE expressed in Watts." ::= {pethPsePortEntry 13pethMainPseEntry 2 }pethPsePortPowerClassificationspethMainPseOperStatus OBJECT-TYPE SYNTAX INTEGER {class0(1), class1(2), class2(3), class3(4), class4(5)on(1), off(2), faulty(3) } MAX-ACCESS read-only STATUS current DESCRIPTION"Classification is a way to tag different terminals on"The operational status of thePower over LAN network according to their power consumption. Devices such as IP telephones, WLAN access points and others, will be classified according to theirmain PSE." ::= { pethMainPseEntry 3 } pethMainPseConsumptionPower OBJECT-TYPE SYNTAX Gauge32 UNITS "Watts" MAX-ACCESS read-only STATUS current DESCRIPTION "Measured usage powerrequirements. The value is only valid while a valid PD is being detected as indicated byexpressed in Watts." ::= { pethMainPseEntry 4 } pethMainPseUsageThreshold OBJECT-TYPE SYNTAX Integer32 (1..99) UNITS "%" MAX-ACCESS read-write STATUS current DESCRIPTION "The usage threshold expressed in percents for comparing theattribute pethPsePortDetectionStatus reportingmeasured power and initiating an alarm if thevalue or deliveringPower(4)." REFERENCE "[IEEE Draft P802.3af/D4.0, November, 2002, object 30.9.1.1.7 aPSEPowerClassification]"threshold is exceeded." ::= {pethPsePortEntry 14pethMainPseEntry 7 } --PD Port table pethPdPortTableNotification Control Objects pethNotificationControl OBJECT IDENTIFIER ::= { pethObjects 4 } pethNotificationControlTable OBJECT-TYPE SYNTAX SEQUENCE OFPethPdPortEntryPethNotificationControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of objects that display and control thepower characteristics power Ethernet portsNotification on aPowered Device(PD)PSE device.This group willValues of all read-write objects in this table are persistent at restart/reboot." ::= { pethNotificationControl 1 } pethNotificationControlEntry OBJECT-TYPE SYNTAX PethNotificationControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of objects that control the Notification events." INDEX { pethNotificationControlGroupIndex } ::= { pethNotificationControlTable 1 } PethNotificationControlEntry ::= SEQUENCE { pethNotificationControlGroupIndex Integer32, pethNotificationControlEnable TruthValue } pethNotificationControlGroupIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This variable uniquely identifies the group. Group means box in the stack, module in a rack and the value 1 MUST beimplementedused for non-modular devices. Furthermore, the same value MUST be used inmanaged poweredthis variable, pethPsePortGroupIndex, andmid-span devices."pethMainPseGroupIndex to refer to a given box in a stack or module in a rack. " ::= {pethObjects 2pethNotificationControlEntry 1 }pethPdPortEntrypethNotificationControlEnable OBJECT-TYPE SYNTAXPethPdPortEntryTruthValue MAX-ACCESSnot-accessibleread-write STATUS current DESCRIPTION"A set of objects"This object controls, on a per-group basis, whether or not notifications from the agent are enabled. The value true(1) means thatdisplay and controlnotifications are enabled; thepower characteristics of a Powered Device port." INDEX { pethPdPortIndex }value false(2) means that they are not." ::= {pethPdPortTable 1pethNotificationControlEntry 2 }PethPdPortEntry ::= SEQUENCE-- -- Notifications Section -- -- pethPsePortOnOffNotification NOTIFICATION-TYPE OBJECTS {pethPdPortIndex InterfaceIndex, pethPdPortAdminEnable INTEGERpethPsePortDetectionStatus }pethPdPortIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS not-accessibleSTATUS current DESCRIPTION"An index value that uniquely identifies an interface to a PD device. The interface identified by a particular value of this index" This Notification indicates if Pse Port is delivering or not power to thesame interface as identified byPD. This Notification SHOULD be sent on every status change except in thesame value of ifIndex. The mappingsearching mode. At least 500 msec must elapse between notifications being emitted by theifIndex values and the numbering of the port on the device is an implementation issue."same object instance." ::= {pethPdPortEntrypethNotifications 1 }pethPdPortAdminEnable OBJECT-TYPE SYNTAX INTEGERpethMainPowerUsageOnNotification NOTIFICATION-TYPE OBJECTS {enable(1), disable(2)pethMainPseConsumptionPower }MAX-ACCESS read-writeSTATUS current DESCRIPTION"This value identifies" This Notification indicate PSE Threshold usage indication is on, theoperational state ofusage power is above thePD functions. An interface which can providethreshold. At least 500 msec must elapse between notifications being emitted by thePD functions will be enabled to do so when this attribute hassame object instance." ::= { pethNotifications 4 } pethMainPowerUsageOffNotification NOTIFICATION-TYPE OBJECTS { pethMainPseConsumptionPower } STATUS current DESCRIPTION " This Notification indicates PSE Threshold usage indication off, thevalue enable. When this attribute hasusage power is below thevalue disablethreshold. At least 500 msec must elapse between notifications being emitted by theinterface will act as it would if it had no PD function."same object instance." ::= {pethPdPortEntry 2pethNotifications 5 } --Main PSE Objects pethMainPseObjects-- Conformance Section -- pethCompliances OBJECT IDENTIFIER ::= {pethObjects 3pethConformance 1 }pethMainPseTable OBJECT-TYPE SYNTAX SEQUENCE OF PethMainPseEntry MAX-ACCESS not-accessiblepethGroups OBJECT IDENTIFIER ::= { pethConformance 2 } pethCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION"A table of objects that display and control"Describes theMain power on a PSE device. Example - an Ethernet switch midspan device can control an Ethnternet port andrequirements for conformance to theMainPowersupply unit's." ::=Ethernet MIB." MODULE -- this module MANDATORY-GROUPS {pethMainPseObjects 1pethPsePortGroup, pethPsePortNotificationGroup, pethNotificationControlGroup }pethMainPseEntry OBJECT-TYPE SYNTAX PethMainPseEntry MAX-ACCESS not-accessible STATUS currentGROUP pethMainPseGroup DESCRIPTION"A set of objects"The pethMainPseGroup is mandatory for PSE systems thatdisplay and control the Mainimplement a main powerofsupply." GROUP pethMainPowerNotificationGroup DESCRIPTION "The pethMainPowerNotificationGroup is mandatory for PSE systems that implement aPSE. " INDEX { pethMainPseGroupIndex }main power supply." ::= {pethMainPseTablepethCompliances 1 }PethMainPseEntry ::= SEQUENCE { pethMainPseGroupIndex Integer32, pethMainPsePower Gauge32 , pethMainPseOperStatus INTEGER, pethMainPseConsumptionPower Gauge32, pethMainPseUsageThreshold Integer32 } pethMainPseGroupIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessiblepethPseCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION"This variable uniquely identifies"Describes thegrouprequirements for conformance towhich power Ethernet PSE is connected.Group means (box inthestack, module in a rack)PSE andthe value 1 MUST be used for non-modular devices "MID-Span." MODULE -- this module MANDATORY-GROUPS {pethPsePortGroup, pethMainPseGroup,pethNotificationControlGroup, pethPsePortNotificationGroup,pethMainPowerNotificationGroup} ::= {pethMainPseEntrypethCompliances 2 } pethPsePortGroup OBJECT-GROUP OBJECTS { pethPsePortAdminEnable, pethPsePortPowerPairsControlAbility, pethPsePortPowerPairs, pethPsePortDetectionStatus, pethPsePortPowerPriority, pethPsePortMPSAbsentCounter, pethPsePortInvalidSignatureCounter, pethPsePortPowerDeniedCounter, pethPsePortOverLoadCounter, pethPsePortShortCounter, pethPsePortType, pethPsePortPowerClassifications } STATUS current DESCRIPTION "PSE Port objects." ::= { pethGroups 1 }pethMainPsePower OBJECT-TYPE SYNTAX Gauge32 (1..65535) UNITS "Watts" MAX-ACCESS read-onlypethMainPseGroup OBJECT-GROUP OBJECTS { pethMainPsePower, pethMainPseOperStatus, pethMainPseConsumptionPower, pethMainPseUsageThreshold } STATUS current DESCRIPTION"The nominal power of the"Main PSEexpressed in Watts."Objects. " ::= {pethMainPseEntry 2pethGroups 3 }pethMainPseOperStatus OBJECT-TYPE SYNTAX INTEGERpethNotificationControlGroup OBJECT-GROUP OBJECTS {on(1), off(2), faulty(3)pethNotificationControlEnable }MAX-ACCESS read-onlySTATUS current DESCRIPTION"The operational status of the main PSE.""Notification Control Objects. " ::= {pethMainPseEntry 3pethGroups 4 }pethMainPseConsumptionPower OBJECT-TYPE SYNTAX Gauge32 UNITS "Watts" MAX-ACCESS read-onlypethPsePortNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { pethPsePortOnOffNotification} STATUS current DESCRIPTION"Measured usage power expressed in Watts.""Pse Port Notifications." ::= {pethMainPseEntrypethCompliances 4 }pethMainPseUsageThreshold OBJECT-TYPE SYNTAX Integer32 (1..99) UNITS "%" MAX-ACCESS read-writepethMainPowerNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { pethMainPowerUsageOnNotification, pethMainPowerUsageOffNotification} STATUS current DESCRIPTION "Main PSE Notifications." ::= { pethCompliances 5 } END 6. Acknowledgements This document is the product of the Ethernet Interfaces and Hub MIB WG. The authors would like to recognize the special contributions of C.M. Heard and David Law. 7. Normative References [RFC2026] Bradner, S., "Theusage threshold expressedInternet Standards Process - Revision 3", BCP 9, RFC 2026, October 1996. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC2119] Bradner, S., "Key words for use inpercentsRFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2665] Flick, J., and J. Johnson, "Definitions of Managed Objects forcomparingthemeasured power and initiating an alarmEthernet-like Interface Types", RFC 2665, August 1999. NOTE - This RFC is under revision by the WG, and may be obsolete by the time of the publication. The RFC editor should replace it with the revised version, if available. [IEEE-802.3af] IEEE 802.3af Working Group, "Data Terminal Equipment (DTE)Power via Media Dependent Interface (MDI)", Draft D4.3, April 2003. NOTE - This normative reference will be replaced with thethreshold is exceeded." ::= { pethMainPseEntry 7 } -- Notification Control Objects pethNotificationControl OBJECT IDENTIFIER ::= { pethObjects 4 } pethNotificationControlTable OBJECT-TYPE SYNTAX SEQUENCE OF PethNotificationControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of objects that displayIEEE 802.3af Standard as soon as the IEEE will ratify it (expected date - July 2003) 8. Informative References [RFC3410] Case, J., Mundy, R., Partain, D. andcontrolB. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002 9.Intellectual Property The IETF takes no position regarding theNotification on a PSE device." ::= { pethNotificationControl 1 } pethNotificationControlEntry OBJECT-TYPE SYNTAX PethNotificationControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A setvalidity or scope ofobjectsany intellectual property or other rights thatcontrolmight be claimed to pertain to theNotification events." INDEX { pethNotificationControlGroupIndex } ::= { pethNotificationControlTable 1 } PethNotificationControlEntry ::= SEQUENCE { pethNotificationControlGroupIndex Integer32, pethNotificationControlEnable INTEGER } pethNotificationControlGroupIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This variable uniquely identifiesimplementation or use of thegroup. Group means boxtechnology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or thestack, module inresult of an attempt made to obtain arack and it is RECOMENDED thatgeneral license or permission for thevalue 1use of such proprietary rights by implementors or users of this specification can beused for non-modular devices " ::= { pethNotificationControlEntry 1 } pethNotificationControlEnable OBJECT-TYPE SYNTAX INTEGER { enable(1), disable(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Enable Notificationobtained fromAgent" ::= { pethNotificationControlEntry 2 } -- -- Notifications Section -- -- pethPsePortOnOffNotification NOTIFICATION-TYPE OBJECTS { pethPsePortDetectionStatus } STATUS current DESCRIPTION " This Notification indicates if Pse Port is deliveringthe IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents ornot powerpatent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address thePD. This Notification SHOULD be sent on every status change except ininformation to thesearching mode." ::= { pethNotifications 1 } pethPsePortPowerMaintenanceStatusNotification NOTIFICATION-TYPE OBJECTS { pethPsePortPowerMaintenanceStatus } STATUS current DESCRIPTION " This Notification indicatesIETF Executive Director. 10. Security Considerations There are aPort Change Status and it SHOULDnumber of management objects defined in this MIB module with a MAX-ACCESS clause of read-write. Such objects may besentconsidered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect onevery status change." ::= { pethNotifications 2 } pethMainPowerUsageOnNotification NOTIFICATION-TYPE OBJECTS { pethMainPseConsumptionPower } STATUS current DESCRIPTION " This Notification indicate PSE Threshold usage indication is on,network operations. Setting theusage power is abovefollowing object to incorrect values can result in improper operation of thethreshold." ::= { pethNotifications 4 } pethMainPowerUsageOffNotification NOTIFICATION-TYPE OBJECTS { pethMainPseConsumptionPower } STATUS current DESCRIPTION " This Notification indicate PSE Threshold usage indication off,PSE, including theusagepossibility that the PD does not receive poweris belowfrom thethreshold." ::= { pethNotifications 5 } -- -- Conformance Section -- pethCompliances OBJECT IDENTIFIER ::= { pethConformance 1 } pethGroups OBJECT IDENTIFIER ::= { pethConformance 2 } pethCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "DescribesPSE port: pethPsePortAdminEnable pethPsePortPowerPairs pethPsePortPowerPriority pethPsePortType Setting therequirements for conformancefollowing objects to incorrect values can result in an excessive number of traps being sent to network management stations: pethMainPseUsageThreshold pethNotificationControlEnable Some of thePower Ethernet MIB." MODULE --readable objects in this MIB moduleGROUP pethPsePortGroup DESCRIPTION "The pethPsePortGroup(i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. These are: pethPsePortPowerPairsControlAbility pethPsePortPowerPriority pethPsePortPowerClassifications It ismandatory for systems which implement PSE ports." GROUP pethPdPortGroup DESCRIPTION "The pethPdPortGroupthus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt their values when sending them over the network via SNMP. SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself ismandatory for systems which implement PD Ports." GROUP pethMainPseGroup DESCRIPTION "The pethMainPseGroupsecure (for example by using IPSec), even then, there ismandatory for systems which implement main power supply within a PSE Device." GROUP pethNotificationControlGroup DESCRIPTION "The pethNotificationControlGroupno control as to who on the secure network ismandatory for systems which implement PSE ports." ::= { pethCompliances 1 } pethPseCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Describesallowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. It is RECOMMENDED that implementers consider therequirementssecurity features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support forconformance tothePSESNMPv3 cryptographic mechanisms (for authentication andMID- Span." MODULE -- this module MANDATORY-GROUPS {pethPsePortGroup, pethMainPseGroup,pethNotificationControlGroup} ::= { pethCompliances 2 } pethPdCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Describes the requirements for conformanceprivacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that thePD." MODULE --SNMP entity giving access to an instance of this MIB moduleMANDATORY-GROUPS {pethPdPortGroup} ::= { pethCompliances 3} pethPsePortGroup OBJECT-GROUP OBJECTS { pethPsePortAdminEnable, pethPsePortPowerPairsControlAbility, pethPsePortPowerDetectionControl, pethPsePortPowerPairs, pethPsePortDetectionStatus, pethPsePortPowerPriority, pethPsePortPowerMaintenanceStatus , pethPsePortMPSAbsentCounter, pethPsePortOverCurrentCounter, pethPsePortType, pethPsePortPowerClassifications } STATUS current DESCRIPTION "The pethPsePortGroup is mandatory for systems which implement PSE ports." ::= { pethGroups 1 } pethPdPortGroup OBJECT-GROUP OBJECTS { pethPdPortAdminEnable } STATUS current DESCRIPTION "The pethPdPortGroupismandatory for systems which implement PD Ports." ::= { pethGroups 2 } pethMainPseGroup OBJECT-GROUP OBJECTS { pethMainPsePower, pethMainPseOperStatus, pethMainPseConsumptionPower, pethMainPseUsageThreshold } STATUS current DESCRIPTION "Main PSE Objects. " ::= { pethGroups 3 } pethNotificationControlGroup OBJECT-GROUP OBJECTS { pethNotificationControlEnable } STATUS current DESCRIPTION "Notification Control Objects. " ::= { pethGroups 4 } pethPsePortNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { pethPsePortOnOffNotification, pethPsePortPowerMaintenanceStatusNotification} STATUS current DESCRIPTION "Pse Notification indications" ::= { pethCompliances 4 } pethMainPowerNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { pethMainPowerUsageOnNotification, pethMainPowerUsageOffNotification} STATUS current DESCRIPTION "Pse Notification indications" ::= { pethCompliances 5 } END 8. Normative References [RFC2571] Harrington, D., Presuhn, R.,properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 11. Authors Addresses Avi Berger PowerDsine Inc. 1, Hanagar St., P.O. Box 7220 Hod Hasharon 45421, Israel Tel: +972-9-7755100 Ext 307 Fax: +972-9-7755120 E-mail: avib@PowerDsine.com Dan Romascanu Avaya Atidim Technology Park, Bldg. #3 Tel Aviv, 61131 Israel Tel: +972-3-645-8414 Email: dromasca@avaya.com A. Full Copyright Statement Copyright (c) The Internet Society (2003). All Rights Reserved This document andB. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.,translations of it may be copied andS. Waldbusser, "Structurefurnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction ofManagement Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.,any kind, provided that the above copyright notice andS. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.,this paragraph are included on all such copies andS. Waldbusser, "Conformance Statementsderivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed forSMIv2", STD 58, RFC 2580, April 1999. [RFC2572] Case, J., Harrington D., Presuhn R.,the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual andB. Wijnen, "Message Processingwill not be revoked by the Internet Society or its successors or assigns. This document andDispatching fortheSimple Network Management Protocol (SNMP)", RFC 2572, April 1999. [RFC2574] Blumenthal, U.,information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. B.Wijnen, "User-based Security Model (USM) for version 3Evolution of theSimple Network Management Protocol (SNMPv3)", RFC 2574, April 1999. [RFC2573] Levi, D., Meyer, P.,Document, Limitations andB. Stewart, "SNMPv3 Applications",Future Work NOTE: This section will be removed at RFC2573, April 1999. [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model (VACM)publication. The IEEE 802.3af is at this stage work in progress. The scope of this document is to do the standards work in the IETF in parallel with the IEEE standardization activity, in order to allow for theSimple Network Management Protocol (SNMP)", RFC 2575, April 1999. [RFC2570] Case, J., Mundy, R., Partain, D.,publication of a standard track document containing an SNMP MIB simultaneously or close to the date of the publication of the IEEE revised standard. It is possible that changes may be brought to the IEEE proposal, andB. Stewart, "Introductionthe Ethernet MIB Working Group will work in order to ensure consistency between the two standards proposals. C. Changes Log This section will be removed at RFC publication. The following changes were introduced relative to the first proposal for a Power Ethernet MIB [PWR-MIB] a. pethPsePortTable has to index pethPsePortGroupIndex & pethPsePortIndex b. pethPsePortIndex INTEGER instead of InterfaceIndex c. Name change pethPsePortStatus insted of pethPsePortFaultError d. Name change pethPsePortStatusClear instead of pethPsePortFaultErrorClear e. DESCRIPTION update for pethPsePortPowerDetectionStatus test(3) f. DESCRIPTION update pethPsePortDetectionOperStatus off(2) g. Adding to pethPsePortStatus one more item both(4) h. Adding pethMainPseTable with a pethMainPseGroupIndex i. Deletting toVersion 3objects pethMainPseMaxVoltage & pethMainPseMinVoltage j. Change SYNTAX ofthe Internet-standard Network Management Framework", RFC 2570, April 1999. [RFC2119] Bradner, S., "Key words for use in RFCspethMainPseUsagePower form INTEGER toIndicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2665] Flick, J., and J. Johnson, "DefinitionsGauge32 k. Change SYNTAX ofManagedpethMainPseUsageCurrent form INTEGER to Gauge32 l. Adding pethMainPseBackupActivated & pethMainPseBackupPresent m. Adding Traps Control Objectsfor the Ethernet-like Interface Types", RFC 2665, August 1999. [IEEE-802.3af] IEEE 802.3af Working Group, "Data Terminal Equipment (DTE) Power via Media Dependent Interface (MDI)", Draft D4.0, December 2002. 9. Informative References [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identificationn. Adding Notifications Section (5 notifications ) o. Adding pethTrapsControlGroup to Conformance Section p. Adding pethPsePortPowerClassifications to pethPsePortTable Class 1-5 q. Adding pethPsePortPowerClassifications to pethPsePortGroup r. Change in pethPsePortStatus none(1) to ok(1) s. Change in DESCRIPTION ofManagement Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990. [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991. [RFC1215] M. Rose, "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991. [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990. [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "IntroductionpethMainPseUsagePower from mW toCommunity-based SNMPv2", RFC 1901, January 1996. [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport Mappings for Version 2Watt t. Change pethMainPseUsagePower to pethMainPseConsumptionPower u. Delete ofthe Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996. [RFC1905] Case, J., McCloghrie, K., Rose, M.,pethMainPseUsageCurrent The following changes were introduced between draft-ietf-hubmib-power-ethernet-mib-00.txt and draft-ietf-hubmib-power-ethernet-mib-01.txt: 1. change pethMainPowerUsageTrap to pethMainPowerUsageOnTrap 2. add pethMainPowerUsageOffTrap 3. change pethMainPowerTrapGroup 4. change pethPsePorPowerEnable to pethPsePortAdminEnable 5. pethPsePortPowerIdPairsControl to pethPsePortPowerPairsControlAbility 6. pethPsePortPowerIdPairs to pethPsePortPowerPairs 7. delete both from pethPsePortPowerPairs object 8. change pethPsePortPowerDetectionStatus to pethPsePortPowerDetectionControl 9. delete from pethPsePortPowerDetectionControl off , andS. Waldbusser, "Protocol Operations for Versionchange test to 2of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. [PWR-MIB] Romascanu, D., " Power Ethernet (DTE Power via MDI) MIB", Internet-Draft, draft-romascanu-hubmib-power-ethernet-mib-00.txt, June 2002. 10.Intellectual Property The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed10. change pethPsePortDetectionOperStatus topertainpethPsePortDetectionStatus 11. change pethPsePortDetectionStatus to: disabled(1), searching(2), detected(3), deliveringPower(4), fault(5), invalidPD(6), test(7), denyLowPriority(8) 12. change description for pethPsePortPowerClassifications 13. change pethPsePortStatus tothe implementation or usepethPsePortCurrentStatus 14. Update description for pethPsePortCurrentStatus 15. change pethPsePortStatusClear to pethPsePortCurrentStatusClear 16. change pethPdPortDetectionOperStatus to pethPdPortDetectionStatus 17. change in description ofthe technology describedpethPdPortPowerPairs 18. change inthis document or the extentpethPdPortDetectionStatus description 19. delete pethPdPortPowerClassifications object 20. change in pethPsePortGroup 21. change in pethPdPortGroup 22. change pethPsePortOnOffTrap with pethPsePortDetectionStatus object 23. change pethPsePortStatusTrap towhich any license under such rights might or might not be available; neither does it represent that it has made any effortpethPsePortCurrentStatusTrap 24. change pethPsePortTrapGroup The following changes were introduced between draft-ietf-hubmib-power-ethernet-mib-01.txt and draft-ietf-hubmib-power-ethernet-mib-02.txt: 1. change pethMainPsePower SYNTAX Integer32 (0..65535) to (1..65535) 2. change pethTrapsControlGroupIndex SYNTAX Integer32 (0..65535) to (1..65535) 3. change int pethMainPseBackUpActivatedTrap pethPsePortGroupIndex to pethMainPseGroupIndex 4. change int pethMainPowerUsageOnTrap pethPsePortGroupIndex to pethMainPseGroupIndex 5. change int pethMainPowerUsageOffTrap pethPsePortGroupIndex to pethMainPseGroupIndex 6. change pethMainPseGroupIndex MAX-ACCESS to read-only updates from IEEE Draft P802.3af/D3.1, June 5, 2002 7. remove from pethPsePortPowerClassifications class5 8. remove from pethPsePortCurrentStatus both(4) and description 9. add pethPsePortUnderCurrentCounter object 10. add pethPsePortOverCurrentCounter object 11. remove pethPsePortCurrentStatusClear object 12. change pethPsePortType OID to end with 13 13. change pethPsePortPowerClassifications OID toidentify any such rights. Information on the IETF's proceduresend withrespect14 14. update pethPsePortGroup OBJECT-GROUP 15. chage reference torights in standards-tracknew IEEE Draft 16. change pethPdCompliance description. The following changes were introduced between draft-ietf-hubmib-power-ethernet-mib-02.txt andstandards-related documentation can be found in BCP-11. Copies of claims of rights made available for publicationdraft-ietf-hubmib-power-ethernet-mib-03.txt: 1. remove pethPsePortGroupIndex andany assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtainedpethPsePortIndex fromthe IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the informationpethPsePortOnOffTrap and pethPsePortCurrentStatusTrap 2. change pethPsePortGroupIndex and pethPsePortIndex MAX-ACCESS tothe IETF Executive Director. 11. Security Considerations There are a number of management objects definednot-accessible 3. remove pethMainPseGroupIndex from pethMainPseBackUpActivatedTrap 4. replace pethMainPseGroupIndex with pethMainPseConsumptionPower inthis MIB that have apethMainPowerUsageOnTrap and pethMainPowerUsageOffTrap 5. change pethMainPseGroupIndex MAX-ACCESSclause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. There are a number of managed objects in this MIB that may contain sensitive information. These are: pethPsePortPowerPairsControlAbility pethPsePortPowerPriority pethPsePortPowerClassifications It is thus important to control even GET accesstothese objectsnot-accessible 6. move pethPsePortTrapGroup NOTIFICATION-GROUP andpossiblypethMainPowerTrapGroup NOTIFICATION-GROUP toeven encryptthevalues of these object when sending them overConformance Section 7. update thenetwork via SNMP. Not all versionsdiscription ofSNMP provide features for such a secure environment. SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control aspethPsePortOnOffTrap 8. add pethPsePortPowerDetectionControl towho on the secure network is allowedpethPsePortGroup 9. change reference toaccessIEEE Draft P802.3af/D3.3 October 2002 10. delete enumaration pethPsePortDetectionStatus detected(3) andGET/SET (read/change/create/delete) the objects in this MIB. It is RECOMMENDED that the implementers consider the security featuresinvalidPD(6) 11. change pethPsePortCurrentStatus to pethPsePortPowerMaintenanceStatus 12 . change pethPsePortUnderCurrentCounter to pethPsePortMPSAbsentCounter 13. add pethPdPortAdminEnable object. 14. replace Trap with Notification. 15. update pethPsePortOnOffNotification description. 16. update pethPsePortDetectionStatus description. 17. remove pethPdPortPowerPairs object. 18. remove pethPdPortDetectionStatus object. 19. remove pethPdPortType object. 20. change pethPdPortAdminEnable OID. The following changes were introduced between draft-ietf-hubmib-power-ethernet-mib-03.txt and draft-ietf-hubmib-power-ethernet-mib-04.txt: 1. remove pethMainPseMaximumDcPower object 2. remove pethMainPseBackupPresent object 3. remove pethMainPseBackupActivated object. 4. remove pethMainPseBackUpActivatedNotification 5. change reference from IEEE Draft P802.3af/D3.3, October, 2002 to IEEE Draft P802.3af/D4.0, November, 2002 6. DESCRIPTION "Initial version, published asprovided by the SNMPv3 framework. Specifically,RFC yyyy." 7. change theusesyntax ofthe User-based Security Model [RFC2274] and the View-based Access Control Model [RFC2275] is RECOMMENDED. It is then a customer/user responsibilitypethPsePortGroupIndex from INTEGER (1..2147483647) toensure thatInteger32 (1..2147483647). 8. change theSNMP entity giving accesssyntax of pethPsePortIndex from INTEGER (1..2147483647) toan instanceInteger32 (1..2147483647). 9.change the syntax ofthis MIB, is properly configuredpethPdPortIndex from INTEGER (0..65535) togive accessInterfaceIndex. 10.import InterfaceIndex from IF-MIB. 11. change the syntax of pethMainPseGroupIndex from INTEGER (0..65535) to Integer32 (1..2147483647) 12. change theobjects onlysyntax of pethMainPseUsageThreshold from INTEGER (1..99) tothose principals (users) that have legitimate rightsInteger32 (1..99). 13. change the syntax of pethNotificationControlGroupIndex from INTEGER (1..65535) toindeed GET or SET (change/create/delete) them. 12. Authors Addresses Avi Berger PowerDsine Inc. 1, Hanagar St., P.O. Box 7220 Hod Hasharon 45421, Israel Tel: +972-9-7755100 Ext 307 Fax: +972-9-7755120 E-mail: avib@PowerDsine.com Dan Romascanu Avaya Inc. Atidim Technology Park, Bldg. #3 Tel Aviv, 61131 Israel Tel: +972-3-645-8414 Email: dromasca@avaya.com A. Full Copyright Statement This document and translationsInteger32 (1..2147483647) 14. replace OID: ! pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 0 } ! pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 } ! pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 2 } 15. change the discription ofit may be copiedthe pethPsePortGroup andfurnishedpethPdPortGroup 16. pethMainPsePower changed toothers, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied,Gauge32 17. add: REVISION "200212020000Z" -- December 02, 2002 DESCRIPTION "Initial version, publishedand distributed, in whole or in part, without restriction of any kind, provided thatas RFC yyyy." 18 change theabove copyrightMIB registered from { dot3 20 } ::= { mib-2 XXX } -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice The following changes were introduced between draft-ietf-hubmib-power-ethernet-mib-04.txt andthis paragraph are included ondraft-ietf-hubmib-power-ethernet-mib-05.txt: 1. Add reference and chhange discription pethPsePortAdminEnable object 2. Add reference to pethPsePortPowerPairsControlAbility object 3. Add reference to pethPsePortPowerPairs object 4. Remove pethPsePortPowerDetectionControl object 5. Change pethPsePortDetectionStatus object 6. Update pethPsePortPowerClassifications description 7. Update pethPsePortPowerMaintenanceStatus 8. Update pethPsePortMPSAbsentCounter description 9. Remove pethPsePortOverCurrentCounter object 10. Add pethPsePortInvalidSignatureCounter new object 11. Add pethPsePortPowerDeniedCounter new object 12. Add pethPsePortOverLoadCounter new Object 13. Add pethPsePortShortCounter new Object 14. Remove pethPdPortTable 15. change allsuch copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice orreferences from P802.3af/D4.2 to P802.3af/D4.3 16. Update theInternet Society or other Internet organizations, except as neededdescription for thepurpose of developing Internet standardspethPsePortPowerPairsControlAbility 17. Change pethPsePortDetectionStatus deliveringPower description text 18. Remove pethPsePortPowerMaintenanceStatus 19. Remove pethPsePortPowerMaintenanceStatusNotification 20. Change pethPsePortOverLoadCounter description 21. Change pethPsePortShortCounter description 22. Change pethPsePortMPSAbsentCounter description 23. Spelling fix inwhich case the procedures for copyrights definedpethPsePortDetectionStatus 24. Spelling fix inthe Internet Standards process must be followed, or as requiredpethPsePortShortCounter 25. Change in MIB module DESCRIPTION totranslate it into languages other than English. The limited permissions granted above are perpetualstrike out Powered Devices (PD) 26. Update references sections according to MIB Doctor Review 27. Change document title to avoid use of acronyms 28. Similar for Introduction section 29. Moved Sections 5 andwill not be revoked by6 at the end of theInternet Society or its successors or assigns. Thisdocument andthe information contained herein is provided on an "AS IS" basisadded note to be removed at RFC publication 30. Change SYNTAX of pethPsePortAdminEnable to TruthValue 31. Same for pethNotificationControlEnable 32. Remove `InterfaceIndex' imported from module `IF-MIB' 33. Add `pethPsePortNotificationGroup' andTHE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.`pethMainPowerNotificationGroup' to pethPseCompliance MODULE-COMPLIANCE 34. Add mailing list information 35. Change pethPsePortAdminEnable from Integer to TruthValue 36. Update Notification description 37. Change the enumeration values in pethPsePortDetectionStatus Object 38. Change in pethCompliance MODULE-COMPLIANCE 39. Change incorrect reference to RFC 2863 to reference to RFC 2119 40. Added Informative Reference to RFC 3410