Thank you Graham, I suspected that this is the case ... Is there another way to overcome this problem ? Because our netflow server connected to OOB management network which is routed only via Fxp interface ...
On Thu, Sep 6, 2012 at 6:55 PM, Graham Brown <juniper-...@grahambrown.info>wrote: > Hi Moki, > > The export of flow data is not supported via an fxp interface. The fxp0 > interface does not have the hardware capabilities to handle this kind of > operation. > > I had a similar customer query a while back; they could configure the > export of flows via the fxp interface, however it never worked. > > I hope that this is of help, > Graham > -- > Graham Brown > Twitter - @mountainrescuer <https://twitter.com/#!/mountainrescuer> > LinkedIn <http://www.linkedin.com/in/grahamcbrown> > > On Thu, Sep 6, 2012 at 1:05 PM, moki <vom...@gmail.com> wrote: > >> Hello >> Does anyone know if inline-jflow support to send traffic via fxp >> interface. >> I tried to configure inline-jflow with the configuration bellow when the >> route to the destination is the fxp interface: >> family inet { >> output { >> flow-server 88.88.88.1 {<-- routed via fxp >> port 2055; >> autonomous-system-type origin; >> version-ipfix { >> template { >> default-temp; >> } >> } >> } >> inline-jflow { >> source-address 88.88.88.2; >> } >> } >> >> Is it possible ? >> _______________________________________________ >> 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