RE: [dhcwg] RE: draft-bakke-dhc-snmp-trap-00.txt

"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Thu, 26 September 2002 01:51 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15431 for <dhcwg-archive@odin.ietf.org>; Wed, 25 Sep 2002 21:51:32 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8Q1r1Z27606 for dhcwg-archive@odin.ietf.org; Wed, 25 Sep 2002 21:53:01 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8Q1r1v27598 for <dhcwg-web-archive@optimus.ietf.org>; Wed, 25 Sep 2002 21:53:01 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15420 for <dhcwg-web-archive@ietf.org>; Wed, 25 Sep 2002 21:51:01 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8Q1kdv27220; Wed, 25 Sep 2002 21:46:39 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8O9Gsv19228 for <dhcwg@optimus.ietf.org>; Tue, 24 Sep 2002 05:16:54 -0400
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20696 for <dhcwg@ietf.org>; Tue, 24 Sep 2002 05:15:02 -0400 (EDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g8O9GME21146 for <dhcwg@ietf.org>; Tue, 24 Sep 2002 05:16:22 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <SLBW5FRX>; Tue, 24 Sep 2002 11:16:21 +0200
Message-ID: <A451D5E6F15FD211BABC0008C7FAD7BC0EFFE01F@nl0006exch003u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Mark Bakke <mbakke@cisco.com>
Cc: "'dhcwg@ietf.org'" <dhcwg@ietf.org>, "snmpv3@lists. tislabs. com (E-mail)" <snmpv3@lists.tislabs.com>, mibs@ops.ietf.org
Subject: RE: [dhcwg] RE: draft-bakke-dhc-snmp-trap-00.txt
Date: Tue, 24 Sep 2002 11:16:07 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

Mark, thanks for the details.

Now... I have seen some discussion as to possible issues and
such (I guess I am to blame for some of that).

What I have not yet seen is any supportive statements from
people that they indeed need this functionality. Best would
be if operators of course tell us they need it. But in 
general, we'd like to hear statements about the need for
this functionality. So an answer to this question:

> > First question would be: is it a generic problem that people face?
> Yes.  There are increasingly more solutions that allow hosts,
> racks of servers, embedded devices, etc. to be booted from
> the network.  When this fails, the host's normal configuration
> info (particularly the SNMP notification list) is not available,
> so there's no good way to tell a management station about it.
> 
> I assume that most networks would want to use SNMP for this,
> but syslog would work as well.
> 

Mark's answer is just one answer that seem to support a YES answer
Any others?

Thanks,
Bert 
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg