Next I’ll show the distributed switch (under Networking > ): There’s a VM connected to justify that you could do this operation with near 0 interruption (depending on your physical networking it could be happens 1 or 2 ping loss). Let’s assume that vminc0 and vmnic1 are physcially connected with 2 switches in stack with the same VLANs. NOTE: for this example the available physical nics are disconnected because I’m using a lab in a piece of production environment. 6.5… Under Hosts and Clusters > Manage > Networking, Standard vSwitch topology looks like the following : Realizing this operation is really simple, in this example I’ll show how to move:īecause I’m under migrations I couldn’t show the cool ui v. Migrating from VSS to DVS with user interface In some scenarios, if you feel safe with the use of NSX, you could ask to your Network admin only few VLANs (Management, DMZand services) at least 1600MTU (Jumbo Frame is the top)… All network deployments and operations could be handled in vSphere environment with the use of VXLAN, DLR and FLR.(More on this blog stay tuned!).For this reason never share your infrastructure network with other services: use a dedicated 2n switches on top of the rack with 802.1q. This becuase other infrastructure traffic like vMotion and backup requires more available bandwidth as possible to guarantee operational tasks. Virtual infrastructure are networking intensive even if the production traffic stays under 1Gb.For this reason say to your network admin :- keep calm and let vmware admin do his work! – Virtual switches are bringing the best of physical switch without creating loop or handling spanning-tree protocol.Distributed virtual switch enables advanced features and the ability install vib packages eg.: VXLAN and Nexus 1000V (Nexus vib will be discontinued in 2018).For these reason: migrate to last “production” available version to gain new features Now it’s used only for 6.x transition purpose. vSphere 5.5 was the best solution to deploy production infrastructure about 3 years ago. vSphere 4.1 is outdated (really outdated!), the migration to higher version doesn’t mean a vRAM extra bid like happened in vSphere 5.0. Unfortunately I heard about this a lot even if is using vSphere > 4.0.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |