Emerson Exchange 365

• Not Answered

DeltaV Simulate VM Controller

I have a DeltaV Simulate system I am using for training & development. I have successfully created a VM for the ProPlus and 2 Pro workstations. After creating a VM controller with Virtual Studio, I am unable to see them recognized as de-commissioned in DV Explorer.

DV Simulate is version is 13.3

Licenses are as follows:

DV Simulate Networked, Version 13

DV Simulate PPN, Networked

DV Simulate PSN, Networked

DV Simulate PSN, Networked

DV Simulate VM Controller

DV Simulate VM Controller Scaleup; 1 Controller

The 3 VM workstations function correctly and communicate with each other.

Any help would be greatly appreciated.

Bert Bendickson

• 2 Mar 2021 6:01 PM
• Cancel

3 Replies

• Lun.Raznik

  

  • 2 Mar 2021 6:16 PM

  Trying to ping 10.5.255.254, see if you get a reply from one the decommissioned controller(s). If no response, check if the network assignment is correct, e.g., PRIMARY on Pro+ is the same PRIMARY network on the VM controller.
  
  What DVS version are you using?

  • Cancel
• Bert Bendickson

  

  • 19 Mar 2021 2:30 PM

  In reply to Lun.Raznik:

  I get no reply when trying to ping 10.5.255.254
  Do the VM controllers need to be on a separate host machine than the workstations? Are there any patches I may be missing?

  • Cancel
• Sam Egelhof

  

  • 31 Mar 2021 8:18 PM

  I had same issue in VMware, I had to enable Promiscuous Mode as Accept under the Security settings in the VMware vSwitch security configuration on the vm host. HyperV did not have the same issue.

  • Cancel