Novell Access Management 3 Linux Novell Identity Server
Novell Access Management 3 Linux Access Gateway
Novell Access Management 3 Netware Access Gateway
Access Manager Interim release 2 applied
The Access Manager 3 Interim Release 2 patch was installed on two Identity (IDP) servers. These IDP servers, all running SLES9 SP3, had multiple interfaces in the machine. When the second IDP server was added to the IDP cluster, the following bogus error condition was reported (only when multiple NICs exist in the IDP server!) on the health check for the IDP server:
Clustering An active cluster member is not in the configured list of cluster members! Expected cluster members: 10.65.2.11, 10.65.2.12. Active cluster members: 172.27.101.61, 172.27.101.62.
(Required Action) An ip address that is not known to the current configuration is a member of the current cluster. Ensure that this ip address is a well known address that should be included in the cluster.There exists a configured cluster member that is not active! Expected cluster members: 10.65.2.11, 10.65.2.12. Active cluster members: 172.27.101.61, 172.27.101.62.
The 2 Identity Servers have 3 NIC/IP Address each:
Server 1: 10.65.1.11, 10.65.2.11(admin), and 18.104.22.168.
Server 2: 10.65.1.12, 10.65.2.12(admin), and 22.214.171.124.
So the error about 172.27.101.61/62 is bogus, since it is the same server as 10.65.2.11/12.
Note that the IDP clustering works well regardless of the above health check warning.
Fixed in SP1 beta build.