Software Images Overview

A software image is an archive of operating environment and N1 Provisioning Server agent software, and it might include application packages. Image creation and deployment enables you to configure the software once and deploy it multiple times. Doing so reduces the chance for error and minimizes system configuration time.

N1 Provisioning Server software supports creation and management of two types of images: global images and account images.

• Global images consist of the operating environment (including patches and service packs), integrated N1 Provisioning Server agents, and certain customizations.

  Global images may also contain applications. Global images are created using the image wizard tool or manually from the command line.

• Account images are for a particular account and might be one of the following account-specific customizations:

  • Global images with customizations such as application and data packages

  • Blank disks (partitioned and formatted)

  Account images are created in the Control Center or on the command line with the snapshot command.

An I-Fabric supports images based on the following operating systems, architectures, and formats:

N1 Provisioning Server software comes with the following preconfigured images that you can import or from which you can create new ones:

• Solaris 9 SPARC flash image

• Solaris 9 x86 flash image

Storing Images and Image Attributes

Images are stored on a local disk of an image server. The image server is a network file system (NFS) file server. The image repository in the control plane database (CPDB) contains attributes of each global image stored in the image server.

Creating and Managing Images

You can create and manage images using one of the following methods:

• Using the image wizard.

• Using image preparation and image release commands on the command line.

• Using the Control Center graphical user interface (GUI). See the N1 Provisioning Server 3.1, Blades Edition, Control Center Management Guide for details.

The following diagram provides an overview of the sequence of steps and the commands involved in performing the following image management tasks:

• Creating images

• Upgrading images

• Importing images

• Validating images

• Updating image attributes

Figure 3–1 Image Management Flow Chart

As the diagram shows, you can import the following newly created images from preconfigured images into the image repository using the image wizard user interface or the image -c command from the command line.

• disk images

• flash images

• JumpStart images

JumpStart and flash images apply to the Solaris operating environment only.

When an image is imported into the image repository, it is marked as either deployable or non-deployable. A deployable image contains all relevant N1 Provisioning Server agent software, customizations, and is ready for deployment to a farm using the Control Center. A non-deployable image is not ready for deployment to a farm using the Control Center. All preconfigured images being shipped with the N1 Provisioning Server contain all the relevant software packages and are therefore marked as deployable when imported into the image repository. Images such as disk, flash, and JumpStart images that might not yet contain all relevant software packages are marked as non-deployable when imported into the image repository.

The image validation process validates a non-deployable image and marks it as deployable if the validation is successful. Validating an image ensures that the image can be deployed using the Control Center during farm creation. You can use either the image wizard or the image -C command from the command line to validate images.

You can create images and add them to the image repository with either the image wizard user interface or the command line using the image -p and image -r commands. With either method, image creation follows a two-step process:

1. Create a farm with a single resource pool server and install an operating environment on the resource pool server using one of the following methods:

   • Creating a new image for the resource pool server from an existing image in the repository

   • Installing an operating environment using an existing JumpStart environment

   • Installing an operating environment manually

2. After you have installed the initial operating environment on the resource pool server, you can customize with other applications. You can then release a disk or flash image using the image -r command.

You also can take a snapshot of an existing image on a resource pool server in a farm using the snapshot command. A disk or flash image created in this way is marked as deployable because the resource pool server in use for a farm has the N1 Provisioning agent installed.

Each image is associated with image attributes, such as image description and size. You can update image attributes using either the image wizard or the image -u command on the command line.

For an image upgrade, such as software upgrade or patch installation, you need to create a new image. You can add the software upgrade or patches during the customization step of the image creation process. See Upgrading Images.

Creating and Managing Images Using the Image Wizard

The image wizard runs on the control plane server and provides a menu-driven, command-line interface for creating, importing, and managing images. Using the image wizard you can perform the following tasks:

Accessing the Image Wizard

Use the /opt/terraspring/sbin/imagewizard command to access the image wizard from the control plane server. See the imagewizard man page for details on how to use the command.

You must have root access to the control plane server before you can access the image wizard.

The following is the image wizard's main dialog:

Please select,

1) Create - Create a new image and store the image in the repository
2) Import - Import an image into the repository
3) List   - List the images in the repository
4) Update - Update image attribute information in the repository
5) Delete - Delete an image in the repository
6) Validate - Validate imported images
7) Quit
Enter your selection [1-7] >

To Create an Image

Steps

1. Type /opt/terrasprin/sbin/imagewizard to access the image wizard's main dialog.

2. In the image wizard's main dialog, type 1 to create an image.

   Make your selections from the following dialog depending on whether you want to create an image from one of the following:

   Image Format	Source	Architecture
   Disk	Existing disk image	Solaris SPARC
   Flash	Existing disk image	Solaris SPARC
   Disk	Existing disk image	Solaris x86
   Flash	Existing disk image	Solaris x86
   Disk	Existing flash image	Solaris SPARC
   Flash	Existing flash image	Solaris SPARC
   Disk	Existing flash image	Solaris x86
   Flash	Existing flash image	Solaris x86
   Disk	JumpStart installation	Solaris SPARC
   Flash	JumpStart installation	Solaris SPARC
   Disk	JumpStart installation	Solaris x86
   Flash	JumpStart installation	Solaris x86
   Disk	Manual installation	Solaris SPARC
   Flash	Manual installation	Solaris SPARC
   Disk	Manual installation	Solaris x86
   Flash	Manual installation	Solaris x86
   Disk	Existing disk image	Linux x86
   Disk	Manual installation	Linux x86

   The following dialogs show example selections for creating images from an existing image.

3. Select the operating environment.

   Following are the operating systems supported: 1) Solaris 2) Linux 3) Return to previous option Please enter your selection [1-3] > 1

4. Select the architecture.

   Following architectures are supported: 1) sun4ublade 2) i86pc 3) Return to previous option Please enter your selection [1-3] > 1

5. Indicate the source for the image.

   You can start creating a new image from: 1) Existing image in the repository 2) JumpStart installation server 3) Manual OS installation 4) Return to previous option Enter your selection [1-4] > 1

6. Select the image type.

   Please select among the following images -------------------------------------------------------------------------- Sel# Image Name Image Id Image Description -------------------------------------------------------------------------- 1) solaris9u5-sun4ublade-flash : 7 : solaris9 update 5 flash image 2) Return to previous option Please enter your selection [1-2] > 1

7. Type 1 to select the device attributes menu for the image.

   Please provide the following information for the new image 1) Device Selection Attributes for the New Image 2) Image Attributes Of the New Image 3) Continue to create the New Image 4) Return to previous option Enter your selection [1-4] > 1

8. Type 1 to select the server type.

   Please enter the following device selection information 1) Server Type: 2) Disk Type: 3) Disk Controller Type: 4) Disk Size: Not specified 5) Return to previous option Please enter your selection [1-5] > 1

9. Indicate the server type.

   Please select the server type 1) sunfireb100x-96-blade 2) sunfireb100s-95-blade 3) Return to previous option Please enter your selection [1-3] > 2

10. Type 2 to select the disk type.

    Please enter the following device selection information 1) Server Type: sunfireb100s-95-blade 2) Disk Type: 3) Disk Controller Type: 4) Disk Size: Not specified 5) Return to previous option Please enter your selection [1-5] > 2

11. Indicate the disk type.

    Please select the disk type 1) local 2) Return to previous option Please enter your selection [1-2] > 1

12. Type 3 to select the disk controller.

    Please enter the following device selection information 1) Server Type: sunfireb100s-95-blade 2) Disk Type: local 3) Disk Controller Type: 4) Disk Size: Not specified 5) Return to previous option Please enter your selection [1-5] > 3

13. Indicate the disk controller.

    Please select the disk controller type 1) ide 2) Return to previous option Please enter your selection [1-2] > 1

14. Type 4 to select the disk size.

    Please enter the following device selection information 1) Server Type: sunfireb100s-95-blade 2) Disk Type: local 3) Disk Controller Type: ide 4) Disk Size: Not specified 5) Return to previous option Please enter your selection [1-5] > 4

15. Indicate the disk size.

    Please select the disk size 1) 30000000000 2) Return to previous option Please enter your selection [1-2] > 1

16. Type 5 to return to the main image information menu shown in step 5.

    Please enter the following device selection information 1) Server Type: sunfireb100s-95-blade 2) Disk Type: local 3) Disk Controller Type: ide 4) Disk Size: 30000000000 Bytes 5) Return to previous option Please enter your selection [1-5] > 5

17. Type 2 to select the image attributes menu.

    Please provide the following information for the new image 1) Device Selection Attributes for the New Image 2) Image Attributes Of the New Image 3) Continue to create the New Image 4) Return to previous option Enter your selection [1-4] > 2

18. Indicate the image name.

    Please enter the following image attribute information 1) Image name: 2) Image description: 3) Image archive type: 4) Image type: Global Image 5) Image size: Not specified 6) Return to previous option Please enter your selection [1-6] > 1 Please enter the image name > s9u5-customized-test

19. Type 2 to select and specify the image description.

    Please enter the following image attribute information 1) Image name: s9u5-customized-test 2) Image description: 3) Image archive type: 4) Image type: Global Image 5) Image size: Not specified 6) Return to previous option Please enter your selection [1-6] > 2 Please enter the image description > created from s9u5 preconfigured image with customizations

20. Type 3 to select the archive type.

    Please enter the following image attribute information 1) Image name: s9u5-customized-test 2) Image description: created from s9u5 preconfigured image with customizations 3) Image archive type: 4) Image type: Global Image 5) Image size: Not specified 6) Return to previous option Please enter your selection [1-6] > 3

21. Indicate the archive type.

    Following image archive types are supported: 1) disk_image 2) flash 3) Return to previous option Please enter your selection [1-3] > 2

22. Type 6 to return to the main image information menu shown in step 5.

    ---

    Note –

    Selection 4 from the following menu is not available for modification because the image wizard enables creation of global images only.

    ---

    Please enter the following image attribute information 1) Image name: s9u5-customized-test 2) Image description: created from s9u5 preconfigured image with customizations 3) Image archive type: flash 4) Image type: Global Image 5) Image size: Not specified 6) Return to previous option Please enter your selection [1-6] > 6

23. Type 3 to continue the image creation.

    Please provide the following information for the new image 1) Device Selection Attributes for the New Image 2) Image Attributes Of the New Image 3) Continue to create the New Image 4) Return to previous option Enter your selection [1-4] > 3 Following is the information you have entered Create from existing image: solaris9u5-sun4ublade-flash Operating system: solaris Architecture: sun4ublade Image name: s9u5-customized-test Image description: created from s9u5 preconfigured image with customizations Image archive type: flash Image type: Global Image Image size: Not specified Server Type: sunfireb100s-95-blade Disk Type: local Disk Controller Type: ide Disk Size: 30000000000 Bytes

24. Type y to continue with the image creation procedure.

    Enter y to continue and n to return to previous option > y

25. Verify that you have enough space on the image server for the new image, then type y.

    Please ensure that you have enough space on the image server to hold the new image that will be created. The path on image server where the image will be created is: /images/master-images Enter y to continue and n to return to previous option > y

26. If you want to use NFS shares from the N1 Provisioning Server, type y. If you do not want to use NFS shares from the N1 Provisioning Server, type n.

    Specify whether you want to use NFS shares from N1 Provisioning Server [default n] > n Preparing farm for image creation/validation. This will take some time, please wait till the operation completes. Do not interrupt the operation. Please run farm -Lt <farm id> for more information.

Example 3–1 Image Creation Output

The following output example also contains instructions on how to prepare the image for release to the resource pool server. See Creating A Solaris Image from a Preconfigured Image, Creating a Solaris Image Manually from JumpStart, Creating the JumpStart Setup, and Customizing the JumpStart Boot and Configuration Server.

If, after starting the image -r command, a replaceFailedDevice request is queued. You must delete this request for the image creation process to complete successfully. Run the request -l command to get the request ID, then use the request -d request_ID command to do delete the request.

Creating farm 'ImageTool1076361866520-751' ...
Request (id: 335) submitted.
Waiting for request 335 to complete...
.
Farm ImageTool1076361866520-751 is created. Farm id = 108
Activating farm 108 ...
Request (id: 336) submitted.
Waiting for farm request 336 to complete or
farm to reach state 50 ...
...........................................................
Farm 108 is ready for image creation/update.
Please proceed to PES 50101, disk 2 and install/update the software.

After you are finished with the image, please execute the following to release the image:
    image -r [-S image_size] [-T image_archive_type] -f 108 -i <new-image-name>


Completed preparing farm for image creation/validation
Farm ID is: 108

The following resource pool server has been
selected for creating an image.
Resource Pool Server Device ID: 50101

Following is the information on how you can gain console
access to this machine.

In an another window, telnet to the specified system controller (SC)
based on the IP address provided below.

Login into the SC using the username and password of the SC and type

console <id>

The <id> is the id printed below,
(for e.g., sc> console s5)
 
 Console Information
 ====================
 IP address of Terminal-Server(Service Controller): 10.5.136.20
 Port(Blade) ID: s1



Issue the following commands on the sytem controller to boot the
resource pool server from the disk

sc> bootmode bootscript="boot disk" s<x>.
(where "s<x>" is provided in resource pool server information)

then you can issue the following command to reset

sc> reset -y s<x> 

Please enter y when the resource pool server has booted from disk > y


You can customize your installation at this point in time.

Please logon to the resource pool server and customize.

Please enter y when your customization is completed > y


Please shutdown the resource pool server by issuing the command

For Solaris:
# /usr/sbin/shutdown -y -g0 -i0
For Linux:
# /sbin/shutdown -h now

Once the resource pool server shuts down, for sparc blades set the
OBP of resource pool server to boot using dhcp by issuing the following
command in the OBP prompt (no changes are required for i86pc blades) 

ok> setenv boot-device net:dhcp

Please enter y when the resource pool server has completed the shutdown
and when you have configured the resource pool server to boot using dhcp > y

Creating image.

This will take some time, please wait till the operation completes.
Do not interrupt the operation.
Please run farm -Lt <farm-id> for more information.

Disabling monitoring on PES 50101
Powering off PES 50101 for a move to it's original VLAN
Setting PES State to OFF
Moving PES 50101 to its original VLAN
Powering on PES 50101 in it's original VLAN
Setting PES State to ON
Activating farm 108 ...
Request (id: 397) submitted.
Waiting for request 397 to complete...
..
Taking snapshot of target 0 for host server for farm 108 to create final image ...
Request (id: 400) submitted.
Waiting for request 400 to complete...
.....................................................................................
Snapshot was successful.
Deactivating the farm 108
Request (id: 456) submitted.
Waiting for request 456 to complete...
.............................................................................
Farm 108 is deactivated.
Image s9u5-customized-test is ready for use.

Image creation completed.


Updating image attributes.


Updated image: 14


Image update completed.

WARNING: The farm created for image creation has to be deleted manually. 
        Use the farm -D <farm-id> command to delete the farm.
        Please wait for the farm to be deactivated before you issue
        this command.

To Upgrade an Image

Before You Begin

For an image upgrade, such as software upgrade or patch installation, you need to create a new image. You can add the software or patches during the customization step of the image creation process.

Steps

1. Select the Create Image option.

2. Select the Create from Existing Image option.

3. Provide the information for the new image.

4. Answer the following questions with “y”.

   Specify whether you want to use NFS shares from the N1 Provisioning Server [default n] y.

5. The image wizard will prompt you to customize the image. To do so connect to the resource pool server using telnet and install any new software packages and patches.

6. Follow the image wizard instructions to create the new image.

To Import an Image

Steps

1. From the image wizard's main dialog, type 2 to import an image.

2. Specify whether you want to import a preconfigured image or another image.

   • Type 1 to import a preconfigured image.

   • Type 2 to import another image.

     You can start importing images from: 1) Canned images supplied with this product 2) Other images 3) Return to previous option Enter your selection [1-3] > 2 CAUTION: You are about to import an image that is not supplied with this product. Please refer to the System Administration Guide for importing images not supplied with the product.

3. Type y to continue importing an image.

   Please enter y if you want to continue [default y] > y

4. Type 1 to provide operating environment information for the image to be imported.

   Please provide information for importing image 1) Operating system: 2) Architecture: 3) Image name: 4) Image description: 5) Image archive type: 6) Image type: Account Image: Account Name: 7) Image size: 0 8) Image location: 9) Image config file: 10) Continue to import image 11) Return to previous option Please enter your selection [1-11] > 1

5. Select an operating environment from the list.

   Following are the operating systems supported: 1) Solaris 2) Linux 3) Return to previous option Please enter your selection [1-3] > 1

6. Type 2 to provide architecture information for the image to be imported.

   Please provide information for importing image 1) Operating system: solaris 2) Architecture: 3) Image name: 4) Image description: 5) Image archive type: 6) Image type: Account Image: Account Name: 7) Image size: 0 8) Image location: 9) Image config file: 10) Continue to import image 11) Return to previous option Please enter your selection [1-11] > 2

7. Select an architecture from the list.

   Following architectures are supported: 1) sun4ublade 2) i86pc 3) Return to previous option Please enter your selection [1-3] > 1

8. Type 3 to provide a name for the image to be imported.

   Please provide information for importing image 1) Operating system: solaris 2) Architecture: sun4ublade 3) Image name: 4) Image description: 5) Image archive type: 6) Image type: Account Image: Account Name: 7) Image size: 0 8) Image location: 9) Image config file: 10) Continue to import image 11) Return to previous option Please enter your selection [1-11] > 3

9. Type the image name.

   Please enter the image name > s9u5-jumpstart-test

10. Type 4 to provide a description for the image to be imported.

    Please provide information for importing image 1) Operating system: solaris 2) Architecture: sun4ublade 3) Image name: s9u5-jumpstart-test 4) Image description: 5) Image archive type: 6) Image type: Account Image: Account Name: 7) Image size: 0 8) Image location: 9) Image config file: 10) Continue to import image 11) Return to previous option Please enter your selection [1-11] > 4

11. Type the image description.

    Please enter the image description > s9u5 jumpstart settings

12. Type 5 to provide the archive type for the image to be imported.

    Please provide information for importing image 1) Operating system: solaris 2) Architecture: sun4ublade 3) Image name: s9u5-jumpstart-test 4) Image description: s9u5 jumpstart settings 5) Image archive type: 6) Image type: Account Image: Account Name: 7) Image size: 0 8) Image location: 9) Image config file: 10) Continue to import image 11) Return to previous option Please enter your selection [1-11] > 5

13. Select the image archive type from the list.

    Following image archive types are supported: 1) disk_image 2) flash 3) jumpstart 4) Return to previous option Please enter your selection [1-4] > 3

14. Type 6 to provide the image type for the image to be imported.

    Please provide information for importing image 1) Operating system: solaris 2) Architecture: sun4ublade 3) Image name: s9u5-jumpstart-test 4) Image description: s9u5 jumpstart settings 5) Image archive type: jumpstart 6) Image type: Account Image: Account Name: 7) Image size: Not specified 8) Image location: 9) Image config file: 10) Continue to import image 11) Return to previous option Please enter your selection [1-11] > 6

15. Select the image type from the list.

    Please enter the image type 1) Global Image 2) Account Image 3) Return to previous option Enter your selection > 1

16. Type 7 to provide the size for the image to be imported.

    Please provide information for importing image 1) Operating system: solaris 2) Architecture: sun4ublade 3) Image name: s9u5-jumpstart-test 4) Image description: s9u5 jumpstart settings 5) Image archive type: jumpstart 6) Image type: Global Image 7) Image size: Not specified 8) Image location: 9) Image config file: 10) Continue to import image 11) Return to previous option Please enter your selection [1-11] > 7

