test

Sun Open Telecommunications Platform 1.0 Installation and Administration Guide

Chapter 3 Preparing Servers for Open Telecommunications Platform Installation

This chapter provides the procedures for downloading and uncompressing the combined Open Telecommunications Platform (OTP) and Solaris 10 Update 2 installation image, and the procedures for installing and configuring the Solaris OS on the clustered OTP systems.

The following topics are discussed:

Note –

The installation procedures in this manual assume that the Open Telecommunications Platform installation source is located in the NFS-mounted directory /opt1.0 on a server that is external to the OTP hosts. If you have purchased the OTP installation DVD-ROM, create the directory /opt1.0 on an external a server that is external to the OTP hosts, and then copy the DVD-ROM contents to the /opt1.0

The directory contents should be as follows:


# ls -a /otp1.0
.otp.version  OTP-Readme.html   Products   copyright-otp1.0.txt

When you have verified the /opt1.0 directory, NFS-mount the directory as described in Step 10 in the following procedure.

Downloading and Uncompressing the OTP and Solaris OS Software

This section provides the procedures for downloading the Open Telecommunications Platform installation zip files and creating the Solaris 10 Update 2 OS installation image and the Open Telecommunications Platform installation directory and files.

ProcedureTo Download and Uncompress the OTP and Solaris OS Installation Zip Files

Before You Begin

The server to which you download the Open Telecommunications Platform installation zip files must be accessible by the standalone OTP host or the clustered OTP hosts, and have at least 6 Gbytes of available free disk space

Note –

If you have chosen to install the Open Telecommunications Platform using the graphical user interface, you can set up the server as the external OTP installation server as described in Preparing for Installation.

  1. Log in as root (su - root) to a server that is network-accessible by your OTP system.

  2. (Optional) Download and install the Sun Download Manager.

    Downloads of large files using Web browsers can sometimes fail. For this reason, use the Sun Download Manager to download the Open Telecommunications Platform installation zip files. For instructions about how to download, install, and use the Sun Download Manager, go to http://www.sun.com/download/sdm/index.xml.

  3. Create a directory into which the installation zip files are to be saved.

    For example:


    # mkdir /otp-download

  4. Open a web browser and go to the Tech/OEM Web site https://sdlc2j.sun.com/eeAdmin/AdminActionServlet?LMLoadBalanced=. Access is password protected. Your password for the Tech/OEM site is provided at the time of the order.

    1. Download the following five Solaris 10 Update 2zip files to the directory you created in Step 3:

      • sol-10-u2-ga-sparc-dvd-iso-a.zip

      • sol-10-u2-ga-sparc-dvd-iso-b.zip

      • sol-10-u2-ga-sparc-dvd-iso-c.zip

      • sol-10-u2-ga-sparc-dvd-iso-d.zip

      • sol-10-u2-ga-sparc-dvd-iso-e.zip

    2. Download the following three Open Telecommunications Platform installation zip files to the directory you created in Step 8:

      • otp1.0.zip-a

      • otp1.0.zip-b

      • otp1.0.zip-c

  5. Change directory to the installation directory you created in Step 3.

  6. Create the single Solaris 10 Update 2 ISO image.

    1. Unzip each of the ISO image zip files.

      For example:


      # unzip sol-10-u21-ga-sparc-dvd-iso-a.zip
# unzip sol-10-u21-ga-sparc-dvd-iso-b.zip
# unzip sol-10-u21-ga-sparc-dvd-iso-c.zip
# unzip sol-10-u21-ga-sparc-dvd-iso-d.zip
# unzip sol-10-u21-ga-sparc-dvd-iso-e.zip

    2. Concatenate the unzipped ISO files to a single ISO image.

      For example:


      # cat sol-10-u2-ga-sparc-dvd-iso-a sol-10-u2-ga-sparc-dvd-iso-b \
	sol-10-u2-ga-sparc-dvd-iso-c sol-10-u2-ga-sparc-dvd-iso-d \
	sol-10-u2-ga-sparc-dvd-iso-e > sol10u2-ga-sparc-dvd.iso

      • If you are installing the Open Telecommunications Platform for the first time, use either of the two following methods to prepare the Solaris 10 Update 2 ISO image for installation on the each server selected for the Open Telecommunications Platform system.

        • Burn the Solaris 10 Update 2 ISO image you created to a DVD-R.

        • Set up a JumpStart server to install Solaris 10 Update 2.

  7. Prepare the Solaris 10 Update 2 ISO image.

    Use any of the three following three methods to prepare the Solaris 10 Update 2 ISO image for installation on the each server selected for the Open Telecommunications Platform system.

    • Burn the Solaris 10 Update 2 ISO image you created to a DVD-R.

    • Set up a JumpStart server to install Solaris 10 Update 2.

    • Create an empty NFS-mounted directory and then mount the Solaris 10 Update 2 to the NFS-mounted directory.

      • Create an empty directory that will be used as the Solaris 10 Update 2 ISO image mount-point directory. For example: mkdir /sol10u2

      • Add the mount-point directory name to the /etc/dfs/dfstab file.

        For example: share -F nfs -o ro,log=global -d "Sol10U2 ISO mount point" /sol10u2

      • Type svcadm restart nfs/server to stop and then restart NFS.

      • Mount the Solaris 10 Update 2 ISO image to the mount-point directory. For example:

        mount -F hsfs -o ro `lofiadm -a /otp-download/sol10u2-ga-sparc-dvd.iso` /sol10u2

  8. Create the Open Telecommunications Platform installation directory and files.

    1. Concatenate the zipped Open Telecommunications Platform files to a single zip file.

      For example:


      # cat otp1.0.zip-a otp1.0.zip-b otp1.0.zip-c > otp1.0.zip

    2. Unzip the Open Telecommunications Platform zip file you created to create the installation directory and files.

      For example:


      # unzip otp1.0.zip

      The Open Telecommunications Platform installation directory otp1.0 is created.

  9. Move the otp1.0 directory to the root file system.

    For example:


    #  mv otp1.0 /

    The instructions and examples in this manual assume that the OTP installation directory is /otp1.0, and that the /otp1.0 directory has been NFS-mounted as described in the next step.

  10. NFS-mount the Open Telecommunications Platform installation directory.

    1. Add the fully-qualified path name of the Open Telecommunications Platform installation directory to the /etc/dfs/dfstab file.

      For example, if you moved the directory otp1.0 to the root file system, you would add the following line to the file /etc/dfs/dfstab:

      share -F nfs -o ro,log=global -d "OTP 1.0 Installation Directory" /otp1.0

      This eliminates the need to type long directory path names during installation.

      Note –

      The /otp1.0 directory is referred to throughout this document as the OTP installation directory.

    2. Type svcadm restart nfs/server to stop and then restart NFS and NFS-mount the Open Telecommunications Platform installation directory.

