Netbrain
Home NetBrain Product One-Skill-at-a-Time Search Mark Forums Read
Go BackThe Net-BrainerOne-Skill-at-a-Time Bandwidth requirement for Network Discovery

Reply
 
Thread Tools Search this Thread Display Modes
Old 06-24-2019, 02:21 AM
shishirchauhan shishirchauhan is offline
 
Join Date: Jun 2019
Posts: 1
Default Bandwidth requirement for Network Discovery

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.
Reply With Quote
Old 06-26-2019, 12:34 PM
AdamT AdamT is offline
 
Join Date: May 2019
Location: Huntsville, AL
Posts: 6
Default Re: Bandwidth requirement for Network Discovery

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.
Reply With Quote
Old 06-30-2019, 10:59 PM
NetBrainTAC NetBrainTAC is offline
Administrator
 
Join Date: Dec 2012
Posts: 511
Default Re: Bandwidth requirement for Network Discovery

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.
Reply With Quote
Reply

Bookmarks

Tags
Network Discovery

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Forum Jump

All times are GMT -4. The time now is 02:51 AM.
Powered by vBulletin
Copyright © 2000-2010 Jelsoft Enterprises Limited.
Copyright © 2009 NetBrain, Inc. All rights reserved.