Objective 4.4 – Expand Transport Zone to Include New Cluster(s)

Knowledge

  • Explain the function of a Transport Zone
    4.4.Transport Zone

    • A transport Zone defines a collection of ESXi hosts that can communicate with each other across a physical network.
    • It extends across one or more ESXi clusters, and in a loose sense defintes the span of logical switches.
  • Add a Transport Zone
    • Log in to the vSphere Web Client.
    • Navigate to “Networking & Security” and “Installation”.
    • Click “Logical Network Preparation” and then click “Transport Zones”.
    • Click the “New Transport Zone” icon.
    • In the New Transport Zone dialog box, type a name and description for the transport zone.
    • Depending on whether you have a controller node in your environment, or you want to use multicast addresses, select the control plane mode.
      • Multicast: Multicast IP addresses on physical network are used for the control plane. This mode is recommended only when you are upgrading from older VXLAN deployments. Requires PIM/IGMP on physical network.
      • Unicast : The control plane is handled by an NSX controller. All unicast traffic leverages headend replication. No multicast IP addresses or special network configuration is required.
      • Hybrid : The optimized unicast mode. Offloads local traffic replication to physical network (L2 multicast). This requires IGMP snooping on the first-hop switch, but does not require PIM. First-hop switch handles traffic replication for the subnet.
    • Select the clusters to be added to the transport zone.
    • Click OK.
  • Expand/Contract a Transport Zone
    • Expand:
      • Log in to the vSphere Web Client.
      • Navigate to “Networking & Security” and “Installation”.
      • Click “Logical Network Preparation” and then click “Transport Zones”.
      • Click a transport zone.
      • In Transport Zones Details, click the Add Cluster icon.
      • Select the clusters you want to add to the transport zone.
      • Click OK.
    • Contract
      • Log in to the vSphere Web Client.
      • Navigate to “Networking & Security” and “Installation”.
      • Click “Logical Network Preparation” and then click “Transport Zones”.
      • Double-click a transport zone.
      • In Transport Zones Details, click the Remove Clusters icon.
      • Select the clusters you want to remove.
      • Click OK.
  • Edit a Transport Zone
    • Log in to the vSphere Web Client.
    • Navigate to “Networking & Security” and “Installation”.
    • Click “Logical Network Preparation” and then click “Transport Zones”.
    • Double-click a transport zone.
      The Summary tab displays the name and description of the transport zone as well as the number of logical switches associated with it. Transport Zone Details displays the clusters in the transport zone.
    • Click the Edit Settings icon in the Transport Zone Details section to edit the name or description of the transport zone.
    • Click OK.
  • Change the Control Plane mode for a Transport Zone
    • Log in to the vSphere Web Client.
    • Navigate to “Networking & Security” and “Installation”.
    • Click “Logical Network Preparation” and then click “Transport Zones”.
    • Double-click a transport zone.
      The Summary tab displays the name and description of the transport zone as well as the number of logical switches associated with it. Transport Zone Details displays the clusters in the transport zone.
    • Click the Edit Settings icon in the Transport Zone Details section to edit the control plane mode of the transport zone.
    • Select Migrate existing Logical Switches to the new control plane mode to change the control plane more for existing logical switches linked to this transport zone. If you do not select this check box, only the logical switches linked to this transport zone after the edit is done will have the new control plane mode.
    • Click OK.

Tools

  • NSX Installation and Upgrade Guide
  • NSX Administration Guide
  • vSphere Web Client

Objective 4.3 – Upgrade Existing vCNS/NSX Implementation

Knowledge

  • Verify upgrade prerequisites have been met
    • Vcenter 5.5 required
    • Can only upgrade from vShield 5.5 to NSX Manager, not 6.0
  • Upgrade vCNS 5.5 to NSX 6.x
    • Download the upgrade bundle
    • From within vShield Manager, Settings & Reports, Browse and upload the file
    • Click Install and the appliance will reboot
    • Login to NSX manager to confirm the upgrade
  • Upgrade vCNS Virtual Wires to NSX Logical Switches
    • From vSphere Web Client, open Network & Security
    • Navigate to Host preparation area
    • Click “Update” – status will change from Legacy to Enabled
    • VIBS are pushed to nodes (using DRS and Maintenance Mode)
    • Install NSX Controllers and create Logical Network
  • Upgrade to NSX Components
    • Upgrade to NSX Firewall
    • Prerequisites
      • vShield Manager has been upgraded to NSX Manager.
      • Virtual wires have been upgraded to NSX Logical Switches. For non-VXLAN users, network virtualization components have been installed.
    • Procedure
      • After you update all the clusters in your infrastructure while upgrading to NSX logical switches (or installing network virtualization components), a pop up message indicates that Firewall is ready to be upgraded.
        4.3.Firewall
      • Click Upgrade.
      • After the upgrade is complete, the Firewall column displays Enabled.
      • Inspect each upgraded section and rule to ensure it works as intended.
    • What to do next
      • Once you upgrade firewall to NSX, you should move the grouping objects used by firewall rules to global scope. To do this, use NSX APIs to create new grouping objects with the same members and then update the relevant firewall rules with the new IDs.
  • Upgrade to NSX Edge
    • From vSphere Web Client, open Network & Security
    • Navigate to NSX Edge
    • Select Upgrade from Actions
    • Check version number and deploy status
  • Upgrade vShield Endpoint from 5.5 to 6.x
    • Log in to the vSphere Web Client.
    • Click Networking & Security and then click Installation.
    • Click the Service Deployments tab.
    • vShield Endpoint 5.5 deployments are displayed and the Installation Status column says Upgrade Available.
    • In the Installation Status column for vShield Endpoint, click the arrow next to Upgrade Available.
    • Select the Data store and Network and click OK.
  • Upgrade to NSX Data Security
    • NSX Data Security does not support a direct upgrade. You must uninstall the current Data Security software before upgrading to NSX Manager. After NSX Manager is upgraded, you can install NSX Data Security version 6.0. If you upgraded to NSX Manager without uninstalling Data Security, you must do so using a REST call.
    • Pre-NSX Data Security policies and violation reports are carried over to the vSphere Web Client, but you can run a Data Security scan only after installing NSX Data Security version 6.0.
  • Upgrade NSX Manager from 6.0 to 6.x
    • Download upgrade bundle from VMware
    • Open NSX Manager web front end, and navigate to Manage area
    • Click Upgrade
    • Wait for upgrade to finish, login and confirm version number
  • Update vSphere Clusters after NSX upgrade
    • From vSphere Web Client, open Network & Security
    • Navigate to Host preparation, and click Update (remember to post host into Maint Mode)

Tools

  • NSX Installation and Upgrade Guide
  • vSphere Web Client

Objective 4.2 – Deploy VMware NSX Components

