Fibre Channel (SAN)

Reply
New Contributor
alastair.gray
Posts: 4
Registered: ‎02-04-2013

FOS releases, fixed defects and FCIP

Looking at the FOS release notes:

FOS 7.0.0d (December 17 2012) contains an extensive selection of fixed FCIP defects.

FOS 7.0.2b (January 14 2013) contains one (different) fixed FCIP defect.

It's never been very easy to identify the release numbers that were forked to create a new release, nor is it clear whether a particular defect has been fixed in a higher release or is just simply not applicable. Is ther a method that others use to try and help in this situation?

More specifically in this instance, how can I determine which would be the more stable release to use if I wanted to exploit FCIP functionality?

Thanks,

Al

Community Manager
Mike Eversole
Posts: 367
Registered: ‎04-08-2009

Re: FOS releases, fixed defects and FCIP

Hi alastair.gray.  Can you provide me the defect ID you are referencing?  I'll do some homework on it and will compare what we know of it in regards to the release notes and will compare that to our bug DB to verify and from there I can give you definitive answer.

New Contributor
alastair.gray
Posts: 4
Registered: ‎02-04-2013

Re: FOS releases, fixed defects and FCIP

Hi meversol,

There are 20+ FCIP specific defects fixed in 7.0.0d, that's a pretty long list! I cannot be certain which, if any, of these defects might potentially impact us.

As I am intending to use FCIP functionality, it would be good to know whether they are also fixed/tested at a higher release or whether we should use 7.0.0d as it is more stable for our needs. If it is believed to be 'more stable' for FCIP, then how do I know when a higher release version also includes all of these fixes and therefore takes over this role in the future?

In this instance I am referring to FCIP, but this is also a general point as it is frequently impossible to determine if I may be effectively re-introducing a fault that we had resolved with a lower release. Having been impacted by such a situation in the past, I'm hoping to understand what the currently correct manner of addressing this is.

Cheers,

Al

Valued Contributor
TechHelp24
Posts: 3,634
Registered: ‎02-23-2004

Re: FOS releases, fixed defects and FCIP

All or most Closed DEFECT referencing to different Issue and each other have different Environments SAN Fabric.

as per example:

Defect ID: DEFECT000404700

refer to

IO Failures to Open Systems Disk or Tape Device on FCIP Tunnel with FCIP Fast Write enabled.

If you have similarly Environments then you should consider to apply this Upgrade, and so on.

TechHelp24
New Contributor
alastair.gray
Posts: 4
Registered: ‎02-04-2013

Re: FOS releases, fixed defects and FCIP

Hi TechHelp24,

I still don't think you're catching the issue here. I recognise what each defect is about, they are detailed in the release notes.

Brocade fork their code at various unspecified levels and then potentially apply the same fixes to multiple branches of the same code tree, this means that unless a defect is listed in the release notes, there is no way to know if it has been fixed or not in a 'theoretically' later version.

So again, for the following:

FOS 7.0.0d (December 17 2012) contains an extensive selection of fixed FCIP defects.

FOS 7.0.2b (January 14 2013) contains one (different) fixed FCIP defect.

How do I determine if the fixes from 7.0.0d have been integrated into the later (although a different code branch) version 7.0.2b?

Cheers,

Al

Community Manager
Mike Eversole
Posts: 367
Registered: ‎04-08-2009

Re: FOS releases, fixed defects and FCIP

Majority, if not all defects listed wont apply to your specific environmental scenarios.  Where i find its good practice to glance over defects, at the same time you must avoid the proverbial "deer in the headlights" where you may get stuck in 'no-action' out of potential fear of issues that, to be quite honest, more then likely wont apply to you.  But given there is always that chance, Brocade advices to obtain a FOS target path from  your switch vendor.

New Contributor
alastair.gray
Posts: 4
Registered: ‎02-04-2013

Re: FOS releases, fixed defects and FCIP

I understand that many of the fixes probably won't affect me. I've been reading software release/fix notes for 25 years and Brocade ones specifically for 10+ years. I have followed the suggested good practice for the majority of that time. This is not about "deer in the headlights".

I was hoping to get the general question answered, but to clarify on a specific ...

We have been recommended by a Brocade specialist (i.e a specialist employed by Brocade) to use FOS version 7.0.0d "as it has a large number of FCIP fixes". However our switch vendor (not Brocade) recommends version 7.0.2b i.e. the 'current' release of the 7.0.x code line.

How do we resolve this difference?

Cheers,

Al

Community Manager
Mike Eversole
Posts: 367
Registered: ‎04-08-2009

Re: FOS releases, fixed defects and FCIP

Now when you say "switch vendor" I'm assuming you are referring to one of the primary companies Brocade manufactures the switch for (ie IBM, HP, Hitachi, Dell, etc).  The switch vendor takes priority as they test and qualify specific environments and builds.  For you to remain in a supported configuration, you would need to follow their guidance.  Brocade's input in these situations should only be treated as a general recommendation only.

Community Manager
Mike Eversole
Posts: 367
Registered: ‎04-08-2009

Re: FOS releases, fixed defects and FCIP

Additionally information... the Brocade guidance for recommended firmware (aka Target Path) will change in the next few months to from FOS 7.0.2b to the next release of FOS 7.0.2c. 

Join the Community

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