draft-ietf-hubmib-power-ethernet-mib-01.txt   draft-ietf-hubmib-power-ethernet-mib-02.txt 
Internet Draft Avi Berger Internet Draft Avi Berger
PowerDsine Inc. PowerDsine Inc.
Dan Romascanu Dan Romascanu
Avaya Inc. Avaya Inc.
20 November 2001 30 June 2002
Power Ethernet (DTE Power via MDI) MIB Power Ethernet (DTE Power via MDI) MIB
<draft-ietf-hubmib-power-ethernet-mib-01.txt> <draft-ietf-hubmib-power-ethernet-mib-02.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 (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). 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 [RFC2665] with a set of objects for managing a power Ethernet
Powered Device (PD) and/or Power Source Equipment (PSE). Powered Device (PD) and/or Power Source Equipment (PSE).
Distribution of this memo is unlimited. Distribution of this memo is unlimited.
skipping to change at page 2, line 9 skipping to change at page 2, line 9
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 SNMP Management Framework 2
3 Overview 3 3 Overview 3
4 MIB Structure 4 4 MIB Structure 4
5 Evolution of the Document, Limitations and Future Work 4 5 Evolution of the Document, Limitations and Future Work 4
6 Changes log 4 6 Changes log 4
7 Definitions 7 7 Definitions 7
8 References 23 8 References 24
9 Intellectual Property 24 9 Intellectual Property 26
10 Security Considerations 25 10 Security Considerations 26
11 Authors Addresses 25 11 Authors Addresses 27
A Full Copyright Statement 26 A Full Copyright Statement 27
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 (DTE Power via MDI)Powered Device (PD) and/or power 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",
skipping to change at page 4, line 33 skipping to change at page 4, line 33
The pethTrapsControlTable includes objects that control the The pethTrapsControlTable includes objects that control the
transmission of traps by the agent to a management application. transmission of traps by the agent to a management application.
5. Evolution of the Document, Limitations and Future Work 5. Evolution of the Document, Limitations and Future Work
The IEEE 802.3af is at this stage work in progress. The scope of this 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 document is to do the standards work in the IETF in parallel with the
IEEE standardization activity, in order to allow for the publication IEEE standardization activity, in order to allow for the publication
of a standard track document containing an SNMP MIB simultaneously of a standard track document containing an SNMP MIB simultaneously
or close to the date of the publication of the IEEE revised standard. or close to the date of the publication of the IEEE revised standard.
It is expected that changes may be brought to the IEEE proposal, and It is possible that changes may be brought to the IEEE proposal, and
the Ethernet MIB Working Group will work in order to ensure the Ethernet MIB Working Group will work in order to ensure
consistency between the two standards proposals. consistency between the two standards proposals.
6. Changes Log 6. Changes Log
The following changes were introduced relative to the first proposal The following changes were introduced relative to the first proposal
for a Power Ethernet MIB [PWR-MIB] for a Power Ethernet MIB [PWR-MIB]
a. pethPsePortTable has to index pethPsePortGroupIndex & a. pethPsePortTable has to index pethPsePortGroupIndex &
pethPsePortIndex pethPsePortIndex
skipping to change at page 7, line 6 skipping to change at page 7, line 6
20. change in pethPsePortGroup 20. change in pethPsePortGroup
21. change in pethPdPortGroup 21. change in pethPdPortGroup
22. change pethPsePortOnOffTrap with pethPsePortDetectionStatus 22. change pethPsePortOnOffTrap with pethPsePortDetectionStatus
object object
23. change pethPsePortStatusTrap to pethPsePortCurrentStatusTrap 23. change pethPsePortStatusTrap to pethPsePortCurrentStatusTrap
24. change pethPsePortTrapGroup 24. change pethPsePortTrapGroup
7. Definitions 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.
7. Definitions
POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32 , Gauge32,NOTIFICATION-TYPE MODULE-IDENTITY, OBJECT-TYPE, Integer32 , Gauge32,Counter32 ,NOTIFICATION-TYPE
FROM SNMPv2-SMI FROM SNMPv2-SMI
dot3 dot3
FROM EtherLike-MIB FROM EtherLike-MIB
TruthValue TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
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 "200111200000Z" -- November 20, 2001 LAST-UPDATED "200206260000Z" -- June 26, 2002
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB ORGANIZATION "IETF Ethernet Interfaces and Hub MIB
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
" "
Chair: Dan Romascanu Chair: Dan Romascanu
Avaya Inc. Avaya Inc.
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 managing Powered Devices (PD) or "The MIB module for for managing Powered Devices (PD) or
Power Source Equipment (PSE) working according to the IEEE Power Source Equipment (PSE) working according to the IEEE
802.af Power Ethernet (DTE Power via MDI) standard. 802.af Powere 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.
"
::= { dot3 20 } ::= { dot3 20 }
pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 } pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 }
pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 2 } pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 2 }
pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 3 } pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 3 }
-- PSE Objects -- PSE Objects
pethPsePortTable OBJECT-TYPE pethPsePortTable OBJECT-TYPE
SYNTAX SEQUENCE OF PethPsePortEntry SYNTAX SEQUENCE OF PethPsePortEntry
skipping to change at page 9, line 17 skipping to change at page 10, line 13
pethPsePortPowerPairs pethPsePortPowerPairs
INTEGER, INTEGER,
pethPsePortPowerDetectionControl pethPsePortPowerDetectionControl
INTEGER, INTEGER,
pethPsePortDetectionStatus pethPsePortDetectionStatus
INTEGER, INTEGER,
pethPsePortPowerPriority pethPsePortPowerPriority
INTEGER, INTEGER,
pethPsePortCurrentStatus pethPsePortCurrentStatus
INTEGER, INTEGER,
pethPsePortCurrentStatusClear pethPsePortUnderCurrentCounter
INTEGER, Counter32,
pethPsePortOverCurrentCounter
Counter32,
pethPsePortType pethPsePortType
INTEGER, INTEGER,
pethPsePortPowerClassifications pethPsePortPowerClassifications
INTEGER INTEGER
} }
pethPsePortGroupIndex OBJECT-TYPE pethPsePortGroupIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647) SYNTAX INTEGER (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable uniquely identifies the group "This variable uniquely identifies the group
containing the port to which power Ethernet PSE is connected. containing the port to which power Ethernet PSE is connected.
Group means (box in the stack, module in a rack) and the value 1 Group means (box in the stack, module in a rack) and the value 1
MUST be used for non-modular devices " MUST be used for non-modular devices."
::= { pethPsePortEntry 1 } ::= { pethPsePortEntry 1 }
pethPsePortIndex OBJECT-TYPE pethPsePortIndex OBJECT-TYPE
SYNTAX INTEGER(1..2147483647) SYNTAX INTEGER(1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
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 pethPseGroupIndex to which the
power Ethernet PSE entry is connected." power Ethernet PSE entry is connected."
skipping to change at page 11, line 25 skipping to change at page 12, line 23
deliveringPower(4), deliveringPower(4),
fault(5), fault(5),
invalidPD(6), invalidPD(6),
test(7), test(7),
denyLowPriority(8) denyLowPriority(8)
} }
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 PD Detection function has A value of disabled(1) indicates that the PD Detection function
been disabled. has been disabled.
A value of searching(2) indicates that the PD Detection function is A value of searching(2) indicates that the PD Detection function
enabled and is searching for a valid PD. is enabled and is searching for a valid PD.
A value of detected(3)indicates that the PD Detection function has A value of detected(3)indicates that the PD Detection function
detected a valid PD but the PSE is not supplying power. has detected a valid PD but the PSE is not supplying power.
A value of deliveringPower(4) indicates that the port A value of deliveringPower(4) indicates that the port
executed the detection algorithm, found a PD connection executed the detection algorithm, found a PD connection
and is currently delivering power. and is currently delivering power.
A value of fault(5) indicates that a fault was detected A value of fault(5) indicates that a fault was detected
on the port , faults detected are vendor-specific. on the port , faults detected are vendor-specific.
A value of invalidPD(6)indicates that the PD Detection function has A value of invalidPD(6)indicates that the PD Detection function
detected a invalid PD. has detected an invalid PD.
A value of test(7)indicates that the PD Detection function has been A value of test(7)indicates that the PD Detection function has
placed in test mode. been placed in test mode.
A value of denyLowPriority(8) indicates that the port was A value of denyLowPriority(8) indicates that the port was
disabled by the power management system, in order to keep disabled by the power management system, in order to keep
active higher priority ports. active higher priority ports.
" "
::= { pethPsePortEntry 7 } ::= { pethPsePortEntry 7 }
pethPsePortPowerPriority OBJECT-TYPE pethPsePortPowerPriority OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
critical(1), critical(1),
high(2), high(2),
skipping to change at page 12, line 21 skipping to change at page 13, line 19
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 }
pethPsePortCurrentStatus OBJECT-TYPE pethPsePortCurrentStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
ok(1), ok(1),
underCurrent(2), underCurrent(2),
overCurrent(3), overCurrent(3)
both(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes a current port status related to the power generation "Describes a current port status related to the power generation
The value ok(1) indicates neither an undercurrent or an overcurrent The value ok(1) indicates neither an undercurrent or an
condition was detected since the attribute was last cleared. overcurrent condition has been
detected since the attribute was last cleared.
The value underCurrent(2) indicates that the port current The value underCurrent(2) indicates that the port current
is below the minimal value since the attribute was last cleared. is below the minimal value since the attribute was last cleared.
The value overCurrent(3) indicates that the port current The value overCurrent(3) indicates that the port current
exceeds the maximal value since the attribute was last cleared. exceeds the maximal value since the attribute was last cleared. "
The value both(4) indicates that both underCurrent and overCurrent
since the attribute was last cleared.
This attribute is cleared through the pethPsePortCurrentStatusClear
action.
An undercurrent condition is detected when the current drawn from REFERENCE "[IEEE Draft P802.3af/D3.1, June 5, 2002 object 30.9.1.1.8 aPSEPowerCurrentStatus]"
the PSE at the MDI is less than
Off-mode current 2 for a duration greater than Under load time
limit.
An overcurrent condition is detected when the current drawn from the
PSE at the MDI is greater than the overload current limit
for a duration greater that Overload time limit.
The values Overload current limit, Overload time
limit, Off-mode current 2 and Under load time limit are specified in
Table 33-5. If a Clause 22 MII or Clause 35 GMII is present, then
this will map to the Under Current and Over Current bits
specified in 33.6.1.2.2 and 33.6.1.2.3.;"
REFERENCE "[IEEE DRAFT STANDARD FOR DTE POWER VIA MDI P802.3af/D1.2]"
::= { pethPsePortEntry 10 } ::= { pethPsePortEntry 10 }
pethPsePortCurrentStatusClear OBJECT-TYPE pethPsePortUnderCurrentCounter OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Counter32
clear(1), MAX-ACCESS read-only
off(2)
}
MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Setting the value of this object to clear(1) clears the value "Counts the number of times that the pethPsePortCurrentStatus
of the pethPsePortStatus and enable the agent to update the attribute changes from any
pethPsePortStatus. enumeration to the enumeration underCurrent ."
Read operation this value will be off(2)."
REFERENCE "[IEEE Draft P802.3af/D3.1, June 5, 2002 object 30.9.1.1.9 aPSEUnderCurrentCounter]"
::= { 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
enumeration to the enumeration overCurrent ."
REFERENCE "[IEEE Draft P802.3af/D3.1, June 5, 2002 object 30.9.1.1.10 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 a value
that indicates the type of the device that is connected that indicates the type of the device that is connected
to theport. This value can be the result of the mapping to theport. This value can be the result of the mapping
the address of the station connected to the port and of the address of the station connected to the port and of
the value of the pethPdPortType of the respective PD port." the value of the pethPdPortType of the respective PD port."
::= { pethPsePortEntry 12 } ::= { 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)
class5(6)
} }
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.
A read-only value that indicates the PD Class of a detected PD as
specified in IEEE Draft P802.3af/D2.1 Supplement to IEEE Std.802.3
November 14 2001 cclause 33.2.5 and 33.2.6.
The value is only valid while a valid PD is being detected as indicated The value is only valid while a valid PD is being detected
by the attribute pethPsePortDetectionStatus reporting the enumeration as indicated by the attribute
pethPsePortDetectionStatus reporting the enumeration
(detected) or (deliveringPower). (detected) or (deliveringPower).
" "
::= { pethPsePortEntry 13 } REFERENCE "[IEEE Draft P802.3af/D3.1, June 5, 2002 object 30.9.1.1.7 aPSEPowerClassification]"
::= { pethPsePortEntry 14 }
-- PD Port table -- PD Port table
pethPdPortTable OBJECT-TYPE pethPdPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF PethPdPortEntry SYNTAX SEQUENCE OF PethPdPortEntry
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 Powered characteristics power Ethernet ports on a Powered
skipping to change at page 15, line 31 skipping to change at page 16, line 22
both(3) both(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the pairs in use by the PD to derive power. "Describes the pairs in use by the PD to derive power.
A value of signal(1) indicates that only PD Pinout Mode A is A value of signal(1) indicates that only PD Pinout Mode A is
supported by the PD. supported by the PD.
A value of spare(2) indicates that only PD Pinout Mode B is A value of spare(2) indicates that only PD Pinout Mode B is
supported by the PD. supported by the PD.
A value of both(3) means indicates that both PD Pinout Mode A and PD A value of both(3) means indicates that both PD Pinout Mode A
Pinout Mode B are supported by the PD." and PD Pinout Mode B are supported by the PD."
::= { pethPdPortEntry 2 } ::= { pethPdPortEntry 2 }
pethPdPortDetectionStatus OBJECT-TYPE pethPdPortDetectionStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
off(1), off(1),
receivingPower(2) receivingPower(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the operational status of the port detection. "Describes the operational status of the port detection.
The value off(1) indicates that the PD is drawing a current less The value off(1) indicates that the PD is drawing a current less
than I than I Port as specified in [IEEE-802.3af]
Port as specified in IEEE Draft P802.3af/D2.1 Supplement to IEEE
Std.802.3 November 14 2001 Table 33-10.
The value receivingPower(2) indicates that the PD is drawing a The value receivingPower(2) indicates that the PD is drawing a
current greater I Port as specified in current greater I Port as specified in [IEEE-802.3af]
IEEE Draft P802.3af/D2.1 Supplement to
IEEE Std.802.3 November 14 2001 Table 33-10.
" "
REFERENCE "[IEEE Draft P802.3af/D3.1, June 5, 2002 object 30.9.2.1.2 aPDPowerStatus]"
::= { pethPdPortEntry 3 } ::= { pethPdPortEntry 3 }
pethPdPortType OBJECT-TYPE pethPdPortType 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-only MAX-ACCESS read-only
skipping to change at page 16, line 34 skipping to change at page 17, line 21
-- 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 the Main power
on a PSE device. Example internet switch midspan device can on a PSE device. Example internet switch midspan
control an Internet port and the Main Power supply unit's." device can control an
Ethernet port and the Main Power supply unit's."
::= { 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 power
of a PSE. " of a PSE. "
INDEX { pethMainPseGroupIndex } INDEX { pethMainPseGroupIndex }
skipping to change at page 17, line 20 skipping to change at page 18, line 9
INTEGER, INTEGER,
pethMainPseBackupActivated pethMainPseBackupActivated
TruthValue, TruthValue,
pethMainPseUsageThreshold pethMainPseUsageThreshold
INTEGER, INTEGER,
pethMainPseMaximumDcPower pethMainPseMaximumDcPower
INTEGER INTEGER
} }
pethMainPseGroupIndex OBJECT-TYPE pethMainPseGroupIndex OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (0..65535)
MAX-ACCESS not-accessible MAX-ACCESS read-only
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 the stack,
module in a rack) and the value 1 MUST be used for non-modular module in a rack) and the value 1 MUST be used for
devices " non-modular devices "
::= { pethMainPseEntry 1 } ::= { pethMainPseEntry 1 }
pethMainPsePower OBJECT-TYPE pethMainPsePower OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (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 }
pethMainPseOperStatus OBJECT-TYPE pethMainPseOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
on(1), on(1),
skipping to change at page 18, line 50 skipping to change at page 19, line 40
comparing the measured power and initiating comparing the measured power and initiating
an alarm if the threshold is exceeded." an alarm if the threshold is exceeded."
::= { pethMainPseEntry 7 } ::= { pethMainPseEntry 7 }
pethMainPseMaximumDcPower OBJECT-TYPE pethMainPseMaximumDcPower OBJECT-TYPE
SYNTAX INTEGER SYNTAX INTEGER
UNITS "Watts" UNITS "Watts"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the maximum available power in "describes the maximum available power in
Watt to be supplied by the DC backup source to this Watt to be supplied by the DC backup source to this
device." device."
::= { pethMainPseEntry 8 } ::= { pethMainPseEntry 8 }
-- Traps Control Objects -- Traps Control Objects
pethTrapsControl OBJECT IDENTIFIER ::= { pethObjects 4 } pethTrapsControl OBJECT IDENTIFIER ::= { pethObjects 4 }
pethTrapsControlTable OBJECT-TYPE pethTrapsControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF PethTrapsControlEntry SYNTAX SEQUENCE OF PethTrapsControlEntry
skipping to change at page 19, line 37 skipping to change at page 20, line 27
INDEX { pethTrapsControlGroupIndex } INDEX { pethTrapsControlGroupIndex }
::= { pethTrapsControlTable 1 } ::= { pethTrapsControlTable 1 }
PethTrapsControlEntry ::= SEQUENCE { PethTrapsControlEntry ::= SEQUENCE {
pethTrapsControlGroupIndex pethTrapsControlGroupIndex
INTEGER, INTEGER,
pethTrapsControlEnable pethTrapsControlEnable
INTEGER INTEGER
} }
pethTrapsControlGroupIndex OBJECT-TYPE pethTrapsControlGroupIndex OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (1..65535)
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 means
box in the stack, module in a rack and it is recommended (box in the stack, module in a rack) and recommend
that the value 1 MUST be used for non-modular devices " that the value 1 MUST be used for non-modular devices "
::= { pethTrapsControlEntry 1 } ::= { pethTrapsControlEntry 1 }
pethTrapsControlEnable OBJECT-TYPE pethTrapsControlEnable OBJECT-TYPE
SYNTAX INTEGER SYNTAX INTEGER
{ {
enable(1), enable(1),
disable(2) disable(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
skipping to change at page 20, line 20 skipping to change at page 21, line 10
::= { pethTrapsControlEntry 2 } ::= { pethTrapsControlEntry 2 }
-- --
-- Notifications Section -- Notifications Section
-- --
-- --
pethPsePortOnOffTrap NOTIFICATION-TYPE pethPsePortOnOffTrap NOTIFICATION-TYPE
OBJECTS { pethPsePortGroupIndex,pethPsePortIndex,pethPsePortDetectionStatus } OBJECTS { pethPsePortGroupIndex,pethPsePortIndex,pethPsePortDetectionStatus }
STATUS current STATUS current
DESCRIPTION " This trap indicate if Pse Port is delivering or not power to the PD." DESCRIPTION " This trap indicate if Pse Port is delivering
or not power to the PD."
::= { pethNotifications 1 } ::= { pethNotifications 1 }
pethPsePortCurrentStatusTrap NOTIFICATION-TYPE pethPsePortCurrentStatusTrap NOTIFICATION-TYPE
OBJECTS { pethPsePortGroupIndex,pethPsePortIndex,pethPsePortCurrentStatus } OBJECTS { pethPsePortGroupIndex,pethPsePortIndex,pethPsePortCurrentStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This trap indicate Port Change Status and it will be " This trap indicate Port Change Status and
sent on every status change." it will be sent on every status change."
::= { pethNotifications 2 } ::= { pethNotifications 2 }
pethMainPseBackUpActivatedTrap NOTIFICATION-TYPE pethMainPseBackUpActivatedTrap NOTIFICATION-TYPE
OBJECTS { pethPsePortGroupIndex,pethMainPseBackupActivated } OBJECTS { pethMainPseGroupIndex,pethMainPseBackupActivated }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This trap indicate BackUp is Activated or BackUp " This trap indicate BackUp is Activated or
is released." BackUp is released."
::= { pethNotifications 3 } ::= { pethNotifications 3 }
pethMainPowerUsageOnTrap NOTIFICATION-TYPE pethMainPowerUsageOnTrap NOTIFICATION-TYPE
OBJECTS { pethPsePortGroupIndex } OBJECTS { pethMainPseGroupIndex }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This trap indicate PSE Threshold usage indication is on , "This trap indicate PSE Threshold usage indication is on ,
the useage power is above the treshold." the usage power is above the threshold."
::= { pethNotifications 4 } ::= { pethNotifications 4 }
pethMainPowerUsageOffTrap NOTIFICATION-TYPE pethMainPowerUsageOffTrap NOTIFICATION-TYPE
OBJECTS { pethPsePortGroupIndex } OBJECTS { pethMainPseGroupIndex }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This trap indicate PSE Threshold usage indication off , "This trap indicate PSE Threshold usage indication off ,
the useage power is below the treshold.." the usage power is below the threshold.."
::= { pethNotifications 5 } ::= { pethNotifications 5 }
pethPsePortTrapGroup NOTIFICATION-GROUP pethPsePortTrapGroup NOTIFICATION-GROUP
NOTIFICATIONS { pethPsePortOnOffTrap, pethPsePortCurrentStatusTrap} NOTIFICATIONS { pethPsePortOnOffTrap, pethPsePortCurrentStatusTrap}
STATUS current STATUS current
DESCRIPTION DESCRIPTION "Pse trap indications"
"Pse trap indications"
::= { pethNotifications 6 } ::= { pethNotifications 6 }
pethMainPowerTrapGroup NOTIFICATION-GROUP pethMainPowerTrapGroup NOTIFICATION-GROUP
NOTIFICATIONS { pethMainPseBackUpActivatedTrap, pethMainPowerUsageOnTrap,pethMainPowerUsageOffTrap} NOTIFICATIONS { pethMainPseBackUpActivatedTrap, pethMainPowerUsageOnTrap,pethMainPowerUsageOffTrap}
STATUS current STATUS current
DESCRIPTION "Pse trap indications" DESCRIPTION "Pse trap indications"
::= { pethNotifications 7 } ::= { pethNotifications 7 }
-- --
-- Conformance Section -- Conformance Section
skipping to change at page 22, line 9 skipping to change at page 22, line 46
implement main power supply within a PSE Device." implement main power supply within a PSE Device."
GROUP pethTrapsControlGroup GROUP pethTrapsControlGroup
DESCRIPTION DESCRIPTION
"The pethTrapsControlGroup is mandatory for systems which "The pethTrapsControlGroup is mandatory for systems which
implement PSE ports." implement PSE ports."
::= { 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 MidSpan." "Describes the requirements for conformance to the PSE
and MID-Span."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS {pethPsePortGroup, pethMainPseGroup,pethTrapsControlGroup} MANDATORY-GROUPS {pethPsePortGroup, pethMainPseGroup,pethTrapsControlGroup}
::= { pethCompliances 2 } ::= { pethCompliances 2 }
pethPdCompliance MODULE-COMPLIANCE pethPdCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the requirements for conformance to the PSE "Describes the requirements for conformance to the PD."
and MidSpan."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS {pethPdPortGroup} MANDATORY-GROUPS {pethPdPortGroup}
::= { pethCompliances 3 } ::= { pethCompliances 3 }
pethPsePortGroup OBJECT-GROUP pethPsePortGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pethPsePortGroupIndex, pethPsePortGroupIndex,
pethPsePortIndex, pethPsePortIndex,
pethPsePortAdminEnable, pethPsePortAdminEnable,
pethPsePortPowerPairsControlAbility, pethPsePortPowerPairsControlAbility,
pethPsePortPowerPairs, pethPsePortPowerPairs,
pethPsePortDetectionStatus, pethPsePortDetectionStatus,
pethPsePortPowerPriority, pethPsePortPowerPriority,
pethPsePortCurrentStatus, pethPsePortCurrentStatus,
pethPsePortCurrentStatusClear, pethPsePortUnderCurrentCounter,
pethPsePortOverCurrentCounter,
pethPsePortType, pethPsePortType,
pethPsePortPowerClassifications pethPsePortPowerClassifications
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PSE Port Objects." "PSE Port Objects."
::= { pethGroups 1 } ::= { pethGroups 1 }
pethPdPortGroup OBJECT-GROUP pethPdPortGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 25, line 6 skipping to change at page 25, line 46
"Introduction to Version 3 of the Internet-standard Network "Introduction to Version 3 of the Internet-standard Network
Management Framework", RFC 2570, April 1999. 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 Objects
for the Ethernet-like Interface Types", RFC 2665, August 1999. for the Ethernet-like Interface Types", RFC 2665, August 1999.
[IEEE-802.3af] IEEE 802.3af Working Group, "Data Terminal Equipment (DTE) [IEEE-802.3af] IEEE 802.3af Working Group, "Data Terminal Equipment (DTE)
Power via Media Dependent Interface (MDI)", Draft D2.1, Power via Media Dependent Interface (MDI)", Draft D3.1,
November 2001. November 2001.
[PWR-MIB] Romascanu, D., " Power Ethernet (DTE Power via MDI) MIB", [PWR-MIB] Romascanu, D., " Power Ethernet (DTE Power via MDI) MIB",
Internet-Draft, draft-romascanu-hubmib-power-ethernet-mib-00.txt, Internet-Draft, draft-romascanu-hubmib-power-ethernet-mib-00.txt,
February 2001. June 2002.
9.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
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/