Install Fabric Server

Director Fabric ties together the Director Console and LPSM with Logpoint servers. It consists of one or more Fabric Servers and an API Server.

ISO

Install Fabric Server Using ISO

1. Boot your system with Logpoint Director ISO v1.0.0.

2. Select Fabric Server and click OK.

   Fabric Server must be installed before installing API server. The hardware used to configure the cluster mode must be identical to ensure efficiency.

3. The installer detects the number of hard disk drives (HDD) present in the system and provides various options for Director installation accordingly. If you use more than one HDD, it increases the fault tolerance of the system. The available types of Director installation according to the number of HDDs are:

   Number of HDD(s)	Mode of Installation
   1	Single
   2	Mirror/ Single
   3 or more	RAIDZ/ Mirror/ Single

   • The ZFS (Zettabyte File System), used in the Logpoint Director, itself provides a software-defined solution for disk-based redundancy (Mirror, RAIDZ). Hence, it is not recommended to use hardware-based RAID. Doing so limits the ZFS to perform self-healing on checksum failures.

   • When selecting the RAIDZ mode, the first three disks is used for OS and application installation. The remaining disks, if any, can be used to extend the disk space or used as L2ARC (Level 2 Adjustable Replacement Cache) or ZIL (ZFS Intent Log) for enhancing the read/write performance of ZFS. It can be done using the ZFS commands.

   For One HDD:

   For Two HDDs:

   For Three HDDs

   Select a mode of installation and click Continue.

4. Click Back to revisit the LP Director Server Type window or click Continue to proceed.

   The first reboot of the installer occurs, and the installation process starts. The installation may take some time.

   Multiple warning messages may appear during the first boot of the installation process. These errors are related to setting up a Live DVD environment and can be ignored. These messages do not cause any issue during the installation.

   Once the installation is complete, a message appears in the console. Press Enter and wait for the installer to list all the available Ethernet interfaces.

5. The installer detects and lists all the Ethernet interfaces connected to the system. Choose the required network interface to modify its configuration and click OK.

6. The installer extracts the configuration of selected Ethernet interface of the Fabric Server. Revise the configurations if necessary and click Submit.

   The full configuration details of the selected Ethernet interface is displayed if DHCP is enabled. If DHCP is not enabled, then only the fields “Hostname” and “DOMAIN” appear and you need to manually enter the “IP”, “Netmask”, and “Gateway” fields.

7. Click Back to revisit the configurations or click Continue to proceed.

8. The Fabric Server Installation Type window appears. There are two modes of Fabric Server installation, the Standalone and the Cluster.

Standalone mode

Standalone mode requires the installation of a single Fabric Server.

Configure Fabric Server in Standalone Mode

1. Select Standalone and click OK.

2. Enter the tunnel IP for Fabric Network connection and click OK. The tunnel IP is the internal IP address through which the Logpoint Director components communicate with each other.

3. Enter the IP address of Remote Syslog Server where the Audit Logs of the Fabric Server must be forwarded and click OK.

   If the Remote Syslog Server is not ready, you can leave the default settings as they are. You can later execute the change-rsyslogip command to change the IP address of the Remote Syslog Server, once the installation process is completed.

4. After the installation of the standalone Fabric Server, a dialog box appears to configure the API server.

   Enter the fully qualified hostname of the API Server and its static IP address and click Submit.

   The IP range 10.98.1.2 - 10.98.1.9 is used by API Server and LPSM for administrative purposes. If you cancel this step in the installation process, you can later use the addfwrule command to set the Static Tunnel IP Address for the API Server.

5. Click Back to revisit the configurations or click Continue to proceed.

   The system reboots to support new configurations and the Fabric login window appears.

6. Log in using the following credentials:

   username: cmdr-admin
   password: changeme

   It is recommended that the password is changed immediately using the passwd command.

7. Execute the fabric-app-installer command and click OK. You are reminded to configure the NTP server after installing the Fabric applications.

8. Execute the config-ntp command to configure and manage the NTP server.

   It is mandatory to synchronize the time between all the Director components (Fabric-enabled Logpoint, Logpoint Search Master, Fabric Server(s) and API Server).

9. The Fabric application installation continues on the Standalone Fabric Server. Click OK.

   The system reboots to continue with the Fabric application installation.

   • You must repeat the entire installation cycle if you install a new Fabric Server.

   • It is recommended to store the transactional logs of the Fabric Proxy on a dedicated hard disk. It makes the system faster and more efficient in terms of memory, thus improving the throughput. Refer to the Storing Transactional Logs of Fabric Proxy on a Different Disk section for details.

Cluster mode

Cluster mode creates a group of servers that work together to maintain high availability of applications and services. If one Fabric Server fails, another server in the cluster can take over its workload. The number of servers required to overcome n number of server failure is 2n+1. That means, to overcome two server failures you need to install five servers in the cluster.

The Director setup currently handles upto three server failures.

Configure Fabric Server in Cluster Mode

1. Select Cluster in the Fabric Server Installation Type window and click OK.

2. Enter the number of cluster nodes to be used in the Fabric Server and click OK.

3. Enter the Fabric Proxy Node ID for the configuration of the Fabric Server and click OK. The Fabric Proxy Node ID must be different for each node.

4. Enter the IP addresses of the interface and their respective tunnels and click OK.

   • For each node of the Fabric Cluster, a private tunnel is provided for a secure communication.

   • The tunnel IP is the internal IP address through which the Logpoint Director components communicate with each other.

   • The number of interfaces is determined by the number of cluster nodes.

   • The IPs of the Fabric Server must be entered sequentially.

5. Click Back to revisit the configurations or Click Continue to proceed.

6. A confirmation window pops up after the installation process completes. Click OK.

7. Enter the IP address of Remote Syslog Server to which the Audit Logs must be forwarded and click OK.

   If the Remote Syslog Server is not ready, you can leave the default settings as they are. You can later execute the change-rsyslogip command to change the IP address of the Remote Syslog Server, once the installation process completes.

8. After the installation of the Fabric Server, a dialog box appears to configure the API server. Enter the Fully Qualified Domain Name (Hostname) of the API Server and its static IP address.

   The IP range 10.98.1.2 - 10.98.1.9 is used by API Server and LPSM for administrative purposes. If you cancel this step in the installation process, you can later use the addfwrule command to set the Static Tunnel IP Address for the API Server.

9. Click Submit.

10. Click Back to revisit the configurations or click Continue.

    The system reboots to support the new configurations, and the Director login window appears.

11. Log in using the following credentials:

    username: cmdr-admin
    password: changeme

    It is recommended to change the password immediately using the passwd command.

12. Enter the fabric-app-installer command and click OK. You are reminded to configure NTP server after installing the Fabric applications.

    Configure NTP Server Notice

13. Execute the config-ntp command to configure and manage the NTP server.

    It is mandatory to synchronize the time between all the Director components (Fabric-enabled Logpoint, Logpoint Search Master, Fabric Server(s) and API Server).

14. If the Fabric Proxy Node ID of the Fabric Server is 1, it is automatically configured as the Master Fabric Authenticator Server. If the Fabric Proxy Node ID of the Fabric Server is other than 1, then it is configured as the Fabric Authenticator Slave Server.

    1. For the Master Fabric Authenticator Server (when the Fabric Proxy Node ID is equal to 1), you should provide the Fully Qualified Domain Name (FQDN) of all Fabric Authenticator Slave Servers and click OK.

       1. Click Back to revisit the Fabric Authenticator configuration or click Continue to confirm the configuration.

       2. Enter the tunnel IP address of the respective Fabric Authenticator Slave Servers and click OK.

       3. Click Continue to confirm the configurations.

          The system reboots after the successful installation of the Fabric application.

    2. For the Fabric Authenticator Slave Server (when the Fabric Proxy Node ID is other than 1), you must provide the IP address of the Master Fabric Authenticator Server and click OK. The fabric application installation initiates. Click OK. The system reboots to continue with the Fabric application installation.

15. After successfully installing the Fabric application on all the Fabric Servers, execute start-fabric-app command in Master Fabric Authenticator Server Node 1 to initialize the Fabric application.

    • Repeat the installation process for the Fabric Server for every node of the cluster. For example, if a Fabric Server has 3 nodes you will install the Fabric Server 3 times. Once on each node.

    • Assign the same Domain Name for each node of the Fabric Server.

    • Repeat the entire installation when you install a new Fabric Server.

    • Store transactional logs of the Fabric Proxy on a dedicated hard disk. This increases system performance and efficiency and improves throughput. Go to the Storing Transactional Logs of Fabric Proxy on a Different Disk for details.

AMI/OVA/VHD

You must deploy the Fabric Server AMI/OVA/VHD before installing the Fabric Server. To learn how, go to the Deploying the Director AMIs, the Deploying the Director OVAs and Deploying the Director Azure VHDs.

Install Fabric Server Using AMI/OVA/VHD

