test

Sun N1 System Manager 1.2 Administration Guide

Chapter 3 Provisioning Operating Systems, OS Updates, and Firmware Updates

This chapter describes how to manage the aggregate installation of operating systems, OS updates, and firmware updates.

The N1 System Manager enables you to perform the management tasks in the following sections:

Introduction to OS Provisioning

This section provides an overview of the OS provisioning process and supported OS types. This section includes the following:

OS Provisioning Command Overview

The N1 System Manager enables you to provision hundreds of heterogeneous servers using one interface. The N1–ok shell provides a simple command set with which to provision and reprovision servers.

The OS provisioning process consists of the following high-level steps:

  1. Copying an OS image to the management server.

  2. (Optional) Creating a custom OS profile. Default OS profiles are created automatically when OS distributions are copied.

  3. Installing an OS profile on a server or a server group.

To import an OS image, use the create os command with the cdrom or file attribute. For example:


N1–ok> create os os file files

The Create OS job uses the location of the OS media or files to import the image and save it on the management server. You can view the job results to track the process.

After successful completion of the Create OS job, an image or distribution is identified by its name. The same name is used for the default OS profile. To view the available OS profiles, use the show osprofile command and the all attribute. For example:


N1–ok> show osprofile all

Provision individual servers and groups of servers by using the load server command with the group attribute, and the osprofile parameter and the required values. For example:


N1–ok> load server server osprofile osprofile networktype networktype
Tip –

The N1 System Manager browser interface provides an OS profile wizard and drag-and-drop installation of groups of servers to limit the complexity of OS provisioning. The wizard builds commands to help you learn the syntax and provides default settings to enable efficient configuration of common parameters. See To Access the N1 System Manager Browser Interface for login instructions. Refer to the N1 System Manager online help for wizard instructions.

Reprovision servers and server groups with a new OS profile by running the load command on servers or server groups that have previously been provisioned.

The following graphic illustrates the OS provisioning process.

This graphic illustrates the seven detailed steps required to provision operating systems.

The following list provides links to the tasks that are illustrated in the graphic.

Supported Operating Systems on Provisionable Servers

The following tables provide the complete list of operating systems that can be installed and are supported on the provisionable servers with the N1 System Manager.

Note –

Solaris 9 OS on x86 platform distributions require the application of two updates from a separate patch server if your management server is running Linux. See To Patch a Solaris 9 OS Distribution by Using a Solaris 9 OS on x86 Patch Server for detailed instructions on how to create a valid Solaris 9 OS on x86 platform distribution. These patches are necessary for the N1 System Manager to be able to provision Solaris OS 9 update 7 and below. This procedure is not required for Solaris OS 9 update 8 and above.

Provisionable server hardware and operating software requirements for the N1 System Manager are listed in the following tables.

Table 3–1 SPARC-Based Provisionable Server Hardware and Operating System Requirements

Type 

Management Port Type 

Provisionable OS 

Disk Space Requirements 

RAM Requirements 

Sun Netra 240 and 440 

ALOM 

Solaris 10 GA and later 

Solaris 9 Update 7 and Update 8 

12 Gbytes minimum for all provisionable servers 

512 Mbytes minimum, 1-Gbyte recommended for all provisionable servers 

Sun Fire V210, V240, and V440 

ALOM 

Solaris 10 GA and later 

Solaris 9 Update 7 and Update 8 

Sun Fire T1000 and T2000 

ALOM 

Solaris 10 HW2 and later 

Table 3–2 x86–Based Provisionable Server Hardware and Operating System Requirements

Type 

Management Port Type 

Provisionable OS 

Disk Space Requirements 

RAM Requirements 

Sun Fire X2100 with the 8081A IPMI 1.5 Remote Management Card: Part Number: 371-0743 

SP 

Solaris x86 Version 10 HW1 and later 

Red Hat Enterprise Linux 3.0 WS, ES, and AS Update 5, 32–bit and 64–bit 

Red Hat Enterprise Linux 4.0 WS, ES, and AS update 1, 32–bit and 64–bit 

SUSE Linux Professional 9.2, 64–bit only 

SUSE Linux Professional 9.3, 64–bit only 

12 Gbytes minimum for all  

512 Mbytes minimum, 1-Gbyte recommended 

Sun Fire X4100 and X4200 

ILOM 

Solaris x86 Version 10 HW1 and later 

Red Hat Enterprise Linux 3.0 WS, ES, and AS Update 5, 32–bit and 64–bit 

Red Hat Enterprise Linux 4.0 WS, ES, and AS update 1, 64–bit only 

SUSE Linux Enterprise Server 9 SP1, 64–bit only 

Sun Fire V20z and V40z 

SP 

Solaris x86 Version 10 and later 

Solaris x86 Version 9 update 7 and update 8 

Red Hat Enterprise Linux 3.0 WS, ES, and AS, Updates 1 through 5 for 32–bit only 

Red Hat Enterprise Linux 3.0 WS, ES, and AS, Updates 3 through 5, 64-bit only 

Red Hat Enterprise Linux 4.0 WS, ES, and AS, 64-bit only 

Red Hat Enterprise Linux 4.0 WS, ES, and AS update 1, 32–bit and 64-bit 

SUSE Linux Enterprise Server 9, 32–bit and 64–bit 

SUSE Linux Enterprise Server 9 SP1, 32–bit and 64–bit 

SUSE Linux Professional 9.2 , 32–bit and 64–bit 

SUSE Linux Professional 9.3, 32–bit and 64–bit 

Provisioning the Solaris 10 Operating System

This section provides instructions for provisioning the Solaris 10 OS by using the browser interface or the command line. See To Provision the Solaris 10 OS. This procedure familiarizes you with the provisioning process and the most reliable method for performing aggregate server installations at any skill level.

The example that follows the procedure provides the command-line equivalents for provisioning the Solaris 10 OS. The command-line interface is the most efficient method for performing aggregate installations for more experienced system administrators.

ProcedureTo Provision the Solaris 10 OS

Before You Begin
Steps

  1. Copy the Solaris 10 OS ISO file to the management server.


    N1-ok> create os os file file-location
    Note –

    This operation is CPU intensive and might take several minutes to complete.

    A default OS profile is created on the management server. To view the list of OS profiles, type show osprofile all.

    See To Copy an OS Distribution From ISO Files or To Copy an OS Distribution From CDs or a DVD for more information.

  2. (Optional) Set up a flash archive file on the management server.

    See To Copy a Flash Archive to the Management Server.

  3. (Optional) Create a custom post-installation script to configure the bge1 data network interface when the server boots. Save the file on the management server.

    The following sample script configures the provisionable server's bge1 data network interface at system boot using the data network DHCP server.


    cat << EOF > /etc/sysconfig/network-scripts/ifcfg-eth1DEVICE=bge1
BOOTPROTO=dhcp
ONBOOT=yesEOF

  4. (Optional) Customize the default OS profile so that it uses a flash archive and a post-installation script.


    N1-ok> set osprofile osprofile flar flar

    The flar attribute value is the full path and flash archive file name, for example, /jumpstart/Flash/archive1.flar.


    N1-ok> add osprofile osprofile script script type type

    The script attribute value is the full path and script file name, for example, /etc/sysconfig/network-scripts/ifcfg-bge1.

    The type attribute specifies the time when the custom script will run during the installation. Valid values for the type attribute are:

    • pre – Run the script before the installation (for example, drivers).

    • post – Run the script after the installation.

    • postnochroot – Run the script after the installation. The script does not have to be run as superuser (root).

    The OS profile is modified to use the designated post-installation script and the flash archive file.

  5. Show the drag-and-drop OS profile icon on the Dashboard tab.

    1. Click the Edit List button beneath the OS Profiles list.

      The list of available OS profiles appears.

    2. Select the relevant check box and click OK.

      The selected OS profile is added to the Shortcuts pane.

  6. (Optional) Connect to the serial console of the provisionable server.

    1. Choose All Servers from the View Selector menu.

      The Servers table appears.

    2. Select the server for which you want to launch a serial console.

      The Server Details page appears.

    3. Choose Open Serial Console from the Actions menu.

      The serial emulator appears.

  7. Choose Servers By Group from the View Selector menu.

    The Server Groups table appears.

  8. Drag and drop the OS profile icon from the Shortcuts pane to a server group.

    The Load OS Profile wizard appears. Use the wizard steps to guide you through the screens.

  9. To begin loading the OS profile on the selected servers, click the Finish button in the final step of the wizard.

    The wizard window closes and a job number appears in the Command Line pane.

  10. Track the OS profile installation by using any of the following methods:

    • View the Serial Console window output from Step 5.

    • Click the Jobs tab to view the OS Load job, and click the Job ID for details.

    • Click the Event Log tab to view any events generated by the job.

Example 3–1 Provisioning the Solaris 10 OS Through the Command Line

For the following example, assume that you have created a Solaris 10 OS on x86 platform flash archive file named archive1.flar and that you have created a post-installation script called ifcfg-bge1. Your management server is also assumed to be running the Solaris 10 OS on x86 platform software.

The following example shows how to copy an OS distribution from the /tmp/solarisdvd.iso file.


N1-ok> create os solaris_ver10 file /tmp/solarisdvd.iso
Job "1" started.

The following example shows how to add a line to the /etc/dfs/dfstab file, below the last comment, which creates the /jumpstart/Flash directory.


# vi /etc/dfs/dfstab


# Put custom additions below (Do not change/remove this line)
share -F nfs -o ro,anon=0 -d "Flash Share" /jumpstart/Flash

The following example shows how to copy the flash archive to the /jumpstart/Flash directory.


# cp /tmp/archive1.flar /jumpstart/Flash/

The following example shows how to restart NFS.


# /etc/init.d/nfs.server stop
# /etc/init.d/nfs.server start

The following example shows how to create an OS profile that uses the flash archive.


N1-ok> create osprofile solaris_ver10 rootpassword admin flar /jumpstart/Flash/archive1.flar
description "solaris 10with flar" os solx86
Job "2" started.

The following example shows how to add a swap partition to the OS profile.


N1-ok> add osprofile solaris_ver10 partition swap sizeoption fixed size 2048 
device c1t1d0s1 type swap

The following example shows how to add a root partition to the OS profile.


N1-ok> add osprofile solaris_ver10 partition / sizeoption free device 
c1t1d0s0 type ufs

The following example shows how to add a post-installation script to the OS profile.


N1-ok> add osprofile solaris_ver10 script 
/etc/sysconfig/network-scripts/ifcfg-bge1 type post

The following example shows how to load the OS profile on a server group with the name devgroup.


N1-ok> load group devgroup osprofile solaris_ver10 
excludeserver=192.168.73.205,192.168.73.31,192.168.73.14 
networktype=static ip=192.168.72.201-192.168.73.214
Job "3" started.

The excludeserver attribute shows how to exclude certain provisionable IP addresses from the load operation. The networktype attribute specifies the static IP range to assign to the provisioned servers.

The networktype attribute must be set to static for Solaris profile installations. See Table 3–4 and load server in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

The following example shows how to view the job status.


N1-ok> show job 3
Job ID:   3
Date:     2005-06-01T13:11:46-0600
Type:     OS Load
Status:   Completed (2005-06-01T13:11:59-0600)
Command: 	 load group devgroup osprofile solaris_ver10 
excludeserver=192.168.73.205,192.168.73.31,192.168.73.14 
networktype=static ip=192.168.72.201-192.168.73.214Owner:    root
Errors:   0
Warnings: 0
Troubleshooting
See Also
Next Steps

To Add the OS Monitoring Feature

Managing OS Distributions

This section describes the following tasks:

Copying OS Distributions and Flash Archives

Before you can install an OS profile on a provisionable server, you must copy an OS image. This copied image is called an OS distribution. You can copy an OS image from files that are located on the management server or from a network mounted file system. OS distributions are copied to the directories on the management server as follows:

Supported file types are:

Note –

The N1 System Manager does not support the copying of Solaris OS CDs and CD ISO files. You must copy a Solaris DVD or DVD ISO file.

Refer to Supported Operating Systems on Provisionable Servers for a detailed list of supported distributions for each provisionable server type.

To copy an OS distribution, use the create os command. Type help create os at the N1–ok command line for syntax and parameter details, or see create os in Sun N1 System Manager 1.2 Command Line Reference Manual. Refer to the following procedures for instructions about how to copy an OS distribution:

After you have copied an OS distribution, you can copy a flash archive file to the management server for use with a customized OS profile. Copying flash archives involves several manual steps, but it provides the most efficient method for loading OS distributions with the N1 System Manager. See To Copy a Flash Archive to the Management Server.

ProcedureTo Copy an OS Distribution From ISO Files

This procedure describes how to copy an OS distribution to the management server from a set of ISO files by using the command line.

Note –

After a distribution is copied, an OS profile of the same name is created by default. This profile appears in the OS Profiles list in the Shortcuts pane of the browser interface or by typing show osprofile all at the N1–ok> prompt.

Before You Begin
Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. Type the following command:


    N1-ok> create os os file file[,file...]

    Refer to create os in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

  3. Verify that the OS distribution was copied.


    N1-ok> show os all

    The OS distribution appears in the output.

Example 3–2 Creating an OS Distribution From a File

The following example shows how to create an OS distribution called solaris_ver9 from a single Solaris DVD ISO file.


N1-ok> create os solaris_ver9 file /tmp/solaris_9_dvd.iso
Job "7" started.
See Also

To find out how to load the OS distribution, see To Load an OS Profile on a Server or a Server Group.

ProcedureTo Copy a SUSE Linux Enterprise Server 9 SP1 OS Distribution from ISO Files

The following procedure describes how to copy the SLES 9 SP1 OS distribution to the management server.

Before You Begin

Move any file systems off of the /mnt mount point.

Steps

  1. Copy the SLES 9 distribution:


    # n1sh create os sles9u1 file
  /directory/SLES-9-i386-RC5-CD1.iso,/directory/SLES-9-i386-RC5-CD2.iso,
  /directory/SLES-9-i386-RC5-CD3.iso,/directory/SLES-9-i386-RC5-CD4.iso,
  /directory/SLES-9-i386-RC5-CD5.iso,/directory/SLES-9-i386-RC5-CD6.iso
    Note –

    Wait for the Create OS command to complete before going to the next step.

  2. Copy the SLES 9 Update 1 distribution:

    Note –

    The same OS profile name should be used when adding Update1.


    # n1sh create os sles9u1 file
  /directory/SLES-9-SP-1-i386-RC5-CD1.iso,directory/SLES9/SLES-9-SP-1-i386-RC5-CD2.iso,
  /directory/SLES-9-SP-1-i386-RC5-CD3.iso

  3. Verify that the OS distribution was copied.


    N1-ok> show os all

    The OS distribution appears in the output.

See Also

To find out how to load the OS distribution, see To Load an OS Profile on a Server or a Server Group.

ProcedureTo Copy an OS Distribution From CDs or a DVD

This procedure describes how to copy an OS distribution to the management server from CDs or a DVD by using the command line.

Note –

The N1 System Manager does not support the copying of Solaris OS CDs and CD ISO files. You must copy a Solaris DVD or DVD ISO file.

When copying an OS distribution from multiple installation CDs, you must run the create os command multiple times. For example, if you are copying an OS distribution that is provided on two CDs, you must insert the first CD, run the create os command, and wait for the job to complete. Once the first job completes, you must insert the second CD, run the create os command again, and wait for the job to complete. The OS distribution is successfully copied when the second job completes.

When copying the SUSE Linux Enterprise Server 9 SP1 distribution, you must run the create os command multiple times. First, copy the SLES 9 base distribution. When that job finishes, you can then copy the SLES 9 Update 1 distribution. A default OS profile is automatically created for each newly created OS distribution, with the same name as the OS distribution. The default profile is provided as an example. Most of the time, you will have to update the default profile to match your hardware or it may be easier to just create a new profile. Use the show osprofile osprofile command to see the configuration of an OS profile. The same OS profile name should be used when adding the Update 1 distribution.

Note –

After a distribution is copied, an OS profile of the same name is created by default. This profile appears in the OS Profiles list in the Shortcuts pane of the browser interface or by typing show osprofile all at the N1–ok> prompt.

Before You Begin

Move any file systems off of the /mnt mount point.

Steps

  1. Insert Disk 1 and type the following command:


    N1-ok> create os os cdrom cdrom

    A Create OS Distribution job is started. Note the job ID. When the job completes, insert the next disk. See create os in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

    Note –

    You are not prompted to insert the next disk, so you must track the Create OS Distribution job completion and the disk number for your OS. When the job completes, an event is generated.

  2. Insert Disk 2 and type the following command:


    N1-ok> create os os cdrom cdrom

  3. Continue with additional disks if needed.

  4. When the final Create OS Distribution job completes, type the following command:


    N1-ok> show os os

    The new OS distribution appears in the output.

Troubleshooting

Troubleshooting OS Distributions

Next Steps

To find out how to load the OS distribution by using an profile, see To Load an OS Profile on a Server or a Server Group.

ProcedureTo Copy a Flash Archive to the Management Server

This procedure describes how to set up and deploy a flash archive on a server or a server group by using the command line.

Before You Begin
Steps

  1. Log in to the management server as root.

    See To Access the N1 System Manager Command Line for details.

  2. Perform one of the following actions:

    • If your management server is running the Solaris Operating System, modify the /etc/dfs/dfstab file to add share -F nfs -o ro,anon=0 -d "Flash Share" /jumpstart/Flash below the last comment in the file.

      For example:


      # Put custom additions below (Do not change/remove this line)
share -F nfs -o ro,anon=0 -d "Flash Share" /jumpstart/Flash

    • If your management server is running Linux, modify the /etc/exports file to add /jumpstart/Flash *(ro,no_root_squash) below the last comment in the file.

      For example:


      # Put custom additions below (Do not change/remove this line)
/jumpstart/Flash      *(ro,no_root_squash)

  3. Copy the flash archive file to the /jumpstart/Flash directory.

  4. Perform one of the following actions to restart NFS:

    • If your management server is running the Solaris Operating System, type the following commands:


      # /etc/init.d/nfs.server stop
# /etc/init.d/nfs.server start

    • If your management server is running Linux, type the following commands:


      # /etc/init.d/nfs restart

      OR


      # /etc/rc3.d/S60nfs restart

  5. Create an OS profile that specifies the location of the flash archive file that you copied in Step 3.


    N1-ok> create osprofile osprofile os os rootpassword rootpassword flar flar 
description description language language timezone timezone

    The flar attribute value is the path and flash archive file name, for example, /jumpstart/Flash/archive1.flar.

    The OS profile is created.

  6. To verify the OS profile settings, type the following command:


    N1-ok> show osprofile osprofile

    The OS profile details appear. Check that the partition settings are appropriate for your business needs. See To Create an OS Profile for partition settings and examples.

  7. Load the OS profile on a server or a server group.

    See To Load an OS Profile on a Server or a Server Group.

Example 3–3 Deploying a Solaris 9 OS Flash Archive

The following example shows how to create an OS profile that uses a flash archive file.


N1-ok> create osprofile solaris9_flar rootpassword admin description "solaris 
9 with flar" os solx86 flar /jumpstart/Flash/S9-u7-req-v20z.archive

The following examples show how to add root and swap partitions to the OS profile.


N1-ok> add osprofile solaris9_flar partition / sizeoption free device 
c1t1d0s0 type ufs

N1-ok> add osprofile solaris9_flar partition swap sizeoption fixed size 128 
device c1t1d0s1 type swap

The following example shows how to deploy the modified OS profile to a server.


N1-ok> load server 192.168.73.2 osprofile 
solaris9_flar networktype=static ip=192.168.73.244

The networktype attribute specifies that the installed host is assigned the 192.168.73.244 IP address.

ProcedureTo Delete an OS Distribution

Note –

An OS distribution cannot be deleted if it is associated with a deployed OS profile. A deployed OS profile is a profile that is currently being installed on a provisionable server.

Before You Begin

Delete all of the OS profiles that are associated with the OS distribution. This process includes deleting the default OS profile that was created when the OS distribution was copied. An OS profile cannot be deleted while it is being deployed. You may remove it after the deployment is completed. See To Delete an OS Profile for instructions.

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. Type the following command:


    N1-ok> delete os os

    The distribution is deleted. See delete os in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

  3. View the available OS distributions.


    N1-ok> show os all

    The deleted OS distribution should not appear in the output.

Managing OS Profiles

This section describes the following tasks:

Creating, Listing, and Modifying OS Profiles

OS profiles specify the following information:

After you have copied an OS distribution, the N1 System Manager automatically creates an OS profile of the same name on the management server. This OS profile is also called a default OS profile. See Default OS Profiles for parameter settings and best practices for customizing OS profiles.

To view details of a default OS profile, use the show command with the osprofile keyword.

To create a new OS profile, use the create osprofile, add osprofile, and set osprofile commands. See Example 3–5 and Example 3–6 for command-line examples.

Default OS Profiles

