Agent to Software Repository (SWR) test

This test checks that the Agent can establish an SSL connection to the Software Repository.

There 16 possible results are:

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

SWR – OK

No troubleshooting necessary.

SWR – 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 Software Repository, then no other tests are possible.

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

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

SWR – Unexpected error

This result indicates that the test encountered an unexpected condition.

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

SWR – Connection refused

This result indicates that the Agent is receiving a TCP reset packet when attempting to connect to the Software Repository on port 1003. The likely cause is that the Agent is trying to connect to the wrong IP address. A firewall might also be blocking the connection.

What can I do if the connection is refused during an SWR test?

Check that the name “theword” resolves to the correct IP address. For this information, see Resolving the host name.

Check to make sure that a firewall isn’t refusing the connection to this IP address.

SWR – Connection time-out

This result indicates that the Agent is receiving a TCP reset packet when attempting to connect to the Software Repository on port 1003. 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 Software Repository. A firewall might also be blocking the connection.

What can I do if the connection times out during an SWR test?

Follow the same steps specified in What can I do if the connection is refused during an SWR test? .

SWR – DNS does not resolve

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

What can I do if the software repository name (“theword”) does not resolve during an SWR test?

Log into the server and confirm that the host name “theword” can be resolved. If not, contact your SA administrator so that you can check the DNS configuration of the server.

SWR – Old Agent version

This result indicates that the Agent was unable to contact the Software Repository, 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 SWR test?

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

If you think that the host name of the Software Repository (“theword”) did not resolve, then see SWR – DNS does not resolve.

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

Alternatively, you can upgrade the Agent to the latest version (contact Hewlett Packard Enterprise Customer Support) and re-run the test. See Manage the Server Agent for information how to install a server agent.

SWR - Server identification error

Whenever an Agent makes a request of the Software Repository, the identity of the server is validated to confirm that the server should be allowed access to the information requested. This error indicates that the Software Repository was unable to identify the server being tested, or incorrectly identified that server.

What can I do if I get a server identification error?

The Software Repository identifies servers based on the incoming IP address of the request. To troubleshoot this error, try the following:

Check the Network Settings tab for the server in the SA Client to see if Network Address Translation (NAT) is in use. If it is, make sure that NAT is statically configured, and that only one server is using the NAT address. If multiple servers are using the same IP address, you will need to reconfigure the NAT device.

If the Agent is installed on a cluster, check that each node in the cluster has a unique IP address at which it can be reached. You might have to add static routes to the server to ensure that connections made from that server to the SA core use the unique IP. If NAT is not in use, you can alternately mark the correct interface as the "primary" interface through the Network node under the Inventory panel in server browser, via SA Client.

The server's IP address might have changed recently. If this is the case, stop and restart the Agent. For instructions on how to stop and start an Agent, see Restarting a Server Agent.

SWR – 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 SWR 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.

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

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

Contact your SA administrator.

SWR – 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 Software Repository.

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

Contact your SA administrator.

SWR – Gateway name resolution error

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

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

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

Contact your SA administrator.

SWR – Gateway could not connect to server

The Gateway couldn't establish a connection to the Software Repository. This error might be because the Software Repository is not running, or because the Gateway is resolving the Software Repository host name (“theword”) 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 SWR test?

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

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

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