Description
Performs the connection test for the managed server managed by Systemwalker Software Configuration Manager
The connection test enables you to check whether patch management, software parameter management, or software configuration information management can be performed for the specified managed server. In addition, information about Windows OS patch management (SusClientID(*1)) is collected from managed Windows servers. To perform Windows OS patch management for manually registered Windows servers, it is necessary to collect SusClient IDs beforehand.
Connections tests can also be performed for the admin server.
*1: SusClient ID refers to the key for identifying a WSUS client in WSUS. For this reason, a unique id must be used for each WSUS client. If multiple WSUS clients use the same SusClientId, reallocation is required to resolve the conflict. For information on how to change SusClientID, refer to the information published by Microsoft. Note that SusClientID can also be changed using "swcfmg_register_repsv" (connection destination repository server registration command) provided in Systemwalker Software Configuration Manager. However, the former method (referring to the Microsoft publication) is recommended.
If the option that performs the connection test has also been specified when the server information is registered or updated using swcfmg_server (Server Information Management command) or swcfmg_define_serverinfo (managed server information definition command), the connection test will be automatically performed by Systemwalker Software Configuration Manager.
Execute the connection test in the following cases:
To check whether patch management, software parameter management, or software configuration information management can be performed for the specified managed server
To perform Windows OS patch management for manually registered Windows servers
When the SusClientID of a Windows managed server that has been manually registered and for which Windows OS patch management has already been performed has been changed
Format
Windows
swcfmg_connectiontest.exe {-serverid <Server ID> | [-ip] <IP address>} |
Linux
swcfmg_connectiontest {-serverid <Server ID> | [-ip] <IP address>} |
Options
Specify the server ID or IP address of the server for which the connection test is performed.
Return values
Return value | Meaning |
|---|---|
0 | Completed normally. |
10 | A parameter error has occurred. |
20 | Unable to communicate with the Systemwalker Software Configuration Manager agent. |
21 | File transfer failed. |
30 | Failed to receive the basic product information. |
31 | Failed to receive the basic platform information. |
40 | Unable to analyze the basic information. |
50 | The specified managed server information does not exist. |
100 | Systemwalker Software Configuration Manager is not running. |
101 | A command that cannot be executed at the same time as this command is already running. |
102 | You do not have the permission to execute this command. |
200 | Setup has not been performed. |
255 | A system error has occurred. |
Command location
Admin server
Windows
<Systemwalker Software Configuration Manager installation directory>\SWCFMGM\bin |
Linux
/opt/FJSVcfmgm/bin |
Privilege required/execution environment
Windows
Administrator privileges are required. Execute as an administrator.
This command can be executed on the admin server.
Linux
This command can only be executed by the system administrator (superuser).
This command can be executed on the admin server.
Notes
The connection test results can be checked in the standard output and return values (refer to "Execution result/output format" for information on the standard output and return values).
If this command is executed for a managed server on which an earlier version of Systemwalker Software Configuration Manager is installed, the connection test will fail and the following message will be displayed on the standard output (stdout):
The connection test for the managed server managed by Systemwalker Software Configuration Manager has started. Systemwalker Software Configuration Manager is not installed (UB5IFK3AT@Direct).
To use this command, install the latest version of Systemwalker Software Configuration Manager. Even if an earlier version is used, patch management works as long as the environment is appropriate.
If the connection test fails, patch management cannot be performed correctly for that managed server. Resolve the problem on the particular server. Note that there is an exception:
An earlier version of Systemwalker Software Configuration Manager is installed on the managed server.
In this case, patch management will work correctly as long as the patch management operating environment is correct, even if the connection test fails.
This command cannot be executed at the same time as other commands. An exclusive control error will occur if a command is executed while another command is still running.
Execute this command while Systemwalker Software Configuration Manager is running.
Examples
Windows
swcfmg_connectiontest.exe -serverid UB5IFK3AT@Direct |
Linux
swcfmg_connectiontest -serverid UB5IFK3AT@Direct |
Execution results/output format
Connection test successful. The connection test for the managed server managed by Systemwalker Software Configuration Manager has started. The connection test for the managed server managed by Systemwalker Software Configuration Manager has completed normally (UB5IFK3AT@Direct).
The connection test for the managed server managed by Systemwalker Software Configuration Manager has started. Unable to communicate (UB5IFK3AT@Direct).
20
The file transfer infrastructure might have stopped.
Communication with the managed server might not be possible.
The managed server might have stopped.
Start the file transfer infrastructure using the actions below.
Alternatively, check whether the managed server is running.
[Windows]
Start "Systemwalker File Transfer Library Control (SWCFMG)" using the Windows service.
[Linux]
Execute the following command:
service FJSVlnkcf start
[Solaris]
Execute the following command:
/etc/init.d/FJSVlnkcf start
Alternatively, check whether the managed server is running.
The connection test for the managed server managed by Systemwalker Software Configuration Manager has started. Failed to transfer collected information (UB5IFK3AT@Direct).
21
The file acceptance process for the admin server might have stopped.
Alternatively, the file transfer infrastructure might have stopped.
Restart Systemwalker Software Configuration Manager.
Alternatively, start the file transfer infrastructure using the actions below:
[Windows]
Start "Systemwalker File Transfer Library Control (SWCFMG)" using the Windows service.
[Linux]
Execute the following command:
service FJSVlnkcf start
[Solaris]
Execute the following command:
/etc/init.d/FJSVlnkcf start
The connection test for the managed server managed by Systemwalker Software Configuration Manager has started. Failed to receive the basic information (10.10.10.10).
30
Failed to receive the basic Systemwalker Software Configuration Manager product information.
[Windows]
The Systemwalker Software Configuration Manager product name, version, and server type have not been registered in the registry.
[Linux]
Systemwalker Software Configuration Manager is not installed.
Reinstall Systemwalker Software Configuration Manager.
If the problem persists, contact Fujitsu technical support.
The connection test for the managed server managed by Systemwalker Software Configuration Manager has started. Failed to receive the platform information (10.10.10.10).
31
Failed to receive the basic platform information.
[Windows]
Failed to receive the SusClientId and service pack information from the registry.
[Linux]
Failed to receive the OS release number.
[Solaris]
Failed to receive the OS release level.
If this occurs on the Windows server for which Windows OS patch management is not performed, there is no need to take any action. In other cases, contact Fujitsu technical support.
The connection test for the managed server managed by Systemwalker Software Configuration Manager has started. Failed to register the collected information (10.10.10.10).
40
CMDB might have stopped.
Restart Systemwalker Software Configuration Manager.
If the problem persists, contact Fujitsu technical support.
The connection test for the managed server managed by Systemwalker Software Configuration Manager has started. A system error has occurred (10.10.10.10).
255
Systemwalker Software Configuration Manager might not have been installed correctly.
The execution environment might be invalid.
Restart Systemwalker Software Configuration Manager.
If the problem persists, contact Fujitsu technical support.
