A.1 hacheck Error Messages

The hacheck command displays the following messages in the console. Use the information here to correct the error.

did not find framework configuration file (hadfconfig)

hacheck could not access the hadfconfig(4) file. The hadfconfig file should be found in /etc/opt/SUNWhadf/hadf. Check for access to the file. The original installation may be incomplete or corrupted. Verify the necessary packages are in place using the pkgchk(1M) command.

error(s) found in performing "configuration" checks

One or more errors or warnings occurred while performing the configuration category of checks. Refer to other messages for the source of the problem.

HA_BASEDIR and HA_FILES settings are inconsistent

There is an error in the hadfconfig(4) file. Contact your service representative for assistance.

not enough memory

You must reconfigure the system with additional swap space to correct this error.

bad keyword value for base directory directory_name

There is an error in the hadfconfig file. Contact your service representative for assistance.

base directory must begin with /

There is an error in the hadfconfig file. Contact your service representative for assistance.

no HOSTNAME entries found in config_file

There is an error in the hadfconfig file. Contact your service representative for assistance.

cannot find local host name in the HOSTNAME entries

There is an error in the hadfconfig file. Contact your service representative for assistance.

cannot find remote host name in the HOSTNAME entries

There is an error in the hadfconfig file. Contact your service representative for assistance.

cannot find address in /etc/etc/hosts for host hostname

There is an error in the hadfconfig file. Contact your service representative for assistance.

netmask in /etc/netmasks conflicts with ifconfig for host hostname

There is an error in the hadfconfig file. Contact your service representative for assistance.

cannot find netmask in /etc/inet/netmasks for host hostname

There is an error in the hadfconfig file. Contact your service representative for assistance.

more than one network interface is assigned to host

Solstice HA systems use /etc/hostname.interface files at boot time to assign host names to network interfaces. This error message indicates that the same hostname is found in more than one of these files. To correct the error, remove or correct the incorrect /etc/hostname.interface files and reboot the systems.

attempt to set logical network interface (/etc/hostname.name)

Solstice HA systems use /etc/hostname.name files at boot time to assign host names to network interfaces. If the name position of the file name contains a colon (:) this is interpreted as an attempt to set a logical or virtual address for the host. To correct the error, remove the indicated hostname.name file.

there is no hostname.name file for local host hostname

Solstice HA systems use /etc/hostname.name files at boot time to assign host names to network interfaces. There should be a hostname.name file for all LOCAL physical public and private interfaces found in the HOSTNAME and PRIVATELINK keyword parameter declarations in the hadfconfig file. To correct this error, create the necessary /etc/hostname.name file.

network interface mismatch in PRIVATELINK entry entry for host host

There is an error in the hadfconfig file. Contact your service representative for assistance.

file hostname.name describes unknown host host

Solstice HA systems use /etc/hostname.name files at boot time to assign host names to network interfaces. If a host name which is not known as a Solstice HA system is found in any of the /etc/hostname.name files, this warning message is issued. You must remove the file and reboot the system.

trying to default lookup facility for host host

There is an error in the hadfconfig file. Contact your service representative for assistance.

the default lookup facility failed to get address for host host

There is an error in the hadfconfig file. Contact your service representative for assistance.

network naming service required to find address for host

There is an error in the hadfconfig file. Contact your service representative for assistance.

misplaced - found in HOSTNAME entries entries

There is an error in the hadfconfig file. Contact your service representative for assistance.

duplicate local host names found in HOSTNAME entries entries

There is an error in the hadfconfig file. Contact your service representative for assistance.

duplicate remote host names found in HOSTNAME entries entries

There is an error in the hadfconfig file. Contact your service representative for assistance.

unable to generate list of local physical public hosts

There is an error in the hadfconfig file. Contact your service representative for assistance.

unable to generate list of remote physical public hosts

There is an error in the hadfconfig file. Contact your service representative for assistance.

unable to determine local host name from entries

There is an error in the hadfconfig file. Contact your service representative for assistance.

unexpected local host name found for this configuration

There is an error in the hadfconfig file. Contact your service representative for assistance.

unable to determine local host names from names

There is an error in the hadfconfig file. Contact your service representative for assistance.

unexpected local host name found for this configuration

There is an error in the hadfconfig file. Contact your service representative for assistance.

unable to determine remote host name from names

