Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 28 subscribers
  • Views 1789 views
  • Users 0 members are here
Options
Suggested
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

Upgrading XG to V18 Issues

Carlos Carrasquillo

So I have a customer with 2 XG230 on HA (Active Passive).  They have some failover internet issues and support basically told me that I need to upgrade them to v18 because the rules that we need are part of the new SD-WAN solution on v18.  I have another customer that currently has a pair of XG430 unused and they let me borrow.  I did perform a boot fresh install of 17.5.9 like my customer with the XG230 is currently on.  I restored a backup from the XG230 and set up HA.  then I went through the procedure to upgrade to v18 and I have not been able to successfully upgrade to v18 on my test lab.

I tried doing the upgrade through the gui from 17.5.9 to 18.0.1 and it never update the primary and bricked the HA.  Re-imaged the HA and tried it again going to 17.5.9 to 17.5.13 and that upgrade worked but then v18 will not show under the upgrade tabs so I downloaded the file and perform the upgrade manually but it updated the secondary and not the primary and broke HA.   Then I tried all the same step but without HA setup and I have not been able to upgrade from 17.5.9 or from 17.5.13 to 18.0.1   just keeps rebooting to the v17 version.   I have tried everything.  Any suggestions will greatly appreciate it.  This customer basically works almost 24/7 so I have a very small work window and that is why I'm trying to find the best way to perform this upgrade with a minimal amount of time.



This thread was automatically locked due to age.
Parents
  • 0

    Upgrade from V17.5 MR13 to V18 is not supported, right now. 

    V17.5 MR9 should work fine. 

    So after the upgrade (both nodes will restart), you need to verify the reason for this blocker.

    Check /log/migration.log for more information, after the migration. 

Reply
  • 0

    Upgrade from V17.5 MR13 to V18 is not supported, right now. 

    V17.5 MR9 should work fine. 

    So after the upgrade (both nodes will restart), you need to verify the reason for this blocker.

    Check /log/migration.log for more information, after the migration. 

Children
  • 0 in reply to LuCar Toni

    I tried viewing it from putty and it was empty so I PSCP it over to the computer and it copied it but it was empty.  I grab a random log(ips.log) and copied it over to my computer and it show data from IPS so I know my command is good.  I tried doing a migration again and check the logs after and still nothing.  I even reimaged the firewall and tried the migration afterwards and still the same issue.