Course Content
VMware vSphere: Install, Configure, Manage Content
0/1
Introduction to vSphere and the Software Defined Data Center
As a vSphere administrator, you must be familiar with the components on which vSphere is based. You must also understand the following concepts: Virtualization, the role of the ESXi hypervisor in virtualization and virtual machines Fundamental vSphere components and the use of vSphere in the software-defined data center Use of vSphere clients to administer and manage vSphere environments
0/4
Virtual Machines
You can create a virtual machine in several ways. Choosing the correct method can save you time and make the deployment process manageable and scalable.
0/3
vCenter Server
vCenter Server helps you centrally manage multiple ESXi hosts and their virtual machines. If you do not properly deploy, configure, and manage vCenter Server Appliance, your environment might experience reduced administrative efficiency or ESXi host and virtual machine downtime.
0/8
Configuring and Managing Virtual Networks
When you configure ESXi networking properly, virtual machines can communicate with other virtual, and physical, machines. In this way, remote host management and IP-based storage operate effectively.
0/2
Configuring and Managing Virtual Storage
Understanding the available storage options helps you set up your storage according to your cost, performance, and manageability requirements. You can use shared storage for disaster recovery, high availability, and moving virtual machines between hosts.
0/6
Virtual Machine Management
Virtual machines are the foundation of your virtual infrastructure. Managing VMs effectively requires skills in creating templates and clones, modifying VMs, migrating VMs, taking snapshots, and protecting the VMs through replication and backups.
0/8
Resource Management and Monitoring
Although the VMkernel works proactively to avoid resource contention, maximizing performance requires both analysis and ongoing monitoring. Developing skills in resource management, you can dynamically reallocate resources so that you can use available capacity more efficiently.
0/5
vSphere Clusters
Most organizations rely on computer-based services like email, databases, and web-based applications. The failure of any of these services can mean lost productivity and revenue. By understanding and using vSphere HA, you can configure highly available, computer-based services, which are important for an organization to remain competitive in contemporary business environments. And by developing skills in using vSphere DRS, you can improve service levels by guaranteeing appropriate resources to virtual machines.
0/6
vSphere Lifecycle Management
Managing the life cycle of vSphere involves keeping vCenter Server and ESXi hosts up to date and integrated with other VMware and third-party solutions. To achieve these goals, you must understand how to use the new features provided by vSphere Lifecycle Manager, namely, clusterlevel management of ESXi hosts and the vCenter Server Update Planner.
0/5
VMware vSphere: Install, Configure, Manage
About Lesson

Configuring Standard Switch Policies

Learner Objectives

After completing this lesson, you should be able to meet the following objectives:

  • Explain how to set the security policies for a standard switch port group
  • Explain how to set the traffic shaping policies for a standard switch port group
  • Explain how to set the NIC teaming and failover policies for a standard switch port group

Network Switch and Port Policies

Policies that are set at the standard switch level apply to all port groups on the standard switch by default.

Available network policies:

  • Security
  • Traffic shaping
  • NIC teaming and failover

Policy levels:

  • Standard switch level: Default policies for all the ports on the standard switch.
  • Port group level: Effective policies defined at this level override the default policies that are set at the standard switch level.

Configuring Security Policies

As an administrator, you can define security policies at both the standard switch level and the port group level:

  • Promiscuous mode: You can allow a virtual switch or port group to forward all traffic regardless of the destination.
  • MAC address changes: You can accept or reject inbound traffic when the MAC address is altered by the guest.
  • Forged transmits: You can accept or reject outbound traffic when the MAC address is altered by the guest.

Traffic-Shaping Policies

  • Network traffic shaping is a mechanism for limiting a virtual machine’s consumption of available network bandwidth.
  • Average rate, peak rate, and burst size are configurable.

Configuring Traffic Shaping

A traffic-shaping policy is defined by average bandwidth, peak bandwidth, and burst size. You can establish a traffic-shaping policy for each port group and each distributed port or distributed port group:

  • Traffic shaping is disabled by default.
  • Parameters apply to each virtual NIC in the standard switch.
  • On a standard switch, traffic shaping controls only outbound traffic, that is, traffic traveling from the VMs to the virtual switch and out onto the physical network.

NIC Teaming and Failover Policies

With NIC teaming, you can increase the network capacity of a virtual switch by including two or more physical NICs in a team.

Load-Balancing Method: Originating Virtual Port ID

With the load-balancing method that is based on the originating virtual port ID, a virtual machine’s outbound traffic is mapped to a specific physical NIC.

Load-Balancing Method: Source MAC Hash

For the load-balancing method based on source MAC hash, each virtual machine’s outbound traffic is mapped to a specific physical NIC that is based on the virtual NIC’s MAC address.

Load-Balancing Method: Source and Destination IP Hash

With the IP-based load-balancing method, a NIC for each outbound packet is selected based on its source and destination IP addresses.

Detecting and Handling Network Failure

The VMkernel can use link status or beaconing, or both, to detect a network failure.

Network failure is detected by the VMkernel, which monitors the link state and performs beacon probing.

The VMkernel notifies physical switches of changes in the physical location of a MAC address.

Failover is implemented by the VMkernel based on configurable parameters:

  • Failback: How the physical adapter is returned to active duty after recovering from failure.
  • Load-balancing option: Use explicit failover order. Always use the vmnic uplink at the top of the active adapter list.

Physical Network Considerations

Your virtual networking environment relies on the physical network infrastructure. As a vSphere administrator, you should discuss your vSphere networking needs with your network administration team. The following issues are topics for discussion:

  • Number of physical switches
  • Network bandwidth required
  • Physical switch configuration support for 802.3ad, for NIC teaming
  • Physical switch configuration support for 802.1Q, for VLAN tagging
  • Physical switch configuration support for Link Aggregation Control Protocol (LACP)
  • Network port security
  • Link Layer Discovery Protocol (LLDP) and Cisco Discovery Protocol (CDP) and their operation modes, such as listen, broadcast, listen and broadcast, and disabled

Review of Learner Objectives

After completing this Configuring Standard Switch Policies lesson, you should be able to meet the following objectives:

  • Explain how to set the security policies for a standard switch port group
  • Explain how to set the traffic shaping policies for a standard switch port group
  • Explain how to set the NIC teaming and failover policies for a standard switch port group

Key Points

  • Virtual switches can have the following connection types: VM port group, VMkernel port, and physical uplinks.
  • A standard switch is a virtual switch configuration for a single host.
  • Network policies set at the standard switch level can be overridden at the port group level.
  • A distributed switch provides centralized management and monitoring for the networking configuration of all ESXi hosts that are associated with the switch.
Join the conversation