I-D ACTION:draft-ietf-disman-remops-mib-v2-04.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Distributed Management Working Group of the IETF.

	Title		: Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
	Author(s)	: J. Quittek, K. White
	Filename	: draft-ietf-disman-remops-mib-v2-04.txt
	Pages		: 89
	Date		: 2004-8-9
	
This memo defines Management Information Bases (MIBs) for performing
remote ping, traceroute and lookup operations at a remote host.  When
managing a network it is useful to be able to initiate and retrieve
the results of ping or traceroute operations when performed at a
remote host.  A Lookup capability is defined in order to enable
resolving of either an IP address to an DNS name or an DNS name to an
IP address at a remote host.
Currently, there are several enterprise-specific MIBs for performing
remote ping or traceroute operations.  The purpose of this memo is to
define a standards-based solution to enable interoperability.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-04.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,

Editor for NOTIFICATION-LOG-MIB

Hi All,
After discussion with Ram Kavasseri regarding
NOTIFICATION-LOG-MIB I found out that you are looking
for an editor for the above MIB.

I would like to propose myself for this esteemed position.

I have not been active on this list, but I have co-implemented the
NOTIFICATION-LOG-MIB for Cisco IOS and have
tested it. I have even made it High-Availability aware.

I you accept this, I will work with Ram who is the present editor
and take the ownership of the editorial activity.

Regards,
Kiran. 

Re: I-D ACTION:draft-ietf-disman-remops-mib-v2-04.txt

Dear all,

Please find the list of changes between version -03 and version -04
listed at the end of this message.  We already discussed the changes
on this list and - so far - there are no further open issues left.

Thanks,

    Juergen
-- 
Juergen Quittek        quittek <at> netlab.nec.de       Tel: +49 6221 90511-15
NEC Europe Ltd.,       Network Laboratories        Fax: +49 6221 90511-55
Kurfuersten-Anlage 36, 69115 Heidelberg, Germany   http://www.netlab.nec.de

--On 09.08.2004 15:25 h -0400 Internet-Drafts <at> ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Distributed Management Working Group of the IETF.
>
> 	Title		: Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
> 	Author(s)	: J. Quittek, K. White
> 	Filename	: draft-ietf-disman-remops-mib-v2-04.txt
> 	Pages		: 89
> 	Date		: 2004-8-9

	
=======================================
changes from version -03 to version -04
=======================================

========================================================================

Re: Event MIB Implementation Survey

Event MIB - some more examples?

Re: Event MIB Implementation Survey

Re: Event MIB Implementation Survey

Hi -

Thanks for the implementation report and the clarification.

Randy

> From: "Benoit Claise" <bclaise <at> cisco.com>
> To: "Benoit Claise" <bclaise <at> cisco.com>
> Cc: "Randy Presuhn" <randy_presuhn <at> mindspring.com>; "Disman (E-mail)" <disman <at> ietf.org>
> Sent: Wednesday, August 11, 2004 9:15 AM
> Subject: Re: [Disman] Event MIB Implementation Survey
>

> Benoit Claise wrote:
>
> > Hi Randy,
> >
> > Sorry for the late reply.
> > Note that some URLs below might require a www.cisco.com login.
> >
> >Implementation Survey for RFC 2981, Event MIB
> >
> >_Module:_ DISMAN-EVENT-MIB
> >
> >_Implementation Source:_
> >Cisco IOS
> > Release 12.0(12)S was based on the draft-ietf-disman-event-mib-10.txt
> > Release 12.2(4)T is compliant to RFC2981
> > http://www.cisco.com/en/US/customer/products/sw/iosswrel/ps1834/products_feature_guide09186a00800801fd.html
> > http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a00800c391a.html
> >
> >
> >_Management Application / Agent:_ Agent
> >
> >
> > <>_GROUPs:_
> > dismanEventResourceGroup (y/n): y
> > dismanEventTriggerGroup (y/n): y
> > dismanEventObjectsGroup (y/n): y
> > dismanEventEventGroup (y/n): y
> > dismanEventNotificationObjectGroup (y/n): y
> > dismanEventNotificationGroup (y/n): y
> >
> > _OBJECTs:_
> > mteTriggerTargetTag (ro/rw): ro
> > mteEventSetTargetTag (ro/rw): ro
> > mteTriggerValueIDWildcard (ro/rw): rw
> > mteTriggerContextNameWildcard (ro/rw): ro
> > mteObjectsIDWildcard (ro/rw): rw
> > mteEventSetContextNameWildcard (ro/rw): ro
>
> Actually, when I wrote ro, I wanted to say that remote monitoring and
> context wildcarding are not implemented.
> So potentially, the right answer should: no
>
> Regards, Benoit
>
> >
> > _Deployment / Operational Experience:_
> > We have a couple of working examples posted on www.cisco.com
> > - The example monitors the locIfInputQueueDrops MIB object for increases
> > http://www.cisco.com/en/US/customer/products/hw/routers/ps133/products_white_paper09186a00801a5a68.shtml
> >
> > - A combined exampled of the EVENT and EXPRESSION MIBs
> > http://www.cisco.com/en/US/tech/tk648/tk362/technologies_configuration_example09186a008023267a.shtml
> >
> > Some other working examples will be posted soon:
> > - Customized notification.
> > A trigger will monitor the status of the ifOperStatus snmp-variable of
> > all the interfaces. When this value changes for one of the interfaces,
> > then a snmp-trap will be sent that will contain some customized
> > fields: ifIndex, ifDescr, ifType, sysLocation, sysName.
> > This example uses the existence + notification functionalities of the
> > EVENT-MIB
> >
> > - Writing the new configuration automatically to a tftp server.
> > A trigger will monitor the status of the ccmHistoryRunningLastChanged
> > snmp-variable. When the value
> > changes (which means that the config was possibly changed), a copy of
> > the current config will be sent to a server via tftp.
> > This example uses the existence + SNMPSet functionalities of the EVENT-MIB
> >
> > - Backup interface
> > A trigger will monitor the status of the ifInOctets snmp-variable of a
> > specific the interface. When the delta reaches a threshold, a
> > secondary line will be brought up using ifOperStatus. When the delta
> > goes below a threshold then the secondary line will be shut down.
> > This example uses the threshold + SNMPSet functionalities of the
> > EVENT-MIB
> >
> >_Comments:_
> >This MIB has been implemented for a couple of years already, but not widely used.
> >The first issue is that not many customers knew about it.
> >I presented a "Fault Management" update at 2 big events recently (total: 300 customers). After
presenting the EVENT MIB, I asked
a few questions. To be perfectly accurate, the questions were for both EVENT & EXPRESSION MIB, as those 2
MIBs go along together.
The EXPRESSION MIB will triger another email later on; anyway the conclusions are useful for the EVENT MIB.
> > 1. Who knew about this MIBs before Networkers?
> >           Just one of two hands up
> >        2. Who consider those 2 MIBs useful in their environments?
> >           A majority of hands up
> >        3. Who will be playing with those 2 MIBs back home?
> >           I would say 1/3 of the audience.
> >The second issue is that this MIB is not easy to set up. For example, the indexing must be clearly explained
with one example. So
more examples should be posted to help the easier deployement.
> >
> >Customizing the events in the network elements in time consuming. We don't want to loose the
configuration in case of network
element reload. The EVENT MIB persistence was introduced
> >http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps1839/products_feature_guide09186a0080087bdc.html
> >
> >Regards, Benoit.
> >
> >
> >
>
>

Status of DISMAN-EVENT-MIB?

Re: Status of DISMAN-EVENT-MIB?