Replacing a Linux server

Last Updated : Mar 20, 2025 |

Always follow the relevant safety and static handling procedures.

Before you begin

  • Always follow the relevant safety and static handling procedures.

  • The hard drives and power supplies on some particular servers are hot swappable. There is no need for chassis replacement. These items should can be replaced while the system is running. For further information see the Avaya Common Server installation guides.

  • If viable and appropriate, take server backup using Web Manager. Take a backup of all components, all data sets, and to a remote server. Note any parameters required for the new server’s ignition process

  • If not down already, shut down the server using Web Manager, then power off.

  • Ensure any resilient switch over of phones, hunt groups, voicemail services has taken place.

  • Remove and replace chassis with same capacity.

About this task

Use this procedure to replace all Avaya-supplied Linux servers.

Procedure

  1. Power on the system with local connectivity only
  2. Upgrade to the latest version of IP Office Server Edition Solution using Web Manager.
  3. Configure the server using the ignition process, using the same settings as the original ignition.
  4. Configure the server using IP Office Manager Initial Configuration Utility (ICU) to provide management connectivity and valid IP address. Use the same settings as the original ICU.
  5. Using Web Manager, on the Server Edition Primary server, run node restore with override for new ID .

    The system restores all configuration and data saved in the original backup except security settings. If this is an Application Server that is not a part of Server Edition, use Web Manager to restore.

  6. Reapply the security settings as these will be default.
    • If you are replacing a Server Edition Primary server, set all the non-default security settings using IP Office Manager.

    • If you are replacing a Server Edition Secondary server, a Server Edition Expansion System, or an Application Server, use the Synchronize Security feature of Web Manager.

  7. Validate status and configuration with Web Manager, Manager, and SSA.
  8. Perform a backup using Web Manager.
  9. Using IP Office Manager, administer new local licenses and delete old.

    Any local licenses will become invalid after 30 days. An offline license swap-out exists.