VAPP setup

Back

Preparing to Install

To install LBL Global Distributed Gateway in version VAPP is sufficient to perform the download through the web site.

Compatibility Matrix

Vapps  distributed and available directly from the downloads are for the most widespread virtual platforms on the market today, other virtual images may be requested via e-mail: customercare@oplon.net.

Images available directly from the site:

  • VMware¬†(with OS basic¬†“Powered by¬†CentOS”¬†or¬†“Powered by¬†Ubuntu”)
  • Microsoft Hyper-V¬†(with OS basic¬†“Powered by CentOS” or “Powered by Ubuntu”)
  • Virtual Box¬†(with OS basic¬†“Powered by CentOS” or “Powered by Ubuntu”)

It is also available a¬†VAPP¬†destined to the development of rules and classes of¬†rewriting¬†LBL¬†R9GDG Developer¬†(on¬†OS¬†basic¬†“Powered by¬†Ubuntu”).

WANING:
In order for the installation is supported check the compatibility matrix on the white paper document or Web site

Compatibility Matrix: of Operating System Modules and Services

Vapps  are arranged with the services necessary for the operation of the system LBL S.A.A.I. nevertheless you can install other features to the base operating system previously verified the coexistence of the modules with the services provided by the platform LBL S.A.A.I.

WANING
LBL ADC requires for each Operating System only services related to reachability (SSHD for Unix / Linux Operating Systems, Windows Desktop Console for MS Windows Operating Systems) and Ethernet connectivity and basic network services (TCP / IP, UDP, ICMP , MULTICAST). Other services like firewall e-mail services application server etc. they are not necessary to LBL ADC for its operation and they concur in the use of the same resources or, as in the case of firewalls, they carry out very heavy operations on data traffic. In these cases all the modules must be configured to obtain the maximum result from the resources present and commensurate with the traffic they must sustain.

Virtual Appliance import

The import of VAPP is facilitated by the instruments of virtualizing systems. Each system virtualization provides a console to perform the operation.

Once imported the VAPP the system is ready to perform your first setup compatibly with the datacenter environment.

Note: During import it is important to take care to choose, in the different systems of virtualization, an import with regeneration of the MAC address of the virtual adapters. In this way the virtual machines will not come into conflict.

Virtual Appliance VM Guest OS setup

Once imported the VAPPS in virtualization system it is necessary to insert it in the operational context.

The parameters that are to be taken into consideration are the dimensional type (sizing) and the context of the existing network.

Below in a synthetic manner the parameters to be monitored prior to import and the start of the virtual instance:

  1. RAM memory (default 4096 MB)
  2. Number of CPUS (default 1 CPU *Core)
  3. Virtual Network Interface (default 1 VNICS)
  4. HDD 40GB Thin Provision

Once verified these parameters it is possible to perform the start of virtual machine.

For network settings check:

For distribution with underlying OS Ubuntu: official documentation

(Generically /etc/network/interfaces)

For distribution with underlying OS CentOS: And tool available from console # nmtui

Virtual Appliance configuration

After the start of virtual machine the system part in character mode for all VAPP production, in graphical mode for VAPPS development. In this document you will take into consideration the VAPP destined to the production.

To start the system will require a login and password for administrative purposes:


Login : administrator

Password: adminadmin

Just typed login and password, the console will suggest available commands.

With the command lblhelp you can request a list of the available functions.

Performing lblsetup the system will require the setting of the administrator password. The VAPP is preset with the password: adminadmin

The initial configuration system has been reduced to a minimum in the console to allow a simple setting of functions with which then connect through LBL Global Distributed Gateway where it is possible to carry out the extended configuration. By default the console running a bind on all available addresses:

The following explanation of the requests made by the console:

Management Address: (Default 0.0.0.0)

  • Is the address to which you can connect from the outside with¬†LBL Management¬†Console

Management port: (54443 default)

  • Is the port from which it is possible to connect from the outside with¬†LBL Management¬†Console

Global Distributed Gateway final port (default 4444)

  • Is the port from which it is possible to connect from the outside with¬†LBL Global¬†Distributed Gateway. You can change this port through the web console of the process Global Distributed Gateway.

Type LBL root username and password:

  • Is the setting of the Administrator login¬†root¬†with sdar√† which can perform from¬†LBL Management¬†Console the full setup and set or delete other users

Type the primary system name and password for system delegation.

  • Set the login user password¬†delelgato¬†primary to perform operations between multiple systems¬†LBL S.A.A.I.¬†(it is recommended to set up a login is associated with a password of only the knowledge of the staff assigned to security or otherwise not available to all staff. For more information¬†in the case of particular critical installation check the manual¬†LBL_AutonomousDelegatedAuthentication)

Note: The setup program will automatically leave after 3 minutes from the start.

For safety reasons, we advise you to change the address, login and password with respect to the default indicated.

Once set login and password it is possible to perform the output with saving.

WANING
When the management address or port is changed, a monitor restart command must be performed. You can do this from the console through the command:

# lblrestart

The lblrestart command takes about 60 seconds to run. In this period of time the LBL S.A.A.I. it is not operational.

Setting the Date and Time timezone of the operating system

LBL Global Distributed Gateway is not sensitive to time differences on the nodes during the operation. Nevertheless if during operation you may change the date and time of the system some considerations could be distorted as for example calculations of time-out, lease time or considerations on dates of repository (es.: date of the version of the repository of georeferencing).

As far as described it is therefore advisable to set the date and time of the system with values as close as possible to the current date and time. The use of the alignment using NTP is recommended.

To change the timezone is available command lbltimezone that, in dependence of the base operating system used, will have its own interface to setup or directions to make the change.

WANING:

If installation with licenses to rental (rent licensing) setting the date and time are critical to the operation of the products

Setting the keyboard of the operating system

To change the keyboard of the console is available command lblkeyboard that, in dependence of the base operating system used, will have its own interface to setup or directions to make the change.

Based CentOS:

Based Ubuntu:

First login from LBL Global Distributed Gateway

From the console it is possible to check the current configuration and DHCP address associated through normal Linux commands (ip addr).


The system LBL Monitor and LBL Global Distributed Gateways are by default set up to accept connections from all networks.


It is therefore sufficient to, check with the command “ip addr” an available address and log in from LBL Management¬†Console, LBL Web Console¬†or from¬†LBL Global¬†Distributed Gateway on the specified address es.:

To access the services LBL Global Distributed Gateway type: Https://x.x.x.x:4444

(Where x.x.x.x is any address of the system if you have not changed the address 0.0.0.0 or the address you have chosen with lblsetup).


If not modified in phase of setup: login: root

Names and conventions LBL Global Distributed Gateway

The following are the conventional names of the areas used by the graphic interface to which all documentation refers.

  • Content
  • System¬†bar
  • Panel
  • Navigation¬†bar
  • System
  • Content
  • Panel