[j-nsp] MX80 JFlow Setup

[Andy Litzinger]

Levi,
 did you get this working?  My MX80 appears to be collecting flows, but I
don't see any output to my flow server.  The server ip is reachable from my
MX 80.

# show chassis
<snip>
tfeb {
    slot 0 {
        sampling-instance tp-sampling-instance;
    }
}

# show forwarding-options sampling
traceoptions {
    file ipfix.log size 10k;
}
instance {
    tp-sampling-instance {
        input {
            rate 1000;
        }
        family inet {
            output {
                flow-server <my flow server> {
                    port 2055;
                    version-ipfix {
                        template {
                            ipfix-ipv4-template;
                        }
                    }
                }
                inline-jflow {
                    source-address <my loopback>;
                }
            }
        }
    }
}

# show services
flow-monitoring {
    version-ipfix {
        template ipfix-ipv4-template {
            ipv4-template;
        }
    }
}

# show interfaces ge-1/0/0
<snip>
unit 0 {
    family inet {
        sampling {
            input;
        }
        address <isp-uplink-ip>;
    }
}

# run show services accounting status inline-jflow
  Status information
    TFEB Slot: 0
    IPV4 export format: Version-IPFIX, IPV6 export format: Not set
    VPLS export format: Not set
    IPv4 Route Record Count: 516479, IPv6 Route Record Count: 4
    Route Record Count: 516483, AS Record Count: 143756
    Route-Records Set: Yes, Config Set: Yes

# run show services accounting flow inline-jflow
  Flow information
    TFEB Slot: 0
    Flow Packets: 1445, Flow Bytes: 1419455
    Active Flows: 22, Total Flows: 935
    Flows Exported: 764, Flow Packets Exported: 752
    Flows Inactive Timed Out: 623, Flows Active Timed Out: 290

regards,
 -andy

On Tue, Dec 23, 2014 at 9:16 AM, Levi Pederson <
levipederson at mankatonetworks.net> wrote:

> All,
>
> Trying to get an MX80 to output Flow to an external collector.  I've been
> reading several pieces of documentation and I keep getting differing views
> and opinions on how this is supposed to be done.  I'm looking for the
> simplest option right now and if I need to expand I can move to more
> detailed processes after
>
> I'm currently using the following
>
> [edit chassis]
> -   tfeb {
> -       slot 0 {
> -           sampling-instance calix;
> -       }
> -   }
> [edit]
> -  forwarding-options {
> -      sampling {
> -          instance {
> -              calix {
> -                  input {
> -                      rate 50;
> -                  }
> -                  family inet {
> -                      output {
> -                          flow-server [ipaddress] {
> -                              port 2058;
> -                              version-ipfix {
> -                                  template {
> -                                      ipv4;
> -                                  }
> -                              }
> -                          }
> -                          inline-jflow {
> -                              source-address [ipaddress];
> -                          }
> -                      }
> -                  }
> -              }
> -          }
> -      }
> -  }
> -  services {
> -      flow-monitoring {
> -          version-ipfix {
> -              template ipv4 {
> -                  flow-active-timeout 60;
> -                  flow-inactive-timeout 70;
> -                  template-refresh-rate {
> -                      seconds 30;
> -                  }
> -                  option-refresh-rate {
> -                      seconds 30;
> -                  }
> -                  ipv4-template;
> -              }
> -          }
> -      }
> -  }
>
>
> Edited for Anonymity.
>
> Thank you,
> .
> *Levi Pederson*
> Mankato Networks LLC
> cell | 612.481.0769
> work | 612.787.7392
> levipederson at mankatonetworks.net
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>