17. Specify the image size.

    Please enter the image size [Not specified] > 30000000000

18. Type 8 to provide the location for the image to be imported.

    Please provide information for importing image 1) Operating system: solaris 2) Architecture: sun4ublade 3) Image name: s9u5-jumpstart-test 4) Image description: s9u5 jumpstart settings 5) Image archive type: jumpstart 6) Image type: Global Image 7) Image size: 30000000000 8) Image location: 9) Image config file: 10) Continue to import image 11) Return to previous option Please enter your selection [1-11] > 8

19. Specify the location.

    Provide the image location URL (<protocol>://<device-id>/<path>) Make sure the directory specified by <path> exists before going further. (e.g., nfs://3001/images/master-images/test-image-1 e.g., ftp://3001/images/master-images/test-image-2 e.g., nfs://3001/images/jumpstart) > nfs://3001/images/jumpstart

20. Type 9 to provide the configuration file for the image to be imported.

    Please provide information for importing image 1) Operating system: solaris 2) Architecture: sun4ublade 3) Image name: s9u5-jumpstart-test 4) Image description: s9u5 jumpstart settings 5) Image archive type: jumpstart 6) Image type: Global Image 7) Image size: 30000000000 8) Image location: nfs://3001/images/jumpstart 9) Image config file: 10) Continue to import image 11) Return to previous option Please enter your selection [1-11] > 9

21. Type 1 to provide the JumpStart installation server for the image to be imported.

    Please provide the following information for the Jumpstart configuration 1) Solaris install server:Solaris product directory: 2) Solaris boot server:Solaris boot directory: 3) Configuration server:Configuration directory: 4) JumpStart server:JumpStart directory: 5) Return to previous option Please enter your selection [1-5] > 1

22. Specify the JumpStart installation server and path.

    Specify server and the path to directory on the server where the solaris distribution can be found. Refer setup_install_server -s option. [10.42.42.1:/images/s9u5] > 10.42.42.1:/images/s9u5

23. Type 2 to provide the JumpStart boot server for the image to be imported.

    Please provide the following information for the Jumpstart configuration 1) Solaris install server:Solaris product directory: 10.42.42.1:/images/s9u5 2) Solaris boot server:Solaris boot directory: 3) Configuration server:Configuration directory: 4) JumpStart server:JumpStart directory: 5) Return to previous option Please enter your selection [1-5] > 2

24. Specify the JumpStart boot server and path.

    Specify server and the path to directory on the server where the solaris miniroot is located. Refer setup_install_server -b -t option. [10.42.42.1:/tftpboot/terraspring/boot_loader/sun4ublade/Boot] > 10.42.42.1:/tftpboot/terraspring/boot_loader/sun4ublade/Boot

25. Type 3 to provide the JumpStart configuration server for the image to be imported.

    Please provide the following information for the Jumpstart configuration 1) Solaris install server:Solaris product directory: 10.42.42.1:/images/s9u5 2) Solaris boot server:Solaris boot directory: 10.42.42.1:/tftpboot/terraspring/boot_loader/sun4ublade/Boot 3) Configuration server:Configuration directory: 4) JumpStart server:JumpStart directory: 5) Return to previous option Please enter your selection [1-5] > 3

26. Specify the JumpStart configuration server and path.

    Specify server and the path to directory on the server where the user-defined sysidcfg file for pre-configuring system or network information is located. Refer add_install_client -p option. [10.42.42.1:/images/jumpstart] > 10.42.42.1:/images/jumpstart

27. Type 4 to provide the JumpStart server directory for the image to be imported.

    Please provide the following information for the Jumpstart configuration 1) Solaris install server:Solaris product directory: 10.42.42.1:/images/s9u5 2) Solaris boot server:Solaris boot directory: 10.42.42.1:/tftpboot/terraspring/boot_loader/sun4ublade/Boot 3) Configuration server:Configuration directory: 10.42.42.1:/images/jumpstart 4) JumpStart server:JumpStart directory: 5) Return to previous option Please enter your selection [1-5] > 4

28. Specify the JumpStart directory location.

    Specify server and the path to the directory on the server where the JumpStart files are located. Refer add_install_client -c option. [10.42.42.1:/images/jumpstart] > 10.42.42.1:/images/jumpstart

29. Type 5 to return to the previous menu.

    Please provide the following information for the Jumpstart configuration 1) Solaris install server:Solaris product directory: 10.42.42.1:/images/s9u5 2) Solaris boot server:Solaris boot directory: 10.42.42.1:/tftpboot/terraspring/boot_loader/sun4ublade/Boot 3) Configuration server:Configuration directory: 10.42.42.1:/images/jumpstart 4) JumpStart server:JumpStart directory: 10.42.42.1:/images/jumpstart 5) Return to previous option Please enter your selection [1-5] > 5

30. Type 10 to continue to import the image.

    Please provide information for importing image 1) Operating system: solaris 2) Architecture: sun4ublade 3) Image name: s9u5-jumpstart-test 4) Image description: s9u5 jumpstart settings 5) Image archive type: jumpstart 6) Image type: Global Image 7) Image size: 30000000000 8) Image location: nfs://3001/images/jumpstart 9) Image config file: Has config file 10) Continue to import image 11) Return to previous option Please enter your selection [1-11] > 10

Example 3–2 Image Importing Output

Importing image: s9u5-jumpstart-test
Importing image into image repository.

-------------------- output of internal commands --------------------
Created server image: 16

To Validate an Image

Steps

1. In the image wizard's main dialog, type 6 to validate images.

2. Select the image to be validated.

   You can validate these images: Please select among the following images -------------------------------------------------------------------------- Sel# Image Name Image Id Image Description -------------------------------------------------------------------------- 1) s9u5-jumpstart-test : 16 : s9u5 jumpstart settings 2) Return to previous option Please enter your selection [1-2] > 1

3. Type 1 to provide the server type information.

   Please enter the following device selection information 1) Server Type: 2) Disk Type: 3) Disk Controller Type: 4) Disk Size: Not specified 5) Continue to validate image 6) Return to previous option Please enter your selection [1-6] > 1

4. Select the server type.

   Please select the server type 1) sunfireb100x-96-blade 2) sunfireb100s-95-blade 3) Return to previous option Please enter your selection [1-3] > 2

5. Type 2 to provide the disk type information.

   Please enter the following device selection information 1) Server Type: sunfireb100s-95-blade 2) Disk Type: 3) Disk Controller Type: 4) Disk Size: Not specified 5) Continue to validate image 6) Return to previous option Please enter your selection [1-6] > 2

6. Select the disk type.

   Please select the disk type 1) local 2) Return to previous option Please enter your selection [1-2] > 1

7. Type 3 to provide the disk controller type information.

   Please enter the following device selection information 1) Server Type: sunfireb100s-95-blade 2) Disk Type: local 3) Disk Controller Type: 4) Disk Size: Not specified 5) Continue to validate image 6) Return to previous option Please enter your selection [1-6] > 3

8. Select the disk controller type.

   Please select the disk controller type 1) ide 2) Return to previous option Please enter your selection [1-2] > 1

9. Type 4 to provide the disk size information.

   Please enter the following device selection information 1) Server Type: sunfireb100s-95-blade 2) Disk Type: local 3) Disk Controller Type: ide 4) Disk Size: Not specified 5) Continue to validate image 6) Return to previous option Please enter your selection [1-6] > 4

10. Select the disk size.

    Please select the disk size 1) 30000000000 2) Return to previous option Please enter your selection [1-2] > 1

11. Type 5 to continue to validate the image.

    Please enter the following device selection information 1) Server Type: sunfireb100s-95-blade 2) Disk Type: local 3) Disk Controller Type: ide 4) Disk Size: 30000000000 Bytes 5) Continue to validate image 6) Return to previous option Please enter your selection [1-6] > 5

12. Confirm whether you want to continue image validation.

    • Type y to continue validation.

    • Type nto discontinue validation.

      You are about to validate the selected image. Enter y to continue and n to return to previous option > y

Example 3–3 Image Validation Output

Preparing farm for image creation/validation.

This will take some time, please wait till the operation completes.
Do not interrupt the operation.
Please run farm -Lt <farm-id> for more information.


-------------------- output of internal commands --------------------
Creating farm 'ImageTool1076366989009-409' ...
Request (id: 468) submitted.
Waiting for request 468 to complete...
.
Farm ImageTool1076366989009-409 is created. Farm id = 110
Activating farm 110 ...
Request (id: 471) submitted.
Waiting for farm request 471 to complete or
farm to reach state 40 ...
..........................................................................................................
Farm 110 has reached the ACTIVE/ACTIVE state.
Deactivating the farm 110
Request (id: 559) submitted.
Waiting for request 559 to complete...
...................................................................................
Farm 110 is deactivated.
Image s9u5-jumpstart-test is validated and  ready for use.
--------------------------- end of command --------------------------

Completed preparing farm for image creation/validation
Farm ID is: 110

WARNING: The farm created for image validation has to be deleted manually. 
        Use the farm -D <farm-id> command to delete the farm.
        Please wait for the farm to be deactivated before you issue
        this command.

To List Images

Steps

1. In the image wizard's main dialog, type 3 to list images.

