Hi Landon,
There is a system where multiple traffic servers can be linked, yes.
See the "Multi-Site" menu. This provides the illusion of there
being just one system - at least for the operational (minute-by-
minute) data anyway. This scales up well. Some customers have
more than 10 sites.
In the scenario you describe, however, it might be simpler (and less
expensive) to deploy our probe software at the remote site. It will
take care of all the SNMP polling (and BGP peering) and receive all
the NetFlow locally over the LAN, and then forward sFlow to the
remote traffic server. As long as you choose appropriate sampling
rates and counter polling intervals the sFlow traffic will be much
less than the netflow+SNMP+BGP would have been. It will also be
tolerant of any packet-loss in transit. Doing it this way means you
get complete integration of the data from both sites: the hourly
traffic matrices are merged enterprise-wide.
If you need the WAN traffic to be zero, or you want the traffic
history to be completely separate for each site, or you need to use
a fast sampling rate, then you could deploy another traffic
server, otherwise the probe solution should do what you want.
Does this answer your question?
regards,
neil
On Aug 8, 2005, at 2:01 PM, Landon Stewart | Superb Internet Corp.
wrote:
> Hello,
>
> We are running into a problem where the amount of netflow data
> between two
> locations is quite high in terms of bandwidth and since we are opening
> another location on the west coast this is only going to get worse.
>
> Can Inmon be distributed accross multiple traffic servers so that
> netflow
> data can be routed locally at each location but queries and
> information can
> be managed from one master server?
>
> --
> Landon Stewart
> Superb Internet Corporation
Received on Mon Aug 8 16:17:02 2005
This archive was generated by hypermail 2.1.8 : 08/08/05 PDT