test

N1 Provisioning Server 3.1, Blades Edition, Installation Guide

Upgrading to N1 Provisioning Server Version 3.1

You can perform an upgrade of the N1 Provisioning Server software on an I-Fabric that contains live farms. The Provisioning Server software cannot be patched or upgraded when the Provisioning Server services are handling farm modification requests. Farm modification requests include farm activation, moving a farm to standby, farm snapshots, DHCP synchronization, and so on. If any requests are in progress when you start the upgrade, the upgrade process exits. You are prompted to wait for the requests to complete or to stop any requests before running the upgrade. Any requests in that are in the queue before the upgrade, may fail once the request is processed after the upgrade. Therefore, all queued requests should be deleted before upgrading.

Upgrading from N1 Provisioning Server version 3.0 to N1 Provisioning Server 3.1 requires that you perform the following tasks in sequence:

Refer to the release notes to get detailed information about the upgrade, such as the list of packages that are newer than the last release, or the list of new packages and any special instructions for the upgrade.

ProcedureTo Delete Queued Requests

Upgrades can only be performed while no requests are in progress or queued. The upgrade process verifies that no requests are in progress before starting the upgrade. However, for queued requests no such check is performed. You must check if there are any queued requests before starting the upgrade as described below. If you update N1 Provisioning Server software without deleting the queued and queued-blocked requests from the system, some of these requests may appear as failed or in error after the upgrade. You can delete the failed requests or choose to ignore them. For each request that was deleted before the upgrade or which appears as failed after the upgrade, you must reissue the request from the control center.

Steps

  1. Login in as root (su - root) on the control plane server.

  2. List queued and queued-blocked requests.

    Type opt/terraspring/sbin/request -l to list all queued and in-progress requests.

  3. Delete queued and queued-blocked requests.

    If there are any queued or queued-blocked requests. type the command /opt/terraspring/sbin/request -d request_id where request_id is the ID of the request. This must be done for each request listed by the request -l command.

ProcedureTo Upgrade from N1 Provisioning Server Version 3.0 to Version 3.1

Before You Begin

Make certain you have performed the following tasks before you start the upgrade process:

Steps

  1. Login in as root (su - root) on the control plane server.

  2. Insert the N1 Provisioning Server, Blades Edition version 3.1 DVD-ROM into the DVD-ROM drive.

  3. Type the command /cdrom/crom0/install to start the upgrade.

    The following messages appear.


    N1 Provisioning Server Software version 3.0 is already installed on
this system.
Continuing will upgrade to version 3.1.

Continue (y/N):

    Type y and press Return.

    • If you are upgrading a combined Provisioning Server and Image Server machine, the following messages appear.


      Upgrading Roles: PS IS
Continue (y/N):

    • If you are upgrading a Provisioning Server only machine, the following messages appear.


      Upgrading Roles: PS
Continue (y/N):

    Type y and press Return.

  4. You are prompted for the database administrator user name.

    Enter database administrator user [system]:

    Type the name of the database administrator user, or press Enter to accept the default system.

  5. You are prompted for the database administration password.

    Enter database administrator Password:

    Type the database administrator password. You are prompted to confirm the database administrator password. Retype the password.

  6. You are asked whether to enable flash permission.

    Do you want flash permission enabled?[y/n]

    To enable flash permission, type y. To disable flash permission, type n.

    Messages similar to the following appear.


    removing TSPRblibl package.
Parsing /tmp/Upgrade_24373__WML__ ...done!

Encrypting passwords ...done!Check for pending requests in progress ...done!
Configuration of Combined Provisioning and Image Server software and setup
in progress (Please wait) ...
Determining packages to upgrade/install ...removing TSPRblibl package.
Parsing /tmp/Upgrade_24373__WML__ ...done!

    The upgrade process then stops all Provisioning Server services, backs up the control center database, and then stops the domain. The upgrade process then removes old packages and upgrades the Provisioning Server packages, updates the control plane database and state, updates the control center database, and starts the Provisioning Server services.

    When the Provisioning Server services have started, the upgrade process configures the Provisioning Server settings, sets up the ignition operating system, and starts the control center. After the control center has started, the upgrade process tests each server blade.

See Also

When the server blade validation tests have completed, the upgrade process exits to the system prompt. You must now synchronize each chassis with the I-Fabric as directed by the next procedure, To Synchronize a Chassis's Physical State and Its Information in the Database.

ProcedureTo Synchronize a Chassis's Physical State and Its Information in the Database

Before You Begin

Make certain you have upgraded the Provisioning Server software as directed by To Upgrade from N1 Provisioning Server Version 3.0 to Version 3.1

Note –

You must synchronize each chassis in your installation. When you complete synchronizing a chassis, you are given the option to synchronize another chassis.

Steps

  1. Login in as root (su - root) on the control plane server.

  2. To start the synchronization process, type the command opt/terraspring/sbin/shelfsync.

    You are prompted to enter the IP address or device ID of the chassis.

  3. Provide the IP address or device ID of the chassis you want to synchronize.

    Type the IP address or the device ID of the chassis.

    The upgrade process queries the database for the chassis, checks the chassis network connectivity, and runs discovery on the chassis. You are then prompted for the chassis management interface user name.

  4. Provide the chassis management interface user name.

    Type the chassis user name. You are then prompted for the chassis user name password.

    Note –

    The default chassis user name is admin.

  5. Provide the chassis user name password.

    Type the chassis user name password. The following prompt appears:

    Are the switch user name and password the same as the management user 
name and password?
[yY/nN]

  6. Verify that the switch user name and password are the same as the management user name and password.

    • Type y if the user name and password are the same for the switch and chassis management.

      Note –

      The chassis switch user name and password and the chassis management user name and password must be the same only when discovering devices during installation. The user names and passwords do not have to be the same when you have modified a chassis or added a new chassis and are subsequently running shelfsync. For more information about shelfsync, see Adding, Moving, and Deleting Chassis Components in N1 Provisioning Server 3.1, Blades Edition, System Administration Guide.

    • Type n if the user name and password are not the same.

    The following prompt appears.

    Is there any new switch added to the shelf that you want to bench configure?
 [yY/nN]

  7. Configure new chassis switch and system controllers.

    • Type y if any chassis contains a new SSC.

      You are prompted in sequence for the default gateway IP address, the netmask address, the VLAN ranges, the IP address of the switch, and the SSC number of the switch. When you have provided the information required by each prompt, the upgrade process configures the new SSC. The upgrade process then runs discovery on the chassis as described below.

    • Type n if no new switches are present in any chassis.

      The upgrade process runs discovery on the chassis, writes WML output for the chassis to /var/tmp, and retrieves the database state.

      A list of recommended actions then appears. For example:


      Recommended actions:
                Recommended
#  Cause        Action     Identification       Conflicting IDs
-- -----------  ------- ----------------------- ---------------
0  Discovered   ADD     50211 00:03:BA:26:91:AD
1  Discovered   ADD     50251 sw_50251_SSC1 

* = action has been run, entering -y will suppress acknowledgement prompts

enter line number(s) from above or q for quit:

  8. Resolve the listed problems or continue the upgrade process.

    • To resolve a problem, type the line number of the problem. For example, to add the device 50211 shown in the previous step, you would type 0 to add the device, and then provide the information for which you are prompted.

    • To continue the upgrade process, type q.

      You are given the opportunity to resynchronize the current chassis, synchronize another chassis, or exit the upgrade process.

  9. Select an action.


    What do you want to do next:
#1. Re-sync the current SFB1600 device with its saved state.
#2. Synchronize another SFB1600 device with its saved state.
#3. Exit.
Make selection (1-3):

    • To resynchronize the current chassis, type 1.

    • To synchronize another chassis, type 2.

    • To exit to the system prompt, type 3.

    Caution – Caution –

    You must synchronize each chassis in your installation. If you have more than one chassis, type 2 to synchronize the next chassis. You are prompted to provide the IP address or device ID of the chassis you want to synchronize. Go to Step 3.

See Also

When you have completed chassis synchronization, update the control center application server as directed by the next procedure, To Update the Control Center Application Server.

ProcedureTo Update the Control Center Application Server

Before You Begin

Make certain you have performed the following tasks before you update the control center application server:

Steps

  1. Login in as root (su - root) on the control plane server.

  2. Stop the Provisioning Server and the Application Server.

    Type the command /opt/terraspring/sunone/bin/appserv stop. The following messages appear.


    Stopping admin server instance...
Instance admin-server stopped
Stopping server server_gw...
Instance server_gw stopped

    • If the administrator server fails to stop, type the following command :

      /opt/terraspring/sunone/domain_gw/admin-server/bin/stopserv

    • If the application server fails to stop, type the following command:

      /opt/terraspring/sunone/domain_gw/server_gw/bin/stopserv

  3. Update the Control Center application server.

    Type /opt/terraspring/sunone/bin/setup7.sh -silent -upgrade.

    The setup7.sh process copies files required for the update, updates the server and security database, and generates the required database and security keys. The update process exits to the system prompt when it has completed the update.

  4. Restart the application server.

    Type the command /opt/terraspring/sunone/bin/appserv start. The following messages appear.


    Starting admin server instance...
Instance admin-server started
Starting server server_gw...
Instance server_gw started

    • If the administrator server fails to start, type the following command :

      /opt/terraspring/sunone/domain_gw/admin-server/bin/startserv

    • If the application server fails to start, type the following command:

      /opt/terraspring/sunone/domain_gw/server_gw/bin/startpserv

    When the administrator server and application server have started, import the operating system images as directed by the next procedure, To Import Operating System Images.

ProcedureTo Import Operating System Images

Before You Begin

Make certain you have performed the following tasks before you import the N1 Provisioning Server version 3.1 operating system images:

Steps

  1. Log in as root (su - root)on the image server machine.

  2. Type the command ps -ef | grep mountd to check whether the network file system (NFS) daemon is running.

    If the NFS daemon is not running, type /etc/init.d/nfs.server start to start the NFS daemon.

  3. Import the operating system images.

    On the control plane server, type the command /opt/terraspring/sbin/imagewizard -n -i /cdrom/cdrom0/Images. The Solaris images on the N1 Provisioning Server installation DVD-ROM are imported to the image server.

See Also

When the images have been imported, you must perform the following tasks.