2. From the display options menu make a selection for displaying the images.

   Please enter one of the following options for displaying the images 1) List all images 2) List images available for use (READY state) 3) List images marked as deleted 4) List global images 5) List information of global images (brief) 6) List information of global images (verbose) 7) List images of a specific account 8) List information of an image of a specific account (brief) 9) List information of an image of a specific account (verbose) 10) List information of an image specified by id 11) List information of an image specified by id (brief) 12) List information of an image specified by id (verbose) 13) Return to previous option Enter your selection [1-13] > 1

   The following output shows the display of images if you had selected 1 from the display options menu.

   -------------------- output of internal commands -------------------- IMAGE_ID IMAGE_NAME CUSTOMER SIZE OS TYPE STATE 2 solaris9u5-sun4ublade-flash __grid__ 3004789248 solaris flash READY LOCATION nfs://3001//images/master-images/solaris9u5-sun4ublade-flash 3 solaris9u5-sun4ublade-disk-image __grid__ 30000000000 solaris disk_image READY LOCATION nfs://3001//images/master-images/solaris9u5-sun4ublade-disk-image 4 solaris9u5-i86pc-disk-image __grid__ 30000000000 solaris disk_image READY LOCATION nfs://3001//images/master-images/solaris9u5-i86pc-disk-image 5 sw@50250 __grid__ 19813 disk_image READY 6 sw@50150 __grid__ 19807 disk_image READY 21 s9u5-disk_image __grid__ 5000000 solaris disk_image READY LOCATION nfs://3001//images/master-images/s9u5-disk_image 22 s9u5-flash __grid__ 5000000 solaris flash READY LOCATION nfs://3001//images/master-images/s9u5-flash 23 test-other-images-wizard testid 500000 solaris disk_image NOT READY LOCATION nfs://3001/images/master-images/test-image --------------------------- end of command --------------------------

3. Press y to continue displaying the list of images available.

   Enter y to continue [default y] > y

To Update Image Attributes

Steps

1. In the image wizard's main dialog, type 4 to update image attributes.

2. Type the number of the image you want to update.

   You are about to update attributes of an existing image in the image repository. CAUTION: Please refer to the System Administration Guide for updating images. Updating wrongly the operating system, architecture, image archive type, image size, image location, or image config file might lead to failures in deploying the image. Please select among the following images -------------------------------------------------------------------------- Sel# Image Name Image Id Image Description -------------------------------------------------------------------------- 1) solaris9u5-sun4ublade-flash : 7 : solaris9 update 5 flash image 2) solaris9u5-i86pc-flash : 8 : solaris9 update 5 flash image 3) sw@50150 : 10 : sw@50150 4) Return to previous option Please enter your selection [1-4] > 1

3. Type the number of the image information you want to update.

   You can update the following image information 1) Operating system: solaris 2) Architecture: sun4ublade 3) Image name: solaris9u5-sun4ublade-flash 4) Image description: solaris9 update 5 flash image for sun4ublade with Cassini NIC 5) Image archive type: flash 6) Image size: 30000000000 7) Image location: nfs://3001//images/master-images/solaris9u5-sun4ublade-flash 8) Image config file: Has config file 9) Continue to update image 10) Return to previous option

   ---

   Note –

   The image location, selection 7 on the menu, is a default value that you cannot modify.

   ---

4. You are prompted to continue to make update selections depending on what type of image information you chose to update in the previous step.

   ---

   Caution –

   If you make a wrong choice in the updating process, no alert message will display. The image will not deploy.

   ---

Example 3–4 Updating the Image Size

Please enter your selection [1-10] > 6

Please enter the image size [30000000000] > 28000000000

Please enter your selection [1-10] > 9

Updating image attributes.


-------------------- output of internal commands --------------------
Updated image: 7

To Delete an Image

Steps

1. In the image wizard's main dialog, type 5 to delete images.

2. Make your selections from the following dialogs depending on whether you want to:

   • Delete a global image.

   • Delete an account-specific image.

   The following example shows how to delete a global image:

   You can delete these images: 1) Delete a global image from the repository 2) Delete an account image from the repository 3) Return to the previous option Enter your selection [1-3] > 1 You are about to delete an existing image in the image repository. Please select among the following images -------------------------------------------------------------------------- Sel# Image Name Image Id Image Description -------------------------------------------------------------------------- 1) solaris9u5-sun4ublade-flash : 7 : solaris9u5-sun4ublade-flash 2) solaris9u5-i86pc-flash : 8 : solaris9 update 5 flash image 3) sw@50150 : 10 : sw@50150 4) s9u5-customized-test : 14 : s9u5-customized-test 5) Return to previous option Please enter your selection [1-5] > 4 Deleting image. -------------------- output of internal commands -------------------- Delete Image 14 (y/n)? y Queueing request to delete image ... Request (id: 612) submitted. Waiting for request 612 to complete... . Deleting image content at: nfs://3001/images/master-images/s9u5-customized-test size: 759406246 ip: 10.42.42.1 State: done --------------------------- end of command -------------------------- Image deletion completed.

Creating and Managing Images from the Command Line

Using the command line, you can perform the following image management tasks:

The following graphic illustrates the sequence of creating and upgrading a global image:

Figure 3–2 Creating and Updating Global Images from the Command Line

Images are available to farms through the Control Center once the Control Center is synchronized. When configuring servers for a farm, you can select global images from a drop-down list as described in the N1 Provisioning Server 3.1, Blades Edition, Control Center Management Guide.

Before you begin creating global images, ensure that enough storage is available on the N1 Provisioning Server or, if you are using a separate server for storing images, on the image server.

Image Creation Methods and the Steps Involved

The following table summarizes the command line image creation methods supported by the N1 Provisioning Server software.

Creating A Solaris Image from a Preconfigured Image

Before creating an image, use the image -ls command or the Control Center Administration dialog to check whether the image already exists. See the N1 Provisioning Server 3.1, Blades Edition, Control Center Management Guide for details. The N1 Provisioning Server software package comes with a preconfigured Solaris image. Use this image as a basis to create your Solaris image. This section describes how to create a Solaris image from the preconfigured Solaris image provided with the N1 Provisioning Server software product.

Creating a Solaris image involves 11 steps. These steps are performed either on the control plane server or on the resource pool server. The following table describes the sequence of the steps to be performed and on which device you need to perform each step for creating an image:

To Create a Solaris Image From a Preconfigured Image

Steps

1. Determine the server type, disk type, disk size, and disk controller by using the following commands:

   /opt/terraspring/sbin/disk -l

   /opt/terraspring/sbin/disk -lv

   /opt/terraspring/sbin/device -l

   The output of these commands is used as a parameter to the image command in subsequent steps.

2. Obtain a list of images using the image -ls command.

3. Run the image -p -i command from the N1 Provisioning Server.

   The command creates a farm with one disk on a resource pool server that contains an appropriate-sized disk.

   The image -p -i command for such an image creation procedure takes the form:

   image -p -i image_name server_type disk_type controller_type disk_size

   For example:

   image -p -i solaris9u5sun4ublade-flash sunfire100s-95-blade local ide 30000000000

   ---

   Note –

   For more detailed information, see the image man page.

   ---

   ---

   Note –

   In addition, if access to the N1 Provisioning Server DVD or another shared medium is required for software installation, use the -z option to specify this. You can also specify this option to have access to these shared media during new image creation.

   ---

   ---

   Note –

   The image -p command creates a new farm to be used in creating a new image. The image -p tool exits with information regarding the allocated resource pool server and the farm ID of the farm created. The farm ID is required for the eventual release of the allocated resources using the image -r command (see below). The image -r command releases the image, reactivates the farm, and completes the image creation process.

   ---

4. Logon to the resource pool server selected by the image -p -i command.

5. Customize the image with applications and services according to your requirements.

   ---

   Note –

   To find out which resource pool server is mapped to the farm that was created by the image -p command, type device -l.

   ---

6. Verify that the N1 Provisioning Server agent is running by typing from the resource pool server:

   ps -aef | grep tspragt IP-address-of-server-used-to-create-image "tsprnop IP-address-of-server-used-to-create-image"

   The output from the ps command should look similar to the following:

   root 361 1 1 00:37:41 ? 0:01 java-Dsun.net.inetaddr.ttl=0 com.terraspring.mon.client.tspragt start 220.240

7. Stop the resource pool server by typing:

   /usr/sbin/shutdown -y -g0 -i0 for Solaris

   /sbin/shutdown —h now for Linux

8. Configure the server blade to boot from DHCP.

   • For SPARC, at the OBP prompt type:

     setenv boot-device net:dhcp

     ---

     Note –

     x86 servers boot from DHCP by default.

     ---

9. Run the image -r command from the N1 Provisioning Server.

   This command releases the farm you created with the image —p command. Releasing the farm includes the following:

   • Taking a snapshot of the image. The snapshot serves as the new image you have just created.

   • Releasing the resource pool server to the resource pool.

   • Updating the N1 Provisioning Server database with a reference to the image.

   image -r -f farm_ID -S image_size -i image_name -T archive-type

   For example:

   image -r -f 171 -S 3000000000 -i new_solaris_image -T flash-image

   ---

   Note –

   If, after starting the image -r command, a replaceFailedDevice request is queued. You must delete this request for the image creation process to complete successfully. Run the request -l command to get the request ID, then use the request -d request_ID command to do delete the request.

   ---

10. Optionally, you can update the image attributes by using the image -u command.

11. Delete the farm by typing farm -Df farm-ID.

    Example:

    farm -Df 171

Make the Image Available to Accounts

To make the image available to accounts, use the Administration dialog of the Control Center to synchronize the Control Center with the CPDB. See the N1 Provisioning Server 3.1, Blades Edition, Control Center Management Guide for details.

Creating a Solaris Image Manually from JumpStart

Before creating an image, use the image -ls command or the Control Center Administration dialog to check whether the image already exists. See the N1 Provisioning Server 3.1, Blades Edition, Control Center Management Guide for details.

Creating a Solaris image requires setting up a JumpStart server. This section describes how to create a Solaris image using a JumpStart server.

Creating a Solaris image using JumpStart involves 14 steps. These steps are performed either on the control plane server or on the resource pool server. The following table describes the sequence of the steps to be performed and on which device you need to perform each step for creating an image:

To Create a Solaris Image Manually From JumpStart

Steps

1. Determine the server type, disk type, disk size, and disk controller by using the following commands:

   /opt/terraspring/sbin/disk -l

   /opt/terraspring/sbin/disk -lv

   /opt/terraspring/sbin/device -l

   The output of these commands is used as a parameter to the image command in subsequent steps.

2. Set up a JumpStart installation Server.

   See Creating the JumpStart Setup.

3. Customize the boot and configuration JumpStart servers appropriately for SPARC and x86 architectures.

   See Customizing the JumpStart Boot and Configuration Server.

4. Run the image -p -j command from the N1 Provisioning Server.

   The command creates a farm with one disk on a resource pool server that contains an appropriate-sized disk.

   The image -p -j command for such an image creation procedure takes the form:

   image -p -j JumpStart_options_file server_type disk_type controller_type disk_size

   For example:

   image -p -j /image/jumpstart/js-options sunfire100s-95-blade local ide 30000000000

   ---

   Note –

   For more detailed information, see the image man page.

   ---

   ---

   Note –

   In addition, if access to the N1 Provisioning Server DVD or another shared medium is required for software installation, use the -z option to specify this. You can also specify this option to have access to these shared media during new image creation.

   ---

   Use the -j option to specify the path to a file containing the DHCP name/value pairs pertinent to the Solaris SPARC JumpStart server. This file might look like the following:

   SinstNM image-server SinstIP4 10.42.42.1 SinstPTH /images/s9u5s SrootNM image-server SrootIP4 10.42.42.1 SrootPTH /images/s9u5s/Solaris_9/Tools/Boot SsysidCF 10.42.42.1:/images/jumpstart/sun4ublade SjumpsCF 10.42.42.1:/images/jumpstart

   The file contains one option pair per line. The Solaris DHCP server options are required and they are typically furnished by the add_install_client tool (when used with the -d option) for configuring a JumpStart client. See alsoCreating the JumpStart Setup for an example of setting up a JumpStart server and running the add_install_client script.

   ---

   Note –

   The image -p command creates a new farm to be used in creating a new image. The farm attempts to activate but will fail because no image has yet been installed on the server. The image -p tool exits with information regarding the allocated resource pool server and the farm ID of the farm created. The farm ID is required for the eventual release of the allocated resources using the image -r command (see below). The image -r command releases the image, reactivates the farm, and completes the image creation process.

   ---

   The image command sets up a resource pool server of the type requested. When the resource pool server is ready, you are notified to connect to the server through the console to initiate the JumpStart installation.

5. Logon to the system controller of the chassis that contains the resource pool server through telnet.

   ---

   Note –

   To find out which resource pool server is mapped to the farm that was created by the image -p command, type device -l.

   ---

   ---

   Note –

   If you are using the postinstall.sh script and customizing the JumpStart boot and configuration servers, the DHCP client configuration and the N1 Provisioning Server agent installation onto the resource pool server are completed. If you are not using the postinstall.sh script, see Customizing the Resource Pool Server Manually.

   ---

6. Logon to the blade's SSC to set up the resource pool server to start installation type:

   For SPARC architecture:

   bootmode bootscript="boot net:dhcp - install" blade-ID

   reset -y blade-ID

   For x86 architecture:

   bootmode bootscript="boot net:dhcp" blade-ID

   reset -y blade-ID

   This command initiates the JumpStart installation, if the DHCP parameters you provided in previous steps are correct.

   ---

   Note –

   If the resource pool server does not boot from disk, from the system controller type:

   bootmode bootscript="boot disk" blade blade-ID

   reset -y

   ---

7. Optionally, you can customize the image with applications and services according to your requirements. To customize the image logon to the resource pool server as root.

8. Verify that the N1 Provisioning Server agent is running by typing:

   ps -aef | grep tspragt IP-address-of-server-used-to-create-image "tsprnop IP-address-of-server-used-to-create-image"

   The output from the ps command should look similar to the following:

   root 361 1 1 00:37:41 ? 0:01 java-Dsun.net.inetaddr.ttl=0 com.terraspring.mon.client.tspragt start 220.240

9. Stop the server by typing:

   /usr/sbin/shutdown -y -g0 -i0 for Solaris

   /sbin/shutdown -h now for Linux

10. Configure the server blade to boot from DHCP.

    • For SPARC, at the OBP prompt type:

      setenv boot-device net:dhcp

      ---

      Note –

      x86 servers boot from DHCP by default.

      ---

11. Logon to the blade's SSC to set the boot mode for the blade to boot from DHCP:

    bootmode bootscript="boot net:dhcp" blade-ID

    reset -y blade ID

12. Run the image -r command from the N1 Provisioning Server.

    This command releases the farm you created with the image —p command. Releasing the farm includes the following:

    • Taking a snapshot of the image. The snapshot serves as the new image you have just created.

    • Releasing the resource pool server to the resource pool.

    • Updating the N1 Provisioning Server database with a reference to the image.

    image -r -f farm_ID -S image_size -i image_name -T archive-type

    For example:

    image -r -f 171 -S 3000000000 -i new_solaris_image -T flash

    ---

    Note –

    If, after starting the image -r command, a replaceFailedDevice request is queued. You must delete this request for the image creation process to complete successfully. Run the request -l command to get the request ID, then use the request -d request_ID command to do delete the request.

    ---

13. Optionally, you can update the image attributes by using the image -u command.

14. Delete the farm by typing farm -Df farm-ID.

Make the Image Available to Accounts

To make the image available to accounts, use the Administration dialog of the Control Center to synchronize the Control Center with the CPDB. See the N1 Provisioning Server 3.1, Blades Edition, Control Center Management Guide for details.

Creating a Linux Image Manually

For details on how to manually create a Linux image, see the N1 Provisioning Server 3.1, Blades Edition, Release Notes.

Upgrading Images

You might want to upgrade an image with patches or software packages. This section describes how to upgrade images. Upgrading images involves the same steps and commands as are used for creating images, except that you use the -i image_name option with the image -p command.

When you upgrade an image, a copy of the original image is placed onto a new disk to allow you to upgrade the newly copied image. Before releasing the new image using the image -r command, you must give the new image a unique name.

To Upgrade Images

Steps

1. Obtain a list of the images using the command:

   image -ls IMAGE_ID IMAGE_NAME CUSTOMER DISK_VOL_ID SIZE OS 2 solaris __grid__ 22001/5 8631 Solaris 1087 solaris_dhcpfix __grid__ 22001/22 8631 Solaris

2. Type the following command:

   image –p [-z] [-i image_name] server_type disk_type controller_typ disk_size

   For example:

   image -p –z –i master_image sun_svr_420R local ide 30004789248

   ---

   Note –

   If access to the N1 Provisioning Server DVD or other shared media is required for software installation, use the -z option to specify this.

   ---

3. Logon to the resource pool server.

4. Modify the image according to your requirements, such as updating the N1 Provisioning Server monitoring package. See Upgrading the N1 Provisioning Server Agent of an Image for more information.

5. Run the image —r command from the control plane server.

   This command releases the farm you created with the image —p command. Releasing the farm includes the following:

   • Taking a snapshot of the image. The snapshot serves as the new image you have just created.

   • Releasing the resource pool server to the resource pool.

   • Updating the N1 Provisioning Server database with a reference to the image.

   image -r -f farm_ID [-S image_size] -i image_name

   For example:

   image -r -f 171 -S 9050849280 -i image_name

   The value of the farm-ID option is the ID of the farm you created using the image —p command in step 3.

6. Delete the farm by typing:

   farm -Df farm-ID

Upgrading the N1 Provisioning Server Agent of an Image

You can upgrade the monitoring software of an image at any time.

To Upgrade the N1 Provisioning Server Agent Package of an Image

Steps

1. Use TFTP to get the agent package from the control plane server.

   ---

   Note –

   If you are running the JumpStart post installation script postinstall.sh, skip this step.

   ---

   cd var/tmp tftp>cp tftp>binary tftp>get TSPRagsol.pkg Received 456704 bytes in 0.4 seconds tftp>quit

2. Type the command pkgrm old-package-name.

3. Type the command pkgadd -d new-package-name.

Importing Images

The N1 Provisioning Server supports importing preconfigured and manually created image from the command line.

To Import Preconfigured Images

Use the image -c command to import preconfigured images. The -c option creates a server image entry in the database.

Before You Begin

Ensure that the image contents are accessible on an NFS-shared directory on the image server.

Ensure that enough storage is available on the N1 Provisioning Server or, if you are using a separate server for storing images, on the image server.

Preconfigured images are packaged with the N1 Provisioning Server agent and other configurations. Do not use the -n option with the image -c command because it will set the image to a non-deployable state.

Step

1. Type image -c

Example 3–5 Importing an Image

image -c -s -L nfs://3001/image/s9u5-img -S 4096M -A sun4ublade 
-o solaris s9u5-js 'Solaris 9 update 5 jumpstart for sparc blades' 

In the example, an image is created and imported with the name s9u5-img, the size 4096MB, located at device 3001 in the directory path /images/s9u5-js. The image is for the sun4ublade architecture.

To Import JumpStart Images

Steps

1. Set up the JumpStart server.

   See Creating the JumpStart Setup.

2. Customize the boot and configuration JumpStart servers.

   See Customizing the JumpStart Boot and Configuration Server.

3. Use the following command to import the JumpStart environment into the N1 Provisioning Server environment:

   image -c -s -n -L nfs://3001/images/jumpstart -S image size -A sun4ublade -O solaris -T jumpstart -P /images/jumpstart/dhcp-options.txt sun4ublade-js-image "*description*"

   Example:

   image -c -s -n -L nfs://3001//images/jumpstart-3 -S 1 -A sun4ublade -O solaris -T jumpstart -P dhcp-options.txt solaris-jumpstart-validate-img "Jumpstart validation desc" Created server image: 92

   ---

   Note –

   The image locator URL must be unique. The -n option is required.

   ---

   This operation will create a new image in a non-deployable state. You need to validate the image before you can deploy the image to a farm.

Validating Images

To Validate a Solaris JumpStart Image

Validating an image puts the image in a deployable state.

Steps

1. Import the JumpStart image as described in Importing Images.

