As we moved from BP V6 to V7 we noticed that a number of our schedules were failing. The common symptom was an App Server log showing 'no response from resource PC' with a timeout of 10 minutes. We traced this back to the upwards connectivity from the resource VM's back to our App Servers.
In V6 each resource VM is tightly locked to the App Server the login agent is set to connect through. So long as that VM can see the tied App Server it will both receive and respond. We historically had issues on some machines and had to add some static routes to connect into the App Servers.
IN V7, any App Server can send an instruction to any resource VM (we have 5 hosts and 400+ workers). What tripped us up was that although each worker could reach its own nominated App Server, it could not reach all.
If you are about to move into V7 ... check all resouces can reach all App Servers
If you see schedules fail with 'no response from resource' and a 10 min timeout, speak to your VM management team and ask them to add routing rules to all machines to be able to reach all App Servers.
