The last thing you want to do is to recreate all zoning if switch loses config during the upgrade: For example, if my production FC switch is running FOS version 6.3.2b and I want to upgrade to version 7.2.1d, which is the latest recommended version for my hardware platform, then I’ll have to upgrade from 6.3.2b to 6.4.x to 7.0.x to 7.1.x and finally to 7.2.1d.įirst and foremost save the current switch config and make a config backup via FTP (give write permissions to your FTP user’s home folder). For a NDU the rule of thumb is to apply all major releases consecutively. Which is fine for a new deployment, but not ideal for production.īrocade Fabric OS major firmware release versions are 6.3.x, 6.4.x, 7.0.x, 7.1.x, 7.2.x, etc. The reason is, if you’re upgrading to a Fabric OS version which is two or more versions apart from the current switch firmware revision, it will be disruptive and take the FC ports offline. For a production switch the process is different. I intentionally didn’t go into all details of firmware upgrade in my previous post, as it’s not necessary for a green field install. You will need it to upload firmware to the switch. Make sure to check the post out for instructions on how to install a FTP server. In my previous post Brocade 300 Initial Setup I briefly went through the firmware upgrade process, which is a part of every new switch installation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |