About Microsoft deployments
The deployment package for Microsoft Hyper‑V is a ZIP archive. You’ll need to run the installation script in the deployment package from Windows PowerShell. To run the script, you might need to configure the virtual machine’s security policy to Unrestricted using the PowerShell Set-ExecutionPolicy Unrestricted command. This table lists the parameters for the installation script.
Network setting | Your value |
|---|
InstallLocation (required) | Path to the directory for the virtual machine. |
Model (required) | The hardware model to be configured. Choosing the model causes the installation to allocate the correct disk sizes, memory, and CPU cores. |
VHDLocation (optional) | The default is the selected directory. The script looks for the management VHD image at this location. |
VMName (optional) | The default is Riverbed SteelHead. |
ComputerName (optional) | The default is localhost. If you are installing to a remote computer, enter the name of that computer. |
NumInpaths (optional) | The default is 1. Enter the number of in-path pairs to create. |
SegstoreSize (optional) | The default is the allocated disk size for your model. Enter a value in bytes (B) or gigabytes (GB) to override the allocated size. |
PowerOn (optional) | Include this setting if you want the appliance to start up after the installation is complete. |
PrimaryNetwork (optional) | Enter the name of the vSwitch to connect the primary NIC to. |
AuxNetwork (optional) | Enter the name of the vSwitch to connect the auxiliary NIC to. |
{WL}an{01234}_0Network (optional) | Enter the name of the vSwitch to connect the named network interface to. |
Deploying on Microsoft
1. Obtain a deployment package and extract the contents to a directory accessible to the host virtual machine.
2. In PowerShell, run the installation script. You can enter all the script parameters as part of the run command. If you do not enter any parameters, you are prompted for the two required parameters.
3. If prompted, enter the installation location and the product model. Virtual machine creation can take 30 minutes or more to complete.
4. In Hyper-v Manager, verify all the virtual machine settings.
5. In the virtual machine settings, set the reserve weight for CPU to 100 and the memory weight to High.
6. In Hyper‑V Manager, create a virtual switch for the appliance’s primary, auxiliary, LAN, and WAN interfaces. Ensure that Enable virtual LAN identification for management operating system is disabled; you do not enable VLAN tagging at the Hyper‑V Virtual Network Switch level.
7. Connect each virtual switch interface to the corresponding appliance interface. If your network uses VLAN tagging, enable Enable virtual LAN identification for the LAN0_0 and WAN0_0 interfaces. If your network does not use VLAN tagging, disable the feature.
8. Power on the virtual machine and log in to it.
9. In the virtual machine, open the network connections control panel.
10. Under the networking properties settings for the connection to the Hyper-V server, set the jumbo frame size to 9014 bytes.
11. In the same advanced properties dialog box, select Priority & VLAN. For a VLAN-tagged network, select Packet Priority & VLAN Enabled. For a non-VLAN-tagged network, select Packet Priority & VLAN Disabled.
12. Close the properties dialog box and restart the virtual machine.
Deploying manually on Microsoft
Before you begin, create and connect the necessary virtual interfaces and switches.
1. Create a new virtual machine.
2. Remove the CD drive.
3. Create a fixed-size disk for the management VHD. You can perform this step from the Hyper‑V Manager, or you can use the Convert-VHD script in the product’s deployment package.
4. Add the management VHD as the disk in controller 0, slot 0.
5. Create a fixed-size disk for the appliance’s data store. Add this disk to controller 0, slot 1.
6. Create virtual NICs for the primary and auxiliary interfaces, and create two virtual NICs for each additional in-path interface pair.
MAC address spoofing
We recommend that you enable MAC address spoofing on the virtual network adapters. You’ll need to run PowerShell as an administrator.
set-vmnetworkadapter -VMname “<vm-name>” -computername <hyper‑v-host>
-name <v-network-adapter> -macaddressspoofing on
where <vm-name> is the name of the virtual machine, <hyper‑v-host> is the name of the Hyper‑V host, and <v-network-adapter> is the name of the virtual network adapter.
This example shows how to enable MAC address spoofing for the lan0_0 and wan0_0 interfaces on the virtual machine myVM and Hyper‑V host myHost:
Administrator> set-vmnetworkadapter -VMname “myVM” -computername myHost -name lan0_0
-macaddressspoofing on
Administrator> set-vmnetworkadapter -VMname “myVM” -computername myHost -name wan0_0
-macaddressspoofing on
Verify that MAC address spoofing has been enabled:
Get-VMNetworkAdapter -VMname <vm-name> -computername <hyper‑v-host> |fl Name,macaddressspoofing
where <vm-name> is the name of the virtual machine and <hyper‑v-host> is the name of the Hyper‑V host.
This example shows how to display MAC address spoofing status for the configuration as a formatted list:
Get-VMNetworkAdapter -VMname “myVM” -computername myHost |fl Name,macaddressspoofing
Name : primary
MacAddressSpoofing : Off
Name : aux
MacAddressSpoofing : Off
Name : lan0_0
MacAddressSpoofing : On
Name : wan0_0
MacAddressSpoofing : On
VLAN tagging networks
Determine if your network uses VLAN tagging before you deploy the appliance. Specific configuration is required depending on the VLAN configuration. This table shows the configuration to use for networks with and without VLAN tagging.
Type of adapter or interface | VLAN-tagged packet setting | Non-VLAN-tagged packet setting |
|---|
Windows network adapter configuration for VLAN | VLAN enabled | VLAN disabled |
Hyper‑V virtual switch network interface configuration | VLAN disabled | VLAN disabled |
Hyper‑V virtual machine network interface configuration | VLAN enabled | VLAN disabled |
SteelHead in-path interface configuration | VLAN ID 0 | VLAN ID 0 |
Troubleshooting Microsoft deployments
After powering on the virtual machine, if you see messages about missing interfaces or disks, check these troubleshooting tips:
• If there are missing interfaces on the appliance, check the virtual machine settings and verify that you are using synthetic NICs, and that the cards are connected.
• If the appliance logs messages about missing disks, ensure that the data store disk is present and is in slot 1 of controller 0.
After every change to Hyper-V configuration settings, you must shut down and restart the Hyper-V.
Be sure that the lan0_0 and wan0_0 interfaces are mapped to the correct NIC on the server.