Administrator's Guide

Managing HyperFabric

Starting HyperFabric

Chapter 5 109

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 SAM (described in “Using SAM” on

page 110).

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 or SAM has been used to

conﬁgure the HyperFabric adapters on this node.

• If the HyperFabric conﬁguration has been changed by using the

clic_init command or using SAM. In this situation, you must have

run clic_shutdown or used SAM to stop HyperFabric, before

restarting HyperFabric.

• If a new HyperFabric adapter has been added to a system online and

conﬁgured 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 44).

NOTE 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 -ef | grep clic

If the CLIC daemon is not running, start the HyperFabric subsystem by

executing the following command:

/opt/clic/bin/clic_start