Configuring HyperFabric
Doing the Configuration
| Using the clic_init Command |
| Run the clic_init command to create the global configuration file. |
|
|
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’ve 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 99 and “Starting HyperFabric” on page 85 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 |
| • |
| for the information described in “Information You Need” on page 86. 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. |
| • |
| If you do not specify any of the above parameters, the online help for clic_init is |
| displayed. |
| After you have entered the information for all the adapters in the node and all of the |
| switches (if any) in the fabric, a summary of the configuration information is displayed. |
| Once clic_init has finished, you do one of the following things: |
| • If you want to configure HyperFabric with MC/ServiceGuard, complete the |
| configuration described in “Configuring HyperFabric with MC/ServiceGuard” on |
| page 98, then run clic_start or use SAM to start HyperFabric. |
| • If you have just created the global configuration file on the local node for the first |
| time (and you are not configuring MC/ServiceGuard), run clic_start or use SAM to |
| start HyperFabric. |
| • If you have just changed an existing configuration file on the node, run |
| clic_shutdown or use SAM to stop HyperFabric, and then run clic_start or use |
| SAM to start HyperFabric. Until you do those two things, your configuration changes |
| will not take effect. |
| See “Stopping HyperFabric” on page 99 and “Starting HyperFabric” on page 85 for more |
| information. |
92 | Chapter 4 |