• SonicOS/X NSv 7
• Introducing the NSv Series
  • Feature Support Information
  • Node Counts Per Platform
  • Installation File / Supported Platforms
  • Hardware Compatibility
  • Product Matrix and Requirements
  • Backup and Recovery Information
  • High Availability Configurations
  • Exporting and Importing Firewall Configurations
  • Upgrading from SonicOS 6.5
  • Upgrading to a Higher Capacity NSv Model
  • Creating a MySonicWall Account
• Installing SonicOS/X on the NSv Series
  • Preparing the Windows Server System
  • Creating Virtual Switches in Hyper-V
  • Obtaining the NSv Image
  • To Install NSv on Hyper-V
  • Troubleshooting Installation Configuration
    • Insufficient Memory Assignment
    • Incompatible CPU
    • Incorrect CPU Configuration
    • Insufficient Resources at Time of Configuration
• Licensing and Registering Your NSv
  • Registering the NSv Virtual Machine with SonicOS/X
• SonicOS/X Management
  • Managing SonicOS/X on the NSv Series
  • Using System Diagnostics
• Using the Virtual Console and SafeMode
  • Connecting to the CLI and Management Console
  • Navigating the NSv Management Console
    • System Info
    • Management Network or Network Interfaces
    • Test Management Network
    • Diagnostics
    • NTP Server
    • Lockdown Mode
      • Temporary Lockdown Mode
    • System Update
    • Reboot | Shutdown
    • About
    • Logs
  • Using SafeMode on the NSv
    • Enabling SafeMode
    • Disabling SafeMode
    • Configuring the Management Network in SafeMode
      • Configuring Interface Settings
      • Disabling an Interface
    • Downloading Logs in SafeMode
  • Using the SafeMode Web Interface
    • Accessing the SafeMode Web Interface
    • Entering/Exiting SafeMode
    • Downloading the SafeMode Logs
    • Uploading a New Image in SafeMode
• SonicWall Support
  • About This Document

Creating Virtual Switches in Hyper-V

Microsoft Hyper-V allows you to create three types of virtual switches (vSwitches):

• External vSwitch – binds to a physical network adapter and provides the vSwitch access to a physical network.

• Internal vSwitch – passes traffic between the virtual machines and the Hyper-V host. This type of vSwitch does not provide connectivity to a physical network.

• Private vSwitch – passes traffic between the virtual machines on the Hyper-V host only.

For an NSv Series Microsoft Hyper-V deployment, an External vSwitch is required to provide connectivity for NSv management access and for routing traffic to and from the network devices that the virtual machine is securing (such as LAN or DMZ side devices).

An Internal vSwitch or Private vSwitch is required when the virtual machines that the virtual machine is securing (e.g. LAN or DMZ side virtual machine) are created in the same Hyper-V server. The difference between an Internal vSwitch and a Private vSwitch is whether to allow traffic between the NSv and the Hyper-V host (through an Internal vSwitch or, between the NSv and other virtual systems running under Hyper-V (through a Private VSwitch).

To create an External vSwitch

1. Open the Hyper-V Manager tool.

   

2. To bring up the detailed Actions panel, click on the Hyper-V designation in the upper left and then double-click on the name that appears under it.

   

3. Select Virtual Switch Manager.

   

4. Select External for the type of virtual switch and then click Create Virtual Switch.

   

5. Under Virtual Switch Properties, type a descriptive name for the switch into the Name field.

6. For Connection Type, select External network and select the physical network adapter that connects to the external vSwitch from the drop-down menu.

7. If you want to use this same physical adapter to manage the Hyper-V host at the same time, select the Allow management operating system to share this network adapter check box.

   

   When the Allow management operating system to share this network adapter option is selected, you need to specify the VLAN ID that is used for this management traffic. When the VLAN ID is not configured, the management traffic is untagged.

   Always make sure to isolate the Hyper-V management traffic from the NSv traffic by using a different VLAN ID.

8. Repeat Step 4 through Step 7 to create more External vSwitches if there are more physical connections deployed between the Windows Server and the external switch and you would like to use them for routing NSv traffic.

If your NSv protects virtual machines (LAN or DMZ side virtual machine) located in the same Hyper-V server, perform the next procedure to create an Internal vSwitch or Private vSwitch.

To create an Internal or Private vSwitch

1. On the Action tab of the Hyper-V Manager tool, select Virtual Switch Manager.

2. Select Internal or Private for the type of virtual switch and then click Create Virtual Switch.

3. Under Virtual Switch Properties, type a descriptive name for the switch into the Name field.

4. For Connection Type, select Internal network or Private network.