idnits 2.17.1 draft-ietf-dhc-server-mib-03.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 expiration date. The document expiration date should appear on the first and last page. ** 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 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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 90 instances of too long lines in the document, the longest one being 1 character 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 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 (February 1999) is 9201 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: 'RFC2132' is defined on line 1395, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'DEN' ** Obsolete normative reference: RFC 1902 (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (Obsoleted by RFC 2580) ** Obsolete normative reference: RFC 2274 (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 2275 (Obsoleted by RFC 2575) Summary: 12 errors (**), 0 flaws (~~), 3 warnings (==), 3 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 G. Waters 4 Nortel Networks 5 February 1999 7 Dynamic Host Configuration Protocol (DHCP) Server MIB 9 10 Friday, February 19, 1999, 3:39 PM 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with all 15 provisions of Section 10 of RFC2026. 17 Internet-Drafts are working documents of the Internet Engineering Task 18 Force (IETF), its areas, and its working groups. Note that other 19 groups may also distribute working documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 To learn the current status of any Internet-Draft, please check the 27 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 28 Directories on ds.internic.net (US East Coast), nic.nordu.net 29 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 31 Copyright Notice 33 Copyright (C) The Internet Society (1999). All Rights Reserved. 35 Abstract 37 This memo defines an experimental portion of the Management 38 Information Base (MIB) for use with network management protocols in 39 the Internet Community. In particular, it defines objects used for 40 the management of Dynamic Host Configuration Protocol (DHCP) and 41 Bootstrap Protocol (BOOTP) servers. 43 Table of Contents 45 1. Introduction......................................................2 46 2. Overview..........................................................2 47 2.1. BOOTP and DHCP Counter Groups................................3 48 2.2. BOOTP and DHCP Statistics Group..............................3 49 2.3. Server Configuration Group...................................4 50 2.4. Response Times and ICMP Echo.................................5 51 3. Definitions.......................................................5 52 4. Intellectual Property............................................25 53 5. Notes............................................................26 54 5.1. Issues......................................................26 55 5.2. Changes from Prior Drafts...................................26 56 6. Acknowledgements.................................................27 57 7. Security Considerations..........................................27 58 8. References.......................................................28 59 9. Editors' Addresses...............................................28 60 10. Full Copyright Statement........................................29 62 1. Introduction 64 This memo was produced by the DHCP Working Group and defines a portion 65 of the Management Information Base (MIB) for use with network 66 management protocols in the Internet community. In particular, it 67 describes a set of extensions that DHCP and Bootstrap Protocol (BOOTP) 68 servers implement. Many implementations support both DHCP and BOOTP 69 within a single server and hence this memo describes the MIB for both 70 DHCP and BOOTP servers. 72 This memo is applicable only to IPv4 addresses. 74 This memo does not cover DHCP/BOOTP client nor relay agent extensions: 75 these are possibly the subjects of future investigation. 77 This memo is based on the Internet-standard Network Management 78 Framework as defined by [RFC1902, RFC1903, RFC1904]. 80 Objects defined in this MIB allow access to and control of DHCP Server 81 Software. Servers MAY also provide additional management capabilities 82 through the use of the Applications MIB [RFC2287]. 84 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 85 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 86 document are to be interpreted as described in [RFC2119]. 88 2. Overview 90 In the tradition of the Simple Network Management Protocol (SNMP) the 91 minimum number of objects possible are defined in this MIB, while 92 still providing as rich a set of management information as possible. 93 An object is left out of this MIB when it can be derived from other 94 objects that are provided. Further to the tradition of the SNMP, 95 computationally intense operations are left to the domain of the 96 management station. Thus, this MIB provides a set of objects from 97 which other management information may be derived. 99 The examples provided in the following sections are not meant to be 100 comprehensive, they are merely illustrative of the potential uses of 101 the objects defined by this MIB. 103 2.1. BOOTP and DHCP Counter Groups 105 This section describes some of the management information that may be 106 derived from the objects provided in the counter groups. 108 The total number of valid DHCP packets received by the server is 109 computed as the sum of the dhcpCountDiscovers, dhcpCountRequests, 110 dhcpCountReleases, dhcpCountDeclines, and dhcpCountInforms objects. 111 The total number of valid packets (BOOTP and DHCP) received is 112 computed as the total number of valid DHCP packets plus the value of 113 the bootpCountRequests object. The total number of packets received 114 is computed as the total number of valid packets plus 115 bootpCountInvalids and dhcpCountInvalids. 117 Similar to the received computations, the total number of DHCP packets 118 sent by the server is computed as the sum of the dhcpCountOffers, 119 dhcpCountAcks, and dhcpCountNacks objects. The number of packets 120 (BOOTP and DHCP) sent by the server is computed as the total number of 121 DHCP packets sent plus the value of the bootpCountReplies object. 123 2.2. BOOTP and DHCP Statistics Group 125 This section describes some of the management information that may be 126 derived from the objects provided in the statistics group. 128 Given time 1 (t1) and time 2 (t2) greater than t1, the mean inter- 129 arrival time of valid DHCP messages for the interval t1 to t2 can be 130 computed as (dhcpStatLastArrivalTime at t2 minus 131 dhcpStatLastArrivalTime at t1) divided by (valid DHCP received packet 132 count at t2 minus valid DHCP received packet count at t1). 134 Under the simplifying assumption that the capture of packet counts and 135 times is discontinuous (that is, for the measurement interval the 136 captured data represents the complete set for the server) the variance 137 of the mean may be computed as (dhcpStatSumSquaresArrivalTime at t2 138 less dhcpStatSumSquaresArrivalTime at t1) divided by (valid DHCP 139 received packet count at t2 less valid DHCP received packet count at 140 t1). Standard deviation of the mean is the square root of the 141 variance. 143 Calculation of statistics for message response time is entirely 144 similar to the calculations for inter-arrival time, except that the 145 response time objects are used for the calculations. 147 Calculation of statistics for BOOTP is similar to the calculations for 148 DHCP, except that the similar objects from the bootStatistics group 149 are used instead of the objects from dhcpStatistics group. 151 2.3. Server Configuration Group 153 The server configuration group contains objects that describe the 154 configuration information that is contained in the server. Some of 155 the configuration information is static (e.g.: a statically configured 156 IP address) and some of the configuration is dynamic (e.g.: an 157 assigned DHCP lease). The intent of the server configuration group is 158 to be able to read the server's configuration. Mechanisms outside of 159 the SNMP are currently in use (e.g.: vendor defined solutions) and are 160 being standardized (e.g.: the Directory Enabled Networks [DEN] 161 initiative) to update a server's configuration. 163 The configuration information provides a minimal set of information 164 that most servers should be able to provide. Each row of the 165 serverSubnetTable lists the subnet, the subnet mask, and the subnet 166 that is equivalent to this subnet. Equivalence is defined as more 167 than one subnet being present on the same physical media as some other 168 subnet. 170 The serverRangeTable lists the start and end IP addresses of the 171 ranges and the subnet which the range is a member of. The 172 serverRangeInUse object indicates the amount of the range that is 173 currently in use, either through dynamic allocation or being reserved. 174 The range size can be computed by taking the difference of the 175 serverRangeStart and serverRangeEnd objects. 177 The serverAddressTable provides information about the static and 178 dynamic addresses that the server contains in its configuration. 179 Addresses may be: 181 o Static, in which case they are predefined though the server's 182 configuration. Static addresses may or may not have been 183 previously served by the server; 185 o Dynamic, in which case the server has served the addresses at least 186 once. Leases which have expired MAY appear in the address list; 188 o Configuration-reserved, in which case the address is not available 189 for the server to allocate to a client. A configuration-reserved 190 address is one that has been reserved by the administrator. An 191 example of a configuration-reserved address is an address that is 192 assigned to a client, not through DHCP (e.g.: statically assigned), 193 and the address is within a DHCP range; and, 195 o Server-reserved, in which case the server has taken the address out 196 of use. Examples of server-reserved addresses are those which have 197 been declined (i.e.: through a DHCPDECLINE) by a client or those 198 which have responded to an ICMP echo before they were assigned. 200 The protocol used to allocate the address may be determined from the 201 serverAddressServedProtocol object. This object indicates whether the 202 address has never been served (value of none(1)), or, whether BOOTP or 203 DHCP was used to allocate the address. 205 2.4. Response Times and ICMP Echo 207 According to [RFC2131], servers SHOULD try to determine if an address 208 is in use before assigning it. Some servers choose not to perform 209 this check, letting the client determine for itself if the address is 210 in use. Other servers perform an ICMP echo (Ping) just prior to 211 assigning an address. Servers that perform a Ping before responding 212 to a DHCPDISCOVER should not include in the response time the time 213 from when the Ping was transmitted until the time that either a 214 response was received or that the server timed out waiting for a 215 response. 217 3. Definitions 219 DHCP-SERVER-MIB DEFINITIONS ::= BEGIN 221 IMPORTS 222 Counter64, Counter32, Gauge32, Unsigned32, mib-2, 223 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, IpAddress 224 FROM SNMPv2-SMI 226 TEXTUAL-CONVENTION, RowStatus, DisplayString, TruthValue, 227 DateAndTime 228 FROM SNMPv2-TC 230 MODULE-COMPLIANCE, OBJECT-GROUP 231 FROM SNMPv2-CONF; 233 dhcp OBJECT-IDENTITY 234 STATUS current 235 DESCRIPTION 236 "The dhcp branch in the standard network management framework." 237 ::= { mib-2 ?? } -- IANA will make official assignment 239 dhcpServerMib MODULE-IDENTITY 240 LAST-UPDATED "9902190000Z" 241 ORGANIZATION "IETF DHCP Working Group" 242 CONTACT-INFO 243 " Richard Barr Hibbs 244 Postal: Pacific Bell 245 666 Folsom Street, Room 1225 246 San Francisco, CA 94107-1384 247 USA 248 Tel: +1 415-545-1576 249 Fax: +1 415-543-3539 250 Email: rbhibbs@pacbell.com 252 Glenn Waters 253 Postal: Nortel Networks, Inc. 254 310-875 Carling Avenue 255 Ottawa, Ontario K1S 5P1 256 Canada 257 Tel: +1 613-798-4925 258 Email: gww@nortelnetworks.com " 259 DESCRIPTION 260 "The MIB module for entities implementing the server side of 261 the Bootstrap Protocol (BOOTP) and the Dynamic Host 262 Configuration protocol (DHCP) for Internet Protocol version 4 263 (IPv4)." 264 ::= { dhcp 1 } 266 dhcpServerMibObjects OBJECT-IDENTITY 267 STATUS current 268 DESCRIPTION 269 "DHCP Server MIB objects are all defined in this branch." 270 ::= { dhcpServerMib 1 } 272 serverSystem OBJECT-IDENTITY 273 STATUS current 274 DESCRIPTION 275 "Group of objects that are related to the overall system." 276 ::= { dhcpServerMibObjects 1 } 278 bootpCounters OBJECT-IDENTITY 279 STATUS current 280 DESCRIPTION 281 "Group of objects that count various BOOTP events." 282 ::= { dhcpServerMibObjects 2 } 284 dhcpCounters OBJECT-IDENTITY 285 STATUS current 286 DESCRIPTION 287 "Group of objects that count various DHCP events." 288 ::= { dhcpServerMibObjects 3 } 290 bootpStatistics OBJECT-IDENTITY 291 STATUS current 292 DESCRIPTION 293 "Group of objects that measure various BOOTP statistics." 294 ::= { dhcpServerMibObjects 4 } 296 dhcpStatistics OBJECT-IDENTITY 297 STATUS current 298 DESCRIPTION 299 "Group of objects that measure various DHCP statistics." 300 ::= { dhcpServerMibObjects 5 } 302 serverConfiguration OBJECT-IDENTITY 303 STATUS current 304 DESCRIPTION 305 "Objects that contain pre-configured and dynamic configuration 306 information." 307 ::= { dhcpServerMibObjects 6 } 309 bootpClients OBJECT-IDENTITY 310 STATUS current 311 DESCRIPTION 312 "Objects that map bootp clients to IP addresses." 313 ::= { dhcpServerMibObjects 7 } 315 dhcpClients OBJECT-IDENTITY 316 STATUS current 317 DESCRIPTION 318 "Objects that map DHCP clients to IP addresses." 319 ::= { dhcpServerMibObjects 8 } 321 dhcpServerConformance OBJECT-IDENTITY 322 STATUS current 323 DESCRIPTION 324 "DHCP Server MIB objects are all defined in this branch." 325 ::= { dhcpServerMib 1 } 327 -- Textual conventions defined by this memo 329 DhcpTimeInterval ::= TEXTUAL-CONVENTION 330 STATUS current 331 DESCRIPTION 332 "The number of milli-seconds that has elapsed since some epoch. 333 Systems that cannot measure events to the milli-second 334 resolution SHOULD round this value to the next available 335 resolution that the system supports." 336 SYNTAX Unsigned32 338 -- serverSystem Group 340 serverSystemDescr OBJECT-TYPE 341 SYNTAX DisplayString (SIZE (0..255)) 342 MAX-ACCESS read-only 343 STATUS current 344 DESCRIPTION 345 "A textual description of the server. This value should 346 include the full name and version identification of the server. 347 This string MUST contain only printable NVT ASCII characters." 348 ::= { serverSystem 1 } 350 serverSystemObjectID OBJECT-TYPE 351 SYNTAX OBJECT IDENTIFIER 352 MAX-ACCESS read-only 353 STATUS current 354 DESCRIPTION 355 "The vendor's authoritative identification of the network 356 management subsystem contained in this entity. This value is 357 allocated within the SMI enterprise subtree (1.3.6.1.4.1) and 358 provides an easy and unambiguous means for determining 'what 359 kind of server' is being managed. For example, if vendor 360 'VeryBigServers, Inc.' was assigned the subtree 361 1.3.6.1.4.1.4242, it may assign the identifier 362 1.3.6.1.4.1.4242.1.1 to its `Hercules DHCP Server'." 363 ::= { serverSystem 2 } 365 -- bootpCounters Group 367 bootpCountRequests OBJECT-TYPE 368 SYNTAX Counter32 369 MAX-ACCESS read-only 370 STATUS current 371 DESCRIPTION 372 "The number of packets received that contain a Message Type of 373 1 (BOOTREQUEST) in the first octet and do not contain option 374 number 53 (DHCP Message Type) in the options." 375 ::= { bootpCounters 1 } 377 bootpCountInvalids OBJECT-TYPE 378 SYNTAX Counter32 379 MAX-ACCESS read-only 380 STATUS current 381 DESCRIPTION 382 "The number of packets received that do not contain a Message 383 Type of 1 (BOOTREQUEST) in the first octet or are not valid 384 BOOTP packets (e.g.: too short, invalid field in packet 385 header)." 386 ::= { bootpCounters 2 } 388 bootpCountReplies OBJECT-TYPE 389 SYNTAX Counter32 390 MAX-ACCESS read-only 391 STATUS current 392 DESCRIPTION 393 "The number of packets sent that contain a Message Type of 1 394 (BOOTREQUEST) in the first octet and do not contain option 395 number 53 (DHCP Message Type) in the options." 397 ::= { bootpCounters 3 } 399 bootpCountDroppedUnknownClients OBJECT-TYPE 400 SYNTAX Counter32 401 MAX-ACCESS read-only 402 STATUS current 403 DESCRIPTION 404 "The number of BOOTP packets dropped due to the server not 405 recognizing or not providing service to the hardware address 406 received in the incoming packet." 407 ::= { bootpCounters 4 } 409 bootpCountDroppedNotServingSubnet OBJECT-TYPE 410 SYNTAX Counter32 411 MAX-ACCESS read-only 412 STATUS current 413 DESCRIPTION 414 "The number of BOOTP packets dropped due to the server not 415 being configured or not otherwise able to serve addresses on 416 the subnet from which this message was received." 417 ::= { bootpCounters 5 } 419 -- dhcpCounters Group 421 dhcpCountDiscovers OBJECT-TYPE 422 SYNTAX Counter32 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "The number of DHCPDISCOVER (option 53 with value 1) packets 427 received." 428 ::= { dhcpCounters 1 } 430 dhcpCountRequests OBJECT-TYPE 431 SYNTAX Counter32 432 MAX-ACCESS read-only 433 STATUS current 434 DESCRIPTION 435 "The number of DHCPREQUEST (option 53 with value 3) packets 436 received." 437 ::= { dhcpCounters 2 } 439 dhcpCountReleases OBJECT-TYPE 440 SYNTAX Counter32 441 MAX-ACCESS read-only 442 STATUS current 443 DESCRIPTION 444 "The number of DHCPRELEASE (option 53 with value 7) packets 445 received." 446 ::= { dhcpCounters 3 } 448 dhcpCountDeclines OBJECT-TYPE 449 SYNTAX Counter32 450 MAX-ACCESS read-only 451 STATUS current 452 DESCRIPTION 453 "The number of DHCPDECLINE (option 53 with value 4) packets 454 received." 455 ::= { dhcpCounters 4 } 457 dhcpCountInforms OBJECT-TYPE 458 SYNTAX Counter32 459 MAX-ACCESS read-only 460 STATUS current 461 DESCRIPTION 462 "The number of DHCPINFORM (option 53 with value 8) packets 463 received." 464 ::= { dhcpCounters 5 } 466 dhcpCountInvalids OBJECT-TYPE 467 SYNTAX Counter32 468 MAX-ACCESS read-only 469 STATUS current 470 DESCRIPTION 471 "The number of DHCP packets received whose DHCP message type 472 (i.e.: option number 53) is not understood or handled by the 473 server." 474 ::= { dhcpCounters 6 } 476 dhcpCountOffers OBJECT-TYPE 477 SYNTAX Counter32 478 MAX-ACCESS read-only 479 STATUS current 480 DESCRIPTION 481 "The number of DHCPOFFER (option 53 with value 2) packets 482 sent." 483 ::= { dhcpCounters 7 } 485 dhcpCountAcks OBJECT-TYPE 486 SYNTAX Counter32 487 MAX-ACCESS read-only 488 STATUS current 489 DESCRIPTION 490 "The number of DHCPACK (option 53 with value 5) packets sent." 491 ::= { dhcpCounters 8 } 493 dhcpCountNacks OBJECT-TYPE 494 SYNTAX Counter32 495 MAX-ACCESS read-only 496 STATUS current 497 DESCRIPTION 498 "The number of DHCPNACK (option 53 with value 6) packets sent." 499 ::= { dhcpCounters 9 } 501 dhcpCountDroppedUnknownClient OBJECT-TYPE 502 SYNTAX Counter32 503 MAX-ACCESS read-only 504 STATUS current 505 DESCRIPTION 506 "The number of DHCP packets dropped due to the server not 507 recognizing or not providing service to the client-id and/or 508 hardware address received in the incoming packet." 509 ::= { dhcpCounters 10 } 511 dhcpCountDroppedNotServingSubnet OBJECT-TYPE 512 SYNTAX Counter32 513 MAX-ACCESS read-only 514 STATUS current 515 DESCRIPTION 516 "The number of DHCP packets dropped due to the server not being 517 configured or not otherwise able to serve addresses on the 518 subnet from which this message was received." 519 ::= { dhcpCounters 11 } 521 -- bootpStatistics group 523 bootpStatMinArrivalInterval OBJECT-TYPE 524 SYNTAX DhcpTimeInterval 525 MAX-ACCESS read-write 526 STATUS current 527 DESCRIPTION 528 "The minimum amount of time between receiving two BOOTP 529 messages. A message is received at the server when the server 530 is able to begin processing the message. This typically occurs 531 immediately after the message is read into server memory. If 532 no messages have been received, then this object contains a 533 zero value." 534 ::= { bootpStatistics 1 } 536 bootpStatMaxArrivalInterval OBJECT-TYPE 537 SYNTAX DhcpTimeInterval 538 MAX-ACCESS read-write 539 STATUS current 540 DESCRIPTION 541 "The maximum amount of time between receiving two BOOTP 542 messages. A message is received at the server when the server 543 is able to begin processing the message. This typically occurs 544 immediately after the message is read into server memory. If 545 no messages have been received, then this object contains a 546 zero value." 547 ::= { bootpStatistics 2 } 549 bootpStatLastArrivalTime OBJECT-TYPE 550 SYNTAX DateAndTime 551 MAX-ACCESS read-only 552 STATUS current 553 DESCRIPTION 554 "The date and time that the last valid BOOTP message was 555 received by the server. Invalid messages do not cause this 556 value to change. If valid no messages have been received, then 557 this object contains a date and time that is all zero." 558 ::= { bootpStatistics 3 } 560 bootpStatSumSquaresArrivalTime OBJECT-TYPE 561 SYNTAX Counter64 562 MAX-ACCESS read-only 563 STATUS current 564 DESCRIPTION 565 "The sum of the squared BOOTP packet inter-arrival times in 566 micro-seconds. This value may be used to compute the variance 567 and standard deviation of the BOOTP arrival times. Note that a 568 micro-second resolution of this object requires a clock 569 resolution to the milli-second since the square of a milli- 570 second value produces a value with micro-second resolution." 571 ::= { bootpStatistics 4 } 573 bootpStatMinResponseTime OBJECT-TYPE 574 SYNTAX DhcpTimeInterval 575 MAX-ACCESS read-write 576 STATUS current 577 DESCRIPTION 578 "The smallest time interval measured as the difference between 579 the arrival of a BOOTP message at the server and the successful 580 transmission of the response to that message. A message is 581 received at the server when the server is able to begin 582 processing the message. A message is transmitted after the 583 server has no further use for the message. Note that the 584 operating system may still have the message queued internally. 585 The operating system queue time is not to be considered as part 586 of the response time. Invalid messages do not cause this value 587 to change. If no valid messages have been received, then this 588 object contains a zero value." 589 ::= { bootpStatistics 5 } 591 bootpStatMaxResponseTime OBJECT-TYPE 592 SYNTAX DhcpTimeInterval 593 MAX-ACCESS read-write 594 STATUS current 595 DESCRIPTION 596 "The largest time interval measured as the difference between 597 the arrival of a BOOTP message at the server and the successful 598 transmission of the response to that message. A message is 599 received at the server when the server is able to begin 600 processing the message. A message is transmitted after the 601 server has no further use for the message. Note that the 602 operating system may still have the message queued internally. 604 The operating system queue time is not to be considered as part 605 of the response time. Invalid messages do not cause this value 606 to change. If no valid messages have been received, then this 607 object contains a zero value." 608 ::= { bootpStatistics 6 } 610 bootpStatSumResponseTime OBJECT-TYPE 611 SYNTAX Counter32 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "The sum of the response time intervals in milli-seconds where 616 a response time interval is measured as the difference between 617 the arrival of a BOOTP message at the server and the successful 618 transmission of the response to that message. A message is 619 received at the server when the server is able to begin 620 processing the message. A message is transmitted after the 621 server has no further use for the message. Note that the 622 operating system may still have the message queued internally. 623 The operating system queue time is not to be considered as part 624 of the response time. Invalid messages do not cause this value 625 to change. If no valid messages have been received, then this 626 object contains a zero value." 627 ::= { bootpStatistics 7 } 629 bootpStatSumSquaresResponseTime OBJECT-TYPE 630 SYNTAX Counter64 631 MAX-ACCESS read-only 632 STATUS current 633 DESCRIPTION 634 "The sum of the squared BOOTP packet response times in micro- 635 seconds. This value may be used to compute the variance and 636 standard deviation of the BOOTP response times. Note that a 637 micro-second resolution of this object requires a clock 638 resolution to the milli-second since the square of a milli- 639 second value produces a value with micro-second resolution." 640 ::= { bootpStatistics 8 } 642 -- dhcpStatistics group 644 dhcpStatMinArrivalInterval OBJECT-TYPE 645 SYNTAX DhcpTimeInterval 646 MAX-ACCESS read-write 647 STATUS current 648 DESCRIPTION 649 "The minimum amount of time between receiving two DHCP 650 messages. A message is received at the server when the server 651 is able to begin processing the message. This typically occurs 652 immediately after the message is read into server memory. If 653 no messages have been received, then this object contains a 654 zero value." 656 ::= { dhcpStatistics 1 } 658 dhcpStatMaxArrivalInterval OBJECT-TYPE 659 SYNTAX DhcpTimeInterval 660 MAX-ACCESS read-write 661 STATUS current 662 DESCRIPTION 663 "The maximum amount of time between receiving two DHCP 664 messages. A message is received at the server when the server 665 is able to begin processing the message. This typically occurs 666 immediately after the message is read into server memory. If 667 no messages have been received, then this object contains a 668 zero value." 669 ::= { dhcpStatistics 2 } 671 dhcpStatLastArrivalTime OBJECT-TYPE 672 SYNTAX DateAndTime 673 MAX-ACCESS read-only 674 STATUS current 675 DESCRIPTION 676 "The date and time that the last valid DHCP message was 677 received by the server. Invalid messages do not cause this 678 value to change. If no valid messages have been received, then 679 this object contains a date and time that is all zero." 680 ::= { dhcpStatistics 3 } 682 dhcpStatSumSquaresArrivalTime OBJECT-TYPE 683 SYNTAX Counter64 684 MAX-ACCESS read-only 685 STATUS current 686 DESCRIPTION 687 "The sum of the squared DHCP packet inter-arrival times in 688 micro-seconds. This value may be used to compute the variance 689 and standard deviation of the DHCP arrival times. Note that a 690 micro-second resolution of this object requires a clock 691 resolution to the milli-second since the square of a milli- 692 second value produces a value with micro-second resolution." 693 ::= { dhcpStatistics 4 } 695 dhcpStatMinResponseTime OBJECT-TYPE 696 SYNTAX DhcpTimeInterval 697 MAX-ACCESS read-write 698 STATUS current 699 DESCRIPTION 700 "The smallest time interval measured as the difference between 701 the arrival of a DHCP message at the server and the successful 702 transmission of the response to that message. A message is 703 received at the server when the server is able to begin 704 processing the message. A message is transmitted after the 705 server has no further use for the message. Note that the 706 operating system may still have the message queued internally. 707 The operating system queue time is not to be considered as part 708 of the response time. Invalid messages do not cause this value 709 to change. If no valid messages have been received, then this 710 object contains a zero value." 711 ::= { dhcpStatistics 5 } 713 dhcpStatMaxResponseTime OBJECT-TYPE 714 SYNTAX DhcpTimeInterval 715 MAX-ACCESS read-write 716 STATUS current 717 DESCRIPTION 718 "The largest time interval measured as the difference between 719 the arrival of a DHCP message at the server and the successful 720 transmission of the response to that message. A message is 721 received at the server when the server is able to begin 722 processing the message. A message is transmitted after the 723 server has no further use for the message. Note that the 724 operating system may still have the message queued internally. 725 The operating system queue time is not to be considered as part 726 of the response time. Invalid messages do not cause this value 727 to change. If no valid messages have been received, then this 728 object contains a zero value." 729 ::= { dhcpStatistics 6 } 731 dhcpStatSumResponseTime OBJECT-TYPE 732 SYNTAX Counter32 733 MAX-ACCESS read-only 734 STATUS current 735 DESCRIPTION 736 "The sum of the response time intervals in milli-seconds where 737 a response time interval is measured as the difference between 738 the arrival of a DHCP message at the server and the successful 739 transmission of the response to that message. A message is 740 received at the server when the server is able to begin 741 processing the message. A message is transmitted after the 742 server has no further use for the message. Note that the 743 operating system may still have the message queued internally. 744 The operating system queue time is not to be considered as part 745 of the response time. Invalid messages do not cause this value 746 to change. If no valid messages have been received, then this 747 object contains a zero value." 748 ::= { dhcpStatistics 7 } 750 dhcpStatSumSquaresResponseTime OBJECT-TYPE 751 SYNTAX Counter64 752 MAX-ACCESS read-only 753 STATUS current 754 DESCRIPTION 755 "The sum of the squared DHCP packet response times in micro- 756 seconds. This value may be used to compute the variance and 757 standard deviation of the DHCP response times. Note that a 758 micro-second resolution of this object requires a clock 759 resolution to the milli-second since the square of a milli- 760 second value produces a value with micro-second resolution." 761 ::= { dhcpStatistics 8 } 763 -- serverConfiguration group 765 serverSubnetTable OBJECT-TYPE 766 SYNTAX SEQUENCE OF ServerSubnetEntry 767 MAX-ACCESS not-accessible 768 STATUS current 769 DESCRIPTION 770 "A list of subnets that are configured in this server." 771 ::= { serverConfiguration 1 } 773 serverSubnetEntry OBJECT-TYPE 774 SYNTAX ServerSubnetEntry 775 MAX-ACCESS not-accessible 776 STATUS current 777 DESCRIPTION 778 "A logical row in the serverSubnetTable." 779 INDEX { serverSubnet } 780 ::= { serverSubnetTable 1 } 782 ServerSubnetEntry ::= SEQUENCE { 783 serverSubnet IpAddress, 784 serverSubnetMask IpAddress, 785 serverSubnetSharedNet IpAddress 786 } 788 serverSubnet OBJECT-TYPE 789 SYNTAX IpAddress 790 MAX-ACCESS not-accessible 791 STATUS current 792 DESCRIPTION 793 "The IP address of the subnet." 794 ::= { serverSubnetEntry 1 } 796 serverSubnetMask OBJECT-TYPE 797 SYNTAX IpAddress 798 MAX-ACCESS read-only 799 STATUS current 800 DESCRIPTION 801 "The subnet mask of the subnet. This MUST be the same as the 802 value of DHCP option 1 offered to clients on this subnet." 803 ::= { serverSubnetEntry 2 } 805 serverSubnetSharedNet OBJECT-TYPE 806 SYNTAX IpAddress 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION 810 "The IP address of another subnet that is on the same shared 811 media as this subnet. The address of the shared subnet MUST 812 also be configured on this server. The address 0.0.0.0 should 813 be used if this subnet is not shared." 814 ::= { serverSubnetEntry 3 } 816 serverRangeTable OBJECT-TYPE 817 SYNTAX SEQUENCE OF ServerRangeEntry 818 MAX-ACCESS not-accessible 819 STATUS current 820 DESCRIPTION 821 "A list of ranges that are configured on this server." 822 ::= { serverConfiguration 2 } 824 serverRangeEntry OBJECT-TYPE 825 SYNTAX ServerRangeEntry 826 MAX-ACCESS not-accessible 827 STATUS current 828 DESCRIPTION 829 "A logical row in the serverRangeTable." 830 INDEX { serverRangeStart } 831 ::= { serverRangeTable 1 } 833 ServerRangeEntry ::= SEQUENCE { 834 serverRangeStart IpAddress, 835 serverRangeEnd IpAddress, 836 serverRangeSubnetMask IpAddress, 837 serverRangeInUse Gauge32, 838 serverRangeOutstandingOffers Gauge32 839 } 841 serverRangeStart OBJECT-TYPE 842 SYNTAX IpAddress 843 MAX-ACCESS not-accessible 844 STATUS current 845 DESCRIPTION 846 "The IP address of the first address in the range. The value of 847 range start must be less than or equal to the value of range 848 end." 849 ::= { serverRangeEntry 1 } 851 serverRangeEnd OBJECT-TYPE 852 SYNTAX IpAddress 853 MAX-ACCESS read-only 854 STATUS current 855 DESCRIPTION 856 "The IP address of the last address in the range. The value of 857 range end must be greater than or equal to the value of range 858 start." 859 ::= { serverRangeEntry 2 } 861 serverRangeSubnetMask OBJECT-TYPE 862 SYNTAX IpAddress 863 MAX-ACCESS read-only 864 STATUS current 865 DESCRIPTION 866 "The subnet mask (DHCP option 1) provided to any client offered 867 an address from this range." 868 ::= { serverRangeEntry 3 } 870 serverRangeInUse OBJECT-TYPE 871 SYNTAX Gauge32 872 MAX-ACCESS read-only 873 STATUS current 874 DESCRIPTION 875 "The number of addresses in this range that are currently in 876 use. This number includes those addresses whose lease has not 877 expired and addresses which have been reserved (either by the 878 server or through configuration)." 879 ::= { serverRangeEntry 4 } 881 serverRangeOutstandingOffers OBJECT-TYPE 882 SYNTAX Guage32 883 MAX-ACCESS read-only 884 STATUS current 885 DESCRIPTION 886 "The number of outstanding DHCPOFFER messages for this range is 887 reported with this value. An offer is outstanding if the 888 server has sent a DHCPOFFER message to a client, but has not 889 yet received a DHCPREQUEST message from the client nor has the 890 server-specific timeout (limiting the time in which a client 891 can respond to the offer message) for the offer message 892 expired." 893 ::= { serverRangeEntry 5 } 895 serverAddressTable OBJECT-TYPE 896 SYNTAX SEQUENCE OF ServerAddressEntry 897 MAX-ACCESS not-accessible 898 STATUS current 899 DESCRIPTION 900 "A list of addresses that are known by this server. The list 901 MUST contain addresses that have not expired. The list MUST 902 NOT contain addresses that have never been assigned by the 903 server UNLESS the lease is pre-configured in the server (e.g.: 904 a static lease on a subnet)." 905 ::= { serverConfiguration 3 } 907 serverAddressEntry OBJECT-TYPE 908 SYNTAX ServerAddressEntry 909 MAX-ACCESS not-accessible 910 STATUS current 911 DESCRIPTION 912 "A logical row in the serverAddressTable." 914 INDEX { serverAddress } 915 ::= { serverAddressTable 1 } 917 ServerAddressEntry ::= SEQUENCE { 918 serverAddress IpAddress, 919 serverAddressSubnetMask IpAddress, 920 serverAddressRange IpAddress, 921 serverAddressType INTEGER, 922 serverAddressTimeReminaing Unsigned32, 923 serverAddressAllowedProtocol INTEGER, 924 serverAddressServedProtocol INTEGER, 925 serverAddressMacAddress OCTET STRING, 926 serverAddressClientId OCTET STRING, 927 serverAddressHostName DisplayString, 928 serverAddressDomainName DisplayString 929 } 931 serverAddress OBJECT-TYPE 932 SYNTAX IpAddress 933 MAX-ACCESS not-accessible 934 STATUS current 935 DESCRIPTION 936 "The IP address of the entry." 937 ::= { serverAddressEntry 1 } 939 serverAddressSubnetMask OBJECT-TYPE 940 SYNTAX IpAddress 941 MAX-ACCESS read-only 942 STATUS current 943 DESCRIPTION 944 "The subnet mask (DHCP option 1) provided to the client offered 945 this address. The subnet, resulting from logically ANDing the 946 subnet mask with the entry's IP address, must be configured on 947 this server and appear as a row in the dhcpSubnetTable." 948 ::= { serverAddressEntry 2 } 950 serverAddressRange OBJECT-TYPE 951 SYNTAX IpAddress 952 MAX-ACCESS read-only 953 STATUS current 954 DESCRIPTION 955 "The starting IP address (serverRangeStart object) of the range 956 to which this address belongs. If the address does not fall 957 into one of the configured ranges (e.g.: a statically 958 configured address on a subnet) the range may be 0.0.0.0." 959 ::= { serverAddressEntry 3 } 961 serverAddressType OBJECT-TYPE 962 SYNTAX INTEGER { 963 static(1), 964 dynamic(2), 965 configuration-reserved(3), 966 server-reserved(4) 967 } 968 MAX-ACCESS read-only 969 STATUS current 970 DESCRIPTION 971 "The type of this address." 972 ::= { serverAddressEntry 4 } 974 serverAddressTimeRemaining OBJECT-TYPE 975 SYNTAX Unsigned32 976 MAX-ACCESS read-only 977 STATUS current 978 DESCRIPTION 979 "The number of seconds until the lease expires. A value of 980 4294967295 (i.e.: 0xFFFFFFFF) should be used for leases that 981 have a lease time which is 'infinite' and for BOOTP leases." 982 ::= { serverAddressEntry 5 } 984 serverAddressAllowedProtocol OBJECT-TYPE 985 SYNTAX INTEGER { 986 none(1), 987 bootp(2), 988 dhcp(3), 989 bootp-or-dhcp(4) 990 } 991 MAX-ACCESS read-only 992 STATUS current 993 DESCRIPTION 994 "The type of protocol that is allowed to be used to serve this 995 address. A type of none(1) indicates that the address is not 996 available to be served (e.g.: a reserved address)." 997 ::= { serverAddressEntry 6 } 999 serverAddressServedProtocol OBJECT-TYPE 1000 SYNTAX INTEGER { 1001 none(1), 1002 bootp(2), 1003 dhcp(3) 1004 } 1005 MAX-ACCESS read-only 1006 STATUS current 1007 DESCRIPTION 1008 "The type of protocol that was used when this address was 1009 assigned. This object will have the value of none(1) if the 1010 address has not been served." 1011 ::= { serverAddressEntry 7 } 1013 serverAddressMacAddress OBJECT-TYPE 1014 SYNTAX OCTET STRING (SIZE (0 | 2..17)) 1015 MAX-ACCESS read-only 1016 STATUS current 1017 DESCRIPTION 1018 "The hardware type and hardware address of the client that has 1019 been assigned this lease. The first octet of this object 1020 contains the hardware type from the 'htype' field of the BOOTP 1021 packet and the remaining octets contain the hardware address 1022 from the 'chaddr' field of the BOOTP packet. This object may 1023 be empty if the address has not been previously served." 1024 ::= { serverAddressEntry 8 } 1026 serverAddressClientId OBJECT-TYPE 1027 SYNTAX OCTET STRING (SIZE (0..255)) 1028 MAX-ACCESS read-only 1029 STATUS current 1030 DESCRIPTION 1031 "The client-id of the client that has been assigned this lease. 1032 The client-id is the value specified in option 61 (client-id 1033 option) when the lease was assigned. This object may be empty 1034 if the lease has not been previously assigned or if the client- 1035 id option was not specified when the address was assigned." 1036 ::= { serverAddressEntry 9 } 1038 serverAddressHostName OBJECT-TYPE 1039 SYNTAX DisplayString (SIZE (0..64)) 1040 MAX-ACCESS read-only 1041 STATUS current 1042 DESCRIPTION 1043 "The host name (DHCP option 12) the client is configured with 1044 or if no host name was configured then the host name that the 1045 client supplied when requesting an address." 1046 ::= { serverAddressEntry 10 } 1048 serverAddressDomainName OBJECT-TYPE 1049 SYNTAX DisplayString (SIZE (0..255)) 1050 -- need correct maximum length 1051 MAX-ACCESS read-only 1052 STATUS current 1053 DESCRIPTION 1054 "The domain name (DHCP option 15) assigned to the client." 1055 ::= { serverAddressEntry 11 } 1057 serverClientTable OBJECT-TYPE 1058 SYNTAX SEQUENCE OF ServerClientEntry 1059 MAX-ACCESS not-accessible 1060 STATUS current 1061 DESCRIPTION 1062 "A list of clients that are known by this server. Details about 1063 the clients may be found by indexing into the 1064 serverAddressTable using the serverClientAddress object. This 1065 table is indexed first by the MAC address of the client and 1066 then by the subnet address on which the client resides. The 1067 subnet is included as an index since a MAC address is only 1068 guaranteed to be unique within a subnet (i.e.: a MAC address is 1069 not globally unique)." 1070 ::= { bootpClients 1 } 1072 serverClientEntry OBJECT-TYPE 1073 SYNTAX ServerClientEntry 1074 MAX-ACCESS not-accessible 1075 STATUS current 1076 DESCRIPTION 1077 "A logical row in the serverClientTable. An entry in this table 1078 may be a client that requested an address but was refused 1079 (e.g.: not authorized). Servers MAY track these types of 1080 clients if desired and may choose to remove such client entries 1081 using a server defined algorithm. As an example, a server may 1082 choose to keep client request that does not map to an address 1083 for a one hour time period before removing that entry from this 1084 table." 1085 INDEX { serverClientMacAddress, serverClientSubnet } 1086 ::= { bootpClientTable 1 } 1088 ServerClientEntry ::= SEQUENCE { 1089 serverClientTypeAndMacAddress OCTET STRING, 1090 serverClientSubnetMask IpAddress, 1091 serverClientAddress IpAddress, 1092 serverClientLastRequestTime DateAndTime, 1093 serverClientLastRequestType INTEGER, 1094 serverClientLastResponseType INTEGER 1095 } 1097 serverClientTypeAndMacAddress OBJECT-TYPE 1098 SYNTAX OCTET STRING (SIZE (2..17)) 1099 MAX-ACCESS not-accessible 1100 STATUS current 1101 DESCRIPTION 1102 "The hardware type and hardware address of the client that has 1103 been assigned this lease. The first octet of this object 1104 contains the hardware type from the 'htype' field of the BOOTP 1105 packet and the remaining octets contain the hardware address 1106 from the 'chaddr' field of the BOOTP packet." 1107 ::= { serverClientEntry 1 } 1109 serverClientSubnetMask OBJECT-TYPE 1110 SYNTAX IpAddress 1111 MAX-ACCESS not-accessible 1112 STATUS current 1113 DESCRIPTION 1114 "The subnet mask (DHCP option 1) applied to the client IP." 1115 ::= { serverClientEntry 2 } 1117 serverClientAddress OBJECT-TYPE 1118 SYNTAX IpAddress 1119 MAX-ACCESS read-only 1120 STATUS current 1121 DESCRIPTION 1122 "The IP address of the entry. May be used to index into the 1123 serverAddressTable. May be 0.0.0.0 if an address is not 1124 associated with this client." 1125 ::= { serverClientEntry 3 } 1127 serverClientLastRequestTime OBJECT-TYPE 1128 SYNTAX DateAndTime 1129 MAX-ACCESS read-only 1130 STATUS current 1131 DESCRIPTION 1132 "The time when the last request was received." 1133 ::= { serverClientEntry 4 } 1135 serverClientLastRequestType OBJECT-TYPE 1136 SYNTAX INTEGER { 1137 dhcpdiscover(1), 1138 bootp(2), 1139 dhcprequest(3), 1140 dhcpdecline(4), 1141 unknown(5), 1142 dhcprelease(7), 1143 dhcpinform(8) 1144 } 1145 MAX-ACCESS read-only 1146 STATUS current 1147 DESCRIPTION 1148 "The type of the last request that was received for this 1149 client." 1150 ::= { serverClientEntry 5 } 1152 serverClientLastResponseType OBJECT-TYPE 1153 SYNTAX INTEGER { 1154 bootp(1), 1155 dhcpoffer(2), 1156 unknown(3), 1157 dhcpack(5), 1158 dhcpnak(6) 1159 } 1160 MAX-ACCESS read-only 1161 STATUS current 1162 DESCRIPTION 1163 "The type of the last response that was sent to this client." 1164 ::= { serverClientEntry 6 } 1166 -- Compliance groups 1168 dhcpServerMIBCompliances OBJECT IDENTIFIER ::= { 1169 dhcpServerConformance 1 } 1170 dhcpServerMIBGroups OBJECT IDENTIFIER ::= { 1171 dhcpServerConformance 2 } 1173 dhcpServerMIBCompliance MODULE-COMPLIANCE 1174 STATUS current 1175 DESCRIPTION 1176 "Describes the requirements for conformance to the System 1177 Application MIB" 1178 MODULE -- this module 1179 MANDATORY-GROUPS 1180 { serverSystemGroup, bootpCountersGroup, dhcpCountersGroup, 1181 bootpStatisticsGroup, dhcpStatisticsGroup, 1182 serverConfigurationGroup, serverClientsGroup } 1183 ::= { dhcpServerMIBCompliances 1 } 1185 serverSystemGroup OBJECT-GROUP 1186 OBJECTS { serverSystemDescr, serverSystemObjectID } 1187 STATUS current 1188 DESCRIPTION 1189 "" 1190 ::= { dhcpServerMIBGroups 1 } 1192 bootpCountersGroup OBJECT-GROUP 1193 OBJECTS 1194 { bootpCountRequests, bootpCountInvalids, bootpCountReplies, 1195 bootpCountDroppedUnknownClients, 1196 bootpCountDroppedNotServingSubnet } 1197 STATUS current 1198 DESCRIPTION 1199 "" 1200 ::= { dhcpServerMIBGroups 2 } 1202 dhcpCountersGroup OBJECT-GROUP 1203 OBJECTS 1204 { dhcpCountDiscovers, dhcpCountRequests, dhcpCountReleases, 1205 dhcpCountDeclines, dhcpCountInforms, dhcpCountInvalids, 1206 dhcpCountOffers, dhcpCountAcks, dhcpCountNacks, 1207 dhcpCountDroppedUnknownClint, dhcpCountDroppedNotServingSubnet 1208 } 1209 STATUS current 1210 DESCRIPTION 1211 "" 1212 ::= { dhcpServerMIBGroups 3 } 1214 bootpStatisticsGroup OBJECT-GROUP 1215 OBJECTS 1216 { bootpStatMinArrivalInterval, bootpStatMaxArrivalInterval, 1217 bootpStatLastArrivalTime, bootpStatSunSquaresArrivalTime, 1218 bootpStatMinResponseTime, bootpStatMaxResponseTime, 1219 bootpStatSumReponseTime, bootpStatSumSquaresResponseTime } 1220 STATUS current 1221 DESCRIPTION 1222 "" 1223 ::= { dhcpServerMIBGroups 4 } 1225 dhcpStatisticsGroup OBJECT-GROUP 1226 OBJECTS 1227 { dhcpStatMinArrivalInterval, dhcpStatMaxArrivalInterval, 1228 dhcpStatLastArrivalTime, dhcpStatSumSquaresArrivalTime, 1229 dhcpStatMinResponseTime, dhcpStatMaxResponseTime, 1230 dhcpStatSumResponseTime, dhcpStatSumSquaresResponseTime } 1231 STATUS current 1232 DESCRIPTION 1233 "" 1234 ::= { dhcpServerMIBGroups 5 } 1236 serverConfigurationGroup OBJECT-GROUP 1237 OBJECTS 1238 { serverSubnet, serverSubnetMask, serverSubnetSharedNet, 1239 serverRangeStart, serverRangeEnd, serverRangeSubnet, 1240 serverRangeInUse, serverRangeOutstandingOffers, serverAddress, 1241 serverAddressSubnet, serverAddressRange, serverAddressRange, 1242 serverAddressType, serverAddressTimeRemaining, 1243 serverAddressAllowedProtocol, serverAddressServedProtocol, 1244 serverAddressTypeAndMacAddress, serverAddressClientId, 1245 serverAddressHostName, serverAddressDomainName } 1246 STATUS current 1247 DESCRIPTION 1248 "" 1249 ::= { dhcpServerMIBGroups 6 } 1251 serverClientsGroup OBJECT-GROUP 1252 OBJECTS 1253 { serverClientMacAddress, serverClientSubnet, 1254 serverClientAddress, serverClientLastRequestTime, 1255 serverClientLastRequestType, serverClientLastResponseType } 1256 STATUS current 1257 DESCRIPTION 1258 "" 1259 ::= { dhcpServerMIBGroups 7 } 1261 END 1263 4. Intellectual Property 1265 The IETF takes no position regarding the validity or scope of any 1266 intellectual property or other rights that might be claimed to pertain 1267 to the implementation or use of the technology described in this 1268 document or the extent to which any license under such rights might or 1269 might not be available; neither does it represent that it has made any 1270 effort to identify any such rights. Information on the IETF's 1271 procedures with respect to rights in standards-track and standards- 1272 related documentation can be found in BCP-11. 1274 Copies of claims of rights made available for publication and any 1275 assurances of licenses to be made available, or the result of an 1276 attempt made to obtain a general license or permission for the use of 1277 such proprietary rights by implementers or users of this specification 1278 can be obtained from the IETF Secretariat. 1280 The IETF invites any interested party to bring to its attention any 1281 copyrights, patents or patent applications, or other proprietary 1282 rights which may cover technology that may be required to practice 1283 this standard. Please address the information to the IETF Executive 1284 Director. 1286 5. Notes 1288 This section will be removed when this memo is published as an RFC. 1290 5.1. Issues 1292 o what is the best way to reset statistics? 1294 o do we need to reset them individually, as groups, or as a whole? 1296 o we need a timestamp of when they were reset 1298 o should all invalid packets received be collapsed into a single 1299 counter for each protocol type (BOOTP and DHCP), or broken out by 1300 type of error? 1302 o if counted by error type, what is the set of errors that we should 1303 use? 1305 o perhaps we should develop a common vocabulary (and glossary) for 1306 terms such as "abandoned" so that the objects defined and their 1307 descriptions aren't misinterpreted by implementers. 1309 o do we need to be concerned about the potential size of some of the 1310 configuration data tables? Wouldn't it be better to maintain 1311 counters for things like number of leases assigned than to expect 1312 the management station to calculate the values by reading very 1313 large tables to count the number of leases in that state? 1315 5.2. Changes from Prior Drafts 1317 The "-01" revision removed the Server Identity section from the 1318 proposed MIB, relying on the Application MIB to accomplish the same 1319 result. 1321 The min/max (inter-arrival and response times) were changed to 1322 Unsigned32 so that they could be reset. Sum of inter-arrival and 1323 response times was deleted since the management station can easily 1324 calculate them. The last arrival time objects were added. 1326 The "-03" version incorporated the proposed configuration tables 1327 suggested by Ryan Troll of CMU. The "01" revision of this version 1328 added three elements to the server subnet table, number of outstanding 1329 offers, number of addresses in use, and number of free addresses, as 1330 well as changing subnet address to subnet mask in the server address, 1331 server range, and client address tables. The client MAC address 1332 element of the client address table was separated into a 1-octet 1333 hardware type and a 16-octet client hardware address, causing a 1334 renumbering of the elements in this table. Clarifying text was added 1335 to several element descriptions, and limitations on values, and the 1336 reported value when the server did not support the data element were 1337 also specified. 1339 6. Acknowledgements 1341 This document is the result of work undertaken the by DHCP working 1342 group. The authors would like to particularly acknowledge the 1343 development team from Carnegie-Mellon University whose work creating a 1344 private MIB for their DHCP server inspired the development of this 1345 proposal. In particular, many thanks to Ryan Troll who provided a 1346 great deal of useful feedback during the development of this MIB. 1348 7. Security Considerations 1350 There are a number of management objects defined in this MIB that have 1351 a MAX-ACCESS clause of read-write and/or read-create. Such objects may 1352 be considered sensitive or vulnerable in some environments. The 1353 support for SET operations in a non-secure environment without proper 1354 protection can have a negative effect on network operations. 1356 SNMPv1 by itself is not a secure environment. Even if the network 1357 itself is secure (for example by using IPSec), even then, there is no 1358 control as to who on the secure network is allowed to access and 1359 GET/SET (read/change/create/delete) the objects in this MIB. 1361 It is recommended that the implementers consider the security features 1362 as provided by the SNMPv3 framework. Specifically, the use of the 1363 User-based Security Model RFC 2274 [RFC2274] and the View-based Access 1364 Control Model RFC 2275 [RFC2275] is recommended. 1366 It is then a customer/user responsibility to ensure that the SNMP 1367 entity giving access to an instance of this MIB, is properly 1368 configured to give access to the objects only to those principals 1369 (users) that have legitimate rights to indeed GET or SET 1370 (change/create/delete) them. 1372 8. References 1374 [DEN] Directory Enabled Networks Working Group, 1375 http://www.universe.digex.net/~murchiso/den. 1377 [RFC1902] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1378 "Structure of Management Information for Version 2 of the Simple 1379 Network Management Protocol (SNMPv2)", RFC 1902, January 1996. 1381 [RFC1903] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1382 "Textual Conventions for Version 2 of the Simple Network Management 1383 Protocol (SNMPv2)", RFC 1903, January 1996. 1385 [RFC1904] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1386 "Conformance Statements for Version 2 of the Simple Network 1387 Management Protocol (SNMPv2)", RFC 1904, January 1996. 1389 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1390 Requirement Levels", RFC 2119, BCP 14, March 1997. 1392 [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, 1393 March 1997. 1395 [RFC2132] Alexander, S. and Droms, R., "DHCP Options and BOOTP Vendor 1396 Extensions", RFC 2132, March 1997. 1398 [RFC2274] Blumenthal, U., and B. Wijnen, "User-based Security Model 1399 (USM) for version 3 of the Simple Network Management Protocol 1400 (SNMPv3)", RFC 2274, January 1998. 1402 [RFC2275] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1403 Access Control Model for the Simple Network Management Protocol 1404 (SNMP)", RFC 2275, January 1998. 1406 [RFC2287] Krupczak, C. and Saperia, J., "Definitions of System-Level 1407 Managed Objects for Applications", RFC 2287, February 1998. 1409 9. Editors' Addresses 1411 Richard Barr Hibbs 1412 Pacific Bell 1413 666 Folsom Street, Room 1225 1414 San Francisco, CA 94107-1384 1415 USA 1417 Phone: +1 415-545-1576 1418 Fax: +1 415-543-3539 1419 Email: rbhibbs@pacbell.com 1421 Glenn Waters 1422 Nortel Networks 1423 310-875 Carling Avenue, 1424 Ottawa, Ontario K1S 5P1 1425 Canada 1427 Phone: +1 613-798-4925 1428 Email: gww@nortelnetworks.com 1430 10. Full Copyright Statement 1432 Copyright (C) The Internet Society (1999). All Rights Reserved. 1434 This document and translations of it may be copied and furnished to 1435 others, and derivative works that comment on or otherwise explain it 1436 or assist in its implementation may be prepared, copied, published and 1437 distributed, in whole or in part, without restriction of any kind, 1438 provided that the above copyright notice and this paragraph are 1439 included on all such copies and derivative works. However, this 1440 document itself may not be modified in any way, such as by removing 1441 the copyright notice or references to the Internet Society or other 1442 Internet organizations, except as needed for the purpose of developing 1443 Internet standards in which case the procedures for copyrights defined 1444 in the Internet Standards process must be followed, or as required to 1445 translate it into languages other than English. 1447 The limited permissions granted above are perpetual and will not be 1448 revoked by the Internet Society or its successors or assigns. 1450 This document and the information contained herein is provided on an 1451 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1452 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 1453 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 1454 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1455 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.