Performing server ignition

Last Updated : Dec 15, 2020 |

About this task

Server ignition is used to set the server's role and other key settings.

Procedure

  1. Using a browser, connect to the virtual machine. See Connecting to the uninitialized virtual machine.
  2. If you accept the license, select I Agree and click Next.
  3. Select the role that the server should perform and click Next. The subsequent menus vary depending on the chosen server type.
  4. If an additional hard disk was added during the virtual server deployment, details of the additional hardware appear. Otherwise the menu displays No new hardware available.

    For Media Manager support, it is recommended to accept the defaults. These are:

    1. Leave Format Hard Drive checked.
    2. Create a single partition for the whole disk. You can create up to 3 logical partitions on the physical disk.
    3. Leave the Mount Point name as /additional-hdd#1. The full mount path name for each partition is automatically configured by the system adding /partition1, /partition2 and so on, as a suffix.

      For example /additional-hdd#1/partition1. Note that it is this partition name, including /partition1, that should be used for Media Manager settings.

    4. Select Mount Hardware to have the additional disk automatically mounted.
  5. Click Next. Enter the server's network settings.
    • Remember that the LAN1 and LAN2 IP addresses and DHCP mode selections affect the virtual machine's PLDS Host ID used for licensing . Therefore, if using or planing to use local nodal licensing, we strongly recommended that before obtaining any licenses, you ensure that these are set to their final values.

    • The ignition process allows you to set the IP address for the LAN1 port only. The LAN2 port initially uses the default address 192.168.43.1. To avoid the duplicate IP address issue you should set the LAN2 address after ignition. This can be done using IP Office Manager or IP Office Web Manager.

    • For AWS virtual machine these settings affect the private IP address settings of the instance. They do not alter the public IP address values assigned by AWS.

    • Hostname is used as the DNS host name of the server.

      • For internal applications, this value must be reachable by DNS within the customer network. If the server is also supporting external applications, the host name also needs to be reachable by external DNS. Consult with the customers IT support to ensure that the host name is acceptable and that routing to the host name has been configured correctly.

  6. Click Next.
  7. Set the time source for the server.
    • Remember that the virtual machine uses the Timezone for licensing. Therefore, we strongly recommended that this is set to its final value before obtaining any licenses.

    • Select to use the time provided by an NTP server.

    • For a virtual server, if not using NTP, the server takes its time from the virtual server's host platform rather than allow manual configuration through the server menus.

    • By default, Secondary Server and Expansion System (L) servers automatically get their time from the Primary Server and you can only change the Timezone.

    • Select the companding setting to use. For telephone systems in North American locations and Japan, select μ-Law (also referred to as U-Law or Mu-Law). For most other locations, select A-Law.

  8. Click Next.
  9. Enter and confirm a new password.

    These are the passwords for various IP Office service accounts and also for the Linux accounts created on the server. Ensure that you note the passwords set.

  10. Click Next.
  11. If the selected Server Type was Application Server, select the services provided by the server.

    Unselected services remain installed but not running unless manually started.

  12. Click Next.

    The menu prompts which security certificate the server should use. This option is not used for Secondary Server and Expansion System (L) servers.

    • If you select Generate CA automatically, you must download the certificate from the next screen.

    • If you select Import CA, click Browse and locate the security certificate file that the server should use and click Upload.

  13. Select whether you want the server to be supported by Avaya through their EASG service and click Next.
  14. Check the displayed summary. Use the Previous and Next options to readjust settings if necessary.
  15. Click Apply.
  16. The browser menu will attempt to redirect you to the server IP address you configured during ignition. Click OK when displayed to access the server's IP Office Web Manager menus.

    AWS: For an AWS virtual machine the browser is redirected to the private IP address of the server. You need to manually change the browser address back to the instance's public IP address.

Next Steps