22.04.2020, 11:08
OK 
1. I would do VLAN in a managed switch in each panel.
2. Nothing need to be done if done in the switch
3. It is up to you. If the offices are independent and no central commands needed then no need in my opinion but this is project specific. KNX traffic will not go trough VLAN. You can use different ways to send commands to local LMs for example web services.
4. There is no limit on amount of users created. The question is how many users will be connected at the same time. It is really hard to answer this question. There were some tests done by SE you can take them in to account, They were done on older CPU so new can do even more but all depends on all the other load on LM.
Virtual IP can be done like this
Regarding more than one LM on KNX. This is general rule about KNX. You can have only one IP router connected to the same TP as then telegrams will be repeated in the loop. In your case is different. If you have more than one LM connected to the same TP you can do few things, change multicast, disable KNX IP, Protect KNX IP via password, create filters.
BR
1. I would do VLAN in a managed switch in each panel.
2. Nothing need to be done if done in the switch
3. It is up to you. If the offices are independent and no central commands needed then no need in my opinion but this is project specific. KNX traffic will not go trough VLAN. You can use different ways to send commands to local LMs for example web services.
4. There is no limit on amount of users created. The question is how many users will be connected at the same time. It is really hard to answer this question. There were some tests done by SE you can take them in to account, They were done on older CPU so new can do even more but all depends on all the other load on LM.
Virtual IP can be done like this
Code:
os.execute('ifconfig eth0:1 192.168.1.99 up')
os.execute('ifconfig eth0:2 192.168.2.99 up')BR
------------------------------
Ctrl+F5
Ctrl+F5