Solaris Cluster 4.x on Solaris 11.x should not be configured as router (Doc ID 2262798.1)

Last updated on MAY 05, 2017

Applies to:

Solaris Cluster - Version 4.1 to 4.3 [Release 4.1 to 4.3]
Information in this document applies to any platform.

Symptoms

Although there might be various symptoms when Solaris Cluster is running routing services these errors indicating that routing is enabled. For example after a ZoneCluster zone is booted the following errors are seen in /var/adm/messages:

Apr 24 11:36:06 node1 cl_runtime: [ID 564910 kern.notice] NOTICE: Membership: Node 'node2' (node id 1) of cluster 'zc_4' joined.
Apr 24 11:36:06 node1 in.routed[735]: [ID 417587 daemon.error] IP_ADD_MEMBERSHIP ALLHOSTS: Cannot assign requested address
Apr 24 11:36:06 node1 in.routed[735]: [ID 537788 daemon.warning] Could not join 224.0.0.9 on interface clprivnet0:3: Cannot assign requested address
Apr 24 11:36:06 node1 in.routed[735]: [ID 667074 daemon.warning] Send bcast sendto(clprivnet0:3, 172.16.3.127.520): No route to host

Apr 24 11:36:06 node1 in.routed[735]: [ID 417587 daemon.error] IP_ADD_MEMBERSHIP ALLHOSTS: Cannot assign requested address
Apr 24 11:36:06 node1 in.routed[735]: [ID 537788 daemon.warning] Could not join 224.0.0.9 on interface clprivnet0:4: Cannot assign requested address
Apr 24 11:36:06 node1 in.routed[735]: [ID 667074 daemon.warning] Send bcast sendto(clprivnet0:4, 172.16.3.191.520): No route to host



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms