解决了

Nutanix和NSX

n
徽章 +9
嗨，大家好，

我仍在挖掘，以正确地给我的经理，后者在桌子上贴上果酱的利弊。

由于我需要在不知道他想去的地方进行设计，所以我对此进行了反感。我知道他们想将NSX放在vra和vcloud sp上。

我在Nutanix上找到了NSX上的几个推荐 /技巧，但是在设计部分上没有什么可以使用的（更多关于实现的信息！）是否有人将其集成到4.5群集上？

Nutanix是否计划在NSX上给我们提供技术笔记 /任何其他很酷的东西？

纯粹，

图标

最好的答案VCDXNZ0012015年11月3日，03:19

\n
\nI'm doing the testing for NSX with Nutanix that will be documented in an upcoming tech note. I'm also planning to put a blog together once i've done the testing. The results so far are very good. At a high level Nutanix is invisible to NSX and it really just works. The recommended versions are NSX 6.2 with vSphere \/ ESXi 6.0 U1a (assumes NSX-V). This gives the best features and also the highest performance. I have tested 4.8GB\/s, i.e. line rate, per host with 2 x 10GbE NIC's (scales linearly) and latency of 76us on average between nodes.
\n
\nThe design patterns for NSX in terms of the vSphere clusters will be the same as VMware recommends, Management Cluster, Edge Services Cluster(s), Resource\/Compute Cluster(s). Installation \/ Configuration is also the same. Also as our CVM is just a VM, it also works on an NSX vWire.
\n
\nImportant considerations are MTU size on the underlay network. In my environment I'm using 9216, and I'm using 9000 on the vDS. Due to the VXLAN overhead this makes the maximum MTU of any VM = 8950 bytes. In my case the CVM's are configured with MTU 8950 and are on a NSX vWire\/VXLAN stretched between two different ToR switches. I've configured a leaf spine network architecture with L2 ToR to L3 Spine.
\n
\nIn terms of platform model selection the 1065G4 is a great choice for management clusters and ESG clusters. 3060G4 and 8035G4 or any of the other models make great resource\/compute clusters.
\n
\nNutanix works with vRA, vCloud SP etc, so nothing changes there, again the platform is invisible to them. The value that Nutanix brings is a greatly simplified architecture that is quick to deploy, expand on demand, very simple to manage, and self heals when things go wrong. Deploy in minutes, one click upgrade at lunch time, spend more time doing what you want to do.
\n
\nIf you have any specific questions I'd be happy to answer them.","className":"post__content__best_answer"}">
查看原件
[b] @virttom [/b]，实际上是富裕的，新技术迷，欧洲武术家（或某种;））
\n
\nI'm still digging to give corrects answer to my manager who is puting pros and cons for nutanix on the table.
\n
\nAs I need to make a design without knowing exactly where he want to go, I'm making assomption on it. I understood that they wanted to put NSX on it VRA and vCloud SP.
\n
\nI've found a couple of recommandations \/ tips on NSX over NUTANIX but nothing that can be used on design part (more on implementation which is quite cool !) Do someone have integrated it on a 4.5 cluster ?
\n
\ndo Nutanix plan to give us a technical note \/ any other cool stuff on NSX ?
\n
\nsheers,
\n
\n\ufeff","quoteUsername":"NewVirtTom","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

14个答复

阿卢西亚尼
UserLevel 7
徽章 +34
让我看看我是否可以为您提供一些信息
在Twitter上关注我：https：//twitter.com/angeloluciani
VCDXNZ001
秩
UserLevel 3
徽章 +19
嗨，

我正在使用Nutanix进行NSX的测试，该测试将在即将到来的技术音符中记录。完成测试后，我还计划将博客放在一起。到目前为止的结果非常好。在高水平的Nutanix上是NSX看不见的，它确实可以正常工作。推荐的版本为NSX 6.2，带有VSPHERE / ESXI 6.0 U1A（假设NSX-V）。这提供了最佳功能，也提供了最高的性能。我已经测试了4.8GB/s，即每宿主，使用2 x 10GBE NIC（线性缩放）和节点之间的延迟为76US。

NSX根据VSPHERE簇的设计模式将与VMware推荐，管理集群，Edge Services Services群集，资源/计算集群相同。安装 /配置也相同。同样，由于我们的CVM只是VM，因此它还可以在NSX VWIRE上使用。

