解决了

虚拟机网络故障排除

  • 2020年5月12日
  • 5回复
  • 2110的浏览量
J

你好,

如果使用balance-slb，如何确定一个虚拟机正在使用哪个物理设备?

例如，在ESXi中，我运行esxtop，我可以看到哪个物理网卡被“映射”到我的虚拟网卡。AHV有可能吗?如果是，怎么做?

我认为这在你排解疑难问题时很重要。

图标

最佳答案diegodco2020年5月13日，00:29

查看原始
Hello,\u00a0<\/p>

If you use balance-slb, how does one figure out which physical is being used by one VM ?<\/p>

For instance, with ESXi I\u2019d run esxtop, and I can see which physical nic is being \u201cmapped\u201d to my virtual nic. Is it possible with AHV? If yes how ?\u00a0<\/p>

I think it is important when you troubleshoot.<\/p>","quoteUsername":"jgautierit","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

本主题已关闭供评论

5回复

D

嗨

您可以使用网络可视化:

https://portal.nutanix.com/page/documents/kbs/details/?targetId=kA032000000TVfiCAG

https://next.nutanix.com/how-it-works-22/network-visualization-and-network-switch-information-37473

J

这是唯一的办法吗?没有cli命令?

Is it the only way ? No cli commands ?\u00a0<\/p>","quoteUsername":"jgautierit","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
D

我不知道在AHV上匹配esxtop的任何命令。

I don\u2019t know any matching command to esxtop on AHV.<\/p>","quoteUsername":"diegodco","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
J

谢谢您的回答!

Thank you for answering !<\/p>","quoteUsername":"jgautierit","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
bbbburns
排名
Userlevel 2
徽章 + 14

如果你使用balance-slb，你的虚拟机源MAC地址会被OVS转换成一个哈希值(1-255)。然后在bond_rebalance_interval(默认情况下是10秒，Nutanix建议是30秒)在绑定中的活动物理适配器之间平衡这个散列值。

你可以在CVM中使用以下命令查看每个适配器上的活动哈希值:

sshroot@192.168.5.1ovs-appctl债券/显示

你会看到如下输出:

$ SSH root@192.168.5.1 ovs-appctl bond/show

——br0-up

bond_mode: balance-slb

下一个再平衡:4762毫秒

主从mac: 00:e0:ed:73:f3:5f(eth3)

奴隶eth2:启用

may_enable:真

哈希10:5 kB的负载

哈希22:1 kB的负载

哈希34:1 kB的负载

哈希58:1 kB的负载

哈希60:6kb的负载

哈希68:6kb的负载

哈希78,21 kB的负载

哈希81:1 kB的负载

哈希83:1574kb的负载

.．.

奴隶eth3:启用

活跃的奴隶

may_enable:真

hash 2: 2kb的负载

哈希3:11 kB的负载

哈希4:23 kB的负载

哈希8:3 kB的负载

hash 13: 48kb的负载

哈希17:25 kB的负载

哈希19:1 kB的负载

据我所知，没有一种简单的方法来确定哪个MAC地址属于哪个哈希值。因为最多有255个哈希值，并且无法避免哈希冲突，所以可能会有多个VM被哈希为相同的值。

balance-slb的目标是试图将来自多个源MAC地址的流量均匀地分配到一组绑定接口中，并在流量模式变化时保持这种平衡，这是上述策略所实现的。

缺点如下:

  1. 您无法轻松地将单个VM映射到当前活动的链路。
  2. 不能保证任意两个虚拟机映射到对立的绑定成员接口上。

在组播处理方面保持负载均衡还有其他缺点，在AHV网络最佳实践指南-值得一看。

Jason Burns | CCIE Collaboration #20707 |技术营销工程师| jason.burns@nutanix.com | @bbbburns
If you use balance-slb, your VM\u00a0source MAC addresses are converted to a hash (1-255) by OVS. This hash value is then balanced between the active physical adapters in the bond at the bond_rebalance_interval (10 second by default, Nutanix recommends 30 seconds).<\/p>

You can view the active hashes on each adapter by using the following\u00a0command from the CVM:<\/p>

ssh root@192.168.5.1<\/a>\u00a0ovs-appctl bond\/show<\/code><\/p>

\u00a0<\/p>

You\u2019ll see output like:<\/p>

$ ssh root@192.168.5.1 ovs-appctl bond\/show<\/code><\/p>

---- br0-up ----<\/code><\/p>

bond_mode: balance-slb<\/code><\/p>

next rebalance: 4762 ms<\/code><\/p>

active slave mac: 00:e0:ed:73:f3:5f(eth3)<\/code><\/p>

\u00a0<\/p>

slave eth2: enabled<\/code><\/p>

may_enable: true<\/code><\/p>

hash 10: 5 kB load<\/code><\/p>

hash 22: 1 kB load<\/code><\/p>

hash 34: 1 kB load<\/code><\/p>

hash 58: 1 kB load<\/code><\/p>

hash 60: 6 kB load<\/code><\/p>

hash 68: 6 kB load<\/code><\/p>

hash 78: 21 kB load<\/code><\/p>

hash 81: 1 kB load<\/code><\/p>

hash 83: 1574 kB load<\/code><\/p>

...<\/p>

\u00a0<\/p>

slave eth3: enabled<\/code><\/p>

active slave<\/code><\/p>

may_enable: true<\/code><\/p>

hash 2: 2 kB load<\/code><\/p>

hash 3: 11 kB load<\/code><\/p>

hash 4: 23 kB load<\/code><\/p>

hash 8: 3 kB load<\/code><\/p>

hash 13: 48 kB load<\/code><\/p>

hash 17: 25 kB load<\/code><\/p>

hash 19: 1 kB load<\/code><\/p>

\u00a0<\/p>

As far as I know, there is no easy way to determine which MAC addresses belong to which hash value. Since there are a maximum of 255 hash values, and hash collision is not avoided, it\u2019s possible that more than one VM gets hashed to the same value.<\/p>

\u00a0<\/p>

The goal of balance-slb is to attempt to evenly distribute traffic from a number of source MAC addresses among a set of bond interfaces, and maintain that balance over time as traffic patterns change, which the above strategy accomplishes.<\/p>

\u00a0<\/p>

The drawbacks are as follows:<\/p>

  1. You cannot easily map a single VM to the currently active link.<\/li>
  2. You cannot guarantee that any two VMs are mapped to opposing bond member interfaces.<\/li> <\/ol>

    \u00a0<\/p>

    There are other drawbacks to balance-slb around multicast handling, highlighted in the AHV Networking Best Practices Guide<\/a> - which is worth a look.<\/p>","quoteUsername":"bbbburns","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

Baidu