draft-ietf-hubmib-power-ethernet-mib-04.txt | draft-ietf-hubmib-power-ethernet-mib-05.txt | |||
---|---|---|---|---|
Internet Draft Avi Berger | Internet Draft Avi Berger | |||
PowerDsine Inc. | PowerDsine Inc. | |||
Dan Romascanu | Dan Romascanu | |||
Avaya Inc. | Avaya | |||
19 December 2002 | 21 May 2003 | |||
Power Ethernet (DTE Power via MDI) MIB | Power Ethernet MIB | |||
<draft-ietf-hubmib-power-ethernet-mib-04.txt> | <draft-ietf-hubmib-power-ethernet-mib-05.txt> | |||
Status of this Memo | Status of this Memo | |||
This document is an Internet-Draft and is in full conformance with | This document is an Internet-Draft and is in full conformance with | |||
all provisions of Section 10 of RFC2026. Internet-Drafts are working | all provisions of Section 10 of RFC2026. Internet-Drafts are working | |||
documents of the Internet Engineering Task Force (IETF), its areas, | documents of the Internet Engineering Task Force (IETF), its areas, | |||
and its working groups. Note that other groups may also distribute | and its working groups. Note that other groups may also distribute | |||
working documents as Internet-Drafts. | working documents as Internet-Drafts. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet- Drafts as reference | time. It is inappropriate to use Internet- Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
To view the list Internet-Draft Shadow Directories, see | To view the list Internet-Draft Shadow Directories, see | |||
http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
Copyright Notice | Copyright Notice | |||
Copyright (C) The Internet Society (2002). All Rights Reserved. | Copyright (C) The Internet Society (2003). All Rights Reserved. | |||
Abstract | Abstract | |||
This memo defines a portion of the Management Information Base (MIB) | This memo defines a portion of the Management Information Base (MIB) | |||
for use with network management protocols in the Internet community. | for use with network management protocols in the Internet community. | |||
The document proposes an extension to the Ethernet-like Interfaces | The document proposes an extension to the Ethernet-like Interfaces | |||
MIB [RFC2665] with a set of objects for managing a power Ethernet | MIB with a set of objects for managing a Power Source Equipment | |||
Powered Device (PD) and/or Power Source Equipment (PSE). | (PSE). | |||
Distribution of this memo is unlimited. | Distribution of this memo is unlimited. | |||
Table of Contents | Table of Contents | |||
Status of this Memo 1 | Status of this Memo 1 | |||
Abstract 1 | Abstract 1 | |||
1 Introduction 2 | 1 Introduction 2 | |||
2 The SNMP Management Framework 2 | 2 The Internet-Standard Management Framework 2 | |||
3 Overview 3 | 3 Overview 2 | |||
4 MIB Structure 4 | 4 MIB Structure 3 | |||
5 Evolution of the Document, Limitations and Future Work 4 | 5 Definitions 3 | |||
6 Changes log 4 | 6 Acknowledgements 17 | |||
7 Definitions 10 | 7 Normative References 17 | |||
8 Normative References 24 | 8 Informative References 18 | |||
9 Informative References 25 | 9 Intellectual Property 18 | |||
10 Intellectual Property 26 | 10 Security Considerations 18 | |||
11 Security Considerations 27 | 11 Authors Addresses 20 | |||
12 Authors Addresses 27 | A Full Copyright Statement 20 | |||
A Full Copyright Statement 28 | B Evolution of the Document, Limitations and Future Work 21 | |||
C Changes log 21 | ||||
1. Introduction | 1. Introduction | |||
This memo defines a portion of the Management Information Base (MIB) | This memo defines a portion of the Management Information Base (MIB) | |||
for use with network management protocols in the Internet community. | for use with network management protocols in the Internet community. | |||
In particular, it defines a set of MIB objects to manage a Power | 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 | Ethernet [IEEE-802.3af] Source Equipment (PSE). | |||
Equipment (PSE). | ||||
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | |||
document are to be interpreted as described in [RFC2863]. | document are to be interpreted as described in [RFC2119]. | |||
2. The SNMP Management Framework | ||||
The SNMP Management Framework presently 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 set of fundamental applications described in RFC 2573 | 2. The Internet-Standard Management Framework | |||
[RFC2573] and the view-based access control mechanism described | ||||
in RFC 2575 [RFC2575]. | ||||
A more detailed introduction to the current SNMP Management Framework | For a detailed overview of the documents that describe the current | |||
can be found in RFC 2570 [RFC2570]. | Internet-Standard Management Framework, please refer to section 7 of | |||
RFC 3410 [RFC3410]. | ||||
Managed objects are accessed via a virtual information store, termed | Managed objects are accessed via a virtual information store, termed | |||
the Management Information Base or MIB. Objects in the MIB are | the Management Information Base or MIB. MIB objects are generally | |||
defined using the mechanisms defined in the SMI. | accessed through the Simple Network Management Protocol (SNMP). | |||
Objects in the MIB are defined using the mechanisms defined in the | ||||
This memo specifies a MIB module that is compliant to the SMIv2. A | Structure of Management Information (SMI). This memo specifies a MIB | |||
MIB conforming to the SMIv1 can be produced through the appropriate | module that is compliant to the SMIv2, which is described in STD 58, | |||
translations. The resulting translated MIB must be semantically | RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 | |||
equivalent, except where objects or events are omitted because no | [RFC2580]. | |||
translation is possible (use of Counter64). Some machine readable | ||||
information in SMIv2 will be converted into textual descriptions in | ||||
SMIv1 during the translation process. However, this loss of machine | ||||
readable information is not considered to change the semantics of the | ||||
MIB. | ||||
3. Overview | 3. Overview | |||
The emergence of IP telephony as an application that allows for voice | The emergence of IP telephony as an application that allows for voice | |||
applications to be run over the same infrastructure as data | applications to be run over the same infrastructure as data | |||
applications led to the emergence of Ethernet IP phones, with similar | applications led to the emergence of Ethernet IP phones, with similar | |||
functions and characteristics as the traditional phones. Powering a | functions and characteristics as the traditional phones. Powering a | |||
phone is one of these functions that are being taken as granted. The | 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, | IEEE 802.3 Working Group initiated a standard work on this subject, | |||
currently known as the IEEE 802.3af work [IEEE-802.3af]. | currently known as the IEEE 802.3af work [IEEE-802.3af]. | |||
skipping to change at page 4, line 4 | skipping to change at page 3, line 17 | |||
only the hardware registers that will allow for a management | only the hardware registers that will allow for a management | |||
interfaces to be built for a powered Ethernet device. The MIB module | interfaces to be built for a powered Ethernet device. The MIB module | |||
defined in this document extends the Ethernet-like Interfaces MIB | defined in this document extends the Ethernet-like Interfaces MIB | |||
[RFC2665] with the management objects required for the management of | [RFC2665] with the management objects required for the management of | |||
the powered Ethernet devices and ports. | the powered Ethernet devices and ports. | |||
The following abbreviations are defined in [IEEE-802.3af] and will be | The following abbreviations are defined in [IEEE-802.3af] and will be | |||
used with the same significance in this document: | used with the same significance in this document: | |||
PSE - Power Sourcing Equipment; | PSE - Power Sourcing Equipment; | |||
PD - Powered Device | PD - Powered Device | |||
4. MIB Structure | 4. MIB Structure | |||
This MIB objects are included in four MIB groups - three of them | This MIB objects are included in three MIB groups. | |||
include MIB tables, and the fourth scalar objects | ||||
The pethPsePortTable defines the objects used for the configuration | The pethPsePortTable defines the objects used for the configuration | |||
and describing the status of ports on a PSE device. Examples of PSE | and describing the status of ports on a PSE device. Examples of PSE | |||
devices are Ethernet switches that support power Ethernet and mid- | devices are Ethernet switches that support power Ethernet and mid- | |||
span boxes. | span boxes. | |||
The pethPdPortTable defines the objects used for the configuration | ||||
and describing the status of ports on a PD device. Examples of PD | ||||
devices are Ethernet phones. | ||||
The pethMainPseObjects MIB group defines the management objects for a | The pethMainPseObjects MIB group defines the management objects for a | |||
managed main power source in a PSE device. Ethernet switches are one | managed main power source in a PSE device. Ethernet switches are one | |||
example of boxes that would support these objects. | example of boxes that would support these objects. | |||
The pethTrapsControlTable includes objects that control the | The pethNotificationsControlTable includes objects that control the | |||
transmission of traps by the agent to a management application. | Transmission of notifications 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 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 possible 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 | ||||
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 to objects pethMainPseMaxVoltage & pethMainPseMinVoltage | ||||
j. Change SYNTAX of pethMainPseUsagePower form INTEGER to Gauge32 | ||||
k. Change SYNTAX of pethMainPseUsageCurrent 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. 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 | ||||
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 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 | 5. Definitions | |||
POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN | POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN | |||
IMPORTS | IMPORTS | |||
MODULE-IDENTITY, mib-2, OBJECT-TYPE, Integer32, | MODULE-IDENTITY, mib-2, OBJECT-TYPE, Integer32, | |||
Gauge32, Counter32, NOTIFICATION-TYPE | Gauge32, Counter32, NOTIFICATION-TYPE | |||
FROM SNMPv2-SMI | FROM SNMPv2-SMI | |||
TruthValue | TruthValue | |||
FROM SNMPv2-TC | FROM SNMPv2-TC | |||
InterfaceIndex | ||||
FROM IF-MIB | ||||
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP | MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP | |||
FROM SNMPv2-CONF; | FROM SNMPv2-CONF; | |||
powerEthernetMIB MODULE-IDENTITY | powerEthernetMIB MODULE-IDENTITY | |||
LAST-UPDATED "200212020000Z" -- December 02, 2002 | LAST-UPDATED "200304250000Z" -- April 25, 2003 | |||
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB | ORGANIZATION "IETF Ethernet Interfaces and Hub MIB | |||
Working Group" | Working Group" | |||
CONTACT-INFO | 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 | Chair: Dan Romascanu | |||
Avaya Inc. | Avaya | |||
Tel: +972-3-645-8414 | Tel: +972-3-645-8414 | |||
Email: dromasca@avaya.com | Email: dromasca@avaya.com | |||
Editor: Avi Berger | Editor: Avi Berger | |||
PowerDsine Inc. | PowerDsine Inc. | |||
Tel: 972-9-7755100 Ext 307 | Tel: 972-9-7755100 Ext 307 | |||
Fax: 972-9-7755120 | Fax: 972-9-7755120 | |||
E-mail: avib@PowerDsine.com | E-mail: avib@PowerDsine.com | |||
" | " | |||
DESCRIPTION | DESCRIPTION | |||
"The MIB module for for managing Powered Devices (PD) or | "The MIB module for managing Power Source Equipment | |||
Power Source Equipment (PSE) working according to the IEEE | (PSE) working according to the IEEE 802.af Powered | |||
802.af Powered Ethernet (DTE Power via MDI) standard. | Ethernet (DTE Power via MDI) standard. | |||
The following terms are used throughout this | The following terms are used throughout this | |||
MIB module. For complete formal definitions, | MIB module. For complete formal definitions, | |||
the IEEE 802.3 standards should be consulted | the IEEE 802.3 standards should be consulted | |||
wherever possible: | wherever possible: | |||
Group - A recommended, but optional, entity | Group - A recommended, but optional, entity | |||
defined by the IEEE 802.3 management standard, | defined by the IEEE 802.3 management standard, | |||
in order to support a modular numbering scheme. | in order to support a modular numbering scheme. | |||
The classical example allows an implementor to | The classical example allows an implementor to | |||
represent field-replaceable units as groups of | represent field-replaceable units as groups of | |||
ports, with the port numbering matching the | ports, with the port numbering matching the | |||
modular hardware implementation. | modular hardware implementation. | |||
Port - This entity identifies the port within the group | Port - This entity identifies the port within the group | |||
for which this entry contains information. The numbering | for which this entry contains information. The numbering | |||
scheme for ports is implementation specific." | scheme for ports is implementation specific. | |||
REVISION "200212020000Z" -- December 02, 2002 | Copyright (c) The Internet Society (2003). This version of | |||
this MIB module is part of RFC yyyy; See the RFC itself | ||||
for full legal notices. | ||||
-- RFC Ed.: replace yyyy with the actual RFC number & remove this notice. | ||||
" | ||||
REVISION "200305210000Z" -- May 21, 2003 | ||||
DESCRIPTION "Initial version, published as RFC yyyy." | DESCRIPTION "Initial version, published as RFC yyyy." | |||
-- RFC Ed.: replace yyyy with actual RFC number & remove this notice | -- RFC Ed.: replace yyyy with actual RFC number & remove this notice | |||
::= { mib-2 XXX } | ::= { mib-2 XXX } | |||
-- RFC Ed.: replace XXX with IANA-assigned number & remove this notice | -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice | |||
pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 0 } | pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 0 } | |||
pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 } | pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 } | |||
pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 2 } | pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 2 } | |||
-- PSE Objects | -- PSE Objects | |||
pethPsePortTable OBJECT-TYPE | pethPsePortTable OBJECT-TYPE | |||
SYNTAX SEQUENCE OF PethPsePortEntry | SYNTAX SEQUENCE OF PethPsePortEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A table of objects that display and control the power | "A table of objects that display and control the power | |||
characteristics power Ethernet ports on a Power Source | characteristics power Ethernet ports on a Power Source | |||
Entity (PSE) device. This group will be implemented in | Entity (PSE) device. This group will be implemented in | |||
managed power Ethernet switches and mid-span devices." | managed power Ethernet switches and mid-span devices. | |||
Values of all read-write objects in this table are | ||||
persistent at restart/reboot." | ||||
::= { pethObjects 1 } | ::= { pethObjects 1 } | |||
pethPsePortEntry OBJECT-TYPE | pethPsePortEntry OBJECT-TYPE | |||
SYNTAX PethPsePortEntry | SYNTAX PethPsePortEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A set of objects that display and control the power | "A set of objects that display and control the power | |||
characteristics of a power Ethernet PSE port." | characteristics of a power Ethernet PSE port." | |||
INDEX { pethPsePortGroupIndex , pethPsePortIndex } | INDEX { pethPsePortGroupIndex , pethPsePortIndex } | |||
skipping to change at page 12, line 6 | skipping to change at page 6, line 4 | |||
pethPsePortEntry OBJECT-TYPE | pethPsePortEntry OBJECT-TYPE | |||
SYNTAX PethPsePortEntry | SYNTAX PethPsePortEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A set of objects that display and control the power | "A set of objects that display and control the power | |||
characteristics of a power Ethernet PSE port." | characteristics of a power Ethernet PSE port." | |||
INDEX { pethPsePortGroupIndex , pethPsePortIndex } | INDEX { pethPsePortGroupIndex , pethPsePortIndex } | |||
::= { pethPsePortTable 1 } | ::= { pethPsePortTable 1 } | |||
PethPsePortEntry ::= SEQUENCE { | PethPsePortEntry ::= SEQUENCE { | |||
pethPsePortGroupIndex | pethPsePortGroupIndex | |||
Integer32, | Integer32, | |||
pethPsePortIndex | pethPsePortIndex | |||
Integer32, | Integer32, | |||
pethPsePortAdminEnable | pethPsePortAdminEnable | |||
INTEGER, | TruthValue, | |||
pethPsePortPowerPairsControlAbility | pethPsePortPowerPairsControlAbility | |||
TruthValue, | TruthValue, | |||
pethPsePortPowerPairs | pethPsePortPowerPairs | |||
INTEGER, | INTEGER, | |||
pethPsePortPowerDetectionControl | ||||
INTEGER, | ||||
pethPsePortDetectionStatus | pethPsePortDetectionStatus | |||
INTEGER, | INTEGER, | |||
pethPsePortPowerPriority | pethPsePortPowerPriority | |||
INTEGER, | INTEGER, | |||
pethPsePortPowerMaintenanceStatus | ||||
INTEGER, | ||||
pethPsePortMPSAbsentCounter | pethPsePortMPSAbsentCounter | |||
Counter32, | Counter32, | |||
pethPsePortOverCurrentCounter | pethPsePortInvalidSignatureCounter | |||
Counter32, | ||||
pethPsePortPowerDeniedCounter | ||||
Counter32, | ||||
pethPsePortOverLoadCounter | ||||
Counter32, | ||||
pethPsePortShortCounter | ||||
Counter32, | Counter32, | |||
pethPsePortType | pethPsePortType | |||
INTEGER, | INTEGER, | |||
pethPsePortPowerClassifications | pethPsePortPowerClassifications | |||
INTEGER | INTEGER | |||
} | } | |||
pethPsePortGroupIndex OBJECT-TYPE | pethPsePortGroupIndex OBJECT-TYPE | |||
SYNTAX Integer32 (1..2147483647) | SYNTAX Integer32 (1..2147483647) | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This variable uniquely identifies the group | "This variable uniquely identifies the group | |||
containing the port to which a power Ethernet PSE is connected. | containing the port to which a power Ethernet PSE is | |||
Group means box in the stack, module in a rack and the value 1 | connected. Group means box in the stack, module in a | |||
MUST be used for non-modular devices . | rack and the value 1 MUST be used for non-modular devices. | |||
Furthermore, the same value MUST be used in this variable, | ||||
pethPseMidSpanGroupCapacity is the number of Mid-Span PSE | pethMainPseGroupIndex, and pethNotificationControlGroupIndex | |||
groups that can be contained within the Mid-Span PSE." | to refer to a given box in a stack or module in the rack." | |||
::= { pethPsePortEntry 1 } | ::= { pethPsePortEntry 1 } | |||
pethPsePortIndex OBJECT-TYPE | pethPsePortIndex OBJECT-TYPE | |||
SYNTAX Integer32 (1..2147483647) | SYNTAX Integer32 (1..2147483647) | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This variable uniquely identifies the power Ethernet PSE | "This variable uniquely identifies the power Ethernet PSE | |||
port within group pethPseGroupIndex to which the | port within group pethPsePortGroupIndex to which the | |||
power Ethernet PSE entry is connected." | power Ethernet PSE entry is connected." | |||
::= { pethPsePortEntry 2 } | ::= { pethPsePortEntry 2 } | |||
pethPsePortAdminEnable OBJECT-TYPE | pethPsePortAdminEnable OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX TruthValue | |||
enable(1), | ||||
disable(2) | ||||
} | ||||
MAX-ACCESS read-write | MAX-ACCESS read-write | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Enables power supply on this port. | "true (1) An interface which can provide the PSE functions. | |||
Setting this object at a value enable(1) enables power | false(2) The interface will act as it would if it had no PSE | |||
and detection mechanism for this port. | function." | |||
Setting this object at a value disable(2) disables power | REFERENCE | |||
for this port." | "IEEE Draft P802.3af/D4.3 Section 30.9.1.1.2 aPSEAdminState" | |||
::= { pethPsePortEntry 3 } | ::= { pethPsePortEntry 3 } | |||
pethPsePortPowerPairsControlAbility OBJECT-TYPE | pethPsePortPowerPairsControlAbility OBJECT-TYPE | |||
SYNTAX TruthValue | SYNTAX TruthValue | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Describes the capability of controlling the power pairs | "Describes the capability of controlling the power pairs | |||
functionality to switch pins for sourcing power. | functionality to switch pins for sourcing power. | |||
The value true indicate that the device has the capability | The value true indicate that the device has the capability | |||
to control the power pairs" | to control the power pairs. When false the PSE Pinout | |||
Alternative used cannot be controlled through the | ||||
PethPsePortAdminEnabe attribute." | ||||
REFERENCE | ||||
"IEEE Draft P802.3af/D4.3 Section 30.9.1.1.3 | ||||
aPSEPowerPairsControlAbility" | ||||
::= { pethPsePortEntry 4 } | ::= { pethPsePortEntry 4 } | |||
pethPsePortPowerPairs OBJECT-TYPE | pethPsePortPowerPairs OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
signal(1), | signal(1), | |||
spare(2) | spare(2) | |||
} | } | |||
MAX-ACCESS read-write | MAX-ACCESS read-write | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Describes or controls the pairs in use. If the value of | "Describes or controls the pairs in use. If the value of | |||
pethPsePortPowerPairsControl is true, this object is | pethPsePortPowerPairsControl is true, this object is | |||
writable. | writable. | |||
A value of signal(1) means that the signal pairs | A value of signal(1) menas that the signal pairs | |||
only are in use. | only are in use. | |||
A value of spare(2) means that the spare pairs | A value of spare(2) means that the spare pairs | |||
only are in use." | only are in use." | |||
REFERENCE | ||||
"IEEE Draft P802.3af/D4.3 Section 30.9.1.1.4 aPSEPowerPairs" | ||||
::= { pethPsePortEntry 5 } | ::= { 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 | pethPsePortDetectionStatus OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
disabled(1), | disabled(1), | |||
searching(2), | searching(2), | |||
deliveringPower(4), | deliveringPower(3), | |||
fault(5), | fault(4), | |||
test(7), | test(5), | |||
denyLowPriority(8) | otherFault(6) | |||
} | } | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Describes the operational status of the port PD detection. | "Describes the operational status of the port PD detection. | |||
A value of disabled(1)- indicates that the PSE State diagram is in | A value of disabled(1)- indicates that the PSE State diagram | |||
the state IDLE | is in the state DISABLED. | |||
A value of searching(2)- indicates that the PSE State diagram is in | A value of deliveringPower(3) - indicates that the PSE State | |||
the state DETECTION, CLASSIFICATION, SIGNATURE_INVALID or BACKOFF. | diagram is in the state POWER_ON for a duration greater than | |||
A value of deliveringPower(4) - indicates that the PSE State diagram | tlim max (see IEEE Drafts P802.3af/D4.3 Table 33-5 tlim). | |||
is in the state POWER_UP, POWER_ON or POWER_OFF. | A value of fault(4) - indicates that the PSE State diagram is | |||
A value of fault(5) - indicates that the PSE State diagram is in the | in the state TEST_ERROR. | |||
state TEST_ERROR or the state IDLE due to the variable error | A value of test(5) - indicates that the PSE State diagram is | |||
condition. | in the state TEST_MODE. | |||
Faults detected are vendor specific. | A value of otherFault(6) - indicates that the PSE State diagram | |||
A value of test(7) - indicates that the PSE State diagram is in the | is in the state IDLE due to the variable error_conditions. | |||
state TEST_MODE. | A value of searching(2)- indicates the PSE State diagram is | |||
A value of denyLowPriority(8) indicates that the port was | in a state other than those listed above." | |||
disabled by the power management system, in order to keep | REFERENCE | |||
active higher priority ports. | "IEEE Draft P802.3af/D4.3 Section 30.9.1.1.5 | |||
" | aPSEPowerDetectionStatus" | |||
::= { pethPsePortEntry 7 } | ::= { pethPsePortEntry 7 } | |||
pethPsePortPowerPriority OBJECT-TYPE | pethPsePortPowerPriority OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
critical(1), | critical(1), | |||
high(2), | high(2), | |||
low(3) | low(3) | |||
} | } | |||
MAX-ACCESS read-write | MAX-ACCESS read-write | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This object controls the priority of the port from the point | "This object controls the priority of the port from the point | |||
of view of a power management algorithm. The priority that | of view of a power management algorithm. The priority that | |||
is set by this variable could be used by a control mechanism | is set by this variable could be used by a control mechanism | |||
that prevents over current situations by disconnecting first | that prevents over current situations by disconnecting first | |||
ports with lower power priority. Ports that connect devices | ports with lower power priority. Ports that connect devices | |||
critical to the operation of the network - like the E911 | critical to the operation of the network - like the E911 | |||
telephones ports - should be set to higher priority." | telephones ports - should be set to higher priority." | |||
::= { pethPsePortEntry 8 } | ::= { pethPsePortEntry 8 } | |||
pethPsePortPowerMaintenanceStatus OBJECT-TYPE | ||||
SYNTAX INTEGER { | ||||
ok(1), | ||||
underCurrent(2), | ||||
mPSAbsent(3) | ||||
} | ||||
MAX-ACCESS read-only | ||||
STATUS current | ||||
DESCRIPTION | ||||
"The value ok(1) indicates the Power Maintenance | ||||
Signature is present and the overcurrent condition has not been | ||||
detected. | ||||
The value overCurrent (2) indicates an overcurrent condition | ||||
has been detected. | ||||
The value mPSAbsent(3) indicates that the Power Maintenance | ||||
Signature is absent." | ||||
REFERENCE "[IEEE Draft P802.3af/D4.0, November, 2002, 30.9.1.1.8 | ||||
aPSEPowerMaintenanceStatus]" | ||||
::= { pethPsePortEntry 10 } | ||||
pethPsePortMPSAbsentCounter OBJECT-TYPE | pethPsePortMPSAbsentCounter OBJECT-TYPE | |||
SYNTAX Counter32 | SYNTAX Counter32 | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Counts the number of times that the | "This counter is incremented when the PSE state diagram | |||
pethPsePortPowerMaintenanceStatus attribute changes from any | transitions directly from the state POWER_ON to the state | |||
value to the value mPSAbsent(3)." | IDLE due to tmpdo_timer_done being asserted." | |||
REFERENCE "[IEEE Draft P802.3af/D4.0, November, 2002, object 30.9.1.1.9 | REFERENCE | |||
aPSEUnderCurrentCounter]" | "IEEE Draft P802.3af/D4.3 Section 30.9.1.1.11 | |||
aPSEMPSAbsentCounter" | ||||
::= { pethPsePortEntry 11 } | ::= { pethPsePortEntry 11 } | |||
pethPsePortOverCurrentCounter OBJECT-TYPE | ||||
SYNTAX Counter32 | ||||
MAX-ACCESS read-only | ||||
STATUS current | ||||
DESCRIPTION | ||||
"Counts the number of times that the aPSEPowerCurrentStatus | ||||
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]" | ||||
::= { pethPsePortEntry 12 } | ||||
pethPsePortType OBJECT-TYPE | pethPsePortType OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
other(1), | other(1), | |||
telephone(2), | telephone(2), | |||
webcam(3), | webcam(3), | |||
wireless(4) | wireless(4) | |||
} | } | |||
MAX-ACCESS read-write | MAX-ACCESS read-write | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A manager will set the value of this variable to a value | "A manager will set the value of this variable to indicate | |||
that indicates the type of the device that is connected | the type of powered device that is connected to the port." | |||
to theport. This value can be the result of the mapping | ||||
the address of the station connected to the port and of | ||||
the value of the pethPdPortType of the respective PD port." | ||||
::= { pethPsePortEntry 13 } | ::= { pethPsePortEntry 13 } | |||
pethPsePortPowerClassifications OBJECT-TYPE | pethPsePortPowerClassifications OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
class0(1), | class0(1), | |||
class1(2), | class1(2), | |||
class2(3), | class2(3), | |||
class3(4), | class3(4), | |||
class4(5) | class4(5) | |||
} | } | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Classification is a way to tag different terminals on the | "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, | Devices such as IP telephones, WLAN access points and others, | |||
will be classified according to their power requirements. | will be classified according to their power requirements. | |||
The value is only valid while a valid PD is being detected as | The meaning of the classification labels is defined in the | |||
indicated by the attribute pethPsePortDetectionStatus reporting | IEEE specification. | |||
the value or deliveringPower(4)." | ||||
REFERENCE "[IEEE Draft P802.3af/D4.0, November, 2002, | ||||
object 30.9.1.1.7 aPSEPowerClassification]" | ||||
::= { pethPsePortEntry 14 } | ||||
-- PD Port table | This variable is valid only while a PD is being powered, | |||
that is, while the attribute pethPsePortDetectionStatus | ||||
is reporting the enumeration deliveringPower." | ||||
REFERENCE | ||||
"IEEE Draft P802.3af/D4.3 Section 30.9.1.1.6 | ||||
aPSEPowerClassification" | ||||
::= { pethPsePortEntry 14 } | ||||
pethPdPortTable OBJECT-TYPE | pethPsePortInvalidSignatureCounter OBJECT-TYPE | |||
SYNTAX SEQUENCE OF PethPdPortEntry | SYNTAX Counter32 | |||
MAX-ACCESS not-accessible | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A table of objects that display and control the power | "This counter is incremented when the PSE state diagram | |||
characteristics power Ethernet ports on a Powered | enters the state SIGNATURE_INVALID." | |||
Device(PD) device. This group will be implemented in | REFERENCE | |||
managed powered and mid-span devices." | "IEEE Draft P802.3af/D4.3 Section 30.9.1.1.7 | |||
::= { pethObjects 2 } | aPSEInvalidSignatureCounter" | |||
::= { pethPsePortEntry 15 } | ||||
pethPdPortEntry OBJECT-TYPE | pethPsePortPowerDeniedCounter OBJECT-TYPE | |||
SYNTAX PethPdPortEntry | SYNTAX Counter32 | |||
MAX-ACCESS not-accessible | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A set of objects that display and control the power | "This counter is incremented when the PSE state diagram | |||
characteristics of a Powered Device port." | enters the state POWER_DENIED." | |||
INDEX { pethPdPortIndex } | REFERENCE | |||
::= { pethPdPortTable 1 } | "IEEE Draft P802.3af/D4.3 Section 30.9.1.1.8 | |||
aPSEPowerDeniedCounter" | ||||
PethPdPortEntry ::= SEQUENCE { | ::= { pethPsePortEntry 16 } | |||
pethPdPortIndex | ||||
InterfaceIndex, | ||||
pethPdPortAdminEnable | ||||
INTEGER | ||||
} | ||||
pethPdPortIndex OBJECT-TYPE | pethPsePortOverLoadCounter OBJECT-TYPE | |||
SYNTAX InterfaceIndex | SYNTAX Counter32 | |||
MAX-ACCESS not-accessible | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"An index value that uniquely identifies an | "This counter is incremented when the PSE state diagram | |||
interface to a PD device. The | enters the state ERROR_DELAY_OVER." | |||
interface identified by a particular value of | REFERENCE | |||
this index is the same interface as identified | "IEEE Draft P802.3af/D4.3 Section 30.9.1.1.9 | |||
by the same value of ifIndex. The mapping | aPSEOverLoadCounter" | |||
between the ifIndex values and the numbering of | ::= { pethPsePortEntry 17 } | |||
the port on the device is an implementation | ||||
issue." | ||||
::= { pethPdPortEntry 1 } | ||||
pethPdPortAdminEnable OBJECT-TYPE | pethPsePortShortCounter OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX Counter32 | |||
enable(1), | MAX-ACCESS read-only | |||
disable(2) | ||||
} | ||||
MAX-ACCESS read-write | ||||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This value identifies the operational state of the PD functions. | "This counter is incremented when the PSE state diagram | |||
An interface which can provide the PD functions will be enabled | enters the state ERROR_DELAY_SHORT." | |||
to do so when this attribute has the value enable. When this | REFERENCE | |||
attribute has the value disable the interface will act | "IEEE Draft P802.3af/D4.3 Section 30.9.1.1.10 | |||
as it would if it had no PD function." | aPSEShortCounter" | |||
::= { pethPdPortEntry 2 } | ::= { pethPsePortEntry 18 } | |||
-- Main PSE Objects | -- Main PSE Objects | |||
pethMainPseObjects OBJECT IDENTIFIER ::= { pethObjects 3 } | pethMainPseObjects OBJECT IDENTIFIER ::= { pethObjects 3 } | |||
pethMainPseTable OBJECT-TYPE | pethMainPseTable OBJECT-TYPE | |||
SYNTAX SEQUENCE OF PethMainPseEntry | SYNTAX SEQUENCE OF PethMainPseEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A table of objects that display and control the Main power | "A table of objects that display and control attributes | |||
on a PSE device. Example - an Ethernet switch midspan device can | of the main power source in a PSE device. Ethernet | |||
control an Ethnternet port and the Main Power supply unit's." | 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." | ||||
::= { pethMainPseObjects 1 } | ::= { pethMainPseObjects 1 } | |||
pethMainPseEntry OBJECT-TYPE | pethMainPseEntry OBJECT-TYPE | |||
SYNTAX PethMainPseEntry | SYNTAX PethMainPseEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A set of objects that display and control the Main power | "A set of objects that display and control the Main | |||
of a PSE. " | power of a PSE. " | |||
INDEX { pethMainPseGroupIndex } | INDEX { pethMainPseGroupIndex } | |||
::= { pethMainPseTable 1 } | ::= { pethMainPseTable 1 } | |||
PethMainPseEntry ::= SEQUENCE { | PethMainPseEntry ::= SEQUENCE { | |||
pethMainPseGroupIndex | pethMainPseGroupIndex | |||
Integer32, | Integer32, | |||
pethMainPsePower | pethMainPsePower | |||
Gauge32 , | Gauge32 , | |||
pethMainPseOperStatus | pethMainPseOperStatus | |||
INTEGER, | INTEGER, | |||
skipping to change at page 19, line 28 | skipping to change at page 12, line 20 | |||
Gauge32, | Gauge32, | |||
pethMainPseUsageThreshold | pethMainPseUsageThreshold | |||
Integer32 | Integer32 | |||
} | } | |||
pethMainPseGroupIndex OBJECT-TYPE | pethMainPseGroupIndex OBJECT-TYPE | |||
SYNTAX Integer32 (1..2147483647) | SYNTAX Integer32 (1..2147483647) | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This variable uniquely identifies the group to which | "This variable uniquely identifies the group to which | |||
power Ethernet PSE is connected.Group means (box in the stack, | power Ethernet PSE is connected. Group means (box in | |||
module in a rack) and the value 1 MUST be used for non-modular | the stack, module in a rack) and the value 1 MUST be | |||
devices " | used for non-modular devices. Furthermore, the same | |||
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 } | ::= { pethMainPseEntry 1 } | |||
pethMainPsePower OBJECT-TYPE | pethMainPsePower OBJECT-TYPE | |||
SYNTAX Gauge32 (1..65535) | SYNTAX Gauge32 (1..65535) | |||
UNITS "Watts" | UNITS "Watts" | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The nominal power of the PSE expressed in Watts." | "The nominal power of the PSE expressed in Watts." | |||
::= { pethMainPseEntry 2 } | ::= { pethMainPseEntry 2 } | |||
skipping to change at page 20, line 36 | skipping to change at page 13, line 31 | |||
-- Notification Control Objects | -- Notification Control Objects | |||
pethNotificationControl OBJECT IDENTIFIER ::= { pethObjects 4 } | pethNotificationControl OBJECT IDENTIFIER ::= { pethObjects 4 } | |||
pethNotificationControlTable OBJECT-TYPE | pethNotificationControlTable OBJECT-TYPE | |||
SYNTAX SEQUENCE OF PethNotificationControlEntry | SYNTAX SEQUENCE OF PethNotificationControlEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A table of objects that display and control the Notification | "A table of objects that display and control the | |||
on a PSE device." | Notification on a PSE device. | |||
Values of all read-write objects in this table are | ||||
persistent at restart/reboot." | ||||
::= { pethNotificationControl 1 } | ::= { pethNotificationControl 1 } | |||
pethNotificationControlEntry OBJECT-TYPE | pethNotificationControlEntry OBJECT-TYPE | |||
SYNTAX PethNotificationControlEntry | SYNTAX PethNotificationControlEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A set of objects that control the Notification events." | "A set of objects that control the Notification events." | |||
INDEX { pethNotificationControlGroupIndex } | INDEX { pethNotificationControlGroupIndex } | |||
::= { pethNotificationControlTable 1 } | ::= { pethNotificationControlTable 1 } | |||
skipping to change at page 21, line 4 | skipping to change at page 13, line 45 | |||
::= { pethNotificationControl 1 } | ::= { pethNotificationControl 1 } | |||
pethNotificationControlEntry OBJECT-TYPE | pethNotificationControlEntry OBJECT-TYPE | |||
SYNTAX PethNotificationControlEntry | SYNTAX PethNotificationControlEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A set of objects that control the Notification events." | "A set of objects that control the Notification events." | |||
INDEX { pethNotificationControlGroupIndex } | INDEX { pethNotificationControlGroupIndex } | |||
::= { pethNotificationControlTable 1 } | ::= { pethNotificationControlTable 1 } | |||
PethNotificationControlEntry ::= SEQUENCE { | PethNotificationControlEntry ::= SEQUENCE { | |||
pethNotificationControlGroupIndex | pethNotificationControlGroupIndex | |||
Integer32, | Integer32, | |||
pethNotificationControlEnable | pethNotificationControlEnable | |||
INTEGER | TruthValue | |||
} | } | |||
pethNotificationControlGroupIndex OBJECT-TYPE | pethNotificationControlGroupIndex OBJECT-TYPE | |||
SYNTAX Integer32 (1..2147483647) | SYNTAX Integer32 (1..2147483647) | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This variable uniquely identifies the group. Group means | "This variable uniquely identifies the group. Group | |||
box in the stack, module in a rack and it is RECOMENDED | means box in the stack, module in a rack and the value | |||
that the value 1 be used for non-modular devices " | 1 MUST be used for non-modular devices. Furthermore, | |||
the same value MUST be used in this variable, | ||||
pethPsePortGroupIndex, and | ||||
pethMainPseGroupIndex to refer to a given box in a | ||||
stack or module in a rack. " | ||||
::= { pethNotificationControlEntry 1 } | ::= { pethNotificationControlEntry 1 } | |||
pethNotificationControlEnable OBJECT-TYPE | pethNotificationControlEnable OBJECT-TYPE | |||
SYNTAX INTEGER | SYNTAX TruthValue | |||
{ | ||||
enable(1), | ||||
disable(2) | ||||
} | ||||
MAX-ACCESS read-write | MAX-ACCESS read-write | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Enable Notification from Agent" | "This object controls, on a per-group basis, whether | |||
or not notifications from the agent are enabled. The | ||||
value true(1) means that notifications are enabled; the | ||||
value false(2) means that they are not." | ||||
::= { pethNotificationControlEntry 2 } | ::= { pethNotificationControlEntry 2 } | |||
-- | -- | |||
-- Notifications Section | -- Notifications Section | |||
-- | -- | |||
-- | -- | |||
pethPsePortOnOffNotification NOTIFICATION-TYPE | pethPsePortOnOffNotification NOTIFICATION-TYPE | |||
OBJECTS { pethPsePortDetectionStatus } | OBJECTS { pethPsePortDetectionStatus } | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" This Notification indicates if Pse Port is delivering or | " This Notification indicates if Pse Port is delivering or | |||
not power to the PD. This Notification SHOULD be sent on | not power to the PD. This Notification SHOULD be sent on | |||
every status change except in the searching mode." | every status change except in the searching mode. | |||
At least 500 msec must elapse between notifications | ||||
being emitted by the same object instance." | ||||
::= { pethNotifications 1 } | ::= { pethNotifications 1 } | |||
pethPsePortPowerMaintenanceStatusNotification NOTIFICATION-TYPE | ||||
OBJECTS { pethPsePortPowerMaintenanceStatus } | ||||
STATUS current | ||||
DESCRIPTION | ||||
" This Notification indicates a Port Change Status and it | ||||
SHOULD be sent on every status change." | ||||
::= { pethNotifications 2 } | ||||
pethMainPowerUsageOnNotification NOTIFICATION-TYPE | pethMainPowerUsageOnNotification NOTIFICATION-TYPE | |||
OBJECTS { pethMainPseConsumptionPower } | OBJECTS { pethMainPseConsumptionPower } | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" This Notification indicate PSE Threshold usage indication is | " This Notification indicate PSE Threshold usage | |||
on, the usage power is above the threshold." | indication is on, the usage power is above the | |||
threshold. At least 500 msec must elapse between | ||||
notifications being emitted by the same object | ||||
instance." | ||||
::= { pethNotifications 4 } | ::= { pethNotifications 4 } | |||
pethMainPowerUsageOffNotification NOTIFICATION-TYPE | pethMainPowerUsageOffNotification NOTIFICATION-TYPE | |||
OBJECTS { pethMainPseConsumptionPower } | OBJECTS { pethMainPseConsumptionPower } | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
" This Notification indicate PSE Threshold usage indication | " This Notification indicates PSE Threshold usage indication | |||
off, the usage power is below the threshold." | off, the usage power is below the threshold. | |||
At least 500 msec must elapse between notifications being | ||||
emitted by the same object instance." | ||||
::= { pethNotifications 5 } | ::= { pethNotifications 5 } | |||
-- | -- | |||
-- Conformance Section | -- Conformance Section | |||
-- | -- | |||
pethCompliances OBJECT IDENTIFIER ::= { pethConformance 1 } | pethCompliances OBJECT IDENTIFIER ::= { pethConformance 1 } | |||
pethGroups OBJECT IDENTIFIER ::= { pethConformance 2 } | pethGroups OBJECT IDENTIFIER ::= { pethConformance 2 } | |||
pethCompliance MODULE-COMPLIANCE | pethCompliance MODULE-COMPLIANCE | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Describes the requirements for conformance to the | "Describes the requirements for conformance to the | |||
Power Ethernet MIB." | Power Ethernet MIB." | |||
MODULE -- this module | MODULE -- this module | |||
GROUP pethPsePortGroup | MANDATORY-GROUPS { pethPsePortGroup, | |||
DESCRIPTION | pethPsePortNotificationGroup, | |||
"The pethPsePortGroup is mandatory for systems which | pethNotificationControlGroup | |||
implement PSE ports." | } | |||
GROUP pethPdPortGroup | ||||
DESCRIPTION | ||||
"The pethPdPortGroup is mandatory for systems which | ||||
implement PD Ports." | ||||
GROUP pethMainPseGroup | GROUP pethMainPseGroup | |||
DESCRIPTION | DESCRIPTION | |||
"The pethMainPseGroup is mandatory for systems which | "The pethMainPseGroup is mandatory for PSE systems | |||
implement main power supply within a PSE Device." | that implement a main power supply." | |||
GROUP pethNotificationControlGroup | GROUP pethMainPowerNotificationGroup | |||
DESCRIPTION | DESCRIPTION | |||
"The pethNotificationControlGroup is mandatory for systems which | "The pethMainPowerNotificationGroup is mandatory for | |||
implement PSE ports." | PSE systems that implement a main power supply." | |||
::= { pethCompliances 1 } | ::= { pethCompliances 1 } | |||
pethPseCompliance MODULE-COMPLIANCE | pethPseCompliance MODULE-COMPLIANCE | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Describes the requirements for conformance to the PSE and MID- | "Describes the requirements for conformance to the | |||
Span." | PSE and MID-Span." | |||
MODULE -- this module | MODULE -- this module | |||
MANDATORY-GROUPS {pethPsePortGroup, pethMainPseGroup,pethNotificationControlGroup} | MANDATORY-GROUPS {pethPsePortGroup, pethMainPseGroup,pethNotificationControlGroup, | |||
pethPsePortNotificationGroup,pethMainPowerNotificationGroup} | ||||
::= { pethCompliances 2 } | ::= { pethCompliances 2 } | |||
pethPdCompliance MODULE-COMPLIANCE | ||||
STATUS current | ||||
DESCRIPTION | ||||
"Describes the requirements for conformance to the PD." | ||||
MODULE -- this module | ||||
MANDATORY-GROUPS {pethPdPortGroup} | ||||
::= { pethCompliances 3} | ||||
pethPsePortGroup OBJECT-GROUP | pethPsePortGroup OBJECT-GROUP | |||
OBJECTS { | OBJECTS { | |||
pethPsePortAdminEnable, | pethPsePortAdminEnable, | |||
pethPsePortPowerPairsControlAbility, | pethPsePortPowerPairsControlAbility, | |||
pethPsePortPowerDetectionControl, | ||||
pethPsePortPowerPairs, | pethPsePortPowerPairs, | |||
pethPsePortDetectionStatus, | pethPsePortDetectionStatus, | |||
pethPsePortPowerPriority, | pethPsePortPowerPriority, | |||
pethPsePortPowerMaintenanceStatus , | ||||
pethPsePortMPSAbsentCounter, | pethPsePortMPSAbsentCounter, | |||
pethPsePortOverCurrentCounter, | pethPsePortInvalidSignatureCounter, | |||
pethPsePortPowerDeniedCounter, | ||||
pethPsePortOverLoadCounter, | ||||
pethPsePortShortCounter, | ||||
pethPsePortType, | pethPsePortType, | |||
pethPsePortPowerClassifications | pethPsePortPowerClassifications | |||
} | } | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The pethPsePortGroup is mandatory for systems which | "PSE Port objects." | |||
implement PSE ports." | ||||
::= { pethGroups 1 } | ::= { pethGroups 1 } | |||
pethPdPortGroup OBJECT-GROUP | ||||
OBJECTS { | ||||
pethPdPortAdminEnable | ||||
} | ||||
STATUS current | ||||
DESCRIPTION | ||||
"The pethPdPortGroup is mandatory for systems which | ||||
implement PD Ports." | ||||
::= { pethGroups 2 } | ||||
pethMainPseGroup OBJECT-GROUP | pethMainPseGroup OBJECT-GROUP | |||
OBJECTS { | OBJECTS { | |||
pethMainPsePower, | pethMainPsePower, | |||
pethMainPseOperStatus, | pethMainPseOperStatus, | |||
pethMainPseConsumptionPower, | pethMainPseConsumptionPower, | |||
pethMainPseUsageThreshold | pethMainPseUsageThreshold | |||
} | } | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Main PSE Objects. " | "Main PSE Objects. " | |||
skipping to change at page 24, line 34 | skipping to change at page 17, line 14 | |||
pethNotificationControlGroup OBJECT-GROUP | pethNotificationControlGroup OBJECT-GROUP | |||
OBJECTS { | OBJECTS { | |||
pethNotificationControlEnable | pethNotificationControlEnable | |||
} | } | |||
STATUS current | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Notification Control Objects. " | "Notification Control Objects. " | |||
::= { pethGroups 4 } | ::= { pethGroups 4 } | |||
pethPsePortNotificationGroup NOTIFICATION-GROUP | pethPsePortNotificationGroup NOTIFICATION-GROUP | |||
NOTIFICATIONS { pethPsePortOnOffNotification, | NOTIFICATIONS { pethPsePortOnOffNotification} | |||
pethPsePortPowerMaintenanceStatusNotification} | ||||
STATUS current | STATUS current | |||
DESCRIPTION "Pse Notification indications" | DESCRIPTION "Pse Port Notifications." | |||
::= { pethCompliances 4 } | ::= { pethCompliances 4 } | |||
pethMainPowerNotificationGroup NOTIFICATION-GROUP | pethMainPowerNotificationGroup NOTIFICATION-GROUP | |||
NOTIFICATIONS { pethMainPowerUsageOnNotification, | NOTIFICATIONS { pethMainPowerUsageOnNotification, | |||
pethMainPowerUsageOffNotification} | pethMainPowerUsageOffNotification} | |||
STATUS current | STATUS current | |||
DESCRIPTION "Pse Notification indications" | DESCRIPTION "Main PSE Notifications." | |||
::= { pethCompliances 5 } | ::= { pethCompliances 5 } | |||
END | END | |||
6. Acknowledgements | ||||
8. Normative References | 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. | ||||
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture | 7. Normative References | |||
for Describing SNMP Management Frameworks", RFC 2571, April | ||||
1999. | [RFC2026] Bradner, S., "The Internet Standards Process - Revision | |||
3", BCP 9, RFC 2026, October 1996. | ||||
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., | [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., | |||
Rose, M., and S. Waldbusser, "Structure of Management | Rose, M. and S. Waldbusser, "Structure of Management | |||
Information Version 2 (SMIv2)", STD 58, RFC 2578, April | Information Version 2 (SMIv2)", STD 58, RFC 2578, April | |||
1999. | 1999. | |||
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., | [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., | |||
Rose, M., and S. Waldbusser, "Textual Conventions for | Rose, M. and S. Waldbusser, "Textual Conventions for | |||
SMIv2", STD 58, RFC 2579, April 1999. | SMIv2", STD 58, RFC 2579, April 1999. | |||
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., | [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., | |||
Rose, M., and S. Waldbusser, "Conformance Statements for | Rose, M. and S. Waldbusser, "Conformance Statements for | |||
SMIv2", STD 58, RFC 2580, April 1999. | SMIv2", STD 58, RFC 2580, April 1999. | |||
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message | ||||
Processing and Dispatching for the Simple Network Management | ||||
Protocol (SNMP)", RFC 2572, April 1999. | ||||
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model | ||||
(USM) for version 3 of the Simple Network Management | ||||
Protocol (SNMPv3)", RFC 2574, April 1999. | ||||
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", | ||||
RFC 2573, April 1999. | ||||
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based | ||||
Access Control Model (VACM) for the Simple Network | ||||
Management Protocol (SNMP)", RFC 2575, April 1999. | ||||
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, | ||||
"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 | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
Requirement Levels", BCP 14, RFC 2119, March 1997. | Requirement Levels", BCP 14, RFC 2119, March 1997. | |||
[RFC2665] Flick, J., and J. Johnson, "Definitions of Managed Objects | [RFC2665] Flick, J., and J. Johnson, "Definitions of Managed | |||
for the Ethernet-like Interface Types", RFC 2665, August 1999. | 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 D4.0, | ||||
December 2002. | ||||
9. Informative References | ||||
[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification | ||||
of Management 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 | NOTE - This RFC is under revision by the WG, and may be obsolete by | |||
Network Management Protocol", STD 15, RFC 1157, May 1990. | the time of the publication. The RFC editor should replace it with | |||
the revised version, if available. | ||||
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, | [IEEE-802.3af] IEEE 802.3af Working Group, "Data Terminal Equipment | |||
"Introduction to Community-based SNMPv2", RFC 1901, January | (DTE)Power via Media Dependent Interface (MDI)", Draft D4.3, | |||
1996. | April 2003. | |||
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, | NOTE - This normative reference will be replaced with the IEEE 802.3af | |||
"Transport Mappings for Version 2 of the Simple Network | Standard as soon as the IEEE will ratify it (expected date - July 2003) | |||
Management Protocol (SNMPv2)", RFC 1906, January 1996. | ||||
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, | 8. Informative References | |||
"Protocol Operations for Version 2 of the Simple Network | ||||
Management Protocol (SNMPv2)", RFC 1905, January 1996. | ||||
[PWR-MIB] Romascanu, D., " Power Ethernet (DTE Power via MDI) MIB", | [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, | |||
Internet-Draft, draft-romascanu-hubmib-power-ethernet-mib-00.txt, | "Introduction and Applicability Statements for Internet- | |||
June 2002. | Standard Management Framework", RFC 3410, December 2002 | |||
10.Intellectual Property | 9.Intellectual Property | |||
The IETF takes no position regarding the validity or scope of any | The IETF takes no position regarding the validity or scope of any | |||
intellectual property or other rights that might be claimed to | intellectual property or other rights that might be claimed to | |||
pertain to the implementation or use of the technology described in | pertain to the implementation or use of the technology described in | |||
this document or the extent to which any license under such rights | this document or the extent to which any license under such rights | |||
might or might not be available; neither does it represent that it | might or might not be available; neither does it represent that it | |||
has made any effort to identify any such rights. Information on the | has made any effort to identify any such rights. Information on the | |||
IETF's procedures with respect to rights in standards-track and | IETF's procedures with respect to rights in standards-track and | |||
standards-related documentation can be found in BCP-11. Copies of | standards-related documentation can be found in BCP-11. Copies of | |||
claims of rights made available for publication and any assurances of | claims of rights made available for publication and any assurances of | |||
skipping to change at page 27, line 8 | skipping to change at page 18, line 51 | |||
obtain a general license or permission for the use of such | obtain a general license or permission for the use of such | |||
proprietary rights by implementors or users of this specification can | proprietary rights by implementors or users of this specification can | |||
be obtained from the IETF Secretariat. | be obtained from the IETF Secretariat. | |||
The IETF invites any interested party to bring to its attention any | The IETF invites any interested party to bring to its attention any | |||
copyrights, patents or patent applications, or other proprietary | copyrights, patents or patent applications, or other proprietary | |||
rights which may cover technology that may be required to practice | rights which may cover technology that may be required to practice | |||
this standard. Please address the information to the IETF Executive | this standard. Please address the information to the IETF Executive | |||
Director. | Director. | |||
11. Security Considerations | 10. Security Considerations | |||
There are a number of management objects defined in this MIB module | ||||
with a MAX-ACCESS clause of read-write. 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 management objects defined in this MIB | Setting the following object to incorrect values can result in | |||
that have a MAX-ACCESS clause of read-write and/or read-create. | improper operation of the PSE, including the possibility that the | |||
Such objects may be considered sensitive or vulnerable in some | PD does not receive power from the PSE port: | |||
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 | pethPsePortAdminEnable | |||
contain sensitive information. These are: | pethPsePortPowerPairs | |||
pethPsePortPowerPriority | ||||
pethPsePortType | ||||
Setting the following objects to incorrect values can result in an | ||||
excessive number of traps being sent to network management stations: | ||||
pethMainPseUsageThreshold | ||||
pethNotificationControlEnable | ||||
Some of the readable objects in this MIB module (i.e., objects with a | ||||
MAX-ACCESS other than not-accessible) may be considered sensitive or | ||||
vulnerable in some network environments. These are: | ||||
pethPsePortPowerPairsControlAbility | pethPsePortPowerPairsControlAbility | |||
pethPsePortPowerPriority | pethPsePortPowerPriority | |||
pethPsePortPowerClassifications | pethPsePortPowerClassifications | |||
It is thus important to control even GET access to these objects | It is thus important to control even GET and/or NOTIFY access to | |||
and possibly to even encrypt the values of these object when | these objects and possibly to even encrypt their values when sending | |||
sending them over the network via SNMP. Not all versions of | them over the network via SNMP. | |||
SNMP provide features for such a secure environment. | ||||
SNMPv1 by itself is not a secure environment. Even if the | SNMP versions prior to SNMPv3 did not include adequate security. | |||
network itself is secure (for example by using IPSec), even then, | Even if the network itself is secure (for example by using IPSec), | |||
there is no control as to who on the secure network is allowed | even then, there is no control as to who on the secure network is | |||
to access and GET/SET (read/change/create/delete) the objects in | allowed to access and GET/SET (read/change/create/delete) the objects | |||
this MIB. | in this MIB module. | |||
It is RECOMMENDED that the implementers consider the security | It is RECOMMENDED that implementers consider the security features as | |||
features as provided by the SNMPv3 framework. Specifically, the | provided by the SNMPv3 framework (see [RFC3410], section 8), | |||
use of the User-based Security Model [RFC2274] and the | including full support for the SNMPv3 cryptographic mechanisms (for | |||
View-based Access Control Model [RFC2275] is RECOMMENDED. | authentication and privacy). | |||
It is then a customer/user responsibility to ensure that the SNMP | Further, deployment of SNMP versions prior to SNMPv3 is NOT | |||
entity giving access to an instance of this MIB, is properly | RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to | |||
configured to give access to the objects only to those | enable cryptographic security. It is then a customer/operator | |||
principals (users) that have legitimate rights to indeed GET or | responsibility to ensure that the SNMP entity giving access to an | |||
SET (change/create/delete) them. | instance of this MIB module is 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. | ||||
12. Authors Addresses | 11. Authors Addresses | |||
Avi Berger | Avi Berger | |||
PowerDsine Inc. | PowerDsine Inc. | |||
1, Hanagar St., P.O. Box 7220 | 1, Hanagar St., P.O. Box 7220 | |||
Hod Hasharon 45421, | Hod Hasharon 45421, | |||
Israel | Israel | |||
Tel: +972-9-7755100 Ext 307 | Tel: +972-9-7755100 Ext 307 | |||
Fax: +972-9-7755120 | Fax: +972-9-7755120 | |||
E-mail: avib@PowerDsine.com | E-mail: avib@PowerDsine.com | |||
Dan Romascanu | Dan Romascanu | |||
Avaya Inc. | Avaya | |||
Atidim Technology Park, Bldg. #3 | Atidim Technology Park, Bldg. #3 | |||
Tel Aviv, 61131 | Tel Aviv, 61131 | |||
Israel | Israel | |||
Tel: +972-3-645-8414 | Tel: +972-3-645-8414 | |||
Email: dromasca@avaya.com | Email: dromasca@avaya.com | |||
A. Full Copyright Statement | A. Full Copyright Statement | |||
Copyright (c) The Internet Society (2003). All Rights Reserved | ||||
This document and translations of it may be copied and furnished to | This document and translations of it may be copied and furnished to | |||
others, and derivative works that comment on or otherwise explain it | others, and derivative works that comment on or otherwise explain it | |||
or assist in its implementation may be prepared, copied, published | or assist in its implementation may be prepared, copied, published | |||
and distributed, in whole or in part, without restriction of any | and distributed, in whole or in part, without restriction of any | |||
kind, provided that the above copyright notice and this paragraph are | kind, provided that the above copyright notice and this paragraph are | |||
included on all such copies and derivative works. However, this | included on all such copies and derivative works. However, this | |||
document itself may not be modified in any way, such as by removing | document itself may not be modified in any way, such as by removing | |||
the copyright notice or references to the Internet Society or other | the copyright notice or references to the Internet Society or other | |||
Internet organizations, except as needed for the purpose of | Internet organizations, except as needed for the purpose of | |||
developing Internet standards in which case the procedures for | developing Internet standards in which case the procedures for | |||
skipping to change at line 1304 | skipping to change at page 21, line 8 | |||
The limited permissions granted above are perpetual and will not be | The limited permissions granted above are perpetual and will not be | |||
revoked by the Internet Society or its successors or assigns. | revoked by the Internet Society or its successors or assigns. | |||
This document and the information contained herein is provided on an | This document and the information contained herein is provided on an | |||
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING | "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING | |||
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING | TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING | |||
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION | BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION | |||
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF | HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF | |||
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. | MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. | |||
B. Evolution of the Document, Limitations and Future Work | ||||
NOTE: This section will be removed at RFC 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 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 possible 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. | ||||
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 to objects pethMainPseMaxVoltage & pethMainPseMinVoltage | ||||
j. Change SYNTAX of pethMainPseUsagePower form INTEGER to Gauge32 | ||||
k. Change SYNTAX of pethMainPseUsageCurrent 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. 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 | ||||
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 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 | ||||
The following changes were introduced between draft-ietf-hubmib-power-ethernet-mib-04.txt and draft-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 all references from P802.3af/D4.2 to P802.3af/D4.3 | ||||
16. Update the description for the pethPsePortPowerPairsControlAbility | ||||
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 in pethPsePortDetectionStatus | ||||
24. Spelling fix in pethPsePortShortCounter | ||||
25. Change in MIB module DESCRIPTION to strike 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 and 6 at the end of the document and added 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' and `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 | ||||
End of changes. | ||||
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/ |