Sun N1 Service Provisioning System 5.1 Installation Guide

Chapter 2 System Requirements for the N1 Service Provisioning System 5.1

This chapter lists the system requirements for installing and using the N1 Service Provisioning System 5.1. This chapter discusses the following topics:

Operating System Requirements

You can install the N1 Service Provisioning System 5.1 Master Server, Remote Agent, Local Distributor, and CLI Client on servers that are running the following operating systems:

Table 2–1 Supported Operating Systems for the N1 Service Provisioning System 5.1


N1 Service Provisioning System Application	Supported Operating Systems
Master Server	Solaris 8 OS running on SPARC® based servers Solaris 9 and Solaris 10 OS running on SPARC and x86 based servers Red Hat Linux Advanced Server 2.1 and Red Hat Linux Advanced Server 3.0 Microsoft Windows 2000 Server and Microsoft Windows 2000 Advanced Server
Local Distributor, Remote Agent, CLI Client	Solaris 7 and Solaris 8 OS running on SPARC based servers Solaris 9 and Solaris 10 OS running on SPARC and x86 based servers Red Hat Linux Advanced Server 2.1 and Red Hat Linux Advanced Server 3.0 IBM AIX 5.1, 5.2, and 5.3 SUSE Linux Enterprise Server 8 and SUSE Linux Enterprise Server 9 HP-UX 11i V1 on PA-RISC based servers Microsoft Windows 2000 Server and Microsoft Windows 2000 Advanced Server Microsoft Windows Server 2003: Standard, Enterprise, or Web Edition Microsoft Windows Standard 2003 x64 Edition or Microsoft Windows Enterprise x64 Edition

Operating System Configurations

To install and run the provisioning system, you must configure your systems as described in the following sections.

Solaris System Configuration Requirements

A Solaris system that is running the Master Server requires the following /etc/system settings.

Note –

If you are using the Solaris 9 or Solaris 10 OS, you cannot change the values for shmsys:shminfo_shmmin and shmsys:shminfo_shmseg. If you are using the Solaris 10 OS, you cannot change the values for shmsys:shminfo_shmmax, shmsys:shminfo_shmmni, semsys:seminfo_semmns, and semsys:seminfo_semvmx.

The default values for these settings are acceptable.

Table 2–2 Solaris /etc/system Settings


Variable	Minimum Value
`shmsys:shminfo_shmmax`	0x20000000 [536870912 in decimal (512Mb), but this number must be specified in hex for the Solaris 8 Operating System.]
`shmsys:shminfo_shmmin`	1
`shmsys:shminfo_shmmni`	2
`shmsys:shminfo_shmseg`	1
`semsys:seminfo_semmni`	32
`semsys:seminfo_semmns`	512
`semsys:seminfo_semmsl`	17
`semsys:seminfo_semvmx`	537

For more instructions to change the /etc/system settings, see Solaris Tunable Parameters Reference Manual.

Linux System Configuration Requirements

The bc command must be in the user's path when you install the N1 Service Provisioning System. Without the bc command, the installation exits and requests that bc be installed. Install the bc-1.06-5.rpm package or a later version of the package.

When you install the N1 Service Provisioning System on an NFS mounted directory on a SUSE Linux 8 server and you want to use SSH or SSL for secure connections, configure the NFS client with nolocks or the NFS server to allow locks. If neither the NFS client nor the NFS server is configured properly, the N1 Service Provisioning System application will not start.

The Linux Master Server installation program checks the following system parameters and exits with an error if the minimum values are not met.

Table 2–3 Linux Master Server System Settings


System Parameter	Minimum Value
`shmall` in `/proc/sys/kernel/shmall`	536870912 (512Mb)
`shmmax` in `/proc/sys/kernel/shmmax`	536870912 (512Mb)

Required Operating System Patches

The following table lists the required patches for each supported operating system.

Table 2–4 Required Patches for Supported Operating Systems


OS Version	Required Patches
Solaris 7	106980-16 106541-16 107544-03 106950-13 106327-08 106300-09
Solaris 8, SPARC based servers	111310-01 109147-28 111308-04 112438-03 108434-15 108435-15 111111-04 112396-02 110386-03 111023-03 111317-05 113648-03 115827-01 116602-01 108987-13 108528-29 108989-02 108993-33 109326-14 110615-10
Solaris 9, SPARC based servers	114356-06
Solaris 9, x86 based servers	114357–06
Solaris 10, SPARC based servers	None
Solaris 10, x86 based servers	None

IBM AIX 5.1	AIX 5.1–5.1.4.0 maintenance level: APAR IY44478
IBM AIX 5.2	AIX 5.2–5.2.1.0 maintenance level: APAR IY44479
IBM AIX 5.3	AIX 5.3.1.0 maintenance level: APAR IY58143

