Troubleshoot > Troubleshoot server communication tests > Agent to Command Engine (CE) test

Agent to Command Engine (CE) test

This test checks that the Agent can connect to the Command Engine and retrieve a command for execution.

The sixteen possible results are:

CE – OK

No troubleshooting necessary.

CE – Untested

This result is returned when a functional area cannot be tested because of a previous failure that prevents further testing. For example, if the Agent cannot reach the Command Engine, then no other tests are possible.

What can I do if a test is not run during a CE test?

First resolve all tests that failed, and then run the Communication Test again.

CE – Unexpected error

This result indicates that the test encountered an unexpected condition.

What can I do if I get an unexpected error during a CE test?

First resolve all tests that failed, and then run the Communication Test again. If the unexpected error recurs, check to see if any additional details in the error message indicate the problem. If the error cannot be resolved, contact Hewlett Packard Enterprise Customer Support.

CE – Connection refused

This result indicates that the Agent is receiving a TCP reset packet when attempting to connect to the Command Engine on port 1018. The likely cause is that the Agent is connecting to the wrong IP address. In other words, the Agent does not know the correct IP address of the Command Engine. It is also possible that a firewall might be blocking the connection.

What can I do if the connection is refused during a CE test?

Check that the name “way” resolves to its correct IP address. For instructions on how to do this, see Resolving the host name.

Check to make sure there isn't a firewall refusing the connection to this IP address.

CE – Connection time-out

This result indicates that the Agent is not receiving any reply packets when it attempts to initiate a TCP connection to the Command Engine on port 1018. The likely cause is that the Agent is connecting to the “wrong” IP address. In other words, the Agent doesn’t know the correct IP address of the Command Engine. A firewall might also be blocking the connection.

What can I do if the connection times out during a CE test?

Follow the same steps specified in What can I do if the connection is refused during a CE test?

CE – DNS does not resolve

This result indicates that the Agent cannot resolve the host name “way” to a valid IP address. In other words, the Agent does not know the correct IP address of the Command Engine.

What can I do if the command engine name does not resolve during a CE test?

Log into the server and confirm that the host name “way” can resolve. If not, check the DNS configuration of the server to make sure that the host name “way” is configured to its correct IP address. See Resolving the host name for more information.

CE – Old Agent version

This result indicates that the Agent was unable to contact the Command Engine, but the test was unable to determine the exact cause because the Agent is out of date.

What can I do if the agent is out of date during a CE test?

If this error occurs, it will likely be for one of two reasons: either the host name of the Command Engine (“way”) did not resolve, or the connection was refused.

If you believe that the host name of the Command Engine (“way”) did not resolve, then CE – DNS does not resolve.

If you determine that the connection was refused, CE – Connection refused.

Alternatively, you can upgrade the Agent to the latest version (contact Hewlett Packard Enterprise Customer Support) and re-run the test. See Run server communication tests for more information about how to install an agent.

CE – Realm is unreachable

The Satellite realm where the managed server is located is unreachable. This error means that a path of tunnels between the Gateways in the SA core and the realm of the managed server cannot be established.

What can I do if the realm is unreachable during a CE test?

This error could be due to a network problem, a malfunctioning or failed Gateway, or a Gateway misconfiguration. Contact your SA administrator for assistance in troubleshooting the Gateway network.

CE – No Gateway defined

The managed server is in a Satellite realm, but its Agent is not properly configured to use a Gateway. Agents located in satellites must use a Gateway to contact the core.

What can I do if no gateway is defined during a CE test?

To troubleshoot this error, try the following:

Create or open the opswgw.args file on the managed server. The opswgw.args file is located on the managed server at:

UNIX/Linux: /etc/opt/opsware/agent

Windows: %SystemDrive%\Program Files\Common Files\Opsware\etc\agent

Make sure that this file contains a single line as shown:

opswgw.gw_list: <gw_ip_address>:<gw_port>,<gw_up_address>:<gw_port>

CE – Tunnel setup error

The Command Engine could not establish a connection through any of its defined Gateways. This could be due to a network problem, a malfunctioning or failed Gateway, or a Gateway misconfiguration.

What can I do if a tunnel setup occurs error during a CE test?

Contact your SA administrator.

CE – Gateway denied access

The Gateway is working, but refused to proxy the connection on behalf of the Agent. This error most likely means that the Gateway is misconfigured such that the Gateway will not allow the Agent to access the Command Engine.

What can I do if the gateway is denied access during a CE test?

Contact your SA administrator.

CE – Gateway name resolution error

The server running the Gateway in the SA core was unable to resolve the host name “way”. It must be able to do this in order to proxy connections on behalf of managed servers in Satellite realms.

What can I do if a name resolution error cccurs on the gateway during a CE test?

Log into the server where the core Gateway is located and use a command such as ping or host to confirm that the host name “way” can be resolved (for example: “host way”).

If you cannot connect, contact your SA administrator so that you can check the DNS configuration of the core Gateway server.

CE – Internal Gateway error

Due to an internal error, the Gateway was unable to proxy the connection. This typically occurs when the Gateway is overloaded.

What can I do if an internal gateway error occurs during a CE test?

Contact your SA administrator.

CE – Gateway could not connect to server

The Gateway could not establish a connection to the Command Engine. The situation might be because the Command Engine is not running, or because the Gateway is resolving the Command Engine host name (“way”) to the wrong IP address. It is also possible that a firewall might be blocking the connection.

What can I do if the gateway can’t connect to server during a CE test?

Check that the name “way” resolves to the correct IP address and that the Gateway can establish a connection to port 1018 at that IP. See Resolving the host name and Verifying that a port is open on a managed server for more information.

CE – Gateway time-out

The Gateways on the two ends of a tunnel could not communicate with each other, most likely due to a network connectivity problem.

What can I do if the gateway times out during a CE test?

Ensure that network connectivity is available between the Gateways in the path between the realm of the managed server and the SA core.

CE – No callback from Agent

The Command Engine was able to contact the Agent, but the Agent did not call back to retrieve its command. However, the Agent reports that it can connect to a Command Engine.

What can I do if there is no callback from Agent?

Ensure network connectivity between the agent and the nearest agent gateway. For example, make sure no firewalls are preventing access. The default port for the agent gateway is 3001. For more information on gateway monitoring, see the SA 10.60 Administer section. For information on configuring the agent gateway, see the SA 10.60 Install section.

Send Help Center feedback