Deploy on Microsoft Hyper-V

Deploy on Microsoft Hyper-V

Action

More Information

1.

Review the Release Notes for your AsyncOS release.

Release Notes are available from the locations in Additional Information.

2.

Download the virtual appliance image and MD5 hash from Cisco.

You will need the MD5 hash to check the data integrity of the appliance image.

Prepare the Content Secure Image and Files.

3.

Deploy the virtual appliance on Hyper-V.

  1. Set up the Windows Server Operating System. Ensure that you have installed the required Hyper-V roles. See System Requirements for more information.

  2. Download the image as described in Prepare the Content Secure Image and Files.

  3. Using the Hyper-V Manager, install the virtual appliance image using the New Virtual Machine Wizard.

  4. Complete the wizard.

  5. Edit the processor settings in the Hyper-V Manager. See Determine the Best-Sized Virtual Appliance Image for Your Deployment to check for the number of processors and NICs required.

4.

If DHCP is disabled, set up the appliance on your network.

If DHCP Is Disabled, Set Up the Appliance on the Network (Microsoft Hyper-V).

5.

Install the license file

Install the Virtual Appliance License File.

6.

Log into the web UI of your appliance and configure the appliance software as you would do for a physical appliance.

For example, you can:

  • Run the System Setup Wizard

  • Upload a configuration file

  • Manually configure features and functionality.

  • For instructions on accessing and configuring the appliance, including gathering required information, see the online help or user guide for your AsyncOS release, available from the relevant location in Additional Information.

  • To migrate settings from a physical appliance, see the release notes for your AsyncOS release.

Feature keys are not activated until you enable the respective features.

Note

The following are the limitations for virtual Cisco Secure Web appliances (with FreeBSD 10.x) deployed on Microsoft Hyper-V generation 1 platform:

  • It is not possible to modify the virtual appliance interfaces using the etherconfig CLI command.

  • The ifconfig CLI command displays the virtual appliance interface status as Unknown or Simplex even though it runs on Duplex mode.

However, there is no impact on the performance of the appliance due to the above limitations.

If DHCP Is Disabled, Set Up the Appliance on the Network (Microsoft Hyper-V)


Note

If you cloned the virtual security appliance image, perform the following steps for each image.

Procedure

Step 1

From the Hyper-V manager console, run interfaceconfig.

Step 2

Write down the IP address of the virtual appliance’s Management port.

Note

 

The Management port obtains its IP address from your DHCP server. If the appliance cannot reach a DHCP server, it will use 192.168.42.42 by default.

Step 3

Configure the default gateway using the setgateway command.

Step 4

Commit the changes.

Note

 

The hostname does not update until after you have completed the setup wizard.