Next Steps

Disk Drive Partitioning Requirements

The following table lists the partitioning requirements for the disk drive of each server within your OTP system.

Table 3–1 OTP System Server Disk Partition Requirements

Slice 

Partition 

Size 

0 

/ (root)

All remaining free space on the disk after allocating space for slices 2 through 7. 

1 

swap

Two to three times total system ram, or 4 Gbytes, whichever is greater. 

2 

overlap 

The entire system disk. 

3 

/globaldevices

512 Mbytes minimum. 

The OTP high availability framework later assigns this slice a different mount point and mounts the slice as a cluster file system. 

Note –

/globaldevices can reside on any unused slice on any disk on the server. Failure to allocate /globaldevices on an OTP systemwill cause Open Telecommunications Platform to fail.

4 through 6 

unused 

Not used. 

7 

Solaris Volume Manager 

20 Mbytes 

Used by Solaris Volume Manager software for the state database replica. 

Installing and Configuring Solaris 10 Update 2 Operating System

This section provides the procedures for installing Solaris 10 Update 2 on the server or servers you chose for the OTP system. Solaris 10 Update 2 must be installed and configured on each OTP system server before installing the Open Telecommunications Platform software on each server.

If you use an external OTP installation server to install the Open Telecommunications Platform software, you must also install and configure Solaris 10 Update 2 on the external server as well.

This section discusses the following topics:

ProcedureTo Install Solaris 10 Update 2 on the Open Telecommunications Platform Servers

Before You Begin

  1. When prompted for the Type of Install, choose Custom Install.

  2. When prompted to provide the Ethernet port selections, assign the IP addresses, netmask, and gateway values according to your network architecture.

  3. When prompted for the Software Group, choose Entire Distribution Plus OEM.

    Caution – Caution –

    If you do not choose Entire Distribution plus OEM, Open Telecommunications Platform installation and configuration will fail.

  4. When prompted for disk selection, choose all available disks.

  5. When prompted to lay out file systems, partition the system disk according to the requirements listed in Table 3–1.

Next Steps

When Solaris 10 Update 2 installation has completed and the server has rebooted, perform each of the following procedures in sequence to configure the operating environment.

ProcedureTo Update the /etc/default/nfs file

The Open Telecommunications Platform supports only NFS version 3. To ensure system integrity and availability, update the /etc/default/nfs file as follows:

  1. log in as root (su - root) to the server.

  2. Add the following line to the file /etc/default/nfs:

    NFS_SERVER_VERSMAX=3

  3. Save and close the /etc/default/nfs file.

Next Steps

Update the /etc/hosts file as described in the next procedure.

ProcedureTo Update the /etc/hosts file

The IP address and the name of the server must be added to the /etc/hosts on that server. Failure to add the IP address and name will cause Open Telecommunications Platform installation to fail.

  1. Log in as root (su - root) to the server.

  2. Verify that the /etc/hosts file has entries for loopback and the server primary and secondary Ethernet interfaces.

    1. Make certain that either of the following loopback entries is in the /etc/hosts file.

      127.0.0.1    localhost

      or

      127.0.0.1    localhost.localdomain    localhost

    2. Make certain that an entry exists for the server primary and secondary Ethernet IP address.

      For example:

      111.11.111.11 server_name_interface1.domain_name
111.11.111.22 server_name_interface2.domain_name

      where:

      • 111.11.111.11 is the IP address of the primary Ethernet interface

      • server_name_interface1 is the primary name of the server being configured such as the external OTP installation server, the first OTP host, or the additional OTP host

      • 111.11.111.22 is the IP address of the secondary Ethernet interface

      • server_name_interface2 is the secondary name of the server being configured

      • domain_name is your corporate domain name

      The /etc/hosts should be similar to the following example, where server_name.company.com 

      127.0.0.1    localhost.localdomain    localhost
10.11.123.15 management-server.company.com
10.11.123.16 management-server-port2.company.com

    3. Save and close the /etc/hosts file.

  3. Reboot the server.

Next Steps

Ensure port 162 is not in use as described in the next procedure.

Procedure(Optional) To Determine Whether Port 162 is in use

The OTP system management service requires exclusive use of port 162 for SNMP trap notifications. To determine if port 162 is assigned to any process, proceed as follows:

  1. log in as root (su - root) to the server.

  2. Type grep 162 /etc/services to determine whether port 162 has been assigned to a process.

    • If only the command prompt is returned, then port 162 has not been assigned to a process. No further action is required.

    • If port 162 is assigned to a process on the server, then results similar to the following are displayed:


      # grep 162 /etc/services
snmpd     162/udp    daemon name     #daemon description

      You must disable the daemon or the application that is using port 162. To disable a daemon, refer to the operating system documentation. To disable an application that is using the port, refer to the application documentation.

Next Steps

Enable FTP on the server as described in the next procedure.

Procedure(Optional) To Enable FTP

To manage clustered OTP systems, you must enable the FTP service as follows.

  1. Log in as root (su - root) to the server.

  2. Type the command svcadm -v enable network/ftp.

    The FTP service is enabled, and starts when the server is rebooted. After the system is rebooted, you can verify whether the FTP service has start using the inetadm command:


    # inetadm
enabled   online         svc:/network/telnet:default
enabled   online         svc:/network/nfs/rquota:default
disabled  disabled       svc:/network/echo:dgram
disabled  disabled       svc:/network/time:stream
enabled   online         svc:/network/ftp:default
Next Steps

Installing the Open Telecommunications Platform Patches on Sun Fire T2000 Servers

ProcedureTo Install Required Patches on Sun Fire T2000 Servers

Before You Begin

Refer to OTP System Hardware and Firmware Requirements for the list of required patches and firmware versions for the T2000 server and storage devices, and to the hardware documentation for firmware validation and update procedures. All firmware must be at the required level on the T2000 and on the storage devices prior to installing the Open Telecommunications Platform.

  1. log in as root (su - root) to the Sun Fire T2000.

  2. Open a web browser and download the following two patches from http://sunsolve2.central.sun.com/pub-cgi/show.pl?target=patches/patch-access.

    • 118833-24

    • 123334-04

  3. Change directory to the directory in which you downloaded the T2000 patches.

  4. Type patchadd 118833-24 to install the first patch.

    Wait for patch installation to complete.

  5. Type patchadd 123334-04 to install the second patch.

    Wait for patch installation to complete.

  6. Type reboot -- -sx to reboot the T2000 in single user mode.

    Wait for the T2000 to finish rebooting.

  7. Type /usr/sbin/e1000g_transition -e -f to complete the transition to the e1000g driver.

  8. Type reboot.

Next Steps

Ensure that the /globaldevices file system has been created on each clustered OTP system as described in the next section.

Creating the /globaldevices File System on the OTP System Servers

If you have not partitioned each clustered OTP system server's hard drive to include the /globaldevices file system as described in Table 3–1 during installation of the operating system, then you must create and configure the /globaldevices file system on each server in order to enable management of global devices.

The OTP high availability framework requires the /globaldevices file system on one of the local disks on each clustered OTP system server's hard drive. The /globaldevices file system is later mounted as the OTP cluster file system.

For further information about global devices, see the Sun Cluster Concepts Guide for Solaris OS. For information on planning for the global devices file system, see Sun Cluster Software Installation Guide for Solaris OS.

Skip the following procedure If you have already created a /globaldevices file system containing at least 512 Mbytes on the hard drive of each of the clustered OTP systems.

ProcedureTo Create the /globaldevices File System on the OTP SystemServers

If you have not allocated the /globaldevices file system on one of the local disks on each clustered OTP system server, then you must perform the following procedure on each server in the clustered OTP system.

  1. Log on to the server as root (su - root)

  2. Type newfs /dev/dsk/c0t0d0s3 to create the cluster file system

    Note –

    In this step and the following steps, the file system is mounted on disk slice 3. You can create and mount the file system on any available slice.

    If the server has more than one disk, the /globaldevices file system can be created on a disk other than the disk containing the root file system.

  3. Add the following line to the file /etc/vfstab.

    /dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s3   /globaldevices   ufs   2   no   global,logging

  4. Type mkdir /globaldevices to create the cluster global devices directory.

  5. Type mount /globaldevices to mount the /globaldevices file system

Next Steps

Install the Open Telecommunications Platform on each of your OTP system servers using either of the following two methods: