Igniting the server

Last Updated : Oct 07, 2024 |

About this task

Each server needs to be go through a server ignition process. During this process, the server’s particular role is configured and key settings are set.

  • To perform ignition, you need the current IP address of the server. That is shown on the monitor connected to the server.

    • For servers supplied pre-installed by Avaya or installed using automatic USB installation, the address is 192.168.42.1/255.255.255.0.

  • Ignition is performed by browser from another PC.

  • You can only run the ignition process once. To rerun the process requires a complete software reinstall.

  • If the Ignition process is not completed, for example if you click Cancel, the system displays the Ignition menu when you next login.

Procedure

  1. On a PC on the same network as the server, open a web browser.
  2. Enter the address https://<Server_IP_Address>:7070.
  3. Because the browser does not have a copy of the server's root certificate, it displays a warning regarding an unsafe connection.

    • You can ignored this at this stage. Proceed with connecting your browser.

    • Following ignition, you can download the server certificate and add it to the certificate repository used by the browser.

  4. Note the WebLM ID and PLDS ID values displayed on the logging menu. These are required for licensing or subscription of the server.
  5. Login to the server. The password depends on how the software was installed:
    1. In the User Name field, enter root.
    2. In the Password field, enter one of the following:

      • If you installed the software manually, use the password you specified during that process.

      • If the software was installed automatically, use the password Administrator.

    3. Click Login.
  6. The server displays the Accept License menu. Click I Agree and click Next.
  7. The server displays the Server Type menu. Select the particular IP Office role the server will perform:

    Server Type

    Description

    Primary (Server Edition)

    If setting up an IP Office network, this is the first type of server that must be added to the network.

    Secondary (Server Edition)

    This type of server supports the same services as the primary and can temporarily take overs its role in some situations (known as “resilience”).

    Expansion (Server Edition)

    This type of server can be used to support additional IP telephony services in a primary server’s network.

    Application Server

    This type of server can be used in a number of ways:

    • Within a primary server network, it can be used to host the Avaya one-X Portal application service (removing it from the primary). This can be used when the primary is hosted on a lower specification server.

    • For an IP500 V2 system with a Unified Communications Module installed, it can be used to replace the modules Avaya one-X Portal service. This option increases the number of voicemail ports and users supportable by the Unified Communications Module.

    • An application server can also be ignited with no user services and then used as a backup server for other servers.
  8. Select the required server role and click Next. The following menus vary depending on the selected role.
  9. The server displays the New Hardware menu. This contains details if any additional hard drive installed in the server. This is required for a primary or application server supporting the Media Manager application. If the server has an additional drive, check the following steps. Otherwise click Next:
    1. For a new server, select Format Hard Drive. Only select this if you are sure that all data on the hard drive should be erased. For example, do not select it if reigniting the server as part the process to recover a failed server.
    2. Select Mount Hardware.
    3. Leave all the other settings at their defaults unless you have a specific reason to be otherwise. Note the Mount Point path settings. You need this as part of the Media Manager application configuration.
    4. Click Next.
  10. The server displays the Configure Network menu:
    1. Ensure that the Hostname is unique within the network domain. It can be a string of characters 63 characters in length. The characters can be upper-case or lower-case letters A through Z, digits 0 through 9, the minus sign (-), and the period (.).
    2. Check that the settings match those required for the customer network.
    3. Click Next.
  11. The server displays the Time & Companding menu:
    Important:

    • An accurate time source and settings are vital to many functions, including subscriptions and any services that use certificates.

    1. Select Use NTP Client and set the Timezone.
    2. On server’s that support telephony operation, select the Companding mode.

      • µ-law is typically used for North America and Japan.

      • A-law is used for Europe and other parts of the world.

    3. Click Next.
  12. The server displays the Change Password menu. Set the passwords as required. If igniting a server for addition to a network of servers, set passwords that match those used on the network's primary server.

    Option

    Description

    ‘root’ and ‘security’ password

    This sets the initial password of both the Linux root user account and the IP Office security administrator.

    • After ignition, the passwords for these accounts can be changed separately.

    ‘Administrator’ password

    This sets the initial password of both the Linux and IP Office Administrator user accounts.

    • After ignition, the passwords for these accounts can be changed separately.

    ‘System’ password

    This sets the system password of the IP Office system.
    1. Set the passwords as required and click Next.
  13. On an IP Office Application server, the server displays a Configure Services menu:
    1. Select the services that the application server should provide. The voicemail service is only supported when using the application server to support an IP500 V2 system.
    2. Click Next.
  14. On a primary or application server, the server displays the Security menu:
    1. Select whether to upload a certificate for the server or to let the server generate a self-signed certificate.
    2. Select whether you want the server to support the Avaya EASG server. Enabling EASG is a requirement for systems included in an Avaya IPOSS support contract.
    3. Click Next.
  15. The server displays the Review Settings menu:
    1. Check that the settings are correct. Use the Back control if necessary to change or correct any of the settings.,
    2. Use the certificate links to download copies of the server’s certificate file.
    3. When satisfied with the settings, click Apply.

Next Steps

You can now proceed to the initial configuration of the server. The process depends on the selected server role:

Related information
Server Software Installation