Skip to Content

Configurations

How to setup Configuration Change Notification and Tracking

Have you ever found yourself troubleshooting a problem caused by a coworker or consultant mistyping a command? It happens, everyone makes mistakes, but what's frustrating is when people won't own up and admit they made the mistake. Not only is it dishonest, it can impede a fast resolution by knowing what to undo.

As a result, you might find yourself wishing there was a relatively simple way to see every command typed into every router and switch in the network... You can do this with a AAA server, but it can be cumbersome to have to scour through the logs on your ACS server. However, there is another way and it's really easy to configure.

Configuration Change Notification and Logging, or simply Configuration Logging, is Cisco's method to log every configuration command entered on your Cisco IOS routers and switches. The feature was introduced in 12.3(4)T & 12.2(25)S, so it should be available in almost any IOS device that's been upgraded in the last 5 years. It can log locally up to a specified number of lines of config, and even send the commands off to a syslog server.

The following examples are from a Cisco 3550 switch and demonstrate how to configure and monitor change logging.

How to configure DHCP Snooping on a Cisco Catalyst switch

Command Line

A question was asked in the Tekcert forums regarding DHCP snooping configuration. After thinking about writing an in depth response, I decided to just write a full blown blog post.

Everything in this post has been tested in a lab environment with a Cisco 3550, Infoblox DHCP servers, a Netgear router as a "rogue" dhcp server, and a MacBook Pro as a client. The 3550 is configured with ip routing and a layer 3 interface on the subnet where the DHCP servers are located (10.0.10.0/24). VLAN 20 has been created on the 3550 with an interface ip address of 10.0.20.254/24. All the DHCP server configuration and helper addresses were tested and working prior to implementing DHCP snooping to eliminate any doubt as to whether the DHCP snooping configuration is working or not. So, let's get started.

Archive and Restore your Cisco Configs

command_line_eigrp.jpg

If you are used to typing "wr" to backup your configs, Cisco has been working hard at making it less easy to backup your configuration to flash. For years I've heard that write memory is "going away" and that everyone should use "copy running-config startup-config". If you are working on some newer platforms (NX-OS), you might find that wr doesn't work unless you create an alias:

alias exec wr copy run start

But there are cooler ways to backup your configurations now (aside from using third party tools), such as the Archive feature.

To backup your configs using Archive, here's a script to backup your config to disk0 once a day for two weeks:

Router(config)# archive
Router(config-archive)# path disk0:backupconfig
Router(config-archive)# maximum 14
Router(config-archive)# time-period 1440

If something happens to the config and you want to roll back to yesterday, that's where  configure replace comes in:

GLBP Authentication

If you have any type of redundancy protocol running on your network without authentication configured (especially on client subnets), you really should implement some simple security. When GLBP was first implemented in Cisco's routers, if authentication was even available it was in plain text. Since then, the addition of MD5 key-strings and key-chains has enabled engineers to ensure some level of security without simple, plain text passwords. 

How to configure GLBP

So, you might be asking how to configure GLBP. If you already have two routers on the same subnet with GLBP configured, their interface configurations might look something like this:

Virtual Port Channels

Probably one of the coolest features of Cisco's NX-OS is the ability to create a port channel between 3 different switches. This is called a Virtual Port Channel, or vPC. This completely eliminates spanning-tree from the picture when links fail, because the two switches participating in the vPC simply work it out between themselves when links fail. 

There are several steps that are needed to configure a vPC, such as having the feature enabled in NX-OS and setting up your peer link, but aside from that the port channel configuration looks nearly identical to a typical port channel. To simplify things, we will assume there are two Nexus switches already in place with management interfaces and only the default VDC configured. Each of these Nexus switches have ethernet ports 1 and 2 connected to a single 6509 access switch.

Cisco RELOAD IN Command

command_line_crypto.jpg

I'm sure many of you out there have used this command, but for anyone who hasn't, this can save you some drive time. If you are performing work on a Cisco device that is remote and there is a risk that the changes you make may cause the device or your connection to the device to fail, there is a command you can issue before making your changes that can save you.

Reload in <time>

This command effectively issues the reload command after whatever duration of time you specify. For example, if you are performing work on a remote site router that could take the WAN interface down, issue “reload in 20” to reload the router in twenty minutes. The amount of time you use is completely up to you. If you have your change scripted out and it will take 20 seconds to paste it in, you might want to type reload in 5 to give yourself a five minutes to complete the change. 

My Latest Brilliant Idea

