Change the IP address of an Expressway node that's part of a hybrid resource and registered to the cloud. Requires steps in Cisco Webex Control Hub, on the target Expressway node, and on its peer nodes.
Before you begin
This procedure is limited in scope to changing the IP address of one, non-primary, Expressway node in your connector host cluster. It does not extend to changing the FQDN of a node or the cluster, changing the primary node, or otherwise modifying the cluster.
Identify a maintenance window for this task and note the following:
For a cluster of multiple nodes, if you're changing the IP address of one Expressway node, you won't affect the service for your users.
For a single node registered to cloud , changing the IP address of this node results in downtime for users.
Put the node in to maintenance mode in Control Hub:
Remove the old/current IP address, of the peer that is changing, from the clustering configuration on all nodes:
Edit the A/AAAA record for the affected node's FQDN to resolve to the new IP address (if there is an address record for the node).
Use nslookup or similar tool to verify the updated record in DNS.
Change the IP Address on the Expressway node which is changing () and save.
Expressway prompts you for a restart.
Restart the affected Expressway node.
You don't need to restart other nodes in the cluster.
Add the new IP address, of the peer that has changed, to the clustering configuration on all nodes:
Move the Expressway out of Maintenance Mode in Control Hub:
Control Hub now shows the node as Initializing, then Online. This update might take a few minutes.