draft-ietf-dhc-server-mib-05.txt   draft-ietf-dhc-server-mib-06.txt 
Network Working Group R. B. Hibbs Network Working Group Barr Hibbs
INTERNET-DRAFT UltraDNS Corp. INTERNET-DRAFT (no affiliation)
Category: Standards Track G. Waters Category: Standards Track Glenn Waters
Nortel Networks Nortel Networks
November 2000 February 2002
Dynamic Host Configuration Protocol (DHCP) Server MIB Dynamic Host Configuration Protocol (DHCP) Server MIB
<draft-ietf-dhc-server-mib-05.txt> <draft-ietf-dhc-server-mib-06.txt>
Monday, November 13, 2000, 3:50 PM Saved Thursday, February 14, 2002, 11:26:01 AM
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six months
months and may be updated, replaced, or obsoleted by other documents and may be updated, replaced, or obsoleted by other documents at any
at any time. It is inappropriate to use Internet-Drafts as time. It is inappropriate to use Internet-Drafts as reference
reference material or to cite them other than as "work in progress. material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/1id-abstracts.html.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
"
To learn the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ds.internic.net (US East Coast), nic.nordu.net
(Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific
Rim).
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) 2002, The Internet Society. All Rights Reserved.
Abstract Abstract
This memo defines an experimental portion of the Management This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management protocols in Information Base (MIB) for use with network management protocols in
the Internet Community. In particular, it defines objects used for the Internet Community. In particular, it defines objects used for
the management of Dynamic Host Configuration Protocol (DHCP) and the management of Dynamic Host Configuration Protocol (DHCP) and
Bootstrap Protocol (BOOTP) servers. Bootstrap Protocol (BOOTP) servers.
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 1]
Table of Contents Table of Contents
1. Introduction......................................................2 1. Introduction...................................................2
2. Overview..........................................................2 2. Overview.......................................................3
2.1. BOOTP and DHCP Counter Groups.................................3 2.1. Relationship to Other MIBs.................................4
2.2. BOOTP and DHCP Statistics Group...............................3 2.1.1. DHCP MIB Extensions...................................4
2.3. Server Configuration Group....................................3 2.1.2. Host System MIB Extensions............................4
2.4. Response Times and ICMP Echo..................................5 2.1.3. DHCPv6 Server MIB Extensions..........................4
3. Definitions.......................................................5 2.1.4. DHCP Client MIB Extensions............................5
4. Intellectual Property............................................31 2.1.5. DHCP Relay Agent MIB Extensions.......................5
5. Notes............................................................31 2.2. Textual Conventions Introduced in this MIB.................5
5.1. Issues.......................................................31 2.2.1. DhcpTimeInterval......................................5
5.2. Changes from Prior Drafts....................................32 2.2.2. HardwareAddressType...................................5
6. Acknowledgements.................................................33 2.2.3. HardwareAddressLength.................................5
7. Security Considerations..........................................33 2.2.4. MacAddress............................................5
8. References.......................................................33 2.2.5. PhysicalAddress.......................................5
9. Editors' Addresses...............................................34 2.2.6. DhcpLabel.............................................6
10. Full Copyright Statement........................................34 2.3. BOOTP and DHCP Counter Groups..............................6
2.4. BOOTP and DHCP Optional Statistics Group...................6
2.5. Response Times and ICMP Echo...............................8
3. Definitions....................................................8
4. Intellectual Property.........................................39
5. Notes.........................................................40
5.1. Issues....................................................40
5.2. Changes from Prior Drafts.................................41
6. Acknowledgements..............................................42
7. Security Considerations.......................................42
8. References....................................................43
9. Editors' Addresses............................................44
10. Full Copyright Statement.....................................44
1. Introduction 1. Introduction
This memo was produced by the DHCP Working Group and defines a This memo was produced by the DHCP Working Group and defines a
portion of the Management Information Base (MIB) for use with portion of the Management Information Base (MIB) for use with network
network management protocols in the Internet community. In management protocols in the Internet community. In particular, it
particular, it describes a set of extensions that DHCP and Bootstrap describes a set of extensions that DHCP and Bootstrap Protocol
Protocol (BOOTP) servers implement. Many implementations support (BOOTP) servers implement. Many implementations support both DHCP
both DHCP and BOOTP within a single server and hence this memo and BOOTP within a single server and hence this memo describes the
describes the MIB for both DHCP and BOOTP servers. MIB for both DHCP and BOOTP servers.
This memo does not cover DHCP/BOOTP client nor relay agent MIB This memo does not cover DHCP/BOOTP client nor relay agent MIB
extensions: these are possibly the subjects of future investigation. extensions: these are possibly the subjects of future investigation
[see discussion in section 2.1.] Also excluded from this MIB
extension in the interest of simplicity are DHCP Dynamic DNS
Updating, Failover, Authentication, and Load Balancing: these
functions and features could be subjects of future MIB extensions.
Provision is also made for Standards-Track additions to the DHCP
Message Type (option 61.)
This memo is based on the Internet-standard Network Management This memo is based on the Internet-standard Network Management
Framework as defined by documents [RFC1902, RFC1903, RFC1904]. Framework as defined by documents [RFC2578, RFC2579, RFC2580].
Objects defined in this MIB allow access to and control of DHCP Objects defined in this MIB allow access to and control of DHCP
Server Software. Servers MAY also provide additional management Server Software. Servers MAY also provide additional management
capabilities through the use of the Applications MIB [RFC2287]. capabilities through the use of the Applications MIB [RFC2287].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST," "MUST NOT," "REQUIRED," "SHALL," "SHALL NOT,"
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD," "SHOULD NOT," "RECOMMENDED," "MAY," and "OPTIONAL" in this
this document are to be interpreted as described in document document are to be interpreted as described in document [RFC2119].
[RFC2119].
2. Overview 2. Overview
In the tradition of the Simple Network Management Protocol (SNMP) In the tradition of the Simple Network Management Protocol (SNMP) the
the minimum number of objects possible are defined in this MIB, minimum number of objects possible are defined in this MIB, while
while still providing as rich a set of management information as still providing as rich a set of management information as possible.
possible. An object is left out of this MIB when it can be derived An object is left out of this MIB when it can be derived from other
from other objects that are provided. Further to the tradition of objects that are provided. Further to the tradition of the SNMP,
the SNMP, computationally intense operations are left to the domain computationally intense operations are left to the domain of the
of the management station. Thus, this MIB provides a set of objects management station. Thus, this MIB provides a set of objects from
from which other management information may be derived. which other management information may be derived.
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 2] The examples provided in sections 2.3 through 2.5 are not meant to be
The examples provided in the following sections are not meant to be comprehensive but are illustrative of the potential uses of the
comprehensive, they are merely illustrative of the potential uses of objects defined by this MIB.
the objects defined by this MIB.
2.1. BOOTP and DHCP Counter Groups 2.1. Relationship to Other MIBs
This section describes some of the management information that may 2.1.1. DHCP MIB Extensions
be derived from the objects provided in the counter groups.
The DHCP MIB extensions will the "dhcp" branch of the standard MIB-2
tree, as illustrated by the following diagram:
+-------+
| MIB-2 |
+---+---+
|
|
+---+---+
| dhcp |
+---+---+
|
|
+---------------+------+---------+---------------------+
| | | |
+-----+-----+ +-----+----+ +-------+--------+ +------+------+
| dhcp-v4 | | dhcp-v4 | | dhcp-v4 | | dhcp-v6 MIB |
|Server MIB | |Client MIB| |Relay Agent MIB | | Extensions |
|(this memo)| | (future) | | (future work) | | (future) |
+-----------+ +----------+ +----------------+ +-------------+
The MIBs will share a common branching point, but are independently
defined.
2.1.2. Host System MIB Extensions
The Host System MIB [RFC1123] provides for information, command, and
control of the host computer system on which a DHCP server resides.
The DHCP Server MIB specifically does not include any objects that
may be accessible using the Host System MIB.
2.1.3. DHCPv6 Server MIB Extensions
When this set of MIB extensions is developed, it will share a common
branch point in the MIB tree with the other DHCP MIB Extensions.
2.1.4. DHCP Client MIB Extensions
If this set of MIB extensions is ever developed, it will share a
common branch point in the MIB tree with the other DHCP MIB
Extensions, and will use many of the same textual conventions.
2.1.5. DHCP Relay Agent MIB Extensions
If this set of MIB extensions is ever developed, it will share a
common branch point in the MIB tree with the other DHCP MIB
Extensions, and will use many of the same textual conventions.
2.2. Textual Conventions Introduced in this MIB
Severaal conceptual data types have been introduced as textual
conventions in this DHCP MIB document. These additions will
facilitate the common understanding of information used by the DHCP
server. No changes to the SMI or the SNMP are necessary to support
these conventions.
2.2.1. DhcpTimeInterval
This data type measures time intervals since the beginning of some
epoch in milliseconds.
2.2.2. HardwareAddressType
This data type contains the type of hardware address represented by
MacAddress, as defined for ARP messages.
2.2.3. HardwareAddressLength
The length in octets of MacAddress is contained in this type.
2.2.4. MacAddress
The actual layer 1 hardware address is contained in this data type.
2.2.5. PhysicalAddress
This data type combines the hardware type octet with the length and
hardware (NIC or MAC) address to produce a unique address type.
2.2.6. DhcpLabel
This data type contains labels used as identifiers by DHCP servers.
2.3. BOOTP and DHCP Counter Groups
This section describes some of the management information that may be
derived from the objects provided in the counter groups.
The total number of valid DHCP packets received by the server is The total number of valid DHCP packets received by the server is
computed as the sum of the dhcpCountDiscovers, dhcpCountRequests, computed as the sum of the dhcpCountDiscovers, dhcpCountRequests,
dhcpCountReleases, dhcpCountDeclines, and dhcpCountInforms objects. dhcpCountReleases, dhcpCountDeclines, dhcpCountInforms and
The total number of valid packets (BOOTP and DHCP) received is dhcpCountLeaseQueries objects. The total number of valid packets
computed as the total number of valid DHCP packets plus the value of (BOOTP and DHCP) received is computed as the total number of valid
the bootpCountRequests object. The total number of packets received DHCP packets plus the value of the bootpCountRequests object. The
is computed as the total number of valid packets plus total number of packets received is computed as the total number of
bootpCountInvalids and dhcpCountInvalids. valid packets plus the sum of bootpCountInvalids and
dhcpCountInvalids.
Similar to the received computations, the total number of DHCP Similar to the received computations, the total number of DHCP
packets sent by the server is computed as the sum of the packets sent by the server is computed as the sum of the
dhcpCountOffers, dhcpCountAcks, and dhcpCountNacks objects. The dhcpCountOffers, dhcpCountAcks, dhcpCountNacks,
number of packets (BOOTP and DHCP) sent by the server is computed as dhcpCountForcedRenews, dhcpCountKnowns, and dhcpCountUnknowns
the total number of DHCP packets sent plus the value of the objects. The number of packets (BOOTP and DHCP) sent by the server
bootpCountReplies object. is computed as the total number of DHCP packets sent plus the value
of the bootpCountReplies object.
2.2. BOOTP and DHCP Statistics Group 2.4. BOOTP and DHCP Optional Statistics Group
This section describes some of the management information that may This section describes some of the management information that may be
be derived from the objects provided in the statistics group. derived from the objects provided in the optional statistics group.
Given time 1 (t1) and time 2 (t2) greater than t1, the mean inter- Given time 1 (t1) and time 2 (t2) greater than t1, the mean inter-
arrival time of valid DHCP messages for the interval t1 to t2 can be arrival time of valid DHCP messages for the interval t1 to t2 can be
computed as (dhcpStatLastArrivalTime at t2 minus computed as (dhcpStatLastArrivalTime at t2 minus
dhcpStatLastArrivalTime at t1) divided by (valid DHCP received dhcpStatLastArrivalTime at t1) divided by (valid DHCP received packet
packet count at t2 minus valid DHCP received packet count at t1). count at t2 minus valid DHCP received packet count at t1).
Under the simplifying assumption that the capture of packet counts Under the simplifying assumption that the capture of packet counts
and times is discontinuous (that is, for the measurement interval and times is discontinuous (that is, for the measurement interval the
the captured data represents the complete set for the server) the captured data represents the complete set for the server) the
variance of the mean may be computed as variance of the mean may be computed as
(dhcpStatSumSquaresArrivalTime at t2 less (dhcpStatSumSquaresArrivalTime at t2 less
dhcpStatSumSquaresArrivalTime at t1) divided by (valid DHCP received dhcpStatSumSquaresArrivalTime at t1) divided by (valid DHCP received
packet count at t2 less valid DHCP received packet count at t1). packet count at t2 less valid DHCP received packet count at t1).
Standard deviation of the mean is the square root of the variance. Standard deviation of the mean is the square root of the variance.
Calculation of statistics for message response time is entirely Calculation of statistics for message response time is entirely
similar to the calculations for inter-arrival time, except that the similar to the calculations for inter-arrival time, except that the
response time objects are used for the calculations. response time objects are used for the calculations.
Calculation of statistics for BOOTP is similar to the calculations Calculation of statistics for BOOTP is similar to the calculations
for DHCP, except that the similar objects from the bootStatistics for DHCP, except that the similar objects from the
group are used instead of the objects from dhcpStatistics group. bootpOptionalStatistics group are used instead of the objects from
dhcpOptionalStatistics group.server Configuration Group
2.3. Server Configuration Group
The server configuration group contains objects that describe the The server configuration group contains objects that describe the
configuration information that is contained in the server. Some of configuration information that is contained in the server. Some of
the configuration information is static (e.g., a statically
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 3]
the configuration information is static (e.g.: a statically
configured IP address) and some of the configuration is dynamic configured IP address) and some of the configuration is dynamic
(e.g.: an assigned DHCP lease). The intent of the server (e.g., an assigned DHCP lease). The intent of the server
configuration group is to be able to read the server's configuration group is to be able to read the server's configuration.
configuration. Mechanisms outside of the SNMP are currently in use Mechanisms outside of the SNMP are currently in use (e.g., vendor
(e.g.: vendor defined solutions) and are being standardized (e.g.: defined solutions) and are being standardized (e.g., the Directory
the Directory Enabled Networks [DEN] initiative) to update a Enabled Networks [DEN] initiative) to update a server's
server's configuration. configuration.
The configuration information provides a minimal set of information The configuration information defines a minimal set of information
that most servers should be able to provide. Each row of the that most servers should be able to provide. Each row of the
serverSubnetTable lists the subnet, the subnet mask, and the subnet serverSubnetTable lists the subnet, the subnet mask, and the subnet
that is equivalent to this subnet. Equivalence is defined as more that is equivalent to this subnet. Equivalence is defined as more
than one subnet being present on the same physical media as some than one subnet being present on the same network segment as some
other subnet. other subnet.
The serverRangeTable lists the start and end IP addresses of the The serverRangeTable lists the start and end IP addresses of the
ranges and the subnet which the range is a member of. The ranges and the subnet of which the range is a member. The
serverRangeInUse object indicates the amount of the range that is serverRangeInUse object indicates the amount of the range that is
currently in use, either through dynamic allocation or being currently in use, either through dynamic allocation or being
reserved. The range size can be computed by taking the difference reserved. The range size can be computed by taking the difference of
of the serverRangeStart and serverRangeEnd objects. the serverRangeStart and serverRangeEnd objects.
The serverAddressTable provides information about the static and The serverAddressTable provides information about the static and
dynamic addresses that the server contains in its configuration. dynamic addresses that the server contains in its configuration.
Addresses may be: Addresses may be:
o Static, in which case they are predefined though the server's o Static, in which case they are predefined though the server's
configuration. Static addresses may or may not have been configuration. Static addresses may or may not have been
previously served by the server; previously served by the server;
o Dynamic, in which case the server has served the addresses at o Dynamic, in which case the server has served the addresses and
least once. Leases which have expired MAY appear in the address it is currently in active use by a host;
list;
o Expired, in which case the server had previously assigned for
which the lease time has expired, but is retained by the server
for possible future use by the same client;
o Configuration-reserved, in which case the address is not o Configuration-reserved, in which case the address is not
available for the server to allocate to a client. A available for the server to allocate to a client. A
configuration-reserved address is one that has been reserved by configuration-reserved address is one that has been reserved by
the administrator. An example of a configuration-reserved address the administrator. An example of a configuration-reserved
is an address that is assigned to a client, not through DHCP address is an address that is assigned to a client, not through
(e.g.: statically assigned), and the address is within a DHCP DHCP (e.g., statically assigned), and the address is within a
range; and, DHCP range; and
o Server-reserved, in which case the server has taken the address o Server-reserved, in which case the server has taken the address
out of use. Examples of server-reserved addresses are those out of use. Examples of server-reserved addresses are those
which have been declined (i.e.: through a DHCPDECLINE) by a which have been declined (i.e., through a DHCPDECLINE) by a
client or those which have responded to an ICMP echo before they client or those which have responded to an ICMP echo before they
were assigned. were assigned.
The protocol used to allocate the address may be determined from the The protocol used to allocate the address may be determined from the
serverAddressServedProtocol object. This object indicates whether serverAddressServedProtocol object. This object indicates whether
the address has never been served (value of none(1)), or, whether the address has never been served, or whether BOOTP or DHCP was used
BOOTP or DHCP was used to allocate the address. to allocate the address.
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 4] 2.5. Response Times and ICMP Echo
2.4. Response Times and ICMP Echo
According to [RFC2131], servers SHOULD try to determine if an According to [RFC2131], servers SHOULD try to determine if an address
address is in use before assigning it. Some servers choose not to is in use before assigning it. Some servers choose not to perform
perform this check, letting the client determine for itself if the this check, letting the client determine for itself if the address is
address is in use. Other servers perform an ICMP echo (Ping) just in use. Other servers perform an ICMP echo (Ping) just prior to
prior to assigning an address. Servers that perform a Ping before assigning an address. Servers that perform a Ping before responding
responding to a DHCPDISCOVER should not include in the response time to a DHCPDISCOVER should not include in the response time the time
the time from when the Ping was transmitted until the time that from when the Ping was transmitted until the time that either a
either a response was received or that the server timed out waiting response was received or that the server timed out waiting for a
for a response. response.
3. Definitions 3. Definitions
-- definitions for a DHCP (Dynamic Host Configuration Protocol) -- definitions for a DHCP (Dynamic Host Configuration Protocol)
server server
DHCP-SERVER-MIB DEFINITIONS ::= BEGIN DHCP-SERVER-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Counter64, Counter32, Gauge32, Unsigned32, mib-2, Counter64, Counter32, Gauge32, Unsigned32, mib-2, MODULE-IDENTITY,
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, IpAddress OBJECT-TYPE, OBJECT-IDENTITY, IpAddress
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, DisplayString, TruthValue, TEXTUAL-CONVENTION, RowStatus, DisplayString, TruthValue,
DateAndTime DateAndTime FROM SNMPv2-TC
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP # MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
/*modified*/
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
dhcp OBJECT-IDENTITY dhcp OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The dhcp branch in the standard network management "The dhcp branch in the standard network management framework."
framework."
::= { mib-2 99 } -- IANA will make official assignment ::= { mib-2 99 } -- IANA will make official assignment
dhcpServerMIB MODULE-IDENTITY # /*renamed*/ serverMIB MODULE-IDENTITY
LAST-UPDATED "9910060000Z" LAST-UPDATED "2002-02-14 11:26"
ORGANIZATION "IETF DHCP Working Group" ORGANIZATION "IETF DHC Working Group"
CONTACT-INFO CONTACT-INFO
" Richard Barr Hibbs " Richard Barr Hibbs
Postal: UltraDNS Corporation Postal: 952 Sanchex Street
800 North San Mateo Drive San Francisco, California 94114-3362
San Mateo, CA 94401-2261
USA USA
Tel: +1 650-227-2678 Tel: +1-(415)-648-3920
Fax: +1 650-227-2662 Fax: +1-(415)-648-9017
Email: rbhibbs@ultraDNS.com E-mail: rbhibbs@pacbell.net
Glenn Waters Glenn Waters
Postal: Nortel Networks, Inc. Postal: Nortel Networks, Inc.
310-875 Carling Avenue 310-875 Carling Avenue
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 5]
Ottawa, Ontario K1S 5P1 Ottawa, Ontario K1S 5P1
Canada Canada
Tel: +1 613-765-0249 Tel: +1-(613)-798-4925
Email: gww@nortelnetworks.com" E-mail: gww@NortelNetworks.com "
DESCRIPTION DESCRIPTION
"The MIB module for entities implementing the server side of "The MIB module for entities implementing the server side of
the the Bootstrap Protocol (BOOTP) and the Dynamic Host
Bootstrap Protocol (BOOTP) and the Dynamic Host Configuration Configuration protocol (DHCP) for Internet Protocol version
protocol (DHCP) for Internet Protocol version 4(IPv4). This 4(IPv4). This MIB does not include support for Dynamic DNS
MIB (DDNS) updating nor for the DHCP Failover Protocol."
does not include support for Dynamic DNS (DDNS) updating nor
for
the DHCP Failover Protocol."
::= { dhcp 1 } ::= { dhcp 1 }
dhcpServerMIBObjects OBJECT-IDENTITY serverMIBObjects OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"DHCP Server MIB objects are all defined in this branch." "DHCP Server MIB objects are all defined in this branch."
::= { dhcpServerMIB 1 } ::= { serverMIB 1 }
serverSystem OBJECT-IDENTITY serverSystem OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Group of objects that are related to the overall system." "Group of objects that are related to the overall system."
::= { dhcpServerMIBObjects 1 } ::= { serverMIBObjects 1 }
bootpCounters OBJECT-IDENTITY bootpCounters OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Group of objects that count various BOOTP events." "Group of objects that count various BOOTP events."
::= { dhcpServerMIBObjects 2 } ::= { serverMIBObjects 2 }
dhcpCounters OBJECT-IDENTITY dhcpCounters OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Group of objects that count various DHCP events." "Group of objects that count various DHCP events."
::= { dhcpServerMIBObjects 3 } ::= { serverMIBObjects 3 }
bootpStatistics OBJECT-IDENTITY bootpOptionalStatistics OBJECT-IDENTITY -- /*renamed*/
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Group of objects that measure various BOOTP statistics." "Group of objects that measure various BOOTP statistics."
::= { dhcpServerMIBObjects 4 } ::= { serverMIBObjects 4 }
dhcpStatistics OBJECT-IDENTITY dhcpOptionalStatistics OBJECT-IDENTITY -- /*renamed*/
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Group of objects that measure various DHCP statistics." "Group of objects that measure various DHCP statistics."
::= { dhcpServerMIBObjects 5 } ::= { serverMIBObjects 5 }
serverConfiguration OBJECT-IDENTITY serverConfiguration OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects that contain pre-configured and dynamic "Objects that contain pre-configured and dynamic configuration
configuration
information." information."
::= { serverMIBObjects 6 }
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 6] bootpClients OBJECT-IDENTITY
::= { dhcpServerMIBObjects 6 } STATUS current
DESCRIPTION
"Objects that map bootp clients to IP addresses."
::= { serverMIBObjects 7 }
clientGroup OBJECT-IDENTITY dhcpClients OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects that map DHCP and BOOTP clients to IP addresses." "Objects that map DHCP clients to IP addresses."
::= { dhcpServerMIBObjects 7 } ::= { serverMIBObjects 8 }
-- Textual conventions defined by this memo -- Textual conventions defined by this memo
DhcpTimeInterval ::= TEXTUAL-CONVENTION DhcpTimeInterval ::= TEXTUAL-CONVENTION
SYNTAX Unsigned32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of milli-seconds that has elapsed since some "The number of milliseconds that has elapsed since some epoch.
epoch. Systems that cannot measure events to the millisecond
Systems that cannot measure events to the milli-second
resolution SHOULD round this value to the next available resolution SHOULD round this value to the next available
resolution that the system supports." resolution that the system supports."
SYNTAX Unsigned32
HardwareAddressType ::= TEXTUAL-CONVENTION
SYNTAX OCTET
STATUS current
REFERENCE "RFC 2131"
DESCRIPTION
"The value of the hardware type field, as used in ARP messages
(e.g., 1 for Ethernet, 6 for token ring). IANA maintains the
list of registered numbers for this field."
HardwareAddressLength ::= TEXTUAL-CONVENTION
SYNTAX OCTET
STATUS current
REFERENCE "RFC 2131"
DESCRIPTION
"The length in octets of the hardware address field (e.g., 6
for Ethernet). IANA maintains the list of registered numbers
for this field."
MacAddress ::= TEXTUAL-CONVENTION
SYNTAX OCTET STRING (SIZE (1..16))
DISPLAY-HINT "t,l,xx[:xx...]"
STATUS current
REFERENCE "RFC 2131"
DESCRIPTION
"A Layer 1 address, the hardware address of the MAC (Media
Adapter Card) interface. The address length is fixed for a
given hardware address type, but varies by type."
PhysicalAddress ::= TEXTUAL-CONVENTION PhysicalAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "t,xx[:xx...]" SYNTAX SEQUENCE OF {
HardwareAddressType,
HardwareAddressLength,
MacAddress
}
DISPLAY-HINT "t,l,xx[:xx...]"
STATUS current STATUS current
REFERENCE "RFC 2131" REFERENCE "RFC 2131"
DESCRIPTION DESCRIPTION
"A harware type and hardware address. This object is "A Layer 1 address which includes the hardware type space as
encoded as well as the usual MAC address. This encoding is intended to
<type ><address> mirror the representation of physical addresses in DHCP."
where
<type> is the value of the hardware type space
field, as used in ARP (e.g., 1 for Ethernet,
6 for token ring). IANA maintains the list of
registered numbers for this field. The value for
this field comes from the 'htype' field in the
BOOTP
packet header.
<address> is the hardware address of the MAC (Media
Adapter Card) interface. The value for this field
comes from the 'chaddr' field in the BOOTP packet
header."
SYNTAX OCTET STRING (SIZE (0 | 2..17))
DhcpLabel ::= TEXTUAL-CONVENTION
SYNTAX DisplayString (SIZE (1..100))
DISPLAY-HINT
STATUS current
DESCRIPTION
-- serverSystem Group -- serverSystem Group
serverSystemDescr OBJECT-TYPE serverSystemDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255)) SYNTAX DisplayString (SIZE (0..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual description of the server. This value should "A textual description of the server. This value should
include the full name and version identification of the include the full name and version identification of the
server. server."
This string MUST contain only printable NVT ASCII
characters."
::= { serverSystem 1 } ::= { serverSystem 1 }
serverSystemObjectID OBJECT-TYPE serverSystemObjectID OBJECT-TYPE
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 7]
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The vendor's authoritative identification of the network "The vendor's authoritative identification of the network
management subsystem contained in this entity. This value is management subsystem contained in this entity. This value is
allocated within the SMI enterprise subtree (1.3.6.1.4.1) and allocated within the SMI enterprise subtree (1.3.6.1.4.1) and
provides an easy and unambiguous means for determining 'what provides an easy and unambiguous means for determining 'what
kind of server' is being managed. For example, if vendor kind of server' is being managed. For example, if vendor
'VeryBigServers, Inc.' is assigned the subtree 'VeryBigServers, Inc.' is assigned the subtree
1.3.6.1.4.1.4242, it may assign the identifier 1.3.6.1.4.1.4242, it may assign the identifier
1.3.6.1.4.1.4242.1.1 to its `Hercules DHCP Server'." 1.3.6.1.4.1.4242.1.1 to its `Hercules DHCP Server'."
::= { serverSystem 2 } ::= { serverSystem 2 }
-- bootpCounters Group
bootpCountRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets received that contain a Message Type
of
1 (BOOTREQUEST) in the first octet and do not contain option
number 53 (DHCP Message Type) in the options."
::= { bootpCounters 1 }
bootpCountInvalids OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets received that do not contain a Message
Type of 1 (BOOTREQUEST) in the first octet or are not valid
BOOTP packets (e.g., too short, invalid field in packet
header)."
::= { bootpCounters 2 }
bootpCountReplies OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets sent that contain a Message Type of 1
(BOOTREQUEST) in the first octet and do not contain option
number 53 (DHCP Message Type) in the options."
::= { bootpCounters 3 }
bootpCountDroppedUnknownClients OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of BOOTP packets dropped due to the server not
recognizing or not providing service to the hardware address
received in the incoming packet."
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 8]
::= { bootpCounters 4 }
bootpCountDroppedNotServingSubnet OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of BOOTP packets dropped due to the server not
being configured or not otherwise able to serve addresses on
the subnet from which this message was received."
::= { bootpCounters 5 }
-- dhcpCounters Group -- dhcpCounters Group
-- DHCP received packet counters
dhcpCountDiscovers OBJECT-TYPE dhcpCountDiscovers OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPDISCOVER (option 53 with value 1) packets "The number of DHCPDISCOVER (option 53 with value 1) packets
received." received."
REFERENCE
"RFC2131; RFC2132, section 9.6."
::= { dhcpCounters 1 } ::= { dhcpCounters 1 }
dhcpCountRequests OBJECT-TYPE dhcpCountRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPREQUEST (option 53 with value 3) packets "The number of DHCPREQUEST (option 53 with value 3) packets
received." received."
REFERENCE
"RFC2131; RFC2132, section 9.6."
::= { dhcpCounters 2 } ::= { dhcpCounters 2 }
dhcpCountReleases OBJECT-TYPE dhcpCountReleases OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPRELEASE (option 53 with value 7) packets "The number of DHCPRELEASE (option 53 with value 7) packets
received." received."
REFERENCE
"RFC2131; RFC2132, section 9.6."
::= { dhcpCounters 3 } ::= { dhcpCounters 3 }
dhcpCountDeclines OBJECT-TYPE dhcpCountDeclines OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPDECLINE (option 53 with value 4) packets "The number of DHCPDECLINE (option 53 with value 4) packets
received." received."
REFERENCE
"RFC2131; RFC2132, section 9.6."
::= { dhcpCounters 4 } ::= { dhcpCounters 4 }
dhcpCountInforms OBJECT-TYPE dhcpCountInforms OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPINFORM (option 53 with value 8) packets "The number of DHCPINFORM (option 53 with value 8) packets
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 9]
received." received."
::= { dhcpCounters 5 } REFERENCE
"RFC2131; RFC2132, section 9.6."
::= { dhcpCounters 5 } -- /*renumbered*/
dhcpCountInvalids OBJECT-TYPE dhcpCountLeaseQueries OBJECT-TYPE -- /*new*/
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCP packets received whose DHCP message type "The number of DHCPLEASEQUERY (option 53 with value TBD)
(i.e., option number 53) is not understood or handled by the packets received."
server." REFERENCE
::= { dhcpCounters 6 } "draft-ietf-dhc-leasequery-02.txt."
::= { dhcpCounters 6 } -- /*new*/
-- DHCP sent packet counters
dhcpCountOffers OBJECT-TYPE dhcpCountOffers OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPOFFER (option 53 with value 2) packets "The number of DHCPOFFER (option 53 with value 2) packets
sent." sent."
::= { dhcpCounters 7 } REFERENCE
"RFC2131; RFC2132, section 9.6."
::= { dhcpCounters 11 } -- /*renumbered*/
dhcpCountAcks OBJECT-TYPE dhcpCountAcks OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPACK (option 53 with value 5) packets "The number of DHCPACK (option 53 with value 5) packets sent."
sent." REFERENCE
::= { dhcpCounters 8 } "RFC2131; RFC2132, section 9.6."
::= { dhcpCounters 12 } -- /*renumbered*/
dhcpCountNacks OBJECT-TYPE dhcpCountNacks OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCPNACK (option 53 with value 6) packets "The number of DHCPNACK (option 53 with value 6) packets sent."
REFERENCE
"RFC2131; RFC2132, section 9.6."
::= { dhcpCounters 13 } -- /*renumbered*/
dhcpCountForcedRenews OBJECT-TYPE -- /*new*/
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of DHCPFORCERENEW (option 53 with value TBD)
packets sent."
REFERENCE
"draft-ietf-dhc-pv4-reconfigure-06.txt."
::= { dhcpCounters 14 } -- /*new*/
dhcpCountKnowns OBJECT-TYPE -- /*new*/
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of DHCPKNOWN (option 53 with value TBD) packets
sent." sent."
::= { dhcpCounters 9 } REFERENCE
"draft-ietf-dhc-leasequery-02.txt."
::= { dhcpCounters 12 } -- /*new*/
dhcpCountUnknowns OBJECT-TYPE -- /*new*/
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of DHCPUNKNOWN (option 53 with value TBD) packets
sent."
REFERENCE
"draft-ietf-dhc-leasequery-02.txt."
::= { dhcpCounters 13 } -- /*new*/
-- DHCP packet error counters
dhcpCountInvalids OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of DHCP packets received whose DHCP message type
(i.e., option number 53) is not understood or handled by the
server."
::= { dhcpCounters 17 } -- /*renumbered*/
dhcpCountDroppedUnknownClient OBJECT-TYPE dhcpCountDroppedUnknownClient OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCP packets dropped due to the server not "The number of DHCP packets dropped due to the server not
recognizing or not providing service to the client-id and/or recognizing or not providing service to the client-id and/or
hardware address received in the incoming packet." hardware address received in the incoming packet."
::= { dhcpCounters 10 } ::= { dhcpCounters 18 } -- /*renumbered*/
dhcpCountDroppedNotServingSubnet OBJECT-TYPE dhcpCountDroppedNotServingSubnet OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of DHCP packets dropped due to the server not "The number of DHCP packets dropped due to the server not being
being
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 10]
configured or not otherwise able to serve addresses on the configured or not otherwise able to serve addresses on the
subnet from which this message was received." subnet from which this message was received."
::= { dhcpCounters 11 } ::= { dhcpCounters 19 } -- /*renumbered*/
-- dhcpOptionalStatistics group
-- bootpStatistics group
bootpStatMinArrivalInterval OBJECT-TYPE dhcpStatMinArrivalInterval OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum amount of time between receiving two BOOTP "The minimum amount of time between receiving two DHCP
messages. A message is received at the server when the messages. A message is received at the server when the server
server is able to begin processing the message. This typically occurs
is able to begin processing the message. This typically
occurs
immediately after the message is read into server memory. If immediately after the message is read into server memory. If
no messages have been received, then this object contains a no messages have been received, then this object contains a
zero value." zero value."
::= { bootpStatistics 1 } ::= { dhcpOptionalStatistics 1 } -- /*renamed*/
bootpStatMaxArrivalInterval OBJECT-TYPE dhcpStatMaxArrivalInterval OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum amount of time between receiving two BOOTP "The maximum amount of time between receiving two DHCP
messages. A message is received at the server when the messages. A message is received at the server when the server
server is able to begin processing the message. This typically occurs
is able to begin processing the message. This typically
occurs
immediately after the message is read into server memory. If immediately after the message is read into server memory. If
no messages have been received, then this object contains a no messages have been received, then this object contains a
zero value." zero value."
::= { bootpStatistics 2 } ::= { dhcpOptionalStatistics 2 } -- /*renamed*/
bootpStatLastArrivalTime OBJECT-TYPE dhcpStatLastArrivalTime OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The date and time that the last valid BOOTP message was "The date and time that the last valid DHCP message was
received by the server. Invalid messages do not cause this received by the server. Invalid messages do not cause this
value to change. If valid no messages have been received, value to change. If no valid messages have been received, then
then
this object contains a date and time that is all zero." this object contains a date and time that is all zero."
::= { bootpStatistics 3 } ::= { dhcpOptionalStatistics 3 }
bootpStatSumSquaresArrivalTime OBJECT-TYPE dhcpStatSumSquaresArrivalTime OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sum of the squared BOOTP packet inter-arrival times in "The sum of the squared DHCP packet inter-arrival times in
micro-seconds. This value may be used to compute the microseconds. This value may be used to compute the variance
variance and standard deviation of the DHCP arrival times. Note that a
microsecond resolution of this object requires a clock
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 11] resolution to the millisecond since the square of a millisecond
and standard deviation of the BOOTP arrival times. Note that value produces a value with microsecond resolution."
a ::= { dhcpOptionalStatistics 4 }-- /*renamed*/
micro-second resolution of this object requires a clock
resolution to the milli-second since the square of a milli-
second value produces a value with micro-second resolution."
::= { bootpStatistics 4 }
bootpStatMinResponseTime OBJECT-TYPE dhcpStatMinResponseTime OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The smallest time interval measured as the difference "The smallest time interval measured as the difference between
between the arrival of a DHCP message at the server and the successful
the arrival of a BOOTP message at the server and the
successful
transmission of the response to that message. A message is transmission of the response to that message. A message is
received at the server when the server is able to begin received at the server when the server is able to begin
processing the message. A message is transmitted after the processing the message. A message is transmitted after the
server has no further use for the message. Note that the server has no further use for the message. Note that the
operating system may still have the message queued operating system may still have the message queued internally.
internally. The operating system queue time is not to be considered as part
of the response time. Invalid messages do not cause this value
The operating system queue time is not to be considered as to change. If no valid messages have been received, then this
part
of the response time. Invalid messages do not cause this
value
to change. If no valid messages have been received, then
this
object contains a zero value." object contains a zero value."
::= { bootpStatistics 5 } ::= { dhcpOptionalStatistics 5 }-- /*renamed*/
bootpStatMaxResponseTime OBJECT-TYPE dhcpStatMaxResponseTime OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The largest time interval measured as the difference between "The largest time interval measured as the difference between
the arrival of a BOOTP message at the server and the the arrival of a DHCP message at the server and the successful
successful
transmission of the response to that message. A message is transmission of the response to that message. A message is
received at the server when the server is able to begin received at the server when the server is able to begin
processing the message. A message is transmitted after the processing the message. A message is transmitted after the
server has no further use for the message. Note that the server has no further use for the message. Note that the
operating system may still have the message queued operating system may still have the message queued internally.
internally. The operating system queue time is not to be considered as part
of the response time. Invalid messages do not cause this value
The operating system queue time is not to be considered as to change. If no valid messages have been received, then this
part
of the response time. Invalid messages do not cause this
value
to change. If no valid messages have been received, then
this
object contains a zero value." object contains a zero value."
::= { bootpStatistics 6 } ::= { dhcpOptionalStatistics 6 }-- /*renamed*/
bootpStatSumResponseTime OBJECT-TYPE
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 12] dhcpStatSumResponseTime OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sum of the response time intervals in milli-seconds "The sum of the response time intervals in milliseconds where a
where response time interval is measured as the difference between
a response time interval is measured as the difference the arrival of a DHCP message at the server and the successful
between
the arrival of a BOOTP message at the server and the
successful
transmission of the response to that message. A message is transmission of the response to that message. A message is
received at the server when the server is able to begin received at the server when the server is able to begin
processing the message. A message is transmitted after the processing the message. A message is transmitted after the
server has no further use for the message. Note that the server has no further use for the message. Note that the
operating system may still have the message queued operating system may still have the message queued internally.
internally. The operating system queue time is not to be considered as part
of the response time. Invalid messages do not cause this value
The operating system queue time is not to be considered as to change. If no valid messages have been received, then this
part
of the response time. Invalid messages do not cause this
value
to change. If no valid messages have been received, then
this
object contains a zero value." object contains a zero value."
::= { bootpStatistics 7 } ::= { dhcpOptionalStatistics 7 }-- /*renamed*/
bootpStatSumSquaresResponseTime OBJECT-TYPE dhcpStatSumSquaresResponseTime OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sum of the squared BOOTP packet response times in micro- "The sum of the squared DHCP packet response times in micro-
seconds. This value may be used to compute the variance and seconds. This value may be used to compute the variance and
standard deviation of the BOOTP response times. Note that a standard deviation of the DHCP response times. Note that a
micro-second resolution of this object requires a clock microsecond resolution of this object requires a clock
resolution to the milli-second since the square of a milli- resolution to the millisecond since the square of a millisecond
second value produces a value with micro-second resolution." value produces a value with microsecond resolution."
::= { bootpStatistics 8 } ::= { dhcpOptionalStatistics 8 }-- /*renamed*/
-- dhcpStatistics group -- bootpCounters Group
dhcpStatMinArrivalInterval OBJECT-TYPE bootpCountRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets received that contain a Message Type of
1 (BOOTREQUEST) in the first octet and do not contain option
number 53 (DHCP Message Type) in the options."
REFERENCE
"RFC-1541."
::= { bootpCounters 1 }-- /*renamed*/
bootpCountInvalids OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets received that do not contain a Message
Type of 1 (BOOTREQUEST) in the first octet or are not valid
BOOTP packets (e.g., too short, invalid field in packet
header)."
::= { bootpCounters 2 }-- /*renamed*/
bootpCountReplies OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets sent that contain a Message Type of 2
(BOOTREPLY) in the first octet and do not contain option number
53 (DHCP Message Type) in the options."
REFERENCE
"RFC-1541."
::= { bootpCounters 3 }-- /*renamed*/
bootpCountDroppedUnknownClients OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of BOOTP packets dropped due to the server not
recognizing or not providing service to the hardware address
received in the incoming packet."
::= { bootpCounters 4 }-- /*renamed*/
bootpCountDroppedNotServingSubnet OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of BOOTP packets dropped due to the server not
being configured or not otherwise able to serve addresses on
the subnet from which this message was received."
::= { bootpCounters 5 }-- /*renamed*/
-- bootpOptionalStatistics group
bootpStatMinArrivalInterval OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum amount of time between receiving two DHCP "The minimum amount of time between receiving two BOOTP
messages. A message is received at the server when the messages. A message is received at the server when the server
server is able to begin processing the message. This typically occurs
is able to begin processing the message. This typically
occurs
immediately after the message is read into server memory. If immediately after the message is read into server memory. If
no messages have been received, then this object contains a no messages have been received, then this object contains a
zero value." zero value."
::= { dhcpStatistics 1 } ::= { bootpOptionalStatistics 1 }-- /*renamed*/
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 13] bootpStatMaxArrivalInterval OBJECT-TYPE
dhcpStatMaxArrivalInterval OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum amount of time between receiving two DHCP "The maximum amount of time between receiving two BOOTP
messages. A message is received at the server when the messages. A message is received at the server when the server
server is able to begin processing the message. This typically occurs
is able to begin processing the message. This typically
occurs
immediately after the message is read into server memory. If immediately after the message is read into server memory. If
no messages have been received, then this object contains a no messages have been received, then this object contains a
zero value." zero value."
::= { dhcpStatistics 2 } ::= { bootpOptionalStatistics 2 }-- /*renamed*/
dhcpStatLastArrivalTime OBJECT-TYPE bootpStatLastArrivalTime OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The date and time that the last valid DHCP message was "The date and time that the last valid BOOTP message was
received by the server. Invalid messages do not cause this received by the server. Invalid messages do not cause this
value to change. If no valid messages have been received, value to change. If valid no messages have been received, then
then
this object contains a date and time that is all zero." this object contains a date and time that is all zero."
::= { dhcpStatistics 3 } ::= { bootOptionalpStatistics 3 } -- /*renamed*/
dhcpStatSumSquaresArrivalTime OBJECT-TYPE bootpStatSumSquaresArrivalTime OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sum of the squared DHCP packet inter-arrival times in "The sum of the squared BOOTP packet inter-arrival times in
micro-seconds. This value may be used to compute the microseconds. This value may be used to compute the variance
variance and standard deviation of the BOOTP arrival times. Note that a
and standard deviation of the DHCP arrival times. Note that microsecond resolution of this object requires a clock
a resolution to the millisecond since the square of a millisecond
micro-second resolution of this object requires a clock value produces a value with microsecond resolution."
resolution to the milli-second since the square of a milli- ::= { bootpOptionalStatistics 4 }-- /*renamed*/
second value produces a value with micro-second resolution."
::= { dhcpStatistics 4 }
dhcpStatMinResponseTime OBJECT-TYPE bootpStatMinResponseTime OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The smallest time interval measured as the difference "The smallest time interval measured as the difference between
between the arrival of a BOOTP message at the server and the successful
the arrival of a DHCP message at the server and the
successful
transmission of the response to that message. A message is transmission of the response to that message. A message is
received at the server when the server is able to begin received at the server when the server is able to begin
processing the message. A message is transmitted after the processing the message. A message is transmitted after the
server has no further use for the message. Note that the server has no further use for the message. Note that the
operating system may still have the message queued operating system may still have the message queued internally.
internally.
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 14] The operating system queue time is not to be considered as part
The operating system queue time is not to be considered as of the response time. Invalid messages do not cause this value
part to change. If no valid messages have been received, then this
of the response time. Invalid messages do not cause this
value
to change. If no valid messages have been received, then
this
object contains a zero value." object contains a zero value."
::= { dhcpStatistics 5 } ::= { bootpOptionalStatistics 5 }-- /*renamed*/
dhcpStatMaxResponseTime OBJECT-TYPE bootpStatMaxResponseTime OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The largest time interval measured as the difference between "The largest time interval measured as the difference between
the arrival of a DHCP message at the server and the the arrival of a BOOTP message at the server and the successful
successful
transmission of the response to that message. A message is transmission of the response to that message. A message is
received at the server when the server is able to begin received at the server when the server is able to begin
processing the message. A message is transmitted after the processing the message. A message is transmitted after the
server has no further use for the message. Note that the server has no further use for the message. Note that the
operating system may still have the message queued operating system may still have the message queued internally.
internally.
The operating system queue time is not to be considered as The operating system queue time is not to be considered as part
part of the response time. Invalid messages do not cause this value
of the response time. Invalid messages do not cause this to change. If no valid messages have been received, then this
value
to change. If no valid messages have been received, then
this
object contains a zero value." object contains a zero value."
::= { dhcpStatistics 6 } ::= { bootpOptionalStatistics 6 }-- /*renamed*/
dhcpStatSumResponseTime OBJECT-TYPE bootpStatSumResponseTime OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sum of the response time intervals in milli-seconds "The sum of the response time intervals in milliseconds where a
where response time interval is measured as the difference between
a response time interval is measured as the difference the arrival of a BOOTP message at the server and the successful
between
the arrival of a DHCP message at the server and the
successful
transmission of the response to that message. A message is transmission of the response to that message. A message is
received at the server when the server is able to begin received at the server when the server is able to begin
processing the message. A message is transmitted after the processing the message. A message is transmitted after the
server has no further use for the message. Note that the server has no further use for the message. Note that the
operating system may still have the message queued operating system may still have the message queued internally.
internally.
The operating system queue time is not to be considered as The operating system queue time is not to be considered as part
part of the response time. Invalid messages do not cause this value
of the response time. Invalid messages do not cause this to change. If no valid messages have been received, then this
value
to change. If no valid messages have been received, then
this
object contains a zero value." object contains a zero value."
::= { dhcpStatistics 7 } ::= { bootpOptionalStatistics 7 }-- /*renamed*/
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 15] bootpStatSumSquaresResponseTime OBJECT-TYPE
dhcpStatSumSquaresResponseTime OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sum of the squared DHCP packet response times in micro- "The sum of the squared BOOTP packet response times in micro-
seconds. This value may be used to compute the variance and seconds. This value may be used to compute the variance and
standard deviation of the DHCP response times. Note that standard deviation of the BOOTP response times. Note that a
a microsecond resolution of this object requires a clock
micro-second resolution of this object requires a clock resolution to the millisecond since the square of a millisecond
resolution to the milli-second since the square of a milli- value produces a value with microsecond resolution."
second value produces a value with micro-second resolution." ::= { bootpOptionalStatistics 8 }-- /*renamed*/
::= { dhcpStatistics 8 }
-- serverConfiguration group -- server configurationgroup
-- server shared network table
serverSharedNetworkTable OBJECT-TYPE
SYNTAX SEQUENCE OF serverSharedNetworkEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of shared networks that are configured in the server.
A shared network is the logical aggregation of one or more
subnets that share a common network segment (e.g., multi-tapped
coaxial cable, wiring hub, or switch). This table is present
ONLY for those servers that organize the ranges of addresses
available for assignment where a higher-level grouping (i.e.,
the "shared" network) exists above ranges and subnets."
::= { serverConfiguration 1 }
serverSharedNetworkEntry OBJECT-TYPE
SYNTAX ServerSharedNetworkEntry
MAX-ACCESS not-accessible
STATUS current
INDEX { serverSharedNetworkName }
DESCRIPTION
"A logical row in the serverSharedNetworkTable."
::= { serverSharedNetworkTable 1}
ServerSharedNetworkEntry ::= SEQUENCE {
serverSharedNetworkName DhcpLabel,
serverSharedNetworkFreeAddresses Unsigned32,
serverSharedNetworkReservedAddresses Unsigned32,-- /*new*/
serverSharedNetworkTotalAddresses Unsigned32-- /*renamed*/
}
serverSharedNetworkName OBJECT-TYPE
SYNTAX DhcpLabel-- /*modified*/
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The name of the shared network, which uniquely identifies an
entry in the serverSharedNetworkTable."
::= { serverSharedNetworkEntry 1 }
serverSharedNetworkFreeAddresses OBJECT-TYPE-- /*renamed*/
SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The number of IP addresses which are available within this
shared network. If the server does not count free addresses by
shared network segment, this value will be zero."
::= { serverSharedNetworkEntry 2 }-- /*renumbered*/
serverSharedNetworkReservedAddresses OBJECT-TYPE-- /*new*/
SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The number of IP addresses which are reserved (not available
for assignement) within this shared network. If the server
does not count reserved addresses by shared network segment,
this value will be zero."
::= { serverSharedNetworkEntry 3 }
serverSharedNetworkTotalAddresses OBJECT-TYPE-- /*new*/
SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The number of IP addresses which are available within this
shared network. If the server does not count total addresses
by shared network segment, this value will be zero."
::= { serverSharedNetworkEntry 4 }
-- server subnet table
serverSubnetTable OBJECT-TYPE serverSubnetTable OBJECT-TYPE
SYNTAX SEQUENCE OF ServerSubnetEntry SYNTAX SEQUENCE OF serverSubnetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of subnets that are configured in this server." "A list of subnets that are configured in this server."
::= { serverConfiguration 1 } ::= { serverConfiguration 2 }
serverSubnetEntry OBJECT-TYPE serverSubnetEntry OBJECT-TYPE
SYNTAX ServerSubnetEntry SYNTAX ServerSubnetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
INDEX { serverSubnet } INDEX { serverSubnet }
DESCRIPTION DESCRIPTION
"A logical row in the serverSubnetTable." "A logical row in the serverSubnetTable."
::= { serverSubnetTable 1 } ::= { serverSubnetTable 1 }
ServerSubnetEntry ::= SEQUENCE { ServerSubnetEntry ::= SEQUENCE {
serverSubnet IpAddress, serverSubnet IpAddress,
serverSubnetMask IpAddress, serverSubnetMask IpAddress,
serverSubnetSharedNet IpAddress, serverSubnetSharedNetworkName DhcpLabel,-- /*modified*/
serverSubnetConfiguredAddresses Unsigned32,
serverSubnetAvailableAddresses Unsigned32,
serverSubnetFreeAddressLowThreshold Unsigned32, serverSubnetFreeAddressLowThreshold Unsigned32,
serverSubnetFreeAddressHighThreshold Unsigned32 serverSubnetFreeAddressHighThreshold Unsigned32,
ServerSubnetFreeAddresses Unsigned32 -- /*renamed*/
} }
serverSubnet OBJECT-TYPE serverSubnet OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS read-only-- /*changed*/
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the subnet." "The IP address of the subnet."
::= { serverSubnetEntry 1 } ::= { serverSubnetEntry 1 }
serverSubnetMask OBJECT-TYPE serverSubnetMask OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 16]
DESCRIPTION DESCRIPTION
"The subnet mask of the subnet. This MUST be the same as the "The subnet mask of the subnet. This MUST be the same as the
value of DHCP option 1 offered to clients on this subnet." value of DHCP option 1 offered to clients on this subnet."
::= { serverSubnetEntry 2 } ::= { serverSubnetEntry 2 }
serverSubnetSharedNet OBJECT-TYPE serverSubnetSharedNetworkName OBJECT-TYPE-- /*renamed*/
SYNTAX IpAddress SYNTAX DhcpLabel-- /*modified*/
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of another subnet that is on the same shared "The shared subnet name (used as an index into the server
media as this subnet. The address of the shared subnet MUST shared subnet table) to which this subnet belongs. This value
also be configured on this server. The address 0.0.0.0 will be null for servers that do not organize or describe
should networks in this manner."
be used if this subnet is not shared."
::= { serverSubnetEntry 3 } ::= { serverSubnetEntry 3 }
serverSubnetConfiguredAddresses OBJECT-TYPE serverSubnetFreeAddressLowThreshold OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of IP addresses that are configured to be served
on this subnet."
::= { serverSubnetEntry 4 }
serverSubnetAvailableAddresses OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of IP addresses on this subnet that are not
currently assigned to a client."
::= { serverSubnetEntry 5 }
serverSubnetFreeAddressLowThreshold OBJECT-TYPE # /*new*/
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The low threshold for available free addresses in this "The low threshold for available free addresses in this subnet.
subnet.
If the value for available free addresses in this subnet If the value for available free addresses in this subnet
becomes equal to or less than this value, a becomes equal to or less than this value, a
serverSubnetFreeAddressLowThreshold event is generated serverSubnetFreeAddressLowThreshold event is generated for this
for this shared network. No more shared network. No more serverSubnetFreeAddressLowThreshold
serverSubnetFreeAddressLowThreshold events will events will be generated for this subnet during this execution
be generated for this subnet during this execution of of the DHCP server until the value for available free addresses
the DHCP server until the value for available free addresses has exceeded the value of
has serverSubnetFreeAddressHighThreshold."
exceeded the value of serverSubnetFreeAddressHighThreshold. ::= { serverSubnetEntry 4 }
This value may be expressed as either an absolute value or a
percentage; the units are specified by the value of
serverSubnetFreeAddressUnits."
::= { serverSubnetEntry 6 }
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 17] serverSharedNetworkFreeAddressHighThreshold OBJECT-TYPE
serverSubnetFreeAddressHighThreshold OBJECT-TYPE # /*new*/
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The high threshold for available free addresses in this "The high threshold for available free addresses in this
subnet. subnet. If a serverSubnetFreeAddressLowThreshold event has
If a serverSubnetFreeAddressLowThreshold event been generated for this subnet, and the value for available
has been generated for this subnet, and the value for free addresses has exceeded the value of
available free addresses has exceeded the value of
serverSubnetFreeAddressHighThreshold, then a serverSubnetFreeAddressHighThreshold, then a
serverFreeAddressessHigh event will be generated. No more serverFreeAddressessHigh event will be generated. No more
serverFreeAddressessHigh events will be generated for this serverFreeAddressessHigh events will be generated for this
subnet during this execution of the DHCP server until subnet during this execution of the DHCP server until the value
the value for available free addresses becomes equal to or for available free addresses becomes equal to or less than the
less value of serverSubnetFreeAddressHighThreshold."
than the value of serverSubnetFreeAddressHighThreshold. ::= { serverSubnetEntry 5 }
This value may be expressed as either an absolute value or a -- server range table
percentage; the units are specified by the value of
serverSubnetFreeAddressUnits."
::= { serverSubnetEntry 7 }
serverRangeTable OBJECT-TYPE serverRangeTable OBJECT-TYPE
SYNTAX SEQUENCE OF ServerRangeEntry SYNTAX SEQUENCE OF serverRangeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of ranges that are configured on this server." "A list of ranges that are configured on this server."
::= { serverConfiguration 2 } ::= { serverConfiguration 3 }
serverRangeEntry OBJECT-TYPE serverRangeEntry OBJECT-TYPE
SYNTAX ServerRangeEntry SYNTAX ServerRangeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
INDEX { serverRangeStart } INDEX { serverRangeStart }
DESCRIPTION DESCRIPTION
"A logical row in the serverRangeTable." "A logical row in the serverRangeTable."
::= { serverRangeTable 1 } ::= { serverRangeTable 1 }
ServerRangeEntry ::= SEQUENCE { ServerRangeEntry ::= SEQUENCE {
serverRangeStart IpAddress, serverRangeStart IpAddress,
serverRangeEnd IpAddress, serverRangeEnd IpAddress,
serverRangeSubnetMask IpAddress, serverRangeSubnetMask IpAddress,
serverRangeInUse Gauge32, serverRangeInUse Gauge32,
serverRangeOutstandingOffers Gauge32 serverRangeOutstandingOffers Gauge32
} }
serverRangeStart OBJECT-TYPE serverRangeStart OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the first address in the range. The value "The IP address of the first address in the range. The value
of of range start must be less than or equal to the value of range
range start must be less than or equal to the value of range
end." end."
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 18]
::= { serverRangeEntry 1 } ::= { serverRangeEntry 1 }
serverRangeEnd OBJECT-TYPE serverRangeEnd OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the last address in the range. The value "The IP address of the last address in the range. The value of
of
range end must be greater than or equal to the value of range range end must be greater than or equal to the value of range
start." start."
::= { serverRangeEntry 2 } ::= { serverRangeEntry 2 }
serverRangeSubnetAddress OBJECT-TYPE serverRangeSubnetMask OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subnet address "The subnet address mask for this range."
for this range."
::= { serverRangeEntry 3 } ::= { serverRangeEntry 3 }
serverRangeInUse OBJECT-TYPE serverRangeInUse OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of addresses in this range that are currently in "The number of addresses in this range that are currently in
use. This number includes those addresses whose lease has use. This number includes those addresses whose lease has not
not
expired and addresses which have been reserved (either by the expired and addresses which have been reserved (either by the
server or through configuration)." server or through configuration)."
::= { serverRangeEntry 4 } ::= { serverRangeEntry 4 }
serverRangeOutstandingOffers OBJECT-TYPE serverRangeOutstandingOffers OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of outstanding DHCPOFFER messages for this range "The number of outstanding DHCPOFFER messages for this range is
is
reported with this value. An offer is outstanding if the reported with this value. An offer is outstanding if the
server has sent a DHCPOFFER message to a client, but has not server has sent a DHCPOFFER message to a client, but has not
yet received a DHCPREQUEST message from the client nor has yet received a DHCPREQUEST message from the client nor has the
the
server-specific timeout (limiting the time in which a client server-specific timeout (limiting the time in which a client
can respond to the offer message) for the offer message can respond to the offer message) for the offer message
expired." expired."
::= { serverRangeEntry 5 } ::= { serverRangeEntry 5 }
-- server address table
serverAddressTable OBJECT-TYPE serverAddressTable OBJECT-TYPE
SYNTAX SEQUENCE OF ServerAddressEntry SYNTAX SEQUENCE OF serverAddressEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of addresses that are known by this server. The list "An optional list of addresses that are known by this server.
The list MUST contain addresses that have not expired. The
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 19] list MUST NOT contain addresses that have never been assigned
MUST contain addresses that have not expired. The list MUST by the server UNLESS the lease is pre-configured in the server
NOT contain addresses that have never been assigned by the (e.g., a static lease for a host). Expired leases MAY appear
server UNLESS the lease is pre-configured in the server during the time they are 'remembered' by the server for
(e.g., subsequent assignment to the same host."
a static lease on a subnet)." ::= { serverConfiguration 4 }
::= { serverConfiguration 3 }
serverAddressEntry OBJECT-TYPE serverAddressEntry OBJECT-TYPE
SYNTAX ServerAddressEntry SYNTAX ServerAddressEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
INDEX { serverAddress } INDEX { serverAddress }
DESCRIPTION DESCRIPTION
"A logical row in the serverAddressTable." "A logical row in the serverAddressTable."
::= { serverAddressTable 1 } ::= { serverAddressTable 1 }
ServerAddressEntry ::= SEQUENCE { ServerAddressEntry ::= SEQUENCE {
serverAddress IpAddress, serverAddress IpAddress,
serverAddressSubnetMask IpAddress, serverAddressSubnetMask IpAddress,
serverAddressRange IpAddress, serverAddressRange IpAddress,
serverAddressType INTEGER, serverAddressType INTEGER,
serverAddressTimeRemaining Unsigned32, serverAddressTimeRemaining Unsigned32,
serverAddressAllowedProtocol INTEGER, serverAddressAllowedProtocol INTEGER,
serverAddressServedProtocol INTEGER, serverAddressServedProtocol INTEGER,
serverAddressHardwareAddress PhysicalAddress, serverAddressMacAddress OCTET STRING,
serverAddressClientId OCTET STRING, serverAddressClientId OCTET STRING,
serverAddressHostName DisplayString, serverAddressHostName DisplayString,
serverAddressDomainName DisplayString serverAddressDomainName DisplayString
} }
serverAddress OBJECT-TYPE serverAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the entry." "The IP address of the entry."
::= { serverAddressEntry 1 } ::= { serverAddressEntry 1 }
serverAddressSubnetMask OBJECT-TYPE serverAddressSubnetMask OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subnet mask (DHCP option 1) provided to the client "The subnet mask (DHCP option 1) provided to the client offered
offered this address. The subnet, resulting from logically ANDing the
this address. The subnet, resulting from logically ANDing subnet mask with the entry's IP address, must be configured on
the
subnet mask with the entry's IP address, must be configured
on
this server and appear as a row in the dhcpSubnetTable." this server and appear as a row in the dhcpSubnetTable."
::= { serverAddressEntry 2 } ::= { serverAddressEntry 2 }
serverAddressRange OBJECT-TYPE serverAddressRange OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The starting IP address (serverRangeStart object) of the range
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 20]
"The starting IP address (serverRangeStart object) of the
range
to which this address belongs. If the address does not fall to which this address belongs. If the address does not fall
into one of the configured ranges (e.g., a statically into one of the configured ranges (e.g., a statically
configured address on a subnet) the range may be 0.0.0.0." configured address on a subnet) the range may be 0.0.0.0."
::= { serverAddressEntry 3 } ::= { serverAddressEntry 3 }
serverAddressType OBJECT-TYPE serverAddressType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
static(1), static(1),
dynamic(2), dynamic(2),
configuration-reserved(3), expired(3), -- /*new*/
server-reserved(4) configuration-reserved(4), -- /*renumbered*/
server-reserved(5) -- /*renumbered*/
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of this address." "The type of this address. Types are:
(1) static addresses defined by the server configuration.
(2) dynamic addresses defined by the server configuration
AND actually assigned by the server.
(3) expired dynamic addresses, previously assigned by the
server and 'remembered' for subsequent assignment to the
same host.
(4) Addresses reserved (i.e., not assignable) by the server
configuration.
(5) Addresses previously assigned by the server, but
temporarily or permanently removed from assignable state
for some reason, e.g., the server received an ICMP
ECHOREPLY for the IP address or a DHCPDECLINE message
has been received for the IP address."
::= { serverAddressEntry 4 } ::= { serverAddressEntry 4 }
serverAddressTimeRemaining OBJECT-TYPE serverAddressTimeRemaining OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of seconds until the lease expires. A value of "The number of seconds until the lease expires. A value of
4294967295 (i.e., 0xFFFFFFFF) should be used for leases that 4294967295 (i.e., 0xFFFFFFFF) should be used for leases that
have a lease time which is 'infinite' and for BOOTP leases." have a lease time which is 'infinite' and for BOOTP leases."
skipping to change at line 1197 skipping to change at page 29, line 21
serverAddressAllowedProtocol OBJECT-TYPE serverAddressAllowedProtocol OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none(1), none(1),
bootp(2), bootp(2),
dhcp(3), dhcp(3),
bootp-or-dhcp(4) bootp-or-dhcp(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of protocol that is allowed to be used to serve "The type of protocol that is allowed to be used to serve this
this
address. A type of none(1) indicates that the address is not address. A type of none(1) indicates that the address is not
available to be served (e.g., a reserved address)." available to be served (e.g., a reserved address).Type (2) are
reserved for BOOTP only devices, while type (3) are reserved
for DHCP only devices. A type of bootp-or-dhcp (4) may be
offered to any type of client."
::= { serverAddressEntry 6 } ::= { serverAddressEntry 6 }
serverAddressServedProtocol OBJECT-TYPE serverAddressServedProtocol OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none(1), none(1),
bootp(2), bootp(2),
dhcp(3) dhcp(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of protocol that was used when this address was "The type of protocol that was used when this address was
assigned. This object will have the value of none(1) if the assigned. This object will have the value of none(1) if the
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 21]
address has not been served." address has not been served."
::= { serverAddressEntry 7 } ::= { serverAddressEntry 7 }
serverAddressHardwareAddress OBJECT-TYPE serverAddressHardwareAddress OBJECT-TYPE
SYNTAX PhysicalAddress SYNTAX PhysicalAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The hardware type and hardware address of the client that "The hardware type and hardware address of the client that has
has
been assigned this lease. The first octet of this object been assigned this lease. The first octet of this object
contains the hardware type from the 'htype' field of the contains the hardware type from the 'htype' field of the BOOTP
BOOTP
packet and the remaining octets contain the hardware address packet and the remaining octets contain the hardware address
from the 'chaddr' field of the BOOTP packet. This object may from the 'chaddr' field of the BOOTP packet. This object may
be empty if the address has not been previously served." be empty if the address has not been previously served."
::= { serverAddressEntry 8 } ::= { serverAddressEntry 8 }
serverAddressClientId OBJECT-TYPE serverAddressClientId OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..255)) SYNTAX OCTET STRING (SIZE (0..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The client-id of the client that has been assigned this "The client-id of the client that has been assigned this lease.
lease.
The client-id is the value specified in option 61 (client-id The client-id is the value specified in option 61 (client-id
option) when the lease was assigned. This object may be option) when the lease was assigned. This object may be empty
empty if the lease has not been previously assigned or if the client-
if the lease has not been previously assigned or if the
client-
id option was not specified when the address was assigned." id option was not specified when the address was assigned."
::= { serverAddressEntry 9 } ::= { serverAddressEntry 9 }
serverAddressHostName OBJECT-TYPE serverAddressHostName OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255)) SYNTAX DisplayString (SIZE (1..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The host name (DHCP option 12) the client is configured to "The host name (DHCP option 12) the client is configured to
use, use, or if no host name was configured then the host name that
or if no host name was configured then the host name that the the client supplied when requesting an address. While this
client supplied when requesting an address. While this object has a maximum size of 255 octets, a Fully-Qualified
object Domain Name (FQDN) consisting of a Host Name part and a Domain
has a maximum size of 255 octets, a Fully-Qualified Domain Name part is currently limited to 255 octets. Therefore, the
Name sum of the string lengths for this object and the
(FQDN) consisting of a Host Name part and a Domain Name part serverAddressDomainName must, in practice, be less than 256
is octets."
currently limited to 255 octets. Therefore, the sum of the
string lengths for this object and the
serverAddressDomainName
must, in practice, be less than 256 octets."
::= { serverAddressEntry 10 } ::= { serverAddressEntry 10 }
serverAddressDomainName OBJECT-TYPE serverAddressDomainName OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..255)) SYNTAX DisplayString (SIZE (1..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 22]
DESCRIPTION DESCRIPTION
"The domain name (DHCP option 15) assigned to the client. "The domain name (DHCP option 15) assigned to the client.
While While this object has a maximum size of 255 octets, a Fully-
this object has a maximum size of 255 octets, a Fully- Qualified Domain Name (FQDN) consisting of a Host Name part and
Qualified a Domain Name part is currently limited to 255 octets, less the
Domain Name (FQDN) consisting of a Host Name part and a separator (".") character. Therefore, the sum of the string
Domain lengths for this object and the serverAddressHostName must, in
Name part is currently limited to 255 octets, less the practice, be less than 256 octets."
separator
('.') character. Therefore, the sum of the string
lengths for this object and the serverAddressHostName must,
in practice, be less than 256 octets."
::= { serverAddressEntry 11 } ::= { serverAddressEntry 11 }
-- Server Client Table
serverClientTable OBJECT-TYPE serverClientTable OBJECT-TYPE
SYNTAX SEQUENCE OF ServerClientEntry SYNTAX SEQUENCE OF serverClientEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of clients that are known by this server. Details "A list of clients that are known by this server. Details
about about the clients may be found by indexing into the
the clients may be found by indexing into the serverAddressTable using the serverClientHardwareAddress and
serverAddressTable serverClientAddress objects. This table is indexed first by
using the serverClientAddress object. This table is indexed the MAC address of the client and then by the subnet address on
first by the physical address of the client and then by the which the client resides. The subnet is included as an index
subnet since a MAC address is only guaranteed to be unique within a
address on which the client resides. The subnet is included subnet (i.e., a MAC address is not globally unique)."
as ::= { serverConfiguration 5 }
an index since the physical address is only guaranteed to be
unique
within a subnet (i.e., a physical address is not globally
unique)."
::= { clientConfiguration 1 }
serverClientEntry OBJECT-TYPE serverClientEntry OBJECT-TYPE
SYNTAX ServerClientEntry SYNTAX ServerClientEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
INDEX { INDEX { serverClientHardwareAddress, serverClientAddress }
serverClientHardwareAddress,
serverClientSubnetMask
}
DESCRIPTION DESCRIPTION
"A logical row in the serverClientTable. An entry in this "A logical row in the serverClientTable. An entry in this
table table may be a client that requested an address but was refused
may be a client that requested an address but was refused (e.g., not authorized).Servers MAY track these types of clients
(e.g., not authorized). Servers MAY track these types of if desired and may choose to remove such client entries using a
clients if desired and may choose to remove such client server defined algorithm. As an example, a server may choose
entries to keep client request that does not map to an address for a
using a server defined algorithm. As an example, a server one hour time period before removing that entry from this
may
choose to keep client request that does not map to an address
for a one hour time period before removing that entry from
this
table." table."
::= { serverClientTable 1 } ::= { serverClientTable 1 }
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 23]
ServerClientEntry ::= SEQUENCE { ServerClientEntry ::= SEQUENCE {
serverClientHardwareAddress PhsicalAddress serverClientHardwareAddress PhysicalAddress
serverClientSubnetMask IpAddress, serverClientSubnetMask IpAddress,
serverClientAddress IpAddress, serverClientAddress IpAddress,
serverClientLastRequestTime DateAndTime, serverClientLastRequestTime DateAndTime,
serverClientLastRequestType INTEGER, serverClientLastRequestType INTEGER,
serverClientLastResponseType INTEGER serverClientLastResponseType INTEGER
} }
serverClientHardwareAddress OBJECT-TYPE serverClientHardwareAddress OBJECT-TYPE
SYNTAX PhysicalAddress SYNTAX PhysicalAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The hardware type and hardware address of the client that "The hardware type and hardware address of the client that has
has
been assigned this lease. The first octet of this object been assigned this lease. The first octet of this object
contains the hardware type from the 'htype' field of the contains the hardware type from the 'htype' field of the BOOTP
BOOTP
packet and the remaining octets contain the hardware address packet and the remaining octets contain the hardware address
from the 'chaddr' field of the BOOTP packet. This value of from the 'chaddr' field of the BOOTP packet."
this object MUST NOT be zero length."
::= { serverClientEntry 1 } ::= { serverClientEntry 1 }
serverClientSubnetMask OBJECT-TYPE serverClientSubnetMask OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subnet mask (DHCP option 1) applied to "The subnet mask (DHCP option 1) applied to
serverClientAddress." serverClientAddress."
::= { serverClientEntry 2 } ::= { serverClientEntry 2 }
skipping to change at line 1377 skipping to change at page 32, line 23
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the entry. May be used to index into the "The IP address of the entry. May be used to index into the
serverAddressTable. May be 0.0.0.0 if an address is not serverAddressTable. May be 0.0.0.0 if an address is not
associated with this client." associated with this client."
::= { serverClientEntry 3 } ::= { serverClientEntry 3 }
serverClientLastRequestTime OBJECT-TYPE serverClientLastRequestTime OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DhcpTimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time when the last request was received." "The timestamp of the last request received, to millisecond
precision if available on the server."
::= { serverClientEntry 4 } ::= { serverClientEntry 4 }
serverClientLastRequestType OBJECT-TYPE serverClientLastRequestType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
bootprequest(0)
dhcpdiscover(1), dhcpdiscover(1),
bootp(2),
dhcprequest(3), dhcprequest(3),
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 24]
dhcpdecline(4), dhcpdecline(4),
unknown(5),
dhcprelease(7), dhcprelease(7),
dhcpinform(8) dhcpinform(8)
dhcpleasequery(TBD),-- /*new*/
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the last request that was received for this "The type of the last request message received for this
client." client.If the server does not capture this information, the
value 32,767 is returned."
REFERENCE
"RFC2131; RFC2132, section 9.6; draft-ietf-dhc-leasequery-
02.txt."
::= { serverClientEntry 5 } ::= { serverClientEntry 5 }
serverClientLastResponseType OBJECT-TYPE serverClientLastResponseType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
bootp(1), bootpreply(1),
dhcpoffer(2), dhcpoffer(2),
unknown(3),
dhcpack(5), dhcpack(5),
dhcpnak(6) dhcpnak(6)
dhcpknown(TBD),-- /*new*/
dhcpunknown(TBD)-- /*new*/
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the last response that was sent to this client." "The type of the last response message sent to this client. If
the server does not capture this information, the value 32,767
is returned."
REFERENCE
"RFC2131; RFC2132, section 9.6;draft-ietf-dhc-pv4-reconfigure-
06.txt;draft-ietf-dhc-leasequery-02.txt"
::= { serverClientEntry 6 } ::= { serverClientEntry 6 }
-- serverNotifyObjects: Objects which are used only in --serverNotifyObjects: Objects which are used only in notifications
notifications
serverNotifyDuplicateIPAddress OBJECT-TYPE # /*new*/ serverNotifyDuplicateIPAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address which was found to be a duplicate." "The IP address found to be a duplicate. Duplicates are
detected by servers which issue an ICMP ECHOREQUEST prior to
offering an IP address lease."
::= { serverNotifyObjects 1 } ::= { serverNotifyObjects 1 }
serverNotifyMACAddress OBJECT-TYPE # /*new*/ serverNotifyDuplicateMAC OBJECT-TYPE
SYNTAX PhysicalAddress SYNTAX PhysicalAddress
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The offending MAC address which caused a duplicate IP "The offending MAC address which caused a duplicate IP address
address to be detected." to be detected, if captured by the server, else 00-00-00-00-00-
00."
::= { serverNotifyObjects 2 } ::= { serverNotifyObjects 2 }
serverNotifyServer OBJECT-TYPE # /*new*/ serverNotifyClientDuplicateIP OBJECT-TYPE-- /*renamed*/
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP Address of a server with which the DHCP server "The IP Address offered by a server that the requesting client
is attempting to communicate." has determined to be a duplicate, detected by means of a
::= { serverNotifyObjects 3 } gratuitous ARP message and reported through a DHCPDECLINE
serverNotifyDuplicateIPAddressDetectedBy OBJECT-TYPE # /*new*/
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 25]
SYNTAX INTEGER {dhcpClient(1), dhcpServer(2)}
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"For a serverDuplicateAddress notification, this
object indicates whether the client or server detected
the condition. DHCP servers detect a duplicate address
by an unexpected reply to an ICMPECHOREQUEST (ping)
message, while DHCP clients detect duplicates by an
unexpected reply to a gratuitous ARP message, and report
this condition to a DHCP server through a DHCPDECLINE
message." message."
::= { serverNotifyObjects 5 } ::= { serverNotifyObjects 3 }
serverNotifyContestedIpAddress OBJECT-TYPE # /*new*/
SYNTAX IpAddress
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The IP address for which ownership is claimed by two or
more DHCP servers."
::= { serverNotifyObjects 6 }
-- Notifications -- Notifications
dhcpServerMIBNotificationPrefix OBJECT IDENTIFIER # /*new*/ serverMIBNotificationPrefix OBJECT IDENTIFIER
::= { dhcpServerMIB 2 } # /*renamed*/ ::= { serverMIB 2 }serverMIBNotifications OBJECT IDENTIFIER
dhcpServerMIBNotifications OBJECT IDENTIFIER # /*new*/ ::= { serverMIBNotificationPrefix 0 }
::= { dhcpServerMIBNotificationPrefix 0 }
serverFreeAddressLow NOTIFICATION-TYPE # /*new*/ serverFreeAddressLow NOTIFICATION-TYPE
OBJECTS { OBJECTS {
serverSharedNetworkFreeAddressLowThreshold, serverSharedNetworkFreeAddressLowThreshold,
serverSharedNetworkFreeAddressValue, serverSharedNetworkFreeAddresses
serverSharedNetworkFreeAddressUnits
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification signifies that the number of available IP "This notification signifies that the number of available IP
addresses for a particular shared network has fallen below addresses for a particular shared network has fallen below the
the
value of serverSharedNetworkFreeAddressLowThreshold for that value of serverSharedNetworkFreeAddressLowThreshold for that
shared shared network."
network." ::= { serverMIBNotifications 1 }
::= { dhcpServerMIBNotifications 1 }
serverFreeAddressHigh NOTIFICATION-TYPE # /*new*/ serverFreeAddressHigh NOTIFICATION-TYPE
OBJECTS { OBJECTS {
serverSharedNetworkFreeAddressHighThreshold, serverSharedNetworkFreeAddressHighThreshold,
serverSharedNetworkFreeAddressValue, serverSharedNetworkFreeAddresses
serverSharedNetworkFreeAddressUnits
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification signifies that the number of available IP "This notification signifies that the number of available IP
addresses for a particular shared network has risen above the addresses for a particular shared network has risen above the
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 26]
value of serverSharedNetworkFreeAddressHighThreshold for that value of serverSharedNetworkFreeAddressHighThreshold for that
shared network." shared network."
::= { dhcpServerMIBNotifications 2 } ::= { serverMIBNotifications 2 }
serverServerStart NOTIFICATION-TYPE # /*new*/ serverServerStart NOTIFICATION-TYPE
OBJECTS { serverNotifyServerType } OBJECTS { serverNotifyClientDuplicateIP }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification signifies that the server of the specified "This notification signifies that the server of the specified
type has started on the host from which this notification has type has started on the host from which this notification has
been sent." been sent."
::= { dhcpServerMIBNotifications 3 } ::= { serverMIBNotifications 3 }
serverServerStop NOTIFICATION-TYPE # /*new*/ serverServerStop NOTIFICATION-TYPE
OBJECTS { serverNotifyServerType } OBJECTS { serverNotifyClientDuplicateIP }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification signifies that the server of the specified "This notification signifies that the server of the specified
type has stopped normally on the host from which this type has stopped normally on the host from which this
notification has been sent." notification has been sent."
::= { dhcpServerMIBNotifications 4 } ::= { serverMIBNotifications 4 }
serverDuplicateAddress NOTIFICATION-TYPE # /*new*/ serverDuplicateAddress NOTIFICATION-TYPE
OBJECTS { OBJECTS {
serverNotifyDuplicateIPAddress, serverNotifyDuplicateIPAddress,
serverNotifyMACAddress, serverNotifyDuplicateMAC,
serverNotifyDuplicateIPAddressDetectedBy serverNotifyClientDuplicateMAC
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification signifies that a duplicate IP address has "This notification signifies that a duplicate IP address has
been detected. The DHCP server can detect this condition been detected. The DHCP server can detect this condition
through the ping-before-offer mechanism. Alternatively, the through the ping-before-offer mechanism. Alternatively, the
client may have sent a DHCPDECLINE back to the server; this client may have sent a DHCPDECLINE back to the server; this is
is
assumed to be the result of the client detecting that the assumed to be the result of the client detecting that the
address was in use. In either case, the DHCP server marks address was in use. In either case, the DHCP server marks the
the
IP address as unavailable for leasing to clients. The IP address as unavailable for leasing to clients. The
serverNotifyDuplicateIPAddressDetectedBy object indicates serverNotifyClientDuplicateMAC object indicates whether the
whether the client or server detected this condition." client or server detected this condition."
::= { dhcpServerMIBNotifications 7 } ::= { serverMIBNotifications 5 }-- /*renumbered*/
serverAddressConflict NOTIFICATION-TYPE
OBJECTS { serverNotifyClientDuplicateIP }
STATUS current
DESCRIPTION
::= { serverMIBNotifications 6 }-- /*renumbered*/
-- Conformance -- Conformance
dhcpServerMIBConformance OBJECT-IDENTITY # /*renamed*/ serverMIBConformanceOBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"DHCP Server MIB objects are all defined in this branch." "DHCP Server MIB objects are all defined in this branch."
::= { dhcpServerMIB 3 } # /*renamed*/ ::= { serverMIB 3 }
dhcpServerMIBCompliances OBJECT IDENTIFIER serverMIBCompliancesOBJECT IDENTIFIER
::= { dhcpServerMIBConformance 1 } # /*renamed*/ ::= { serverMIBConformance 1 }
dhcpServerMIBGroups OBJECT IDENTIFIER serverMIBGroupsOBJECT IDENTIFIER
::= { dhcpServerMIBConformance 2 } # /*renamed*/ ::= { serverMIBConformance 2 }
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 27]
-- Compliance groups -- Compliance groups
dhcpServerMIBCompliance MODULE-COMPLIANCE serverMIBCompliance MODULE-COMPLIANCE
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
serverSystemGroup, serverSystemGroup,
bootpCountersGroup, bootpCountersGroup,
dhcpCountersGroup, dhcpCountersGroup,
bootpStatisticsGroup,
dhcpStatisticsGroup,
serverConfigurationGroup, serverConfigurationGroup,
serverClientsGroup serverClientsGroup
} }
OPTIONAL-GROUPS {
bootpOptionalStatisticsGroup,
dhcpOptionalStatisticsGroup
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the requirements for conformance to the DCHP "Describes the requirements for conformance to the DCHP Server
Server MIB" MIB"
::= { dhcpServerMIBCompliances 1 } ::= { serverMIBCompliances 1 }
-- Object groups
serverSystemGroup OBJECT-GROUP serverSystemGroup OBJECT-GROUP
OBJECTS { OBJECTS {
serverSystemDescr, serverSystemDescr,
serverSystemObjectID serverSystemObjectID
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects belonging to the serverSystemGroup." "Objects belonging to the serverSystemGroup."
::= { dhcpServerMIBGroups 1 } ::= { serverMIBGroups 1 }
bootpCountersGroup OBJECT-GROUP bootpCountersGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bootpCountRequests, bootpCountRequests,
bootpCountInvalids, bootpCountInvalids,
bootpCountReplies, bootpCountReplies,
bootpCountDroppedUnknownClients, bootpCountDroppedUnknownClients,
bootpCountDroppedNotServingSubnet bootpCountDroppedNotServingSubnet
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects belonging to the bootpBountersGroup." "Objects belonging to the bootpBountersGroup."
::= { dhcpServerMIBGroups 2 } ::= { serverMIBGroups 2 }
dhcpCountersGroup OBJECT-GROUP dhcpCountersGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dhcpCountDiscovers, dhcpCountDiscovers,
dhcpCountRequests, dhcpCountRequests,
dhcpCountReleases, dhcpCountReleases,
dhcpCountDeclines, dhcpCountDeclines,
dhcpCountInforms, dhcpCountInforms,
dhcpCountInvalids, dhcpCountInvalids,
dhcpCountOffers, dhcpCountOffers,
dhcpCountAcks, dhcpCountAcks,
dhcpCountNacks, dhcpCountNacks,
dhcpCountDroppedUnknownClient, dhcpCountDroppedUnknownClient,
dhcpCountDroppedNotServingSubnet dhcpCountDroppedNotServingSubnet
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 28]
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects belonging to the dhcpCountersGroup." "Objects belonging to the dhcpCountersGroup."
::= { dhcpServerMIBGroups 3 } ::= { serverMIBGroups 3 }
bootpStatisticsGroup OBJECT-GROUP bootpOptionalStatisticsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bootpStatMinArrivalInterval, bootpStatMinArrivalInterval,
bootpStatMaxArrivalInterval, bootpStatMaxArrivalInterval,
bootpStatLastArrivalTime, bootpStatLastArrivalTime,
bootpStatSunSquaresArrivalTime, bootpStatSumSquaresArrivalTime,
bootpStatMinResponseTime, bootpStatMinResponseTime,
bootpStatMaxResponseTime, bootpStatMaxResponseTime,
bootpStatSumReponseTime, bootpStatSumReponseTime,
bootpStatSumSquaresResponseTime bootpStatSumSquaresResponseTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects belonging to the bootpStatisticsGroup." "Objects belonging to the bootpOptionalStatisticsGroup."
::= { dhcpServerMIBGroups 4 } ::= { serverMIBGroups 4 }
dhcpStatisticsGroup OBJECT-GROUP dhcpOptionalStatisticsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dhcpStatMinArrivalInterval, dhcpStatMinArrivalInterval,
dhcpStatMaxArrivalInterval, dhcpStatMaxArrivalInterval,
dhcpStatLastArrivalTime, dhcpStatLastArrivalTime,
dhcpStatSumSquaresArrivalTime, dhcpStatSumSquaresArrivalTime,
dhcpStatMinResponseTime, dhcpStatMinResponseTime,
dhcpStatMaxResponseTime, dhcpStatMaxResponseTime,
dhcpStatSumResponseTime, dhcpStatSumResponseTime,
dhcpStatSumSquaresResponseTime dhcpStatSumSquaresResponseTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects belonging to the dhcpStatisticsGroup." "Objects belonging to the dhcpOptionalStatisticsGroup."
::= { dhcpServerMIBGroups 5 } ::= { serverMIBGroups 5 }
serverConfigurationGroup OBJECT-GROUP serverConfigurationGroup OBJECT-GROUP
OBJECTS { OBJECTS {
serverSubnet, serverSubnet,
serverSubnetMask, serverSubnetMask,
serverSubnetSharedNet, serverSubnetSharedNetwork,
serverRangeStart, serverRangeStart,
serverRangeEnd, serverRangeEnd,
serverRangeSubnet, serverRangeSubnetMask,
serverRangeInUse, serverRangeInUse,
serverRangeOutstandingOffers, serverRangeOutstandingOffers,
serverAddress, serverAddress,
serverAddressSubnet, serverAddressSubnetMask,
-- serverAddressRange, # /*duplicate*/
serverAddressRange, serverAddressRange,
serverAddressType, serverAddressType,
serverAddressTimeRemaining, serverAddressTimeRemaining,
serverAddressAllowedProtocol, serverAddressAllowedProtocol,
serverAddressServedProtocol, serverAddressServedProtocol,
serverAddressHardwareAddress, # /*renamed*/ serverAddressHardwareAddress,
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 29]
serverAddressClientId, serverAddressClientId,
serverAddressHostName, serverAddressHostName,
serverAddressDomainName serverAddressDomainName
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects belonging to the serverConfigurationGroup." "Objects belonging to the serverConfigurationGroup."
::= { dhcpServerMIBGroups 6 } ::= { serverMIBGroups 6 }
serverClientsGroup OBJECT-GROUP serverClientsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
serverClientHardwareAddress, # /*renamed*/ serverClientHardwareAddress,
serverClientSubnet, serverClientSubnetMask,
serverClientAddress, serverClientAddress,
serverClientLastRequestTime, serverClientLastRequestTime,
serverClientLastRequestType, serverClientLastRequestType,
serverClientLastResponseType serverClientLastResponseType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects belonging to the serverClientsGroup." "Objects belonging to the serverClientsGroup."
::= { dhcpServerMIBGroups 7 } ::= { serverMIBGroups 7 }
serverSharedNetworkObjectsGroup OBJECT-GROUP # /*new*/ serverSharedNetworkObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
serverSharedNetworkFreeAddrLowThreshold, serverSharedNetworkFreeAddressLowThreshold,
serverSharedNetworkFreeAddrHighThreshold, serverSharedNetworkFreeAddressHighThreshold,
serverSharedNetworkFreeAddrValue, serverSharedNetworkFreeAddressValue
serverSharedNetworkFreeAddrUnits
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"DHCP Server MIB objects used in shared networks." "DHCP Server MIB objects used in shared networks."
::= { dhcpServerMIBGroups 8 } ::= { serverMIBGroups 8 }
serverNotifyObjectsGroup OBJECT-GROUP # /*new*/ serverNotifyObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
serverNotifyDuplicateIPAddress, serverNotifyDuplicateIPAddress,
serverNotifyMACAddress, serverNotifyDuplicateMAC,
serverNotifyDuplicateIPAddressDetectedBy, serverNotifyClientDuplicateMAC,
serverNotifyServer, serverNotifyClientDuplicateIP,
serverNotifyServerType,
serverNotifyContestedIpAddress serverNotifyContestedIpAddress
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"DHCP Server MIB objects used in notifications." "DHCP Server MIB objects used in notifications."
::= { dhcpServerMIBGroups 9 } ::= { serverMIBGroups 9 }
serverNotifyicationsGroup NOTIFICATION-GROUP # /*new*/ serverNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
serverFreeAddressLow, serverFreeAddressLow,
serverFreeAddressHigh, serverFreeAddressHigh,
serverServerStart, serverServerStart,
serverServerStop, serverServerStop,
serverDNSQueueTooBig, serverDNSQueueTooBig,
serverOtherServerNotResponding, serverOtherServerNotResponding,
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 30]
serverDuplicateAddress, serverDuplicateAddress,
serverAddressConflict, serverAddressConflict,
serverOtherServerResponding, serverOtherServerResponding,
serverFailoverConfigMismatch serverFailoverConfigMismatch
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Notifyications which are implemented by the DHCP Server "Notifications that are implemented by the DHCP Server agent."
agent." ::= { serverMIBGroups 10 }
::= { dhcpServerMIBGroups 10 }
END END
4. Intellectual Property 4. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. standards-related documentation can be found in BCP-11.
Copies of claims of rights made available for publication and any Copies of claims of rights made available for publication and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use attempt made to obtain a general license or permission for the use of
of such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF Secretariat. specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights that may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
5. Notes 5. Notes
This section will be removed when this memo is published as an RFC. This section will be removed when this memo goes to Working Group
Last Call.
5.1. Issues 5.1. Issues
Not all of these issues have been resolved, even in the latest (-07)
draft. Some may become items for future study, while some will
probably be dropped.
o Are placeholders for expected DHCP option values a good or bad
idea?
o Ryan Troll proposed four or five traps that Nathan Lane o Ryan Troll proposed four or five traps that Nathan Lane
enthusiastically supported. If traps are to be included, that enthusiastically supported, but it has been difficult to achieve
should be done soon. any consensus (or, for that matter, much interest) in them.
o what is the best way to reset statistics? o What is the best way to reset counters and statistics? Is it
necessary to reset them at all? The -07 draft does not declare
any counters as read-write or read-create, primarily to avoid
these questions, as well as to provide fundamental security over
objects.
o do we need to reset them individually, as groups, or as a -- Do we need to reset them individually, as groups, or as a
whole? whole?
o we need a timestamp of when they were reset -- Do we need a timestamp of when they were reset?
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 31] o Should all invalid packets received be collapsed into a single
o should all invalid packets received be collapsed into a single
counter for each protocol type (BOOTP and DHCP), or broken out by counter for each protocol type (BOOTP and DHCP), or broken out by
type of error? type of error?
o if counted by error type, what is the set of errors that we o If counted by error type, what is the set of errors that we should
should use? use?
o perhaps we should develop a common vocabulary (and glossary) for o Perhaps we should develop a common vocabulary (and glossary) for
terms such as "abandoned" so that the objects defined and their terms such as "abandoned" so that the objects defined and their
descriptions aren't misinterpreted by implementers. descriptions aren't misinterpreted by implementers.
o do we need to be concerned about the potential size of some of o Do we need to be concerned about the potential size of some of the
the configuration data tables? Wouldn't it be better to maintain configuration data tables? Wouldn't it be better to maintain
counters for things like number of leases assigned than to expect counters for things like number of leases assigned than to expect
the management station to calculate the values by reading very the management station to calculate the values by reading very
large tables to count the number of leases in that state? large tables to count the number of leases in that state?
5.2. Changes from Prior Drafts 5.2. Changes from Prior Drafts
The "-01" revision removed the Server Identity section from the The "-01" revision removed the Server Identity section from the
proposed MIB, relying on the Application MIB to accomplish the same proposed MIB, relying on the Application MIB to accomplish the same
result. result.
The min/max (inter-arrival and response times) were changed to The min/max (inter-arrival and response times) were changed to
Unsigned32 so that they could be reset. Sum of inter-arrival and Unsigned32 so that they could be reset. Sums of inter-arrival and
response times was deleted since the management station can easily response times were deleted since the management station can easily
calculate them. The last arrival time objects were added. calculate them. The last arrival time objects were added.
The "-03" version incorporated the proposed configuration tables The "-03" version incorporated the proposed configuration tables
suggested by Ryan Troll of CMU. The "01" revision of this version suggested by Ryan Troll of CMU. The "01" revision of this version
added three elements to the server subnet table, number of added three elements to the server subnet table, number of
outstanding offers, number of addresses in use, and number of free outstanding offers, number of addresses in use, and number of free
addresses, as well as changing subnet address to subnet mask in the addresses, as well as changing subnet address to subnet mask in the
server address, server range, and client address tables. The client server address, server range, and client address tables. The client
MAC address element of the client address table was separated into a MAC address element of the client address table was separated into a
1-octet hardware type and a 16-octet client hardware address, 1-octet hardware type and a 16-octet client hardware address, causing
causing a renumbering of the elements in this table. Clarifying a renumbering of the elements in this table. Clarifying text was
text was added to several element descriptions, and limitations on added to several element descriptions, and limitations on values, and
values, and the reported value when the server did not support the the reported value when the server did not support the data element
data element were also specified. were also specified. This version also incorporated an address
change for one of the authors, revisions to standard text required by
The "-03b" version incorporated an address change for one of the the IETF, and some editorial clarifications.
authors, revisions to standard text required by the IETF, and some
editorial clarifications.
The "-04" version changed the maximum size of the object The "-04" version changed the maximum size of the object
serverAddressHostName from 64 to 255 octets, and added clarifying serverAddressHostName from 64 to 255 octets, and added clarifying
text to both that object and to serverAddressDomainName regarding text to both that object and to serverAddressDomainName regarding the
the practical values for the length of both objects. practical values for the length of both objects.
The "-05" version added a number of traps suggested by Kim Kinnear, The "-05" version added a number of traps suggested by Kim Kinnear,
made a number of small renaming and renumbering changes (annotated made a number of small renaming and renumbering changes (annotated in
in the MIB itself) and added the Shared Network concept to describe the MIB itself) and added the Shared Network concept to describe
shared network segments: several subnetworks that coexist on one shared network segments: several subnetworks that coexist on one
medium. This was done partly because the Address Range concept did medium. This was done partly because the Address Range concept did
not adequately describe the "scoping" of address pools as is common not adequately describe the "scoping" of address pools as is common
with many current server implementations. Also updated the authors with many current server implementations. Also updated the authors
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 32]
address and contact information, and incorporated a number of address and contact information, and incorporated a number of
corrections and amplifications suggested by various readers of the corrections and amplifications suggested by various readers of the "-
-04 draft, including a missing OID for serverNotifyObjects and a 04" draft, including a missing OID for serverNotifyObjects and a
syntax error for PhysicalAddress. syntax error for PhysicalAddress.
The "-05" draft closes several issues raised during peer review The "-06" version corrects a number of flaws reported by Rick Geesen
discussions on the DHC mailing list, incorporates several new and Jin Tao, mostly caused by typographical errors in the "-05"
elements, and makes a number of small revisions based on comments version as well as some unintentionally omitted text for
from reviewers. serverNotifyObjects.
The "-07" version changes BOOTP and DHCP statistics from mandatory to
optional, renaming object identifiers as required to match. All
objects, tables, and groups in previous drafts for Dynamic DNS
updating and Failover have been removed. All tables were carefully
examined to be certain that they really could be simply implemented.
Many items were renamed or renumbered. Placeholder definitions of
message types (both requests and responses) were added to support
DHCPFORCERENEW, DHCPQUERY, DHCPKNOWN, and DHCPUNKNOWN. A few [more]
typographical errors were found and fixed. Because of an error
posting the 07 draft to the editor's queue it was not accepted in
time for IETF-52 and is being submitted to the Internet-Drafts editor
with one change identified by Alan Hackert. Finally, some of the
initial text was brought in line with standard requirements for
Internet-Drafts.
6. Acknowledgements 6. Acknowledgements
This document is the result of work undertaken the by DHCP working This document is the result of work undertaken the by DHCP working
group. The authors would like to particularly acknowledge the group. The editors would like to particularly acknowledge the
development team from Carnegie-Mellon University whose work creating development team from Carnegie-Mellon University whose work creating
a private MIB for their DHCP server inspired the development of this a private MIB for their DHCP server inspired the development of this
proposal. In particular, many thanks to Ryan Troll who provided a proposal. In particular, many thanks to Ryan Troll who provided a
great deal of useful feedback during the development of this MIB. great deal of useful feedback during the development of this MIB.
Thanks to Kim Kinnear, Yannick Koehler, and Nathan Lane for their Thanks to Ryan Troll, Nathan Lane, Kim Kinnear, Yannick Koehler,
review, comments, and contributions. Nathan Lane, Rick Geesen, Jin Tao, James Brister, and Alan Hackert
for their review, comments, and contributions.
7. Security Considerations 7. Security Considerations
There are a number of management objects defined in this MIB that There are no management objects defined in this MIB that have a MAX-
have a MAX-ACCESS clause of read-write and/or read-create. Such ACCESS clause of read-write or read-create. Such objects may be
objects may be considered sensitive or vulnerable in some considered sensitive or vulnerable in some environments. The support
environments. The support for SET operations in a non-secure for SET operations in a non-secure environment without proper
environment without proper protection can have a negative effect on protection can have a negative effect on network operations. Many
network operations. network administrators object to settable management objects because
of the limited security features of SNMPv1 and SNMPv2. We have
chosen not to fight that battle in constructing this MIB.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is itself is secure (for example by using IPSEC), there is no control as
no control as to who on the secure network is allowed to access and to who on the secure network is allowed to access and GET / SET (read
GET/SET (read/change/create/delete) the objects in this MIB. / change / create / delete) the objects in this MIB.
It is recommended that the implementers consider the security SNMPv2 communities provide a minimal level of access control, but it
features as provided by the SNMPv3 framework. Specifically, the use is recommended that the implementers consider the security features
of the User-based Security Model RFC 2274 [RFC2274] and the View- as provided by the SNMPv3 framework. Specifically, the use of the
based Access Control Model RFC 2275 [RFC2275] is recommended. User-based Security Model [RFC2274] and the View-based Access Control
Model [RFC2275] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET (users) that have legitimate rights to indeed GET or SET
(change/create/delete) them. (change/create/delete) them.
Denial of Service attacks on a DHCP server are conceivable by
flooding the SNMP (sub-)agent with requests, tying up host system and
server resources processing SNMP messages. The authors know of no
way to wholly prevent such attacks, but have attempted to construct
relatively simple tables to minimize the work required to respond to
messages.
8. References 8. References
[DEN] Directory Enabled Networks Working Group, [DEN] Directory Enabled Networks Working Group,
http://www.universe.digex.net/~murchiso/den. http://www.universe.digex.net/~murchiso/den.
[RFC1902] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1123] R. Braden, "Requirements for Internet Hosts -- Application
"Structure of Management Information for Version 2 of the and Support," RFC 1123, October 1989.
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 33] [RFC2287] Krupczak, R., and J. Saperia, "Definitions of System-Level
Simple Network Management Protocol (SNMPv2)", RFC 1902, January Managed Objects for Applications," RFC 2287, February 1998.
1996.
[RFC1903] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC2578] Case, J., McCloghrie, K., Perkins, D., Rose, M.,
"Textual Conventions for Version 2 of the Simple Network Schoenwaelder, J., and S. Waldbusser, "Structure of Management
Management Protocol (SNMPv2)", RFC 1903, January 1996. Information for Version 2 of the Simple Network Management Protocol
(SNMPv2)," RFC 2578, April 1999.
[RFC1904] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC2579] Case, J., McCloghrie, K., Rose, M., Schoenwaelder, J., and
"Conformance Statements for Version 2 of the Simple Network S. Waldbusser, "Textual Conventions for Version 2 of the Simple
Management Protocol (SNMPv2)", RFC 1904, January 1996. Network Management Protocol (SNMPv2)," RFC 2579, April 1999.
[RFC2580] Case, J., McCloghrie, K., Rose, M., Schoenwaelder, J., and
S. Waldbusser, "Conformance Statements for Version 2 of the Simple
Network Management Protocol (SNMPv2)," RFC 2580, April 1999.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, BCP 14, March 1997. Requirement Levels," RFC 2119, BCP 14, March 1997.
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC [RFC2131] Droms, R., "Dynamic Host Configuration Protocol," RFC 2131,
2131, March 1997. March 1997.
[RFC2132] Alexander, S. and Droms, R., "DHCP Options and BOOTP [RFC2132] Alexander, S. and Droms, R., "DHCP Options and BOOTP Vendor
Vendor Extensions", RFC 2132, March 1997. Extensions," RFC 2132, March 1997.
[RFC2287] Krupczak, C. and Saperia, J., "Definitions of System- [RFC2287] Krupczak, C. and Saperia, J., "Definitions of System-Level
Level Managed Objects for Applications", RFC 2287, February Managed Objects for Applications," RFC 2287, February 1998.
1998.
<draft-ietf-dhc-pv4-reconfigure-06.txt>, Yves T'Joens and Christian
Hublet, Peter De Schrijver, "The DHCP Reconfigure Extension," July
2001
<draft-ietf-dhc-leasequery-02.txt>, Rich Woundy and Kim Kinnear,
"DHCP Lease Query," July 2001
9. Editors' Addresses 9. Editors' Addresses
Richard Barr Hibbs Richard Barr Hibbs
UltraDNS Corporation 952 Sanchez Street
800 North San Mateo Drive San Francisco, California 94114-3362
San Mateo, CA 94401-2261
USA USA
Phone: +1 650-227-2678 Phone: +1-(415)-648-3920
Fax: +1 650-227-2662 Fax: +1-(415)-648-9017
Email: rbhibbs@ultraDNS.com Email: rbhibbs@pacbell.net
Glenn Waters Glenn Waters
Nortel Networks Nortel Networks
310-875 Carling Avenue, 310-875 Carling Avenue,
Ottawa, Ontario K1S 5P1 Ottawa, Ontario K1S 5P1
Canada Canada
Phone: +1 613-765-0249 Phone: +1-(613)-798-4925
Email: gww@nortelnetworks.com Email: gww@NortelNetworks.com
10. Full Copyright Statement 10. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society, 2002.All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph are
are included on all such copies and derivative works. However, this included on all such copies and derivative works.However, this
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 34]
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 35]
 End of changes. 

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