In brief, nothing extraordinary was done in the design of NSM to help it scale to large numbers of controllers.
Practically speaking, management of the individual controllers should work fine even if large numbers are added to system list. However, there isn't much threading in the notifications and health monitoring, so those will tend to bog down with large numbers of systems. The actual behavior will depend on network and system latency.
> IHAC that has about 80 FAS controllers (40 dual-controller systems) that they
> put into System Manager. These systems are scattered around the US. They
> were complaining of slow response for some of the remote systems.
Are they using AD for authentication? There have been some reports of latency when using AD authentication. Minimizing the latency to AD should help.
If the latency involves health and notifications, it can be explained by what I mentioned above. If it involves active management of individual controllers, it is likely a network latency or AD authentication issue.
> It looks like the initial design of the product was aimed at 10-20 nodes, with the idea
> that customers who needed greater scaling would migrate to DFM/Operations Manager.
Yes, that was approximately the idea. NSM offers a system list, which is a substantial improvement over FilerView. We expect that customers with tens of controllers will hit a variety of scaling issues and will want ot leverage DFM/Ops Manager.
Steve
