FWSM upgrade problem 3.1.1->3.1.4

Unanswered Question
Feb 23rd, 2007

Hi -

Following the sw upgrade procedure from FWSM Configuration Guide (reload standby->switch active->reload primary->switch back) I had no problems upgrading with zero-downtime from 3.1.3 to 3.1.4

in active/standby failover pair.

Making the exact same procesure on another failover pair trying to upgrade from 3.1.1 to 3.1.4 causes be problems: When discovering a mate with the new version failover is forced off on both units, and no replication takes place. The upgraded device ends up in a pseudo standby state, and as I se it I now have the option of downgrading to 3.1.1 or upgrading the primary (with downtime) and then reestablish failover when having same sw on both units.

In the conf guide it is stated that 'You can upgrade from any maintainance release to any other maintainance release within a minor release, so jumping from 3.1.1 to 3.1.4 should not cause a problem.

Has anybody had similar experiences?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
dierigeng Fri, 05/25/2007 - 00:01

this can be a result of:

1.) different feature licenses (activation key)

2.) different underlying switch config (VLANS)

maybe post "show version"...

Gunar

Actions

This Discussion