[j-nsp] junos 10.0 / interface-range implementation

[Derick Winkworth]

Nice, I was just whiteboarding a macro to do just that..  But a macro might be too complicated.  Basically put an apply-macro statement at various points in the interface-range hierarchy (using an apply-group), the presence of which would cause those portions of the hierarchy to be pushed to the interfaces hierarchy and removed from the interface-range config...  I was trying to think of a way to retain both the original functionality of the interface-range config while also kind of emulating the interface-range command in IOS..


 

________________________________
From: Curtis Call <ccall at juniper.net>
To: Felix Schueren <felix.schueren at hosteurope.de>; "juniper-nsp at puck.nether.net" <juniper-nsp at puck.nether.net>
Sent: Fri, November 6, 2009 9:10:41 AM
Subject: Re: [j-nsp] junos 10.0 / interface-range implementation

> 
> So basically, I can now group my interfaces and have those grouped
> interfaces share certain characteristics. That's nice for some
> applications, but it does not help at all with the problem of
> provisioning one-off stuff on ports that are not really grouped
> (meaning that each port might end up with a totally different config at
> some point in time) but that still should be configured identically
> initially. So watch out, it's not the "interface range" many folks were
> expecting.
> 

If a commit script was available that automatically moved all interface-range configuration under the indicated interfaces (and removed the interface-range), would that be more useful?  So, rather than treating interface-ranges as permanent configuration structures, they would be treated as temporary repositories of configuration statements that should be copied to the indicated interfaces at the following commit.  Would that be of interest?

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp