Saturday, April 23, 2005

Static IPs and server updates

The failover is up and running, with heartbeat disabled and certainly not fully upgraded. But several major goals were accomplished:

1) Failover is connected to Main. Thus we can edit Failover by sshing into Main, and then into lin2. We can also do quick backups via rsynch to make ourselves comfortable even if it's not fully operational.

2) Failover is a static IP with successful internet access. This make configuring certain settings much easier because I can only use DHCP to assign one IP via mac address, due to crappy web interface to the router.
2a) I got the static IP working by making sure that the gateway (192.168.1.1) was explicitly set in the network settings for the external network card.
2b) Static IP continues to work even with router firewall and server firewall running. This is good, because previously I was unable to get it to work with the firewalls running.

3) Heartbeat and rsynch are both off, so nothing crazy can happen. Rsynch has been removed from the crontab on Failover and Heartbeat has been removed from runlevels 3 and 5, so it won't activate on a reboot. We should be able to upgrade and test failover at our leisure, and keep it updated with manual rsynchs so it is ready to go if something happens."

2 comments:

Michael said...

Congrats, man. This is huge. Anything you need us to do to try and blast/test the server?

lmortenson said...

Yeah, bring in those SUSE cds so I can do some updates and see if I can get the failover updated with the latest kernel and other goodies.