Description
Performs the connection test for the managed server managed by Systemwalker Software Configuration Manager
The connection test allows you to check if patch management works for the specified managed server.
Additionally, it is also possible to discover the Systemwalker Software Configuration Manager product basic information and platform basic information through the connection test.
Connections tests can also be performed for the admin server.
If the option that performs the connection test has also been specified when the server information is registered and 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:
If the managed server information was registered
When checking if patch management works for the managed server
If Systemwalker Software Configuration Manager was upgraded on the managed server
If the managed server was redeployed or rebuilt (*1)
If the Windows managed server SusClientID was changed (*2)
*1) Usually, the connection test is performed when registration and update is performed using swcfmg_server (Server Information Management command) or swcfmg_define_serverinfo (managed server information definition command). If the managed server was redeployed or rebuilt using exactly the same configuration, only the connection test can be performed without the registration and update using swcfmg_server (Server Information Management command) or swcfmg_define_serverinfo (managed server information definition command).
*2) SusClientID is the key that identifies WSUS clients 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 (refer to the Microsoft publication for information on how to change SusClientID). 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.
The following basic information is retrieved in a connection test:
Basic information | Description | |
|---|---|---|
Systemwalker Software Configuration Manager product basic information | Systemwalker Software Configuration Manager version | Systemwalker Software Configuration Manager version installed on the managed server |
Systemwalker Software Configuration Manager server type | Systemwalker Software Configuration Manager server type installed on the managed server
| |
Connection test results | Connection test results | |
Connection test result details | Detailed information when the connection test failed Format <message>. code={<return value>} Note that the messages related to the file transfer infrastructure are displayed in the following format: Format <message> (Cause: {<file transfer infrastructure error code>}). code={<return value>} | |
Platform basic information | SusClientId (Windows only) | WSUS client ID |
Service pack (Windows only) | Service pack | |
Kernel revision number (Linux only) | Kernel revision number | |
Release level (Solaris only) | Release level | |
Format
Windows
swcfmg_connectiontest.exe <IP address> |
Linux
swcfmg_connectiontest <IP address> |
Options
Specifies the admin 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. When using Windows Server 2008 or later, execute this command 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 (10.10.10.10).
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 10.10.10.10 |
Linux
swcfmg_connectiontest 10.10.10.10 |
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 (10.10.10.10).
The connection test for the managed server managed by Systemwalker Software Configuration Manager has started. Unable to communicate (10.10.10.10).
20
One of the following might have occurred:
The file transfer infrastructure (FJSVlnkcf) might have stopped.
Communication with the managed server might not be possible.
The managed server might have stopped.
Start the file transfer infrastructure (FJSVlnkcf) 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 (10.10.10.10).
21
The file acceptance process for the admin server might have stopped.
Alternatively, the file transfer infrastructure (FJSVlnkcf) might have stopped.
Restart Systemwalker Software Configuration Manager.
Alternatively, start the file transfer infrastructure (FJSVlnkcf) 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.
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.
