Time required
It takes approximately 15 minutes to install this software.
Kernel header
Before installing this software, it is necessary to install the kernel header that supports OS of the system. Check if the kernel header is installed on the system by executing the following command:
# rpm -qi kernel-devel <Return>If the command encounters an error, or the kernel source version different than the system OS, install the kernel source according to the OS document.
System environment check
When installing this software on PRIMEQUEST, it is necessary that the installation of software prerequisites is completed.
For setup instructions, refer to the following manuals:
PRIMEQUEST 2000 Series
PRIMEQUEST 2000 Series Installation Manual
PRIMEQUEST 2000 Series ServerView Mission Critical Option User Manual
PRIMEQUEST 3000 Series
PRIMEQUEST 3000 Series Installation Manual
To install Web-Based Admin View, it is necessary to modify the IP address of the admin LAN for Web-Based Admin View and its corresponding host name, and the host name corresponding to "127.0.0.1"(for IPv4) and "::1"(for IPv6).
Login to the system and become the root user.
$ su <Return> Password:password <Return>
Delete the host name allocated to "127.0.0.1"(for IPv4) and "::1"(for IPv6) using vi(1) and allocate it to the IP address of the admin LAN.
Before change)
# cat /etc/hosts <Return> 127.0.0.1 host-name localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 host-name localhost localhost.localdomain localhost6 localhost6.localdomain6
After change)
# cat /etc/hosts <Return> 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 IP-Address host-name
Check the auto startup of the NetworkManager service.
PRIMECLUSTER does not support the NetworkManager service. Check the auto startup of the NetworkManager service setting.
Check that the setting of auto startup of the NetworkManager service is "disabled" using the following command.
# /usr/bin/systemctl is-enabled NetworkManager.service <Return>
disabledIf the setting is "enabled", disable the NetworkManager service using the following command.
# /usr/bin/systemctl stop NetworkManager.service <Return> # /usr/bin/systemctl disable NetworkManager.service <Return>
Check the auto startup of the snmptrapd service. (For the PRIMEQUEST 3000 Series)
For the PRIMEQUEST 3000 Series, the setting of the auto start of the snmptrapd service is enabled.
Check that the setting of auto startup of the snmptrapd service is "enabled" using the following command.
# /usr/bin/systemctl is-enabled snmptrapd.service <Return>
enabled
If the setting is "disabled", enable the snmptrapd service using the following command.
# /usr/bin/systemctl enable snmptrapd.service <Return>Check the definition of snmptrapd.conf. (For the PRIMEQUEST 3000 Series)
For the PRIMEQUEST 3000 Series, add the definition to snmptrapd.conf.
When "net public" has not been described to the definition of authCommunity entry of /etc/snmp/snmptrapd.conf, edit the authCommunity entry of the /etc/snmp/snmptrapd.conf file using vi(1) etc.
[Before Modification]
# Example configuration file for snmptrapd # # No traps are handled by default, you must edit this file! # # authCommunity log,execute,net public # traphandle SNMPv2-MIB::coldStart /usr/bin/bin/my_great_script cold
[After Modification]
# Example configuration file for snmptrapd # # No traps are handled by default, you must edit this file! # # authCommunity log,execute,net public # traphandle SNMPv2-MIB::coldStart /usr/bin/bin/my_great_script cold authCommunity net public