N1 Provisioning Server 3.1, Blades Edition, Installation Guide

Installing the N1 Provisioning Server Software

You can install the N1 Provisioning Server and N1 image server software on the same machine, or on separate machines.

Note –

The installation process aliases the control plane server as idb, and modifies the /etc/hosts file accordingly.

Installing the N1 provisioning software can take two and a half hours or more depending on the number of chassis and server blades. Validating the server blade configuration takes approximately 25 minutes for each chassis.

To Install the Provisioning Server and Image Server Software

Before You Begin

All tasks described by Chapter 3, N1 Provisioning Server System and Network Preparation must be completed successfully before you can proceed with this task.

Steps

If you are going to use the Postgres database, create the Postgres database group and user accounts.
1. Type groupadd dba to create the database administration group for the Postgres database.
2. Type useradd -g dba postgres to add the Postgres user account.

Insert the N1 Provisioning Server installation DVD-ROM into the DVD-ROM drive.

Type ./cdrom/cdrom0/install to run the N1 Provisioning Server installation script.

The following messages appear.

/cdrom/cdrom is removable, relocating to /tmp ...
Installer for N1 Provisioning Server Software version 3.1.3.2.


Enter the roles to install. 

PS: Provisioning Server Only 
PS IS: Provisioning Server and Image Server on a single system
Press enter to install both roles on a single system. [PS IS]:

Choose whether to install both the Provisioning Server and the Image Server software.
- If you are installing both the Provisioning Server and the image server software on a the control plane server, press Enter. The following messages appear.
  Installing Roles: PS IS Continue (y/N):
- If you are installing only the Provisioning Server software on the control plane server, and installing the image server on a separate machine, type PS. The following messages appear.
  
  You will be prompted near the end of the installation process for information about the separate image server machine.
```
Installing Roles: PS
Continue (y/N):
```
Type y to continue.

You are notified that configuration of the Provisioning Server software is in progress. After configuration completes, the install process checks for the type of gigabit Ethernet card that is installed.

If needed, reboot the system.
- If the SysKonnect gigabit ethernet card is installed on the control plane server, the following messages appear.
  The syskonnect configuration file has been updated to support vlans. A reboot is required to enable the new configuration to take effect.
  Reboot the system. When the system finishes booting, repeat steps 1 through 4. When prompted to continue, type y.
  
  The installation process backs up the system state and stops all provisioning server services.
- If the Sun GigaSwift gigabit ethernet card is installed, no messages are displayed. A system reboot is not needed.
  
  The installation process backs up the system state and stops all provisioning server services.
The installation process then checks whether JRE 1.4.1 is installed.

If needed, accept the JRE 1.4.1 license.
- If JRE 1.4.1 is not already installed, the JRE 1.4.1 license agreement appears. Read the license agreement. You are prompted whether to accept the license.
  
  Type yes to agree to the license terms and install JRE 1.4.1 and continue the installation process.
  
  Type no if you disagree with the license terms. The installation process exits to the system prompt.
- If JRE 1.4.1 is already installed, you are not prompted to agree to the JRE license.
The install process installs the Provisioning Server packages. Informational messages about the configuration and each package appear. For a list of the packages installed and descriptions of each package, see Appendix B, N1 Provisioning Server Packages.

The following menu appears when package installation has completed.
```
N1 Provisioning Server Install Main Menu

  1.  IP Address of external DNS server to forward unknown queries:
  2.  Image Copy Subnet:
  3.  Number of Sun Blades to be managed:
  4.  Database software: Postgres
      4.1.   Infrastructure Database parameters ->
      4.2.   Control Center Application Server and Database parameters ->  
  5.  Datacenter DNS Domain Name for this N1 Provisioning Server:
  6.  Resource Layer VLANs: <list>
  7.  Resource Layer Subnets:
  8.  Sun Blade System Chassis Information for discovery ->
  9.  Flash snapshot permission:  
 10.  Directory where images will be stored:


Please select an item by entering the index value preceding it ('x' to
   exit, 'help' for usage information) :
```
Tip –
To display an explanation of installation menu navigation. type help at the prompt.

For a detailed description of the menu items, see Appendix A, Installation Main Menu Description

Note –
Each time you enter the requested values, the Provisioning Server Install Main Menu is redisplayed with the values you specified listed.

Type 1 to specify the IP address to which to forward unknown queries.

The following prompt appears.
Enter DNS Forwarder IP (<ENTER> for none) :
Type the IP address to which unknown queries are to be forwarded.

If you do not have an external IP address, press Enter to leave this field blank. An incorrect entry causes installation to fail.

The Install Main Menu reappears with the IP address displayed for item 1.

Type 2 to specify the IP address of the Image Copy subnet.

The following prompt appears.
Enter Image Copy Subnet (example: 10.42.42.0/24):
Type the IP address for the Image Copy subnet.

The Install Main Menu reappears with the IP address displayed for item 2.

Type 3 to specify the number of server blades that are to be managed.

The following prompt appears.
Enter the number of blades to be managed:
Type the total number of server blades contained in all of the chassis that are to be managed by the N1 Provisioning Server.

Type 4 to specify the database software.

The following prompt appears.
Enter the Database software to use [Oracle|Postgres]:

Type the name of the database to use exactly as shown by the prompt.

The installation Main Menu reappears.

Type 4.1 to specify the Database Parameters.
- If you specified Oracle in Step 12, go to Step 14.
  
  Caution –
  The Oracle database must already be installed on the control plane server. See Installing the N1 Provisioning Server Database. If you specify Oracle, and have not installed the Oracle database, installation will fail.
- If you specified Postgres in Step 12, go to Step 16.

Specify the Oracle database parameters.

The Infrastructure Database parameters menu appears.
Infrastructure Database parameters 1. The directory where Oracle is installed: 2. Database Data Directory: 3. Database Log Directory 1: 4. Database Log Directory 2:
Note –
The Oracle Data and Log directories must be empty or installation fails. If the directory names you specify do not exist, the installation software creates the directories.
1. Type 1 to provide the name of the Oracle home directory.
  
  The following prompt appears.
  Enter the oracle home directory [/opt/oracle/OraHome1]:
  If you installed Oracle in the above default directory, press Enter. If you installed Oracle in a different location, type the full path of the Orahome1 directory.
2. Type 2 to provide the database data directory name.
  
  The following prompt appears.
  Enter the directory name to use for the database data [/oracle_data1]:
  Press Enter to accept the default, or type the full path of the directory you want to use for database data.
3. Type 3 to provide the database primary logs directory.
  
  The following prompt appears.
  Enter the primary directory name to use for the database logs [/oracle_data2]:
  Press Enter to accept the default, or type the full path of the directory you want to use for as the primary directory for storing database logs.
4. Type 4 to provide the database secondary logs directory.
  
  The following prompt appears.
  Enter the secondary directory name to use for the database logs [/oracle_data3]:
  Press Enter to accept the default, or type the full path of the directory you want to use as the secondary directory for storing database logs.
  
  Type x to return to the Installation Main Menu.

Type 4.2 to specify the Oracle Control Center application server and Database parameters.

The following submenu appears.

Control Center Application Server and Database parameters

  1.  Admin Server user name: 
  2.  Admin Server password: 
  3.  Oracle database administrator user (see help for details): 
  4.  Oracle database administrator password: 
  5.  Oracle database user: 
  6.  Oracle database password: 
  7.  Enable Mail Notification:

Type 1 to provide the administrator server user name.

The following prompt appears.
Enter Admin Server user name [admin]:
Press enter to accept the default, or type the administration server user name if it is different.

Note –
The database submenu is redisplayed with the values you provided for each submenu item.

Type 2 to provide the administrator server password.

The following prompt appears.
Enter admin server Password:
Type the administration server password. The password must be at least 8 characters. You are prompted to confirm the password. Type the password again.

Type 3 to provide the database administration user.

The following prompt appears.
Enter DBA user [system]:
Press enter to accept the default, or type the database administration user name if it is different.

This is the Oracle user account that is used to create the control center database. The account must have full Oracle DBA administrative privileges. This account is the DBA account created within the Oracle database during database installation. It is not a UNIX user account called oracle. Refer to the Oracle documentation for further information.

Type 4 to provide the database administration password.

The following prompt appears.
Enter Oracle DBA Password:
Type the database administration user password. You are prompted to confirm the password. Type the password again.

Type 5 to provide the Control Center database user name.

The following prompt appears.
Enter user name for the control center database [tcc]:
Press enter to accept the default, or type the Control Center database user name if it is different.

Type 6 to provide the Control Center database user password.

The following prompt appears.
Enter Oracle database user Password:
Type the database user password. You are prompted to confirm the password. Type the password again.

Type 7 to enable or disable email notification.

The following prompt appears.
Do you want to enable email notification? ([n]/y)
- To enable email notification, type y.
  
  The email specifications menu appears. Go to Step 17
- To disable email notification, type n and then type x to return to the Installation Main Menu.
  
  Go to Step 18

Specify the Postgres Control Center application server database parameters.

The following submenu appears.

Infrastructure Database parameters

  1.  Database Data Directory: 
  2.  Database Log Directory 1:

Type 1 to provide the name of the Postgres home directory.

The following prompt appears.
Enter the directory name to use for the database data [/postgres_data]:
Press Enter to install Postgres in the default directory /postgres_data. If you want to install Postgres in a different directory, type the full path of the directory.

Type 2 to provide the name of the database logs directory.

The following prompt appears.

Enter the primary directory name to use for the database logs
 [/postgres_log]:

Press Enter to use /postgres_log as the directory in which to store the database logs. If you want to store the logs in a different directory, type the full path of the directory.

The following submenu appears.

Control Center Application Server and Database parameters

  1.  Admin Server user name: 
  2.  Admin Server password: 
  3.  Database user: 
  4.  Database password: 
  5.  Enable Mail Notification:

Type 1 to provide the administration server user name.

The following prompt appears.
Enter Admin Server user name [admin]:
Press enter to accept the default, or type the administration server user name if it is different.

Note –
The password must be at least 8 characters. You are prompted to confirm your password by typing the password again.

Type 2 to provide the administration server password.

The following prompt appears.
Enter admin server Password:
Type the administration server password. You are prompted to confirm the password. Type the password again.

Type 3 to provide the Control Center database user name.

The following prompt appears.
Enter user name for the control center database [tcc]:
Press enter to accept the default, or type the Control Center database user name if it is different.

Type 4 to provide the Control Center database user password.

The following prompt appears.
Enter Database user Password:
Type the database user password You are prompted to confirm the password. Type the password again.

Type 5to choose whether to enable email notification.

The following prompt appears.
Do you want to enable email notification? ([n]/y)
- To disable email notification, type n and then type x to return to the Installation Main Menu.
  
  Go to Step 18
- To enable email notification, type y.
  
  The email specifications submenu appears.

Specify database email notification values.

When you enable email notification, the following submenu appears.
7.1 Mail From: 7.2 Mail To: 7.3 SMTP host name:
1. Type 1.
  
  Provide the name of a valid user account for sending mail. The mail submenu reappears.
2. Type 2.
  
  Provide the name of a valid user account for receiving mail. The mail submenu appears.
3. Type 3.
  
  Provide the host name of the SMTP mail server on your intranet.
4. Type x to return to the Installation Main Menu.

Type 5 to provide the DNS Domain Name for the Provisioning Server.

The following prompt appears.
Enter the fully qualified dns domain name:
Type the fully qualified DNS domain name for the Provisioning Server. For example; n1ps01.companyname.com.

Type 6 to allocate the virtual local area networks (VLANs) for your farms.

The following prompt appears.

Resource Layer VLANs

  1. 10-255

  These are the VLANs that will be allocated to your farms. Each Resource
  VLAN must be a valid integer range such as '11-23' or '25'

  Choose an operation to perform on the list.
  a - add item       d - delete item
  i - insert item    x - exit
  [a|d|i|x]:

Type a to add a VLAN range. The following prompt appears.

Add Item to List
  Enter a VLAN range (example: '11-23'):

Type a range of VLANs to allocate for a farm, for example, 10–22. The Resource Layer VLAN menu is redisplayed.

Repeat this step until you have allocated all VLANs. When you have completed adding VLAN ranges for the farms, type x to exit the VLAN menu.

The Install Main Menu appears.

Type 7 to provide the Resource Layer Subnets IP addresses

The following prompt appears.

Resource Layer Subnets

  <Empty List>

  These are the subnets that are allocated to your farms. Each resource
  subnet must be of the form '<subnet address>/<i|e>' where <subnet
  address> is of the form '<subnet ip>/<masklen>' and the final 'i' or 'e'
  indicates whether this is an internal subnet or an external subnet. For
  example: '10.8.0.0/24/i' and '220.240.255.0/24/e' are valid values.

  Choose an operation to perform on the list.
  a - add item       d - delete item
  i - insert item    x - exit
  [a|d|i|x]: 
  Add Item to List
  Enter Resource Subnet (example: 10.8.0.0/24/i):

Type a to add a Resource Layer subnet. The following prompt appears.

Add Item to List
  Enter Resource Subnet (example: 10.8.0.0/24/i):

Type a valid subnet value. The Resource Layer Subnets menu is redisplayed.

Repeat this step until you have entered all Resource Layer subnets. When you have completed adding subnet values for the farms, type x to exit the VLAN menu.

The Installation Main Menu appears.

Type 8 to provide the blade system chassis information for discovery.

The following menu appears.

Sun Blade System Chassis Information for discovery

  1.  Blade System Chassis IP Addresses and Switch Network Configuration: 
  2.  Blade System Controller and Switch User Login (Note: The System
      Controllers and Switches for ALL the Blade System Chassis MUST have
      the same login): 
  3.  Blade System Controller and Switch Password (Note: The System
      Controllers and Switches for ALL the Blade System Chassis MUST have
      the same password): 


  Please select an item by entering the index value preceding it ('x' to
  exit, 'help' for usage information) :

Type 1 to provide the chassis IP addresses and switch network configuration.

The following menu appears.

Blade System Chassis IP Addresses and Switch Network Configuration

  sc_ip         sw1_ip      sw2_ip       default_gw    netmask      
  -----------------------------------------------------------------
  <empty list> <empty list> <empty list> <empty list> <empty list> 

  These are the IP Addresses of the SunFire Blade System Chassis in your
  I-Fabric. Each Blade System Controller IP Address must be accompanied by
  network configuration data for the Switches on that Blade System Chassis.
  The install program uses the SC IP Address to connect to the SunFire
  Blade System Controller and uses the rest of the information for
  *configuring** the switches on that blade system chassis. Note that the
  installer will destroy any existing switch configurations and replace it
  with the supplied information.
  
  You *must* supply 2 IP addresses for the switches even if only one switch
  is present in a shelf. The installer will ignore the unused address but
  you should keep it reserved  for possible addition of a second switch.

  Choose an operation to perform on the list.
  a - add item	     d - delete item
  i - insert item    x - exit
  [a|d|i|x]:

Note –

A switch address must be specified for SSC1 (a second SSC) even if the chassis has only one SSC. The IP address is reserved for possible addition of a second SSC.

Add the chassis information.

Type a. The following prompt appears.
Add Item to List Enter Blade System Controller IP Address:
Type the chassis system controller IP address, for example, 10.5.144.50. The installation process pings the address to ensure it exist. If it exists, the following message appears:
Pinging 10.5.144.50 ...success!
The following prompt appears.
Enter First Switch IP Address:
Type the first switch IP address.

The following prompt appears.
Enter Second Switch IP Address:
Type the second switch IP address.

The following prompt appears.
Enter Blade Switch Default Gateway:
Type the switch default gateway IP address.

The following prompt appears.
Enter Blade Switch netmask:

Type the netmask value.

The values for the chassis appear. For example:

Blade System Chassis IP Addresses and Switch Network Configuration

  sc_ip        sw1_ip       sw2_ip       default_gw   netmask      
  -----------------------------------------------------------------
  10.5.144.50  10.5.144.53  10.5.144.54  10.5.144.1   255.255.255.0

Repeat this step until you have entered the values for all of the chassis. When you have completed entering the values, type x to exit the Blade System Chassis IP Addresses and Switch Network Configuration menu. The blade system chassis menu reappears.

Sun Blade System Chassis Information for discovery

  1.  Blade System Chassis IP Addresses and Switch Network Configuration: 
  2.  Blade System Controller and Switch User Login (Note: The System
      Controllers and Switches for ALL the Blade System Chassis MUST have
      the same login): 
  3.  Blade System Controller and Switch Password (Note: The System
      Controllers and Switches for ALL the Blade System Chassis MUST have
      the same password): 


  Please select an item by entering the index value preceding it ('x' to
  exit, 'help' for usage information) :

Type 2 to provide the chassis SSC user login.

The following prompt appears.
Enter Blade System Controller and Switch user login:
Type a user name. The blade system chassis menu reappears.

Type 3 to provide the chassis SSC user password.

The following prompt appears.
Enter Blade System Controller and Switch user Password:
Type the password. You are prompted to confirm the password:
Confirm Blade System Controller and Switch user Password:
Type the password again, and then type x to return to the Installation Main Menu.

Type 9 to choose whether to enable Flash snapshot permission.

The following prompt appears.
Enter new value [enabled|disabled]:
Type enabled to enable snapshot permission, or type disabled to disable snapshot permission.

If you want to specify different values for any of the menu items, type the menu item number to edit the values for that item.

Type 10 to specify the directory in which images are to be stored.

The following prompt appears.
Enter new value [/images]:
Press Enter to accept the default value /images, or type the name of a different directory.

The following prompt appears.
(optional) Make a backup of these settings to a file?? ([n]/y)

Choose whether to save the settings to a file.
- Type n to continue without saving the settings. Go to Step 25
- Type y to save the settings. The following messages appear.
  Settings saved. File is /var/tmp/Profile.pl Continue with installation??
  - Type y to continue the installation process. Go to Step 25.
  - Type n to exit the installation process and return to the system prompt.
    
    You can resume the installation process later by typing the following command from the root login prompt:
    
    /cdrom/cdrom0/install -n -s /var/tmp/Profile.pl
    
    When you resume the installation process, informational messages are displayed, and the installation process continues as described in the following steps.
The following prompt appears.
Continue with installation?? (n/[y])

Continue the installation process.

Type y to continue.

The following messages appear.

Done with user input.

Disabling (finger/talk/uucp/printer) / Enabling (tftp) services ...done!
Configuring DNS ...done!
Preparing the system for IDB ...done!

If you selected Oracle as your database, the following messages appear.

The database will be created in the following directories.
    - Data Directory => /export/oracle-data1
    - Log Dirs => [/export/oracle-data2, 
                   /export/oracle-data3/oracle-data3
]


  If you want to mount a second disk or an nfs share onto 
  these directories, do so now. Ensure that the filesystems
  on these directories are created and empty

  If these directories do not exist after this, they will be
  created on the / filesystem

Press Enter to continue.

If you selected Postgres as your database, the following messages appear.

The database will be created in the following directory.
     - Data Directory => /export/postgres_data
 
   If you want to mount a second disk or an nfs share onto
   these directories, do so now. Ensure that the filesystems
   on these directories are created and empty
 
   If these directories do not exist after this, they will be
   created on the / filesystem
 
 Press Enter to continue.

Press Enter to continue.

The installation process then performs setup and configuration tasks, including creation of the control plane database, DNS setup, chassis switch setup and configuration, and chassis server blade setup and configuration. After setup and configuration completes, the installation process runs discovery and starts the provisioning server services, copies required files to the control plane server, configures provisioning server settings, and sets up the ignition operating system.

The setup process then checks whether you have installed a combined Provisioning Server and Image Server.

If you chose to install the Provisioning Server and Image Server on a single machine, the following messages appear.
Installation of N1 Combined Provisioning and Image Server software setup completed successfully.
Go to Step 28

If you chose to install the Provisioning Server software only, the following messages appear.

Setting up separate Image Server ...
Creating new image server 47001
Allocated ip address 10.23.44.2
Now you will need to manually set up the Image Server as follows:

1. Plumb the interface which is connected to VLAN 8

2. Configure the interface using the template: 
   ifconfig ifname  inet 10.23.44.2 netmask 255.255.255.0 broadcast + up
   Make sure the interface is automatically configured during reboot

3. Create a filesystem on /images of at least 6000MB

4. Export the filesystem as: 
	  share -F nfs -o anon=0,rw=@10.23.44.0/24 /images
   Make sure the export is automatically shared upon reboot


When the Image Server machine configuration is complete, come back to 
this machine to finish the image server setup


Press Enter  only AFTER you have set up the Image Server:

Caution –

Do not press Enter until you have completed all of Step 26.

Set up the image server.

Log in as root (su - root) on the image server machine.
1. Plumb the interface connected to the data plane switch (VLAN 8).
  
  Type the command ifconfig ifname plumb where ifname is the name of the gigabit Ethernet card interface.
2. Configure the interface.
  
  Type the command ifconfig ifname inet 10.23.44.2 netmask 255.255.255.0 broadcast + up where ifname is the name of the gigabit Ethernet card interface.
3. Create a filesystem on /images that has at least 6000 Mbytes free space.
  
  If you intend to use a partition other than /images, mount the partition on /images.
  
  If your images directory is part of the image server root file system (/), skip this step.
  
  Type the following commands to mount the partition on /images.
  # mkdir /images # newfs /dev/rdsk/partition # mount /dev/dsk/partition /images
  where partition is the partition disk location. Ensure that the partition contains at least 6000 Mbytes free space.
4. Ensure the /image partition is available over the network
  
  Add the following line to the /etc/dfs/dfstab file.
```
share -F nfs -o anon=0,rw=@10.23.44.0/24 /images
```
5. Preserve the mount point across reboots.
  
  Edit the /etc/vfstab file to preserve the mount point across reboots. See the manual page vfstab(4) for further information.
6. Reboot the image server machine.
  
  When the image server has completed booting, return to the installation session on the control plane server.

Complete image server setup.

Press Enter. The following message appears.
Are you sure you have set up the Image Server? If yes, press Enter to continue or x to exit:
Press Enter to continue. The installation process checks whether the image server is accessible using ping.

Messages similar to the following appear.
Checking if Image Server is pingable ...Done. Image Server Size = 33812 Mbytes Image Server setup completed

Complete Installation.

The installation process now imports the operating system images from the installation DVD-ROM into the image repository, and creates the server images. After server image creation completes, the installation process configures and starts the control center, and then tests the server blades. The status of each test is displayed. When server blade testing completes, the following message appears.
```
Installation of N1 Provisioning Server software completed successfully.
```

Installing the N1 Provisioning Server Software

To Install the Provisioning Server and Image Server Software

Before You Begin

Steps

See Also