Adding a Secondary server using Manager

Last Updated : Jun 10, 2021 |
This process adds the secondary server to the primary server’s network. For a new server it also takes the server through its initial configuration.
Prolog information
Before you begin
  1. Start Manager. See Starting IP Office Manager.
    1. Click FileOpen Configuration.
    2. From the Select IP Office menu, select the primary server and click OK.
    3. Enter Administrator and the password configured for that user account during the primary server’s ignition. Click OK.
  2. Click Solution. On the Summary menu, on the right under Add, click Secondary Server.
  3. In the Add Secondary Server window, either:
    • Enter the IP address of the server and click OK.
    • Click on the search icon. Select the server from those listed and click OK.
  4. The initial configuration menu for the secondary server is displayed. This is similar to that shown for the primary server.
  5. In the System Mode, select one of the following:
    ADDITIONAL INFORMATION:
    System Mode
    Description
    Server Edition
    Select this option for a primary server that will use a PLDS file for licensing.
    Server Edition - Select
    Select this option for a primary server that will use a PLDS file for licensing that includes Select licenses. Note that if in a network, all servers in the network requires a Select license.
    Server Edition - Subscription
    Select this option for a primary server that will use subscriptions for licensing.
  6. Set a unique System Name for the system. This will appear in other administration menus and helps identify the particular server.
  7. If applicable, enter the Services Device ID issued for support of the server.
  8. Set the Locale to match the customer location. Set this accurately as it affects a number of default telephony settings that the system will then use.
  9. Set and confirm the Default Extension Password. This is used to set the extension password required to register IP extension unless a separate specific password is configured in the extension’s own settings.
  10. Using the Public LAN Interface control:
    1. Select LAN1 and check that the IP Address and IP Mask match the network settings that the server should use for its eth0 port.
    2. Select which DHCP Mode the server should support on the LAN.
      ADDITIONAL INFORMATION:
      Option
      Description
      Server
      The server will act as a DHCP server for the network on that interface. For its own address it will use the IP Address details entered in this menu.
      Client
      The server will obtain its IP address settings automatically from a DHCP server elsewhere on the network.
      Dial In
      This DHCP mode is not supported on Linux-based IP Office servers.
      Disabled
      The server will use the fixed IP address details entered in this menu.
    3. Select LAN2 and check that the IP Address and IP Mask settings match the network settings that the server should use for its eth1 port.
    4. Set the Gateway address for the customer network.
  11. Having set and checked the IP address and DHCP details, select which port, LAN1 or LAN2, will be used for outgoing connections from the customer network for general internet access. This choice adds a default IP route from that LAN to the specified Gateway address.
  12. Check that Server Edition Primary is set to the IP address of the primary server.
  13. If the customer network has a specific DNS Server, enter its address.
  14. Enter an Web Socket Password password. This password is used for the links to other IP Office servers in the network.
  15. Check the settings are all as required and match the customer network requirements.
  16. Click Save. The server’s configuration is opened in manager. At this stage it has not been saved to the system.
  17. Click FileSave Configuration
  18. Check that the Change Mode is set to Reboot and click OK.
  19. Click Next. The IP Office services on the servers are restarted using the new configuration.
  20. For non-subscription systems, assign the licenses required by the server in the same way as done for the primary server. See Assigning PLDS licenses.
Next steps