An error is seen when you add a Gateway server

After a Gateway server is removed from an API Connect on-premises cloud, when the administrator tries to add the same Gateway server again an error is displayed.

Description

After a Gateway server is removed from an API Connect cloud, some scenarios exist where the configuration of the Gateway server might not be successfully cleaned. If the administrator tries to add the same Gateway server back in to the cloud, the following error is displayed:

...Error adding loadbalancer for API calls

In particular, this error can occur if the Management server for the cloud is deleted and re-created without first removing the Gateway server, that is, the Gateway server was not removed from the cloud.

Solution

This issue can be resolved by completing the following steps:

Manually remove the load balancer configuration from the Gateway server (the DataPower® appliance), by using one of the following methods:
- In the command-line interface, run the following command:
```
ssh datapower_hostname
login
co
int eth0
no standby
exit
write mem
```
  Where login is your login credentials, datapower_hostname is your DataPower host name, and your DataPower appliance is configured to use the network interface eth0.
- In the DataPower WebGUI:
  1. In the navigation tree, open the Network and Interface folders.
  2. Click Ethernet Interface.
  3. In the table, click the relevant interface row.
  4. Click the Standby Control tab.
  5. To delete the load balancing group, click X in the relevant table row.
  6. Click Apply.
  7. In the page header, click Save Config.
To prevent any port conflicts, remove all of the IBM API Connect domains from the Gateway server (the DataPower appliance). Otherwise, adding the Gateway server appears to be successful, but when APIs that are created by using the readded Management server are accessed, you receive 404 errors. The IBM API Connect related domains are of the format: APIMgmt_10_characters, where 10_characters is 10 alphanumeric characters.