This happens with both clustered and dual-boot systems (though it's a bit less common to have a dual boot system be an SSHD host, I do have a test machine that does...). I would say that it is perfectly natural to share the SSH server key between two machines that occupy the same internet address (either via clustering or dual-booting).
On Fri, Sep 26, 2008 at 5:39 PM, Steven S. Critchfield <[EMAIL PROTECTED]> wrote: > > I am implementing a DRBD cluster for a nfs fileserver. > > I have the following IPs setup. > data0 192.168.0.3 > data1 192.168.0.4 > cluster 192.168.0.2 > > So basically I can log into either of the machines via their own > IP address or the current primary machine via the cluster address. > > As I just experienced, if I had been logged in to a machine and it > fails(reboots), the secondary takes over as primary and assumes the > cluster address. When this happens right now, if I log back into the > cluster IP, I get ssh whining about the key being different. > > Does anyone have a good reason why one couldn't just use the same ssh > key on both machines so it doesn't cause ssh to whine after fail over? > > BTW, I do think I may have a write up if not a presentation eventually > out of this project. > > -- > Steven Critchfield [EMAIL PROTECTED] > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en -~----------~----~----~----~------~----~------~--~---
