Can you please provide more info on Profile Isolation feature in Layer 2 configuration?
Enable this option if you want to block network traffic between the remote networks, this will not affect the connectivity between them and this local LAN.
Essentially Lets say you have a Head end and two remote ends connecting to it via L2SF. With this enabled the Head end will be able to talk to the remote networks and vice-versa; the remote networks will be able to talk to the head end. However, the remote networks will not be able to talk to each other.
This is something we really need, using your diagram, in case the HQ looses the connection with one of the remote balance i.e. top then the traffic will go to the bottom balance and then to the top right?
Based on the tests we have performed when the connection from the HQ to the top balance is restored the packets are still travelling to through the bottom Balance. Is it a way to define a priority speedfusion on the HQ?
For clarification, assuming the two remote ends are directly connected to each other via Ethernet?
Yes, they are connected on their LAN
You can set HQ Balance to lowest LAN MAC ensure it is a root bridge. Then 2 WAN ports of HQ Balance will always active.
We have tried the lowest MAC, it is working on the testing environment but when we set it to the production we have created a broacast storm. That is why we are asking about the Profile Isolation Feature in Layer 2 Speedfusion. Below is an example diagram
I believe you have opened a support ticket way back in July pertaining this issue. You may want to re-open the same ticket by replying the support email, and our support team could revisit the case.
At that time with that version we could not find a solution, can you please let us know if the 6.2 version will support that, or can someone eventually let us know in detail what is the purpose of the “Profile Isolation” and some usage examples?
Yes, firmware 6.2 will come with SpeedFusion Layer 2 isolation. This feature is mainly to be applied on the main site unit, to prevent remote sites broadcast traffic flow through SpeedFusion tunnel. One of the example would WiFi Hotspot environment, where a big DHCP pool IP addresses (same subnet) share across all the subscribers via our MAX cellular routers, connected via Layer 2 SpeedFusion back to datacenter/Internet-Hub. And all these MAX cellular routers need not communicate to each other, thus the SpeedFusion Layer 2 Isolation will ensure each MAX cellular router only able to communicate to central site.
In your case, you have the switches behind the Peplink units (at Site B &C) that connected directly, which SpeedFusion Layer 2 Isolation won’t able to block any traffic flow through between these 2 switches.
Hope this clarified the matter.
Thanks and regards,