Installing the Red Hat operating system

  1. See the Red Hat documentation to install Red Hat Enterprise Linux 6.7 through latest 6.X or Red Hat Enterprise Linux 7.1 through latest 7.X.
    1. Make sure that these components are installed on the secondary computer:
      • Korn shell
      • /usr/lib64/

        The 64-bit version of a shared library that Ricoh ProcessDirector uses.

        • On Red Hat 6.7 through latest 6.X, the libraries are installed by
          • .so.6: libstdc++-4.4.7-16.el6.x86_64
        • On Red Hat 7.1 through latest 7.X, the libraries are installed by:
          • .so.6: libstdc++-4.8.5-4.el7.x86_64
        • The libraries are provided on the operating system installation media or can be downloaded from the Red Hat website.

      • Perl interpreter (Perl.rte 5.8.8 or later).
      • Zip and unzip utilities.
  2. Create Linux partitions and file systems. See Planning for file systems for recommendations and considerations.
  3. Run these commands and look for the expected results to verify that you installed Red Hat correctly:

    Red Hat commands and expected results

    Command Expected result
    To check the Red Hat release:

    cat /etc/redhat-release

    Red Hat 6.7 through latest 6.X:

    Red Hat Linux Enterprise Server release 6.x

    Red Hat 7.1 through latest 7.X:

    Red Hat Enterprise Linux Server release 7.x (Maipo)

    To verify that the operating system is 64-bit:

    uname -a

    Red Hat 6.7 through latest 6.X:

    Linux myserver 2.6.32-131.0.15.el6.x86_64 #1 SMP Tue May 10 15:42:40 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux

    Red Hat 7.1 through latest 7.X:

    Linux myserver 3.10.0-123.el7.x86_64 #1 SMP Mon May 5 11:16:57 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux

    To check the Korn shell level:

    rpm -q ksh

    Red Hat 6.7 through latest 6.X:

    ksh - 20100621-6.el6.x86_64

    Red Hat 7.1 through latest 7.X:

    ksh - 20120801-19.el7.x86_64

    To check for /usr/lib64/

    Go to /usr/lib64/ and type


    The list of files must include this exact entry:
    The list might link that entry to this one:
    To check the version of Perl that is installed:

    rpm -q perl

    Red Hat 6.7 through latest 6.X:


    Red Hat 7.1 through latest 7.X:


    To check the versions of zip and unzip that are installed:

    rpm -q zip

    rpm -q unzip

    zip-3.0-1.el6.x86_64 (typical)

    unzip-6.0-1.el6.x86_64 (typical)

    getconf GNU_LIBPTHREAD_VERSION Red Hat 6.7 through latest 6.X:

    NPTL 2.12

    Red Hat 7.1 through latest 7.X:

    NPTL 2.17

    To verify the RPM files that printer objects require:

    rpm -qa | grep system-config-printer

    The list of results should include:
    If you are going to print with AFP printers whose parent server is a secondary server, the portmap utility must be installed and running.

    rpcinfo -p

    A response that includes portmap, such as:
    program vers proto   port
    100000  4      tcp   111    portmapper
    • 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 the operating system tools to make sure that you have installed the required components (see step 1).

  4. Verify date, time, and time zone settings, and correct if necessary. To display the settings, type:


    Use the Time and Date Properties tool to correct the settings (including time zone) if necessary. To launch the tool, type:


  5. Set up networking based on system networking information:
    1. Make sure that Ricoh 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 Ricoh ProcessDirector primary and application/secondary computer on the network.
      • Ricoh ProcessDirector supports both IPv4 and IPv6 protocols. If you use IPv4, IP addresses can be expressed using dotted-decimal addresses or the fully qualified host name. If you use IPv6, you must use the fully qualified host name of the server.
    2. In your firewall, open any ports that Ricoh ProcessDirector uses. Depending on your configuration, you might need these ports:

      Port numbers

      Port number Used by
      111 User Name Mapping and Server for Network File System (NFS)
      515 LPD protocol
      2049 Server for NFS
      Assigned by your system administrator Network Information Service (NIS) file sharing
      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.

      6984–6992 InfoPrint Transform Manager or Ricoh Transform features

      If you want to use InfoPrint Transform Manager or the Ricoh Transform features, open these ports.

      15080 Ricoh ProcessDirector base product
      15090 Ricoh ProcessDirector Feature Manager
      15081 Ricoh Printer Connector services for Custom PDF printers
      15443 Ricoh ProcessDirector base product when SSL is enabled
      15453 Ricoh ProcessDirector Feature Manager when SSL is enabled
      16080 Default port for the Ricoh 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
  6. 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 For example: is

    2. From all application/secondary computers (if any), ping the primary computer.
    3. From the primary computer, ping all application/secondary computers.
    4. Contact the network administrator if you are not successful with any of these verifications.