Agent to Data Access Engine (DAE) test

This test checks that the Agent can retrieve its device record from Data Access Engine. The fifteen possible results are:

• DAE – OK
• DAE – Untested
• DAE – Unexpected error
• DAE – Connection refused
• DAE – Connection time-out
• DAE – DNS does not resolve
• DAE – Old Agent version
• DAE – Old Agent version
• DAE – Realm is unreachable
• DAE – No Gateway defined
• DAE – Tunnel setup error
• DAE – Gateway denied access
• DAE – Gateway name resolution error
• DAE – Internal Gateway error
• DAE – Gateway could not connect to server
• DAE – Gateway time-out

DAE – OK

No troubleshooting necessary.

DAE – 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 Data Access Engine then no other tests are possible.

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

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

DAE – Unexpected error

This result indicates that the test encountered an unexpected condition.

What can I do if I get an unexpected error during a DAE 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.

DAE – Connection refused

This result indicates that the Agent is receiving a TCP reset packet when attempting to connect to the Data Access Engine on port 1004. The likely cause is that the Agent is connecting to the wrong IP address. A firewall might also be blocking the connection.

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

Check that the name “spin” resolves to its correct IP address. See Resolving the host name for more information.

Check to make sure that a firewall is not refusing the connection to this IP address.

DAE – 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 Data Access Engine on port 1004. 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. A firewall might also be blocking the connection.

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

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

DAE – DNS does not resolve

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

What can I do if the data access engine name does not resolve during a DAE test?

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

DAE – Old Agent version

This result indicates that the Agent was unable to contact the Data Access Engine, and the test is 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 an DAE test?

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

If you believe that the host name of the Data Access Engine (“way”) did not resolve, then see DAE – DNS does not resolve.

If you determine that the connection was refused, see What can I do if I get an unexpected error during a DAE test? .

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 information about how to install an agent.

DAE – 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 DAE 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

DAE – 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 DAE 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 this file contains a single line as shown:

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

DAE – Tunnel setup error

The Data Access 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 error occurs during a DAE test?

Contact your SA administrator.

DAE – 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 Data Access Engine.

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

Contact your SA administrator.

DAE – Gateway name resolution error

The server running the Gateway in the SA core was unable to resolve the host name “spin”. 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 there is a name resolution error on the gateway during a DAE 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 “spin” can be resolved (for example: “host spin”).

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

DAE – 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 DAE test?

Contact your SA administrator.

DAE – Gateway could not connect to server

The Gateway could not establish a connection to the Data Access Engine. This might be because the Data Access Engine is not running, or because the Gateway is resolving the Data Access Engine host name (“spin”) 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 DAE test?

Check that the name “spin” 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.

DAE – 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 DAE test?

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