2. Customize the boot and configuration JumpStart servers as described in Customizing the JumpStart Boot and Configuration Server.

3. Obtain a list of images by using the image -ls command.

4. Use the following command to validate the image:

   image -C -i image_name server_type disk_type controller_type disk_size

   Example:

   image -C -i solaris-jumpstart-validate-img sunfireb100s-95-blade local ide 3004789248

   The following shows the output of the image -l command before image validation:

   image -l IMAGE_ID IMAGE_NAME CUSTOMER SIZE OS TYPE STATE 3 sw@50150 __grid__ 19809 disk_image READY 92 solaris-jumpstart-validate-img __grid__ 1 solarisjumpstart NOT READY LOCATION nfs://3001//images/jumpstart-3

   The following shows the output of the image -l command after image validation:

   image -l IMAGE_ID IMAGE_NAME CUSTOMER SIZE OS TYPE STATE 92 solaris-jumpstart-validate-img __grid__ 1 solarisjumpstart READY LOCATION nfs://3001//images/jumpstart-3

Listing Images from the Command Line

The image command provides several options for listing images from the command line:

• Listing all images in the image repository — image -l -a

• Listing images available for use— image -l -y

• Listing images marked as deleted— image -l -R

• Listing global images only — image -l

• Listing images of a specific account — image -lv customer-name

• Listing detailed information of images of a specific account — image -lV customer-name

• Listing a single image by specifying the image ID — image -lv image-ID

• Listing detailed information about single image by specifying its ID — image -lV image-ID

To List all Images in the Image Repository

Step

1. Type image -l at the command line.

   Example output:

   IMAGE_ID IMAGE_NAME CUSTOMER SIZE OS TYPE STATE 7 solaris9u5-sun4ublade-flash __grid__ 28000000000 solaris flash READY LOCATION: nfs://3001//images/master-images/solaris9u5-sun4ublade-flash 8 solaris9u5-i86pc-flash __grid__ 30000000000 solaris flash READY LOCATION: nfs://3001//images/master-images/solaris9u5-i86pc-flash 9 js-x86-test-img __grid__ 30000000000 solaris jumpstart READY LOCATION: nfs://3001/images/jumpstartx-GA 10 sw@50150 __grid__ 19807 disk_image READY 11 js-sparc-test-img __grid__ 30000000000 solaris jumpstart READY LOCATION: nfs://3001/images/jumpstarts-GA 13 s9u5-x86-disk-jstest-img __grid__ 30000000000 unknown disk_image READY LOCATION: nfs://3001/images/master-images/s9u5-x86-disk-jstest-img 16 s9u5-jumpstart-test __grid__ 30000000000 solaris jumpstart READY LOCATION: nfs://3001/images/jumpstart

To List a Single Image by Specifying its ID

Step

1. Type image -lv image-ID at the command line.

   Example output:

   IMAGE_ID IMAGE_NAME CUSTOMER SIZE OS TYPE STATE 13 s9u5-x86-disk-jstest-img __grid__ 30000000000 unknown disk_image READY LOCATION: nfs://3001/images/master-images/s9u5-x86-disk-jstest-img Description: s9u5-x86-disk-jstest-img Architecture: i86pc Last Updated: 2004-02-09 13:48:19.0 Image Locations: ID STATE SIZE LOCATION 58 done 699981071

To List Detailed Information about a Single Image by Specifying its ID

Step

1. Type image -lV image-ID at the command line.

   Example output for a flash archive image:

   IMAGE_ID IMAGE_NAME CUSTOMER SIZE OS TYPE STATE 7 solaris9u5-sun4ublade-flash __grid__ 28000000000 solaris flash READY LOCATION: nfs://3001//images/master-images/solaris9u5-sun4ublade-flash Description: solaris9u5-sun4ublade-flash Architecture: sun4ublade Last Updated: 2004-02-09 13:52:26.0 Image Locations: ID STATE SIZE LOCATION 7 done 759291924 nfs://3001//images/master-images/solaris9u5-sun4ublade-flash Image Contents: =============================================== partitioning explicit filesys any free /

   Example output for a JumpStart image:

   IMAGE_ID IMAGE_NAME CUSTOMER SIZE OS TYPE STATE 9 js-x86-test-img __grid__ 30000000000 solaris jumpstart READY LOCATION: nfs://3001/images/jumpstartx-GA Description: Testing validation of image Architecture: i86pc Last Updated: 2004-02-08 10:25:28.0 Image Locations: ID STATE SIZE LOCATION 9 done 512 nfs://3001/images/jumpstartx-GA Image Contents: =============================================== SinstNM 10.42.42.1 SinstIP4 10.42.42.1 SinstPTH /images/s9u5x SrootNM 10.42.42.1 SrootIP4 10.42.42.1 SrootPTH /images/s9u5x/Solaris_9/Tools/Boot SsysidCF 10.42.42.1:/images/jumpstartx-GA SjumpsCF 10.42.42.1:/images/jumpstartx-GA BootFile nbp.SUNW.i86pc SbootURI tftp://10.42.42.1/SUNW.i86pc

Updating Image Attributes from the Command Line

If you upgrade an image, the image attributes should reflect any upgrades you have made.

With the image -u command, you can update the following attributes:

• Image name

• Image size

• Architecture

• Operating environment

• Image description

• Archive type

• Image configuration file

Command usage: image -u -N image name -S image size -A architecture- O operating sytem -U image description -T image archive type -P configuration file image ID

For any image, except for a disk image, if you specify the -T option, you must also specify the -P option.

Example 3–6 image -u Command

image -u -S 3000000000 101

You can specify a new disk layout for a global flash image using the image -u command. You can view the default disk layout in the output of the image -lV command:

image -lV 16
IMAGE_ID IMAGE_NAME                   CUSTOMER  SIZE       OS       TYPE   STATE    
16       solaris9u5-sun4ublade-flash  __grid__  3200000000 solaris  flash  READY    
LOCATON:  nfs://3001//images/master-images/solaris9u5-sun4ublade-flash

Description:   solaris9 update 5 flash image for sun4ublade with Cassini NIC
Architecture:  sun4ublade
Last Updated:  2004-02-13 23:35:53.0

Image Locations:
    ID    STATE     SIZE             LOCATION
    16    done      759291924        
nfs://3001//images/master-images/solaris9u5-sun4ublade-flash
Image Contents: 
===============================================
partitioning explicit
filesys any free /

===============================================

Create a new layout file with the following contents:

/var/tmp/newdisklayout.sun4ublade
partitioning explicit 
filesys any 8096 / 
filesys any free /export 

Then run the command:

image -u -P /var/tmp/newdisklayout.sun4ublade 16 
Updated image: 16  
image -lV 16 
IMAGE_ID IMAGE_NAME                   CUSTOMER  SIZE       OS       TYPE   STATE   
16       solaris9u5-sun4ublade-flash  __grid__  3200000000 solaris  flash   READY    
LOCATION: nfs://3001//images/master-images/solaris9u5-sun4ublade-flash  

Description:   solaris9 update 5 flash image for sun4ublade with Cassini NIC 
Architecture:  sun4ublade 
Last Updated:  2004-02-13 23:35:53.0  

Image Locations:    
ID    STATE     SIZE      LOCATION     
16    done      759291924  nfs://3001//images/master-images/solaris9u5-sun4ublade-flash 
Image Contents:  
=============================================== 
partitioning explicit 
filesys any 8096 / 
filesys any free /export  
===============================================

To Update Image Attributes from the Command Line

Steps

1. Obtain a list of the images using the command:

   image -ls IMAGE_ID IMAGE_NAME CUSTOMER DISK_VOL_ID SIZE OS 2 solaris __grid__ 22001/5 8631 Solaris 1087 solaris_dhcpfix __grid__ 22001/22 8631 Solaris

2. Run the image -u command with the options of the attributes you want to update.

   image -l 22 IMAGE_ID IMAGE_NAME CUSTOMER SIZE OS TYPE STATE 22 js-sample __grid__ 30000000000 unknown disk_image NOT READY LOCATION: nfs://3001/images/master-images/js-sample image -u -S 40000000000 22 Updated image: 22 image -l 22 IMAGE_ID IMAGE_NAME CUSTOMER SIZE OS TYPE STATE 22 js-sample __grid__ 40000000000 unknown disk_image NOT READY LOCATION: nfs://3001/images/master-images/js-sample

Deleting Images

When you delete snapshots and images from the Control Center, they are only marked as deleted; they are not yet deleted from the image server and the I-Fabric. Until you delete them from the image server and the I-Fabric, you will not be able to create snapshots and images with the same names as the ones marked as deleted.

To purge snapshots and images from the image server and the I-Fabric, type the image -lR command from the control plane server to view a list of the images marked as deleted, then execute the image -d command to delete them from the I-Fabric.

To Delete Images

Steps

1. Obtain a list of the images using the image command:

   image-ls

   Example output when listing images:

   IMAGE_ID IMAGE_NAME CUSTOMER SIZE OS STATE 1 solaris8-blade-3001 __grid__ 3004789248 solaris8 READY LOCATION: nfs://3001//images/master-images/solaris8-blade 2 solaris8-blade-3002 __grid__ 3004789248 solaris8 READY LOCATION: nfs://3002//images/master-images/solaris8-blade 3 solaris8-blade-3003 __grid__ 3004789248 solaris8 READY nfs://3003//images/master-images/solaris8-blade

2. Type one of the following commands to delete the image:

   image -d {-s | customer_name} [-L URL] name

   image -d [-L URL] image ID

   For example:

   image -d -s js-sample-new Delete system image js-sample-new (y/n)? y Queueing request to delete image ... Request (id: 1633) submitted. Waiting for request 1633 to complete... . Deleting image content at: nfs://3001/images/master-images/js-sample size: 0 ip: 10.2.2.1 State: created

   The image -d command deletes an image from the image server and removes the entry for that image from the CPDB. It also scrubs and frees the disk. You then use the Administration dialog of the Control Center to synchronize the Control Center with the CPDB. See the N1 Provisioning Server 3.1, Blades Edition, Control Center Management Guide for details.

