Looking over the R71 Upgrade Options…
Are you sure you can upgrade R71.40, and R71.45 directly to R75?
According to the release notes, this is not possible without downgrading to R71.20 first.
I have not tested it yet. I wrote this to find out if you had.
In the R75 diagram, I had the paths from R71.40 and R71.45 pointing specifically to R75.40. I guess it wasn’t as detailed as it could have been in the R71 diagram. I made the change to the R71 diagram here, and on CPUG. Thanks for the feedback.
I Have launched the upgrade from R71.40 to R75.40 and it’s seems to works perfectly (into my labs).
I get few warning regarding vpn_table.def but I decided to go.
I have had a half dozen successful upgrades from R71.40 to R75.40 and then to R75.45. These policies were not too complex so far, but everything worked the first time. Testing a migration in the lab (when possible) is definitely a good practice. Shows you are putting a lot of thought into your environment. Good luck with the production upgrade!
Looking over the R71 Upgrade Options…
Are you sure you can upgrade R71.40, and R71.45 directly to R75?
According to the release notes, this is not possible without downgrading to R71.20 first.
I have not tested it yet. I wrote this to find out if you had.
In the R75 diagram, I had the paths from R71.40 and R71.45 pointing specifically to R75.40. I guess it wasn’t as detailed as it could have been in the R71 diagram. I made the change to the R71 diagram here, and on CPUG. Thanks for the feedback.
I Have launched the upgrade from R71.40 to R75.40 and it’s seems to works perfectly (into my labs).
I get few warning regarding vpn_table.def but I decided to go.
I have had a half dozen successful upgrades from R71.40 to R75.40 and then to R75.45. These policies were not too complex so far, but everything worked the first time. Testing a migration in the lab (when possible) is definitely a good practice. Shows you are putting a lot of thought into your environment. Good luck with the production upgrade!