Re: [j-nsp] inline-jflow

* dha...@juniper.net (Doug Hanks) [Thu 06 Sep 2012, 18:58 CEST]: Using fxp0 for inline-jflow has been disabled since 10.2; you need to use a revenue port as the egress. Or what engineers call a non-management port -- Niels. -- ___ juniper-n

Re: [j-nsp] inline-jflow

Using fxp0 for inline-jflow has been disabled since 10.2; you need to use a revenue port as the egress. On 9/6/12 5:05 AM, "moki" 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

Re: [j-nsp] inline-jflow

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

[j-nsp] inline-jflow

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