Setting up the IVS (Imaging Virtual Server)

Subnets

The FileWave Imaging appliance has to be configured as an “ip-helper” on your switches so it can receive and answer BOOTP requests from your clients.

The FileWave network imaging solution is unicast so there will need to be some preparation on your end if you intend to image across multiple subnets. The two options will be:

A. Install a separate FileWave Imaging Virtual Server (IVS) on each subnet you plan to image from and connect them all to the FileWave server by following the "Connecting IVS to FileWave Server" section in this document.

B. Setup "Helper IPs" on your layer 3 devices (e.g. routers, routing switches) that will point the broadcast requests for PXE and Netbooting to your single FileWave IVS. Once this has been completed you will need to make a change on the IVS. To do this either open the console for this server in your virtual environment or ssh into the server with Putty (Windows) or terminal (macOS):

1. 1. Open terminal (If on Windows you can use Putty linked here and use the credentials root/filewave (FileWave 15.4.2 and older) or fwadmin/filewave (FileWave 15.5.0 and beyond) then skip to step 3 below)
      

      # replace IVS-IP-Address with your IP address
      # replace fwadmin with root if your Appliance is pre-15.5.0
      $ ssh fwadmin@IVS-IP-Address 

   2. Type the following command

   3. # enter in imaging-control subnet add to add your subnet addresses
      $ imaging-control subnet add

   4. This will prompt for a valid IP address from the subnet and subnet mask
      Note: use command imaging-control subnet remove to remove a subnet

Firewall

The IVS needs to be able to connect to your FileWave Server on the following Ports

• 20017

• 20443

• 20445

Any client(s) subnets where imaging should work must be able to reach the following Ports on the IVS:

• 67 (DHCP), 69 (TFTP), 80 (HTTP), and 20444 (HTTPS)

• Ports 111 (TCP,UDP) and 20490 (TCP,UDP) are used for VPN to NFS access

Prior to FileWave 15.5.0 port 2049 TCP/UDP was used for a client to reach the NFS mount, but with 15.5.0 a VPN connection is made on 20490 TCP/UDP and then allows access to the mount.

Any machine running FileWave Central needs to be able to connect to your IVS on the following Ports:

• 20010 (Client Monitor), 20444 (Remote Configuration, Shared Keys)

The FileWave Server must be able to reach the IVS on port 20444 for On-Premise customers.

Login to the IVS (either console or SSH) and change the default password from what is currently filewave to your own.

1. Type in the following command, when prompted for a password use 'filewave':

    

   # replace IVS-IP-Address with your IP address
   $ ssh root@IVS-IP-Address

2. Then type the command below to enter your new password

    

   $ passwd

3. Enter new password
   

1. Locate Network Interface:

First, identify the network interface you wish to configure. You can list all network interfaces using:

networkctl list

2. Edit the /etc/network/interfaces file: Using 'nano', edit the interfaces file to set the network configurations.

nano /etc/network/interfaces

Your default interfaces file should look something like this (your interface name may be different):

# The loopback network interface
auto lo eth0
iface lo inet loopback


# The primary network interface
iface eth0 inet dhcp

Change the file to look like this, using your network preferences (note 'dhcp' has been changed to 'static' in line 6)

# The loopback network interface
auto lo eth0
iface lo inet loopback


# The primary network interface
iface eth0 inet static
address 192.168.10.33
netmask 255.255.255.0
gateway 192.168.10.255
dns-nameservers 192.168.10.254 192.168.10.255

3. Verify Resolv.conf, hosts and hostname files: Verify that these files in /etc/ are configured correctly for your network and server.
/etc/resolv.conf: This file should list your DNS servers

/etc/hosts: This file should point your FQDN to localhost (127.0.0.1) - Below is an example of what the file looks like on ivs1.filewave.net for example. Notice the 2 entries for loopback. Although IPv6 should be disabled, it is good to include the IPv6 loopback in case it is ever enabled. 

127.0.0.1       localhost
::1             localhost ip6-localhost ip6-loopback
ff02::1         ip6-allnodes
ff02::2         ip6-allrouters
127.0.0.1       ivs1.filewave.net
::1             ivs1.filewave.net

/etc/hostname: Specifies the hostname for your server. This is filewave by default.

4. Disable IPv6: Edit the sysctl.conf file by adding the following lines to the end of the file:

nano /etc/sysctl.conf

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
net.ipv6.conf.tun0.disable_ipv6 = 1

5. Restart/Check Network Status:

systemctl restart networking.service

systemctl status networking.service

6. Verify IP:

ip a