Solaris Cluster Troubleshooting Private Interconnect Transport Network in a 'failed' or 'faulted' State
(Doc ID 1315772.1)
Last updated on JUNE 27, 2018
Applies to:Solaris Cluster - Version 3.0 to 4.3 [Release 3.0 to 4.3]
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on x86 (32-bit)
Solaris Cluster has a minimum of two private transports also known as private interconnect or private network for high availability.
This article applies to situations when you have one path in 'failed' or 'faulted' state.
If all private transport in failed/faulted state it is more likely that the node they are connected to is down or not part of the cluster.
In Sun Cluster 3.0 or 3.1 you would see the failure/errors in
- Cluster Transport Paths --
Endpoint Endpoint Status
-------- -------- ------
Transport path: clnode1:nxge1 clnode2:nxge1 faulted
Transport path: clnode1:nxge0 clnode2:nxge0 Path online
In Oracle Solaris Cluster 3.2 or higher you see it also with
# clinterconnect status
=== Cluster Transport Paths ===
Endpoint1 Endpoint2 Status
--------- --------- ------
clnode1:net1 clnode2:net1 Path online
clnode1:net0 clnode2:net0 faulted
This procedure uses nxge interfaces but it is not specific to nxge and applies to other types of transports. The article shows Solaris Cluster 3.2 and above command set. For older revisions see man pages for scconf and scsetup.
This resolution path can also be used to analyze cluster interconnect issue, when the speed is not correct, e.g. the interconnect is running on 100Mbit instead of 1000Mbit.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!