To use LBL Global Distributed Gateway in version VAPP is enough to have performed the installation and assigned addresses to network interfaces. You can check if the addresses have been configured correctly through the console of the VAPP reachable with virtualization system used by typing your login and password:
The default login and password of Virtual Appliance:
Type: lblsetup, you will be prompted for your root password: adminadmin
Then check the address on which it is possible to connect the browser for configuration e.g.:
Then connect from your desk with the browser to port 4444 es.: https://192.168.56.11:4444
The authentication request, type the user name and password specified in the character console, optionally repeat es.:
You will see the Dashboard to start the task:
LBL Dashboard interface is designed to be used on all terminals available today that support HTML 5.
The Dashboard is composed by a component of choice visible or can be activated depending on the size of the screen. You can also use large monitors useful in the control room of the datacenter.
LBL Global Distributed Gateway has licenses inside it that allow its use in the foreseen cases.
In order to perform the first setup choose ADC Settings >ADCs:
Once you have selected the “ADCs”, the system will display the ADC systems available including configurations template. In the case of distributed installations, you will see all the modules can be reached which has made the registration and to which you are entitled to management based on the privileges. The system provides a global vision of the routing application.
In this case will display the three types of available deploy more configurations template: Enterprise has (Grid), Platform (single instance), Standard has (Active stand-by/mutual fail- over), templates (Templates with the most widespread rules and types of routing). The form on which we are going to perform the first routing is the platform version that is automatically activated at the start of the VAPPS.
First, we are going to set up the service from balance by creating a group of services.
Being the first service, we will create the first endpoints group with the + button:
Choose the form on which you want to add the new group, in this case A10_LBLGoPlatform:
Once you have clicked OK, set a mnemonic name of the group you want to create, e.g.: http_https
Then click OK. The new group will appear in the list of groups. At this point, press the edit key:
Expand virtual domains to which for the moment does not indicate anything and thus will not be any control on domain name or address required. Once you open the virtual domains, enter Popular services that you want to balance …
As soon as you enter the detail of managed services from virtual domains you can type the services of back-end by expanding the details of endpoints:
To enter the services of the backend is sufficient to enter the following parameters:
Once you have configured the endpoint, in this case a Tomcat, it is necessary to configure the listener that will accept connection requests from route on the group of services.
Again choose ADCs and then enabled listeners:
Appears an empty list of listeners, press the + button to add a listener:
You will be prompted on which module add a listener and choose A10_LBLGoPlatform:
Enter the description of the listener, the address and the port on which you will listen and the group of services that will refer, in this case choose http_https, the newly created group:
At this point it is sufficient to follow the link for saving data:
We will highlight the modified configurations up to this moment. You can proceed with the save:
It is possible to indicate the reason for editing, all changes are saved in order to be restored or otherwise verified in case of need.
Na after saving it is proposed to make it operational. You can then make changes and save them and make them operational in different moments.
In the section “Reinit” will display all the saved configuration that can be made operational. By pressing the button “Reinit” the configuration will be rendered operative:
If there are no other modified configurations, the browser will not show other configurations to re-initialize.
If the specified service is reachable, check with a browser:
To set the first listener HTTPS in keeping the backend in HTTP, it is sufficient to use a template already prepared and then, once operational, edit it in the essential parameters, typically with its digital certificate:
Choose ADCs and follow the link enabled listeners of the template:
The system proposes a series of preset listeners from the factory with the most popular protocols. In order to use them is sufficient to press the button Copy and then select the form on which you want to copy the template:
Select A10_LBLGoPlatform from the pulldown menu and on subsequent confirmation:
Returning to the ADCs you will notice that the indicator Enabled listeners will return 2 elements:
By following the link will be displayed the two listener, one of which is derived from the template on which we are going to change address:
In addition to changing the address, you can check sslparams that we leave for this exercise unchanged. LBL®Global Distributed Gateway contains some certificates self-signed that are used for this first routing ssl. below highlights the address of listening SSL amended.
To use your own SSL Certificate You can upload through the panel SSL with simboloposto to the right of the field Path
As for the previous parameters, proceed with the rescue and Reinit configuration:
Once the Reinit go to the browser and change from http to https:
If this is the first time you log in to the service, the browser will inform you that the certificate is self-signed, choose Advanced, add exception and then Confirm Security Exception
The browser will proceed with the request and will then be delivered service in HTTPS