I have found it quite useful in the past to use multiple includes when searching for information on Cisco devices. Recently, I noticed a customer who had a port down in a port-channel. I then wanted to know what other port-channels had only 1 member, indicating something was down. For something like this, multiple includes become very handy. A normal "show interface gives way too much information. rtra#sh int port-channel 1 Port-channel1 is up, line protocol is up (connected) Hardware is EtherChannel, address is 0019.e8f7.9b9a (bia 0019.e8f7.9b9a) Description: po1.rtrb MTU 1500 ...

Upgrades are inevitable.  At some point during your server's life, you may want to know exactly what is in your machine, in terms of RAM, Hard Drives, CPUs, etc., so that you can plan your upgrades without having to take the server down. For situations like this, give lshw a spin. This stands for "LiSt HardWare". In many cases, people use lspci to find out what hardware they're using. It isn't a bad tool, but it isn't very complete, either. test:~# lspci 00:00.0 Host bridge: Intel Corporation E7520 Memory Controller Hub (rev 09) 00:02.0 PCI bridge: Intel Corporation ...

If you're as lazy and impatient as I am and you just dont want to hit the Up arrow and in infinite rapid succesion, use this shell script while [ true ]; do mii-tool eth1; sleep 1; done Oh yeah, hit CTRL+C when you're done -James ...

Hello! If you're like me, a scatterbrain, you frequently have thoughts pop in an out of your head and have a troubling time managing them. One solution that I've been able to concoct using a little bit of Google Apps trickery and Labs features, is to use the 'Multiple Inboxes' plugin, in conjunction with Google Apps' built in label functionality to create a follow-up queue. How it works This method works by creating a filter to match a certain To: address, apply a label, and have Multiple Inboxes display only that label. To use, you simply reply to any email thread, change the To: to ...

So I often log into CentOS/RHEL servers and discover that there are tons of custom RPMs installed that were just downloaded from random places. While I understand that sometimes you just need to get things done, please just create your yum repo somewhere and install from there. You’ll thank me later when you need to update said packages on 20+ servers. Here’s the basic gist. On what you plan to be your yum repo server: 1. Copy all your custom/cool RPMs over to some web accessible directory on a server. (optional: maybe create some cool vhost in Apache or whatever to have a name ...