|
From: Sanjeev G. <sa...@dc...> - 2011-02-21 13:31:07
|
On Mon, Feb 21, 2011 at 8:43 PM, Viresh Varma <vir...@gm...> wrote: > Hello, > > Thank u for your quick answer. So, it is not possible to discover > exclusively customer network topology's while running Netdisco in my own > network, which is excluded from CDP ? > Your network need not run CDP (or LLDP), if you do not wish to discover and map it. Your netdisco server needs to connect via SNMP to the routers/switches in the network being mapped. > For my project i want to be able to determine the individual topology of > the customers networks, and save the details in my own network. > Let me re-phrase this: *For my project I want to be able to determine the topology of the customer's networks,from a server running at my location.* This is very much possible. I was thinking of an alternative, where the database is seperated from the > netdisco server. see the attached sketch. Would it be possible to run > Netdisco in the customers' networks, but saving the results of different > customers in our own network (over internet or VPN) in multiply postgres > db's on 1 machine? So, by using different ports. Or is the Netdisco server's > database limited to localhost? > Are you thinking of giving the customer access to the netdisco reports? If no, you do not need multiple database(s) server(s). > > Another question: The database does actually save the info of how the > network devices are connected to eachother and what interfaces right? > Yes, please. > > > Again, thanks in advance for your answer. > > Regards, > > Vireshov > -- Sanjeev Gupta |