Updating the network configuration

Last Updated : Apr 01, 2022 |

About this task

Server networking information can be updated by using the netSetup command in a Linux® shell. The netSetup command guides you through the process of updating the following settings:

  • Time zone and UTC

  • Date and time

  • Hostname

  • IPv4 address

  • IPv4 Netmask

  • Gateway IPv4 address

  • IPv6 autoconfigure

  • IPv6 address

  • IPv6 prefix length

  • IPv6 gateway address

  • Domain name

  • Static route(s) (virtual appliance and systems with out of band management enabled only only)

  • Up to three DNS server IPv4 addresses

  • Up to three NTP server IPv4 addresses or hostnames

  • Out of band management IPv4 address

  • Out of band management IPv4 netmask

  • Out of band management IPv4 gateway address

Before you begin

Stop Avaya Aura® MS before changing the network configuration. See Implementing and Administering Avaya Aura® Media Server.

Procedure

  1. If you are making changes to the IP address or FQDN you must disenroll AAMS cluster from System Manager first.
  2. Log in to a Linux® shell using the customer account.
  3. Type the following command:

    netSetup

    Follow the on-screen prompts to update the network settings.

    For Avaya Appliance Virtualization Platform systems, accept the system-determined default value for the Enable static route prompt. Enable static route has a default value of Y for Avaya Aura® Appliance Virtualization Platform systems. When you press Enter with a value of Y, the system displays prompts that allow you to reconfigure the Utility Services static route.

    For all appliances, if the secondary network interface is enabled, and specific static routing is required, change the value to Y and proceed to configure the additional static routes.

    All other virtual appliance installations must use the default value of N for Enable static route.

  4. Perform the following steps if you changed the IP addresses or hostname.
    1. Navigate to EM > System Configuration > Network Settings > IP Interface Assignment.
    2. IP Interface Assignment fields show errors, due to the IP address change. Select valid IP addresses from the drop-down menus for each field showing Invalid.
    3. If you are using security certificates with information dependent on FQDN or other server specific information, create new certificates. To update the certificates, navigate to EM > Security Certificate Management.
    4. If this server is a member of a load sharing cluster or High Availability cluster, then navigate to EM > Cluster Configuration > Server Designation.

      On each server, ensure that the IP address you just changed is updated.

    5. If this server is a primary server of a master cluster, then replication clusters that point to the master cluster must be updated with the new address of this server.

      On the primary node in each replication cluster, navigate to EM > Cluster Configuration > Replication Settings > Master Cluster Primary Node Address.

    For more information on configuring each item, see Implementing and Administering Avaya Aura® Media Server.

  5. You must restart the server. Use one of the following methods to restart the server:

    • Type reboot in a Linux® shell.

    • Press the power button to turn the server off and then press the power button again to turn it back on.

    • Press the reset button until the server restarts.

  6. Enroll the cluster with SMGR.

Next Steps

If required for your solution, enroll the cluster with Avaya Aura® System Manager.