I actually learned a few things while writing this article. Did it contain helpful info for anyone else out there?
Thanks for reading TechRepublic!
David Davis
Discussion on:
View:
Show:
Yes, most of the information presented here was new to me. While I usually prefer to capture cli output to a txt file and search there having another tool in the box is always benificial.
I consider all of your topics a primer!
I plan to take the certification exams at the end of the year or early next year. Right now I am in the process of self-study, so I gladly appreciate all of your topics.
Thank you very much.
I plan to take the certification exams at the end of the year or early next year. Right now I am in the process of self-study, so I gladly appreciate all of your topics.
Thank you very much.
Hi there.
I din't know about the begin or the forward slash at the "--- More ---" prompt... It's always good to have another way to do things...
For those of you that don't know this, you don't need to type out the full commands, you can just truncate them, but truncate them so that they don't conflict with any other command, otherwise you'll get an error message.
Eg. Instead of "enable", just type "en". Instead of "configure terminal", "conf t". Instead of "exit", "ex". Instead of "show running-config interface Serial3/0", "sh run int ser3/0". Instead of "show ip route | include 10.83.", "sh ip r | inc 10.83.".
It's always good to experiment to see just how short you can truncate the commands, this way you can get more done in less time.
??? Hasta Lasag?e !!!
Gazz.
I din't know about the begin or the forward slash at the "--- More ---" prompt... It's always good to have another way to do things...
For those of you that don't know this, you don't need to type out the full commands, you can just truncate them, but truncate them so that they don't conflict with any other command, otherwise you'll get an error message.
Eg. Instead of "enable", just type "en". Instead of "configure terminal", "conf t". Instead of "exit", "ex". Instead of "show running-config interface Serial3/0", "sh run int ser3/0". Instead of "show ip route | include 10.83.", "sh ip r | inc 10.83.".
It's always good to experiment to see just how short you can truncate the commands, this way you can get more done in less time.
??? Hasta Lasag?e !!!
Gazz.
Indeed it was.
I knew include and exclude, but not begin and forward slash filters.
I am not a network engineer per se, but I often have to have a look at our Cisco routers or even do something simple. So these articles are invaluable source of quick information, - you don't have to peruse thick manuals.
If there's a need for more info you can always look further - but you need a heads up like this one.
So, the input is much appreciated.
I knew include and exclude, but not begin and forward slash filters.
I am not a network engineer per se, but I often have to have a look at our Cisco routers or even do something simple. So these articles are invaluable source of quick information, - you don't have to peruse thick manuals.
If there's a need for more info you can always look further - but you need a heads up like this one.
So, the input is much appreciated.
So the / filtering was new to me. Good to know, but I usually just use include/begin/exclude to get to what I need.
To make these even easier, I set up aliases:
srb - Show Running-Config | Begin
sre - Show Running-Config | Exclude
sri - Show Running-Config | Include
srint - Show Running-Config Interface
Other good commands:
show interface description
show interface status
Hope that helps you all some more.
To make these even easier, I set up aliases:
srb - Show Running-Config | Begin
sre - Show Running-Config | Exclude
sri - Show Running-Config | Include
srint - Show Running-Config Interface
Other good commands:
show interface description
show interface status
Hope that helps you all some more.
I knew about the include and the / for searching output. The begin, exclude and linenum are new to me. Many of our routers are running IOS 12.1(19) and the linenum option is not available. We just got a new router running 12.3(6c) and the linenum is available. Do you known what version the linenum option became available?
Taken from the Cisco website:
"Introduced in Cisco IOS Software Release 12.2(4), this command displays line numbers to a show output."
Thanks,
David
"Introduced in Cisco IOS Software Release 12.2(4), this command displays line numbers to a show output."
Thanks,
David
Seldom think about this (filtering) but came in handy recently and some of my peers had never seen output filtering. Always think it is good to cover the basics.
great article as always. quick query.
i've got a 2610 running 12.2(21b) and it doesn't seem to have the linenum option, i noticed the Cisco doc's say 12.2(4) should have it in there.
love to get line numbers working.. make life nice. Any ideas why it might not work in my case?
thanks again.
i've got a 2610 running 12.2(21b) and it doesn't seem to have the linenum option, i noticed the Cisco doc's say 12.2(4) should have it in there.
love to get line numbers working.. make life nice. Any ideas why it might not work in my case?
thanks again.
How can I filter the first 20 lines and send the exact 20 lines to a file in tftp server.
show processes cpu sort 5 mins
ONLY first 20 lines need to be redirected to tftp server.
Thanks.
show processes cpu sort 5 mins
ONLY first 20 lines need to be redirected to tftp server.
Thanks.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle

