When you copy an OS distribution, a default OS profile is automatically created for the OS distribution. The default profile is created for a typical Sun Fire V20z server, and it is mainly provided as an example. Settings for the default OS profiles are described in the following table.

Table 3–3 Default OS Profile Parameter Settings

Parameters 

Solaris OS 

Red Hat OS 

SUSE OS 

Root password 

admin

admin

admin

Language 

U.S. English 

U.S. English 

U.S. English 

Time zone 

Greenwich Mean Time (GMT) 

Greenwich Mean Time (GMT) 

Greenwich Mean Time (GMT) 

Partitions 

  • Root mount point ufs with a free file system size option on the c1t1d0s0 slice

  • swap mount point 2048-Mbyte swap on the c1t1d0s1 slice

  • Root mount point ext3 with a free file system size option on the sda slice

  • swap mount point 2048-Mbyte swap on the sda slice

  • Root mount point reiser with a free file system size option on the /dev/sda slice

  • swap mount point 2048-Mbyte swap on the /dev/sda slice

Distribution group 

Entire Distribution plus OEM support

Everything

Default Installation

Network Interfaces 

Provisioning interface configured 

Data interface not configured 

Provisioning interface configured 

Data interface not configured 

Provisioning interface configured 

Data interface not configured 

Best Practices for Modifying Default OS Profiles

To provision servers other than Sun Fire V20z servers, you need to modify the default profile, create a new OS profile, or clone an existing OS profile and customize the parameter settings. Each server at your site with different hardware and provisioning requirements requires the creation of a customized OS profile.

The browser interface provides a wizard for creating new OS profiles to limit the complexity of this operation. See To Create an OS Profile for instructions.

Some best practices for modifying default OS profiles are:

ProcedureTo List the Available OS Profiles

This procedure describes how to list the available OS profiles by using the browser interface. The example that follows the procedure provides the command-line equivalent.

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. Click the System Dashboard tab.

    The Shortcuts pane appears on the right side of the page.

  3. Click the Edit List button beneath the OS Profiles list.

    The list of available OS profiles appears.

Example 3–4 Listing Available OS Profiles Through the Command Line

The following example shows how to view all of the OS profiles in the system.


N1-ok> show osprofile all

All available OS profiles appear in the output. See show osprofile in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

ProcedureTo Create an OS Profile

This procedure describes how to use the browser interface's OS Profile wizard. The examples that follow the procedure provide command-line equivalents for creating and customizing OS profiles for the Solaris, Red Hat, and SUSE platforms.

Before You Begin

You must copy an OS distribution before you can create an OS profile. See To Copy an OS Distribution From CDs or a DVD or To Copy an OS Distribution From ISO Files.

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. Click the System Dashboard tab.

    The Shortcuts pane appears on the right side of the page.

  3. Click the New button beneath the OS Profiles list.

    The Create New Operating System Profile wizard appears.

  4. Use the wizard steps to guide you through the screens.

    Note –

    Click the Help tab in the left pane of the wizard for detailed information about the entry fields.

  5. To complete the creation of the OS profile, click the Finish button in the wizard.

    The wizard window closes.

  6. Click the Edit List button in the OS Profile Shortcuts.

    A dialog box appears.

  7. Select the check box for the OS profile and click the OK button.

    The drag-and-drop icon appears in the OS profiles Shortcuts list.

Example 3–5 Creating a Solaris OS Profile Through the Command Line

The following example illustrates the commands that are used to create an OS profile for a Solaris OS distribution. The first command creates a Solaris 10 profile that is named S10profile and sets the root password to admin.


N1-ok> create osprofile S10profile rootpassword admin 
description "S10 for host123" os solaris10

The following example command shows how to configure a swap partition with a size of 2048 Mbytes.


N1-ok> add osprofile s10profile partition swap size 2048 device c1t1d0s1 
type swap

The following example command shows how to configure a free ufs partition.


N1-ok> add osprofile s10profile partition / sizeoption free device c1t1ds0 
type ufs

The following example command shows how to add the default Solaris distribution group.


N1-ok> add osprofile s10profile distributiongroup "Entire Distribution 
plus OEM support"

OS profiles that install only the Core System Support distribution group cannot be monitored by using the OS monitoring feature.

Example 3–6 Creating a Red Hat OS Profile Through the Command Line

The following example illustrates the commands that are used to create an OS profile for a Red Hat distribution.


N1-ok> create osprofile RH30profile rootpassword admin 
os RedHat30

The following example command shows how to configure a root partition.


N1-ok> add osprofile RH30profile partition / device sda type ext3 
sizeoption free

The following example command shows how to configure a swap partition.


N1-ok> add osprofile RH30profile partition swap device sda type swap 
size 2048 sizeoption fixed

The following example command shows how to specify the distribution group.


N1-ok> add osprofile RH30profile distributiongroup "Everything"
Example 3–7 Creating a SUSE OS Profile Through the Command Line

The following example illustrates the commands that are used to create an OS profile for a SUSE distribution.


N1-ok> create osprofile default os suse rootpassword admin

The following example command shows how to configure a root partition.


N1-ok> add osprofile default partition / device /dev/sda type reiser 
sizeoption free

The following example command shows how to configure a swap partition.


N1-ok> add osprofile default partition swap device /dev/sda type swap 
size 2048 sizeoption fixed

The following example command shows how to specify the distribution group.


N1-ok> add osprofile default distributiongroup "Default Installation"
Troubleshooting
See Also

To find out how to load the OS profile, see To Load an OS Profile on a Server or a Server Group.

ProcedureTo Clone an Existing OS Profile

The following procedure describes how to clone or copy an existing OS profile. You might want to clone an existing OS profile if you need to modify it, but cannot do so because it is deployed. A deployed OS profile is a profile that is currently being installed on a provisionable server.

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. Type the following command:


    N1-ok> create osprofile osprofile clone oldprofile

    The new OS profile is created. See create osprofile in Sun N1 System Manager 1.2 Command Line Reference Manual

  3. Type the following command:


    N1-ok> show osprofile osprofile

    The new OS profile appears in the output.

See Also

To find out how to load the OS profile, see To Load an OS Profile on a Server or a Server Group.

ProcedureTo Modify an OS Profile

This procedure describes how to modify the scripts, partitions, updates, and distribution groups that are configured for an OS profile.

Note –

An OS profile that is currently being deployed cannot be modified.

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. Modify an OS profile by performing one of the following actions:

  3. View the new OS profile details.


    N1-ok> show osprofile osprofile

    The modified OS profile information appears in the output.

Example 3–8 Modifying an OS Profile Through the Command Line

This example shows how to use a flash archive and a post-installation script by modifying the solaris_ver10 OS profile.

For this example, assume that you have created the following script in a directory named /scripts on the management serverdirectory.

This sample script name is add_host.sh and the script adds a host to the /etc/hosts file on a provisionable server.


echo "129.10.12.101 myhost" >>/a/etc/hosts

Note that the root file system on the provisioned server is /a during the post installation time.

This example also assumes that you have created a flash archive file called archive1.flar and that you have completed the steps in To Copy a Flash Archive to the Management Server.

The following example shows how to add the script to the OS profile.


N1-ok> add osprofile solaris_ver10 script 
/scripts/add_host.sh type post

The following example shows how to set up the OS profile to use the flash archive.


N1-ok> set osprofile solaris_ver10 flar /jumpstart/Flash/archive1.flar
See Also

To find out how to load the modified OS profile, see To Load an OS Profile on a Server or a Server Group.

ProcedureTo Delete an OS Profile

An OS profile cannot be deleted if it is deployed. A profile is deployed if it is currently being installed on a provisionable server.

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. Type the following command:


    N1-ok> delete osprofile osprofile

    The OS profile is deleted from the management server.

  3. Type the following command:


    N1-ok> show osprofile all

    The deleted OS profile should not appear in the output.

Installing OS Distributions by Deploying OS Profiles

This section describes the following tasks:

Deploying OS Profiles

OS profile installations can be customized to fit your provisioning and network needs.

To deploy default or custom OS profiles, use the load command with the server or group keyword and the osprofile subcommand.

To add the base management and OS monitoring features that support updating and patching, use the feature attribute with the osmonitor value when you issue the load command. The feature attribute of the load command enables you to automatically configure monitoring when you load the OS profile.

For syntax and parameter details, type help load server, help load group, and help add server at the N1–ok command line.

Servers boot from their default network boot interface automatically as the final step of a load operation.

The following table provides a quick reference of all the parameters that are available for the load group and load server commands.

Note –

Before you attempt any Solaris OS on x86 platform deployments by using the N1 System Manager, you must ensure that the nameserver and search values are correctly configured at the operating system level on your management server. Otherwise, the installations will fail.

For more details, see the resolv.conf(5) man page. You need root user access on your management server to modify these settings.

Table 3–4 OS Profile Installation Parameters

Parameters 

Red Hat or SUSE OS 

Solaris OS 

Multiple Servers 

Single Server 

Notes 

bootip

√ (R) 

 

√ 

√ 

Also known as provisionable IP. 

ip

√ 

√ (R) 

√ 

√ 

Required if networktype is set to static.

networktype

√ (R) 

√ (R) 

√ 

√ 

Must be set to static for Solaris installation.

bootgateway

√ 

 

√ 

√ 

 

boothostname

√ 

   

√ 

 

bootnameserver

√ 

 

√ 

√ 

 

bootnetmask

√ 

 

√ 

√ 

Default is set to the provisioning network interface that is specified using the n1smconfig utility.

bootnetworkdevice

√ 

√ 

√ 

√ 

 

bootpath

 

√ 

 

√ 

 

console

√ 

√ 

 

√ 

 

consolebaud

√ 

√ 

 

√ 

 

kernelparameter

√ 

 

√ 

√ 

 

domainname

 

√ 

√ 

√ 

If domainname is not specified, a default will be configured

gateway

√ 

√ 

√ 

√ 

 

hostname

√ 

√ 

 

√ 

 

nameserver

√ 

√ 

√ 

√ 

 

netmask

√ 

√ 

√ 

√ 

Default is set to the provisioning network interface that is specified using the n1smconfig utility.

networkdevice

√ 

 

√ 

√ 

The Linux default is eth0. The Primary network interface is the default for Solaris installations.

(R) = Required 

√ = Configurable 

ProcedureTo Load an OS Profile on a Server or a Server Group

The following procedure describes how to load an OS profile on a server or a server group by using the browser interface. The examples that follow the procedure provide command-line equivalents.

Caution – Caution –

Uninstallation of an OS profile is not supported. However, you can reprovision a server by loading another OS profile on a server that is already provisioned.

Before You Begin
Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Browser Interface for details.

  2. (Optional) Modify the OS profile to use a flash archive and a post-installation script.


    N1-ok> set osprofile osprofile flar flar

    The flar attribute value is the full path and flash archive file name, for example, /jumpstart/Flash/archive1.flar.


    N1-ok> add osprofile osprofile script script type type

    The script attribute value is the full path and script file name, for example, /etc/sysconfig/network-scripts/ifcfg-eth1.

    The type attribute specifies the time when the custom script will run during the installation. Valid values for the type attribute are:

    • pre – Run the script before the installation (for example, drivers).

    • post – Run the script after the installation.

    • postnochroot – Run the script after the installation. The script does not have to be run as superuser (root).

    The OS profile is modified to use the designated post-installation script and the flash archive file.

  3. Navigate to the table that contains the server or the server group by performing one of the following actions:

    • Choose All Servers from the View Selector menu.

      The Servers table appears.

    • Choose Servers By Group from the View Selector menu.

      The Server Groups table appears.

  4. Drag and drop the OS profile icon from the Shortcuts pane to the server or the server group.

    The Load OS Profile wizard appears.

  5. Use the wizard steps to guide you through the screens.

    Note –

    Click the Help tab in the left pane of the wizard for detailed information about the entry fields.

  6. To begin loading the OS profile on the selected servers, click the Finish button in the wizard.

    The wizard window closes and a job ID appears in the Command Line pane.

  7. Click the Jobs tab.

    The Jobs table appears with information about your Load OS job.

    Note –

    The Load OS job will not complete until a final reboot occurs.

  8. Save the options that you used to load the OS profile as a note in case you need to restore the server sometime in the future.

    See Modifying Server and Server Group Information for details.

Example 3–9 Loading a Solaris OS Profile on a Server Through the Command Line

The following example shows you how to install a Solaris OS profile on a server by using the load command. The feature parameter specifies that the OS monitoring feature is installed. See Adding and Upgrading Base Management and OS Monitoring Features for details.


N1-ok> load server 192.168.8.9 osprofile S10profile 
networktype static ip 192.168.18.19 feature osmonitor agentssh root/rootpassword

The networktype attribute must be set to static for Solaris profile installations. See Table 3–4 and load server in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

Use the show job command to view the results.


N1-ok> show job target=192.168.8.9
Example 3–10 Loading a Solaris OS Profile on a Server Group Through the Command Line

The following example shows you how to install a Solaris OS profile on a server group by using the load command.


N1-ok> load group devgroup osprofile S10profile 
excludeserver=server1 networktype static ip 192.186.8.8-192.186.8.9
Job "14" started.

The networktype attribute must be set to static for Solaris profile installations. See Table 3–4 and load server in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

The following command shows you how to view the job results.


N1-ok> show job 14
Example 3–11 Loading a Linux OS Profile on a Server

The following example shows you how to install a Linux OS profile on a server by using the load command.


N1-ok> load server 192.168.8.9 osprofile RH3profile 
bootip 192.168.8.9 networktype dhcp

The bootip attribute is only used for Linux profile installations.

The following command shows you how to view the job results.


N1-ok> show job target=192.168.8.9

Setting the networktype attribute to DHCP means that the server uses DHCP to get its provisioning network IP address. If the system reboots, any added management features will break. In this case, use the set server agentip command to modify the server's agent IP address. See To Modify the Agent IP for a Server for more information.

Example 3–12 Loading a Linux OS Profile on a Server Group

The following example shows you how to install a Linux OS profile on a server group by using the load command.


N1-ok> load group devgroup osprofile RH3profile 
bootip 192.186.8.8-192.186.8.9 networktype dhcp
Job "15" started

