Tracking when upgrades are needed and then carrying in an environment with multiple modules and pollers is complex and time consuming. When you get to having 5+ modules and more than a single additional poller it gets very hard to plan and then complete upgrades.
The following additional features will greatly help with planning and upgrading:
- There seems to be no way to report on software versions that are installed on each server, the web interface having an matrix like the following will enable you to quickly and easily confirm that an upgrade has been correctly applied and what needs updated (even better if it hooked into the new upgrade planner):
Server | NPM | NTA | SAM | IVIM | NCM |
---|---|---|---|---|---|
Main | 11.5.2 | 4.1.0 (Upgrade to 4.1.1) | 6.2.0 (Upgrade to 6.2.1) | 2.1.0 | 7.4 |
Additional Webserver | 11.5.1 (Upgrade to 11.5.2) | 4.1.0 (Upgrade to 4.1.1) | 6.2.0 (Upgrade to 6.2.1) | 2.1.0 | 7.4 |
Additional Poller | 11.5.2 | 4.1.0 (Upgrade to 4.1.1) | 6.2.0 (Upgrade to 6.2.1) | 2.1.0 | 7.4 |
Flow Storage | - | 4.1.0 (Upgrade to 4.1.1) | - | - | - |
- Downtime required to upgrade multiple modules in the same change window is huge, having to run multiple installers, configuration wizards in turn greatly increases the required time to complete the upgrade. If we could have a single installer (that's small) than would have a preflight check step of allowing you to download selected (i.e. one or all) installers and then install in a single run would be very helpful.
- The upgrade reporting seems to be hit and miss at best, currently I'm being told that we have 7 upgrades needed and it's only reporting one (and I know it's at least 2) [this I'll raise as a case].
Jon.
Top Comments