Upgrading SevOne NPM to 7.2.x from Previous Versions

Overview

The IBM SevOne Network Performance Management (NPM) 7.2 contains the following components.

Note:

To upgrade to SevOne NMS 7.2.0, the minimum mandatory version you must be on is SevOne NMS 7.0.1 or above. If you are on a version prior to SevOne NMS 7.0.1, please refer to Upgrading SevOne NPM to 7.0.x from Previous Versions.
To ensure the smoothest upgrade and not interrupt your user’s productivity, do not initiate your upgrade until you have reviewed all deprecations for each release you pass through on your upgrade path to 7.2. Deprecation notices are communicated in the IBM’s Release announcements. Please sign into the IBM Support Portal and subscribe to IBM SevOne NPM.
To complete your upgrade, all components must be on the same version. IBM supports one version back for the purpose of performing upgrades.
- Not all features will be enabled until components are on the same version.
- Some features will not work unless the components are on the same version.
Order of Upgrades
When multiple components of SevOne NPM are involved, the Solutions components (SDN, SD-WAN, and Wi-Fi) must be upgraded first followed by SevOne Data Insight and then, SevOne NMS.

If you have any doubts, please reach out to SevOne Support or Expert Labs for guidance before initiating the upgrade.

You must be on SevOne NMS 7.0.1 or above to upgrade to SevOne NMS 7.2.0.

Example# 1: SevOne NMS 7.0.1 or above to SevOne NMS 7.2.0 Upgrade on a small cluster

Cluster Setup
- Cluster consists of 4 x vPAS 20Ks, no DNCs, no HSAs
- Cluster is monitoring 800 devices, 79,200 objects, and 548,800 indicators
- Backfilled with 3 months of data
- SDB export configured

Timings

Upgrade takes ~30 minutes


Total Time of Upgrade	Time Taken
Instant Graph Downtime	5 minutes
Device Manager Availability	5 minutes
Collection Outage (SNMP / ICMP) - Data Loss	5 minutes
Alerting Outage	5 minutes
Trap Generation	5 minutes
SDB Publishing Outage	5 minutes
Reboot Cluster	3-5 minutes

Example# 2: SevOne NMS 7.0.1 or above to SevOne NMS 7.2.0 Upgrade on a large cluster

Cluster Setup
- Cluster consists of 20 x (PAS 200Ks, DNCs, HSAs)
- Cluster is monitoring 800 devices, 79,200 objects, and 548,800 indicators
- Backfilled with 3 months of data
- SDB export configured

Timings

Upgrade takes ~1 hours 45 minutes


Total Time of Upgrade	Time Taken
Instant Graph Downtime	3-5 minutes
Device Manager Availability	3-5 minutes
Collection Outage (SNMP / ICMP) - Data Loss	0 seconds
Alerting Outage	3-5 minutes
Trap Generation	Undetected
SDB Publishing Outage	n/a
Reboot Cluster	8-10 minutes

NOTE: Timings may vary based on your cluster.

When downgrading from SevOne NMS 7.2.0, you can only downgrade to SevOne NMS 7.1.0.

Example# 1: SevOne NMS 7.2.0 to SevOne NMS 7.1.0 Downgrade on a small cluster

Cluster Setup
- Cluster consists of 4 x vPAS 20Ks, no DNCs, no HSAs
- Cluster is monitoring 800 devices, 79,200 objects, and 548,800 indicators
- Backfilled with 3 months of data
- SDB export configured
Timings
- Downgrade takes ~44 minutes
- System is unavailable for ~6 minutes for the pods to restart

Example# 2: SevOne NMS 7.2.0 to SevOne NMS 7.1.0 Downgrade on a large cluster

Cluster Setup
- Cluster consists of 20 x (PAS 200Ks, DNCs, HSAs)
- Cluster is monitoring 800 devices, 79,200 objects, and 548,800 indicators
- Backfilled with 3 months of data
- SDB export configured
Timings
- Downgrade takes ~1 hour 30 minutes
- System is unavailable for ~6 minutes for the pods to restart

NOTE: Timings may vary based on your cluster.

To proceed with the upgrade, you must be on version SevOne NMS 7.0.1+.

Note: SevOne NMS 7.0.1+ and the other components in-use can now be upgraded to end version 7.2.0.

Important: SD-WAN Fortinet, SD-WAN VeloCloud (VMWare), SDN, and Wi-Fi are automatically upgraded when SevOne NMS is upgraded to 7.2.0.

You are now on version SevOne NMS 7.2.0.