Replacing switches, what info is needed from old

[BillClarkCC]

We have a mixed bag of Cisco switches at a secondary location that we are planning on upgrading.  They are a mixed bag as in they are not stacked and have different configs, nothing is standard.  We are moving to newer Cisco switches that will be stackable and I need to know what critical information I need to pull off the old to make sure I have proper vlans, IP routes, special port configurations and etherchannel setups, etc., so when I'm planning the new configs I don't miss anything.  I'm thinking of dumping out results for the following "show commands":

- run

- vlan

- etherchannel summary

- cdp neighbors

What am I missing that would be important?  Thanks!

Bill

[chrihussey]

Also suggest:

1- Pulling down the mac address table on each switch. If you know how to use the pipe and exclude the uplinks it will be a lot shorter and informative. With this you'll have a record of the device and associated switch port for later reference.

2- Clear counters and then after a day or week get the output of "sh interface counters errors" so you have a record of any devices generating errors. Don't want to move it then see the errors and wonder if it is the new switch.

3- "sh spanning tree root" is good to also have.

4- "sh interface status" and "sh ip interface brief" may also come in handy.

5- "sh interface trunk"

6- "sh power inline"

7- Lastly a "sh tech" just because it pulls a lot of stuff down.

Best if you telnet or ssh to the switch and not the console or it will take forever. I usually set the term length to "0" and copy it all to a text file leaving spacing between commands. You can't have too much reference information. Once everything is moved it's always good to have something to fall back on if things get confused.

Regards