There is an error in the hadfconfig file. Contact your service representative for assistance.

unexpected remote host name found for this configuration

There is an error in the hadfconfig file. Contact your service representative for assistance.

unable to determine remote host name from names

There is an error in the hadfconfig file. Contact your service representative for assistance.

unexpected remote host name found for this configuration

There is an error in the hadfconfig file. Contact your service representative for assistance.

no PATHPREFIX entries found in filename

There is an error in the hadfconfig file. Contact your service representative for assistance.

found number PATHPREFIX entries

There is an error in the hadfconfig file. Contact your service representative for assistance.

PATHPREFIX - bad number of lines num for asymmetric configuration PATHPREFIX - bad number of lines num for symmetric configuration DISKSET - bad number of lines num for asymmetric configuration DISKSET - bad number of lines num for symmetric configuration

There is an error in the hadfconfig file. Contact your service representative for assistance.

A.2 hasetup Error Messages

The following messages are reported by the hasetup command.

USAGE: hasetup

hasetup does not accept command line arguments.

Initialization errors ...

Errors were encountered during the initialization phase of hasetup. Such errors are likely the result of a lack of swap space. Check the system for the amount of available swap. If swap space is low, correct the problem and restart hasetup. If swap space is not the problem, contact your service provider.

Cannot initialize directory names ...

Errors were encountered during the initialization phase of hasetup. Such errors are likely due to either a lack of swap space or the required SUNWhadf directories were not found. To correct this error, check the SUNWhadf package using the pkgchk(1M) command to ensure it is installed correctly. Verify that none of the following environment variables are set: HA_BASEDIR, HA_BIN, HA_FILES, HA_VAR, CM_BIN, FM_PROGS, or CT_PROGS. Also check the server for the amount of swap space. If the swap space is low, correct the problem and restart hasetup.

Cannot locate bin directory ...

This message is displayed when either an internal error has occurred or there is not enough swap space. Check the server for the amount of available swap space. If the swap space is low, correct the problem and restart hasetup. If swap space is not the problem, contact your service provider.

You must be root to run "hasetup"

You must be the superuser in order to run hasetup. Use the su(1M) command to become root and restart hasetup.

"hasetup" is an interactive program Only keyboard input is accepted

hasetup can only be run interactively. Input is only accepted from the keyboard. If this message is printed, hasetup finds that standard input is not associated with a tty device. Restart hasetup from you shell prompt. Do not attempt to redirect standard input away from your terminal or terminal window.

"hasetup" is an interactive program Output must go to your screen

hasetup is designed to run interactively and must send output to your terminal or terminal window. If this message is displayed, hasetup has found that standard output is not associated with a tty device. You should restart hasetup from the shell prompt. Do not attempt to redirect standard output away from your terminal or terminal window.

Exiting before configuration is complete ...

You have chosen to quit hasetup without allowing the program to complete all its functions. You either entered a Control-D or responded with negative answers to certain questions. This message will not be displayed if hasetup is terminated as a result of a signal. Depending on where in the configuration setup you were when you quit the program there may have been additional instructions telling you how to manually complete certain steps. If no additional instructions were given, you may need to restart hasetup to complete the necessary set up procedures. Refer to the Chapter 8, "Creating the Configuration," for additional information.

Exiting due to fatal error

hasetup has encountered an unrecoverable error. This message will always be preceded by other error or warning messages. Check those messages for additional information.

Cannot locate files directory ...

This error is either a result of a lack of swap space or an internal error. Check the system for the amount of available swap space. If the swap space is low, correct the problem and restart hasetup. If swap space is not the problem, contact your service provider.

The "/etc/opt/SUNWhadf/hadf/hadfconfig" file is found to already exist.

If this warning message is printed, hasetup will simply skip over the steps necessary for the creation of the hadfconfig file. hasetup will never overwrite an already existing hadfconfig file on the local system. Instead, it

will check the contents of the file and find the information it needs in order to continue with other parts of the set up. No action is necessary when this message is displayed.

The "/etc/opt/SUNWhadf/hadf/hadfconfig" file is found to already exist But, "/etc/opt/SUNWhadf/hadf/cmm_confcdb" is NOT found! You may need to remove the "hadfconfig" file and try again

The two files are important to the configuration of Solstice HA. The files are always created at the same time by hasetup.This message should not be displayed, unless the cmm_confcdb file has been removed. You may need to remove or rename the hadfconfig file and restart hasetup.

Cannot find any installed HA dataservice packages!

At least one of the data service packages, either SUNWhanfs or SUNWhaor, must be installed on the system before hasetup can be run. Use the pkgadd(1M) command to install the desired package.

Attempting to discover local network controller config ... failed

One or more errors were encountered while hasetup attempted to compile a list of all the local network controllers. You should verify the following:

• The ifconfig -a command is working correctly.
• The SUNWhadf package is correctly installed on both servers and that the /opt/SUNWhadf/bin/hadfconfig file has the correct execute permissions.

WARNING: found logical net interface configured as "<ctrl>:n" (<hostname>) WARNING: reboot is recommended

One or more logical network interface is configured. Reboot the server and restart the hasetup command.

Primary hostnames used in this environment must NOT be qualified with trailing domain names (<hostname>.<domain>)

A dot (.) was found in or more of the hostnames. Remove the domain name from the hostname /etc/inet/hosts files.

Attempting to rediscover local network controller config ... failed

One or more errors were encountered when hasetup attempted to compile a list of all the assigned local network controllers. You should verify the following:

• The ifconfig -a command is working correctly.
• The SUNWhadf package is correctly installed on both servers and that the /opt/SUNWhadf/bin/hadfconfig file has the correct execute permissions.

The primary host is not on the network!

The hostname for the local machine, as reported by uname(1) does not match any of the hosts assigned to the configured network controllers. You should verify the following:

• That you are not attempting to run hasetup from a standalone, nonnetworked machine.

• The ifconfig -a command is working correctly.
• The SUNWhadf package is correctly installed on both servers and that the /opt/SUNWhadf/bin/hadfconfig file has the correct permissions.
• The /etc/inet/hosts file has the correct IP address for the host.
• The uname -n command returns the correct name for your host. If not, update the /etc/nodename file and reboot the server.
• The uname -n output matches that of /etc/nodename and that it also matches one or more of the /etc/hostname.* files.
• There were no warning messages complaining about unsupported network controller types.

Two private networks are required

For your Solstice HA configuration to meet requirements, at least two private networks are required. Verify that the output from ifconfig shows at least three assigned and configured networks, one for the primary local host and two for the private networks. Also verify that all required Solaris package are correctly installed and that ifconfig is working. Use the pkgchk(1M) command to verify that the SUNWhadf package is correctly installed and that the /opt/SUNWhadf/bin/haconfig file has the correct permissions.

Attempting to discover remote network controller config ... failed

One or more errors were encountered while hasetup attempted to compile a list of all the remote network controllers. You should verify the following:

• The ifconfig -a command is working correctly.
• The SUNWhadf package is correctly installed on both servers and that the /opt/SUNWhadf/bin/haconfig file has the correct permissions.

WARNING: found logical net interface configured as "<ctrl>:n" (<hostname>) on remote host WARNING: reboot of remote host is recommended

One or more logical network interfaces are configured on the sibling host. Reboot the sibling server and restart hasetup.

Attempting to rediscover remote network controller config ... failed

One or more errors were encountered when hasetup attempted to compile a list of all the assigned remote network controllers. You should verify the following:

• That the use of the rsh command through the private link interfaces is successful.
• The ifconfig -a command is working correctly.
• The SUNWhadf package is correctly installed on both servers and that the /opt/SUNWhadf/bin/haconfig file has the correct permissions.

Not enough space

There is not enough swap space for hasetup to run. Check the system for the amount of swap space available. Correct the problem and restart hasetup.

Unable to locate remote host <remote_privatehost> in the remote network config

hasetup could not find the remote (sibling) host. You should verify the following:

• That the use of the rsh command through the private link interfaces is successful.
• The ifconfig -a command is working correctly.
• The SUNWhadf package is correctly installed on both servers and that the /opt/SUNWhadf/bin/haconfig file has the correct permissions.
• That the /etc/inet/hosts file on the sibling server has the correct IP address for the host name.
• That the /etc/inet/hosts files on both servers are in agreement.

• That there were no warning messages complaining about unsupported network controller types.

Internal error while matching private hosts

You should contact your service provider if this message is displayed.

Finding the name of the remote host for the main public net ... failed

The hostname for the sibling server, as reported by uname, does not match any of the hosts assigned to the configured network controllers. You should verify the following:

