NOTE
Managing HyperFabric
Starting HyperFabric
Starting HyperFabric
HyperFabric is started in one of these three ways:
•As part of the normal local node boot process (HP 9000 system).
•By running the HyperFabric clic_start command (described below).
•By starting HyperFabric through SMH (described in “Using SMH” on page 96). HyperFabric needs to be started in the following situations:
•If HyperFabric hardware and software have just been installed on the system and the clic_init command has been used to configure the HyperFabric adapters on this node.
•If the HyperFabric configuration has been changed by using the clic_init command or using SMH
•If a new HyperFabric adapter has been added to a system online and configured using clic_init. In this situation, it is not necessary to run clic_shutdown before running clic_start (see “Online Addition and Replacement” on page 42in Ch. 3 of this user guide).
Starting HyperFabric launches the HyperFabric CLuster InterConnect (CLIC) daemon (clic_mgmtd). This daemon process must be running for the HyperFabric product to operate correctly. It is possible that other daemons will be running, but it is essential that at least one CLIC daemon is running. To check if a CLIC daemon is running, use the following command:
ps
If the CLIC daemon is not running, start the HyperFabric subsystem by executing the following command:
/opt/clic/bin/clic_start
Using the clic_start Command
Run the clic_start command on each node to start the HyperFabric management process on that node.
If you include /opt/clic/bin in your PATH statement, you can run the command as it is shown below. Otherwise, you must include /opt/clic/bin as part of the command name (that is, /opt/clic/bin/clic_start).
You must be logged in as root to run this command.
The syntax is as follows:
clic_start
Chapter 5 | 95 |
