Linux Bond Guide

Linux Bond Guide

Linux Bond Guide

Preface

This document outlines how to access and use the service on Cloudmylab infrastructure.

This document is intended for use by Cloudmylab Customer. It can be used by anyone working in the Information Technology Sector.

The scope of this document is to specifically ensure that the user understands how to configure bonded interfaces for Ubuntu Desktop 20.04

Process

STEP 1: Create your Ubuntu 20.04 Node with at least 2x Ethernet devices.


STEP 2: Connect your Ubuntu node to the respective network device(s).  Configuring the network device is out of scope for this tutorial.  It will be assumed that LACP is configured on the network device(s) for the remainder of this tutorial.


STEP 3: Login to the Linux node and open the Network Manager.



STEP 4: Select the option to Add another interface.


STEP 5: For the type select Bond under the Virtual interface types.



STEP 6: Add your Ethernet devices to the bond by selecting the Add option on the Bond tab.


STEP 7: Select your connection type, this should usually be an Ethernet type (the default).



STEP 8: Under the Ethernet tab navigate to the dropdown menu labelled Device and select your network device and press Save.


Repeat steps 6 through 8 until you have added all devices required for your bond.
STEP 9: Change the Bond Mode field to 802.3ad to enable LACP on the bonded links and press Save.


STEP 10: Your bond is now created and ready for additional configuration.  On the network connection window highlight the newly created bond and select the configure button.



STEP 11: Select the IPv4 (or v6) Settings tab and configure your interface as required and save once completed.


STEP 12: It is recommended to use the Delete button remove the original Wired connection 1 or 2.  The Final result is show below.


If your connection does not show now for the Last Used column you should reload the networking services or reboot the VM.  Any devices used in the bond should not be configured under another interface.
STEP 13: Verify the bonded connection was successful by pinging a connected network and verifying the bond exists and connects after a reboot.  Examples to help verify the bonded interface are included below.










1) A Common cause that prevents LACPPDUs from transmitting is if the link speed is unable to be automatically negotiated on the member interfaces. Manually setting the link speed         and restarting the networking stack/rebooting should resolve this case.  Be sure to update all member interfaces.

    This can be verified by using the bond0 interface check from step 14 shows Unknown for the Speed of the member.




Manual correction is shown below.


2) Verify the mode is set to 802.3ad for the master interface.



3) Ensure that all member interfaces and the bond appear to be in the UP state.  See step 14 as an example.

Support Information: Please contact support@cloudmylab.com or chat with us at cloudmylab.com





    • Related Articles

    • Ready to Download Linux Images

      Due to very high demand of this section and problems with how to create Linux images under EVE, we are offering ready to go and prepared Linux image pack. You can choose any of Linux image from the pack below and simply upload into EVE. Download your ...
    • CloudMyLab Registration and Account Creation Guide

      INTRODUCTION PREFACE This document outlines how to access and use the service on Cloud My Lab infrastructure. AUDIENCE This document is intended for use for Enterprise Customer and Partners only. SCOPE The scope of this document is to ensure that the ...
    • GNS3 Access Guide

      Getting Access to the Pod There are two methods you can get access to the access detail as mentioned below. Check for the Url and Port Number in the email from support@cloudmylab.com You can alternatively log in to your account and under my account ...
    • Subscription Purchase Guide

      How to Purchase Subscription Example Preface This document outlines how to purchase subscription for CLOUDMYLAB Subscribers Audience This document is intended for use by our Cloudmylab Subscribers Scope The scope of this document is to specifically ...
    • VIRL BYOL Lab Access Guide

      Getting Access to the Pod There are two methods you can get access to the access detail as mentioned below. Check for the Url and Port Number in the email from support@cloudmylab.com You can alternatively log in to your account and under my account ...