But do MX (or Juniper boxes in general) route traffic from MPC to fxp? Last time I tried on MX it did not work.
-----Original Message----- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of moki Sent: Friday, September 07, 2012 11:02 AM To: Graham Brown Cc: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] inline-jflow Actually I thought of something I have another router which is connected to the MPC on the problematic router . I will configure the source interface address with this interface on the MPC and configure static route toward specific destination of the flow server to this another router which has also fxp which is connected to the OOB network . In this case the jflow traffic will go via valid interface(located on the MPC) to the other router , the other router will forward this traffic via his FXP interface... On Fri, Sep 7, 2012 at 10:22 AM, Graham Brown <juniper-...@grahambrown.info>wrote: > Hi Moki, > > No worries; this is the exact challenge that faced my customer. Their > server was on the management subnet which was only connected to the routers > via the management interfaces. I'm not sure what they did to resolve it; I > would presume that they moved the server. > > Sorry that I don't have a better solution for you. > Graham > > > On Friday, September 7, 2012, moki wrote: > >> 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 >>> >>> >>> >> > > -- > -sent from my iPad; please excuse spelling, grammar and brevity- > _______________________________________________ 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
