Routing

last person joined: 5 days ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.
Expand all | Collapse all

JFLOW configuration on MX480...

  • 1.  JFLOW configuration on MX480...

    Posted 11-15-2015 23:50

    Hi All,

     

    Need some guide regarding JFLOW configuration. I'm use this url https://www.forwardingplane.net/2013/09/inline-jflow-on-mx-series-juniper/ as reference.

     

    set forwarding-options sampling instance 1to1 family inet output flow-server 10.16.120.204 port 9995

     

    My question the the flow-server ip address is refer to NMS right such as PRTG. Regarding the port is it refer to what port. Let's assume i'm using the PRTG as collector.

     

    Thanks and appreciate someone feedback



  • 2.  RE: JFLOW configuration on MX480...

    Posted 11-16-2015 01:36

    Hi , yes ip address is addres of PRTG, udp port should be tthe same you configure for this sensor in PRTG configuration 

     

    https://www.paessler.com/manuals/prtg/ipfix_sensor



  • 3.  RE: JFLOW configuration on MX480...

    Posted 11-16-2015 01:47

    Hi Akusher,

     

     

    Another question. The source address is refer to router Loopback IP right?

     

    set forwarding-options sampling instance 1to1 family inet output inline-jflow source-address 10.16.120.1

     

    Thanks and appreciate your response.



  • 4.  RE: JFLOW configuration on MX480...

    Posted 11-16-2015 07:16

    With inline you can set any ip (and even ip not configured on router) but preffered will be sett to lo0.0 address



  • 5.  RE: JFLOW configuration on MX480...

    Posted 11-16-2015 07:33

      for source address you loopback or interface address as a source address.

     



  • 6.  RE: JFLOW configuration on MX480...

    Posted 11-16-2015 08:33

    Hi All,

     

     family inet {
                    output {
                        flow-server 10.16.120.204 {
                            port 9995;
                            version-ipfix {
                                template {
                                    ##
                                    ## Warning: Template type must match input protocol
                                    ##
                                    ipv4;
                                }
                            }
                        }
                        inline-jflow {
                            source-address 10.16.120.1;
                        }
                    }

     

     

    I've get the warning on template as per config above. Is is the template just a name only or i need to configure at another additional place. Thanks and appreciate someone feedback.



  • 7.  RE: JFLOW configuration on MX480...



  • 8.  RE: JFLOW configuration on MX480...

    Posted 11-16-2015 09:10

    Hi All,

     

    Below is my complete config. Appeciate someone can verify if i have missing something.

     

    xxx@mx480# run show configuration forwarding-options
    inactive: sampling {
        traceoptions {
            file ipfix.log size 10k;
        }
        instance {
            jflow {
                input {
                    rate 1;
                    run-length 0;
                }
                family inet {
                    output {
                        flow-server 10.16.120.204 {
                            port 9995;
                            version-ipfix {
                                template {
                                    ipv4;
                                }
                            }
                        }
                        inline-jflow {
                            source-address 10.16.120.1;
                        }
                    }
                }
                family inet6 {
                    output {
                        flow-server 10.16.120.204 {
                            port 9995;
                            version-ipfix {
                                template {
                                    ipv6;
                                }
                            }
                        }
                        inline-jflow {
                            source-address 10.16.120.1;
                        }
                    }
                }

     

    {master}[edit]
    xxxx@mx480# run show configuration services
    inactive: flow-monitoring {
        version-ipfix {
            template ipv4 {
                flow-active-timeout 10; -----------------------> what is best practice
                flow-inactive-timeout 10; -----------------------> what is best practice 
                template-refresh-rate {
                    packets 480000; -----------------------> what is best practice
                    seconds 10; -----------------------> what is best practice 
                }
                ipv4-template;
            }
            template ipv6 {
                flow-active-timeout 10; -----------------------> what is best practice 
                flow-inactive-timeout 10; -----------------------> what is best practice 
                template-refresh-rate { -----------------------> what is best practice 
                    packets 480000; -----------------------> what is best practice 
                    seconds 10;-----------------------> what is best practice 
                }
                ipv6-template;
            }
        }
    }

     

    {master}[edit]
    xxxx@mx480# run show configuration chassis
    redundancy {
        routing-engine 0 master;
        routing-engine 1 backup;
        graceful-switchover;
    }
    aggregated-devices {
        ethernet {
            device-count 2;
        }
    }
    fpc 0 {
        pic 0 {
            tunnel-services {
                bandwidth 1g;
            }
        }
        pic 1 {
            tunnel-services {
                bandwidth 1g;
            }
        }
        inactive: sampling-instance jflow;
        inline-services {
            flow-table-size {
                ipv4-flow-table-size 5;
                ipv6-flow-table-size 5;
            }
        }
    }
    alarm {
        management-ethernet {
            link-down ignore;
        }
    }
    network-services enhanced-ip;

     

    {master}[edit]
    xxxx@mx480# run show configuration interfaces ge-0/0/1
    description "UPSTREAM --> xxxxx";
    unit 0 {
    family inet {
    inactive: sampling {
    input;
    }
    address x.x.x.x.;
    }
    family inet6 {
    inactive: sampling {
    input;
    }
    address x.x.x.x.;
    }
    }



  • 9.  RE: JFLOW configuration on MX480...

    Posted 11-16-2015 09:12
    Edited by Jodi Meier 02-09-2024 16:35

    Hi,

     

    just want to add that i using this KB url as reference alsobecause i'm using MPC https://www.juniper.net/documentation/us/en/software/junos/flow-monitoring/topics/concept/services-configuring-traffic-sampling.html

     Moderator note: Edited Feb 9, 2024, to updated broken KB link> 



  • 10.  RE: JFLOW configuration on MX480...

    Posted 11-17-2015 04:58

    Hi all,

     

     

    I'm still cannot see any trafic on JFLOW at my PRTG. May i know if someone have exprience using JFLOW on MX480 (MPC) with PRTG?

     

     

    I'm not sure which part is wrong MX480 config or PRTG setting.

     

     

    Thanks and appreciate someone help.



  • 11.  RE: JFLOW configuration on MX480...

    Posted 11-17-2015 19:54

    Hi,

     

    Just to update the problem solved. Need some changing on PRTG only.

     

    Thanks for helping