On May 14, 2010, at 6:00 PM, [email protected] wrote: > > Can someone give me a hint about what I might be doing wrong. > I'm upgrading fwsm from release 3.1.13 to 3.1.17. > I uploaded the new image to the secondary module, saved the config and > reloaded the module. > It came up totally blank. Every config on each context was gone. > So I sat it up again as failover, and the primary module replicated the > complete config of all contexts. > Now I'm a bit afraid what will happened when I reload the primary module. > Has any experienced anything like this. > > /Arne
I've seen very strange things happen when you run a failover pair of FWSM's with different versions - if you can get them to run at all. I've seen them both become active, both go beserk and other random strangeness. If I recall correctly Cisco advises you to do both upgrades at the same time. Hope this helps... Overall I think they are great, but the upgrade procedure could get a facelift ;-) Regards Rutger _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
