Cisco vwlc on Microsoft Hyper-V Deployment Guide

Transcription

1 Cisco vwlc on Microsoft Hyper-V Deployment Guide Introduction 2 Advantages of the vwlc 2 Hardware Requirement 2 Download Cisco Virtual Wireless LAN Controller 2 Prerequisite 5 HYPER-V Requirement 5 Product Overview 5 Deploying vwlc on Hyper-V 6 Using Windows PowerShell 27

2 Revised: July 19, 2017, Introduction With release 8.4 and above, we are introducing vwlc support for Microsoft Hyper-V. The focus of this deployment guide is to provide guidance on deploying vwlc on Hyper-V. Prior to release 7.4, Wireless LAN (WLAN) controller software ran on dedicated hardware you were expected to purchase. The Virtual Wireless LAN Controller (vwlc) runs on general hardware under an industry standard virtualization infrastructure. The vwlc is ideal for small and mid-size deployments with a virtual infrastructure and require an on-premises controller. Distributed branch environments can also benefit with a centralized virtual controller with branches requiring up to 3000 access points.. vwlcs are not a replacement of shipping hardware controllers. The function and features of the vwlc offer deployment advantages and benefits of controller services where data centers with virtualization infrastructure exist or are considered. Advantages of the vwlc Flexibility in hardware selection based on your requirements. Reduced cost, space requirements, and other overheads since multiple boxes can be replaced with single hardware running multiple instances of virtual appliances. Hardware Requirement Virtual Wireless LAN Controller Version 8.2 and above Settings Minimum Number of vcpus Minimum Memory Required Storage Minimum Number of VMNICs Maximum Access Points Maximum Clients Support Upgrade to Small* Upgrade to Large* Small 1 2 GB 8 GB Yes No Large 2 8 GB 8 GB No Yes * Upgrades are only supported on the same platform. Download Cisco Virtual Wireless LAN Controller Download the latest 8.x software from: 2

3 For software release 8.x, virtual wireless controllers will be offered in 2 types of deployment, SMALL or LARGE, in *aes (software upgrade) or *.ova (VMware) or *.iso (KVM/Hyper-V) format. Refer to the HW requirement needed to support the target deployment. Software upgrade is *.aes format. To upgrade existing vwlc, use the *.aes software and go through the normal upgrade process of WLCs. 3

4 Note vwlc upgrade supports only of the same type (e.g. Small to Small, Large to Large). Mixed is not supported (e.g. Small to Large, or Large to Small). For installing NEW virtual wireless controllers on VMware, use *.ova. For installing NEW virtual wireless controllers on Hyper-V and KVM, use *.iso. 4

5 Prerequisite Before attempting to deploy the Cisco vwlc on HYPER-V, the following prerequisites apply: You must have Hyper-V running on Microsoft 2012 Servers or higher, with a virtual switch already created. An SSH client (for example, Putty on Windows or Terminal on Macintosh) is required to access the Cisco vwlc console. Browsers such as Chrome, Firefox are recommended to access the Cisco vwlc web UI. Determine the type that you want to deploy for the Cisco vwlc. See the next section for more information. HYPER-V Requirement Hyper-V requirement is based on vwlc scale. Small vwlc 200 access points 6000 clients Large vwlc 3000 access points 32,000 clients The following table lists Microsoft Hyper-V virtual machine requirements. Requirement Type Minimum Requirements CPU Clock speed: 2.0 GHz or faster Number of cores: Small--1 vcpu Large 2 vcpu Memory Hard Disks NIC Hypervisor Host Minimum 8GB or higher Small 2 GB Large 8 GB Host 100GB or higher vwlc Small or Large 8 GB 2 GB NIC interfaces required Hyper-V (Microsoft Servers 2012 and above) Product Overview The Cisco Virtual Wireless LAN Controller (vwlc) is available with two types of software images: small scale image (supports up to 200 access points and 6000 clients) and large scale image (supports up to 3000 access points and clients). 5

6 vwlc Data Sheet: vwlc Deployment Guide: html FlexConnect Feature Matrix: technote-wlc-00.html?referring_site=RE&pos=2&page= configuration/guide/cg/cg_flexconnect.html Enterprise Mobility 8.x Design Guide - FlexConnect: Enterprise_Mobility_8-1_Deployment_Guide/ch7_HREA.html Information about Microsoft Hyper-V: Information about Windows PowerShell: Video demonstration of how to deploy vwlc on Hyper-V: Deploying vwlc on Hyper-V To deploy vwlc on Hyper-V, follow the procedure below: Procedure Step 1 Download the appropriate ISO image from CCO (or within beta, download from the beta file forum.) 6

7 Step 2 Step 3 Save it to a server s local file folder. Start Hyper-V Manager. 7

8 Step 4 In the Actions pane, click New > Virtual Machine. 8

9 Step 5 Click Next to Specify Name and Location. 9

10 Step 6 For generation of vwlc, accept Generation 1 as default. 10

11 Step 7 Assign proper memory (see small or large requirement). 11

12 Step 8 We can skip Network connection config for later, as we are required to manually add a second vnic. 12

13 Step 9 Create the virtual disk, assign 8GB as the size for small or large. 13

14 Step 10 At the Installation option, select the default Install an operating system later. 14

15 Step 11 Click Finish at the Summary page to create your vwlc. 15

16 Step 12 Once the vwlc is created, select the vwlc > Actions > Settings. 16

17 Step 13 Select Add Hardware > Network Adapter > Add. This will create the 2nd vnic that will be the management interfact of the vwlc. 17

18 Step 14 Once the 2nd Network Adapter is added, assign this vnic to the proper vswitch. In this example, the vswitch is assigned to the server s physical connection to our network switch. Confirm selection > click Apply. 18

19 Step 15 Navigate to the DVD Drive within the Hardware pane, select Image file > Browse > locate your vwlc_image.iso > click Open. 19

20 Step 16 Step 17 Click OK to commit and save changes to virtual machine configuration. From the Actions pane, click > Connect > Start to power on the vwlc. 20

21 Step 18 Upon power start, you will see the screen Cisco WNBU Installation. System will automatically go through install process until completion. Step 19 Upon completion, vwlc will reboot. Turn off vwlc at this point. Note vwlc will try to boot with CD iso image, we need to disable CD boot to continue. 21

22 Step 20 Go to vwlc settings > CD Drive > select 'None' for Media, so it does not attempt to boot from ISO on power up. Click OK to save. 22

23 Step 21 Turn on vwlc machine, and press any key at the load prompt to access console to configure for the first time. Note It is normal behavior of vwlc on power up without direct virtual console (ssh and HTTP/s only) unless an admin manually interrupt at boot to access terminal. 23

24 Step 22 Once vwlc fully boots, it will initiate controller provisioning. 24

25 Step 23 Step 24 vwlc will initiate day0 WLAN Express setup, or override for CLI Wizard configuration. Proceed with basic setup (admin user, credentials, Management interface, NTP etc.) before accessing the vwlc. Note For guidance on using the WLAN Express setup go to 8-0/configuration-guide/b_cg80/b_cg80_chapter_010.html Once configured, test network ping for connectivity. You can access the vwlc GUI at this point. 25

26 Step 25 Step 26 Connect to the vwlc web GUI. Go to Management > Software Activation > Licenses > click ap count. Set License Status to Active. Click Set Status. At the EULA prompt, click I Accept. 26

27 Step 27 Step 28 You have completed a deployment of vwlc on Hyper-V. Proceed to join access points, creating WLAN and connect wireless clients. Using Windows PowerShell The Hyper-V module for Windows PowerShell includes many Hyper-V cmdlets to help automate Hyper-V management tasks. There are 2 optional use-cases specific to vwlc that requires using PowerShell. Configuring tagged ports for vwlc Deploying vwlc on Hyper-V using a file/script with ISO image Configure Tagged Ports C:\Users\Administrator>powershell Windows PowerShell Copyright (C) 2014 Microsoft Corporation. All rights reserved. 27

28 Show list of adapters and assignment: Get-VMNetworkAdapter -VMName <vwlc name> Figure 1: Configure Ethernet1 (vwlc data port/management) as Trunk, with Native VLAN id 0 Set-VMNetworkAdapterVlan -VMName vwlc -VMNetworkAdapterName Eth1 -Trunk -AllowedVlanIdList NativeVlanId 0 Configure Ethernet0 (vwlc serial port) as access/untagged Set-VMNetworkAdapterVlan -VMName vwlc -VMNetworkAdapterName Eth0 -Untagged Deploying vwlc on Hyper-V via Script Create a PowerShell script (*.ps1) using a text editor (e.g. Notepad) and save to a file folder. Note A *.ps1 extension is needed to be recognized as a PowerShell script. param($mpsw="vsw9x",$spsw="vsw10x",$name="vwlc",$ram=2gb,$iso="null") $VHD=8GB $VMLocation="C:\HyperV" "" "" "Input parameters are:" "" "Management Port Virtual Switch is : $MPSW" "Service Port virtual Switch is : $SPSW" "Name of the VM is : $Name" "Memory requestd is : $RAM" "Sotware input ISO is : $ISO" "Default media Storage is : $VHD" #Create Storage space for VHD files MD $VMLocation -ErrorAction SilentlyContinune #Create VM switches if not present $TestSwitch = Get-VMSwitch -Name $MPSW -ErrorAction SilentlyContinue if ($TestSwitch.Count -EQ 0){New-VMSwitch -Name $MPSW -SwitchType Private} $TestSwitch = Get-VMSwitch -Name $SPSW -ErrorAction SilentlyContinue if ($TestSwitch.Count -EQ 0){New-VMSwitch -Name $SPSW -SwitchType Private} #remove existing file if any for the current VM Remove-Item $VMLocation\$Name* -recurse $NewVM=New-VM -Name $Name -Path $VMLocation -MemoryStartupBytes 8GB -NewVHDPath $VMLocation\$Name.vhdx -NewVHDSizeBytes ${VHD} -SwitchName $SPSW Rename-VMNetworkAdapter -VMName $Name -Name "Network Adapter" -NewName Eth0 Add-VMNetworkAdapter -VMName $Name -SwitchName $MPSW -Name Eth1 #Set Management port to Trunk Set-VMNetworkAdapterVlan -VMName $Name -VMNetworkAdapterName Eth1 -Trunk -AllowedVlanIdList "1-4000" -NativeVlanId 0 #Set ISO path Set-VMDvdDrive -VMName $Name -Path $ISO #Set boot order Set-VMBios -VMName $Name 28

29 #Boot the VM "Your VM is Starting.. Please enter any key within 15secs on VM console to boot Start-Sleep 5 Start-VM $Name "VM Started" #connect the user to console vmconnect localhost $Name PowerShell cmdlet to invoke script within file location of the script created above. powershell -f <script> -ISO <location\installer iso> -RAM <size 2GB or 8GB> -Name <vmname> -MPSW <name of vsw for Mgmt> -SPSW <name of service port vsw> 29

30 2017 Cisco Systems, Inc. All rights reserved.

31 Americas Headquarters Cisco Systems, Inc. San Jose, CA USA Asia Pacific Headquarters Cisco Systems (USA) Pte. Ltd. Singapore Europe Headquarters Cisco Systems International BV Amsterdam, The Netherlands Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco Website at