ABD Not Ready

Problem: You run a job and you receive the error message: ABD not ready. Failed to connect to ABD (XX.XX..XX) after [XYZ] seconds

Solution: Resolve the IP issue that prevents network connectivity.

This particular error means that the ABD was likely provisioned and booted correctly by the A2 on your Xen environment, but the IP assigned to the ABD is not routable. In other words, the ABD is OK, but it's networking does not allow the A2 to "see" it. Other machines on your network may "see" it, but the A2 cannot.

Here are some ways to troubleshoot:

1. ABDs default to using DHCP. This is the easiest way to get them working. Double-check that you have DHCP on your network and that your ABD is getting a valid IP by running an ABD diagnostic test.
2. Double-check the Xen network. A wrong Xen network in your ABD settings will make the ABD unreachable to your A2, but possibly visible elsewhere.
3. If you're using a static IP for your ABD, make sure to assign plenty of IPs. This allows you to have more than one job at a time and handles edge-cases, such as error conditions.
4. Find the ABDs in Xen by viewing hidden objects. Log into the ABD using diag/diag from the console. Try pinging the A2 and other machines.