[pmacct-discussion] Juniper IPFIX (as_src)

Hi All! nfacctd 1.7.0 config: nfacctd_port: 2205 nfacctd_time_new: true nfacctd_account_options: true nfacctd_as: bgp bgp_daemon: true bgp_daemon_ip: X.X.X.X plugins: print[data] aggregate[data]: src_host,dst_host,src_port,dst_port,proto,src_as,dst_as,in_iface,out_iface print_output[data]: jso

Re: [pmacct-discussion] Juniper IPFIX (as_src)

cify which ASN to assign them to > (this is in general the solution to go when you have 3rd parties on your > own IP address space and want to reckon them differently): > nfacctd_net: fallback > nfacctd_as: fallback > networks_file: /path/to/networks.lst > networks_file_

[pmacct-discussion] Wait for BGP peering and massiv ipfix data

Hi All! Config: bgp_daemon : true bgp_stdcomm_pattern_to_asn : MYASN:MYASN plugins : pgsql[storage] aggregate[storage] : src_host,dst_host,src_port,dst_port,proto,src_as,dst_as,in_iface,out_iface sql_optimize_clauses[storage] : tr

Re: [pmacct-discussion] Wait for BGP peering and massiv ipfix data

Hi Paolo! >> 1) sql_startup_delay does not work for me . I would like to postpone the >> first data processing/cache purging before BGP peering is up. otherwise the >> table contains data without information from BGP daemon. > Correlation happens when flow data is received - not upon purge. So

Re: [pmacct-discussion] Wait for BGP peering and massiv ipfix data

Paolo, thanks for your reply! >> sorry typo. of course %w. The problem is that i need to rotate the table, >> but do not aggregate this table. why - to reduce the number of entries in >> the active table (after two days of working with my ipfix flow, the number >> of records in the sql_table re

[pmacct-discussion] Dynamic SQL data

Hello! my config aggregate[storage] : src_host,dst_host,src_port,dst_port,proto,src_as,dst_as,in_iface,out_iface,timestamp_start,timestamp_end sql_optimize_clauses[storage] : true sql_table[storage] : traffic_%d%m%Y sql_table_schema[storage]

Re: [pmacct-discussion] Dynamic SQL data

Y traffic_01011970 (ip_src, ip_dst, as_src, iface_in, iface_out, as_dst, port_src, port_dst, ip_proto, timestamp_start, timestamp_start_residual, timestamp_end, timestamp_end_residual, packets, bytes) FROM STDIN DELIMITER ',' each time a different line number, but the sa

Re: [pmacct-discussion] Dynamic SQL data

> Then you may be missing the sql_history and sql_history_roundoff then. Paolo, thank you. Created table has correct name. Which is strange - with my config sql_table[storage] : traffic_%d%m%Y sql_table_schema[storage] : /etc/pmacct/nfacct_schema.psql sql_tabl

Re: [pmacct-discussion] Dynamic SQL data

Hi Paolo, > On the error from your other email: any chance you can post what is the > problematic column (since you said it's always the same one)? It would > allow to formulate an idea and/or reproduce the issue. I can confirm the > error as it is spit out does not ring a bell to me. This error

Re: [pmacct-discussion] Dynamic SQL data

Здравствуйте, Paolo. Вы писали 21 березня 2018 р., 1:18:26: > Hi Andrey, > Yes what i meant is: any chance you can try to understand what precisely > is the problematic value? If it's a specific one or there is a set of > values that give problems? Having this info would put us in pole > positi

Re: [pmacct-discussion] Dynamic SQL data

Здравствуйте, Paolo. Вы писали 24 березня 2018 р., 21:55:46: > Hi Andrey, > So there are some rows that contain empty ip addresses and this is > causing the issue. I don't have a full vision of your config so i can > not guess what could be the cause - please send it over. It could also > be no