One of the task of a good Network engineer is update the Cisco IOS to avoid bugs and to have new features; but what is the correct procedure to upgrade a Cisco stack. Forum. I have a client whom has asked me to enable web management on some of his 2960 switches. I did not think this was going to be an issue, and so I told the. Release Notes for the Catalyst 2960, 2960-S, 2960-SF, 2960-C, 2960-Plus, and 3560-C Switches, Cisco IOS Release 15.2(2)E and Later. Book Title. Catalyst 2960-X Switch Cisco IOS File System and Image Management Configuration Guide, Cisco IOS Release 15.0(2)EX. Chapter Title. Working with Image Files.
Recently I had to decommission a Cisco 3560 switch and upgrade the IOS via a tar file. I figured I'd share some of the best practices like deleting the. Hi, you can use the archive download-sw command. see helpful link: http://wannabelab.blogspot.com/2015/04/cisco-me-3600x-ios-upgrade-via-archive.html. This video will show you how to upgrade IOS on Cisco Switch. For this video, I am using Cisco Catalyst 2950 but same method can be applied to Catalyst 2960.
How Do I Upgrade a Cisco Catalyst 2. G using the Image . Tar file after tftp copy to flash | LAN, Switching and Routing. Have a Catalyst 2.
G- 2. 4TC- L, I am consoled into it and had VLAN1 configured with an IP. Used TFTP3. 2 and from the switch used copy tftp flash.
Entered source file from the tftp and destination as the same name. Now I have a . The only reason I am even using the console for this is because the Web UI fails, and the Cisco Network Assistant fails with no reason given. Any assistance with this before 5p. EST 4/2. 7/2. 01. How do I complete the upgrade process, the file is on flash, just need to get from: c.
SE2toc. 29. 60- lanbasek. SE7. tar. Thanks.
Cisco Smart Install - Install, Sync and Backup Workgroup Switches. Working in an environment where you have few staff resources, especially at remote sites, deploying workgroup switches can be a bit of a pain. Or maybe you just want to make sure all new switches have the latest IOS image you are using and a basic standard configuration. The Cisco Smart Install process can be useful so you can send out an unopened new switch, have your remote arms- and- legs rack it up and magically, the switch comes on line with a current image and a standard configuration. Another useful thing is that Smart Install has a neat backup facility which is on by default. The true zero- touch install requires that the “client” switch be at least version 1. SE, although there are methods whereby switches with older software can be bootstrapped. For more information on that, see the Cisco documentation. Below is a diagram of the setup I am going to use. Where I worked, this was the typical building network block; a C3. C2. 96. 0 workgroup switches. Cisco calls the switch that provides the information (image names, configurations, etc) the “director”. The director can host the TFTP server locally, although if you have a mixed client- switch environment, this can become cumbersome; I prefer a centrally- located TFTP server. However, I have used the director switch as the DHCP server for the management VLAN, as it seems a logical place to do it, although you could futz around with your central DHCP server to do the job, too.
I am going to prep this as if I was going to be using a couple of different model workgroup switches. The configuration is slightly more involved, but it lets you prepare for the future without having to back out a single model config. So first, prepare your TFTP server. You will need two files: The .
A configuration file you want to upload to the new client switch. By naming your files appropriately, keeping switch models separate, you can create custom base configs for different types – 8- port, 2. Po. E, and so on. In this case, I am using a C2. PD- 8. TT- L, so I am calling the configuration file “2.
No need for configuring 2. Gigabit port. You can make a standardized template configuration for each switch type, model or even stack member; put in passwords, TACACS+, whatever as you need it. OK, so we have our TFTP server ready.
Now we start configuring the distribution switch. The Smart Install uses the vstack commands, but first some basic housekeeping. Put an IP address on VLAN1 SVI, as we will use the switch as the DHCP server for the client switches: Switch(config- if)#ip address 1. Switch(config- if)#no shut.
Next, whack in a hostname. Here I am being original, as this is the distribution switch for fictional Building A: Switch(config)#hostname bldg- a- dist. If needed, exclude the usual areas for the VLAN from DHCP as per your usual rules. Although, as you will see, this is the only “regular†DHCP command you will see. My TFTP server is directly attached, so my final configuration will have a local VLAN and SVI, but that is not necessary. Just place it where you need it, and make sure the switch can reach it. Set up your VTP as required. Set your trunking correctly so the new switch can come up. Whatever happened to dynamic desireable by default?
Fast. Ethernet. 0/2bldg- a- dist(config- if)# switchport mode dynamic desirable. Now, on to the good bits. First, we need to tell the switch it will be doing DHCP. It does this in the vstack space. This is not your usual DHCP. Of course, you can use an external DHCP server, but this is a convenient spot. SMARTPOOLbldg- a- dist(config- vstack- dhcp)# address- pool 1. Next, a little cosmetic stuff for the client switch. This prepends a hostname prefix to the second half of the client switch MAC address. It takes the string you give it and appends a hyphen. Right. Now to reference those files. For this, we use the vstack groups. The IOS has a list of built- in switch models and sub- types you can use that are automatically detected.
You can set up a group for each of them, each with their own software image and standard configuration. NME- ES product familysm- d- es. SM- D- ES2 product familysm- d- es. SM- D- ES3 product familysm- d- es.
SM- D- ES3. G product familysm- es. SM- ES2 product familysm- es. SM- ES3 product familysm- es. SM- ES3. G product family. I am using a 2. 96. Lanbase image. 24- 8poe         2.
POE switch. Lanbase image. POE switch. Lanlite image. Lanlite image. 24poe           2. POE switch. Lanbase image.
POE switch. Lanlite image. Lanbase image. 48- lanlite      2.
Lanlite image. 48poe           2. POE switch. Lanbase image.
POE switch. Lanlite image. Lanbase image. 8- lanlite       2. Lanlite image. 8- pd            2. And I am using the 8- pd: bldg- a- dist(config)#vstack group built- in 2.
Now, reference the image and config: bldg- a- dist(config- vstack- group) image tftp: //1. SE2. tarbldg- a- dist(config- vstack- group) config tftp: //1. Almost there. Finally, tell the switch it is the Smart Install Director by referencing an IP on the switch and enable it using the “vstack basic†command.
Created backup file- server directory flash: /vstack. For now, I’m going to turn the backup off. Mar 1 0. 1: 1. 2: 4.
SMI- 6- SWITCH_ADD: New Device detected by Director with mac address: 0. Mar 1 0. 1: 1. 2: 4.
SMI- 5- DIRECTOR: Director is enabled. OK, so we should be good to go. On the director: bldg- a- dist#sho run | sec vstackvstack group built- in 2. SE2. tarconfig tftp: //1.
SMARTPOOLaddress- pool 1. Connect an unconfigured switch with software later than 1. SE, and away we go. Either out of the box, or delete the config. One quirk with Smart Install is that it will do the software “upgrade†even if the installed version is the same. To see the upgrade process, I made a video. Be warned, it is long and boring, although I edited out some of the most boring bits. It is my first attempt at screencasting, so be kind.[youtube http: //www.
Hg. Am. FKZY]The backup process is quite simple. It is turned on by default, and the default location for storing files is on the flash: /vstack/ directory on the director. However, you can point the backup location at a TFTP server or whatever you like. As long as the Smart Install/vstack relationship is maintained, then whenever a “wr mem†is performed on the client switch, a backup will occur. Only two generations of the backup are maintained and this seems non- configurable, but a quick script on your server could archive things away in a triggered fashion. There you have it. Cisco Smart Install is a useful tool for helping with workgroup switch deployment. Take a fresh switch out of the box, rack it up, and the software will be upgraded to your standard, a base template configuration installed, and, if you like, a rudimentary backup performed for workgroup switch configurations. There are some other nice features, too. You can actually use Smart Install to schedule new image upgrades with a few commands on the director, and you can upgrade switches that are running older than 1. SE with a bit more effort. Or, once a switch is installed, it no longer needs to have the relationship with the director if you don’t want it to, so you can use this simply as a deployment aid. Even if you don’t want to do it live in the network, you could use it on the bench for new switches to be upgraded and have a fresh standard config before going on the shelf. With a little bit of effort up front, your remote workgroup switch deployment can be made a little easier, and you will know that every new switch has a consistent image and configuration.