[Nfdump-discuss] next hop always 0.0.0.0
netflow collecting and processing tools
Brought to you by:
phaag
|
From: Jordan W. <jwh...@gm...> - 2013-08-02 04:17:06
|
For both v5 and IPFIX flow records nfdump is always saving 0.0.0.0 as the nhip and nhbip. I verified it is present (not 0.0.0.0) via pcap, does anyone else see this issue with 1.6.10? v5: # nfdump -R . -s nhip Verify map id 0: ERROR: Expected 7 elements in map, but found 2! Top 10 Nexthop IP ordered by flows: Date first seen Duration Proto Nexthop IP Flows(%) Packets(%) Bytes(%) pps bps bpp 2013-07-31 23:58:41.982 86476.659 any 0.0.0.0 3.1 M(100.0) 21.4 G(100.0) 13.2 T(100.0) 247877 1.2 G 614 # nfdump -R . -s nhbip Verify map id 0: ERROR: Expected 7 elements in map, but found 2! Top 10 Nexthop BGP IP ordered by flows: Date first seen Duration Proto Nexthop BGP IP Flows(%) Packets(%) Bytes(%) pps bps bpp 2013-07-31 23:58:41.982 86476.659 any 0.0.0.0 3.1 M(100.0) 21.4 G(100.0) 13.2 T(100.0) 247877 1.2 G 614 ipfix: # nfdump -R . -s nhip Top 10 Nexthop IP ordered by flows: Date first seen Duration Proto Nexthop IP Flows(%) Packets(%) Bytes(%) pps bps bpp 2013-08-01 22:24:16.377 5739.684 any 0.0.0.0 946(100.0) 2.9 M(100.0) 2.1 G(100.0) 503 2.9 M 720 # nfdump -R . -s nhbip Top 10 Nexthop BGP IP ordered by flows: Date first seen Duration Proto Nexthop BGP IP Flows(%) Packets(%) Bytes(%) pps bps bpp 2013-08-01 22:24:16.377 5739.684 any 0.0.0.0 946(100.0) 2.9 M(100.0) 2.1 G(100.0) 503 2.9 M 720 |