test

Sun Open Telecommunications Platform 1.0 Installation and Administration Guide

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