IBM Verify

IBM Verify

Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  9.0.5 Upgrade and Clustering

    Posted Thu June 28, 2018 12:51 AM
    Reading through the release notes for 9.0.5: https://www.ibm.com/support/knowledgecenter/SSPREK_9.0.5/com.ibm.isam.doc/productoverview/task/tsk_upgrading.html

    One thing that seems to have changed is the requirement remove all cluster nodes from the cluster whereas previously you always had to.

    Is this an oversight in the documentation or is it ok (safe?) to upgrade the Primary node, let it reboot, then upgrade the secondary without any configuration changes.

    Looking to run through this in a lab but wanted confirmation this is an intentional change.

    ------------------------------
    Peter Lambrechtsen
    ------------------------------


  • 2.  RE: 9.0.5 Upgrade and Clustering

    Posted Fri June 29, 2018 03:22 AM
    Hi Peter,

    I asked our internal support folks. They confirm that you don't need to break the cluster to update to 9.0.5.0.
    They did say (as written in release notes):
    Upgrade the Primary Master and DO NOT REBOOT IT BEFORE UPGRADE THE SECONDARY IF USING THE INTERNAL DB.

    Cheers... Jon.


    ------------------------------
    Jon Harry
    Consulting IT Security Specialist
    IBM
    ------------------------------



  • 3.  RE: 9.0.5 Upgrade and Clustering

    Posted Tue July 10, 2018 10:05 AM
    Hi John,
    is this also true for external DB? Shouldn't make a difference as you need to update the DB separately anyway.
    Thanks,
    Jens

    ------------------------------
    Jens Petersen
    ------------------------------



  • 4.  RE: 9.0.5 Upgrade and Clustering

    Posted Tue July 10, 2018 10:59 AM
    Hi Jens,

    I'm pretty sure that the "don't reboot" requirement is specific to using the internal database and is related to how the internal database is updated during the upgrade process.

    If you're using an external database the the schema changes have to be made manually using the scripts provided on the appliance.  The release notes cover this.

    I must caveat all this by saying I have not done an update with an external database.  If it was me I'd want to test any upgrade process before doing it a production system (or have a verified backup).

    Cheers... Jon.

    ------------------------------
    Jon Harry
    Consulting IT Security Specialist
    IBM
    ------------------------------



  • 5.  RE: 9.0.5 Upgrade and Clustering

    Posted Tue July 24, 2018 01:12 PM
    My assumption was after upgrade the appliance is automatically restarted and the install guide also says that. So the caution is not to reboot manually after the automatic reboot soon after the upgrade?

    https://www.ibm.com/support/knowledgecenter/SSPREK_9.0.5/com.ibm.isam.doc/productoverview/task/tsk_upgrading.html
    Use the online update server.
    1. Meet the following conditions:
      • A valid license is installed on the appliance.
      • The appliance has network connectivity to the online update server.
    2. Log in to the local management interface. If you are upgrading a cluster, log in to the local management interface of the primary master first.
    3. Select Manage System Settings > Updates and Licensing > Available Updates.
    4. Click Refresh.
    5. Select the firmware update.
    6. Click Install. The firmware update might take a long time to complete, depending on the bandwidth that is available to the appliance. After the update is successfully applied, the appliance automatically restarts.


    ------------------------------
    Harish Duvvuru
    ------------------------------



  • 6.  RE: 9.0.5 Upgrade and Clustering

    Posted Fri July 27, 2018 12:27 PM
    Edited by Nick Lloyd Fri July 27, 2018 12:27 PM
    Correct, do not reboot immediately after the appliance comes up from the firmware upgrade.

    ------------------------------
    Nick
    ISAM Level II Support

    ------------------------------