Fibre Channel (SAN)

Reply
Contributor
Posts: 28
Registered: ‎02-21-2007

FOS 6.0.1a to 6.1.2c upgrade fails

I'm trying to upgrade the FOS version on a 48000 director, and the firmwaredownload is failing with a 0x6e error, on the standby cp.  The messages indicate that a firmwarecommit was started on the standby cp, yet after 40 minutes, the firmwareshow command still shows the primary/secondary versions on the standby cp are not the same.

What's going on here, and how do I get past this?

Peter

Super Contributor
Posts: 635
Registered: ‎04-12-2010

Re: FOS 6.0.1a to 6.1.2c upgrade fails

Can you post the current versions of both cards and which port cards are installed in the 48K?

Try to manually install the FOS version of the active CP card on the secondary card to make both the same before you update to the new version.

Check the fimrwaredownload command option "-s" 

I hope this helps,

Andreas

Contributor
Posts: 28
Registered: ‎02-21-2007

Re: FOS 6.0.1a to 6.1.2c upgrade fails

Andreas,

The current levels installed are:

Slot Name     Appl     Primary/Secondary Versions               Status
------------------------------------------------------------------------
  5  CP0      FOS      v6.0.1a                                  STANDBY *
                       v6.1.2c
  6  CP1      FOS      v6.0.1a                                  ACTIVE
                       v6.0.1a

I logged into the standby cp and when I did an errshow, I'm seeing the message:

2010/12/30-14:14:31, , 165,, INFO, ED_48000B, Firmwarecommit failed (status=0x18).

As far as the port fibre cards, we have 6 of the 32 port, 4 Gbit cards installed.

Peter

External Moderator
Posts: 4,787
Registered: ‎02-23-2004

Re: FOS 6.0.1a to 6.1.2c upgrade fails

SULB-1010 indicate FirmwareCommit error.

the command firmwaredownload -s started the firmwaredownload into a Single CP but with firmwarecommit.

In such case I would ( is my opinion ) don't use -s command.

The error you have reported here in the threads show to me as result malconfigured FTP access, or Firewall behind.

Another problem can be caused due a Dump file in the FOS.

Before you procede with firmwaredownload, try the command supportftp and if any Dump file is available remove such file.

Make sure the FTP is correct configured, and the is in same IP Strange.

Restart "firmnwaredownload"

TechHelp24
Contributor
Posts: 28
Registered: ‎02-21-2007

Re: FOS 6.0.1a to 6.1.2c upgrade fails

There was no dump file on the director.  The original attempt to update the firmware was initiated by DCFM.  The second time I tried, it was via the web tools interface.

I am currently trying the firmwaredownload, by telneting in and running the command from command line.

Pete

Contributor
Posts: 28
Registered: ‎02-21-2007

Re: FOS 6.0.1a to 6.1.2c upgrade fails

This firmwaredownload also failed.  Here are the exact messages shown.  The download had gotten through downloading 80% of the packages.

Server Name or IP Address: 134.141.20.58
User Name: admin
File Name: /Firmware/Switches/6.x/6.1.x/6.1.2/v6.1.2c
File Name: /Firmware/Switches/6.x/6.1.x/6.1.2/v6.1.2c
Network Protocol(1-auto-select, 2-FTP, 3-SCP) : 2
Password:
Checking system settings for firmwaredownload...
Protocol selected: FTP
Trying address-->AF_INET IP: 134.141.20.58, flags : 2
System settings check passed.

This command will upgrade the firmware on both CP blades. If you want to
upgrade firmware on a single CP only, please use -s option.

You may run firmwaredownloadstatus to get the status of this
command.

This command will cause a warm/non-disruptive boot on the active CP,
but will require that existing telnet, secure telnet or SSH sessions
be restarted.


Do you want to continue : y
Firmware is being downloaded to standby CP. This step may take up to 30 minutes.
Firmware is being downloaded to Standby CP. Please wait...
Firmware download failed on standby CP - Unknown error. (0x6e)
Firmwarecommit has started on the remote CP. Please use firmwaredownloadstatus and firmwareshow to see the firmware status.
Another firmwareDownload or firmwareCommit is running now.
Please run firmwaredownloadstatus to check and retry later.
Please use firmwaredownloadstatus and firmwareshow to see the firmware status.
HC900S10:admin>

Contributor
Posts: 28
Registered: ‎02-21-2007

Re: FOS 6.0.1a to 6.1.2c upgrade fails

At the present time, when I do a firmwareshow I see:

Slot Name     Appl     Primary/Secondary Versions               Status
------------------------------------------------------------------------
  5  CP0      FOS      v6.0.1a                                  STANDBY
                       Unknown
  6  CP1      FOS      v6.0.1a                                  ACTIVE *
                       v6.0.1a

What do I do to get past this?  The standby is again showing the 0x18 error code on the firmware commit.

Contributor
Posts: 28
Registered: ‎02-21-2007

Re: FOS 6.0.1a to 6.1.2c upgrade fails

One additional tidbit of information here.  When I looked at the errshow data on the standby cp, and compared it to the timestamps in the errshow of the primary, the commit failed at 12:15, but the timestamp of the firmwaredownload failure is 12:36.  Do I need to run the firmwarecommit on the standby cp to bring it's primary/secondary copies back into sync?

External Moderator
Posts: 4,787
Registered: ‎02-23-2004

Re: FOS 6.0.1a to 6.1.2c upgrade fails

Hi Pete,

good morning and Happy New Year.

--->>> The original attempt to update the firmware was initiated by DCFM.  The second time I tried, it was via the web tools interface.


--->>> I am currently trying the firmwaredownload, by telneting in and running the command from command line.

Sound no good that the firmwaredownload was interrupted at 3 times...

AFAIK, 0x18 error stay indicated for a corrupet CF/FOS partition.

I hope you are under maintenance Contract with Brocade or you Service Provider

About firmwarecommit, i don#t this work, because the first Error result from commit command.

I would procede as follow:

Try to re-install trough telnet in to corrupted standby CP with FOS 6.0.1a, with a little luck the unknown partition is working now.

I note in the past that some Customer and other User here in the community facing the same issue/problem with 6.0.1a with 48K.

Let me know.

TechHelp24
Super Contributor
Posts: 635
Registered: ‎04-12-2010

Re: FOS 6.0.1a to 6.1.2c upgrade fails

Hi,

you have said that 80% of the packages....

I have seen such an issue sometimes due to a bad Ethernet connection. I my case the CP cards were not connected with 100Mbit Full dulpex. Not all packages were transferred to the switch in a timeframe of 30 minutes. I have seen many collisions on the Ethernet port. Slow FTP performance was the result.

The download never finished in time. After 30 minutes a rollback was initiated by the switch.

In my case the switch was able to revert back to the old code on all partinions.

Maybe check your ethernet connections on the CP cards with the "ifmodeshow eth0" command. I have fixed the the interfaces to 100Mbit full duplex. I know about the disadvantage. It work for me very good.

Ask the network team if they can check the ethernet ports as well.

I don't know if this will fit to your issue.

Andreas

Join the Community

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