draft-ietf-hubmib-power-ethernet-mib-08.txt   rfc3621.txt 
Internet Draft Avi Berger Network Working Group A. Berger
PowerDsine Inc. Request for Comments: 3621 PowerDsine Inc.
Dan Romascanu Category: Standards Track D. Romascanu
Avaya Avaya
22 June 2003 December 2003
Power Ethernet MIB
<draft-ietf-hubmib-power-ethernet-mib-08.txt> Power Ethernet MIB
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document specifies an Internet standards track protocol for the
all provisions of Section 10 of RFC2026. Internet-Drafts are working Internet community, and requests discussion and suggestions for
documents of the Internet Engineering Task Force (IETF), its areas, improvements. Please refer to the current edition of the "Internet
and its working groups. Note that other groups may also distribute Official Protocol Standards" (STD 1) for the standardization state
working documents as Internet-Drafts. and status of this protocol. Distribution of this memo is unlimited.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress."
To view the list Internet-Draft Shadow Directories, see
http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). 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 This document proposes an extension to the Ethernet-like Interfaces
MIB with a set of objects for managing a Power Source Equipment MIB with a set of objects for managing Power Sourcing Equipment
(PSE). (PSE).
Distribution of this memo is unlimited.
Table of Contents Table of Contents
Status of this Memo 1 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
Abstract 1 2. The Internet-Standard Management Framework . . . . . . . . . . 2
1 Introduction 2 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 The Internet-Standard Management Framework 2 4. MIB Structure. . . . . . . . . . . . . . . . . . . . . . . . . 3
3 Overview 2 5. Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . 3
4 MIB Structure 3 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
5 Definitions 3 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
6 Acknowledgements 17 7.1. Normative References . . . . . . . . . . . . . . . . . . 16
7 Normative References 17 7.2. Informative References . . . . . . . . . . . . . . . . . 17
8 Informative References 18 8. Intellectual Property Statement. . . . . . . . . . . . . . . . 17
9 Intellectual Property 18 9. Security Considerations. . . . . . . . . . . . . . . . . . . . 18
10 Security Considerations 18 10. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 19
11 Authors Addresses 20 11. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 20
A Full Copyright Statement 20
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 Power
Ethernet [IEEE-802.3af] Source Equipment (PSE). Ethernet [IEEE-802.3af] Power Sourcing 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 [RFC2119]. document are to be interpreted as described in [RFC2119].
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. 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. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
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 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 has led to the emergence of Ethernet IP phones, which
functions and characteristics as the traditional phones. Powering a have similar functions and characteristics as traditional phones.
phone is one of these functions that are being taken as granted. The Powering the phone with the same cable used for signal transfer is
IEEE 802.3 Working Group initiated a standard work on this subject, one of the functions that are being taken as granted. The IEEE 802.3
Working Group has initiated standardization 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].
The IEEE 802.3af WG did not define a full management interface, but The IEEE 802.3af WG did not define a full management interface, but
only the hardware registers that will allow for a management only the hardware registers that will allow for management interfaces
interfaces to be built for a powered Ethernet device. The MIB module to be built for a powered Ethernet device. The MIB module defined in
defined in this document extends the Ethernet-like Interfaces MIB this document extends the Ethernet-like Interfaces MIB [RFC3635] with
[RFC2665] with the management objects required for the management of the management objects required for the management of the powered
the powered Ethernet devices and ports. 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 three MIB groups. These MIB objects are categorized into three MIB groups.
The pethPsePortTable defines the objects used for the configuration The pethPsePortTable defines the objects used for configuring and
and describing the status of ports on a PSE device. Examples of PSE 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 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 pethNotificationControlTable includes objects that control the The pethNotificationControlTable includes objects that control the
transmission of notifications by the agent to a management transmission of notifications from the agent to a management
application. application.
5. Definitions 5. Definitions
POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN
IMPORTS POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN
MODULE-IDENTITY, mib-2, OBJECT-TYPE, Integer32,
Gauge32, Counter32, NOTIFICATION-TYPE
FROM SNMPv2-SMI
TruthValue
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
SnmpAdminString IMPORTS
FROM SNMP-FRAMEWORK-MIB; MODULE-IDENTITY, mib-2, OBJECT-TYPE, Integer32,
Gauge32, Counter32, NOTIFICATION-TYPE
FROM SNMPv2-SMI
TruthValue
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
powerEthernetMIB MODULE-IDENTITY SnmpAdminString
FROM SNMP-FRAMEWORK-MIB;
LAST-UPDATED "200306220000Z" -- June 22, 2003 powerEthernetMIB MODULE-IDENTITY
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB
Working Group"
CONTACT-INFO
"
WG Charter:
http://www.ietf.org/html.charters/hubmib-charter.html
Mailing lists: LAST-UPDATED "200311240000Z" -- November 24, 2003
General Discussion: hubmib@ietf.org ORGANIZATION "IETF Ethernet Interfaces and Hub MIB
To Subscribe: hubmib-requests@ietf.org Working Group"
In Body: subscribe your_email_address
Chair: Dan Romascanu CONTACT-INFO
Avaya "
Tel: +972-3-645-8414 WG Charter:
Email: dromasca@avaya.com http://www.ietf.org/html.charters/hubmib-charter.html
Editor: Avi Berger Mailing lists:
PowerDsine Inc. General Discussion: hubmib@ietf.org
Tel: 972-9-7755100 Ext 307 To Subscribe: hubmib-requests@ietf.org
Fax: 972-9-7755120 In Body: subscribe your_email_address
E-mail: avib@PowerDsine.com
"
DESCRIPTION Chair: Dan Romascanu
"The MIB module for managing Power Source Equipment Avaya
(PSE) working according to the IEEE 802.af Powered Tel: +972-3-645-8414
Ethernet (DTE Power via MDI) standard. Email: dromasca@avaya.com
The following terms are used throughout this Editor: Avi Berger
MIB module. For complete formal definitions, PowerDsine Inc.
the IEEE 802.3 standards should be consulted Tel: 972-9-7755100 Ext 307
wherever possible: Fax: 972-9-7755120
E-mail: avib@PowerDsine.com
"
Group - A recommended, but optional, entity DESCRIPTION
defined by the IEEE 802.3 management standard, "The MIB module for managing Power Source Equipment
in order to support a modular numbering scheme. (PSE) working according to the IEEE 802.af Powered
The classical example allows an implementor to Ethernet (DTE Power via MDI) standard.
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 The following terms are used throughout this
for which this entry contains information. The numbering MIB module. For complete formal definitions,
scheme for ports is implementation specific. the IEEE 802.3 standards should be consulted
wherever possible:
Copyright (c) The Internet Society (2003). This version of Group - A recommended, but optional, entity
this MIB module is part of RFC yyyy; See the RFC itself defined by the IEEE 802.3 management standard,
for full legal notices. in order to support a modular numbering scheme.
-- RFC Ed.: replace yyyy with the actual RFC number & remove this notice. The classical example allows an implementor to
" represent field-replaceable units as groups of
ports, with the port numbering matching the
modular hardware implementation.
REVISION "200306220000Z" -- June 22, 2003 Port - This entity identifies the port within the group
DESCRIPTION "Initial version, published as RFC yyyy." for which this entry contains information. The numbering
-- RFC Ed.: replace yyyy with actual RFC number & remove this notice scheme for ports is implementation specific.
::= { mib-2 XXX } Copyright (c) The Internet Society (2003). This version
-- RFC Ed.: replace XXX with IANA-assigned number & remove this notice of this MIB module is part of RFC 3621; See the RFC
itself for full legal notices."
pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 0 } REVISION "200311240000Z" -- November 24, 2003
pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 } DESCRIPTION "Initial version, published as RFC 3621."
pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 2 } ::= { mib-2 105 }
-- PSE Objects pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 0 }
pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 }
pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 2 }
pethPsePortTable OBJECT-TYPE -- PSE Objects
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.
Values of all read-write objects in this table are
persistent at restart/reboot."
::= { pethObjects 1 }
pethPsePortEntry OBJECT-TYPE pethPsePortTable OBJECT-TYPE
SYNTAX PethPsePortEntry SYNTAX SEQUENCE OF 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 table of objects that display and control the power
characteristics of a power Ethernet PSE port." characteristics of power Ethernet ports on a Power Source
INDEX { pethPsePortGroupIndex , pethPsePortIndex } Entity (PSE) device. This group will be implemented in
::= { pethPsePortTable 1 } managed power Ethernet switches and mid-span devices.
Values of all read-write objects in this table are
persistent at restart/reboot."
::= { pethObjects 1 }
PethPsePortEntry ::= SEQUENCE { pethPsePortEntry OBJECT-TYPE
pethPsePortGroupIndex SYNTAX PethPsePortEntry
Integer32, MAX-ACCESS not-accessible
pethPsePortIndex STATUS current
Integer32, DESCRIPTION
pethPsePortAdminEnable "A set of objects that display and control the power
TruthValue, characteristics of a power Ethernet PSE port."
pethPsePortPowerPairsControlAbility INDEX { pethPsePortGroupIndex , pethPsePortIndex }
TruthValue, ::= { pethPsePortTable 1 }
pethPsePortPowerPairs
INTEGER,
pethPsePortDetectionStatus
INTEGER,
pethPsePortPowerPriority
INTEGER,
pethPsePortMPSAbsentCounter
Counter32,
pethPsePortInvalidSignatureCounter
Counter32,
pethPsePortPowerDeniedCounter
Counter32,
pethPsePortOverLoadCounter
Counter32,
pethPsePortShortCounter
Counter32,
pethPsePortType
SnmpAdminString,
pethPsePortPowerClassifications
INTEGER
}
pethPsePortGroupIndex OBJECT-TYPE PethPsePortEntry ::= SEQUENCE {
SYNTAX Integer32 (1..2147483647) pethPsePortGroupIndex
MAX-ACCESS not-accessible Integer32,
STATUS current pethPsePortIndex
DESCRIPTION Integer32,
"This variable uniquely identifies the group pethPsePortAdminEnable
containing the port to which a power Ethernet PSE is TruthValue,
connected. Group means box in the stack, module in a pethPsePortPowerPairsControlAbility
rack and the value 1 MUST be used for non-modular devices. TruthValue,
Furthermore, the same value MUST be used in this variable, pethPsePortPowerPairs
pethMainPseGroupIndex, and pethNotificationControlGroupIndex INTEGER,
to refer to a given box in a stack or module in the rack." pethPsePortDetectionStatus
::= { pethPsePortEntry 1 } INTEGER,
pethPsePortPowerPriority
INTEGER,
pethPsePortIndex OBJECT-TYPE pethPsePortMPSAbsentCounter
SYNTAX Integer32 (1..2147483647) Counter32,
MAX-ACCESS not-accessible pethPsePortType
STATUS current SnmpAdminString,
DESCRIPTION pethPsePortPowerClassifications
"This variable uniquely identifies the power Ethernet PSE INTEGER,
port within group pethPsePortGroupIndex to which the pethPsePortInvalidSignatureCounter
power Ethernet PSE entry is connected." Counter32,
::= { pethPsePortEntry 2 } pethPsePortPowerDeniedCounter
Counter32,
pethPsePortOverLoadCounter
Counter32,
pethPsePortShortCounter
Counter32
}
pethPsePortAdminEnable OBJECT-TYPE pethPsePortGroupIndex OBJECT-TYPE
SYNTAX TruthValue SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-write MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"true (1) An interface which can provide the PSE functions. "This variable uniquely identifies the group
false(2) The interface will act as it would if it had no PSE containing the port to which a power Ethernet PSE is
function." connected. Group means box in the stack, module in a
REFERENCE rack and the value 1 MUST be used for non-modular devices.
"IEEE Std 802.3af Section 30.9.1.1.2 aPSEAdminState" Furthermore, the same value MUST be used in this variable,
::= { pethPsePortEntry 3 } pethMainPseGroupIndex, and pethNotificationControlGroupIndex
to refer to a given box in a stack or module in the rack."
::= { pethPsePortEntry 1 }
pethPsePortPowerPairsControlAbility OBJECT-TYPE pethPsePortIndex OBJECT-TYPE
SYNTAX TruthValue SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the capability of controlling the power pairs "This variable uniquely identifies the power Ethernet PSE
functionality to switch pins for sourcing power. port within group pethPsePortGroupIndex to which the
The value true indicate that the device has the capability power Ethernet PSE entry is connected."
to control the power pairs. When false the PSE Pinout ::= { pethPsePortEntry 2 }
Alternative used cannot be controlled through the
PethPsePortAdminEnabe attribute."
REFERENCE
"IEEE Std 802.3af Section 30.9.1.1.3
aPSEPowerPairsControlAbility"
::= { pethPsePortEntry 4 }
pethPsePortPowerPairs OBJECT-TYPE pethPsePortAdminEnable OBJECT-TYPE
SYNTAX INTEGER { SYNTAX TruthValue
signal(1), MAX-ACCESS read-write
spare(2) STATUS current
} DESCRIPTION
MAX-ACCESS read-write "true (1) An interface which can provide the PSE functions.
STATUS current false(2) The interface will act as it would if it had no PSE
DESCRIPTION function."
"Describes or controls the pairs in use. If the value of
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."
REFERENCE
"IEEE Std 802.3af Section 30.9.1.1.4 aPSEPowerPairs"
::= { pethPsePortEntry 5 }
pethPsePortDetectionStatus OBJECT-TYPE REFERENCE
SYNTAX INTEGER { "IEEE Std 802.3af Section 30.9.1.1.2 aPSEAdminState"
disabled(1), ::= { pethPsePortEntry 3 }
searching(2),
deliveringPower(3),
fault(4),
test(5),
otherFault(6)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Describes the operational status of the port PD detection.
A value of disabled(1)- indicates that the PSE State diagram
is in the state DISABLED.
A value of deliveringPower(3) - indicates that the PSE State
diagram is in the state POWER_ON for a duration greater than
tlim max (see IEEE Std 802.3af Table 33-5 tlim).
A value of fault(4) - indicates that the PSE State diagram is
in the state TEST_ERROR.
A value of test(5) - indicates that the PSE State diagram is
in the state TEST_MODE.
A value of otherFault(6) - indicates that the PSE State
diagram is in the state IDLE due to the variable
error_conditions.
A value of searching(2)- indicates the PSE State diagram is
in a state other than those listed above."
REFERENCE
"IEEE Std 802.3af Section 30.9.1.1.5
aPSEPowerDetectionStatus"
::= { pethPsePortEntry 6 }
pethPsePortPowerPriority OBJECT-TYPE pethPsePortPowerPairsControlAbility OBJECT-TYPE
SYNTAX INTEGER { SYNTAX TruthValue
critical(1), MAX-ACCESS read-only
high(2), STATUS current
low(3) DESCRIPTION
} "Describes the capability of controlling the power pairs
MAX-ACCESS read-write functionality to switch pins for sourcing power.
STATUS current The value true indicate that the device has the capability
DESCRIPTION to control the power pairs. When false the PSE Pinout
"This object controls the priority of the port from the point Alternative used cannot be controlled through the
of view of a power management algorithm. The priority that PethPsePortAdminEnable attribute."
is set by this variable could be used by a control mechanism REFERENCE
that prevents over current situations by disconnecting first "IEEE Std 802.3af Section 30.9.1.1.3
ports with lower power priority. Ports that connect devices aPSEPowerPairsControlAbility"
critical to the operation of the network - like the E911 ::= { pethPsePortEntry 4 }
telephones ports - should be set to higher priority."
::= { pethPsePortEntry 7 }
pethPsePortMPSAbsentCounter OBJECT-TYPE pethPsePortPowerPairs OBJECT-TYPE
SYNTAX Counter32 SYNTAX INTEGER {
MAX-ACCESS read-only signal(1),
STATUS current spare(2)
DESCRIPTION }
"This counter is incremented when the PSE state diagram MAX-ACCESS read-write
transitions directly from the state POWER_ON to the STATUS current
state IDLE due to tmpdo_timer_done being asserted." DESCRIPTION
REFERENCE "Describes or controls the pairs in use. If the value of
"IEEE Std 802.3af Section 30.9.1.1.11 pethPsePortPowerPairsControl is true, this object is
aPSEMPSAbsentCounter" writable.
::= { pethPsePortEntry 8 } A value of signal(1) means that the signal pairs
only are in use.
A value of spare(2) means that the spare pairs
only are in use."
REFERENCE
"IEEE Std 802.3af Section 30.9.1.1.4 aPSEPowerPairs"
::= { pethPsePortEntry 5 }
pethPsePortType OBJECT-TYPE pethPsePortDetectionStatus OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX INTEGER {
MAX-ACCESS read-write disabled(1),
STATUS current searching(2),
DESCRIPTION deliveringPower(3),
"A manager will set the value of this variable to indicate fault(4),
the type of powered device that is connected to the port. test(5),
The default value supplied by the agent if no value has otherFault(6)
ever been set should be a zero-length octet string." }
::= { pethPsePortEntry 9 }
pethPsePortPowerClassifications OBJECT-TYPE MAX-ACCESS read-only
SYNTAX INTEGER { STATUS current
class0(1), DESCRIPTION
class1(2), "Describes the operational status of the port PD detection.
class2(3), A value of disabled(1)- indicates that the PSE State diagram
class3(4), is in the state DISABLED.
class4(5) A value of deliveringPower(3) - indicates that the PSE State
} diagram is in the state POWER_ON for a duration greater than
MAX-ACCESS read-only tlim max (see IEEE Std 802.3af Table 33-5 tlim).
STATUS current A value of fault(4) - indicates that the PSE State diagram is
DESCRIPTION in the state TEST_ERROR.
"Classification is a way to tag different terminals on the A value of test(5) - indicates that the PSE State diagram is
Power over LAN network according to their power consumption. in the state TEST_MODE.
A value of otherFault(6) - indicates that the PSE State
diagram is in the state IDLE due to the variable
error_conditions.
A value of searching(2)- indicates the PSE State diagram is
in a state other than those listed above."
REFERENCE
"IEEE Std 802.3af Section 30.9.1.1.5
aPSEPowerDetectionStatus"
::= { pethPsePortEntry 6 }
Devices such as IP telephones, WLAN access points and others, pethPsePortPowerPriority OBJECT-TYPE
will be classified according to their power requirements. SYNTAX INTEGER {
critical(1),
high(2),
low(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object controls the priority of the port from the point
of view of a power management algorithm. The priority that
is set by this variable could be used by a control mechanism
that prevents over current situations by disconnecting first
ports with lower power priority. Ports that connect devices
critical to the operation of the network - like the E911
telephones ports - should be set to higher priority."
::= { pethPsePortEntry 7 }
The meaning of the classification labels is defined in the pethPsePortMPSAbsentCounter OBJECT-TYPE
IEEE specification. SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This counter is incremented when the PSE state diagram
transitions directly from the state POWER_ON to the
state IDLE due to tmpdo_timer_done being asserted."
REFERENCE
"IEEE Std 802.3af Section 30.9.1.1.11
aPSEMPSAbsentCounter"
::= { pethPsePortEntry 8 }
This variable is valid only while a PD is being powered, pethPsePortType OBJECT-TYPE
that is, while the attribute pethPsePortDetectionStatus SYNTAX SnmpAdminString
is reporting the enumeration deliveringPower." MAX-ACCESS read-write
REFERENCE STATUS current
"IEEE Std 802.3af Section 30.9.1.1.6 DESCRIPTION
aPSEPowerClassification" "A manager will set the value of this variable to indicate
::= { pethPsePortEntry 10 } the type of powered device that is connected to the port.
The default value supplied by the agent if no value has
ever been set should be a zero-length octet string."
::= { pethPsePortEntry 9 }
pethPsePortInvalidSignatureCounter OBJECT-TYPE pethPsePortPowerClassifications OBJECT-TYPE
SYNTAX Counter32 SYNTAX INTEGER {
MAX-ACCESS read-only class0(1),
STATUS current class1(2),
DESCRIPTION class2(3),
"This counter is incremented when the PSE state diagram class3(4),
enters the state SIGNATURE_INVALID." class4(5)
REFERENCE }
"IEEE Std 802.3af Section 30.9.1.1.7 MAX-ACCESS read-only
aPSEInvalidSignatureCounter" STATUS current
::= { pethPsePortEntry 11 } DESCRIPTION
"Classification is a way to tag different terminals on the
Power over LAN network according to their power consumption.
Devices such as IP telephones, WLAN access points and others,
will be classified according to their power requirements.
pethPsePortPowerDeniedCounter OBJECT-TYPE The meaning of the classification labels is defined in the
SYNTAX Counter32 IEEE specification.
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This counter is incremented when the PSE state diagram
enters the state POWER_DENIED."
REFERENCE
"IEEE Std 802.3af Section 30.9.1.1.8
aPSEPowerDeniedCounter"
::= { pethPsePortEntry 12 }
pethPsePortOverLoadCounter OBJECT-TYPE This variable is valid only while a PD is being powered,
SYNTAX Counter32 that is, while the attribute pethPsePortDetectionStatus
MAX-ACCESS read-only is reporting the enumeration deliveringPower."
STATUS current REFERENCE
DESCRIPTION "IEEE Std 802.3af Section 30.9.1.1.6
"This counter is incremented when the PSE state diagram aPSEPowerClassification"
enters the state ERROR_DELAY_OVER." ::= { pethPsePortEntry 10 }
REFERENCE
"IEEE Std 802.3af Section 30.9.1.1.9
aPSEOverLoadCounter"
::= { pethPsePortEntry 13 } pethPsePortInvalidSignatureCounter OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This counter is incremented when the PSE state diagram
enters the state SIGNATURE_INVALID."
REFERENCE
"IEEE Std 802.3af Section 30.9.1.1.7
aPSEInvalidSignatureCounter"
::= { pethPsePortEntry 11 }
pethPsePortShortCounter OBJECT-TYPE pethPsePortPowerDeniedCounter OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This counter is incremented when the PSE state diagram "This counter is incremented when the PSE state diagram
enters the state ERROR_DELAY_SHORT." enters the state POWER_DENIED."
REFERENCE REFERENCE
"IEEE Std 802.3af Section 30.9.1.1.10 "IEEE Std 802.3af Section 30.9.1.1.8
aPSEShortCounter" aPSEPowerDeniedCounter"
::= { pethPsePortEntry 14 } ::= { pethPsePortEntry 12 }
-- Main PSE Objects pethPsePortOverLoadCounter OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This counter is incremented when the PSE state diagram
enters the state ERROR_DELAY_OVER."
REFERENCE
"IEEE Std 802.3af Section 30.9.1.1.9
aPSEOverLoadCounter"
::= { pethPsePortEntry 13 }
pethMainPseObjects OBJECT IDENTIFIER ::= { pethObjects 3 } pethPsePortShortCounter OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This counter is incremented when the PSE state diagram
enters the state ERROR_DELAY_SHORT."
REFERENCE
"IEEE Std 802.3af Section 30.9.1.1.10
aPSEShortCounter"
::= { pethPsePortEntry 14 }
pethMainPseTable OBJECT-TYPE -- Main PSE Objects
SYNTAX SEQUENCE OF PethMainPseEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display and control attributes
of the main power source in a PSE device. Ethernet
switches are one example of boxes that would support
these objects.
Values of all read-write objects in this table are
persistent at restart/reboot."
::= { pethMainPseObjects 1 }
pethMainPseEntry OBJECT-TYPE pethMainPseObjects OBJECT IDENTIFIER ::= { pethObjects 3 }
SYNTAX PethMainPseEntry pethMainPseTable OBJECT-TYPE
MAX-ACCESS not-accessible SYNTAX SEQUENCE OF PethMainPseEntry
STATUS current MAX-ACCESS not-accessible
DESCRIPTION STATUS current
"A set of objects that display and control the Main DESCRIPTION
power of a PSE. " "A table of objects that display and control attributes
INDEX { pethMainPseGroupIndex } of the main power source in a PSE device. Ethernet
::= { pethMainPseTable 1 } 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 }
PethMainPseEntry ::= SEQUENCE { pethMainPseEntry OBJECT-TYPE
pethMainPseGroupIndex SYNTAX PethMainPseEntry
Integer32, MAX-ACCESS not-accessible
pethMainPsePower STATUS current
Gauge32 , DESCRIPTION
pethMainPseOperStatus "A set of objects that display and control the Main
INTEGER, power of a PSE. "
pethMainPseConsumptionPower INDEX { pethMainPseGroupIndex }
Gauge32, ::= { pethMainPseTable 1 }
pethMainPseUsageThreshold
Integer32
}
pethMainPseGroupIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
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) and the value 1 MUST be
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 }
pethMainPsePower OBJECT-TYPE PethMainPseEntry ::= SEQUENCE {
SYNTAX Gauge32 (1..65535) pethMainPseGroupIndex
UNITS "Watts" Integer32,
MAX-ACCESS read-only pethMainPsePower
STATUS current Gauge32 ,
DESCRIPTION pethMainPseOperStatus
"The nominal power of the PSE expressed in Watts." INTEGER,
::= { pethMainPseEntry 2 } pethMainPseConsumptionPower
Gauge32,
pethMainPseUsageThreshold
Integer32
}
pethMainPseGroupIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
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) and the value 1 MUST be
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 }
pethMainPseOperStatus OBJECT-TYPE pethMainPsePower OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Gauge32 (1..65535)
on(1), UNITS "Watts"
off(2), MAX-ACCESS read-only
faulty(3) STATUS current
} DESCRIPTION
MAX-ACCESS read-only "The nominal power of the PSE expressed in Watts."
STATUS current ::= { pethMainPseEntry 2 }
DESCRIPTION
"The operational status of the main PSE."
::= { pethMainPseEntry 3 }
pethMainPseConsumptionPower OBJECT-TYPE pethMainPseOperStatus OBJECT-TYPE
SYNTAX Gauge32 SYNTAX INTEGER {
UNITS "Watts" on(1),
MAX-ACCESS read-only off(2),
STATUS current faulty(3)
DESCRIPTION }
"Measured usage power expressed in Watts." MAX-ACCESS read-only
::= { pethMainPseEntry 4 } STATUS current
DESCRIPTION
"The operational status of the main PSE."
::= { pethMainPseEntry 3 }
pethMainPseUsageThreshold OBJECT-TYPE pethMainPseConsumptionPower OBJECT-TYPE
SYNTAX Integer32 (1..99) SYNTAX Gauge32
UNITS "%" UNITS "Watts"
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The usage threshold expressed in percents for "Measured usage power expressed in Watts."
comparing the measured power and initiating ::= { pethMainPseEntry 4 }
an alarm if the threshold is exceeded."
::= { pethMainPseEntry 5 }
-- Notification Control Objects pethMainPseUsageThreshold OBJECT-TYPE
SYNTAX Integer32 (1..99)
UNITS "%"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The usage threshold expressed in percents for
comparing the measured power and initiating
an alarm if the threshold is exceeded."
::= { pethMainPseEntry 5 }
pethNotificationControl OBJECT IDENTIFIER ::= { pethObjects 4 } -- Notification Control Objects
pethNotificationControlTable OBJECT-TYPE pethNotificationControl OBJECT IDENTIFIER ::= { pethObjects 4 }
SYNTAX SEQUENCE OF PethNotificationControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display and control the
Notification on a PSE device.
Values of all read-write objects in this table are
persistent at restart/reboot."
::= { pethNotificationControl 1 }
pethNotificationControlEntry OBJECT-TYPE pethNotificationControlTable OBJECT-TYPE
SYNTAX PethNotificationControlEntry SYNTAX SEQUENCE OF 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 table of objects that display and control the
INDEX { pethNotificationControlGroupIndex } Notification on a PSE device.
::= { pethNotificationControlTable 1 } Values of all read-write objects in this table are
persistent at restart/reboot."
::= { pethNotificationControl 1 }
PethNotificationControlEntry ::= SEQUENCE { pethNotificationControlEntry OBJECT-TYPE
pethNotificationControlGroupIndex SYNTAX PethNotificationControlEntry
Integer32, MAX-ACCESS not-accessible
pethNotificationControlEnable STATUS current
TruthValue DESCRIPTION
} "A set of objects that control the Notification events."
pethNotificationControlGroupIndex OBJECT-TYPE INDEX { pethNotificationControlGroupIndex }
SYNTAX Integer32 (1..2147483647) ::= { pethNotificationControlTable 1 }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This variable uniquely identifies the group. Group
means box in the stack, module in a rack and the value
1 MUST 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 }
pethNotificationControlEnable OBJECT-TYPE PethNotificationControlEntry ::= SEQUENCE {
SYNTAX TruthValue pethNotificationControlGroupIndex
MAX-ACCESS read-write Integer32,
STATUS current pethNotificationControlEnable
DESCRIPTION TruthValue
"This object controls, on a per-group basis, whether }
or not notifications from the agent are enabled. The pethNotificationControlGroupIndex OBJECT-TYPE
value true(1) means that notifications are enabled; the SYNTAX Integer32 (1..2147483647)
value false(2) means that they are not." MAX-ACCESS not-accessible
::= { pethNotificationControlEntry 2 } STATUS current
DESCRIPTION
"This variable uniquely identifies the group. Group
means box in the stack, module in a rack and the value
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 }
-- pethNotificationControlEnable OBJECT-TYPE
-- Notifications Section SYNTAX TruthValue
-- MAX-ACCESS read-write
-- STATUS current
DESCRIPTION
"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 }
pethPsePortOnOffNotification NOTIFICATION-TYPE --
OBJECTS { pethPsePortDetectionStatus } -- Notifications Section
STATUS current --
DESCRIPTION --
" This Notification indicates if Pse Port is delivering or
not power to the PD. This Notification SHOULD be sent on
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 }
pethMainPowerUsageOnNotification NOTIFICATION-TYPE pethPsePortOnOffNotification NOTIFICATION-TYPE
OBJECTS { pethMainPseConsumptionPower } OBJECTS { pethPsePortDetectionStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This Notification indicate PSE Threshold usage " This Notification indicates if Pse Port is delivering or
indication is on, the usage power is above the not power to the PD. This Notification SHOULD be sent on
threshold. At least 500 msec must elapse between every status change except in the searching mode.
notifications being emitted by the same object At least 500 msec must elapse between notifications
instance." being emitted by the same object instance."
::= { pethNotifications 2 } ::= { pethNotifications 1 }
pethMainPowerUsageOffNotification NOTIFICATION-TYPE pethMainPowerUsageOnNotification NOTIFICATION-TYPE
OBJECTS { pethMainPseConsumptionPower } OBJECTS { pethMainPseConsumptionPower }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This Notification indicates PSE Threshold usage indication " This Notification indicate PSE Threshold usage
off, the usage power is below the threshold. indication is on, the usage power is above the
At least 500 msec must elapse between notifications being threshold. At least 500 msec must elapse between
emitted by the same object instance." notifications being emitted by the same object
::= { pethNotifications 3 } instance."
::= { pethNotifications 2 }
-- pethMainPowerUsageOffNotification NOTIFICATION-TYPE
-- Conformance Section OBJECTS { pethMainPseConsumptionPower }
-- STATUS current
pethCompliances OBJECT IDENTIFIER ::= { pethConformance 1 } DESCRIPTION
pethGroups OBJECT IDENTIFIER ::= { pethConformance 2 } " This Notification indicates PSE Threshold usage indication
off, the usage power is below the threshold.
At least 500 msec must elapse between notifications being
emitted by the same object instance."
::= { pethNotifications 3 }
pethCompliance MODULE-COMPLIANCE --
STATUS current -- Conformance Section
DESCRIPTION --
"Describes the requirements for conformance to the pethCompliances OBJECT IDENTIFIER ::= { pethConformance 1 }
Power Ethernet MIB." pethGroups OBJECT IDENTIFIER ::= { pethConformance 2 }
MODULE -- this module
MANDATORY-GROUPS { pethPsePortGroup,
pethPsePortNotificationGroup,
pethNotificationControlGroup
}
GROUP pethMainPseGroup
DESCRIPTION
"The pethMainPseGroup is mandatory for PSE systems
that implement a main power supply."
GROUP pethMainPowerNotificationGroup
DESCRIPTION
"The pethMainPowerNotificationGroup is mandatory for
PSE systems that implement a main power supply."
::= { pethCompliances 1 }
pethPsePortGroup OBJECT-GROUP pethCompliance MODULE-COMPLIANCE
OBJECTS {
pethPsePortAdminEnable,
pethPsePortPowerPairsControlAbility,
pethPsePortPowerPairs,
pethPsePortDetectionStatus,
pethPsePortPowerPriority,
pethPsePortMPSAbsentCounter,
pethPsePortInvalidSignatureCounter,
pethPsePortPowerDeniedCounter,
pethPsePortOverLoadCounter,
pethPsePortShortCounter,
pethPsePortType,
pethPsePortPowerClassifications
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PSE Port objects." "Describes the requirements for conformance to the
::= { pethGroups 1 } Power Ethernet MIB."
pethMainPseGroup OBJECT-GROUP MODULE -- this module
OBJECTS { MANDATORY-GROUPS { pethPsePortGroup,
pethMainPsePower, pethPsePortNotificationGroup,
pethMainPseOperStatus, pethNotificationControlGroup
pethMainPseConsumptionPower, }
pethMainPseUsageThreshold GROUP pethMainPseGroup
} DESCRIPTION
STATUS current "The pethMainPseGroup is mandatory for PSE systems
DESCRIPTION that implement a main power supply."
"Main PSE Objects. " GROUP pethMainPowerNotificationGroup
::= { pethGroups 2 } DESCRIPTION
"The pethMainPowerNotificationGroup is mandatory for
PSE systems that implement a main power supply."
::= { pethCompliances 1 }
pethNotificationControlGroup OBJECT-GROUP pethPsePortGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pethNotificationControlEnable pethPsePortAdminEnable,
} pethPsePortPowerPairsControlAbility,
STATUS current pethPsePortPowerPairs,
DESCRIPTION pethPsePortDetectionStatus,
"Notification Control Objects. " pethPsePortPowerPriority,
::= { pethGroups 3 } pethPsePortMPSAbsentCounter,
pethPsePortInvalidSignatureCounter,
pethPsePortPowerDeniedCounter,
pethPsePortOverLoadCounter,
pethPsePortShortCounter,
pethPsePortType,
pethPsePortPowerClassifications
}
STATUS current
DESCRIPTION
"PSE Port objects."
::= { pethGroups 1 }
pethPsePortNotificationGroup NOTIFICATION-GROUP pethMainPseGroup OBJECT-GROUP
NOTIFICATIONS { pethPsePortOnOffNotification} OBJECTS {
STATUS current pethMainPsePower,
DESCRIPTION "Pse Port Notifications." pethMainPseOperStatus,
::= { pethGroups 4 } pethMainPseConsumptionPower,
pethMainPseUsageThreshold
}
STATUS current
DESCRIPTION
"Main PSE Objects. "
::= { pethGroups 2 }
pethMainPowerNotificationGroup NOTIFICATION-GROUP pethNotificationControlGroup OBJECT-GROUP
NOTIFICATIONS { pethMainPowerUsageOnNotification, OBJECTS {
pethMainPowerUsageOffNotification} pethNotificationControlEnable
STATUS current }
DESCRIPTION "Main PSE Notifications." STATUS current
::= { pethGroups 5 } DESCRIPTION
"Notification Control Objects. "
::= { pethGroups 3 }
END pethPsePortNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { pethPsePortOnOffNotification}
STATUS current
DESCRIPTION "Pse Port Notifications."
::= { pethGroups 4 }
6. Acknowledgements pethMainPowerNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { pethMainPowerUsageOnNotification,
pethMainPowerUsageOffNotification}
STATUS current
DESCRIPTION "Main PSE Notifications."
::= { pethGroups 5 }
This document is the product of the Ethernet Interfaces END
and Hub MIB WG. The authors would like to recognize the
special contributions of C.M. Heard and David Law.
7. Normative References 6. Acknowledgements
[RFC2026] Bradner, S., "The Internet Standards Process - Revision This document is the product of the Ethernet Interfaces and Hub MIB
3", BCP 9, RFC 2026, October 1996. WG. The authors would like to recognize the special contributions of
C.M. Heard and David Law.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 7. References
Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 7.1. Normative References
Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2026] Bradner, S., "The Internet Standards Process -
Rose, M. and S. Waldbusser, "Conformance Statements for Revision 3", BCP 9, RFC 2026, October 1996.
SMIv2", STD 58, RFC 2580, April 1999.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2578] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
Requirement Levels", BCP 14, RFC 2119, March 1997. "Structure of Management Information Version 2
(SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2665] Flick, J., and J. Johnson, "Definitions of Managed [RFC2579] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
Objects for the Ethernet-like Interface Types", RFC "Textual Conventions for SMIv2", STD 58, RFC 2579,
2665, August 1999. April 1999.
NOTE - This RFC is under revision by the WG, and may be obsolete by [RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
the time of the publication. The RFC editor should replace it with "Conformance Statements for SMIv2", STD 58, RFC 2580,
the revised version, if available. April 1999.
[RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Architecture for Describing Simple Network Management Requirement Levels", BCP 14, RFC 2119, March 1997.
Protocol (SNMP) Management Frameworks", RFC 3411,
December 2002.
[IEEE-802.3af] IEEE 802.3 Working Group, "Data Terminal Equipment [RFC3635] Flick, J., "Definitions of Managed Objects for the
(DTE)Power via Media Dependent Interface (MDI)", publication Ethernet-like Interface Types", RFC 3635, September
date TBD 2003.
NOTE - This normative reference will be replaced with the IEEE 802.3af [RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An
Standard as soon as the IEEE will ratify it (expected date - July 2003) Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC
3411, December 2002.
8. Informative References [IEEE-802.3af] IEEE 802.3 Working Group, "IEEE Std 802.3af-2003 -
Data Terminal Equipment (DTE) Power via Media
Dependent Interface (MDI)", July 2003.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 7.2. Informative References
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002
9.Intellectual Property [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410,
December 2002.
8. Intellectual Property Statement
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 18, line 46 skipping to change at page 18, line 5
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.
10. Security Considerations 9. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write. Such objects may be with a MAX-ACCESS clause of read-write. Such objects may be
considered sensitive or vulnerable in some network environments. considered sensitive or vulnerable in some network environments. The
The support for SET operations in a non-secure environment without support for SET operations in a non-secure environment without proper
proper protection can have a negative effect on network operations. protection can have a negative effect on network operations.
Setting the following object to incorrect values can result in Setting the following object to incorrect values can result in
improper operation of the PSE, including the possibility that the improper operation of the PSE, including the possibility that the PD
PD does not receive power from the PSE port: does not receive power from the PSE port:
pethPsePortAdminEnable pethPsePortAdminEnable
pethPsePortPowerPairs pethPsePortPowerPairs
pethPsePortPowerPriority pethPsePortPowerPriority
pethPsePortType pethPsePortType
Setting the following objects to incorrect values can result in an Setting the following objects to incorrect values can result in an
excessive number of traps being sent to network management stations: excessive number of traps being sent to network management stations:
pethMainPseUsageThreshold pethMainPseUsageThreshold
skipping to change at page 20, line 6 skipping to change at page 19, line 13
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
11. Authors Addresses 10. 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
Fax: +972-9-7755120
E-mail: avib@PowerDsine.com
Dan Romascanu Phone: +972-9-7755100 Ext 307
Avaya Fax: +972-9-7755120
Atidim Technology Park, Bldg. #3 EMail: avib@PowerDsine.com
Tel Aviv, 61131
Israel
Tel: +972-3-645-8414
Email: dromasca@avaya.com
A. Full Copyright Statement Dan Romascanu
Avaya
Atidim Technology Park, Bldg. #3
Tel Aviv, 61131
Israel
Copyright (c) The Internet Society (2003). All Rights Reserved Phone: +972-3-645-8414
EMail: dromasca@avaya.com
11. 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
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
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 assignees.
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.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 112 change blocks. 
681 lines changed or deleted 663 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/