== Video Content ==
 
== Video Content ==
   −
These videos were originally created using the vSphere 5.5 technology - however, the UI and workflows have not substantially changed in vSphere 6.0 U1.  
+
These videos were originally created using the vSphere 5.5 technology - however, the UI and workflows have not substantially changed in vSphere 6.5 U1.  
    
In these "Show Me How" videos we look at how to create a distributed switch, add virtual machine portgroups and VMkernel portgroups to it. The second video shows how to migrate from the Standard Switch to the Distributed Switch. The third and final video is a "Discuss The Options" video with [https://twitter.com/ChrisWahl @ChrisWahl.] Chris talks about the merits of using Standard and Distributed Switches together, and also walks us through the various network bandwidth controls and optimizations available  
 
In these "Show Me How" videos we look at how to create a distributed switch, add virtual machine portgroups and VMkernel portgroups to it. The second video shows how to migrate from the Standard Switch to the Distributed Switch. The third and final video is a "Discuss The Options" video with [https://twitter.com/ChrisWahl @ChrisWahl.] Chris talks about the merits of using Standard and Distributed Switches together, and also walks us through the various network bandwidth controls and optimizations available  
 
'''3.''' Next, '''select what version of Distribute Switch you wish to use'''. Older formats are supported for backwards compatibility in situations where vCenter is managing a cluster of VMware ESXi hosts that have yet to be upgraded to the latest version.  
 
'''3.''' Next, '''select what version of Distribute Switch you wish to use'''. Older formats are supported for backwards compatibility in situations where vCenter is managing a cluster of VMware ESXi hosts that have yet to be upgraded to the latest version.  
   −
[[File:Screen_Shot_2016-04-28_at_10.42.39.png]]
+
[[File:Screen_Shot_2018-02-21_at_11.19.13.png]]
    
'''4. Select the number of uplinks to be assigned'''. The default here is 4 vmnics. In our case vmnic0/1 have been assigned to a Standard vSwitch (vSwitch0), leaving another two physical NICs available (vmnic2/3). These physical adapters will be assigned to the Distributed Switch when we add the VMware ESXi hosts to the Distributed Switch in a later wizard. '''NIOC allows for advanced methods of triaging and prioritising network traffic''' which makes it a more sophisticated method than using Traffic Shaping on its own. '''Finally, you can create an initial portgroup'''. If you do wish for VLAN tagging to be supported this done by modifying the settings of the portgroup after it has been created in this wizard.
 
'''4. Select the number of uplinks to be assigned'''. The default here is 4 vmnics. In our case vmnic0/1 have been assigned to a Standard vSwitch (vSwitch0), leaving another two physical NICs available (vmnic2/3). These physical adapters will be assigned to the Distributed Switch when we add the VMware ESXi hosts to the Distributed Switch in a later wizard. '''NIOC allows for advanced methods of triaging and prioritising network traffic''' which makes it a more sophisticated method than using Traffic Shaping on its own. '''Finally, you can create an initial portgroup'''. If you do wish for VLAN tagging to be supported this done by modifying the settings of the portgroup after it has been created in this wizard.
 
Clicking '''Finish''' will trigger the adding of the ESXi host to the Distributed Switch, and you can confirm the hosts are correctly added and connected from
 
Clicking '''Finish''' will trigger the adding of the ESXi host to the Distributed Switch, and you can confirm the hosts are correctly added and connected from
   −
[[File:Screen_Shot_2014-02-12_at_08.50.46.png]]
+
[[File:Screen_Shot_2018-02-21_at_11.25.43.png]]
    
=== Creating and Modifying Virtual Machine Portgroups ===
 
=== Creating and Modifying Virtual Machine Portgroups ===
 
Once the portgroup has been created then we can transition to creating a VMKernel Port.
 
Once the portgroup has been created then we can transition to creating a VMKernel Port.
   −
'''5.''' Select the VMware ESX host, and under the '''Manage''' tab, and the '''Networking''' column - select the '''VMKernel Adapters''' type
+
'''5.''' Select the VMware ESX host, and under the '''Configure''' tab, and the '''Networking''' section - select the '''VMKernel Adapters'''
    
'''6.''' Click the '''Globe''' icon, to '''Add Host Networking'''
 
'''6.''' Click the '''Globe''' icon, to '''Add Host Networking'''
   −
[[File:Screen_Shot_2014-02-12_at_13.51.04.png]]
+
[[File:Screen_Shot_2018-02-21_at_11.32.23.png]]
    
'''7.''' In the wizard, select '''VMKernel Adapter'''
 
'''7.''' In the wizard, select '''VMKernel Adapter'''
 
'''9.''' In this case under VMkernel port settings we selected Fault Tolerance Logging
 
'''9.''' In this case under VMkernel port settings we selected Fault Tolerance Logging
   −
[[File:Screen_Shot_2016-04-28_at_11.43.32.png]]
+
[[File:Screen_Shot_2018-02-21_at_11.40.02.png]]
    
'''10.''' '''Configure appropriate IP settings as befits your network'''
 
'''10.''' '''Configure appropriate IP settings as befits your network'''
 
'''11.''' After clicking next, the Web Client should refresh, and show the new VMK portgroup with its assign Distributed Switch. These configuration steps need to be repeated for each host  
 
'''11.''' After clicking next, the Web Client should refresh, and show the new VMK portgroup with its assign Distributed Switch. These configuration steps need to be repeated for each host  
   −
[[File:Screen_Shot_2014-02-12_at_14.00.18.png‎ ]]
+
[[File:Screen_Shot_2018-02-21_at_11.50.02.png]]
    
'''Note''': For the configuration status for FT to switch from No, to Yes - the VMware ESXi host must be part of High-Availability Cluster (HA)
 
'''Note''': For the configuration status for FT to switch from No, to Yes - the VMware ESXi host must be part of High-Availability Cluster (HA)
 
The topology view is a good way to get an overhead view on the Distributed Configuration. He was can see the three distributed portgroups; the IP addresses used by the FT VMkernel portgroup; The physical NICs associated with the hosts and the UpLink container. The small (i) information icon allows you to view the settings on each component.
 
The topology view is a good way to get an overhead view on the Distributed Configuration. He was can see the three distributed portgroups; the IP addresses used by the FT VMkernel portgroup; The physical NICs associated with the hosts and the UpLink container. The small (i) information icon allows you to view the settings on each component.
   −
[[File:Screen_Shot_2014-02-12_at_14.57.13.png]]
+
[[File:Screen_Shot_2018-02-21_at_11.55.55.png]]
    
=== Properties ===
 
=== Properties ===
 
* Set a name and contact details for the Administrator
 
* Set a name and contact details for the Administrator
   −
[[File:Screen_Shot_2014-02-12_at_15.48.40.png]]
+
[[File:Screen_Shot_2018-02-21_at_12.06.02.png]]
    
'''The MTU value''' is applied to all communications passing to/from the Distributed Switch - and its important all paths in the communication flow are configured for the correct MTU size. If the MTU size impact on a virtual machine portgroup the MTU size should be adjusted within the guest operating system to a matching size. This is to aviod a scenario called fragmentation. If a 9000 MTU ethernet packet encounters a 1500 system then the packet will be split into 6x1500 packets which will actually reduce performance, and increase the overhead on the device/system that carries out the fragmentation.  
 
'''The MTU value''' is applied to all communications passing to/from the Distributed Switch - and its important all paths in the communication flow are configured for the correct MTU size. If the MTU size impact on a virtual machine portgroup the MTU size should be adjusted within the guest operating system to a matching size. This is to aviod a scenario called fragmentation. If a 9000 MTU ethernet packet encounters a 1500 system then the packet will be split into 6x1500 packets which will actually reduce performance, and increase the overhead on the device/system that carries out the fragmentation.  
 
'''Define the Promiscuous PVLAN'''
 
'''Define the Promiscuous PVLAN'''
   −
'''1.''' Select the Distributed Switch, and click the '''Manage''' tab, and click the '''Settings''' column
+
'''1.''' Select the Distributed Switch, and click the '''Configure''' tab
    
'''2.''' Select '''Private VLAN''', and click the '''Edit''' button
 
'''2.''' Select '''Private VLAN''', and click the '''Edit''' button
 
'''3.''' In the subsequent dialog box, in the left-hand column click '''Add''' and type the PVLAN ID number that '''represents the Promiscuous PVLAN''' - in this case PVLAN ID 103
 
'''3.''' In the subsequent dialog box, in the left-hand column click '''Add''' and type the PVLAN ID number that '''represents the Promiscuous PVLAN''' - in this case PVLAN ID 103
   −
[[File:Screen_Shot_2014-02-21_at_10.55.35.png]]  
+
[[File:Screen_Shot_2018-02-21_at_12.23.32.png]]  
    
Notice how along side every Promiscuous PVLAN, a secondary PVLAN is created.  
 
Notice how along side every Promiscuous PVLAN, a secondary PVLAN is created.  
 
'''Enabling Health Check'''
 
'''Enabling Health Check'''
   −
'''1.''' '''Select the Distributed Switch''', and click the '''Manage''' Tab
+
'''1.''' '''Select the Distributed Switch''', and click the '''Configure''' Tab
   −
'''2.''' In the '''Settings''' column, select '''Health check'''
+
'''2.''' Select '''Health check'''
    
'''3.''' The '''Edit''' button to enable the feature.  
 
'''3.''' The '''Edit''' button to enable the feature.  
 
Its possible to see virtual distributed switch as if it is a physical switch. Physical switches come with a limited and predefined number of ports to which ethernet ready devices can be attached. Typically physical switches come with 8/16/24/48 ports on them. One a device is using a port it cannot be used by another device until the original device is unplugged. With a virtual switch the number of ports is configurable, and a combination of two settings Port Binding and Port Allocation control how they are consumed. A Distributed Switch does have a finite number of support ports which is outlined in the maximum configuration guide.
 
Its possible to see virtual distributed switch as if it is a physical switch. Physical switches come with a limited and predefined number of ports to which ethernet ready devices can be attached. Typically physical switches come with 8/16/24/48 ports on them. One a device is using a port it cannot be used by another device until the original device is unplugged. With a virtual switch the number of ports is configurable, and a combination of two settings Port Binding and Port Allocation control how they are consumed. A Distributed Switch does have a finite number of support ports which is outlined in the maximum configuration guide.
   Exception encountered, of type "Error"
[e79dd5f6] /vmwiki/index.php?title=Configuring_Distributed_Switches_in_vCenter_6&diff=prev&oldid=3736 Error from line 434 of /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DairikiDiff.php: Call to undefined function each()
Backtrace:
#0 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DairikiDiff.php(544): DiffEngine->diag(integer, integer, integer, integer, integer)
#1 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DairikiDiff.php(344): DiffEngine->compareSeq(integer, integer, integer, integer)
#2 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DairikiDiff.php(227): DiffEngine->diffLocal(array, array)
#3 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DairikiDiff.php(721): DiffEngine->diff(array, array)
#4 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DairikiDiff.php(859): Diff->__construct(array, array)
#5 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DairikiDiff.php(980): MappedDiff->__construct(array, array, array, array)
#6 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/TableDiffFormatter.php(194): WordLevelDiff->__construct(array, array)
#7 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DiffFormatter.php(140): TableDiffFormatter->changed(array, array)
#8 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DiffFormatter.php(82): DiffFormatter->block(integer, integer, integer, integer, array)
#9 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DifferenceEngine.php(910): DiffFormatter->format(Diff)
#10 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DifferenceEngine.php(828): DifferenceEngine->textDiff(string, string)
#11 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/poolcounter/PoolCounterWorkViaCallback.php(69): DifferenceEngine->{closure}()
#12 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/poolcounter/PoolCounterWork.php(123): PoolCounterWorkViaCallback->doWork()
#13 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DifferenceEngine.php(841): PoolCounterWork->execute()
#14 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DifferenceEngine.php(797): DifferenceEngine->generateTextDiffBody(string, string)
#15 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DifferenceEngine.php(728): DifferenceEngine->generateContentDiffBody(WikitextContent, WikitextContent)
#16 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DifferenceEngine.php(662): DifferenceEngine->getDiffBody()
#17 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DifferenceEngine.php(632): DifferenceEngine->getDiff(string, string, string)
#18 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/diff/DifferenceEngine.php(453): DifferenceEngine->showDiff(string, string, string)
#19 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/page/Article.php(797): DifferenceEngine->showDiffPage(boolean)
#20 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/page/Article.php(508): Article->showDiffPage()
#21 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/actions/ViewAction.php(44): Article->view()
#22 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/MediaWiki.php(490): ViewAction->show()
#23 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/MediaWiki.php(287): MediaWiki->performAction(Article, Title)
#24 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/MediaWiki.php(714): MediaWiki->performRequest()
#25 /home/wp_zdjm9n/michellelaverick.com/vmwiki/includes/MediaWiki.php(508): MediaWiki->main()
#26 /home/wp_zdjm9n/michellelaverick.com/vmwiki/index.php(41): MediaWiki->run()
#27 {main}