Configuring HyperFabric
Performing the Configuration
| Using the clic_init Command |
| Run the clic_init command to create the global configuration file. |
| To view the man page for clic_init see “Viewing man Pages” on |
| page 127 of this manual. |
| To use clic_init to configure the Transparent Local Failover feature on |
| HMP, see the section, “Configuring HMP for Transparent Local Failover |
| Support - Using the clic_init command” on page 104. |
|
|
IMPORTANT | If the global configuration file already exists and you are running |
| clic_init again (to change the file), you have the option of retaining or |
| modifying the existing configuration information, in addition to adding |
| new information pertaining to new hardware. |
| Also, once you have completed your changes and clic_init ends its |
| processing, you must stop HyperFabric (by running the clic_shutdown |
| command or using SAM) and then start HyperFabric (by running the |
| clic_start command or using SAM). Otherwise, your configuration |
| information changes will not take effect. See “Stopping HyperFabric” on |
| page 128 and “Starting HyperFabric” on page 109 for more information. |
| 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_init). |
| You must be logged in as root to run this command. |
| The syntax is as follows: |
| clic_init |
| where |
| • |
| are prompted for the information described in “Information You |
| Need” on page 71. Note that if the global configuration file already |
| exists (for example, when you are adding an adapter to an existing |
| fabric), clic_init prompts you with the existing configuration |
| information. As you are prompted with each piece of information, you |
| can then confirm that you want to keep it or you can change it. |
| • |
Chapter 4 | 79 |