ENDIAN 4i-edge-virtual-x64 6.8.0


-------------------------
Installation Instructions
-------------------------

When unzipping the .zip file you will get a directory containing
many files. The list will look similar to the one below:

  endian_4i-edge-virtual-x64_6.8.0/
  endian_4i-edge-virtual-x64_6.8.0/endian_4i-edge-virtual-x64_6.8.0_virtual_softwarex86-64.mf
  endian_4i-edge-virtual-x64_6.8.0/endian_4i-edge-virtual-x64_6.8.0_virtual_softwarex86-64.ovf
  endian_4i-edge-virtual-x64_6.8.0/endian_4i-edge-virtual-x64_6.8.0_virtual_softwarex86-64.vmdk
  endian_4i-edge-virtual-x64_6.8.0/License.txt
  endian_4i-edge-virtual-x64_6.8.0/Readme-Xen.txt

The .ovf file contains an XML specification of the virtual applianc
in the Open Virtualization Format which can
be imported by the latest versions of Citrix XenServer.
The .vmdk file is the XenServer hard disk that contains the 
installed appliance.
The .mf file contains SHA1 checksums of the two above mentioned
files. These checksums can be used to verify the integrity
of the files.
The License.txt file contains the ENDIAN End User License Agreement.
The Readme-Xen.txt file contains this text.


Installing the .ovf file to XenServer
=====================================

This is the recommended installation procedure.
If you have a product that supports the Open Virtualization
Format, such as Citrix XenServer (5.6 or higher) you can simply
import the .ovf file by selecting *Import...* from the File menu.
When going through the wizard you can choose to check the manifest
file (i.e. the .mf file that is part of this package).
Note that it is not necessary to run operating system fixups.
After the wizard has finished you are ready to launch your appliance.


Installing the .vmdk file to a Xen host system
=============================================

If you do not use Citrix XenServer in your Xen environment you
can still use the paravirtualized appliance. However,
there are a few steps that have to be followed.

1. Convert the file to a RAW disk image. This can be done with
   various tools. An excellent tool is qemu-img that comes with
   the qemu hypervisor which is available in almost every linux
   distribution or can be downloaded from qemu.org.
   The convert command looks like this:

   qemu-img convert endian_4i-edge-virtual-x64_6.8.0_virtual_softwarex86-64.vmdk \
        endian_4i-edge-virtual-x64_6.8.0_virtual_softwarex86-64.raw

   Note that converting the .vmdk file to a raw disk image will
   result in a new file that occupies ca. 60 GBytes on your hard
   disk.

2. Configure the virtual machine in your Xen environment.
   On Red Hat Enterprise Linux you can do this by running the 
   virt-install command like this:

   virt-install -n "ENDIAN 4i-edge-virtual-x64" -r 1024 -f \
                /root/endian_4i-edge-virtual-x64_6.8.0_virtual_softwarex86-64.raw \
                --os-type=linux --import -p

   You can also configure the virtual machine manually in the
   /etc/xen directory. A sample configuration would look like the
   following:

   name = "ENDIAN 4i-edge-virtual-x64"
   uuid = "b6cdfc8e-0667-6ca1-f249-91320a13b0ac"
   maxmem = 1024
   memory = 1024
   vcpus = 1
   bootloader = "/usr/bin/pygrub"
   on_poweroff = "destroy"
   on_reboot = "restart"
   on_crash = "restart"
   vfb = [ "type=vnc,vncunused=1,keymap=en" ]
   disk = [ "file:/root/endian_4i-edge-virtual-x64_6.8.0_virtual_softwarex86-64.raw,xvda,w" ]
   vif = [ "mac=00:16:36:15:10:64,bridge=xenbr0,script=vif-bridge" ]

3. Start the virtual machine
   If you named your configuration file /etc/xen/VirtualAppliance you can
   start the virtual machine by calling:

   xm create VirtualAppliance

   Obviously you can also start the virtual machine from one of the
   various virtual machine management tools like *Virtual Machine
   Manager*.


----------------------
Additional information
----------------------

- This virtual machine comes already pre-installed. When booting for
  the first time, the machine will be adapted to Xen. Once this has
  been done the machine will perform a reboot. After the
  reboot the machine will be configured using a DHCP client on the 
  GREEN interface.
  This means, that if there is a DHCP server running in your GREEN
  zone you will then be able to access the virtual appliance
  on the newly assigned IP address.
  If you do not have the possibility to find out which IP address
  has been assigned to the system you can use your Xen console
  to login with the default password and then execute the
  command that will show you the IP address. This procedure looks
  like the following:

    > login
    enter root@hostname's password:
    > ip a show br0
    2: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> ...
        link/ether 00:3d:42:ec:72:1a brd ff:ff:ff:ff:ff:ff
        inet 192.168.0.15/24 brd 192.168.0.255 scope global eth0
        inet6 fe80::21d:92ff:feec:521a/64 scope link 
           valid_lft forever preferred_lft forever

  Once you found out the IP address you can configure the system
  by connecting to https://<IP_ADDRESS>:10443. There you can then
  define the static GREEN IP address you want to use.

- Connecting to the virtual machine's console when not running XenServer
  To connect to the console you can call:

  xm console VirtualAppliance

  Note that when using *Virtual Machine Manager* to see the console of
  the virtual machine you must select *Serial Console* in the *View*
  menu.
