When running an APIConnect Gateway outside of Kubernetes it is often required to replace a DataPower VM or physical appliance. These steps listed here what is suggested as the process for completing this.

1) Make sure the DataPower that you are going to remove is not the Primary for each of the gateway peering objects.

https://www.ibm.com/docs/en/datapower-gateway/10.6.x?topic=mode-viewing-statistics-about-peers-in-peer-groups

1b) If yes, please switch another gateway peering member to the Primary:

https://www.ibm.com/docs/en/datapower-gateway/10.6.x?topic=enforcement-switching-replica-primary

2) In the DataPower that you are going to remove, disable the APIC domain.

3) In the remaining DataPower, for each of the gateway peering objects, remove the DataPower in the “peers” list that you are removing.

4) In the two existing physical IDG, for each of the gateway peering objects, click Remove stale peers: https://www.ibm.com/docs/en/datapower-gateway/10.6.x?topic=mode-removing-stale-peers-from-peer-group

5) Start the replacement DataPower and configure the API Connect Gateway Service so that it has has the same details as the exisiting ones.

6) In the two existing DataPower, for each of the gateway peering objects, add the new Datapower into the “peers” list.