Creating Account Images Using the Control Center

You can create custom application and data software images using the tools available in the Control Center. Typical operations include creating, deploying, updating, and replacing application+data images, and operating environment+application+data images. You can use the Control Center for managing account images. See theN1 Provisioning Server 3.1, Blades Edition, Control Center Management Guide for details on how to create and deploy account images.

Alternatively, you can use the snapshot command-line tool available on the N1 Provisioning Server to take a snapshot of an existing disk for account image creation. See the snapshot man pages for details.

Creating the JumpStart Setup

This section describes how to set up JumpStart for SPARC and x 86 architectures. This section also provides details on how to customize the JumpStart configuration and boot server for SPARC and x86 architectures. Procedures for customizing a resource pool server manually are also included.

To Create the JumpStart Setup for SPARC Architecture

The following procedure only provides the information on JumpStart setup required in the context of the N1 Provisioning Server environment. For details on JumpStart setup see the documentation for Solaris 9. You can set up a JumpStart installation server in several ways. The following procedure is only one example.

Steps

1. Logon to the image server as superuser.

2. Insert the Solaris 9 DVD on the image server.

3. Create a directory to contain the DVD image.

   Example:

   mkdir -p /images/s9u5s

   ---

   Note –

   This document assumes the Solaris distribution is available at /images/s9u5s (for SPARC) and /images/s9u5x (for x86).

   ---

4. Change to the Tools directory on the mounted disc.

   Example:

   cd /cdrom/cdrom0/s0/Solaris_9/Tools

5. Copy the DVD image in the drive to the installation server's hard disk.

   Example:

   ./setup_install_server /images/s9u5s

6. Verify that the path to the installation server's image is shared appropriately.

   share | grep /images/s9u5s

   ---

   Note –

   If the path is displayed and anon=0 is displayed in the options, proceed to the next step. If the path is not displayed or you do not have anon=0 in the options, continue with this step.

   ---

   1. Make the installation server available to the boot server by adding this entry to the /etc/dfs/dfstab file.

      share -F nfs -o rw,anon=0 -d "install server directory" /images/s9u5s

   2. Make sure the installation server's directory path is correctly shared.

      ps -ef | grep nfsd

      If the nfsd daemon is not running, start it.

      /etc/init.d/nfs.server start

      If the nfsd daemon is running, share the installation server.

      shareall

7. Change directories to root by typing cd /.

8. Eject the Solaris 9 DVD.

To Create the JumpStart Setup for the x86 Architecture

Steps

1. Use the Solaris 9 x86 DVD the /images/s9u5x directory to hold the Solaris 9 distribution.

2. Follow the instructions given above for SPARC architecture to create a Solaris x86 installation server , but instead of /images/s9u5s use the/images/s9u5x path.

3. Patch the miniroot shipped with Solaris 9 12/03 x86 for the drivers for Sun Fire B100x, Sun Fire B200x. See the Sun Fire B1600 Chassis, and B100s, B100x, and B200x Blade Product Notes and the section Applying Mandatory Software Patches to the Solaris x86 Install Image for patching details.

4. On the image server create the following directory:

   mkdir -m 755 /var/tmp/blades

5. Download the software by following the instructions in section Solaris x86 Drivers and Documentation of the Sun Fire B1600 Chassis, and B100s, B100x, and B200x Blade Product Notes.

6. Save the downloaded file to the directory /var/tmp/blades.

7. At the Solaris prompt on the system you are going to use as the network installation server, unzip the files you have downloaded:

   cd /var/tmp/blades unzip mis.259-4174-11.zip

8. Change to the directory in which you placed mis.259-4174-11.zip by typing:

   cd /var/tmp/blades

9. Add the patches and packages automatically to the network installation server image by typing:

   ./modify_install_server -d /images/s9u5x

Customizing the JumpStart Boot and Configuration Server

This section describes how to set up and customize the JumpStart boot and configuration server on SPARC and x86 architectures. The JumpStart environment ensures that all the required software is installed on the resource pool server. This section describes customization of the JumpStart boot and configuration server on SPARC and x86 architectures.

If you have specific JumpStart customizations you must merge the scripts provided for N1 Provisioning Server with your customizations. The following example procedures for customizing the JumpStart boot and configuration server for SPARC and x 86 architectures set up a JumpStart environment that uses DHCP.

To Customize the Boot and Configuration Server for the SPARC Architecture

Steps

1. Create the JumpStart directory on image server.

   Example:

   mkdir -p /images/jumpstart-sparc

2. Verify that the path to the JumpStart directory is shared appropriately by typing:

   share | grep /images/jumpstart-sparc

   If the path is displayed and anon=0 is displayed in the options, proceed to the next step. If the path is not displayed or you do not have anon=0 in the options, continue with this step.

   1. Make the JumpStart directory NFS shared by adding the following entry to the /etc/dfs/dfstab file.

      share -F nfs -o anon=0,rw=@10.42.42.0/24 -d "jumpstart server directory sparc" /images/jumpstart-sparc

   2. Make sure the JumpStart server's directory path is correctly shared.

      ps -ef | grep nfsd

      If the nfsd daemon is not running, start it by typing /etc/init.d/nfs.server start.

      If the nfsd daemon is running, share the JumpStart server by typing shareall.

3. Use the following two scripts to customize the JumpStart begin and postinstallation for N1 Provisioning Server and copy them to the JumpStart directory:

   cp /tftpboot/terraspring/jumpstart/profiles/begin_js.sh /images/jumpstart-sparc cp /tftpboot/terraspring/jumpstart/profiles/postinstall.sh /images/jumpstart-sparc

   See Customizing the Resource Pool Server Manually if you intend not to use the above two scripts to customize your JumpStart environment.

   ---

   Note –

   If you do not have your own specific begin or postinstallation scripts skip to step 4.

   ---

   ---

   Note –

   If you have your own specific begin or postinstallation scripts incorporate the begin_js.sh functionality in your begin scripts and postinstall.sh functionality into your postinstallation scripts.

   ---

4. Create the following files with the following content for each file:

   cat /images/jumpstart-sparc/profile.sparc

   install_type initial_install cluster SUNWCXall partitioning explicit filesys any free /

   cat /images/jumpstart-sparc/rules

   arch sparc begin_js.sh profile.sparc postinstall.sh

   cat /images/jumpstart-sparc/sysidcfg

   system_locale=en US timezone=US/Pacific timerserver=localhost terminal=xterm name_service=NONE security_policy=NONE root_password=WPUDTTMUiG2JI network_interface=primary { default_route=10.42.42.1 netmask=255.255.255.0 protocol_ipv6==no }

5. Make any other specific JumpStart customizations that you might want to have. See the Solaris 9 12/03 Installation Guide for details on how a JumpStart server can be configured.

6. Validate the files using the check script.

   cd /images/jumpstart-sparc /images/s9u5s/Solaris_9/Misc/jumpstart_sample/check

7. Ensure that you profile access to the resource pool server through rsh by issuing the following commands:

   cd /image/9su5s/Solaris_9/Tools/Boot echo "+" > .rhosts

8. Ensure that a proper boot environment is setup for the platform name and group by issuing the following command:

   add_install_client -d -s Solaris-install-server-ip-address:Solaris-product-directory -c JumpStart-server-ip-address:JumpStart-directory -p Jumpstart-Configuration-server-ip-address:Jumpstart-Configuration-directory platform_name platform_group

   ---

   Note –

   See the add_install_client -d -s for details.

   ---

   1. When you install the N1 Provisioning Server software, you specify the image subnet. So when using the N1 Provisioning Server as your JumpStart server, use the IP address on the image subnet. To determine what image IP address the N1 Provisioning Server is using, run the command ifconfig -a to get a list of interfaces and their IP addresses. Look for the IP address that is on the image subnet.

      Example:

      /images/s9u5s/Solaris_9/Tools/add_install_client -d -s 10.42.42.1:/images/s9u5s -c 10.42.42.1:/images/jumpstart-sparc -p 10.42.42.1:/images/jumpstart-sparc SUNW.Serverblade1 sun4u

      ---

      Note –

      Each time you run add_install_client you are changing the boot file used for booting hardware of the specified platform_name and platform_group. The resource pool server will boot from the boot file that was setup by the last add_install_client command.

      ---

9. The image command supports the following set of DHCP options:

   • SrootOpt

   • SrootIP4

   • SrootNM

   • SrootPTH

   • SswapIP4

   • SswapPTH

   • SbootFIL

   • Stz

   • SbootRS

   • SinstIP4

   • SinstNM

   • SinstPTH

   • SsysidCF

   • SjumpsCF

   • Sterm

   See the Preconfiguring System Configuration Information section of the Solaris 9 12/03 Installation Guide for more information on the DHCP options.

   Following are the contents of the DHCP options file for the example JumpStart configuration created in this procedure:

   cat dhcp-options.txt SinstNM 10.42.42.1 SinstPTH /image/s9u5s SrootNM 10.42.42.1 SinstIP4M 10.42.42.1 SinstPTH /images/s9u5/Solaris_9/Tools/Boot SsysidCF 10.42.42.1:/images/jumpstart SjumpsCFF 10.42.42.1:/images/jumpstart

   ---

   Note –

   The image server IP address is used for the root server, installation server, and JumpStart configuration.

   ---

To Customize the Boot and Configuration Server for the x86 Architecture

Steps

1. Create the JumpStart directory on image server.

   Example:

   mkdir -p /images/jumpstart-x86

