NSX practice LAB for exam 3v0-643, Leitfäden, Projektarbeiten und Recherchen von Informatik

Nur auf Docsity: Lade NSX practice LAB for exam 3v0-643 und mehr Leitfäden, Projektarbeiten und Recherchen als PDF für Informatik herunter!

© 2015 VMware Inc. All rights reserved.

VMware NSX 6.2 Test Drive

Lab Exercises

Confidential

Lab Time!

1. Log in to myLearn 1. Go to https://mylearn.vmware.com/register.cfm?course= 2. Authenticate with your myLearn credentials. 3. If you don't have a myLearn account you can create one 4. Register for Training Labs 5. Go to the lab registration link above. 6. Review the details on the registration page then click "Continue" to confirm your registration. 7. Start the lab 8. Click on "Start this Course". This will open a new browser window which will provide access to your lab. 9. Click on the "Exit" button if you want to leave your lab and continue later on, or just close the browser window. 2. Important: How to reconnect to your lab: 1. Log in to myLearn again, and then click on the link for myEnrollments. 2. Find the Training Lab course, and then click on the Continue button, and then click the Continue this Course button. If you try to access the labs through the registration link from step (2) you will get a "duplicate registration" error. CONFIDENTIAL 2

Credentials used within the NSX Training lab Confidential § ControlCenter (machine you are RDPing to): [email protected]/VMware1! § vCenter Server: root/VMware1! § ESXi hosts: root/VMware1! § NSX Manager Web: admin/VMware1! § NSX Manager API: admin/VMware1! § Linux vVMs: root/VMware1! § Windows vVMs: vmware/VMware1! § vpodrouter: admin/VMware1!VMware1! § Log Insight: admin/VMware1!

NSX Training – Lab Networks and IP Addressing

Confidential

• • Transit Network - 192.168.10.0/ § Logical Networks (VXLAN)
• • Web Tier Network - 172.16.10.0/
  • • web-sv-01a - 172.16.10.
  • • web-sv-02a - 172.16.10.
• • App Tier Network - 172.16.20.0/
  • • app-sv-01a - 172.16.20.
• • DB Tier Network - 172.16.30.0/
  • • db-sv-01a - 172.16.30.
• • HQ Uplink A Network - 192.168.100.0/ § VLAN Networks
• • HQ Uplink B Network - 192.168.100.0/
• • Primary Management Network – 192.168.110.0/
• • Management & Edge VTEP - 192.168.150.0/
• • Compute VTEP - 192.168.250.0/

Lab Exercise 1 – NSX Manager and vSphere Web Client Goal: Attach NSX Manager to vCenter Server and familiarize yourself with both the lab environment and NSX vSphere Web Client Plugin § Review the Lab Credentials and Tips, then login to your vPod using the provided access information and details on Slide 5. You should see a desktop similar to the image below, with shortcuts for browsers, putty and the NSX vSphere product documentation.

§ This is the NSX appliance administration User Interface Tasks performed here include Managing NSX system processes, configuring appliance networking and services such as NTP/Syslog, Database backup and restore, certificate management and attaching NSX to vCenter Server. Apart from the initial setup, there is generally limited need to use this interface however you should still understand the available options. § To begin configuration of your lab environment, click Manage vCenter Registration to attach NSX Manager to the following vCenter Server: § vc-l-01a.corp.local § Using Firefox, access the NSX Manager Administrative UI at: § https://nsxmgr-l-01a.corp.local (bookmarked) § If you are logged in to the vSphere web client, log out to ensure the NSX Networking and Security Web Client plugin is loaded § Login using the credentials on slide 4 Lab Exercise 1 – NSX Manager and vSphere Web Client

§ Now Configure a Syslog Server under Manage - > Settings - > General and point to: 192.168.110.79 Port 514 and Protocol TCP § Syslog data will be useful for troubleshooting and reviewing data logged during configuration, and this step is required for the later Log Insight exercises

§ Also verify the NTP Server is correctly set to: 192.168.110.

§ Confirm both the Lookup Service and vCenter Server are reporting a status of Connected Lab Exercise 1 – NSX Manager and vSphere Web Client

