Introduction

This document provides install guidance for the virtual catalyst 9800 wireless controller with VMware ESXi. The purpose of this document is to:

  • Provide an overview of the virtual deployment options.

  • Provide instructions on configuration and setup of virtual wireless controller.

Supported VMware Versions

  • VMware Virtual Machine version 11, minimum of ESXi 6.0 Update 2.

  • Red hat Enterprise RHEL 7.1 & 7.2, Ubuntu 14.04, 16.04 LTS

C9800-CL Virtual Machine Requirement

Scale and sizing, suggests the following minimum virtual resource requirement:

Model Configuration

Small

Medium

Large

Minimum Number of vCPUs

4

6

10

Minimum CPU Allocation (MHz)

4000

6000

10000

Minimum Memory (GB)

8

16

32

Required Storage (GB)

8

8

8

Virtual NICs*

*3rd NIC is for High Availability

2/(3)*

2/(3)*

2/(3)*

ESXi vNIC

VMXNET3

VMXNET3

VMXNET3

Linux KVM vNIC

OVS

Linux bridge (brctl)

OVS

Linux bridge (brctl)

OVS

Linux bridge (brctl)

NIC Virtualization

Virtio

Virtio

Virtio

Maximum Access Points

1000

3,000

6,000

Maximum Clients Support

10,000

32,000

64,000

vMotion, vNIC teaming, L2 LAG, SRIOV

Not supported

Not supported

Not supported

High Availability

High Availability is supported on the C9800-CL VM hosts using virtual redundant ports, in SSO configuration.

Unsupported VM Operations

The following VMware features and operations are not supported in all versions of the Cisco Catalyst Wireless Controller, but can still be used or performed on non-supported versions at the risk of encountering dropped packets, dropped connections, services, and other error statistics:

  • Distributed Resource Scheduling (DRS)

  • Fault Tolerance

  • Resume

  • Snapshot

  • Suspend

  • vMotion

  • vNIC teaming

  • L2 LAG

  • SRIOV

C9800-CL File Format Options

Cisco C9800-CL deployment OVA Template (OVA)

C9800-CL-universalk9.BLD_V***.ova

Cisco C9800-CL deployment image

C9800-CL-universalk9.BLD_V***.iso

Cisco C9800-CL Upgrade and Patches (bin)

C9800-CL-universalk9.upgrade***.bin

Deploying C9800-CL OVA to the VM using vSphere

You can use the provided OVA file package to deploy the Cisco wireless controller to the VM. The OVA package includes an OVF file that contains a default VM configuration based on a Cisco IOS XE release and the supported hypervisor.

The following apply when deploying the OVA package to the VM:

  • The single OVA package creates a VM with options for 3 types of virtual wireless controllers, small/medium/large. Selecting a profile specifies the required virtual CPU and memory. Hard disk will be the same of 8GB for any wireless controller type. It is not recommended to change the virtual CPU and memory configuration after deployment.

  • When deploying using the OVA template, the VM will bootstrap with three interfaces: one interface is for out of band management, one is for wireless management (usually mapped to a trunk interface on the switch side) and the third one is for HA to connect to the SSO peer.

  • You can monitor the installation process on the virtual VGA console or the console on the virtual serial port. A virtual serial port is optional and can be added after deploying the OVA. At FCS the serial console port is not supported for large scale deployments; in the Appendix A you find how to configure it in case you want to use it.

Deploying C9800-CL OVA to ESXi Host using VSphere Client

VMware ESXi direct provides a direct deployment of the virtual Catalyst wireless controller without bootstrap customization (see vCenter deployment).

Perform the following steps in VMware vSphere Client:

Procedure


Step 1

Log in to the VMware vSphere Client.

Step 2

From the vSphere Client Menu Bar, choose File > Deploy OVF Template.

Step 3

In the OVA Wizard, point the source to the Cisco wireless controller OVA to be deployed. Click Next

Step 4

OVA Template details, click Next.

Step 5

Under Name and Inventory Location, specify the name for the VM and click Next.

Step 6

Under Deployment Configuration, select the desired hardware configuration (AP/Client scale) profile from the drop-down menu and click Next.

Step 7

Under Disk Format, select the disk format option (select default):

Step 8

