Cluster Warning - 10130:... VIPStatus = 11

The master node of a Novell Cluster Services installation is able to access the cluster just fine.  When a second node is attempting to join the cluster, the master server starts displaying the message: "CLUSTER WARNING - 10130: CRM:CRMViaSend - VIPPostSend failed = d4ce2d00 VIPStatus = 11" on the logger screen.
CLUSTER-<WARNING>-<10130>: CRM:CRMViaSend: VipPostSend failed Desc = CDD46140, VipStatus = 11 on the console screen or the logger screen.
The state of the volume resource does not change when attempting to off-line, on-line, or migrate it.
Volume resources can be on-lined and off-lined on the Master node UNTIL a second node attempts to join the cluster.
On the Master node "cluster status" and "cluster resources" work on the other nodes it does not.

Edit the scripts for the resource object and eliminate any unnecessary comments or white space.

It is also possible to move the load script statements to one NCF file and the unload script statements to another NCF file.  Then simply replace the moved statements with the names of the corresponding NCF files.  One disadvantage with this process is that there is no error handling capability when clustering is executing the NCF files.

You will then have to migrate the Master_IP_Address_Resource by doing a "cluster leave" on that node.

Upgrading to OES2 Linux cluster increases the limitation to 3200 bytes but until the cluster conversion is finalized, this could cause some issues in a mixed node cluster.

Each time a node attempts to join its cluster, the Master sends it a series of messages.  Each message contains the load and unload scripts for one  volume resource, as the master reads them from the directory.  This guarantees that every node in the cluster will have the same load and unload scripts.  Only the master node reads these scripts from the directory.  Because the message buffer has a fixed size, the number of characters in the load script when added to the number of characters in the unload script, must not exceed 924 (including spaces and comments).  If it does, the master will not be able to send the message for that volume resource and will start displaying the above warning message once every second on its logger screen.
Troubleshooting Helps:  To count the characters in the load and unload scripts, copy/paste them into a Microsoft Word document and do a word count.  Do this for each of the volume resources, one at a time, until you have found and fixed the problem script/scripts.  You will also need to restart the cluster if the master is already scrolling the warning message.

On Linux you can quickly find the size of the scripts by changing to the /var/opt/novell/ncs/ directory and running the following command:  Then add the load and unload script totals to make sure it is under 924.

  wc --char *.*load

Formerly known as TID# 10057145

Note: This is not the case with an OES 2 Linux cluster as the limitation is now 3200 bytes.  The "cluster convert commit" command needs to be run on a migrated NetWare to OES Linux cluster before this limitation is increased.  The "cluster convert commit" command will upgrade the cluster from NCS:Revision=280 to NCS:Revision=282.  You may need to restart the cluster to completely eliminate the error message once the cluster has been upgraded or at least try move the Master node to another node in the cluster.

Juston Mortenson Jan 29, 2009 Added OES Linux information to this node for mixed clusters.
Rich Brunt - Oct 26, 2011 Added information on OES Linux clusters and current limitations.  Note: in Additional information.