Knowledge

  • Install NSX Manager
    • Deploy OVF Template
    • Select source (URL or Browse to local file)
    • Review details (shows product, version, size, description etc)
    • Accept EULA
    • Specify a name (NSX Manager) and location (folder or datacentre)
    • Select the storage (datastore)
    • Setup networks (which port group the VM will be on)
    • Customize template (enter passwords, network properties)
    • Ready to complete (review config and click Finish)
  • Register NSX Manager with vCenter Server
    • Connect to NSX Manager Web Frontend
    • Manage vCenter Registration
    • Click on Edit
    • Enter DNS name, username, password
    • Yes to proceed with this registration
    • Yes to proceed with the SSL certificate
    • Shows status “Connected”
  • Install NSX License
    • Open the Web Client
    • Navigate to Administration > Licensing
    • Click “+” under License Keys
    • Paste in the NSX license key and click Finish
  • Prepare ESXi hosts
    • Log in to Web Client
    • Navigate to Networking & Security
    • Installation/Host Preparation
    • Select the Cluster and click “Install”
    • This installs VIBs to hosts
  • Deploy NSX Controllers
    • Must be odd number of Controllers – recommended 3
    • Use anti-affinity rules to keep separate (create manually)
    • Web Client, Networking & Security
    • Installation
    • Click “+” by NSX Controller nodes
    • Enter Datacenter, Cluster/RP, Datastore, Host, Connected To, IP Pool, Password
    • VM is then deployed and built
  • Assign Segment ID pool and Multicast addresses
    • Log in to Web Client
    • Navigate to Networking & Security
    • Installation/Logical Network Preparation
    • Click “Segment ID”
    • Click “Edit”
    • Enter the Segment ID pool range
    • If Multicast addressing is to be used, click the “Enable multicast addressing” checkbox, and enter the multicast addresses range.
    • Click OK.
  • Configure VXLAN Transport
    • VXLAN Replication Modes:
      • Unicast – Ease of entry. More work for hypervisor, but requires fewer network changes.
      • Hybrid – Requires IGMP Snooping on the switch. Uses multicast locally, but unicast across WAN.
      • Multicast – Offload more work to network infrastructur
    • Log in to Web Client
    • Navigate to Networking & Security
    • Installation/Host Preparation
    • Select the Cluster and click on “Configure” under the VXLAN column
    • Select the Switch, VLAN, MTU, choice of DHCP/IP Pool, Teaming policy, VTEP ID
      • If using IP Pool, all hosts need to be on shared L2, or manually reconfigured afterwards.
    • Click on “Transport Zones”
    • Click on “+” to start the New Transport Zone dialog
    • Enter Name, Description, Control Plane Mode (Multicast/Unicast/Hybrid), and choose the Clusters to Add.
  •  Install NSX Edge
    • A VM that provides services such as VPN, Stretch L2, Dynamic Routing etc
    • Log in to Web Client
    • Navigate to Networking & Security
    • Click on NSX Edges
    • Click on “+”
    • Select Edge Services Gateway
    • Select checkbox option to choose High Availability if required
    • Enter the Name, Hostname, Description, TenantEnter CLI credentials (enable SSH if required)
    • Configure the Datacenter, Appliance size
    • Configure interfaces (need Internal and Uplink)
    • Choose correct MTU (1500 for internal)
  • Install vShield Endpoint
    • On NSX 6.1 vShield Endpoint has been replaced with the Data Security and Guest Introspection appliances
    • Log in to Web Client
    • Navigate to Networking & Security
    • Click on Installation and Service Deployments
    • Click “+” and the “Deploy Network & Security Services” dialog starts
    • Select “VMware Endpoint”, Next
    • Select the Cluster to deploy the Endpoints to, Next
    • Select the Datastore on which to place the Endpoint, Next
    • Select the Management Network for the Endpoint, Next
    • The Endpoints are now deployed from OVFs
    • Monitor the Installation status and it will go from In Progress to Succeeded.
  • Install Data Security
    • Log in to Web Client
    • Navigate to Networking & Security
    • Click on Data Security
    • Click on Edit for “Regulations and standards to detect”
    • Click on “All”
    • Select the regulations to monitor for, Next
    • Enter Data Patterns, if prompted to enter them for the chosen regulations
    • Click Finish
    • Click on Edit for “Files to scan”
    • Make changes to the Size/Modified Date/File Extension Type if necessary
    • Click Save
    • Click Publish Changes
    • Click Start
  • Create an IP pool
    • Log in to Web Client
    • Navigate to Networking & Security
    • Click on NSX Managers
    • Click on the IP address of the NSX Manager
    • Navigate to “Manage” and “Grouping Objects”
    • Select IP Pools, and click on “+” to add a new IP pool
    • Enter the Name of the pool, Gateway, Prefix length, Primary DNS, Secondary DNS, DNS Suffix and Static IP Pool details.
    • Click OK.

Tools

  • NSX Installation and Upgrade Guide
  • NSX Manager
  • vSphere Web Client

Objective 4.1 – Configure Environment for Network Virtualization

Knowledge

  • Configure the physical infrastructure (MTU, Dynamic Routing for edge, etc.)
    • MTU needs to be 1600 for transport zone
      Can use 1550 if you aren’t going to have VLAN tagging in the VM Guest OS
      Has been suggested that 1600 is the minimum recommended in 6.0, and 1550 is the minimum recommended in 6.1
    • Configure OSPF adjacency for routing on Edge (or BGP, ISIS equivalent)
  • Prepare a new vSphere infrastructure
    • Configure Quality of Service (QoS)
      • L2/L3 fabric must be configured to trust the hypervisor for QoS marking – hypervisor is the trusted boundary.
    • Configure Link Aggregation Control Protocol (LACP)
      • Can use LACP or Etherchannel for the Transport network, but only a single VTEP is supported with bonded channels.
  • Configure an existing vSphere infrastructure
    • Ensure DNS entries are configured correctly for all components
    • Requires vSphere 5.5 and vCenter 5.5
    • Upgrade VMware Tools – minimum 8.6, vHW 7+
    • Must use Enterprise+ license
  • Explain how IP address assignments work in VMware NSX
    • Can use IP Pools or DHCP to assign addresses for NSX components. DHCP allows configuration of VTEP on different VLANs, whereas IP Pools require the same VLAN or manual configuration to change after install.
  • Identify minimum permissions required to deploy NSX in a vSphere environment
    • Administrative access to vCenter – required to synchronise the NSX Manager with vCenter

