Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Installing and Configuring Red Hat (CentOS) Linux

    This section provides information about installing and configuring Red Hat (CentOS) Linux for the PSM server.

    Before You Install Red Hat (CentOS) Linux

    Obtain the following information from your IT department before installing Red Hat (CentOS) Linux.

    • the IP address for the server where the operating system will be installed
    • the system name
    • the domain name
    • the subnet mask
    • the gateway
    • the DNS server
    • the proxy server if applicable (see below)

    Note: Before installing any software, consult the proNX Service Manager Release Notes for this release. The proNX Service Manager Release Notes contains important information relating to installing and upgrading software for this release, and may require you to take additional steps prior to or after executing the procedures in this section.

    Running with a Proxy Server

    If the machine that you're installing the PSM server on is located behind a proxy, you must make changes to the following configuration files in order for the installation to proceed properly:

    • wgetrc - The wget command is used by the installation script supplied by Juniper Networks to download files. The wget command needs to know that it's running behind a proxy. The recommended approach is to modify the wget configuration file, /etc/wgetrc for the system or ~/.wgetrc for an individual user, by adding the following lines:
      use_proxy=on
      http_proxy=proxy_host_or_ip:proxy_port
      proxy_user=username
      proxy_password=password
      
    • curlrc - The curl command is used by the installation script supplied by Juniper Networks to download files. The curl command needs to know that it's running behind a proxy. The recommended approach is to modify the curl configuration file, ~/.curlrc, by adding the following line:
      proxy=http://username:password@proxy_host_or_ip:proxy_port
      

    Installing and Configuring Red Hat (CentOS) Linux, 64-bit, for the PSM Server

    Use this procedure to install and configure Red Hat (CentOS) Linux, 64-bit, from an installation DVD.

    • See PSM Server Requirements.
    • Obtain the installation DVD for Red Hat (CentOS) Linux.
    • Obtain the PSM DVD or ISO image.
    • Obtain the information specified in Before You Install Red Hat (CentOS) Linux.
    • Ensure the server machine is physically connected to a LAN and is able to access the Internet.
    • Ensure the system is bootable from the DVD drive.
    • Ensure the SATA mode in the BIOS is set to support AHCI instead of legacy. For some BIOSs, this may be called "Enable SATA AHCI Support".

    Note: Before starting this procedure, consult the proNX Service Manager Release Notes for this release. The proNX Service Manager Release Notes contains important information relating to installing and upgrading software for this release, and may require you to take additional steps prior to or after executing this procedure.

    Note: This procedure provides supplementary installation information on how to configure the operating system and/or software packages in order to run the PSM server application, and is not intended to replace the procedures provided by the operating system and/or software package suppliers.

    Note: This section uses examples to illustrate the installation procedure. The examples refer to IP addresses and software version numbers that may not match your particular network configuration or the current software release. Consequently, the output that you see may differ from what is shown in the examples.

    1. Insert the Red Hat (CentOS) Linux installation DVD and follow the on-screen instructions.

      Select the following options during the installation:

      • If the server has an existing Linux installation, specify that you want to perform a fresh installation. In some installations, this may appear as the Fresh Installation option.
      • Provision the network settings. In some installations, this may appear as the Network Configuration option. Specify a static IP address, netmask, hostname, default gateway, and DNS server. Ensure the Connect automatically option is selected and that the server machine is physically connected to the network.
      • Select the option to make use of all the disk space for the new installation. In some installations, this may appear as the Use All Space option. See NOTE below.
      • Select the minimal server installation option. In some installations, this may appear as the Minimal installation option.

      Note: It is recommended that you partition the disk such that the /home partition takes up only 15% of the total disk space. You should configure the / partition to take up the rest of the partitionable space. For RHEL (CentOS) 6, you can configure the partitioning by selecting Review and modify partitioning layout. For RHEL (CentOS) 7, you can configure the partitioning by selecting I will configure partitioning in the INSTALLATION DESTINATION window.

      For all other options, follow the on-screen instructions and/or use the defaults.

    2. Reboot the server and log in as root using the credentials you specified during the OS installation.
    3. Confirm that your network settings are correct.
      1. Check your network connectivity.

        Ping a known IP address in your network. For example:

        [root@psmdemo ~]# ping -c2 10.64.0.1
        PING 10.64.0.1 (10.64.0.1) 56(84) bytes of data.
        64 bytes from 10.64.0.1: icmp_seq=1 ttl=64 time=1.06 ms
        64 bytes from 10.64.0.1: icmp_seq=2 ttl=64 time=1.03 ms
        
        --- 10.64.0.1 ping statistics ---
        2 packets transmitted, 2 received, 0% packet loss, time 1002ms
        rtt min/avg/max/mdev = 1.037/1.049/1.062/0.034 ms
        
      2. Confirm your DNS server is working properly.

        Ping a well-known site to ensure the site name is resolved. For example:

        [root@psmdemo ~]# ping -c2 www.google.com
        PING www.google.com (173.194.43.113) 56(84) bytes of data.
        64 bytes from yyz08s10-in-f17.1e100.net (173.194.43.113): icmp_seq=1 ttl=57 time=7.73 ms
        64 bytes from yyz08s10-in-f17.1e100.net (173.194.43.113): icmp_seq=2 ttl=57 time=7.93 ms
        
        --- www.google.com ping statistics ---
        2 packets transmitted, 2 received, 0% packet loss, time 1009ms
        rtt min/avg/max/mdev = 7.736/7.833/7.930/0.097 ms
        

      If either of these steps fails, fix your network settings before proceeding.

    4. If you are installing Red Hat, you must register your computer, attach a subscription, and subscribe to the necessary channels before you can update your server machine from the Red Hat repositories. If you are installing CentOS, skip to 5.
      1. Register your subscription by using the subscription-manager register command and entering your Red Hat subscription username and password.
      2. Attach the subscription by using the subscription-manager attach --auto command.
      3. Subscribe to the options channel.
        • For Red Hat 6, use the following command:
          subscription-manager repos --enable=rhel-6-server-optional-rpms
        • For Red Hat 7, use the following command:
          subscription-manager repos --enable=rhel-7-server-optional-rpms
      4. Additionally, for Red Hat 7, you must subscribe to the extras channel by using the following command.
        subscription-manager repos --enable=rhel-7-server-extras-rpms
    5. Update the system packages.
      [root@psmdemo ~]# yum -y update
      
    6. Reboot the server and log back in as root.
    7. Add the server to the hosts file.

      Look in the /etc/hosts file and add the name of the server, the domain, and the IP address as one of the entries.

      For example, for a server named psmdemo:

      [root@psmdemo ~]# vi /etc/hosts
      [root@psmdemo ~]# cat /etc/hosts | grep psmdemo
      10.64.8.155 psmdemo.example.org psmdemo
      [root@psmdemo ~]#
    8. Ensure the date and time are set correctly.

      To verify the date, for example:

      [root@psmdemo ~]# date
      Mon Jan 13 09:28:54 EST 2014

      If the date and time are not set correctly, manually set the date and time. For example:

      [root@psmdemo ~]# date -s "Jan 21 14:38:00 2014 EST"

      Note: Alternatively, if NTP has been set up, you can use the ntpdate command to manually synchronize the time with an NTP server (for example, ntpdate us.pool.ntp.org). The ntpdate command can only be performed if you do not have an ntpd service running. If you do, then stop the service first by issuing the service ntpd stop command. In a new installation, NTP will not have been set up yet. NTP is set up as part of the psm-xxxxx.run script.

      Proceed to the next step only after the date and time are correct.

    9. Install an SSH client, such as openSSH.
      yum install openssh-clients

      This installs openSSH and its dependencies.

    10. Install the Extra Packages for Enterprise Linux (EPEL). EPEL contains packages that are required by the PSM server.
      1. For CentOS:

        The EPEL package is available through YUM.

        yum -y install epel-release
      2. For Red Hat:

        EPEL is part of the Fedora project, and can be installed as follows:

        rpm –ivh http://dl.fedoraproject.org/pub/epel/epel-release-latest-n.noarch.rpm

        where n is 6 for Red Hat 6, and 7 for Red Hat 7.

      Confirm by checking for the repository. For example:

      [root@psmdemo ~]# ls /etc/yum.repos.d/epel*
      epel.repo    epel-testing.repo
    11. Install the Oracle Java Development Kit.
      1. On a regular desktop or laptop, use your browser to go to http://www.oracle.com/technetwork/java/javase/downloads/index.html%20.
      2. Download the appropriate Java JDK RPM for Linux (jdk-xxxx-linux-x64.rpm for 64-bit). See PSM Server Requirements for the version to download.
      3. Transfer or copy the downloaded file to the server machine. You can use scp if transferring from a Linux machine, or you can use a Windows SCP application (for example, WinSCP) if transferring from a Windows machine.

        For example, using WinSCP on a Windows machine to transfer the JDK to the server machine:

      4. Install the Java RPM on the server machine.

        For example:

        [root@psmdemo ~]# ls jdk*
        jdk-7u45-linux-x64.rpm
        [root@psmdemo ~]# rpm -ivh jdk-7u45-linux-x64.rpm
        Preparing...           ################################## [100%]
           1:jdk               ################################## [100%}
        Unpacking JAR files...
                rt.jar...
                jsse.jar...
                charsets.jar...
                tools.jar...
                localedata.jar...
                jrxrt.jar...
        
      5. Check that Java has been installed.

        For example:

        [root@psmdemo ~]# ls /usr/java  
        default    jdk1.7.0_45    latest
        

        The Java installation directory is jdk1.7.0_45. The default and latest directories are softlinks.

    12. Run the psm-xxxxx.run script provided by Juniper Networks in the PSM ISO image. This script requires Internet access, and configures the operating system and installs the software packages required by the PSM server.

      Note: If you are installing the PSM server on a machine that is behind a proxy, ensure you have modified the appropriate configuration files as described in Before You Install Red Hat (CentOS) Linux.

      1. Insert the PSM DVD into the DVD drive of the server or copy the PSM ISO image onto the server.

        To copy the ISO image onto the server, you can use scp if transferring from a Linux machine, or you can use a Windows SCP application (for example, WinSCP) if transferring from a Windows machine.

      2. Create the mount directory on the server if it is not already created.

        For example:

        mkdir /media
      3. Mount the DVD or the ISO.

        To mount the DVD:

        mount -t iso9660 /dev/cdrom /media

        To mount the ISO:

        mount -t iso9660 -o loop xxx.iso /media

        where xxx.iso is the name of the ISO file (for example, PSM-7.5.0.iso).

      4. In the mount directory, look for the psm-xxxxx.run script and copy that file into the /root directory. xxxxx is the update version number, which varies from release to release.

        For example:

        [root@psmdemo ~]# cp /media/psm-15008.run .
      5. If necessary, change permissions on the script to allow it to be run.

        For example:

        [root@psmdemo ~]# chmod +x psm-15008.run
      6. Run the script.

        For example:

        [root@psmdemo ~]# ./psm-15008.run

        Here is sample output from one version of the script:

        By accepting this license you agree that you have read, understood and agree to be bound by and comply with the terms and conditions of this End-User Software License Agreement (this License or 'EULA'
                                        Please type y to accept, n otherwise: y
        Verifying archive integrity... All good.
        Uncompressing PSM Server Setup ..  100%
        
        Confirming distro is a Redhat variant:                     [  OK  ]
        Confirming script running as root:                         [  OK  ]
        Confirming hardware is x86 64 bit:                         [  OK  ]
        Confirming yum is available:                               [  OK  ]
        Confirming epel is provisioned:This system is receiving updates from Red Hat Subscription Management.
                                                                   [  OK  ]
        Confirming theres an uplink to the internet:               [  OK  ]
        Confirming hostname not localhost:                         [  OK  ]
        Confirming FQDN is known /etc/hosts (pingable):            [  OK  ]
        Installing Development Tools (be patient):                 [  OK  ]
        Installing base dependencies from yum (be patient):        [  OK  ]
        Installing epel dependencies (be patient):                 [  OK  ]
        Installing maven:                                          [  OK  ]
        Installing scripts and configuration files:                [  OK  ]
        Setup mysql backups:                                       [  OK  ]
        Setup monit configuration:                                 [  OK  ]
        Installing resty and friends:                              [  OK  ]
        Starting Performance metrics install:                      [  OK  ]
        Installing yum deps (be patient):                          [  OK  ]
        Installing Django 1.3.3:                                   [  OK  ]
        Installing django-tagging 0.3.1:                           [  OK  ]
        Downloading Whisper, Carbon and Graphite 0.9.9:            [  OK  ]
        Installing Whisper:                                        [  OK  ]
        Installing Carbon:                                         [  OK  ]
        Installing Graphite:                                       [  OK  ]
        Creating Graphite database:                                [  OK  ]
        PM installation complete:                                  [  OK  ]
        Confirming Oracle 1.7 Java installed:                      [  OK  ]
        Configuring Java:                                          [  OK  ]
        Configuring SNMP:                                          [  OK  ]
        Starting snmpd:                                            [  OK  ]
        Configuring NTP:                                           [  OK  ]
        Starting ntpd:                                             [  OK  ]
        Configuring ssh keys:                                      [  OK  ]
        Configuring OS:                                            [  OK  ]
        Configuring Monit:                                         [  OK  ]
        

        Note: All RPMs installed by the script, and all files created or updated by the script, are logged in /root/uninstall.log. The log is provided in case you want to manually uninstall the packages and/or remove the files that the script has installed. Because these packages and files are required for proper operation of the PSM server, you should only do this if you are no longer using this machine as a PSM server.

    13. Reboot the server.

      The reboot is necessary to ensure the path variables are set up properly.

    14. After the server reboots, log back in and verify that the $JAVA_HOME variable is correctly set to reference the newly installed Java directory (for example, jdk1.7.0_45). This reference may be through soft links..

      For example:

      [root@psmdemo /]# echo $JAVA_HOME
      /usr/java/default
      

    You have successfully installed and configured Red Hat (CentOS) Linux and all necessary packages for the PSM server.

    Modified: 2017-11-07