• The /etc/inet/hosts file on the sibling server has the correct IP address for the host.
• The /etc/inet/hosts files on both servers are in agreement.
• The ifconfig -a command is working correctly.
• The SUNWhadf package is correctly installed on both servers and that the /opt/SUNWhadf/bin/haconfig file has the correct permissions.
• The uname -n command on the sibling server returns the correct name for your host. If not, update the /etc/nodename file and reboot the server.
• The uname -n output matches that of /etc/nodename and that it also matches one or more of the /etc/hostname.* files.
• There were no warning messages complaining about unsupported network controller types.
• The rsh command works across the private link interfaces.

Verifying that the two primary hostnames are on the same net ... failed

hasetup found that the primary host names for the two servers are not found to be on the same networks. You should verify the following:

• The two servers are on the same network.

• The netmasks for the two servers are identical.
• The network portion of the network IP addresses for the two servers are identical.
• All required Solaris packages are correctly installed on both servers.
• The ifconfig -a command is working correctly.
• The SUNWhadf package is correctly installed on both servers and that the /opt/SUNWhadf/bin/haconfig file has the correct permissions.
• The /etc/inet/hosts files on both servers are in agreement and correct.
• There were no warning messages complaining about unsupported network controller types.
• The rsh command works across the private link interfaces.

WARNING: network controller name mismatch for hostnames "<hostname>" and "<hostname>"

The two host names given are either primary or secondary hostnames, which are both found to be assigned to the same networks. However, their network controller names do not match. Solstice HA installation procedures recommend symmetric hardware and software configurations between the two servers. This is not a supported configuration. Correct the problem by matching the network controller names with the networks on both machines. This may involve changes to the hardware configuration or to the /etc/hostnames.* files. You must reboot before restarting hasetup.

At least one data service must be selected

You must select at least one data service in order to complete configuration of the servers.

Updating "/etc/opt/SUNWhadf/hadf/hadfconfig" ... failed

hasetup was unable to update or create the hadfconfig file. You should verify the following:

• That all required Solaris packages are correctly installed.

• Use pkgchk to check on whether the SUNWhadf package is correctly installed on both servers.
• If only a partial update was found to occur to the hadfconfig file, remove the file before restarting hasetup.

Updating "/etc/opt/SUNWhadf/hadf/cmm_confcdb" ... failed

hasetup was unable to update or create the cmm_confcdb file. You should verify the following:

• That all required Solaris packages are correctly installed.
• Use pkgchk to check on whether the SUNWhadf package is correctly installed on both servers.
• If only a partial update was found to occur to the cmm_confcdb file, remove the file before restarting hasetup.

Bad configuration file - /etc/opt/SUNWhadf/hadf/hadfconfig

hasetup found an existing hadfconfig file that was corrupted. You should remove or rename the file and restart hasetup. If the problem persists, contact your support representative.

Unable to setup necessary variables

Errors were discovered during an internal check. These errors may be due to a lack of swap space. Check the server for available swap space. If the swap space is too small, correct the problem and restart hasetup. If this is not the problem, contact your support representative.

Bad configuration parameters!

Errors were discovered during an internal check. These errors may be due to a lack of swap space. Check the server for available swap space. If the swap space is too small, correct the problem and restart hasetup. If this is not the problem, contact your support representative.

Unable to determine if the cluster monitor is running on the local host

An attempt to check for an instance of the cluster membership monitor on the local host failed. You should verify that all required Solaris packages are correctly installed and that the ps(1) command is working. Also check to make sure the SUNWhadf package is correctly installed and that the /opt/SUNWhadf/bin/hadf file has the correct execute permissions.

Unable to determine if the cluster monitor is running on the remote host

An attempt to check for an instance of the cluster membership monitor on the local host failed. You should verify that all required Solaris packages are correctly installed and that the ps(1) command is working correctly. Also check to make sure the SUNWhadf package is correctly installed and that the /opt/SUNWhadf/bin/hadf file has the correct execute permissions. Make sure that the use of the rsh command through the private link interfaces is successful.

The cluster monitor is active on the local host!

The cluster membership monitor is running on the local host. Solstice HA does not allow the cluster membership monitor (clustd) to be active on either host while hasetup is running. You should remove the

