RE: how long should the manager maintain the connection with his device?

["Kent Watsen" <kwatsen@juniper.net>]

The duration of the connection is closely related to how often the non-initiating side needs to flush its buffers (i.e. event notifications).  We find that persistent connections work fine for up to 6000 devices - this is the practical connection limit for a single machine.  For more than 6000 devices, either a server-cluster or a periodic-poll architecture needs to be considered - the choice pending on the interaction requirements of your system

When NetConf pursues event notifications, in addition to following the publish/subscribe messaging pattern it would be good to also consider the durable-subscriber and priority-queuing patterns for NMSs wishing to have non-persistent connections

Kent


-----Original Message-----
From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On Behalf Of y030737@njupt.edu.cn
Sent: Tuesday, July 05, 2005 8:21 PM
To: netconf
Subject: how long should the manager maintain the connection with his device?

hi all:

   I have read the netconf-pro06 and "scalability of netconf" topic on the list, I saw 
Juergen Schoenwaelder said he find that holding 300 TCP connections is not a hard thing.

   but I want to know in the real world , does the manager just hold the connection when there are still some config operation need to be performed and the connection will be kill as soon as these operations completed?  Or it will hold the connection with his "agent" all the time until some accident happens? 


thanks for coming in!

Best Regards

---------------------------------------------------
Wang Han

y030737@njupt.edu.cn
Research Center of Network Technology
Nanjing University of Posts and Telecommunications
---ââââââââââââââââââââââââââ



ærzuçzæçîåçzçæzäwrzÐçç