Thanks for getting in touch with this.
From the log file you sent apparently the switch sends element #104
(layer2packetSectionData) to include portion of the sampled frame.
Unfortunately such element has been "deprecated in favor of 315
dataLinkFrameSection. Layer 2 packet section data." according to
IANA. Element #315, implemented by some Nexus-family kits, is instead
supported by pmacct just fine.
The above is just to say that implementing element #104 should be
relatively straightforward, pretty much handle it same as #315 that is
already implemented, we speak about adding a couple lines of code.
Can you send me privately a sample of your data to see if the theory
holds and we are not set off by any pesky details?
On Tue, May 19, 2020 at 04:45:34PM +0300, Ionuț Bîru wrote:
> Hi guys,
> I'm struggling a bit to collect netflow-v9 lite from this particular device.
> cisco configuration: https://paste.xinu.at/QLW0j/
> nfacctd config: https://paste.xinu.at/bnKHc3/
> nfacctd -f netflow.conf -d log: https://paste.xinu.at/oaJ/
> pmacct -s doesn't have any information, is like nfacctd doesn't receive any
> information from cisco related to src_ip and so on.
> Is somebody that managed to collect flow information using netflow-lite?
> pmacct-discussion mailing list
pmacct-discussion mailing list