Exinda How to Guide: Virtual Appliance. Exinda ExOS Version Exinda, Inc

Transcription

1 Exinda How to Guide: Virtual Appliance Exinda ExOS Version 6.3

2 2 Virtual Appliance Table of Contents Part I Introduction 4 1 Using... this Guide 4 Part II Overview 6 Part III Deployment Options 8 Part IV Sizing 11 Part V Licensing 13 Part VI VMware vsphere (ESX and ESXi) 16 1 Downloading... and Installing 16 2 Custom... Settings 19 3 Additional... NICs 20 Promiscuous... Mode 24 4 Additional... Storage 27 5 Booting Installing... the Silicom Bypass Driver on ESXi Installing... the Silicom Bypass Driver on ESXi Part VII Citrix XenServer 38 1 Downloading... and Installing 38 2 Custom... Settings 44 3 Additional... NICs 45 4 Additional... Storage 48 5 Booting... 50

3 Part I

4 4 Virtual Appliance 1 Introduction Virtual Appliance Exinda Firmware Version: 6.3 All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems - without the written permission of the publisher. Products that are referred to in this document may be either trademarks and/or registered trademarks of the respective owners. The publisher and the author make no claim to these trademarks. While every precaution has been taken in the preparation of this document, the publisher and the author assume no responsibility for errors or omissions, or for damages resulting from the use of information contained in this document or from the use of programs and source code that may accompany it. In no event shall the publisher and the author be liable for any loss of profit or any other commercial damage caused or alleged to have been caused directly or indirectly by this document. 1.1 Using this Guide Throughout the manual the following text styles are used to highlight important points: Useful features, hints and important issues are called "notes" and they are identified in a light blue background. Note: This is a note. Practical examples are presented throughout the manual for deeper understanding of specific concepts. These are called "examples" and are identified with a light green background. This is an example. Warnings that can cause damage to the device are included when necessary. These are indicated by the word "caution" and are highlighted in yellow. Caution: This is a caution.

5 Part II

6 6 Virtual Appliance 2 Overview Exinda's range of UPM appliances are available as fully featured Virtual Appliances. In fact, there is no difference between the software that runs on bare metal hardware, and the software that runs on Virtual Appliances. If the Exinda software detects that it's running under a hypervisor, certain optimizations are enabled in order to ensure maximum performance. Exinda provides full support for Virtual Appliances running on the following hypervisors: VMware vsphere (ESX and ESXi) (4.1 and later) Citrix XenServer (5.5 and later) This guide explains how to successfully download and deploy Exinda Virtual Appliances. The following documentation may also be useful: Exinda Topologies Guide Exinda Virtualization Deployment Guide Exinda Storage How to Guide Exinda User Manual Note: Particular attention should be paid to the Sizing and Licensing requirements of Virtual Appliances. These are covered later in this guide.

7 Part III

8 8 Virtual Appliance 3 Deployment Options Virtual Appliances can be deployed in all the same ways hardware appliances can. There are generally 2 typical deployment topologies, inline and out-of-path. Inline deployments involve 1 or more LAN/WAN port pairs bridged together at layer 2. Traffic must be directed through the bridge in order to be Monitored and Optimized. Using n hardware appliance as an example, here is what an inline deployment looks like: The challenge in a virtual environment is how to pass traffic through the bridge. There are several options: Dedicate 2 physical NICs on the host to be LAN and WAN ports. Used shared NICs on the host to be LAN and WAN ports, but logically separate the traffic with VLAN tags. Create a virtual network such that traffic is directed through virtual LAN/WAN ports. How this is best achieved largely depends on the virtual environment and which hypervisor technology is used. Out-of-path deployments are typically used in SPAN port mirroring, WCCPv2, HA and Clustering scenarios. Using a hardware appliance as an example, here is what an out-of path deployment looks like:

9 Deployment Options 9 This is quite straight forward to setup in a virtual environment, you need one NIC for Management and another NIC for Auxiliary (which is how Virtual Appliances are configured by default). Note: For more information, consult the Exinda Topologies Guide and the Exinda Virtualization Deployment Guide.

10 Part IV

