Hi all,
I've set up a two node Solaris zone cluster with a SUNW.LogicalHostname resource that can fail over between nodes for high availability.
# clrg show
=== Resource Groups and Resources ===
Resource Group: oracle-rg
RG_description: <NULL>
RG_mode: Failover
RG_state: Managed
Failback: False
Nodelist: vutora01-b vutora01-a
--- Resources for Group oracle-rg ---
Resource: vutora01-rs
Type: SUNW.LogicalHostname:5
Type_version: 5
Group: oracle-rg
R_description:
Resource_project_name: default
Enabled{vutora01-b}: True
Enabled{vutora01-a}: True
Monitored{vutora01-b}: True
Monitored{vutora01-a}: True
The resource (group) can switch over seamlessly between nodes, but when we try to access the zone server via the logical host name over SSH, we find that the SSH host key has changed after each switchover, leading to security warnings in SSH client software such as PuTTY.
Does anyone know how to resolve this? Is there a way to maintain consistency of host key between the zone cluster servers?
Thank you,
Stuart