Fibre Channel (SAN)

Reply
Occasional Contributor
Posts: 17
Registered: ‎01-07-2010

non-disruptive HCL(hot code load)

Hi ,

Our prod fabric contains 4900,acting as principle switch and remaining 4 * 4024( Hewlett Packard Brocade 4/24 SAN Switch for HP c-Class Bladesystem (AE372A) ) ISL'ed with 4900 and they all running with FOS 6.1.0h. We are planning to go for, and add DCX-4S to existing fabric and migrate them later.OR we may go with 5300 to expand the fabric. I did check the FOS support matrix as we need to go 6.4.1 to support both new switches on 4900 and FOS 6.2.2b on 4024 switches.

What are the options I have to make the fabric expansion non-disruptively ?

From which point of switch I can start upgrading the recommended FOS first and how many levels of FOS I can go with, without loosing the existing ISL connections ?

I would greatly appreciate on your valuable feedback on it. Thanks.

Valued Contributor
Posts: 931
Registered: ‎12-30-2009

Re: non-disruptive HCL(hot code load)

Did you check the HP Spock site http://h20272.www2.hp.com/?

It has the information (support matrixen) your asking for.

As for where to start, I would go for the switches with lowest firmware first.

Gives you a better change it will be/stay compatible during your upgrade.

BTW if your blade swwitches run in AG mode, the FOS level doesn't really matter.

Fabric expansion is usually non-disrutive.

Just make sure the new switch has an empty zone config, but has been configured with same fabric.ops except did.

disable the switch ISL the existing fabric and switchenable.

Occasional Contributor
Posts: 17
Registered: ‎01-07-2010

Re: non-disruptive HCL(hot code load)

Hi Dion,

Thanks for the quick responce...

I do have ths FOS support matrix from EMC. but I am not able to locate from HP.

The question is how to upgrade 4024 switch to 6.1.0h to 6.2.2b , like first step upgrade to 6.2.0 then 6.2.2b ? OR directly upgrade to 6.2.2b ?

If this is a two step procedure, once I upgrade to 6.2.0 does it will break the ISL between 4900 & 4024 ? if not, does it break the ISL once the second step completes which is at 6.2.2b ?

similarly , I would like to upgrade 4900 from 6.1.0h to 6.4.1 and how many steps involved in this upgrade proces? can I directly upgrade to 6.4.1 ?

if so , the compatibility between ISL's on each step of upgrade ? like do they stay online or loses the ISL connectivity ?

Valued Contributor
Posts: 931
Registered: ‎12-30-2009

Re: non-disruptive HCL(hot code load)

You probably have an EMC matrix because of an EMC storage device.

So you have to find an upgrade thats both supported by EMC (storage array) en HP (switch vendor).

With regards to HP only and please observe if only looked at the release notes for 6.4.1b and 6.2.2.b.

With links given you should look, if (intermediate) releases will work with regards to EMC and HP.

The 4/24 (4024) is a one step upgrade and above the minimum for 6.4.1b on your 4900

>> rel notes for 6.2.2b http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=3709945&prodSeriesId=3185340&swItem=co-81448-1&prodNameId=3185345&swEnvOID=54&swLang=8&taskId=135&mode=4&idx=0

>> 4/24 support page http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3185345&prodTypeId=12169&prodSeriesId=3185340&swLang=8&taskId=135&swEnvOID=54

The 4/64 (4900) is a 3 step upgrade from 6.1.x > 6.2.x > 6.3.x > 6.4.1b minimum level for a C class Enc. switch compatible against 6.4.1b is 6.2.1.b

>>rel notes for 6.4 http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=12169&prodSeriesId=3185358&swItem=co-91769-1&prodNameId=3185363&swEnvOID=54&swLang=8&taskId=135&mode=4&idx=0

>> 4/64 supportpage http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3185363&prodTypeId=12169&prodSeriesId=3185358&swLang=8&taskId=135&swEnvOID=54

Valued Contributor
Posts: 931
Registered: ‎12-30-2009

Re: non-disruptive HCL(hot code load)

O i forgot to mention, hot code load has been around for a while.

If you have redundant fabrics, I wouldn't worry to much about losing ISL's during upgrades.

If you don't I would worry about it either.

Occasional Contributor
Posts: 17
Registered: ‎01-07-2010

Re: non-disruptive HCL(hot code load)

Hi Dion,

Actully it's not matter of worry on loosing ISL on my redundant fabric rather to find and give some defenitive answer on production site maintenace discussions.

Decided to go from 6.1.0h to 6.2.2b. Still the question rising to me is once I upgrade 4900(principal which has cx+NAS connections) to 6.2.2b on native mode, you giving me the impression that I do lose the ISL connection till I upgrade the remaining 4024's in the fabric ? Cause I don't see 6.1.0h firmware anymore in the compatiblilty matrix.

Thanks in advance....

Contributor
Posts: 44
Registered: ‎05-22-2009

Re: non-disruptive HCL(hot code load)

According to Brocade's Release Notes for 6.2.2b, you should not attempt an Hot-Code Load when you have 4024s below code level 6.2.x.

It may work, but it is not recommended.

You should first upgrade your 4024s and then upgrade the 4900. 

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

Click to Register
Download FREE NVMe eBook