- completely new functionalities, so bumped port revision
this was overdue, since this complex port needs more docu,
explanation, preparation, etc ...
- installation directory moved
from ${PREFIX}/var/flows to ${PREFIX}/var/db/flows
to match our typical /var filesystem layout, but since I want
to package this port, I don't want to write into /var/filesystem
its up to the user, to move the data around later if he has a large
/var and likes the data to reside there.
- create needed directories in ${PREFIX}/var/db/flows (bin and graphs)
use a .keep_me file, so that things are packaged properly
- install needed documentation
the INSTALL file is essential as well as the various example file.
NOPORTDOCS only covers unneeded files, which are not crucial for
installation
- the ${PREFIX}/var/db/flows/bin directory carries the sample files
for the flowscan script. Therefore those sample files reside there.
Other sample files like the crontab settings are up to the user, so
they reside in ${PREFIX}/share/doc/flowscan
- install a sample rc file in ${PREFIX}/etc/rc.d, its deactivated, since
this is a port that needs thinking and handcrafting config files before
use...
- added a pkg-message file, that explains pre-requisites (cisco configuration)
and other post installation tasks as well as a BIG WARNING, that enabling
Netflow Switching and Netflow Data Export on your Cisco CORE or DISTRIBUTION
routers might affect the routers switching performance.
You should know IF you need to do it and if its o.k. IF you enable it.
- output pkg-message on port based installation as well since the warnings
are important.
- updated PLIST
2001-03-25 11:48:48 +00:00
|
|
|
This is not an "easy" port. You have to take many things into consideration,
|
|
|
|
|
what flow data to collect (disk space, etc), how and when to remove unneeded
|
|
|
|
|
flow files. And you have to know, what it is all about. If you don't know
|
|
|
|
|
Cisco NetFlow switching and its data export feature, then I recommend you
|
|
|
|
|
to deinstall this port.
|
|
|
|
|
|
|
|
|
|
Prerequisites:
|
|
|
|
|
A) You need to read the installation instructions closely, see:
|
|
|
|
|
${PREFIX}/share/doc/flowscan/INSTALL
|
|
|
|
|
|
|
|
|
|
B) You need to configure your Cisco Router, to enable Netflow Switching
|
2001-03-25 17:44:44 +00:00
|
|
|
and Netflow data export (version 5 flow export format).
|
- completely new functionalities, so bumped port revision
this was overdue, since this complex port needs more docu,
explanation, preparation, etc ...
- installation directory moved
from ${PREFIX}/var/flows to ${PREFIX}/var/db/flows
to match our typical /var filesystem layout, but since I want
to package this port, I don't want to write into /var/filesystem
its up to the user, to move the data around later if he has a large
/var and likes the data to reside there.
- create needed directories in ${PREFIX}/var/db/flows (bin and graphs)
use a .keep_me file, so that things are packaged properly
- install needed documentation
the INSTALL file is essential as well as the various example file.
NOPORTDOCS only covers unneeded files, which are not crucial for
installation
- the ${PREFIX}/var/db/flows/bin directory carries the sample files
for the flowscan script. Therefore those sample files reside there.
Other sample files like the crontab settings are up to the user, so
they reside in ${PREFIX}/share/doc/flowscan
- install a sample rc file in ${PREFIX}/etc/rc.d, its deactivated, since
this is a port that needs thinking and handcrafting config files before
use...
- added a pkg-message file, that explains pre-requisites (cisco configuration)
and other post installation tasks as well as a BIG WARNING, that enabling
Netflow Switching and Netflow Data Export on your Cisco CORE or DISTRIBUTION
routers might affect the routers switching performance.
You should know IF you need to do it and if its o.k. IF you enable it.
- output pkg-message on port based installation as well since the warnings
are important.
- updated PLIST
2001-03-25 11:48:48 +00:00
|
|
|
|
|
|
|
|
PLEASE NOTE, YOU HAVE TO KNOW EXACTLY, IF YOU REALLY WANT TO ENABLE NETFLOW
|
|
|
|
|
SWITCHING ON YOUR CISCO CORE OR DISTRIBUTION ROUTERS, WHAT PERFORMANCE IMPACT
|
|
|
|
|
MIGHT BE INVOLVED WHEN DOING THIS, WITH THE GOAL, NOT TO LOOSE YOUR ROUTING/
|
|
|
|
|
SWITCHING PERFORMANCE. BE WARNED !!!
|
|
|
|
|
|
2001-03-25 16:56:55 +00:00
|
|
|
C) You need to configure SNMP on your Cisco Router.
|
|
|
|
|
|
- completely new functionalities, so bumped port revision
this was overdue, since this complex port needs more docu,
explanation, preparation, etc ...
- installation directory moved
from ${PREFIX}/var/flows to ${PREFIX}/var/db/flows
to match our typical /var filesystem layout, but since I want
to package this port, I don't want to write into /var/filesystem
its up to the user, to move the data around later if he has a large
/var and likes the data to reside there.
- create needed directories in ${PREFIX}/var/db/flows (bin and graphs)
use a .keep_me file, so that things are packaged properly
- install needed documentation
the INSTALL file is essential as well as the various example file.
NOPORTDOCS only covers unneeded files, which are not crucial for
installation
- the ${PREFIX}/var/db/flows/bin directory carries the sample files
for the flowscan script. Therefore those sample files reside there.
Other sample files like the crontab settings are up to the user, so
they reside in ${PREFIX}/share/doc/flowscan
- install a sample rc file in ${PREFIX}/etc/rc.d, its deactivated, since
this is a port that needs thinking and handcrafting config files before
use...
- added a pkg-message file, that explains pre-requisites (cisco configuration)
and other post installation tasks as well as a BIG WARNING, that enabling
Netflow Switching and Netflow Data Export on your Cisco CORE or DISTRIBUTION
routers might affect the routers switching performance.
You should know IF you need to do it and if its o.k. IF you enable it.
- output pkg-message on port based installation as well since the warnings
are important.
- updated PLIST
2001-03-25 11:48:48 +00:00
|
|
|
Post-installation tasks involve:
|
|
|
|
|
a) Configure cflowd properly for your needs, see above mentioned docu !
|
|
|
|
|
Example files reside in ${PREFIX}/etc, files:
|
|
|
|
|
cflowd.conf.example and cfdcollect.conf
|
|
|
|
|
b) Configure flowscan, see above mentioned docu !
|
|
|
|
|
Example files reside in ${PREFIX}/var/db/flows/bin, files:
|
|
|
|
|
"foo".sample ...
|
|
|
|
|
c) Customize and install crontab file, example see:
|
|
|
|
|
${PREFIX}/share/doc/flowscan/crontab.sample
|
|
|
|
|
d) Activate flowscan startscript by renaming it as usual, see example in:
|
|
|
|
|
${PREFIX}/etc/rc.d/flowscan.sh.sample
|
2001-03-25 15:54:48 +00:00
|
|
|
e) Create graphs using make by customizing the sample Makefile, see docu !
|
|
|
|
|
${PREFIX}/var/db/flows/graphs/Makefile.sample
|
|
|
|
|
Please note, that the Makefile has to be reconfigured if you add
|
|
|
|
|
or remove protocols in ${PREFIX}/var/db/flows/bin/CampusIO.cf !
|