vs1が作成できない | Nutanix Community
Skip to main content

ESXi 8u3 上に Nested 3ノードクラスタを構築しています。
3台 * 16 vCPU / 56 GB / SSD 32G-200G-500G / vmxnet3 4nic

クラスタ構築まではうまくいったのですが、vr1の作成ができない状態です。

vr0の認識がおかしいのも気になります。(後述)

Element UI (VIP)にアクセス後、vr1を作成しようとしても Failed とだけでます。

試しにCVMから以下コマンドで作成しようと試みましたが、エラーとなりました。

CE版の制限やバグなど、何か情報をお持ちの方、教えてください。

nutanix@NTNX-ahv2-A-CVM:192.168.11.15:~$ manage_ovs --bridge_name br1 --interfaces "eth2,eth3" --bond_mode active-backup update_uplinks
OVS error (192.168.5.1 update_uplinks): Command failed: ovs-ofctl show br1: b'ovs-ofctl: br1 is not a bridge or a socket\n'

Input:
{
"args": l
"br1",
C
"eth2",
"eth3"
],
null
],
"cmd": "update_uplinks",
"config_override": {
"enable_vlan_learning": false
},
"kwargs": {
"bond_mode": "active-backup",
"enable_vlan_splinters": true,
"force": false,
"lacp_fallback": "true",
"lacp_mode": "off",
"mtu": null,
"num_arps": 3
}
}

Traceback:
Traceback (most recent call last):
File "/root/acropolis_modules/ovs.py", line 121, in _execute_command
return _enforce_atomic(_ovs_execute)(config, input_obj)
File "/root/acropolis_modules/ovs.py", line 70, in actual_func
return fn(*args, **kwargs)
File "/root/acropolis_modules/ovs.py", line 98, in _ovs_execute
ret = getattr(br_manager, cmd)(*args, **kwargs)
File "/root/acropolis_modules/br_manager.py", line 2055, in update_uplinks
self.update_uplink_vlan_learning(/bridge], delete=True)
File "/root/acropolis_modules/br_manager.py", line 1729, in update_uplink_vlan_learning
br_uplink.update_vlan_learning(delete)
File "/root/acropolis_modules/br_uplink.py", line 427, in update_vlan_learning
flow_commands.extend(self._delete_vlan_learn_flows())
File "/root/acropolis_modules/br_uplink.py", line 381, in _delete_vlan_learn_flows
port_mapping = self._ovs_util.discover_port_mapping(self._br)
File "/root/acropolis_modules/utils.py", line 713, in discover_port_mapping
out = self._run_ofctl_command(x"show %s" % br])
File "/root/acropolis_modules/utils.py", line 146, in _run_ofctl_command
return self._execute_fn(cmd)
File "/root/acropolis_modules/br_manager.py", line 146, in _execute_fn
raise Exception("%s: %s" % (errmsg, err))
Exception: Command failed: ovs-ofctl show br1: b'ovs-ofctl: br1 is not a bridge or a socket\n'

 

CVMでNICは認識している状態です。

nutanix@NTNX-ahv2-A-CVM:192.168.11.15:~$ allssh "manage_ovs show_interfaces"
================== 192.168.11.14 =================
name mode link speed
eth0 10000 True 10000
eth1 10000 True 10000
eth2 10000 True 10000
eth3 10000 True 10000
================== 192.168.11.16 =================
name mode link speed
eth0 10000 True 10000
eth1 10000 True 10000
eth2 10000 True 10000
eth3 10000 True 10000
================== 192.168.11.15 =================
name mode link speed
eth0 10000 True 10000
eth1 10000 True 10000
eth2 10000 True 10000
eth3 10000 True 10000
nutanix@NTNX-ahv2-A-CVM:192.168.11.15:~$

気になっている点としては、Elementでのvr0認識がAHV2号機だけなのが気になります。

 

Hello, 

Could you please send me the result out of this command from one CVM : 

  • allssh manage_ovs show_uplinks

Thanks.


@DylanH 

Thank u for reply.

Result as follow. All 3 node have the same result.

Bridge: br0
Bond: br0-up
bond_mode: active-backup
interfaces: eth0 eth1
lacp: off
lacp-fallback: false
lacp_speed: slow
lacp_status: off

It took a lot of trial and error.
I noticed that I have to create a bridge interface(br1) on the AHV side before CVM add the Uplinks.

ahv# ovs-vsctl add-br br1

It is now as follows.

nutanix@NTNX-ahv2-A-CVM:192.168.11.15:~$ allssh "manage_ovs show_uplinks"
================== 192.168.11.14 =================
Bridge: br0
Bond: br0-up
bond_mode: active-backup
interfaces: eth0 eth1
lacp: off
lacp-fallback: false
lacp_speed: slow
lacp_status: off
Bridge: br1
Bond: br1-up
bond_mode: active-backup
interfaces: eth2 eth3
lacp: off
lacp-fallback: false
lacp_speed: slow
lacp_status: off
================== 192.168.11.16 =================
Bridge: br0
Bond: br0-up
bond_mode: active-backup
interfaces: eth0 eth1
lacp: off
lacp-fallback: false
lacp_speed: slow
lacp_status: off
Bridge: br1
Bond: br1-up
bond_mode: active-backup
interfaces: eth3 eth2
lacp: off
lacp-fallback: false
lacp_speed: slow
lacp_status: off
================== 192.168.11.15 =================
Bridge: br0
Bond: br0-up
bond_mode: active-backup
interfaces: eth0 eth1
lacp: off
lacp-fallback: false
lacp_speed: slow
lacp_status: off
Bridge: br1
Bond: br1-up
bond_mode: active-backup
interfaces: eth2 eth3
lacp: off
lacp-fallback: false
lacp_speed: slow
lacp_status: off
nutanix@NTNX-ahv2-A-CVM:192.168.11.15:~$

 

But now the bridge interface has completely disappeared from Prism, and the Create button is grayed out……

 

Building CE is difficult…..


Ok, if i remember it’s not advised to create bridge through AHV.

Do you have an alert/message notice the inconsistent vswitch ? 

Thanks.


Reply