Routing

 View Only

IMPORTANT MODERATION NOTICE

This community is currently under full moderation, meaning  all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you'll receive an email outlining the reason(s). We've implemented full moderation to control spam. Thank you for your patience and participation.



  • 1.  flow-tap data rate

    Posted 08-11-2016 12:10

    I found this reference in the below document.  Is it correct that this is a current limitation of flow-tap (about 40 Mbit/sec)

     

    “For flow-tap, a services PIC supports a total limit of 20 Kpps ingress and 20 Kpps egress

    traffic, assuming 256 bytes per packet. Carefully select the match conditions in the

    LEA filter so that these limits are not exceeded when traffic comes from a high-speed

    interface. Ensure that only necessary traffic is sent by the Packet Forwarding Engine

    firewall filter to the services PIC.”

     

    https://www.juniper.net/techpubs/en_US/release-independent/nce/information-products/topic-collections/nce/lawful-intercept-flow-tap/lawful-intercept-using-flow-tap.pdf


    #flow-tap


  • 2.  RE: flow-tap data rate
    Best Answer

    Posted 08-11-2016 18:52

    This limitation only for M/T series which need a service pic (AS or MS) for LI. MX do LI inline with tunnel services. rate and number of filters are much better