Diff: draft-ietf-hubmib-power-ethernet-mib-03.txt - draft-ietf-hubmib-power-ethernet-mib-04.txt

	draft-ietf-hubmib-power-ethernet-mib-03.txt	draft-ietf-hubmib-power-ethernet-mib-04.txt

	Internet Draft Avi Berger	Internet Draft Avi Berger
	PowerDsine Inc.	PowerDsine Inc.
	Dan Romascanu	Dan Romascanu
	Avaya Inc.	Avaya Inc.

	30 October 2002	19 December 2002

	Power Ethernet (DTE Power via MDI) MIB	Power Ethernet (DTE Power via MDI) MIB


	<draft-ietf-hubmib-power-ethernet-mib-03.txt>	<draft-ietf-hubmib-power-ethernet-mib-04.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 9	7 Definitions 10
	8 References 24	8 Normative References 24
	9 Intellectual Property 26	9 Informative References 25
	10 Security Considerations 26	10 Intellectual Property 26
	11 Authors Addresses 27	11 Security Considerations 27
	A Full Copyright Statement 27	12 Authors Addresses 27
		A Full Copyright Statement 28

	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 9, line 7	skipping to change at page 9, line 7
	16. update pethPsePortDetectionStatus description.	16. update pethPsePortDetectionStatus description.

	17. remove pethPdPortPowerPairs object.	17. remove pethPdPortPowerPairs object.

	18. remove pethPdPortDetectionStatus object.	18. remove pethPdPortDetectionStatus object.

	19. remove pethPdPortType object.	19. remove pethPdPortType object.

	20. change pethPdPortAdminEnable OID.	20. change pethPdPortAdminEnable OID.


		The following changes were introduced between draft-ietf-hubmib-
		power-ethernet-mib-03.txt and draft-ietf-hubmib-power-ethernet-
		mib-04.txt:

		1. remove pethMainPseMaximumDcPower object

		2. remove pethMainPseBackupPresent object

		3. remove pethMainPseBackupActivated object.

		4. remove pethMainPseBackUpActivatedNotification

		5. change reference from IEEE Draft P802.3af/D3.3, October, 2002 to
		IEEE Draft P802.3af/D4.0, November, 2002

		6. DESCRIPTION "Initial version, published as RFC yyyy."

		7. change the syntax of pethPsePortGroupIndex from INTEGER
		(1..2147483647) to Integer32 (1..2147483647).

		8. change the syntax of pethPsePortIndex from INTEGER (1..2147483647)
		to Integer32 (1..2147483647).

		9.change the syntax of pethPdPortIndex from INTEGER (0..65535) to
		InterfaceIndex.

		10.import InterfaceIndex from IF-MIB.

		11. change the syntax of pethMainPseGroupIndex from INTEGER
		(0..65535) to Integer32 (1..2147483647)

		12. change the syntax of pethMainPseUsageThreshold from INTEGER
		(1..99) to Integer32 (1..99).

		13. change the syntax of pethNotificationControlGroupIndex from
		INTEGER (1..65535) to Integer32 (1..2147483647)

		14. replace OID: ! pethNotifications OBJECT IDENTIFIER ::= {
		powerEthernetMIB 0 } ! pethObjects OBJECT IDENTIFIER ::= {
		powerEthernetMIB 1 } ! pethConformance OBJECT IDENTIFIER ::= {
		powerEthernetMIB 2 }

		15. change the discription of the pethPsePortGroup and
		pethPdPortGroup

		16. pethMainPsePower changed to Gauge32
		17. add: REVISION "200212020000Z" -- December 02, 2002
		DESCRIPTION "Initial version, published as RFC yyyy."
		18 change the MIB registered from { dot3 20 } ::= {
		mib-2 XXX } -- RFC Ed.: replace XXX with IANA-assigned
		number & remove this notice

	7. Definitions	7. Definitions

	POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN	POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN

	IMPORTS	IMPORTS

	MODULE-IDENTITY, OBJECT-TYPE, Integer32 , Gauge32,Counter32,	MODULE-IDENTITY, mib-2, OBJECT-TYPE, Integer32,
	NOTIFICATION-TYPE	Gauge32, Counter32, NOTIFICATION-TYPE
	FROM SNMPv2-SMI	FROM SNMPv2-SMI

	dot3
	FROM EtherLike-MIB
	TruthValue	TruthValue
	FROM SNMPv2-TC	FROM SNMPv2-TC

		InterfaceIndex
		FROM IF-MIB
	MODULE-COMPLIANCE, OBJECT-GROUP ,NOTIFICATION-GROUP	MODULE-COMPLIANCE, OBJECT-GROUP ,NOTIFICATION-GROUP
	FROM SNMPv2-CONF;	FROM SNMPv2-CONF;

	powerEthernetMIB MODULE-IDENTITY	powerEthernetMIB MODULE-IDENTITY

	LAST-UPDATED "200210190000Z" -- October 19, 2002
		LAST-UPDATED "200212020000Z" -- December 02, 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


	skipping to change at page 10, line 14	skipping to change at page 11, line 21
	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 }


		REVISION "200212020000Z" -- December 02, 2002
		DESCRIPTION "Initial version, published as RFC yyyy."
		-- RFC Ed.: replace yyyy with actual RFC number & remove this notice

		::= { mib-2 XXX }
		-- RFC Ed.: replace XXX with IANA-assigned number & remove this notice

		pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 0 }
	pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 }	pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 }

	pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 2 }	pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 2 }
	pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 3 }

	-- PSE Objects	-- PSE Objects

	pethPsePortTable OBJECT-TYPE	pethPsePortTable OBJECT-TYPE
	SYNTAX SEQUENCE OF PethPsePortEntry	SYNTAX SEQUENCE OF PethPsePortEntry
	MAX-ACCESS not-accessible	MAX-ACCESS not-accessible
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"A table of objects that display and control the power	"A table of objects that display and control the power
	characteristics power Ethernet ports on a Power Source	characteristics power Ethernet ports on a Power Source

	skipping to change at page 10, line 45	skipping to change at page 12, line 9
	MAX-ACCESS not-accessible	MAX-ACCESS not-accessible
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"A set of objects that display and control the power	"A set of objects that display and control the power
	characteristics of a power Ethernet PSE port."	characteristics of a power Ethernet PSE port."
	INDEX { pethPsePortGroupIndex , pethPsePortIndex }	INDEX { pethPsePortGroupIndex , pethPsePortIndex }
	::= { pethPsePortTable 1 }	::= { pethPsePortTable 1 }

	PethPsePortEntry ::= SEQUENCE {	PethPsePortEntry ::= SEQUENCE {
	pethPsePortGroupIndex	pethPsePortGroupIndex

	INTEGER,	Integer32,
	pethPsePortIndex	pethPsePortIndex

	INTEGER,	Integer32,
	pethPsePortAdminEnable	pethPsePortAdminEnable
	INTEGER,	INTEGER,
	pethPsePortPowerPairsControlAbility	pethPsePortPowerPairsControlAbility
	TruthValue,	TruthValue,
	pethPsePortPowerPairs	pethPsePortPowerPairs
	INTEGER,	INTEGER,
	pethPsePortPowerDetectionControl	pethPsePortPowerDetectionControl
	INTEGER,	INTEGER,
	pethPsePortDetectionStatus	pethPsePortDetectionStatus
	INTEGER,	INTEGER,

	skipping to change at page 11, line 26	skipping to change at page 12, line 37
	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 Integer32 (1..2147483647)
	MAX-ACCESS not-accessible	MAX-ACCESS not-accessible
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"This variable uniquely identifies the group	"This variable uniquely identifies the group
	containing the port to which a power Ethernet PSE is connected.	containing the port to which a power Ethernet PSE is 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	pethPseMidSpanGroupCapacity is the number of Mid-Span PSE
	groups that can be contained within the 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 Integer32 (1..2147483647)
	MAX-ACCESS not-accessible	MAX-ACCESS not-accessible
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"This variable uniquely identifies the power Ethernet PSE	"This variable uniquely identifies the power Ethernet PSE
	port within group pethPseGroupIndex to which the	port within group 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 {

	skipping to change at page 12, line 39	skipping to change at page 13, line 50
	SYNTAX INTEGER {	SYNTAX INTEGER {
	signal(1),	signal(1),
	spare(2)	spare(2)
	}	}
	MAX-ACCESS read-write	MAX-ACCESS read-write
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"Describes or controls the pairs in use. If the value of	"Describes or controls the pairs in use. If the value of
	pethPsePortPowerPairsControl is true, this object is	pethPsePortPowerPairsControl is true, this object is
	writable.	writable.

	A value of signal(1) menas that the signal pairs	A value of signal(1) means that the signal pairs
	only are in use.	only are in use.
	A value of spare(2) means that the spare pairs	A value of spare(2) means that the spare pairs
	only are in use."	only are in use."
	::= { pethPsePortEntry 5 }	::= { pethPsePortEntry 5 }

	pethPsePortPowerDetectionControl OBJECT-TYPE	pethPsePortPowerDetectionControl OBJECT-TYPE
	SYNTAX INTEGER {	SYNTAX INTEGER {
	auto(1),	auto(1),
	test(2)	test(2)
	}	}

	skipping to change at page 14, line 32	skipping to change at page 15, line 44
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"The value ok(1) indicates the Power Maintenance	"The value ok(1) indicates the Power Maintenance
	Signature is present and the overcurrent condition has not been	Signature is present and the overcurrent condition has not been
	detected.	detected.
	The value overCurrent (2) indicates an overcurrent condition	The value overCurrent (2) indicates an overcurrent condition
	has been detected.	has been detected.
	The value mPSAbsent(3) indicates that the Power Maintenance	The value mPSAbsent(3) indicates that the Power Maintenance
	Signature is absent."	Signature is absent."


	REFERENCE "[IEEE Draft P802.3af/D3.3, October, 2002, 30.9.1.1.8	REFERENCE "[IEEE Draft P802.3af/D4.0, November, 2002, 30.9.1.1.8
	aPSEPowerMaintenanceStatus]"	aPSEPowerMaintenanceStatus]"
	::= { pethPsePortEntry 10 }	::= { pethPsePortEntry 10 }

	pethPsePortMPSAbsentCounter OBJECT-TYPE	pethPsePortMPSAbsentCounter OBJECT-TYPE
	SYNTAX Counter32	SYNTAX Counter32
	MAX-ACCESS read-only	MAX-ACCESS read-only
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"Counts the number of times that the	"Counts the number of times that the
	pethPsePortPowerMaintenanceStatus attribute changes from any	pethPsePortPowerMaintenanceStatus attribute changes from any
	value to the value mPSAbsent(3)."	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/D4.0, November, 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 value to the value overCurrent(2)."	attribute changes from any value to the value overCurrent(2)."

	REFERENCE "[IEEE Draft P802.3af/D3.3, October, 2002, object 30.9.1.1.10	REFERENCE "[IEEE Draft P802.3af/D4.0, November, 2002, object 30.9.1.1.1
	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)
	}	}

	skipping to change at page 15, line 48	skipping to change at page 17, line 13
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"Classification is a way to tag different terminals on the	"Classification is a way to tag different terminals on the
	Power over LAN network according to their power consumption.	Power over LAN network according to their power consumption.
	Devices such as IP telephones, WLAN access points and others,	Devices such as IP telephones, WLAN access points and others,
	will be classified according to their power requirements.	will be classified according to their power requirements.

	The value is only valid while a valid PD is being detected as	The value is only valid while a valid PD is being detected as
	indicated by the attribute pethPsePortDetectionStatus reporting	indicated by the attribute pethPsePortDetectionStatus reporting
	the value or deliveringPower(4)."	the value or deliveringPower(4)."

	REFERENCE "[IEEE Draft P802.3af/D3.3, October , 2002,	REFERENCE "[IEEE Draft P802.3af/D4.0, November, 2002,
	object 30.9.1.1.7 aPSEPowerClassification]"	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 16, line 29	skipping to change at page 17, line 42
	MAX-ACCESS not-accessible	MAX-ACCESS not-accessible
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"A set of objects that display and control the power	"A set of objects that display and control the power
	characteristics of a Powered Device port."	characteristics of a Powered Device port."
	INDEX { pethPdPortIndex }	INDEX { pethPdPortIndex }
	::= { pethPdPortTable 1 }	::= { pethPdPortTable 1 }

	PethPdPortEntry ::= SEQUENCE {	PethPdPortEntry ::= SEQUENCE {
	pethPdPortIndex	pethPdPortIndex

	INTEGER,	InterfaceIndex,
	pethPdPortAdminEnable	pethPdPortAdminEnable
	INTEGER	INTEGER
	}	}

	pethPdPortIndex OBJECT-TYPE	pethPdPortIndex OBJECT-TYPE

	SYNTAX INTEGER (0..65535)	SYNTAX InterfaceIndex
	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

	skipping to change at page 17, line 45	skipping to change at page 19, line 12
	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 }
	::= { pethMainPseTable 1 }	::= { pethMainPseTable 1 }

	PethMainPseEntry ::= SEQUENCE {	PethMainPseEntry ::= SEQUENCE {
	pethMainPseGroupIndex	pethMainPseGroupIndex

	INTEGER,
	pethMainPsePower
	Integer32,	Integer32,

		pethMainPsePower
		Gauge32 ,
	pethMainPseOperStatus	pethMainPseOperStatus
	INTEGER,	INTEGER,
	pethMainPseConsumptionPower	pethMainPseConsumptionPower
	Gauge32,	Gauge32,

	pethMainPseBackupPresent
	INTEGER,
	pethMainPseBackupActivated
	TruthValue,
	pethMainPseUsageThreshold	pethMainPseUsageThreshold

	INTEGER,	Integer32
	pethMainPseMaximumDcPower
	INTEGER
	}	}
	pethMainPseGroupIndex OBJECT-TYPE	pethMainPseGroupIndex OBJECT-TYPE

	SYNTAX INTEGER (0..65535)	SYNTAX Integer32 (1..2147483647)
	MAX-ACCESS not-accessible	MAX-ACCESS not-accessible
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"This variable uniquely identifies the group to which	"This variable uniquely identifies the group to which
	power Ethernet PSE is connected.Group means (box in the stack,	power Ethernet PSE is connected.Group means (box in 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 non-modular
	devices "	devices "
	::= { pethMainPseEntry 1 }	::= { pethMainPseEntry 1 }

	pethMainPsePower OBJECT-TYPE	pethMainPsePower OBJECT-TYPE

	SYNTAX Integer32 (1..65535)	SYNTAX Gauge32 (1..65535)
	UNITS "Watts"	UNITS "Watts"
	MAX-ACCESS read-only	MAX-ACCESS read-only
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"The nominal power of the PSE expressed in Watts."	"The nominal power of the PSE expressed in Watts."
	::= { pethMainPseEntry 2 }	::= { pethMainPseEntry 2 }

	pethMainPseOperStatus OBJECT-TYPE	pethMainPseOperStatus OBJECT-TYPE
	SYNTAX INTEGER {	SYNTAX INTEGER {
	on(1),	on(1),

	skipping to change at page 19, line 8	skipping to change at page 20, line 16

	pethMainPseConsumptionPower OBJECT-TYPE	pethMainPseConsumptionPower OBJECT-TYPE
	SYNTAX Gauge32	SYNTAX Gauge32
	UNITS "Watts"	UNITS "Watts"
	MAX-ACCESS read-only	MAX-ACCESS read-only
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"Measured usage power expressed in Watts."	"Measured usage power expressed in Watts."
	::= { pethMainPseEntry 4 }	::= { pethMainPseEntry 4 }


	pethMainPseBackupPresent OBJECT-TYPE
	SYNTAX INTEGER {
	present(1),
	notPresent(2),
	faulty(3)
	}
	MAX-ACCESS read-only
	STATUS current
	DESCRIPTION
	"reflects the presence of a backup PSE ."
	::= { pethMainPseEntry 5 }

	pethMainPseBackupActivated OBJECT-TYPE
	SYNTAX TruthValue
	MAX-ACCESS read-only
	STATUS current
	DESCRIPTION
	"- reflects the activation status of the backup PSE .
	The value true Backup is activated."
	::= { pethMainPseEntry 6 }

	pethMainPseUsageThreshold OBJECT-TYPE	pethMainPseUsageThreshold OBJECT-TYPE

	SYNTAX INTEGER (1..99)	SYNTAX Integer32 (1..99)
	UNITS "%"	UNITS "%"
	MAX-ACCESS read-write	MAX-ACCESS read-write
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"The usage threshold expressed in percents 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
	SYNTAX INTEGER
	UNITS "Watts"
	MAX-ACCESS read-write
	STATUS current
	DESCRIPTION
	"Describes the maximum available power in
	Watt to be supplied by the DC backup source to this
	device."
	::= { pethMainPseEntry 8 }
	-- Notification Control Objects	-- Notification Control Objects

	pethNotificationControl OBJECT IDENTIFIER ::= { pethObjects 4 }	pethNotificationControl OBJECT IDENTIFIER ::= { pethObjects 4 }

	pethNotificationControlTable OBJECT-TYPE	pethNotificationControlTable OBJECT-TYPE
	SYNTAX SEQUENCE OF PethNotificationControlEntry	SYNTAX SEQUENCE OF PethNotificationControlEntry
	MAX-ACCESS not-accessible	MAX-ACCESS not-accessible
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"A table of objects that display and control the Notification	"A table of objects that display and control the Notification

	skipping to change at page 20, line 25	skipping to change at page 21, line 4
	::= { pethNotificationControl 1 }	::= { pethNotificationControl 1 }

	pethNotificationControlEntry OBJECT-TYPE	pethNotificationControlEntry OBJECT-TYPE
	SYNTAX PethNotificationControlEntry	SYNTAX PethNotificationControlEntry
	MAX-ACCESS not-accessible	MAX-ACCESS not-accessible
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"A set of objects that control the Notification events."	"A set of objects that control the Notification events."
	INDEX { pethNotificationControlGroupIndex }	INDEX { pethNotificationControlGroupIndex }
	::= { pethNotificationControlTable 1 }	::= { pethNotificationControlTable 1 }


	PethNotificationControlEntry ::= SEQUENCE {	PethNotificationControlEntry ::= SEQUENCE {
	pethNotificationControlGroupIndex	pethNotificationControlGroupIndex

	INTEGER,	Integer32,
	pethNotificationControlEnable	pethNotificationControlEnable
	INTEGER	INTEGER
	}	}
	pethNotificationControlGroupIndex OBJECT-TYPE	pethNotificationControlGroupIndex OBJECT-TYPE

	SYNTAX INTEGER (1..65535)	SYNTAX Integer32 (1..2147483647)
	MAX-ACCESS not-accessible	MAX-ACCESS not-accessible
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"This variable uniquely identifies the group. Group means	"This variable uniquely identifies the group. Group means
	box in the stack, module in a rack and it is RECOMENDED	box in the stack, module in a rack and it is RECOMENDED
	that the value 1 be used for non-modular devices "	that the value 1 be used for non-modular devices "
	::= { pethNotificationControlEntry 1 }	::= { pethNotificationControlEntry 1 }

	pethNotificationControlEnable OBJECT-TYPE	pethNotificationControlEnable OBJECT-TYPE
	SYNTAX INTEGER	SYNTAX INTEGER

	skipping to change at page 21, line 29	skipping to change at page 22, line 10
	::= { pethNotifications 1 }	::= { pethNotifications 1 }

	pethPsePortPowerMaintenanceStatusNotification NOTIFICATION-TYPE	pethPsePortPowerMaintenanceStatusNotification NOTIFICATION-TYPE
	OBJECTS { pethPsePortPowerMaintenanceStatus }	OBJECTS { pethPsePortPowerMaintenanceStatus }
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	" This Notification indicates a Port Change Status and it	" This Notification indicates a Port Change Status and it
	SHOULD be sent on every status change."	SHOULD be sent on every status change."
	::= { pethNotifications 2 }	::= { pethNotifications 2 }


	pethMainPseBackUpActivatedNotification NOTIFICATION-TYPE
	OBJECTS { pethMainPseBackupActivated }
	STATUS current
	DESCRIPTION
	" This Notification indicate BackUp is Activated or BackUp is
	released."
	::= { pethNotifications 3 }

	pethMainPowerUsageOnNotification NOTIFICATION-TYPE	pethMainPowerUsageOnNotification NOTIFICATION-TYPE
	OBJECTS { pethMainPseConsumptionPower }	OBJECTS { pethMainPseConsumptionPower }
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	" This Notification indicate PSE Threshold usage indication is	" This Notification indicate PSE Threshold usage indication is
	on, the usage power is above the threshold."	on, the usage power is above the threshold."
	::= { pethNotifications 4 }	::= { pethNotifications 4 }

	pethMainPowerUsageOffNotification NOTIFICATION-TYPE	pethMainPowerUsageOffNotification NOTIFICATION-TYPE
	OBJECTS { pethMainPseConsumptionPower }	OBJECTS { pethMainPseConsumptionPower }

	skipping to change at page 23, line 27	skipping to change at page 23, line 45
	pethPsePortDetectionStatus,	pethPsePortDetectionStatus,
	pethPsePortPowerPriority,	pethPsePortPowerPriority,
	pethPsePortPowerMaintenanceStatus ,	pethPsePortPowerMaintenanceStatus ,
	pethPsePortMPSAbsentCounter,	pethPsePortMPSAbsentCounter,
	pethPsePortOverCurrentCounter,	pethPsePortOverCurrentCounter,
	pethPsePortType,	pethPsePortType,
	pethPsePortPowerClassifications	pethPsePortPowerClassifications
	}	}
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION

	"PSE Port Objects."	"The pethPsePortGroup is mandatory for systems which
		implement PSE ports."
	::= { pethGroups 1 }	::= { pethGroups 1 }

	pethPdPortGroup OBJECT-GROUP	pethPdPortGroup OBJECT-GROUP
	OBJECTS {	OBJECTS {
	pethPdPortAdminEnable	pethPdPortAdminEnable
	}	}
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION

	"PD Port Objects."	"The pethPdPortGroup is mandatory for systems which
		implement PD Ports."
	::= { pethGroups 2 }	::= { pethGroups 2 }

	pethMainPseGroup OBJECT-GROUP	pethMainPseGroup OBJECT-GROUP
	OBJECTS {	OBJECTS {
	pethMainPsePower,	pethMainPsePower,
	pethMainPseOperStatus,	pethMainPseOperStatus,
	pethMainPseConsumptionPower,	pethMainPseConsumptionPower,

	pethMainPseBackupPresent,	pethMainPseUsageThreshold
	pethMainPseBackupActivated,
	pethMainPseUsageThreshold,
	pethMainPseMaximumDcPower
	}	}
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"Main PSE Objects. "	"Main PSE Objects. "
	::= { pethGroups 3 }	::= { pethGroups 3 }

	pethNotificationControlGroup OBJECT-GROUP	pethNotificationControlGroup OBJECT-GROUP
	OBJECTS {	OBJECTS {
	pethNotificationControlEnable	pethNotificationControlEnable
	}	}

	skipping to change at page 24, line 23	skipping to change at page 24, line 41
	::= { pethGroups 4 }	::= { pethGroups 4 }

	pethPsePortNotificationGroup NOTIFICATION-GROUP	pethPsePortNotificationGroup NOTIFICATION-GROUP
	NOTIFICATIONS { pethPsePortOnOffNotification,	NOTIFICATIONS { pethPsePortOnOffNotification,
	pethPsePortPowerMaintenanceStatusNotification}	pethPsePortPowerMaintenanceStatusNotification}
	STATUS current	STATUS current
	DESCRIPTION "Pse Notification indications"	DESCRIPTION "Pse Notification indications"
	::= { pethCompliances 4 }	::= { pethCompliances 4 }

	pethMainPowerNotificationGroup NOTIFICATION-GROUP	pethMainPowerNotificationGroup NOTIFICATION-GROUP

	NOTIFICATIONS { pethMainPseBackUpActivatedNotification,	NOTIFICATIONS { pethMainPowerUsageOnNotification,
	pethMainPowerUsageOnNotification,
	pethMainPowerUsageOffNotification}	pethMainPowerUsageOffNotification}
	STATUS current	STATUS current
	DESCRIPTION "Pse Notification indications"	DESCRIPTION "Pse Notification indications"
	::= { pethCompliances 5 }	::= { pethCompliances 5 }

	END	END


	8. References	8. Normative 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
	of Management Information for TCP/IP-based Internets", STD
	16, RFC 1155, May 1990.

	[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
	16, RFC 1212, March 1991.

	[RFC1215] M. Rose, "A Convention for Defining Traps for use with the
	SNMP", RFC 1215, March 1991.

	[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,	[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
	Rose, M., and S. Waldbusser, "Structure of Management	Rose, M., and S. Waldbusser, "Structure of Management
	Information Version 2 (SMIv2)", STD 58, RFC 2578, April	Information Version 2 (SMIv2)", STD 58, RFC 2578, April
	1999.	1999.

	[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,	[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
	Rose, M., and S. Waldbusser, "Textual Conventions for	Rose, M., and S. Waldbusser, "Textual Conventions for
	SMIv2", STD 58, RFC 2579, April 1999.	SMIv2", STD 58, RFC 2579, April 1999.

	[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,	[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
	Rose, M., and S. Waldbusser, "Conformance Statements for	Rose, M., and S. Waldbusser, "Conformance Statements for
	SMIv2", STD 58, RFC 2580, April 1999.	SMIv2", STD 58, RFC 2580, April 1999.


	[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
	Network Management Protocol", STD 15, RFC 1157, May 1990.

	[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
	"Introduction to Community-based SNMPv2", RFC 1901, January
	1996.

	[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
	"Transport Mappings for Version 2 of the Simple Network
	Management Protocol (SNMPv2)", RFC 1906, January 1996.

	[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message	[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
	Processing and Dispatching for the Simple Network Management	Processing and Dispatching for the Simple Network Management
	Protocol (SNMP)", RFC 2572, April 1999.	Protocol (SNMP)", RFC 2572, April 1999.

	[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model	[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model
	(USM) for version 3 of the Simple Network Management	(USM) for version 3 of the Simple Network Management
	Protocol (SNMPv3)", RFC 2574, April 1999.	Protocol (SNMPv3)", RFC 2574, April 1999.


	[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
	"Protocol Operations for Version 2 of the Simple Network
	Management Protocol (SNMPv2)", RFC 1905, January 1996.

	[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications",	[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications",
	RFC 2573, April 1999.	RFC 2573, April 1999.

	[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based	[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
	Access Control Model (VACM) for the Simple Network	Access Control Model (VACM) for the Simple Network
	Management Protocol (SNMP)", RFC 2575, April 1999.	Management Protocol (SNMP)", RFC 2575, April 1999.

	[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,	[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
	"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.3,	Power via Media Dependent Interface (MDI)", Draft D4.0,
	October 2002.	December 2002.

		9. Informative References

		[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification
		of Management Information for TCP/IP-based Internets", STD
		16, RFC 1155, May 1990.

		[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
		16, RFC 1212, March 1991.

		[RFC1215] M. Rose, "A Convention for Defining Traps for use with the
		SNMP", RFC 1215, March 1991.

		[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
		Network Management Protocol", STD 15, RFC 1157, May 1990.

		[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
		"Introduction to Community-based SNMPv2", RFC 1901, January
		1996.

		[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
		"Transport Mappings for Version 2 of the Simple Network
		Management Protocol (SNMPv2)", RFC 1906, January 1996.

		[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
		"Protocol Operations for Version 2 of the Simple Network
		Management Protocol (SNMPv2)", RFC 1905, January 1996.

	[PWR-MIB] Romascanu, D., " Power Ethernet (DTE Power via MDI) MIB",	[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	10.Intellectual Property

	The IETF takes no position regarding the validity or scope of any	The IETF takes no position regarding the validity or scope of any
	intellectual property or other rights that might be claimed to	intellectual property or other rights that might be claimed to
	pertain to the implementation or use of the technology described in	pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights	this document or the extent to which any license under such rights
	might or might not be available; neither does it represent that it	might or might not be available; neither does it represent that it
	has made any effort to identify any such rights. Information on the	has made any effort to identify any such rights. Information on the
	IETF's procedures with respect to rights in standards-track and	IETF's procedures with respect to rights in standards-track and
	standards-related documentation can be found in BCP-11. Copies of	standards-related documentation can be found in BCP-11. Copies of
	claims of rights made available for publication and any assurances of	claims of rights made available for publication and any assurances of

	skipping to change at page 26, line 36	skipping to change at page 27, line 8
	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	11. Security Considerations

	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:

	skipping to change at page 27, line 26	skipping to change at page 27, line 46
	features as provided by the SNMPv3 framework. Specifically, the	features as provided by the SNMPv3 framework. Specifically, the
	use of the User-based Security Model [RFC2274] and the	use of the User-based Security Model [RFC2274] and the
	View-based Access Control Model [RFC2275] is RECOMMENDED.	View-based Access Control Model [RFC2275] is RECOMMENDED.

	It is then a customer/user responsibility to ensure that the SNMP	It is then a customer/user responsibility to ensure that the SNMP
	entity giving access to an instance of this MIB, is properly	entity giving access to an instance of this MIB, is properly
	configured to give access to the objects only to those	configured to give access to the objects only to those
	principals (users) that have legitimate rights to indeed GET or	principals (users) that have legitimate rights to indeed GET or
	SET (change/create/delete) them.	SET (change/create/delete) them.


	11. Authors Addresses	12. Authors Addresses

	Avi Berger	Avi Berger
	PowerDsine Inc.	PowerDsine Inc.


	1, Hanagar St., P.O. Box 7220	1, Hanagar St., P.O. Box 7220
	Hod Hasharon 45421,	Hod Hasharon 45421,
	Israel	Israel
	Tel: +972-9-7755100 Ext 307	Tel: +972-9-7755100 Ext 307
	Fax: +972-9-7755120	Fax: +972-9-7755120
	E-mail: avib@PowerDsine.com	E-mail: avib@PowerDsine.com

	Dan Romascanu	Dan Romascanu
	Avaya Inc.	Avaya Inc.
	Atidim Technology Park, Bldg. #3	Atidim Technology Park, Bldg. #3

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