test

Deployment Example: Sun Java System Communications Services for Access Anywhere (EdgeMail)

ProcedureTo Prepare and Jump-Start a Server

Steps

  1. Log into the puppet web interface at https://puppetServer.domain:6364/config.

  2. Select the Advanced Client link. On the Advanced Client page, enter the hostname of the server to jump-start, and press Enter. The server's MAC address should automatically be entered in the Ethernet Address field. Fill in the other fields as follows:

    • Machine Type: sun4u

    • Boot Image: sparc-sunos5.9_u7

    • Model Configuration: for a BE server, select PSC_META, for all others select FE_PSC_META

    Click Add when all fields are complete.

  3. Click on Update Screen, and then on Verify Configuration. In the next screen, click on Commit Changes, and then on Go Back.

  4. Under Base Jumpstart Profile, select the profile corresponding to the type of server:

    • For a BE server, select req_BE+_rootdisk

    • For a FE server, select req_FE+_rootdisk

    • For a FEMTA server, select req_FEMTA+_rootdisk

    • For the administration station, select all_AW+_rootdisk

    • For the backup server, select req_BACKUP+_rootdisk

  5. Make sure the sysidbase value is set to DEFAULT.

  6. Click on Verify Configuration, then on Commit Changes. Now click Go Back and Fetch Current Configuration.

  7. Review the profile and if everything is correct, click on Verify Configuration. The next screen will reconfirm the information, with different models for different server types:


    Hostname serverName
Ethernet Address 0:3:cd:aa:d7:21
Boot Method bootp
Puppet Platform sparc-sunos5.9
Install Image sparc-sunos5.9_u7
Picked Models PSC_META
Expanded Models server server:std-server200501 std-server200501:psc-JES-
model200501 std-server200501:psc-cluster-model200501 std-server200501:psc-
model200501 std-server200501:psc-vts200501 std-server200501:san44-model200501
SunOS: Profile req_BE+_rootdisk
SunOS: sysidcfg(s)
base:  DEFAULT

  8. Click Commit Changes one last time and verify that there are no errors in the configuration. The next screen summarized the actions of the configurator:


    Puppet: Begin Installation Configuration

    * Puppet: Client configuration written
    * SunOS: profile written.
    * SunOS: sysidcfg written.
    * SunOS: bootenv.rc written.
    * SunOS: rules written.
    * SunOS: SI_CONFIG_DIR/rules re-built.
    * SunOS: passed quickcheck.
    * Puppet: OS Driver passed

Puppet: End Installation Configuration

  9. Connect to the console port of the server to be jump-started and enter the following command: 


    ok> boot net - install

  10. After the server has rebooted, follow the configuration procedure for the type of server: