Installing the UNIX OS on Managed Servers

This section describes the following tasks:

• Deploying OS Profiles

• To Load an OS Profile on a Server or a Server Group

• To Initiate Network Boot Manually

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.

Most managed servers boot from their default network boot interface automatically as the final step of a load operation. However, you must boot manually any managed server that was discovered through the OS or manual discovery processes. The N1 System Manager is not able to boot automatically these systems from the network. See To Initiate Network Boot Manually for instructions.

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

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.

To 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. Although you can load an OS profile from the command-line interface, it is easier to load the profile from the browser interface. The examples that follow the procedure provide command-line equivalents.

You cannot uninstall an OS profile. However, you can reprovision a server by loading another OS profile on a server that is already provisioned.

Before You Begin

• Create an OS profile. See To Create an OS Profile.

• Disable monitoring for the servers that will be loaded with an OS profile. See To Disable Monitoring for a Managed Server or a Managed Server Group in Sun N1 System Manager 1.3 Discovery and Administration Guide for details. Disabling monitoring prevents the fault notifications that are generated if the server reboots after installation.

• Ensure that you have enough disk space available to load an OS profile.

• If you are loading a Red Hat 4 OS profile on a Sun Fire X2100 server or group of Sun Fire X2100 servers, see Example 2–16 for the required bootnetworkdevice and networkdevice attribute values.

• Optionally create and copy a flash archive file. See To Copy a Flash Archive to the Management Server.

• Optionally create and copy a post-installation script to the management server. See Step 4.

Steps

1. Log in to the N1 System Manager.

   See To Access the N1 System Manager Browser Interface in Sun N1 System Manager 1.3 Discovery and Administration Guide for details.

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

   N1-ok> set osprofile osprofile-name 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-name 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 (Red Hat Linux only) – 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 Task 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.

   When loading an OS profile on a managed server that was discovered through the OS or manual discovery processes, select the “Enable Manual Net Boot” option on the appropriate step in the wizard. The N1 System Manager is not able to boot these systems automatically from the network, and you must tell N1 System Manager to enable you to initiate the boot manually.

   ---

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 Managed Server and Group Information in Sun N1 System Manager 1.3 Discovery and Administration Guide for details.

Example 2–11 Loading a Solaris OS Profile on a Server Through the Command Line

The following command provides an example of the syntax for loading an OS profile and supporting the OS monitoring feature on a server. See Deploying OS Profiles for the complete list of available attributes and supported values.

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 in Sun N1 System Manager 1.3 Discovery and Administration Guide 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 2–2 and load server in Sun N1 System Manager 1.3 Command Line Reference Manual for details.

If the managed server to which you intend to install the OS was discovered manually or using OS-based discovery, add manualnetboot=”true” on the load command.

Use the show job command to view the results.

N1-ok> show job target=192.168.8.9

Example 2–12 Loading a Solaris OS Profile on a Server Group Through the Command Line

This example of load command syntax installs an OS profile on a group of servers, excluding specified servers with the excludeserver attribute. The SSH user account that is used in the add server feature command must have root privileges on the remote machine.

This command adds base management or OS monitoring feature support. See Adding and Upgrading Base Management and OS Monitoring Features in Sun N1 System Manager 1.3 Discovery and Administration Guide for detailed information about supported management features.

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 2–2 and load server in Sun N1 System Manager 1.3 Command Line Reference Manual for details.

The excludeserver=server1 option specifies that the OS profile is installed on all managed server within the devgroup server group except server1.

If the managed servers to which you intend to install the OS were discovered manually or using OS-based discovery, add manualnetboot=”true” on the load command.

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

N1-ok> show job 14

Example 2–13 Loading a Linux OS Profile on a Server Using a Static IP Address

The following command provides an example of the syntax for loading an OS profile and supporting the OS monitoring feature on a server. See Deploying OS Profiles for the complete list of available attributes and supported values.

The following example shows you how to install a Linux OS profile on a server. The feature parameter specifies that the OS monitoring feature is installed. See Adding and Upgrading Base Management and OS Monitoring Features in Sun N1 System Manager 1.3 Discovery and Administration Guide for details.

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

In this example, the networktype attribute is set to static. For an example that uses DHCP instead, see Example 2–15.

If the managed server to which you intend to install the OS was discovered manually or using OS-based discovery, add manualnetboot=”true” on the load command.

Use the show job command to view the results.

N1-ok> show job target=192.168.8.9

Example 2–14 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 
ip 192.186.77.1-192.186.77-2 bootip 192.186.8.8-192.186.8.9 networktype static
Job "15" started

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

N1-ok> show job 15

Example 2–15 Loading a Linux OS Profile on a Server Using DHCP

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.

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 in Sun N1 System Manager 1.3 Discovery and Administration Guide for more information.

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

N1-ok> show job target=192.168.8.9

Example 2–16 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 2–17 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 in Sun N1 System Manager 1.3 Installation and Configuration Guide.

If the deployment fails, see the topics in OS Distributions and Deployment in Sun N1 System Manager 1.3 Troubleshooting Guide 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 in Sun N1 System Manager 1.3 Discovery and Administration Guide.

To Initiate Network Boot Manually

Most managed servers boot from their default network boot interface automatically as the final step of a load operation. However, you must manually boot any managed server that was discovered through the OS or manual discovery processes. The N1 System Manager is not able to boot these systems automatically from the network.

This procedure describes the steps that are required to ensure that servers do not boot from their default network boot interface after a load operation. Once you follow these steps, you will need to manually boot the managed server when the load operation completes.

Steps

1. Access the N1 System Manager command line on the management server.

   See To Access the N1 System Manager Command Line in Sun N1 System Manager 1.3 Discovery and Administration Guide for details.

2. To install a given OS profile on a managed server and not boot that server automatically, set the manualnetboot option to true.

   For a single managed server, use the following form of the load server command with the manualnetboot option:

   N1-ok> load server server-name osprofile osprofile-name ip ip-address networktype static manualnetboot="true"

   For a group of managed servers, use the following form of the load group command:

   N1-ok> load group group-name osprofile osprofile-name ip ip-addresss networktype static manualnetboot="true"

   ---

   Tip –

   If you load the OS profile through the browser interface, check the “Enable Manual Net Boot” option in the wizard.

   ---