解决了

将1个GBE接口修改为br0后无法访问集群中的cvm

  • 2016年12月16日
  • 2回答
  • 1023的浏览量
mbolano73
徽章 ＋1
你好,上周我们安装第一个Nutanix集群在委内瑞拉与3节点,成立作为一个最佳实践,vSwitch br0“峰”两个vSwitch通过创建br1那么对10 GBE接口(eth2和eth3)被分配到br0,对1 GBE接口(eth0和eth1)分配给br1,集群管理员决定切换该分配，即通过在CVM的命令行执行该命令，将1个GBE接口分配给br0, 10个GBE接口分配给br1。

Allssh manage_ovs——bridge_name br0——bond_name bond0——interface 1g update_uplinks . Allssh manage_ovs——bridge_name br0——bond_name bond0——interface 1g update_上行链路

在第三个节点响应命令后，连接到CVM的ssh会话被丢失，现在不能访问CVM来恢复命令，无论是ssh连接还是PRISM。在节点1 GBE接口led是橙色和红色的，只有通过连接显示器和键盘到物理节点访问控制台，我的问题是，是否存在通过这个物理控制台恢复问题的方法?我们能做什么?该集群目前正在测试中，但计划下周投入生产。我已经打开了一个箱子。

致以最亲切的问候
图标

最佳答案乔恩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，并保持简单。
    JonKohler |技术总监，工程，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)，你可以通过使用OpenvSwitch命令逆转你已经做的事情，以回到正常状态

    您可以访问每个物理节点，并执行以下命令来验证您的工作:

    - ovs-vsctl show(显示openvswitch端口表，你也可以在这里看到绑定接口br0-up from AOS 4.6)

    - ovs-appctl bond/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"}}}">

    回复


    Baidu