Interstage Big DataParallel Processing ServerV1.0.0 User's Guide

2.3.3 Installing Mandatory Software

Install the software indicated in "2.1.2.3 Mandatory Software" on the master server, slave server, development server, and collaboration server.

The following explains the mandatory software settings requiring particular attention.

2.3.3.1 Obtaining and Setting Up the Mandatory Software

Obtaining mandatory software

• Obtaining and deploying the Microsoft LAN Manager module

  This task is required on only the primary server, not the secondary server.

  Obtain the Microsoft LAN Manager module from the FTP site shown below.
  Note that the Microsoft LAN Manager module can be used regardless of the CPU architecture (x86, x64).

  URL:
  	ftp://ftp.microsoft.com/bussys/clients/msclient/DSK3-1.EXE (as of June 2012)

  If this product is being installed in an environment where ServerView Deployment Manager is installed, it is not necessary to obtain the Microsoft LAN Manager module.

  The obtained module must be expanded in advance under the Windows of the CPU architecture (x86) by means of the Expand command. Refer to the example below for the expansion method.

  Example

  If dsk3-1.exe is deployed to C:\temp:

  > cd /d c:\temp
  > dsk3-1.exe
  > Expand c:\temp\protman.do_ /r
  > Expand c:\temp\protman.ex_ /r

  Use Windows 8.3 format (*1) for folder and file names.

  The expanded Microsoft LAN Manager module is no longer required after the Manager is installed.

  *1: The rules are a maximum of eight characters for the file name part and a maximum of three characters for the extension part.

  
  

  Place the following expanded modules in the work directory (/tmp) of the system being installed:

  • PROTMAN.DOS

  • PROTMAN.EXE

  • NETBIND.COM

Mandatory software settings

• SNMP trap daemon settings

  This task is required on only the primary server, not the secondary server.

  In order for this product to operate correctly, the net-snmp package must be installed and the setting below must be added to the /etc/snmp/snmptrapd.conf file. If the file does not exist, create the file, and then add the following setting:

  disableAuthorization yes

• kdump settings

  1. Check kdump

     Check that the kdump server function can be used. If it cannot be used, make it usable. Use the runlevel command and the chkconfig command to perform the checking operation.

     • Use the runlevel command to check the current run level.

       Example

       In the following example, the current run level is 3.

       #/sbin/runlevel <Enter>
       N 3

     • Use the chkconfig command to check the kdump usability status.

       Example

       In the following example, the current run level 3 kdump is off.

       #/sbin/chkconfig --list kdump <Enter>
       kdump 0:off 1:off 3:off 4:off 5:off 6:off

     • If kdump is off at the current run level, use the chkconfig command to switch it on, then use the service command to start kdump.

       #/sbin/chkconfig kdump on <Enter>
       # /sbin/service kdump start