Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: update RMP caveat


  • An interface cannot belong to multiple bonds.
  • A bond can have subinterfaces, but subinterfaces cannot have a bond. 

  • A bond cannot enslave VLAN subinterfaces.
  • Set all slave ports within a bond to the same speed/duplex and make sure they match the link partner’s slave ports.
  • On a Cumulus RMP switch, if you create a bond with multiple 10G member ports, traffic gets dropped when the bond uses members of the same sdk_intf from the portmap unit listed in the /var/lib/cumulus/porttab file. For example, traffic gets dropped if both swp49 and swp52 are in the bond because they both are in the xe0 unit (or if both swp50 and swp51 are in the same bond because they are both in xe1):
    swp49 xe0 0 0 -1 0
    swp50 xe1 0 0 -1 0
    swp51 xe1 1 0 -1 0
    swp52 xe0 1 0 -1 0
    Single port member bonds, bonds with different sdk_intf, units (xe0 or xe1, as above), or layer 3 bonds do not have this issue.


    LACP is not supported across the 10G ports between two On Cumulus RMP switches, which are built with two Hurricane2 ASICs, you cannot form an LACP bond on links that terminate on different Hurricane2 ASICs.