2.4.4 Distributed Management (disman)

NOTE: This charter is a snapshot of the 56th IETF Meeting in San Francisco, California USA. It may now be out-of-date.

Last Modified: 2003-02-25

Chair(s):
Randy Presuhn <randy_presuhn@mindspring.com>
Operations and Management Area Director(s):
Randy Bush <randy@psg.com>
Bert Wijnen <bwijnen@lucent.com>
Operations and Management Area Advisor:
Bert Wijnen <bwijnen@lucent.com>
Mailing Lists:
General Discussion: disman@ietf.org
To Subscribe: disman-request@ietf.org
In Body: subscribe
Archive: http://www.ietf.org/mail-archive/working-groups/disman/current/maillist.html
Description of Working Group:
The Distributed Management Working Group is chartered to define an initial set of managed objects for specific distributed network management applications which can be consistently developed and deployed. A distributed network manager is an applicaton that acts in a manager role to perform management functions and in an agent role so that it can be remotely controlled and observed.

Distributed network management is widely recognized as a requirement for dealing with today's growing internets. A manager application is a good candidate for distribution if it requires minimal user interaction, it would potentially consume a significant amount of network resources due to frequent polling or large data retrieval, or it requires close association with the device(s) being managed.

The working group will limit its work to distributed network management applications where the main communication mechanism for monitoring and control is SNMP. Future work (and other working groups) may be chartered to investigate other distribution techniques such as CORBA or HTTP. The objects defined by the working group will be consistent with the SNMP architecture defined in RFC 2571. The working group will especially keep security considerations in mind when defining the interface to distributed management.

The working group will complete these tasks:

Define a Scheduling MIB

Define a Script MIB

Define a Remote Operations MIB

Define an Expression and Event MIB to support Threshold Monitoring

Define a Notification Log MIB

Define an Alarm MIB

The working group will consider existing definitions, including:

o the RMON working group's work in this area

o the Application MIB (RFC 2564), SysAppl MIB (RFC 2287) and related standards.

The work on the Alarm MIB will take into consideration existing standards and practices, such as ITU-T X.733. Whether any mappings to these other standards appear in the Alarm MIB or in separate documents will be decided by the WG. The WG will actively seek participation from ITU participants to make ensure that the ITU work is correctly understood.

It is recognized that the scope of this working group is narrow relative to the potential in the area of distributed network management. This is intentional in order to increase the likelihood of producing useful, quality specifications in a timely manner. However, we will keep in mind and account for potential related or future work when developing the framework including:

o Event and alarm logging and distribution

o Historical data collection/summarization

o Topology discovery