Red Hat Linux Advanced Server 2.1	None
Red Hat Linux Advanced Server 3.0	None

SUSE Linux Enterprise Server 8	None
SUSE Linux Enterprise Server 9	None

HP-UX 11i V1 on PA-RISC based systems	PHNE_23502 PHKL_24253 PHKL_24254 PHKL_24255 PHKL_24256 PHKL_24257 PHKL_24751 PHNE_25084 PHCO_25226 PHKL_25227 PHKL_25367 PHCO_25452 PHKL_25468 PHKL_25614 PHKL_25728 PHKL_25729 PHKL_25840 PHKL_25842 PHKL_25871 PHKL_27091 PHKL_27092 PHKL_28489 PHNE_29887 PHCO_29960 PHSS_30049

Windows 2000 Server or Windows 2000 Advanced Server	Service Pack 3
Windows Server 2003	none
Windows Server 2003 x64	none

Hardware Requirements

Master Server Hardware Requirements

The following table lists the hardware requirements for installing the Master Server on the supported operating systems.

Table 2–5 Hardware Requirements for the Master Server


	Solaris	Red Hat Linux	Windows
Hardware	SPARC or x86 based [SPARC only for the Solaris 8 OS]	x86 based	x86 based
CPU	450 MHz single or multiple CPU	1 GHz single or multiple CPU	1 GHz single or multiple CPU
RAM	At least 1 GByte RAM	At least 1 GByte RAM	At least 1 GByte RAM
Free Hard Disk Space	2 GBytes	2 GBytes	2 GByte

Local Distributor, Remote Agent, and CLI Client Hardware Requirements

The following table lists the hardware requirements for installing the Local Distributor, Remote Agent, and CLI Client on the supported operating systems.

Table 2–6 Hardware Requirements for the Local Distributor, Remote Agent, and CLI Client


	Solaris	Red Hat Linux	IBM AIX	Suse Linux	HP-UX	Windows
Hardware	SPARC or x86 based [SPARC only for the Solaris 7 and Solaris 8 OS]	x86 based	pSeries	x86 based	PA-RISC based	x86 based
CPU	400 MHz single or multiple CPU	1 GHz single or multiple CPU	400 MHz single or multiple CPU	400 MHz single or multiple CPU	400 MHz single or multiple CPU	1 GHz single or multiple CPU
RAM	At least 256 MBytes RAM	At least 1 GByte RAM	At least 256 MBytes RAM	At least 1 Gbye RAM	At least 256 MBytes RAM	At least 1 GByte RAM
Free Hard Disk Space	1 GBytes	1 GByte	1 GByte	1 GByte	1 GByte	1 GByte HD free space

General System Requirements

This section lists general system requirements for installing and using the N1 Service Provisioning System 5.1.

Supported Web Browsers

The following table lists the web browser requirements for the N1 Service Provisioning System 5.1 browser interface.

Table 2–7 Web Browser Requirements for the Browser Interface


Platform	Browser
Solaris, Red Hat, SUSE, HP-UX	Netscape Navigator^TM 7.1, Mozilla^TM 1.4
Windows	Netscape Navigator 7.1, Mozilla 1.4, Internet Explorer 5.5, Internet Explorer 6.0
AIX	Mozilla 1.4

Note –

Some web proxy servers are configured to block popup windows. The N1 Service Provisioning System 5.1 relies on the ability to present popup windows to run properly. Do not run web proxy servers that block popup windows or set your browser to block popup windows.

To run properly, the N1 Service Provisioning System 5.1 relies on the ability to use cookies. Set your browser to allow the use of cookies.

Requirements for SSH

If you want to use SSH for secure connections on Linux and UNIX systems, you must have SSH protocol version 2 installed on each server that you want to use SSH.

Requirement for Jython

If you want to use Jython with the CLI Client, install Jython version 2.0 or higher. For more information about Jython, see http://www.jython.org.

Requirements for Locales

The N1 Service Provisioning System 5.1 has been internationalized to install and run in localized environment. Also, the N1 Service Provisioning System 5.1 accepts non–ASCII characters. You will need to adhere to the following requirements if you require that the software support non-ASCII characters:

All applications must be run in the same locale or in locales that are equivalent. The Remote Agent, Local Distributors, and CLI Client must run a locale that is compatible with the locale in which the Master Server is running.
You must use Internet Explorer 5.5 or 6.0, or Netscape 7.0.
Set the web browser Character Interface to use UTF-8, which is also known as Unicode or Universal Alphabet.
In the configuration files, such as the config.properties file, all non-ASCII characters must be Unicode-encoded. You can create configuration files in any encoding. Then, use the native2ascii command that is available in the Java^TM Development Kit (JDK) package to convert the file to Unicode-encoded ASCII characters.