MSE Delivery Modes - Cisco€¦ · MSE Delivery Modes TheCiscoMSEcomespreinstalledonaphysicalappliancewithvariousperformancecharacters.TheMSE …

MSE Delivery Modes

The Cisco MSE comes preinstalled on a physical appliance with various performance characters. The MSEis delivered in two modes, the physical appliance and the virtual appliance.

This chapter contains the following sections:

• Physical Appliance, page 1

• Virtual Appliance, page 1

• Deploying the MSE Virtual Appliance, page 4

• Adding Virtual Appliance License to the Prime Infrastructure, page 8

• Viewing the MSE License Information Using the License Center, page 9

• Removing a License File Using the License Center, page 10

Physical ApplianceWhen the MSE is located on the physical appliance, you can use the standard license center UI to add newlicenses.When theMSE is located on the physical appliance, the license installation process is based on CiscoUDI (Unique Device Identifier). ChooseAdministration >License Center on the Cisco Prime InfrastructureUI to add the license.

Virtual appliance licenses are not allowed on physical appliances.Note

Virtual ApplianceThe MSE is also offered as a virtual appliance, to support lower-level, high, and very high end deployments.When the MSE is located on the virtual appliance, the license is validated against VUDI (Virtual UniqueDevice Identifier) instead of UDI.

Cisco Adaptive Wireless Intrusion Prevention System Configuration Guide, Release 7.4 OL-28566-01 1

MSE is available as a virtual appliance for Release 7.2 and later. The virtual appliance must be activatedfirst before installing any other service licenses.

Note

The MSE virtual appliance software is distributed as an Open Virtualization Archive (OVA) file. You caninstall the MSE virtual appliance using any of the methods for deploying an OVF supported by the VMwareenvironment. Before starting, make sure that the MSE virtual appliance distribution archive is in a locationthat is accessible to the computer on which you are running vSphere Client.

For a virtual appliance, you must have an activation license. Without an activation license, the MSE starts inevaluation mode. Even if service licenses are present on the host, it rejects them if the activation license isnot installed.

See the VMware vSphere 4.0 documentation for more information about setting up your VMwareenvironment.

Note

You can add and delete a virtual appliance license either using the Services >Mobility Services Engine >Add Mobility Services Engine page when you are installing MSE for the first time, or you can use theAdministration > License Center page to add or delete a license.

See the Adding and Deleting Mobility Services Engines and Licenses and the Deleting an MSE License Filefor more information on adding a license and deleting a license using the mobility services engine wizard.

This section contains the following topics:

• Operating Systems Requirements, on page 2

• Client Requirements, on page 3

• Prerequisites for Setting up an MSE Virtual Appliance on Server, on page 3

• Virtual Appliance Sizing, on page 3

• Reinstalling MSE on a Physical Appliance, on page 4

• Deploying the MSE Virtual Appliance, on page 4

• Adding a License File to the MSE Using the License Center, on page 9

• Viewing the MSE License Information Using the License Center, on page 9

• Removing a License File Using the License Center, on page 10

Operating Systems RequirementsThe following operating systems are supported:

• Red Hat Linux Enterprise server 5.4 64-bit operating system installations are supported.

• Red Hat Linux version support on VMware ESX/ESXi Version 4.1 and later with either local storageor SAN over fiber channel.

Cisco Adaptive Wireless Intrusion Prevention System Configuration Guide, Release 7.42 OL-28566-01

MSE Delivery ModesOperating Systems Requirements

7_4_MSE_wIPS_chapter_010.pdf#unique_28

The recommended deployments for a virtual appliance are UCS and ESX/ESXi.Note

Client RequirementsThe MSE user interface requires Microsoft Internet Explorer 7.0 or later with the Google Chrome plugin orMozilla Firefox 3.6 or later releases.

We strongly advise that you do not enable third-party browser extensions. In Internet Explorer, you candisable third-party browser extensions by choosing Tools > Internet Options and unselecting the Enablethird-party browser extensions check box on the Advanced tab.

Note

The client running the browser must have a minimum of 1 GB of RAM and a 2-GHz processor. The clientdevice should not be running any CPU or memory-intensive applications.

Prerequisites for Setting up an MSE Virtual Appliance on ServerBefore setting up an MSE virtual appliance, ensure that you have completed the following:

• Make sure that your computer has at least 500 GB+ hard disk space and fast SAS drives with enhancedRAID controllers.

• Use VM ESXi 4.1 or later.

• Insert the ESXi 4.1 or later DVD and boot from the drive. Install ESXi. If there are multiple drives,install in the drive that is configured as the boot drive. If you select the wrong drive for install, you canreformat using a Fedora Live CD and select the other drive when you install ESXi again.

• Default username and password for ESX/i are root and blank, just leave blank and hit enter (no password).

• Configure the IP address and make sure to select the correct Network Adapter (select the ones that areenabled and active, you might have multiple if your host is connected to multiple networks).

• (If you are using UCS box) - You can also set the same IP address during CIMC setup (press F8 duringboot up). Also change the default password.

• Once ESXi is setup, you can use a Win XP/7 machine and connect to the ESXi host through vSphereclient using the above configured IP address and login credentials.

• Refer to this article to setup datastores on ESXi: http://pubs.vmware.com/vsphere-esxi-4-1-embedded/wwhelp/wwhimpl/js/html/wwhelp.htm

Virtual Appliance SizingThe following table lists the information on virtual appliance sizing.


MSE Delivery ModesClient Requirements

http://pubs.vmware.com/vsphere-esxi-4-1-embedded/wwhelp/wwhimpl/js/html/wwhelp.htmhttp://pubs.vmware.com/vsphere-esxi-4-1-embedded/wwhelp/wwhimpl/js/html/wwhelp.htm

Table 1: Virtual Appliance Sizing

Supported License (Individually)ResourcesPrimary MSE

wIPS LicenseCAS LicenseCPUTotal MemoryVirtual ApplianceLevel

2010013.5GLevel1

2000200026GLevel2

500018000811GLevel3

10000500001220GLevel4

Reinstalling MSE on a Physical ApplianceYou must have root privileges to install the MSE on a physical appliance. To reinstall the MSE on a physicalappliance, follow these steps:

Step 1 Insert the provided MSE software image DVD. The system boots up and a console appears.Step 2 Select option 1 to reinstall the MSE software image. The system reboots and the configure appliance screen appears.Step 3 Enter the initial setup parameters and the system reboots again. Remove the DVD and follow the provided steps to start

the MSE server.

Deploying the MSE Virtual ApplianceThis section describes how to deploy the MSE virtual appliance on an ESXi host using the vSphere Clientusing the Deploy OVF wizard or from the command line. This section contains the following topics:

• Deploying the MSE Virtual Appliance from the VMware vSphere Client, on page 4

• Configuring the Basic Settings to Start the MSE Virtual Appliance VM, on page 7

• Deploying the MSE Virtual Appliance Using the Command-Line Client, on page 8

Deploying the MSE Virtual Appliance from the VMware vSphere ClientThe MSE virtual appliance is distributed as an OVA file that can be deployed on an ESXi using the vSphereClient. An OVA is a collection of items in a single archive. In the vSphere Client, you can deploy the OVAwizard to create a virtual machine running the MSE virtual appliance application as described in this section.


MSE Delivery ModesReinstalling MSE on a Physical Appliance

While the following procedure provides general guidelines for how to deploy the MSE virtual appliance,the exact steps that you must perform may vary depending on the characteristics of your VMwareenvironment and setup.

Note

Deploying virtual appliance takes at least 500 GB of available disk space on the ESXi host database. Werecommend that the datastore on the host have a block size of atleast 4 MB or more for ESXi 4.1 or earlier,else the deployment may fail. No such restriction is placed on the datastores on ESXi 5.0 and later.

Note

To deploy the MSE virtual appliance, follow these steps:

Step 1 From the VMware vSphere Client main menu, choose File > Deploy OVF Template. The Deploy OVF Templatewindow appears.

Figure 1: Deploy OVF Template Window


MSE Delivery ModesDeploying the MSE Virtual Appliance from the VMware vSphere Client

Step 2 Select the Deploy From File radio button and choose the OVA file that contains the MSE virtual appliance distributionfrom the drop-down list.

Step 3 Click Next. The OVF Template Details window appears. VMware ESX/ESXi reads the OVA attributes. The detailsinclude the product you are installing, the size of the OVA file (download size), and the amount of disk space that mustbe available for the virtual machine.

Step 4 Verify the OVF Template details and click Next. The Name and Location window appears.

Figure 2: Name and Location Window


MSE Delivery ModesDeploying the MSE Virtual Appliance from the VMware vSphere Client

Step 5 Either keep the default name for the VM to be deployed in the Name text box or provide a new one, and clickNext. Thisname value is used to identify the new virtual machine in the VMware infrastructure, you should use any name thatdistinguishes this particular VM in your environment. The Host / Cluster window appears.

Figure 3: Host/Cluster Window

Step 6 Choose the destination host or HA cluster on which you want to deploy the MSE VM, and click Next. The ResourcePool window appears.

Step 7 If you have more than one resource pool in your target host environment, choose the resource pool to use for thedeployment, and click Next. The Ready to Complete window appears.

Step 8 Review the settings shown for your deployment and, if needed, click Back to modify any of the settings shown.Step 9 Click Finish to complete the deployment. A message notifies you when the installation completes and you can see the

MSE virtual appliance in your inventory.Step 10 Click Close to close the Deployment Completed Successfully dialog box.

Configuring the Basic Settings to Start the MSE Virtual Appliance VMYou have completed deploying (installing) the MSE virtual appliance on a new virtual machine. A node forthe virtual machine now appears in the resource tree in the VMware vSphere Client window. Deploying theOVF template creates a new virtual machine in vCenter with theMSE virtual appliance application and relatedresources already installed on it. After deployment, you need to configure basic settings for the MSE virtualappliance.


