Thanks very much Nikita! I think I can make this work for our situation now that you’ve done all the work! :D
On Oct 31, 2013, at 12:00 AM, Nikita Shirokov <[email protected]> wrote: > The closest thing which could do what you want is commit script + apply > macro. Something like this: > https://github.com/tehnerd/juniper_scripts/blob/master/commit/com_test.slax > — > Sent from Mailbox for iPhone > > > On Thu, Oct 31, 2013 at 2:57 AM, Brad Fleming <[email protected]> wrote: > > Does anyone know any tricks for creating a grouping of interfaces based on > the description attached? > For example: Any logical interface with the label “BACKBONE to far-node” goes > into a group that could then be referenced in OSPF, LDP, RSVP, etc. > > An interface-range is close but doesn’t allow you to reference a tagged link; > it expands it’s members only to ge-0/0/0.0 even if other units are configured > within the range. Interface-sets are not allowed to be referenced in protocol > configuration as near as I can tell. > > I’d really love a way to provision an interface, label it with “BACKBONE” or > “CPE”, and have that label automatically configure the interface for the > proper protocols. It’d really eliminate mistakes when turning up new tail > circuit locations. Any suggestions or pointers would be greatly appreciated! > _______________________________________________ > 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
