07-11-2006 06:11 AM
Hi,
We're needing to upgrade from 2.0(1b) to 3.0.1... It's been a while, and the last IOS upgrade we did we had maybe 10 hosts on - tape backup only. I kinda remember the upgrade supposed to be "do-able" without interuption to the fabric. But I can't find this one way or another via seach.
Does the upgrade interupt the fabric? If so, whats the best way to approach an upgrade? We have two MDS 9509's pretty well packed. But we do not have compilcated SAN config, two VSANs a few zones per.
Thanks,
Tom de
Solved! Go to Solution.
07-12-2006 06:57 AM
You will need to goto a newer 2.x than the 2.0.1b and then to 3.0.1. And actually, it would proably be best to go to the 3.0.2a that is out now instead of 3.0.1. If you are not upgrading for a particular code issue or to take advantage of the new hardware, consider that you might want to stop at he 2.1.2e or 2.1.3 and not into the 3.0.1 code. The 16 and regular-32 port blades will non-disruptively upgrade. The IPS and SSM blades will be disruptive. The following is from the release notes on the upgrade path.
Follow the upgrade path for your current release:
?Upgrading from Cisco SAN-OS Release 1.x to Release 3.x requires that you upgrade first to Cisco SAN-OS Release 1.3(4a), then upgrade to Cisco SAN-OS Release 2.1(2b), then upgrade to Cisco SAN-OS Release 3.0(1).
?Upgrading from Cisco SAN-OS Release 2.0(2b), 2.0(2c), 2.0(3), 2.1(2b), 2.1(2c), 2.1(2d), and 2.1(2e), allows you to nondisruptively upgrade directly to Release 3.0(1). If you do not have one of these releases installed, you must upgrade first to Cisco SAN-OS Release 2.1(2b) and then upgrade to Cisco SAN-OS Release 3.0(1).
?Upgrading from Cisco SAN-OS Release 2.x releases to Release 3.x requires that you upgrade first to Cisco SAN-OS Release 2.1(2b) and then upgrade to Cisco SAN-OS Release 3.0(1).
?If you have IVR enabled and you are upgrading from Cisco SAN-OS Release 2.1.(1a), 2.1(1b), or Release 2.1.(2a), there are additional steps you should follow before upgrading. See "Upgrading with IVR Enabled" section.
?Upgrading for FICON from Cisco SAN-OS Release 1.x to Release 3.x requires that you upgrade first to Cisco SAN-OS Release 1.3(4a), then upgrade to Cisco SAN-OS Release 2.0(2b), then upgrade to Cisco SAN-OS Release 3.0(1).
07-12-2006 06:57 AM
You will need to goto a newer 2.x than the 2.0.1b and then to 3.0.1. And actually, it would proably be best to go to the 3.0.2a that is out now instead of 3.0.1. If you are not upgrading for a particular code issue or to take advantage of the new hardware, consider that you might want to stop at he 2.1.2e or 2.1.3 and not into the 3.0.1 code. The 16 and regular-32 port blades will non-disruptively upgrade. The IPS and SSM blades will be disruptive. The following is from the release notes on the upgrade path.
Follow the upgrade path for your current release:
?Upgrading from Cisco SAN-OS Release 1.x to Release 3.x requires that you upgrade first to Cisco SAN-OS Release 1.3(4a), then upgrade to Cisco SAN-OS Release 2.1(2b), then upgrade to Cisco SAN-OS Release 3.0(1).
?Upgrading from Cisco SAN-OS Release 2.0(2b), 2.0(2c), 2.0(3), 2.1(2b), 2.1(2c), 2.1(2d), and 2.1(2e), allows you to nondisruptively upgrade directly to Release 3.0(1). If you do not have one of these releases installed, you must upgrade first to Cisco SAN-OS Release 2.1(2b) and then upgrade to Cisco SAN-OS Release 3.0(1).
?Upgrading from Cisco SAN-OS Release 2.x releases to Release 3.x requires that you upgrade first to Cisco SAN-OS Release 2.1(2b) and then upgrade to Cisco SAN-OS Release 3.0(1).
?If you have IVR enabled and you are upgrading from Cisco SAN-OS Release 2.1.(1a), 2.1(1b), or Release 2.1.(2a), there are additional steps you should follow before upgrading. See "Upgrading with IVR Enabled" section.
?Upgrading for FICON from Cisco SAN-OS Release 1.x to Release 3.x requires that you upgrade first to Cisco SAN-OS Release 1.3(4a), then upgrade to Cisco SAN-OS Release 2.0(2b), then upgrade to Cisco SAN-OS Release 3.0(1).
07-13-2006 06:23 AM
Thanks, just the info I was looking for and more.
Tom
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide