--- 1/draft-ietf-hubmib-power-ethernet-mib-00.txt 2006-02-04 23:26:24.000000000 +0100 +++ 2/draft-ietf-hubmib-power-ethernet-mib-01.txt 2006-02-04 23:26:24.000000000 +0100 @@ -1,38 +1,35 @@ Internet Draft Avi Berger PowerDsine Inc. Dan Romascanu Avaya Inc. - 25 June 2001 + 20 November 2001 Power Ethernet (DTE Power via MDI) MIB - + 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." - The list of current Internet-Drafts can be accessed at - http://www.ietf.org/1id-abstracts.html - - The list of Internet-Draft Shadow Directories can be accessed at + To view the list Internet-Draft Shadow Directories, see http://www.ietf.org/shadow.html. Copyright Notice Copyright (C) The Internet Society (2001). 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. @@ -45,26 +42,26 @@ Table of Contents Status of this Memo 1 Abstract 1 1 Introduction 2 2 The SNMP Management Framework 2 3 Overview 3 4 MIB Structure 4 5 Evolution of the Document, Limitations and Future Work 4 6 Changes log 4 - 7 Definitions 5 - 8 References 20 - 9 Intellectual Property 22 - 10 Security Considerations 22 - 11 Authors Addresses 23 - A Full Copyright Statement 23 + 7 Definitions 7 + 8 References 23 + 9 Intellectual Property 24 + 10 Security Considerations 25 + 11 Authors Addresses 25 + A Full Copyright Statement 26 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 Source Equipment (PSE). The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", @@ -160,26 +157,27 @@ The pethMainPseObjects 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. The pethTrapsControlTable includes objects that control the transmission of traps by the agent to a management application. 5. Evolution of the Document, Limitations and Future Work The IEEE 802.3af is at this stage work in progress. The scope of this - document is to initiate standards work in the IETF in order to allow - for the 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 expected that changes may be brought to - the IEEE proposal, and the Ethernet MIB Working Group will work in - order to ensure consistency between the two standards proposals. + document is to do the standards work in the IETF in parallel with the + IEEE standardization activity, in order to allow for the 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 expected that changes may be brought to the IEEE proposal, and + the Ethernet MIB Working Group will work in order to ensure + consistency between the two standards proposals. 6. Changes Log 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 @@ -216,23 +214,86 @@ q. Adding pethPsePortPowerClassifications to pethPsePortGroup r. Change in pethPsePortStatus none(1) to ok(1) s. Change in DESCRIPTION of pethMainPseUsagePower 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.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 , and change test + to 2 + + 10. change pethPsePortDetectionOperStatus to + pethPsePortDetectionStatus + + 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 to pethPsePortCurrentStatus + + 14. Update description for pethPsePortCurrentStatus + + 15. change pethPsePortStatusClear to pethPsePortCurrentStatusClear + + 16. change pethPdPortDetectionOperStatus to pethPdPortDetectionStatus + + 17. change in description of pethPdPortPowerPairs + + 18. change in pethPdPortDetectionStatus description + + 19. delete pethPdPortPowerClassifications object + + 20. change in pethPsePortGroup + + 21. change in pethPdPortGroup + + 22. change pethPsePortOnOffTrap with pethPsePortDetectionStatus + object + + 23. change pethPsePortStatusTrap to pethPsePortCurrentStatusTrap + 24. change pethPsePortTrapGroup + 7. Definitions - PETH-MIB DEFINITIONS ::= BEGIN + POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32 , Gauge32,NOTIFICATION-TYPE FROM SNMPv2-SMI dot3 FROM EtherLike-MIB TruthValue FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP ,NOTIFICATION-GROUP FROM SNMPv2-CONF; @@ -229,51 +290,69 @@ IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32 , Gauge32,NOTIFICATION-TYPE FROM SNMPv2-SMI dot3 FROM EtherLike-MIB TruthValue FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP ,NOTIFICATION-GROUP FROM SNMPv2-CONF; + powerEthernetMIB MODULE-IDENTITY - LAST-UPDATED "200106200000Z" -- June 20, 2001 + LAST-UPDATED "200111200000Z" -- November 20, 2001 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 + 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 + "The MIB module for managing Powered Devices (PD) or Power Source Equipment (PSE) working according to the IEEE - 802.af Powere Ethernet (DTE Power via MDI) standard." + 802.af Power 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. + ::= { dot3 20 } pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 } pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 2 } pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 3 } - -- pethAgentControl MIB group defines the control objects for the power - -- Ethernet Agent + -- 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." @@ -287,151 +366,158 @@ "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 INTEGER, pethPsePortIndex INTEGER, - pethPsePortPowerEnable + pethPsePortAdminEnable INTEGER, - pethPsePortPowerIdPairsControl + pethPsePortPowerPairsControlAbility TruthValue, - pethPsePortPowerIdPairs + pethPsePortPowerPairs INTEGER, - pethPsePortPowerDetectionStatus + pethPsePortPowerDetectionControl INTEGER, - pethPsePortDetectionOperStatus + pethPsePortDetectionStatus INTEGER, pethPsePortPowerPriority INTEGER, - pethPsePortDenyError - INTEGER, - pethPsePortStatus + pethPsePortCurrentStatus INTEGER, - pethPsePortStatusClear + pethPsePortCurrentStatusClear INTEGER, pethPsePortType INTEGER, pethPsePortPowerClassifications INTEGER } pethPsePortGroupIndex OBJECT-TYPE SYNTAX INTEGER (1..2147483647) - MAX-ACCESS not-accessible + MAX-ACCESS read-only STATUS current DESCRIPTION "This variable uniquely identifies the group containing the port to which power Ethernet PSE is connected. - Group means a box in the stack, or a module in a rack. - For non-modular devices the value 1 is recommended." + Group means (box in the stack, module in a rack) and the value 1 + MUST be used for non-modular devices " ::= { pethPsePortEntry 1 } pethPsePortIndex OBJECT-TYPE SYNTAX INTEGER(1..2147483647) - MAX-ACCESS not-accessible + MAX-ACCESS read-only 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 } - pethPsePortPowerEnable OBJECT-TYPE + pethPsePortAdminEnable OBJECT-TYPE SYNTAX INTEGER { - auto(1), - off(2) + enable(1), + disable(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Enables power supply on this port. - Setting this object at a value auto(1) enables power + Setting this object at a value enable(1) enables power and detection mechanism for this port. - Setting this object at a value off(2) disables power - and detection mechanism for this port." + Setting this object at a value disable(2) disables power + for this port." ::= { pethPsePortEntry 3 } - pethPsePortPowerIdPairsControl OBJECT-TYPE + 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." + "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" ::= { pethPsePortEntry 4 } - pethPsePortPowerIdPairs OBJECT-TYPE + pethPsePortPowerPairs OBJECT-TYPE SYNTAX INTEGER { signal(1), - spare(2), - both(3) + spare(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Describes or controls the pairs in use. If the value of - pethPsePortPowerIdpairsControl is true, thisobject is + pethPsePortPowerPairsControl is true, this object is writable. A value of signal(1) menas that the signal pairs only are in use. - A value of spare(2) means that the spare pairs - only are in use. - A value of both(3) means that both the signal - and the spare pairs are in use." + only are in use." ::= { pethPsePortEntry 5 } - pethPsePortPowerDetectionStatus OBJECT-TYPE + pethPsePortPowerDetectionControl OBJECT-TYPE SYNTAX INTEGER { auto(1), - off(2), - test(3) + 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 off(2) disables the power detection - mechanism of the port. - Setting the value test(3) puts the port in a - test mode forcing continuous discovery without applying + Setting the value test(2) puts the port in a + testmode: force continuous discovery without applying power regardless of whether PD detected." ::= { pethPsePortEntry 6 } - pethPsePortDetectionOperStatus OBJECT-TYPE + pethPsePortDetectionStatus OBJECT-TYPE SYNTAX INTEGER { - deliveringPower(1), - off(2), - searching(3), - fault(4) + disabled(1), + searching(2), + detected(3), + deliveringPower(4), + fault(5), + invalidPD(6), + test(7), + denyLowPriority(8) } MAX-ACCESS read-only STATUS current DESCRIPTION - "Describes the operational status of the port detection. - A value of deliveringPower(1) indicates that the port + "Describes the operational status of the port PD detection. + A value of disabled(1) indicates that the PD Detection function has + been disabled. + A value of searching(2) indicates that the PD Detection function is + enabled and is searching for a valid PD. + A value of detected(3)indicates that the PD Detection function has + detected a valid PD but the PSE is not supplying power. + A value of deliveringPower(4) indicates that the port executed the detection algorithm, found a PD connection and is currently delivering power. - A value of off(2) indicates that the port did not find - a PD connection and is not in serching mode. - A value of searching(3) indicates that the detection - algorithm is in work, and did not detect a valid PD. No - power is currently provided. - A value of fault(4) indicates that a fault was detected - on the port . " + A value of fault(5) indicates that a fault was detected + on the port , faults detected are vendor-specific. + A value of invalidPD(6)indicates that the PD Detection function has + detected a invalid PD. + A value of test(7)indicates that the PD Detection function has been + placed in test mode. + A value of denyLowPriority(8) indicates that the port was + disabled by the power management system, in order to keep + active higher priority ports. + " ::= { 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 @@ -436,63 +522,69 @@ 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 } - pethPsePortDenyError OBJECT-TYPE - SYNTAX INTEGER { - other(1), - lowPriority(2) - } - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "This object describes an error resulted from an action of the - power management mechanism. The value lowPriority(2) indicates - that the port was disabled by the power management system, in - order to keep active higher priority ports." - ::= { pethPsePortEntry 9 } - - pethPsePortStatus OBJECT-TYPE + pethPsePortCurrentStatus OBJECT-TYPE SYNTAX INTEGER { ok(1), underCurrent(2), overCurrent(3), both(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "Describes a current port status related to the power generation + The value ok(1) indicates neither an undercurrent or an overcurrent + condition was detected since the attribute was last cleared. The value underCurrent(2) indicates that the port current - is below the minimal value. + is below the minimal value since the attribute was last cleared. The value overCurrent(3) indicates that the port current - exceeds the maximal value. + exceeds the maximal value since the attribute was last cleared. The value both(4) indicates that both underCurrent and overCurrent - status happend from the lase Clear." + since the attribute was last cleared. + This attribute is cleared through the pethPsePortCurrentStatusClear + action. + + An undercurrent condition is detected when the current drawn from + the PSE at the MDI is less than + Off-mode current 2 for a duration greater than Under load time + limit. + An overcurrent condition is detected when the current drawn from the + PSE at the MDI is greater than the overload current limit + for a duration greater that Overload time limit. + The values Overload current limit, Overload time + limit, Off-mode current 2 and Under load time limit are specified in + Table 33-5. If a Clause 22 MII or Clause 35 GMII is present, then + this will map to the Under Current and Over Current bits + specified in 33.6.1.2.2 and 33.6.1.2.3.;" + REFERENCE "[IEEE DRAFT STANDARD FOR DTE POWER VIA MDI P802.3af/D1.2]" ::= { pethPsePortEntry 10 } - pethPsePortStatusClear OBJECT-TYPE + pethPsePortCurrentStatusClear OBJECT-TYPE SYNTAX INTEGER { clear(1), off(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Setting the value of this object to clear(1) clears the value - of the pethPsePortStatus to none(1)." + of the pethPsePortStatus and enable the agent to update the + pethPsePortStatus. + Read operation this value will be off(2)." ::= { pethPsePortEntry 11 } pethPsePortType OBJECT-TYPE SYNTAX INTEGER { other(1), telephone(2), webcam(3), wireless(4) } MAX-ACCESS read-write @@ -511,31 +603,31 @@ class1(2), class2(3), class3(4), class4(5), class5(6) } 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. + 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. + A read-only value that indicates the PD Class of a detected PD as + specified in IEEE Draft P802.3af/D2.1 Supplement to IEEE Std.802.3 + November 14 2001 cclause 33.2.5 and 33.2.6. - Class Usage Maximum Power - 0 Default 0.5 - 15.0 W - 1 Optional 0.5 - 4.0 W - 2 Optional 4.0 - 7.0 W - 3 Optional 7.0 - 15.0 W - 4 Optional Future Use - 5 Optional Future Use + The value is only valid while a valid PD is being detected as indicated + by the attribute pethPsePortDetectionStatus reporting the enumeration + (detected) or (deliveringPower). " ::= { pethPsePortEntry 13 } -- PD Port table pethPdPortTable OBJECT-TYPE SYNTAX SEQUENCE OF PethPdPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION @@ -553,21 +645,21 @@ "A set of objects that display and control the power characteristics of a Powered Device port." INDEX { pethPdPortIndex } ::= { pethPdPortTable 1 } PethPdPortEntry ::= SEQUENCE { pethPdPortIndex INTEGER, pethPdPortPowerPairs INTEGER, - pethPdPortDetectionOperStatus + pethPdPortDetectionStatus INTEGER, pethPdPortType INTEGER } pethPdPortIndex OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION @@ -583,42 +675,48 @@ pethPdPortPowerPairs OBJECT-TYPE SYNTAX INTEGER { signal(1), spare(2), both(3) } MAX-ACCESS read-only STATUS current DESCRIPTION - "Describes the pairs in use. - A value of signal(1) menas that the signal pairs - only are in use. - A value of spare(2) means that the spare pairs - only are in use. - A value of both(3) means that both the signal - and the spare pairs are inuse." + "Describes the pairs in use by the PD to derive power. + A value of signal(1) indicates that only PD Pinout Mode A is + supported by the PD. + A value of spare(2) indicates that only PD Pinout Mode B is + supported by the PD. + A value of both(3) means indicates that both PD Pinout Mode A and PD + Pinout Mode B are supported by the PD." ::= { pethPdPortEntry 2 } - pethPdPortDetectionOperStatus OBJECT-TYPE + pethPdPortDetectionStatus OBJECT-TYPE SYNTAX INTEGER { off(1), receivingPower(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "Describes the operational status of the port detection. - The value off(1) means that the port does not receive - power and the detection algorithm might still be operating. - The value receivingPower(2) means that the port is - receiving power. " + The value off(1) indicates that the PD is drawing a current less + than I + Port as specified in IEEE Draft P802.3af/D2.1 Supplement to IEEE + Std.802.3 November 14 2001 Table 33-10. + The value receivingPower(2) indicates that the PD is drawing a + current greater I Port as specified in + IEEE Draft P802.3af/D2.1 Supplement to + IEEE Std.802.3 November 14 2001 Table 33-10. + + " ::= { pethPdPortEntry 3 } pethPdPortType OBJECT-TYPE SYNTAX INTEGER { other(1), telephone(2), webcam(3), wireless(4) } MAX-ACCESS read-only @@ -633,21 +731,22 @@ -- Main PSE Objects pethMainPseObjects OBJECT IDENTIFIER ::= { pethObjects 3 } pethMainPseTable OBJECT-TYPE SYNTAX SEQUENCE OF PethMainPseEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of objects that display and control the Main power - on a PSE device." + on a PSE device. Example internet switch midspan device can + control an Internet port and the Main Power supply unit's." ::= { pethMainPseObjects 1 } pethMainPseEntry OBJECT-TYPE SYNTAX PethMainPseEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of objects that display and control the Main power of a PSE." INDEX { pethMainPseGroupIndex } @@ -658,108 +757,120 @@ INTEGER, pethMainPsePower Integer32, pethMainPseOperStatus INTEGER, pethMainPseConsumptionPower Gauge32, pethMainPseBackupPresent INTEGER, pethMainPseBackupActivated - INTEGER, + TruthValue, pethMainPseUsageThreshold + INTEGER, + pethMainPseMaximumDcPower INTEGER } pethMainPseGroupIndex OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This variable uniquely identifies the group to which - power Ethernet PSE is connected. Group means box in the stack, - module in a rack. It is recommended that the value 1 be - used for non-modular devices " + 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 " ::= { pethMainPseEntry 1 } pethMainPsePower OBJECT-TYPE SYNTAX Integer32 (0..65535) - MAX-ACCESS read-write + UNITS "Watts" + MAX-ACCESS read-only STATUS current DESCRIPTION "The nominal power of the PSE expressed in Watts." ::= { pethMainPseEntry 2 } pethMainPseOperStatus OBJECT-TYPE SYNTAX INTEGER { on(1), off(2), faulty(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The operational status of the main PSE." ::= { pethMainPseEntry 3 } pethMainPseConsumptionPower OBJECT-TYPE SYNTAX Gauge32 + UNITS "Watts" MAX-ACCESS read-only STATUS current DESCRIPTION "Measured usage power expressed in Watts." ::= { pethMainPseEntry 4 } pethMainPseBackupPresent OBJECT-TYPE SYNTAX INTEGER { present(1), notPresent(2), faulty(3) } MAX-ACCESS read-only STATUS current DESCRIPTION - "This value reflects the presence and status - of a backup PSE ." + "reflects the presence of a backup PSE ." ::= { pethMainPseEntry 5 } pethMainPseBackupActivated OBJECT-TYPE - SYNTAX INTEGER { - activated(1), - notActivated(2) - } + SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION - "This variable reflects the activation status - of the backup PSE" + "Reflects the activation status of the backup PSE . + The value true Backup is activated." ::= { pethMainPseEntry 6 } pethMainPseUsageThreshold OBJECT-TYPE SYNTAX INTEGER (1..99) + UNITS "%" MAX-ACCESS read-write STATUS current DESCRIPTION - "The usage threshold expressed in percents for + "The usage threshold expressed in percens for comparing the measured power and initiating an alarm if the threshold is exceeded." ::= { pethMainPseEntry 7 } + pethMainPseMaximumDcPower OBJECT-TYPE + SYNTAX INTEGER + UNITS "Watts" + MAX-ACCESS read-write + STATUS current + DESCRIPTION + "Describes the maximum available power in + Watt to be supplied by the DC backup source to this + device." + ::= { pethMainPseEntry 8 } + -- Traps Control Objects pethTrapsControl OBJECT IDENTIFIER ::= { pethObjects 4 } pethTrapsControlTable OBJECT-TYPE SYNTAX SEQUENCE OF PethTrapsControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "A table of objects that display and control the Main power + "A table of objects that display and control the Traps on a PSE device." ::= { pethTrapsControl 1 } pethTrapsControlEntry OBJECT-TYPE SYNTAX PethTrapsControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of objects that control the Trap events." INDEX { pethTrapsControlGroupIndex } @@ -770,73 +881,90 @@ INTEGER, pethTrapsControlEnable INTEGER } pethTrapsControlGroupIndex OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This variable uniquely identifies the group. Group means - box in the stack, or module in a rack. It is recommended - that the value 1 is used for non-modular devices." + box in the stack, module in a rack and it is recommended + that the value 1 MUST be used for non-modular devices " ::= { pethTrapsControlEntry 1 } pethTrapsControlEnable OBJECT-TYPE SYNTAX INTEGER { enable(1), disable(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "Enable Traps from Agent" ::= { pethTrapsControlEntry 2 } -- -- Notifications Section -- -- pethPsePortOnOffTrap NOTIFICATION-TYPE - OBJECTS { pethPsePortGroupIndex,pethPsePortIndex,pethPsePortDetectionOperStatus } + OBJECTS { pethPsePortGroupIndex,pethPsePortIndex,pethPsePortDetectionStatus } STATUS current DESCRIPTION " This trap indicate if Pse Port is delivering or not power to the PD." ::= { pethNotifications 1 } - pethPsePortDenyTrap NOTIFICATION-TYPE - OBJECTS { pethPsePortGroupIndex,pethPsePortIndex,pethPsePortDenyError } + + pethPsePortCurrentStatusTrap NOTIFICATION-TYPE + OBJECTS { pethPsePortGroupIndex,pethPsePortIndex,pethPsePortCurrentStatus } STATUS current DESCRIPTION - " This trap indicate Port Deny service." + "This trap indicate Port Change Status and it will be + sent on every status change." ::= { pethNotifications 2 } - pethPsePortStatusTrap NOTIFICATION-TYPE - OBJECTS { pethPsePortGroupIndex,pethPsePortIndex,pethPsePortStatus } + pethMainPseBackUpActivatedTrap NOTIFICATION-TYPE + OBJECTS { pethPsePortGroupIndex,pethMainPseBackupActivated } STATUS current DESCRIPTION - " This trap indicate Port Change Status." + "This trap indicate BackUp is Activated or BackUp + is released." ::= { pethNotifications 3 } - pethMainPseBackUpActivatedTrap NOTIFICATION-TYPE - OBJECTS { pethPsePortGroupIndex,pethMainPseBackupActivated } + pethMainPowerUsageOnTrap NOTIFICATION-TYPE + OBJECTS { pethPsePortGroupIndex } STATUS current DESCRIPTION - " This trap indicates that BackUp PSE is Activated ." + "This trap indicate PSE Threshold usage indication is on , + the useage power is above the treshold." ::= { pethNotifications 4 } - pethMainPowerUsageTrap NOTIFICATION-TYPE + pethMainPowerUsageOffTrap NOTIFICATION-TYPE OBJECTS { pethPsePortGroupIndex } STATUS current DESCRIPTION - " This trap indicate PSE Threshold usage indication ." + "This trap indicate PSE Threshold usage indication off , + the useage power is below the treshold.." ::= { pethNotifications 5 } + pethPsePortTrapGroup NOTIFICATION-GROUP + NOTIFICATIONS { pethPsePortOnOffTrap, pethPsePortCurrentStatusTrap} + STATUS current + DESCRIPTION + "Pse trap indications" + ::= { pethNotifications 6 } + + pethMainPowerTrapGroup NOTIFICATION-GROUP + NOTIFICATIONS { pethMainPseBackUpActivatedTrap, pethMainPowerUsageOnTrap,pethMainPowerUsageOffTrap} + STATUS current + DESCRIPTION "Pse trap indications" + ::= { pethNotifications 7 } -- -- Conformance Section -- pethCompliances OBJECT IDENTIFIER ::= { pethConformance 1 } pethGroups OBJECT IDENTIFIER ::= { pethConformance 2 } pethCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION @@ -854,58 +982,75 @@ GROUP pethMainPseGroup DESCRIPTION "The pethMainPseGroup is mandatory for systems which implement main power supply within a PSE Device." GROUP pethTrapsControlGroup DESCRIPTION "The pethTrapsControlGroup is mandatory for systems which implement PSE ports." ::= { pethCompliances 1 } + pethPseCompliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "Describes the requirements for conformance to the PSE and MidSpan." + MODULE -- this module + MANDATORY-GROUPS {pethPsePortGroup, pethMainPseGroup,pethTrapsControlGroup} + ::= { pethCompliances 2 } + + pethPdCompliance MODULE-COMPLIANCE + STATUS current + DESCRIPTION + "Describes the requirements for conformance to the PSE + and MidSpan." + MODULE -- this module + MANDATORY-GROUPS {pethPdPortGroup} + ::= { pethCompliances 3 } + pethPsePortGroup OBJECT-GROUP OBJECTS { - pethPsePortPowerEnable, - pethPsePortPowerIdPairsControl, - pethPsePortPowerIdPairs, - pethPsePortPowerDetectionStatus, - pethPsePortDetectionOperStatus, + pethPsePortGroupIndex, + pethPsePortIndex, + pethPsePortAdminEnable, + pethPsePortPowerPairsControlAbility, + pethPsePortPowerPairs, + pethPsePortDetectionStatus, pethPsePortPowerPriority, - pethPsePortDenyError, - pethPsePortStatus, - pethPsePortStatusClear, + pethPsePortCurrentStatus, + pethPsePortCurrentStatusClear, pethPsePortType, pethPsePortPowerClassifications } STATUS current DESCRIPTION "PSE Port Objects." ::= { pethGroups 1 } pethPdPortGroup OBJECT-GROUP OBJECTS { pethPdPortPowerPairs, - pethPdPortDetectionOperStatus, + pethPdPortDetectionStatus, pethPdPortType } STATUS current DESCRIPTION "PD Port Objects." ::= { pethGroups 2 } - pethMainPseGroup OBJECT-GROUP OBJECTS { pethMainPsePower, pethMainPseOperStatus, pethMainPseConsumptionPower, pethMainPseBackupPresent, pethMainPseBackupActivated, - pethMainPseUsageThreshold + pethMainPseUsageThreshold, + pethMainPseMaximumDcPower } STATUS current DESCRIPTION "Main PSE Objects. " ::= { pethGroups 3 } pethTrapsControlGroup OBJECT-GROUP OBJECTS { pethTrapsControlEnable } @@ -978,22 +1123,22 @@ "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2665] Flick, J., and J. Johnson, "Definitions of Managed Objects for 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 D1.1, - January 2001. + Power via Media Dependent Interface (MDI)", Draft D2.1, + November 2001. [PWR-MIB] Romascanu, D., " Power Ethernet (DTE Power via MDI) MIB", Internet-Draft, draft-romascanu-hubmib-power-ethernet-mib-00.txt, February 2001. 9.Intellectual Property The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in @@ -1048,22 +1193,22 @@ 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 + 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