Adding additional IP addresses from different ranges will require you to setup VLAN tagging (IEEE 802.1Q networking standard). Our switches support mixed modes i.e. you can have untagged traffic in your main VLAN and tagged traffic in additional VLAN's.
In this example our main VLAN is 453 with range 184.108.40.206/24 and our additional VLAN is 3014 with range 220.127.116.11/24. Because of the mixed setup traffic on our main VLAN can be untagged so we decide not to change anything on the main VLAN.
After the setup on the network switch has been done (contact our support to have that setup) you should add the additional VLAN to your networking setup.
Login to vSpehere Client
Add additional VLAN to Network configuration
- VLAN tagging on VMware 01
Click on "Configuration" tab, "Networking" then "Add Networking..."
- VLAN tagging on VMware 02
The "Add Network Wizard" should show, select "Virtual Machine" as Connection Type and click on Next:
- VLAN tagging on VMware 03
Select "Use vSwitch0" and click Next:
- VLAN tagging on VMware 04
Give an appropriate name as "Network Label", we use 18.104.22.168/24 so we know which IP addresses belong to this network. Give the correspondig VLAN ID of that network (if unsure ask our support), in our example 3014, click on Next:
- VLAN tagging on VMware 05
On the Summary screen check your settings and click on Finish:
Select appropriate network when adding or updating settings of VM
- VLAN tagging on VMware 06
After creating your additional network you can use an IP address from that VLAN when you select that network when creating a VM. For an existing VM click on the VM, click on the "Summary" tab, click on "Edit Settings":
- VLAN tagging on VMware 07
On the Virtual Machine Properties screen go to "Network adapter 1" and select the appropriate "Network label" under "Network Connection":
Setup your VM as usual
After setting up your hypervisor correctly you shouldn't do anything special on your VM. The VM network settings should be setup as usual and you should not be doing VLAN tagging on the VM because the hypervisor will take care of that.