Merge pull request #5317 from bfallonf/vmware_1490806

Bug 1490806 Changed vmware vsphere info to be more accurate

admin_guide/managing_networking.adoc

@@ -355,11 +355,13 @@ Hat Enterprise Virtualization], you should set
 
 VMware vSphere::
 
-If you are using VMware vSphere, follow VMware's
-link:http://pubs.vmware.com/vsphere-4-esxi-installable-vcenter/index.jsp?topic=/com.vmware.vsphere.esxi_server_config.doc_40_u1/esx_server_config/securing_an_esx_configuration/c_securing_virtual_switch_ports.html[Securing
-Virtual Switch Ports] and
-link:http://pubs.vmware.com/vsphere-4-esxi-installable-vcenter/index.jsp?topic=/com.vmware.vsphere.esxi_server_config.doc_40_u1/esx_server_config/securing_an_esx_configuration/c_forged_transmissions.html[Forged
-Transmissions] guidance.
+If you are using VMware vSphere, see the link:https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.security.doc/GUID-3507432E-AFEA-4B6B-B404-17A020575358.html[VMWare documentation for securing vSphere standard switches]. View and change VMWare vSphere default settings by selecting the host's virtual switch from the vSphere Web Client.
+
+Specifically, ensure that the following are enabled:
+
+* https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.security.doc/GUID-942BD3AA-731B-4A05-8196-66F2B4BF1ACB.html[MAC Address Changes]
+* https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.security.doc/GUID-7DC6486F-5400-44DF-8A62-6273798A2F80.html[Forged Transits]
+* https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.security.doc/GUID-92F3AB1F-B4C5-4F25-A010-8820D7250350.html[Promiscuous Mode Operation]
 
 [[admin-guide-egress-router-modes]]
 *Egress Router Modes*
@@ -942,7 +944,7 @@ In a cluster
 xref:../install_config/configuring_sdn.adoc#install-config-configuring-sdn[configured
 to use the *ovs-networkpolicy* plug-in], network isolation is controlled
 entirely by
-link:https://github.com/kubernetes/community/blob/master/contributors/design-proposals/network-policy.md[`NetworkPolicy`
+link:https://github.com/kubernetes/community/blob/master/contributors/design-proposals/network/network-policy.md[`NetworkPolicy`
 objects]. In particular, by default, all projects are able to access pods in all
 other projects. To isolate a project, opt in to isolation by configuring the
 Namespace object, then create a `NetworkPolicy` object to indicate the allowed