[j-nsp] setting named communities on static routes

Luis Balbinot luis at luisbalbinot.com
Thu Jan 28 23:13:18 EST 2016


+1M

Or a policy rule if it makes sense. Like IOS that allows you to apply a
route-map to every network statement under the BGP configuration.
On Jan 28, 2016 18:56, "Chuck Anderson" <cra at wpi.edu> wrote:

> On Thu, Jan 28, 2016 at 02:30:52PM -0500, Jeff Haas wrote:
> >
> > > On Jan 28, 2016, at 2:16 PM, Chuck Anderson <cra at WPI.EDU> wrote:
> > >
> > > Does anyone know why Junos doesn't accept named communities for static
> > > routes?  This doesn't work:
> > >
> > > set routing-options static route 192.0.2.0/24 community TEST
> > > set policy-options community TEST members 65000:100
> > >
> > > Instead we are forced to put the value directly:
> > >
> > > set routing-options static route 192.0.2.0/24 community 65000:100
> > > set policy-options community TEST members 65000:100
> > >
> > > Can Juniper please fix this?  Thanks :-)
> >
> > Speaking unofficially, these consistency warts drive us just as crazy as
> they do you.
> >
> > But in order to preserve our own sanity, and not bring down the wrath of
> everyone else's operations who use the existing behavior, it's not likely
> to get changed.
>
> Well, please just add a new option "community-name" then, like there
> is for the operational mode command.
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>


More information about the juniper-nsp mailing list