draft-ietf-hubmib-power-ethernet-mib-02.txt   draft-ietf-hubmib-power-ethernet-mib-03.txt 
Internet Draft Avi Berger Internet Draft Avi Berger
PowerDsine Inc. PowerDsine Inc.
Dan Romascanu Dan Romascanu
Avaya Inc. Avaya Inc.
30 June 2002 30 October 2002
Power Ethernet (DTE Power via MDI) MIB Power Ethernet (DTE Power via MDI) MIB
<draft-ietf-hubmib-power-ethernet-mib-02.txt> <draft-ietf-hubmib-power-ethernet-mib-03.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
skipping to change at page 2, line 8 skipping to change at page 2, line 8
Table of Contents Table of Contents
Status of this Memo 1 Status of this Memo 1
Abstract 1 Abstract 1
1 Introduction 2 1 Introduction 2
2 The SNMP Management Framework 2 2 The 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 9
8 References 24 8 References 24
9 Intellectual Property 26 9 Intellectual Property 26
10 Security Considerations 26 10 Security Considerations 26
11 Authors Addresses 27 11 Authors Addresses 27
A Full Copyright Statement 27 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.
skipping to change at page 3, line 48 skipping to change at page 3, line 48
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 will not define a full management interface, but The IEEE 802.3af WG will 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 a management
interfaces to be built for a powered Ethernet device. The MIB module interfaces to be built for a powered Ethernet device. The MIB module
defined in this document extends the Ethernet-like Interfaces MIB defined in this document extends the Ethernet-like Interfaces MIB
[RFC2665] with the management objects required for the management of [RFC2665] with the management objects required for the management of
the powered Ethernet devices and ports. the powered Ethernet devices and ports.
The following abbreviations are defined in [IEEE-802.3af] and will be The following abbreviations are defined in [IEEE-802.3af] and will be
used with the same significance in this document: PSE - Power used with the same significance in this document:
Sourcing Equipment; PD - Powered Device
PSE - Power Sourcing Equipment;
PD - Powered Device
4. MIB Structure 4. MIB Structure
This MIB objects are included in four MIB groups - three of them This MIB objects are included in four MIB groups - three of them
include MIB tables, and the fourth scalar objects include MIB tables, and the fourth scalar objects
The pethPsePortTable defines the objects used for the configuration The pethPsePortTable defines the objects used for the configuration
and describing the status of ports on a PSE device. Examples of PSE and describing the status of ports on a PSE device. Examples of PSE
devices are Ethernet switches that support power Ethernet and mid- devices are Ethernet switches that support power Ethernet and mid-
span boxes. span boxes.
skipping to change at page 7, line 48 skipping to change at page 8, line 5
12. change pethPsePortType OID to end with 13 12. change pethPsePortType OID to end with 13
13. change pethPsePortPowerClassifications OID to end with 14 13. change pethPsePortPowerClassifications OID to end with 14
14. update pethPsePortGroup OBJECT-GROUP 14. update pethPsePortGroup OBJECT-GROUP
15. chage reference to new IEEE Draft 15. chage reference to new IEEE Draft
16. change pethPdCompliance description. 16. change pethPdCompliance description.
The following changes were introduced between draft-ietf-hubmib-
power-ethernet-mib-02.txt and draft-ietf-hubmib-power-ethernet-
mib-03.txt:
1. remove pethPsePortGroupIndex and pethPsePortIndex from
pethPsePortOnOffTrap and pethPsePortCurrentStatusTrap
2. change pethPsePortGroupIndex and pethPsePortIndex MAX-ACCESS to
not-accessible
3. remove pethMainPseGroupIndex from pethMainPseBackUpActivatedTrap
4. replace pethMainPseGroupIndex with pethMainPseConsumptionPower in
pethMainPowerUsageOnTrap and pethMainPowerUsageOffTrap
5. change pethMainPseGroupIndex MAX-ACCESS to not-accessible
6. move pethPsePortTrapGroup NOTIFICATION-GROUP and
pethMainPowerTrapGroup NOTIFICATION-GROUP to the Conformance Section
7. update the discription of pethPsePortOnOffTrap
8. add pethPsePortPowerDetectionControl to pethPsePortGroup
9. change reference to IEEE Draft P802.3af/D3.3 October 2002
10. delete enumaration pethPsePortDetectionStatus detected(3) and
invalidPD(6)
11. change pethPsePortCurrentStatus to
pethPsePortPowerMaintenanceStatus
12 . change pethPsePortUnderCurrentCounter to
pethPsePortMPSAbsentCounter
13. add pethPdPortAdminEnable object.
14. replace Trap with Notification.
15. update pethPsePortOnOffNotification description.
16. update pethPsePortDetectionStatus description.
17. remove pethPdPortPowerPairs object.
18. remove pethPdPortDetectionStatus object.
19. remove pethPdPortType object.
20. change pethPdPortAdminEnable OID.
7. Definitions 7. Definitions
POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32 , Gauge32,Counter32 ,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 "200206260000Z" -- June 26, 2002 LAST-UPDATED "200210190000Z" -- October 19, 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 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 Powere Ethernet (DTE Power via MDI) standard. 802.af Powered 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 10, line 11 skipping to change at page 11, line 13
pethPsePortPowerPairsControlAbility pethPsePortPowerPairsControlAbility
TruthValue, TruthValue,
pethPsePortPowerPairs pethPsePortPowerPairs
INTEGER, INTEGER,
pethPsePortPowerDetectionControl pethPsePortPowerDetectionControl
INTEGER, INTEGER,
pethPsePortDetectionStatus pethPsePortDetectionStatus
INTEGER, INTEGER,
pethPsePortPowerPriority pethPsePortPowerPriority
INTEGER, INTEGER,
pethPsePortCurrentStatus pethPsePortPowerMaintenanceStatus
INTEGER, INTEGER,
pethPsePortUnderCurrentCounter pethPsePortMPSAbsentCounter
Counter32, Counter32,
pethPsePortOverCurrentCounter pethPsePortOverCurrentCounter
Counter32, 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 not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable uniquely identifies the group "This variable uniquely identifies the group
containing the port to which power Ethernet PSE is connected. containing the port to which a power Ethernet PSE is connected.
Group means (box in the stack, module in a rack) and the value 1 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 .
pethPseMidSpanGroupCapacity is the number of Mid-Span PSE
groups that can be contained within the Mid-Span PSE."
::= { pethPsePortEntry 1 } ::= { pethPsePortEntry 1 }
pethPsePortIndex OBJECT-TYPE pethPsePortIndex OBJECT-TYPE
SYNTAX INTEGER(1..2147483647) SYNTAX INTEGER(1..2147483647)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable uniquely identifies the power Ethernet PSE "This variable uniquely identifies the power Ethernet PSE
port within group pethPseGroupIndex to which the port within group pethPseGroupIndex to which the
power Ethernet PSE entry is connected." power Ethernet PSE entry is connected."
::= { pethPsePortEntry 2 } ::= { pethPsePortEntry 2 }
pethPsePortAdminEnable OBJECT-TYPE pethPsePortAdminEnable OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
enable(1), enable(1),
skipping to change at page 12, line 12 skipping to change at page 13, line 17
mechanism of the port. mechanism of the port.
Setting the value test(2) puts the port in a Setting the value test(2) puts the port in a
testmode: force continuous discovery without applying testmode: force continuous discovery without applying
power regardless of whether PD detected." power regardless of whether PD detected."
::= { pethPsePortEntry 6 } ::= { pethPsePortEntry 6 }
pethPsePortDetectionStatus OBJECT-TYPE pethPsePortDetectionStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
disabled(1), disabled(1),
searching(2), searching(2),
detected(3),
deliveringPower(4), deliveringPower(4),
fault(5), fault(5),
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 A value of disabled(1)- indicates that the PSE State diagram is in
has been disabled. the state IDLE
A value of searching(2) indicates that the PD Detection function A value of searching(2)- indicates that the PSE State diagram is in
is enabled and is searching for a valid PD. the state DETECTION, CLASSIFICATION, SIGNATURE_INVALID or BACKOFF.
A value of detected(3)indicates that the PD Detection function A value of deliveringPower(4) - indicates that the PSE State diagram
has detected a valid PD but the PSE is not supplying power. is in the state POWER_UP, POWER_ON or POWER_OFF.
A value of deliveringPower(4) indicates that the port A value of fault(5) - indicates that the PSE State diagram is in the
executed the detection algorithm, found a PD connection state TEST_ERROR or the state IDLE due to the variable error
and is currently delivering power. condition.
A value of fault(5) indicates that a fault was detected Faults detected are vendor specific.
on the port , faults detected are vendor-specific. A value of test(7) - indicates that the PSE State diagram is in the
A value of invalidPD(6)indicates that the PD Detection function state TEST_MODE.
has detected an invalid PD.
A value of test(7)indicates that the PD Detection function has
been placed in test mode.
A value of denyLowPriority(8) indicates that the port was 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 13, line 15 skipping to change at page 14, line 15
DESCRIPTION DESCRIPTION
"This object controls the priority of the port from the point "This object controls the priority of the port from the point
of view of a power management algorithm. The priority that of view of a power management algorithm. The priority that
is set by this variable could be used by a control mechanism is set by this variable could be used by a control mechanism
that prevents over current situations by disconnecting first that prevents over current situations by disconnecting first
ports with lower power priority. Ports that connect devices ports with lower power priority. Ports that connect devices
critical to the operation of the network - like the E911 critical to the operation of the network - like the E911
telephones ports - should be set to higher priority." telephones ports - should be set to higher priority."
::= { pethPsePortEntry 8 } ::= { pethPsePortEntry 8 }
pethPsePortCurrentStatus OBJECT-TYPE pethPsePortPowerMaintenanceStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
ok(1), ok(1),
underCurrent(2), underCurrent(2),
overCurrent(3) mPSAbsent(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes a current port status related to the power generation "The value ok(1) indicates the Power Maintenance
The value ok(1) indicates neither an undercurrent or an Signature is present and the overcurrent condition has not been
overcurrent condition has been detected.
detected since the attribute was last cleared. The value overCurrent (2) indicates an overcurrent condition
The value underCurrent(2) indicates that the port current has been detected.
is below the minimal value since the attribute was last cleared. The value mPSAbsent(3) indicates that the Power Maintenance
The value overCurrent(3) indicates that the port current Signature is absent."
exceeds the maximal value since the attribute was last cleared. "
REFERENCE "[IEEE Draft P802.3af/D3.1, June 5, 2002 object 30.9.1.1.8 aPSEPowerCurrentStatus]" REFERENCE "[IEEE Draft P802.3af/D3.3, October, 2002, 30.9.1.1.8
aPSEPowerMaintenanceStatus]"
::= { pethPsePortEntry 10 } ::= { pethPsePortEntry 10 }
pethPsePortUnderCurrentCounter OBJECT-TYPE pethPsePortMPSAbsentCounter OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Counts the number of times that the pethPsePortCurrentStatus "Counts the number of times that the
attribute changes from any pethPsePortPowerMaintenanceStatus attribute changes from any
enumeration to the enumeration underCurrent ." value to the value mPSAbsent(3)."
REFERENCE "[IEEE Draft P802.3af/D3.3, October, 2002, object 30.9.1.1.9
REFERENCE "[IEEE Draft P802.3af/D3.1, June 5, 2002 object 30.9.1.1.9 aPSEUnderCurrentCounter]" aPSEUnderCurrentCounter]"
::= { pethPsePortEntry 11 } ::= { pethPsePortEntry 11 }
pethPsePortOverCurrentCounter OBJECT-TYPE pethPsePortOverCurrentCounter OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Counts the number of times that the aPSEPowerCurrentStatus "Counts the number of times that the aPSEPowerCurrentStatus
attribute changes from any attribute changes from any value to the value overCurrent(2)."
enumeration to the enumeration overCurrent ." REFERENCE "[IEEE Draft P802.3af/D3.3, October, 2002, object 30.9.1.1.10
REFERENCE "[IEEE Draft P802.3af/D3.1, June 5, 2002 object 30.9.1.1.10 aPSEOverCurrentCounter]" aPSEOverCurrentCounter]"
::= { pethPsePortEntry 12 } ::= { 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
skipping to change at page 14, line 45 skipping to change at page 15, line 45
class4(5) class4(5)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Classification is a way to tag different terminals on the "Classification is a way to tag different terminals on the
Power over LAN network according to their power consumption. Power over LAN network according to their power consumption.
Devices such as IP telephones, WLAN access points and others, Devices such as IP telephones, WLAN access points and others,
will be classified according to their power requirements. will be classified according to their power requirements.
The value is only valid while a valid PD is being detected The value is only valid while a valid PD is being detected as
as indicated by the attribute indicated by the attribute pethPsePortDetectionStatus reporting
pethPsePortDetectionStatus reporting the enumeration the value or deliveringPower(4)."
(detected) or (deliveringPower). REFERENCE "[IEEE Draft P802.3af/D3.3, October , 2002,
" object 30.9.1.1.7 aPSEPowerClassification]"
REFERENCE "[IEEE Draft P802.3af/D3.1, June 5, 2002 object 30.9.1.1.7 aPSEPowerClassification]"
::= { pethPsePortEntry 14 } ::= { 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
Device(PD) device. This group will be implemented in Device(PD) device. This group will be implemented in
skipping to change at page 15, line 32 skipping to change at page 16, line 30
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that display and control the power "A set of objects that display and control the power
characteristics of a Powered Device port." characteristics of a Powered Device port."
INDEX { pethPdPortIndex } INDEX { pethPdPortIndex }
::= { pethPdPortTable 1 } ::= { pethPdPortTable 1 }
PethPdPortEntry ::= SEQUENCE { PethPdPortEntry ::= SEQUENCE {
pethPdPortIndex pethPdPortIndex
INTEGER, INTEGER,
pethPdPortPowerPairs pethPdPortAdminEnable
INTEGER,
pethPdPortDetectionStatus
INTEGER,
pethPdPortType
INTEGER INTEGER
} }
pethPdPortIndex OBJECT-TYPE pethPdPortIndex OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (0..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index value that uniquely identifies an "An index value that uniquely identifies an
interface to a PD device. The interface to a PD device. The
interface identified by a particular value of interface identified by a particular value of
this index is the same interface as identified this index is the same interface as identified
by the same value of ifIndex. The mapping by the same value of ifIndex. The mapping
between the ifIndex values and the numbering of between the ifIndex values and the numbering of
the port on the device is an implementation the port on the device is an implementation
issue." issue."
::= { pethPdPortEntry 1 } ::= { pethPdPortEntry 1 }
pethPdPortAdminEnable OBJECT-TYPE
pethPdPortPowerPairs OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
signal(1), enable(1),
spare(2), disable(2)
both(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the pairs in use by the PD to derive power. "This value identifies the operational state of the PD functions.
A value of signal(1) indicates that only PD Pinout Mode A is An interface which can provide the PD functions will be enabled
supported by the PD. to do so when this attribute has the value enable. When this
A value of spare(2) indicates that only PD Pinout Mode B is attribute has the value disable the interface will act
supported by the PD. as it would if it had no PD function."
A value of both(3) means indicates that both PD Pinout Mode A
and PD Pinout Mode B are supported by the PD."
::= { pethPdPortEntry 2 } ::= { pethPdPortEntry 2 }
pethPdPortDetectionStatus OBJECT-TYPE
SYNTAX INTEGER {
off(1),
receivingPower(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Describes the operational status of the port detection.
The value off(1) indicates that the PD is drawing a current less
than I Port as specified in [IEEE-802.3af]
The value receivingPower(2) indicates that the PD is drawing a
current greater I Port as specified in [IEEE-802.3af]
"
REFERENCE "[IEEE Draft P802.3af/D3.1, June 5, 2002 object 30.9.2.1.2 aPDPowerStatus]"
::= { pethPdPortEntry 3 }
pethPdPortType OBJECT-TYPE
SYNTAX INTEGER {
other(1),
telephone(2),
webcam(3),
wireless(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of the device. A management application may read
the value of this variable and use it for setting the
corresponding value of pethPsePortType of the port that
connects the device."
::= { pethPdPortEntry 4 }
-- 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 on a PSE device. Example - an Ethernet switch midspan device can
device can control an control an Ethnternet port and the Main Power supply unit's."
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 18, line 9 skipping to change at page 18, line 16
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 read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable uniquely identifies the group to which "This variable uniquely identifies the group to which
power Ethernet PSE is connected.Group means (box in the stack, power Ethernet PSE is connected.Group means (box in the stack,
module in a rack) and the value 1 MUST be used for module in a rack) and the value 1 MUST be used for non-modular
non-modular devices " devices "
::= { pethMainPseEntry 1 } ::= { pethMainPseEntry 1 }
pethMainPsePower OBJECT-TYPE pethMainPsePower OBJECT-TYPE
SYNTAX Integer32 (1..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 }
skipping to change at page 19, line 19 skipping to change at page 19, line 25
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"reflects the presence of a backup PSE ." "reflects the presence of a backup PSE ."
::= { pethMainPseEntry 5 } ::= { pethMainPseEntry 5 }
pethMainPseBackupActivated OBJECT-TYPE pethMainPseBackupActivated OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Reflects the activation status of the backup PSE . "- reflects the activation status of the backup PSE .
The value true Backup is activated." The value true Backup is activated."
::= { pethMainPseEntry 6 } ::= { pethMainPseEntry 6 }
pethMainPseUsageThreshold OBJECT-TYPE pethMainPseUsageThreshold OBJECT-TYPE
SYNTAX INTEGER (1..99) SYNTAX INTEGER (1..99)
UNITS "%" UNITS "%"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The usage threshold expressed in percens for "The usage threshold expressed in percents for
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 }
-- Notification Control Objects
-- Traps Control Objects pethNotificationControl OBJECT IDENTIFIER ::= { pethObjects 4 }
pethTrapsControl OBJECT IDENTIFIER ::= { pethObjects 4 }
pethTrapsControlTable OBJECT-TYPE pethNotificationControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF PethTrapsControlEntry SYNTAX SEQUENCE OF PethNotificationControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that display and control the Traps "A table of objects that display and control the Notification
on a PSE device." on a PSE device."
::= { pethTrapsControl 1 } ::= { pethNotificationControl 1 }
pethTrapsControlEntry OBJECT-TYPE pethNotificationControlEntry OBJECT-TYPE
SYNTAX PethTrapsControlEntry SYNTAX PethNotificationControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of objects that control the Trap events." "A set of objects that control the Notification events."
INDEX { pethTrapsControlGroupIndex } INDEX { pethNotificationControlGroupIndex }
::= { pethTrapsControlTable 1 } ::= { pethNotificationControlTable 1 }
PethTrapsControlEntry ::= SEQUENCE { PethNotificationControlEntry ::= SEQUENCE {
pethTrapsControlGroupIndex pethNotificationControlGroupIndex
INTEGER, INTEGER,
pethTrapsControlEnable pethNotificationControlEnable
INTEGER INTEGER
} }
pethTrapsControlGroupIndex OBJECT-TYPE pethNotificationControlGroupIndex OBJECT-TYPE
SYNTAX INTEGER (1..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 recommend box in the stack, module in a rack and it is RECOMENDED
that the value 1 MUST be used for non-modular devices " that the value 1 be used for non-modular devices "
::= { pethTrapsControlEntry 1 } ::= { pethNotificationControlEntry 1 }
pethTrapsControlEnable OBJECT-TYPE pethNotificationControlEnable OBJECT-TYPE
SYNTAX INTEGER SYNTAX INTEGER
{ {
enable(1), enable(1),
disable(2) disable(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Enable Traps from Agent" "Enable Notification from Agent"
::= { pethTrapsControlEntry 2 } ::= { pethNotificationControlEntry 2 }
-- --
-- Notifications Section -- Notifications Section
-- --
-- --
pethPsePortOnOffTrap NOTIFICATION-TYPE pethPsePortOnOffNotification NOTIFICATION-TYPE
OBJECTS { pethPsePortGroupIndex,pethPsePortIndex,pethPsePortDetectionStatus } OBJECTS { pethPsePortDetectionStatus }
STATUS current STATUS current
DESCRIPTION " This trap indicate if Pse Port is delivering DESCRIPTION
or not power to the PD." " 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."
::= { pethNotifications 1 } ::= { pethNotifications 1 }
pethPsePortCurrentStatusTrap NOTIFICATION-TYPE pethPsePortPowerMaintenanceStatusNotification NOTIFICATION-TYPE
OBJECTS { pethPsePortGroupIndex,pethPsePortIndex,pethPsePortCurrentStatus } OBJECTS { pethPsePortPowerMaintenanceStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This trap indicate Port Change Status and " This Notification indicates a Port Change Status and it
it will be sent on every status change." SHOULD be sent on every status change."
::= { pethNotifications 2 } ::= { pethNotifications 2 }
pethMainPseBackUpActivatedTrap NOTIFICATION-TYPE pethMainPseBackUpActivatedNotification NOTIFICATION-TYPE
OBJECTS { pethMainPseGroupIndex,pethMainPseBackupActivated } OBJECTS { pethMainPseBackupActivated }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This trap indicate BackUp is Activated or " This Notification indicate BackUp is Activated or BackUp is
BackUp is released." released."
::= { pethNotifications 3 } ::= { pethNotifications 3 }
pethMainPowerUsageOnTrap NOTIFICATION-TYPE pethMainPowerUsageOnNotification NOTIFICATION-TYPE
OBJECTS { pethMainPseGroupIndex } OBJECTS { pethMainPseConsumptionPower }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This trap indicate PSE Threshold usage indication is on, " This Notification indicate PSE Threshold usage indication is
the usage power is above the threshold." on, the usage power is above the threshold."
::= { pethNotifications 4 } ::= { pethNotifications 4 }
pethMainPowerUsageOffTrap NOTIFICATION-TYPE pethMainPowerUsageOffNotification NOTIFICATION-TYPE
OBJECTS { pethMainPseGroupIndex } OBJECTS { pethMainPseConsumptionPower }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This trap indicate PSE Threshold usage indication off, " This Notification indicate PSE Threshold usage indication
the usage power is below the threshold.." off, the usage power is below the threshold."
::= { pethNotifications 5 } ::= { pethNotifications 5 }
pethPsePortTrapGroup NOTIFICATION-GROUP
NOTIFICATIONS { pethPsePortOnOffTrap, pethPsePortCurrentStatusTrap}
STATUS current
DESCRIPTION "Pse trap indications"
::= { pethNotifications 6 }
pethMainPowerTrapGroup NOTIFICATION-GROUP
NOTIFICATIONS { pethMainPseBackUpActivatedTrap, pethMainPowerUsageOnTrap,pethMainPowerUsageOffTrap}
STATUS current
DESCRIPTION "Pse trap indications"
::= { pethNotifications 7 }
-- --
-- Conformance Section -- Conformance Section
-- --
pethCompliances OBJECT IDENTIFIER ::= { pethConformance 1 } pethCompliances OBJECT IDENTIFIER ::= { pethConformance 1 }
pethGroups OBJECT IDENTIFIER ::= { pethConformance 2 } pethGroups OBJECT IDENTIFIER ::= { pethConformance 2 }
pethCompliance MODULE-COMPLIANCE pethCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the requirements for conformance to the "Describes the requirements for conformance to the
skipping to change at page 22, line 37 skipping to change at page 22, line 32
"The pethPsePortGroup is mandatory for systems which "The pethPsePortGroup is mandatory for systems which
implement PSE ports." implement PSE ports."
GROUP pethPdPortGroup GROUP pethPdPortGroup
DESCRIPTION DESCRIPTION
"The pethPdPortGroup is mandatory for systems which "The pethPdPortGroup is mandatory for systems which
implement PD Ports." implement PD Ports."
GROUP pethMainPseGroup GROUP pethMainPseGroup
DESCRIPTION DESCRIPTION
"The pethMainPseGroup is mandatory for systems which "The pethMainPseGroup is mandatory for systems which
implement main power supply within a PSE Device." implement main power supply within a PSE Device."
GROUP pethTrapsControlGroup GROUP pethNotificationControlGroup
DESCRIPTION DESCRIPTION
"The pethTrapsControlGroup is mandatory for systems which "The pethNotificationControlGroup 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 "Describes the requirements for conformance to the PSE and MID-
and MID-Span." Span."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS {pethPsePortGroup, pethMainPseGroup,pethTrapsControlGroup} MANDATORY-GROUPS {pethPsePortGroup, pethMainPseGroup,pethNotificationControlGroup}
::= { pethCompliances 2 } ::= { pethCompliances 2 }
pethPdCompliance MODULE-COMPLIANCE pethPdCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the requirements for conformance to the PD." "Describes the requirements for conformance to the PD."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS {pethPdPortGroup} MANDATORY-GROUPS {pethPdPortGroup}
::= { pethCompliances 3} ::= { pethCompliances 3}
pethPsePortGroup OBJECT-GROUP pethPsePortGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 23, line 14 skipping to change at page 23, line 13
pethPdCompliance MODULE-COMPLIANCE pethPdCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the requirements for conformance to the PD." "Describes the requirements for conformance to the PD."
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,
pethPsePortIndex,
pethPsePortAdminEnable, pethPsePortAdminEnable,
pethPsePortPowerPairsControlAbility, pethPsePortPowerPairsControlAbility,
pethPsePortPowerDetectionControl,
pethPsePortPowerPairs, pethPsePortPowerPairs,
pethPsePortDetectionStatus, pethPsePortDetectionStatus,
pethPsePortPowerPriority, pethPsePortPowerPriority,
pethPsePortCurrentStatus, pethPsePortPowerMaintenanceStatus ,
pethPsePortUnderCurrentCounter, pethPsePortMPSAbsentCounter,
pethPsePortOverCurrentCounter, 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 {
pethPdPortPowerPairs, pethPdPortAdminEnable
pethPdPortDetectionStatus,
pethPdPortType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"PD Port Objects." "PD Port Objects."
::= { pethGroups 2 } ::= { pethGroups 2 }
pethMainPseGroup OBJECT-GROUP pethMainPseGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pethMainPsePower, pethMainPsePower,
pethMainPseOperStatus, pethMainPseOperStatus,
skipping to change at page 24, line 10 skipping to change at page 24, line 6
pethMainPseBackupPresent, pethMainPseBackupPresent,
pethMainPseBackupActivated, pethMainPseBackupActivated,
pethMainPseUsageThreshold, pethMainPseUsageThreshold,
pethMainPseMaximumDcPower pethMainPseMaximumDcPower
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Main PSE Objects. " "Main PSE Objects. "
::= { pethGroups 3 } ::= { pethGroups 3 }
pethTrapsControlGroup OBJECT-GROUP pethNotificationControlGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pethTrapsControlEnable pethNotificationControlEnable
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Trap Control Objects. " "Notification Control Objects. "
::= { pethGroups 4 } ::= { pethGroups 4 }
pethPsePortNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { pethPsePortOnOffNotification,
pethPsePortPowerMaintenanceStatusNotification}
STATUS current
DESCRIPTION "Pse Notification indications"
::= { pethCompliances 4 }
pethMainPowerNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { pethMainPseBackUpActivatedNotification,
pethMainPowerUsageOnNotification,
pethMainPowerUsageOffNotification}
STATUS current
DESCRIPTION "Pse Notification indications"
::= { pethCompliances 5 }
END END
8. References 8. References
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
for Describing SNMP Management Frameworks", RFC 2571, April for Describing SNMP Management Frameworks", RFC 2571, April
1999. 1999.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification
of Management Information for TCP/IP-based Internets", STD of Management Information for TCP/IP-based Internets", STD
skipping to change at page 25, line 46 skipping to change at page 26, line 7
"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 D3.1, Power via Media Dependent Interface (MDI)", Draft D3.3,
November 2001. October 2002.
[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,
June 2002. 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
skipping to change at page 26, line 39 skipping to change at page 26, line 48
There are a number of management objects defined in this MIB There are a number of management objects defined in this MIB
that have a MAX-ACCESS clause of read-write and/or read-create. that have a MAX-ACCESS clause of read-write and/or read-create.
Such objects may be considered sensitive or vulnerable in some Such objects may be considered sensitive or vulnerable in some
network environments. The support for SET operations in a network environments. The support for SET operations in a
non-secure environment without proper protection can have a non-secure environment without proper protection can have a
negative effect on network operations. negative effect on network operations.
There are a number of managed objects in this MIB that may There are a number of managed objects in this MIB that may
contain sensitive information. These are: contain sensitive information. These are:
pethPsePortPowerPairsControlAbility
pethPsePortPowerPriority
pethPsePortPowerClassifications
It is thus important to control even GET access to these objects It is thus important to control even GET access to these objects
and possibly to even encrypt the values of these object when and possibly to even encrypt the values of these object when
sending them over the network via SNMP. Not all versions of sending them over the network via SNMP. Not all versions of
SNMP provide features for such a secure environment. SNMP provide features for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if the SNMPv1 by itself is not a secure environment. Even if the
network itself is secure (for example by using IPSec), even then, network itself is secure (for example by using IPSec), even then,
there is no control as to who on the secure network is allowed there is no control as to who on the secure network is allowed
to access and GET/SET (read/change/create/delete) the objects in to access and GET/SET (read/change/create/delete) the objects in
this MIB. this MIB.
 End of changes. 

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