Distributed Management (disman)

Last Modified: 2006-03-24

Chair(s):

Operations and Management Area Director(s):

Operations and Management Area Advisor:

Mailing Lists:

General Discussion: disman@ietf.org
To Subscribe: disman-request@ietf.org
In Body: subscribe
Archive: http://www.ietf.org/mail-archive/web/disman/index.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.
Done    WG last call on updates to Remote Operations MIB
Mar 2004    Implementation Report on Remote Operations MIB
Done    Remote Operations MIB submitted to IESG for consideration as Draft Standard

No Current Internet-Drafts

Request For Comments:

Definitions of Managed Objects for Scheduling Management Operations (RFC 2591) (52920 bytes) obsoleted by RFC 3231
Definitions of Managed Objects for the Delegation of Management Scripts (RFC 2592) (110649 bytes) obsoleted by RFC 3165
Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations (RFC 2925) (150691 bytes) obsoleted by RFC 4560
Distributed Management Expression MIB (RFC 2982) (81371 bytes)
Event MIB (RFC 2981) (98248 bytes)
Notification Log MIB (RFC 3014) (48287 bytes)
Definitions of Managed Objects for the Delegation of Management Scripts (RFC 3165) (134479 bytes) obsoletes RFC 2592
Definitions of Managed Objects for Scheduling Management Operations (RFC 3231) (61308 bytes) obsoletes RFC 2591
Alarm MIB (RFC 3877) (149783 bytes)
Alarm Reporting Control MIB (RFC 3878) (31093 bytes)
Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations (RFC 4560) (207956 bytes) obsoletes RFC 2925