/etc/rc3.d/S20SUNWhadf file on both servers. The S20SUNWhadf file is a hard link to /etc/init.d/SUNWhadf, which must be restored as the final step to installation. You must also run the following command:

# /etc/init.d/SUNWhadf stop

The cluster monitor is active on the remote host!

The cluster membership monitor is running on the sibling server. Solstice HA does not allow the cluster membership monitor (clustd) to be active on either host while hasetup is running. You should remove the /etc/rc3.d/S20SUNWhadf file on both servers The S20SUNWhadf file is a hard link to /etc/init.d/SUNWhadf, which must be restored as the final step to installation. You must also run the following command:

# /etc/init.d/SUNWhadf stop

Updating local /etc/nsswitch.conf file for Solstice HA compliance ... failed

The operation of updating the /etc/nsswitch.conf file failed on the local server. You should verify that all required Solaris packages are correctly installed. Also check that the SUNWhadf package is correctly installed and that /opt/SUNWhadf/bin/haconfig has the correct execute permissions.

Copying <filename> to host "<hostname>" ... failed

The indicated copy operation failed. You should verify that all required Solaris packages are correctly installed and that the use of the rcp(1) command through the private link interfaces is successful.

"<hostname>" is already assigned

The hostname you entered is already in use. Enter a different hostname. If the problem is due to an earlier entry, exit hasetup with a Control-D and restart the program.

Can't find "hostname" in the hosts map Do you want to add it now (yes/no) [yes]?

The hostname you entered has no IP address. If you answer yes you must enter the IP address. If you answer no, you must enter a different hostname.

Can't find "hostname" in the hosts map Try again or type control-D to exit ...

At one of the hostname prompts, you entered a hostname for a private link that does not have an IP address. Since the private links must be entered into /etc/inet/hosts before running hasetup, you are not given the opportunity to enter a network IP address. To correct the problem, exit hasetup by entering a Control-D, set up the private links, and restart hasetup.

Address already in use by host "<hostname>"

At one of the prompts for a network IP address, you entered an IP address that is already assigned to the indicated hostname. hasetup cannot be used to create hostname aliases. If this was the intent, you must manually edit the /etc/inet/hosts file. To correct the problem, exit hasetup by entering a Control-D, set up the IP address, and restart hasetup.

Updating /etc/inet/hosts ... failed

Either a local or remote update to the /etc/inet/hosts file failed. You should verify that all required Solaris packages are correctly installed on both servers. Also check to make sure the SUNWhadf package is correctly installed on both servers and that the /opt/SUNWhadf/bin/haconfig file has the correct permissions.

Updating /etc/inet/netmasks ... failed

An update to the /etc/inet/netmasks file failed. You should verify that all required Solaris packages are correctly installed on both servers. Also check to make sure the SUNWhadf package is correctly installed on both servers and that the /opt/SUNWhadf/bin/haconfig file has the correct permissions.

Configuring network controller interface ... failed

The configuration of the network controller interface failed. You should verify that all required Solaris packages are correctly installed on both servers and that ifconfig is working. Also check to make sure the SUNWhadf package is correctly installed and that the /opt/SUNWhadf/bin/haconfig file has the correct permissions. Rebooting the servers may solve the problem.

Internal error getting private hosts ...

You should contact your service provider if this message is displayed.

Hostname "<hostname>" is not configured Try again or type control-D to exit ...

At one of the hostname prompts, you entered a hostname for one of the private links that is not configured. All private links must be configured before running hasetup. Enter a different hostname. You can also exit hasetup by entering a Control-D, set up the private links, and restart hasetup.

Hostname "<hostname>" is not legal

At one of the hostname prompts, you entered an illegal hostname for one of the private links. You may have entered a hostname which is associated with a logical network interface. Enter a different hostname. You can also exit hasetup by entering a Control-D, set up the private links, and restart hasetup.

Hostname "<hostname>" has already been used

The hostname you entered has already been used. Select a different one.

Interface for host "<hostname>" is not up

At one of the hostname prompts you entered a hostname for one of the private links that is configured but not marked as up (see ifconfig). The private links must be configured up before running hasetup. Enter a different hostname. You can also exit hasetup by entering a Control-D, use ifconfig to configure up the private links, and restart hasetup.

Hostname "<hostname>" is not on the same network as "<hostname>"

