27.02.2013 Views

ExpressCluster X 2.0 for Windows Reference Guide - Nec

ExpressCluster X 2.0 for Windows Reference Guide - Nec

ExpressCluster X 2.0 for Windows Reference Guide - Nec

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Message Solution<br />

There is the HBA in<strong>for</strong>mation that is<br />

not configured. Are you sure you want<br />

automatic configuration?<br />

There is difference between the disk<br />

in<strong>for</strong>mation in the configuration<br />

in<strong>for</strong>mation and the disk in<strong>for</strong>mation in<br />

the server.<br />

Are you sure you want automatic<br />

modification?<br />

The upload was stopped. To upload<br />

the configuration file, suspend the<br />

cluster from the Service menu.<br />

The upload was stopped. To upload<br />

the configuration file, stop the groups<br />

to which you made changes.<br />

The upload was stopped. To upload<br />

the configuration file, stop the<br />

resources to which you made<br />

changes.<br />

The upload was stopped. Applying the<br />

cluster configuration file failed in one<br />

or more servers.<br />

The upload was stopped. Applying the<br />

cluster configuration file failed in one<br />

or more servers.<br />

The upload was stopped. There is<br />

one ore more servers that cannot be<br />

connected to. To apply cluster<br />

configuration in<strong>for</strong>mation <strong>for</strong>cibly, run<br />

the clpcfctrl command on the server.<br />

An error occurred when applying data<br />

to the cluster. Cfctrl (%0)<br />

Section I Detailed functions of <strong>ExpressCluster</strong><br />

Using the menu bar of the Builder<br />

The HBA in<strong>for</strong>mation is not configured <strong>for</strong> the server<br />

where the in<strong>for</strong>mation of HBA <strong>for</strong> accessing the shared<br />

disk was configured at the time of the installation. If you<br />

select Yes, the in<strong>for</strong>mation configured at the time of the<br />

installation is inherited.<br />

The combination between the GUID in<strong>for</strong>mation of the<br />

volume and the drive letter does not match with the one<br />

on the actual servers. If you select Yes, automatic<br />

configuration is per<strong>for</strong>med by determining the current<br />

GUID in<strong>for</strong>mation from the derive letter.<br />

Since the cluster has not been stopped, uploading the<br />

cluster configuration data has been cancelled. Stop the<br />

cluster first, and then upload the data again.<br />

Since the cluster has not been suspended, uploading<br />

the cluster configuration data has been cancelled.<br />

Suspend the cluster first, and then upload the data<br />

again.<br />

Since the group whose settings have been changed<br />

has not been stopped, uploading the cluster<br />

configuration data has been cancelled. Stop the group<br />

whose settings have been changed, or the group to<br />

which the resource whose settings have been changed<br />

belongs, and then upload the data again.<br />

Since the resource whose settings have been changed<br />

has not been stopped, uploading the cluster<br />

configuration data has been cancelled. Stop the<br />

resource whose settings have been changed, and then<br />

upload the data again.<br />

Since there is a server that failed to send the cluster<br />

configuration data, uploading the cluster configuration<br />

data has been cancelled. Upload the data again.<br />

Since there is a server that cannot be connected to<br />

exist in the cluster, uploading the cluster configuration<br />

data has been cancelled. Make sure that all the servers<br />

in the cluster have been started, and then upload the<br />

cluster configuration data.<br />

Even if a server that cannot be connected to exists in<br />

the cluster, to upload the cluster configuration data<br />

<strong>for</strong>cibly, refer to “Creating a cluster and backing up<br />

configuration data (clpcfctrl command)” in Chapter 4<br />

“<strong>ExpressCluster</strong> command reference.”<br />

Since an error has occurred while per<strong>for</strong>ming<br />

processing, uploading the cluster configuration data<br />

has been cancelled. Upload the data again.<br />

Related In<strong>for</strong>mation:<br />

If a server that cannot be connected to exists in the cluster, the cluster configuration data cannot<br />

be uploaded from the Builder. In this case, by running the clpcfctrl command, you can <strong>for</strong>cibly<br />

upload the cluster configuration data only on the server that can be connected to.<br />

Follow the steps below to <strong>for</strong>cibly upload the cluster configuration data.<br />

111

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!