Let’s talk about the networks. So use bond network interfaces with the OLVM. So OLVM supports bond network interfaces which enable the aggregation of multiple physical network interfaces into a single logical bond. And this aggregation enhances network reliability and throughput by providing redundancy and load balancing across bonded interfaces.
It can also work with using VLANs to separate different traffic types. I can use virtual local area networks which are used in OLVM to segment and isolate different types of network traffic within the virtualized environments. The VLANs allow administrators to logically partition a physical network into multiple virtual networks, each identified by unique VLAN IDs.
VLAN is assigned directly to the physical interface. And these VLANs can be directly assigned to a physical network interface. This means that administrators can configure VLAN tagging directly on the physical network interface cards, which are termed as NICs. Each VLAN tag interface can then handle traffic specific to its assigned VLAN, facilitating the network segmentation and management.
So based on these network configurations, OLVM also works with something called as logical network. So each logical network is playing a critical role in ensuring efficient and secure operations of virtualized environments, like the management network is dedicated to handling communication between Oracle Linux Virtualization Manager and the hypervisor host. And this network is essential for tasks that are related to administration monitoring and maintenance.
Then we have got one more logical network that is created, which is called the VM network. And this VM network is used for communication between virtual machines within the virtualized environments, like guest-to-guest communication or internet access, which provides VMs with access to external networks or internal services, which facilitates communication with internal services and resources.
We’ve also got the next level of networks which are called as display networks, which is used for handling remote displays and graphical outputs from virtual machines. This network is particularly important for scenarios where graphical desktop environments or applications running inside VMs need to be accessed remotely, like using the remote desktop access, which enables administrators or users to connect to VM desktops or applications using remote desktop protocols, which is termed as RDPs for Windows, or virtual console access. It provides access to virtual machine consoles for management and troubleshooting purpose.
We have also got networks which are related to migration. The migration network is a dedicated network to facilitate live migration of virtual machines between hypervisor host, without disrupting their operations. So it helps you in data transfers, live migration, and resource optimization.
In the networks, when we create the resources, we also need to configure something called as MAC address. So MAC address can be defined by using something called as MAC address pools. The MAC address pool is actually defined inside your virtualized environments by defining specific ranges for each cluster. It ensures efficient allocation and utilization of MAC addresses and supports scalability across multiple clusters. And it facilitates network management practices that enhance overall system reliability and security.
A MAC address pool is specified for each cluster. And MAC address pools are more efficient with memory allocations. The same MAC address pool can be used by shared multiple clusters, or you can use the same MAC address by multiple different clusters. And the MAC address pool assigns the next available MAC address to the allocation.
When a VM is created within OLVM, the MAC address pool assigns the next available MAC address from the specified range for the particular cluster. This automate assignments ensures that each VM receives a unique MAC address without conflicts.
If the MAC addresses, as we said, can be shared across multiple different clusters, the MAC address pool can be configured across multiple clusters. And this allows administrators to optimize MAC address allocation across different segments of their virtualized environments.
Now let’s see how we can configure a MAC address. You can do that by getting into the administration menu of your administration portal and selecting MAC address pool. And then using this and selecting MAC address pool, you can go for adding the MAC address pool list. There’s a default MAC address pool that is pre-created for you. You can still add new MAC address pools.
When you click on the Add MAC address pool, it opens the new MAC address pool where you’ll provide the name of the MAC address pool. You will allow the options of MAC address ranges. You specify the from range, the to range, defining the MAC address references, which will give you the calculated value of how many MAC addresses are generated for this particular pool. And then you can use this pool by multiple clusters to assign MAC addresses to the virtual machines.
Recent Comments