Instruction/ maintenance manual of the product LAIRCTVM5K9 Cisco Systems
Go to page of 33
Cisco Virtual Wireless Controller Deployment Guide Document ID: 113677 Introduction Prerequisites Virtual Controller Support Virtual WLAN Controller Unsupported Features Single Virtual Controller Reso.
VMware benefits with the vWLC: vSphere : A virtualization infrastructure package from VMware, which includes ESX/ESXi hypervisor, vMotion, DRS, HA, Fault Tolerance, vSphere Distributed Switch, and more.
Suggested Hardware Recommendations for Hosting Cisco Virtual Controllers UCS R210−2121605W Rack Mount Server (2 RU): 2 * Intel Xeon CPU X5670 @ 2.93 GHz ♦ 16 G memory ♦ • IBM x3550 M3 Server: 2 * Intel Xeon 5600 series processors with 4 cores each and each core capable of doing hyper threading which gives you 16 CPUs in total @3.
and local access to Internet). Conventions Refer to Cisco Technical Tips Conventions for more information on document conventions. Release Notes Cisco Unified Wireless Network (CUWN) 7.3 Release Notes contain important information about this release. Log in to Cisco.
Virtual Controller Virtual Interfaces Management Interface • Virtual Interface • Dynamic Interface • AP Manager Interface • Switch Interface Configuration Connected to UCS Server This section provides a sample configuration of the Cisco Catalyst interface connection to the ESXi server for the virtual switch as trunk interface.
interface GigabitEthernet1/1/3 description ESXi Trunk switchport trunk encapsulation dot1q switchport mode trunk end Complete these steps: Create two separate virtual switches in order to map to the virtual controller Service and Data Port. Go to ESX > Configuration > Networking , and click Add Networking .
Click Next . 7. Here, you see vSwitch1 is created for vWLC Service Port. Click Add Networking in order to repeat for the Data Port. 8. For the new vSwitch, select the physical NIC(s) connected on a trunk port if there are multiple NICs / portgroup assigned to an etherchannel on the switch.
Click Next until you complete the steps to add the vSwitch. 14. VMware Promiscuous Mode Definition Promiscuous mode is a security policy which can be defined at the virtual switch or portgroup level in vSphere ESX/ESXi.
In the Properties window, select the Security tab. 3. Check the box for Promiscuous Mode , choose Accept from the drop−down list, and click OK . 4. Confirm the change, and click Close .
The virtual controller software is posted as an .ovf package in the Cisco software center. You can download the .ova/.ovf package and install to any other virtual application.
Provide a name for the vWLC or accept the default, and click Next . 10. Accept the default Thick Provision Lazy Zeroed setting, and click Next . 11. Accept the Network Mapping default, and click Next .
Confirm the Deployment settings, and click Finish in order to begin installation. 13. Click Close when Deployment is complete. 14. Two important things to note regarding upgrading virtual controllers: The OVA image is needed only for first time installation.
Select Network adapter 1 to vWLC Service Port (vSwitch created in ESX networking). 2. Map Network adapter 2 to vWLC Data Port . 3. Confirm the correct mapping. 4. Virtual Controller Console Port The console port gives access to the console prompt of the WLC.
Physical Serial Port on the Host : The vWLCs virtual serial port is mapped to the hardware serial port on the server. This option is limited to the number of physical serial port(s) on the host. If in a multi−tenant vWLC scenario, this may not be ideal.
Click Next in order to review the Options, and click Finish . 5. Click OK in order to complete the configured settings. In order to enable for the serial via network, ESX must be configured to allow for such requests. 6. Navigate to the ESX, click the Configuration tab, go to Software > Security Profile , and click on Properties .
In the Firewall Properties window, select VM serial port connected to vSPC , and click OK . 8. Start up the vWLC Complete these steps: Start the vWLC, and select the console in order to observe the first−time installation process.
Monitor the progress until the VM console shows that the vWLC has restarted (this is automatic). 2. Open a Telnet session to the vWLC as shown here: 3.
Note: Only one mode of console can be operational at any time, such as a VM console (by key−interrupt at startup) or serial console (physical/network). It is not possible to maintain both at the same time. Continue to wait until the vWLC has come online fully and prompts you to start the configuration tool wizard.
configuration, which may result in APs not joining in the process. Complete the configuration and allow the vWLC to reset. 8. It is suggested that you ping the vWLC management interface in order to ensure that it has come online. Log in to the vWLC. 9.
Initially, there are 0 (zero) Access Points Supported. Enable the evaluation license in order to allow the AP to join. 12. Go to Management > Software Activation > Licenses .
Click OK , and Accept the EULA in order to continue. 14. Click OK , and reset the vWLC in order for the evaluation license to take effect. 15. Reboot the vWLC.
Log back in to the vWLC, and note that the 200 APs are now supported with the evaluation license enabled. 17. Connect an AP, and monitor for the join message to occur. 18. From the browser, go to WIRELESS and confirm that the AP has joined. 19. Click the AP, and change the AP Mode to FlexConnect .
It may be useful to consider using the autoconvert function of the controller (for example, any mode AP joining the vWLC will be converted automatically to FlexConnect). Issue this command in order to implement: (Cisco Controller) > config ap autoconvert flexconnect enable 21.
In Device Work Center, click Add Device . 3. Enter the IP Address and SNMP Community string (Read/Write). By default, the SNMP RW for the controller is Private.
Cisco Prime Infrastructure will discover and synchronize with the virtual controller. Click refresh in order to update the screen. 5. When the virtual controller is discovered, it is listed as Managed and Reachable (shown in green). Add any other virtual controller(s) at this point, if available.
Navigate to Home for a Summary view (in Lifecycle Theme) of the devices being managed. 8. For the remainder of this guide, the Classic Theme is used to perform similar task of adding the virtual controller, as well as updating the system image. Go to and select Switch to Classic Theme .
Enter the IP Address, Read/Write SNMP Community string, and click Add . 12. Cisco Prime Infrastructure will display this notification: 13. Go to Configure > Controllers . The virtual controller will be listed as Reachable once it has been successfully discovered and added.
Upgrade the Virtual Controller In the early steps of installation, the Cisco Virtual Controller initially required an OVA file for new virtual appliance creation. However, maintaining virtual controller features and software upgrades require a common AES file downloadable from the Cisco website.
Click Save and Reboot . 4. Cisco Prime Infrastructure can also be useful for upgrading one virtual controller or many virtual controllers at the same time. Go to Configure > Controllers . Select (check box) one or more virtual controllers. Select Download Software (TFTP) from the command drop−down list.
This screen is an example of the AES image being transferred to the virtual controllers: 7. Cisco Prime Infrastructure will update the status until the software has transferred successfully. 8. Similar to the experience directly from the controller, a reboot is required when the transfer is complete.
Cisco Prime Infrastructure will prompt for reboot parameters such as save configuration, and so forth. Click OK . 10. Cisco Prime Infrastructure will notify the administrator that the virtual controllers are being rebooted. 11. When complete, Cisco Prime Infrastructure will provide the results of the process.
The hash validation, which is an extra authorization step, will be performed only if the AP is joining a virtual controller. There will be a knob to turn on/off hash key validation.
The AP may have an older SSC hash, either from an old installation or joining other controllers. It is possible to configure the WLC to not validate SSC, allow APs to join the vWLC, then re−enabling the validation again.
An important point after buying a device Cisco Systems LAIRCTVM5K9 (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought Cisco Systems LAIRCTVM5K9 yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data Cisco Systems LAIRCTVM5K9 - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, Cisco Systems LAIRCTVM5K9 you will learn all the available features of the product, as well as information on its operation. The information that you get Cisco Systems LAIRCTVM5K9 will certainly help you make a decision on the purchase.
If you already are a holder of Cisco Systems LAIRCTVM5K9, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime Cisco Systems LAIRCTVM5K9.
However, one of the most important roles played by the user manual is to help in solving problems with Cisco Systems LAIRCTVM5K9. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device Cisco Systems LAIRCTVM5K9 along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
