Steps for setting the monitoring server are described below.
The following two definition files are necessary to collect performance information from the monitored server.
Define the settings for telnet/ssh communication between 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.
When communicating by telnet
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 when connecting with the agentless function. Set to "TELNET" as this is for telnet connection. |
2 | USER | Mandatory | 63 characters or fewer | Set the login account for telnet connection. |
3 | PASSWORD | Mandatory | Character string generated with genpwd (*1) | Set the password for telnet connection. |
*1: Refer to "A.6 genpwd (password encryption command)" for details about how to use the genpwd command to generate encrypted passwords.
When communicating by ssh
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 when connecting with the agentless function. Set to "SSH" as this is for ssh connection. |
2 | USER | Mandatory | 63 characters or fewer | Set the account for ssh connection. |
3 | PASSWORD | Mandatory | Character string generated with genpwd (*1) | Set the password for ssh 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 definitions when the communication method is telnet or ssh.
# When communicating by telnet [TELNET-ACCOUNT1] CONNECTTYPE=TELNET USER=telnetuser PASSWORD=C5sJGBE3ONs= # When communicating by ssh [SSH-ACCOUNT2] CONNECTTYPE=SSH USER=sshuser PASSWORD=6zAp+gTGDzHyzswPuANqsw== |
Define the settings for the monitored server.
Edit the remote monitoring configuration file (remoteAgent.txt).
Storage location
The file is stored in the following location:
Windows
<variable file storage directory>\control\remoteAgent.txt |
UNIX
/etc/opt/FJSVssqc/remoteAgent.txt |
Edit the above file using the definition method described below.
Definition method
This is an ini format file.
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. Make it so that the section name is a unique character string. It is recommended to use the host 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 system name displayed in the SQC console. Note: HOSTNAME becomes the system name if this is not specified. |
3 | OSTYPE | Any | WINDOWS LINUX SOLARIS AIX HP-UX | OS of the monitored host. WINDOWS: For Windows LINUX: For Linux SOLARIS: For Solaris AIX: For AIX HP-UX: For HP-UX Note: OS is set to the OS of the monitoring server if this is not specified. |
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. Specify the section name of the account group set in remortAccount.txt (Connection account configuration file). |
5 | CONNECTION | Any | ON or OFF | Set ON/OFF for monitoring. Specify "OFF" to stop monitoring. Note: Set to "ON" if this is not specified. |
Example of definition
The following is an example of definitions when the communication method is telnet or ssh.
# If the monitoring server is a Solaris server [host1] HOSTNAME=host1 OSTYPE=SOLARIS ACCOUNT=TELNET-ACCOUNT1 # If the monitoring server is a Linux server # When this monitoring server is not to be monitored [linux-host2] HOSTNAME=192.168.1.2 DISPLAYNAME=host2 OSTYPE=LINUX ACCOUNT=SSH-ACCOUNT2 CONNECTION=OFF |
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 Section 5.1, "Common Messages" in the Reference Guide and take the steps described.
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 Section 1.1.3, "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 Section 1.2.2.3, "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 server to be monitored is a Windows server
%USERPROFILE%\sqc_temp directory
%USERPROFILE% : Path name of the user profile folder
If the server to be monitored is a UNIX 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.
