idnits 2.17.1 draft-ietf-hubmib-power-ethernet-mib-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 20 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 21 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 18 instances of too long lines in the document, the longest one being 4 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The "Author's Address" (or "Authors' Addresses") section title is misspelled. == Line 532 has weird spacing: '...ck) and the v...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (22 June 2003) is 7613 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2026' is defined on line 762, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 789, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2665 (Obsoleted by RFC 3635) -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE-802.3af' Summary: 8 errors (**), 0 flaws (~~), 9 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Avi Berger 3 PowerDsine Inc. 4 Dan Romascanu 5 Avaya 6 22 June 2003 8 Power Ethernet MIB 10 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026. Internet-Drafts are working 16 documents of the Internet Engineering Task Force (IETF), its areas, 17 and its working groups. Note that other groups may also distribute 18 working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet- Drafts as reference 23 material or to cite them other than as "work in progress." 25 To view the list Internet-Draft Shadow Directories, see 26 http://www.ietf.org/shadow.html. 28 Copyright Notice 30 Copyright (C) The Internet Society (2003). All Rights Reserved. 32 Abstract 34 This memo defines a portion of the Management Information Base (MIB) 35 for use with network management protocols in the Internet community. 36 The document proposes an extension to the Ethernet-like Interfaces 37 MIB with a set of objects for managing a Power Source Equipment 38 (PSE). 40 Distribution of this memo is unlimited. 42 Table of Contents 44 Status of this Memo 1 45 Abstract 1 46 1 Introduction 2 47 2 The Internet-Standard Management Framework 2 48 3 Overview 2 49 4 MIB Structure 3 50 5 Definitions 3 51 6 Acknowledgements 17 52 7 Normative References 17 53 8 Informative References 18 54 9 Intellectual Property 18 55 10 Security Considerations 18 56 11 Authors Addresses 20 57 A Full Copyright Statement 20 59 1. Introduction 61 This memo defines a portion of the Management Information Base (MIB) 62 for use with network management protocols in the Internet community. 63 In particular, it defines a set of MIB objects to manage a Power 64 Ethernet [IEEE-802.3af] Source Equipment (PSE). 66 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 67 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 68 document are to be interpreted as described in [RFC2119]. 70 2. The Internet-Standard Management Framework 72 For a detailed overview of the documents that describe the current 73 Internet-Standard Management Framework, please refer to section 7 of 74 RFC 3410 [RFC3410]. 76 Managed objects are accessed via a virtual information store, termed 77 the Management Information Base or MIB. MIB objects are generally 78 accessed through the Simple Network Management Protocol (SNMP). 79 Objects in the MIB are defined using the mechanisms defined in the 80 Structure of Management Information (SMI). This memo specifies a MIB 81 module that is compliant to the SMIv2, which is described in STD 58, 82 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 83 [RFC2580]. 85 3. Overview 87 The emergence of IP telephony as an application that allows for voice 88 applications to be run over the same infrastructure as data 89 applications led to the emergence of Ethernet IP phones, with similar 90 functions and characteristics as the traditional phones. Powering a 91 phone is one of these functions that are being taken as granted. The 92 IEEE 802.3 Working Group initiated a standard work on this subject, 93 currently known as the IEEE 802.3af work [IEEE-802.3af]. 95 The IEEE 802.3af WG did not define a full management interface, but 96 only the hardware registers that will allow for a management 97 interfaces to be built for a powered Ethernet device. The MIB module 98 defined in this document extends the Ethernet-like Interfaces MIB 99 [RFC2665] with the management objects required for the management of 100 the powered Ethernet devices and ports. 102 The following abbreviations are defined in [IEEE-802.3af] and will be 103 used with the same significance in this document: 105 PSE - Power Sourcing Equipment; 107 PD - Powered Device 109 4. MIB Structure 111 This MIB objects are included in three MIB groups. 113 The pethPsePortTable defines the objects used for the configuration 114 and describing the status of ports on a PSE device. Examples of PSE 115 devices are Ethernet switches that support power Ethernet and mid- 116 span boxes. 118 The pethMainPseObjects MIB group defines the management objects for a 119 managed main power source in a PSE device. Ethernet switches are one 120 example of boxes that would support these objects. 122 The pethNotificationControlTable includes objects that control the 123 transmission of notifications by the agent to a management 124 application. 126 5. Definitions 128 POWER-ETHERNET-MIB DEFINITIONS ::= BEGIN 130 IMPORTS 131 MODULE-IDENTITY, mib-2, OBJECT-TYPE, Integer32, 132 Gauge32, Counter32, NOTIFICATION-TYPE 133 FROM SNMPv2-SMI 134 TruthValue 135 FROM SNMPv2-TC 136 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 137 FROM SNMPv2-CONF 139 SnmpAdminString 140 FROM SNMP-FRAMEWORK-MIB; 142 powerEthernetMIB MODULE-IDENTITY 144 LAST-UPDATED "200306220000Z" -- June 22, 2003 145 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB 146 Working Group" 147 CONTACT-INFO 148 " 149 WG Charter: 150 http://www.ietf.org/html.charters/hubmib-charter.html 152 Mailing lists: 153 General Discussion: hubmib@ietf.org 154 To Subscribe: hubmib-requests@ietf.org 155 In Body: subscribe your_email_address 157 Chair: Dan Romascanu 158 Avaya 159 Tel: +972-3-645-8414 160 Email: dromasca@avaya.com 162 Editor: Avi Berger 163 PowerDsine Inc. 164 Tel: 972-9-7755100 Ext 307 165 Fax: 972-9-7755120 166 E-mail: avib@PowerDsine.com 167 " 169 DESCRIPTION 170 "The MIB module for managing Power Source Equipment 171 (PSE) working according to the IEEE 802.af Powered 172 Ethernet (DTE Power via MDI) standard. 174 The following terms are used throughout this 175 MIB module. For complete formal definitions, 176 the IEEE 802.3 standards should be consulted 177 wherever possible: 179 Group - A recommended, but optional, entity 180 defined by the IEEE 802.3 management standard, 181 in order to support a modular numbering scheme. 182 The classical example allows an implementor to 183 represent field-replaceable units as groups of 184 ports, with the port numbering matching the 185 modular hardware implementation. 187 Port - This entity identifies the port within the group 188 for which this entry contains information. The numbering 189 scheme for ports is implementation specific. 191 Copyright (c) The Internet Society (2003). This version of 192 this MIB module is part of RFC yyyy; See the RFC itself 193 for full legal notices. 194 -- RFC Ed.: replace yyyy with the actual RFC number & remove this notice. 195 " 197 REVISION "200306220000Z" -- June 22, 2003 198 DESCRIPTION "Initial version, published as RFC yyyy." 199 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 201 ::= { mib-2 XXX } 202 -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice 204 pethNotifications OBJECT IDENTIFIER ::= { powerEthernetMIB 0 } 205 pethObjects OBJECT IDENTIFIER ::= { powerEthernetMIB 1 } 206 pethConformance OBJECT IDENTIFIER ::= { powerEthernetMIB 2 } 208 -- PSE Objects 210 pethPsePortTable OBJECT-TYPE 211 SYNTAX SEQUENCE OF PethPsePortEntry 212 MAX-ACCESS not-accessible 213 STATUS current 214 DESCRIPTION 215 "A table of objects that display and control the power 216 characteristics power Ethernet ports on a Power Source 217 Entity (PSE) device. This group will be implemented in 218 managed power Ethernet switches and mid-span devices. 219 Values of all read-write objects in this table are 220 persistent at restart/reboot." 221 ::= { pethObjects 1 } 223 pethPsePortEntry OBJECT-TYPE 224 SYNTAX PethPsePortEntry 225 MAX-ACCESS not-accessible 226 STATUS current 227 DESCRIPTION 228 "A set of objects that display and control the power 229 characteristics of a power Ethernet PSE port." 230 INDEX { pethPsePortGroupIndex , pethPsePortIndex } 231 ::= { pethPsePortTable 1 } 233 PethPsePortEntry ::= SEQUENCE { 234 pethPsePortGroupIndex 235 Integer32, 236 pethPsePortIndex 237 Integer32, 238 pethPsePortAdminEnable 239 TruthValue, 240 pethPsePortPowerPairsControlAbility 241 TruthValue, 242 pethPsePortPowerPairs 243 INTEGER, 244 pethPsePortDetectionStatus 245 INTEGER, 246 pethPsePortPowerPriority 247 INTEGER, 248 pethPsePortMPSAbsentCounter 249 Counter32, 250 pethPsePortInvalidSignatureCounter 251 Counter32, 252 pethPsePortPowerDeniedCounter 253 Counter32, 254 pethPsePortOverLoadCounter 255 Counter32, 256 pethPsePortShortCounter 257 Counter32, 258 pethPsePortType 259 SnmpAdminString, 260 pethPsePortPowerClassifications 261 INTEGER 262 } 264 pethPsePortGroupIndex OBJECT-TYPE 265 SYNTAX Integer32 (1..2147483647) 266 MAX-ACCESS not-accessible 267 STATUS current 268 DESCRIPTION 269 "This variable uniquely identifies the group 270 containing the port to which a power Ethernet PSE is 271 connected. Group means box in the stack, module in a 272 rack and the value 1 MUST be used for non-modular devices. 273 Furthermore, the same value MUST be used in this variable, 274 pethMainPseGroupIndex, and pethNotificationControlGroupIndex 275 to refer to a given box in a stack or module in the rack." 276 ::= { pethPsePortEntry 1 } 278 pethPsePortIndex OBJECT-TYPE 279 SYNTAX Integer32 (1..2147483647) 280 MAX-ACCESS not-accessible 281 STATUS current 282 DESCRIPTION 283 "This variable uniquely identifies the power Ethernet PSE 284 port within group pethPsePortGroupIndex to which the 285 power Ethernet PSE entry is connected." 286 ::= { pethPsePortEntry 2 } 288 pethPsePortAdminEnable OBJECT-TYPE 289 SYNTAX TruthValue 290 MAX-ACCESS read-write 291 STATUS current 292 DESCRIPTION 293 "true (1) An interface which can provide the PSE functions. 294 false(2) The interface will act as it would if it had no PSE 295 function." 296 REFERENCE 297 "IEEE Std 802.3af Section 30.9.1.1.2 aPSEAdminState" 298 ::= { pethPsePortEntry 3 } 300 pethPsePortPowerPairsControlAbility OBJECT-TYPE 301 SYNTAX TruthValue 302 MAX-ACCESS read-only 303 STATUS current 304 DESCRIPTION 305 "Describes the capability of controlling the power pairs 306 functionality to switch pins for sourcing power. 307 The value true indicate that the device has the capability 308 to control the power pairs. When false the PSE Pinout 309 Alternative used cannot be controlled through the 310 PethPsePortAdminEnabe attribute." 311 REFERENCE 312 "IEEE Std 802.3af Section 30.9.1.1.3 313 aPSEPowerPairsControlAbility" 314 ::= { pethPsePortEntry 4 } 316 pethPsePortPowerPairs OBJECT-TYPE 317 SYNTAX INTEGER { 318 signal(1), 319 spare(2) 320 } 321 MAX-ACCESS read-write 322 STATUS current 323 DESCRIPTION 324 "Describes or controls the pairs in use. If the value of 325 pethPsePortPowerPairsControl is true, this object is 326 writable. 327 A value of signal(1) menas that the signal pairs 328 only are in use. 329 A value of spare(2) means that the spare pairs 330 only are in use." 331 REFERENCE 332 "IEEE Std 802.3af Section 30.9.1.1.4 aPSEPowerPairs" 333 ::= { pethPsePortEntry 5 } 335 pethPsePortDetectionStatus OBJECT-TYPE 336 SYNTAX INTEGER { 337 disabled(1), 338 searching(2), 339 deliveringPower(3), 340 fault(4), 341 test(5), 342 otherFault(6) 343 } 344 MAX-ACCESS read-only 345 STATUS current 346 DESCRIPTION 347 "Describes the operational status of the port PD detection. 348 A value of disabled(1)- indicates that the PSE State diagram 349 is in the state DISABLED. 350 A value of deliveringPower(3) - indicates that the PSE State 351 diagram is in the state POWER_ON for a duration greater than 352 tlim max (see IEEE Std 802.3af Table 33-5 tlim). 353 A value of fault(4) - indicates that the PSE State diagram is 354 in the state TEST_ERROR. 355 A value of test(5) - indicates that the PSE State diagram is 356 in the state TEST_MODE. 357 A value of otherFault(6) - indicates that the PSE State 358 diagram is in the state IDLE due to the variable 359 error_conditions. 360 A value of searching(2)- indicates the PSE State diagram is 361 in a state other than those listed above." 362 REFERENCE 363 "IEEE Std 802.3af Section 30.9.1.1.5 364 aPSEPowerDetectionStatus" 365 ::= { pethPsePortEntry 6 } 367 pethPsePortPowerPriority OBJECT-TYPE 368 SYNTAX INTEGER { 369 critical(1), 370 high(2), 371 low(3) 372 } 373 MAX-ACCESS read-write 374 STATUS current 375 DESCRIPTION 376 "This object controls the priority of the port from the point 377 of view of a power management algorithm. The priority that 378 is set by this variable could be used by a control mechanism 379 that prevents over current situations by disconnecting first 380 ports with lower power priority. Ports that connect devices 381 critical to the operation of the network - like the E911 382 telephones ports - should be set to higher priority." 383 ::= { pethPsePortEntry 7 } 385 pethPsePortMPSAbsentCounter OBJECT-TYPE 386 SYNTAX Counter32 387 MAX-ACCESS read-only 388 STATUS current 389 DESCRIPTION 390 "This counter is incremented when the PSE state diagram 391 transitions directly from the state POWER_ON to the 392 state IDLE due to tmpdo_timer_done being asserted." 393 REFERENCE 394 "IEEE Std 802.3af Section 30.9.1.1.11 395 aPSEMPSAbsentCounter" 396 ::= { pethPsePortEntry 8 } 398 pethPsePortType OBJECT-TYPE 399 SYNTAX SnmpAdminString 400 MAX-ACCESS read-write 401 STATUS current 402 DESCRIPTION 403 "A manager will set the value of this variable to indicate 404 the type of powered device that is connected to the port. 405 The default value supplied by the agent if no value has 406 ever been set should be a zero-length octet string." 407 ::= { pethPsePortEntry 9 } 409 pethPsePortPowerClassifications OBJECT-TYPE 410 SYNTAX INTEGER { 411 class0(1), 412 class1(2), 413 class2(3), 414 class3(4), 415 class4(5) 416 } 417 MAX-ACCESS read-only 418 STATUS current 419 DESCRIPTION 420 "Classification is a way to tag different terminals on the 421 Power over LAN network according to their power consumption. 423 Devices such as IP telephones, WLAN access points and others, 424 will be classified according to their power requirements. 426 The meaning of the classification labels is defined in the 427 IEEE specification. 429 This variable is valid only while a PD is being powered, 430 that is, while the attribute pethPsePortDetectionStatus 431 is reporting the enumeration deliveringPower." 432 REFERENCE 433 "IEEE Std 802.3af Section 30.9.1.1.6 434 aPSEPowerClassification" 435 ::= { pethPsePortEntry 10 } 437 pethPsePortInvalidSignatureCounter OBJECT-TYPE 438 SYNTAX Counter32 439 MAX-ACCESS read-only 440 STATUS current 441 DESCRIPTION 442 "This counter is incremented when the PSE state diagram 443 enters the state SIGNATURE_INVALID." 444 REFERENCE 445 "IEEE Std 802.3af Section 30.9.1.1.7 446 aPSEInvalidSignatureCounter" 447 ::= { pethPsePortEntry 11 } 449 pethPsePortPowerDeniedCounter OBJECT-TYPE 450 SYNTAX Counter32 451 MAX-ACCESS read-only 452 STATUS current 453 DESCRIPTION 454 "This counter is incremented when the PSE state diagram 455 enters the state POWER_DENIED." 456 REFERENCE 457 "IEEE Std 802.3af Section 30.9.1.1.8 458 aPSEPowerDeniedCounter" 459 ::= { pethPsePortEntry 12 } 461 pethPsePortOverLoadCounter OBJECT-TYPE 462 SYNTAX Counter32 463 MAX-ACCESS read-only 464 STATUS current 465 DESCRIPTION 466 "This counter is incremented when the PSE state diagram 467 enters the state ERROR_DELAY_OVER." 468 REFERENCE 469 "IEEE Std 802.3af Section 30.9.1.1.9 470 aPSEOverLoadCounter" 472 ::= { pethPsePortEntry 13 } 474 pethPsePortShortCounter OBJECT-TYPE 475 SYNTAX Counter32 476 MAX-ACCESS read-only 477 STATUS current 478 DESCRIPTION 479 "This counter is incremented when the PSE state diagram 480 enters the state ERROR_DELAY_SHORT." 481 REFERENCE 482 "IEEE Std 802.3af Section 30.9.1.1.10 483 aPSEShortCounter" 484 ::= { pethPsePortEntry 14 } 486 -- Main PSE Objects 488 pethMainPseObjects OBJECT IDENTIFIER ::= { pethObjects 3 } 490 pethMainPseTable OBJECT-TYPE 491 SYNTAX SEQUENCE OF PethMainPseEntry 492 MAX-ACCESS not-accessible 493 STATUS current 494 DESCRIPTION 495 "A table of objects that display and control attributes 496 of the main power source in a PSE device. Ethernet 497 switches are one example of boxes that would support 498 these objects. 499 Values of all read-write objects in this table are 500 persistent at restart/reboot." 501 ::= { pethMainPseObjects 1 } 503 pethMainPseEntry OBJECT-TYPE 504 SYNTAX PethMainPseEntry 505 MAX-ACCESS not-accessible 506 STATUS current 507 DESCRIPTION 508 "A set of objects that display and control the Main 509 power of a PSE. " 510 INDEX { pethMainPseGroupIndex } 511 ::= { pethMainPseTable 1 } 513 PethMainPseEntry ::= SEQUENCE { 514 pethMainPseGroupIndex 515 Integer32, 516 pethMainPsePower 517 Gauge32 , 518 pethMainPseOperStatus 519 INTEGER, 520 pethMainPseConsumptionPower 521 Gauge32, 522 pethMainPseUsageThreshold 523 Integer32 524 } 525 pethMainPseGroupIndex OBJECT-TYPE 526 SYNTAX Integer32 (1..2147483647) 527 MAX-ACCESS not-accessible 528 STATUS current 529 DESCRIPTION 530 "This variable uniquely identifies the group to which 531 power Ethernet PSE is connected. Group means (box in 532 the stack, module in a rack) and the value 1 MUST be 533 used for non-modular devices. Furthermore, the same 534 value MUST be used in this variable, pethPsePortGroupIndex, 535 and pethNotificationControlGroupIndex to refer to a 536 given box in a stack or module in a rack." 537 ::= { pethMainPseEntry 1 } 539 pethMainPsePower OBJECT-TYPE 540 SYNTAX Gauge32 (1..65535) 541 UNITS "Watts" 542 MAX-ACCESS read-only 543 STATUS current 544 DESCRIPTION 545 "The nominal power of the PSE expressed in Watts." 546 ::= { pethMainPseEntry 2 } 548 pethMainPseOperStatus OBJECT-TYPE 549 SYNTAX INTEGER { 550 on(1), 551 off(2), 552 faulty(3) 553 } 554 MAX-ACCESS read-only 555 STATUS current 556 DESCRIPTION 557 "The operational status of the main PSE." 558 ::= { pethMainPseEntry 3 } 560 pethMainPseConsumptionPower OBJECT-TYPE 561 SYNTAX Gauge32 562 UNITS "Watts" 563 MAX-ACCESS read-only 564 STATUS current 565 DESCRIPTION 566 "Measured usage power expressed in Watts." 567 ::= { pethMainPseEntry 4 } 569 pethMainPseUsageThreshold OBJECT-TYPE 570 SYNTAX Integer32 (1..99) 571 UNITS "%" 572 MAX-ACCESS read-write 573 STATUS current 574 DESCRIPTION 575 "The usage threshold expressed in percents for 576 comparing the measured power and initiating 577 an alarm if the threshold is exceeded." 578 ::= { pethMainPseEntry 5 } 580 -- Notification Control Objects 582 pethNotificationControl OBJECT IDENTIFIER ::= { pethObjects 4 } 584 pethNotificationControlTable OBJECT-TYPE 585 SYNTAX SEQUENCE OF PethNotificationControlEntry 586 MAX-ACCESS not-accessible 587 STATUS current 588 DESCRIPTION 589 "A table of objects that display and control the 590 Notification on a PSE device. 591 Values of all read-write objects in this table are 592 persistent at restart/reboot." 593 ::= { pethNotificationControl 1 } 595 pethNotificationControlEntry OBJECT-TYPE 596 SYNTAX PethNotificationControlEntry 597 MAX-ACCESS not-accessible 598 STATUS current 599 DESCRIPTION 600 "A set of objects that control the Notification events." 601 INDEX { pethNotificationControlGroupIndex } 602 ::= { pethNotificationControlTable 1 } 604 PethNotificationControlEntry ::= SEQUENCE { 605 pethNotificationControlGroupIndex 606 Integer32, 607 pethNotificationControlEnable 608 TruthValue 609 } 610 pethNotificationControlGroupIndex OBJECT-TYPE 611 SYNTAX Integer32 (1..2147483647) 612 MAX-ACCESS not-accessible 613 STATUS current 614 DESCRIPTION 615 "This variable uniquely identifies the group. Group 616 means box in the stack, module in a rack and the value 617 1 MUST be used for non-modular devices. Furthermore, 618 the same value MUST be used in this variable, 619 pethPsePortGroupIndex, and 620 pethMainPseGroupIndex to refer to a given box in a 621 stack or module in a rack. " 622 ::= { pethNotificationControlEntry 1 } 624 pethNotificationControlEnable OBJECT-TYPE 625 SYNTAX TruthValue 626 MAX-ACCESS read-write 627 STATUS current 628 DESCRIPTION 629 "This object controls, on a per-group basis, whether 630 or not notifications from the agent are enabled. The 631 value true(1) means that notifications are enabled; the 632 value false(2) means that they are not." 633 ::= { pethNotificationControlEntry 2 } 635 -- 636 -- Notifications Section 637 -- 638 -- 640 pethPsePortOnOffNotification NOTIFICATION-TYPE 641 OBJECTS { pethPsePortDetectionStatus } 642 STATUS current 643 DESCRIPTION 644 " This Notification indicates if Pse Port is delivering or 645 not power to the PD. This Notification SHOULD be sent on 646 every status change except in the searching mode. 647 At least 500 msec must elapse between notifications 648 being emitted by the same object instance." 649 ::= { pethNotifications 1 } 651 pethMainPowerUsageOnNotification NOTIFICATION-TYPE 652 OBJECTS { pethMainPseConsumptionPower } 653 STATUS current 654 DESCRIPTION 655 " This Notification indicate PSE Threshold usage 656 indication is on, the usage power is above the 657 threshold. At least 500 msec must elapse between 658 notifications being emitted by the same object 659 instance." 660 ::= { pethNotifications 2 } 662 pethMainPowerUsageOffNotification NOTIFICATION-TYPE 663 OBJECTS { pethMainPseConsumptionPower } 664 STATUS current 665 DESCRIPTION 666 " This Notification indicates PSE Threshold usage indication 667 off, the usage power is below the threshold. 668 At least 500 msec must elapse between notifications being 669 emitted by the same object instance." 670 ::= { pethNotifications 3 } 672 -- 673 -- Conformance Section 674 -- 675 pethCompliances OBJECT IDENTIFIER ::= { pethConformance 1 } 676 pethGroups OBJECT IDENTIFIER ::= { pethConformance 2 } 678 pethCompliance MODULE-COMPLIANCE 679 STATUS current 680 DESCRIPTION 681 "Describes the requirements for conformance to the 682 Power Ethernet MIB." 683 MODULE -- this module 684 MANDATORY-GROUPS { pethPsePortGroup, 685 pethPsePortNotificationGroup, 686 pethNotificationControlGroup 687 } 688 GROUP pethMainPseGroup 689 DESCRIPTION 690 "The pethMainPseGroup is mandatory for PSE systems 691 that implement a main power supply." 692 GROUP pethMainPowerNotificationGroup 693 DESCRIPTION 694 "The pethMainPowerNotificationGroup is mandatory for 695 PSE systems that implement a main power supply." 696 ::= { pethCompliances 1 } 698 pethPsePortGroup OBJECT-GROUP 699 OBJECTS { 700 pethPsePortAdminEnable, 701 pethPsePortPowerPairsControlAbility, 702 pethPsePortPowerPairs, 703 pethPsePortDetectionStatus, 704 pethPsePortPowerPriority, 705 pethPsePortMPSAbsentCounter, 706 pethPsePortInvalidSignatureCounter, 707 pethPsePortPowerDeniedCounter, 708 pethPsePortOverLoadCounter, 709 pethPsePortShortCounter, 710 pethPsePortType, 711 pethPsePortPowerClassifications 712 } 713 STATUS current 714 DESCRIPTION 715 "PSE Port objects." 716 ::= { pethGroups 1 } 718 pethMainPseGroup OBJECT-GROUP 719 OBJECTS { 720 pethMainPsePower, 721 pethMainPseOperStatus, 722 pethMainPseConsumptionPower, 723 pethMainPseUsageThreshold 724 } 725 STATUS current 726 DESCRIPTION 727 "Main PSE Objects. " 728 ::= { pethGroups 2 } 730 pethNotificationControlGroup OBJECT-GROUP 731 OBJECTS { 732 pethNotificationControlEnable 733 } 734 STATUS current 735 DESCRIPTION 736 "Notification Control Objects. " 737 ::= { pethGroups 3 } 739 pethPsePortNotificationGroup NOTIFICATION-GROUP 740 NOTIFICATIONS { pethPsePortOnOffNotification} 741 STATUS current 742 DESCRIPTION "Pse Port Notifications." 743 ::= { pethGroups 4 } 745 pethMainPowerNotificationGroup NOTIFICATION-GROUP 746 NOTIFICATIONS { pethMainPowerUsageOnNotification, 747 pethMainPowerUsageOffNotification} 748 STATUS current 749 DESCRIPTION "Main PSE Notifications." 750 ::= { pethGroups 5 } 752 END 754 6. Acknowledgements 756 This document is the product of the Ethernet Interfaces 757 and Hub MIB WG. The authors would like to recognize the 758 special contributions of C.M. Heard and David Law. 760 7. Normative References 762 [RFC2026] Bradner, S., "The Internet Standards Process - Revision 763 3", BCP 9, RFC 2026, October 1996. 765 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 766 Rose, M. and S. Waldbusser, "Structure of Management 767 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 768 1999. 770 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 771 Rose, M. and S. Waldbusser, "Textual Conventions for 772 SMIv2", STD 58, RFC 2579, April 1999. 774 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 775 Rose, M. and S. Waldbusser, "Conformance Statements for 776 SMIv2", STD 58, RFC 2580, April 1999. 778 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 779 Requirement Levels", BCP 14, RFC 2119, March 1997. 781 [RFC2665] Flick, J., and J. Johnson, "Definitions of Managed 782 Objects for the Ethernet-like Interface Types", RFC 783 2665, August 1999. 785 NOTE - This RFC is under revision by the WG, and may be obsolete by 786 the time of the publication. The RFC editor should replace it with 787 the revised version, if available. 789 [RFC3411] Harrington, D., Presuhn, R. and B. Wijnen, "An 790 Architecture for Describing Simple Network Management 791 Protocol (SNMP) Management Frameworks", RFC 3411, 792 December 2002. 794 [IEEE-802.3af] IEEE 802.3 Working Group, "Data Terminal Equipment 795 (DTE)Power via Media Dependent Interface (MDI)", publication 796 date TBD 798 NOTE - This normative reference will be replaced with the IEEE 802.3af 799 Standard as soon as the IEEE will ratify it (expected date - July 2003) 801 8. Informative References 803 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 804 "Introduction and Applicability Statements for Internet- 805 Standard Management Framework", RFC 3410, December 2002 807 9.Intellectual Property 809 The IETF takes no position regarding the validity or scope of any 810 intellectual property or other rights that might be claimed to 811 pertain to the implementation or use of the technology described in 812 this document or the extent to which any license under such rights 813 might or might not be available; neither does it represent that it 814 has made any effort to identify any such rights. Information on the 815 IETF's procedures with respect to rights in standards-track and 816 standards-related documentation can be found in BCP-11. Copies of 817 claims of rights made available for publication and any assurances of 818 licenses to be made available, or the result of an attempt made to 819 obtain a general license or permission for the use of such 820 proprietary rights by implementors or users of this specification can 821 be obtained from the IETF Secretariat. 823 The IETF invites any interested party to bring to its attention any 824 copyrights, patents or patent applications, or other proprietary 825 rights which may cover technology that may be required to practice 826 this standard. Please address the information to the IETF Executive 827 Director. 829 10. Security Considerations 831 There are a number of management objects defined in this MIB module 832 with a MAX-ACCESS clause of read-write. Such objects may be 833 considered sensitive or vulnerable in some network environments. 834 The support for SET operations in a non-secure environment without 835 proper protection can have a negative effect on network operations. 837 Setting the following object to incorrect values can result in 838 improper operation of the PSE, including the possibility that the 839 PD does not receive power from the PSE port: 841 pethPsePortAdminEnable 842 pethPsePortPowerPairs 843 pethPsePortPowerPriority 844 pethPsePortType 846 Setting the following objects to incorrect values can result in an 847 excessive number of traps being sent to network management stations: 849 pethMainPseUsageThreshold 850 pethNotificationControlEnable 852 Some of the readable objects in this MIB module (i.e., objects with a 853 MAX-ACCESS other than not-accessible) may be considered sensitive or 854 vulnerable in some network environments. These are: 856 pethPsePortPowerPairsControlAbility 857 pethPsePortPowerPriority 858 pethPsePortPowerClassifications 860 It is thus important to control even GET and/or NOTIFY access to 861 these objects and possibly to even encrypt their values when sending 862 them over the network via SNMP. 864 SNMP versions prior to SNMPv3 did not include adequate security. 865 Even if the network itself is secure (for example by using IPSec), 866 even then, there is no control as to who on the secure network is 867 allowed to access and GET/SET (read/change/create/delete) the objects 868 in this MIB module. 870 It is RECOMMENDED that implementers consider the security features as 871 provided by the SNMPv3 framework (see [RFC3410], section 8), 872 including full support for the SNMPv3 cryptographic mechanisms (for 873 authentication and privacy). 875 Further, deployment of SNMP versions prior to SNMPv3 is NOT 876 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 877 enable cryptographic security. It is then a customer/operator 878 responsibility to ensure that the SNMP entity giving access to an 879 instance of this MIB module is properly configured to give access to 880 the objects only to those principals (users) that have legitimate 881 rights to indeed GET or SET (change/create/delete) them. 883 11. Authors Addresses 885 Avi Berger 886 PowerDsine Inc. 887 1, Hanagar St., P.O. Box 7220 888 Hod Hasharon 45421, 889 Israel 890 Tel: +972-9-7755100 Ext 307 891 Fax: +972-9-7755120 892 E-mail: avib@PowerDsine.com 894 Dan Romascanu 895 Avaya 896 Atidim Technology Park, Bldg. #3 897 Tel Aviv, 61131 898 Israel 899 Tel: +972-3-645-8414 900 Email: dromasca@avaya.com 902 A. Full Copyright Statement 904 Copyright (c) The Internet Society (2003). All Rights Reserved 906 This document and translations of it may be copied and furnished to 907 others, and derivative works that comment on or otherwise explain it 908 or assist in its implementation may be prepared, copied, published 909 and distributed, in whole or in part, without restriction of any 910 kind, provided that the above copyright notice and this paragraph are 911 included on all such copies and derivative works. However, this 912 document itself may not be modified in any way, such as by removing 913 the copyright notice or references to the Internet Society or other 914 Internet organizations, except as needed for the purpose of 915 developing Internet standards in which case the procedures for 916 copyrights defined in the Internet Standards process must be 917 followed, or as required to translate it into languages other than 918 English. 920 The limited permissions granted above are perpetual and will not be 921 revoked by the Internet Society or its successors or assigns. 923 This document and the information contained herein is provided on an 924 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 925 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 926 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 927 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 928 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.