draft-ietf-dhc-server-mib-04.txt   draft-ietf-dhc-server-mib-05.txt 
Network Working Group R. B. Hibbs Network Working Group R. B. Hibbs
INTERNET-DRAFT Pacific Bell INTERNET-DRAFT UltraDNS Corp.
Category: Standards Track G. Waters Category: Standards Track G. Waters
Nortel Networks Nortel Networks
October 1999 November 2000
Dynamic Host Configuration Protocol (DHCP) Server MIB Dynamic Host Configuration Protocol (DHCP) Server MIB
<draft-ietf-dhc-server-mib-04.txt> <draft-ietf-dhc-server-mib-05.txt>
Saved Thursday, October 21, 1999, 3:19 PM Monday, November 13, 2000, 3:50 PM
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 and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference 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/ietf/1id-abstracts.txt
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 To learn the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ds.internic.net (US East Coast), nic.nordu.net Directories on ds.internic.net (US East Coast), nic.nordu.net
(Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific
Rim). Rim).
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (2000). 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.
This version (the "-05" draft) closes several issues raised during Hibbs & Waters Expires: Nov 2000 + 6 months [Page 1]
peer review discussions on the DHC mailing list, incorporates
several new elements, and makes a number of small revisions based on
comments from reviewers. See Section 5.2 for a better description
of the changes.
Table of Contents Table of Contents
1. Introduction......................................................2 1. Introduction......................................................2
2. Overview..........................................................2 2. Overview..........................................................2
2.1. BOOTP and DHCP Counter Groups..................................3 2.1. BOOTP and DHCP Counter Groups.................................3
2.2. BOOTP and DHCP Statistics Group................................3 2.2. BOOTP and DHCP Statistics Group...............................3
2.3. Server Configuration Group.....................................4 2.3. Server Configuration Group....................................3
2.4. Response Times and ICMP Echo...................................5 2.4. Response Times and ICMP Echo..................................5
3. Definitions.......................................................5 3. Definitions.......................................................5
4. Intellectual Property............................................33 4. Intellectual Property............................................31
5. Notes............................................................33 5. Notes............................................................31
5.1. Issues........................................................33 5.1. Issues.......................................................31
5.2. Changes from Prior Drafts.....................................34 5.2. Changes from Prior Drafts....................................32
6. Acknowledgements.................................................34 6. Acknowledgements.................................................33
7. Security Considerations..........................................35 7. Security Considerations..........................................33
8. References.......................................................35 8. References.......................................................33
9. Editors' Addresses...............................................36 9. Editors' Addresses...............................................34
10. Full Copyright Statement........................................36 10. Full Copyright Statement........................................34
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 management protocols in the Internet community. In network management protocols in the Internet community. In
particular, it describes a set of extensions that DHCP and Bootstrap particular, it describes a set of extensions that DHCP and Bootstrap
Protocol (BOOTP) servers implement. Many implementations support Protocol (BOOTP) servers implement. Many implementations support
both DHCP and BOOTP within a single server and hence this memo both DHCP and BOOTP within a single server and hence this memo
describes the MIB for both DHCP and BOOTP servers. describes the MIB for both DHCP and BOOTP servers.
skipping to change at page 3, line 10 skipping to change at line 109
In the tradition of the Simple Network Management Protocol (SNMP) In the tradition of the Simple Network Management Protocol (SNMP)
the minimum number of objects possible are defined in this MIB, the minimum number of objects possible are defined in this MIB,
while still providing as rich a set of management information as while still providing as rich a set of management information as
possible. An object is left out of this MIB when it can be derived possible. An object is left out of this MIB when it can be derived
from other objects that are provided. Further to the tradition of from other objects that are provided. Further to the tradition of
the SNMP, computationally intense operations are left to the domain the SNMP, computationally intense operations are left to the domain
of the management station. Thus, this MIB provides a set of objects of the management station. Thus, this MIB provides a set of objects
from which other management information may be derived. from which other management information may be derived.
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 2]
The examples provided in the following sections are not meant to be The examples provided in the following sections are not meant to be
comprehensive, they are merely illustrative of the potential uses of comprehensive, they are merely illustrative of the potential uses of
the objects defined by this MIB. the objects defined by this MIB.
2.1. BOOTP and DHCP Counter Groups 2.1. BOOTP and DHCP Counter Groups
This section describes some of the management information that may This section describes some of the management information that may
be derived from the objects provided in the counter groups. 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
skipping to change at page 4, line 17 skipping to change at line 167
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 bootStatistics
group are used instead of the objects from dhcpStatistics group. group are used instead of the objects from dhcpStatistics group.
2.3. 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
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 3]
the configuration information is static (e.g.: a statically 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. Mechanisms outside of the SNMP are currently in use configuration. Mechanisms outside of the SNMP are currently in use
(e.g.: vendor defined solutions) and are being standardized (e.g.: (e.g.: vendor defined solutions) and are being standardized (e.g.:
the Directory Enabled Networks [DEN] initiative) to update a the Directory Enabled Networks [DEN] initiative) to update a
server's configuration. server's configuration.
The configuration information provides a minimal set of information The configuration information provides a minimal set of information
skipping to change at page 5, line 18 skipping to change at line 223
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 (value of none(1)), or, whether
BOOTP or DHCP was used to allocate the address. BOOTP or DHCP was used to allocate the address.
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 4]
2.4. 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 is in use before assigning it. Some servers choose not to address is in use before assigning it. Some servers choose not to
perform this check, letting the client determine for itself if the perform this check, letting the client determine for itself if the
address is in use. Other servers perform an ICMP echo (Ping) just address is in use. Other servers perform an ICMP echo (Ping) just
prior to assigning an address. Servers that perform a Ping before prior to assigning an address. Servers that perform a Ping before
responding to a DHCPDISCOVER should not include in the response time responding to a DHCPDISCOVER should not include in the response time
the time from when the Ping was transmitted until the time that the time from when the Ping was transmitted until the time that
either a response was received or that the server timed out waiting either a response was received or that the server timed out waiting
skipping to change at page 5, line 46 skipping to change at line 252
IMPORTS IMPORTS
Counter64, Counter32, Gauge32, Unsigned32, mib-2, Counter64, Counter32, Gauge32, Unsigned32, mib-2,
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, IpAddress MODULE-IDENTITY, 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, -- /*modified*/ MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP #
NOTIFICATION-GROUP -- /*new*/ /*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*/ dhcpServerMIB MODULE-IDENTITY # /*renamed*/
LAST-UPDATED "9910060000Z" LAST-UPDATED "9910060000Z"
ORGANIZATION "IETF DHCP Working Group" ORGANIZATION "IETF DHCP Working Group"
CONTACT-INFO CONTACT-INFO
" Richard Barr Hibbs " Richard Barr Hibbs
Postal: Pacific Bell Postal: UltraDNS Corporation
666 Folsom Street, Room 1225 800 North San Mateo Drive
San Francisco, CA 94107-1384 San Mateo, CA 94401-2261
USA USA
Tel: +1 415-545-1576 Tel: +1 650-227-2678
Fax: +1 415-543-3539 Fax: +1 650-227-2662
Email: rbhibbs@pacbell.com Email: rbhibbs@ultraDNS.com
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-798-4925 Tel: +1 613-765-0249
Email: gww@nortelnetworks.com" Email: gww@nortelnetworks.com"
DESCRIPTION DESCRIPTION
"The MIB module for entities implementing the server side of the "The MIB module for entities implementing the server side of
the
Bootstrap Protocol (BOOTP) and the Dynamic Host Configuration Bootstrap Protocol (BOOTP) and the Dynamic Host Configuration
protocol (DHCP) for Internet Protocol version 4(IPv4). This MIB protocol (DHCP) for Internet Protocol version 4(IPv4). This
does not include support for Dynamic DNS (DDNS) updating nor for MIB
does not include support for Dynamic DNS (DDNS) updating nor
for
the DHCP Failover Protocol." the DHCP Failover Protocol."
::= { dhcp 1 } ::= { dhcp 1 }
dhcpServerMIBObjects OBJECT-IDENTITY -- /*renamed*/ dhcpServerMIBObjects 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 } -- /*renamed*/ ::= { dhcpServerMIB 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 } -- /*renamed*/ ::= { dhcpServerMIBObjects 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 } -- /*renamed*/ ::= { dhcpServerMIBObjects 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 } -- /*renamed*/ ::= { dhcpServerMIBObjects 3 }
bootpStatistics OBJECT-IDENTITY bootpStatistics OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Group of objects that measure various BOOTP statistics." "Group of objects that measure various BOOTP statistics."
::= { dhcpServerMIBObjects 4 } -- /*renamed*/ ::= { dhcpServerMIBObjects 4 }
dhcpStatistics OBJECT-IDENTITY dhcpStatistics OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Group of objects that measure various DHCP statistics." "Group of objects that measure various DHCP statistics."
::= { dhcpServerMIBObjects 5 } -- /*renamed*/ ::= { dhcpServerMIBObjects 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."
::= { dhcpServerMIBObjects 6 } -- /*renamed*/
bootpClients OBJECT-IDENTITY Hibbs & Waters Expires: Nov 2000 + 6 months [Page 6]
STATUS current ::= { dhcpServerMIBObjects 6 }
DESCRIPTION
"Objects that map bootp clients to IP addresses."
::= { dhcpServerMIBObjects 7 } -- /*renamed*/
dhcpClients OBJECT-IDENTITY clientGroup OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects that map DHCP clients to IP addresses." "Objects that map DHCP and BOOTP clients to IP addresses."
::= { dhcpServerMIBObjects 8 } -- /*renamed*/ ::= { dhcpServerMIBObjects 7 }
-- Textual conventions defined by this memo -- Textual conventions defined by this memo
DhcpTimeInterval ::= TEXTUAL-CONVENTION DhcpTimeInterval ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of milli-seconds that has elapsed since some epoch. "The number of milli-seconds that has elapsed since some
epoch.
Systems that cannot measure events to the milli-second 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 SYNTAX Unsigned32
PhysicalAddress ::= TEXTUAL-CONVENTION -- /*new*/
SYNTAX OCTET STRING (SIZE (1..17)) PhysicalAddress ::= TEXTUAL-CONVENTION
DISPLAY-HINT "t,xx[:xx...]" DISPLAY-HINT "t,xx[:xx...]"
STATUS current STATUS current
REFERENCE "RFC 2131" REFERENCE "RFC 2131"
DESCRIPTION DESCRIPTION
"A Layer 1 address which includes the hardware type "A harware type and hardware address. This object is
space as well as the usual MAC address. This object is
encoded as encoded as
<type><address> <type><address>
where where
<type> is the value of the hardware type space <type> is the value of the hardware type space
field, as used in ARP (e.g., 1 for Ethernet, field, as used in ARP (e.g., 1 for Ethernet,
6 for token ring). IANA maintains the list of 6 for token ring). IANA maintains the list of
registered numbers for this field. 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 <address> is the hardware address of the MAC (Media
Adapter Card) interface, of size <length> Adapter Card) interface. The value for this field
octets. comes from the 'chaddr' field in the BOOTP packet
This encoding is intended to mirror the representation header."
of MAC addresses in DHCP." SYNTAX OCTET STRING (SIZE (0 | 2..17))
-- 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 This string MUST contain only printable NVT ASCII
characters." 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
skipping to change at page 9, line 4 skipping to change at line 412
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 -- bootpCounters Group
bootpCountRequests OBJECT-TYPE bootpCountRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets received that contain a Message Type of "The number of packets received that contain a Message Type
of
1 (BOOTREQUEST) in the first octet and do not contain option 1 (BOOTREQUEST) in the first octet and do not contain option
number 53 (DHCP Message Type) in the options." number 53 (DHCP Message Type) in the options."
::= { bootpCounters 1 } ::= { bootpCounters 1 }
bootpCountInvalids OBJECT-TYPE bootpCountInvalids OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets received that do not contain a Message "The number of packets received that do not contain a Message
skipping to change at page 9, line 45 skipping to change at line 455
::= { bootpCounters 3 } ::= { bootpCounters 3 }
bootpCountDroppedUnknownClients OBJECT-TYPE bootpCountDroppedUnknownClients OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of BOOTP packets dropped due to the server not "The number of BOOTP packets dropped due to the server not
recognizing or not providing service to the hardware address recognizing or not providing service to the hardware address
received in the incoming packet." received in the incoming packet."
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 8]
::= { bootpCounters 4 } ::= { bootpCounters 4 }
bootpCountDroppedNotServingSubnet OBJECT-TYPE bootpCountDroppedNotServingSubnet OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of BOOTP packets dropped due to the server not "The number of BOOTP packets dropped due to the server not
being configured or not otherwise able to serve addresses on being configured or not otherwise able to serve addresses on
the subnet from which this message was received." the subnet from which this message was received."
skipping to change at page 10, line 50 skipping to change at line 513
"The number of DHCPDECLINE (option 53 with value 4) packets "The number of DHCPDECLINE (option 53 with value 4) packets
received." received."
::= { 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 } ::= { dhcpCounters 5 }
dhcpCountInvalids OBJECT-TYPE dhcpCountInvalids 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 received whose DHCP message type "The number of DHCP packets received whose DHCP message type
(i.e., option number 53) is not understood or handled by the (i.e., option number 53) is not understood or handled by the
skipping to change at page 12, line 4 skipping to change at line 572
hardware address received in the incoming packet." hardware address received in the incoming packet."
::= { dhcpCounters 10 } ::= { dhcpCounters 10 }
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 11 }
-- bootpStatistics group -- bootpStatistics group
bootpStatMinArrivalInterval OBJECT-TYPE bootpStatMinArrivalInterval OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum amount of time between receiving two BOOTP "The minimum amount of time between receiving two BOOTP
messages. A message is received at the server when the server messages. A message is received at the server when the
is able to begin processing the message. This typically occurs server
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 } ::= { bootpStatistics 1 }
bootpStatMaxArrivalInterval OBJECT-TYPE bootpStatMaxArrivalInterval OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum amount of time between receiving two BOOTP "The maximum amount of time between receiving two BOOTP
messages. A message is received at the server when the server messages. A message is received at the server when the
is able to begin processing the message. This typically occurs server
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 } ::= { bootpStatistics 2 }
bootpStatLastArrivalTime 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 BOOTP 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 valid no messages have been received, value to change. If valid no messages have been received,
then this object contains a date and time that is all zero." then
this object contains a date and time that is all zero."
::= { bootpStatistics 3 } ::= { bootpStatistics 3 }
bootpStatSumSquaresArrivalTime 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 BOOTP 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 variance micro-seconds. This value may be used to compute the
and standard deviation of the BOOTP arrival times. Note that a variance
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 11]
and standard deviation of the BOOTP arrival times. Note that
a
micro-second resolution of this object requires a clock micro-second resolution of this object requires a clock
resolution to the milli-second since the square of a milli- resolution to the milli-second since the square of a milli-
second value produces a value with micro-second resolution." second value produces a value with micro-second resolution."
::= { bootpStatistics 4 } ::= { bootpStatistics 4 }
bootpStatMinResponseTime OBJECT-TYPE bootpStatMinResponseTime OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The smallest time interval measured as the difference between "The smallest time interval measured as the difference
the arrival of a BOOTP 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 internally. operating system may still have the message queued
internally.
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."
::= { bootpStatistics 5 } ::= { bootpStatistics 5 }
bootpStatMaxResponseTime OBJECT-TYPE bootpStatMaxResponseTime OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-write MAX-ACCESS read-write
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 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 internally. operating system may still have the message queued
internally.
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."
::= { bootpStatistics 6 } ::= { bootpStatistics 6 }
bootpStatSumResponseTime OBJECT-TYPE bootpStatSumResponseTime OBJECT-TYPE
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 12]
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 where "The sum of the response time intervals in milli-seconds
a response time interval is measured as the difference between where
the arrival of a BOOTP message at the server and the successful a response time interval is measured as the difference
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 internally. operating system may still have the message queued
internally.
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."
::= { bootpStatistics 7 } ::= { bootpStatistics 7 }
bootpStatSumSquaresResponseTime OBJECT-TYPE bootpStatSumSquaresResponseTime 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 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
skipping to change at page 15, line 4 skipping to change at line 731
DESCRIPTION DESCRIPTION
"The sum of the squared BOOTP 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 BOOTP response times. Note that a standard deviation of the BOOTP response times. Note that a
micro-second resolution of this object requires a clock micro-second resolution of this object requires a clock
resolution to the milli-second since the square of a milli- resolution to the milli-second since the square of a milli-
second value produces a value with micro-second resolution." second value produces a value with micro-second resolution."
::= { bootpStatistics 8 } ::= { bootpStatistics 8 }
-- dhcpStatistics group -- dhcpStatistics group
dhcpStatMinArrivalInterval OBJECT-TYPE dhcpStatMinArrivalInterval OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum amount of time between receiving two DHCP "The minimum amount of time between receiving two DHCP
messages. A message is received at the server when the server messages. A message is received at the server when the
server
is able to begin processing the message. This typically is able to begin processing the message. This typically
occurs 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 } ::= { dhcpStatistics 1 }
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 13]
dhcpStatMaxArrivalInterval OBJECT-TYPE dhcpStatMaxArrivalInterval OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum amount of time between receiving two DHCP
"The maximum amount of time between receiving two DHCP messages. messages. A message is received at the server when the
A message is received at the server when the server is able to server
begin processing the message. This typically occurs immediately is able to begin processing the message. This typically
after the message is read into server memory. If no messages occurs
have been received, then this object contains a zero value." immediately after the message is read into server memory. If
no messages have been received, then this object contains a
zero value."
::= { dhcpStatistics 2 } ::= { dhcpStatistics 2 }
dhcpStatLastArrivalTime 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 DHCP 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 no valid messages have been received, then value to change. If no valid messages have been received,
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 } ::= { dhcpStatistics 3 }
dhcpStatSumSquaresArrivalTime 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 DHCP 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 variance micro-seconds. This value may be used to compute the
and standard deviation of the DHCP arrival times. Note that a variance
and standard deviation of the DHCP arrival times. Note that
a
micro-second resolution of this object requires a clock micro-second resolution of this object requires a clock
resolution to the milli-second since the square of a milli- resolution to the milli-second since the square of a milli-
second value produces a value with micro-second resolution." second value produces a value with micro-second resolution."
::= { dhcpStatistics 4 } ::= { dhcpStatistics 4 }
dhcpStatMinResponseTime OBJECT-TYPE dhcpStatMinResponseTime OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The smallest time interval measured as the difference between "The smallest time interval measured as the difference
the arrival of a DHCP 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 internally. operating system may still have the message queued
The operating system queue time is not to be considered as part internally.
of the response time. Invalid messages do not cause this value
to change. If no valid messages have been received, then this Hibbs & Waters Expires: Nov 2000 + 6 months [Page 14]
The operating system queue time is not to be considered as
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."
::= { dhcpStatistics 5 } ::= { dhcpStatistics 5 }
dhcpStatMaxResponseTime OBJECT-TYPE dhcpStatMaxResponseTime OBJECT-TYPE
SYNTAX DhcpTimeInterval SYNTAX DhcpTimeInterval
MAX-ACCESS read-write MAX-ACCESS read-write
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 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 internally. operating system may still have the message queued
The operating system queue time is not to be considered as part internally.
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."
::= { dhcpStatistics 6 } ::= { dhcpStatistics 6 }
dhcpStatSumResponseTime OBJECT-TYPE 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 where "The sum of the response time intervals in milli-seconds
a response time interval is measured as the difference between where
the arrival of a DHCP message at the server and the successful a response time interval is measured as the difference
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 internally. operating system may still have the message queued
The operating system queue time is not to be considered as part internally.
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."
::= { dhcpStatistics 7 } ::= { dhcpStatistics 7 }
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 15]
dhcpStatSumSquaresResponseTime 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 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 DHCP response times. Note that a standard deviation of the DHCP response times. Note that
a
micro-second resolution of this object requires a clock micro-second resolution of this object requires a clock
resolution to the milli-second since the square of a milli- resolution to the milli-second since the square of a milli-
second value produces a value with micro-second resolution." second value produces a value with micro-second resolution."
::= { dhcpStatistics 8 } ::= { dhcpStatistics 8 }
-- serverConfiguration group -- serverConfiguration group
serverSubnetTable OBJECT-TYPE serverSubnetTable OBJECT-TYPE
SYNTAX SEQUENCE OF ServerSubnetEntry SYNTAX SEQUENCE OF ServerSubnetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 18, line 16 skipping to change at line 902
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 serverSubnetSharedNet IpAddress,
serverSubnetConfiguredAddresses Unsigned32,
serverSubnetAvailableAddresses Unsigned32,
serverSubnetFreeAddressLowThreshold Unsigned32,
serverSubnetFreeAddressHighThreshold Unsigned32
} }
serverSubnet OBJECT-TYPE serverSubnet 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 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 serverSubnetSharedNet OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
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 IP address of another subnet that is on the same shared
media as this subnet. The address of the shared subnet MUST media as this subnet. The address of the shared subnet MUST
also be configured on this server. The address 0.0.0.0 should also be configured on this server. The address 0.0.0.0
should
be used if this subnet is not shared." be used if this subnet is not shared."
::= { serverSubnetEntry 3 } ::= { serverSubnetEntry 3 }
serverSubnetConfiguredAddresses 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
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The low threshold 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
serverSubnetFreeAddressLowThreshold event is generated
for this shared network. No more
serverSubnetFreeAddressLowThreshold events will
be generated for this subnet during this execution of
the DHCP server until the value for available free addresses
has
exceeded the value of serverSubnetFreeAddressHighThreshold.
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]
serverSubnetFreeAddressHighThreshold OBJECT-TYPE # /*new*/
SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The high threshold for available free addresses in this
subnet.
If a serverSubnetFreeAddressLowThreshold event
has been generated for this subnet, and the value for
available free addresses has exceeded the value of
serverSubnetFreeAddressHighThreshold, then a
serverFreeAddressessHigh event will be generated. No more
serverFreeAddressessHigh events will be generated for this
subnet during this execution of the DHCP server until
the value for available free addresses becomes equal to or
less
than the value of serverSubnetFreeAddressHighThreshold.
This value may be expressed as either an absolute value or a
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 2 }
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 {
skipping to change at page 19, line 26 skipping to change at line 1034
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 not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the first address in the range. The value of "The IP address of the first address in the range. The value
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 of "The IP address of the last address in the range. The value
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 }
serverRangeSubnetMask OBJECT-TYPE serverRangeSubnetAddress 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 any client offered "The subnet address
an address from 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 not use. This number includes those addresses whose lease has
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 is "The number of outstanding DHCPOFFER messages for this range
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 the yet received a DHCPREQUEST message from the client nor has
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 }
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 "A list of addresses that are known by this server. The list
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 19]
MUST contain addresses that have not expired. The list MUST MUST contain addresses that have not expired. The list MUST
NOT contain addresses that have never been assigned by the NOT contain addresses that have never been assigned by the
server UNLESS the lease is pre-configured in the server (e.g., server UNLESS the lease is pre-configured in the server
(e.g.,
a static lease on a subnet)." a static lease on a subnet)."
::= { serverConfiguration 3 } ::= { 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,
serverAddressMacAddress OCTET STRING, serverAddressHardwareAddress PhysicalAddress,
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 offered "The subnet mask (DHCP option 1) provided to the client
this address. The subnet, resulting from logically ANDing the offered
subnet mask with the entry's IP address, must be configured on this address. The subnet, resulting from logically ANDing
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), configuration-reserved(3),
skipping to change at page 22, line 29 skipping to change at line 1197
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 this "The type of protocol that is allowed to be used to serve
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)."
::= { 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 -- /*renamed*/ serverAddressHardwareAddress OBJECT-TYPE
SYNTAX PhysicalAddress -- /*modified*/ 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 has "The hardware type and hardware address of the client that
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 BOOTP contains the hardware type from the 'htype' field of the
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 lease. "The client-id of the client that has been assigned this
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 e,[pty option) when the lease was assigned. This object may be
if the lease has not been previously assigned or if the client- empty
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 (0..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 use, "The host name (DHCP option 12) the client is configured to
use,
or if no host name was configured then the host name that the or if no host name was configured then the host name that the
client supplied when requesting an address." client supplied when requesting an address. While this
object
has a maximum size of 255 octets, a Fully-Qualified Domain
Name
(FQDN) consisting of a Host Name part and a Domain Name part
is
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 (0..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
this object has a maximum size of 255 octets, a Fully-
Qualified
Domain Name (FQDN) consisting of a Host Name part and a
Domain
Name part is currently limited to 255 octets, less the
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 }
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 the clients may be found by indexing into the about
serverAddressTable using the serverClientAddress object. This the clients may be found by indexing into the
table is indexed first by the MAC address of the client and then serverAddressTable
by the subnet address on which the client resides. The subnet using the serverClientAddress object. This table is indexed
is included as an index since a MAC address is only guaranteed first by the physical address of the client and then by the
to be unique within a subnet (i.e., a MAC address is not subnet
globally unique)." address on which the client resides. The subnet is included
::= { bootpClients 1 } as
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, -- /*renamed*/ serverClientHardwareAddress,
serverClientSubnet serverClientSubnetMask
} }
DESCRIPTION DESCRIPTION
"A logical row in the serverClientTable. An entry in this table "A logical row in the serverClientTable. An entry in this
may be a client that requested an address but was refused (e.g., table
not authorized). Servers MAY track these types of clients if may be a client that requested an address but was refused
desired and may choose to remove such client entries using a (e.g., not authorized). Servers MAY track these types of
server defined algorithm. As an example, a server may choose to clients if desired and may choose to remove such client
keep client request that does not map to an address for a one entries
hour time period before removing that entry from this table." using a server defined algorithm. As an example, a server
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."
::= { serverClientTable 1 } ::= { serverClientTable 1 }
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 23]
ServerClientEntry ::= SEQUENCE { ServerClientEntry ::= SEQUENCE {
serverClientHardwareAddress PhsicalAddress -- /*renamed*/ serverClientHardwareAddress PhsicalAddress
serverClientSubnetMask IpAddress, serverClientSubnetMask IpAddress,
serverClientAddress IpAddress, serverClientAddress IpAddress,
serverClientLastRequestTime DateAndTime, serverClientLastRequestTime DateAndTime,
serverClientLastRequestType INTEGER, serverClientLastRequestType INTEGER,
serverClientLastResponseType INTEGER serverClientLastResponseType INTEGER
} }
serverClientHardwareAddress OBJECT-TYPE -- /*renamed*/ serverClientHardwareAddress OBJECT-TYPE
SYNTAX PhysicalAddress -- /*modified*/ 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 has "The hardware type and hardware address of the client that
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 BOOTP contains the hardware type from the 'htype' field of the
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." from the 'chaddr' field of the BOOTP packet. This value of
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." -- /*modified*/ serverClientAddress."
::= { serverClientEntry 2 } ::= { serverClientEntry 2 }
serverClientAddress OBJECT-TYPE serverClientAddress 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 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."
skipping to change at page 25, line 47 skipping to change at line 1389
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time when the last request was received." "The time when the last request was received."
::= { serverClientEntry 4 } ::= { serverClientEntry 4 }
serverClientLastRequestType OBJECT-TYPE serverClientLastRequestType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
dhcpdiscover(1), dhcpdiscover(1),
bootp(2), bootp(2),
dhcprequest(3), dhcprequest(3),
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 24]
dhcpdecline(4), dhcpdecline(4),
unknown(5), unknown(5),
dhcprelease(7), dhcprelease(7),
dhcpinform(8) dhcpinform(8)
} }
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 that was received for this
client." client."
skipping to change at page 26, line 26 skipping to change at line 1420
} }
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 that was sent to this client."
::= { 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 # /*new*/
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 which was found to be a duplicate."
::= { serverNotifyObjects 1 } ::= { serverNotifyObjects 1 }
serverNotifyMACAddress OBJECT-TYPE -- /*new*/ serverNotifyMACAddress OBJECT-TYPE # /*new*/
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 to be detected." address to be detected."
::= { serverNotifyObjects 2 } ::= { serverNotifyObjects 2 }
serverNotifyServer OBJECT-TYPE -- /*new*/ serverNotifyServer OBJECT-TYPE # /*new*/
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 of a server with which the DHCP server
is attempting to communicate." is attempting to communicate."
::= { serverNotifyObjects 3 } ::= { serverNotifyObjects 3 }
serverNotifyServerType OBJECT-TYPE -- /*new*/ serverNotifyDuplicateIPAddressDetectedBy OBJECT-TYPE # /*new*/
SYNTAX INTEGER {
dns(1),
dhcp(2),
ldap(3)
}
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The type of server with which the DHCP server is attempting
to communicate (corresponds to the serverNotifyServer
object.)"
::= { serverNotifyObjects 4 }
serverNotifyDuplicateIPAddressDetectedBy OBJECT-TYPE -- /*new*/ Hibbs & Waters Expires: Nov 2000 + 6 months [Page 25]
SYNTAX INTEGER {dhcpClient(1), dhcpServer(2)} SYNTAX INTEGER {dhcpClient(1), dhcpServer(2)}
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For a serverDuplicateAddress notification, this object "For a serverDuplicateAddress notification, this
indicates whether the client or server detected the object indicates whether the client or server detected
condition. A DHCP server would typically detect duplicates the condition. DHCP servers detect a duplicate address
by unexpected ICMPECHO replies, while a client would by an unexpected reply to an ICMPECHOREQUEST (ping)
typically use a gratuitous ARP for the same purpose and message, while DHCP clients detect duplicates by an
indicate this to the server by a DHCPDECLINE message." unexpected reply to a gratuitous ARP message, and report
this condition to a DHCP server through a DHCPDECLINE
message."
::= { serverNotifyObjects 5 } ::= { serverNotifyObjects 5 }
serverNotifyContestedIpAddress OBJECT-TYPE -- /*new*/ serverNotifyContestedIpAddress OBJECT-TYPE # /*new*/
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address for which ownership is claimed by two or "The IP address for which ownership is claimed by two or
more DHCP servers." more DHCP servers."
::= { serverNotifyObjects 6 } ::= { serverNotifyObjects 6 }
-- Notifications -- Notifications
dhcpServerMIBNotificationPrefix OBJECT IDENTIFIER -- /*new*/ dhcpServerMIBNotificationPrefix OBJECT IDENTIFIER # /*new*/
::= { dhcpServerMIB 2 } -- /*renamed*/ ::= { dhcpServerMIB 2 } # /*renamed*/
dhcpServerMIBNotifications OBJECT IDENTIFIER -- /*new*/ dhcpServerMIBNotifications OBJECT IDENTIFIER # /*new*/
::= { dhcpServerMIBNotificationPrefix 0 } ::= { dhcpServerMIBNotificationPrefix 0 }
serverFreeAddressLow NOTIFICATION-TYPE -- /*new*/ serverFreeAddressLow NOTIFICATION-TYPE # /*new*/
OBJECTS { OBJECTS {
serverSharedNetworkFreeAddressLowThreshold, serverSharedNetworkFreeAddressLowThreshold,
serverSharedNetworkFreeAddressValue, serverSharedNetworkFreeAddressValue,
serverSharedNetworkFreeAddressUnits 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 the addresses for a particular shared network has fallen below
the
value of serverSharedNetworkFreeAddressLowThreshold for that value of serverSharedNetworkFreeAddressLowThreshold for that
shared network." shared
network."
::= { dhcpServerMIBNotifications 1 } ::= { dhcpServerMIBNotifications 1 }
serverFreeAddressHigh NOTIFICATION-TYPE -- /*new*/ serverFreeAddressHigh NOTIFICATION-TYPE # /*new*/
OBJECTS { OBJECTS {
serverSharedNetworkFreeAddressHighThreshold, serverSharedNetworkFreeAddressHighThreshold,
serverSharedNetworkFreeAddressValue, serverSharedNetworkFreeAddressValue,
serverSharedNetworkFreeAddressUnits 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 } ::= { dhcpServerMIBNotifications 2 }
serverServerStart NOTIFICATION-TYPE -- /*new*/ serverServerStart NOTIFICATION-TYPE # /*new*/
OBJECTS { serverNotifyServerType } OBJECTS { serverNotifyServerType }
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 } ::= { dhcpServerMIBNotifications 3 }
serverServerStop NOTIFICATION-TYPE -- /*new*/ serverServerStop NOTIFICATION-TYPE # /*new*/
OBJECTS { serverNotifyServerType } OBJECTS { serverNotifyServerType }
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 } ::= { dhcpServerMIBNotifications 4 }
serverDuplicateAddress NOTIFICATION-TYPE -- /*new*/ serverDuplicateAddress NOTIFICATION-TYPE # /*new*/
OBJECTS { OBJECTS {
serverNotifyDuplicateIPAddress, serverNotifyDuplicateIPAddress,
serverNotifyMACAddress, serverNotifyMACAddress,
serverNotifyDuplicateIPAddressDetectedBy serverNotifyDuplicateIPAddressDetectedBy
} }
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 is client may have sent a DHCPDECLINE back to the server; this
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 the address was in use. In either case, the DHCP server marks
the
IP address as unavailable for leasing to clients. The IP address as unavailable for leasing to clients. The
serverNotifyDuplicateIPAddressDetectedBy object indicates serverNotifyDuplicateIPAddressDetectedBy object indicates
whether the client or server detected this condition." whether the client or server detected this condition."
::= { dhcpServerMIBNotifications 7 } ::= { dhcpServerMIBNotifications 7 }
-- Conformance -- Conformance
dhcpServerMIBConformance OBJECT-IDENTITY -- /*renamed*/ dhcpServerMIBConformance OBJECT-IDENTITY # /*renamed*/
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*/ ::= { dhcpServerMIB 3 } # /*renamed*/
dhcpServerMIBCompliances OBJECT IDENTIFIER dhcpServerMIBCompliances OBJECT IDENTIFIER
::= { dhcpServerMIBConformance 1 } -- /*renamed*/ ::= { dhcpServerMIBConformance 1 } # /*renamed*/
dhcpServerMIBGroups OBJECT IDENTIFIER dhcpServerMIBGroups OBJECT IDENTIFIER
::= { dhcpServerMIBConformance 2 } -- /*renamed*/ ::= { dhcpServerMIBConformance 2 } # /*renamed*/
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 27]
-- Compliance groups -- Compliance groups
dhcpServerMIBCompliance MODULE-COMPLIANCE dhcpServerMIBCompliance MODULE-COMPLIANCE
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
serverSystemGroup, serverSystemGroup,
bootpCountersGroup, bootpCountersGroup,
dhcpCountersGroup, dhcpCountersGroup,
bootpStatisticsGroup, bootpStatisticsGroup,
dhcpStatisticsGroup, dhcpStatisticsGroup,
skipping to change at page 30, line 30 skipping to change at line 1620
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 } ::= { dhcpServerMIBGroups 3 }
bootpStatisticsGroup OBJECT-GROUP bootpStatisticsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
bootpStatMinArrivalInterval, bootpStatMinArrivalInterval,
bootpStatMaxArrivalInterval, bootpStatMaxArrivalInterval,
skipping to change at page 31, line 29 skipping to change at line 1672
serverSubnet, serverSubnet,
serverSubnetMask, serverSubnetMask,
serverSubnetSharedNet, serverSubnetSharedNet,
serverRangeStart, serverRangeStart,
serverRangeEnd, serverRangeEnd,
serverRangeSubnet, serverRangeSubnet,
serverRangeInUse, serverRangeInUse,
serverRangeOutstandingOffers, serverRangeOutstandingOffers,
serverAddress, serverAddress,
serverAddressSubnet, serverAddressSubnet,
-- serverAddressRange, -- /*duplicate*/ -- serverAddressRange, # /*duplicate*/
serverAddressRange, serverAddressRange,
serverAddressType, serverAddressType,
serverAddressTimeRemaining, serverAddressTimeRemaining,
serverAddressAllowedProtocol, serverAddressAllowedProtocol,
serverAddressServedProtocol, serverAddressServedProtocol,
serverAddressHardwareAddress, -- /*renamed*/ serverAddressHardwareAddress, # /*renamed*/
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 } ::= { dhcpServerMIBGroups 6 }
serverClientsGroup OBJECT-GROUP serverClientsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
serverClientHardwareAddress, -- /*renamed*/ serverClientHardwareAddress, # /*renamed*/
serverClientSubnet, serverClientSubnet,
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 } ::= { dhcpServerMIBGroups 7 }
serverSharedNetworkObjectsGroup OBJECT-GROUP -- /*new*/ serverSharedNetworkObjectsGroup OBJECT-GROUP # /*new*/
OBJECTS { OBJECTS {
serverSharedNetworkFreeAddrLowThreshold, serverSharedNetworkFreeAddrLowThreshold,
serverSharedNetworkFreeAddrHighThreshold, serverSharedNetworkFreeAddrHighThreshold,
serverSharedNetworkFreeAddrValue, serverSharedNetworkFreeAddrValue,
serverSharedNetworkFreeAddrUnits 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 } ::= { dhcpServerMIBGroups 8 }
serverNotifyObjectsGroup OBJECT-GROUP -- /*new*/ serverNotifyObjectsGroup OBJECT-GROUP # /*new*/
OBJECTS { OBJECTS {
serverNotifyDuplicateIPAddress, serverNotifyDuplicateIPAddress,
serverNotifyMACAddress, serverNotifyMACAddress,
serverNotifyDuplicateIPAddressDetectedBy, serverNotifyDuplicateIPAddressDetectedBy,
serverNotifyServer, serverNotifyServer,
serverNotifyServerType, 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 } ::= { dhcpServerMIBGroups 9 }
serverNotifyicationsGroup NOTIFICATION-GROUP -- /*new*/ serverNotifyicationsGroup NOTIFICATION-GROUP # /*new*/
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 "Notifyications which are implemented by the DHCP Server
agent." agent."
::= { dhcpServerMIBGroups 10 } ::= { dhcpServerMIBGroups 10 }
skipping to change at page 33, line 44 skipping to change at line 1793
enthusiastically supported. If traps are to be included, that enthusiastically supported. If traps are to be included, that
should be done soon. should be done soon.
o what is the best way to reset statistics? o what is the best way to reset statistics?
o do we need to reset them individually, as groups, or as a o do we need to reset them individually, as groups, or as a
whole? whole?
o we need a timestamp of when they were reset o 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 use? should 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.
skipping to change at page 34, line 46 skipping to change at line 1846
authors, revisions to standard text required by the IETF, and some authors, revisions to standard text required by the IETF, and some
editorial clarifications. 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 practical values for the length of both objects. the 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 the MIB itself) and restored the Security Considerations text in the MIB itself) and added the Shared Network concept to describe
that had somehow been deleted: several subnetworks that coexist on shared network segments: several subnetworks that coexist on one
one medium. This was done partly because the Address Range concept medium. This was done partly because the Address Range concept did
did not adequately describe the "scoping" of address pools as is not adequately describe the "scoping" of address pools as is common
common with many current server implementations. 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
corrections and amplifications suggested by various readers of the
-04 draft, including a missing OID for serverNotifyObjects and a
syntax error for PhysicalAddress.
The "-05" draft closes several issues raised during peer review
discussions on the DHC mailing list, incorporates several new
elements, and makes a number of small revisions based on comments
from reviewers.
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 authors 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.
skipping to change at page 35, line 22 skipping to change at line 1885
7. Security Considerations 7. Security Considerations
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some objects may be considered sensitive or vulnerable in some
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
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, there is no control as itself is secure (for example by using IPSec), even then, there is
to who on the secure network is allowed to access and GET/SET no control as to who on the secure network is allowed to access and
(read/change/create/delete) the objects in this MIB. GET/SET (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2274 [RFC2274] and the View- of the User-based Security Model RFC 2274 [RFC2274] and the View-
based Access Control Model RFC 2275 [RFC2275] is recommended. based Access Control Model RFC 2275 [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.
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, [RFC1902] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Structure of Management Information for Version 2 of the "Structure of Management Information for Version 2 of the
Hibbs & Waters Expires: Nov 2000 + 6 months [Page 33]
Simple Network Management Protocol (SNMPv2)", RFC 1902, January Simple Network Management Protocol (SNMPv2)", RFC 1902, January
1996. 1996.
[RFC1903] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1903] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Textual Conventions for Version 2 of the Simple Network "Textual Conventions for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1903, January 1996. Management Protocol (SNMPv2)", RFC 1903, January 1996.
[RFC1904] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1904] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Conformance Statements for Version 2 of the Simple Network "Conformance Statements for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1904, January 1996. Management Protocol (SNMPv2)", RFC 1904, January 1996.
skipping to change at page 36, line 21 skipping to change at line 1936
[RFC2132] Alexander, S. and Droms, R., "DHCP Options and BOOTP [RFC2132] Alexander, S. and Droms, R., "DHCP Options and BOOTP
Vendor Extensions", RFC 2132, March 1997. Vendor Extensions", RFC 2132, March 1997.
[RFC2287] Krupczak, C. and Saperia, J., "Definitions of System- [RFC2287] Krupczak, C. and Saperia, J., "Definitions of System-
Level Managed Objects for Applications", RFC 2287, February Level Managed Objects for Applications", RFC 2287, February
1998. 1998.
9. Editors' Addresses 9. Editors' Addresses
Richard Barr Hibbs Richard Barr Hibbs
Pacific Bell UltraDNS Corporation
666 Folsom Street, Room 1225 800 North San Mateo Drive
San Francisco, CA 94107-1384 San Mateo, CA 94401-2261
USA USA
Phone: +1 415-545-1576 Phone: +1 650-227-2678
Fax: +1 415-543-3539 Fax: +1 650-227-2662
Email: rbhibbs@pacbell.com Email: rbhibbs@ultraDNS.com
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-798-4925 Phone: +1 613-765-0249
Email: gww@nortelnetworks.com Email: gww@nortelnetworks.com
10. Full Copyright Statement 10. Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (2000). 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 included on all such copies and derivative works. However, this are 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/