test

Sun N1 System Manager 1.2 Installation and Configuration Guide

Chapter 2 Upgrading the Sun N1 System Manager Software and Provisionable Server Management Agents

This chapter provides the procedures for upgrading your N1 System Manager 1.1 management server to N1 System Manager 1.2, and for upgrading the provisionable server OS management agents to version 1.2.

The following topics are discussed:

Upgrading to Sun N1 System Manager 1.2

This section provides the procedure for upgrading N1 System Manager 1.1 on the management server to N1 System Manager 1.2, and the procedure for configuring the ALOM email alerts

The following topics are discussed:

ProcedureTo Upgrade the Sun N1 System Manager Software

Before You Begin

Back up your N1 System Manager 1.1 installation as described in Backing Up and Restoring N1 System Manager Database and Configuration Files in Sun N1 System Manager 1.2 Administration Guide.

Steps

  1. Log in as root to the N1 System Manager management server.

  2. Stop all N1 System Manager processes.

    Type /etc/init.d/n1sminit stop in a terminal window. Wait for the message N1 services stopped to appear before continuing.

  3. Change directory to the N1 System Manager installation source.

    If you are installing from the N1 System Manager DVD, change directory as follows.

    • Solaris SPARC-based management server: 


      # cd /cdrom/n1_system_mngr/Solaris_sparc/Product/installer

    • Solaris x86-based management server:


      # cd /cdrom/n1_system_mngr/Solaris_x86/Product/installer

    • Linux x86-based management server:


      # cd /cdrom/n1_system_mngr/Linux_x86/Product/installer

    If you are installing from an N1 System Manager installation ISO image, substitute your mount point directory name for /cdrom in the path names.

  4. Type ./install -u to start the upgrade installation process

    The Software Evaluation Agreement appears.

  5. Choose whether to accept the agreement and continue installation.

    Read the agreement carefully. Type y to continue installation, or type n to exit the installation.

    When you continue the upgrade, the upgrade script checks for required Perl modules. When this process completes, the upgrade process then checks the component versions on the management server against the application versions in the N1 System Manager 1.2 installation media. The N1SM Installer upgrade menu then appears, listing which components are up to date, and for which components an upgrade is available.

    The appearance of the N1SM Upgrade menu, and the list of components to be upgraded depends on the operating system installed on the management server as shown by the following examples.

    • Solaris 10 Based Management Server


                N1SM Upgrade (version 1.1 to 1.2 on SunOS)

 1. Install IPMI tool.                            [Upgrade Available]
 2. Install JDK 1.5.                              [Up To Date]
 3. Install service provisioning components.      [Up To Date]
 4. Install OS provisioning components.           [Upgrade Available]
 5. Install user interface components.            [Upgrade Available]
 6. Install service container components.         [Upgrade Available]
 7. Install N1 System Manager.                    [Upgrade Available]


Non-interactive install in progress

Executing current step:  Install OS packages...

    • Linux Based Management Server


                      N1SM Upgrade (version 1.1 to 1.2 on Linux)

 1. Install IPMI tool.                            [Upgrade Available]
 2. Install JDK 1.5.                              [Up To Date]
 3. Install Python.                               [Up To Date]
 4. Install service provisioning components.      [Up To Date]
 5. Install OS provisioning components.           [Upgrade Available]
 6. Install user interface components.            [Upgrade Available]
 7. Install service container components.         [Upgrade Available]
 8. Install N1 System Manager.                    [Upgrade Available]


Non-interactive upgrade in progress.

Executing current step:  Install IPMI tool...

    The installation process runs each step in sequence. When a step completes successfully, the status of the step is changed to [Up to Date].

    If a step fails, you are notified, and the status remains [Upgrade Available] or is changed to [Partially Run]. Exit the installation process and examine the log file /var/tmp/installer.log.latest to determine the cause of the failure. Correct the problem and then run the upgrade process again.

    When the upgrade process completes, all running N1 System Manager processes are stopped and restarted, and then you are informed that the N1SM upgrade process is complete. The following messages are then displayed:


    Please use "n1smconfig -A" to configure email alerts for ALOM and to
configure your management interface.
 
 
Please use "/opt/sun/n1gc/bin/agentupgrade" to upgrade the agents on
provisionable servers with OS deployments.
bash-3.00#

    The installation process then exits.

Next Steps

Configure the ALOM email alert settings as described next in To Configure the ALOM Email Alert Settings.

ProcedureTo Configure the ALOM Email Alert Settings

Steps

  1. Log in as root to the N1 System Manager management server.

  2. Configure the ALOM email alert settings by typing n1smconfig -A.

    You are notified that proper settings are required to send email alerts, and the existing values are displayed. You are then asked whether to modify the email alert settings.

  3. Choose whether to modify the email alert settings.

    • Type n to accept the displayed settings. The email alert configuration process exits to the system prompt.

    • Type y to modify the email alert configuration.

      You are prompted for the email alert user name.

  4. Specify the email alert user name.

    Type the account name that you provided in To Configure the System Files and Account for the Mail Service in Sun N1 System Manager 1.2 Site Preparation Guide.

    For example: n1smadmin

    You are prompted for the email alert folder.

  5. Specify the email folder in which the email alerts are to be stored.

    Type the name of an email folder for the alert account, for example, inbox

    You are prompted for the email protocol

  6. Specify the email alert protocol.

    Type the name of the email protocol used by the management server. Valid entries are pop3 or imap.

    You are prompted for the email alert user account password.

  7. Type the password for the email alert user account.

    Type the password that you provided in To Configure the System Files and Account for the Mail Service in Sun N1 System Manager 1.2 Site Preparation Guide.

    You are prompted for the email alert user account email address.

  8. Type the user account email address.

    For example: n1smadmin@company.com

    You are prompted for the IP address of the email server.

  9. Specify the IP address of the email server.

    • If you have installed and enabled an email server on the management server, type the IP address of the management server management network interface.

    • If you have installed and enabled an email server on a different machine that is accessible by the management server management network interface, type the IP address of that machine.

    The values you have specified are displayed, and you are asked whether you want to use the values.

  10. Choose whether to accept the displayed email alert settings.

    • Type n if the settings are not correct. The ALOM email alert settings process is restarted, and you are prompted to specify the email alert user name.

    • Type y to use the displayed email alert settings.

      The settings are displayed again, and you are asked whether you want to apply the settings.

      Type y to apply the settings, or type n to exit to the command prompt.

Next Steps

Update the provisionable server OS management agents to version 1.2 as described next in Upgrading the Provisionable Server OS Management Agents.

Troubleshooting

For problem resolution procedures, see Chapter 4, Troubleshooting in this guide, and see Chapter 6, Troubleshooting, in Sun N1 System Manager 1.2 Administration Guide.

Upgrading the Provisionable Server OS Management Agents

This section provides the procedure for upgrading provisionable server version 1.1 OS management agents to version 1.2.

The agentupgrade command can be used to upgrade the OS management agent on all provisionable servers, a group of servers, provisionable servers running a specific operating system, a specific group of provisionable servers based on the server model, or a specific server.

Note –

N1 System Manager 1.1 does not support sun4v servers such as the Sun Fire T1000 and T2000. Therefore, any Solaris s10s-hw2-04 or s10s-hw2-05 distributions that you created using N1 System Manager 1.1 do not contain the files required to support the Sun Fire T1000, T2000, and other sun4v servers.

To support the Sun Fire T1000, T2000, and other sun4v servers in N1 System Manager 1.2, you must recreate the distributions after running agentupgrade and then redeploy the distribution to the provisionable servers.

The agentupgrade syntax is as follows:

Usage: agentupgrade [--debug] [--role <role>]
        (--all|<servers>|--group <group>|[--f_ip <ip>] [--f_runningos <os>]
        [--f_jobcount (0|1)] [--f_model <model>] [--f_name <name>])

        --debug    Show additional status information
        --role     Specify session role for execution

        --all      All healthy, powered on servers
        <servers>  List of space separated servers
        --group    Group name
        --f_*      Filter on property

The following agentupgrade parameters are exclusive. Only one of the parameters can be specified when running agentupgrade.

The following parameters can be used with the above exclusive parameters.

The following procedure illustrates an OS monitoring agent upgrade of all healthy provisionable servers.

ProcedureTo Upgrade the Provisionable Server OS Management Agents

Steps

  1. Ensure all provisionable servers that are to be updated are online and healthy.

    1. Open a browser window and log in to the N1 System Manager.

    2. Check the status of the provisionable servers and server groups.

    3. Resolve any problems noted before going to the next step.

      See Chapter 4, Managing Servers and Server Groups, in Sun N1 System Manager 1.2 Administration Guide and Chapter 5, Monitoring Your Servers, in Sun N1 System Manager 1.2 Administration Guide.

  2. Log in as root to the N1 System Manager management server.

  3. Upgrade the provisionable server monitoring agents by typing /opt/sun/n1gc/bin/agentupgrade --all.

    The agent upgrade process is sequential, and can take a long time if you have a large number of provisionable servers. As each provisionable server is updated, a status message is displayed that provides information about whether the agent update succeeded.

    The output generated by the agentupgrade command is sent to stdout. If a provisionable server OS management agent cannot be updated, information about the failure is written to stdout, and the agentupgrade process continues.

    You can also update the OS management agent on provisionable servers using the N1 System Manager browser. For more information, see Adding and Upgrading Base Management and OS Monitoring Features in Sun N1 System Manager 1.2 Administration Guide for procedures for updating provisionable servers. SeeTo Upgrade the OS Monitoring Feature on a Server in Sun N1 System Manager 1.2 Administration Guide for specific procedures for updating the OS management agents on provisionable servers.