UIM admins noticed that after robot's IP address was changed, the probes turned red.
Due to the changes in a robot name or IP (or other changes that alter the robot binary code), the robot's probes' magic keys are invalidated. The magic_key is essentially a checksum which is based on a hash of the robot name, ip, and a checksum of the binary for the probe. If any one of those things change, the checksum calculated will no longer match the recorded magic_key. In IM, choosing rt-click-> Security-> Validate->Yes to All forces a re-write of the magic key to the new checksum. It's a security check. Otherwise someone could replace a probe executable with something they had written and it would then be run with the security level of the monitoring software rather than the user.
Component : UIM - ROBOT
Unified Infrastructure Management (UIM), any version
Listed below are links to two articles that offer up options on how to reset the magic key for probes automatically/programmatically:
Is it possible to re-validate a probe via the PU Command?
Re-validate probe via NAS Auto-Operation when FAILED due changes in the probe