I haven't gone through your config files, but one thing you could check is
that cflowd is configured to accept packets from the router that is sending
them. This may seem trivial, but as a default the router will export the
stats with a source IP address of the interface the stats are sent out on.
If your router has lots of interfaces, the stats can potentially have any
one of many IP addresses as the source. It is possible to put all of the
interface IP addresses in the cflowd config. There is a better way however.
When configuring netflow exports on the router it is possible to specify a
source address for the stats. I always use the loopback address of the
router for this value. Then, no matter what interface the stats go out,
they always have the single IP address of the loopback as the source. This
is easy to keep track of, and of course it's easy to maintain one IP address
in the cflowd config file.
I hope this helps.
-- "Buying a car because it's reliable is like marrying someone because they are punctual" - Jeremy Clarkson
> -----Original Message----- > From: Timothy Vann [mailto:email@example.com] > Sent: Monday, 5 February 2001 21:00 > To: 'firstname.lastname@example.org' > Subject: Netflow pkts not seen by cflowd > > > I am having problems with my cflowd setup. I am running > cflowd-2-1-b1 with > arts++-1-1-a8 on RedHat Linux 7.0. > > My basic problem is this. I can see the Netflow pkts come > into the linux > box using tcpdump. The pkts seem uncorrupted. The problem > is cflowdmux > never seems to rcv the packets. At least flowwatch never > shows anything and > I never get any info stored in the flow files. I have done > all of the usual > verification stuff that is listed in the config guide and > don't see anything > wrong. I am attaching my cflowd.conf and cfdcollect.conf > files for further > info. Hopefully it's just something simple that I have setup > incorrectly. > > I've seen this similar problem discussed in the mail group > but the threads > always seem to end without anyone posting the solution, > hence, I'm asking > again. > > Tim Vann > > <<cfdcollect.conf>> <<cflowd.conf>> > > ------------------------------------------------ > Tim Vann > Extreme Networks > 630 Davis Drive > Suite 250 > Morrisville, NC 27560 > (919) 884-3218 > email@example.com > >
-- cflowd mailing list firstname.lastname@example.org
This archive was generated by hypermail 2b29 : Tue Feb 06 2001 - 06:24:29 PST