The page is intended to help users of the FirstWave monitoring modules to ensure upgrades of the software has minimal impact to their environments.

  1. Recommended Pre Upgrade Checks

    1. Operating System Checks

      1. Check free disk space
      2. Baseline CPU and memory utilisation
      3. If possible, a snapshot (and or full/incremental backup depending on your organisation's backup strategy) of the server should be recommended 

    2. FirstWave Module Checks

      1. opCharts node status checks - take note of the node and status counts
      2. opEvents - confirm events are being received on the pollers and (where applicable in a opHA environment) forwarded to the primary.
      3. opHA - on the primary opHA home page, confirm all pollers and primary are showing all green. If possible screenshot the server/en/omk/opHA/verify page for validation after upgrade
      4. NMIS9 - ensure custom models and model edits are in the /usr/local/nmis9/models-custom directory NOT the models-default directory
      5. opConfig - At this time upgrades will overwrite custom pharsebook's (pb's), if you have custom pb's make a copy and save to separate directory

  2. Post Upgrade Checks

    1. Operating System Checks

      1. Check free disk space
      2. Confirm CPU and memory utilisation is within pre upgrade baseline levels

    2. FirstWave Module Checks

      1. opCharts - confirm node and status counts are the same or similar post change.
      2. opEvents - confirm events are being received on the pollers and forwarded to the primary.
      3. opHA - on the primary opHA home page, confirm all pollers and primary are showing all green. 

Upgrade Rollback 

If there are issues after the upgrade of our modules, it is recommended that the upgrade is rolled back to ensure server functionality is restored as soon as possible.

We mention more about this in Restore Backup after Install.

Before rollback, FirstWave recommend that you capture support zips for NMIS and OMK modules so the FirstWave support team can analyse any issues that might have occurred.

  • No labels