The service engine
was unresponsivewhen the EIP Scanner
was configured with an "our IP address" that did not exist on the
host, because the invalid local IP prevented the scanner's networking and
blocked the VM cycle.
The
issue has been addressed and the behavior is now as expected.
To benefit from this fix:
Update your zenon Software
Platform to the latest build of zenon 9 or higher.