Hi all - new to the list, so easy on me ;o)

Does anyone have any experience of running SSH of any kind on clustern
systems such as 
SUNCluster 2.2 or HP Serviceguard?

The problem I have been asked about is a SUNCluster, and basically ssh runs
fine on the 
logical host of the cluster until failover, whereupon the host key changes
and SSH thinks 
it's under attack.  Logic tells me therefore that the SSH running on the
logical host is using 
the host key of the physical host that the logical host happens to be on at
startup.

Logic further tells me that there are some ways that *might* be tried to fix
this, with their advantages 
and disadvantages

1) Have a install of ssh software just for the logical host which resides
completely on the shared 
    storage of the cluster (so that the same host key is always available)

2) have the same host keys on both nodes of the cluster (!)

Does anyone have any experience of SSH on commercial clustering software and
if so, is there a 
"proper" solution?  If not, will *my* solutions above work?

I ask this because someone's trying to get SSH up on this one cluster, but I
have just been 
given a project to roll out SSH to the entire enterprise's secured intranet,
on which there are lots 
of clusters of various types...

Thanks for your help.

-- 
| Gary Wilson, Senior UNIX Analyst,
| One2One UNIX Systems Group
| Email: [EMAIL PROTECTED]
======= http://www.one2one.co.uk =======





NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.


Reply via email to