Goals and Milestones:
Done  Post Internet-Draft for Threshold Monitoring MIB.
Done  Meet at the Montreal IETF meeting to discuss charter and review the Threshold Monitoring MIB Internet-Draft.
Done  Post Internet-Draft for Framework document.
Done  Post Internet-Draft for Script MIB.
Done  Submit final version of Threshold Monitor MIB Internet-Draft for consideration as a Proposed Standard. Submit updated versions of Internet-Drafts for Script MIB.
Done  Meet at the IETF meeting to discuss Internet-Drafts and issues that come up on the mailing list.
Done  Submit final versions of Internet-Drafts for Script MIB and Schedule MIB document for consideration as Proposed Standards.
Done  Agree on charter revisions for future work.
Done  Submit final versions of Internet-Drafts for Expression, Event and Notification MIB documents for consideration as Proposed Standards.
Done  Submit final version of Internet-Draft for Remote Ping, Traceroute, and Lookup Operations Using SMIv2
Done  Meeting in Oslo to discuss implementation and deployment experience with Schedule and Script mibs, identify any updates needed to these documents.
Done  WG agreement on direction regarding mappings to / from other alarm frameworks
Done  Submit updated Script and Schedule MIBs for consideration as Draft Standard (or recycle at Proposed).
Done  Submit updated draft of Alarm MIB for IETF meeting
Done  decision on question of whether recycle the Log MIB.
Done  Submit updated draft of Alarm MIB for IETF meeting.
Done  call for implementation experience and updates to the remote operations MIB.
Done  call for implementation experience and updates to the Event and Expression MIBs.
Done  WG last call on Alarm Management MIB.
Done  Alarm Management MIB delivered to IESG for consideration as a Proposed Standard.
Internet-Drafts:
  • - draft-ietf-disman-alarm-mib-09.txt
  • - draft-ietf-disman-conditionmib-06.txt
  • - draft-ietf-disman-event-mib-v2-01.txt
  • - draft-ietf-disman-express-mib-v2-01.txt
  • - draft-ietf-disman-notif-log-mib-v2-00.txt
    • Request For Comments:
    RFCStatusTitle
    RFC2591 PS Definitions of Managed Objects for Scheduling Management Operations
    RFC2592 PS Definitions of Managed Objects for the Delegation of Management Scripts
    RFC2925 PS Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
    RFC2982 PS Distributed Management Expression MIB
    RFC2981 PS Event MIB
    RFC3014 PS Notification Log MIB
    RFC3165 PS Definitions of Managed Objects for the Delegation of Management Scripts
    RFC3231 PS Definitions of Managed Objects for Scheduling Management Operations

    Current Meeting Report

     
    Disman WG Minutes from the 56th IETF
  - reported by Ramanathan Kavasseri (ramk@cisco.com)

1. Sharon Chisholm tasked with drafting a "Thank You" message to the ITU-T 
Liaison, and sending the draft to the DISMAN wg.

2. Sharon will look for any cases where we missed carrying over range 
constraints into the Alarm MIB docs...

3. Need to wordsmith the description of AlarmResourceID on the mailing list

4. Need to add  language describing the persistence of the alarm model 
table.  Also need to determine whether the lang reg persistence is in 
terms of MUST.  That was believed to be the consensus in the past - need to 
reverify the consensus on the mailing list.

5. Timeframe for finishing Alarm MIB edits (and discussion) - end of March 
2003. Updated I-D to appear in April.

6. Hing-Kam Lam needs to look at latest version of ID nits doc, the 
update to the RFC authors guidelines - for the ARC MIB update, as well as 
the latest guidelines for MIB reviewers.

7. Kam to make known edits to ARC from above tasks, and send it to Bert and 
internet-drafts...

8. For Script MIB and Schedule MIB - Randy to look at a 
questionnaire for implementation requests on these MIBs.

9. Remops MIB - if anyone is interested in assiting with edits, to 
contact RP on the disman mailing list.

10. Octet String in Remops MIB for payload - has a constraint related to 
ipv4 - computes pkt size - ipv4 hdr size. Need description 
clarification on what the object should do (return an error or silently 
truncate payload size) when transport type is ipv6 - Randy Presuhn 
suggested silently truncating. Need further discussion on the mailing 
list. This action item is assigned to Randy Presunhn.

10. Ram Kavasseri to initiate thread on taking Expression MIB to 
historic status

11. Bert to check whether a doc recommending historic status for Expr MIB is 
reqd.

12. Need interoperability results (for event and notif-log mibs) summary on 
wg mailing list.  Ram Kavasseri to drive the interoperability test 
effort. Results need to be posted to the wg by May.

13. NetSNMP implements the EVENT-MIB - this MIB is the target of 
internal polling for NetSNMP apps. Wes Hardaker to provide pointers on how to 
set up a copy of NetSNMP running the EVENT-MIB for 
interoperability testing.

14. Sharon to check and report back on implementations of log MIB at 
Nortel.

15. Updates for Expr, Event, Notif-Log MIB expected by April 1st.  Editor 
needs to look at latest version of ID nits doc, the update to the RFC 
authors guidelines - for the ARC MIB update, as well as the latest 
guidelines for MIB reviewers.

16. Ram to repost implementation requests for the event, expression and 
notif-log mibs on the disman wg.

    Slides

    Agenda
    Condition MIB
    Alarm MIB