DHCP Option for SNMP Notifications 55th IETF

1
DHCP Option for SNMP Notifications55th IETF
AtlantaNovember 2002draft-bakke-dhc-snmp-trap-01
.txtMark Bakke, Cisco Systemsmbakke_at_cisco.com
2
Summary

• Hosts need notification list from DHCP
• During network boot
• Cant get information from disk, which isnt
  there yet
• Need to notify management station if boot fails
• For centrally-configured environments
• Similar to DNS, NTP, other standard DHCP options
• New DHCP option
• List of hosts (hostname/IP address / UDP port) to
  notify
• Community or security model, level, and name
• Scope of solution
• SNMP notification list option
• Does not include other SNMP parameters

3
Next Steps

• Would like DHC to adopt as WG draft
• Decide which mailing list(s) to use for
  discussion
• Re-publish as DHC WG draft
• Ensure scope of draft is correct
• Push to Proposed Standard RFC
• Enter WG Last Call in December 2002
• Technical work
• Probably include INFORMs as well as TRAPs
• Revise based on comments and final scope of draft

4
References

• DHCP option draft
• draft-bakke-dhc-snmp-trap-01.txt
• iSCSI boot draft
• draft-ietf-ips-iscsi-boot-07.txt
• This presentation
• ftp//ftpeng.cisco.com/mbakke/ips/dhcp/

5
Backup Example options

• V1, no security, default port
• V1traphost.example.com
• (must set DNS option as well)
• V2c with community string, port 5162
• v2c192.0.2.1005162my-community
• V3 with USM
• v3192.0.2.3162usmauthNoPrivjoe
• V2c, IPv6 address
• V2c10800008800200C417Aexample-communit
  y

6
Backup Option Contents

• Comma-separated list of notification targets
• Each host contains
• Processor model (v1, v2c, v3)
• Host name or IP (v4 or v6) address
• UDP port
• v1 and v2 target security
• Community string
• v3 target security
• Security model (v1, v2c, usm)
• Security level (noAuthNoPriv, authNoPriv,
  authPriv)
• Security name