Sun Update Connection - Enterprise 1.0 Quick Start Guide: Getting Started

Chapter 2 Installation Planning

This chapter provides system requirements for the server, agents, console, and the operating systems (OS). Also, instructions on registering with vendors is given. An installation checklist provides a list of important information that you might need to know before you begin the installations.

The following topics are covered in this chapter:

System Requirements

This section provides information about the system requirements that must be met before Sun Update Connection – Enterprise is installed.

The following requirements are covered in this section:

Table 2–1, System Requirements for System Dependency Server
Table 2–2, System Requirements for Console
Table 2–3, System Requirements for Agents

The latest requirements can also be found at http://www.sun.com/service/sunupdate/enterprise/specs.html.

Table 2–1 System Requirements for System Dependency Server


Requirement Type	Size
Platform and OS Environment	z/OS and S/390: Any IBM zSeries or S/390 environment supporting Linux [Support for this mainframe environment will be part of a future release.] 32–bit x86: Intel Pentium IV or equivalent AMD64, including EM64-T
Disk Space Requirements	Installation: 512 MB minimum free in the file system that serves `/usr/local` Software Components: 500 MB minimum SWAP: 500 MB minimum
Memory	z/OS and S/390: 256 MB minimum 32–bit x86: 512 MB minimum AMD64 and EM64–T: 512 MB minimum

Table 2–2 System Requirements for Console


Requirement Type	Requirements
Platform	Intel Pentium IV or equivalent
Presentation Environment	One of the following: UNIX® environment with terminal emulator. Execute the console remotely and re-direct your display to a local server. X Windows on a Linux environment. Microsoft Windows with X Emulator for example `CGWIN`, `EXCEED`, or similar. Note – On SUSE 9.0 Professional, set resolution to 1024 x 768.
Disk Space Requirements	256 MB, plus 20 MB for each additional channel
Memory	512 MB
Access	IP connectivity to the system dependency server

Table 2–3 System Requirements for Agents


Requirement Type	Requirements
Platform and Operating System Environment	z/OS and S/390: Any IBM zSeries or S/390 environment supporting Linux 32–bit x86: Intel Pentium IV or equivalent Solaris: SPARC AMD64, including EM64–T POWER: OpenPower server, JS Blade server, pSeries, iSeries mainframe
Memory	128 MB minimum, 256 MB recommended Note – Memory requirements for a mainframe are generally lower.
Disk Space Requirements	256 MB minimum
Access	Superuser access and IP connectivity to the system dependency server

Operating System Requirements

The following tables show the Linux and Solaris distributions that are supported by each application and listed by hardware platform.

The following requirements are covered in this section:

Table 2–4, Supported Channels for the 32-bit x86
Table 2–5, Supported Channels for 32-bit S/390 Systems
Table 2–6,Supported Channels for 64-bit S/390 Systems
Table 2–7, Supported Channels for AMD64
Table 2–8, Supported Channels for 64-bit on POWER
Table 2–9, Supported Channels for the 64-bit x86 (Itanium)
Table 2–10, Supported UNIX Versions on SPARC
Table 2–11, Supported Microsoft Windows Versions

Note –

The bare-metal installation (BMI) server automates Linux distributions and operating system installation on a bare-metal system. For more information, see Sun Update Connection - Enterprise Bare Metal Installation Guide.

Distributions that support an application are marked with a plus sign (+), while distributions that do not support an application are marked with a minus sign (–).

A channel is a combination of distributions and architecture.

For example, a channel would be one of the following:

A Solaris 10 distribution on the SPARC architecture
A Solaris 10 distribution on the x86 architecture
A Linux - RHEL WS 3.0 distribution on the AMD64 architecture

The latest list can also be found at http://www.sun.com/service/sunupdate/enterprise/knowledge.html.

Table 2–4 Supported Channels for the 32-bit x86


Operating System or Channel	Operating System Version	System Dependency Server	Agent	Console	BMI Server	BMI Provision
Red Hat	7.2, 7.3, 8.0, or 9.0	Not Recommended	+	+	–	–
Fedora Core	2	Not Recommended	+	+	–	–
Red Hat Enterprise Linux Advanced Server	2.1	+	+	+	–	+
	3.0	+	+	+	+	+
	4.0	+	+	+	–	–
Red Hat Enterprise Linux Enterprise Server	2.1	+	+	+	–	+
	3.0	+	+	+	+	+
	4.0	+	+	+	–	–
Red Hat Enterprise Linux Workstation Server	2.1	+	+	+	–	–
	3.0	+	+	+	+	+
	4.0	+	+	+	–	–
SUSE Professional	9.0 or 9.1	+	+	+	+	+
SUSE Professional	9.2	+	+	+	–	+
SUSE Linux Enterprise Server	8 or 9	+	+	+	–	+
Novell Linux Desktop	9	+	+	+	–	+
Novell SLSS	8	–	+	–	–	–
Solaris Operating System	10	–	+	–	–	–

Table 2–5 Supported Channels for 32-bit S/390 Systems


Operating System /Channel	Operating System Version	System Dependency Server	Agent	Console	BMI Server	BMI Provision
SUSE Linux Enterprise Server [Support for this mainframe environment will be part of a future release.]	7, 8, 9, S390	+	+	–	–	–
Red Hat Enterprise Linux Advanced Server	4.0	+	+	–	–	–

Table 2–6 Supported Channels for 64-bit S/390 Systems


Operating System /Channel	Operating System Version	System Dependency Server	Agent	Console	BMI Server	BMI Provision
Red Hat Enterprise Linux Advanced Server	3.0 or 4.0	+	+	–	–	–
SUSE Linux Enterprise Server	8 or 9	+	+	–	–	–

Table 2–7 Supported Channels for AMD64


Operating System /Channel	Operating System Version	System Dependency Server	Agent	Console	BMI Server	BMI Provision
Red Hat Enterprise Linux Advanced Server	3.0	+	+	+	–	+
Red Hat Enterprise Linux Advanced Server	4.0	+	+	+	–	–
Red Hat Enterprise Linux Workstation Server	3.0	+	+	+	–	+
Red Hat Enterprise Linux Workstation Server	4.0	+	+	+	–	–
Red Hat Enterprise Linux Enterprise Server	4.0	+	+	+	–	–
SUSE Professional	9.0	+	+	–	–	+
SUSE Professional	9.1	+	+	–	–	–
SUSE Linux Enterprise Server	8 or 9	+	+	–	–	+

Table 2–8 Supported Channels for 64-bit on POWER


Operating System /Channel	Operating System Version	System Dependency Server	Agent	Console	BMI Server	BMI Provision
Red Hat Enterprise Linux Advanced Server	3.0	–	+	–	–	–
SUSE Linux Enterprise Server	9	–	+	–	–	+

Table 2–9 Supported Channels for the 64-bit x86 (Itanium)


Operating System /Channel	Operating System Version	System Dependency Server	Agent	Console	BMI Server	BMI Provision
Red Hat Enterprise Linux Workstation Server	3.0	–	+	–	–	–

Table 2–10 Supported UNIX Versions on SPARC


Operating System /Channel	Operating System Version	System Dependency Server	Agent	Console	BMI Server	BMI Provision
Solaris Operating Environment	8	–	+	–	–	+
	9	–	+	–	–	–
	10	–	+	–	–	+

Table 2–11 Supported Microsoft Windows Versions


Operating System /Channel	Operating System Version	System Dependency Server	Agent	Console	BMI Server	BMI Provision
Windows	2000	–	–	+	–	–
Windows	XP	–	–	+	–	–

Register With Vendors for Authentication

Sun Update Connection – Enterprise enables you to download software components from vendor sources. For example, if your environment includes managed hosts that run the Solaris OS or a Linux distribution, you need to be able to retrieve software from the appropriate vendor source. Sun Update Connection – Enterprise determines which software distributions apply to your environment by evaluating the agents that you have installed on your managed hosts. Sun Update Connection - Enterprise needs authentication information for each distribution that is associated with vendor web sites.

To download software components from some of the vendor sources, you must first register with that source. The registration process sets up an account with a user name and password. Then the Sun Update Connection – Enterprise software can successfully access binaries from this source. To access software components from these sources, you must have a valid account. For example, you must be registered with Sun Update Connection to obtain Solaris updates and baselines.

If you have distribution sources without the appropriate authentication information, you can add the user name and password the next time you log in to the console. You must log in to the console as the admin user or as a user with full permissions. After you log in the Authentication window opens. For example, if you have a Solaris agent installed and no authentication information has been supplied, the Authentication window automatically opens so that you can specify the user name and password you created when you registered with SunSolve^SM. Another example is if you later install an agent on a Red Hat Linux system, the Authentication window opens to request authentication information for that source the next time you log in to the console. If the console is already started, you can edit the Authentication window. See To Change User Name and Password for Authentication.

Not all distributions require authentication to access binaries from the vendor source. Sun Update Connection – Enterprise contacts the following vendor sources to obtain binaries. Table 2–12 provides registration sites and addresses for vendor sources.

Table 2–12 Authenticating and Registering With Vendor Sources


Vendor Source	Authorization Required?	Registration Sites
Solaris update and baselines are available from SunSolve.	Yes	`http://sunsolve.sun.com`
Red Hat Linux binaries are available from the Red Hat Network.	Yes	`http://rhn.redhat.com`
SUSE Linux Enterprise Server binaries	Yes	`http://sdb.suse.de//download`
SUSE binaries	No	Obtain from ftp://ftp.suse.com

To Change User Name and Password for Authentication

This procedure provides steps to change the user name and password to match those you registered with at the vendor web sites. Use this procedure if you are logged in to the console.

In the console window, choose Authentication from the Tools menu.

The Authentication window is displayed.

To open the Authentication Editor window, select the source and click Edit.

Type the user name and password.

The Authentication Editor does not verify that the information you supply is correct. Therefore, ensure that you specify the exact user name and password that the vendor source needs, or the software download fails.

Gathering Information Before Installation

Use the following checklist to gather the information you need to install the Sun Update Connection – Enterprise components.

Table 2–13 Checklist for Installing the System Dependency Server


System	Information for Installation	Description	For More Information
	Sun Online Account	A Sun Online Account is used to download Solaris updates. If you have Solaris software installed on systems that you plan to manage with the Sun Update Connection – Enterprise solution, you must provide a Sun Online Account user name and password.	To get a Sun Online Account, go to http://www.sunsolve.sun.com
System dependency server	Choosing `ezinstaller` options	You can choose a standard, secure, or a predefined channels installation. Standard - Installs the system dependency server. Secure - Installs the system dependency server and provides a secure installation with a secure password. Predefined channels - Installs the system dependency server and provides an opportunity to activate channels. Use this option if you plan to add systems of different distributions later and want to create multidistribution profiles that include those systems when they are added to your environment. You can activate any channel from a list of all supported channels from the universal server.
System dependency server	Configuring Web proxies	If Internet security is set up when you install the system dependency server, you can configure a web proxy at installation time. If Internet security is set up or changed after installation, you can configure the web proxy.	To configure a web proxy during installation , see Installing the Proxy System Dependency Server To configure a web proxy after installation, see Chapter 6, Configuring Web Proxies and Firewalls, in Sun Update Connection - Enterprise 1.0 Administration Guide
System dependency server	Determining the host name or IP address	During installation, you must verify the local host name and domain or IP address.
System dependency server	Deciding where to install the console files	You can keep the default path or type another directory name.
System dependency server	Deciding which information to use for the SSL certificate	Sun recommends that you provide information about your organization, but you can use the provided Sun information.
System dependency server	Setting ports between the universal server and components	The default port between the following components and the universal server is 8002. Agent Console CLI API If port 8002 is not free on the local site, ports ranging from 8000 to 8100 are searched. You can set a different default.	See Reconfiguring Agent, Console, CLI, and APIParameters in Sun Update Connection - Enterprise 1.0 Administration Guide
Console	Registering with vendors	Sun Update Connection – Enterprise enables you to download software components from vendor sources. You must register with most of these vendors. Authentication can be set up with the Authentication window on the console.	Table 2–12
Proxy system dependency server	Installation limitations	You must have IP connectivity to the system dependency server. A system dependency server cannot be already installed on the proxy.

To define managed hosts before the systems are set up and the agent is installed, see Chapter 1, Application Administration, in Sun Update Connection - Enterprise 1.0 Administration Guide.