As you I'm sure have figured out, I've been enthralled with this GNS3 product. But there's a few problems that I've hit:
First Problem: Every time I recommend GNS3 to someone, they get all excited until they find out they need a copy of the IOS to run it. The next question becomes, "So where to I get that?" At which point, I'm forced to mutter something about using someone's SmartNet contract. And I honestly feel bad! There's so many people that want to learn Cisco that can't get a copy of the IOS from somewhere.
Second Problem: Even if you DO get a copy of the IOS and get GNS3 set up, you end up in a, "what now?" scenario. Let me describe...When I teach Cisco classes, I always encourage people to get some lab equipment from Ebay...but I know a lot of people do this, get all this shiny, racked equipment in place and then don't know what to do with it.

Simple Article on Configuring 802.1X

802.1X is a powerful technology forcing people to authenticate before they are able to access Layer 2 services (such as a switchport or wireless access point). I recently stumbled on a step-by-step article showing an end-to-end configuration for the Windows RADIUS server, the Windows XP client, and the Cisco wireless access point - the link is below; just click the Server, Client, and Access Point links at the bottom of the page to get the configurations.
http://www.cs.umd.edu/~mvanopst/8021x/howto/

Completely Clearing a Cisco Switch...The Easy Way!

Clearing out a Cisco switch configuration is always a
pain because VLANs are kept in a seperate file from the startup-config
(NVRAM). There's two ways to clear a switch back to the factory defaults
- the easy way and the REALLY easy way:

The easy way
-

Switch# write erase
Switch# delete flash:vlan.dat
Switch# reload

The REALLY easy way -

Hold the "mode" button on the front of the switch for 10 seconds. The
lights will blink then go solid - the switch completely wipes all
configuration and then reboots. Obviously, this method only works on
stackable switches as the chassis based switches do not have mode
buttons.

Configuration Change Tracking...Built in?!?

For years, I have been relying on outside tools to tack changes in running configurations on Cisco devices. One of my favorite (cheaper) tools has been Kiwi CatTools. However, recently, someone turned me on to the fact that this functionality is BUILT-IN to the Cisco IOS! Here's the basics:
The feature is called Configuraton Change Notification and Logging. It has been available since IOS 12.3(4)T/12.2(25)S (it has really gone mainstream in 12.4).
For each configuration command that is executed, the following information will be logged:
• The command that was executed
• The configuration mode in which the command was executed
• The name of the user that executed the command
• The time at which the command was executed
• A configuration change sequence number
• Parser return codes for the command

Macbook Pro USB to Serial GUC232A

This is a pretty specific post for me - sorry if it does not apply. I've recently purchased an Intel-based 17" MacBook Pro and have an IOGear GUC232A USB to Serial converter I use for my console connections to Cisco routers that I've had a heck of a time getting working. BUT, I've finally conquered and wanted to write the steps I performed to aleviate the time spent if I have to do this again:
1. Download the LATEST driver from Prolific (http://www.prolific.com.tw/eng/downloads.asp?ID=31 - download the file md_pl2303H_HX_X_dmg_v1.2.1.zip)
2. Run through the install, reboot
3. The Prolific is a generic driver that works with the GUC232A, so you have to tweek it:

  • Plug the GUC232A into any available USB port on your Mac
  • Open the System Profiler, in /Application -> Utilites
  • Click USB in the Contents pane
  • Select the GUC232A in the Device Tree; usually it will be listed under USB-Serial Controller

PIX Syslog

It seems to be PIX week here. I've had more requests for PIX configurations than anything! Anyhow, just a quick configuration to make a PIX correctly log to a SYSLOG server:
logging on
logging standby
logging timestamp
logging trap notifications (or warnings - notifications will send a ton of info)
logging facility 18
logging host inside/outside ip address
I also like to use the command logging device-id string name. This tags all messages in my syslog with an identifier so I know what device sent the message (by name rather than IP address).

Welcome!

Hello everyone! I'd like to welcome you to the Cisco Blog! I don't know
about you, but there are times when I have those unanswerable questions
or just a flat out weird network configuration I'm trying to set up...Or
even those times when you're looking over someone's shoulder as they
are setting up a router, and you think, "wow! I didn't know you could do
it that way!" (but of course, never say anything for sake of your own
pride). Well, that's why I created this blog - to give a forum to all
interested in the topic of Cisco. Feel free to post about anything Cisco
related: questions, comments, configurations, tips...whatever.
Just a quick run through the few rules-of-the-blog:
1. Keep the language clean
2. Try to keep the topics centralized around Cisco technology
3. Invite a friend!

That's it! Post away!

Update: As of September 2010, Cisco Blog is now Tekcert.com

Syndicate content


Dr. Radut