flexVDI Config main menu shows the following options:
- Network: TCP/IP configuration, creation of virtual bridges, vLANs and bonding interfaces.
- Manager: Installation and configuration of flexVDI Manager.
- OCFS2: Configuration of OCFS2 storage clusters.
- CIFS: Configuration of a CIFS server on this host to be used as a Media Storage.
- Subscription: register the host in flexVDI Customer Portal to enable downloading software updates and flexVDI Manager instance images.
When you select Network in the main menu, you will be presented with the following options:
The first option lets you set up bonds among several physical interfaces. This feature enables the use of multiple network cards as if there was just one. flexVDI Config allows you to configure two different bonding modes:
A new network interface named bondN will be created, where N is the bonding number starting at 0.
Now you have to attach slave devices to this interface:
You will be informed that a new network bridge named virbr0 has been created. Upon returning to the screen of network bridges, you will see you have a new bridge with that name, without any assigned slave. An isolated network bridge like that can be useful to define a subnet of virtual machines without direct access to the outside.
In order to attach a physical interface to the virtual bridge, just follow these steps:
- Select virbr0.
- Select Attach. A list of free network interfaces in that Host will be displayed. Select the one you want to use in order to provide network access to virtual machines (see how network interfaces are named). In our example you would use bond0, but in a simpler scenario you could just select a physical interface like enp2s0:
Like with bondings, you can also remove the network interface from the bridge with the Dettach option, or delete it completely with the Delete option. flexVDI Config will not let you attach more than one interface to a bridge, to avoid the potential creation of a network loop. If you want to use more than one physical network interface with a bridge, aggregate them first with a bond interface.
A new network interface is created with the name virbr0.id, where id is the VLAN identifier; in our example, virbr0.8. Thus, through this interface the host is now able to access the VLAN on that virtual bridge.:
The TCP/IP submenu lets you define the IP network parameters associated with each interface. We will configure the network bridge virbr0 so that the host can access the Internet through it. This will allow us to update the host and download the flexVDI Manager image later. If you created a local VLAN interface in the previous step, configure that interface instead.
- Select Network in the main menu.
- Select TCP/IP.
- You will see a list of all available network interfaces on the host. Interfaces that are slaved to a bonding or a bridge are not shown here:
- Select virbr0 and assign the appropriate parameters to access your corporate network. For example:
Finally, the DNS option of the Network menu allows you to configure DNS servers for host name resolution. Simply enter the DNS option, and configure the address of the name servers you want to use.
Applying network configuration changes