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

[Felix Schueren]

Curtis Call wrote:
>> 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?
> 
that actually sounds like a nice idea and would resemble the "one-off"
idea - but a proper way like
  set interface ge-1/2/4-9 unit 0 family inet filter input foo
(aka simply "multiplexing" the set command to many interfaces)
would still be much preferred from an operational point of view.

kind regards,

Felix

> 


-- 
Felix Schüren
Head of Network

-----------------------------------------------------------------------
Host Europe GmbH - http://www.hosteurope.de
Welserstraße 14 - 51149 Köln - Germany
Telefon: 0800 467 8387 - Fax: +49 180 5 66 3233 (*)
HRB 28495 Amtsgericht Köln - USt-IdNr.: DE187370678
Geschäftsführer:
Uwe Braun - Alex Collins - Mark Joseph - Patrick Pulvermüller

(*) 0,14 EUR/Min. aus dem dt. Festnetz, Mobilfunkpreise ggf. abweichend