Hi,
I'm having trouble creating realistic dynamic simulations
I made a xml file as described in the documentation, tried both with the 127.0.0.1 and real IP address of my PC and with different ports: 7001, 161, 1601.
After I run QADeviceSimulator while the element in question is stopped I get following output in QADeviceSimulator:
[2022-11-29 17:46:46:807] (PID: 53772) Please wait... Parsing simulation file: Data.xml[2022-11-29 17:46:46:844] (PID: 53772) The proxy simulation "Data - 127.0.0.1 - 7001" will run for a maximum time of 0 days 0 hours 10 minutes 0 seconds
[2022-11-29 17:46:46:847] (PID: 53772) Simulation started: Data.xml
[2022-11-29 17:46:46:847] (PID: 53772) ->Listening for 127.0.0.1:7001
If I start element which is using same port as defined in xml for creating proxy simulation (7001 in this case) while QADeviceSimulator is running, the QADeviceSimulator will crash/shut down, with nothing in the log file besides the message above.
If the element is already running when I try to create simulation using QADeviceSimulator, the QADeviceSimulator will crash/shut down as soon as it starts.
Let me note that the device in question can only be accessed with VPN and I had to open port 161 to be able to access it with DM element, I could access it using web without opening ports, but not with DM element.
Also, an empty txt file is created in folder ProxySimulations.
Hi Ajdin,
After some investigation an issue was found with parsing the proxy simulation xml file. The device port wasn't stored correctly. This caused the simulator to try to send the packet to the IP of the device on port 0 which would result in the crash you experienced.
A fix has already been made and we aim to ship it with the next feature release of DataMiner.
As a side note, the 'ip' attribute should always be your computer's real IP and not the loopback address 127.0.0.1.
Hi Ajdin,
Did you check the event viewer already? A crash should normally be documented there.
Can you also post the contents of the simulation xml together with the element.xml file? Would be helpful to further investigate this.