Where is LACP in ovs-vsctl show ? | Nutanix Community
Skip to main content
Solved

Where is LACP in ovs-vsctl show ?

focaccio
Forum|alt.badge.img

I am curious why the running “ovs-vsctl show” on a AHV host does not show any “bond” whereas the “ovsdb-client dump | grep -i lacp” command and the Prism GUI show lacp is present (the switch too)

?

Here is the GUI view

full “ovs-vsctl show” output from AHV host:

[root@NTNX-895b5886-A ~]# ovs-vsctl show
84a00041-1b46-44f0-99a1-01a0b1a66713
    Bridge br.mx
        Port br.mx.u.br1
            Interface br.mx.u.br1
                type: patch
                options: {peer=br1.local.d}
        Port br.mx.u.br2
            Interface br.mx.u.br2
                type: patch
                options: {peer=br2.local.d}
        Port br.mx.u.br0
            Interface br.mx.u.br0
                type: patch
                options: {peer=br0.local.d}
        Port br.mx
            Interface br.mx
                type: internal
        Port br.mx.d
            Interface br.mx.d
                type: patch
                options: {peer=br.microseg.u}
    Bridge br.dmx
        Port br.dmx
            Interface br.dmx
                type: internal
        Port br.dmx.u
            Interface br.dmx.u
                type: patch
                options: {peer=br.nf.d}
        Port br.dmx.d.br0
            Interface br.dmx.d.br0
                type: patch
                options: {peer=br0.u}
        Port br.dmx.d.br2
            Interface br.dmx.d.br2
                type: patch
                options: {peer=br2.u}
        Port br.dmx.d.br1
            Interface br.dmx.d.br1
                type: patch
                options: {peer=br1.u}
    Bridge br2.local
        Port br2.local.d
            Interface br2.local.d
                type: patch
                options: {peer=br.mx.u.br2}
        Port br2.local
            Interface br2.local
                type: internal
    Bridge brSpan
        fail_mode: secure
        Port brSpan
            Interface brSpan
                type: internal
    Bridge br.nf
        Port br.nf.d
            Interface br.nf.d
                type: patch
                options: {peer=br.dmx.u}
        Port br.nf
            Interface br.nf
                type: internal
        Port br.nf.u
            Interface br.nf.u
                type: patch
                options: {peer=br.microseg.d}
    Bridge br1.local
        Port br1.local.d
            Interface br1.local.d
                type: patch
                options: {peer=br.mx.u.br1}
        Port br1.local
            Interface br1.local
                type: internal
    Bridge br1
        Port br1
            Interface br1
                type: internal
        Port br1-up
            Interface eth4
            Interface eth3
        Port br1-arp
            Interface br1-arp
                type: vxlan
                options: {key="2", remote_ip="192.168.5.2"}
        Port br1-dhcp
            Interface br1-dhcp
                type: vxlan
                options: {key="2", remote_ip="192.168.86.171"}
        Port br1.u
            Interface br1.u
                type: patch
                options: {peer=br.dmx.d.br1}
    Bridge br.microseg
        Port br.microseg.u
            Interface br.microseg.u
                type: patch
                options: {peer=br.mx.d}
        Port br.microseg.d
            Interface br.microseg.d
                type: patch
                options: {peer=br.nf.u}
        Port br.microseg
            Interface br.microseg
                type: internal
    Bridge br0
        Port br0.u
            Interface br0.u
                type: patch
                options: {peer=br.dmx.d.br0}
        Port br0-dhcp
            Interface br0-dhcp
                type: vxlan
                options: {key="1", remote_ip="192.168.86.171"}
        Port vnet0
            Interface vnet0
        Port br0
            tag: 0
            Interface br0
                type: internal
        Port br0-up
            Interface eth2
            Interface eth1
        Port vnet2
            Interface vnet2
        Port br0-arp
            Interface br0-arp
                type: vxlan
                options: {key="1", remote_ip="192.168.5.2"}
    Bridge br0.local
        Port br0.local
            Interface br0.local
                type: internal
        Port br0.local.d
            Interface br0.local.d
                type: patch
                options: {peer=br.mx.u.br0}
    Bridge br2
        Port vnet4
            tag: 77
            Interface vnet4
        Port br2.u
            Interface br2.u
                type: patch
                options: {peer=br.dmx.d.br2}
        Port br2
            Interface br2
                type: internal
        Port eth0
            Interface eth0
        Port br2-arp
            Interface br2-arp
                type: vxlan
                options: {key="3", remote_ip="192.168.5.2"}
        Port br2-dhcp
            Interface br2-dhcp
                type: vxlan
                options: {key="3", remote_ip="192.168.86.171"}
    ovs_version: "2.14.8"
[root@NTNX-895b5886-A ~]#

Best answer by Nishant1992

manage_ovs show_uplinks  ont the CVM

View original
on-net
Did this topic help you find an answer to your question?

3 replies

N
Forum|alt.badge.img+2
  • Nishant1992
  • Trailblazer
  • 18 replies
  • Answer
  • April 10, 2025

manage_ovs show_uplinks  ont the CVM

focaccio
Forum|alt.badge.img
  • focaccio
  • Author
  • Adventurer
  • 3 replies
  • April 15, 2025

Thanks, that works.  Need to keep in mind that a bond brX-up is a “port” on a bridge.

 

nutanix@NTNX-895b5886-A-CVM:192.168.86.171:~$ manage_ovs show_uplinks
Bridge: br0
  Bond: br0-up
    bond_mode: balance-tcp
    interfaces: eth1 eth2
    lacp: active
    lacp-fallback: True
    lacp_speed: fast
    lacp_status: negotiated
Bridge: br1
  Bond: br1-up
    bond_mode: balance-tcp
    interfaces: eth3 eth4
    lacp: active
    lacp-fallback: True
    lacp_speed: fast
    lacp_status: negotiated
Bridge: br2
  Bond: eth0
    bond_mode: none
    interfaces: eth0
    lacp: off
    lacp-fallback: false
    lacp_speed: slow
    lacp_status: none
nutanix@NTNX-895b5886-A-CVM:192.168.86.171:~$

I think the way I could get something like on the node is:

  1. get a list of bridges: ovs-vsctl list interface |grep name |grep -v _name |grep br |nl
  2. get a list of ports on interesting bridge: ovs-vsctl list-ports br1
  3. looking at br1-up, focus on that: ovs-vsctl list port br1-up
  4. from that SEE bound interfaces shown as uuid list, trace uuids to physical ports with:  
    [root@NTNX-895b5886-A ~]# ovs-vsctl list port br1-up
_uuid               : 7d91390d-8e61-4a88-8c75-0731e8f51535
bond_active_slave   : "a0:36:9f:1f:c1:1a"
bond_downdelay      : 0
bond_fake_iface     : false
bond_mode           : balance-tcp
bond_updelay        : 0
cvlans              : []
external_ids        : {}
fake_bridge         : false
interfaces          : [17e55f0e-c671-4065-8bc5-cb95f466d564, 53ec5f8d-de7e-4d3a-a316-19d2910bb25d]
lacp                : active
mac                 : []
name                : br1-up
other_config        : {lacp-fallback-ab=True, lacp-time=fast}
protected           : false
qos                 : []
rstp_statistics     : {}
rstp_status         : {}
statistics          : {}
status              : {}
tag                 : []
trunks              : []
vlan_mode           : []
[root@NTNX-895b5886-A ~]# ovs-vsctl list interface |grep name |grep -v _name |nl |grep eth
    11  name                : eth0
    15  name                : eth2
    19  name                : eth3
    21  name                : eth4
    32  name                : eth1
[root@NTNX-895b5886-A ~]# ovs-vsctl list interface |grep _uuid |nl |grep 564
    21  _uuid               : 17e55f0e-c671-4065-8bc5-cb95f466d564
[root@NTNX-895b5886-A ~]# ovs-vsctl list interface |grep _uuid |nl |grep 25d
    19  _uuid               : 53ec5f8d-de7e-4d3a-a316-19d2910bb25d
[root@NTNX-895b5886-A ~]#

     

on-net
N
Forum|alt.badge.img+2
  • Nishant1992
  • Trailblazer
  • 18 replies
  • April 15, 2025

 

 

https://nishantpanchal.wordpress.com/2025/01/27/lacp-nutanix-ahv/

 

i keep some note for me in the blogs format 

Reply


Terms & Conditions