Sun N1 System Manager 1.3 Site Preparation Guide

Management Server Configuration

This section provides the post-operating installation configuration procedures that must be performed before you can install the N1 System Manager 1.3 software.

Installing the Internationally Compliant Perl Module

N1 System Manager requires Perl version 1.5.3–16 or above to ensure correct functioning in any locale. This section provides the procedure for downloading and installing the internationally compliant Perl module.

ProcedureTo Download and Install the Internationally Compliant Perl Module

Steps
  1. Log in as root on the N1 System Manager management server.

  2. Open a web browser and find a site that provides the perl-5.8.3-16.i386.rpm file for download.

  3. Download the perl-5.8.3-88.4.i386.rpm file to a directory on the management server.

  4. In a terminal window, change directory to the location where you saved the RPM file.

  5. Type rpm -i --force perl-5.8.3–16.i386.rpm to install the Perl module.

Next Steps

Ensure port 162 is not in use on the management server as described in the next section.

Ensure Port 162 is not in Use

N1 System Manager requires exclusive use of port 162 for SNMP trap notifications. To determine if port 162 is assigned to any process, proceed as follows:

ProcedureTo Determine Whether Port 162 is in use

Steps
  1. Log in as root on the management 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 management server, then results similar to the following are displayed:

      • Solaris:


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


        # grep 162 /etc/services
        snmp    162/TCP   #Simple Net Mgmt Proto
        snmp    162/UDP   #Simple Net Mgmt Proto

      You must disable the daemon or 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 management server as described in the next section.

Enabling FTP on the Management Server

If you plan to manage SPARC-based manageable servers, you must enable the FTP service on the management server.

ProcedureTo Enable FTP on a Solaris Based Management Server

Steps
  1. Log in to the management server as root.

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

    The FTP service is enabled, and starts when the management 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

Update the /etc/hosts file as described in Updating the /etc/hosts File

ProcedureTo Enable FTP on a Linux Based Management Server

Steps
  1. Log in to the management server as root.

  2. Create symbolic links to the /etc/init.d/vsftpd file in the /etc/rc3.d and /etc/rc5.d directories.

    For example:


    # ln -s /etc/init.d/vsftpd /etc/rc3.d/S99vsftpd
    # ln -s /etc/init.d/vsftpd /etc/rc5.d/S99vsftpd
    

    The FTP service is enabled, and starts when the management server is rebooted. After the system is rebooted, you can verify whether the FTP service has started by using the ps and grep commands:


    # ps -eaf | grep ftp
    root    3035    1  0  16:27 ?    00:00:00 /usr/sbin/vsftpd /etc/vsftpd/vsf
Next Steps

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

Updating the /etc/hosts File

The IP address and the name of your management server must be added to the /etc/hosts. Failure to add the IP address and name will cause Sun N1 System Manager installation to fail.

ProcedureTo Update the /etc/hosts file

Steps
  1. Log in as root to the Sun N1 System Manager management server.

  2. Verify that the /etc/hosts file has entries for loopback and the management server.

    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 management server and its IP address. For example:

      111.11.111.11 n1mgmt.domain n1mgmt.domain

      where 111.11.111.11 is the IP address of the management server, and n1mgmt is the name of the management server and domain is your company domain name.

      Your /etc/hosts should be similar to the following example:

      127.0.0.1    localhost.localdomain    localhost
      10.5.157.123 n1mgmt.company.com
      
    3. Save and close /etc/hosts.

  3. Reboot the N1 System Manager management server.