No TSA found connecting to OES2 linux cluster resource

  • 3522697
  • 04-Jan-2008
  • 27-Apr-2012

Environment

Novell Open Enterprise Server 2 (OES2) (x86_64)
Novell Cluster Services

Situation

The "No TSA found connecting to OES2 linux cluster resource" error are presented when the SMS engine is trying to connect to the OES2 Linux virtual NCP server, using any sms compliant software.

In general connections are made by specifying either the virtual NCP server name, or the resource TCP/IP address, and both resulted in this error. Connecting to the OES Linux server directly using the server's physical TCP/IP address, opposed to connecting to the virtual NCP server, works fine.

The problem is only seen in combination with Novell Open Enterprise Server 2 (OES2) (x86_64) and Novell Clustering services.

The '/etc/hosts'  files on both servers were setup correctly with all Node's names and IP address added.

Resolution

This is a bug on the FCS release code for OES2 64bit clustering services.

The root cause of the problem is because the installation of Cluster Services is missing a 32bit library that is
required by SMDR to handle cluster functionality.

For new installations this has been resolved by modifying the installation pattern to check for this 32 bit library.
Existing 64 bit OES deployments should install the libraries manually, by issuing the following on the server console: "rug in novell-cluster-services-32bit"

Feedback service temporarily unavailable. For content questions or problems, please contact Support.