StoneGate FW/VPN and SMC 5.3 provide a couple of nice enhancements related to StoneGate’s unique Multi-Link feature.
StoneGate FW/VPN and SMC 5.3 provide a couple of nice enhancements related to StoneGate’s unique Multi-Link feature.
Hello,
I’ve been on your main site looking for something to use as a bit of a sales tool to demonstrate how straightforward it is to set-up multi-homing using Multi-Link. Can’t find anything.
Do you have anything I can point my customers to which is similar to Cisco’s explanation here of how to configure BGP for multi-homing?
http://www.cisco.com/en/US/tech/tk365/technologies_configuration_example09186a008009456d.shtml
Seems like there is an undocumented setting in SMC regarding the Netlinks. You’ll see them when you right-click any Netlink on the Status view and select Netlink state. A new drop-down menu opens with three choises:
1. always enabled 2.always disabled and 3. reset to auto
By default, the state selection setting is “auto”. With this setting, netlink works normally meaning that netlink status probing is taken into account.
1. always enabled
When setting is “always enabled”, netlink remains in active state even if the status probing fails. In other words, it remains active/enabled even if probing shows it to be down. This can be used in situation where netlink status probing doesn’t work reliably. For example if you know that netlink is up and working but probing shows status to be down, setting netlink state to “always enabled” will allow using this netlink as well.
2. Always disabled
Well, this quite clear. When this setting is on the particular netlink is always in inactive/disabled state and doesn’t process traffic.
3. Reset to auto
Last option “reset to auto” can be used to change this setting in engine back to default auto setting if it was previously set to “always enabled” or “always disabled”.
Some details about StoneGate MultiLink VPN and Load Balancing.
Goal is to explain a bit how it works to avoid false expectations.
Link selection is done per packet.
This means that single tcp/udp connection can change link during it’s lifetime.
This provides transparent connection failover of links when using Multi-Link VPN, but this does not mean that consecutive packets would be intelligently routed over different links in order to provide increased bandwidth.
Results, especially on multiple connections, is a de facto aggregation of multiple links performances with transparent failover (the latter is not possible with MultiLink ISP).
For example: there is a customer who has two sites (Site A and Site B) and there is a 1 Mbps connection between them. When the customer put StoneGate Multi-Link VPN there and added another 1Mbps ISP connection, the performance did not double to 2Mbps when it was tested. Why is that?
Because,
Maybe a good analogy is highway where you have 70 miles per hour speed limit. If you add another lane to highway then the speed limit is same (70 miles per hour), but you will get twice as many cars there.
Roar!
hello, can someone explain the shortcomings of bonding and how it compares to stonesoft’s multilink please
Recent Comments