Building a HS Mutiny system pair
Firstly you are going to need 3 IP addresses on the current VLAN that Mutiny is attached to:
- 1) Current Mutiny IP address (will become the Floating Address).
- 2) New additional IP address for the Primary appliance.
- 3) New additional IP address for the Secondary appliance
Starting point: Trial mutiny system on a virtual appliance moving to physical HS pair
1.1 Upgrade your current mutiny trial to the current release
1.2 Take a snapshot and save the backup to your PC
1.3 Shutdown your trial VM (do not delete from host until stage 2 is complete)
2.1 Rack up and power on the first new appliance this will be the new Primay system
2.2 Use the Console to put the IP address (1) onto "eth1" and set the default gateway etc.
Installers tip: if you cannot locate eth1 on the rear of the appliance (as it's not labelled from the factory) just use the console to configure eth1 then try and ping it from a PC, if it doesn't respond just swap the network cable over to the other port and if it pings your done. The single nic on it's own is used for out of band access to the appliance bios.
2.3 Web onto the new appliance
2.4 Upload and restore your backup, leave time to restore backup and do not reboot, ignore errors regarding serial number changes at this stage.
2.5 Check the restore is complete and users, views, nodes and contacts all exist as before (if the system drops off the network check on the console that the IP address is on the correct nic as it may have moved during restore)
2.6 Take note of the new serial number (just above the licence panel in [Admin]=>[System] ) and submit a licence request
3.1 Rack up and power on the second new appliance this will be the Secondary system
3.2 Use the console to put a new IP address (3) onto "eth1" and set the default gateway etc.
3.3 Web onto the new secondry appliance
3.4 Take note of the new serial number (just above the licence panel in [Admin]=>[System] ) and submit a seond licence request
This will allow us to generate you new licence and then we can continue with the configuration.
DO NOT Progress any further until you have obtained your Mutiny Hot-Stanby Licence.
4.1 Put the whole Mutiny system into Global Maintenance Mode from "[Admin]=>[Contacts]"
4.2 In "[Admin]=>[Network]", Change the eth1 (important) IP address of the Mutiny system to be IP address 2 (above). Set the eth0 address to a private, non-routetable network (e.g. 10.1.1.2). When you click [Update], you will lose connection to the Mutiny system, so you need to re-connect using the IP address (2). If you cannot re-connect, go to the Console and set up the IP addresses from there.
(as a safe alternative to the above, connect a laptop to the the eth0 port on the back of the Mutiny appliance and the connect using the IP address 172.17.77.77 (set your laptop to be 172.17.77.100 or similar) and do the above.
4.3 Reconnect to Mutiny on the new IP address (2) and go to "[Admin]=>[System]". You are going to need to assign a unique system name for this Mutiny system ( hs1-mutiny.yourdomain.local ).
4.4 Set up the Mutiny as shown below but DO NOT click [Update] yet (note that the Netmask for the VLAN will need to applied everywhere it is asked for) :
4.5 Now scroll to the bottom of the page and install the hot-standby licence and press [Update] (DO NOT Reboot!!!)
Large parts of the Mutiny system will now restart and after 30 seconds, you should be able to log back on to Mutiny using IP address (1) (the appliance's old IP address and the new Floating address).
4.6 If all is OK, you can take Mutiny out of Global Maintenance.
5.1 Web back on to the new seconday appliance
5.2 Setup [Admin]=[SMS/modem] to match the primary
5.3 Setup [Admin]=[Network] and configure any static routes you have if required
5.4 Setup [Admin]=>[system] as shown below, NO NOT PRESS UPDATE and also duplicate the email and snmp settings from the primary. Scroll down the page add the new licence and now, when all the page has been completed correctly, you can press [Update].
The polling engines will now restart and if it is all correct and it can see the primary server, it will come back up as a secondary system.
There will be a delay before the secondary system can take over as the primary as the databases will need to replicate.
5.5 Connect to the maintenance web interface which will be either http://ip address (3):81or https://ip address (3):444 of the secondary appliance and check it is now a secondary system. It should look like this;
Please note that you will no longer be able to log into the secondary system front end on its eth1 IP address (3) you must use the Floating address to administer mutiny in the normal way. The Secondary can be accessed on its maintenance interface on eth1 port:81 or port:444
Remember to turn off global maintenance mode in [Admin]=>[Contacts]
If this has all worked, get yourself a beer, you deserve it! (Mutiny promotes safe drinking see; www.drinkaware.co.uk)