At one of the hostname prompts you entered a hostname for one of the remote private links that does not have a network IP address matching that or the corresponding local private link name. Enter a different hostname. You can also exit hasetup by entering a Control-D, correct the problem, and restart hasetup.

Checking access to "<hostname>" from "<hostname>" ... failed

Access to the specified hostname failed. You should verify that the /.rhosts files on both systems are set up correctly. Check that all required Solaris packages are correctly installed on both systems and that /bin/rsh and /bin/echo are working correctly. You can try the rsh command with a simple echo(1) command to the host that rejects access.

Broadcast from "<hostname>" to discover remote private hostname.." Hostname "<hostname>" is not on a private network

The indicated hostname for the private link is not on a private link. This is known because more than one other host replied to a broadcast on the link. Enter a different host name. You can also exit hasetup by entering a Control-D, correct the problem, and restart hasetup.

Broadcast from "<hostname>" to discover remote private hostname.." No response from the remote host on this network

The broadcast to hostname timed out with no response. Enter a different hostname. You can also exit hasetup by entering a Control-D, correct the problem, and restart hasetup

WARNING: Ignoring unsupported controller - "<network_controller>"

The indicated network_controller is not supported by Solstice HA and has been ignored by hasetup. You should contact your service provider.

Internal error while searching for primary host

You should contact your service provider if this message is displayed.

Logical hosts MUST be on the same subnets as their masters Try again ...

The logical hostnames must be on the same network as the master. Enter the correct logical hostname for the master.

Internal error - bad filename

You should contact your service provider if this message is displayed.

How large will the UFS logs be (MB) [10]? Error: "<number>" is out of range [1 - 64]

UNIX file system logs must be between 1 and 64 Mbytes in size. Enter a value in this range.

Please use the unqualified hostname; do not include trailing domain names!

A dot (.) was found in one or more of the hostnames. Remove the domain name portion of the hostname from the /etc/inet/hosts files.

You will need to use the metaset(1m) command to create diskset(s) manually!

You answered no at the following prompt:

All multi-host disks will now be repartitioned and populated with metadevice state database replicas. Is this okay? no

The necessary operations for repartitioning the disks and creating disksets must be done manually. If you accidentally entered no, you should restart hasetup. Otherwise, refer to the Solstice DiskSuite 4.0 Administration Guide for instructions on creating disksets.

Checking for Solstice DiskSuite replicas on the local host ... failed Unable to execute "metadb" on the local host Checking for Solstice DiskSuite replicas on the local host ... failed Unexpected response from "metadb" on the local host Checking for Solstice DiskSuite replicas on the local host ... failed Error running "metadb" on the local host

Any of the above messages indicates there was a error when hasetup attempted to execute the metadb(1M) command on the local host. You should check to make sure the SUNWmd package is correctly installed. You can also try running the /usr/opt/SUNWmd/sbin/metadb command with no options to make sure it is functioning properly.

Checking for Solstice DiskSuite replicas on the remote host ... failed Unable to execute "metadb" on the remote host Checking for Solstice DiskSuite replicas on the remote host ... failed Unexpected response from "metadb" on the remote host Checking for Solstice DiskSuite replicas on the remote host ... failed Error running "metadb" on the remote host

Any of the above messages indicates there was a error when hasetup attempted to execute the metadb(1M) command on the sibling host. You should check to make sure the SUNWmd package is correctly installed. You can also try running the /usr/opt/SUNWmd/sbin/metadb command with no options to make sure it is functioning properly. Verify that the you can communicate with the sibling host using the rsh command.

Checking for Solstice DiskSuite replicas on the local host ... failed No replicas were found on the local host

No metadevice state database replicas were found on the private disks of the local server. Solstice HA requires that a minimum of three replicas be created on the local boot disk on each of the servers before running hasetup. Refer to Chapter 5, "Solaris 2.4 Installation," for instructions on setting up the replicas and restart hasetup.

Checking for Solstice DiskSuite replicas on the remote host ... failed No replicas were found on the remote host

No metadevice state database replicas were found on the private disks of the sibling server. Solstice HA requires that a minimum of three replicas be created on the local boot disk on each of the servers before running hasetup. Refer to Chapter 5, "Solaris 2.4 Installation," for instructions on setting up the replicas and restart hasetup.

Checking for Solstice DiskSuite replicas on the local host ... failed There must be at least 3 private replicas on each host But, only <n> replicas were found on the local host

