Emerson Exchange 365

• Not Answered

Any way to wipe memory for a virtual controller that was left commissioned in an old database - ie equivalent of reset controller to factory defaults

Does anyone know if there is a way to access a virtual controller and wipe it's memory/reset it to decommissioned state?  Situation we have here is we're using Virtual Studio and had a few virtual controllers commissioned into a development system.  We created a new database on the Dev system but forgot to decommission the virtual controllers before we did that...so what's happening now is those controllers are still out there with their previous IP's and if we try to commission a controller to a placeholder in the new database that has an IP the same as those previous controllers, we get comm issues.

I know one solution is to just delete those virtual controllers and re-spool them up from the VM template, but was curious if there was a quicker way (via HTTP interface, or telnet, etc.) that we could connect to them via their IP and reset them so they show up as decommissioned in the new database.

Any tips appreciated...

• virtual controller

gtkrueger

• 12 Oct 2017 6:25 PM
• Cancel

3 Replies

• Andre Dicaire

  

  • 12 Oct 2017 7:38 PM

  I think the fastest way is to delete them and create new ones.
  
  I had this happen where the VM controllers remained commissioned, but I had not controller in the database. (not sure all the details of how we got there). I was able to recreate the node and export it. In the FHX I modified the node to be commissioned to the MAC address of the VM. Imported and the node came up commissioned and downloaded. I then decommissioned successfully. Then I decided this was too much effort and simply deleted the other VM's and recreated them.
  
  This was with DVS 2.3. Have not worked with DVS 3.3 yet to see if anything has changed in that respect. Spinning up a VM controller is takes short amount of time though...

  Andre Dicaire

  • Cancel
• Youssef.El-Bahtimy

  

  • 9 May 2020 3:51 PM

  In reply to Andre Dicaire:

  The new version has a 'Decommission' command in Virtual studio! Doesn't seem to do anything though....

  • Cancel
• Youssef.El-Bahtimy

  

  • 10 May 2020 2:01 AM

  In reply to Youssef.El-Bahtimy:

  unless of course you are connected to the license key. In which case it does indeed decommission the controller.
  I just didn't realize I wasn't connected to the license key, as no error message or warning was issued.
  Anyway, version 3.3.1 has a decommission command and it does work.

  • Cancel