Hi Chuck, No, no any flowspec filter in LS has been created. To check I've created a dummy filter in the LS:
1. admin@lab-2> show firewall logical-system LS4 2. 3. Filter: __LS4/dummy 4. So, the question is still open On Thu, Mar 23, 2017 at 2:05 AM, Chuck Anderson <c...@wpi.edu> wrote: > Try: > > show firewall | match flowspec > > Sometimes the filter names aren't what you expect when dealing with > logical-systems. The ones I see are prepended with __LSYSNAME/ to you > might find them names __LSYSNAME/__flowspec_.... > > On Wed, Mar 22, 2017 at 09:07:22PM +0200, Michail Litvak wrote: > > Hi all, > > > > Did anybody tried to use flowspec in the logical-system ? > > The BGP session with flowspec family is up and receiving appropriate > NLRI, > > the inetflow.0 table exists in the LS with appropriate values: > > > > But no firewall filter __flowspec_default_inet__ exists in the LS. > > > > > > 1. > > > > admin@lab-2> show firewall filter logical-system LS4 > > __flowspec_default_inet__ > > > > 2. > > > > error: filter name inconsistent with logical router > -- MYL2-RIPE _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
