On Wed, 23 Aug 2017, John Brown wrote:

yes, sorry I forgot to include that
fpc 1 {
   sampling-instance 1to1;

Be very careful with 1:1 sampling if that's what you are in fact doing. In most of the cases that come to mind, 1:1 sampling isn't necessary to get the data you need for things like traffic visualization/capacity planning. Beyond perhaps very small traffic levels, it might not be supported at all.

jms

   inline-services {

       flow-table-size {

           ipv4-flow-table-size 5;

           ipv6-flow-table-size 5;

       }

   }

}

fpc 2 {

   sampling-instance 1to1;

   inline-services {

       flow-table-size {

           ipv4-flow-table-size 5;

           ipv6-flow-table-size 5;

       }

   }

}


On Wed, Aug 23, 2017 at 9:46 AM, Alvaro Pereira <start...@gmail.com> wrote:
Hi John,

Do you have the following configured on the fpc you have installed?
ATTENTION! THIS WILL AUTOMATICALLY REBOOT THE FPC !!!

https://www.juniper.net/documentation/en_US/junos12.3/topics/reference/configuration-statement/ipv6-flow-table-size.html

Note: Any change in the configured size of the flow hash table sizes
initiates an automatic reboot of the FPC.

set chassis fpc 0 inline-services flow-table-size ipv4-flow-table-size 12
set chassis fpc 0 inline-services flow-table-size ipv6-flow-table-size 3

You might want to play with the numbers depending on your use case.

Alvaro

On Wed, Aug 23, 2017 at 7:17 AM, John Brown <j...@citylinkfiber.com> wrote:

Hi,  I'm trying to add IPv6 to my flow picture and I'm getting an
error from Junos.
Any help is much appreciated.  THANK YOU

Junos: 14.2R1.9

Error from commit check

 sampling inline configuration error
    Can't configure inline output with V5, V8 and V9 collector
configured for family inet6

Config snip

family inet {
    output {
        flow-server 192.168.1.2 {
            port 2055;
            version9 {
                template {
                    ipv4;
                }
            }
        }
        inline-jflow {
            source-address 10.0.0.1;
        }
    }
}
family inet6 {
    output {
        flow-server 192.168.1.2 {
            port 2055;
            version9 {
                template {
                    ipv6;
                }
            }
        }
        inline-jflow {
            source-address 10.0.0.1;
        }
    }
}

flow-monitoring {
    version9 {
        template ipv4 {
            ipv4-template;
        }
        template ipv6 {
            ipv6-template;
        }
    }
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to