Error Code Number
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
The error code numbers are recorded in a log file that you can use to view status changes for BCC.
The path to the log file on Linux is
related messages and entries in the log file.
13.24 Clustered Pool Is Stuck in an eDirectory
Synchronization State
Pools might get stuck in an eDirectory synchronization state if all of the volumes in that pool are not
active and mounted.
To resolve this problem:
1 In NSSMU or iManager, activate and mount the deactive volumes.
2 In iManager, click Clusters, then select the cluster resource for the clustered pool.
3 Click Offline to dismount the pool's volumes and deactivate the pool.
Wait until the resources are successfully offline before continuing.
4 Click Online to bring the resource back online.
124 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux
Message
CIM Client error.
Error creating a system resource (mutex, semaphore, etc.).
File IO error.
No data.
Not a member of the cluster.
Invalid token in the script.
Invalid or unknown cluster.
The NSMI script is too long. It must be less than 64 KB.
The cluster-enabled pool resource does not contain a volume.
An operation has timed out.
The specified resource is already busy.
/var/log/messages
. You can search for BCCD to view BCC
Need help?
Do you have a question about the BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION and is the answer not in the manual?
Questions and answers