[dhcwg] Re: DHCP Option for SNMP Notifications

["David T. Perkins" <[e-mail]>]

HI,

So, you are developing a mechanism that works only for
SNMPv1 with no proxy or security. Note that SNMPv1 is
a "not recommended" protocol. It would be much more
valuable to create an approach that worked for SNMPv1,
SNMPv2, and SNMPv3 protocols, that supported security
parameters from the DHCP server and from local persistent
storage, and that allowed a multi-stage boot.

There are security trade-offs that need to be covered.

At 04:40 PM 9/11/2002 -0500, Mark Bakke wrote:
>Hi David-
>
>My assumption was that in this case, we could get away with using
>"public" for the community string, and that any defined traps would
>be enabled (we would only send these when something failed, so
>we shouldn't have to allow the user to configure which ones to
>send).  That would take care of early boot, unless configuring the
>community string was important.  Perhaps this would be enough.
>
>Are there other things that might be important to set for an initial
>boot implementation that only sends traps?
>
>Thanks,
>
>Mark
>
>"David T. Perkins" wrote:
>> 
>> HI,
>> 
>> Mark,
>> 
>> Having only an IP address of a management target is insufficient for
>> achieving your objective. What you need to add depends on how many
>> "stages" that you have for your boot operation, and what you assume
>> can be configured in persistent storage for the device.
>> 
>> At 11:22 AM 9/11/2002 -0500, Mark Bakke wrote:
>> >Hi-
>> >
>> >I needed a method to configure a list of SNMP notification (AKA trap)
>> >hosts for use by diskless workstations booting from a network device.
>> >Since none of the usual SNMP configuration information is available
>> >at this time, I would like to use a DHCP option to provide a list of
>> >IP addresses to which to send notifications when, for instance, booting
>> >from a network device fails for some reason.  This could also be used
>> >to centrally configure the list of SNMP notification hosts, rather than
>> >setting them individually on each machine.
>> >
>> >Anyway, I've submitted a short draft describing the proposed option
>> >as draft-bakke-dhc-snmp-trap-00.txt.  I'll forward the message to
>> >these two groups when the draft is published.  In the mean time, it
>> >is available at:
>> >
>> >ftp://ftpeng.cisco.com/mbakke/ips/dhcp/draft-bakke-dhc-snmp-trap-00.txt
>> >
>> >I'm guessing that these two mailing lists (dhcwg and mibs) are the
>> >correct places to discuss this (please let me know if there's a more
>> >appropriate list).
>> >
>> >Regards,
>> >
>> >Mark A. Bakke
>> >Cisco Systems
>> >[e-mail]
>> >763.398.1054
>> Regards,
>> /david t. perkins
>
>-- 
>Mark A. Bakke
>Cisco Systems
>[e-mail]
>763.398.1054 
Regards,
/david t. perkins

_______________________________________________
dhcwg mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/dhcwg