Robot ID Should Reset on Controller Startup

Idea created by DavidLeDeaux Employee on Sep 16, 2015

    In today's world where cloning VMs is becoming common practice, the robot should generate a new robot device ID upon startup.


    This will prevent discovery_server from ignoring a cloned robot which thereby prevents it being displayed in USM.


    As it stands right now, if a customer is not aware of this conflict, robots won't show up in USM.  Once they log a support case and find out the cause, there maybe hours spent cleaning up and resetting robot device IDs and resetting S_QOS_DATA ci_metric_ids in order for metrics to show up in USM.