Installing the SLES 10.0 operating system

See the SLES documentation to install SUSE Linux® Enterprise Server (SLES) 10.0 with SP2 for x86_64.
1. Make sure that these components are installed:
  - Required on both the primary and secondary computers:
    - Korn shell.
      The Korn shell is installed automatically in a new installation, but you must select it if you are migrating from SLES 9.0.
    - /usr/lib/libstdc++.so.5 and /usr/lib64/libstdc++.so.5
      The 32-bit and 64-bit versions of a shared library that InfoPrint® ProcessDirector uses. They are standard on some versions of SLES, but not all. Both libraries must be installed if they are not present.
      Note: You must install the .5 versions of these libraries, even if you have the .6 or later versions installed. InfoPrint ProcessDirector relies on code that is present in the .5 versions, but that is changed in later versions. Multiple versions of these libraries can coexist on your system.
      
      The libraries are provided on the operating system installation media or can be downloaded from the Novell Web site.
    - Perl interpreter (Perl.rte 5.8.8 or later).
  - Required on the primary computer only: If you plan to install Windows® secondary computers, you must install the Network Information Service (NIS) server 219-13.2 on the SLES 10.0 primary computer. You can use YaST (Yet Another Setup Tool) to install NIS. In YaST, click Software –> Software Management and search for ypserv.
  - Required on the primary computer, optional on secondary computers:
    - Web browser: Mozilla Firefox 3.5 or later
    - Adobe® Reader 9.0
Create Linux partitions and file systems. See Planning for file systems for recommendations and considerations.

Run these commands and look for the expected results to verify that you installed SLES correctly:

Table 1. SLES commands and expected results
Command	Expected result
To check the SLES release: `cat /etc/SuSE-release`	`SUSE Linux Enterprise Server 10 (x86_64) VERSION = 10 PATCHLEVEL = 2`
To check the Korn shell level: `rpm -q ksh`	`ksh-93r-12.28`
To verify that the operating system is 64-bit: `uname -a`	`Linux myserver 2.6.16.60-0.54.5-smp #1 SMP Fri Sep 4 01:28:03 UTC 2009 x86_64 x86_64 x86_64 GNU/Linux`
To check for /usr/lib/libstdc++.so.5: Navigate to /usr/lib/ and type `ls`	The list of files must include this exact entry: `/usr/lib/libstdc++.so.5` The list might link that entry to this one: `/usr/lib/libstdc++.so.5.0.7`
To check for /usr/lib64/libstdc++.so.5: Navigate to /usr/lib64/ and type `ls`	The list of files must include this exact entry: `/usr/lib64/libstdc++.so.5` The list might link that entry to this one: `/usr/lib64/libstdc++.so.5.0.7`
`getconf GNU_LIBPTHREAD_VERSION`	`NPTL 2.4`
Note: If you have installed a later version of a prerequisite, the version number returned varies.

If the command results are not as you expect, use YaST to make sure you have installed the required components (see step 1). In YaST, click Software –> Install/Remove Software.

Verify date, time, and time zone settings through YaST, and correct if necessary:
Click System –> Date and Time –> Clock and Time Zone Configuration. If you change the date, time, or zone, you might have to reboot the system for your changes to take effect.

Set up networking based on system networking information:

Make sure that InfoPrint ProcessDirector has access to a Domain Name System (DNS) server. The DNS server must have correct entries for the host name and IP address of each InfoPrint ProcessDirector primary computer and secondary computer on the network.

In your firewall, open any ports that InfoPrint ProcessDirector uses. Depending on your configuration, you might need these ports:

Table 2. Port numbers
Port number	Used by
515	LPD protocol
5001–65535	IPDS™ printers Open only the ports that your printers use. They generally fall into this range.
6001 or alternative	AFP™ Download Plus or Download for z/OS®
6100	DownloadAFP input device This port is for the supplied input device. If you copy this input device, open additional ports as needed.
6102	DownloadLineData input device This port is for the supplied input device. If you copy this input device, open additional ports as needed.
6986–6992	InfoPrint Transform Manager or Transform features If you want to use InfoPrint Transform Manager or the Transform features with InfoPrint ProcessDirector, open only the ports that are used. They generally fall into this range.
15080	InfoPrint ProcessDirector base product
15443	InfoPrint ProcessDirector base product when SSL is enabled
15888	InfoPrint ProcessDirector information center
16080	Default port for the Transform feature user interface. If you choose to use a different port during the installation process, open that port instead.
50000	DB2® on a different computer DB2 uses port 50000 by default. If your installation of DB2 uses a different port, open the port you use.
55555	Primary servers listening for secondary servers

Verify network connectivity:
1. To verify that host name resolution is working, enter this command:
  host localhost
  If you can access the DNS server, the response includes the host name localhost or loopback and the address 127.0.0.1. For example:
  localhost.infoprint.com is 127.0.0.1
2. From the computer where you will access the InfoPrint ProcessDirector user interface, use both the host name and the IP address to ping the primary computer.
3. From all secondary computers (if any), ping the primary computer.
4. From the primary computer, ping all secondary computers (if any).
5. Contact the network administrator if you are not successful with any of these verifications.
Verify that the speed, duplexing, and autonegotiation settings for the Ethernet card are those that your network administrator recommends for optimum performance. The optimum settings are different for each installation.
To display and change these settings:
1. Log in as the root user.
2. To display the Ethernet settings, enter:
  ethtool eth0
3. If necessary, use the ethtool command to change these settings. Check with the network administrator for the appropriate flags and values for your network. For example, this command sets full-duplex mode:
  ethtool -s eth0 duplex full
  This command sets autonegotiation on:
  ethtool -s eth0 autoneg on