[j-nsp] Interface group based on description

[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 <cjc+j-nsp at pumpky.net> wrote:

> 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 <bdflemin at gmail.com> 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 juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp