-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
1/274
Implementing the Cisco
Nexus 1000V (DCNX1K)
v2.0 Lab GuideL5557C-001December 2012
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
2/274For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
3/274
Implementing the Cisco Nexus 1000V
(DCNX1K) v2.0 Lab GuideL5557C-001December 2012
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
4/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
5/274
Global Knowledge Training LLC TOC-1
Table of Contents
Lab 0: Global Knowledge Remote Labs .................................................................. L0-1
Lab 1: Set Up the VMware vSphere Environment ................................................... L1-1
Lab 2: Install and Configure the Cisco Nexus 1000V VSMs .................................. L2-1
Lab 3: Install and Configure the Cisco Nexus 1000V VEMs .................................. L3-1
Lab 4: Upgrading the Cisco Nexus 1000V VSM and VEM .................................... L4-1
Lab 5: Optimize the Cisco Nexus 1000V Implementation ...................................... L5-1
Lab 6: Configuring Security Features ...................................................................... L6-1
Lab 7: Configuring Quality of Service ..................................................................... L7-1
Lab 8: Configuring Management Features ............................................................... L8-1
Lab 9: Configuring SPAN and ERSPAN ................................................................. L9-1
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
6/274
Table of Contents
TOC-2 Global Knowledge Training LLC
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
7/274
Global Knowledge Training LLC L0-1
L0
Global Knowledge Remote Labs
The purpose of this lab is to introduce you to the Global Knowledge Remote Labs
Environment used for this course.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
8/274
Lab 0: Global Knowledge Remote Labs
L0-2 Global Knowledge Training LLC
Activity ObjectivesIn this activity, you will be introduced to the Global Knowledge Remote Labs environment
and the labs contained in this course. You will familiarize yourself with the interface and
devices.
After completing this activity, you will be able to meet these objectives:
Understand the labs in the course and IP addressing scheme used
Login to the Global Knowledge Remote Labs environment
Become familiar with the lab topology and access all devices
Outline
This lab guide includes the following activities:
Lab 0: Global Knowledge Remote Labs Lab 1: Set Up the VMware vSphere Environment
Lab 2: Install and Configure the Cisco Nexus 1000V VSMs
Lab 3: Install and Configure the Cisco Nexus 1000V VEMs
Lab 4: Upgrading the Cisco Nexus 1000V VSM and VEM
Lab 5: Optimizing the Cisco Nexus 1000V Implementation
Lab 6: Configuring Security Features
Lab 7: Configuring Quality of Service Lab 8: Configuring Management Features
Lab 9: Configuring SPAN and ERSPAN
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
9/274
Lab 0: Global Knowledge Remote Labs
Global Knowledge Training LLC L0-3
Visual Objective
The figure portrays the Global Knowledge DCNX1KV v2.0 lab topology you will be
accessing. Each pod (team of two students) will have three dedicated servers: a server
dedicated for VMware vCenter Server 5.0 and two VMware ESXi 5.0 hosts. Each pod will
leverage shared networking and storage.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
10/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
11/274
Lab 0: Global Knowledge Remote Labs
Global Knowledge Training LLC L0-5
Required Resources
These are the resources and equipment that are required to complete this activity:
A computer with an Internet connection, a web browser, and Remote Desktop.
Lab logins assigned by your instructor.
Activity Procedure
Complete these steps:
Note The Global Knowledge Remote Labs environment is accessed via a web browser.
Each pod (team of two) will have a unique login, which will grant access to the
equipment assigned to your pod.
1. Examine the lab topology diagram in the Visual Objective of this lab to familiarizeyourself with the environment before we login.
2. Your instructor will provide the credentials necessary to log into Global KnowledgeRemote Labs. Write them down here for your reference:
There is also a tear-out topology diagram as the last page of the lab guide where you can
note your username and password. This page also contains logins and IP addresses for all
lab devices you may need to reference throughout the labs.
Username Password
Note When troubleshooting with your instructor you will need to provide them with your
pod number, and possibly your credentials.
3. From the classroom computer (or your own computer), launch a web browser. Navigate tothe following URL:
http://www.remotelabs.com/
Note You can access Remote Labs from the classroom, and also from home/hotel using
the same steps outlined in this lab. For the duration of this class you will have 24-
hour access to your equipment.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
12/274
Lab 0: Global Knowledge Remote Labs
L0-6 Global Knowledge Training LLC
Note While at a Global Knowledge training center, you will need a wired Internet
connection to access www.remotelabs.com. You cannot connect to the site using
Global Knowledges wireless network.
4. You should see the Global Knowledge Live Labs login screen.
5. Log in using the credentials provided to you by your instructor. Click >Log In.
6. Accept any terms and conditions and close any dialog boxes that appear.
7. You should see the Live Labs start page when you have successfully logged in.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
13/274
Lab 0: Global Knowledge Remote Labs
Global Knowledge Training LLC L0-7
8. In the upper left-hand side of the Live Labs page there is a countdown timer. This timerindicates the amount time remaining in your lab reservation and will provide ample time to
complete the labs. Review the time you have left in your pod for the week.
9. Expand + Pod P(where Pis your pod number) so you can view information about yourpod and its initial setup. DO NOT use the Reset To link.
10. The Topologylink is how you connect to your Lab Topology. This is the only link you
should click in this menu.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
14/274
Lab 0: Global Knowledge Remote Labs
L0-8 Global Knowledge Training LLC
11. Click the Topologylink. This will open an RDP session to the Remote Labs equipment.Click Open to launch the RDP session, trust connections to the server, and dismiss all other
dialog boxes.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
15/274
Lab 0: Global Knowledge Remote Labs
Global Knowledge Training LLC L0-9
Note Both students in a single team can log in to the Topologyat the same time. One
student can type the commands for a given lab, while the other student shadows on
their own computer.
12. If prompted, click your username and again enter the password provided by your instructorin Step 2, and then click the arrow or hit Enterto login.
13. Once the Remote Desktop window opens, you will see the Remote Lab Panel, with theLab Topologytab open. You should see a picture of the Remote Labs topology.
14. There are several clickable icons in the Lab Topology. This is how you will access yourlab devices. Clicking an icon will open a new tab.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
16/274
Lab 0: Global Knowledge Remote Labs
L0-10 Global Knowledge Training LLC
15. First, you will connect to the vCenter Serverhost. Click on the icon labeled vCenterServer.
16. If you are not automatically logged into the server, click the Ctrl Alt Del icon in theright-hand bar to login to the server.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
17/274
Lab 0: Global Knowledge Remote Labs
Global Knowledge Training LLC L0-11
17. Click the Administratoruser, and enter the password cisco123.
This will open a session to a Windows Server system with a number of applications on the
desktop. This is where you will later install vCenter Server and perform most of the lab
configuration.
18. Go back to the Lab Topologytab at the top of the RDP window.
19. Next, click on the ESXi 1host 10.0.1.1. Verify you see the following screen.
20. Last, click on the ESXi 2host 10.0.1.2. Verify you see the same screen.
21. You have successfully connected to Global Knowledge Remote Labs!
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
18/274
Lab 0: Global Knowledge Remote Labs
L0-12 Global Knowledge Training LLC
Activity Verification
You have completed this task when you attain these results:
Understand all the devices and the lab IP addressing scheme
Logged into Global Knowledge Remote Labs using the credentials supplied by yourinstructor.
Verified connectivity to vCenter Server and both ESXi hosts.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
19/274
Global Knowledge Training LLC L1-1
L1
Set Up the VMware vSphereEnvironment
Complete this lab activity to practice what you learned in the related lesson.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
20/274
Lab 1: Set Up the VMware vSphere Environment
L1-2 Global Knowledge Training LLC
Activity ObjectiveIn this activity, you will install VMware vCenter Server on your server and configure it to
manage your ESXi hosts. After performing this lab, you should be able to do the following:
Install vCenter Server and the vSphere Client to manage your VMware environment.
Login to vCenter Server via the vSphere Client, create a data center, and add your ESXihosts to the data center.
View the default VMware vNetwork standard switches on your ESXi hosts.
Configure access to an iSCSI datastore.
Modify a virtual machine port group on vSwitch0.
Add a pre-configured Windows virtual machine, and connect the VMs vNICs tovSwitch0 on the ESXi host.
Clone the first virtual machine and place the new VM on the seconds ESXi host.
Verify connectivity between the two virtual machines.
Required Resources
These are the resources and equipment required for each pod to complete this activity:
Two VMware ESXi 5 hosts
One server to install VMware vCenter 5 and vSphere Client 5 onto
All pods share the following lab core devices:
One switch for server networking
One iSCSI-based storage device
Job Aids
These job aids are available to help you complete the lab activity:
Appendix A: Answer Key
Lab Topology diagram
Tear-Out reference (last page of this lab guide)
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
21/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-3
Task 1: Install vCenter ServerIn this task, you will install vCenter Server 5 on your server in order to manage your ESXi
5 hosts.
Activity ProcedureComplete these steps:
1. From your vCenter Server machine, open the folder with the name VMware VIM 5.0.0from your desktop and double-click on the autorun.exe application.
2. The VMware vCenter Installer will open. Click vCenter Server, and then click Install.
3. Accept the default language of English by clicking OK.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
22/274
Lab 1: Set Up the VMware vSphere Environment
L1-4 Global Knowledge Training LLC
4. Wait for the VMware vCenter installation window to start. You will have to wait for theMicrosoft C++ and .NET Framework to install.
5. Click Nextwhen you can.
6. Click Nextto the End-User Patent Agreement.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
23/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-5
7. Click I agree to the terms in the license agreementand then click Next.
8. Enter customer information and leave the License Keyfield blank, and then click Next.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
24/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
25/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-7
10. Accept the default SYSTEM account, and ensure the fully qualified domain name is listedas LAB-VCENTER, and then click Next.
11. Click Okayto acknowledge if the fully qualified domain name cannot be resolved.
12. Accept the default installation folders and click Next.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
26/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
27/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
28/274
Lab 1: Set Up the VMware vSphere Environment
L1-10 Global Knowledge Training LLC
16. Accept the default JVM (Java Virtual Machine) memory size and click Next.
17. Click Install.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
29/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-11
Note The installation will take 20-30 minutes to complete. Kick off the installation, and then
take a break!
18. When the installation has completed, click Finish.
19. Return to the vCenter Installer wizard. Click vSphere Client, and then click Installtoinstall the client application used to access vCenter Server.
20. Accept the default language of English by clicking OK. The install wizard will start.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
30/274
Lab 1: Set Up the VMware vSphere Environment
L1-12 Global Knowledge Training LLC
21. Click Nextto begin the vSphere Client installation.
22. Click Nextto accept the End-User Patent Agreement.
23. Click I agree to the terms in the licenseagreement to accept the EULA, and then clickNext.
24. Enter user Ciscoand organization Cisco Systems, and then click Next.
25. Leave the default Destination Folder. Click Next.
26. Click Install. The install process will take approximately 5-10 minutes.
27. Click Finishwhen the installation has completed.
28. Click Exiton the VMware vSphere Installerpage.
Activity Verification
You have completed this task when you attain these results:
Installed vCenter Server 5.0
Installed the vSphere Client 5.0 application
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
31/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
32/274
Lab 1: Set Up the VMware vSphere Environment
L1-14 Global Knowledge Training LLC
30. If you receive a warning, click the Install this certificatecheckbox and then clickIgnore.
31. Click OK. You are using the VMware evaluation license, which is valid for 60 days.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
33/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-15
32. Right-click your vCenter Server instance in the left-hand inventory pane and click NewDatacenter.
33. Name your data center Lab-Datacenter.
34. Right-click your data center and choose Add Host.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
34/274
Lab 1: Set Up the VMware vSphere Environment
L1-16 Global Knowledge Training LLC
35. Enter the first ESXi hosts IP address 10.0.1.1. Enter the username rootand the passwordcisco123.
36. Click Yes to trust the host.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
35/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-17
37. Click Nextto proceed.
38. Click Nextto use evaluation mode.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
36/274
Lab 1: Set Up the VMware vSphere Environment
L1-18 Global Knowledge Training LLC
39. Click Next. Do not enable lockdown mode.
Note Lockdown Mode is a feature that denies remote rootuser access to the ESXi host.
Lockdown Mode can be enabled and disabled at any point from vCenter Server. You
will not leverage this feature in the lab.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
37/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-19
40. Click Nextto place this host in your newly-created datacenter.
41. Click Finishto add the host to your datacenter.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
38/274
Lab 1: Set Up the VMware vSphere Environment
L1-20 Global Knowledge Training LLC
42. Repeat Steps 34 to 41 to add a second ESXi host with IP address 10.0.1.2. Enter the sameusername rootand password cisco123.
43. Note the progress on the Recent Taskspane on the bottom. Confirm both ESXi hostsappear under Lab-Datacenter.
Activity VerificationYou have completed this task when you attain these results:
Created a datacenter and added two ESXi hosts using the vSphere Client, connected tovCenter Server.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
39/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-21
Task 3: View the vNetwork Standard SwitchConfiguration
In this task, you will use the VMware vSphere Client to view the default virtual network
configuration on your ESXi hosts.
Activity Procedure
Complete these steps:
44. Using the navigation bar, navigate to the Hosts and Clusters inventory view Home>Inventory> Hosts and Clusters, or use the shortcut Ctrl-Shift-H.
Note There are shortcuts for each inventory view in vCenter Server. Each inventory view
controls what is visible in the left-land inventory pane.
Note Use Ctrl-Shift-Hfor Hosts and Clusters, Ctrl-Shift-Vfor VMs and Templates,
Ctrl-Shift-Nfor Networking, or Ctrl-Shift-Dfor Datastores and Datastore
Clusters.
45. If necessary, maximize the inventory view and select your first ESXi host 10.0.1.1, thenclick the Configurationtab.
46. In the Hardwaresection, click the Networkinglink. A vNetwork standard switch vSwitch0 is created by default when the Global Knowledge labs team installed ESXi
during the course setup procedure. On vSwitch0 you should see a VMkernel port, a Virtual
Machine port group, and a physical NIC (Network Interface Card) uplink adapter, labeled
as vnmnic0.
Note VMkernel ports are used to provide an IP stack to the VMware Hypervisor. They are
used for management, vMotion, Fault Tolerance, and IP-based storage like iSCSI
and NAS.
Note The VMkernel port created by default is assigned the management IP address of the
ESXi server. This IP address was assigned upon initial configuration of the server bythe labs team. This port is named Management Networkby default.
Note Virtual Machine port groups connect Virtual Machine vNICs to the vSwitch, just like a
regular NIC would connect to a switchport. The VM port group named VM Network
is created by default. Currently, there are no virtual machines (VM) connected to it.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
40/274
Lab 1: Set Up the VMware vSphere Environment
L1-22 Global Knowledge Training LLC
Note The left side of vSwitch0 is virtual, and the right side of vSwitch0 is physical. You
should see one physical NIC (vmnic0) connected to vSwitch0. VMware enumerates
physical NIC ports as vmnic0, vmnic1, and so on. vmnics are physical adapters
despite the v in the naming convention.
47. Now select your second ESXi host 10.0.1.2 in the left-hand inventory pane. Double checkthat there is also a vSwitch0 that contains a similar configuration.
Note vSwitch0 is what is called a standardvirtual switch. Standard vSwitches must be
configured on each and every host (their configuration is not shared), and are limited
in their feature set. The Nexus 1000V is a distributedvirtual switch, which permits
for a single point of network management, clear delineation of network and server
responsibility, VM policy mobility, and a much richer feature set closer to that of a
physical Ethernet switch.
Activity Verification
You have completed this task when you attain these results:
Viewed the configuration of vSwitch0 on both of your ESXi hosts.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
41/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
42/274
Lab 1: Set Up the VMware vSphere Environment
L1-24 Global Knowledge Training LLC
52. The Add Network Wizardwill appear. Select VMkernel as the new connection type, andthen click Next. You will use this port to connect to iSCSI storage.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
43/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
44/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
45/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-27
55. Verify the VMkernel port configuration, and then click Finishto complete.
56. Click Closeto close the vSwitch0 Properties window.
57. Now that you have a VMkernel port that can talk to the iSCSI storage target in VLAN 11,you will enable the iSCSI software adapter to speak iSCSI over this network.
58. Under the Configuration tab, select Storage Adaptersunder the Hardwarepane.
Click the Addlink to add a new software storage adapter.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
46/274
Lab 1: Set Up the VMware vSphere Environment
L1-28 Global Knowledge Training LLC
59. Leave Add Software iSCSI Adapterselected, and then click OK. Click OKto dismissthe notification.
60. Click the newly created iSCSI software adapter on top of the Storage Adapterspane, andthen click the Propertieslink on the lower Detailspane.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
47/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-29
61. Click the Generaltab, and then click the Configurebutton.
62. Ensure the Enabledcheckbox is clicked. Enter an (optional) iSCSI Aliasof SW-Init-1foryour first server as shown below, and then SW-Init-2for your second server. Click OK.
Leave the iSCSI Nameas it appears.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
48/274
Lab 1: Set Up the VMware vSphere Environment
L1-30 Global Knowledge Training LLC
63. Now that the iSCSI software initiator has been enabled, you can connect to iSCSI storage.
Click the Dynamic Discoverytab then click Addto connect to a storage target.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
49/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
50/274
Lab 1: Set Up the VMware vSphere Environment
L1-32 Global Knowledge Training LLC
67. Right-click on datastore1 and select Rename. On your first host, name this datastorelocal1. On your second host, name this datastore local2.
68. Repeat all of Task 4 for your second ESXi server, 10.0.1.2. When you create the VMkernelport for IP storage for this server, use IP address 10.0.11.2/24. Connect to the same iSCSI
storage target.
Activity Verification
You have completed this task when you attain these results:
You have connected your two ESXi hosts to iSCSI-based storage, and the ISCSIVMFSdatastore is visible to both hosts.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
51/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-33
Task 5: Modify a Virtual Machine Port Group onvSwitch0
In this task, you will rename the default virtual machine port group on vSwitch0, and
assign its ports to a VLAN on both ESXi hosts.
Activity Procedure
Complete these steps:
69. Using the navigation bar, navigate to the Hosts and Clusters inventory view Home>Inventory> Hosts and Clusters, or use the shortcut Ctrl-Shift-H.
70. Select your first ESXi host 10.0.1.1, and then click the Configurationtab.
71. In the Hardwarepane, click the Networkinglink.
72. Click the Properties link next to vSwitch0.73. Click the network called VM Network, and then click Edit
Note VM Networkis the default virtual machine port group created when ESXi is installed.
As a best practice, this port group should be renamed.
74. Under the General tab, enter the Network Label Production, overwriting the existingname. Enter VLAN ID14, click OK, and then click Close.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
52/274
Lab 1: Set Up the VMware vSphere Environment
L1-34 Global Knowledge Training LLC
75. Click Finishand Close. Repeat all of Task 5 on your second ESXi host. Verify the virtualmachine port group was successfully modified. Your vSwitch configuration should match
the provided screenshots one shown for each host.
ESXi Host 1 (10.0.1.1):
ESXi Host 2 (10.0.1.2):
Activity Verification
You have completed this task when you attain these results:
Modified a virtual machine port groups name and VLAN assignment on vSwitch0 ofboth ESXi hosts.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
53/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-35
Task 6: Add Virtual Machines to the vCenterServer Inventory
In this task, you will add Windows virtual machines to the vCenter Server inventory to be
used as production VMs in later labs.
Activity Procedure
Complete these steps:
76. Navigate to the Datastoreinventory view by clicking Inventory > Datastores, or usingthe shortcut Ctrl-Shift-D.
Expand your vCenter and Datacenter icons until you see your datastores listed in the
inventory pane.
77. Right-click on the ISCSIVMFSdatastore in the inventory pane, and select Browse
Datastore...
78. In the Datastore Browserwindow, double-click the WinServer-1folder. Locate theWinServer-1.vmxfile, right-click it, and then choose Add to Inventory.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
54/274
Lab 1: Set Up the VMware vSphere Environment
L1-36 Global Knowledge Training LLC
79. Leave the name WinServer-1and then click Next.
80. Select your first ESXi host 10.0.1.1 as the destination for the VM and click Next.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
55/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
56/274
Lab 1: Set Up the VMware vSphere Environment
L1-38 Global Knowledge Training LLC
84. Click Network Adapter 1 in the hardware list. On the right-hand side, click the Networklabeldropdown and select the newly named Productionvirtual machine port group (if it is
not already selected). Click OK.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
57/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-39
85. Right-click the WinServer-1VM in the inventory pane and click Open Console.
86. Click the green Power Onicon.
87. If you are prompted, choose I moved itand click OK.
VMware asks this since you imported an existing VM, instead of creating a new one.
88. After Windows boots, in the menu bar of the console, click VM > Guest > SendCtrl+Alt+Del (if you do not see the login screen).
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
58/274
Lab 1: Set Up the VMware vSphere Environment
L1-40 Global Knowledge Training LLC
89. Log in with username administratorand passwordcisco123.
90. From within the Windows VM console window, click Start > Settings >NetworkConnections.
Note If you see more than one network connection listed, you are likely looking at yourremote PC desktop. Make sure that you are clicking the Start button within the
Windows VM console window.
91. Right-click the Local Area Connectionand click Properties.
92. Select Internet Protocol (TCP/IP)and then click the Propertiesbutton.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
59/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-41
93. Ensure the IP address is 10.0.14.1with a mask of 255.255.255.0, and no default gateway.Correct the IP address/mask if necessary, and then click OK.
Select Show icon in notification area when connected. Click OK. Then close the
Network Connectionswindow.
94. Next, confirm the Windows Firewall service is off so you can use ping to test VM-to-VMconnectivity once you create more VMs.
From within the VM console, click Start > Settings > Control Panel.
95. Double-click the Windows Firewallicon.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
60/274
Lab 1: Set Up the VMware vSphere Environment
L1-42 Global Knowledge Training LLC
96. Ensure Offis selected. Click OK.
97. Close the Control Panelwindow and return to the vSphere Client.
Activity Verification
You have completed this task when you attain these results:
Added a Windows virtual machine to the vCenter Server inventory
Connected the virtual machines vNIC to the Production virtual machine port group on
vSwitch0
Configured the IP address and subnet mask on the vNIC inside the virtual machine
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
61/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-43
Task 7: Clone a Virtual Machine and VerifyConnectivity
In this task, you will clone (make an identical copy of) the Windows VM imported in the
previous task called WinServer-1, which is running on your first ESXi host. Place thecloned VM, which will be called WinServer-2, on your second ESXi host.
Activity Procedure
Complete these steps:
98. Ensure you are in the Hosts and Clustersinventory view or use the shortcut Ctrl-Shift-H.
99. Right-click the WinServer-1VM and click Clone.
100.Enter the name WinServer-2and click Next.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
62/274
Lab 1: Set Up the VMware vSphere Environment
L1-44 Global Knowledge Training LLC
101.Choose your second ESXi host 10.0.1.2and click Next.
102.Choose the iSCSI datastore ISCSIVMFS as the destination for the VMs files. Click Next.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
63/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-45
Note Being able to change the format of a cloned VMs hard disk is a significant benefit of
the VMware cloning feature. The source VM can remain powered on and
uninterrupted during the cloning process.
Note VM disks (represented as .vmdk files) can be thick provisioned, which means the
space allocated to a VMs hard drive is shown as used on the datastore, whether
there is anything written to it or not. Alternately, a VM disk can be thin provisioned,
which leaves the unused space free for other VMs to use until the VM requests more
space to write to.
103.On the Guest Customizationpage click Power on this virtual machine after creation,and then click Next.
Note If a VMware administrator wanted to have the ability to customize rollouts of multiple
similar virtual machines while customizing their identities before they were powered
on, Microsoft sysprep or a comparable customization tool could be loaded into
vCenter Server for this purpose.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
64/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
65/274
Lab 1: Set Up the VMware vSphere Environment
Global Knowledge Training LLC L1-47
Note The VMs and Templatesview shows a logical view, without the physical hosts..
Folders created in one view will not appear in a different view, allowing a VMware
administrator to organize differently based on inventory object type.
107.Right-click the VM WinServer-2and select OpenConsole. Log in with usernameAdministratorand password cisco123.
Note You may get an IP address and computer name conflict error message because
WinServer-2 initially has the same IP address and computer name as WinServer-1,
since a clone is a completely identical copy of VM. Next, you will change the IP
address and name of the WinServer-2 VM.
108.From within the Windows VM console window, click Start > Settings >Network
Connections.
109.Right-click Local Area Connectionand click Properties.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
66/274
Lab 1: Set Up the VMware vSphere Environment
L1-48 Global Knowledge Training LLC
110.Select Internet Protocol (TCP/IP)and then click the Propertiesbutton.
111.Enter the IP address 10.0.14.2 with a mask of 255.255.255.0, and no default gateway.
Click OK. Select Show icon in notification area when connected. Click OK. Close the
Network Connectionswindow.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
67/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
68/274
Lab 1: Set Up the VMware vSphere Environment
L1-50 Global Knowledge Training LLC
117.Open the Command Promptshortcut on the desktop.
118.To verify connectivity between your two new VMs, ping the other VMs IP address at10.0.14.1.
Activity Verification
You have completed this task when you attain these results:
Cloned the virtual machine WinServer-1 located on the first ESXi host to create asecond virtual machine, WinServer-2, located on your second ESXi host.
Verified connectivity between both virtual machines using ping.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
69/274
Global Knowledge Training LLC L2-1
L2
Install and Configure the CiscoNexus 1000V VSMs
Complete this lab activity to practice what you learned in the related lesson.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
70/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
L2-2 Global Knowledge Training LLC
Activity ObjectiveIn this activity, you will install and perform initial configuration of a primary and
secondary Cisco Nexus 1000V VSM (Virtual Supervisor Module) using VMware vCenter
Server v5.0. After performing this lab, you should be able to perform the following:
Install a primary Cisco Nexus 1000V VSM using the Open Virtualization Format(OVF) template wizard-based method
Perform the initial configuration of the primary VSM
Establish the SVS connection to vCenter Server
Install a secondary Cisco Nexus 1000V VSM
Perform the initial configuration of the secondary VSM
Required Resources
These are the resources and equipment required for each pod to complete this activity:
Two VMware ESXi v5.0 hosts
One server running VMware vCenter Server v5.0 and VMware vSphere Client v5.0
Two Cisco Nexus 1000V VSM VM appliances
All pods share the following lab core devices (you will not be able to see other pods):
One switch for server networking
One iSCSI-based storage device
Command List
The table describes the commands used in this activity.
Command Description
svs-domain Enters SVS domain configuration mode.
domain id Assigns a Cisco Nexus 1000V domain-id.
control vlan Assigns a control VLAN to the domain.
packet vlan Assigns a packet VLAN to the domain.
svs connection Enables an SVS connection.remote {ip address | hostname}
Specifies the IP address or remote host name ofvCenter Server.
vmware dvs datacenter-name
Specifies the datacenter name in vCenter.
show svs connections
Displays the current connections to the CiscoNexus 1000V for verification.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
71/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
Global Knowledge Training LLC L2-3
show svs domain Displays the VSM domain configuration.
show interface brief Displays a short version of the interfaceconfiguration.
show system redundancystatus
Display the current redundancy status for theVSM.
copy running-configstartup-config Saves the running configuration.
system redundancy role{primary | secondary |standalone}
Configures a redundancy role for the VSM.
show module Displays module information.
attach module 2 Access the standby VSM console from the activeVSM.
show system resources Display system-related CPU and memorystatistics.
system switchover Switches over to the standby VSM.
Job Aids
These job aids are available to help you complete the lab activity.
Lab topology diagram in visual objective section in the beginning of this lab
Lab connections table in the general lab topology information section in the beginningof the lab guide
Lab IP address and VLAN plan in the general lab topology information section in thebeginning of the lab guide
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
72/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
L2-4 Global Knowledge Training LLC
Task 1: Prepare the VLAN InfrastructureIn this task, you will prepare the VMware environment for Cisco Nexus 1000V
deployment. The Cisco Nexus 1000V requires several dedicated VLANs (networks),
including Management, Control, and Packet, when deployed in Layer 2 mode.
The Nexus 1000V can also be deployed in routed mode (Layer 3), wherein the hosts
(VEMs) and Nexus 1000V VSM are on different subnets. Note the Nexus 1000V is not a
router. Routed mode simply means the VSM and VEMs are in different VLANs. Another
network device must actually perform the routing between the VLANs.
In this lab, you will deploy the Nexus 1000V in Layer 2 mode, where the VSM and VEMs
will have IP addresses in the same VLAN (subnet).
The Management VLAN is used for system login, configuration, and corresponds to the
mgmt0 interface. The management interface appears as the mgmt0 port on a Cisco Nexus
switch, and is assigned an IP address. Although the management interface is not used to
exchange data between the VSM and VEM, it is used to establish and maintain theconnection between the VSM and VMware vCenter Server.
The Control VLAN and the Packet VLAN are used for communication between the VSM
and the VEMs within a switch domain. The Packet VLAN is used by protocols such as
CDP, LACP, and IGMP. The Control VLAN is used for the following:
VSM configuration commands to each VEM, and their responses
VEM notifications to the VSM, for example a VEM notifies the VSM of the attachmentor detachment of ports to the DVS
VEM NetFlow exports are sent to the VSM, where they are then forwarded to aNetFlow Collector.
VSM active to standby synchronization for high availability.
Activity Procedure
Complete these steps:
1. Ensure you have clicked on the vCenter Servertab.
2. Log in to vCenter Server via the vSphere Client using localhost and the Windows sessioncredentials if you are not already logged in.
3. Go to the Hosts and Clustersinventory view, or use the shortcut Ctrl-Shift-H.
4. Select your first ESXi host 10.0.1.1, and then click the Configurationtab.
5. Click the Networkinglink, and then click the Propertieslink next to vSwitch0.
6. Click the Addbutton.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
73/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
74/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
75/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
Global Knowledge Training LLC L2-7
ESXi Host 2 (10.0.1.2)
Activity Verification
You have completed this task when you attain these results:
Added the virtual machines port groups Management, Control, and Packet to vSwitch0on both ESXi hosts.
The Management port group should not be a member of any VLAN.
The Control port group should be a member of VLAN 12.
The Packet port group should be a member of VLAN 13.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
76/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
77/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
Global Knowledge Training LLC L2-9
16. Select the OVA template nexus-1000v.4.2.1.SV1.4.ovaand click Open.
17. Click Nextto deploy the VM from the OVA file.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
78/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
L2-10 Global Knowledge Training LLC
18. Click Nextto confirm the OVF Template Details screen.
19. Click Acceptto the End User License Agreement and click Nextto proceed.
20. Enter the name N1000V-VSM1and click Next.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
79/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
80/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
L2-12 Global Knowledge Training LLC
23. Accept the default disk format and click Next.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
81/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
Global Knowledge Training LLC L2-13
24. Make sure the VSM source and destination networks are properly mapped: ControlControl, Management Management, Packet Packet. Click Next.
Note How you can click below the Destination Networksand a pull down option exists to
change the selection if needed.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
82/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
L2-14 Global Knowledge Training LLC
25. Configure the following values on the Propertiespage:
VSM Domain ID: 1
Nexus 1000V Admin User Password: cisco123
Management IP Address: 10.0.1.200
Management IP Subnet Mask: 255.255.255.0
Management IP Gateway: 10.0.1.254
26. Click Next.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
83/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
Global Knowledge Training LLC L2-15
27. Click the Power on after deploymentcheckbox, verify your configuration, and then clickFinishto complete the wizard and begin importing the VSM.
28. Wait for the deployment to complete, and then click Close.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
84/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
L2-16 Global Knowledge Training LLC
29. Click the N1000V-VSM1VSM virtual machine in the left-hand inventory pane and clickthe Summarytab. You should see the VSM deployed on the ISCSIVMFS datastore, and
connected to the three new networks.
Note If you accidentally deployed the VSM on the wrong host, simply drag and drop the
VM to the correct host to initiate a vMotion.
30. Right-click the VSM and select Open Console(or click the Open Console icon in themenu bar). Wait for the VSM to finish booting up, at which point the switch login prompt
will appear. This process can take several minutes.
31. Do not login to the VSM at this time. Close the console window when the VSM hasfinished booting.
Note If you clicked within the console window, you will need to press CTRL+ALTto
release the cursor out of the focus of the console.
32. From your vCenter Server host, open Internet Explorer and navigate to your VSM at theURL http://10.0.1.200.
The Nexus 1000V has a web interface where you can access an installer application, the
extension (plug-in) required for vCenter Server, and VEM software.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
85/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
Global Knowledge Training LLC L2-17
33. If the browser prompts you to add a security exception, do so. Close the window when youare done.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
86/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
L2-18 Global Knowledge Training LLC
34. Right-click on cisco_nexus_1000v_extension.xml. Click Save Target As and save the fileto the desktop.
Close the download dialog when the download is complete. Close Internet Explorer.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
87/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
Global Knowledge Training LLC L2-19
Note The extension is an XML-based plug-in used to authenticate the VSM to vCenter
Server, and enable communication between the two. The extension is unique per
VSM, and must therefore be downloaded directly from each VSM via the web
interface.
35. Go back to the vSphere Client connected to vCenter Server. Click Plug-ins > ManagePlug-insfrom the menu bar.
36. Right-click in the white space and select New Plug-in
37. Click Browseand navigate to your desktop. Double-click the XML file you justdownloaded.
38. Click Register Plug-into bind your VSM to vCenter Server using its unique extensionkey.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
88/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
L2-20 Global Knowledge Training LLC
39. Click Ignoreto continue using the default certificate.
40. Click OKto close the dialog box.
41. Once your Nexus 1000V plug-in appears as pictured, click Closein the Plug-in Managerwindow.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
89/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
Global Knowledge Training LLC L2-21
Activity Verification
You have completed this task when you attain these results:
Installed the Cisco Nexus 1000V VSM on your first ESXi host
Registered the Cisco Nexus 1000V extension to VMware vCenter
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
90/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
91/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
Global Knowledge Training LLC L2-23
47. Configure a connection to your vCenter Server.
N1000V-VSM(config)# svs connection LAB-VCENTERN1000V-VSM(config-svs-conn)# protocol vmware-vimN1000V-VSM(config-svs-conn)# remote ip address 10.0.1.50N1000V-VSM(config-svs-conn)# vmware dvs datacenter-name Lab-DatacenterN1000V-VSM(config-svs-conn)# connectN1000V-VSM(config-svs-conn)#
end
Note The first line in the configuration specifies the name of the connection. This name
does nothave to match the name of your vCenter instance. Multiple connections can
be stored in a single configuration. The second line specifies the protocol to use to
speak to vCenter Server, which is VIM (VMware). By default, VIM runs on SSL over
HTTP (HTTPS). The third and fourth lines specify the IP address of vCenter Server,
and the VMware Datacenter the Nexus 1000V should be a part of. Lastly, the
connectcommand uses the connection information entered to initiate a connection
to vCenter.
48. Verify the connection to vCenter from the NX-OS CLI.
Note If you are monitoring the Recent Taskspane in vCenter Server, you can see the
VSM being added to the inventory.
N1000V-VSM# show svs connections
connection LAB-VCENTER:
ip address: 10.0.1.50remote port: 80protocol: vmware-vim https
certificate: defaultdatacenter name: Lab-Datacenter
admin:max-ports: 8192
DVS uuid: 32 fe 2d 50 62 2c db 59-4e d7 c2 52 c9 aa f5 34config status: Enabledoperational status: Connectedsync status: Completeversion: VMware vCenter Server 5.0.0 build-455964
Note Your DVS (Distributed Virtual Switch) universally unique identifier (UUID) will vary.
UUIDs uniquely identify servers. The UUID shown is for this DVS. Each Nexus
1000V DVS will have a different UUID.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
92/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
L2-24 Global Knowledge Training LLC
49. Verify the status of the SVS domain.
N1000V-VSM# show svs domain
SVS domain config:Domain id: 1
Control vlan: 12Packet vlan: 13
L2/L3 Control mode: L2
L3 control interface: NAStatus: Config push to VC successful.
50. Inspect the connected interfaces on the Nexus 1000V.
N1000V-VSM# show interface brief
---------------------------------------------------------------------Port VRF Status IP Address Speed MTU
---------------------------------------------------------------------mgmt0 -- up 10.0.1.200 1000 1500
---------------------------------------------------------------------
Port VRF Status IP Address Speed MTU---------------------------------------------------------------------
control0 -- up -- 1000 1500
51. Verify the VSM is installed and active.
N1000V-VSM# show module
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------1 0 Virtual Supervisor Module Nexus1000V active *
Mod Sw Hw
--- ---------------- ------------------------------------------------
1 4.2(1)SV1(4a) 0.0
Mod MAC-Address(es) Serial-Num--- -------------------------------------- ----------1 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
Mod Server-IP Server-UUID Server-Name--- --------------- ------------------------------------ ------------------
1 10.0.1.200 NA NA
* this terminal session
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
93/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
Global Knowledge Training LLC L2-25
52. Confirm this VSM is the only Supervisor in the virtual Nexus 1000V chassis.
N1000V-VSM# show system redundancy status
Redundancy role
---------------
administrative: standalone
operational: standalone
Redundancy mode
---------------
administrative: HA
operational: None
This supervisor (sup-1)
-----------------------
Redundancy state: Active
Supervisor state: Active
Internal state: Active with no standby
Other supervisor (sup-2)------------------------
Redundancy state: Not present
Note You have not yet installed a secondary VSM (Supervisor) or any VEMs, but note how
this looks like the output of a physical chassis-based switchs modules, although our
switch is completely virtual.
53. Save the configuration.
N1000V-VSM# copy run start
[########################################] 100%
54. Return to the vCenter Server window.
55. You should see in the Recent Taskspane at the bottom of the window a new DistributedVirtual Switch (dvS) has been added to vCenter.
56. Navigate to the Networkinginventory view, or use the shortcut Ctrl-Shift-N.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
94/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
L2-26 Global Knowledge Training LLC
57. Expand the networking tree in the left pane to view the new vSwitch.
Note Any ports not specifically placed in a port group will be placed in the Quarantineport groups. Also notice that a VMware administrator cannot edit the settings of the
1000V dvS or its port groups all networking configuration is now the responsibility
of the network administrator.
Activity Verification
You have completed this task when you attain these results:
Performed initial configuration of the primary VSM
Registered and connected the Cisco Nexus 1000V VSM to VMware vCenter Server
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
95/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
Global Knowledge Training LLC L2-27
Task 4: Install a Secondary Cisco Nexus 1000VVSM
In this task, you will install a secondary VSM so you can run the Nexus 1000V in a highly
available Active/Standby configuration. This simulates having two Supervisors in a switchchassis.
Activity Procedure
Complete these steps:
58. Return to the Putty SSH session to your VSM at IP address 10.0.1.200.
59. Change the VSM HA role from standalone to primary.
N1000V-VSM# configureN1000V-VSM(config)# system redundancy role primary
60. Verify the VSMs role is now listed as primary, instead of standalone.
N1000V-VSM(config)# show system redundancy status
Redundancy role
---------------administrative: primary
operational: primary
Redundancy mode---------------
administrative: HAoperational: None
This supervisor (sup-1)-----------------------
Redundancy state: ActiveSupervisor state: Active
Internal state: Active with no standby
Other supervisor (sup-2)------------------------
Redundancy state: Not present
Note You MUST change the redundancy role before installing the secondary VSM.
Otherwise, both VSMs will become active and independent control planes as they
are not expecting to see a secondary VSM.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
96/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
L2-28 Global Knowledge Training LLC
61. Save your configuration.
N1000V-VSM(config)# copy run start[########################################] 100%
62. Now, you will add another VSM to fill the secondaryrole. Return to the vCenter Serverscreen and go to the Hosts and Clustersview, or use the Ctrl-Shift-Hshortcut.
63. Make sure your second ESXi host 10.0.1.2is selected.
64. Click File. Then click Deploy OVF TemplateThe Deploy OVF Template wizardopens.
65. Verify that the OVA nexus-1000v.4.2.1.SV1.4.ova is selected.
66. Click Nextto confirm the OVF Template Details.
67. Click Acceptto accept the EULA and click Nextto proceed.
68. Enter the name N1000V-VSM2and click Next.69. Select Nexus 1000V Secondaryand click Next.
Note Ensure you have selected the Secondaryinstaller before moving on.
70. Select your second ESXi host.
71. Choose the datastore ISCSIVMFS, Click Next.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
97/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
Global Knowledge Training LLC L2-29
72. Accept the default Disk Format(Thick Provision Lazy Zeroed) and click Next.
73. Make sure the networks are properly mapped and click Next.
74. Configure domain ID 1and password cisco123.
For the secondary VSM, do notenter an IP address, subnet mask and gateway, since the
information will be shared between the primary and secondary. Click Next.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
98/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
L2-30 Global Knowledge Training LLC
75. Click the Power on after deploymentcheckbox, verify your configuration, and then clickFinishto complete the wizard and begin importing the secondary VSM.
76. Wait for the deployment to complete and click Close.
77. Right-click the N1000V-VSM2 VMand select Open Console.
78. Wait for boot up to complete and the switch login message to appear.
Note The VSM power on process can take several minutes. The primary VSM may cause
the secondary VSM to reboot for HA synchronization.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
99/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
Global Knowledge Training LLC L2-31
79. Login with username adminand password cisco123. If you cannot login via the VMwareconsole, move on to the next step. There is an alternate method to connect. Close the
console to the secondary when you have verified you can login.
Note The switch prompt should contain (standby)after the hostname, which indicates
this is the standby, or secondary VSM.
80. Return to the Putty window to your primary VSM. Verify that the secondary VSM nowappears in the output of show module command.
You must wait for the secondary VSM to completely finish booting before it will show the
ha-standbystate. While booting, it will appear as powered-up.
N1000V-VSM(config)# show module
Mod Ports Module-Type Model Status--- ----- -------------------------------- ------------------ ------------
1 0 Virtual Supervisor Module Nexus1000V active *2 0 Virtual Supervisor Module Nexus1000V ha-standby
Mod Sw Hw
--- ---------------- ------------------------------------------------1 4.2(1)SV1(4a) 0.02 4.2(1)SV1(4a) 0.0
Mod MAC-Address(es) Serial-Num--- -------------------------------------- ----------
1 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA2 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
Mod Server-IP Server-UUID Server-Name
--- --------------- ------------------------------------ ------------------1 10.0.1.200 NA NA2 10.0.1.200 NA NA
* this terminal session
Note You may see a console message on the primary VSM regarding dropped frames
while the secondary VSM boots. This is normal.
Note You should see a console message indicating the secondary VSM is now online:
switch %PLATFORM-2-MOD_DETECT: Module 2 detected (Serial number
:unavailable) Module-Type Virtual Supervisor Module Model : unavailable
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
100/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
L2-32 Global Knowledge Training LLC
81. Verify that VSM is now in operational HA mode.
N1000V-VSM(config)# show system redundancy status
Redundancy role---------------
administrative: primaryoperational: primary
Redundancy mode---------------
administrative: HA
operational: HA
This supervisor (sup-1)-----------------------
Redundancy state: ActiveSupervisor state: Active
Internal state: Active with HA standby
Other supervisor (sup-2)------------------------
Redundancy state: Standby
Supervisor state: HA standbyInternal state: HA standby
82. Use the attachcommand to connect directly to the secondary VSM.
N1000V-VSM1(config)# attach module 2
Attaching to module 2 ...
To exit type 'exit', to abort type '$.'Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tacCopyright (c) 2002-2011, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software areowned by other third parties and used and distributed underlicense. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each such license isavailable athttp://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
83. Display the secondary VSMs system resources utilization.
N1000V-VSM(standby)# show system resources
Load average: 1 minute: 0.02 5 minutes: 0.25 15 minutes: 0.15Processes : 197 total, 1 running
CPU states : 0.0% user, 1.0% kernel, 99.0% idleMemory usage: 2075740K total, 865364K used, 1210376K free
62632K buffers, 469044K cache
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
101/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
102/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
L2-34 Global Knowledge Training LLC
89. Open a Command Prompt window from your vCenter Server desktop.
90. Start a continuous ping to the VSM IP address 10.0.1.200, using the command ping10.0.1.200 t.
91. Switchover again to make the VSM in module 1 the active primary VSM again.
N1000V-VSM# system switchover
92. Verify connectivity to the VSM is maintained from the continuous ping. Although a couplepings may be lost, there is no interruption to the data plane or end application user on thefailure of a VSM in a highly available configuration.
93. Open a Putty session to 10.0.1.200, login, and verify the active VSM is in module one andthat the VSM in module two changes from powered-up to ha-standby as follows.
N1000V-VSM# show module
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------1 0 Virtual Supervisor Module Nexus1000V active *
2 0 Virtual Supervisor Module Nexus1000V ha-standby
Mod Sw Hw--- --------------- ------
1 4.2(1)SV1(4a) 0.02 4.2(1)SV1(4a) 0.0
Mod MAC-Address(es) Serial-Num
--- -------------------------------------- ----------1 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
2 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
103/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
Global Knowledge Training LLC L2-35
Mod Server-IP Server-UUID Server-Name--- --------------- ------------------------------------ -----------------1 10.0.1.200 NA NA
2 10.0.1.200 NA NA
94. Close the Command Prompt continuous ping window.
Activity Verification
You have completed this task when you attain these results:
Installed a secondary VSM on your second ESXi host
Verified operational VSM high availability by manually issuing a system switchover
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
104/274
Lab 2: Install and Configure the Cisco Nexus 1000V VSM
L2-36 Global Knowledge Training LLC
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
105/274
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
106/274
Lab 3: Install and Configure the Cisco Nexus 1000V VEM
L3-2 Global Knowledge Training LLC
Activity ObjectiveIn this activity, you will install the Cisco Nexus 1000V VEM on each ESXi host, add hosts
to the distributed virtual switch, and configure Cisco Nexus 1000V port profiles. After
performing this lab, you should be able to perform the following:
Create a port profile for the Cisco Nexus 1000V uplinks
Create a Cisco Nexus 1000V virtual machine data port profile
Install Cisco Nexus 1000V VEM on each ESX host
Add hosts to the Cisco Nexus 1000V VSM
Verify that the VSM can see the VEMs
Migrate virtual machines to the Cisco Nexus 1000V
Required ResourcesThese are the resources and equipment required for each pod to complete this activity:
Two VMware ESXi 5.0 hosts
One server running VMware vCenter Server 5.0 and VMware vSphere Client 5.0
Two Cisco Nexus 1000V VSM VM appliances
All pods share the following lab core devices:
One switch for server networking
One iSCSI-based storage device
Command List
The table describes the commands used in this activity.
Command Description
hostname Configures the hostname for the switch.
port-profile [type{ethernet | vethernet}]
Creates a port profile.
vmware port-group Creates a VMware port group.
switchport mode trunk Configures an interface as a trunk port.
switchport trunk allowedvlan
Configures the allowed VLANs for a trunkinterface.
no shutdown Activates an interface.
system vlan Adds a system VLAN to a port profile.
state enabled Enables a port profile.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
107/274
Lab 3: Install and Configure the Cisco Nexus 1000V VEM
Global Knowledge Training LLC L3-3
copy running-config
startup-configSaves the running configuration.
show port-profile name
Specifies to display information about a specificport profile.
vmware -v Displays ESX version and build number.
esxcli software vib
install -v//cross
Installs the Cisco Nexus 1000V VEM image intothe ESX host.
vem status Displays whether the VEM agent is running.
vemcmd show port Displays a summary of VEM interfaces.
vemcmd show card Displays detailed information of a VEM.
show module Displays module information.
show interface ethernetstatus
Displays information about the interfaceconfiguration.
show mac address-table Displays the MAC address table.
show module vem mapping Displays information about the VEM mapping.
switchport mode access Sets the port mode to access interface.
switchport access vlan
Sets the VLAN membership of an accessinterface.
Job Aids
These job aids are available to help you complete the lab activity.
Lab topology diagram in the visual objectives section in the beginning of this lab
Lab connections table in the general lab topology information section in the beginning
of the lab guide
Lab IP address and VLAN plan in the general lab topology information section in thebeginning of the lab guide
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
108/274
Lab 3: Install and Conf igure the Cisco Nexus 1000V VEM
L3-4 Global Knowledge Training LLC
Task 1: Create VLANsIn this task, you will create the required VLANs on your Cisco Nexus 1000V virtual
switch. These VLANs will be used for Nexus 1000V traffic, storage and vMotion traffic,
and production VM traffic.
Activity Procedure
Complete these steps:
1. From the desktop of vCenter Server open a Putty SSH session to your VSM at IP address10.0.1.200. Log in to the switch with username adminand passwordcisco123.
2. Rename the VSM to N1000V.
N1000V- VSM# configureN1000V- VSM( conf i g) # hostname N1000V
N1000V( conf i g)#
3. Return to vCenter Server and note that VSM has already pushed this configuration changeto vCenter Server. Navigate to the Networkinginventory view, or use the shortcut Ctrl-
Shift-N.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
109/274
Lab 3: Install and Configure the Cisco Nexus 1000V VEM
Global Knowledge Training LLC L3-5
4. Return to your putty session to the VSM and create all the VLANs required for the labs.
N1000V( conf i g)# vlan 11N1000V( conf i g- vl an) # name vMotion/StorageN1000V( conf i g- vl an) # vlan 12N1000V( conf i g- vl an) # name Control
N1000V( conf i g- vl an) #vlan 13
N1000V( conf i g- vl an) # name PacketN1000V( conf i g- vl an) # vlan 14N1000V( conf i g- vl an) # name ProductionN1000V( conf i g- vl an) # exit
Note In NX-OS you must explicitly create VLANs. Simply putting a port into a VLAN that
does not exist will not create the VLAN for you. VLAN naming is optional.
5. Verify your configuration.
N1000V( conf i g)# show vlan
VLAN Name St at us Por t s- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -1 def aul t act i ve11 vMot i on/ St orage act i ve12 Cont r ol act i ve13 Packet act i ve14 Product i on act i ve
VLAN Type- - - - - - - - -
1 enet11 enet12 enet13 enet14 enet
Remot e SPAN VLANs- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Pr i mary Secondar y Type Port s- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Activity VerificationYou have completed this task when you attain these results:
Changed the hostname of the VSM and noted the change pushed to vCenter
Created and named the required VLANs on the VSM
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
110/274
Lab 3: Install and Configure the Cisco Nexus 1000V VEM
L3-6 Global Knowledge Training LLC
Task 2: Create an Uplink Port Profi leIn this task, you will create a type Ethernet port profile, which will be applied on the
physical uplink interface NICs on the ESXi hosts. You will also create an NX-OS CLI
alias.
In vCenter, physical NICs are referred to as vmnics. For example, the first NIC on the
server will be labeled vmnic0.
Activity Procedure
Complete these steps:
6. Return to the Putty SSH session to your VSM at IP address 10.0.1.200.
7. Create an uplink system port profile.
N1000V( conf i g)#port-profile type ethernet Host-UplinksN1000V( conf i g- port - pr of ) # description Uplinks from ESXi hosts to switchN1000V( conf i g- port - pr of ) # vmware port-group VMNIC-UplinksN1000V( conf i g- port - pr of ) # switchport mode trunkN1000V( conf i g- port - pr of ) # switchport trunk allowed vlan 1,11-14N1000V( conf i g- port - pr of ) # no shutdownN1000V( conf i g- port - pr of ) # system vlan 1, 12-13N1000V( conf i g- port - pr of ) # state enabledN1000V( conf i g- port - pr of ) # exit
Note The vmware port-groupcommand allows you to present a different port group
name to vCenter. If you type the command vmware port-groupwith no name, the
name of the port profile will be pushed to vCenter instead (i.e. Host-Uplinks). Thevmware port-groupcommand is required, but an alternate name is not.
Note The system vlancommand is crucial to understand and configure. System VLANs
behave differently than other VLANs in that they will always remain in a forwarding
state. Systems VLANs will forward traffic even before a VEM connects to the VSM.
System VLANs need to forward traffic in order for the VEM and VSM to
communicate, and must therefore be added to any port profile that will be applied to
uplinks that carry system VLAN traffic.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
111/274
Lab 3: Install and Configure the Cisco Nexus 1000V VEM
Global Knowledge Training LLC L3-7
8. Create a CLI alias to ease saving your configuration.
Note IOS devices traditionally supported the write memorycommand to commit running-
config to startup-config. NX-OS does not support the write memorycommand. NX-
OS uses copy run start. This can be shortened to an alias of your choosing, or wrif
you are feeling nostalgic.
N1000V( conf i g)# cli alias name wr copy running-config startup-config
9. Save your VSM configuration using your CLI alias.
N1000V( conf i g)# wr[ ########################################] 100%
10. Note the port profile configuration was pushed to vCenter when you entered the stateenabledcommand.
For individual use only; may not be reprinted, reused, or distributed without the express written consent of Global Knowledge.
-
8/9/2019 Implementing the cisco Nexus 1000v DCNX1k v2.0 Lab Guide.pdf
112/274
Lab 3: Install and Configure the Cisco Nexus 1000V VEM
L3-8 Global Knowledge Training LLC
11. Verify the port profile from the NX-OS CLI.
N1000V( conf i g)# show port-profile name Host-Uplinks
por t - pr of i l e Host- Upl i nkst ype: Et her net
descri pt i on: Upl i nks f r om ESXi host s t o swi t chst at us: enabl edmax- por t s: 32mi n- por t s: 1i nher i t :conf i g at t r i but es:
swi t chpor t mode t r unkswi t chport t r unk al l owed vl an 1, 11- 14no shut down
eval uat ed conf i g at t r i but es:swi t chpor t mode t r unkswi t chport t r unk al l owed vl an 1, 11- 14no shut down
assi gned i nt er f aces:
port - gr oup: VMNI C- Upl i nkssyst em vl ans: 1, 12- 13capabi l i t y l 3cont r ol : nocapabi l i t y i scsi - mul t i pat h: nopor t - pr of i l e r ol e: nonepor t - bi ndi ng: stat i c
Note No assigned interfaces are shown because there are no vmnics (physical NICs)
connected to the port profile. So far you have created the port profile and pushed it to
vCenter. From vCenter you will associate a VMs vNIC to a port group, which
attaches a VM to a port profile. This draws a clear line where the network
responsibility ends (create port profiles and push to vCenter), and where the serverteams responsibility begins (associate vNICs or physical vmnics to a port group
the VMware name for a Nexus 1000V