sun.com | docs.sun.com | How To Buy | My Sun | Worldwide Sites |  |

| Previous Contents Index Next
2. ## Creating a Deployable Flash Archive and the Solaris JumpStart Environment This section describes how to create a deployable flash archive by using the `fldeploy` command. The `fldeploy` command is run on the build server. This command does the following: Adds the exported data from the `sldeploy` command to the generic or configured flash archive. The exported data are configuration files for the Foundation Services, including the common configuration file, `nhfs.conf`. Generates the Solaris JumpStart environment for each master-eligible node group and dataless node group. The `fldeploy` command is run once for each master-eligible node group and dataless node group in the software load, because each node group is processed individually. Adds a complete cluster definition to the flash archive. This enables the flash archive to be reused without being regenerated. For example, IP addressing and any changes made before running the `sldeploy` command. For further information, see the `sldeploy`(1M) man page. Creates a deployable flash archive. ### To Create a Deployable Flash Archive and the Solaris JumpStart Environment by Using the `fldeploy` Command Log in to the installation server as a superuser. Run the `fldeploy` command:
       # fldeploy -n SWL1 -v ha_v1 -g master_el -f FLASH_1
   This command generates the flash archive in the default directory defined by the `SMCT_FLASH_DIR` environment variable. It also generates the Solaris JumpStart files in the default directory defined by the `SMCT_JUMPSTART_DIR` environment variable. If you are using configuration data to create a flash archive on the installation server, use the `-e` option of the `fldeploy` command. For example:
       # fldeploy -n swl1 -v ha_v1 -e export-dir -g master_el -f FLASH_1
The `fldeploy` command can be run several times. You can configure the flash archive for one cluster to test it, then reconfigure the cluster archive information and rerun `fldeploy`. For information, see the `fldeploy`(1M) man page. ## Modifying User-Defined Configuration Data This section describes how to modify user-defined configuration data added to a flash archive in stage 2. This is the only part of the deployable flash archive that can be modified after it has been created. However, modifications are only possible with a complete SMCT environment. Ensure that you have run the procedure described in To Transfer the Complete SMCT Environment From the Build Server to the Installation Server. ### To Modify User-Defined Configuration Data To modify user-defined configuration data, the `slconfig` and `flconfig` commands must be run again with the modified user application configuration file. Modify the user application configuration file. For example, `config.master_el` For information on how to modify the user application configuration file, see Creating a User Application Configuration File for a Node Group. Run the `slconfig` command. For information, see To Prepare the User-Defined Configuration Data by Using the `slconfig` Command. Run the `slexport` command. For information, see To Copy the User-Defined Configuration Data to the Export Directory by Using the `slexport` Command. Run the `flconfig` command. For information, see To Add User-Defined Configuration Data to the Flash Archive by Using the `flconfig` Command. If the name or location of the flash archive has changed, run the `fldeploy` command.
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems