Starting from Release 3.11, you can modify the network settings of an Avaya Aura® Web Gateway node from a single location by running the cliChangeNet.sh script from the node CLI. You can configure the following settings:

• IP address of the node

• Subnet mask

• Host name of the node

• Domain name of the node

• Default gateway IP address

• DNS server IP address

• Default search list

• NTP server IP or FQDN

• Time zone

• Country

The following are examples of scenarios where you can use the cliChangeNet.sh script:

• Re-configuring network settings for your Avaya Aura® Web Gateway standalone system or cluster.

• Updating network configuration for an Avaya Aura® Web Gateway node. For example, when moving one or several Avaya Aura® Web Gateway nodes to another data center.

• Changing your DNS or NTP servers.

cliChangeNet.sh script limitations

• You cannot use the cliChangeNet.sh script in AWS OVA-based deployments.

• You cannot use the cliChangeNet.sh script to change the following Avaya Aura® Web Gateway network settings:

  • Front-end FQDN

  • Virtual IP address

  You also cannot use cliChangeNet.sh to update the System Manager FQDN.

  To update these settings, use the Avaya Aura® Web Gateway configuration utility.

• If you change the IP addresses or FQDN of an Avaya Aura® Web Gateway node, you cannot restore the data using backups created before you made these network changes. This limitation applies to manual and automatic backups.

• If you perform a rollback after changing Avaya Aura® Web Gateway IP addresses or FQDNs, Avaya Aura® Web Gateway continues to use these new IP addresses or FQDNs after the rollback. The rollback process does not revert IP addresses or FQDN changes.