On 11/1/11 19:52, Jens Hektor wrote:
> Am 01.11.2011 18:57, schrieb Peter Haag:
>>> Is it possible to run nfdump and nfsen on separate systems?please help.
>>
>> no - and please stop spamming the list.
>
> I would not be so harsh.
Sorry for that - but sending repeated mails within hours is not really a good
idea.
As long as the collectors (nfdumps nfcapd) run on the same box as NfSen, you
can swap out the entire data as you like,
as long as locking over NFS works. If locking does not work, the profile-stat
part has to be local. The profile-data
part can still stay on NFS. Having good i.O. is essential for storing high
volume flow data.
At the moment, having the collectors and nfsen running on the same box is
compulsory. Otherwise the data bookkeeping for
the live profile will get incorrect and expiring data for the live profile will
fail. nfexpire and nfcapd talk to each
other using shared memory and semaphores. There is a pretty ugly hack for doing
that anyway. For that you need to run
two NfSen instances, one on each side, with configs tuned for that and data
shared via NFS. But this is far from
fail-save and may corrupt your data.
There are floating several ideas around in my head about the separation topic,
as it's inevitable to cope with the
increasing data volumes expected. But it also increases the complexity of the
system by an order of magnitude.
Authorisation will be part of future Nfsen - yes, and may be even come for 1.x.
There will be most likely several 1.4
releases before 2.x due to a smoother transition path. Those 1.4.x transition
releases so to speak will constantly
integrate new feature, or replace old ones until final 2.x.
- Peter
>
> Yes, it could be done and if you have performance problems it
> might be a choice that could help.
>
> In any way, both machines should share the data via
> NFS or maybe fibre channel.
>
> I am pretty sure that "/usr/local/nfsen" must be shared
> but Peter may correct me if subdirectories would be enough.
>
> There are several reasons to ask for the separation
> of gneration (or storing) data and access to it:
> one might be authorized access to the data which is
> not addressed in nfsen 1.X so far
> (@Peter: is it on the list for nfsen 2.X?)
> the other might be perfomance.
>
> My previous machine was far too slow on the disks
> that when I made some extensive seaches via nfsen,
> I did not get the graphs updated during the time
> period I made the searches.
>
> So, if you are investigating the data regularly, you should
> have really fast disks.
>
> I have one machine with now really fastdisk (fibre channel - NetApp)
>
>
>
>
> This body part will be downloaded on demand.
>
>
>
> This body part will be downloaded on demand.
--
--
Be nice to your netflow data
------------------------------------------------------------------------------
RSA® Conference 2012
Save $700 by Nov 18
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Nfsen-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