1. Access the Fabric Server. The installer detects and lists all the ethernet interfaces connected to the system. Select the appropriate network interface to modify its configuration and click OK.

2. Enter the IP Address, Netmask, and Gateway. The installer extracts the remaining configuration of selected ethernet interface of the Fabric Server. You can change the configurations if you need to.

   For Fabric Server AMI: Do not change the IP Address, Netmask, and Gateway. AWS environment does not allow these changes after launching the instances.

   

3. Click Submit.

4. Click Continue. You can click Back to revisit the configurations.

5. The Fabric Server Installation Type window appears. There are two modes of Fabric Server installation, the Standalone and the Cluster.

Standalone Mode

Standalone mode requires the installation of a single Fabric Server instance.

Configure Fabric Server Instances in Standalone Mode

1. Select Standalone and click OK.

2. Enter the tunnel IP for the Fabric network connection and click OK. The tunnel IP is the internal IP address through which the Logpoint Director components communicate with each other.

   The Fabric Server reboots to support new configurations.

3. Enter the Fabric Server’s default credentials:

   username: cmdr-admin
   password: changeme

   We recommend you to change the password immediately using the passwd command.

   You can now establish an SSH connection with the Fabric Server. To learn how, go to Establish an SSH Connection section.

4. Execute the fabric-app-installer command exposed to the cmdr-admin user. You are reminded to configure the NTP server after installing the Fabric applications.

5. Click OK. The system reboots.

6. Execute the config-ntp command to configure and manage the NTP server in the Fabric Server instance.

   It is mandatory to synchronize the time between all the Director components: Fabric-enabled Logpoint instances, Logpoint Search Master, the Fabric Server, and the API Server.

Cluster Mode

Cluster mode creates a group of servers that work together to maintain high availability of applications and services. If one Fabric Server fails, another server in the cluster can take over its workload. The number of servers required to overcome n number of server failure is 2n+1. To overcome two server failures you need to install five servers in the cluster.

• The Director setup currently handles up to three server failures.

• If you are deploying the Fabric Server AMI in cluster mode or if you are scaling the Fabric Server instances, you must create a route table and stop source/destination check in the AWS management console. A route table ensures the network traffic is directed correctly. For details, go to the Accessing the Fabric Server Instance section.

• You must install each Fabric Server instance individually in the cluster mode.

• The Domain name for each Fabric Server instance should be the same.

• You must repeat the installation cycle if you install a new Fabric Server instance.

Configure Fabric Server Instances in Cluster Mode

1. Select Cluster and click OK.

2. Enter the number of Fabric Server instances to be installed and click OK.

3. Enter the Fabric Proxy Node ID for the Fabric Server instance and click OK. The Fabric Proxy Node ID must be different for each instance. If the Fabric Proxy Node ID of the Fabric Server instance is 1, it is configured as the Master Fabric Authenticator Server. Alternatively, it is configured as the Fabric Authenticator Slave Server.

   You must complete the Master Fabric Authenticator Server’s setup before the Fabric Authenticator Slave Server’s setup.

4. Specify the IP addresses of the interface and their respective tunnels. Each Fabric Server instance has a private tunnel for a secure communication. The tunnel IP is the internal IP address through which the Director components communicate with each other.

5. Click OK.

   • The number of interfaces is determined by the number of instances.

   • The IP addresses of the Fabric Server instances must be entered sequentially.

   

6. Click Continue. Click Back to revisit the configurations. The system reboots to support the new configurations.

7. Enter the Fabric Server’s default credentials:

   username: cmdr-admin
   password: changeme

   We recommend you to change the password immediately using the passwd command.

   You can now establish an SSH connection with the Fabric Server. To learn how, go to the Establishing an SSH Connection with the Fabric Server section.

8. Execute the fabric-app-installer command exposed to the cmdr-admin user.

9. If the current Fabric Server instance is your Master Fabric Authenticator Server (when the Fabric Proxy Node ID is 1):

   1. Enter the Fully Qualified Domain Name (FQDN) of all Fabric Authenticator Slave Servers.

   2. Click OK.

   3. Click Continue. You can click Back to revisit the configuration.

   4. Enter the tunnel IP address of the respective Slave Fabric Authenticator Servers.

   5. Click OK.

   6. Click Continue. The system reboots after installing the Fabric applications.

10. If the current Fabric Server instance is your Fabric Authenticator Slave Server when the Fabric Proxy Node ID is other than 1:

    1. Enter the IP address of the Master Fabric Authenticator Server

    2. Click OK. The system reboots after installing the Fabric applications.

