Hi,
I have done everything according to the manual. When I run the simulation it shows it as running, with the ticks and all in the current simulations but I don't see any event list/ statistics/ any sort of simulation taking place. I am new to Nessi, and am finding it very tough to get this rectified.
The log file :
2014 28 03 17:28:50,028 INFO : Starting simulation node [@de.dailab.nessi.beans.SimulationNode]
2014 28 03 17:28:51,025 WARN : JIAC version: JIAC TNG Agent Core version 5.1.3 (21.09.2012 16:28:36) (DAI-Labor, TU Berlin) [@n-26455c19cd6e3]
2014 28 03 17:28:51,257 WARN : Agentnode is: NeSSi2-Node (n-26455c19cd6e3) with owner: satin-local [@n-26455c19cd6e3]
2014 28 03 17:28:51,375 WARN : Adding JMX connector servers for new interface lo with address 127.0.0.1 [@n-26455c19cd6e3.JmxConnectorManager]
2014 28 03 17:28:51,440 WARN : JMX connector server successfully started: service:jmx:rmi://127.0.0.1/stub/rO0ABXNyAC5qYXZheC5tYW5hZ2VtZW50LnJlbW90ZS5ybWkuUk1JU2VydmVySW1wbF9TdHViAAAAAAAAAAICAAB4cgAaamF2YS5ybWkuc2VydmVyLlJlbW90ZVN0dWLp/tzJi+FlGgIAAHhyABxqYXZhLnJtaS5zZXJ2ZXIuUmVtb3RlT2JqZWN002G0kQxhMx4DAAB4cHc0AAtVbmljYXN0UmVmMgAACTEyNy4wLjAuMQAAy+1NEawxRZDZgTpSJ/kAAAFGYo/MsoADAHg= [@n-26455c19cd6e3.JmxConnectorManager]
2014 28 03 17:28:51,553 WARN : Adding JMX connector servers for new interface wlan0 with address 10.33.226.119 [@n-26455c19cd6e3.JmxConnectorManager]
2014 28 03 17:28:51,555 WARN : JMX connector server successfully started: service:jmx:rmi://10.33.226.119/stub/rO0ABXNyAC5qYXZheC5tYW5hZ2VtZW50LnJlbW90ZS5ybWkuUk1JU2VydmVySW1wbF9TdHViAAAAAAAAAAICAAB4cgAaamF2YS5ybWkuc2VydmVyLlJlbW90ZVN0dWLp/tzJi+FlGgIAAHhyABxqYXZhLnJtaS5zZXJ2ZXIuUmVtb3RlT2JqZWN002G0kQxhMx4DAAB4cHc4AAtVbmljYXN0UmVmMgAADTEwLjMzLjIyNi4xMTkAAMvtaAdcEj0n0hA6Uif5AAABRmKPzLKABAB4 [@n-26455c19cd6e3.JmxConnectorManager]
2014 28 03 17:28:51,772 INFO : Starting simulation control agent [@de.dailab.nessi.beans.SimulationNode]
2014 28 03 17:28:52,471 INFO : Simulation environment ready [@de.dailab.nessi.beans.SimulationNode]
2014 29 03 17:29:15,010 INFO : Loaded Application: class de.dailab.ilias.applications.consumer.AbstractProfilebasedConsumer successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,011 INFO : Loaded Application: class de.dailab.ilias.applications.consumer.AdjustableGConsumerApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,013 INFO : Loaded Application: class de.dailab.ilias.applications.consumer.H0AdjustableConsumerApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,014 INFO : Loaded Application: class de.dailab.ilias.applications.consumer.H0ProfileApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,015 INFO : Loaded Application: class de.dailab.ilias.applications.consumer.MultiH0NodeApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,017 INFO : Loaded Application: class de.dailab.ilias.applications.consumer.MultiSmartHomeConsumerApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,018 INFO : Loaded Application: class de.dailab.ilias.applications.consumer.SmartHomeConsumerApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,020 INFO : Loaded Application: class de.dailab.ilias.applications.failure.DeviceFailureApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,022 INFO : Loaded Application: class de.dailab.ilias.applications.failure.LineFailureApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,026 INFO : Loaded Application: class de.dailab.ilias.applications.generation.AdjustablePowerPlantApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,027 INFO : Loaded Application: class de.dailab.ilias.applications.generation.ProducerApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,029 INFO : Loaded Application: class de.dailab.ilias.applications.generation.SolarPowerPlantApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,030 INFO : Loaded Application: class de.dailab.ilias.applications.generation.SolarPowerPlantProfileApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,032 INFO : Loaded Application: class de.dailab.ilias.applications.generation.WindfarmApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,034 INFO : Loaded Application: class de.dailab.ilias.applications.generation.WindfarmProfileApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,040 INFO : Loaded Application: class de.dailab.ilias.applications.ip.IPEnergyFailureApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,041 INFO : Loaded Application: class de.dailab.ilias.applications.load.ConstILoadApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,043 INFO : Loaded Application: class de.dailab.ilias.applications.load.EVChargingApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,046 INFO : Loaded Application: class de.dailab.ilias.applications.prosumer.ProsumerApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,047 INFO : Loaded Application: class de.dailab.ilias.applications.prosumer.StorageApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,049 INFO : Loaded Application: class de.dailab.ilias.applications.special.DelayedLineSwitchApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,050 INFO : Loaded Application: class de.dailab.ilias.applications.special.LineSwitchApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,052 INFO : Loaded Application: class de.dailab.ilias.applications.special.SwingBusApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,063 INFO : Loaded Application: class de.dailab.nessi.applications.ddos.DDoSFSM successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,065 INFO : Loaded Application: class de.dailab.nessi.applications.failure.IPFailureApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,067 INFO : Loaded Application: class de.dailab.nessi.applications.firewall.FirewallApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,069 INFO : Loaded Application: class de.dailab.nessi.applications.scanner.SimplePortScanner successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,071 INFO : Loaded Application: class de.dailab.nessi.applications.sniffer.ArffPacketSniffer successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,078 INFO : Loaded Application: class de.dailab.nessi.applications.sniffer.PacketSnifferApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,081 INFO : Loaded Application: class de.dailab.nessi.applications.tcptest.TCPTestClient successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,084 INFO : Loaded Application: class de.dailab.nessi.applications.tcptest.TCPTestServer successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,086 INFO : Loaded Application: class de.dailab.nessi.applications.tcptest.TCPTestServerThread successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,088 INFO : Loaded Application: class de.dailab.nessi.applications.testConf.QueueClientApplication successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,091 INFO : Loaded Application: class de.dailab.nessi.applications.testConf.QueueServerApplication successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,095 INFO : Loaded Application: class de.dailab.nessi.applications.udp.RandomUDPClient successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,096 INFO : Loaded Application: class de.dailab.nessi.applications.udp.TargetedUDPClient successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,099 INFO : Loaded Application: class de.dailab.nessi.applications.udp.UDPClient successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,101 INFO : Loaded Application: class de.dailab.nessi.applications.udp.UDPServer successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,103 INFO : Loaded Application: class de.dailab.nessi.applications.version.DDoSClientVersion successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,105 INFO : Loaded Application: class de.dailab.nessi.applications.version.ServerVersion successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,107 INFO : Loaded Application: class de.dailab.nessi.applications.version.SimpleClientVersion successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,109 INFO : Loaded Application: class de.dailab.nessi.applications.worm.WormFSM successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,112 INFO : Loaded Application: class de.dailab.nessi.tutorial.EchoClient successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,113 INFO : Loaded Application: class de.dailab.nessi.tutorial.EchoServer successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:16,145 ERROR: de.dailab.nessi.ip.handler.link.Lossless not found. Using default error model for link AccessRouter5 - Client2 [@de.dailab.nessi.ip.handler.PacketForwardingHandler]
2014 29 03 17:29:16,155 ERROR: de.dailab.nessi.ip.handler.link.Lossless not found. Using default error model for link AccessRouter5 - CoreRouter9 [@de.dailab.nessi.ip.handler.PacketForwardingHandler]
2014 29 03 17:29:16,218 ERROR: de.dailab.nessi.ip.handler.link.Lossless not found. Using default error model for link AccessRouter5 - Client3 [@de.dailab.nessi.ip.handler.PacketForwardingHandler]
2014 29 03 17:29:16,270 ERROR: de.dailab.nessi.ip.handler.link.Lossless not found. Using default error model for link AccessRouter5 - Client4 [@de.dailab.nessi.ip.handler.PacketForwardingHandler]
2014 29 03 17:29:16,337 ERROR: de.dailab.nessi.ip.handler.link.Lossless not found. Using default error model for link Server10 - CoreRouter9 [@de.dailab.nessi.ip.handler.PacketForwardingHandler]
2014 29 03 17:29:16,767 INFO : uncompressed: 55919 B [@de.dailab.nessi.hibernate.DAO]
2014 29 03 17:29:16,768 INFO : compressed: 27563 B [@de.dailab.nessi.hibernate
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Simulations in NeSSi2 are only executed in backend by agents and don't support any visualization during execution of a simulation. You can replay and review results after a simulation has been executed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just replayed few of the simulations, and I can see the green flashes for the packets, but again there are no results in the statistics area. And no list of events.
Also, when I use an energy network I get errors such as:
House1 is not an IP device
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Statistics only appear for selected nodes or links, if any event occurred on them. By default only transmitted packets are recorded on links, so clicking on link that showed activity should also provide results in the statistics view.
For the second problem regarding energy networks: I am not sure what you did to create this error. It seems you tried to mix energy network related nodes/applications with IP related nodes/applications. That is something that should not work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As far as the energy network is concerned. I made an IP Network and an Energy network and mapped to work out a simulation for a power meter. It's the case study in the attached paper.
Last edit: Satin 2014-06-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I asked a bit around and did not find anybody that had a clear idea what is going wrong. I was also not able to find the "is not an IP device"-part of the error message in the source code. Is this the exact error message? Also which version of NeSSi2 do you use? If you provide us your simulation project as a zip file, we could try to debug the problem. In the moment we have not a clear idea were the problem is, other than something is wrong with the mapping between energy and IP networks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I looked at the Day1 project: This project is broken in zip file. It is missing the layout for the energy network, which could be a bug in our code. Since you used Day1 and day1 for network names, maybe we were not careful in checking lower and upper cases for file names. As a workaround use different names for energy and IP networks.
Do you use Windows, Linux or MacOs?
A second problem: the scenario2 has no condition for termination condition.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For the energy network simulation. One obvious problem with simulation is that it only has producers. Like a real energy network production/consumption need to be balance.
I will try to find someone in our team that can take a closer look at energy simulation and describe the required changes to make it work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Now, if I try and run a simple energy network with no mappings, just a simple energy network. I get this error:
2014 06 04 15:06:10,962 ERROR: Unable to start simulation [@de.dailab.nessi.beans.SimulationControl]
java.lang.IllegalArgumentException: The feature 'subnets' is not a valid feature
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For your energy simulation. It can be different circumstances, that you can not see any statistics.
1. database settings in recorder configuration:
You does not need to specify the database settings in this xml file. It is enough to specify this in the GUI (Window->Preferences->NeSSi2). If you do these settings in the file (settings are only for the backend), than you should set the same settings also in the GUI, to see the statistics. When you not doing it, than the GUI do not know where the results from the simulation are (which were written from the backend).
2. settings from the energy load calculation for the network (Window->Preferences->NeSSi2->Power Network Handler):
For the example above it was enough to set the 'Base KVA' to 1 000 000 (method: NR). If you have a realy high energy load in the network you can set the method alternativly to GS with the highest 'Base KVA' you can set. (Normally the backend would show errors from the 'LoadFlowUtil' if something goes wrong with the calculation.)
3. mutliple replications:
I saw that, if you simulate more than one replication, the backend shows errors. The first replication is all right, but after that the next replications throwing only errors and there are not any results. I do not know why it is so. You should only simulate one replication per simulation. This one alone should take some time, if it will all be logged.
With the swingbus:
You need only one of them in a scenario. It will show the energy load from the whole network. You should set this application on a network node with no other applications, which produce statistics. Otherwise the statistics can be falsify.
What your error above concerns (House1 is not an IP device):
I also do not know why it comes up. If you get such error try this:
-> remove the scenarios from the simulation
-> save the simulation file
-> close the file
-> open it again
-> add the scenarios
-> save the file again
This solved the problem for me.
I could not solve the problems for you failure simulation, so I wrote a little example, which was attached above.
description:
It contains three simulations:
1. An energy simulation with only a solar power plant and three households.
2. An IP simulation with one server ('EchoServer') and three clients ('EchoClient').
3. A combined simulation from the two above with an link failure in the energy network. If the failure occurs (between Tick 300 and 400) the 'House 5' does not get energy anymore. The corresponding client in the IP simulation also can not send any packets to the server during this time. For this simulation the clients from the IP simulation are mapped to the households from the energy simulation.
I hope this will help you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks Bianca, for the detailed reply. I tried everything that you mentioned. But, I am getting a different error altogether. I have attached the log file in my previous reply to Karsten. I would like to thank you once again, for your help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You still have this problem with the example project we posted before the weekend?
I just downloaded the current NeSSi2 version from NeSSi2 and also downloaded the example and cannot reproduce your problem.
All simulations are executed fine and produced events that can be shown in the statistics view. Both for the energy- and IP-related simulations.
Judging from the log file you posted before. Please make sure your MySQL server is running. At first I received exceptions like the ones in your log file, but than I remembered to start the MySQL server and everything worked.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just checked the server is running. And any how if the server wasn't running, I shouldn't have been able to see IP simulation stats. I am trying the sample project that you sent. Could it be, that Nessi didn't install properly ?
Also is it possible that the sample data that I imported to the database, was not the right one ?
Because the Error: The Feature ' subnets' is not a valid feature doesn't make sense. It's a java.lang.IllegalArgumentException
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't think that installing NeSSi2 could be the cause of the problem. As long as you did not move/delete anything after unpacking the zip-files, everything should work.
What sample data did you import? But this also should only affect one NeSSi2 project/simulation and not all of them.
The error message is also confusing to me, since I was unable to locate it in the source code.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The examples files you are using explains a lot of your problems. This was part of an older version of NeSSi2, which was prior to our energy network simulation support. The changes required to allow the simulation of IP and energy networks and to synchronize events between is not compatible to prior versions.
Hi,
I have done everything according to the manual. When I run the simulation it shows it as running, with the ticks and all in the current simulations but I don't see any event list/ statistics/ any sort of simulation taking place. I am new to Nessi, and am finding it very tough to get this rectified.
The log file :
2014 28 03 17:28:50,028 INFO : Starting simulation node [@de.dailab.nessi.beans.SimulationNode]
2014 28 03 17:28:51,025 WARN : JIAC version: JIAC TNG Agent Core version 5.1.3 (21.09.2012 16:28:36) (DAI-Labor, TU Berlin) [@n-26455c19cd6e3]
2014 28 03 17:28:51,257 WARN : Agentnode is: NeSSi2-Node (n-26455c19cd6e3) with owner: satin-local [@n-26455c19cd6e3]
2014 28 03 17:28:51,375 WARN : Adding JMX connector servers for new interface lo with address 127.0.0.1 [@n-26455c19cd6e3.JmxConnectorManager]
2014 28 03 17:28:51,440 WARN : JMX connector server successfully started: service:jmx:rmi://127.0.0.1/stub/rO0ABXNyAC5qYXZheC5tYW5hZ2VtZW50LnJlbW90ZS5ybWkuUk1JU2VydmVySW1wbF9TdHViAAAAAAAAAAICAAB4cgAaamF2YS5ybWkuc2VydmVyLlJlbW90ZVN0dWLp/tzJi+FlGgIAAHhyABxqYXZhLnJtaS5zZXJ2ZXIuUmVtb3RlT2JqZWN002G0kQxhMx4DAAB4cHc0AAtVbmljYXN0UmVmMgAACTEyNy4wLjAuMQAAy+1NEawxRZDZgTpSJ/kAAAFGYo/MsoADAHg= [@n-26455c19cd6e3.JmxConnectorManager]
2014 28 03 17:28:51,553 WARN : Adding JMX connector servers for new interface wlan0 with address 10.33.226.119 [@n-26455c19cd6e3.JmxConnectorManager]
2014 28 03 17:28:51,555 WARN : JMX connector server successfully started: service:jmx:rmi://10.33.226.119/stub/rO0ABXNyAC5qYXZheC5tYW5hZ2VtZW50LnJlbW90ZS5ybWkuUk1JU2VydmVySW1wbF9TdHViAAAAAAAAAAICAAB4cgAaamF2YS5ybWkuc2VydmVyLlJlbW90ZVN0dWLp/tzJi+FlGgIAAHhyABxqYXZhLnJtaS5zZXJ2ZXIuUmVtb3RlT2JqZWN002G0kQxhMx4DAAB4cHc4AAtVbmljYXN0UmVmMgAADTEwLjMzLjIyNi4xMTkAAMvtaAdcEj0n0hA6Uif5AAABRmKPzLKABAB4 [@n-26455c19cd6e3.JmxConnectorManager]
2014 28 03 17:28:51,772 INFO : Starting simulation control agent [@de.dailab.nessi.beans.SimulationNode]
2014 28 03 17:28:52,471 INFO : Simulation environment ready [@de.dailab.nessi.beans.SimulationNode]
2014 29 03 17:29:15,010 INFO : Loaded Application: class de.dailab.ilias.applications.consumer.AbstractProfilebasedConsumer successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,011 INFO : Loaded Application: class de.dailab.ilias.applications.consumer.AdjustableGConsumerApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,013 INFO : Loaded Application: class de.dailab.ilias.applications.consumer.H0AdjustableConsumerApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,014 INFO : Loaded Application: class de.dailab.ilias.applications.consumer.H0ProfileApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,015 INFO : Loaded Application: class de.dailab.ilias.applications.consumer.MultiH0NodeApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,017 INFO : Loaded Application: class de.dailab.ilias.applications.consumer.MultiSmartHomeConsumerApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,018 INFO : Loaded Application: class de.dailab.ilias.applications.consumer.SmartHomeConsumerApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,020 INFO : Loaded Application: class de.dailab.ilias.applications.failure.DeviceFailureApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,022 INFO : Loaded Application: class de.dailab.ilias.applications.failure.LineFailureApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,026 INFO : Loaded Application: class de.dailab.ilias.applications.generation.AdjustablePowerPlantApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,027 INFO : Loaded Application: class de.dailab.ilias.applications.generation.ProducerApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,029 INFO : Loaded Application: class de.dailab.ilias.applications.generation.SolarPowerPlantApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,030 INFO : Loaded Application: class de.dailab.ilias.applications.generation.SolarPowerPlantProfileApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,032 INFO : Loaded Application: class de.dailab.ilias.applications.generation.WindfarmApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,034 INFO : Loaded Application: class de.dailab.ilias.applications.generation.WindfarmProfileApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,040 INFO : Loaded Application: class de.dailab.ilias.applications.ip.IPEnergyFailureApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,041 INFO : Loaded Application: class de.dailab.ilias.applications.load.ConstILoadApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,043 INFO : Loaded Application: class de.dailab.ilias.applications.load.EVChargingApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,046 INFO : Loaded Application: class de.dailab.ilias.applications.prosumer.ProsumerApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,047 INFO : Loaded Application: class de.dailab.ilias.applications.prosumer.StorageApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,049 INFO : Loaded Application: class de.dailab.ilias.applications.special.DelayedLineSwitchApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,050 INFO : Loaded Application: class de.dailab.ilias.applications.special.LineSwitchApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,052 INFO : Loaded Application: class de.dailab.ilias.applications.special.SwingBusApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,063 INFO : Loaded Application: class de.dailab.nessi.applications.ddos.DDoSFSM successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,065 INFO : Loaded Application: class de.dailab.nessi.applications.failure.IPFailureApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,067 INFO : Loaded Application: class de.dailab.nessi.applications.firewall.FirewallApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,069 INFO : Loaded Application: class de.dailab.nessi.applications.scanner.SimplePortScanner successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,071 INFO : Loaded Application: class de.dailab.nessi.applications.sniffer.ArffPacketSniffer successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,078 INFO : Loaded Application: class de.dailab.nessi.applications.sniffer.PacketSnifferApp successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,081 INFO : Loaded Application: class de.dailab.nessi.applications.tcptest.TCPTestClient successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,084 INFO : Loaded Application: class de.dailab.nessi.applications.tcptest.TCPTestServer successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,086 INFO : Loaded Application: class de.dailab.nessi.applications.tcptest.TCPTestServerThread successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,088 INFO : Loaded Application: class de.dailab.nessi.applications.testConf.QueueClientApplication successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,091 INFO : Loaded Application: class de.dailab.nessi.applications.testConf.QueueServerApplication successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,095 INFO : Loaded Application: class de.dailab.nessi.applications.udp.RandomUDPClient successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,096 INFO : Loaded Application: class de.dailab.nessi.applications.udp.TargetedUDPClient successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,099 INFO : Loaded Application: class de.dailab.nessi.applications.udp.UDPClient successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,101 INFO : Loaded Application: class de.dailab.nessi.applications.udp.UDPServer successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,103 INFO : Loaded Application: class de.dailab.nessi.applications.version.DDoSClientVersion successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,105 INFO : Loaded Application: class de.dailab.nessi.applications.version.ServerVersion successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,107 INFO : Loaded Application: class de.dailab.nessi.applications.version.SimpleClientVersion successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,109 INFO : Loaded Application: class de.dailab.nessi.applications.worm.WormFSM successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,112 INFO : Loaded Application: class de.dailab.nessi.tutorial.EchoClient successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:15,113 INFO : Loaded Application: class de.dailab.nessi.tutorial.EchoServer successfully [@de.dailab.nessi.core.api.JarProcessor]
2014 29 03 17:29:16,145 ERROR: de.dailab.nessi.ip.handler.link.Lossless not found. Using default error model for link AccessRouter5 - Client2 [@de.dailab.nessi.ip.handler.PacketForwardingHandler]
2014 29 03 17:29:16,155 ERROR: de.dailab.nessi.ip.handler.link.Lossless not found. Using default error model for link AccessRouter5 - CoreRouter9 [@de.dailab.nessi.ip.handler.PacketForwardingHandler]
2014 29 03 17:29:16,218 ERROR: de.dailab.nessi.ip.handler.link.Lossless not found. Using default error model for link AccessRouter5 - Client3 [@de.dailab.nessi.ip.handler.PacketForwardingHandler]
2014 29 03 17:29:16,270 ERROR: de.dailab.nessi.ip.handler.link.Lossless not found. Using default error model for link AccessRouter5 - Client4 [@de.dailab.nessi.ip.handler.PacketForwardingHandler]
2014 29 03 17:29:16,337 ERROR: de.dailab.nessi.ip.handler.link.Lossless not found. Using default error model for link Server10 - CoreRouter9 [@de.dailab.nessi.ip.handler.PacketForwardingHandler]
2014 29 03 17:29:16,767 INFO : uncompressed: 55919 B [@de.dailab.nessi.hibernate.DAO]
2014 29 03 17:29:16,768 INFO : compressed: 27563 B [@de.dailab.nessi.hibernate
Simulations in NeSSi2 are only executed in backend by agents and don't support any visualization during execution of a simulation. You can replay and review results after a simulation has been executed.
Thanks Karsten,
I just replayed few of the simulations, and I can see the green flashes for the packets, but again there are no results in the statistics area. And no list of events.
Also, when I use an energy network I get errors such as:
House1 is not an IP device
Statistics only appear for selected nodes or links, if any event occurred on them. By default only transmitted packets are recorded on links, so clicking on link that showed activity should also provide results in the statistics view.
For the second problem regarding energy networks: I am not sure what you did to create this error. It seems you tried to mix energy network related nodes/applications with IP related nodes/applications. That is something that should not work.
Thanks a ton !
As far as the energy network is concerned. I made an IP Network and an Energy network and mapped to work out a simulation for a power meter. It's the case study in the attached paper.
Last edit: Satin 2014-06-04
I asked a bit around and did not find anybody that had a clear idea what is going wrong. I was also not able to find the "is not an IP device"-part of the error message in the source code. Is this the exact error message? Also which version of NeSSi2 do you use? If you provide us your simulation project as a zip file, we could try to debug the problem. In the moment we have not a clear idea were the problem is, other than something is wrong with the mapping between energy and IP networks.
I have attached both the simulations for a simple energy network and the one for a power meter
I looked at the Day1 project: This project is broken in zip file. It is missing the layout for the energy network, which could be a bug in our code. Since you used Day1 and day1 for network names, maybe we were not careful in checking lower and upper cases for file names. As a workaround use different names for energy and IP networks.
Do you use Windows, Linux or MacOs?
A second problem: the scenario2 has no condition for termination condition.
I am using windows, I will make the changes
I changed the name for the ip network in the Day1 project and now the Ip network is also broken.
For the energy network simulation. One obvious problem with simulation is that it only has producers. Like a real energy network production/consumption need to be balance.
I will try to find someone in our team that can take a closer look at energy simulation and describe the required changes to make it work.
Now, if I try and run a simple energy network with no mappings, just a simple energy network. I get this error:
2014 06 04 15:06:10,962 ERROR: Unable to start simulation [@de.dailab.nessi.beans.SimulationControl]
java.lang.IllegalArgumentException: The feature 'subnets' is not a valid feature
I am using nessi 2.1.2
Just a quick update before the long weekend, attached is simple example for the use of IP and energy networks.
Some more details will follow.
Hi,
I ran the simulations. the normal IP one is running smoothly, without any glitches. But, its showing the same error for the other two.
Error: The feature 'subnets' is not a valid feature
Sorry for the late response.
For your energy simulation. It can be different circumstances, that you can not see any statistics.
1. database settings in recorder configuration:
You does not need to specify the database settings in this xml file. It is enough to specify this in the GUI (Window->Preferences->NeSSi2). If you do these settings in the file (settings are only for the backend), than you should set the same settings also in the GUI, to see the statistics. When you not doing it, than the GUI do not know where the results from the simulation are (which were written from the backend).
2. settings from the energy load calculation for the network (Window->Preferences->NeSSi2->Power Network Handler):
For the example above it was enough to set the 'Base KVA' to 1 000 000 (method: NR). If you have a realy high energy load in the network you can set the method alternativly to GS with the highest 'Base KVA' you can set. (Normally the backend would show errors from the 'LoadFlowUtil' if something goes wrong with the calculation.)
3. mutliple replications:
I saw that, if you simulate more than one replication, the backend shows errors. The first replication is all right, but after that the next replications throwing only errors and there are not any results. I do not know why it is so. You should only simulate one replication per simulation. This one alone should take some time, if it will all be logged.
With the swingbus:
You need only one of them in a scenario. It will show the energy load from the whole network. You should set this application on a network node with no other applications, which produce statistics. Otherwise the statistics can be falsify.
What your error above concerns (House1 is not an IP device):
I also do not know why it comes up. If you get such error try this:
-> remove the scenarios from the simulation
-> save the simulation file
-> close the file
-> open it again
-> add the scenarios
-> save the file again
This solved the problem for me.
I could not solve the problems for you failure simulation, so I wrote a little example, which was attached above.
description:
It contains three simulations:
1. An energy simulation with only a solar power plant and three households.
2. An IP simulation with one server ('EchoServer') and three clients ('EchoClient').
3. A combined simulation from the two above with an link failure in the energy network. If the failure occurs (between Tick 300 and 400) the 'House 5' does not get energy anymore. The corresponding client in the IP simulation also can not send any packets to the server during this time. For this simulation the clients from the IP simulation are mapped to the households from the energy simulation.
I hope this will help you.
Thanks Bianca, for the detailed reply. I tried everything that you mentioned. But, I am getting a different error altogether. I have attached the log file in my previous reply to Karsten. I would like to thank you once again, for your help.
The log files point to a problem with your database.
Did I understand correctly that you see some results, but other are not available?
Do you only use the preference page for setting up the database connection?
Are UI, backend and database on the same computer?
For Ip networks, there is no problem with the simulation. Its only when i run energy simulations that I get the error.
Error: The feature 'subnets' is not a valid feature
and it doesn't run the simulation.
Last edit: Satin 2014-06-10
You still have this problem with the example project we posted before the weekend?
I just downloaded the current NeSSi2 version from NeSSi2 and also downloaded the example and cannot reproduce your problem.
All simulations are executed fine and produced events that can be shown in the statistics view. Both for the energy- and IP-related simulations.
Judging from the log file you posted before. Please make sure your MySQL server is running. At first I received exceptions like the ones in your log file, but than I remembered to start the MySQL server and everything worked.
I just checked the server is running. And any how if the server wasn't running, I shouldn't have been able to see IP simulation stats. I am trying the sample project that you sent. Could it be, that Nessi didn't install properly ?
Also is it possible that the sample data that I imported to the database, was not the right one ?
Because the Error: The Feature ' subnets' is not a valid feature doesn't make sense. It's a java.lang.IllegalArgumentException
I don't think that installing NeSSi2 could be the cause of the problem. As long as you did not move/delete anything after unpacking the zip-files, everything should work.
What sample data did you import? But this also should only affect one NeSSi2 project/simulation and not all of them.
The error message is also confusing to me, since I was unable to locate it in the source code.
I have attached the sample data. Also, I am going to install Nessi2 again, would Ubuntu be fine ?
Yes, Ubuntu should work.
The examples files you are using explains a lot of your problems. This was part of an older version of NeSSi2, which was prior to our energy network simulation support. The changes required to allow the simulation of IP and energy networks and to synchronize events between is not compatible to prior versions.
In the current version we also don't provide a SQL dump for executed simulation anymore. As an alternative we provide an example project: http://sourceforge.net/projects/nessi2/files/nessi2/2.1.1-beta/Example-Simulation.zip/download