Fewer than three metadevice state database replicas were found on the boot disk of the local server. Solstice HA requires that a minimum of three replicas be created on the local boot disk on each of the servers before running hasetup. Refer to Chapter 5, "Solaris 2.4 Installation," for instructions on setting up the replicas and restart hasetup.

Checking for Solstice DiskSuite replicas on the remote host ... failed There must be at least 3 private replicas on each host But, only <n> replicas were found on the remote host

Fewer than three metadevice state database replicas were found on the boot disk of the sibling server. Solstice HA requires that a minimum of three replicas be created on the local boot disks on each of the servers before running hasetup. Refer to Chapter 5, "Solaris 2.4 Installation," for instructions on setting up the replicas and restart hasetup.

Verifying that disksets do not already exist ... failed Unable to execute "metaset" Verifying that disksets do not already exist ... failed Error executing "metaset"

An error was discovered when hasetup attempted to execute the metaset command. Use the pkgchk command to verify that the SUNWmd package is correctly installed. Also try running /usr/opt/SUNWmd/sbin/metaset with no options.

Verifying that disksets do not already exist ... failed One or more disksets already exist! You may need to use metaset(1m) to either remove or update these disksets!

hasetup discovered that disksets already existed. The program will not attempt to partition disks or in any way modify existing disksets. You must decide if the removal or modification of the disksets is the action you want to take and perform the appropriate steps. If you do decide not to modify the disksets, you should consider the hasetup phase of the installation complete. If you do decide to remove the disksets you can restart hasetup.

Checking the list of multi hosted disks ... ERROR: unable to open "<disk>" Checking the list of multi hosted disks ... ERROR: unable to get geometry of "<disk>"

When hasetup checked the list of multi-host disks, it discovered failures occurred for the specified disks. Check the console for disk errors and correct the problem before restarting hasetup. You may also need to check the /dev and /device names along with the permissions. Use the ssaadm(1M) command with the display option to verify that all multi-host disks have a label.

Repartitioning all multi hosted disks ... ERROR: unable to open "<disk>" Repartitioning all multi hosted disks ... ERROR: unable to get geometry of "<disk>" Repartitioning all multi hosted disks ... ERROR: unable to get geometry of "<disk>" Repartitioning all multi hosted disks ... ERROR: unable to read vtoc of "<disk>" Repartitioning all multi hosted disks ... ERROR: unable to write vtoc of "<disk>"

The above errors are reported when one or more failures occurs on the specified multi-host disk. Check the console for disk errors and correct the problem before restarting hasetup. You may also need to check the /dev and /device names along with the permissions. Use the ssaadm command with the display option to verify that all multi-host disks have a label.

Creating diskset "<diskset>" ... failed Error executing "metaset" command

hasetup discovered an error when it attempted to execute the metaset command during diskset creation. Check for any error messages printed by the metaset command. Also refer to the Solstice DiskSuite 4.0 Administration Guide for additional information. Before attempting to restart the hasetup command you may need to manually remove any disksets that were created. You should also run pkgchk on the sibling host to verify that the SUNWmd package is correctly installed.

Populating diskset "<diskset>" ... failed Error executing "metaset" command

An error occurred when attempting to execute the metaset command. Check for any error messages printed by the metaset command. Also refer to the Solstice DiskSuite 4.0 Administration Guide for additional information. Before attempting to restart the hasetup command, you will need to manually remove any existing diskset. You should also run pkgchk on the sibling host to verify that the SUNWmd package is correctly installed.

Releasing diskset "<diskset>" ... failed Error executing "metaset" command

An error occurred when attempting to execute the metaset command. Check for any error messages printed by the metaset command. Also refer to the Solstice DiskSuite 4.0 Administration Guide for additional information. You should also run pkgchk on the sibling host to verify that the SUNWmd package is correctly installed. Run the metaset command manually to release the disksets. There is no need to restart hasetup.

Compiling the list of multi hosted disks ... failed

hasetup failed to compile the list of multi-host disks. You should verify that all multi-host disks are correctly cabled and that the disk names for these disks are identical on each of the servers. Check for error in the console. Verify that all required Solaris packages are correctly installed. You should also run pkgchk to verify that the SUNWhadf package is correctly installed and that /opt/SUNWhadf/bin/haconfig has the correct execute permissions.