Interstage Big DataParallel Processing ServerV1.0.0 User's Guide

2.3.2 Performing Advance Preparations for Installing Servers

This section describes the advance preparations required before installing this product.

• Server BIOS settings

  Refer to "Server BIOS settings".

• File system when installing the OS

  Refer to "File system when installing the OS".

• System parameter settings

  Refer to "System parameter settings".

• Firewall settings

  Refer to "Firewall settings".

• Host name settings

  Refer to "Host name settings".

• Public LAN network interface settings
  Refer to "Public LAN network interface settings".

• System time settings

  Refer to "System time settings".

• Mandatory software preparations and checking

  Refer to "Mandatory software preparations and checking"

Server BIOS settings

To introduce another slave server by cloning, it is necessary to set the BIOS settings of the slave servers as follows.

System BIOS

Set the boot sequence as follows.

1. Booting from the network interface used in the admin LAN (the first network interface)

2. Booting from DVD-ROM or CD-ROM (if a DVD-ROM or CD-ROM is connected)

3. Booting from storage

Note

• Do not change the boot sequence even if operation is started from the managed server and then booted from the disk.

• If "UEFI" and "Legacy" are displayed when setting the boot from the network interface, select "Legacy".

File system when installing the OS

To introduce another slave server by cloning, it is necessary to make the file system type "EXT3" when installing the OS on the slave server.

If the file system type used is "LVM (Logical Volume Manager)", it is not possible to introduce a slave server using cloning. Install the OS with the file system type "EXT3".

System parameter settings

The system parameters must be tuned. Refer to "A.4 Tuning System Parameters" for the method for setting tuning settings, and tune the master server system parameters.

Firewall settings

If this product is installed in an environment where firewall functions are used, the required communications (ports) must be authorized in the firewall function.

Refer to the operating system manual for the method for authorizing the required communications (ports) in the firewall function. Refer to "A.3 Port List" for the ports used by this product, and ensure connection is authorized.

Host name settings

For correct operation on the master server, slave server, development server, and collaboration server, it is necessary to set the host name (the official host name output by a command such as the "hostname" command) of the public LAN used by Hadoop.

The host names of the servers must have 11 alphanumeric characters with the first character being alphabetical. The names must be entered in the hosts file of the master server.

Make sure the hosts file on the primary and secondary master servers match.

Also add the host name information added to the master server to the hosts files of the slave server, development server and collaboration server.

hosts file

/etc/hosts

Refer to the help for "hosts" for information on the hosts file.

Note

Note the following if registering a local host in the hosts file.

• If setting a local host name for "127.0.0.1", it is essential to first enter an IP address that can be referenced remotely. Alternatively, do not set a local host name for "127.0.0.1".

• Do not use an alias for the host name.

In the following example, the host name "master1" having the IP address "10.10.10.10" is set.

10.10.10.10 master1
127.0.0.1 localhost.localdomain localhost

Public LAN network interface settings

Before this product is installed the IP address must be set for the public LAN network interface of each server, and the interfaces must be in the active state.

Use the ifconfig command to check the status of the targeted network interfaces. If settings are not yet set or if the status is inactive, set the IP address and make the interface active.

Example

# ifconfig eth5 <Enter>
eth5      Link encap:Ethernet  HWaddr 00:19:99:8D:7E:90
          inet addr:10.10.10.11  Bcast:192.168.1.255  Mask:255.255.255.0
          ... omitted ...
          RX bytes:2440357552 (2.2 GiB)  TX bytes:1144015405 (1.0 GiB)
          Memory:cd400000-cd480000

System time settings

Use NTP (Network Time Protocol) to set the system times of the master servers, slave servers, development servers and collaboration servers to the same time.

Mandatory software preparations and checking

Before installing this product, check that the software in "2.1.2.3 Mandatory Software" is installed in the system. If not installed, it must be installed before installing this product.

Note

ServerView Agent settings

In order for this product to operate correctly with the PRIMERGY Series, set the required SNMP service settings during ServerView Agent installation.

Refer to the ServerView Agent manual for the method for setting the SNMP service.

• For the SNMP community name, set the same value as the SNMP community name set in the iRMC.

• Set Read (reference permission) or Write (reference and update permission) for the SNMP community name.

• Set the master server admin LAN IP address as the host that receives SNMP packets.

• Set the master server IP address as the SNMP trap send destination.

• If the master server that is the SNMP trap send destination has multiple NICs, set the IP address of the admin LAN of the side connected to the slave servers.