11 Sizing 11 4 Sizing The following sizing guide can be used to estimate the amount of resources required for each Virtual Appliance depending on the WAN bandwidth. Visibility and Control Visibility, Control and Optimization Virtual CPUs Minimum RAM Storage Up to 10 Mbps Up to 2 Mbps 1-2 1GB ~250GB Up to 45 Mbps Up to 5 Mbps 2 2GB 250GB-500GB Up to 100 Mbps Up to 10 Mbps 2 4GB ~500GB Up to 250 Mbps Up to 20 Mbps 2-4 6GB 500GB-1TB * Up to 500 Mbps Up to 45 Mbps 4 8GB ~1TB * * Storage at higher throughput will require higher disk I/O bandwidth, so the underlying storage should be RAID based, ideally RAID 10. This is a guide only and there are several factors that may mean more or less resources are required in individual environments. Factors that may have an effect include: Quality, speed, performance of the host CPUs. Quality and performance of host NICs. Host disk I/O bandwidth. Note: Refer to the Exinda Virtualization Deployment Guide for a additional sizing information and the IOPS requirements critical to external storage performance.

12 Part V

13 Licensing 13 5 Licensing Licensing is a little different for Virtual Appliances compared to Hardware Appliances. All Virtual Appliances are shipped unlicensed. On first-boot, they automatically generate a unique Host ID. Exinda must be notified of this Host ID before a license can be issued. All Virtual Appliances must have access to Exinda's licensing server. That is, they must be able to access Virtual Appliances that do not have access will become unlicensed after 96 hours. The Exinda virtual appliance license process is very simple. To trial the Exinda Virtual appliance, go to the Exinda website for the virtual appliance and select the 30 day free trial icon. You will be prompted for your contact information and hypervisor type. After submitting your contact information, two things will happen: 1. An notification is sent to your local Exinda sales team for them to contact you; 2. A new landing page for the EX-V is presented to you with the option to download the virtual appliance, EX-V documentation, and the link to create a trial license. You also have the option to purchase an Exinda license for your EX-V appliance. You are either presented with a new purchase license landing page, or you can come back to the page after you have completed the evaluation. The purchased license web form prompts you for: o your contact information, o PO number Note: You must have already completed a Purchase Order to complete this form. o Host-ID, o hypervisor type, and o the license level you have purchased for each EX-V appliance. Once you have completed the purchased license form, the Exinda accounting team is notified and the purchased license keys will be ed to you. Warning: After the license has been installed on the virtual machine, you MUST check for updates to the Exinda software. To check for the latest update, in the Exinda Web UI go to System > Maintenance > Firmware Update and click Check for Latest Update. Install any updates available for the Exinda.

14 14 Virtual Appliance For complete instructions on generating a license, see the Exinda V irtua lized A pplia nce Licensing Guide.

15 Part VI

16 16 Virtual Appliance 6 VMware vsphere (ESX and ESXi) Exinda Virtual Appliances are available for VMware ESX/ESXi hypervisors. Note: VMware ESX/ESXi 4.1 (or later) is required. The following sections describe how to deploy Exinda Virtual Appliances as well as customize the virtual hardware to suit your requirements. 6.1 Downloading and Installing Step 1 Locate the latest release of the Exinda VMware Virtual Appliance from the Firmware Downloads section of the Exinda website. You must download both the VMware ESX/ESXi Download (exinda.ovf) and the VMware VMDK (Exinda-disk1.vmdk) files. Step 2 Open your VMware vsphere client and select File -> Deploy OVF Template... Then, copy the URL of the latest release of the Exinda VMware Virtual Appliance into the wizard. Then click Next. Step 3 Review the Virtual Appliance details.

17 VMware vsphere (ESX and ESXi) 17 Then click Next. Step 4 Review and Accept the End User License Agreement (EULA). Then click Next. Step 5 Specify and name for the new Virtual Appliance, and also choose the location to deploy the Virtual Appliance if asked to do so. Then click Next. Step 6

