Install Guide for JunosV Wireless LAN Controller · PDF fileInstall Guide for JunosV Wireless LAN Controller ... and procedures to install a Juniper Networks JunosV ... Install Guide
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Install Guide for JunosV Wireless LAN Controller
The next-generation Juniper Networks JunosV Wireless LAN Controller is a virtual controller
using a cloud-based architecture with physical access points. The current functionality of a
physical controller is available on the virtual controller, and the virtual controller can support up
to 256 access points.
This document describes the installation requirements and procedures to install a Juniper
Networks JunosV Wireless LAN Controller (JunosV controller) on a VMware server.
Installation Requirements
Installing the virtual Controller on ESXi 5.x Hypervisor
Upgrading MSS on JunosV Wireless LAN Controller
The JunosV controller runs on a virtual machine (VM) environment that run contained
operating systems and execute applications. If you are not running any VM environments and
do not already have VMware ESXi deployed, you can download it at
http://www.vmware.com/products/vsphere/esxi-and-esx/overview.html. You have to register
and create a free account, and then register separately for each download.
The JunosV controller is a 32-bit Linux application, but ESXi requires hardware with 64-bit
capability such as Core 2 family of processors. You must enable the virtualization feature in
the BIOS of each host device that deploys the VM environment. Each virtualization host has
the following requirements:
Dual Core 2 or higher
2GB of memory dedicated to the JunosV controller
1 GB for the host computer
Minimum 16 GB of the disk space
1 to 4 Network Interface Cards (NICs)
Use DHCP to obtain network settings dynamically or define them statically for the LAN card on
your computer.
Once you have installed the VM and JunosV controller images, you can log into the JunosV
controller and configure it in the same manner as MSS on a physical controller.
The following are not supported by the JunosV controller:
Changing the OS (supports only LINUX OS)
Informational Note:
Before you begin installing this feature in a VMware environment, you should have an
understanding of VM environments and installing VMs. Installing and using VMs is
set license ap - allows you to enter access points for licensed features on the JunosV
controller.
Upgrading MSS on JunosV Wireless LAN Controller
You can upgrade the MSS image on the JunosV controller. You can upgrade the MSS version in
two methods:
Within the same major release version (for example, from MSS 9.0.1 to an MR release).
From one major release to the next major release (for example, from MSS 9.0.1 to the next
major release version).
Upgrading Within the Same Major ReleaseTo upgrade from MSS 9.0.1 to a 9.0 MR release:
1. Unpack the release_img.tar.gz file to a location from where it can be copied to the JunosV
WLC using tftp or scp copy protocols.
2. Copy the .ina file, (/release_img/public/WLCV0xx.ina) to the boot partition on the JunosV
controller using tftp or SCP copy protocols. For example,
copy scp://<IP>://<path to .ina file>/<.ina file> boot<x>:
3. Then, follow the same procedure used while upgrading a physical wireless LAN controller.
Informational Note: The SCP copy protocol is faster than the tftp, but can only be used if the station where the .ina file is a linux station. Also, copying the .ina file closer to the blade that hosts the JunosV WLC results in faster file transfer rates.
Upgrading from MSS 9.0.1 to the Next Major ReleaseTo upgrade from MSS 9.0.1 to the next major release:
1. Create a new virtual machine (VM) for the JunosV WLC using the new .OVA file for the next
major release and copy the old configuration to the new machine.
2. Set the system serial number and MAC address to the previous VM values using the CLI
command:
set system serial <serial-number>
set system mac <mac-address>
3. Delete the old VM after creating and testing the new JunosV controller successfully.