Steps for setting the monitoring server are described below.
Define in the following order:
When using Hyper-V/ Red Hat Virtualization function (KVM)/ Red Hat Virtualization function (Xen)/ Solaris container
Define the settings for the monitoring server and the monitored server.
Edit the connection account configuration file (remoteAccount.txt).
Storage location
The file is stored in the following location:
Windows
<variable file storage directory>\control\remoteAccount.txt |
UNIX
/etc/opt/FJSVssqc/remoteAccount.txt |
Edit the above file using the definition method described below.
Definition method
This is an ini format file.
Set the sections by connection account groups for communication between the monitoring server and the monitored server.
The method of definition depends on the communication method. Edit to match the communication method.
No | Item | Mandatory/optional | Format | Description |
|---|---|---|---|---|
- | [ACCOUNT] | Mandatory | 63 characters or fewer, using alphanumerics, hyphens (-), periods (.), and hash symbols (#) only | Use an account group name for the section name. Make it so that the section name is a unique character string. |
1 | CONNECTTYPE | Mandatory | TELNET | Set the connection method for when using the install-less function for connection.
|
2 | USER | Mandatory | 63 characters or fewer | Set the login account for connection. |
3 | PASSWORD | Mandatory | Character string generated with genpwd (*1) | Set the password for connection. |
*1: Refer to "A.6 genpwd (Password Encryption Command)" for details about how to use the genpwd command to generate encrypted passwords.
Example of definition
The following is an example of connection account definition file when using Hyper-V.
[Hyper-V-Account1] CONNECTTYPE=TELNET USER=telnetuser PASSWORD=C5sJGBE3ONs= |
When using VMware ESX/VMware ESXi/VMware vCenter
Define the settings for the monitoring server and the monitored server.
Edit the connection account configuration file (remoteAccount.txt).
Storage location
The file is stored in the following location:
Windows
<variable file storage directory>\control\remoteAccount.txt |
UNIX
/etc/opt/FJSVssqc/remoteAccount.txt |
Edit the above file using the definition method described below.
Definition method
This is an ini format file.
Set the sections by connection account groups for communication between the monitoring server and the monitored server.
The method of definition depends on the communication method. Edit to match the communication method.
No | Item | Mandatory/optional | Format | Description |
|---|---|---|---|---|
- | [ACCOUNT] | Mandatory | 63 characters or fewer, using alphanumerics, hyphens (-), periods (.), and hash symbols (#) only | Use an account group name for the section name. Make it so that the section name is a unique character string. |
1 | CONNECTTYPE | Mandatory | SSH | Set the connection method for when using the install-less function for connection.
|
2 | USER | Mandatory | 63 characters or fewer | Set the login account for connection. |
3 | PASSWORD | Mandatory | Character string generated with genpwd (*1) | Set the password for connection. |
*1: Refer to "A.6 genpwd (Password Encryption Command)" for details about how to use the genpwd command to generate encrypted passwords.
Example of definition
The following is an example of connection account definition file when using VMware ESXi.
[ESXi-Account1] CONNECTTYPE=HTTPS USER=httpsuser PASSWORD=C5sJGBE3ONs= |
Define the settings for the virtual environment.
Edit the remote monitoring configuration file (remoteAgent.txt).
Windows
<variable file storage directory>\control\remoteAgent.txt |
UNIX
/etc/opt/FJSVssqc/remoteAgent.txt |
ini file format
Set sections for each server to be monitored.
No | Item | Mandatory/optional | Format | Description |
|---|---|---|---|---|
- | [HOSTNAME] | Mandatory | 63 characters or fewer, using alphanumerics, hyphens (-), periods (.), and hash symbols (#) only | Set an optional section name as the section name. |
1 | HOSTNAME | Mandatory | 63 characters or fewer, using alphanumerics, hyphens (-), periods (.), and hash symbols (#) only | Specify the IP address or host name used for connection to the monitored server. |
2 | DISPLAYNAME | Any | 63 characters or fewer, using alphanumerics, hyphens (-), periods (.), and hash symbols (#) only | Specify the host name displayed in the SQC console. |
3 | VMTYPE | Any | ESXI | Type of monitored virtualization software. ESXI: VMware ESX(https connection), VMware ESXi VMWARE: VMware ESX(ssh connection) |
4 | ACCOUNT | Mandatory | 63 characters or fewer, using alphanumerics, hyphens (-), periods (.), and hash symbols (#) only | Specify a connection account for communicating with the monitored server. |
5 | CONNECTION | Any | ON or OFF | Set ON/OFF for monitoring. |
The following is an example of definitions if the virtualization software is a VMware ESX(ssh connection), VMware ESXi, Hyper-V, Red Hat Virtualization function (KVM), Red Hat Virtualization function (Xen), or Solaris container server
# If the monitoring server is a VMware ESX server: # If the monitoring server is a VMware ESXi server: HOSTNAME=192.0.2.20 DISPLAYNAME=esxi-01 VMTYPE=ESXI ACCOUNT=ESXi-Account1 # If the monitoring server is a Hyper-V server: # When the monitoring server is a Red Hat Virtualization function (KVM) server and is not to be monitored # When the monitoring server is a Red Hat Virtualization function (Xen) server and is not to be monitored: # If the monitoring server is a Solaris container server: |
Refer to "A.1 Server Resource Information Collection Policy Creation Command" and execute sqcRPolicy and sqcSetPolicy.
Point
Perform a check of the text entered into the definitions files during setup. Start the service to check that connection can be made to the monitored server. Warning messages are output to the event log when performance information collection is executed on monitored servers that cannot be connected. Refer to "Common Messages" in the Reference Guide and take the steps described.
If the connection method is Telnet or SSH, deploy a script for agent for Agentless Monitoring management collection in the monitored server. If the deployed script is not required, it can be deleted by executing the agent for Agentless Monitoring management cleanup command.Refer to "sqcAgentlessCleanUp (Agent for Agentless Monitoring Management Collection Script Deletion Command)" in the Reference Guide.
If definitions files (Connection account configuration file and remote monitoring configuration file) have errors, monitored servers that have the errors will not be managed.
When sqcSetPolicy is executed, the following message is output for monitored servers that have been excluded from management due to errors in the definition.
(Warning) : <Install-less Agent> ignored section name[section name] |
The section name defined in "remote monitoring configuration file" is output to "section name".
The following message is also output if any errors are found in a definitions file.
(Warning) : <Install-less Agent> There is an error in definition. |
The following is output to "file name".
Windows
<variable file storage directory>\log\setpolicy_error.log |
UNIX
/var/opt/FJSVssqc/setpolicy_error.log |
If this message appears, check the file content, correct the definitions files (Connection account configuration file and remote monitoring configuration file) according to the message in the file, and then setup again. Refer to "sqcSetPolicy (Policy Application Command)" in the Reference Manual for details about messages output to the file.
Note that collection policy setup must be passed to the console. Refer to "Agents" in the User's Guide (Console Edition) and use the Agent Settings window to collect configuration information.
Note
It takes about 15 to 20 minutes for this information to appear in the console's "UnregisteredAgents folder" after starting the Manager/Proxy Manager service.
If it does not appear, look in the Manager/Proxy Manager's event log/syslog to see if a message has been output.
It is necessary to create directories and files (needed to carry out monitoring) on the server to be monitored when managing with an agent for Agentless Monitoring.
Directories and files are created in the following location:
If the monitored server is a Hyper-V:
When communicating by telnet
%USERPROFILE%\SQC_TEMP directory
%USERPROFILE% : Path name of the user profile folder
If the server to be monitored is a VMware, Red Hat Virtualization function (KVM), Red Hat Virtualization function (Xen) or Solaris container server:
Home directory of the user
The created directory name is as follows:
dsa_temp_***
Do not delete the above directory during monitoring. Performance information will not be collected if this directory is deleted. If this directory is deleted by accident, restart the Manager/Proxy Manager service.
Delete the above directory to exclude the server from monitoring.