18 18 Virtual Appliance Choose the disk provisioning format. Exinda recommends Thick Provisioning (the default). By default, the Virtual Appliance comes with a single, 50GB disk. Additional storage can be added in the form of another disk after the Virtual Appliance has been deployed. See the Additional Storage section for more information. Then click Next. Step 7 Choose the NIC mapping. By default, the Virtual Appliance comes with 2 NICs. The first NIC is the Management Interface, and you should connect it to a network that allows you to manage the Virtual Appliance. The second NIC is an AUX Interface, and is usually used for clustering, high availability or out-of-path deployments. This interface can be left disconnected if not required. In order to deploy the Virtual Appliance inline, you will need to add additional NICs after deployment. See the Additional NICs section for more information. Then click Next.

19 VMware vsphere (ESX and ESXi) 19 Step 8 Review the information then click Finish to deploy the Virtual Appliance. Once it's deployed, review the following sections on Custom Settings and adding extra NICs and Storage. 6.2 Custom Settings The most common customizations to Virtual Appliances are to increase the number of CPUs and the amount of RAM. By default, all Virtual Appliances come configured with 2 virtual CPUs and 2GB RAM. These should be considered minimum values, however, you can increase these to suit your requirements. From the Exinda Virtual Appliance Properties screen, you can increase the amount of RAM as shown below. You can also increase the number of virtual CPUs as shown below.

20 20 Virtual Appliance Note: You should adjust CPU and RAM settings while the Virtual Appliance is powered off. Adding extra NICs and storage are covered in the following sections. 6.3 Additional NICs By default, all Exinda Virtual Appliances come with 2 NICs. By default, the first NIC is the Management Interface (for managing the Virtual Appliance) and the second NIC is the Auxiliary Interface (for things like HA, clustering and out-of-path deployments). There are 2 options when it comes to placing the Virtual Appliance inline:

21 VMware vsphere (ESX and ESXi) Convert the 2 default NICs into a bridge, so that the Management Interface becomes a LAN Interface and the Auxiliary Interface becomes a WAN Interface. This is achieved by booting into the Virtual Appliance and navigating to the System -> Network -> IP Address page on the Web UI, advanced mode. From this page, you can click the 'br0' checkbox to bridge the 2 default NICs together. In order to manage the Virtual Appliance, an IP Address must be specified for this bridge. Take care when using this option as this will cause the 2 default NICs to be bridged. Note: In order for inline deployments to work correctly under VMware, the virtual switches need to allow promiscuous mode. See Promiscuous Mode for more information. 2. Add 2 extra NICs to be used as LAN and WAN ports. The 2 additional NICs will be bridged and allow the Virtual Appliance to be placed inline. The following steps describe how to add extra NICs to the Virtual Appliance. You need to add extra NICs in pairs, in order to create LAN/WAN bridges. Step 1 From the Hardware tab in the Exinda Virtual Appliance Properties screen, click Add.

22 22 Virtual Appliance Select Ethernet Adaptor, then click Next. Step 2 Select "VMXNET 3" as the Adaptor Type and also choose the network to map this new NIC to.

23 VMware vsphere (ESX and ESXi) 23 Then click Next. Step 3 Review the information and click Finnish to add the NIC. When the Virtual Appliance is next booted, the new NICs will be automatically detected and any additional NIC pairs will be bridged. Below is what the System -> Network -> IP Address page on the Web UI looks like after 2 extra NICs have been added.

24 24 Virtual Appliance Note: You should add extra NICs while the Virtual Appliance is powered off. Note: In order for inline deployments to work correctly under VMware, the virtual switches need to allow promiscuous mode. See Promiscuous Mode for more information Promiscuous Mode Any VMware virtual NIC that is to be used to deploy the Virtual Appliance inline needs to be configured to allow promiscuous mode. This ensures that the LAN and WAN ports are capable of accepting and bridging packets that are not destined for them. In VMware, in the host's Configuration, Networking section, the following changes should be made.

25 VMware vsphere (ESX and ESXi) 25 Step 1 Identify the Virtual Switches that are attached to the NICs that are to be used to deploy the Virtual Appliance inline. Click on the 'Properties' link. Step 2 Note the status of the Promiscuous Mode setting under the Security section. If the value is set to "Accept", there is no need to make any changes. If the value is set to "Reject", continue on.

26 26 Virtual Appliance Highlight the vswitch configuration and click 'Edit...'. Step 3 Navigate to the 'Security' tab and change the value of Promiscuous Mode to "Accept".

27 VMware vsphere (ESX and ESXi) 27 Click 'OK' and repeat these steps for each Virtual Switch that is attached to a NIC that is to be used in an inline deployment. 6.4 Additional Storage By default, all Exinda Virtual Appliances come with a single 50GB (fixed-size) disk. Usually, you will want more storage for features such as WAN Memory and Edge Cache. This is achieved by adding an additional disk to the Virtual Appliance.

28 28 Virtual Appliance The size of the disk you should add largely depends on the amount of RAM allocated to the Virtual Appliance. As a general rule, you should add a maximum of 100GB of disk storage per 1GB of RAM. So if you have given 4GB of RAM to your Virtual Appliance, you can add up to 400GB of extra storage. The steps below describe how to add and provision extra storage. Step 1 From the Hardware tab in the Exinda Virtual Appliance Properties screen, click Add. Select Hard Disk, then click Next. Step 2 Specify the size of the additional disk to create. This space will be added to the default 50GB that comes with the Virtual Appliance. So if you add a 200GB disk here, the total storage for the Virtual Appliance will be 250GB.

29 VMware vsphere (ESX and ESXi) 29 Then click Next. Step 3 Attach the new disk to the next available SCSI node for best performance.

30 30 Virtual Appliance Then click Next. Step 4 Review the information and click Finnish to add the disk. Step 5 When the Virtual Appliance is next booted, you can use the storage commands in the CLI to provision the new storage. The 'show storage' command lists the current storage allocations as well as the Virtual Appliance's disks.

31 VMware vsphere (ESX and ESXi) 31 (config) # show storage Services: cifs: available M free of 3876M total edge-cache: available M free of 3872M total monitor: available M free of 10G total users: available M free of 1024M total wan-memory: available G free of 17.65G total Disks: sda10(internal): in use GB sdb: not in use GB Total: Unallocated: 0 The output shows that our new 200G disk is called 'sdb' and it's currently not in use. The 'storage disk add' command is used to provision the new disk. (config) # storage disk add sdb This will erase all data on the disk. Do you really want to do this (Y/N)? [N] Y After this command has executed, another look at 'show storage' shows that the new disk is now in use and our 200G is ready for allocation. (config) # show storage Services: cifs: available M free of 3876M total edge-cache: available M free of 3872M total monitor: available M free of 10G total users: available M free of 1024M total wan-memory: available G free of 17.65G total Disks: sda10(internal): in use GB sdb: in use GB Total: G Unallocated: 200G For more information on adding disks in general and allocating storage, see the Storage How to Guide. Note: You should add extra disks while the Virtual Appliance is powered off. 6.5 Booting When you're ready to boot the Virtual Appliance for the first time, go ahead and Power it on. The Virtual Appliance will boot, and when ready, will display a login prompt on the VMware console. At this point, you can login with the default username 'admin' and password 'exinda'.

32 32 Virtual Appliance If the first NIC is connected to a network that provides addresses using DHCP, the Virtual Appliance should have picked up an IP address. On the Virtual Appliance summary screen, VMware tools should display the IP address that the Virtual Appliance has obtained. Note: The VMware Tools state 'Unmanaged' is normal. This simply means that VMware Tools are installed and running, but are managed by the guest (the Exinda Virtual Appliance) rather than the host. If the first NIC is not able to obtain an address using DHCP, you'll need to use the VMware console to enter the following CLI commands to set a static IP address. > en # con t (config) # interface eth0 ip address <ip> <netmask> (config) # ip default-gateway <default gateway> (config) # ip name-server <dns server> Once you have determined the IP address or set a static IP address, you can access the webbased user interface by navigating to address>. At this point, the following tasks should be completed before using the Virtual Appliance: 1. Obtain a license for this Virtual Appliance. 2. Add and provision extra storage (if required). 3. Add extra NICs (if required) and deploy the Virtual Appliance either inline or out-ofpath.

33 VMware vsphere (ESX and ESXi) Installing the Silicom Bypass Driver on ESXi Enable SSH on your ESX system. To enable SSH through the CLI: a. In the /etc/ssh/sshd_config modify the following variable: PermitRootLogin yes b. Restart the sshd service. # service sshd restart To enable local or remote TSM from the Direct Console User Interface (DCUI): a. At the DCUI of the ESXi host, press F2 and provide credentials when prompted. b. Scroll to Troubleshooting Options, and press Enter. c. If you want to enable local TSM, select Local Tech Support and press Enter once. This allows users to login on the virtual console of the ESXi host. d. If you want to enable remote TSM, select Remote Tech Support (SSH) and press Enter once. This allows users to login via SSH on the virtual console of the ESXi host. 2. Query the existing VIBs. If the VIB you are deploying (with offline-bundle.zip) exist, you must first remove the existing VIB. Run the following command to determine if any existing VIB matches the VIB you are deploying. # esxupdate --vib-view query grep bpvm If no matches with your VIB, skip the next step. 3. Optional: Remove the existing VIB. # esxupdate remove -b <VIB_ID> --maintenancemode 4. Download the VIB from the following URL: 5. Copy the VIB to the ESX system with SCP. # scp vmware-esx-drivers-net-bpvm oem.x86_64.vib root@<esx-serverip>:/tmp 6. Deploy the VIB on the ESX system. # esxupdate -b /tmp/vmware-esx-drivers-net-bpvm oem.x86_64.vib -- nodeps --maintenancemode --nosigcheck update Note: Ensure that you specify the full path to vib file. 7. Reboot the appliance.

34 34 Virtual Appliance # reboot 8. After the system has restarted, check that the bpvm driver is loaded in the networks adapter list. 9. If the ESXi host is still in Maintenance Mode, exit the same from console or Vmware client. # vim-cmd /hostsvc/maintenance_mode_exit 10. Install Exinda as a Virtual Appliance. 11. For Exinda releases 6.3 and above Bridges with Bypass Capability is displayed on the System->Network Setups->NICs page of the Web GUI. 6.7 Installing the Silicom Bypass Driver on ESXi Enable local or remote TSM from the Direct Console User Interface (DCUI). a. At the DCUI of the ESXi host, press F2 and provide credentials when prompted. b. Scroll to Troubleshooting Options, and press Enter. c. If you want to enable local TSM, select Local Tech Support and press Enter once. This allows users to login on the virtual console of the ESXi host. d. If you want to enable remote TSM, select Remote Tech Support (SSH) and press Enter once.

35 VMware vsphere (ESX and ESXi) 35 This allows users to login via SSH on the virtual console of the ESXi host. 2. Query the existing VIBs. Make sure you are in maintenance mode: # vim-cmd /hostsvc/maintenance_mode_enter If the VIB you are deploying exist, you must first remove the existing VIB. 3. Run the following command to determine if any existing VIB matches the VIB you are deploying. # esxcli software vib list grepbpvm If there are no matches with your VIB, skip the next step. 4. Optional: Remove the existing VIB. # esxcli software vib remove -n net-bpvm # reboot 5. Download the VIB from the following URL: 6. Copy the VIB to the ESX system with SCP. # scp net-bpvm oem x86_64.vib root@<esx-server-ip>:/ tmp 7. Deploy the VIB on the ESX system. # esxcli software vib install -v /tmp/net-bpvm oem x86_64.vib --no-sig-check Note: Ensure that you specify the full path to vib file. 8. Ensure that the bypass driver gets loaded after every reboot by adding the following entry in /etc/rc.local. # vmkload_mod bpvm 9. Reboot the appliance. # reboot 10.After reboot check that bpvm driver is loaded in the networks adapter list

36 36 Virtual Appliance 11.If the ESXi host is still in Maintenance Mode, exit the same from console or Vmware client. # vim-cmd /hostsvc/maintenance_mode_exit 12.Install Exinda as a Virtual Appliance. 13.For Exinda releases 6.3 and above Bridges with Bypass Capability will be displayed on the System->Network Setups->NICs page of the Web GUI.

37 Part VII

38 38 Virtual Appliance 7 Citrix XenServer Exinda Virtual Appliances are available for Citrix XenServer hypervisors. Note: Citrix XenServer 5.5 (or later) is required. The following sections describe how to deploy Exinda Virtual Appliances as well as customize the virtual hardware to suit your requirements. 7.1 Downloading and Installing Step 1 Locate the latest release of the Exinda XenServer Virtual Appliance from the Firmware Downloads section of the Exinda website. Download the ZIP file to your local PC and unzip the Virtual Appliance XVA file. Step 2 Open your Citrix XenCenter client and select File -> Import... Then, select the unzipped Virtual Appliance XVA file. Click Next. Step 3 Select the target XenServer to deploy the Virtual Appliance.