11. After successfully installing the Fabric applications on all the Fabric Server instances, execute the start-fabric-app command in the Master Fabric Authenticator Server to initialize the Fabric application.

12. Execute the config-ntp command to configure and manage the NTP server in all the Fabric Server instances.

    It is mandatory to synchronize the time between all the Director components: Fabric-enabled Logpoint instances, Logpoint Search Master, the Fabric Server instances, and the API Server.

Scale Fabric Server

You can upscale the number of Fabric Servers to create a failover cluster and increase the fault tolerance of the Director setup. Scalability is achieved by adding two new servers at a time to the Director environment.

The cmdr-admin user can scale up the Fabric Server after executing the fabric-scalable command.

Scale Standalone Fabric Server

A single Fabric Server failure can lead to disruption of Director operations. Upscaling a standalone Fabric Server to a cluster of Fabric Server increases the fault tolerance of the Fabric Server nodes by maintaining high availability of applications and services.

Scale Standalone Fabric Server

1. Install two new Fabric Servers individually in the cluster setup

   Refer to Installation of Fabric Server for the stepwise installation process.

   • The fabric-scalable command automatically initializes the Fabric applications in the new Fabric Server nodes. Therefore, it is not required to execute the fabric-app-installer command while installing the new servers.

   • Make sure to upgrade the new Fabric Servers to the same version as the existing Fabric Server.

2. Update the keys on the new Fabric Servers using the change-server-keys command to ensure all servers have a common key.

   The keys for the new nodes must be the same as the existing keys of Fabric and API server.

3. Execute the fabric-scalable command in the Primary Server.

   A confirmation screen appears.

4. Enter the Server Name, Server IP, and Tunnel IP for the additional Fabric nodes. Each node in the Fabric cluster uses a private tunnel for secure communication.

5. Enter Ok to confirm the configuration.

   The summary of the specified configuration appears.

6. Enter Back to revisit the configurations.

7. Enter Continue to accept the configuration and proceed.

   A confirmation window pops up once the installation process completes.

8. Enter OK.

9. Reboot all the Fabric Server instances using the reboot command.

10. Change the API and LPSM VPN passwords on the new Fabric nodes by running the following commands:

    • change-vpn-clientpwd api

    • change-vpn-clientpwd lpsm

    The new VPN passwords must match the passwords used on the existing Standalone Fabric Server.

11. Update the proxy ACL on the two new Fabric nodes by running the change-fabric-proxyacl command.

    The proxy ACL passwords for the new nodes must be the same as the passwords set on the existing Standalone Fabric Server.

12. Run the com-appinstaller command on the API Server with the new cluster details.

Scale Cluster Fabric Server

Upscaling the number of cluster Fabric Servers increases the fault tolerance of the Fabric Servers by maintaining high availability of applications and services.

Scale Cluster Fabric Server

1. Install two new Fabric Servers individually in the cluster setup.

   Refer to the Installation of Fabric Server for the stepwise installation process.

   • The fabric-scalable command automatically initializes the Fabric applications in the new Fabric Server nodes. Therefore, it is not required to execute the fabric-app-installer command while installing the new servers.

   • Make sure to upgrade the new Fabric Servers to the same version as the existing Fabric Server.

2. Update the keys on the new Fabric Servers using the change-server-keys command to ensure all servers have a common key.

   The keys for the new nodes must be the same as the existing keys of Fabric and API server.

3. Execute the fabric-scalable command in the master Fabric Server.

   A confirmation screen appears.

4. Enter the Server Name, Server IP, and Tunnel IP for the additional Fabric nodes. Each node in the Fabric cluster uses a private tunnel for secure communication.

5. Enter OK to confirm the configuration. Enter Back to revisit the configurations.

   The summary of the specified configuration appears on the screen.

6. Enter Continue to accept the configuration and proceed.

   A confirmation window pops up after the installation process completes.

7. Enter OK.

8. Reboot all the Fabric Server instances using the reboot command.

9. Change the API and LPSM VPN passwords on the new Fabric nodes by running the following commands: change-vpn-clientpwd api

   change-vpn-clientpwd lpsm

   The new VPN passwords must match the passwords used on the existing Cluster Fabric Servers.

10. Update the proxy ACL on the two new Fabric nodes by running the change-fabric-proxyacl command.

    The proxy ACL passwords for the new nodes must be the same as the passwords set on the existing Cluster Fabric Servers.

11. Run the com-appinstaller command on the API Server with the new cluster details.