If you’re updating a chassis switch such as a 4500 series and the config register is not set to 0x2102 then enter enable mode and run: LAB2960X# conf t To do so run show ver and skip to the bottom to find current config register like so: LAB2960X# show ver This will ensure the switch uses whatever image is specified in the config rather than booting the first on the flash. Update the Boot Path List in the Configįirst, we need to make sure that the config register is set to 0xF (on 2900, 3700, etc series switches) or 0x2102 (on 4500 and other chassis switches). Repeat for the remaining switches in the stack: LAB2960X# copy tftp flash2: Take the extra minute and make sure the MD5 checksum of the uploaded file matches that given on the Cisco website to make sure the file integrity is good: LAB2960X# verify /md5 flash1:6.bin Verify the image copied by checking the flash yet again: LAB2960X# dir flash1:ģ -rwx 21268480 14:28:52 -05:00 6.bin >Address or name of remote host? 192.168.1.10 To start the copy process run: LAB2960X# copy tftp flash1 To upload images I run a small tftp server on my workstation, set my workstation to an IP on the same network as my switch, and connect the workstation to a switchport via ethernet. Verify the contents of the flash are clear by running: LAB2960X# dir flash1: To delete the image run: LAB2960X# delete /f /r flash1:6.bin Sometimes that’s not possible and you’ll have to delete the existing image first to make room. Space permitting, I like to update first and verify everything works before deleting the old firmware version from flash. Delete Old IOS Image from Flash if Short on Space You also need to make sure you don’t need to update Boot Rom or ROMMON (chassis switches) or anything like that to support the latest update. All I’ll add is that you need to check the release notes to make sure there aren’t any intermediate update jumps you need to make between your current IOS version and the one you’re update to. This will tell you what version currently exists in flash which may be helpful if you need to return this version because of problems with the new firmware.įinally, lets run a show ver to see the version that’s currently running and make sure everything lines up. Once you know how many switches you’re working with you can inspect the contents of the flash to see what version the. This command may be unavailable on a single switch deployment. Switch# Role Mac Address Priority Version State Switch/Stack Mac Address : 0012.efgh.4567 Start by entering enable mode and running a show switch from the CLI: LAB2960X# show switch For me that is verifying what the current IOS version running on the switch is so I can compare it to the release notes of the version I’m upgrading to so I can make any intermediate upgrades if need be. Verify Current Cisco IOS Versionīefore starting any upgrades, you need to establish your baseline. For the purpose of demonstration, I wanted to do it the long way, which subsequently has a shorter downtime while the stack reloads. When the master comes up it will see a version mismatch and begin updating and reloading the members. To be completely honest, the additional flash steps below will be a little redundant since updating the master should update all member switches as well. The steps for a single switch are very similar except you’ll only be working with one flash directory and it will most likely be named flash or bootflash instead of flash1, flash2, etc… In this tutorial I’m going to lists the steps for upgrading a stack of 2960-X switches. Plus, let’s be honest, IOS doesn’t change THAT much across devices and deployments and we both know you’re a smart cookie! Hopefully the steps below are close enough that you can extrapolate them to your specific type of hardware. How to Upgrade Cisco IOS Switches and Routersīefore we get to the steps I want to point out that there will be some variation in update steps between single switches and stack switches as well as between switches and routers. This will also make it easier for you to come up with more secure templates since you’ll just have one standard template to run through tools like Nipper to ensure you’re following best practices. You won’t have to keep a separate template for every flavor of IOS you have deployed across the same devices. Keeping everything up to date also aids in keeping your environment standardized. New updates not only fix security holes and bugs but they often enable new features (and deprecate others). Just as patching Windows is regular event so should be updating your Cisco networking equipment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |