Conventions Used in This Document .................................................................................................................... 5
Notations used in the text .............................................................................................................................. 5
Optical disk drive ........................................................................................................................................... 5
Hard disk drive .............................................................................................................................................. 5
Abbreviations of Operating Systems (Linux) ................................................................................................. 5
POST ........................................................................................................................................................... 6
Chapter 1 Installing Operating System ............................................................................................................... 9
1.
Before Starting Setup ...................................................................................................................................... 10
1.1
Supported Linux OS ............................................................................................................................. 10
1.2
Overview of Setup ................................................................................................................................ 10
2.
Setting up ........................................................................................................................................................ 11
Preparation for software .......................................................................................................... 18
2.3
OS Setup .............................................................................................................................................. 20
2.3.1
Installing Red Hat Enterprise Linux 7.2.................................................................................... 20
2.3.2
Installing the recommended package ...................................................................................... 31
2.3.3
Installing the required package ................................................................................................ 32
Bundled Software for the Server ..................................................................................................................... 62
1.1
NEC ESMPRO Agent (Linux) ............................................................................................................... 62
2.
Bundled Software for "PC for Management" ................................................................................................... 63
2.1
NEC ESMPRO Manager ...................................................................................................................... 63
Revision Record .................................................................................................................................................. 65
In addition to safety-related symbols urging caution, three other types of notations are used in this document.
These notations have the following meanings.
Important Indicates critical items that must be followed when handling hardware or operating software. If
the procedures described are not followed, hardware failure, data loss, and other serious
malfunctions could occur.
Note Indicates items that must be confirmed when handling hardware or operating software.
Tips Indicates information that is helpful to keep in mind when using this server.
Optical disk drive
This server is equipped with one of the following drives. These drives are referred to as optical disk drive in this
document.
DVD Super MULTI drive
Hard disk drive
Unless otherwise stated, hard disk drive described in this document refers to both of the following.
Hard disk drive (HDD)
Solid state drive (SSD)
Abbreviations of Operating Systems (Linux)
Linux Operating Systems are referred to as follows.
See Chapter 1 (1.1 Supported Linux OS) in Installation Guide (Linux) for detailed information.
Notations in this document Official names of Linux
1. Unauthorized reproduction of the contents of this document, in part or in its entirety, is prohibited.
2. This document is subject to change at any time without notice.
3. Do not make copies or alter the document content without permission from NEC Corporation.
4. If you have any concerns, or discover errors or omissions in this document, contact your sales
representative.
5. Regardless of article 4, NEC Corporation assumes no responsibility for effects resulting from your
operations.
6. The sample values used in this document are not the actual values.
Keep this document for future use.
Latest editions
This document was created based on the information available at the time of its creation. The screen images,
messages and procedures are subject to change without notice. Substitute as appropriate when content has
been modified.
The most recent version of the guide, as well as other related documents, is also available for download from
the following website.
http://www.nec.com/
Safety notes
To use this server safely, read thoroughly Safety Precautions and Regulatory Notices that comes with your
server.
This section describes overview of setup and precautions on installing an OS.
1. Before Starting Setup
Important
OS is not installed to this machine at purchasing. The system must be set up
after purchasing. Refer to this document while the system is set up again.
The target reader of this manual is a customer w ho has a basic knowledge of
Linux.
1.1 Supported Linux OS
This machine is compatible with the BIOS boot mode and installation due to the minor release.
Boot mode
Minor release (architecture)
UEFI Legacy
Red Hat Enterprise Linux 7.2(x86_64)
Note For setting of the BIOS boot mode, see "Chapter 3 (1. System BIOS)" in "Maintenance
Guide".
: Supported : Not Supported
-
1.2 Overview of Setup
This document describes how to set up the system by starting up the OS standard insta ller from the RHEL7.2
install media and installing it. The installation parameter of RHEL7.2 is input on the interactive installation
program provided by Red Hat. After installing RHEL7.2, install application programs including the ft control
software manually. Setup by using"EXPRESSBUILDER" coming with this product is not allowed.
Important This document describes the procedure for establishing the environment
recommended by NEC. If customers customize the system, full y study the system
configuration in advance, and replace the description as required to set up the
system.
3. Perform the preparation process for the server as shown below.
– Disconnect all LAN cables.
– Disconnect the cable from the connector on an SAS board if it is installed.
– Disconnect the cable from the connector on a Fibre Channel board if it is installed.
– Disconnect the USB cable if an USB device for Backup (i.e. external/internal RDX) is connected
to USB port.
– Install one hard disk drive in slot 0 of CPU/IO modules 0 and 1, respectively.
Important
4. Make sure that preparations for setup on CPU/IO modules 0 and 1 are ready.
As shown in the previous figure, install one hard disk drive in slot 0 of CPU/IO module 0 and another
one in slot 0 of CPU/IO module 1. Do not install any hard disk drive in any other slots than specified.
2. Setting up
Install only one hard disk drive in the slot specified here.
If the hard disk drive is not a new one, physically format it. See Chapter 3 (3. SAS
Configuration Utility) in Maintenance Guide for physical formatting.
5. Connect power cords to the server in the following order.
(1) Connect a power cord to AC inlet A.
(2) Connect a power cord to AC inlet B.
(3) Make sure the PRIMARY LED on CPU/IO module 0 is lit.
Note If you disconnect the power cord, wait at least 30 seconds before connect it again.
After performing step (1), wait for 15 seconds or longer, and then perform step (2).
Before starting setup process, the OS boot monitoring feature needs to be disabled.
Important Be sure to disable OS boot monitoring feature before setting up the system for
2. Setting up
successful setup. This function is enabled by shipping default. If this setting is valid,
setup cannot be performed correctly.
Tips
For details of operations for BIOS Setup Utility and parameters for boot monitoring feature,
see Chapter 3 (1. System BIOS) in Maintenance Guide.
1. Turn on the display and the peripheral equipment connected to the server.
Note If the power cords are connected to a power controller like a UPS, make sure that it is
powered on.
2. Remove the front bezel.
3. Press the POWER switch located on the front side of the server.
Note Check that the module POWER lamps of the CPU/IO module 0 and CPU/IO module 1 are
blinking, and then turn the POWER switch of this system on.
Lift the acrylic cover, and press the POWER switch.
Important Do not turn off the power before the "NEC" logo appears.
14
Acrylic cover
POWER switch
After a while, the "NEC" logo will appear on the screen.
Tips
While the "NEC" logo is displayed on the screen, the server performs a power-on self test
(POST) to check itself. OS starts upon completion of POST.
For details, see Chapter 3 (1.1 POST) in User’s Guide.
Note
If the server finds errors during POST, it will interrupt POST and display the error message.
See Chapter 1 (6.2 POST Error Message) in Maintenance Guide.
6. Among the parameters, choose Disabled and press Enter.
When the <Enter> key is pressed, the current display of the configuration for OS Boot Monitoring will
be changed to "Disabled".
7. Now OS Boot Monitoring setting is completed.
Continue to check Boot Mode Settings in next procedure (2.2.3 Checking Boot Mode Settings).
Important In Samba included in the RHEL7.2 installation media, the vulnerability
2. Setting up
output an error message repeatedly at startup of OS, and the operation may stall.
This problem has been corrected in dracut-033-360.el7_2 or later.
amount of error messages may be output to the system log. The correction package
has not been provided as of April 2016. Downgrade the file to nfs-utils-1.3.0-0.8.el7.
for a customer, it is not required to obtain this file.
(CVE-2015-5370, CVE-2016-2118, and other 6 cases, known as BADLOCK) that has
an extremely serious impact has been found out. Installation of the DCE/RPC
protocol of samba is vulnerable, and the samba server may crash, and the desired
code may be executed in case of the illegal use. This problem has been corrected in
samba-4.2.10-6.el7_2 or later.
Tips If Samba included in the RHEL7.2 installation media is not installed due to customization
for a customer, it is not required to obtain this file.
Accessories of the server
– Installation Guide (Linux) (This manual)
– ft Server Control Software 11.0.2 for Red Hat Enterprise Linux 7.2 Install CD
Prepare the following as needed:
– Environment that allows writing to DVD (for creating install media)
– A blank DVD (for creating install media or storing correction package)
Registration to Red Hat Network
(2)
To use Red Hat Enterprise Linux, you must have RHN-ID (registration number for Red Hat Network). If you do
not have RHN-ID or it has expired, the software channel corresponding to subscription is not displayed.
Install Red Hat Enterprise Linux 7.2 according to the following procedure.
1. Turn the power of this system ON, and then set the RHEL7.2 installation media to the optical disk drive.
2. The boot screen appears. Select [Test this media & install Red Hat Enterprise Linux 7.2] if you check the
installation media. If you do not check the installation media, select [Install Red Hat Enterprise Linux 7.2].
Then, press the <Enter> key.
This document describes the procedure for establishing the environment
recommended by NEC. If customers customize the system, fully study the
system configuration in advance, and replace the description as required to set
up the system.
It is recommended to make a backup copy of user data as needed.
Tips If nothing is input for a certain amount of time, [Test this media & install Red Hat
Enterprise Linux 7.2] is selected automatically, and the next screen appears after
executing the installation media check.
It is recommended to check the installation media for a problem. Checking the media
takes several or several tens of minutes.
3. The screen to select language and keyboard appears. Select [English], and click [Continue].
7. The "SOFTWARE SERECTION" screen appears. Select [Server with GUI] for "Base Environment", select the
module marked with for "Add-Ons for Selected Environment", and click [Done].
Tips The required package for the ft control software is automatically installed. See Chapter
8. Click [INSTALLATION DESTINATION].
2. Setting up
1 (2.3.3 Installing the required package) of this manual.
Select [Server with GUI] for "Base Environment" to use the graphical target (graphical
login mode).
For the specified base environment or packages included in add-on, check the
"repodata/*-comps-Server.x86_64.xml" file of the installation media. This file describes
the available environment (<environment> tag) and add-on (<group> tag) in the XML
format.
The installation media includes the package group and package that cannot be
installed from the Red Hat installation program selection screen. For the package group
and how to add the package, see Chapter 1 (3.1 Adding the Package Group and
Package) of this manual.
If [Minimal Install] is selected, the required hard disk drive capacity is 5 GB. I all the
selectable add-ons are selected, the capacity is 10 GB.
9. Select 2 units of the devices at the installation destination from the local standard disk, select [[I will configure
partitioning], and click [Done].
*5 The following table shows the recommended swap partition size in accordance with the memory space
mounted in this machine.
Mounted memory space swap partition size
8 GB or less Mounted memory space
More than 8 GB and 64 GB or
less
More than 64 GB Depends on the workload.
Note If the mounted memory space is larger, swap is hardly used in some cases. Determine
*6 The partitions can be created freely in this free space. For the procedure for adding the partitions, see
the following sections.
- Chapter 1 (3.3 Adding Partitions) in this manual
- Chapter 1 (3.4 Expanding the swap Area) in this manual
Important
2. Setting up
Half of the mounted memory
space
the size according to the purpose of using the system and the workload during the
operation.
The free command enables you to check the swap use status during the operation. If
the usage rate of swap is higher, expand the swap area and add the memory.
For the partitions created by all the built-in hard disks, the software RAID1
consisting of the CPU/IO module 0 and CPU/IO module 1 with the same slot
numbers must be configured. Only RAID1 is supported for the built-in hard disk
including the system partition. RAID1 or RAID1+0 is supported for the built-in
hard disk excluding the system partition. For the built-in hard disk excluding the
system partition, see Chapter 2 (1. Hard Disk Drive Duplexing) in the
maintenance manual.
The built-in hard disk including the system partition does not support the use of LVM.
Configure RAID1 or RAID1+0 before using the built-in hard disk excluding the system
partition. Please note that the configuration to create RAID furthermore on the LVM
logical volume is not supported. LVM provides the advanced storage function and the
procedure for management or recovery in case of a failure is complex. It is
recommended to use LVC only if it is required.
Tips The number of the partition created during the installation is automatically allocated by
the Red Hat installation program. Therefore, the numbers may not be allocated in the
same order as creation of the partition.
Use the parted command or df command to display the partition information or free
The "ADD A NEW MOUNT POINT" screen appears. Set [Mount Point] and [Desired Capacity], and click [Add
mount point].
Important
Note
Tips
For [Device Type], make sure to select “RAID1 (Redundancy)” for [RAID Level], and set [File System]. Create
all partitions according to the same procedure.
2. Setting up
Do not allocate the /usr partition to the partitions other than the / (root) partition
since the boot process becomes complex.
As the mount point of EFI System Partition , be sure to set /boot/efi.
If [Desired Capacity] is blank, all the remaining spaces are used.
22. The "LICENSE INFORMATION" screen appears. Read the license terms and conditions. If you agree to the
terms, select [I accept the license agreement.] in agreement, and click [Done].
2. Setting up
23. Click [FINISH CONFIGURATION].
2.3.2
Installing the recommended package
Individually install the package recommended by NEC according to the following procedure.
1. Log in to the server as the root user. If you login with graphical mode, select [Others...] to login.
2. Install the following packages additionally by using the yum command. For how to add the package, see
Chapter 1 (3.1 Adding the Package Group and Package)of this manual.
3. Remove the ft control software installation CD from the optical disk drive, and insert the RHEL7.2
installation media. The package is mounted automatically after a while.
4. Execute the following command to install the package.
# /tmp/pkginst.sh
5. After installation is completed, the following message appears.
2. Setting up
The package may not be mounted automatically depending on the environment. Mount it to
the desired position in this case. If the mounting destination is different, replace it as
required.
The install has completed.
6. Remove the RHEL7.2 installation media from the optical disk drive.
2.3.4
Applying Initial Configuration Script
Initial Configuration Script provides various settings for stable operation of the system. Be sure to apply the
initial configuration script according to the steps below.
See Chapter 1 (4.1 Processing detail of initial configuration script) for details of initial configuration script.
1. Set the ft Server Control Software Install CD to optical disk drive. After a while, the drive will be
automatically mounted.
Tips
If the optical disk drive is not mounted automatically depending on your environment,
mount it on the desired location manually. If the mount destination differs, substitute it for
the actual destination appropriately.
2. Run the following command to apply initial configuration script.
# /run/media/root/FT1102052/ftsys/nec_setup.sh
3. The following message appears when the configuration is applied. The system needs to be
rebooted, however, proceed to the next step.
Follow the steps below to install ft Server Control Software.
1. Login the system with root user. If you login with graphical mode, select [Others...] to login.
2. Set the ft Server Control Software Install CD to optical disk drive. After a while, the drive will be
automatically mounted.
2. Setting up
Tips
If the optical disk drive is not mounted automatically depending on your environment,
mount it on the desired location manually. If the mount destination differs, substitute it for
the actual destination appropriately.
3. Run the following command to install ft Server Control Software.
# /run/media/root/FT1102052/ftsys/install.sh
4. The following message appears when installation completes. Press the <Enter> key to reboot the
system.
Enter YES to reboot now or NO to allow a manual reboot later: [YES]
Tips
Start up the multi-user target (text login mode) after reboot. If you temporarily use the
graphical target (graphical login mode) environment, execute the following command after
login.
# startx
The indication on screen may be corrupted when the system is shutdown or rebooted.
However, end processing is normally terminated.
5. Eject the ft Server Control Software Install CD from the optical disk drive.
6. After a while, system FT LED turns on. For details, see Chapter 1 (6.1 Error Messages by LED Indication) in Maintenance Guide.
Take the steps below before starting installation of NEC ESMPRO Agent.
1. Login the system with root user.
2. When monitoring the server using NEC ESMPRO Agent from NEC ESMPRO Manager, use SNMP.
To perform remote shutdown, local polling, and to change threshold from NEC ESMPRO Manager,
modify the SNMP environment file (/etc/snmp/snmpd.conf) to set a community privilege to "read
write" for ESMPRO MIB, and restart snmpd. If these features are not used, the community privilege
can be "read".
When NEC ESMPRO Agent is installed by using rpm command, it adds the following information to
snmpd.conf to cope with SNMP request from ESMPRO MIB and Ethernet Like MIB.
In the following example, "read write" privilege is given to every MIB(.1) in default community (public).
2. Setting up
####
# First, map the community name "public" into a "security name"
# sec.name source community
com2sec notConfigUser default public
####
# Second, map the security name into a group name:
# groupName securityModel securityName
group notConfigGroup v1 notConfigUser
group notConfigGroup v2c notConfigUser
####
# Third, create a view for us to let the group have rights to:
# name incl/excl subtree mask(optional)
#view systemview included .1.3.6.1.2.1.1
#view systemview included .1.3.6.1.2.1.25.1.1
view all included .1 80
####
# Finally, grant the group read-only access to the systemview view.
# group context sec.model sec.level prefix read write notif
#access notConfigGroup "" any noauth exact systemview none none
access notConfigGroup "" any noauth exact all all none
For detailed information, refer to help of snmpd.conf.
Setting required after installing NEC ESMPRO Agent
NEC ESMPRO Manager uses the following network port when it monitors the server where NEC ESMPRO
Agent is installed.
When configuring access control on your server, allow these ports as accessible.
As for "Auto-assign" in the table, OS assigns available port within the certain range. Accordingly, these ports
cannot be fixed. The available range is described in the following file.
# cat /proc/sys/net/ipv4/ip_local_port_range
2. Setting up
Tips
If you use an example of opening the port by using iptables, you have to install
iptables-services in advance.
Between NEC ESMPRO Agent and NEC ESMPRO Manager
Features
Automatic registration (SNMP)
Server monitoring (SNMP)
Report to Manager (SNMP) Auto-assign
Report to Manager
(TCP/IP in Band, TCP/IP Out-of-Band)
NEC ESMPRO
Agent
161/udp
Auto-assign
Direction
NEC ESMPRO
Manager
161/udp
162/udp
31134/tcp
Remarks
snmp
snmp-trap
* If left and right arrows are shown in Direction column, an upper arrow shows the direction at start-up, and the
lower shows the return.
* Port numbers not used by SNMP can be changed on alert setting screen.
* Shown below is an example of ports opened by using iptables. Setting must be saved finally.
* In the direction column, the upper arrow indicates the direction in which the communication started and
the lower arrow indicates the returning communication.
* The port to be used can be changed from the report setting screen.
* An example of opening the port by using iptables is shown below. Save the setting at the end.
Features ESMPRO/SA Direction HTTPS server Remarks
Express Report Service (HTTPS)
* In thedirection column, the upper arrow indicates the direction in which the communication started and
the lower arrow indicates the returning communication.
* The port number to be used can be changed from the report setting screen.
* An example of opening the port by using iptables is shown below. Save the setting at the end.
# iptables -I OUTPUT -p tcp --dport 443 -j ACCEPT
# service iptables save
NEC ESMPRO Agent uses the following internal ports. When configuring access control on your server using
iptables or TCP Wrapper, allow these ports as accessible.
Between NEC ESMPRO Agent and another NEC ESMPRO Agent
Feature Port number
rpcbind 111/tcp
Auto-assign
111/udp
→
←
443/tcp
2. Setting up
https
NEC ESMPRO Agent Auto-assign
2.3.10
Troubleshooting
If the OS setup does not progress normally, see the following check list.
[?] RHEL7.2 cannot be installed as described in this manual.
→ Check that the BIOS boot modeis set toUEFI . For details, see Chapter 1 (2.2.3 Checking Boot Mode
Settings).
→ Check that the module POWER lamps of the CPU/IO module 0 and CPU/IO module 1 are lit.
Check that the PRIMARY lamp of the CPU/IO module 0 is lit.
Check that the hard disk drive is mounted only to the slot 0 of the CPU/IO module 0 and CPU/IO module 1,
and the hard disk drive is physically formatted.
For details, see Chapter 1 (2.2.1 Preparation for hardware) in this manual.
[?]The system suddenly restarts during the setup processing.
→ Check that the BIOS startup monitoring feature is invalid. For details, see Chapter 1 (2.2.2 Disabling OS
Boot Monitoring Feature) in this manual.
[?]An error or warning message is output during the setup processing.
→ Although an error or warning message may be output due to the temporary system conditions, the setup is
completed successfully if the system FT LED is lit as described on “2.3.6 Installing ft Server Control
Software” in this manual. For the message output after completion of setup, see Chapter 1 (8.3 Problems
When Starting OS) in "Maintenance Guide".
If there is an uninstalled hard disk drive, install and duplicate it by referring to the following procedure.
- Chapter 2 (5.3 2.5-inch Hard Disk Drive) in "Maintenance Guide"
- Chapter 2 (1. Hard Disk Drive Duplexing) in "Maintenance Guide"
2.4.3
Other
If there is an unconnected USB device for backup (i.e. external/internal RDX), connect the USB cable by
referring to the manual attached to the USB device.
If LAN cable connected to Management LAN conector was removed in Chapter 1 (2.2.1 Preparation for
hardware), connect it if needed.
Important Be sure to use the vndctl command if setting the IP address, subnet mask, and
default gateway. For details, see Chapter 2 (2. Network Duplexing) in "Maintenance
Guide".
Overview of network setting
The network duplexing is configured as a pair of the CPU/IO module 0 and CPU/IO module 1 and the network
interface of the PCI slot corresponding to each module. The network interface is named according to the naming
rule described below.
PCI slot and network interface name
PCI slot Port CPU/IO module 0 CPU/IO module 1 Slot number of the vndctl
command
1G LAN connector #1 eth100600 eth110600 1
#2 eth100601 eth110601 2
10G LAN
connector
PCI slot 1 #1 eth100100 eth110100 5
PCI slot 2 #1 eth100200 eth110200 7
PCI slot 3* #1 eth100300 eth110300 9
PCI slot 4* #1 eth100400 eth110400 11
* For R320e-E4, 10G LAN connector, PCI slot 3, and PCI slot 4 do not exist.
Slot RealDevice Status Interface LinkState LinkSpeed
1 top eth100600 DUPLEX UP LINK 1000Mb/s-FD
bottom eth110600 DUPLEX UP LINK 1000Mb/s-FD
2 top eth100601 DUPLEX UP LINK 1000Mb/s-FD
bottom eth110601 DUPLEX UP LINK 1000Mb/s-FD
It is recommended to write down your system information when you finish system setup.
With backup copy of system information, the information and settings that are specific to your server can be
restored after the server is repaired. Take the steps below to make a backup copy of your system information:
BIOS SETUP
Power on the server.
While the following message is displayed on POST, press the <F2> key.
Press <F2> SETUP, <F4> ROM Utility, <F12> Network
Write down the new parameter values upon completion of POST.
Example)
[Advanced]-[PCI Configuration]-[SAS Option ROM Scan]
5. Execute the following command, and check the lists of "Environment Groups" and package group
"Groups".
# LANG=C yum grouplist hidden
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription : manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to
register.
Available Environment Groups:
Minimal Install
Infrastructure Server
File and Print Server
Basic Web Server
Virtualization Host
Server with GUI
Available Groups:
Additional Development
Anaconda Tools
Backup Client
Backup Server
Base
・
・
・
6. Execute the following command, and check the package included in the package group (the
package group "Web Server" is specified here). Among the packages in "Mandatory Packages:" and
"Default Packages:", the packages with "+" at the head of the package name are installed. The
packages displayed in "Optional Packages:" must be installed with the package name specified. For
the installation with the package group specified, proceed to step 7. For the installation with the
package specified, proceed to step 8.
# LANG=C yum groupinfo "Web Server" *Specify the package group name
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription : manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to
register.
Group: Web Server
Group-Id: web-server
Description: Allows the system to act as a web server, and run Perl and Python web applications.
Mandatory Packages:
httpd
Default Packages:
+crypto-utils
+httpd-manual
+mod_fcgid
+mod_ssl
Optional Packages:
certmonger
libmemcached
memcached
mod_auth_kerb
mod_auth_mellon
mod_nss
mod_revocator
mod_security
mod_security_crs
perl-CGI
perl-CGI-Session
python-memcached
squid
3. Procedure for Changing the System Environment Setting
7. Execute the following command, specify the package group, and install it (the package group "Web
Server" is specified here).
# LANG=C yum groupinstall "Web Server"
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription : manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to
register.
Resolving Dependencies
--> Running transaction check
---> Package crypto-utils.x86_64 0:2.4.1-42.el7 will be installed
--> Processing Dependency: perl(Newt) for package: crypto-utils-2.4.1-42.el7.x86_64
---> Package httpd-manual.noarch 0:2.4.6-40.el7 will be installed
---> Package mod_fcgid.x86_64 0:2.3.9-4.el7 will be installed
---> Package mod_ssl.x86_64 1:2.4.6-40.el7 will be installed
--> Running transaction check
---> Package perl-Newt.x86_64 0:1.08-36.el7 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Installing for group install "Web Server":
crypto-utils x86_64 2.4.1-42.el7 dvd 78 k
httpd-manual noarch 2.4.6-40.el7 dvd 1.3 M
mod_fcgid x86_64 2.3.9-4.el7 dvd 79 k
mod_ssl x86_64 1:2.4.6-40.el7 dvd 103 k
Installing for dependencies:
perl-Newt x86_64 1.08-36.el7 dvd 64 k
8. Execute the following command, specify the package, and install it (the package "squid" is specified
here).
# LANG=C yum install squid
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription : manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to
register.
Resolving Dependencies
--> Running transaction check
---> Package squid.x86_64 7:3.3.8-26.el7 will be installed
--> Processing Dependency: libecap.so.2()(64bit) for package: 7:squid-3.3.8-26.el7.x86_64
--> Running transaction check
---> Package libecap.x86_64 0:0.2.0-9.el7 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
squid x86_64 7:3.3.8-26.el7 dvd 2.6 M
Installing for dependencies:
libecap x86_64 0.2.0-9.el7 dvd 20 k
3. Procedure for Changing the System Environment Setting
3.3
Adding Partitions
Perform the following procedure to create an additional partition in a free space of a hard disk drive installed in
slot0 of CPU/IO module 0 and CPU/IO module 1. In the following example, a RAID1 device (/dev/md/data) is
created in a partition of 10GB and that partition is set as “/mnt/data”.
Important
If the partition is wrongly operated, the system may not start up or data may be
lost. Be sure to back up the important data before starting the work. Especially,
the results of the sub command executed by the parted command will be
reflected to the disk immediately. Take extreme care when operating it.
LVM is not supported.
1. Log in to the server as the root user. If you login with graphical mode, select [Others...] to login.
2. Execute the following command to set the slot 0 of the CPU/IO 0.
# parted /dev/disk/by-dpid/disk-104001
GNU Parted 3.1
Using /dev/sdq
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted)
Tips
The (parted) command prompt appears, and the internal command of parted can be
received.
3. Execute the print sub command to check the partition status.
(parted) print
Model: HGST HUC156030CSS200 (scsi)
Disk /dev/sdq: 300GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 17.2GB 17.2GB raid
2 17.2GB 25.8GB 8598MB raid
3 25.8GB 26.9GB 1075MB ext4 raid
4 26.9GB 27.1GB 211MB fat16 raid
5 27.1GB 61.5GB 34.4GB raid
4. Execute the mkpart sub command to create the partition.
(parted) mkpart
Partition name? []? * Input the desired partition name.
File system type? [ext2]? * Input the <Enter> key.
Start? 61.5GB * Input the partition start position.
End? 71.5GB * Input the partition end position.
Tips
The unit of the partition start/end is MB. GB can be used as a unit as described above.
3. Procedure for Changing the System Environment Setting
3.4
3.4.1
Expanding the swap Area
Expand the swap area according to the following procedure.
Using the swap partition
If there is a free space in the hard disk drive of the slot 0 of the CPU/IO module 0 and CPU/IO module 1, the
partition for swap can be created, and the swap area can be expanded.
1. Create the partition by referring to steps 1 to 12 of Chapter 1 (3.3 Adding Partitions) in this manual.
The case where the partition "/dev/md/swap2"is created is described here.
2. Execute the following command to create the swap area.
# mkswap /dev/md/swap2
3. Set so that the partition can be mounted automatically at startup.
Execute the following command to check the UUID value.
If the swap partition cannot be secured, the swap file can be created and the swap area can be expanded. The
procedure for creating the swap file with the file name "swap file" and 1 GB capacity in the root directory is
described here.
1. Log in to the server as the root user. If you login with graphical mode, select [Others...] to login.
2. Execute the following command to create the file for swap.
3. Procedure for Changing the System Environment Setting
3.5
Setting SELinux
SELinux is set to "Disabled" by default. Change the SELinux setting as required according to the following
procedure.
Tips
1. Log in to the server as the root user. If you login with graphical mode, select [Others...] to login.
2. Execute the following command to check the SELinux current setting.
If the current setting is "Disabled", the following message appears.
# getenforce
Disabled
If the current setting is "Enforcing", the following message appears.
# getenforce
Enforcing
If the current setting is "Permissive", the following message appears.
If the SELinux setting is not "Disabled", set the appropriate security context by the SELinux
policy setting file. Otherwise, the security violation warning may be issued or an error may
occur while the software is used, and the system may not operate normally. Fully
understand the SELinux security context before changing the setting.
# getenforce
Permissive
3. Open "/etc/sysconfig/selinux" with the editor, and search for the following line.
SELINUX=<current_setting>
4. Edit the above line and save the file.
Change the line as shown below for "Disabled".
SELINUX=disabled
Change the line as shown below for "Enforcing".
SELINUX=enforcing
Change the line as shown below for "Permissive".
SELINUX=permissive
5. Execute the following command to restart this system.
This section describes processing detail of initial configuration script.
4.1 Processing detail of initial configuration script
The following processings are executed by initial configuration script.
1. Change of default setting of SELinux
Change setting of SELinux from "Enforcing" (OS's default setting) to "Disabled" so that SELinux is to be
used only when it is necessary.
▪ Changing the setting
Change SELinux to the setting other than "Disabled" as required by referring to Chapter 1 (3.5 Setting
SELinux) in this manual.
4. Appendix
2. Change of activation of service
Stop services that required by unsupported hardware or not to be used for server.
– avahi-daemon
– bluetooth
– cups
– smartd
In system environment where the package group of Virtualization Platform is not installed, stop
libvirt-guests service to suppress the unnecessary message issued at shutdown.
3. Stopping the clock synchronization
The following two services are available as the clock synchroniz ation service. The both services are
stopped at the initial setting so that you can choose either of services can be selected.
– ntpd
– chronyd
4. Exclude update target of yum
To exclude the kernel-related module from update target of yum, add "kernel-*" to exclude line of
"/etc/yum.conf".
When installing the library package that provides both 32-bit and 64-bit version in x86_64 environment
by using yum, add "multilib_policy=all" to "/etc/yum.conf" to install 32-bit library together with 64-bit
library.
▪ Changing the installation setting of 32-bit library
If 32-bit library is not installed at the update of yum, delete "multilib_policy=all" from "/etc/yum.conf".
Before change
[main]
multilib_policy=all
↓
After change
[main]
6. Interval of information collection
Change interval to collect sysstat information from 10 minutes (default) to 1 minute so that system status
can be obtained more precisely at the occurrence of failure.
4. Appendix
▪ Changing the setting (Example: Changing to 10 minutes set by default)
Edit the "/etc/cron.d/sysstat" file as described below.
Before change
# Run system activity accounting tool every 1 minutes
*/1 * * * * root /usr/lib64/sa/sa1 1 1
↓
After change
# Run system activity accounting tool every 10 minutes
*/10 * * * * root /usr/lib64/sa/sa1 1 1
* For the detailed format of the "/etc/cron.d/sysstat" file, refer to "man 5 crontab".
7. Deleting the unnecessary packages
To prevent the dump files collected when the panic occurs from being copied to the "/var/tmp/abrt"
directory, delete the following message.
To monitor the process signal transmission, set the following contents in the
"/etc/audit/rules.d/audit.rules" file.
-a always,exit -F arch=b64 -S kill,rt_sigqueueinfo,tkill -F a1=0x1 -k signal_send
-a always,exit -F arch=b32 -S kill,rt_sigqueueinfo,tkill -F a1=0x1 -k signal_send
-a always,exit -F arch=b64 -S tgkill,rt_tgsigqueueinfo -F a2=0x1 -k signal_send
-a always,exit -F arch=b32 -S tgkill,rt_tgsigqueueinfo -F a2=0x1 -k signal_send
-a always,exit -F arch=b64 -S kill,rt_sigqueueinfo,tkill -F a1=0x2 -k signal_send
-a always,exit -F arch=b32 -S kill,rt_sigqueueinfo,tkill -F a1=0x2 -k signal_send
-a always,exit -F arch=b64 -S tgkill,rt_tgsigqueueinfo -F a2=0x2 -k signal_send
-a always,exit -F arch=b32 -S tgkill,rt_tgsigqueueinfo -F a2=0x2 -k signal_send
-a always,exit -F arch=b64 -S kill,rt_sigqueueinfo,tkill -F a1=0x6 -k signal_send
-a always,exit -F arch=b32 -S kill,rt_sigqueueinfo,tkill -F a1=0x6 -k signal_send
-a always,exit -F arch=b64 -S tgkill,rt_tgsigqueueinfo -F a2=0x6 -k signal_send
-a always,exit -F arch=b32 -S tgkill,rt_tgsigqueueinfo -F a2=0x6 -k signal_send
-a always,exit -F arch=b64 -S kill,rt_sigqueueinfo,tkill -F a1=0x9 -k signal_send
-a always,exit -F arch=b32 -S kill,rt_sigqueueinfo,tkill -F a1=0x9 -k signal_send
-a always,exit -F arch=b64 -S tgkill,rt_tgsigqueueinfo -F a2=0x9 -k signal_send
-a always,exit -F arch=b32 -S tgkill,rt_tgsigqueueinfo -F a2=0x9 -k signal_send
-a always,exit -F arch=b64 -S kill,rt_sigqueueinfo,tkill -F a1=0xa -k signal_send
-a always,exit -F arch=b32 -S kill,rt_sigqueueinfo,tkill -F a1=0xa -k signal_send
-a always,exit -F arch=b64 -S tgkill,rt_tgsigqueueinfo -F a2=0xa -k signal_send
-a always,exit -F arch=b32 -S tgkill,rt_tgsigqueueinfo -F a2=0xa -k signal_send
-a always,exit -F arch=b64 -S kill,rt_sigqueueinfo,tkill -F a1=0xc -k signal_send
-a always,exit -F arch=b32 -S kill,rt_sigqueueinfo,tkill -F a1=0xc -k signal_send
-a always,exit -F arch=b64 -S tgkill,rt_tgsigqueueinfo -F a2=0xc -k signal_send
-a always,exit -F arch=b32 -S tgkill,rt_tgsigqueueinfo -F a2=0xc -k signal_send
-a always,exit -F arch=b64 -S kill,rt_sigqueueinfo,tkill -F a1=0xd -k signal_send
-a always,exit -F arch=b32 -S kill,rt_sigqueueinfo,tkill -F a1=0xd -k signal_send
-a always,exit -F arch=b64 -S tgkill,rt_tgsigqueueinfo -F a2=0xd -k signal_send
-a always,exit -F arch=b32 -S tgkill,rt_tgsigqueueinfo -F a2=0xd -k signal_send
-a always,exit -F arch=b64 -S kill,rt_sigqueueinfo,tkill -F a1=0xf -k signal_send
-a always,exit -F arch=b32 -S kill,rt_sigqueueinfo,tkill -F a1=0xf -k signal_send
-a always,exit -F arch=b64 -S tgkill,rt_tgsigqueueinfo -F a2=0xf -k signal_send
-a always,exit -F arch=b32 -S tgkill,rt_tgsigqueueinfo -F a2=0xf -k signal_send
12. Prevention of the OS existence check in all disks
4. Appendix
This prevents all disks from performing unnecessary I/O when executing the grub2-mkconfig command.
Checking the OS existence check in all disks
Delete the following line in the "/etc/default/grub" file.
GRUB_DISABLE_OS_PROBER="true"
13. Saving the root user command history
Add the following setting to the "/root/.bashrc" file to correctly understand the operation status when a
system problem occurs.
unset HISTCONTROL # Saving the duplicated command history
HISTSIZE=20000 # Setting the maximum history count to 20000
HISTTIMEFORMAT=" %F %T " # Displaying the date and time when displaying the history
14. Add the "acpi_pad" module to the blacklist.
Add the following setting to the "/etc/modprobe.d/nec.conf" file to add "acpi_pad" module to the
blacklist and disable it.
If systemd runs while the default setting remains unchanged, a problem occurs in the semaphore of the
IPC (interprocess communication) or the shared memory. Add the setting to the
"/etc/systemd/logind.conf" file to avoid this problem.
RemoveIPC=no
16. Creation of backup file
If the file is modified while running initial configuration script, the backup file immediately b efore applying
the script is created in the following directory.
This section introduces the software bundled in the server package. For details, refer to the software
documents.
1.1 NEC ESMPRO Agent (Linux)
NEC ESMPRO Agent (Linux) is an application used to monitor the server.
NEC ESMPRO Agent (Linux) is stored in ft Server Constol Software Install CD. For how to install it, see Chapter
1 (2.3.7 Before installing NEC ESMPRO Agent), (2.3.8 Installing NEC ESMPRO Agent), and (2.3.9 Setting
required after installing NEC ESMPRO Agent).
BIOS Setup Utility (SETUP) Software for setting BIOS. You can run this software by pressing <F2> key during POST.
BMC Baseboard Management Controller (BMC) is a built-in controller that supports the IPMI
version 2.0 protocol. BMC can manage the server hardware.
BMC Configuration Utility Software for setting BIOS or BMC. You can use as Windows application or run this
software when pressing <F4> key during POST.
CPU module A CPU subsystem logically configured in a CPU/IO module. It includes CPUs and
memory.
CPU/IO module A module that includes CPUs (processors), memory, PCI boards, a cooling fan, hard disk
drives and power supply units.
DUMP Switch A switch that is used for collecting the memory dump if an error occurs. You can specify
the destination of the dump by using the OS function.
EXPRESSBUILDER Standard software with a feature that makes it easier to install Windows OS in Win dows
model. This also includes several useful applications and instruction manuals. (When
installing OS other than Windows in ft server, the feature that helps easy OS installation is
not available.)
EXPRESSSCOPE ENGINE 3 A name of BMC for NEC Express5800 series.
Express Report Service Software that can report the server failure to the contact center by E-mail or modem. This
software is installed with NEC ESMPRO Agent to the server.
Express Report Service (HTTPS) Software that can report the server failure to the contact center by HTTPS.
ExpressUpdate A feature for updating BIOS, firmware, driver, or software of the server. This feature is
available when NEC ESMPRO Manager cooperates with EXPRESSSCOPE ENGINE 3
and ExpressUpdate Agent.
ExpressUpdate Agent Software for performing ExpressUpdate. This is installed to the server.
Flash FDD An optional USB device that can use as a floppy disk drive.
NEC ESMPRO Standard software for the server management. This consists of several applications for
managing or monitoring.
NEC ESMPRO A gent Software for monitoring the server. This works with NEC ESMPRO Manager and resides
as the OS service.
NEC ESMPRO Agent Extension Software for performing the scheduled operations. This works with NEC ESMPRO
Manager.
NEC ESMPRO Manager Software for managing plural servers on network.
OS standard installer An installer that stored in Windows installation disc. Use this installer if you want to install
the OS manually.
Offline tools Software that can confirm or change IPMI data such as SEL, SDR, or FRU. You can start
Offline tools when pressing <F4> key during POST.
PC for Management A computer for managing the server on network. A general Windows/Linux computer can
be used as "PC for Management".
PCI module An I/O subsystem logically configured in a CPU/IO module. It includes hard disk drives,
PCI cards, BMC and 1G/10G LAN.
Product Info Collection Utility Software for collecting several hardware/software statuses or event logs. You can easily
collect the data for the server maintenance by using this software.
Windows OS parameter file A file that saved settings for installing Windows. You can install with the saved settings in
this file when setting Windows with EXPRESSBUILDER.