MSE Delivery ModesConfiguring the Basic Settings to Start the MSE Virtual Appliance VM

To start the MSE setup, follow these steps:

Step 1 In the vSphere Client, click theMSE virtual appliance node in the resource tree. The virtual machine node shouldappear in the Hosts and Clusters tree below the host, cluster, or resource pool to which you deployed the MSE virtualappliance.

Step 2 On the Getting Started tab, click the Power on the virtual machine link in Basic Tasks. The Recent Tasks window at thebottom of the vSphere Client pane indicates the status of the task associated with powering on the virtual machine. Afterthe virtual machine successfully starts, the status column for the task shows Completed.

Step 3 Click the Console tab, within the console pane to make the console prompt active for keyboard input.Step 4 Use the MSE setup wizard to complete the setup.

Deploying the MSE Virtual Appliance Using the Command-Line ClientThis section describes how to deploy the MSE virtual appliance from the command line. As an alternative tousing the vSphere Client to deploy the MSE OVA distribution, you can use the VMware OVF tool, which isa command-line client.

To deploy an OVA with the VMware OVF tool, use the ovftool command, which takes the name of the OVAfile to be deployed and the target location as arguments, as in the following example:

ovftool MSE-VA-X.X.X-large.ova vi://my.vmware-host.example.comIn this case, the OVA file to be deployed is MSE-VA-X.X.X-large.ova and the target ESX host ismy.vmware-host.example.com. For complete documentation on the VMware OVF Tool, see the VMwarevSphere 4.0 documentation.

Adding Virtual Appliance License to the Prime InfrastructureYou can add virtual appliance license to the Prime Infrastructure using the following two options:

• Using the Add Mobility Service Engine page when you are installing MSE for the first time. See theAdding a Mobility Services Engine to the Prime Infrastructure for more information.

• Using the License Center page. See the Adding a License File to the MSE Using the License Center formore information.


MSE Delivery ModesDeploying the MSE Virtual Appliance Using the Command-Line Client

7_4_MSE_wIPS_chapter_010.pdf#unique_27

Adding a License File to the MSE Using the License CenterTo add a license, follow these steps:

Step 1 Install the MSE virtual appliance.Step 2 Add the MSE to the Prime Infrastructure.Step 3 Choose Administration > License Center in the Prime Infrastructure UI to access the License Center page.Step 4 Choose Files >MSE Files from the left sidebar menu.Step 5 Click Add to add a license.

The Add A License File menu appears.

Step 6 Select the MSE and browse to the activation license file.Step 7 Click Submit.

Once you submit, the license is activated and license information appears in the License Center page.

Viewing the MSE License Information Using the License CenterThe license center allows you to manage the Prime Infrastructure, Wireless LAN Controllers, and MSElicenses. To view the license information, follow these steps

Step 1 Choose Administration > License Center to access the License Center page.Step 2 Choose Summary >MSE from the left sidebar menu, to view the MSE summary page.

The following table lists the MSE Summary page fields.

Table 2: MSE Summary Page

DescriptionField

Provides a link to the MSE license file list page.MSE Name

Service type can be CAS, wIPS, Mobile Concierge service, LocationAnalytics service, and Billboard service.

Service

Platform limit.Platform Limit

Specifies the type of MSE.Type

Shows the total number of client elements licensed across MSEs.Installed Limit

The three different types of licenses: permanent, evaluation, andextension.

License Type


MSE Delivery ModesAdding a License File to the MSE Using the License Center

DescriptionField

The number of CAS or wIPS elements currently licensed acrossMSEs.Count

Shows the number of client elements that are not licensed.Unlicensed Count

The percentage of CAS or wIPS elements licensed across MSEs.%Used

Removing a License File Using the License CenterTo remove a license, follow these steps:

Step 1 Install the MSE virtual appliance.Step 2 Add the MSE to the Prime Infrastructure using the wizard.Step 3 Choose Administration > License Center to access the License Center page.Step 4 Choose Files >MSE Files from the left sidebar menu.Step 5 Choose anMSE license file that you want to remove by selecting theMSELicense File radio button, and clickRemove.Step 6 Click OK to confirm the deletion.


MSE Delivery ModesRemoving a License File Using the License Center

MSE Delivery ModesPhysical ApplianceVirtual ApplianceOperating Systems RequirementsClient RequirementsPrerequisites for Setting up an MSE Virtual Appliance on ServerVirtual Appliance SizingReinstalling MSE on a Physical Appliance

Deploying the MSE Virtual ApplianceDeploying the MSE Virtual Appliance from the VMware vSphere ClientConfiguring the Basic Settings to Start the MSE Virtual Appliance VMDeploying the MSE Virtual Appliance Using the Command-Line Client

Adding Virtual Appliance License to the Prime InfrastructureAdding a License File to the MSE Using the License Center

Viewing the MSE License Information Using the License CenterRemoving a License File Using the License Center

Documents

MSE Delivery Modes - Cisco€¦ · MSE Delivery Modes TheCiscoMSEcomespreinstalledonaphysicalappliancewithvariousperformancecharacters.TheMSE …