Hi, so I opened a ticket with TAC to confirm and it appears this is correct. Flow sampling is supported on what they call “high end SRX” but not on Branch SRX. The work around they suggested is I enable port mirroring on the switches and forward to a collector (I would assume something like an NCAP instance). Sounds like a lot of work to work around something that should be included but that could be over simplifying the problem on my part.
Thanks for the response. On Aug 20, 2014, at 2:21 PM, Mike Gonnason <[email protected]> wrote: > It seems like you can do it on Data Center SRX devices, but not branch. > > http://forums.juniper.net/t5/SRX-Services-Gateway/RETH-interfaces-on-branch-SRX-clusters-and-jFlow/td-p/253211 > > I cannot find a workaround for this limitation, still seems to be present > in 12.1x46 > > http://www.juniper.net/techpubs/en_US/junos12.1x46/information-products/topic-collections/release-notes/12.1x46/junos-release-notes-12.1X46.pdf > > > > On Wed, Aug 20, 2014 at 10:55 AM, Scott Granados <[email protected]> > wrote: > >> Hi, another SRX flow related question. >> >> Doing some googling it appears that you can’t sample flow data on RETH >> (redundant ethernet) interfaces. >> >> example >> set interfaces RETH0.30 family inet sampling input >> >> Is there a work around for this? should I sample on the redundant member >> interfaces or is this just a no go entirely. >> >> What if any work around is there for this type of sampling? >> >> Thanks >> Scott >> >> >> _______________________________________________ >> juniper-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
