IBM Security Verify

 View Only
  • 1.  Can I upgrade an IGI virtual appliance

    Posted Mon July 26, 2021 11:14 AM
    I plan on setting up an IGI cluster. I already have my primary at 5.2.6.1 that I had before. I have my secondary but it is in 5.2.6.0 and I cannot set it up as a secondary because of the difference in fixpack. I tried reverting my primary to 5.2.6.0 but it had an error. 

    Considering this, I am thinking of upgrading the secondary to 5.2.6.1 first, then connect it to my primary. Is there a way for me to upgrade my secondary to fixpack 2 while its not yet in the cluster, and while its not yet configured? Since its new, when I go to the VA, it still shows the startup screen of selecting either to setup a primary or a member node.

    I tried using the FileUploadUtility.jar method and was able to upload the file successfully.
    When I go to the CLI and entered igi>upgrade>install, it didn't do anything and just says this:

    Thank you very much to anyone who can share their thoughts.



    ------------------------------
    Derrick Nidar
    ------------------------------


  • 2.  RE: Can I upgrade an IGI virtual appliance

    Posted Tue July 27, 2021 10:19 AM
    Hi Derrick,

    This is an interesting scenario. I was thinking, What if you setup/configure secondary node in the cluster first and later apply the fix pack to it. Doesn't IGI allows to setup a member node in cluster if there is a mismatch in fix pack?

    ------------------------------
    Jaskeerat Singh
    ------------------------------



  • 3.  RE: Can I upgrade an IGI virtual appliance

    Posted Tue July 27, 2021 10:48 AM
    Hi Jaskeerat,

    That was actually my initial plan, but IGI doesn't allow clustering when the primary and member nodes are of different versions/fix pack. 

    I am planning to explore 2 approaches:
    1. Change the primary to 5.2.6.0 (since the firmware backup is still in that fix pack). I did this but its showing an error on the last step for some reason. So I am still searching for answers there.
    2. Upgrade the member node to 5.2.6.1 prior to clustering. But seems the process indicated in the fix pack read me documentation isnt working if its not initially setup or not yet clustered.

    Regards,
    Derrick

    ------------------------------
    Derrick Nidar
    ------------------------------