2. Verify that the path to the JumpStart directory is shared appropriately by typing:

   share | grep /images/jumpstart-x86

   If the path is displayed and anon=0 is displayed in the options, proceed to the next step. If the path is not displayed or you do not have anon=0 in the options, continue with this step.

   1. Make the JumpStart directory NFS shared by adding the following entry to the /etc/dfs/dfstab file.

      share -F nfs -o anon=0,rw=@10.42.42.0/24 -d "jumpstart server directory x86" /images/jumpstart-x86

   2. Make sure the JumpStart server's directory path is correctly shared.

      ps -ef | grep nfsd

      If the nfsd daemon is not running, start it by typing /etc/init.d/nfs.server start.

      If the nfsd daemon is running, share the JumpStart server by typing shareall.

3. Use the following two scripts to customize the JumpStart begin and postinstallation for N1 Provisioning Server and copy them to the JumpStart directory:

   cp /tftpboot/terraspring/jumpstart/profiles/begin_js.sh /images/jumpstart-x86 cp /tftpboot/terraspring/jumpstart/profiles/postinstall.sh /images/jumpstart-x86

   See Customizing the Resource Pool Server Manually if you intend not to use the above two scripts to customize your JumpStart environment.

   ---

   Note –

   If you do not have your own specific begin or postinstallation scripts skip to step 4.

   ---

   ---

   Note –

   If you have your own specific begin or postinstallation scripts incorporate the begin_js.sh functionality in your begin scripts and postinstall.sh functionality into your postinstallation scripts.

   ---

4. Create the following files with the following content for each file:

   cat /images/jumpstart-x86/profile.x86

   install_type initial_install cluster SUNWCXall partitioning explicit filesys any free /

   cat /images/jumpstart-x86/rules

   arch i386 begin_js.sh profile.x86 postinstall.sh

   cat /images/jumpstart-x86/sysidcfg

   system_locale=en US timezone=US/Pacific timerserver=localhost terminal=dtterm keyboard=UNKNOWN display=UNKOWN pointer=UNKNOWN monitor=UNKNOWN { DisplayChksum=0x0 } root_password=WPUDTTMUiG2JI name_service=NONE security_policy=NONE network_interface=PRIMARY { default_route=10.42.42.1 netmask=255.255.255.0 protocol_ipv6==no }

5. Make any other specific JumpStart customizations that you might want to have. See the Solaris 9 12/03 Installation Guidefor details on how a JumpStart server can be configured.

6. Validate the files using the check script.

   ---

   Note –

   Run the check command from the same Solaris distribution.

   ---

   cd /images/jumpstart-x86 s9u5x/images/s9u5x/Solaris_9/Misc/jumpstart_sample/check

7. Ensure that you profile access to the resource pool server through rsh by issuing the following commands:

   cd /image/s9u5s/Solaris_9/Tools/Boot echo "+" > .rhosts

8. Ensure that a proper boot environment is setup for the platform name and group by issuing the following command:

   add_install_client -d -s Solaris-install-server-ip-address:Solaris-product-directory -c JumpStart-server-ip-address:JumpStart-directory -p Jumpstart-Configuration-server-ip-address:Jumpstart-Configuration-directory platform_name platform_group

   ---

   Note –

   See the add_install_client -d -s for details.

   ---

   1. When you install the N1 Provisioning Server software, you specify the image subnet. So when using the N1 Provisioning Server as your JumpStart server, use the IP address on the image subnet. To determine what image IP address the N1 Provisioning Server is using, run the command ifconfig -a to get a list of interfaces and their IP addresses. Look for the IP address that is on the image subnet.

      Example:

      /images/s9u5x/Solaris_9/Tools/add_install_client -d -s 10.42.42.1:/s9u5x/images/s9u5x -c 10.42.42.1:/images/jumpstart-x86 -p 10.42.42.1:/images/jumpstart-x86 SUNW.i86pc i86pc

      ---

      Note –

      Each time you run add_install_client you are changing the boot file used for booting hardware of the specified platform_name and platform_group. The resource pool server will boot from the boot file that was setup by the last add_install_client command.

      ---

9. The image command supports the following set of DHCP options:

   • SrootOpt

   • SrootIP4

   • SrootNM

   • SrootPTH

   • SswapIP4

   • SswapPTH

   • SbootFIL

   • Stz

   • SbootRS

   • SinstIP4

   • SinstNM

   • SinstPTH

   • SsysidCF

   • SjumpsCF

   • Sterm

   • BootFile

   • SbootURI

   See the Preconfiguring System Configuration Information section of the Solaris 9 12/03 Installation Guide for more information on the DHCP options.

   The following is a sample DHCP options file for the example JumpStart configuration created in this procedure.

   cat dhcp-options.txt SinstNM 10.42.42.1 SinstPTH /image/s9u5x SrootNM 10.42.42.1 SinstIP4M 10.42.42.1 SinstPTH /images/s9u5x/Solaris_9/Tools/Boot SsysidCF 10.42.42.1:/images/jumpstart-x86 SjumpsCFF 10.42.42.1:/images/jumpstart-x86 BootFile nbp.SUNW.i86pc SSbootURI tftp://10.42.42.1/SUNW.i86pc

   ---

   Note –

   The image server IP address is used for the root server, installation server, and JumpStart configuration.

   ---

Customizing the Resource Pool Server Manually

This section describes how to manually customize the resource pool server.

To Customize the Resource Pool Server Manually

Steps

1. Manually complete the JumpStart installation and configure the Solaris image according to the instructions in the Solaris documentation and the following steps.

   1. Enable the DHCP on its primary interface (the default).

      1. Create the /etc/hostname.interface-identifier file for the primary interface:

         For example:

         /etc/hostname.ce0

         This file should be empty.

      2. Create the /etc/dhcp.interface-identifier file for the primary interface.

         This file should contain a single line that reads wait forever primary. Do not disable the default icmp ping operation on the primary interface from the N1 Provisioning Server software. The monitoring software performs anicmp ping operation on the primary interface to check whether a device is running.

      3. Create the following file for each additional interface, excluding the loopback interface:

         /etc/dhcp.<interface_identifier>

         Each of these files should contain a single line that reads wait 60.

      4. If the image is for a Solaris device with more than two interfaces, also create the following file for each nonprimary and nonloopback interface:

         /etc/hostname.interface_identifier

         These files should be empty.

   2. Change the last line of /etc/default/dhcpagent from:

      PARAM_REQUEST_LIST=1,3,12,43

      to

      PARAM_REQUEST_LIST=1,3,6,12,15,43

      If the image is for a Solaris device with more than two interfaces (excluding the loopback interface), also make the following modification to the /etc/default/dhcpagent file:

      Uncomment the parameter value pair “RELEASE_ON_SIGTERM=yes”.

   3. Delete all *.dhc files in the /etc/dhcp/ directory.

   4. Enable FTP.

      Although by default FTP is enabled, the following is how to enable FTP:

      1. Uncomment the line in the /etc/inetd.d. file that reads:

         ftpstream tcp6 nowait root /usr/sbin/n.ftpd n.ftpd

      2. To determine the ID of the net daemon, type the command:

         ps -ef | grep inetd

      3. Type the command:

         kill -HUP net_pid

      4. Ensure that root is not in the /etc/ftpusers file.

   5. Verify that the Java 2 Platform, Standard Edition, on the resource pool server is version 1.4.1_02.

      ---

      Note –

      For installation of Solaris 8, include a workaround for Solaris 8 bug No. 4457119. The recommended fix is to create the file /etc/rcS.d/S99dhcpfix with the following contents:

      # # Name: /etc/rcS.d/S99dhcpfix # # Author: Chris Morton # Ericsson, Inc. # (919) 472-6494 # # This is here to fix a bug in Solaris DHCP It will remove any lines # in /etc/inet/hosts that DHCP added, so the # /sbin/netstrategy program will return the correct values. HOSTSFILE=/etc/inet/hosts TEMPHOSTFILE=/tmp/hosts.$$ case "$1" in "start") echo "N1"s Standard DHCP Environment" ;; # Fall through -- rest of script is the initialization code "stop") exit 0 ;; *) echo "Usage: $0 { start | stop }" exit 1 ;; esac # What's my hostname?: hostname=`/sbin/dhcpinfo Hostnamè if [ -z "$hostname" ]; then hostname="unknown" fi # What's my IpAddress ipaddress=`ifconfig ce0 | grep inet | awk '{print $2}'` # If you can find my hostname anywhere in /etc/inet/hosts, delete that line. /usr/bin/rm -f ${TEMPHOSTFILE} /usr/bin/egrep -v "[ ]${hostname}([ ]|$)" ${HOSTSFILE} > ${TEMPHOSTFILE} 2> /dev/null # Add a line based on the actuals echo "${ipaddress} ${hostname} ${TEMPHOSTFILE} /usr/bin/cp -p ${TEMPHOSTFILE} ${HOSTSFILE} /usr/bin/rm -f ${TEMPHOSTFILE}

      ---

   6. Verify that the symbolic link /usr/java points to the directory where the Java 2 Platform is installed.

   7. Reboot the server.

2. Copy the N1 Provisioning Server agent package from the N1 Provisioning Server software to the tftboot directory on the N1 Provisioning Server for installation on the image.

   ---

   Note –

   If you are running the JumpStart post installation script postinstall.sh, skip this step.

   ---

3. Use TFTP to get the agent package from the control plane server.

   ---

   Note –

   If you are running the JumpStart post installation script postinstall.sh, skip this step.

   ---

   cd var/tmp tftp>cp tftp>binary tftp>get TSPRagsol.pkg Received 456704 bytes in 0.4 seconds tftp>quit

4. Manually install the monitoring software package by typing the following command:

   pkgadd -d TSPRagsol.pkg

   ---

   Note –

   If you are running the JumpStart post installation script postinstall.sh, skip this step.

   ---

   ---

   Note –

   Run the command pkginfo | grep package_name to ensure that you have installed the following operating environment packages:

   SUNWbzip SUNWbzipx SUNWzip

   SUNWgzip SUNWtcsh SUNWscpux

   ---

5. Run the following command to start the monitoring software:

   /etc/init.d/N1PSagt start