Re: Additions to CMU's proposed DHCP MIB

Milt Roselinsky <milt@acc.com> Mon, 26 August 1996 16:04 UTC

Received: from ietf.org by ietf.org id aa05124; 26 Aug 96 12:04 EDT
Received: from cnri by ietf.org id aa05120; 26 Aug 96 12:04 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa09552; 26 Aug 96 12:04 EDT
Received: from localhost by reef.bucknell.edu with SMTP (5.65/IDA-1.2.8) id AA03080; Mon, 26 Aug 1996 11:59:46 -0400
Date: Mon, 26 Aug 1996 11:59:46 -0400
Message-Id: <v02130500ae4780467249@[129.192.64.36]>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
X-Orig-Sender: dhcp-v4@bucknell.edu
Precedence: bulk
Sender: ietf-archive-request@ietf.org
From: Milt Roselinsky <milt@acc.com>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Additions to CMU's proposed DHCP MIB
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Mime-Version: 1.0

At 1:37 PM 8/16/96, Hibbs, R Barr (rbhibbs) wrote:
>Erikas provided a copy of Carnegie-Mellon's enterprise MIB for SNMP control
>of a DHCP server last week.  After examining CMU's  work, I believe it could
>be the basis for a general command and control facility for DHCP servers.

I agree.  The CMU MIB is a good start.

To follow current conventions,  counter values need to be defined as per
the SMIv2 in RFC1902.  We need to define if we want Counter32 or Counter64
values.

>DHCP performance statistics
>     1.  Inter-arrival time
>          DHCPMinArrival  OBJECT-TYPE
>                    SYNTAX  INTEGER
>                    ACCESS  read-only
>                    STATUS  optional
>                    :: = { stats ? }
>
>          DHCPMaxArrival  OBJECT-TYPE
>                    SYNTAX  INTEGER
>                    ACCESS  read-only
>                    STATUS  optional
>                    ::= { stats ? }
>
>          Mean inter-arrival time = sum of inter-arrival times / number of
>received messages
>          DHCPSumArrival  OBJECT-TYPE
>                    SYNTAX  INTEGER
>                    ACCESS  read-only
>                    STATUS  optional
>                    :: = { stats ? }
>
>          Variance of mean inter-arrival time = sum of squares of
>inter-arrival time / number of received messages
>          DHCPSumSquaresArival  OBJECT-TYPE
>                    SYNTAX  INTEGER
>                    ACCESS  read-only
>                    STATUS  optional
>                    :: = { stats ? }
>

I'm a bit concerned about the performance statistics you've defined.  They
seem to be interesting values, but I'm curious what a network administrator
will do with the information?  Please include a detailed DESCRIPTION
section for each of the values.


>     2.  Response time
>          DHCPMinResponse  OBJECT-TYPE
>                    SYNTAX  INTEGER
>                    ACCESS  read-only
>                    STATUS  optional
>                    :: = { stats ? }
>
>          DHCPMaxResponse  OBJECT-TYPE
>                    SYNTAX  INTEGER
>                    ACCESS  read-only
>                    STATUS  optional
>                    :: = { stats ? }
>
>          Mean response time = sum of response times / number of received
>messages
>          DHCPSumResponse  OBJECT-TYPE
>                    SYNTAX  INTEGER
>                    ACCESS  read-only
>                    STATUS  optional
>                    :: = { stats ? }
>
>          Variance of mean response time = sum of squares of response time /
>number of received messages
>          DHCPSumSquaresResponse  OBJECT-TYPE
>                    SYNTAX  INTEGER
>                    ACCESS  read-only
>                    STATUS  optional
>                    :: = { stats ? }

This section is very unclear.  Is this time calculated from reciept of the
query?  My question from above regarding the value of this to a net admin
is repeated here.


>
>Barr Hibbs
>Pacific Bell
>+1 (415) 545-1576
>rbhibbs@pacbell.com

>From information in this and previous emails, it sounds like you've built
an interesting server.  Is Pac Bell willing to release it for others to
use?

Milt Roselinsky                                 milt@acc.com