{"docId":"sd00007332en_us","page_html":"<main role=\"main\" class=\"ditasrc\"> <article role=\"article\" aria-labelledby=\"ariaid-title1\">  <h1 class=\"title topictitle1 ryffine-title\" id=\"ariaid-title1\">Network Bonding</h1>  <div class=\"body conbody ryffine-body\">   <p class=\"shortdesc\"></p>   <p class=\"p\" id=\"GUID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290__P_D298E1_D299E1_D300E1_D301E1\">Network bonding is the combining of multiple network adapters into a single logical interface. This is done to build in redundancy and to increase throughput. Network bonds are configured at the operating system level and there are multiple types of network bonds depending on hardware support and other factors.</p>   <p class=\"p\">In the scenarios described in the following sections, we will call out two types of network bonds that are effective for virtualization (active-backup and LACP) and show them in example configurations. VMware LBT bonds are also shown in the table below for the sake of comparison, though only the other two have been utilized in verified scenarios.</p>   <p class=\"p\">Once established, we can later offer up these bonded interfaces as a compute network (for virtual machine traffic) or storage network (for interacting with external storage) when creating our cluster within the VM Essentials manager.</p><img class=\"image\" id=\"GUID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290__IMAGE_VJL_PHG_DHC\" src=\"https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-3959336C-7ECD-49B7-85FC-62198924DE79-high.png\" alt=\"\">  </div> </article></main>","doc_meta":null,"page_meta":null}