[shishirchauhan]

We are in process to implement it in our customer's environment with the number of devices to discover is between 1500-2000, i would like to know how much bandwidth will it use for the first time discovery and once that is done how much bandwidth needed for live troubleshooting for a day to day task.

[AdamT]

We have over 5000 devices and we have not noticed any real spikes in bandwidth in the discovery process. I hope this helps a bit.

[NetBrainTAC]

Hi ,

The traffic that NetBrain generates relies on what kinds of data the system needs to retrieve and the size of the retrieved data. During the live discovery process, the traffic NetBrain generates relies on the size the configuration files, routing tables and other kinds of data. If you have huge configuration files and huge routing tables (like internet routing table which may up to 30MB ), the traffic NetBrain generates will be more than that generated in normal cases. During the benchmark process, if you define the benchmark task to retrieve NCT tables, this will generate more traffic as the system needs to retrieve more data from live network.

For SNMP polling used during the discovery/benchmark process, NetBrain won’t retrieve huge interface info via SNMP. And we don’t use SNMP to retrieve the whole routing table for all devices. So SNMP queries issued by NetBrain won’t cause performance problems. If you have Tacacs server which limits the simultaneous sessions to the network devices, we have the solution to limit the simultaneous login threads to prevent potential issues.

So basically, the traffic can be limited by defining the simultaneous sessions from config settings. We don’t have exact number for the traffic in different situations. Just take one of our customers for example, during the benchmark process, it takes appropriately 9 hours to finish the data retrieval/upload process. And the benchmark folder is about 5GB. So the traffic during the benchmark process is about 150KB/s.

Here is the show commands used for live access. This will help user estimate the traffic generated during the discovery/benchmark process.