How to Configure VLAN`s on Kemp LoadMaster
The LoadMaster, like many other network appliances, can combine multiple interfaces to create one logical interface. The LoadMaster also can receive traffic from multiple VLANs over a single physical interface.
As networking evolves and increases in complexity, the use of VLANs is more and more commonplace. Often integrating VLAN traffic can be difficult and painstaking. Fortunately the LoadMaster has attempted to simplify this process.
Note: When configuring a LoadMaster interface that you know will be passing tagged VLAN traffic, it is important to note if the traffic will be from multiple VLANs, or just a single VLAN. If only passing a single VLAN's traffic over a specific interface, there will be no need for a special configuration on this interface. You will be able to supply the LoadMaster’s interface with IP addresses and that will be the end of the configuration. Ensure that the local switch is set to access mode for this interface.
If a single physical link will be used to pass along several VLANs worth of traffic, the LoadMaster needs to be configured to do so. Choose the interface to be used and then create many VLANs that will use this single interface. Before creating individual VLANs, you will need to ensure that the interface you will be using, does not currently have any IP addresses configured. When configuring your interface, you will have the ability to specify VLAN IDs and specify IP address(es) for each interface created in this way. In addition to configuring the LoadMaster, the local switch will also need to be configured. A switch’s ports will often need to be set to “trunk mode” and you will be asked to specify which VLANs will have traffic passed through this interface.
Of course, these two useful LoadMaster features can be used in conjunction. If you plan to use VLANs on a bonded interface, ensure to bond the interfaces first to avoid any foreseeable issues.
It seems that firmware 220.127.116.11.20471 doesn't like to create VLANs on bonded interfaces. Needed to remove the bond, then setup the VLAN and recreate the bond.
It would not let you physically do it, or the functionality was not working? The way it has always been, is that you first need to create the bond then create the VLAN.
The create VLAN function would not work. The process would seem to go fine, but the additional interface with the VLAN never appeared. After deleting the bond, the VLAN created just fine and we were able to re-bond the interfaces. It was a weird. This was on a LM-X15.
The problem is not happening today but the units had failed over for no know reason last night. Is there a way to test this.
We also, noticed a problem with the port aggregation. From the documents the Kemp wants the other end to be LACP Active and trunked? connecting to HP Provision Switch