Tools

  • vSphere Networking Guide
  • NSX Administration Guide
  • vSphere Web Client

Objective 3.3 – Configure and Manage vSS and vDS Policies

Knowledge

  • Identify common vSS and vDS policies
    • Common Security Policies
      • Promiscuous Mode (default is reject) – When enabled, allows a VM to see all traffic passing through the vSwitch
      • MAC address changes (default is accept) – Determine whether a VM is permitted to receive traffic on a changed MAC address. May be required for NLB or Windows Clustering.
      • Forged Transmits (default is accept) – Determine whether a VM is permitted to transmit traffic on a changed MAC address.
  • Configure dvPortgroup blocking policies
    • Block single port with Web Client
      • Go to vCenter Home and Networking
      • Expand the Datacenter object
      • Click on the vDS object
      • Manage > Ports
      • Find the port ID in the list
      • Select the port ID click the pencil icon to edit
      • Go to the Miscellaneous section and select “Block port”, and change the Override to “yes”
      • Click OK to apply the setting
    • Block all ports on a Distributed Port Group with Web Client
      • Go to vCenter Home and Networking
      • Expand the Datacenter object
      • Right click on the vDS object and select “Edit settings”
      • Go to the Miscellaneous section and change “Block all ports” to “yes”
      • Click OK to apply the setting
  • Configure load balancing and failover policies
    • vSS – Default policies are set on the vswitch, these can be overridden on the port group.
    • vDS – Policies are set on each Distributed Port Group
    • Load Balancing
      • Route basd on IP hash – requires Etherchannel (or LACP on vDS) on the physical switch
      • Route based on source MAC hash – similar to above, but doesn’t need channel bonding
      • Router basd on originating virtual port – traffic exits through the same port it came in on
      • Use explicit failover order – no load balancing, just failover
      • Route based on physical NIC load (vDS only) – distributes the load based on traffic volume
    • Network Failover Detection
      • Link Status Only – This uses the link state of the physical NIC. If the switch fails or the cable gets unplugged, the failure will be detected and failover will be initiated. This cannot detect if the switch becomes isolated, or misconfigured.
      • Beacon Probing – This sends and listens for beacon probes on all NICs that are part of the team. This is used to determine whether a NIC has connectivity, and can detect more failures than LSO. Do not use in conjunction with IP hash Load Balancing
      • Notify Switches – If set to “yes” then physical switches will be notified to update MAC/ARP tables in the event of a failover. Do not use when using Microsoft NLB in unicast mode.
      • Failback Policy – If set to “yes” then return to the original configuration after a NIC failure has been resolved, if set to “no” continue in failover mode.
  • Configure VLAN settings
    •  vSS
      • Configured on the port group, under Edit Settings and Properties, configure the chosen VLAN ID or set to 0 to use the base VLAN on the physical switch port.
    • vDS
      • Configured on the distributed port group, under Manage, Settings, Edit, VLAN
        • None – no VLAN tagging
        • VLAN – Enter the VLAN ID to be used
        • VLAN Trunking – Enter the range of VLANs to be trunked
        • Private VLAN – Enter the private VLAN to be used (must be configured on the vDS first)
  • Configure traffic shaping policies
    • vSS
      • Configured on the vSwitch or port group, under Edit Settings and Properties
      • Applies only to egress traffic
    • vDS
      • Configured on the distributed port group, under Manage, Settings, Edit, Traffic Shaping
      • Applies to ingress and/or egress traffic
    • Policies:
      • Average Bandwidth – determines the Kbits/sec allowed to traverse each port, averaged over time.
      • Peak Bandwidth – the maximum rate the bandwidth can burst to
      • Burst Size – the amount of data allowed to burst up to the Peak Bandwidth rate
      • Network IO Control – under “Resource Allocation” tab, only applies to egress traffic. Create a new policy group and apply to a port group
  • Enable TCP Segmentation Offload (TOE) support for a virtual machine
    • TOE is enabled when using the VMXNet3 network adapter
  • Enable Jumbo Frame support on appropriate components
    • Enable on the vSwitch (vSS or vDS), enable on vmknics, enable on VMs by installing the VMXNet3 adapter and enabling within the Guest OS.
    • Normally only enable for iSCSI and/or vMotion
  • Determine appropriate VLAN configuration for a vSphere implementation
    • There is no single appropriate configuration to put here. Understand the following:
      • External Switch Tagging – all tagging occurs at the physical switch
      • Virtual Switch Tagging – all tagging occurs at the virtual switch. The physical switch ports must be configured as trunk ports. Port groups must have the VLAN ID specified.
      • Virtual Machine Tagging – tagging is done by the VM. The Guest OS must be able to handle 802.1Q traffic. The physical switch ports must be configured as trunk ports.
      • Private VLANs – Understand PVLANs and where/why to use them.