重要的考虑因素是底层网络上的MTU大小。在我的环境中，我使用的是9216，并且在VDS上使用了9000。由于VXLAN的头顶，这使得任何VM = 8950字节的最大MTU。在我的情况下，CVM配置了MTU 8950，并在两个不同的TOR开关之间伸展的NSX VWIRE/VXLAN。我已经配置了带有L2 TOR到L3脊柱的Leaf Spine网络体系结构。

在平台模型选择方面，1065G4是管理群集和ESG群集的绝佳选择。3060G4和8035G4或其他任何型号都可以制造出很好的资源/计算簇。

Nutanix与VRA，Vcloud SP等一起使用，因此在那里没有任何变化，他们的平台对他们来说是看不见的。Nutanix带来的价值是一个非常简化的体系结构，可以快速部署，按需扩展，非常简单地管理以及自我治愈，当事情出现问题时就可以自我治愈。几分钟内部署，在午餐时间单击升级，花更多的时间做您想做的事情。

如果您有任何具体问题，我会很乐意回答它们。
\n
\nI'm doing the testing for NSX with Nutanix that will be documented in an upcoming tech note. I'm also planning to put a blog together once i've done the testing. The results so far are very good. At a high level Nutanix is invisible to NSX and it really just works. The recommended versions are NSX 6.2 with vSphere \/ ESXi 6.0 U1a (assumes NSX-V). This gives the best features and also the highest performance. I have tested 4.8GB\/s, i.e. line rate, per host with 2 x 10GbE NIC's (scales linearly) and latency of 76us on average between nodes.
\n
\nThe design patterns for NSX in terms of the vSphere clusters will be the same as VMware recommends, Management Cluster, Edge Services Cluster(s), Resource\/Compute Cluster(s). Installation \/ Configuration is also the same. Also as our CVM is just a VM, it also works on an NSX vWire.
\n
\nImportant considerations are MTU size on the underlay network. In my environment I'm using 9216, and I'm using 9000 on the vDS. Due to the VXLAN overhead this makes the maximum MTU of any VM = 8950 bytes. In my case the CVM's are configured with MTU 8950 and are on a NSX vWire\/VXLAN stretched between two different ToR switches. I've configured a leaf spine network architecture with L2 ToR to L3 Spine.
\n
\nIn terms of platform model selection the 1065G4 is a great choice for management clusters and ESG clusters. 3060G4 and 8035G4 or any of the other models make great resource\/compute clusters.
\n
\nNutanix works with vRA, vCloud SP etc, so nothing changes there, again the platform is invisible to them. The value that Nutanix brings is a greatly simplified architecture that is quick to deploy, expand on demand, very simple to manage, and self heals when things go wrong. Deploy in minutes, one click upgrade at lunch time, spend more time doing what you want to do.
\n
\nIf you have any specific questions I'd be happy to answer them.","quoteUsername":"vcdxnz001","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
n
徽章 +9
嗨，

非常感谢您的分享！当它启动并运行时，我会给您的反馈；）

纯粹，

托马斯
[b] @virttom [/b]，实际上是富裕的，新技术迷，欧洲武术家（或某种;））
\n
\nMany thanks for your sharing ! i'll give you feedback from the trench when it will be up and running ;)
\n
\nsheers,
\n
\nThomas","quoteUsername":"NewVirtTom","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
s
徽章 +4
这可能很有用：

请从NSX防火墙设置中排除CVM IP地址和VIP。否则，NFS安装会断裂。
\n
\nPlease exclude the CVM IP address and VIP from NSX firewall settings. Otherwise, NFS mount breaks.","quoteUsername":"shan","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
n
Userlevel 1
徽章 +4
，，，，

您在经验的地方运行哪个版本的NSX？NSX 6.2甚至没有为您提供选择“ deny”的DFW默认规则的选项，但这是以前版本中设置期间的选项。显然，如果您以默认规则为拒绝将NSX部署为拒绝，则将将每个VM放在一个岛上，包括您的CVM。只是想听听您是否有默认规则的NFS问题，或者可能会影响他们的另一条防火墙规则。

