解决了

将1 GBE接口到BR0之后，无法访问群集中的CVM

Mbolano73
徽章 +1
嗨，上周，我们用3个节点在委内瑞拉安装了第一个Nutanix集群，它是建立的，作为最佳实践，通过创建BR1，将VSWitch BR0“拆分”到两个Vswitches中，然后分配了10 GBE接口（ETH2和ETH3）将BR0和1 GBE接口（ETH0和ETH1）分配给BR1，集群的管理员决定切换该分配，即通过执行1 GBE接口将1 GBE接口分配给BR0，将10 GBE接口分配给BR1在CVM的命令行上，命令。

allssh manage_ovs -bridge_name br0 -bond_name bond0 - -interface 1G update_uplinks

在对命令的第三个节点响应之后，丢失了与SSH SESION与CVM的连接，现在无法访问CVM来恢复命令SSH连接也不恢复。在节点中，1 GBE接口LED是橙色和红色，只能通过将监视器和键盘连接到物理节点来访问控制台，我的问题是，是否存在一种通过此Phisical Console恢复问题的方法？我们可以做什么？..群集现在正在测试中，但要在下周进行生产。..我已经打开了一个案子。

此致
图标

最好的答案乔恩2016年12月16日，18:40

\n
\nPersonally, unless you absolutely need this level of separation, I'd recommend just having one bond \/ bridge, with just the 10G connections.
\n
\nThe only time I've seen someone actually need it is when they needed to bring in a separate physical network, like a DMZ. Otherwise, just run all your VLANs through the 10G environment, and keep it simple.","className":"post__content__best_answer"}">
查看原件
    \n
    \nallssh manage_ovs --bridge_name br0 --bond_name bond0 --interface 1g update_uplinks<\/i><\/b>
    \n
    \nafter the third node response to the command, the connection to the ssh sesion to the CVM was lost and now can't access the CVMs to revert the command neither ssh connection nor PRISM. In the nodes the 1 GBE interfaces leds are orange and red, only have access to the console by connecting a monitor and a keyboard to the physical nodes, my question is, does exist a way to revert the problem through this phisical console? what we can do?.. The cluster is under test now but it is intended to be in production next week. .. I open a case already.
    \n
    \nBest regards","quoteUsername":"mbolano73","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    该主题已关闭以供评论

    2个答复

    乔恩
    秩
    UserLevel 6
    徽章 +29
    您提到您已经打开了一个案例，这是正确的方向。

    就个人而言，除非您绝对需要这种分离水平，否则我建议只使用一个债券 /桥，只有10G连接。

    我唯一见到某人真正需要它的时间是当他们需要引入单独的物理网络（例如DMZ）时。否则，只需在10G环境中运行所有VLAN，然后将其简单。
    乔恩·科勒|Nutanix工程技术总监|Nutanix NPX＃003，VCDX＃116 |@jonkohler |如果有用的话，请荣誉！
    \n
    \nPersonally, unless you absolutely need this level of separation, I'd recommend just having one bond \/ bridge, with just the 10G connections.
    \n
    \nThe only time I've seen someone actually need it is when they needed to bring in a separate physical network, like a DMZ. Otherwise, just run all your VLANs through the 10G environment, and keep it simple.","quoteUsername":"Jon","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    H
    UserLevel 2
    徽章 +17
    CVM命令创建键接口只是一种脚本，它可以自动分配/创建基础网络（OpenVswitch），您可以通过使用OpenVswwitch命令将您所做的工作逆转以恢复正常状态

    您可以访问每个物理节点并执行以下命令以验证您的作品：

    -OVS-VSCTL show（要显示OpenVswitch端口表，您还可以在此处查看br0 up aos 4.6的键接口）

    -OVS-APPCTL键/show [bond-name]（显示键接口的属性）

    如果您现在陷入混乱，我建议您删除所有债券接口并删除BR1，然后从头开始所有内容以控制您的作品
    \n
    \nYou can access to each physical node and execute the command below to verify your works:
    \n
    \n- ovs-vsctl show (to show the openvswitch port table, you can also see the bond interface here br0-up from AOS 4.6)
    \n
    \n- ovs-appctl bond\/show [bond-name] (to show the properties of the bond interface)
    \n
    \nIf you are in mess now, I recommend deleting all bond interfaces as well as delete the br1 and start everything from scratch to control your works well","quoteUsername":"hienle","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    条款和条件
    Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
    Functional","cookiepolicy.modal.level2":"Normal
    Functional + analytics","cookiepolicy.modal.level3":"Complete
    Functional + analytics + social media + embedded videos"}}}">
    Baidu