Solaris 10 Cluster Nodes May Fail to Communicate With Machines That Have Both IPv4 and IPv6 Address Mappings (6306113)

Problem Summary: If a Sun Cluster node running Solaris 10 does not have IPv6 interfaces configured for public networking (for example, not for cluster interconnects), it cannot access machines that have both an IPv4 and IPv6 address mapping in a name service, such as NIS. Applications such as telnet and traceroot that choose the IPv6 address over IPv4 will see their packets getting sent to the cluster transport adaptors and dropped.

Workaround: Use one of the following workarounds depending on the configuration or your cluster.

• If IPv6 is not required to run on the cluster, then remove the nis entry in the ipnodes line in /etc/nsswitch.conf. For example, change the ipnodes line to the following:

  ipnodes files # Work Around for CR 6306113

• If IPv6 is required, but no scalable service is running on the cluster, add the following line to /etc/system and reboot all nodes.

  set clcomm:ifk_disable_v6=1

• If IPv6 scalable service is running, make sure all cluster nodes have an IPv6 network interface configured for public networking (non-cluster use). See ifconfig(1M)) and System Administration Guide: IP Servicesfor how to deploy IPv6 with Solaris.