RE: manager subscription model for notifications: usage survey

["David B Harrington" <dbharrington@comcast.net>]

Hi,

At Enterasys, which focused on enterprise networks, we had a customer
managing an 88000 node network with our snmp application. The size of
managed networks is growing rapidly, so let's not constrain the
network size too much (but let's not go add lots of features only
useful in huge networks either).

Understand that some of the devices being managed were fairly simple
things like vending machines, not complex things like routers, but it
will be a good thing if devices other than routers can be used with
netconf.

dbh

> -----Original Message-----
> From: owner-netconf@ops.ietf.org 
> [mailto:owner-netconf@ops.ietf.org] On Behalf Of Balazs Lengyel
> Sent: Tuesday, May 02, 2006 3:10 AM
> To: Netconf (E-mail)
> Subject: Re: manager subscription model for notifications: 
> usage survey
> 
> 
> Andy mentions 100-1000 devices. In Ericsson we have systems 
> supervising up to 30000 
> devices. So we should aim somewhat higher with scalability. 
> (Today these use other 
> protocols, but they are a candidate for Netconf.)
> Balazs
> 
> Andy Bierman wrote:
> > Hi,
> > 
> > I am having a hard time understanding how the
> > peer-to-peer manager subscribe model defined
> > in the notifications draft fits with syslog and
> > SNMP notifications already in use.
> > 
> > 
> > I think it would be wise to understand how the entire
> > managed system is going to work when netconf notifications
> > are added to the mix.   How will a network of 100 - 10000 devics
> > behave in various common failure scenarios?
> > 
> 
> --
> 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/>
> 


--
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/>