我个人选择不将CVM放在NSX逻辑网络上（并且也免于DFW），只是因为它是所有内容所遍历的基础层，并且不想遇到一个场景NSX的问题也引起了我的存储问题。我走到了为CVM/存储流量和其他DVSWWITCH上的其他物理NIC专用于NSX/常规VM网络上的其他物理NIC。可能是过分的，但是考虑到我最近在VMware产品的新版本中发现的一些错误，我感到更舒服。
\n
\nWhat version of NSX are you running where you experienced that? NSX 6.2 doesn't even give you the option to choose a DFW default rule of \"deny\", but that was an option during setup in previous versions. Obviously, if you deploy NSX with the default rule as deny, it's going to put every VM on an island, including your CVM's. Just interested to hear if you had NFS issues with a default rule of allow, or possibly another firewall rule impacting them.
\n
\nI personally chose not to have the CVM's on an NSX logical network (and they're exempted from DFW as well) just due to the fact that it's the underlying layer everything rides upon, and didn't want to run into a scenario where an issue with NSX also caused me a storage problem. I've gone so far as dedicate separate physical NICs for the CVM\/storage traffic and the other physical NICs on a different dvSwitch for NSX\/regular VM networking. Might be overkill, but I feel more comfortable that way given some of the bugs I've found in newer releases of VMware's products recently.","quoteUsername":"ndolson","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
Bbbburns
秩
UserLevel 2
徽章 +14
跟进此线程 - 我们终于发布了Nutanix解决方案注释，涵盖了VSPhere的VMware NSX。

在此处查看博客：
http://next.nutanix.com/t5/nutanix-connect-blog/nutanix-validates-two-cucial-deployment-scenarios-with-vmware/ba-pare/ba-p/7580

该文档可以在此处找到：
//www.jhbzcj.com/go/vmware-nsx-for-vsphere.html
杰森·伯恩斯|CCIE合作＃20707 |技术营销工程师|jason.burns@nutanix.com |@bbbburns
n
徽章 +9
是的，感谢您参与此线程！我会一次又一次阅读。...我通过VCP时在NSX上待了一段时间;）

托马斯
[b] @virttom [/b]，实际上是富裕的，新技术迷，欧洲武术家（或某种;））
\n
\nThomas","quoteUsername":"NewVirtTom","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
s
徽章 +3
你好Bbbburns VCDXNZ001

我在下面的类似情况下。您是否有可能在上面的帖子中修复链接。我在尝试访问文档时找不到404页。

干杯
苏希尔
VCDXNZ001
秩
UserLevel 3
徽章 +19
感谢您引起我们的注意。我们将修复链接。同时，您应该能够通过Nutanix支持门户访问文档。URL为https://portal.nutanix.com/#/page/solutions/details?targetId=sn-2040_vmware_nsx_for_vsphere：sn-2040_vmware_nsx_for_vsphere。
d
Userlevel 1
徽章 +10
VCDXNZ001和Bbbburns

谢谢（你的）信息 ！
s
徽章 +3
VCDXNZ001

感谢您的URL。不幸的是，它仍在工作。
vcdxnz001<\/a>
\n
\nThanks for URL. Unfortunately It is still working.. perhaps truncated when you posted it. 🙂","quoteUsername":"sushilkm","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
VCDXNZ001
秩
UserLevel 3
徽章 +19
我昨天修复了Orignal URL。但是，您仍然可以在解决方案文档下通过支持门户访问内容。因此，请使用原始URL或支持门户网站上的URLhttps://portal.nutanix.com/#/page/solutions/details?targetId=sn-2040_vmware_nsx_for_vsphere:sn-2040_vmware_nsx_for_for_vspherere。请确保复制完整的URL。
https:\/\/portal.nutanix.com\/#\/page\/solutions\/details?targetId=SN-2040_VMware_NSX_for_vSphere:SN-2040_VMware_NSX_for_vSphere<\/a>. Please make sure to copy the complete URL.","quoteUsername":"vcdxnz001","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
VCDXNZ001
秩
UserLevel 3
徽章 +19
如果您单击URL，它将带您到达门户网站。如果您复制和粘贴，则该工具将无法截断它。
s
徽章 +3
VCDXNZ001

万分感谢。我现在可以访问它。

干杯
苏希尔
vcdxnz001<\/a>
\n
\nThanks a ton. I am able to access it now.
\n
\nCheers
\nsushil","quoteUsername":"sushilkm","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

回复


Baidu