Ceburu Installation Overview

Ceburu focuses on developing artificial intelligence-based network monitoring solutions, including asset and network management, metric logs, bandwidth, and database KPIs.

As our Ceburu application is designed in a modular approach, any one of the following modules or a combination of more than one can be configured to be run by the installer.  

1. Network Monitoring 

2. Asset Monitoring 

3. Bandwidth Monitoring 

4. DB Key Performance Indicators  

5. Remote Connect 

6. Patch Manager 

Probe system requirement (On Cloud)

Installer Pre-Requisites

Before installing Ceburu on your system, there are a few requisites that must be satisfied to avoid installation errors or compatibility issues during the installation process.   We have categorized the pre-requisites based on the operating system as follows:

General Requirements for both Windows and Linux Installations

Internal Port Management:

To install on both Windows and Linux, follow these general requirements:

• Ceburu Portal: To enable portal.ceburu.com, ensure that Port 7878 is open. Refer to the Manage Network Group for the necessary Network set up. This will cover public IP, subnets, and other essential configuration required for the deployment.

• The specified Probe Host IP must be contained within a permitted subnet range.
  

• Network Monitoring : Open Port 20050 & Port 20051 (UDP) for internal communication between proxy and node.
• DNS Monitoring : Open Port 20052 (UDP) for Internal communication between proxy and node.
• DB/IIS Monitoring : Open Port 20053 (UDP) for Internal communication between proxy and node.
• APM Monitoring: Open Port 8200 (TCP) for Internal communication between proxy and node.
• Suricata: Open Port 5044 (TCP) for Internal communication between suricata agent and logstash.
• Log Explorer: Open Port 5140(UDP) for Internal communication between router/switch and aiops proxy.
• WinRM: Open Port 5985(TCP) for Internal communication between proxy and node. 

The probe machine and all associated subnets must be part of Active Directory.

WinRM should be enabled:

• Test WinRM:
  • Run the below command from the probe machine powershell.
    • Test-Wsman <Client machine IP>
    • Eg:- Test-Wsman 192.168.1.9
  • If Enable the output be like this:

• Enable WinRM:
  • Run the below command in the client machine powershell.
    • Enable-PSRemoting

Firewall Rules for Node:

            1. Ping should be reachable from the probe machine to the node machine.

            2. WinRM should be enabled on the node machine (port 5985/TCP inbound).

            3. Port 20050/UDP outbound should be opened for Ceburu Agent communication from the node machine to the probe machine.

            4. Port 20051/UDP inbound should be opened for Ceburu Proxy communication from the probe to the node machine.

            5. Port 20052/UDP outbound should be opened for Ceburu DNS communication from the node machine to the probe machine.

            6. Port 20053/UDP outbound should be opened for Ceburu Metric Agent communication from the node machine to the probe machine.

System Requirement:

• Windows:
  • Workstation -> 10 & above
  • Windows Server -> 2012 & above
• Linux:
  • Ubuntu -> 20.04 & above
  • Redhat -> 7 & above
  • Centos -> 7 & above
• System should have 1TB free storage.
• System should have 32GB free RAM.

What is Ephemeral?

• Ephemeral ports are temporary ports used for a brief period to establish connections between clients and servers on the internet.

• These ports allow multiple connections to occur simultaneously without conflicts. For instance, a browser can use different ephemeral ports to connect to various websites at the same time

Internal Port : 20050,20551 - > For internal communication Proxy and node

Ensure that all devices are connected to the internet. Additionally, the Administrator Username and Password should be uniform across all devices within the specified subnet ranges on the Asset Network page to enable broadcasting.

Additional Requirements for Windows

In addition to the general requirements, a few extra steps are needed when installing Ceburu on Windows:

• Operating System: Ensure that host workstations are running at least Windows 10, and servers are using at least Windows Server 2019 for proxy installation.

• Probe Machine Specifications: The probe machine must have a minimum of 16 GB or 32 GB of RAM, while all other devices on the network should have at least 16 GB of RAM, 150 to 200 GB Disk space depending on the size of the network.

• Administrator Permissions: Run the installer using the Run as Administrator option.

• SSL Whitelisting: Add portal.ceburu.com to the whitelist to avoid SSL certificate issues.

• Windows Defender Exclusion: Create a group policy to exclude the Ceburu folder from Windows Defender scans.

• Firewall Configuration: Ensure that the firewall whitelists the xyz folder and its files to prevent disruptions.

Additional Requirements for Linux

Similarly, additional requirements must be met when installing Ceburu on Linux:

• Operating System: Host workstations and servers should meet the same specifications as for Windows installations (Windows 10 for workstations, Windows Server 2019 for servers).

• Probe Machine Specifications: The probe machine should have at least 16 GB or 32 GB of RAM, and all other devices on the network must have at least 16 GB of RAM.

• Port 22 Configuration: Ensure that port 22 is enabled on all machines within the network.

• SSH Protocol: All machines must have SSH protocol enabled and properly configured.

Ceburu On-Cloud Installation:

Once your account is set up, configure asset management settings before proceeding  with the installation by clicking the link:  Manage Network Groups

To finalize the installation, run the following two executable files: 

1. Ceburu Infrastructure 
2. Ceburu Application.

1. Ceburu Infrstructure Setup:

Download Installer Files:

            Login to Ceburu Portal   (portal.ceburu.com) > Downloads

Welcome Page 

Select directory where you want to install

Enter Credentials

Please enter your Ceburu username, password, and license key.

Validating the Credentials

Checking Dependencies

Verifying all the dependencies required for installing Ceburu.

Select the modules to be installed

Installing the environment

                    Infrastructure Installation Completed:

Infrastructure installation completed successfully. Once done, proceed to run the Application installer.

Finish Infrastructure Page:

2. Ceburu Application Installation:

Download the Ceburu Application

Welcome Page

Enter Credentials

Please enter your Ceburu username, password, and license key.

Checking Dependencies

Verifying all the dependencies required for installing Ceburu.

Select the modules to be installed

Enter Domain Credentials

Enter your network domain credentials. If you choose "Save and Continue," your credentials will be stored in the Ceburu database for future use. Otherwise, they will not be saved.
            

Installation Started

Installing Scanner, Proxy and Agent

Installing DBKPI Monitoring Agent

Installing Backup Manager

Installing Remote Connect

Installing Patch Manager

Installing Application Manager:

Preparing files for distribution to all node machines

Installation Completed all our services are in running state

Probe machine setup completed

The probe machine setup is now complete. If you wish to proceed with installing agents on all endpoints, select "Scan and Install Agents on All Devices." Otherwise, you may quit the installer.

Scanning In progress:

These are devices are scanned by scanner

Installing all Endpoints

Status of all Endpoints

Finish Page:

Endpoint Installation Using ADDS:

To install Active Directory Domain Services (ADDS), select the checkbox labeled "Endpoint Installation Using ADDS."

Next, you will be prompted to enter the domain name on the following page.

Example: see.local

When you choose "Endpoint Installation Using ADDS," it automatically creates a Group Policy Object (GPO) for the specified domain name.

After setting up the Probe, it will create a Group Policy Object (GPO) for the domain and then close the installer. The installer will not proceed to the broadcasting process, as the GPO will handle all necessary configurations.

Note: GPO will take a minimum one and half hours to two hours.

Once the installation is complete, the monitoring of devices is automatically initiated.

Note:  The process may take a few minutes. 

Microsoft Windows Defender Exclusion  

Note: This is exclusively for Microsoft downloads.

Follow the steps shown above to bypass any potential interruptions for the Ceburu download process from Microsoft Defender.