This section explains the preparations and checks required before commencing installation.
Software preparation and checks are explained in the following sections.
Exclusive Software Checks
Before installing Resource Coordinator VE, check that the software listed in "1.1.2.3 Exclusive Software" and the manager of Resource Coordinator VE have not been installed on the system.
Use the following procedure to check that exclusive software has not been installed.
[Windows]
Open "Add or Remove Programs" on the Windows Control Panel.
The [Add or Remove Programs] window will be displayed.
Check on the "Add or Remove Programs" window that none of the software listed in "1.1.2.3 Exclusive Software" or the following software are displayed.
"Systemwalker Resource Coordinator Virtual server Edition Manager"
"ServerView Resource Coordinator VE Manager"
When any of the exclusive software is displayed on the [Add or Remove Programs] window, uninstall it according to the procedure described in the relevant manual before installing Resource Coordinator VE.
If managers of an earlier version of Resource Coordinator VE have been installed, they can be upgraded. Refer to "4.2 Manager". When reinstalling a manager on a system on which of the same version of Resource Coordinator VE has been installed, perform uninstallation referring to "3.1 Manager Uninstallation" and then perform the re-installation.
Information
For Windows Server 2008, select "Programs and Features" from the Windows Control Panel.
[Linux]
Insert the Resource Coordinator VE CD-ROM, and then execute the following command.
# cd CD-ROM_mount_point/manager <RETURN> |
When the following message is displayed, it indicates that Resource Coordinator VE, an older version of a Resource Coordinator product, or exclusive software has been installed. Follow the uninstallation procedure given in the manual of the relevant software, and uninstall the software before proceeding with installation.
When Resource Coordinator VE has been installed
WARNING : Resource Coordinator VE Manager cannot be installed on this system because Resource Coordinator VE software_name has already been installed. |
When an older version of a Resource Coordinator product has been installed
WARNING : Resource Coordinator VE Manager cannot be installed on this system because another version of Resource Coordinator has already been installed. |
When exclusive software has been installed
WARNING : Resource Coordinator VE Manager cannot be installed on this system because software_name has already been installed. |
Note
When uninstalling exclusive software, there are cases where other system administrators might have installed the software, so check that deleting the software causes no problems before actually doing so.
With the standard settings of Red Hat Enterprise Linux 5 or later, when CD-ROMs are mounted automatically, execution of programs on the CD-ROM cannot be performed. Release the automatic mount settings and perform mounting manually, or start installation after copying the contents of the CD-ROM to the hard disk.
When copying the contents of the CD-ROM, replace "CD-ROM_mount_point" with the used directory in the procedures in this manual.
Required Software Preparation and Checks
Before installing Resource Coordinator VE, check that the required software given in "1.1.2.2 Required Software" has been installed. If it has not been installed, install it before continuing.
When operating managers in cluster environments, refer to "Appendix B Manager Cluster Operation Settings and Deletion" and "B.2.1 Preparations", and perform preparations and checks in advance.
Note
Microsoft LAN Manager Module
Before installing Resource Coordinator VE, obtain the Microsoft LAN Manager module from the following FTP site:
URL: ftp://ftp.microsoft.com/bussys/clients/msclient/dsk3-1.exe (As of February 2010) |
When installing Resource Coordinator VE to an environment that already has ServerView Deployment Manager installed, it is not necessary to obtain the Microsoft LAN Manager module.
[Windows]
After obtaining the module, extract it in a work folder (such as C:\temp) of the system for installation.
The Microsoft LAN Manager module can be installed without extracting it in advance.
The obtained module is for x86 CPU architecture.
It cannot be extracted on x64 CPU architecture systems.
When extracting the module, do so on an x86 CPU architecture system.
[Linux]
Extract the obtained module on Windows. Transfer the following extracted files to a work folder on the system for installation. Ensure that the file names of the transferred files are all uppercase.
PROTMAN.DOS
PROTMAN.EXE
NETBIND.COM
Use the following method to extract the compressed file (dsk3-1.exe).
Example
When dsk3-1.exe was deployed on c:\temp
>cd /d c:\temp <RETURN> |
Use the Windows 8.3 format (*1) for the folder name or the file name.
After manager installation is complete, the extracted Microsoft LAN Manager module is no longer necessary.
*1: File names are limited to 8 characters and extensions limited to 3 characters.
[Windows]
Settings for ServerView Operations Manager for Windows
In order for Resource Coordinator VE to operate correctly, ensure that the following settings are made when installing ServerView Operations Manager for Windows.
Do not select "IIS (MS Internet Information Server)" for Select Web Server.
Do not check "Use SSL and Authentification" for WebServer Destination Path.
For the settings, refer to the ServerView Operations Manager for Windows manual.
Settings for ServerView Virtual-IO Manager
When using VIOM, in order for Resource Coordinator VE to operate correctly, ensure that the following settings are made when installing ServerView Virtual-IO Manager for Windows.
When using the I/O Virtualization Option
Clear the "Select address ranges for IO Virtualization" checkbox on the virtual I/O address range selection window.
When not using the I/O Virtualization Option
Select the "Select address ranges for IO Virtualization" checkbox on the virtual I/O address range selection window, and then select address ranges for the MAC address and the WWN address.
When there is another manager, select address ranges which do not conflict those of the other manager.
For details, refer to the ServerView Virtual-IO Manager for Windows manual.
Before installing Resource Coordinator VE, collect required information and check the system status, then determine the information to be specified on the installation window. The information that needs to be prepared is given below.
Installation Folder
Decide the installation folder for Resource Coordinator VE.
Note that folders on removable disks cannot be specified.
Check that there are no files or folders in the installation folder.
Check that the necessary disk space can be secured on the drive for installation.
For the amount of disk space necessary for Resource Coordinator VE, refer to "1.1.2.4 Static Disk Space" and "1.1.2.5 Dynamic Disk Space".
Image File Storage Folder
Decide the image file storage folder.
Note that folders on removable disks cannot be specified.
Check that there are no files or folders in the image file storage folder.
Check that sufficient disk space can be secured on the drive where the storage folder will be created.
For the necessary disk space, refer to "1.1.2.5 Dynamic Disk Space".
Port numbers
When Resource Coordinator VE is installed, the port numbers used by it will automatically be set in the services file of the system. So usually, there is no need to pay attention to port numbers.
If the port numbers used by Resource Coordinator VE are being used for other applications, a message indicating that the numbers are in use is displayed when the installer is started, and installation will stop.
In that case, describe the entries for the following seven port numbers used by Resource Coordinator VE in the services file using numbers not used by other software, and then start the installer.
Example
# service name port number/protocol name nfdomain 23457/tcp nfagent 23458/tcp rcxmgr 23460/tcp rcxweb 23461/tcp rcxtask 23462/tcp rcxmongrel1 23463/tcp rcxmongrel2 23464/tcp |
For details, refer to "6.3.1.2 Changing Port Numbers" of the "ServerView Resource Coordinator VE Setup Guide".
User account for administrative users of Resource Coordinator VE
Decide the user account name and password for administrative users of Resource Coordinator VE.
For details, refer to "Chapter 4 User Accounts" of the "ServerView Resource Coordinator VE Operation Guide".
Check the admin LAN of the admin server and the status of the NIC
Decide the network (IP addresses) to be used for the admin LAN of the admin server.
Check that the NIC used for communication with the admin LAN is enabled.
For admin LANs, refer to "3.2.2 IP Addresses (Admin LAN)" of the "ServerView Resource Coordinator VE Setup Guide".
This section explains the SNMP trap daemon.
On the server operating the manager, the standard Linux SNMP trap daemon cannot be used.
Also, applications that use the SNMP trap daemon cannot be used.
When the standard Linux SNMP trap daemon has been configured to start automatically, change the settings so that it does not start automatically.
Use the following procedure to prevent the SNMP trap daemon from being started automatically.
Login as the OS administrator (root), and then execute the following command.
# /usr/sbin/setup <RETURN> |
The "setup" command is a Red Hat Enterprise Linux command.
A menu window will be displayed.
Select "System service", and press the Enter key.
The service window will be displayed.
Remove the "*" from the "snmptrapd" parameter.
To remove the "*", align the cursor with the parameter and press the Space key.
Use the Tab key to align the cursor with "OK", and press the Enter key.
Use the Tab key to align the cursor with "Cancel", and press the Enter key.
"setup" is complete.
When "PRIMERGY server management software ServerView for Linux" has been installed, the ServerView Trap Server for Linux (trpsrvd) is necessary. For details, refer to "ServerView Trap Server for Linux (trpsrvd)".
ServerView Trap Server for Linux (trpsrvd)
When using ServerView Operations Manager AlarmService on servers that a manager has been installed on, ServerView Trap Server for Linux (trpsrvd) for transferring SNMP Traps is required.
ServerView Trap Server for Linux (trpsrvd) is used to transfer snmp traps received at UDP port number 162 to other UDP port numbers.
For details of how to obtain ServerView Trap Server for Linux (trpsrvd), refer to "1.1.2.2 Required Software".
By default the ServerView Trap Server for Linux is included in some versions of ServerView Operations Manager. Use the following procedure to check whether it is installed.
Log in as the OS administrator (root).
Execute the following command.
# rpm -qa |grep SMAWtrpsv <RETURN> |
If it is already installed, the following will be displayed.
Example
# rpm -qa |grep SMAWtrpsv |
"1.1A10-13" indicates the installed version of ServerView Trap Server for Linux.
If it is not installed, perform installation referring to the documents provided with ServerView Trap Server for Linux (trpsrvd).
After installing ServerView Trap Server for Linux, perform the following settings.
Log in as the OS administrator (root).
Edit the /etc/services file, and add the following line.
mpwksttr-trap 49162/udp |
Edit the /usr/share/SMAWtrpsv/conf/trpsrvtargets file, and add port 49162.
Before editing
######################################################################## |
After editing
######################################################################## |
Restart the system.
