Join this episode for more Stories from the EUC Road as Sean Donahue (Nutanix) and Al Solorzano (E360) tackle this all too familiar question. But does it have to an \u201cOR\u201d statement? Can you have an \u201cAND\u201d statement instead? Tune in to learn more about performance in EUC, happy employees and how you might sleep better at night in the age of Malware and Ransomware.<\/p><\/oembed>

Resources<\/p>

网络注意事项

  • 2016年3月2日
  • 3个答复
  • 1779年的观点
m
徽章 +2
嗨伙计，



我处于部署的中间，并有一个问题。



我们有一对Nexus 3548的表现为10 g的边缘切换到我们的Nuntanix群集，这些群集被抛入了一对Cisco 4500



我们在群集中有4个节点，总共有10个NIC，全部10个演出，并分配给VSPHERE中的VDS。在VDS上，我们将MTU设置为9000



有没有办法将CVM流量与管理流量分开？



我想使CVM流量从上升到4500，但是我们需要在4500上创建SVI，以便我们可以管理它们。



我在Nexus和4500上都遇到了巨型帧错误，当我将VDS上的MTU设置为1500时，错误就会消失。我的猜测是CVM流量是造成问题的原因，我会不再弄乱4500的MTU设置。



什么是最佳练习？其他做什么？



