Re: [j-nsp] Interface group based on description

2013-10-31 Thread Brad Fleming
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 wrote: > The closest thing which could do what you want is commit script + apply > macro. Something like this: > https://github.com/tehne

Re: [j-nsp] Interface group based on description

2013-10-31 Thread Nikita Shirokov
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 wrote: > Does anyone know any tricks for

Re: [j-nsp] Interface group based on description

2013-10-30 Thread Nikita Shirokov
On the other hand we prefer external scripting (mostly m4 in our case) for generating configuration + load set terminal. It gives more features + you can link it with external tools (such as bgpq3 etc) — Sent from Mailbox for iPhone On Thu, Oct 31, 2013 at 9:48 AM, Crist Clark wrote: > If you

Re: [j-nsp] Interface group based on description

2013-10-30 Thread Crist Clark
If you want to start down the commit script rabbit hole to do this, here is a good start: http://www.juniper.net/us/en/community/junos/script-automation/library/configuration/backbone-mtu/ On Wed, Oct 30, 2013 at 2:50 PM, Brad Fleming wrote: > Does anyone know any tricks for creating a groupi

[j-nsp] Interface group based on description

2013-10-30 Thread Brad Fleming
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