650 likes | 817 Views
CIT 198 Week#6 Module 5 from the e-book. Configure Shared Storage for vSphere – Sybex Chapter#5. Instructor - Allan Ackerman VCA-DCV & VCP5-DCV. Click the graphic for assessment. This week our objectives will be. Finish off lab 11 by installing our XPpro.ova
E N D
CIT 198 Week#6Module 5 from the e-book.Configure Shared Storage for vSphere – Sybex Chapter#5 Instructor - Allan Ackerman VCA-DCV & VCP5-DCV Click the graphic for assessment
This week our objectives will be • Finish off lab 11 by installing our XPpro.ova • Complete labs 14 & 15 on the in-class virtual lab. • Complete labs 5 , 6, & 7 from the NDG/Cisco • Be able to describe vSS. • Understand connection types • Identify the components of a vSS • Configure Shared storage • Identify storage adapters • Configure a VMFS datastore (extend and expand) • Identify storage naming conventions Week#6 vSphere 5.1
Our in-class lab#14 • This is a simple lab doing miscellaneous tasks. • We will be joining our two esxi hosts, esxi1.vita.local and esxi2.vita.local to the vita.local domain. • We will verify that the process worked by going over to the domain controller and running ADUC and checking out the computer container. • We will learn how to change the number of ports on a vSS. • We will learn how to change the speed and duplex settings of a vmnic. • Finally we will learn how to use the vmxnet3 NICs that comes with VMware tools. We will use this NIC on our e732c vm. • All of these tasks are quite simple and your instructor’s signature on this lab is not required. Week#6 vSphere 5.1
Our in-class lab#15 • VMware gives the vSphere administrator two tools to increase the size of a datastore. • They sound similar, extend & expand, but the mechanics of each are quite different. • Expand allows us to increase the size of a datastore if there is some unallocated space available. • Extend allows us to add a new empty LUN to a datastore expanding its size. This is very similar to MicroSoft’s spanned volume type. Week#6 vSphere 5.1
Our NDG lab#5 • This lab will give us more practice creating a VMkernel port that will support iSCSI. • We will enable the iSCSI adapter in ESXi and start to setup our shared storage for the downstairs virtual lab. • Note – the NDG lab is not as sophisticated as our in-class lab. Only one vmknic, 172.16.1.100, to support our iSCSI SAN – no round robin multipathing. Week#6 vSphere 5.1
Our NDG lab#6 • In this lab we will setup our NFS datastore • Remember NFS is a protocol that sits on top of a native file system. So it could be NTFS on a Microsoft box or a Linux file system like ext3. • We will practice using the storage views tab in this lab and view both the NFS datastore and our iSCSI datastore. Week#6 vSphere 5.1
Our NDG lab#7 • This lab will be very similar to our own in-class lab#15. • We will setup DAS (direct attached storage) • We will expand a datastore • We will extend a datastore • We will remove an VMFS datastore • We will rename a VMFS datastore. Week#6 vSphere 5.1
Stuff I forgot to mention last week. Make sure you know for next week’s exam. Forgot to put these port numbers up on the board last week. Week#6 vSphere 5.1
Configuring and Managing Virtual Networks Module 5 Week#6 vSphere 5.1
You Are Here Configuring and Managing Virtual Networks Week#6 vSphere 5.1
Importance • VMware vSphere® ESXi™ networking features allow the following: • Virtual machines to communicate with other virtual and physical machines • Management of the ESXi host • The VMkernel to access IP-based storage and perform VMware vSphere® vMotion® migrations • Failure to properly configure ESXi networking can negatively affect virtual machine management and storage operations. Week#6 vSphere 5.1
Module Lessons • Lesson 1: Introduction to vNetwork Standard Switches • Lesson 2: Configuring Standard Virtual Switch Policies Week#6 vSphere 5.1
Lesson 1: Introduction to vNetwork Standard Switches Week#6 vSphere 5.1
Learner Objectives • After this lesson, you should be able to do the following: • Define a virtual network. • Describe a virtual switch. • Describe the virtual switch connection types. • Describe the components of a vNetwork standard switch. • Create a vNetwork standard switch. Week#6 vSphere 5.1
What Is a Virtual Network? What Is a Virtual Switch? • A virtual network provides networking for hosts and virtual machines. • A virtual switch: • Directs network traffic between virtual machines and links to external networks. • Combines the bandwidth of multiple network adapters and balances traffic among them. It can also handle physical network interface card (NIC) failover. • Models a physical Ethernet switch: • A virtual machine’s NIC can connect to a port. • Each uplink adapter uses one port. Virtual NIC Virtual NIC Virtual NIC Physical NIC vmnic0 vmnic1 Week#6 vSphere 5.1
Types of Virtual Switch Connections • A virtual switch allows the following connection types: • One or more virtual machine port groups • VMkernel port: • For IP storage, vMotion migration, VMware vSphere® Fault Tolerance • For the ESXi management network Production Test Dev DMZ vMotion Management Week#6 vSphere 5.1
Virtual Switch Connection Examples • More than one network can coexist on the same virtual switch, or networks can exist on separate virtual switches. Week#6 vSphere 5.1
Types of Virtual Switches • A virtual network supports two types of virtual switches: • vNetwork standard switches: • Virtual switch configuration for a single host • Discussed in this module • vNetwork distributed switches: • Virtual switches that provide a consistent network configuration for virtual machines as they migrate across multiple hosts Week#6 vSphere 5.1
Standard Virtual Switch Components vSS components Week#6 vSphere 5.1
Default Standard Virtual Switch Configuration Display standard virtual switches. Enable IPv6 on ESXi host. Remember the vSS can only handle the CDP Delete the virtual switch. Display virtual switch properties. Display Cisco Discovery Protocol information. Display port group properties. Week#6 vSphere 5.1
Standard Virtual Switch Ports You can change the number of ports on a standard virtual switch but you have to reboot the host. Week#6 vSphere 5.1
Network Adapter Properties • For each physical adapter, speed and duplex can be changed. • You might need to set the speed and duplex for certain NIC and switch combinations. Week#6 vSphere 5.1
VLANs • ESXi supports 802.1Q VLAN tagging. • Virtual switch tagging is one of three tagging policies supported. • Packets from a virtual machine are tagged as they exit the virtual switch. • Packets are untagged as they return to the virtual machine. • Affect on performance is minimal. • ESXi provides VLAN support by giving a port group a VLAN ID. Week#6 vSphere 5.1
Physical Network Considerations • Discuss VMware vSphere® networking needs with your network administration team. Discuss the following issues: • Number of physical switches • Network bandwidth required • Physical switch support for 802.3AD (for NIC teaming) • Physical switch support for 802.1Q (for VLAN trunking) • Network port security • Cisco Discovery Protocol (CDP) and its operational modes: listen, broadcast, listen and broadcast, and disabled. Week#6 vSphere 5.1
Lab 5 • In this lab, you will create a standard virtual switch and port group. • View the current standard virtual switch configuration. • Create a standard virtual switch with a virtual machine port group. • Attach your virtual machine to a virtual switch port group. Week#6 vSphere 5.1
Review of Learner Objectives • You should be able to do the following: • Define a virtual network. • Describe a virtual switch. • Describe the virtual switch connection types. • Describe the components of a vNetwork standard switch. • Create a vNetwork standard switch. Week#6 vSphere 5.1
Lesson 2 Configuring Standard Virtual Switch Policies Week#6 vSphere 5.1
Learner Objectives • After this lesson, you should be able to describe the security properties of a standard virtual switch port group: • Security • Traffic shaping • NIC teaming policies Week#6 vSphere 5.1
Network Policies • Three network policies: • Security • Traffic shaping • NIC teaming • Policies are defined: • At the standard virtual switch level: • Default policies for all the ports on the standard virtual switch • At the port or port group level: • Effective policies: Policies defined at this level override the default policies set at the standard virtual switch level. Week#6 vSphere 5.1
Security Policy Administrators can configure layer 2 Ethernet security options at the standard virtual switch and at the port groups. Week#6 vSphere 5.1
Traffic-Shaping Policy Network traffic shaping is a mechanism for controlling a virtual machine’s network bandwidth. Average rate, peak rate, and burst size are configurable.
Configuring Traffic Shaping Traffic shaping is disabled by default. Parameters apply to each virtual NIC in the standard virtual switch. On a standard switch, traffic shaping controls outbound traffic only. Week#6 vSphere 5.1
NIC Teaming Policy • NIC Teaming settings: • Load Balancing (outbound only) • Network Failure Detection • Notify Switches • Failback • Failover Order Week#6 vSphere 5.1
Load-Balancing Method: Originating Virtual Port ID This is the default virtualswitch physicalswitch virtualNICs physicalNICs Week#6 vSphere 5.1
Internet Load-Balancing Method: Source MAC Hash Only the dVS can do route based on physical NIC load physicalswitch virtualswitch virtualNICs physicalNICs Week#6 vSphere 5.1
Internet Load-Balancing Method: IP-Hash This one needs 802.3ad at the physical switch physicalswitch virtualswitch virtualNICs physicalNICs Week#6 vSphere 5.1
Detecting and Handling Network Failure Network failure is detected by the VMkernel, which monitors: • Link state only • Link state, plus beaconing Switches can be notified whenever: • A failover event occurs • A new virtual NIC is connected to the virtual switch Failover implemented by the VMkernel based on configurable parameters: • Failback: • How physical adapter is returned to active duty after recovering from failure • Load-balancing option: • Use explicit failover order. Always use the highest order uplink from the list of active adapters that pass failover detection criteria. Week#6 vSphere 5.1
Review of Learner Objectives • You should be able to describe the security properties of a standard virtual switch port group: • Security • Traffic shaping • NIC teaming policies Week#6 vSphere 5.1
Key Points • There are two connection types on a virtual switch: virtual machine and VMkernel. • A standard virtual switch is a virtual switch configuration for a single host. • Network policies set at the standard virtual switch level can be overridden at the port group level. • Questions? Week#6 vSphere 5.1
A virtual switch, just like a real switch, work at layer 3 of the OSI model. • True or False Week#6 vSphere 5.1
Answer • False – they work at layer 2. Week#6 vSphere 5.1
It is possible to have two virtual switches mapped to the same vmnic. True or False Week#6 vSphere 5.1
Answer • False Week#6 vSphere 5.1
It is possible to have two vmnics mapped to the same vSS. True or False Week#6 vSphere 5.1
Answer • True Week#6 vSphere 5.1
A virtual standard switch allows two connection types, _____________ and _______________ Fill in the blanks Week#6 vSphere 5.1
Answer • Virtual machine • VMkernel Week#6 vSphere 5.1
You are configuring a Vmkernel port. Which is not a configuration setting? • DNS • IP address • Netmask • Gateway Week#6 vSphere 5.1
Answer • A Week#6 vSphere 5.1