This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Upgrade from v4 to v5

Hello all,

We have several ASL firewalls deployed across the company, all our remote offices are connected via VPN to the HQ using ASL as well. All running v4.022 at the moment.

We're planning on upgrading to v5. The upgrade will be made gradually. Are there any important issues that we should be aware of ? We rely heavilly on the VPNs (especially at HQ where we have a lot of them) , anything important changed with the VPN in v5 ? Will importing the config from v4 work "out of the box" ?

Also, can I just upgrade to v5 as an nomal upgrade ? Or do I have to install the box from scratch with v5 and import the config ?

If anybody did this in a production environment, I would appreciate any info you might have.

Thanks,
Stefan

This thread was automatically locked due to age.

Parents

0 Javier Fernandez over 20 years ago

I just migrate from v4 to v5 without problems. There are few rules:

1) You need to migrate from 4.021 or later.
2) You need to do a backup on v4
3) Install v5 release 5.027 or 5.100 (forget about previous ones).
4) Restore the v4 (4.021 or letar) backup.

My system was 5 ethernets with PPTP, IPSec, httpd, close to 100 filter rules and close to 70 N.A.T. rules.... so.. quite complex. I migrated from 4.021 to 5.027 and once I check was working I upgrade into 5.100 using the Up2Date service. Anyway the migration to 5.100 is perfectly possible.
Cancel
Vote Up 0 Vote Down

Cancel
0 Stefan_ over 20 years ago in reply to Javier Fernandez

Thanks for the info, Javier. That's what I wanted to hear.

Regards,
Stefan
Cancel
Vote Up 0 Vote Down

Cancel
0 Javier Fernandez over 20 years ago in reply to Stefan_

Just one extra information. I have a Compaq server which is Pentium 4 2.4 GHz with 1 Giga memory and 80 GB disk.

I know is overkill but this is the smallest server I can buy.
Cancel
Vote Up 0 Vote Down

Cancel
0 Javier Fernandez over 20 years ago in reply to Stefan_

I finnaly went into troubles on DNAT/SNAT rules not working. Some of the imported rules works some other not. If I delete the not working one and recreate from scratch and wait for a while is working properly.

So I took the decision of roll-back the migration.
Cancel
Vote Up 0 Vote Down

Cancel
0 Stefan_ over 20 years ago in reply to Javier Fernandez

That sucks. If you recreated the NAT rule exactly as it was when imported, and it works, then it's clearly a bug in the config importing.

What about importing VPNs, did you have any problem with that ?
Cancel
Vote Up 0 Vote Down

Cancel
0 Javier Fernandez over 20 years ago in reply to Stefan_

VPN where imported properly and works.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Javier Fernandez over 20 years ago in reply to Stefan_

VPN where imported properly and works.
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data