HyperFabric Administrator's Guide (HP-UX 11i v1)

Overview of the HyperFabric Product
HyperFabric Concepts
Chapter 110
HyperFabric to run. If the HyperFabric management process on a node
stops running for some reason (for example, if it is killed), all
HyperFabric-related communications on that node are stopped
immediately. This makes the node unreachable by other components in
the fabric.
When you start HyperFabric, the fabric is verified automatically. This is
because each node performs a self diagnosis and verification over each
adapter installed in the node. In addition, the management process
performs automatic routing and configuring for each switch (if switches
are part of the fabric). You can, if needed, run the clic_stat command
to get a textual map of the fabric, which can be used as another method
of quick verification.
Notice that the commands to administer HyperFabric have a prefix of
clic_, and some of the other components have CLIC as part of their
name (for example, the CLIC firmware and the CLIC software). CLIC
stands for CLuster InterConnect, and it is used to differentiate those
HyperFabric commands or components from other commands or
components. For example, the HyperFabric command clic_init is
different from the HP-UX init command.