Re: Real Notification Requirements

["Randy Presuhn" <randy_presuhn@mindspring.com>]

Hi -

> From: "Andy Bierman" <ietf@andybierman.com>
> To: "Netconf (E-mail)" <netconf@ops.ietf.org>
> Sent: Monday, March 27, 2006 7:48 AM
> Subject: Real Notification Requirements


...
> Content Layer Requirements
> --------------------------
> 
> C1) 'Full XML' or 'XML Wrapper' notification for SYSLOG content
> 
> C2) NETCONF configuration change notification
> 
> C3) ???
...

Based on experience with a product for which management protocol was
the sole means of configuration, the following are some events that the
notification protocol should be able to represent.  (there were more, but
these are some I remember as being important to the configuration
management part)  These are low-level, but I think they make the point that
configuration change notification isn't the only thing a configuration management
system will need to know about.

   - (configurable) hardware resource added (e.g. card plugged into chassis of
     running system, or a cable to an expansion chassis plugged in)
   - hardware resource removed (e.g. card pulled out of running system, or
     expansion chassis cable unplugged)
   - failover in n:m redundancy (failover results in 1 of m posible configurations
     being activated on 1 of the n backup resources - this is a very interesting event)
   - system reverting to configuration version foo (because version bar is corrupt
     or has become unusable, e.g. due to swapped hardware version compatibility issues)
   - configuration data store off-line (e.g., disk drive failed or removed from chassis)

Randy


--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>