[j-nsp] Condensing "monitor interface traffic" output to "relevant" interfaces
Richard A Steenbergen
ras at e-gerbil.net
Fri Nov 6 17:52:19 EST 2009
On Fri, Nov 06, 2009 at 11:29:32PM +0100, Daniel Roesen wrote:
> It would be really nice to not display all those internal interfaces
> by default, but only when using a special qualifier, e.g. "monitor
> interface traffic all". Of course, with "show" we could filter via
> regexp, but typing regexp every time is kinda annoying you know. :-)
>
> I'm trolling about this in public to see wether anyone has already
> managed to get an RFE opened on that one so we can hook up on that on
> our next multi-trillion EUR purchase. :) Just something to counter the
> usual "no customer demand" with proof of the contrary.
Been asking about that one for years. But hey they finally hid the
internal __juniper_private ribs in recent code, so it's proof miracles
really can happen.
While you're doing features requests, I'll buy you beers for life if you
can get them to put in some #$%^&*() commas in the counters (and yes
they have to be commas, until you can convince them to also add "show
bgp neighbours" :P). Nothing says fun like holding your finger over the
screen of a constantly updating number trying to count the digits to
figure out what the hell the actual value is, or better yet missing one
by accident and coming up an order of magnitude off. How many seconds
does it take you to figure out what this says, even with it not
updating:
Traffic statistics: [0]
Input bytes: 4680158011119510 (3275000368 bps) [0]
Output bytes: 62375102336927409 (33865856768 bps) [0]
--
Richard A Steenbergen <ras at e-gerbil.net> http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
More information about the juniper-nsp
mailing list