1 / 6

DHCP Option for SNMP Notifications: Host Notification List

This draft proposes a new DHCP option to provide a list of hosts to notify during network boot, specifically for cases where information cannot be obtained from disk. The option includes the host's hostname/IP address/UDP port, community or security model, level, and name. This solution is intended for centrally-configured environments and is similar to other standard DHCP options. The draft outlines next steps to be taken, including adoption by DHCP Working Group, scope clarification, and publication as a Proposed Standard RFC.

tvanpelt
Download Presentation

DHCP Option for SNMP Notifications: Host Notification List

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DHCP Option for SNMP Notifications55th IETF – AtlantaNovember 2002draft-bakke-dhc-snmp-trap-01.txtMark Bakke, Cisco Systemsmbakke@cisco.com

  2. Summary • Hosts need notification list from DHCP • During network boot • Can’t get information from disk, which isn’t 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 • V1:traphost.example.com • (must set DNS option as well) • V2c with community string, port 5162 • v2c:192.0.2.100:5162:my-community • V3 with USM • v3:192.0.2.3:162:usm:authNoPriv:joe • V2c, IPv6 address • V2c:[1080:0:0:0:8:800:200C:417A]::example-community

  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

More Related