{"id":539,"date":"2013-05-13T10:10:00","date_gmt":"2013-05-13T10:10:00","guid":{"rendered":"https:\/\/www.geekmungus.co.uk\/?p=539"},"modified":"2022-11-05T10:53:19","modified_gmt":"2022-11-05T10:53:19","slug":"cisco-4500-ios-upgrade","status":"publish","type":"post","link":"https:\/\/geekmungus.co.uk\/?p=539","title":{"rendered":"Cisco 4500 IOS Upgrade"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">This is not as easy as it is on a Cisco 3750 or 6500 series switch but once you know how its not too bad.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 1<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Copy the new IOS image to the switch, you need to use: <strong>copy tftp: bootflash:<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">(Notice its not &#8220;flash:&#8221;, first of the oddities.)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 2<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">verify the image is okay with the command: <strong>verifiy bootflash:&lt;IMAGENAME&gt;<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 3<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Set the boot register to 0\u00d72102 for the switch to boot from the \u2018BOOT variable\u2019, if you leave this it will try to use the 0x201 setting and just try to use the first IOS image on the flash, if of course you delete all the other images, this isn&#8217;t a problem!<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Command: <strong>config-register 0x2102<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 4<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Now you need to set the boot variable, I had some problems with this, I recommend you follow this procedure that worked for me.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong># no boot system flash bootflash:&lt;OLD IMAGE NAME&gt;<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong># write (or copy run start)<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong># boot system flash bootflash:&lt;NEW IMAGE NAME&gt;<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong># write (or copy run start)<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 5<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you don&#8217;t save the config, you don&#8217;t see the updated bootvar, this is a bit of a mind bender, as you&#8217;ll think it hasn&#8217;t changed the setting unless you save the config.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>switch#show bootvar<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">BOOT variable = bootflash:cat4500e-ipbase-mz.122-53.SG2.bin,1;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">CONFIG_FILE variable does not exist<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">BOOTLDR variable does not exist<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Configuration register is 0x102 (will be 0x2102 at next reload)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Standby BOOT variable = bootflash:cat4500e-ipbase-mz.122-53.SG2.bin,1;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Standby CONFIG_FILE variable does not exist<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Standby BOOTLDR variable does not exist<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Standby Configuration register is 0x102 (will be 0x2102 at next reload)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">after the changes should look like this:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">BOOT variable = bootflash:cat4500e-entservicesk9-mz.122-53.SG2.bin,1;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">CONFIG_FILE variable does not exist<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">BOOTLDR variable does not exist<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Configuration register is 0x102 (will be 0x2102 at next reload)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Standby BOOT variable = bootflash:cat4500e-entservicesk9-mz.122-53.SG2.bin,1;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Standby CONFIG_FILE variable does not exist<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Standby BOOTLDR variable does not exist<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Standby Configuration register is 0x102 (will be 0x2102 at next reload)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 6<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Once you are happy you are going to boot off the correct IOS you need to reload the switch.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong># reload<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">NOTE: if you have a reundant supervisor blade you can follow this:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"http:\/\/www.google.com\/url?q=http%3A%2F%2Fwww.cisco.com%2Fen%2FUS%2Fdocs%2Fswitches%2Flan%2Fcatalyst4500%2F12.2%2F20ew%2Fconfiguration%2Fguide%2FRPR.html&amp;sa=D&amp;sntz=1&amp;usg=AFQjCNHF8m6cUA7TUqUCKT1Og4j9sTClDw\" target=\"_blank\" rel=\"noreferrer noopener\">http:\/\/www.cisco.com\/en\/US\/docs\/switches\/lan\/catalyst4500\/12.2\/20ew\/configuration\/guide\/RPR.html<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Otherwise you might find that the supervisor kicks in and doesn&#8217;t upgrade. Alternatively you can reload the standby from the command prompt: <strong>redundancy reload peer<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 7<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Once reloaded, check you are all good with these commands, look to ensure that the new IOS image is being used:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong># show version<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">and<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong># show module<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>This is not as easy as it is on a Cisco 3750 or 6500 series switch but once you know how its not too bad. Step 1 Copy the new IOS image to the switch, you need to use: copy tftp: bootflash: (Notice its not &#8220;flash:&#8221;, first of the oddities.) Step 2 verify the image &#8230; <a title=\"Cisco 4500 IOS Upgrade\" class=\"read-more\" href=\"https:\/\/geekmungus.co.uk\/?p=539\" aria-label=\"Read more about Cisco 4500 IOS Upgrade\">Read more<\/a><\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17],"tags":[],"class_list":["post-539","post","type-post","status-publish","format-standard","hentry","category-networking"],"_links":{"self":[{"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/539","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=539"}],"version-history":[{"count":1,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/539\/revisions"}],"predecessor-version":[{"id":1488,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/539\/revisions\/1488"}],"wp:attachment":[{"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=539"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=539"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=539"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}