谢谢

    \n

    \nI'm in the middle of a deployment and have a question.

    \n

    \nWe have a pair of Nexus 3548's acting as 10 G edge switch to our Nuntanix Clusters who are trunked up to a pair of Cisco 4500's

    \n

    \nWe have 4 nodes in the cluster with a total of 10 nics all 10 gig and assigned to the VDS in Vsphere. On the VDS we set the MTU to 9000

    \n

    \nIs there a way to separate the CVM traffic from the management traffic?

    \n

    \nI would like to keep the CVM traffic from going up to the 4500's however we needed to create an SVI on the 4500's so we could manage them.

    \n

    \nI'm getting Jumbo frame errors on both the Nexus and the 4500's and when I set the MTU on the VDS back to 1500 the errors went away. My guess is the CVM traffic is what's causing the issues and I would prefre not to mess with the MTU settings on the 4500's.

    \n

    \nWhat is best practice here? What are other doing?

    \n

    \nThanks","quoteUsername":"mikeperrin","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    该主题已关闭以供评论

    3个答复

    Bbbburns
    秩
    UserLevel 3
    徽章 +14
    嗨



    巨型框架有特定的需求吗？我们发现，标准1500字节MTU仍然表现出色。您可能会发现这是您问题的最简单答案，除非您需要满足的艰巨要求，否则我建议您建议这样做。





    如果您需要用于性能或功能（VXLAN / NSX）要求的巨型框架，我们建议您查看以下指南：



    vmware vsphere在nutanix上网络

    http://go.nutanix.com/rs/nutanix/images/nutanix_technote-vmware_vsphere_networking_with_with_nutanix.pdf



    VMware nsx for vSphere

    //www.jhbzcj.com/go/vmware-nsx-for-vsphere.html



    如果您想将CVM的管理流量与CVM的存储流量分开，我们将其称为“多人”或“三足” CVM。除非出于安全原因需要分开，否则我不建议这样做，因为您必须进去并更改CVM中的某些内容。我们在此处记录了程序：



    将CVM连接到多个网络

    https://portal.nutanix.com/#/page/kbs/details?targetId=ka0600000008i7qcaa



    CVM的多个网络将使您能够将启用巨型框架启用的存储接口保持在叶开关上（如果它们相互连接），同时将1500字节MTU MGMT接口放在路由网络上，该网络可以达到4500交换机。



    最终 - 我认为配置太复杂了，无法推荐。



    如果您确实走了启用巨型帧的路径，我建议您确保任何可能的流量的端到端网络路径具有巨型框架能够和配置。
    杰森·伯恩斯|CCIE合作＃20707 |导演技术营销|jason.burns@nutanix.com |@bbbburns

    \n

    \nIs there a specific need for jumbo frames? We find that performance is still excellent with standard 1500 byte MTUs. You may find this is the simplest answer to your problem, and it's what I would recommend unless there is a hard customer requirement you need to satisfy.

    \n

    \n

    \nIf you have a need for jumbo frames for either performance or feature (VXLAN \/ NSX) requirements we recommend taking a look at the following guides:

    \n

    \nVMware vSphere Networking on Nutanix<\/b>

    \nhttp:\/\/go.nutanix.com\/rs\/nutanix\/images\/Nutanix_TechNote-VMware_vSphere_Networking_with_Nutanix.pdf<\/a>

    \n

    \nVMWARE NSX FOR VSPHERE<\/b>

    \n    \/\/www.jhbzcj.com\/go\/vmware-nsx-for-vsphere.html<\/a>

    \n

    \nIf you want to separate the management traffic of the CVM from the storage traffic of the CVM we call this a \"multi-homed\" or \"three-legged\" CVM. I wouldn't recommend this unless separation is required for security reasons, because you'll have to go in and change some things in the CVM. We have the procedure documented here:

    \n

    \nConnecting CVMs to Multiple Networks<\/b>

    \n    https:\/\/portal.nutanix.com\/#\/page\/kbs\/details?targetId=kA0600000008i7qCAA<\/a>

    \n

    \nMultiple networks for the CVM would allow you to keep the jumbo frame enabled storage interface traffic down on the leaf switches (if they're interconnected), while putting the 1500 byte MTU mgmt interface on a routed network that can reach up to the 4500 switches.

    \n

    \nUltimately - I think that configuration is too complex to recommend.

    \n

    \nIf you do go down the path of enabling jumbo frames I'd recommend making sure the end-to-end network path for any possible traffic is jumbo frame capable and configured as such.","quoteUsername":"bbbburns","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    m
    徽章 +2
    Nutanix的VMware Doc使用巨型框架推荐，这就是我们设置它的原因。



    因此，在VDS上，您将MTU设置为1500？

    \n

    \nSo on the VDS you just have the MTU set to 1500?","quoteUsername":"mikeperrin","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    Bbbburns
    秩
    UserLevel 3
    徽章 +14
    麦克风，



    是的 - 1500的默认设置是我在自己的实验室和VSWITCH0 MTU的测试环境中使用的。



    我知道Nutanix（以及一些客户）使用和测试巨型框架的其他一些工程师 - 但他们有自己的实验室网络设置用于端到端巨型。我不能控制自己的所有实验室网络，因此请坚持使用1500。我们进行的所有性能测试（NSX测试除外）也发生在默认MTU时。



    您可以通过端到端的巨型框架获得性能提高，但是（对我来说）额外的复杂性并不值得。Check out Michael Webster's post here for an alternative to my opinion You can decide for yourself based on the performance charts and config complexity which you'd like to use.



    http://longwhiteclouds.com/2013/09/10/the-great-jumbo-frames-debate/



    我强烈同意这句话：

    为什么10G Plus设备不会从工厂配置出来，以接受我不知道的巨型框架。在任何情况下，在设置新的基础架构时，必要的配置是一种琐碎的练习，但是，如果不这样做的话，则在大规模上改造现有的网络交换机，路由器和虚拟环境，这可能会更加困难，更复杂。
    杰森·伯恩斯|CCIE合作＃20707 |导演技术营销|jason.burns@nutanix.com |@bbbburns

    \n

    \nYeah - the default setting of 1500 is what I use in my own lab and test environments for vSwitch0 MTU.

    \n

    \nI know a few of the other engineers at Nutanix (and some customers) use and test jumbo frames - but they have their own lab networks setup for end-to-end jumbo. I don't control all of my own lab network so stick with 1500. All of our performance testing I do (with the exception of NSX testing) also happens with the default MTU.

    \n

    \nYou can get performance gains with end-to-end jumbo frames, but the extra complexity (for me) isn't worth the percentage gains. Check out Michael Webster's post here for an alternative to my opinion 😉 You can decide for yourself based on the performance charts and config complexity which you'd like to use.

    \n

    \nhttp:\/\/longwhiteclouds.com\/2013\/09\/10\/the-great-jumbo-frames-debate\/<\/a>

    \n

    \nThis pull quote is something I strongly agree with:

    \nWhy 10G plus equipment doesn\u2019t come out of the factory configured to accept Jumbo Frames I don\u2019t know. In any case the necessary configuration is a trivial exercise when setting up new infrastructure, but to retrofit existing network switches, routers and the virtual environment on a large scale if it wasn\u2019t done originally can be a little harder and more complex.","quoteUsername":"bbbburns","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