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

[Pavel Lunin]

Hi experts,

Frank, wildcards in CLI operational mode have been in place for ages.

pash at ex4200-cluster.senetsy.lab> show interfaces terse ge-*/0/"[1-3]"
Interface               Admin Link Proto    Local                 Remote
ge-0/0/1                up    up
ge-0/0/2                up    up
ge-0/0/3                up    up
ge-1/0/1                up    up
ge-1/0/2                up    up
ge-1/0/3                up    up
ge-2/0/1                up    up
ge-2/0/2                up    up
ge-2/0/3                up    down


http://www.juniper.net/techpubs/en_US/junos10.0/information-products/topic-collections/swconfig-cli/using-wildcard-characters-in-interface-names-JUNOS-CLI.html#jd0e14356

--
Kind regards,
Pavel
>
> That would be a good start, but interface sets (not just ranges) are 
> often useful in other operational commands, such as monitoring 
> interface states and various counters.  For example, on switches that 
> support it I'll often repeatedly run a command to show interface 
> states on two or three non-contiguous ports to monitor their state as 
> various things are tried with machines at the other end.  On an EX, 
> I'd want to be able to run a command something like this:
>
> show interfaces ge-0/0/1,ge-0/1/2-4 terse
>
> and have it produce results for ge-0/0/1, ge-0/1/2, ge-0/1/3, and 
> ge-0/1/4. Some basic wildcard matching would be very nice, too - 
> something like ge-0/0/* would be more convenient than having to 
> manually specify the full range.
>
> So the ideal (for me, at least) would be that, for any operational or 
> configuration command where you specify an interface, you would be 
> able to specify an arbitrary set of interfaces and interface ranges.
>