Systemwalker Software Configuration Manager Software Parameter Setting Guide for ServerView Resource Orchestrator

14.2.2 Action2

Checkpoint

Is error "VSYS40478" output to the Admin Server vsys_trace_log log?

Example

 [2011-01-19 13:20:13,481] ERROR Error :
java.lang.Exception: VSYS40478:start waiting job error. detail=[IpAddress:10.128.159.46,CategoryCode:50,ErrorCode:80,DetailCode:10] server_id=[div01-JZ2M561UR-S-0001] jobname=[cfmg_startwait]
 at com.fujitsu.sop.vsys.vsys.mw.MwSetup.run(MwSetup.java:937)

Cause

Software parameter settings failed because the Admin Server and the deployed L-Server cannot communicate. Since there are a number of possible reasons why communication is not possible, possible causes are shown below:

1. The agent of this product is not installed on the L-Server.

2. If the L-Server is Linux, the system parameters of the operating system have not been tuned.

3. The port (default 9664) used for the file transfer infrastructure on the Admin Server or the L-Server is not set to enable reception.

4. The Admin Server and L-Server are not connected by a network.

5. If multiple NICs are installed on the L-Server, the control NIC is set incorrectly.

6. If the Admin Server or L-Server is connected to multiple routers, the routing settings are not set.

7. Connection using the L-Server (Windows) IP address displayed in the L-Platform Management window is not possible.

Action

1. If the agent of this product is not installed on the L-Server

   Install the agent of this product on the L-Server. Refer to "Installing on Business Server" in the "Installation Guide" for details.

2. If the L-Server is Linux, and the system parameters of the operating system have not been tuned

   Tune the system parameters of the operating system on the L-Server. Refer to "Tuning System Parameters [Linux] " in the "Installation Guide" for details

3. If the port (default 9664) used for the file transfer infrastructure on the Admin Server or the L-Server is not set to enable reception

   Set the port (default 9664) used for the file transfer infrastructure on the Admin Server or the L-Server to enable reception. This requires setting the operating system firewall. Refer to "Check the Port Numbers and Firewall Settings" in the "Installation Guide" for details.

4. If the Admin Server and L-Server are not connected by a network

   Connect the Admin Server and L-Server by a network. For example, perform the following checks and actions:

   • Use the ping command to check if the Admin Server can connect to the L-Server (depending on the firewall, the ping command might not be usable).

   • Check if the network segment to which the L-Server is connected can connect to the Admin Server. If it cannot connect, select a network segment that can connect.

5. If multiple NICs are installed on the L-Server, and the control NIC is set incorrectly

   If multiple NICs are installed on the L-Server, an NIC that can communicate with the Admin Server must be specified as the control NIC. Refer to "Template Information"-"File Information Details" in the "ServerView Resource Orchestrator Cloud Edition Reference Guide (Command/XML)" for information on the specification method.

6. If the Admin Server or L-Server is connected to multiple routers, and the routing settings are not set

   If the Admin Server or L-Server is connected to multiple routers, set the routing settings. Refer to "A.1 Operating Systems" for details.

7. Connection using the L-Server (Windows) IP address displayed in the L-Platform Management window is not possible

   Check the following troubleshooting scenario:

   "14.1 Deployment Is Successful but Connection cannot be Performed Using IP Address of L-Server"