IBM SevOne NPM should support concurrent HSA adds

IBM SevOne NPM should support concurrent parallel HSA adds, if possible. For instance, one of our clients has 40 peers in their PAS/HSA pair environment and requires the ability to 'repave' by decommissioning and re-adding many peers at once as part of their disaster recovery requirements. However, this process is currently done manually on a per-peer basis and takes days, with HSA peers added in a serial way after being removed, as is supported in the SevOne Best Practices Guide.

Our client would benefit from being able to add multiple HSAs concurrently, assuming they have a 40-peer cluster of single PAS peers without HSA. While our documentation does not explicitly support concurrent HSA adds, the 'SevOne-hsa-add' process and API calls in NMS 7 and later allows for starting multiple HSA adds at once, but it fails during database I/O operations.

A recent test by Support attempted to add three HSAs in parallel and failed on two out of three attempts, with only the first add succeeding. To address this, IBM SevOne NPM should ideally support multiple concurrent HSA adds. However, this could be difficult to implement due to race conditions and other unpredictable cluster details. If this is not feasible, sanity checking to prevent simultaneous HSA adds would be ideal, similar to the cluster peering lock that is placed when a PAS peer is added, until such a time that this feature is possible.