Cisco Nexus 1000V For Microsoft Hyper-V Installation And .
Cisco Nexus 1000V for Microsoft Hyper-VInstallation and Upgrade Guide, Release5.2(1)SM3(1.1)First Published: December 19, 2014Last Updated: May 27, 2015Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000800 553-NETS (6387)Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALLSTATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUTWARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THATSHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSEOR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s publicdomain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITHALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUTLIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OFDEALING, USAGE, OR TRADE PRACTICE.IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCOOR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to thisURL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnershiprelationship between Cisco and any other company. (1110R)Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command displayoutput, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers inillustrative content is unintentional and coincidental.Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1) 2014–2015 Cisco Systems, Inc. All rights reserved.
CONTENTSCHAPTER1Installing the Cisco Nexus 1000V1-1Prerequisites for Installing the VSM SoftwareBefore You Begin 1-1Guidelines and Limitations 1-1System Requirements 1-1Hardware Requirements 1-1Software Requirements 1-2VSM NIC OrderingBasic Topology1-11-21-3Installation Workflow1-4Installing the VSM Software 1-6Downloading the Cisco Nexus 1000V Package 1-6Configuring SCVMM and VSM 1-6Installing SCVMM Components 1-7Installing and Configuring the VSM Workflow 1-8Configuring the SCVMM Fabric Workflow 1-12Installing the VSM Certificate 1-16Installing the VSM Certificate Manually 1-16Installing the VSM Certificate Using a Script 1-16PowerShell Scripts for Configuring the SCVMM Fabric Workflow 1-17Preparing the Microsoft Hyper-V Hosts (Optional) 1-20Configuring the MTU with the Cisco Nexus 1000V 1-20VMQ Processor Configuration with the Cisco Nexus 1000V 1-20Changing the RSS Registry 1-21Adding Hosts to a Logical Switch 1-21Connecting the VM Network Adapter to the Logical Switch 1-22CHAPTER2Upgrading the Cisco Nexus 1000V2-1Prerequisites for Upgrading the VSM SoftwareBefore You Begin 2-1Prerequisites 2-1Licensing 2-12-1Prerequisites for Upgrading the VEM Software2-3Upgrade Procedures2-3Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1)iii
ContentsPreparing SCVMM and Windows Server Hosts 2-3Upgrading SCVMM 2012 SP1 to SCVMM 2012 R2Preparing the Cisco Nexus 1000V 2-4Upgrading Windows Server 2012 Hosts to 2012R22-42-4Upgrading the VSM to the Current Release 2-4Software Images 2-5In-Service Software Upgrades on Systems with Dual VSMs 2-5ISSU Process for the Cisco Nexus 1000V 2-6ISSU VSM Switchover 2-6ISSU Command Attributes 2-6Upgrading VSMs Using Kickstart and System Images 2-7Upgrading VSMs in an HA Pair 2-7Upgrading a Standalone VSM 2-9Reregistering the Policy Agent of the Upgraded VSM 2-11Upgrading the Cisco VSEM to the Current Release2-12Upgrading the VEM Software to the Current Release 2-13Upgrade Workflow 2-13Upgrading the VEM Software Using WSUS Server 2-15Downloading the Cisco Nexus 1000V package 2-15Preparing the Windows Server Update Services (WSUS) Server 2-15Preparing the Active Directory 2-17Configuring SCVMM 2-18Checking Compliance and Performing the VEM upgrade 2-18Upgrading the VEM Software Using a Script 2-19Prerequisites 2-19Running the VEM Upgrade Script 2-19Upgrading the VEM Software Manually from Cisco Nexus 1000V Release 5.2(1)SM1(5.2) or Later to5.2(1)SM3(1.1) 2-21Performing Post Upgrade Operations 2-22Changing the Feature Support Level 2-22Prerequisites 2-22Changing the Feature Level Support 2-22Installing the Windows Patch 2-23CHAPTER3Installing a VSM on the Cisco Cloud Services PlatformBefore You Begin 3-1Procedure 3-13-1Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1)iv
CH A P T E R1Installing the Cisco Nexus 1000VPrerequisites for Installing the VSM SoftwareFor information about your software and platform compatibility, see the Cisco Nexus 1000V andMicrosoft Hyper-V Compatibility Information document.Before You BeginEnsure that you have installed and configured the following components on the target setup: Windows Active Directory service. Microsoft System Center Virtual Machine Manager (SCVMM) 2012 R2 UR4 or later. Windows Server 2012 R2 hosts with 3014795 hotfix applied. For more information, seehttp://support.microsoft.com/kb/3014795/en-us. For the hosts that are running the Virtual Ethernet Module (VEM), you should enable the Hyper-Vmodule for Windows PowerShell.Guidelines and LimitationsIt is your responsibility to monitor and install all the relevant patches from Microsoft on the Windowshosts.System RequirementsThis section describes the hardware and software requirements.Hardware RequirementsThe hardware must meet the requirements set by Microsoft to run the Hyper-V role. The Cisco Nexus1000V Virtual Supervisor Module (VSM) requires VMs with the following configuration: 4 GB minimum of hard disk space 4 GB minimum of RAMCisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1)1-1
Chapter 1Installing the Cisco Nexus 1000VVSM NIC Ordering As a best practice, we recommend that you have four network adapters (network interfacecards—NICs) on the host where Microsoft Hyper-V is installed. You can have various combinationsdepending on the hardware that you have. For example, you can have one NIC with four ports orfour NICs with one port each.Software RequirementsTo install and bring up a Cisco Nexus 1000V, you need the following server setup: Microsoft System Center Virtual Machine Manager (SCVMM) 2012 R2 UR4 or later Windows 2012 R2 hosts Active Directory serverTo configure the VSM, you need the following information: VSM IP address. VSM domain ID (1–1023)—This ID is used for high availability (HA). Layer 3 connectivity between a VSM and the hosts that run a VEM is required.– Layer2 mode is not supported.– Layer3 UDP port number 4785.– Communication between the VSM and VEM occurs over UDP port number 4785 that uses theCisco Nexus Control Protocol (CNCP). TCP port 80 is open on the network for communication from the SCVMM to VSM. With the HTTPSprotocol, the TCP port is 443.VSM NIC OrderingThe VSM creates interfaces in an ascending MAC address order of the virtual NIC offered by MicrosoftHyper-V. Currently, Microsoft Hyper V provides no guarantees that this order is the same as displayedat the VSM VM Settings panel. The VSM always uses its first interface as control0 and its secondinterface as mgmt0. The network profiles for these two interfaces might need different VLANs.Therefore, you should verify that the interfaces are selected by the VSM in the same order that aredisplayed in the Settings panel.Enter the following command on the VSM to verify the order of the management and control MACaddresses:Nexus1000V# show interface ----------------------------------------Interface Mac-Address Burn-in ----------------------------------------mgmt0 001d.d8b7.1e61 001d.d8b7.1e61control0 001d.d8b7.1e60 001d.d8b7.1e60If the order is not the same, use the following commands to specify the preferredMAC-to-control0/mgmt0 interface mappings:system internal control-mac XXXX.XXXX.XXXXsystem internal mgmt-mac XXXX.XXXX.XXXXThese commands require that you enter the copy running-config startup-config command afterwardsto make the change persistent and effective after the next VSM reload.Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1)1-2
Chapter 1Installing the Cisco Nexus 1000VBasic Topologyswitch# show system internal interface mac-addressSample output:Interface Preferred MACsh interface mac-address--------- -------------mgmt0 cccc.bbbb.aaaacontrol0 aaaa.bbbb.ccccIf any of the preferred MACs are not available at VSM bootup, the driver picks another interface instead(following MAC ascending order). The system logs an error with a syslog as follows:%KERN-3-SYSTEM MSG: Preferred MAC (aaaa.bbbb.cccc) for control0 not found – kernelBasic TopologyFigure 1-1 displays the basic Hyper-V topology on a Cisco Nexus 1000V VEM.Figure 1-1Basic Topology for the Cisco Nexus 1000VManagement VM ClusterSecondary VSM HostInfra VM HostNICNICNICManagementNICLive MigrationManagementHYPER-VNative SwitchNexus 1000V VSMClusterLive MigrationSQL SCVMMVMVMClusterADServerPrimary VSM HostHYPER-VNative SwitchNICNICNICNICData VM Cluster. Host 64Host 1NoteNICNICNexus 1000V SwitchTeamNICNIC . NIC304068ManagementNICLive MigrationClusterVM1 . VMNThe management NIC is actually on the Microsoft switch. The management VM cluster is for infra VMs.The data VM cluster is for workload VMs. The minimum topology is three servers with four NICs each.Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1)1-3
Chapter 1Installing the Cisco Nexus 1000VInstallation WorkflowFigure 1-1 displays the Cisco Nexus 1000V deployment on two servers with the following networkconfiguration: Management NIC—This network adapter is connected to an external network for the host OSconnectivity. Microsoft virtual switch—The Microsoft virtual switch has one physical network adapter for theVSM connectivity. Two physical network adapters—These adapters are connected to the Cisco Nexus 1000V logicalswitch instance of the Hyper-V host.Installation WorkflowFigure 1-2 displays the Cisco Nexus 1000V installation process on Microsoft SCVMM.Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1)1-4
Chapter 1Installing the Cisco Nexus 1000VInstallation WorkflowFigure 1-2Cisco Nexus 1000V Installation Workflow1. Download CiscoNexus 1000V Package2.1 Install Cisco Provider MSI2.2 Install Cisco Template Files2. Install SCVMM Components2.3 Copy VEM to SCVMM Repository2.4 Copy VSM ISO to SCVMM Library3.1 Create Mocrosoft Switch forVSM Connectivity3. Install and Configure VSM3.2 Install VSM VM using VM Template3.3 Configure VSM4.1 Add Switch Extension Manager(Connect to VSM)4. Configure SCVMM Fabric andVM Network4.2 Create Logical Switch4.3 Create VM Networks5.1 Configure PNIC MTU Settings5. Prepare Hyper-V Hosts5.1 Configure VMQ RSS Settings6. Create Nexus 1000VLogical Switch Instance on hostsManagement PNIC WorkflowNon-MGMT PNIC Workflow6.1.1 Select Host6.2.1 Select Host6.1.2 Select the MGMT PNIC6.2.2 Select the PNICs except MGMT PNIC6.1.3 Create MGMT Host VirtualNetwork Adapter6.2.3 Deploy Logical Switch6.2.4 Add any Remaining PNICsto Logical Switch6.1.4 Deploy Logical Switch6.1.5 Add Remaining PNICs toLogical Switch7. Connect VMs toCisco Nexus 1000V7.2 Connect VM Network Adapterto Logical Switch3040697.1 Select VM Network Adapter7.3 Select VM Network and PortClassification for the Network AdapterCisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1)1-5
Chapter 1Installing the Cisco Nexus 1000VInstalling the VSM SoftwareInstalling the VSM SoftwareTo install the VSM software, perform the following steps:1.Downloading the Cisco Nexus 1000V Package, page 1-6.2.Configuring SCVMM and VSM, page 1-6.3.Installing the VSM Certificate, page 1-16.4.Preparing the Microsoft Hyper-V Hosts (Optional), page 1-20.5.Adding Hosts to a Logical Switch, page 1-21.6.Connecting the VM Network Adapter to the Logical Switch, page 1-22.Downloading the Cisco Nexus 1000V PackageThe Cisco Nexus 1000V for Microsoft Hyper-V package (a zip file) is available at the download URLlocation provided with the software.To download the Cisco Nexus 1000V package, download the Cisco Nexus 1000V package for MicrosoftSystem Center Virtual Machine Manager (SCVMM) 2012 SP1. This package contains the followingfiles: VSM ISO 5.2.1.SM3.1.1.iso) VEM MSI package .SM3.1.1.0.msi) Cisco VSEM Provider MSI EMProvider-5.2.1.SM3.1.10.msi) Kickstart 00V-kickstart.5.2.1.SM3.1.1.bin) System file 5.2.1.SM3.1.1.bin) PNSC-PA bin) WSUS scripts (Nexus1000V.5.2.1.SM3.1.1\WSUS\)– Publish-CiscoUpdate.ps1– Remove-CiscoUpdates.ps1– Get-CiscoUpdates.ps1– Get-MSIDetails.ps1Configuring SCVMM and VSMThis section describes how to install the Cisco Nexus 1000V for Microsoft Hyper-V VSM software andincludes the following topics: Installing SCVMM Components, page 1-7 Installing and Configuring the VSM Workflow, page 1-8 Configuring the SCVMM Fabric Workflow, page 1-12Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1)1-6
Chapter 1Installing the Cisco Nexus 1000VInstalling the VSM SoftwareInstalling SCVMM ComponentsTo install the SCVMM components, perform the following steps:Step 1Install the Cisco Provider MSI.a. Install the Nexus1000V-VSEMProvider-5.2.1.SM3.1.1.0.msi from the Cisco Nexus1000V ziplocation on the SCVMM server in order to establish communication between SCVMM and theCisco Nexus1000V VSM.The MSI installation restarts the SCVMM service.Noteb. Verify that the Cisco Provider is installed properly:Step 2 Open the SCVMM console. Navigate to the Settings Pane. Click Configuration Providers. Verify that the Cisco Nexus 1000V extension is displayed.Install the Cisco VSM template files.After downloading the Cisco Nexus 1000V for Microsoft Hyper-V package, complete the followingsteps to install the VSM template: On the SCVMM server, open the PowerShell console from the SCVMM console. Run the script Register-Nexus1000VVSMTemplate.ps1 from the following 000V-VSMTemplate.This script imports the Cisco VSM template in the SCVMM library. To verify the template, do the following:– Navigate to the Templates tab.– Choose Templates. On the right pane, the Nexus 1000V-VSM-Template is listed.Step 3Copy the VEM to the SCVMM repository.The VEM is an MSI file that needs to be placed in the following location on the SCVMM server:%ALLUSERSPROFILE%\Switch Extension Drivers. For example, C:\ProgramData\SwitchExtension Drivers. SCVMM uses the MSI file during Add host operation.CautionStep 4Do not install the VEM on the SCVMM server. Only copy the file to the location specified.Copy the VSM ISO file. For example, copy Nexus-1000V.5.2.1.SM3.1.1.iso to the SCVMM library inthe following location on SCVMM server: \\VMName\MSSCVMMLibrary. After copying the ISO file,make sure to refresh the SCVMM library so that SCVMM detects the copied ISO.Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1)1-7
Chapter 1Installing the Cisco Nexus 1000VInstalling the VSM SoftwareInstalling and Configuring the VSM WorkflowTo install and configure the VSM workflow, use an existing Microsoft Switch with external connectivityor create a new one, for the VSM connectivity.1.Installing the VSM using a VM Template, page 1-82.Configuring the VSM, page 1-93.Deploying the VSM, page 1-94.Configuring the VSM, page 1-11Installing the VSM using a VM TemplateTo install the VSM using a VM template, perform the following steps:Step 1From the left navigation pane in the SCVMM user interface, click the VMs and Services icon and fromthe top menu bar, choose Create Virtual Machine. The Create Virtual Machine wizard opens.Step 2In the Select Source panel, choose the Use an existing virtual machine, VM template, or virtual harddisk option and click Browse.Step 3Choose the Nexus1000V VSM Template file listed under the Type: VM Template header.Step 4Click OK and click Next.Step 5In the Specify Virtual Machine Identity panel, enter the name of the virtual machine and click Next.Step 6In the Configure Hardware panel, configure the hardware settings for the virtual machine. If you areusing a template, most of the settings have already been configured (For example, the hard drive is setto 4 GB and there are three network adapters). The only item that you have to manually configure is theISO image.Step 7Click Virtual DVD drive below the Bus Configuration header in the center pane.Step 8Click Existing ISO image file and click Browse.Step 9Choose the ISO image from the SCVMM library, click OK, and click Next.Step 10In the Select Destination panel, keep the default settings of Place the virtual machine on a host;Destination: All Hosts and click Next.Step 11After the host is displayed in the Select Host panel, chose it, and click Next.Step 12In the Configure Settings panel, review the settings and click Next.Step 13In the Select Networks panel, choose the virtual switches that are used for the virtual machine. For eachnetwork adapter, select the type of the virtual switch. For example, choose Standard Switch or LogicalSwitch and click Next.Step 14In the Add Properties panel, keep the default settings of the Automatic Actions and click Next.Step 15In the Confirm the Settings panel in the final Summary window, review and confirm the settings.Step 16Click Create to begin the virtual machine creation. A progress bar is displayed in the Job Status columnin the VM window.Step 17After the virtual machine creation is complete, right-click the Name of the virtual machine in theSCVMM user interface and choose Power On.Step 18Right-click the Name of the virtual machine again, click Connect or View, and choose Connect viaConsole.See Table 1-1 for more information about the Cisco Nexus 1000V ISO boot options.Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1)1-8
Chapter 1Installing the Cisco Nexus 1000VInstalling the VSM SoftwareTable 1-1Cisco Nexus 1000V ISO Boot OptionsNoBoot Option1Install the Cisco Nexus1000V and bring up the newimage234If the disk is unformattedInstall the Cisco Nexus1000V and go to the VSHshellInstall the Cisco Nexus1000V only if the disk isunformatted, and bring upthe new imageInstall Cisco Nexus 1000Vonly if the disk isunformatted and go to theVSH shellIf disk is formatted Boot the kickstart image from ISO Boot the kickstart image from ISO Format the disk and copy the imagesfrom ISO to bootflash: Copy the images from ISO tobootflash: Load the system image Load the system image Boot the kickstart image from ISO Boot the kickstart image from ISO Format the disk and copy the imagesfrom ISO to bootflash: Copy the images from ISO tobootflash: Start the VSH shell Start the VSH shell Boot the kickstart image from ISO Boot the kickstart image from ISO Format the disk and copy the imagesfrom ISO to bootflash: Try to load the system image from thedisk with the same name as that in ISO Load the system image If the image is not found, start the VSHshell Boot the kickstart image from ISO Boot the kickstart image from ISO Format the disk and copy the imagesfrom ISO to bootflash: Start the VSH shell Load the system imageConfiguring the VSMAfter installing VSM using a VM template, connect to a VM console and configure the VSM. Werecommend that the VSM is deployed using the template provided by Cisco. After the deployment iscomplete, power on the VSM. The following basic inputs are required for the VSM configuration:Note1.Switch name2.Domain ID3.Management address4.Subnet mask5.Gateway addressMake sure that you eject the virtual ISO image from the CD ROM.Deploying the VSMTo deploy the VSM, perform the following steps:Step 1When the Virtual Machine Viewer window opens, the message “Do you want to format it? (y/n)”appears. Enter Y (yes).Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1)1-9
Chapter 1Installing the Cisco Nexus 1000VInstalling the VSM SoftwareStep 2At the command prompt, when the message “Perform r/w tests (takes very long time) on target disks?(y/n)” appears, enter Y (yes).NoteThe default action is taken if you do not immediately respond to the message prompts.Step 3After the software is copied and the CD-ROM drive is mounted, you are prompted to enter the SystemAdministrator Account Setup. At the Enter the password for “admin”: prompt, enter the password. Atthe Confirm the password for “admin”: prompt, reenter the password.Step 4Enter the HA role at the prompt Enter HA role [standalone/primary/secondary].NoteWe recommend that you create a VSM HA pair. Configure the first VM as the primary VSM andinstall the second VM as the secondary VSM.If you set the HA role as secondary, the following question is displayed at the prompt: Setting HArole to secondary will cause a system reboot. Are you sure (yes/no)?: Enter Yes if you want toset the HA role to Secondary.Step 5At the prompt, enter the domain ID: Enter the domain ID[1-1023]; for example, 199. A domain ID isrequired for the VSMs to communicate with each other. While installing the secondary VSM, enter thesame domain ID that was specified for the primary VSM.Step 6After step 5 for secondary VSM, the message is displayed: saving boot configuration and the systemreloads.Step 7At the prompt, the Basic System Configuration Dialog is displayed. Enter Yes at the prompt.Step 8At the command prompt, the following message is displayed: Create another login account? [yes/no](n). Select No to skip creating another login account.NoteThe defaults are used if you do not change the values.Step 9Enter the switch name; for example, Nexus1000V-Eng.Step 10Press Y for yes when prompted to continue with the out-of-band management configuration.Step 11Enter the Mgmt0 IPv4 address for the VSM; for example, 10.10.10.4.Step 12Enter the Mgmt0 IPv4 netmask; for example, 255.255.255.0.Step 13At the command prompt, the following message is displayed: Configure the default gateway? Enter Yfor yes.Step 14Enter the IPv4 address of the default gateway; for example, 10.10.10.5.Step 15At the command prompt, the following message is displayed: Vem feature level will be set to5.2(1)SM3(1.1). Do you want to reconfigure? (yes/no) [n]: Press Enter at the prompt to enter thedefault value.Step 16Enter n when the following command prompt message is displayed: Configure Advanced Options?(yes/no)[n]:.Step 17The following message is displayed: Would you like to edit the configuration? (yes/no) [n]: PressEnter at the prompt to enter the default value.Step 18Enter y when the following command prompt message is displayed: Use this configuration and saveit? (yes/no) [y]:.Step 19Complete steps 1 to 5 to configure the secondary VSM with an HA role.Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1)1-10
Chapter 1Installing the Cisco Nexus 1000VInstalling the VSM SoftwareStep 20Verify the HA role using the command show system redundancy status on primary and secondaryVSMs.Configuring the VSMAfter completing these steps, you are prompted to log into the VSM. Access the VSM via SSH using theIP address configured in the VSM installation section. The following minimal objects need to be createdon the VSM: Logical network Network segment pool IP pool template Network segment Virtual Ethernet port profile Ethernet port profile Network uplinkTo configure the VSM, perform the following steps:Step 1Enter the configuration mode using the command config t.Step 2Create a logical network using the command nsm logical network name at the prompt to configurethe SCVMM networking fabric; for example, nsm logical network Intranet. Type exit. You can enterany name for the logical network.Step 3Create a network segment pool using the command nsm network segment pool name ; for example,nsm network segment pool IntranetSJ.Step 4Associate the network segment pool to the logical network using the command member-oflogical-network name ; for example, member-of logical-network Intranet. Type exit.Step 5Create an IP pool template using the command nsm ip pool template name ; for example, nsm ippool template pool10.Step 6Configure the IP address range and network IP address range using the commands, for example, ipaddress 30.0.0.2 30.0.0.100 and network 30.0.0.2 255.255.255.0 .Type exit.Step 7Create a network segment using the command nsm network segment name ; for example, nsmnetwork segment VMNetworkA.Step 8Create a VLAN inside the network segment using the command switchport access vlan number ; forexample, switchport access vlan 100.Step 9Associate the network segment pool to the network segment using the command member-of networksegment pool name ; for example, member-of network segment pool IntranetSJ.Step 10(Optional) Import the IP pool template to the network segment. Specify the IP subnet using thecommands ipsubnet [CIDRnotation] and ip pool import template [name]. For example:ipsubnet 30.30.30.0/24;ip pool import template pool10NoteThe IP subnet should be the same as the network specified in the ip pool template command.Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1)1-11
Chapter 1Installing the Cisco Nexus 1000VInstalling the VSM SoftwareStep 11Publish the network segment using the command publish network segment name ; for example,publish network segment VMNetworkA. Type exit.Step 12Create a virtual Ethernet port profile using the command port-profile type vethernet name ; forexample, port-profile type vethernet Veth-policy.Step 13Enter the no shutdown command to keep the system in a power-on state. Enter state enabled at theprompt.Step 14Publish the port profile using the command publish port-profile and type exit. The port profile isimported for publishing the network uplink.Step 15Create a virtual Ethernet port profile using the command port-profile type ethernet name ; forexample, port-profile type ethernet eth-pp-policy.Step 16Enter the no shutdown command to keep the system in a power-on state. Enter state enabled at theprompt.Step 17Create a network uplink using the command nsm network uplink NexusUplink.Step 18Associate the network segment pool using the command allow network segment pool IntranetSJ; forexample, allow network segment pool IntranetSJ.Step 19Import the port profile that was created earlier using the command import port-profile name ; forexample, import port-profile eth-pp-policy.Step 20Publish the network uplink using the command publish network uplink name ; for example, publishnetwork uplink NexusUplink. Type exit.Step 21Copy the running configuration to the start-up configuration using the command copy running-configstartup-config. The following message is displayed in the window: Copy complete, now saving to disk(please wait)Step 22Enter the command show running-config to verify the configuration.NoteThe setup script configures the VSM to function in L3 control mode. L2 control mode is not supportedwith Cisco Nexus 1000V for Microsoft Hyper-V. When configuring L3 control with Microsoft Hyper-V,you do not need to create a port profile with L3 control.Configuring the SCVMM Fabric WorkflowNoteThe entire workflow to configure the SCVMM fabric can also be performed using scripts. For moreinformation, see PowerShell Scripts for Configuring the SCVMM Fabric Workflow, page 1-17.To install and configure the VSM workflow, create a Microsoft switch for VSM connectivity and thenperform the following steps:1.Connecting SCVMM to VSM, page 1-12.2.Creating a Logical Switch in SCVMM, page 1-14.3.Configuring the VM Network, page 1-15.Connecting SCVMM to VSMOnce the VSM is up, configure the SCVMM networking fabric for the Cisco Nexus 1000V.Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1)1-12
Chapter 1Installing the Cisco Nexus 1000VInstalling the VSM SoftwareNoteCheck and turn off the proxy server settings for your LAN in the Internet Options settings window ofInternet Explorer before proceeding to the next steps.Connecting SCVMM 2012-R2 to VSMTo retrieve the objects from the VSM to SCVMM 2012 R2, perform the following steps:.Step 1When the VSM is up, log in to the VSM using SSH and the IP addres
Contents iv Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide, Release 5.2(1)SM3(1.1) Preparing SCVMM and Windows Server Hosts 2-3 Upgrading SCVMM 2012 SP1 to SCVMM 2012 R2 2-4 Preparing the Cisco Nexus 1000V 2-4 Upgrading Windows Server 2012 Hosts to 2012R2 2-4 Upgrading the VSM to the Current Release 2-4 Software Images 2-5 In-Service Software
Cisco Nexus 1000V Cisco Nexus 1010 Cisco Nexus 4000 Cisco MDS 9100 Series Cisco Nexus 5000 Cisco Nexus 2000 Cisco Nexus 6000 Cisco MDS 9250i Multiservice Switch Cisco MDS 9700 Series Cisco Nexus 7000/7700 Cisco Nexus 3500 and 3000 CISCO NX-OS: From Hypervisor to Core CISCO DCNM: Single
Cisco Nexus 3172TQ, Cisco Nexus 31108TC-V, Cisco Nexus 92348GC-X, Dell S4148T-ON Access or Leaf Switches Cisco Nexus 3132QX, Cisco Nexus 3164Q, Cisco Nexus 93180YC-EX, Cisco Nexus 93180YC-FX, Cisco Nexus 93240YC-FX2, Cisco Nexus N93360YC-FX2, Dell S5048F-ON, Dell S5248F-ON, ‡Dell S5296F-ON , Dell S5224F-ON ‡, Dell S4148F-ON Aggregation or Spine
Cisco Nexus Virtualized Data Center Components Benefits of using Cisco MDS for VDI SAN infrastructure Cisco UCS Overview . – Installing anzzd Configuring the Nexus 1010 Nexus 1000v Port Profile Configuration Configure Nexus 1000V and 1000V Port Profile Nexus 1000v Port Profile Configuration Technical Training
The Cisco Nexus 2000 Series Fabric Extenders behave like remote line cards for a parent Cisco Nexus 5000, Nexus 6000, or Nexus 7000 Series Switch. Working in conjunction with Cisco Nexus switches, the Cisco Nexus 2000 Series Fabric Extenders extend the capabilities and benefits offered by the parent Cisco Nexus switch while
Nexus 5K with Integrated VSM ACI VTS UCS 5108 Blade Chassis Storage Database Relational UPS, RPS Nexus 2000 10GE Nexus 5k Nexus 4k Nexus 3k Nexus 2k Nexus 1KV VSM Nexus 1k Layer 3 Nexus 5k Switch Blade Server (color and subdued) Server DNS Server Secure Server Nexus 1010 Fibre Channel Fabric Switch Nexus 7k Telegram Channel
Cisco Nexus 1000V Installation and Upgrade Guide, Release 4.2(1)SV1(5.1) OL-25792-01 Appendix B Installing the Cisco Nexus 1000V Software Using ISO or OVA Files Installing the Software from the ISO Image † The VSM VM requires the following and this pro cedure includes steps for updating these properties:
Cisco Nexus 5548P Switch Cisco Nexus 5548UP Switch The Cisco Nexus 5548UP (Figure 2) is a 1RU 10 Gigabit Ethernet, Fibre Channel, and FCoE switch offering up to 960 Gbps of throughput and up to 48 ports. The switch has 32 unified ports and one expansion slot. Figure 2. Cisco Nexus 5548UP Switch Cisco Nexus 5596UP Switch
the American Board of Radiology (ABR) Core and Certifying examinations administered between January 1 – December 31, 2018. The guide has undergone a few minor changes compared to the 2018 version, which was significantly revised com- pared to earlier versions, reflecting changes in NIS content on the examinations. The primary change in this study guide is the addition of Core Concepts of .