Configure and map wireless controller management interface - under Network Mapping, allocate one virtual network interface card (vNIC) on the destination network using the drop-down list. By default C9800-CL comes with three network interfaces:

  • GigabitEthernet 1 -> Device Management interface: map it to the out of band management network

  • GigabitEthernet 2 -> Wireless Management interface: map it to your network to reach APs and services. Usually this interface is a trunk to carry multiple vlans.

  • GigabitEthernet 3 -> High Availability interface: map it a separated network for peer to peer communication for SSO

Note 

Do not connect 2 interface to a single subnet as that causes network loop.

Step 9

Click Finish to deploy the OVA.

Step 10

Once the VM is created, select the Cisco Catalyst 9800 Wireless controller VM and Edit Settings.


Mapping C9800-CL Network Interfaces to ESXi VM Network Interfaces

The Cisco C9800 maps the GigabitEthernet network interfaces to the logical virtual network interface card (vNIC) name assigned by the VM. The VM in turn maps the logical vNIC name to a physical MAC address.

When the Cisco C9800 is booted for the first time, the router interfaces are mapped to the logical vNIC interfaces that were added when the VM was created. The figure below shows the relationship between the vNICs and the Cisco C9800 interfaces.

  • GigabitEthernet 1 -> Device Management interface: map it to the out of band management network

  • GigabitEthernet 2 -> Wireless Management interface: map it to your network to reach APs and services. Usually this interface is a trunk to carry multiple vlans

  • GigabitEthernet 3 -> High Availability interface: map it a separated network for peer to peer communication for SSO


Note

Do not connect 2 interface to a single subnet as that causes network loop.


Below shows an example for using the Hypervisor physical port (e.g. vmnic2, connected to a switch trunk), and is mapped to vSwitch0 as intended for the C9800 VM management interface. An optional interface intended for use in redundant HA configuration (e.g. vmnic3) is named RP and mapped to vSwitch3.


Note

If testing 2 x C9800s in the same UCS and using RP ports for HA, it is not necessary to connect the physical RP mapped physical adapters at all. However, if active and standby C9800s are on separate hypervisors, then the RP mapped physical ports need to be connected to the network and is L2 adjacent/reachable to each other.


VSwitch Promiscuous Mode

By default, a hypervisor vswitch is configured to Reject promiscuous mode. If C9800 is using tagged traffic (e.g. management VLAN, AP VLAN, etc.) via management port, promiscuous mode allows the vSwitch to carry tagged traffic. Therefore configure to ‘accept promiscuous mode for the vswitch.

Procedure


Step 1

Under hypervisor > Configuration > Hardware > Networking select vSwitch# being mapped to the C9800 management interface.

Step 2

Select Ports > configuration > vSwitch and click Edit.

Step 3

In Security Tab > Policy Exceptions > set Promiscuous mode = Accept.


Configuring the basic C9800-CL settings

Let’s configure the minimal configuration to then connect to the web GUI interface of C9800-CL and use the DAY 0 guided flow to get the controller fully operational.

At FCS, DAY 0 assumes that the box has two separated virtual interfaces (one for device management and one for wireless management and client traffic) and that the first login happens on the device management (out of band) interface. The wireless management interface is configured via the DAY 0. If you have a different setup and for example you want to use only one interface, please see the next section on how you can skip DAY 0 guided flow and configure the initial settings using CLI.

Connect to the CLI via the VGA console and follow these steps for the basic configuration:

  • Terminate the configuration wizard (this is the general ios CLI wizard and it’s not specific for wireless)

Would you like to enter the initial configuration dialog? [yes/no]: no
Would you like to terminate autoinstall? [yes]:yes
  • Optinally set the hostname:

WLC(config)#hostname C9800
  • Add login credentials using the following command:

C9800(config)#username <name> privilege 15 password <yourpwd>
  • Add an IP address on the device Management interface. The example assumes you have mapped GigabitEthernet 1 to the out of band/device management network during VM bootstrap:

C9800(config)#interface g1
C9800(config-if)#no switchport
C9800(config-if)#ip address 10.58.55.5 255.255.255.0
  • Add the route to the remote network where you want to manage the C9800-CL from

C9800(config)#ip route 10.58.0.0 255.255.0.0 10.58.55.254

Verify that you can ping your management station and then from there just https://<IP of the device management interface>. Use the credentials you have entered earlier. Since the box has never been configured, the web GUI will redirect you to the DAY 0 page. Please see the DAY 0 section later in the document

C9800-CL Day-0 Configuration Setup Wizard

To simplify the bootstrap process of a Catalyst wireless controller, a Day-0 wizard will appear after a virtual instance is deployed, with network connectivity but without any other wireless configuration.

To connect to the DAY 0 GUI, just login to the defined Device Management interface using https.

To login use the username and password credentials given during the C9800 instance creation described in the previous sections.

Once logged in, the user is presented with a simplified configuration flow to set the basic parameters and have the controller fully operational. In the first page, enter the required information:

These are: Deployment mode, Country code, Date and Time, NTP (optional) and AAA Server (optional).

Note how for the VM you can chose standalone or active/standby if you want to configure SSO.

Then enter the wireless Management interface configuration:

Notice that you can only select an interface that is different from the one you used to access the GUI (so you can either select gig 2 or gi3 in this case). You can configure the interface Gigabit 2 by choosing the vlan, the IP address and the default gateway. This will automatically configure the interface as trunk, the SVI interface for wireless management and the default gateway. Click Next

In the next page you can add a WLAN (optional) so that clients can connect. In this example the PSK dialogue is shown:

In the next page the user can set some basic RF parameters and the AP certificate.

A trustpoint is basically a certificate authority who you trust, and it is called a trustpoint because you implicitly trust this authority. A trustpoint certificate is a self-signed certificate, hence the name trustpoint, since it does not rely on the trust of anyone else or other party. A trustpoint is needed for AP to join the C9800-CL and the user can decide to auto generate one during DAY 0, or can toggle the “Generate Certificate” to NO and then it will have to configure its own certificate authority at DAY 1 for APs to join.

Click Summary to review the configuration and then click Finish. The configuration and trustpoint will be pushed to the device and the user will be logged out. The 9800-CL controller will not reboot but it will take about 60s to prompt the user to login again; enter the same credentials:

This time it will skip the DAY 0 page since the box has already an initial configuration, and the user will be redirected to the main Dashboard for DAY 1 configuration.

C9800-CL configuring using CLI: skipping the DAY 0 guided flow

If the user doesn’t want to use two separated virtual interfaces for device management and wireless management, then he/she can configure the day zero configuration via CLI and then access the GUI for DAY 1 configuration.

Follow these steps to configure the c9800 with a wireless management interface and skip the DAY 0. This example assumes that GigabitEthernet 1 is connected to a trunk interface on the switch and you want to configure multiple VLANs and dedicate one for Wireless Management interface.

Procedure


Step 1

Access the CLI via the vga/monitor console of ESXi .

Step 2

Terminate the configuration wizard (this wizard it’s not specific for wireless controller)

Would you like to enter the initial configuration dialog? [yes/no]: no

Would you like to terminate autoinstall? [yes]:yes
Step 3

Optionally set the hostname:

WLC(config)#hostname C9800
Step 4

Enter the config mode and add login credentials using the following command:

C9800(config)#username <name> privilege 15 password <yourpwd>
Step 5

Configure the vlan for wireless management interface.

C9800#conf t
Enter configuration commands, one per line.  End with CNTL/Z.

C9800(config)#vlan 122
C9800(config-vlan)#name wireless_management
Step 6

Configure the SVI for wireless management interface, for example:

C9800(config)#int vlan 122
C9800(config-if)#ip address 172.20.229.21 255.255.255.192
C9800(config-if)#no shutdown
Step 7

Configure the interface gigabit 1 as trunk:

C9800(config-if)#interface GigabitEthernet1   
C9800(config-if)#switchport mode trunk
C9800(config-if)#switchport trunk allowed vlan 122
C9800(config-if)#shut
C9800(config-if)#no shut
Step 8

Configure a default route (or a more specific route) to reach the box:

C9800(config-if)#ip route 0.0.0.0 0.0.0.0 172.20.229.1
Step 9

Disable the wireless network to configure the country code:

C9800(config)#ap dot11 5ghz shutdown 
Disabling the 802.11a network may strand mesh APs.
Are you sure you want to continue? (y/n)[y]: y
C9800(config)#ap dot11 24ghz shutdown 
Disabling the 802.11b network may strand mesh APs.
Are you sure you want to continue? (y/n)[y]: y
Step 10

Configure the AP country domain. This configuration is what will trigger the GUI to skip the DAY 0 flow as the C9800 needs a country code to be operational:


C9800(config)# c9800-10-30(config)#ap country ?
  WORD  Enter the country code (e.g. US,MX,IN) upto a maximum of 20 countries
Step 11

A certificate is needed for the AP to join the virtual C9800. This can be created automatically via the DAY 0 flow or manually using the following commands.

  • Specify the interface to be the wireless management interface

    C9800(config)#wireless management interface vlan 122
  • In exec mode, issue the following command:

    C9800(#wireless config vwlc-ssc key-size 2048 signature-algo sha256 password 0 <pwd> 
    Configuring vWLC-SSC…
    Script is completed
    

    This is a script the automates the whole certificate creation:

  • Verifying Certificate Installation:

    C9800#show wireless management trustpoint
    Trustpoint Name : ewlc-default-tp
    Certificate Info : Available
    Certificate Type : SSC
    Certificate Hash : e55e61b683181ff0999ef317bb5ec7950ab86c9e
    Private key Info : Available
    
Note 

You can skip the certificate/trustpoint configuration but if you do it, APs will not able to join. You would need to go to the GUI and configure it from there by importing the desired certificate.

Verify that you can ping the wireless management interface and then just https://<IP of the device wireless management interface>. Use the credentials you have entered earlier. Since the box has a country code configured, the GUI will skip DAY 0 page and you will get access to the main Dashboard for DAY 1 configuration.


Accessing C9800-CL WebUI

Once the C9800 is reachable successful from the network.

Procedure


Access the C9800 webUI using https://C9800-IP. The username and password will be what you have provided during the OVA installation.

Congratulations, you have installed your virtual C9800.


Deploying the OVA to ESXi 6.0 with vCenter Server

VMware vCenter has similar flow than standalone ESXi, with the exception for the ability to customize/bootstrap virtual wireless controller.

Procedure


Step 1

Log in to the vCenter, choose vSphere Web Client (Flash)

Step 2

Select from Actions > Deploy OVF template.

Step 3

Browse to the OVA file, select the datacenter, click Next.

Step 4

Select the cluster > Host > click Next.

Step 5

Review details of OVF deployment > click Next.

Step 6

Select Configuration (AP/Client scale) profile > click Next.

Step 7

Select the storage > click Next.

Step 8

Map the virtual network interface(s) > click Next.

As mentioned before, vCenter deployment provides a option to customize or bootstrap the Catalyst 9800 wireless controller with hostname, network configuration and login.

Step 9

Go through steps to provide any necessary info using the provided template, click Next.

Note 

Please note that here you need to specify the device management interface, this is the interface you mapped to the out of band management network. This interface is configured as a Layer 3 routed interface with the IP address provided in this step. The network you enter here in step 2.4 is the remote network where you want to manage your c9800-CL from. This will create a static route to that specified network.

Step 10

Finally, review the configuration data, click Next to deploy in vCenter.

Step 11

Select Power on after deployment.


Deploying C9800-CL with ESXi 6.5

At the time of this document, installing .ova file of C9800-CL using GUI does not work. There are issues specific to VMware 6.5 and C9800-CL OVA file deployment in which deployment will fail with a warning displaying "A required disk image was missing." In addition, an error is seen "Failed to deploy VM: postNFCData failed: Cannot POST to non-disk files.” There are two options to install C9800-CL on VMware ESXi 6.5)

  • Installing .iso file of C9800-CL using ESXi embedded GUI (ESXI 6.5 client version 1.29.0 is tested and required)

  • Installing .ova file of C9800-CL using OVF tool

Deploying C9800-CL ISO to ESXi 6.5 Using VMware Embedded GUI

Procedure


Step 1

Copy C9800-CL ISO file into the datastore.

Step 2

If needed, update ESXI 6.5 client version to the minimum version 1.29.0

Step 3

Create a new Virtual machine and choose below suggested OS family/version:

  • Compatibility: ESXi 6.5 virtual machine

  • Guest OS family: Linux

  • Guest OS version: Other 3.x or later Linux (64-bit)

Step 4

Select the datastore for deploying the C9800.

Step 5

Choose CPU/Mem/Hard disk size depending on your deployment requirements, refer to the virtual machine requirement/scale.

Step 6

Ensure Network Adapter Type is VMXNET 3, Device node as IDE controller 0.

Step 7

After ISO installation, walk through the initial setup wizard, configure SVI’s, wireless interface, trustpoint, etc (review previous sections as this will be the same)

Step 8

Finally join and register access points.


Deploying C9800-CL OVA to ESXi 6.5 Using VMware OVF Tool

Procedure


Step 1

Download and Install OVF tool from VMware website, minimum tested version is 4.2.0.

Step 2

Download the OVA file of C9800-CL in a folder

Example:

/users/xyz/C9800/ova-file-on-esxi6.5/
Step 3

Create a file named “.ovftool” (in the folder example above), and modify it with the following content (refer:

$ more .ovftool
acceptAllEulas
datastore=<datastore name>
deploymentOption=<#>CPU-<#>GB  *check VM requirement per scale required
name=prsna-vm
net:GigabitEthernet1=<network name>
prop:com.cisco.vwlc.hostname.1=<C9800 hostname>
Step 4

At this point, your folder must to have 2 files.

$ ls -la
total 1192960
..
-rw-r--r--   1 prasannathakku  staff        156 May 22 14:29 .ovftool
-rw-r--r--   1 prasannathakku  staff  610785280 Apr 25 02:50 vWLC.ova

Step 5

Execute below command from the folder (where you have both ova file and also .ovftool file)

For example:

$/Applications/VMware\ OVF\ Tool/ovftool  ./C9800-CL.ova vi://"root:password"@<Host IP address>
Note 
OVA file that you need to deploy is - C9800-CL
ESXi 6.5 info - vi://"root:<password>"@<Host IP address>”
Execute this cmd from the location where you have ova file and also .ovftool file
Step 6

Access GUI of ESXi and power up related VM that was just installed using the OVF tool.

Step 7

After OVA installation with embedded client, you can browse to the ESXi 6.5 host and see the C9800-CL VM that was installed.

Step 8

Make any changes as required (e.g. network mapping, etc.)

Step 9

Power on the VM, and walk through the initial setup wizard, configure SVI’s, wireless interface, trustpoint, etc (review previous sections as this will be the same).


Deploying Virtual C9800-CL on Linux KVM

The Cisco virtual 9800 Wireless Controller can be deployed in Linux KVM using an ISO file (download from Cisco website), with the support for the following distribution:

  • Linux KVM, Ubuntu, Red Hat, CentOS

This guide will not cover every aspect of Linux or KVM components, only the general set of instructions needed to deploy a virtual wireless controller on KVM.

Virtual C9800 on Linux KVM Scale

Prerequisites before installing KVM

To run KVM, a processor that supports hardware virtualization is required. Intel and AMD both have developed extensionsfor their processors, deemed respectively Intel VT-x (code nameVanderpool) and AMD-V (code name Pacifica).

To see if the processor supports one of these, issue the following command and review the output:

egrep -c '(vmx|svm)' /proc/cpuinfo  

If the result is 0 it means that your CPU doesn't support hardware virtualization.

If 1 or more, then it does - but you still need to make sure that virtualization is enabled in the BIOS.

Required packages for the KVM

The following KVM packages are required for installation:

Qemu-kvm

Qemu-utils

Uml-utilities

Bridge-utils

Socat

Kvm

Libvirt-bin

Virtinst

Ubuntu sample commands to install the packages:

apt-get install qemu-kvm qemu-utils uml-utilities bridge-utils socat
apt-get install kvm libvirt-bin virtinst

Commands to install the packages in RHEL:

yum install kvm libvirt

KVM Networking

Networking options vary within Linux, effectively KVM supports the following:

Linux Bridge

OVS switch

Sample network settings, where br0 and br1 can be mapped to the virtual wireless controller interface(s).

vim /etc/network/interfaces
 
interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
 
 
auto br0
iface br0 inet static
        address 10.104.170.99
        netmask 255.255.255.0
        network 10.104.170.0
        broadcast 10.104.170.255
        #gateway 10.104.170.1
        #up route add default gw 10.104.170.1
        # dns-* options are implemented by the resolvconf package, if installed
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0
        bridge_maxwait 0
        dns-nameservers 72.163.128.140
 
 
auto br1
iface br1 inet static
        address 9.11.124.44
        network 9.11.124.0
        netmask 255.255.255.0
        bridge_ports eth1
        bridge_stp off
        bridge_fd 0
        bridge_maxwait 0

Creating the Cisco C 9800-CL VM Using the virt-manager GUI Tool

Once Linux KVM requirement is met, packages installed, and networking configured, download the ISO from Cisco for use with virt-manager. Virt-manager GUI tool is the easiest method in deploying the virtual 9800 wireless controller. The following examples are based on Ubuntu/Gnome as a desktop environment.

Procedure


Step 1

Start virtual machine manager > Create a new virtual machine. Select Local install media (ISO image..) > click Forward.

Step 2

Browse and select the Catalyst 9800 ISO file.

Step 3

Using the AP/Client scale guide, set CPU and memory requirement. For example, 4 CPUs/8G RAM is set for small/1K AP/6K clients support. Click Forward.

Step 4

Create a disk of 8GiB (standard for all scale). Click Forward.

Step 5

Provide a name for the VM and select (IMPORTANT) ‘Customize configuration before install’. Click Forward.

The default is a single interface at time of VM creation. This can be used as any of the functional virtual 9800 interface, for example, the wireless management interface. However, if an additional interface (or serial port) is needed, use the ‘Add New Virtual Hardware’ tool.
Step 6

Add New vHardware > Network interface. Map each of the NIC to the target bridge interface defined in Linux network configuration.

Step 7

For each NIC, select Device model = virtio. Click Finish.

Step 8

Virtual serial console also exists for KVM, simply add virtual hardware, select Serial, Host=127.0.0.1(local host), Port# (user-defined), Use Telnet (checked). Click Finish.

Below is an example of console using telnet to the KVM hypervisor @ user defined port.

Step 9

Next, click ‘Begin Installation’. VM will boot and progress through the installation process.

Step 10

Progress can be monitored through the KVM VM console.

Step 11

Configure the wireless controller using the console command line.

Step 12

Open the web browser and connect to the C9800 webUI using https://C9800-IP.


Appendix A:

Adding Virtual Serial Port

Adding a virtual serial port allows an admin to connect to the virtual wireless controller similar to accessing a physical appliance’s serial console.

Procedure


Step 1

Next add a new hardware, select serial port for console access to the wireless controller.

Step 2

For Port Type, select Connect through Network, as we will telnet to ESXi network address and custom port assignment.

Step 3

For Network Backing, select Server and enter in the Port URI:telnet://<ESXi IP address>:<port>

Step 4

Complete adding the serial port, you will see the serial port display in the hardware list.

Step 5

Select Power on after deployment to automatically power on the VM.

Step 6

IMPORTANT, For the first boot after creating your VM, use vSphere client console to view and select boot option. Option will be VGA or Serial (recommended).

Step 7

Select ‘vWLC Serial Console’, this will be a one-time action.

Step 8

If above ‘VGA Console’ was selected, to enable console via serial, perform the command within VI Client console: e.g.

  1. C9800>enable

  2. C9800#config terminal

  3. C9800(config)#platform console serial

  4. Mode will be available on next reload

Step 9

Once the C9800 has booted with serial console option selected (or platform serial mode enabled), console to your C9800 by telnet to your ESXi and assigned port.

The following configuration example was created:

version 16.8
!
platform console serial
!
hostname C9800
!
username admin privilege 15 secret 5 $1$2W5l$ufMvehFW/3MAonJwjLODb.
!
!
interface GigabitEthernet1
 negotiation auto
 no mop enabled
 no mop sysid
!
interface Vlan1
 no ip address
 shutdown
 no mop enabled
 no mop sysid

Enabling ESXi VM Serial Security

By default, ESXi (6.x) security profile does not have VM serial port mode enabled and is required for serial console to C9800 virtual machine (if configured).

Go to the ESXi server > Configuration > Software > Security Profile > Firewall > Properties. Enable VM serial port connected over network.

C9800 CLI References

C9800#show platform software vnic-if interface-mapping
-------------------------------------------------------------
 Interface Name        Driver Name         Mac Addr
-------------------------------------------------------------
 GigabitEthernet1       net_vmxnet3        0050.5693.1d6e 


C9800 #show int gig 1
GigabitEthernet1 is up, line protocol is up 
  Hardware is CSR vNIC, address is 0050.5693.1d6e (bia 0050.5693.1d6e)

C9800 #show ip int brief
Interface              IP-Address      OK? Method Status                Protocol
GigabitEthernet1       unassigned      YES unset  up                    up      
Capwap1                unassigned      YES unset  up                    up      
Capwap2                unassigned      YES unset  up                    up      
Capwap3                unassigned      YES unset  up                    up      
Vlan1                  unassigned      YES NVRAM  administratively down down    
Vlan10                 10.10.1.2       YES NVRAM  up                    up      
Vlan118                172.20.228.41   YES NVRAM  up                    up      

Deploying to ESXi 6.5 - OVF Command References

Through the VCenter 6.5

usr/bin/ovftool --acceptAllEulas --X:injectOvfEnv --overwrite --powerOn -ds="datastore1" -dm=thin --deploymentOption="4CPU-8GB " 
-n="<ewlc_vm_name>" --net:"GigabitEthernet1"="<network name>" --net:"GigabitEthernet2"="<network name>" 
--net:"GigabitEthernet3"="<network name>" --prop:com.cisco.vwlc.hostname.1="<hostname>" --prop:com.cisco.vwlc.login-
username.1="<username>" --prop:com.cisco.vwlc.login-password.1="<password>" --prop:com.cisco.vwlc.privilege-
password.1="<privileged_password>"   ./<path to 
ovafile>  <vcenter_username>:<vcenter_password>@<vcenter_server_ip>?ip=<vhost_server_ip>
Example”
 
usr/bin/ovftool --acceptAllEulas --X:injectOvfEnv --overwrite --powerOn -ds="datastore1" -dm=thin --deploymentOption="4CPU-
8GB" -n="ewlc_single_cli" --net:"GigabitEthernet1"="Dummy" --net:"GigabitEthernet2"="Dummy" --
net:"GigabitEthernet3"="Dummy" --prop:com.cisco.vwlc.hostname.1="ewlc_single_cli-host" --prop:com.cisco.vwlc.login-
username.1="cisco" --prop:com.cisco.vwlc.login-password.1="cisco" --prop:com.cisco.vwlc.privilege-password.1="cisco" 
./wlc9500C-universalk9.2018-10-04_17.22_subgadam-vga.ova vi://administrator@vsphere.local:Cisco@123@10.105.203.182?ip=10.104.170.96
Deploying Directly in Vhost
usr/bin/ovftool --acceptAllEulas --X:injectOvfEnv --overwrite --powerOn -ds="datastore1" -dm=thin --deploymentOption="" -
n="<ewlc_vm_name>" --net:"GigabitEthernet1"="<network name>" --net:"GigabitEthernet2"="<network name>" --
net:"GigabitEthernet3"="<network name>" --prop:com.cisco.vwlc.hostname.1="<hostname>" --prop:com.cisco.vwlc.login-
username.1="<username>" --prop:com.cisco.vwlc.login-password.1="<password>" --prop:com.cisco.vwlc.privilege-
password.1="<privileged_password>"  ./<path to ova file>  <vhost_username>:<vhost_password>@<vhost_server_ip>
 
 usr/bin/ovftool --acceptAllEulas --X:injectOvfEnv --overwrite --powerOn -ds="datastore1" -dm=thin --deploymentOption="4CPU-
8GB" -n="ewlc_single_cli" --net:"GigabitEthernet1"="Dummy" --
net:"GigabitEthernet2"="Dummy" --net:"GigabitEthernet3"="Dummy" --prop:com.cisco.vwlc.hostname.1="ewlc_single_cli-host" --prop:com.cisco.vwlc.login-
username.1="cisco" --prop:com.cisco.vwlc.login-password.1="cisco" --prop:com.cisco.vwlc.privilege-password.1="cisco" 
./wlc9500C-universalk9.2018-10-04_17.22_subgadam-vga.ova vi://root:Cisco@123@10.104.170.96