• Document: Wanos on vsphere Hypervisor (esxi)
  • Size: 966.71 KB
  • Uploaded: 2019-05-17 11:47:48
  • Status: Successfully converted


Some snippets from your converted document:

Wanos on vSphere Hypervisor (eSXI) Complete Lab Setup Guide This guide explains how to deploy a complete lab on a VMware vSphere Hypervisor. The step- by-step guide includes steps to create Head Office and Branch Wanos VM instances on the same Hypervisor system as well as virtual networks to simulate the Server LAN, WAN Link and Branch LAN. Physical Interfaces can be used to connect the lab to the physical network. Additional Workstation VM’s are added to simulate end to end testing. The lab setup uses bridge mode and hence the 192.168.1.X/24 address space is used on both Head Office and Branch sides. The lab design is illustrated in the following network diagram: Table of Contents  Configure eSXI vSwitch  PhyNIC  WAN_Link  Branch_LAN  Deploy Wanos and Windows Images on vSphere eSXI  Deploy Wanos-HQ  Deploy Wanos-Branch  Deploy HQ-PC  Deploy Branch-PC  Resource Reservation  IP Configuration Configure eSXI vSwitch Configuring vSwitch before deploying Virtual Machines is a good idea. This section tackles the vSwitch configuration. 3 Port Groups will be created – PhyNIC, WAN_Link, Branch_LAN. To configure vSwitch navigate to Server > Configuration (tab) > Networking > Properties (under Standard Switch). Refer to the screenshot below for reference. PhyNIC From the vSwitch Properties window click Add, select Virtual Machine and click Next to continue. Set the Network Label to PhyNIC, leave VLAN ID to None (0) and click Next to continue. Review the information and click Finish to add a new Port Group. After adding a new Port Group, the Security setting needs to be updated. From the vSwitch Property window, select or click the target Port Group, PhyNIC in this case, and click Edit. Refer to the screenshots below. The vSwitch Properties window show what Port Groups that are available for the given vSwitch. Under Security (tab), enable Promiscuous Mode and set the value to Accept. The Security (tab) allows the Promiscuous Mode to be set which is required in Wanos. WAN_Link To add WAN_Link port group, follow the same steps found in PhyNIC and use the following information: Network Label: WAN_Link VLAN ID: 10 Promiscuous Mode: Accept Branch_LAN To add Branch_LAN port group, follow the same steps found in PhyNIC and use the following information: Network Label: Branch_LAN VLAN ID: 11 Promiscuous Mode: Accept Deploy Wanos and Windows Virtual Machines This section tackles the deployment of Wanos and Windows Virtual Machines. Download the Virtual Appliance OVA from Wanos Downloads section and decompress the zip file to extract the OVA file into a directory of preference (e.g. Downloads). Two Wanos VMs will be deployed to simulate two offices that will be explained in a later chapter. The VMs are named Wanos-HQ and Wanos-Branch. This guide assumes that the user has a Windows-based virtual machine, in OVA format, available for deployment. To get started, click File > Deploy OVF Template from vSphere Client. Refer to the screenshot below for reference. Deploy Wanos-HQ Locate the extracted Wanos OVA file by clicking Browse and point to the directory where Wanos was extracted. Click Next to continue. The next window will show the OVF Template Details. Click Next to continue. Set the Name to Wanos-HQ. Click Next to continue. Select Thick Provision Lazy Zeroed (default) and click Next to continue. Note: If Storage Space is a concern, select Thin Provision. Under Network Mapping set the following: Source Network Destination Network wan0 WAN_Link lan0 PhyNIC Click Next to continue. Review the Deployment settings. Click Back if needed otherwise, click Finish to deploy the Virtual Machine. Ensure that Power on after deployment is not checked / marked. Deploy Wanos-Branch Follow the same steps outlined in Deploy Wanos-HQ and use the following information: Name: Wanos-Branch Network Mapping: Source Network Destination Network wan0 WAN_Link lan0 Branch_LAN Deploy HQ-PC Follow the same steps outlined in Deploy Wanos-HQ and use the following information: Name: HQ-PC Network Mapping: PhyNIC Deploy Branch-PC Follow the same steps outlined in Deploy Wanos-HQ and use the following information: Name: Branch-PC Network Mapping: Branch_LAN Resource Reservation Optionally, depending on performance requirements, resources can be reserved. For example the Virtual Machines can be configured as follows: Wanos-HQ Hardware CPU 4 (2 cores, 2 virtual sockets) Memory 2 GB or 2048 MB Resourc

Recently converted files (publicly available):