6.0.0-747 to 6.1.0-304 not supported?

Unanswered Question
Apr 26th, 2008

I'm currently running AsyncOS 6.0.0-747 and when I view available upgrades the only choice I have is 6.0.0-754.

Can I not upgrade to 6.1.0-304 directly? If not, why?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
tedski_ironport Sun, 04/27/2008 - 13:41

We were expecting to see 6.1.0-301 availalable this morning but now only see 6.0.0-754 (we are at 6.0.0-747). We received the "Release Notification" and scheduled our upgrade for today. Where did 6.1.0 go? Was it pulled due to major bugs?

tedski_ironport Sun, 04/27/2008 - 13:48

apparently we need to FIRST go to 6.0.0-754 and THEN we can see 6.1.0-304 (this was NOT a prerequisite when we upgraded our TEST boxes from 6.0.0-747 directly to 6.1.0-301).


GRRRR..... :x

chhaag Sun, 04/27/2008 - 16:20

Depending on the severity of the security patch, we sometimes remove un-patched builds from our download servers, this differs from standard release protocol.

Pulling the un-patched builds not only ensures our customers run the most secure releases available, but also reduces the number of upgrade paths our QA team must qualify. This allows us to release the patch much faster than would normally be possible.

Our apologies for the extra step and inconvenience. Fortunately, critical security patches are fairly rare, this is the first of 2008 and there was just one in all of 2007.

regards,

Chris Haag
Manager, Technical Support

aliebrahim Mon, 04/28/2008 - 06:14

Depending on the severity of the security patch, we sometimes remove un-patched builds from our download servers, this differs from standard release protocol.


However, isn't 6.1.0-304 already patched? Therefore why pull this from the download servers?
bpoyner_ironport Mon, 04/28/2008 - 15:56

However, isn't 6.1.0-304 already patched? Therefore why pull this from the download servers?


I wondered the same thing. To get to the latest I was forced to do the two step upgrade process from 6.0.0-747 to 6.0.0-754, and finally to 6.1.0-304. This was twice the downtime estimate I gave to my boss, as previously there was a direct upgrade path from 6.0.0 to 6.1.0.
Donald Glynn Mon, 04/28/2008 - 20:14

Correct you can not upgrade from that version.

The qualified upgrade paths to this release are:
From: Version 5-5-1-015 To: Version 6-1-0-304.
From: Version 6-0-0-754 To: Version 6-1-0-304.
From: Version 6-1-0-210 To: Version 6-1-0-304.
From: Version 6-1-0-226 To: Version 6-1-0-304.
From: Version 6-1-0-228 To: Version 6-1-0-304.
From: Version 6-1-0-231 To: Version 6-1-0-304.
From: Version 6-1-0-301 To: Version 6-1-0-304.
From: Version 6-1-0-302 To: Version 6-1-0-304.


I'm currently running AsyncOS 6.0.0-747 and when I view available upgrades the only choice I have is 6.0.0-754.

Can I not upgrade to 6.1.0-304 directly? If not, why?
Doc_ironport Mon, 04/28/2008 - 20:21

However, isn't 6.1.0-304 already patched? Therefore why pull this from the download servers?


It's not 6.1.0-304 which was pulled, it's 6.1.0-301.

It seems 6.0.0-747 to 6.1.0-301 was a certified upgrade path, but 6.0.0-747 to 6.1.0-304 isn't.

Either way it was going to require 2 upgrades to get from 6.0.0-747 to 6.1.0-304, via either 6.0.0-754 or 6.1.0-301 (if it was still available).

These intermediate upgrades are unfortunate, and we try to limit how often they are needed, but occasionally they are required for some version pairs.

Actions

This Discussion