AASTRA BluStar 8000i BAS-Mode Administrator Guides EN - Manual (Page 30)

Software Installation and Network Configuration
2-17 41-001391-00 Rev 03 – 04.2012
Rebuilding a Failed High Availability Server
If either the master or slave server fails, rebuilding the server may be necessary. This process synchronizes the failed
server with the properly functioning one. The two scenarios are outlined below.
Master server fails and slave server takes over
To get the master server back online:
Note:
A PS/2 keyboard and VGA monitor (both user-supplied) must be connected to the server to complete either of the fol-
lowing procedures. For details on these connections, refer to the ViPr
™
Application Server Quickstart Guide.
1. Insert the Application Server CD into the disk drive of the failed master server.
2. Switch the master server off.
3. Disconnect the master server from the network.
4. Switch the master server on, and confirm that it is booting from the CD. If it is not, make sure that the Application Server
CD is properly inserted.
5. At the command prompt, type install.
Note:
All data will be erased from the master server, and restored when synchronized with the slave server.
6. Wait for installation to complete and reboot the server.
7. Reconnect the server to the same network that the slave is on.
Note:
The server will now be running and connected to the network, but SIP Software must be installed.
8. At the login prompt, login as root with password blustar.
9. To begin software installation, type ./vconfig.
10. Select Rebuild Server (High-Availability) from the Network Configuration menu.
11. Select Master Server and continue the installation.
Note:
The master server’s password should still be blustar.
12. The certificates are now synchronized. At the prompt, press enter.
Replicating files will be displayed above the prompt.
13. A network configuration dialog will appear on the screen. Scroll down and select Apply Configuration.
14. The server software now installs. After pressing Enter at the prompt, the database will be resynchronized with the slaves.
Note:
The database synchronization may take some time. A progress bar will give an indication on the screen.
15. Select Yes at the prompt to reboot.
16. Once the reboot completes, login to the server and verify that the master server is active in one of the following ways:
a) Enter vipr_ha_is_active at a command prompt. This command returns yes if the master server is the active device.
b) Using a web browser, visit the Platform :: System Status page via the server Web UI.