# Scenario 1: Recommended Converged Networking Setup

This is where management and VM traffic is converged over the same bonded interface and storage traffic is independent. This is where management and VM traffic is converged over the same bonded interface and storage traffic is independent, for use cases where management and traffic separation is needed, review Scenario 2.

In an ideal scenario, you would have at least four network interfaces spread across at least two network cards on the host (shown in green on the diagram below). Ideally you would also have two separate network switches to help ensure resiliency and redundancy. As mentioned in the prior section, these networking examples are all created with resiliency and redundancy in mind. One storage lane is connected to each switch and likewise one management/VM lane is connected to each switch, which are bonded in and active/backup configuration. Consult the bonding table in the prior section for more details on the benefits and drawbacks to different types of network bonds.

## Example 1

In this scenario, the bond handles management/VM traffic failover while multipathing handles storage failover. A diagram of such a network setup is shown below:

![A network diagram showing the recommended converged networking setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-84F9CBCF-1190-4DC3-88CF-A70AC53F85F7-high.png)

## Example 2

In the example below, we have native VLAN on the trunk ports and on the storage ports. This means the network switch is tagging all the traffic for you and you don't have to tag it yourself. This allows you to put your IP addresses directly on the interfaces and bonds. Here, the storage VLANS get their own IP address directly on the interface while the management IP address goes directly on the bond as shown in the diagram below. With this configuration, all can be done in the installation wizard as long as the VLANs are piped to the interfaces as expected from the network switches. More specific guidance on using the installation wizard is included in later sections covering the software installation.

NOTE

Your environment an configurations will vary. You may or may not have a native VLAN set up for storage traffic as it is best practice to isolate storage traffic when possible. The need for VLAN tagging on specific interfaces is dependent on whether there is a native VLAN on that interface.

![Networks](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-76104E44-DE07-4703-AF66-9222D2B89CDC-high.png)

Below is a chart showing the connection from the bonded network interfaces created in the example network configuration above to OVS bridges (a virtual switch that connects VMs to the physical network), Virtual Networks (logical virtual networks managed by Libvirt), Libvirt Portgroups (subgroups within Libvirt Networks that can expose configurations, such as VLAN tagging), and tap interfaces (the virtual connection that connects the VM to the OVS bridge).

![Bonded network](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-8A913E31-DFDE-48DE-A616-53438B0C5027-high.png)

## Example 3

The prior example included native VLANs on the trunk ports and storage ports so we'll now take a look at an example configuration without native VLANs. You need to create VLAN tags on the interfaces because the switch is no longer handling the tagging for you. Your IP addresses then go on those VLAN tags. In this example bond0 becomes the compute interface and bond0.x becomes the management interface when configuring the cluster in a later step (see [Creating an HVM cluster](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.html)). When not using a native VLAN, the storage VLANs still get their own IP address and interface but a VLAN interface gets created on the bond and the management IP address goes on the VLAN interface.

![VLAN Interfaces](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-D61D44F7-559C-4867-A289-4C4459C7DFF9-high.png)

Just as in the similar chart above, the chart below shows the connection from the bonded network interfaces created in the example network configuration above to OVS bridges (a virtual switch that connects VMs to the physical network), Virtual Networks (logical virtual networks managed by Libvirt), Libvirt Portgroups (subgroups within Libvirt Networks that can expose configurations, such as VLAN tagging), and tap interfaces (the virtual connection that connects the VM to the OVS bridge).

![bonded network interfaces](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-CED6C104-09D7-4640-A630-DC67E9E0BF61-high.png)

## Example 4

You can use this same networking setup with an LACP bond, but this requires extra configuration on the network switch side. Specifically, you must bond the physical switches into a single logical switch so the MLAG can form. The specific hardware in your environment will dictate the exact setup steps. The network setup would look something like the example below:

![LCAP networking setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-9A6A696D-7DA4-4F58-899D-4D33C086757D-high.png)
