Fibre Channel (SAN)

Reply
Contributor
Posts: 23
Registered: ‎07-30-2010

SILKWORM 200E Firmware Upgrade from v5.0.1b to v6.2.2e?

Hi All,

Please confirm is the following correct order for upgrading SILKWORM 200E Firmware?

1st Step......v5.0.1.b to v5.1.

2nd Step.....v5.1 to v5.2

3rd Step......v5.2 to 5.3

4th Step......v5.3 to v6.2.2e


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

Re: SILKWORM 200E Firmware Upgrade from v5.0.1b to v6.2.2e?

If i'm not mistaken you need to add steps 5.3.x > 6.0.x > 6.1.x > 6.2.x

Regular Contributor
Posts: 201
Registered: ‎11-24-2009

Re: SILKWORM 200E Firmware Upgrade from v5.0.1b to v6.2.2e?

Before Fabric OS 6 it was possible to skip one minor release; with 6 and above it is no longer allowed. Thus you can either go

5.0.1b > 5.2.x > 5.3.x > 6.0.0c_brcd_upgrd_01 > 6.1.x > 6.2.2e

or

5.0.1b > 5.1.x > 5.3.x > 6.0.0c_brcd_upgrd_01 > 6.1.x > 6.2.2e

Specific bugfix releases differ from vendor to vendor. The latest available is generally the one to choose.

As an example, for HP SANs one should upgrade as follows:

5.0.1b > 5.2.3 > 5.3.2c > 6.0.0c_brcd_upgrd_01 > 6.1.2b > 6.2.2e

Occasional Contributor
Posts: 7
Registered: ‎04-11-2011

Re: SILKWORM 200E Firmware Upgrade from v5.0.1b to v6.2.2e?

When performing a multiple step upgrade as in this example.

Is it best practice to complete all upgrades on one fabric at a time when you have 2 redundant fabrics?

ie complete all upgrade steps on Fabric 1, test and complete upgrades on fabric 2,

or

step one on fabric 1, step one on fabric 2,  step two on fabric 1, step two on fabric 2...etc.

What about a fabric with multiple switches, should you upgrade each switch in one fabric to each step in the migration or do all upgrades in order on each switch?

ie: Switch1 - Step1, 2, 3, 4; Switch2 - Step 1, 2, 3, 4; etc

or

Switch 1 -Step 1, Switch 2 - Step 1, Switch1 - Step 2, Switch 2 - Step 2, etc

Regular Contributor
Posts: 201
Registered: ‎11-24-2009

Re: SILKWORM 200E Firmware Upgrade from v5.0.1b to v6.2.2e?

Because fabrics are completely independent it makes little sense to keep intermediate versions in sync across fabrics. It is, however, recommended to try and keep versions in sync within a given fabric.

Two fabrics are here for redundancy. Best practice therefore is to upgrade one fabric at a time. In sensitive environments we do it in two separate sessions (upgrade one fabric on one weekend, watch how it works for a week or two; if there are no issues, upgrade the second fabric on another weekend).

As for the switches, a huge gap between versions is not recommended. Ideally a fabric runs on one version with mixed config only during upgrades. Thus it's advised to upgrade the entire fabric in "waves": Fabric 1, all switches -- step 1, then all switches -- step 2, and so on. Then fabric 2, all switches -- step 1, and so on.

For any device that already runs a newer version, downgrade is not necessary (in many cases, not possible). E.g. an EVA embedded switch with 6.1.0_8e1 shoud only be upgraded when other switches are being upgraded to 6.2.x.

New Contributor
Posts: 3
Registered: ‎04-14-2011

Re: SILKWORM 200E Firmware Upgrade from v5.0.1b to v6.2.2e?

Hi, I have Brocade 200E silkworm switch and i want to sniff the fibre channel packets so that i can see the login and link management packets/signals.

Can anyone tell me how shall i sniff the packets (Through GUI like wireshark or any other medium) as wireshark will not sniff the fabric channel packets/signals.

Thanks

Join the Community

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

vADC is now Pulse Secure
Download FREE NVMe eBook