idnits 2.17.1 draft-ietf-dhc-server-mib-04.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: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. == The page length should not exceed 58 lines per page, but there was 21 longer pages, the longest (page 1) being 63 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 37 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Overview' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 7. Security Considerations' ) ** 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.) ** The document seems to lack an Authors' Addresses Section. ** There are 489 instances of too long lines in the document, the longest one being 10 characters in excess of 72. ** The abstract seems to contain references ([DEN], [RFC2119], [RFC2287], [RFC1902,RFC1903,, [RFC2131], [RFC2132], [RFC2274], [RFC1902], [RFC2275], [RFC1903], RFC1904], [RFC1904]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? RFC 2119 keyword, line 93: '...ftware. Servers MAY also provide addi...' RFC 2119 keyword, line 201: '...ich have expired MAY appear in the add...' RFC 2119 keyword, line 225: '... According to [RFC2131], servers SHOULD try to determine if an...' RFC 2119 keyword, line 353: '... resolution SHOULD round this val...' RFC 2119 keyword, line 388: '... This string MUST contain only pri...' (4 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (October 1999) is 8961 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'RFC1902' on line 1687 looks like a reference -- Missing reference section? 'RFC1903' on line 1692 looks like a reference -- Missing reference section? 'RFC1904' on line 1696 looks like a reference -- Missing reference section? 'RFC2287' on line 1709 looks like a reference -- Missing reference section? 'RFC2119' on line 1700 looks like a reference -- Missing reference section? 'DEN' on line 1684 looks like a reference -- Missing reference section? 'RFC2131' on line 1703 looks like a reference -- Missing reference section? 'RFC2274' on line 1673 looks like a reference -- Missing reference section? 'RFC2275' on line 1674 looks like a reference -- Missing reference section? 'RFC2132' on line 1706 looks like a reference Summary: 10 errors (**), 0 flaws (~~), 3 warnings (==), 13 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group R. B. Hibbs 2 INTERNET-DRAFT Pacific Bell 3 Category: Standards Track G. Waters 4 Nortel Networks 5 October 1999 7 Dynamic Host Configuration Protocol (DHCP) Server MIB 9 10 Saved Thursday, October 21, 1999, 3:19 PM 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. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six 23 months and may be updated, replaced, or obsoleted by other documents 24 at any time. It is inappropriate to use Internet-Drafts as 25 reference material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 To learn the current status of any Internet-Draft, please check the 34 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 35 Directories on ds.internic.net (US East Coast), nic.nordu.net 36 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific 37 Rim). 39 Copyright Notice 41 Copyright (C) The Internet Society (1999). All Rights Reserved. 43 Abstract 45 This memo defines an experimental portion of the Management 46 Information Base (MIB) for use with network management protocols in 47 the Internet Community. In particular, it defines objects used for 48 the management of Dynamic Host Configuration Protocol (DHCP) and 49 Bootstrap Protocol (BOOTP) servers. 51 This version (the "-05" draft) closes several issues raised during 52 peer review discussions on the DHC mailing list, incorporates 53 several new elements, and makes a number of small revisions based on 54 comments from reviewers. See Section 5.2 for a better description 55 of the changes. 57 Table of Contents 59 1. Introduction......................................................2 60 2. Overview..........................................................2 61 2.1. BOOTP and DHCP Counter Groups..................................3 62 2.2. BOOTP and DHCP Statistics Group................................3 63 2.3. Server Configuration Group.....................................4 64 2.4. Response Times and ICMP Echo...................................5 65 3. Definitions.......................................................5 66 4. Intellectual Property............................................33 67 5. Notes............................................................33 68 5.1. Issues........................................................33 69 5.2. Changes from Prior Drafts.....................................34 70 6. Acknowledgements.................................................34 71 7. Security Considerations..........................................35 72 8. References.......................................................35 73 9. Editors' Addresses...............................................36 74 10. Full Copyright Statement........................................36 76 1. Introduction 78 This memo was produced by the DHCP Working Group and defines a 79 portion of the Management Information Base (MIB) for use with 80 network management protocols in the Internet community. In 81 particular, it describes a set of extensions that DHCP and Bootstrap 82 Protocol (BOOTP) servers implement. Many implementations support 83 both DHCP and BOOTP within a single server and hence this memo 84 describes the MIB for both DHCP and BOOTP servers. 86 This memo does not cover DHCP/BOOTP client nor relay agent MIB 87 extensions: these are possibly the subjects of future investigation. 89 This memo is based on the Internet-standard Network Management 90 Framework as defined by documents [RFC1902, RFC1903, RFC1904]. 92 Objects defined in this MIB allow access to and control of DHCP 93 Server Software. Servers MAY also provide additional management 94 capabilities through the use of the Applications MIB [RFC2287]. 96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 98 this document are to be interpreted as described in document 99 [RFC2119]. 101 2. Overview 103 In the tradition of the Simple Network Management Protocol (SNMP) 104 the minimum number of objects possible are defined in this MIB, 105 while still providing as rich a set of management information as 106 possible. An object is left out of this MIB when it can be derived 107 from other objects that are provided. Further to the tradition of 108 the SNMP, computationally intense operations are left to the domain 109 of the management station. Thus, this MIB provides a set of objects 110 from which other management information may be derived. 112 The examples provided in the following sections are not meant to be 113 comprehensive, they are merely illustrative of the potential uses of 114 the objects defined by this MIB. 116 2.1. BOOTP and DHCP Counter Groups 118 This section describes some of the management information that may 119 be derived from the objects provided in the counter groups. 121 The total number of valid DHCP packets received by the server is 122 computed as the sum of the dhcpCountDiscovers, dhcpCountRequests, 123 dhcpCountReleases, dhcpCountDeclines, and dhcpCountInforms objects. 124 The total number of valid packets (BOOTP and DHCP) received is 125 computed as the total number of valid DHCP packets plus the value of 126 the bootpCountRequests object. The total number of packets received 127 is computed as the total number of valid packets plus 128 bootpCountInvalids and dhcpCountInvalids. 130 Similar to the received computations, the total number of DHCP 131 packets sent by the server is computed as the sum of the 132 dhcpCountOffers, dhcpCountAcks, and dhcpCountNacks objects. The 133 number of packets (BOOTP and DHCP) sent by the server is computed as 134 the total number of DHCP packets sent plus the value of the 135 bootpCountReplies object. 137 2.2. BOOTP and DHCP Statistics Group 139 This section describes some of the management information that may 140 be derived from the objects provided in the statistics group. 142 Given time 1 (t1) and time 2 (t2) greater than t1, the mean inter- 143 arrival time of valid DHCP messages for the interval t1 to t2 can be 144 computed as (dhcpStatLastArrivalTime at t2 minus 145 dhcpStatLastArrivalTime at t1) divided by (valid DHCP received 146 packet count at t2 minus valid DHCP received packet count at t1). 148 Under the simplifying assumption that the capture of packet counts 149 and times is discontinuous (that is, for the measurement interval 150 the captured data represents the complete set for the server) the 151 variance of the mean may be computed as 152 (dhcpStatSumSquaresArrivalTime at t2 less 153 dhcpStatSumSquaresArrivalTime at t1) divided by (valid DHCP received 154 packet count at t2 less valid DHCP received packet count at t1). 155 Standard deviation of the mean is the square root of the variance. 157 Calculation of statistics for message response time is entirely 158 similar to the calculations for inter-arrival time, except that the 159 response time objects are used for the calculations. 161 Calculation of statistics for BOOTP is similar to the calculations 162 for DHCP, except that the similar objects from the bootStatistics 163 group are used instead of the objects from dhcpStatistics group. 165 2.3. Server Configuration Group 167 The server configuration group contains objects that describe the 168 configuration information that is contained in the server. Some of 169 the configuration information is static (e.g.: a statically 170 configured IP address) and some of the configuration is dynamic 171 (e.g.: an assigned DHCP lease). The intent of the server 172 configuration group is to be able to read the server's 173 configuration. Mechanisms outside of the SNMP are currently in use 174 (e.g.: vendor defined solutions) and are being standardized (e.g.: 175 the Directory Enabled Networks [DEN] initiative) to update a 176 server's configuration. 178 The configuration information provides a minimal set of information 179 that most servers should be able to provide. Each row of the 180 serverSubnetTable lists the subnet, the subnet mask, and the subnet 181 that is equivalent to this subnet. Equivalence is defined as more 182 than one subnet being present on the same physical media as some 183 other subnet. 185 The serverRangeTable lists the start and end IP addresses of the 186 ranges and the subnet which the range is a member of. The 187 serverRangeInUse object indicates the amount of the range that is 188 currently in use, either through dynamic allocation or being 189 reserved. The range size can be computed by taking the difference 190 of the serverRangeStart and serverRangeEnd objects. 192 The serverAddressTable provides information about the static and 193 dynamic addresses that the server contains in its configuration. 194 Addresses may be: 196 o Static, in which case they are predefined though the server's 197 configuration. Static addresses may or may not have been 198 previously served by the server; 200 o Dynamic, in which case the server has served the addresses at 201 least once. Leases which have expired MAY appear in the address 202 list; 204 o Configuration-reserved, in which case the address is not 205 available for the server to allocate to a client. A 206 configuration-reserved address is one that has been reserved by 207 the administrator. An example of a configuration-reserved address 208 is an address that is assigned to a client, not through DHCP 209 (e.g.: statically assigned), and the address is within a DHCP 210 range; and, 212 o Server-reserved, in which case the server has taken the address 213 out of use. Examples of server-reserved addresses are those 214 which have been declined (i.e.: through a DHCPDECLINE) by a 215 client or those which have responded to an ICMP echo before they 216 were assigned. 218 The protocol used to allocate the address may be determined from the 219 serverAddressServedProtocol object. This object indicates whether 220 the address has never been served (value of none(1)), or, whether 221 BOOTP or DHCP was used to allocate the address. 223 2.4. Response Times and ICMP Echo 225 According to [RFC2131], servers SHOULD try to determine if an 226 address is in use before assigning it. Some servers choose not to 227 perform this check, letting the client determine for itself if the 228 address is in use. Other servers perform an ICMP echo (Ping) just 229 prior to assigning an address. Servers that perform a Ping before 230 responding to a DHCPDISCOVER should not include in the response time 231 the time from when the Ping was transmitted until the time that 232 either a response was received or that the server timed out waiting 233 for a response. 235 3. Definitions 237 -- definitions for a DHCP (Dynamic Host Configuration Protocol) 238 server 240 DHCP-SERVER-MIB DEFINITIONS ::= BEGIN 242 IMPORTS 243 Counter64, Counter32, Gauge32, Unsigned32, mib-2, 244 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, IpAddress 245 FROM SNMPv2-SMI 247 TEXTUAL-CONVENTION, RowStatus, DisplayString, TruthValue, 248 DateAndTime 249 FROM SNMPv2-TC 251 MODULE-COMPLIANCE, OBJECT-GROUP, -- /*modified*/ 252 NOTIFICATION-GROUP -- /*new*/ 253 FROM SNMPv2-CONF; 255 dhcp OBJECT-IDENTITY 256 STATUS current 257 DESCRIPTION 258 "The dhcp branch in the standard network management 259 framework." 260 ::= { mib-2 99 } -- IANA will make official assignment 262 dhcpServerMIB MODULE-IDENTITY -- /*renamed*/ 263 LAST-UPDATED "9910060000Z" 264 ORGANIZATION "IETF DHCP Working Group" 265 CONTACT-INFO 266 " Richard Barr Hibbs 267 Postal: Pacific Bell 268 666 Folsom Street, Room 1225 269 San Francisco, CA 94107-1384 270 USA 271 Tel: +1 415-545-1576 272 Fax: +1 415-543-3539 273 Email: rbhibbs@pacbell.com 275 Glenn Waters 276 Postal: Nortel Networks, Inc. 277 310-875 Carling Avenue 278 Ottawa, Ontario K1S 5P1 279 Canada 280 Tel: +1 613-798-4925 281 Email: gww@nortelnetworks.com" 282 DESCRIPTION 283 "The MIB module for entities implementing the server side of the 284 Bootstrap Protocol (BOOTP) and the Dynamic Host Configuration 285 protocol (DHCP) for Internet Protocol version 4(IPv4). This MIB 286 does not include support for Dynamic DNS (DDNS) updating nor for 287 the DHCP Failover Protocol." 288 ::= { dhcp 1 } 290 dhcpServerMIBObjects OBJECT-IDENTITY -- /*renamed*/ 291 STATUS current 292 DESCRIPTION 293 "DHCP Server MIB objects are all defined in this branch." 294 ::= { dhcpServerMIB 1 } -- /*renamed*/ 296 serverSystem OBJECT-IDENTITY 297 STATUS current 298 DESCRIPTION 299 "Group of objects that are related to the overall system." 300 ::= { dhcpServerMIBObjects 1 } -- /*renamed*/ 302 bootpCounters OBJECT-IDENTITY 303 STATUS current 304 DESCRIPTION 305 "Group of objects that count various BOOTP events." 306 ::= { dhcpServerMIBObjects 2 } -- /*renamed*/ 308 dhcpCounters OBJECT-IDENTITY 309 STATUS current 310 DESCRIPTION 311 "Group of objects that count various DHCP events." 312 ::= { dhcpServerMIBObjects 3 } -- /*renamed*/ 314 bootpStatistics OBJECT-IDENTITY 315 STATUS current 316 DESCRIPTION 317 "Group of objects that measure various BOOTP statistics." 318 ::= { dhcpServerMIBObjects 4 } -- /*renamed*/ 320 dhcpStatistics OBJECT-IDENTITY 321 STATUS current 322 DESCRIPTION 323 "Group of objects that measure various DHCP statistics." 324 ::= { dhcpServerMIBObjects 5 } -- /*renamed*/ 326 serverConfiguration OBJECT-IDENTITY 327 STATUS current 328 DESCRIPTION 329 "Objects that contain pre-configured and dynamic 330 configuration 331 information." 332 ::= { dhcpServerMIBObjects 6 } -- /*renamed*/ 334 bootpClients OBJECT-IDENTITY 335 STATUS current 336 DESCRIPTION 337 "Objects that map bootp clients to IP addresses." 338 ::= { dhcpServerMIBObjects 7 } -- /*renamed*/ 340 dhcpClients OBJECT-IDENTITY 341 STATUS current 342 DESCRIPTION 343 "Objects that map DHCP clients to IP addresses." 344 ::= { dhcpServerMIBObjects 8 } -- /*renamed*/ 346 -- Textual conventions defined by this memo 348 DhcpTimeInterval ::= TEXTUAL-CONVENTION 349 STATUS current 350 DESCRIPTION 351 "The number of milli-seconds that has elapsed since some epoch. 352 Systems that cannot measure events to the milli-second 353 resolution SHOULD round this value to the next available 354 resolution that the system supports." 355 SYNTAX Unsigned32 357 PhysicalAddress ::= TEXTUAL-CONVENTION -- /*new*/ 358 SYNTAX OCTET STRING (SIZE (1..17)) 359 DISPLAY-HINT "t,xx[:xx...]" 360 STATUS current 361 REFERENCE "RFC 2131" 362 DESCRIPTION 363 "A Layer 1 address which includes the hardware type 364 space as well as the usual MAC address. This object is 365 encoded as 366
367 where 368 is the value of the hardware type space 369 field, as used in ARP (e.g., 1 for Ethernet, 370 6 for token ring). IANA maintains the list of 371 registered numbers for this field. 372
is the hardware address of the MAC (Media 373 Adapter Card) interface, of size 374 octets. 375 This encoding is intended to mirror the representation 376 of MAC addresses in DHCP." 378 -- serverSystem Group 380 serverSystemDescr OBJECT-TYPE 381 SYNTAX DisplayString (SIZE (0..255)) 382 MAX-ACCESS read-only 383 STATUS current 384 DESCRIPTION 385 "A textual description of the server. This value should 386 include the full name and version identification of the 387 server. 388 This string MUST contain only printable NVT ASCII 389 characters." 390 ::= { serverSystem 1 } 392 serverSystemObjectID OBJECT-TYPE 393 SYNTAX OBJECT IDENTIFIER 394 MAX-ACCESS read-only 395 STATUS current 396 DESCRIPTION 397 "The vendor's authoritative identification of the network 398 management subsystem contained in this entity. This value is 399 allocated within the SMI enterprise subtree (1.3.6.1.4.1) and 400 provides an easy and unambiguous means for determining 'what 401 kind of server' is being managed. For example, if vendor 402 'VeryBigServers, Inc.' is assigned the subtree 403 1.3.6.1.4.1.4242, it may assign the identifier 404 1.3.6.1.4.1.4242.1.1 to its `Hercules DHCP Server'." 405 ::= { serverSystem 2 } 407 -- bootpCounters Group 409 bootpCountRequests OBJECT-TYPE 410 SYNTAX Counter32 411 MAX-ACCESS read-only 412 STATUS current 413 DESCRIPTION 414 "The number of packets received that contain a Message Type of 415 1 (BOOTREQUEST) in the first octet and do not contain option 416 number 53 (DHCP Message Type) in the options." 417 ::= { bootpCounters 1 } 419 bootpCountInvalids OBJECT-TYPE 420 SYNTAX Counter32 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 424 "The number of packets received that do not contain a Message 425 Type of 1 (BOOTREQUEST) in the first octet or are not valid 426 BOOTP packets (e.g., too short, invalid field in packet 427 header)." 428 ::= { bootpCounters 2 } 430 bootpCountReplies OBJECT-TYPE 431 SYNTAX Counter32 432 MAX-ACCESS read-only 433 STATUS current 434 DESCRIPTION 435 "The number of packets sent that contain a Message Type of 1 436 (BOOTREQUEST) in the first octet and do not contain option 437 number 53 (DHCP Message Type) in the options." 438 ::= { bootpCounters 3 } 440 bootpCountDroppedUnknownClients OBJECT-TYPE 441 SYNTAX Counter32 442 MAX-ACCESS read-only 443 STATUS current 444 DESCRIPTION 445 "The number of BOOTP packets dropped due to the server not 446 recognizing or not providing service to the hardware address 447 received in the incoming packet." 448 ::= { bootpCounters 4 } 450 bootpCountDroppedNotServingSubnet OBJECT-TYPE 451 SYNTAX Counter32 452 MAX-ACCESS read-only 453 STATUS current 454 DESCRIPTION 455 "The number of BOOTP packets dropped due to the server not 456 being configured or not otherwise able to serve addresses on 457 the subnet from which this message was received." 459 ::= { bootpCounters 5 } 461 -- dhcpCounters Group 463 dhcpCountDiscovers OBJECT-TYPE 464 SYNTAX Counter32 465 MAX-ACCESS read-only 466 STATUS current 467 DESCRIPTION 468 "The number of DHCPDISCOVER (option 53 with value 1) packets 469 received." 470 ::= { dhcpCounters 1 } 472 dhcpCountRequests OBJECT-TYPE 473 SYNTAX Counter32 474 MAX-ACCESS read-only 475 STATUS current 476 DESCRIPTION 477 "The number of DHCPREQUEST (option 53 with value 3) packets 478 received." 479 ::= { dhcpCounters 2 } 481 dhcpCountReleases OBJECT-TYPE 482 SYNTAX Counter32 483 MAX-ACCESS read-only 484 STATUS current 485 DESCRIPTION 486 "The number of DHCPRELEASE (option 53 with value 7) packets 487 received." 488 ::= { dhcpCounters 3 } 490 dhcpCountDeclines OBJECT-TYPE 491 SYNTAX Counter32 492 MAX-ACCESS read-only 493 STATUS current 494 DESCRIPTION 495 "The number of DHCPDECLINE (option 53 with value 4) packets 496 received." 497 ::= { dhcpCounters 4 } 499 dhcpCountInforms OBJECT-TYPE 500 SYNTAX Counter32 501 MAX-ACCESS read-only 502 STATUS current 503 DESCRIPTION 504 "The number of DHCPINFORM (option 53 with value 8) packets 505 received." 506 ::= { dhcpCounters 5 } 508 dhcpCountInvalids OBJECT-TYPE 509 SYNTAX Counter32 510 MAX-ACCESS read-only 511 STATUS current 512 DESCRIPTION 513 "The number of DHCP packets received whose DHCP message type 514 (i.e., option number 53) is not understood or handled by the 515 server." 516 ::= { dhcpCounters 6 } 518 dhcpCountOffers OBJECT-TYPE 519 SYNTAX Counter32 520 MAX-ACCESS read-only 521 STATUS current 522 DESCRIPTION 523 "The number of DHCPOFFER (option 53 with value 2) packets 524 sent." 525 ::= { dhcpCounters 7 } 527 dhcpCountAcks OBJECT-TYPE 528 SYNTAX Counter32 529 MAX-ACCESS read-only 530 STATUS current 531 DESCRIPTION 532 "The number of DHCPACK (option 53 with value 5) packets 533 sent." 534 ::= { dhcpCounters 8 } 536 dhcpCountNacks OBJECT-TYPE 537 SYNTAX Counter32 538 MAX-ACCESS read-only 539 STATUS current 540 DESCRIPTION 541 "The number of DHCPNACK (option 53 with value 6) packets 542 sent." 543 ::= { dhcpCounters 9 } 545 dhcpCountDroppedUnknownClient OBJECT-TYPE 546 SYNTAX Counter32 547 MAX-ACCESS read-only 548 STATUS current 549 DESCRIPTION 550 "The number of DHCP packets dropped due to the server not 551 recognizing or not providing service to the client-id and/or 552 hardware address received in the incoming packet." 553 ::= { dhcpCounters 10 } 555 dhcpCountDroppedNotServingSubnet OBJECT-TYPE 556 SYNTAX Counter32 557 MAX-ACCESS read-only 558 STATUS current 559 DESCRIPTION 560 "The number of DHCP packets dropped due to the server not 561 being 562 configured or not otherwise able to serve addresses on the 563 subnet from which this message was received." 564 ::= { dhcpCounters 11 } 566 -- bootpStatistics group 568 bootpStatMinArrivalInterval OBJECT-TYPE 569 SYNTAX DhcpTimeInterval 570 MAX-ACCESS read-write 571 STATUS current 572 DESCRIPTION 573 "The minimum amount of time between receiving two BOOTP 574 messages. A message is received at the server when the server 575 is able to begin processing the message. This typically occurs 576 immediately after the message is read into server memory. If 577 no messages have been received, then this object contains a 578 zero value." 579 ::= { bootpStatistics 1 } 581 bootpStatMaxArrivalInterval OBJECT-TYPE 582 SYNTAX DhcpTimeInterval 583 MAX-ACCESS read-write 584 STATUS current 585 DESCRIPTION 586 "The maximum amount of time between receiving two BOOTP 587 messages. A message is received at the server when the server 588 is able to begin processing the message. This typically occurs 589 immediately after the message is read into server memory. If 590 no messages have been received, then this object contains a 591 zero value." 592 ::= { bootpStatistics 2 } 594 bootpStatLastArrivalTime OBJECT-TYPE 595 SYNTAX DateAndTime 596 MAX-ACCESS read-only 597 STATUS current 598 DESCRIPTION 599 "The date and time that the last valid BOOTP message was 600 received by the server. Invalid messages do not cause this 601 value to change. If valid no messages have been received, 602 then this object contains a date and time that is all zero." 603 ::= { bootpStatistics 3 } 605 bootpStatSumSquaresArrivalTime OBJECT-TYPE 606 SYNTAX Counter64 607 MAX-ACCESS read-only 608 STATUS current 609 DESCRIPTION 610 "The sum of the squared BOOTP packet inter-arrival times in 611 micro-seconds. This value may be used to compute the variance 612 and standard deviation of the BOOTP arrival times. Note that a 613 micro-second resolution of this object requires a clock 614 resolution to the milli-second since the square of a milli- 615 second value produces a value with micro-second resolution." 616 ::= { bootpStatistics 4 } 618 bootpStatMinResponseTime OBJECT-TYPE 619 SYNTAX DhcpTimeInterval 620 MAX-ACCESS read-write 621 STATUS current 622 DESCRIPTION 623 "The smallest time interval measured as the difference between 624 the arrival of a BOOTP message at the server and the successful 625 transmission of the response to that message. A message is 626 received at the server when the server is able to begin 627 processing the message. A message is transmitted after the 628 server has no further use for the message. Note that the 629 operating system may still have the message queued internally. 631 The operating system queue time is not to be considered as part 632 of the response time. Invalid messages do not cause this value 633 to change. If no valid messages have been received, then this 634 object contains a zero value." 635 ::= { bootpStatistics 5 } 637 bootpStatMaxResponseTime OBJECT-TYPE 638 SYNTAX DhcpTimeInterval 639 MAX-ACCESS read-write 640 STATUS current 641 DESCRIPTION 642 "The largest time interval measured as the difference between 643 the arrival of a BOOTP message at the server and the successful 644 transmission of the response to that message. A message is 645 received at the server when the server is able to begin 646 processing the message. A message is transmitted after the 647 server has no further use for the message. Note that the 648 operating system may still have the message queued internally. 650 The operating system queue time is not to be considered as part 651 of the response time. Invalid messages do not cause this value 652 to change. If no valid messages have been received, then this 653 object contains a zero value." 654 ::= { bootpStatistics 6 } 656 bootpStatSumResponseTime OBJECT-TYPE 657 SYNTAX Counter32 658 MAX-ACCESS read-only 659 STATUS current 660 DESCRIPTION 661 "The sum of the response time intervals in milli-seconds where 662 a response time interval is measured as the difference between 663 the arrival of a BOOTP message at the server and the successful 664 transmission of the response to that message. A message is 665 received at the server when the server is able to begin 666 processing the message. A message is transmitted after the 667 server has no further use for the message. Note that the 668 operating system may still have the message queued internally. 670 The operating system queue time is not to be considered as part 671 of the response time. Invalid messages do not cause this value 672 to change. If no valid messages have been received, then this 673 object contains a zero value." 674 ::= { bootpStatistics 7 } 676 bootpStatSumSquaresResponseTime OBJECT-TYPE 677 SYNTAX Counter64 678 MAX-ACCESS read-only 679 STATUS current 680 DESCRIPTION 681 "The sum of the squared BOOTP packet response times in micro- 682 seconds. This value may be used to compute the variance and 683 standard deviation of the BOOTP response times. Note that a 684 micro-second resolution of this object requires a clock 685 resolution to the milli-second since the square of a milli- 686 second value produces a value with micro-second resolution." 687 ::= { bootpStatistics 8 } 689 -- dhcpStatistics group 690 dhcpStatMinArrivalInterval OBJECT-TYPE 691 SYNTAX DhcpTimeInterval 692 MAX-ACCESS read-write 693 STATUS current 694 DESCRIPTION 695 "The minimum amount of time between receiving two DHCP 696 messages. A message is received at the server when the server 697 is able to begin processing the message. This typically 698 occurs 699 immediately after the message is read into server memory. If 700 no messages have been received, then this object contains a 701 zero value." 702 ::= { dhcpStatistics 1 } 704 dhcpStatMaxArrivalInterval OBJECT-TYPE 705 SYNTAX DhcpTimeInterval 706 MAX-ACCESS read-write 707 STATUS current 708 DESCRIPTION 710 "The maximum amount of time between receiving two DHCP messages. 711 A message is received at the server when the server is able to 712 begin processing the message. This typically occurs immediately 713 after the message is read into server memory. If no messages 714 have been received, then this object contains a zero value." 715 ::= { dhcpStatistics 2 } 717 dhcpStatLastArrivalTime OBJECT-TYPE 718 SYNTAX DateAndTime 719 MAX-ACCESS read-only 720 STATUS current 721 DESCRIPTION 722 "The date and time that the last valid DHCP message was 723 received by the server. Invalid messages do not cause this 724 value to change. If no valid messages have been received, then 725 this object contains a date and time that is all zero." 726 ::= { dhcpStatistics 3 } 728 dhcpStatSumSquaresArrivalTime OBJECT-TYPE 729 SYNTAX Counter64 730 MAX-ACCESS read-only 731 STATUS current 732 DESCRIPTION 733 "The sum of the squared DHCP packet inter-arrival times in 734 micro-seconds. This value may be used to compute the variance 735 and standard deviation of the DHCP arrival times. Note that a 736 micro-second resolution of this object requires a clock 737 resolution to the milli-second since the square of a milli- 738 second value produces a value with micro-second resolution." 739 ::= { dhcpStatistics 4 } 741 dhcpStatMinResponseTime OBJECT-TYPE 742 SYNTAX DhcpTimeInterval 743 MAX-ACCESS read-write 744 STATUS current 745 DESCRIPTION 746 "The smallest time interval measured as the difference between 747 the arrival of a DHCP message at the server and the successful 748 transmission of the response to that message. A message is 749 received at the server when the server is able to begin 750 processing the message. A message is transmitted after the 751 server has no further use for the message. Note that the 752 operating system may still have the message queued internally. 753 The operating system queue time is not to be considered as part 754 of the response time. Invalid messages do not cause this value 755 to change. If no valid messages have been received, then this 756 object contains a zero value." 757 ::= { dhcpStatistics 5 } 759 dhcpStatMaxResponseTime OBJECT-TYPE 760 SYNTAX DhcpTimeInterval 761 MAX-ACCESS read-write 762 STATUS current 763 DESCRIPTION 764 "The largest time interval measured as the difference between 765 the arrival of a DHCP message at the server and the successful 766 transmission of the response to that message. A message is 767 received at the server when the server is able to begin 768 processing the message. A message is transmitted after the 769 server has no further use for the message. Note that the 770 operating system may still have the message queued internally. 771 The operating system queue time is not to be considered as part 772 of the response time. Invalid messages do not cause this value 773 to change. If no valid messages have been received, then this 774 object contains a zero value." 775 ::= { dhcpStatistics 6 } 777 dhcpStatSumResponseTime OBJECT-TYPE 778 SYNTAX Counter32 779 MAX-ACCESS read-only 780 STATUS current 781 DESCRIPTION 782 "The sum of the response time intervals in milli-seconds where 783 a response time interval is measured as the difference between 784 the arrival of a DHCP message at the server and the successful 785 transmission of the response to that message. A message is 786 received at the server when the server is able to begin 787 processing the message. A message is transmitted after the 788 server has no further use for the message. Note that the 789 operating system may still have the message queued internally. 790 The operating system queue time is not to be considered as part 791 of the response time. Invalid messages do not cause this value 792 to change. If no valid messages have been received, then this 793 object contains a zero value." 794 ::= { dhcpStatistics 7 } 796 dhcpStatSumSquaresResponseTime OBJECT-TYPE 797 SYNTAX Counter64 798 MAX-ACCESS read-only 799 STATUS current 800 DESCRIPTION 801 "The sum of the squared DHCP packet response times in micro- 802 seconds. This value may be used to compute the variance and 803 standard deviation of the DHCP response times. Note that a 804 micro-second resolution of this object requires a clock 805 resolution to the milli-second since the square of a milli- 806 second value produces a value with micro-second resolution." 807 ::= { dhcpStatistics 8 } 809 -- serverConfiguration group 811 serverSubnetTable OBJECT-TYPE 812 SYNTAX SEQUENCE OF ServerSubnetEntry 813 MAX-ACCESS not-accessible 814 STATUS current 815 DESCRIPTION 816 "A list of subnets that are configured in this server." 817 ::= { serverConfiguration 1 } 819 serverSubnetEntry OBJECT-TYPE 820 SYNTAX ServerSubnetEntry 821 MAX-ACCESS not-accessible 822 STATUS current 823 INDEX { serverSubnet } 824 DESCRIPTION 825 "A logical row in the serverSubnetTable." 826 ::= { serverSubnetTable 1 } 828 ServerSubnetEntry ::= SEQUENCE { 829 serverSubnet IpAddress, 830 serverSubnetMask IpAddress, 831 serverSubnetSharedNet IpAddress 832 } 834 serverSubnet OBJECT-TYPE 835 SYNTAX IpAddress 836 MAX-ACCESS not-accessible 837 STATUS current 838 DESCRIPTION 839 "The IP address of the subnet." 840 ::= { serverSubnetEntry 1 } 842 serverSubnetMask OBJECT-TYPE 843 SYNTAX IpAddress 844 MAX-ACCESS read-only 845 STATUS current 846 DESCRIPTION 847 "The subnet mask of the subnet. This MUST be the same as the 848 value of DHCP option 1 offered to clients on this subnet." 849 ::= { serverSubnetEntry 2 } 851 serverSubnetSharedNet OBJECT-TYPE 852 SYNTAX IpAddress 853 MAX-ACCESS read-only 854 STATUS current 855 DESCRIPTION 856 "The IP address of another subnet that is on the same shared 857 media as this subnet. The address of the shared subnet MUST 858 also be configured on this server. The address 0.0.0.0 should 859 be used if this subnet is not shared." 860 ::= { serverSubnetEntry 3 } 862 serverRangeTable OBJECT-TYPE 863 SYNTAX SEQUENCE OF ServerRangeEntry 864 MAX-ACCESS not-accessible 865 STATUS current 866 DESCRIPTION 867 "A list of ranges that are configured on this server." 868 ::= { serverConfiguration 2 } 870 serverRangeEntry OBJECT-TYPE 871 SYNTAX ServerRangeEntry 872 MAX-ACCESS not-accessible 873 STATUS current 874 INDEX { serverRangeStart } 875 DESCRIPTION 876 "A logical row in the serverRangeTable." 877 ::= { serverRangeTable 1 } 879 ServerRangeEntry ::= SEQUENCE { 880 serverRangeStart IpAddress, 881 serverRangeEnd IpAddress, 882 serverRangeSubnetMask IpAddress, 883 serverRangeInUse Gauge32, 884 serverRangeOutstandingOffers Gauge32 885 } 887 serverRangeStart OBJECT-TYPE 888 SYNTAX IpAddress 889 MAX-ACCESS not-accessible 890 STATUS current 891 DESCRIPTION 892 "The IP address of the first address in the range. The value of 893 range start must be less than or equal to the value of range 894 end." 895 ::= { serverRangeEntry 1 } 897 serverRangeEnd OBJECT-TYPE 898 SYNTAX IpAddress 899 MAX-ACCESS read-only 900 STATUS current 901 DESCRIPTION 902 "The IP address of the last address in the range. The value of 903 range end must be greater than or equal to the value of range 904 start." 905 ::= { serverRangeEntry 2 } 907 serverRangeSubnetMask OBJECT-TYPE 908 SYNTAX IpAddress 909 MAX-ACCESS read-only 910 STATUS current 911 DESCRIPTION 912 "The subnet mask (DHCP option 1) provided to any client offered 913 an address from this range." 914 ::= { serverRangeEntry 3 } 916 serverRangeInUse OBJECT-TYPE 917 SYNTAX Gauge32 918 MAX-ACCESS read-only 919 STATUS current 920 DESCRIPTION 921 "The number of addresses in this range that are currently in 922 use. This number includes those addresses whose lease has not 923 expired and addresses which have been reserved (either by the 924 server or through configuration)." 925 ::= { serverRangeEntry 4 } 927 serverRangeOutstandingOffers OBJECT-TYPE 928 SYNTAX Gauge32 929 MAX-ACCESS read-only 930 STATUS current 931 DESCRIPTION 932 "The number of outstanding DHCPOFFER messages for this range is 933 reported with this value. An offer is outstanding if the 934 server has sent a DHCPOFFER message to a client, but has not 935 yet received a DHCPREQUEST message from the client nor has the 936 server-specific timeout (limiting the time in which a client 937 can respond to the offer message) for the offer message 938 expired." 939 ::= { serverRangeEntry 5 } 941 serverAddressTable OBJECT-TYPE 942 SYNTAX SEQUENCE OF ServerAddressEntry 943 MAX-ACCESS not-accessible 944 STATUS current 945 DESCRIPTION 946 "A list of addresses that are known by this server. The list 947 MUST contain addresses that have not expired. The list MUST 948 NOT contain addresses that have never been assigned by the 949 server UNLESS the lease is pre-configured in the server (e.g., 950 a static lease on a subnet)." 951 ::= { serverConfiguration 3 } 953 serverAddressEntry OBJECT-TYPE 954 SYNTAX ServerAddressEntry 955 MAX-ACCESS not-accessible 956 STATUS current 957 INDEX { serverAddress } 958 DESCRIPTION 959 "A logical row in the serverAddressTable." 960 ::= { serverAddressTable 1 } 962 ServerAddressEntry ::= SEQUENCE { 963 serverAddress IpAddress, 964 serverAddressSubnetMask IpAddress, 965 serverAddressRange IpAddress, 966 serverAddressType INTEGER, 967 serverAddressTimeRemaining Unsigned32, 968 serverAddressAllowedProtocol INTEGER, 969 serverAddressServedProtocol INTEGER, 970 serverAddressMacAddress OCTET STRING, 971 serverAddressClientId OCTET STRING, 972 serverAddressHostName DisplayString, 973 serverAddressDomainName DisplayString 974 } 976 serverAddress OBJECT-TYPE 977 SYNTAX IpAddress 978 MAX-ACCESS not-accessible 979 STATUS current 980 DESCRIPTION 981 "The IP address of the entry." 982 ::= { serverAddressEntry 1 } 984 serverAddressSubnetMask OBJECT-TYPE 985 SYNTAX IpAddress 986 MAX-ACCESS read-only 987 STATUS current 988 DESCRIPTION 989 "The subnet mask (DHCP option 1) provided to the client offered 990 this address. The subnet, resulting from logically ANDing the 991 subnet mask with the entry's IP address, must be configured on 992 this server and appear as a row in the dhcpSubnetTable." 993 ::= { serverAddressEntry 2 } 995 serverAddressRange OBJECT-TYPE 996 SYNTAX IpAddress 997 MAX-ACCESS read-only 998 STATUS current 999 DESCRIPTION 1000 "The starting IP address (serverRangeStart object) of the range 1001 to which this address belongs. If the address does not fall 1002 into one of the configured ranges (e.g., a statically 1003 configured address on a subnet) the range may be 0.0.0.0." 1004 ::= { serverAddressEntry 3 } 1006 serverAddressType OBJECT-TYPE 1007 SYNTAX INTEGER { 1008 static(1), 1009 dynamic(2), 1010 configuration-reserved(3), 1011 server-reserved(4) 1012 } 1013 MAX-ACCESS read-only 1014 STATUS current 1015 DESCRIPTION 1016 "The type of this address." 1017 ::= { serverAddressEntry 4 } 1019 serverAddressTimeRemaining OBJECT-TYPE 1020 SYNTAX Unsigned32 1021 MAX-ACCESS read-only 1022 STATUS current 1023 DESCRIPTION 1024 "The number of seconds until the lease expires. A value of 1025 4294967295 (i.e., 0xFFFFFFFF) should be used for leases that 1026 have a lease time which is 'infinite' and for BOOTP leases." 1027 ::= { serverAddressEntry 5 } 1029 serverAddressAllowedProtocol OBJECT-TYPE 1030 SYNTAX INTEGER { 1031 none(1), 1032 bootp(2), 1033 dhcp(3), 1034 bootp-or-dhcp(4) 1035 } 1036 MAX-ACCESS read-only 1037 STATUS current 1038 DESCRIPTION 1039 "The type of protocol that is allowed to be used to serve this 1040 address. A type of none(1) indicates that the address is not 1041 available to be served (e.g., a reserved address)." 1042 ::= { serverAddressEntry 6 } 1044 serverAddressServedProtocol OBJECT-TYPE 1045 SYNTAX INTEGER { 1046 none(1), 1047 bootp(2), 1048 dhcp(3) 1049 } 1050 MAX-ACCESS read-only 1051 STATUS current 1052 DESCRIPTION 1053 "The type of protocol that was used when this address was 1054 assigned. This object will have the value of none(1) if the 1055 address has not been served." 1056 ::= { serverAddressEntry 7 } 1058 serverAddressHardwareAddress OBJECT-TYPE -- /*renamed*/ 1059 SYNTAX PhysicalAddress -- /*modified*/ 1060 MAX-ACCESS read-only 1061 STATUS current 1062 DESCRIPTION 1063 "The hardware type and hardware address of the client that has 1064 been assigned this lease. The first octet of this object 1065 contains the hardware type from the 'htype' field of the BOOTP 1066 packet and the remaining octets contain the hardware address 1067 from the 'chaddr' field of the BOOTP packet. This object may 1068 be empty if the address has not been previously served." 1069 ::= { serverAddressEntry 8 } 1071 serverAddressClientId OBJECT-TYPE 1072 SYNTAX OCTET STRING (SIZE (0..255)) 1073 MAX-ACCESS read-only 1074 STATUS current 1075 DESCRIPTION 1076 "The client-id of the client that has been assigned this lease. 1077 The client-id is the value specified in option 61 (client-id 1078 option) when the lease was assigned. This object may be e,[pty 1079 if the lease has not been previously assigned or if the client- 1080 id option was not specified when the address was assigned." 1081 ::= { serverAddressEntry 9 } 1083 serverAddressHostName OBJECT-TYPE 1084 SYNTAX DisplayString (SIZE (0..255)) 1085 MAX-ACCESS read-only 1086 STATUS current 1087 DESCRIPTION 1088 "The host name (DHCP option 12) the client is configured to use, 1089 or if no host name was configured then the host name that the 1090 client supplied when requesting an address." 1091 ::= { serverAddressEntry 10 } 1093 serverAddressDomainName OBJECT-TYPE 1094 SYNTAX DisplayString (SIZE (0..255)) 1095 MAX-ACCESS read-only 1096 STATUS current 1097 DESCRIPTION 1098 "The domain name (DHCP option 15) assigned to the client. 1099 " 1100 ::= { serverAddressEntry 11 } 1102 serverClientTable OBJECT-TYPE 1103 SYNTAX SEQUENCE OF ServerClientEntry 1104 MAX-ACCESS not-accessible 1105 STATUS current 1106 DESCRIPTION 1107 "A list of clients that are known by this server. Details 1108 about the clients may be found by indexing into the 1109 serverAddressTable using the serverClientAddress object. This 1110 table is indexed first by the MAC address of the client and then 1111 by the subnet address on which the client resides. The subnet 1112 is included as an index since a MAC address is only guaranteed 1113 to be unique within a subnet (i.e., a MAC address is not 1114 globally unique)." 1115 ::= { bootpClients 1 } 1117 serverClientEntry OBJECT-TYPE 1118 SYNTAX ServerClientEntry 1119 MAX-ACCESS not-accessible 1120 STATUS current 1121 INDEX { 1122 serverClientHardwareAddress, -- /*renamed*/ 1123 serverClientSubnet 1124 } 1125 DESCRIPTION 1126 "A logical row in the serverClientTable. An entry in this table 1127 may be a client that requested an address but was refused (e.g., 1128 not authorized). Servers MAY track these types of clients if 1129 desired and may choose to remove such client entries using a 1130 server defined algorithm. As an example, a server may choose to 1131 keep client request that does not map to an address for a one 1132 hour time period before removing that entry from this table." 1133 ::= { serverClientTable 1 } 1135 ServerClientEntry ::= SEQUENCE { 1136 serverClientHardwareAddress PhsicalAddress -- /*renamed*/ 1137 serverClientSubnetMask IpAddress, 1138 serverClientAddress IpAddress, 1139 serverClientLastRequestTime DateAndTime, 1140 serverClientLastRequestType INTEGER, 1141 serverClientLastResponseType INTEGER 1142 } 1144 serverClientHardwareAddress OBJECT-TYPE -- /*renamed*/ 1145 SYNTAX PhysicalAddress -- /*modified*/ 1146 MAX-ACCESS not-accessible 1147 STATUS current 1148 DESCRIPTION 1149 "The hardware type and hardware address of the client that has 1150 been assigned this lease. The first octet of this object 1151 contains the hardware type from the 'htype' field of the BOOTP 1152 packet and the remaining octets contain the hardware address 1153 from the 'chaddr' field of the BOOTP packet." 1154 ::= { serverClientEntry 1 } 1156 serverClientSubnetMask OBJECT-TYPE 1157 SYNTAX IpAddress 1158 MAX-ACCESS not-accessible 1159 STATUS current 1160 DESCRIPTION 1161 "The subnet mask (DHCP option 1) applied to 1162 serverClientAddress." -- /*modified*/ 1163 ::= { serverClientEntry 2 } 1165 serverClientAddress OBJECT-TYPE 1166 SYNTAX IpAddress 1167 MAX-ACCESS read-only 1168 STATUS current 1169 DESCRIPTION 1170 "The IP address of the entry. May be used to index into the 1171 serverAddressTable. May be 0.0.0.0 if an address is not 1172 associated with this client." 1173 ::= { serverClientEntry 3 } 1175 serverClientLastRequestTime OBJECT-TYPE 1176 SYNTAX DateAndTime 1177 MAX-ACCESS read-only 1178 STATUS current 1179 DESCRIPTION 1180 "The time when the last request was received." 1181 ::= { serverClientEntry 4 } 1183 serverClientLastRequestType OBJECT-TYPE 1184 SYNTAX INTEGER { 1185 dhcpdiscover(1), 1186 bootp(2), 1187 dhcprequest(3), 1188 dhcpdecline(4), 1189 unknown(5), 1190 dhcprelease(7), 1191 dhcpinform(8) 1192 } 1193 MAX-ACCESS read-only 1194 STATUS current 1195 DESCRIPTION 1196 "The type of the last request that was received for this 1197 client." 1198 ::= { serverClientEntry 5 } 1200 serverClientLastResponseType OBJECT-TYPE 1201 SYNTAX INTEGER { 1202 bootp(1), 1203 dhcpoffer(2), 1204 unknown(3), 1205 dhcpack(5), 1206 dhcpnak(6) 1207 } 1208 MAX-ACCESS read-only 1209 STATUS current 1210 DESCRIPTION 1211 "The type of the last response that was sent to this client." 1212 ::= { serverClientEntry 6 } 1214 -- serverNotifyObjects: Objects which are used only in 1215 notifications 1217 serverNotifyDuplicateIPAddress OBJECT-TYPE -- /*new*/ 1218 SYNTAX IpAddress 1219 MAX-ACCESS accessible-for-notify 1220 STATUS current 1221 DESCRIPTION 1222 "The IP address which was found to be a duplicate." 1223 ::= { serverNotifyObjects 1 } 1225 serverNotifyMACAddress OBJECT-TYPE -- /*new*/ 1226 SYNTAX PhysicalAddress 1227 MAX-ACCESS accessible-for-notify 1228 STATUS current 1229 DESCRIPTION 1230 "The offending MAC address which caused a duplicate IP 1231 address to be detected." 1232 ::= { serverNotifyObjects 2 } 1234 serverNotifyServer OBJECT-TYPE -- /*new*/ 1235 SYNTAX IpAddress 1236 MAX-ACCESS accessible-for-notify 1237 STATUS current 1238 DESCRIPTION 1239 "The IP Address of a server with which the DHCP server 1240 is attempting to communicate." 1241 ::= { serverNotifyObjects 3 } 1243 serverNotifyServerType OBJECT-TYPE -- /*new*/ 1244 SYNTAX INTEGER { 1245 dns(1), 1246 dhcp(2), 1247 ldap(3) 1248 } 1249 MAX-ACCESS accessible-for-notify 1250 STATUS current 1251 DESCRIPTION 1252 "The type of server with which the DHCP server is attempting 1253 to communicate (corresponds to the serverNotifyServer 1254 object.)" 1255 ::= { serverNotifyObjects 4 } 1257 serverNotifyDuplicateIPAddressDetectedBy OBJECT-TYPE -- /*new*/ 1258 SYNTAX INTEGER {dhcpClient(1), dhcpServer(2)} 1259 MAX-ACCESS accessible-for-notify 1260 STATUS current 1261 DESCRIPTION 1262 "For a serverDuplicateAddress notification, this object 1263 indicates whether the client or server detected the 1264 condition. A DHCP server would typically detect duplicates 1265 by unexpected ICMPECHO replies, while a client would 1266 typically use a gratuitous ARP for the same purpose and 1267 indicate this to the server by a DHCPDECLINE message." 1268 ::= { serverNotifyObjects 5 } 1270 serverNotifyContestedIpAddress OBJECT-TYPE -- /*new*/ 1271 SYNTAX IpAddress 1272 MAX-ACCESS accessible-for-notify 1273 STATUS current 1274 DESCRIPTION 1275 "The IP address for which ownership is claimed by two or 1276 more DHCP servers." 1277 ::= { serverNotifyObjects 6 } 1279 -- Notifications 1281 dhcpServerMIBNotificationPrefix OBJECT IDENTIFIER -- /*new*/ 1282 ::= { dhcpServerMIB 2 } -- /*renamed*/ 1283 dhcpServerMIBNotifications OBJECT IDENTIFIER -- /*new*/ 1284 ::= { dhcpServerMIBNotificationPrefix 0 } 1286 serverFreeAddressLow NOTIFICATION-TYPE -- /*new*/ 1287 OBJECTS { 1288 serverSharedNetworkFreeAddressLowThreshold, 1289 serverSharedNetworkFreeAddressValue, 1290 serverSharedNetworkFreeAddressUnits 1291 } 1292 STATUS current 1293 DESCRIPTION 1294 "This notification signifies that the number of available IP 1295 addresses for a particular shared network has fallen below the 1296 value of serverSharedNetworkFreeAddressLowThreshold for that 1297 shared network." 1298 ::= { dhcpServerMIBNotifications 1 } 1300 serverFreeAddressHigh NOTIFICATION-TYPE -- /*new*/ 1301 OBJECTS { 1302 serverSharedNetworkFreeAddressHighThreshold, 1303 serverSharedNetworkFreeAddressValue, 1304 serverSharedNetworkFreeAddressUnits 1305 } 1306 STATUS current 1307 DESCRIPTION 1308 "This notification signifies that the number of available IP 1309 addresses for a particular shared network has risen above the 1310 value of serverSharedNetworkFreeAddressHighThreshold for that 1311 shared network." 1312 ::= { dhcpServerMIBNotifications 2 } 1314 serverServerStart NOTIFICATION-TYPE -- /*new*/ 1315 OBJECTS { serverNotifyServerType } 1316 STATUS current 1317 DESCRIPTION 1318 "This notification signifies that the server of the specified 1319 type has started on the host from which this notification has 1320 been sent." 1321 ::= { dhcpServerMIBNotifications 3 } 1323 serverServerStop NOTIFICATION-TYPE -- /*new*/ 1324 OBJECTS { serverNotifyServerType } 1325 STATUS current 1326 DESCRIPTION 1327 "This notification signifies that the server of the specified 1328 type has stopped normally on the host from which this 1329 notification has been sent." 1330 ::= { dhcpServerMIBNotifications 4 } 1332 serverDuplicateAddress NOTIFICATION-TYPE -- /*new*/ 1333 OBJECTS { 1334 serverNotifyDuplicateIPAddress, 1335 serverNotifyMACAddress, 1336 serverNotifyDuplicateIPAddressDetectedBy 1337 } 1338 STATUS current 1339 DESCRIPTION 1340 "This notification signifies that a duplicate IP address has 1341 been detected. The DHCP server can detect this condition 1342 through the ping-before-offer mechanism. Alternatively, the 1343 client may have sent a DHCPDECLINE back to the server; this is 1344 assumed to be the result of the client detecting that the 1345 address was in use. In either case, the DHCP server marks the 1346 IP address as unavailable for leasing to clients. The 1347 serverNotifyDuplicateIPAddressDetectedBy object indicates 1348 whether the client or server detected this condition." 1349 ::= { dhcpServerMIBNotifications 7 } 1351 -- Conformance 1353 dhcpServerMIBConformance OBJECT-IDENTITY -- /*renamed*/ 1354 STATUS current 1355 DESCRIPTION 1356 "DHCP Server MIB objects are all defined in this branch." 1357 ::= { dhcpServerMIB 3 } -- /*renamed*/ 1359 dhcpServerMIBCompliances OBJECT IDENTIFIER 1360 ::= { dhcpServerMIBConformance 1 } -- /*renamed*/ 1362 dhcpServerMIBGroups OBJECT IDENTIFIER 1363 ::= { dhcpServerMIBConformance 2 } -- /*renamed*/ 1365 -- Compliance groups 1367 dhcpServerMIBCompliance MODULE-COMPLIANCE 1368 MODULE -- this module 1369 MANDATORY-GROUPS { 1370 serverSystemGroup, 1371 bootpCountersGroup, 1372 dhcpCountersGroup, 1373 bootpStatisticsGroup, 1374 dhcpStatisticsGroup, 1375 serverConfigurationGroup, 1376 serverClientsGroup 1377 } 1378 STATUS current 1379 DESCRIPTION 1380 "Describes the requirements for conformance to the DCHP 1381 Server MIB" 1382 ::= { dhcpServerMIBCompliances 1 } 1384 serverSystemGroup OBJECT-GROUP 1385 OBJECTS { 1386 serverSystemDescr, 1387 serverSystemObjectID 1388 } 1389 STATUS current 1390 DESCRIPTION 1391 "Objects belonging to the serverSystemGroup." 1392 ::= { dhcpServerMIBGroups 1 } 1394 bootpCountersGroup OBJECT-GROUP 1395 OBJECTS { 1396 bootpCountRequests, 1397 bootpCountInvalids, 1398 bootpCountReplies, 1399 bootpCountDroppedUnknownClients, 1400 bootpCountDroppedNotServingSubnet 1401 } 1402 STATUS current 1403 DESCRIPTION 1404 "Objects belonging to the bootpBountersGroup." 1405 ::= { dhcpServerMIBGroups 2 } 1407 dhcpCountersGroup OBJECT-GROUP 1408 OBJECTS { 1409 dhcpCountDiscovers, 1410 dhcpCountRequests, 1411 dhcpCountReleases, 1412 dhcpCountDeclines, 1413 dhcpCountInforms, 1414 dhcpCountInvalids, 1415 dhcpCountOffers, 1416 dhcpCountAcks, 1417 dhcpCountNacks, 1418 dhcpCountDroppedUnknownClient, 1419 dhcpCountDroppedNotServingSubnet 1420 } 1421 STATUS current 1422 DESCRIPTION 1423 "Objects belonging to the dhcpCountersGroup." 1424 ::= { dhcpServerMIBGroups 3 } 1426 bootpStatisticsGroup OBJECT-GROUP 1427 OBJECTS { 1428 bootpStatMinArrivalInterval, 1429 bootpStatMaxArrivalInterval, 1430 bootpStatLastArrivalTime, 1431 bootpStatSunSquaresArrivalTime, 1432 bootpStatMinResponseTime, 1433 bootpStatMaxResponseTime, 1434 bootpStatSumReponseTime, 1435 bootpStatSumSquaresResponseTime 1436 } 1437 STATUS current 1438 DESCRIPTION 1439 "Objects belonging to the bootpStatisticsGroup." 1440 ::= { dhcpServerMIBGroups 4 } 1442 dhcpStatisticsGroup OBJECT-GROUP 1443 OBJECTS { 1444 dhcpStatMinArrivalInterval, 1445 dhcpStatMaxArrivalInterval, 1446 dhcpStatLastArrivalTime, 1447 dhcpStatSumSquaresArrivalTime, 1448 dhcpStatMinResponseTime, 1449 dhcpStatMaxResponseTime, 1450 dhcpStatSumResponseTime, 1451 dhcpStatSumSquaresResponseTime 1452 } 1453 STATUS current 1454 DESCRIPTION 1455 "Objects belonging to the dhcpStatisticsGroup." 1456 ::= { dhcpServerMIBGroups 5 } 1458 serverConfigurationGroup OBJECT-GROUP 1459 OBJECTS { 1460 serverSubnet, 1461 serverSubnetMask, 1462 serverSubnetSharedNet, 1463 serverRangeStart, 1464 serverRangeEnd, 1465 serverRangeSubnet, 1466 serverRangeInUse, 1467 serverRangeOutstandingOffers, 1468 serverAddress, 1469 serverAddressSubnet, 1470 -- serverAddressRange, -- /*duplicate*/ 1471 serverAddressRange, 1472 serverAddressType, 1473 serverAddressTimeRemaining, 1474 serverAddressAllowedProtocol, 1475 serverAddressServedProtocol, 1476 serverAddressHardwareAddress, -- /*renamed*/ 1477 serverAddressClientId, 1478 serverAddressHostName, 1479 serverAddressDomainName 1480 } 1481 STATUS current 1482 DESCRIPTION 1483 "Objects belonging to the serverConfigurationGroup." 1484 ::= { dhcpServerMIBGroups 6 } 1486 serverClientsGroup OBJECT-GROUP 1487 OBJECTS { 1488 serverClientHardwareAddress, -- /*renamed*/ 1489 serverClientSubnet, 1490 serverClientAddress, 1491 serverClientLastRequestTime, 1492 serverClientLastRequestType, 1493 serverClientLastResponseType 1494 } 1495 STATUS current 1496 DESCRIPTION 1497 "Objects belonging to the serverClientsGroup." 1498 ::= { dhcpServerMIBGroups 7 } 1500 serverSharedNetworkObjectsGroup OBJECT-GROUP -- /*new*/ 1501 OBJECTS { 1502 serverSharedNetworkFreeAddrLowThreshold, 1503 serverSharedNetworkFreeAddrHighThreshold, 1504 serverSharedNetworkFreeAddrValue, 1505 serverSharedNetworkFreeAddrUnits 1506 } 1507 STATUS current 1508 DESCRIPTION 1509 "DHCP Server MIB objects used in shared networks." 1510 ::= { dhcpServerMIBGroups 8 } 1512 serverNotifyObjectsGroup OBJECT-GROUP -- /*new*/ 1513 OBJECTS { 1514 serverNotifyDuplicateIPAddress, 1515 serverNotifyMACAddress, 1516 serverNotifyDuplicateIPAddressDetectedBy, 1517 serverNotifyServer, 1518 serverNotifyServerType, 1519 serverNotifyContestedIpAddress 1520 } 1521 STATUS current 1522 DESCRIPTION 1523 "DHCP Server MIB objects used in notifications." 1524 ::= { dhcpServerMIBGroups 9 } 1526 serverNotifyicationsGroup NOTIFICATION-GROUP -- /*new*/ 1527 NOTIFICATIONS { 1528 serverFreeAddressLow, 1529 serverFreeAddressHigh, 1530 serverServerStart, 1531 serverServerStop, 1532 serverDNSQueueTooBig, 1533 serverOtherServerNotResponding, 1534 serverDuplicateAddress, 1535 serverAddressConflict, 1536 serverOtherServerResponding, 1537 serverFailoverConfigMismatch 1538 } 1539 STATUS current 1540 DESCRIPTION 1541 "Notifyications which are implemented by the DHCP Server 1542 agent." 1543 ::= { dhcpServerMIBGroups 10 } 1545 END 1547 4. Intellectual Property 1549 The IETF takes no position regarding the validity or scope of any 1550 intellectual property or other rights that might be claimed to 1551 pertain to the implementation or use of the technology described in 1552 this document or the extent to which any license under such rights 1553 might or might not be available; neither does it represent that it 1554 has made any effort to identify any such rights. Information on the 1555 IETF's procedures with respect to rights in standards-track and 1556 standards-related documentation can be found in BCP-11. 1558 Copies of claims of rights made available for publication and any 1559 assurances of licenses to be made available, or the result of an 1560 attempt made to obtain a general license or permission for the use 1561 of such proprietary rights by implementers or users of this 1562 specification can be obtained from the IETF Secretariat. 1564 The IETF invites any interested party to bring to its attention any 1565 copyrights, patents or patent applications, or other proprietary 1566 rights which may cover technology that may be required to practice 1567 this standard. Please address the information to the IETF Executive 1568 Director. 1570 5. Notes 1572 This section will be removed when this memo is published as an RFC. 1574 5.1. Issues 1576 o Ryan Troll proposed four or five traps that Nathan Lane 1577 enthusiastically supported. If traps are to be included, that 1578 should be done soon. 1580 o what is the best way to reset statistics? 1582 o do we need to reset them individually, as groups, or as a 1583 whole? 1585 o we need a timestamp of when they were reset 1587 o should all invalid packets received be collapsed into a single 1588 counter for each protocol type (BOOTP and DHCP), or broken out by 1589 type of error? 1591 o if counted by error type, what is the set of errors that we 1592 should use? 1594 o perhaps we should develop a common vocabulary (and glossary) for 1595 terms such as "abandoned" so that the objects defined and their 1596 descriptions aren't misinterpreted by implementers. 1598 o do we need to be concerned about the potential size of some of 1599 the configuration data tables? Wouldn't it be better to maintain 1600 counters for things like number of leases assigned than to expect 1601 the management station to calculate the values by reading very 1602 large tables to count the number of leases in that state? 1604 5.2. Changes from Prior Drafts 1606 The "-01" revision removed the Server Identity section from the 1607 proposed MIB, relying on the Application MIB to accomplish the same 1608 result. 1610 The min/max (inter-arrival and response times) were changed to 1611 Unsigned32 so that they could be reset. Sum of inter-arrival and 1612 response times was deleted since the management station can easily 1613 calculate them. The last arrival time objects were added. 1615 The "-03" version incorporated the proposed configuration tables 1616 suggested by Ryan Troll of CMU. The "01" revision of this version 1617 added three elements to the server subnet table, number of 1618 outstanding offers, number of addresses in use, and number of free 1619 addresses, as well as changing subnet address to subnet mask in the 1620 server address, server range, and client address tables. The client 1621 MAC address element of the client address table was separated into a 1622 1-octet hardware type and a 16-octet client hardware address, 1623 causing a renumbering of the elements in this table. Clarifying 1624 text was added to several element descriptions, and limitations on 1625 values, and the reported value when the server did not support the 1626 data element were also specified. 1628 The "-03b" version incorporated an address change for one of the 1629 authors, revisions to standard text required by the IETF, and some 1630 editorial clarifications. 1632 The "-04" version changed the maximum size of the object 1633 serverAddressHostName from 64 to 255 octets, and added clarifying 1634 text to both that object and to serverAddressDomainName regarding 1635 the practical values for the length of both objects. 1637 The "-05" version added a number of traps suggested by Kim Kinnear, 1638 made a number of small renaming and renumbering changes (annotated 1639 in the MIB itself) and restored the Security Considerations text 1640 that had somehow been deleted: several subnetworks that coexist on 1641 one medium. This was done partly because the Address Range concept 1642 did not adequately describe the "scoping" of address pools as is 1643 common with many current server implementations. 1645 6. Acknowledgements 1647 This document is the result of work undertaken the by DHCP working 1648 group. The authors would like to particularly acknowledge the 1649 development team from Carnegie-Mellon University whose work creating 1650 a private MIB for their DHCP server inspired the development of this 1651 proposal. In particular, many thanks to Ryan Troll who provided a 1652 great deal of useful feedback during the development of this MIB. 1654 Thanks to Kim Kinnear, Yannick Koehler, and Nathan Lane for their 1655 review, comments, and contributions. 1657 7. Security Considerations 1659 There are a number of management objects defined in this MIB that 1660 have a MAX-ACCESS clause of read-write and/or read-create. Such 1661 objects may be considered sensitive or vulnerable in some 1662 environments. The support for SET operations in a non-secure 1663 environment without proper protection can have a negative effect on 1664 network operations. 1666 SNMPv1 by itself is not a secure environment. Even if the network 1667 itself is secure (for example by using IPSec, there is no control as 1668 to who on the secure network is allowed to access and GET/SET 1669 (read/change/create/delete) the objects in this MIB. 1671 It is recommended that the implementers consider the security 1672 features as provided by the SNMPv3 framework. Specifically, the use 1673 of the User-based Security Model RFC 2274 [RFC2274] and the View- 1674 based Access Control Model RFC 2275 [RFC2275] is recommended. 1676 It is then a customer/user responsibility to ensure that the SNMP 1677 entity giving access to an instance of this MIB, is properly 1678 configured to give access to the objects only to those principals 1679 (users) that have legitimate rights to indeed GET or SET 1680 (change/create/delete) them. 1682 8. References 1684 [DEN] Directory Enabled Networks Working Group, 1685 http://www.universe.digex.net/~murchiso/den. 1687 [RFC1902] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1688 "Structure of Management Information for Version 2 of the 1689 Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1690 1996. 1692 [RFC1903] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1693 "Textual Conventions for Version 2 of the Simple Network 1694 Management Protocol (SNMPv2)", RFC 1903, January 1996. 1696 [RFC1904] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1697 "Conformance Statements for Version 2 of the Simple Network 1698 Management Protocol (SNMPv2)", RFC 1904, January 1996. 1700 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1701 Requirement Levels", RFC 2119, BCP 14, March 1997. 1703 [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 1704 2131, March 1997. 1706 [RFC2132] Alexander, S. and Droms, R., "DHCP Options and BOOTP 1707 Vendor Extensions", RFC 2132, March 1997. 1709 [RFC2287] Krupczak, C. and Saperia, J., "Definitions of System- 1710 Level Managed Objects for Applications", RFC 2287, February 1711 1998. 1713 9. Editors' Addresses 1715 Richard Barr Hibbs 1716 Pacific Bell 1717 666 Folsom Street, Room 1225 1718 San Francisco, CA 94107-1384 1719 USA 1721 Phone: +1 415-545-1576 1722 Fax: +1 415-543-3539 1723 Email: rbhibbs@pacbell.com 1725 Glenn Waters 1726 Nortel Networks 1727 310-875 Carling Avenue, 1728 Ottawa, Ontario K1S 5P1 1729 Canada 1731 Phone: +1 613-798-4925 1732 Email: gww@nortelnetworks.com 1734 10. Full Copyright Statement 1736 Copyright (C) The Internet Society (1999). All Rights Reserved. 1738 This document and translations of it may be copied and furnished to 1739 others, and derivative works that comment on or otherwise explain it 1740 or assist in its implementation may be prepared, copied, published 1741 and distributed, in whole or in part, without restriction of any 1742 kind, provided that the above copyright notice and this paragraph 1743 are included on all such copies and derivative works. However, this 1744 document itself may not be modified in any way, such as by removing 1745 the copyright notice or references to the Internet Society or other 1746 Internet organizations, except as needed for the purpose of 1747 developing Internet standards in which case the procedures for 1748 copyrights defined in the Internet Standards process must be 1749 followed, or as required to translate it into languages other than 1750 English. 1752 The limited permissions granted above are perpetual and will not be 1753 revoked by the Internet Society or its successors or assigns. 1755 This document and the information contained herein is provided on an 1756 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1757 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1758 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1759 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1760 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.