Keith Smith - Think Ahead. Learn More. Solve Now!

Keith Smith - Think Ahead. Learn More. Solve Now!


Show command multiple filtering

Wednesday, May 21, 2014 - Posted by Keith A. Smith, in Network

Normally when we do show command we make use of the "|" to filter and put in keywords after like include, exclude, begin and section. As we all know "include" means show only that matches the string like for the example below.



R1#sh run | inc CISCO
neighbor CISCO peer-group

We can do some multiple command filtering like the example below using the "include" keyword. Let's say we want to see the interface name, then the description, the OSPF cost and if its configured with the "mpls ip" command.



R1#sh run | inc interface |^ description |^ ip ospf cost |^ mpls ip
interface FastEthernet0/0
description towards LAN
ip ospf cost 100
mpls ip

sh run | inc Keith
View Comments 0 Comments
Share Post   


More on cisco command output filtering

Wednesday, May 21, 2014 - Posted by Keith A. Smith, in Network

Finding the right piece of information that you need from a Cisco router can often be a challenge. For example, if you use the show running-config command on a large production router, you can easily end up with 25 pages of text output.

Locating that one piece of information you're looking for can take a lot of time. Once you find it, you might need to make a change, only to have to rerun the command and go through the whole process again.

However, there are some shortcuts you can take to find this information more quickly. Let's looks at some filtering options you can use when maneuvering through long command output on a Cisco router.

Filter output using line numbers

You can use the show running-config linenum command to configure the system to include line numbers at the start of each line in the output. Here's an example:

Current configuration : 59161 bytes


    1 : !
    2 : ! Last configuration change at 09:25:35 CDT Tue Aug 16 2005 by root
    3 : ! NVRAM config last updated at 09:25:36 CDT Tue Aug 16 2005 by root
    4 : !
    5 : version 12.3
    6 : service tcp-keepalives-in
    7 : service tcp-keepalives-out
    8 : service timestamps debug datetime msec localtime show-timezone
    9 : service timestamps log datetime msec localtime show-timezone
   10 : service password-encryption

Once you have line numbers to use as reference points, you can then filter the output by starting at a certain line or only returning a specified line. Here's an example of starting the output at a specific line:

Router# show running-config linenum | begin 6 : 


    6 : service tcp-keepalives-in
    7 : service tcp-keepalives-out
    8 : service timestamps debug datetime msec localtime show-timezone
    9 : service timestamps log datetime msec localtime show-timezone
   10 : service password-encryption

Here's an example of requesting only one line returned in the output:

Router# show running-config linenum | include ( 6 : )


    6 : service tcp-keepalives-in

Filter output using Include, Exclude, or Begin

You can also use certain commands to help filter your output. For example, you can use the include command to see only lines that include the word service. Here's an example:

Router# show running-config | include service
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
service password-encryption

You can use the begin command to start the output at a certain line (such as an interface). Here's an example:

Router# show running-config | begin interface Serial3/0
interface Serial3/0


 description MPLS T-1
 bandwidth 1544
 ip address 10.0.100.2 255.255.255.252
 no ip proxy-arp (truncated)

In addition, you can use the exclude command in the same way if there's something particularly long that you don't need to see in the output.

The best thing about these three commands is that they work with almost any output on the router. For example, let's say I wanted to see all routes that begin with the IP address 10.83.x.x. But it doesn't work if I use this:

Router# show ip route 10.83.0.0        
% Subnet not in table

However, if I use something like the following example, I can see all of the routes that begin with 10.83.x.x:

Router# show ip route | include 10.83.     
O       10.83.100.8/30 [110/2370] via 10.83.100.2, 05:32:27, Serial1/2:0.83
O       10.83.100.4/30 [110/2115] via 10.20.100.2, 05:32:27, Serial1/2:0.2
C       10.83.100.0/30 is directly connected, Serial1/2:0.83
O       10.83.103.0/24 [110/2195] via 10.83.100.2, 05:32:27, Serial1/2:0.83

Filter output by interface

On the other hand, if you only need to see the output of one specific interface, you can also filter output in that way. Here's an example:

Router# show running-config interface Serial3/0        
Building configuration...

Current configuration : 209 bytes
!


interface Serial3/0
 description MPLS T-1
 bandwidth 1544
 ip address 10.0.100.2 255.255.255.252
 no ip proxy-arp
 no ip mroute-cache
 no fair-queue
 no cdp enable end

Start searching your output

Did you know that you can search directly from the show running-config command's output? If you use the show running-config command, you should see a –More– prompt at the end of each page of output (depending on your page length).

If you enter a forward slash [/] at this prompt, it will replace the prompt with the slash, and you can then type in whatever you want to search for. Press [Enter], and it will say filtering and then begin showing you the results of your search. (This is exactly how the UNIX pg command works.) Here's an example:

/interface Serial3/0
filtering...
interface Serial3/0


 description MPLS T-1
 bandwidth 1544
 ip address 10.0.100.2 255.255.255.252
View Comments 0 Comments
Share Post   


VMware products handy links

Saturday, April 20, 2013 - Posted by Keith A. Smith, in VMware

In order to save time diving through VMware sites, here you can find some links I´ve found useful:
Miscelanea, not from VMware:
View Comments 0 Comments
Share Post   


The end of the IT Department

Saturday, July 09, 2011 - Posted by Keith A. Smith, in Journal of thoughts

When people talk about their IT departments, they always talk about the things they’re not allowed to do, the applications they can’t run, and the long time it takes to get anything done. Rigid and inflexible policies that fill the air with animosity. Not to mention the frustrations of speaking different languages. None of this is a good foundation for a sustainable relationship.

 

If businesses had as many gripes with an external vendor, that vendor would’ve been dropped long ago. But IT departments have endured as a necessary evil. I think those days are coming to an end.

 

The problem with IT departments seems to be that they’re set up as a forced internal vendor. From the start, they have a monopoly on the “computer problem” – such monopolies have a tendency to produce the customer service you’d expect from the US Postal Service. The IT department has all the power, they’re not going anywhere (at least not in the short term), and their customers are seen as mindless peons. There’s no feedback loop for improvement.

 

Obviously, I can see the other side of the fence as well. IT departments are usually treated as a cost center, just above mail delivery and food service in the corporate pecking order, and never win anything when shit just works, but face the wrath of everyone when THE EXCHANGE SERVER IS DOWN!!!!!


At the same time, IT job security is often dependent on making things hard, slow, and complex. If the Exchange Server didn’t require two people to babysit it at all times, that would mean two friends out of work. Of course using hosted Gmail is a bad idea! It’s the same forces and mechanics that slowly turned unions from a force of progress (proper working conditions for all!) to a force of stagnation (only Jack can move the conference chairs, Joe is the only guy who can fix the microphone).

 

But change is coming. Dealing with technology has gone from something only for the techy geeks to something more mainstream. Younger generations get it. Computer savvyness is no longer just for the geek squad.

 

You no longer need a tech person at the office to man “the server room.” Responsibility for keeping the servers running has shifted away from the centralized IT department. Today you can get just about all the services that previously required local expertise from a web site somewhere.

 

The transition won’t happen over night, but it’s long since begun. The companies who feel they can do without an official IT department are growing in number and size. It’s entirely possible to run a 20-man office without ever even considering the need for a computer called “server” somewhere.

 

The good news for IT department operators is that they’re not exactly saddled with skills that can’t be used elsewhere. Most auto workers and textile makers would surely envy their impending doom and ask for a swap.

View Comments 0 Comments
Share Post   


Page  <1...91011