Customer had issues with a module being reported as offline, but it was actually a network issue between pm1 and the module. current logic assumes the module/instance is down and takes action to move dbroots from that module. In the case where they had a network issue, it fixed itself within 2 couple of minutes. so there was no need to take current failvoer action like try to move dbroots from that module..

Need to see if there is better logic that can be coded to tell difference in a module/server down or the network has an temporary issue.