Hi Fabien,
I guess this is a case where you have visibility, space and computing.
Pick two.
You could decrease the bgp_aspath_radius which will hinder your
visibility in long as paths (if you care about that) saving space and
computing. Drawback is you would not be safe from long as-sets since
those could be at the first or second hop away anyway.
You could increase the field size from 80 chars - you would blindly eat
more space but that would keep your database structure fixed (and hence
more efficient from a computing standpoint).
You could make the field variable-length - optimizing space and avoiding
you the try & error of finding the sweet spot size for the as path field
at the expense of more computing.
Paolo
On Fri, Dec 07, 2018 at 10:46:32AM +0100, Fabien VINCENT wrote:
> Dear List,
>
> I've an issue when nfacctd try to push to pgsql database :
>
> PGSQL log file :
>
> ERROR: value too long for type character(80)
> CONTEXT:
>
> COPY flow _*****_, line 74771, column as_path_src: "14061
> {46652,4210010000,4210010200,4210010201,4210010202,4210010297,4210010400,4210010402,4210010499..."
>
>
> In my nfacctd config file I've :
>
> bgp_aspath_radius: 10
>
> because as_path_src is set to CHAR(80). But seems BGP aggregates break
> the rules ?
>
> Is there anyway to limit / cut down BGP aggregates in column as_path_src
> ?
>
> Thanks =)
>
> --
>
> FABIEN VINCENT
> -------------------------------------------------------------------
>
> @beufanet
> -------------------------------------------------------------------
> _______________________________________________
> pmacct-discussion mailing list
> http://www.pmacct.net/#mailinglists
_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists
