N1 Provisioning Server 3.1, Blades Edition, Installation Guide

Installation Worksheets

This section provides a list of tasks that must be done before you install N1 Provisioning Server software, and a worksheet that lists the information you need to provide to the installation process.

Prerequisites

The following prerequisites must be met before you install the N1 Provisioning software:

The server, chassis, and switch hardware have been connected, as described in Connecting the Chassis to the Control Plane Server and Switches.
IP addresses have been assigned, as described by Assigning IP Addresses in the Control Plane.
All server, chassis, server blade, and switch hardware has been procured and firmware updated to the required versions, as described in Chapter 2, Hardware and Software Requirements.
Gigabit-capable Ethernet network cards have been installed in the control plane server and if separate, the image server, as described in Installing Gigabit Ethernet Network Interface Cards
The Solaris 8 2/02 operating environment has been installed in the control plane server and if separate, the Image server, as described in Installing the Solaris Operating System, version 8 2/02.
Required system and gigabit Ethernet network card patches have been installed, as described in Installing Required Patches
If you have chosen to use the Oracle Relational database for the Infrastructure Database, Oracle 8i, version 8.1.7 must be installed on the control plane server, as described in Installing the N1 Provisioning Server Database.

Installation Worksheet

During installation, you are asked for specific information. Use the following table to record the values before you install N1 Provisioning Server.

Table 4–1 Information Required by the Installation Process


Description		Value
IP Address of the external DNS server to which unknown queries are forwarded. If you do not want to forward unknown queries, leave this blank. Example: `201.10.51.155`		`_______________________________`
Provide the 24-bit Image Copy subnet IP address netmask. The IP address is reserved for use by image copy processes only. Example: `192.0.0.0/24`		`_______________________________`
Provide the total number of server blades in all B1600 chassis.		`_______________________________`
Provide the name of the database software to use [Oracle\|Postgres]		`_______________________________`
If you are using the Oracle database, provide the following information:
	The name of the directory where Oracle is installed. Example: `/opt/oracle/OraHome1`	`_______________________________`
	The name of the Oracle database data directory. The directory must be empty or installation fails. Example: `/oracle_data1`	`_______________________________`
	The database primary logs directory name. The directory must be empty or installation fails. Example: `/oracle_data2`	`_______________________________`
	The database secondary logs directory name. The directory must be empty or installation fails. Example: `/oracle_data3`	`_______________________________`
If you are using the Postgres database, provide the following information:
	The name of the Postgres home directory. Example: `/postgres_data`	`_______________________________`
	The name of the Postgres database logs directory. Example: `/postgres_log`	`_______________________________`
The database administrator server user name if different than the default name `admin`.		`_______________________________`
The database user name if different than the default name `system`.		`_______________________________`
The Control Center database user name if it is different than the default name `tcc`.		`_______________________________`
If you enable database email notification, provide the following information:
	The name of a valid user account from which Oracle notification messages are to be sent.	`_______________________________`
	The name of a valid user account to which Oracle notification messages are to be sent.	`_______________________________`
	The name of your SMTP mail server.	`_______________________________`
The fully qualified DNS domain name for the N1 Provisioning server. Example: `n1ps.sun.com`		`_______________________________`
Provide the range or ranges of virtual local area network (VLAN) numbers from 11 through 255 that are to be allocated to the Resource Layer VLANs for your farms. Example: `11–24, 25, 26–35`		`_______________________________`
Provide the IP addresses, mask length, and subnet type (internal or external) for all Resource Layer subnets. The IP addresses must be unique, and cannot be the same as the control subnet or the image subnet. Internal subnets are non-routable addresses that are used internally to communicate with farm devices. Example: `10.8.0.0/24/i, 192.168.16.0/24/i` External subnets are externally routable addresses. Example: `220.240.255.0/24/e`, `204.16.18 /24/e`		`_______________________________` `_______________________________` `_______________________________` `_______________________________`
Provide the following information for each blade system chassis and switch network:
	Blade system controller IP address. Example: `10.5.144.50`	`_______________________________`
	SSC0 switch IP address. Example: `10.5.144.53`	`_______________________________`
	SSC1 switch address. Example: `10.5.144.54` Note – The SSC1 switch address must be specified even if the chassis has only one SSC. The IP address is reserved for possible addition of a second SSC.	`_______________________________`
	SSC default gateway IP address. Example: `10.5.144.1`	`_______________________________`
	Chassis netmask. Example: `255.255.255.0` Note – All chassis have the same default gateway and netmask.	`_______________________________`
	Chassis SSC user login name. Note – The SSC login and password must be the same for all chassis during the initial installation or installation fails.	`_______________________________`