39 Citrix XenServer 39 Then click Next. Step 4 Choose the storage location for the Virtual Appliance. By default, the Virtual Appliance comes with a single, 50GB disk. Additional storage can be added in the form of another disk after the Virtual Appliance has been deployed. See the Additional Storage section for more information. Then click Next. Step 5

40 40 Virtual Appliance Choose the NIC mapping. By default, the Virtual Appliance comes with 2 NICs. The first NIC is the Management Interface, and you should connect it to a network that allows you to manage the Virtual Appliance. The second NIC is an AUX Interface, and is usually used for clustering, high availability or out-of-path deployments. This interface can be left disconnected if not required. In order to deploy the Virtual Appliance inline, you will need to add additional NICs after deployment. See the Additional NICs section for more information. Then click Next. Step 6 Review the information and uncheck the 'Start VM(s) after import' box if you want to add extra NICs or storage.

41 Citrix XenServer 41 Click Finish to deploy the Virtual Appliance. Step 7 Select the Exinda virtual machine you are importing, and switch to the Log tab to see the progress and the completion notification. It is highly recommend that you import the virtual machine on a Gigabit network connection or local storage, as the import file is large in size and installation is affected by slowly performing networks. Step 8 Right-click the imported Exinda and select Start the Exinda virtual appliance. You will see the progress bar screen below in the Log tab indicating you have successfully started the virtual appliance.

42 42 Virtual Appliance Step 9 On the XenCenter Console tab of the Exinda virtual machine, enter the credentials and the default parameters as part of the first time wizard setup. The default user name is admin, and the password is exinda. Step 10 Press Enter to read the EULA agreement. Press Ctrl-C to get to the EULA agreement question. Step 11 Press Y to accept the EULA agreement and press Enter.

43 Citrix XenServer 43 Step 12 You will prompted with a series of questions as part of the initial configuration Wizard. It is recommended you accept the defaults, as you have the option to configure the system later from the Exinda GUI. Press Yes. Use the following defaults to complete the wizard configuration. a. Select No to disable IPv6. b. Select Yes to configure ETH0 for management access. This will disable the BR0 bridge. c. select Yes to use DHCP on ETH0. d. select null to default to the Exinda hostname. e. select null for SMTP server address. f. select null for address for reports and alerts. g. select null to use the default password which is exinda. h. select Yes to change the interface speed.

44 44 Virtual Appliance i. select AUTO to configure the interface speed on ETH0 (assumes a gigabit NIC). You have successfully completed the wizard setup. Step 13 Determine the IP address of your Exinda virtual appliance on the XenServer Network tab of the Exinda virtual machine and note IP address assigned by default to NIC 0. Step 14 Browse to the Dashboard tab and find the Host-ID that the XenServer host created for this virtual machine. Once the appliance is deployed, review the following sections on Custom Settings and adding extra NICs and Storage. 7.2 Custom Settings The most common customizations to Virtual Appliances are to increase the number of CPUs and the amount of RAM. By default, all Virtual Appliances come configured with 2 virtual CPUs and 2GB RAM. These should be considered minimum values, however, you can increase these to suit your requirements.

45 Citrix XenServer 45 From the Exinda Virtual Appliance Properties screen, you can increase the number of virtual CPUs and the amount of RAM as shown below. Note: You should adjust CPU and RAM settings while the Virtual Appliance is powered off. Adding extra NICs and storage are covered in the following sections. 7.3 Additional NICs By default, all Exinda Virtual Appliances come with 2 NICs. By default, the first NIC is the Management Interface (for managing the Virtual Appliance) and the second NIC is the Auxiliary Interface (for things like HA, clustering and out-of-path deployments). There are 2 options when it comes to placing the Virtual Appliance inline:

