Follow

redBorder Manager Installation Guide (Community edition)

INDEX

 

Chapter 1: Requirements for the redborder community platform

Before installing redborder Community Manager, consider the following hardware and connectivity requirements.

Hardware requirements

redborder Community Manager can be installed on:

  • Physical machine (redborder appliance or general purpose machine).
  • Virtual machine.

Installation in virtual environment is permitted, having in mind the above specification. The following hypervisors are suggested:

  • Oracle VM VirtualBox
  • VMware Workstation
  • VMware vCenter

The recommended minimum requirements for installing RedBoder Community Manager on a physical or virtual machine for a non-critical environment that handles a smaller volume of information:

  Minimum Recomended

RAM

8 GB

16 GB

CPU

2 cores

4 cores

HDD

24 GB

100 GB

NIC

1

2*

Redborder, in order to separate the administration access and data flow, permits the usage of two separated network interfaces.

The Intrusion and Traffic requirements in the Manager are the same since both work on a basic configuration of redBorder. The requirements mentioned above are minimum requirements for it to work in a basic environment. The recommended requirements will depend on the sizing of the environment, and this has been developed according to the number of events per second shown below:

Click here to see the Table of hardware requeriments scaling.

 

It must be taken into account that these requirements are the minimum necessary for the Community Manager to be able to operate in a light and non-critical environment.

peligro.png 

For environments of some criticality, please contact the redborder team.

Connectivity requirements

redborder Community Manager only needs to be able to communicate with its sensors and with the administrators who must access it. Therefore, the necessary connectivity is:

 

requirements-01.png
Figure 1. Connectivity requirements
 

 

Chapter 2: Getting the ISO

Before installing redborder Community Manager, consider the following hardware and connectivity requirements.

Request your system image

For the installation of the Community Manager redborder, the user can request from the redborder website an ISO image that can be used to deploy the software on the desired equipment.

request_rb_community.JPG
Figure 2. Request the community edition
 

Burning / handling the ISO Image

  • In case of installation on physical machine, it is possible to record the image on a DVD or USB storage device to proceed with its installation
  • In case of installation in virtual machine, it will be enough to mount the image in a virtual DVD device.

Linux / Unix

In order to burn the ISO image from a Linux system to a USB device, the following command needs to be used if the USB device is mapped in /dev/sdd:

[root@machine ~]# dd if=redBorder-3.1.68-1-x86_64-6.5-community.iso of=/dev/sdd bs=10M

Windows

In order to burn the ISO image from a Windows system to a USB device, the following 3rd party program may be helpful - Rufus

Chapter 3: Installation

As soon as the redborder ISO boots the Welcome screen apears.

 

install-01.png
Figure 3. Welcome screen of the RedBoder Community Manager installation wizard
 

Select Install Community Manager to begin the process of installing the Redborder Community Manager.

 

install-02.png
Figure 4. Installation Wizard: Install Community Manager
 

Once this page has been confirmed, the installation will carry out all of the necessary processes to prepare the system for configuration.

Complete the following basic settings and continue.

tip2.png  redborder is prepared for unattended installations and so we should be especially careful with the time we have to respond to the configurations questions (if we wish to modify the default options).
  • Disk selection

 

04.png
Figure 5. Basic settings: disk selection
 
  • Password selection

Default password: redborder

 

install-04.png
Figure 6. Password selection
 

Once the basic settings are completed, the installation of the Community Manager redBorder starts automatically.

 

install-05.png
Figure 7. Installation of system packages
 

After completing the installation, the system will restart automatically.

 

install-06.png
Figure 8. System restart after installation of system packages
 

 

Chapter 4: Configuration

Once the system is restarted, the process of automatic configuration of the Community Manager redborder begins.

 

config-01.png
Figure 9. Automatic configuration of RedBoder Community Manager
 

After completing the automatic configuration, the login window appears, where you can enter the credentials of the system:

 

config-02.png
Figure 10. Request for credentials to access the system
 
  • User: the one entered during installation process [default: root]
  • Password: the one entered during installation process [default: redborder]

 

systemReady.png
Figure 11. system ready for comand

 

Through the rb_sysconf command it is possible to access the redborder configuration menu. Once inside the system, we will start the configuration manager. To do this we will execute:

[root@rbmanager ~]# rb_sysconf

 

config-03.png
Figure 12. rb_sysconf command

In the configuration we have several options:

 

rb_sysconf_Main.png
Figure 13. execution of rb_sysconf command

 

System configuration 1)

To start the configuration we begin with option 1 - System configuration:

 

rb_sysconf_systemConfig.png
Figure 14. System configuration options
 
  • Option 1 - Hostname: we must enter the host name of the machine where redborder has been installed.
  • Option 2 - Set local time: allows us to indicate a local time for the system.
  • Options 3 y 4 let us configure parameters (not included in this guide).

Returning to the main menu, in option 2 - Network configuration we will have to configure everything related to the network environment:

Network configuration 2)

Upon completing the installation process, we have two configuration options depending on whether or not there is a DHCP server.

  1. Dynamic IP (DHCP): in this case, redborder will have acquired an IP in its network interface and will have auto-configured in order to operate in said address.
  2. Static IP: in this case redborder will not have configured and we will have to access the system in order to perform the configuration. To gain access we will use the root user and the password we selected during the installation.

Once inside the redborder configuration menu, select option 2 (Network configuration) to access the network configuration menu.

 

config-04.png
Figure 15. Redborder configuration menu: selection of Network configuration
 

From the network configuration menu it is possible to set the management interface, the DNS and the domain.

 

config-05.png
Figure 16. Redborder network configuration menu
 

Configuration of the management interface

With DHCP

peligro.png  If the network in which the management interface is located has DHCP, it is not necessary to access (option 1) Management Network configuration, since the automatic configuration process that was previously executed must have correctly configured this interface.
tip2.png  Enter the command 'ip a' from the system CLI to know the assigned IP address. In the example below, you can see how the IP assigned by DHCP for the management interface bond0 is 10.0.150.101.
config-06.png
Figure 17. Output of the ip command to: IP address of the management interface bond0

 

Without DHCP

If the network in which the management interface is located does not have DHCP, or you do not wish to automatically manage IP settings, it is necessary to configure this interface. Select (Management Network configuration) to configure the management interface.

config-07.png
Figure 18. Redborder network configuration menu: selection of Management Network configuration
 

In this menu a list of existing bondings appears, so after installation and automatic configuration it should be empty, as shown in the image below.

 

config-08.png
Figure 19. Management network configuration menu
 

Select option n to add a new bond and enter the parameters that are requested.

When we select the option n, we are asked for:

  • Insert bonding number [0] : The default value is "0" and indicates the link index (at redBorder we use redundant links called bonding).
  • Insert bonding first port [0] : The default value is "0" and allows us to indicate the network port index to use in the management link.
  • Insert second port (y/N) : If only one port is needed for management, use the default value "N".
  • Insert management IP address: We will enter the IP that we want to assign to redborder.
  • Insert management Netmask: We will enter the network mask that we want to assign to redborder.
  • Insert default gateway for this management interface (Y/n): Indicates whether or not we want to assign a link port to redborder. Por defecto indicaremos Y.
  • Insert default gateway []: We will enter the gateway IP address.
  • Insert a route for this bonding (y/N): Indicates whether or not we want to indicate a route for the link created. By default we will indicate "N".

You can see in the image below that the default option is to include a single management interface in the bonding (Insert second port (y / N)?).

information.png To provide redundancy, it is possible to form bondings with 2 management interfaces each. If redundancy is not desired, a bonding should also be formed, even if using a single management interface.
config-09.png
Figure 20. Management network configuration menu: Bonding 0 created successfully
 

The new bonding created now appears in the previous list. Also, it is indicated that for the changes to take effect, the configuration must be applied. This will be done at the end of the network configuration process.

 

config-10.png
Figure 21. New bonding created
 

Once the link is created, we return to the Management Network configuration menu and select: option 2 DNS and domain settings

Domain and DNS settings

The next step will be to configure the DNS and the domain. For this, it will be necessary to return to the previous menu with the option q and select the option 2 (DNS and domain settings).

 

config-11.png
Figure 22. Network configuration menu: DNS and domain settings
 

Finally, it is necessary to apply the network changes. To do this, from the network configuration menu, enter option a to apply the changes.

 

config-12.png
Figure 23. Network configuration menu: apply
 

The wizard will begin to apply the changes made and show the result of the changes. At this time we will see that several operations are executed. Please be patient because this process may be lengthy depending on the machine’s hardware.

 

config-13.png
Figure 24. Network configuration menu: applying changes
 

Once the change application process has finished, the wizard returns to the main screen of the network configuration menu. Select the option to return to the main configuration menu.

 

config-14.png
Figure 25. Network configuration menu: quit
 

And again the option to exit the redborder configuration menu.

Returning to the main menu, we have option 3 - Passwords. Within this option we can modify the different passwords used by default for the different users. Remember that the default password is redborder.

 

rb_sysconf_backUpConfig.png
Figure 26. Passwords Menu
 

The detailed description of this menu is outside of the scope of this Community edition guide.

 

config-15.png
Figure 27. Redborder configuration menu: quit
 

The redborder Community Manager configuration process has finished, so you can now logout.

 

config-16.png
Figure 28. System CLI: exit
 
information.png  Once we have carried out all of the previously described configuration steps, it is required (in function of your machine performance) to give from 5 to 10 min to the system to get running all necessary services. Once this time has had passed we will be able to access the redborder web interface.

 

Chapter 5: Web access

information.png  As Mentioned before, please waite from 5 to 10 min (in function of your machine performance) to the system to boot and get running all necessary services. Once this time has had passed we will be able to access the redborder web interface.

From here, you can access the web interface of the Redborder Community Manager by entering the address https: // IP-de-gestion in your browser.

It is most likely that you ́ll be asked to accept the security exception to your browser, since the SSL certification is not recognised. Please accept it as it is shown below on the illustration.

browser_privacy_warning.JPG
Figure 29. Security browser warning
 

Once inside, the web interface will request the administrator user’s credentials, which by default are:

  • Username: admin
  • Password: redborder

 

web-01.png
Figure 30. Web interface: login
 

Finally, you can navigate through the web console of redborder Community Manager.

 

web-02.png
Figure 31. Redborder Community Manager web interface
 

 

Chapter 6: Troubleshooting

To verify the correct functioning of redborder, we can access the system via ssh using root user and execute the command:

[root@rbmanager ~]# rb_get_services.sh all

And the outcome should be as shown below:

running_services.PNG
Figure 32. Running services command correct execution

This command should show all services in:

  • running in green

This means that all the required components are operating with normality. If any from the services are shown in:

  • not running in orange
  • running in red

It indicates that the service is running but should be turned off. The same applies to the reverse case, if we see a "not running" status in red, it indicates that the service is not running but in fact it should be.

 

ANEX

 

Table of hardware requeriments scaling

    Físico Virtual   Storage

e/s

MB/day

Threads

CPUs

GB RAM

MB/day

GB/year

25

1750

4

5

20

116,67

41,59

50

3500

4

5

20

233,33

83,17

100

7000

4

5

20

466,67

166,34

200

14000

4

5

24

933,33

332,68

300

21000

5

7

24

1400,00

499,02

400

28000

5

7

24

1866,67

665,36

500

35000

6

8

26

2333,33

831,71

750

52500

7

9

28

3500,00

1247,56

1000

70000

8

10

32

4666,67

1663,41

1250

87500

10

13

40

5833,33

2079,26

1500

105000

12

15

48

7000,00

2495,12

1750

122500

13

17

56

8166,67

2910,97

2000

140000

14

18

64

9333,33

3326,82

2500

175000

16

20

72

11666,67

4158,53

3000

210000

23

29

87

14000,00

4990,23

3500

245000

23

29

90

16333,33

5821,94

4000

280000

24

30

92

18666,67

6653,65

4500

315000

24

30

95

21000,00

7485,35

5000

350000

24

30

96

23333,33

8317,06

5500

385000

26

33

99

25666,67

9148,76

6000

420000

26

33

102

28000,00

9980,47

6500

455000

27

34

104

30333,33

10812,17

7000

490000

27

34

107

32666,67

11643,88

7500

525000

27

34

108

35000,00

12475,59

8000

560000

31

39

119

37333,33

13307,29

 

 

 

Have more questions? Submit a request

Comments

Powered by Zendesk