§ Now that NSX Manager is connected to vCenter Server, login to the vSphere Web Client for Site A at: § https://vc-l-01a.corp.local/vsphere-client or use the browser bookmark § Use root / VMware1! Credentials. § If you have already logged in before, you may need to log back out again to see the ‘Networking & Security’ plugin. § With NSX for vSphere administration and configuration has been centralized as a Web Client plugin to provide a consistent look and feel across VMware products. Note that the initial login will take several minutes as the plugin is installed and initialized. Once logged in, you should verify you have a ‘Networking & Security’ option available under Home - > Inventories Lab Exercise 1 – NSX Manager and vSphere Web Client

Goal: Now that NSX Manager is attached to vCenter, we are ready to start configuring NSX. In this exercise you will deploy an NSX Controller Cluster of 3 nodes to provide a highly available, scale out Control Plane for logical networking.

• Navigate to the Networking & Security Plugin, then from NSX Home - > Installation - > Management Screen
• Click plus to add an NSX Controller Node and deploy a controller with the following options:
  • NSX Manager: 192.168.110.
  • Datacenter: NSX Site A
  • Cluster/Resource Pool: Management and Edge Cluster
  • Datastore: ds-site-a-nfs
  • Connected To: Mgmt_Edge_VDS – VM Mgmt dvPortgroup
  • Under IP Pool create a New IP Pool. As NSX Controller nodes are connected to the management network use details in the screenshot to ensure there are no conflicts with existing hosts on this network
  • Set a password (only required on first node) of: Length of 12 or more characters, containing at least one upper case, lower case, numeric and special character, eg VMware1!VMware1!
• Deploy the Controller, and wait for the Status field to change from Deploying to Connected (this will take several minutes) The IP parameters from the Pool and password are injected into the NSX Controller VM as OVF guest properties during deployment time Lab Exercise 2 – NSX Controller

• Next deploy an additional 2 NSX controllers using the same parameters as before
• Wait for deployment to complete and their Status to report Connected. If you see the original controller briefly report Disconnected, this is the expected behavior (the API service is temporarily unavailable during cluster expansion)
• You now have your NSX management plane (NSX Manager) and NSX control plane (NSX Controllers) up and running. In the next section, you will configure the NSX data plane (ie the ESXi hypervisors).
• Well done, you are truly on your way to become a network virtualization expert. Give yourself a pat on the back! Lab Exercise 2 – NSX Controller

Lab Exercise 3 – Logical Switches App Logical Switch 172.16.20.0/ DB Logical Switch 172.16.30.0/ Web Logical Switch 172.16.10.0/ Transit Logical Switch 192.168.10.0/ Topology: In this lab exercise we will create the base L2 connectivity for virtual machines and external connectivity using VXLAN Logical Switches. As a prerequisite for NSX, first we need to prepare the underlying vSphere infrastructure

Goal: Prepare vSphere clusters for network virtualization in one simplified workflow. Then demonstrate how VXLAN provides the ability to provision a L2 overlay across L3 network boundaries to make efficient use of their compute and storage resources without modifying the underlying network configuration.

• From the NSX Home - > Installation - > Host Preparation screen, click on the Actions/Install link to prepare all 2 clusters. This deploys all required kernel modules and user space components needed for NSX
• Once all Clusters are prepared and reporting green, you will move on to configuring VXLAN. Select the Not Configured link (you will perform this step for each cluster) Lab Exercise 3 – Preparation and VXLAN (Logical Switches)

• Now navigate to the NSX Home - > Installation - > Logical Network Preparation screen:
  • Expand the various clusters to ensure all VMKNics are in the correct networks, and the VLAN and teaming policies are as expected. All hosts should also report a status of Green: Lab Exercise 3 – Preparation and VXLAN (Logical Switches)

• Next click on the Segment ID tab and then edit and enter a range of 10000 - 19999 for the Segment ID Pool field Multicast addresses are optional and are used only in Hybrid or Multicast VXLAN replication mode. To demonstrate how NSX reduces dependencies on the physical network, in this lab Unicast mode will be used. This means no multicast addresses are supplied during configuration.
• Finally select the Transport Zones tab and click the Plus sign. Add a Transport Zone spanning all three clusters (this screen can take a while to display) and call it Local-Transport-Zone-A or similar. Then select a Replication Mode of Unicast Transport Zones are similar to the Network Scopes used in vCNS and determine the span of NSX logical networks. Lab Exercise 3 – Preparation and VXLAN (Logical Switches)