Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 4 subscribers
  • Views 25965 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

cloned UTM no SUM connection

systeembeheerder
Hi,

I cloned a virtual UTM 9.107. Now I want to connect the orginal and the cloned version to a SUM, but somehow it is one that is connected or the other. I suspect that the UTM has an ID (like an GUID in Windows) somewhere, it is using to connect to the SUM. Is there anyway to reset this ID to something else?

Or can someone tell me what the SUM sees as an Unique ID to accept it as a new device?


This thread was automatically locked due to age.
Parents
  • 0
    Hi systeembeheerder,

    you're right. SUM identifies the UTMs by a GUID, which is called "system_id". You can reset this system_id on the cloned machine by running the following command on the UTM (as root): 

    cc reset_system_id


    After restarting the agent, both machines should be available in SUM:  

    /var/mdw/scripts/nextgen-agent restart


    Regards
    Matthias
Reply
  • 0
    Hi systeembeheerder,

    you're right. SUM identifies the UTMs by a GUID, which is called "system_id". You can reset this system_id on the cloned machine by running the following command on the UTM (as root): 

    cc reset_system_id


    After restarting the agent, both machines should be available in SUM:  

    /var/mdw/scripts/nextgen-agent restart


    Regards
    Matthias
Children
No Data
Unfiltered HTML