Tools

  • vSphere Installation and Setup Guide
  • vSphere Networking Guide
  • vSphere Web Client
  • vSphere Client

Objective 3.2 – Configure and Manage vSphere Distributed Switches (vDS)

Knowledge

  • Identify vDS capabilities
    All vSS capabilities plus:

    • Maintains a single configuration across all hosts
    • Ensures VMs see consistent network provision regardless of the host they are on
    • Allows the use of NetFlow, Port Mirroring and Private VLANs
    • Performs traffic shaping ingress as well as egress
    • Allows use of LACP for teaming
    • Allows use of Load Based Teaming
    • … see comparison table in 3.1 for more
  • Create/Delete a vDS
    Use C# client, Web client, PowerCLI

    • Create with Web Client:
      • Go to vCenter Home and Networking
      • Right click on the Datacenter object and select “New Distributed Switch”
      • Name the vDS and click Next
      • Select the version (4.0-5.5), Next
      • Choose the number of Uplinks, whether NIOC is enabled and whether a default port group is created, according to what you wish to create.
      • Click Next, and Finish
  • Add/Remove ESXi hosts from a vDS
    Easiest through GUI, same for following items

    • Go to vCenter Home and Networking
    • Expand the Datacenter object
    • Right click on the vDS object and select “Add and Manage Hosts”
    • Leave the radio button on “Add hosts”, Next
    • Click “New hosts…” and select the hosts to add, OK, and Next
    • You can now select to manage the host nics, the vmknics, migrate VM networking and change advanced settings. Leave the defaults and click Next
    • For each host nic you want to use, click on it, then click on “Assign Uplink” to assign it to a vDS uplink, Next
    • Choose to create new vmknics or assign existing ones to port groups on the new vDS, Next
    • Check the impact on existing network services on the next screen, Next
    • Click Finish to apply the change
    • Add hosts with Web Client:
  • Edit general vSphere vDS settings
    Advanced settings includes MTU

    • Edit settings with Web Client:
      • Go to vCenter Home and Networking
      • Expand the Datacenter object
      • Right click on the vDS object and select “Edit Settings”
      • Amend Uplinks/Network IO control in the General tab, or MTU, Discovery protocol and admin contact in the Advanced tab
      • Click OK to apply the changes
  • Add/Configure/Remove dvPortgroups
    • New Distributed Port Group with Web Client:
      • Go to vCenter Home and Networking
      • Expand the Datacenter object
      • Right click on the vDS object and select “New Distributed Port Group”
      • Name the port group and click Next
      • Enter the configuration details for this port group (binding type, no of ports, VLAN etc) and if necessary select the “Advanced” checkbox to customize the default policies)
      • Click Next, and FInish
  • Configure dvPort settings
    • Configure dvPort settings with Web Client
      • Go to vCenter Home and Networking
      • Expand the Datacenter object
      • Select vDS object and click on the Ports tab
      • Select the Port in the list and click the pencil icon to edit.
      • Edit the settings in the dialog box, and click OK to save
  • Add/Remove uplink adapters to dvUplinkgroups
    • Add uplink adapters with Web Client
      • Go to vCenter Home and Networking
      • Expand the Datacenter object
      • Right click on the vDS object and select “Add and Manage Hosts”
      • Select “Manage host networking”, Next
      • Click “Attached Hosts”
      • Select the hosts to manage, OK, Next
      • Select only “Manage physical adapters”, Next
      • Click on the vmnic to assign, and then select “Assign uplink”
      • Choose the Uplink, OK, Next
      • Check the impact on existing network services on the next screen, Next
      • Click Finish to apply the change
  • Create/Configure/Remove virtual adapters
    • Create virtual adapters with Web Client
      • Go to vCenter Home and Networking
      • Expand the Datacenter object
      • Right click on the vDS object and select “Add and Manage Hosts”
      • Select “Manage host networking”, Next
      • Click “Attached Hosts”
      • Select the hosts to manage, OK, Next
      • Select only “Manage VMkernel adapters”, Next
      • Click “New adapter”
      • Choose the port group, Next
      • Choose the port properties and services, Next
      • Set the IP address (or leave as DHCP), Next
      • Click Finish
  • Migrate virtual adapters to/from a vSS
    • Migrate virtual adapters with Web Client
      • Go to vCenter Home and Networking
      • Expand the Datacenter object
      • Right click on the vDS object and select “Add and Manage Hosts”
      • Select “Manage host networking”, Next
      • Click “Attached Hosts”
      • Select the hosts to manage, OK, Next
      • Select only “Manage VMkernel adapters”, Next
      • Select the vmknic to migrate
      • Click “Assign port group” and choose the new Distributed Port Group to assign to
      • Click Ok, and Next
      • Check the impact on existing network services on the next screen, Next
      • Click Finish to apply the changes
  • Migrate virtual machines to/from a vDS
    • Migrate virtual machines with Web Client
      • Go to vCenter Home and Networking
      • Right click on the Datacenter object and select “Migrate VM to Another Network”
      • Choose the source network in the “Specific network” box
      • Choose the destination network, Next
      • Choose the VMs to migrate, Next
      • Click Finish
  • Monitor dvPort state
    • Monitor dvPort state with Web Client
      • Go to vCenter Home and Networking
      • Expand the Datacenter object
      • Click on the vDS object
      • Manage > Ports
      • Find the port ID in the list
      • Select the port ID and the status will show below
  • Determine use cases for a vDS
    • Must have Enterprise Plus licensing
    • Simpler to manage large numbers of hosts with a vDS rather than making sure their vSS and Port Groups are in sync.
    • If you need to use NetFlow, Port Mirroring or Private VLANs
    • If you want to use “Load Based Teaming”
    • If you want to use Network IO Control or Network Resource Pools