The following command shows you how to view the job results.


N1-ok> show job 15

Setting the networktype attribute to DHCP means that the server uses DHCP to get its provisioning network IP address. If the system reboots, any added management features will break. In this case, use the set server agentip command to modify the server's agent IP address. See To Modify the Agent IP for a Server for more information.

Example 3–13 Loading a Red Hat Enterprise Linux 4 OS Profile on a Sun Fire X2100 Server

This example shows you how to load a Red Hat Enterprise Linux 4 OS profile onto a Sun Fire X2100 server using static IP network configuration.


N1-ok> load server server1 osprofile RHEL4profile bootip 192.168.8.8
networktype static ip 192.168.8.8 bootnetworkdevice eth1 networkdevice eth1

This example shows you how to load a Red Hat Enterprise Linux 4 OS profile onto a Sun Fire X2100 server using DHCP network configuration.


N1-ok> load server server34 osprofile rh4u1es-64-min bootip=10.0.101.34
networktype=dhcp bootnetworkdevice=eth1 networkdevice=eth1

The values bootnetworkdevice and networkdevice are only required for Red Hat Linux 4 on Sun Fire X2100 servers.

Example 3–14 Loading a Solaris 10 x86 OS Profile on a Sun Fire X2100 Server

When loading Solaris 10 x86 to a Sun Fire X2100 server , you need to first add a script to the profile. This script will disable the loading of the bge driver in /etc/system.

If your management server is running Linux, use the following command to add the script to the profile:


N1-ok> add osprofile profile_name script 
/opt/sun/scs/data/allstart/scripts/solaris_bge_disable.sh type=post

If your management server is running the Solaris OS, use the following command to add the script to the profile:


N1-ok> add osprofile profile_name script
/opt/SUNWscs/data/allstart/scripts/solaris_bge_disable.sh type=post

The service processor will become inaccessible while the machine is being provisioned.

Troubleshooting

If a value is not specified for the bootnetmask or netmask parameters during the load operation, the netmask will default to the provisioning network interface that is specified in the n1smconfig utility. See To Configure the N1 System Manager System in Sun N1 System Manager 1.2 Installation and Configuration Guide.

If the deployment fails, see the topics in OS Profile Deployment Failures for possible solutions.

Next Steps

To enable remote connectivity, OS resource monitoring, package deployment, and inventory management, you must add the OS monitoring feature on each server. See To Add the OS Monitoring Feature.

Managing Packages, Patches, and RPMs

The N1 System Manager enables you to perform following OS update management tasks:

The following graphic describes the order in which these tasks should be completed.

This graphic illustrates the steps to update an OS.

Introduction to Managing OS Updates

After you have installed an OS on a provisionable server, the N1 System Manager enables you to install OS updates. These OS updates consist of Solaris packages and patches and Linux RPMs.

For Solaris packages or patches, you can issue an optional parameter to install the updates by using a script. This parameter is useful for installation of a set of packages or patches that have dependencies. Use the create update command with the installscriptfile parameter to specify the script. See Example 3–16 for an example script and sample command syntax.

Installing OS updates on servers for the first time involves the following four-step process when you use the N1 System Manager:

  1. Downloading the OS update.

  2. Copying the OS update to the N1 System Manager

    The N1 System Manager must have system access to the OS update before the update can be installed on the provisionable servers.

    By using the create update command, you can import an OS update from a web site or an accessible file system on the management server. After an OS update is imported, you can display the update in the browser interface's Shortcuts pane, or you can use the show update command.

  3. Verifying that the OS update was copied by displaying the Shortcut in the browser interface or by using the show update command.

  4. Installing the OS update on the appropriate provisionable servers by using the browser interface or the load server or load group commands. The provisionable servers must have the base management feature supported.

OS update installations behave differently for every operating system because the native package installation mechanisms are used. For example, if a Solaris package is already installed on the target server, the installation might succeed without reporting an error. However, this same scenario for a Linux RPM results in an error message indicating that the package is already installed.

See OS Update Problems for troubleshooting information.

ProcedureTo Copy an OS Update

This procedure describes how to copy an OS update to the N1 System Manager. Once an OS update is copied, you can use the command line or the browser interface to install the OS update on a provisionable server.

The following graphic illustrates the use of the browser user interface for confirming that an OS update has been successful.

This graphic illustrates the two-step process used to create and verify a new OS update.
Before You Begin

Ensure that the OS update is available to the management server on the local file system, a network accessible file, or a web site. You can copy OS updates in the following formats:

Note –

The *.tar file must match the top-level directory name after the tar expansion. For example, if the tar file is SUNWstade.tar, the top-level directory of the tar expansion must be SUNWstade.

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. Copy the OS update to the N1 System Manager.


    N1-ok> create update update file file ostype ostype [adminfile adminfile]
[responsefile responsefile] [installscriptfile installscriptfile]

    Valid ostype values are in the following list:

    • redhat-es3 – Red Hat Enterprise Linux ES 3.0

    • redhat-ws3 – Red Hat Enterprise Linux WS 3.0

    • redhat-as3 – Red Hat Enterprise Linux, AS 3.0

    • redhat-as4 – Red Hat Enterprise Linux, AS 4.0

    • redhat-es4 – Red Hat Enterprise Linux, ES 4.0

    • redhat-ws4 – Red Hat Enterprise Linux, WS 4.0

    • redhat-es3-64 – Red Hat Enterprise Linux ES 3.0, 64-bit

    • redhat-ws3-64 – Red Hat Enterprise Linux WS 3.0, 64-bit

    • redhat-as3-64 – Red Hat Enterprise Linux, AS 3.0, 64-bit

    • redhat-as4-64 – Red Hat Enterprise Linux, AS 4.0, 64-bit

    • redhat-es4-64 – Red Hat Enterprise Linux, ES 4.0, 64-bit

    • redhat-ws4-64 – Red Hat Enterprise Linux, WS 4.0, 64-bit

    • solaris9x86 – Solaris x86 Version 9 Update 7

    • solaris10x86 – Solaris x86 Version 10

    • solaris9sparc – Solaris SPARC Version 9 Update 7

    • solaris10sparc – Solaris SPARC Version 10

    • suse-es9 – SUSE LINUX Enterprise Server 9

    • suse-es9-64 –SUSE LINUX Enterprise Server 9, 64-bit

    • suse-pro92 – SUSE Professional Edition 9.2

    • suse-pro92-64 – SUSE Professional Edition 9.2, 64-bit

    • suse-pro93 – SUSE Professional Edition 9.3

    • suse-pro93-64 – SUSE Professional Edition 9.3, 64-bit

    See create update in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

Example 3–15 Creating an OS Update Through the Command Line

The following example command shows how to create an OS update named RH3_update where the ostype is Red Hat Enterprise Linux, AS 3.0 and the location of the update file is /tmp/test-i386.rpm.


N1-ok> create update RH3_update file /tmp/test-i386.rpm ostype=redhat-as3
Example 3–16 Copying an OS Update With a Package Install Script Through the Command Line

This example shows an executable Bourne (/bin/sh) shell package installation script.

#!/bin/sh
echo "This is from the install script:"
echo "pkgadd -n -a /tmp/combo-pkgs.pkg.admin -d /tmp/combo-pkgs.pkg SUNWtest1 SUNWtest2"
pkgadd -n -a /tmp/combo-pkgs.pkg.admin -d /tmp/combo-pkgs.pkg SUNWtest1 SUNWtest2
exit $?

The following sample command shows how to associate the package installation script with the OS update files. This example assumes that you have copied the script to the management server's /tmp directory with the name install.sh.


N1-ok> create update combo file /tmp/combo-pkgs.pkg ostype solaris10x86 adminfile 
/tmp/combo-pkgs.pkg.admin installscriptfile /tmp/install.sh

In this example, /tmp/combo-pkgs.pkg contains two Solaris packages in the datastream format.

The script and the source files for the OS update are copied to the target server when the create os command is issued. The script file is executed by using the Bourne shell with the full path to the package file as the sole argument. If the adminfile subcommand is not specified, the default admin file is also copied to the target server and is renamed with .admin appended to the source file name.

Example 3–17 Copying an OS Update With a Patch Install Script Through the Command Line

This example shows an executable Bourne (/bin/sh) shell patch installation script.

As a best practice, any installation script that you use should create a new subdirectory, for example, in the /tmp directory. The script should then move or extract the OS update .tar file into that subdirectory. After the update is complete, the script should remove this subdirectory.

By default, the script executes in the invoker's home directory. In this case, this is the root directory. In addition, the installation script should refer to the full path to the package source files to avoid conflicts.

#!/bin/sh
mkdir /tmp/layer
cd /tmp/layer
echo "untar the source:"
tar -xvf /tmp/mypatches.tar
echo "let's install mypatches:"
patchadd -M /tmp/layer 117448-01 117466-01
exit $?

The following sample command shows how to associate the patch installation script with the OS update files. This example assumes that you have copied the script to the management server's /tmp directory with the name install.sh.


N1-ok> create update mypatches file /tmp/mypatches.tar ostype solaris10x86 installscriptfile 
/tmp/install.sh

In this example, /tmp/mypatches.tar contains the Solaris patches 117448–01 and 117466–01 in the datastream format.

The script and the source files for the OS update are copied to the target server when the create os command is issued. The script file is executed by using the Bourne shell with the full path to the package file as the sole argument.

Troubleshooting

If you use the installscriptfile parameter when creating an OS update, consider loading the OS update on a single server to test whether the script is working correctly before loading on a large server group.

Refer to OS Update Creation Failures for solutions to common errors.

See Also

To find out how to load an OS update, see To Load an OS Update on a Server or a Server Group

ProcedureTo Load an OS Update on a Server or a Server Group

This procedure describes how to load an OS update by using the browser interface. The example that follows the procedure provides a command-line equivalent.

The following default admin file is used to install Solaris packages:


mail=root
instance=unique
partial=nocheck
runlevel=nocheck
idepend=nocheck
rdepend=nocheck
space=quit
setuid=nocheck
conflict=nocheck
action=nocheck
basedir=default
authentication=nocheck

The admin file is located in the /opt/sun/n1gc/etc directory on the management server.

Before You Begin
Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Browser Interface for details.

  2. Navigate to the table that contains the server or the server group by performing one of the following actions:

    • Choose All Servers from the View Selector menu.

      The Servers table appears.

    • Choose Servers By Group from the View Selector menu.

      The Server Groups table appears.

  3. Drag and drop the OS update icon from the Shortcuts pane to the server or the server group.

    The Load OS Update confirmation dialog box appears.

  4. To begin loading the OS update on the selected servers, click the OK button.

    The dialog box closes.

  5. Click the Jobs tab.

    The Jobs table appears with information about your Load OS Update job.

  6. Verify that the installation was successful.


    N1-ok> show server server
Example 3–18 Loading an OS Update Through the Command Line

The following command shows you how to install an OS update on two servers by using the load command.


N1-ok> load server server1,server2 update SUNWn1gcsolsparcag

See load server in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

Example 3–19 Loading an OS Update on a Server Group Through the Command Line

The following command shows you how to install an OS update on a server group by using the load command.


N1-ok> load group devgroup update SUNWupdate1,SUNWupdate2

See load group in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

Troubleshooting

Solaris OS Update Deployment Failures

ProcedureTo List the Available OS Updates

This procedure describes how to list the available OS updates that have been copied to the N1 System Manager. These OS updates can be installed on a provisionable server.

The example that follows the procedure provides a command-line equivalent.

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Browser Interface for details.

  2. Click the System Dashboard tab.

    The Shortcuts pane appears.

  3. Click the Expand/Collapse icon on the Update title bar.

    The Update list expands.

  4. Click the Edit List button.

    The Edit List dialog box appears with the list of available updates.

Example 3–20 Listing Available OS Updates Through the Command Line

The following command shows you how to list all of the OS updates in the system.


N1-ok> show update all

ProcedureTo List the OS Updates Installed on a Provisionable Server

Tip –

You can also use the browser interface Server Details page to view all of the OS updates that are installed on a server.

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. List the OS updates that are installed on a provisionable server.


    N1-ok> show server server

    See show server in Sun N1 System Manager 1.2 Command Line Reference Manual for details

ProcedureTo Delete an OS Update

This procedure describes how to delete an OS update from the N1 System Manager. This procedure does not delete an OS update from a provisionable server. See To Uninstall an OS Update From a Provisionable Server for details on that specific task.

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. Delete an OS update from the N1 System Manager.


    N1-ok> delete update update

    See delete update in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

ProcedureTo Uninstall an OS Update From a Provisionable Server

Before You Begin
Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. Uninstall an OS update from a provisionable server.


    N1-ok> unload server server[,server...] update update
    Caution – Caution –

    If the user-specified update name is not found, the command tries to uninstall an OS update with a matching file name. The show update command enables you to list an OS update's corresponding file name.

    See unload server in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

Troubleshooting

If you cannot uninstall an OS update that was installed with an admin file, check that the package file name matches the name of the package. If the name is not the same, rename the admin file in the provisionable server's /tmp directory to match the name of the package and try the unload command again. If the package still exists, remove it from the provisionable server by using pkgrm.

See Also

OS Update Uninstallation Failures

ProcedureTo Uninstall an OS Update on a Server Group

Before You Begin
Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. Uninstall an OS update on the provisionable servers in a server group.


    N1-ok> unload group group update update
    Caution – Caution –

    If the user-specified update name is not found, the command tries to uninstall an OS update with a matching file name. Use the show update command to list an OS update's corresponding file name.

    See unload group in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

Managing Firmware SP, BIOS, and ALOM Updates

The N1 System Manager enables you to perform the following firmware management tasks:

Note –

Firmware updates to Sun Fire X2100 servers are not supported. Refer to Sun System Handbook documentation for the Sun Fire X2100 server for information about how to update firmware to the versions that are required for management by the Sun N1 System Manager. See Discovering Servers for the firmware versions required to discover a Sun Fire X2100 server.

The following graphic describes the order in which firmware management tasks must be performed.

This graphic illustrates the four steps to deploying a firmware update.

Introduction to Managing Firmware Updates

Updating the firmware on the provisionable servers is a primary administrative task. Installing a firmware update on a provisionable server for the first time involves the following four-step process when you use the N1 System Manager:

  1. Downloading and preparing the firmware update. Ensure that the firmware version matches those set out in Discovering Servers.

  2. Copying the firmware update to the N1 System Manager. The N1 System Manager must have system access to the firmware update before the firmware update can be installed on the provisionable servers.

    By using the create firmware command, you can copy a firmware update from a web site or an accessible file system on the management server. Once a firmware update is copied, you can display the firmware update in the browser interface Shortcuts pane, or you can use the show firmware command.

  3. Verifying that the firmware update was copied successfully by displaying the firmware Shortcut in the browser interface or by using the show firmware command.

  4. Installing the firmware update on the appropriate provisionable servers by using the browser interface, or by using the load server or load group command.

When importing firmware updates, you must specify the following metadata:

Note –

Firmware version 2.2 and above for the Sun Fire V20z servers do not support the PIC firmware upgrade. The upgrade of PIC firmware will fail, and the job step will show an error message similar to the following: “This operation is not supported on server. Refer to the log file for more information.”

ProcedureTo Copy a Firmware Update

This procedure describes how to copy a new firmware update to the N1 System Manager. Once a firmware update is copied, you can use the command line or the browser interface to install the firmware update on a provisionable server.

The following graphic illustrates the use of the browser interface to verify a firmware update.

This graphic illustrates the process to copy and verify a new firmware update.
Before You Begin

Ensure that the firmware update is available to the management server from the local file system, a network accessible file, or a web site.

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. Copy the firmware update.


    N1-ok> create firmware firmware url=url vendor=vendor model=model[,model...] [type type]
 [description description] [version version]

    The type attribute is required for Sun Fire V20z and V40z servers. Valid values for the type are BIOS and SP. All values are case-sensitive.

    See create firmware in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

  3. Verify that the firmware update was copied.


    N1-ok> show firmware firmware

    See show firmware in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

Example 3–21 To Copy an ALOM 1.5 Firmware Through the Command Line

The following example shows how to copy the ALOM 1.5 firmware images. There are two separate firmware images, but both can be associated with the ALOM type attribute value.


N1-ok> create firmware alom-boot type ALOM model SF-V240 vendor 
SUN url file:///var/tmp/alombootfw
N1-ok> create firmware alom-main type ALOM model SF-V240 vendor SUN 
url file:///var/tmp/alommainfw
N1-ok> show firmware
Name                       Type   Vendor      Version     Compatible Model
alom-boot                  ALOM   SUN                     SF-V240
alom-main                  ALOM   SUN                     SF-V240
See Also

ProcedureTo Load a Firmware Update on a Server or a Server Group

This procedure describes how to load a firmware update by using the browser interface. The examples that follow the procedure provide command-line equivalents.

Before You Begin
Note –

Firmware version 2.2 and above for the Sun Fire V20z servers do not support the PIC firmware upgrade. The upgrade of PIC firmware will fail, and the job step will show an error message similar to the following: “This operation is not supported on server. Refer to the log file for more information.”

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Browser Interface for details.

  2. Choose All Servers from the View Selector menu.

    The Servers table appears.

  3. Select the server or servers that you want to update.

    A check mark appears.

  4. Choose Load Firmware from the Actions menu.

    The Load Firmware dialog box appears

  5. Select the appropriate firmware from the Firmware menu.

  6. To apply the firmware update to the listed target servers, click OK.

    The dialog box closes.

  7. Click the Jobs tab.

    A Load Firmware job appears in the Jobs table.

  8. Click the job ID.

    The Job Details page appears. Job steps indicate progress and results. Review the information in the Results section of the Job Details page to determine which servers were successfully updated.

    Note –

    After successful completion, the firmware version number is updated with the actual version number that is reported by the hardware. If the reported version number does not match the original version number, a warning is logged.

  9. Verify that the installation was successful.


    N1-ok> show server server
Example 3–22 Loading Firmware on a Server Through the Command Line

The following example command shows you how to stop a server in preparation for installing a firmware update.


N1-ok> stop server server

The following example command shows you how to install a firmware update on a server by using the load command.


N1-ok> load server server1,server2 firmware v20z-bios.sp force true

See load server in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

By default, the firmware update's model and vendor settings must match every provisionable server that you select for installation; otherwise, the update fails. You can specify the force option to bypass this check. However, installing a noncompatible firmware update on a server might render the server unusable.

Example 3–23 Loading Firmware on a Server Group Through the Command Line

The following example command shows you how to stop a server group in preparation for installing a firmware update.


N1-ok> stop group group

The following example command shows you how to install a firmware update on a server group by using the load command.


N1-ok> load group devgroup firmware bios.sp

See load group in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

ProcedureTo List the Available Firmware Updates

This procedure describes how to list the available firmware updates by using the browser interface. The example that follow the procedure provides the command-line equivalent.

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Browser Interface for details.

  2. Click the System Dashboard tab.

    The Shortcuts pane appears.

  3. Click the Expand/Collapse icon on the Firmware title bar.

    The Firmware list expands.

  4. Click the Edit List button.

    The Edit List dialog box appears with the available firmware list.

Example 3–24 Listing the Available Firmware Updates Through the Command Line


N1-ok> show firmware all

ProcedureTo List the Firmware Updates Installed on a Provisionable Server

Tip –

You can also use the browser interface Server Details page to view all of the firmware updates that are installed on a server.

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. List the firmware updates that are installed on a provisionable server.


    N1-ok> show server server

    See show server in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

Example 3–25 Listing the Firmware for an ALOM Server

The following example shows how to view all of the firmware for an ALOM enabled server. You must log into the service processor before running this command.


showsc version -v
Advanced Lights Out Manager v1.5.3
SC Firmware version: 1.5.3
SC Bootmon version: 1.5.3
 
SC Bootmon Build Release: 02
SC bootmon checksum: 4F888E28
SC Bootmon built Jan  6 2005, 17:05:24
 
SC Build Release: 02
SC firmware checksum: 6FFB200D
 
SC firmware built Jan  6 2005, 17:05:12
SC firmware flashupdate MAY 25 2005, 01:33:55
 
SC System Memory Size: 8 MB
 
SC NVRAM Version = b
 
SC hardware type: 0

ProcedureTo Modify Firmware Update Information

This procedure describes how to modify the information about a firmware update.

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. Modify the name or description of a firmware update.


    N1-ok> set firmware firmware [description description] 
[name name] [model=model]
[vendor=vendor] [version=version]

    See set firmware in Sun N1 System Manager 1.2 Command Line Reference Manual for details.

ProcedureTo Delete a Firmware Update

This procedure describes how to delete a firmware update from the N1 System Manager. This procedure does not delete a firmware update from a provisionable server.

Note –

After you install a firmware update on a provisionable server, you cannot uninstall it.

Steps

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line for details.

  2. Delete a firmware update from the N1 System Manager.


    N1-ok> delete firmware firmware

    See delete firmware in Sun N1 System Manager 1.2 Command Line Reference Manual for details.