46 46 Virtual Appliance 1. Convert the 2 default NICs into a bridge, so that the Management Interface becomes a LAN Interface and the Auxiliary Interface becomes a WAN Interface. This is achieved by booting into the Virtual Appliance and navigating to the System -> Network -> IP Address page on the Web UI, advanced mode. From this page, you can click the 'br0' checkbox to bridge the 2 default NICs together. In order to manage the Virtual Appliance, an IP Address must be specified for this bridge. Take care when using this option as this will cause the 2 default NICs to be bridged. 2. Add 2 extra NICs to be used as LAN and WAN ports. The 2 additional NICs will be bridged and allow the Virtual Appliance to be placed inline. Note: You need to add extra NICs in pairs, in order to create LAN/WAN bridges. From the Networking tab in the Exinda Virtual Appliance settings, click Add Interface...

47 Citrix XenServer 47 Choose the network to map this new NIC to, then click Add. When the Virtual Appliance is next booted, the new NICs will be automatically detected and any additional NIC pairs will be bridged. Below is what the System -> Network -> IP Address page on the Web UI looks like after 2 extra NICs have been added.

48 48 Virtual Appliance Note: You should add extra NICs while the Virtual Appliance is powered off. 7.4 Additional Storage By default, all Exinda Virtual Appliances come with a single 50GB (fixed-size) disk. Usually, you will want more storage for features such as WAN Memory and Edge Cache. This is achieved by adding an additional disk to the Virtual Appliance. The size of the disk you should add largely depends on the amount of RAM allocated to the Virtual Appliance. As a general rule, you should add a maximum of 100GB of disk storage per 1GB of RAM. So if you have given 4GB of RAM to your Virtual Appliance, you can add up to 400GB of extra storage.

49 Citrix XenServer 49 From the Storage tab in the Exinda Virtual Appliance settings, click Add... Specify the size of the additional disk to create. This space will be added to the default 50GB that comes with the Virtual Appliance. So if you add a 200GB disk here, the total storage for the Virtual Appliance will be 250GB. Then click Add. The Virtual Appliance storage should look something like this: When the Virtual Appliance is next booted, you can use the storage commands in the CLI to provision the new storage. The 'show storage' command lists the current storage allocations as well as the Virtual Appliance's disks.

50 50 Virtual Appliance (config) # show storage Services: cifs: available M free of 3876M total edge-cache: available M free of 3872M total monitor: available M free of 10G total users: available M free of 1024M total wan-memory: available G free of 17.65G total Disks: xvda10(internal): in use GB xvdb: not in use GB Total: Unallocated: 0 The output shows that our new 200G disk is called 'xvdb' and it's currently not in use. The 'storage disk add' command is used to provision the new disk. (config) # storage disk add xvdb This will erase all data on the disk. Do you really want to do this (Y/N)? [N] Y After this command has executed, another look at 'show storage' shows that the new disk is now in use and our 200G is ready for allocation. (config) # show storage Services: cifs: available M free of 3876M total edge-cache: available M free of 3872M total monitor: available M free of 10G total users: available M free of 1024M total wan-memory: available G free of 17.65G total Disks: xvda10(internal): in use GB xvdb: in use GB Total: G Unallocated: 200G For more information on adding disks in general and allocating storage, see the Storage How to Guide. Note: You should add extra disks while the Virtual Appliance is powered off. 7.5 Booting When you're ready to boot the Virtual Appliance for the first time, go ahead and Power it on. The Virtual Appliance will boot, and when ready, will display a login prompt on the XenCenter console. At this point, you can login with the default username 'admin' and password 'exinda'.

51 Citrix XenServer 51 If the first NIC is connected to a network that provides addresses using DHCP, the Virtual Appliance should have picked up an IP address. On the Virtual Appliance Networking screen, XenCenter should display the IP address that the Virtual Appliance has obtained. If the first NIC is not able to obtain an address using DHCP, you'll need to use the XenCenter console to enter the following CLI commands to set a static IP address. > en # con t (config) # interface eth0 ip address <ip> <netmask> (config) # ip default-gateway <default gateway> (config) # ip name-server <dns server> Once you have determined the IP address or set a static IP address, you can access the webbased user interface by navigating to address>. At this point, the following tasks should be completed before using the Virtual Appliance: 1. Obtain a license for this Virtual Appliance. 2. Add and provision extra storage (if required). 3. Add extra NICs (if required) and deploy the Virtual Appliance either inline or out-ofpath.