Tools

  • vSphere Installation and Setup Guide
  • vSphere Networking Guide
  • vSphere Web Client
  • vSphere Client

Objective 3.1 – Configure and Manage vSphere Standard Switches (vSS)

Knowledge

  • Identify vSS capabilities
    • Routes traffic internally between virtual machines and links to external networks
    • Allows for multiple port groups configured with different policies
      • Allows for VLANs
      • Create network labels for virtual machine virtual adapters to attach to (is unique within the current datacentre)
    • Balance communication across multiple network adapters for load and/or resilience
    • Configurable to handle physical NIC failure by failing over to another physical NIC
    • Maximum of 256 port groups
    • Supports EtherChannel but not LACP
    • Source Port and Source MAC Load Balancing but not LB
  • vSS-dSS comparison
    3.1.comparison
  • Configuration Maximums
    3.1.maximums
  • Add/Configure/Remove vmnics on a vSS
    Use C# client, Web client, esxcli, PowerCLIAdd via Web Client:

    • Hosts and Cluster view
    • Select host
    • Manage > Networking > Virtual Switches
    • Click on “Manage the physical network adapters connected to the selected switch” 3.1.physical
    • Click the [+] and select the vmnic to add
  • Configure vmkernel ports for network services
    Easiest to select in GUI (Web client or C#)
    Tickboxes to enable services (vMotion/FT/Management/vSAN)
    3.1.services
  • Add/Edit/Remove port groups on a vSS
    Use C# client, Web client, esxcli, PowerCLIAdd via Web Client:

    • Hosts and Cluster view
    • Select host
    • Manage > Networking > Virtual Switches
    • Click on “Add host networking”3.1.portgroups
    • Select “Virtual Machine Port Group for a Standard Switch”, Next
    • Select “Select an existing standard switch”, Next
    • Input the Network Label (name of the Port Group) and VLAN ID
    • Next, and Finish
  • Determine use cases for a vSphere Standard Switch
    • No Ent+ license
    • Management cluster

Tools

  • vSphere Installation and Setup Guide
  • vSphere Networking Guide
  • vSphere Web Client
  • vSphere Client