Version:

Configuring Logpoint Director in LPSM

Logpoint Director enables you to configure the Fabric Network, Fabric Storage, and the Fabric Authenticator settings in LPSM. You must configure the settings sequentially to set up LPSM in the Logpoint Director setup.

Warning

  • The Logpoint Director setup does not work if Fabric Network, Fabric Storage, and Fabric Authenticator is not configured.

Fabric Network

Fabric Network allows LPSM and Logpoint to operate in the Director setup in an isolated and secure environment. To enable the Fabric Connect option for a regular Logpoint, the Fabric Network must be established in the LPSM.

  1. Go to Settings >> System from the navigation bar and click Logpoint Director.

    ../_images/LPSM_System_LD.png

    Logpoint Director Settings

  2. Enter the Fabric Server IP(s) in the Fabric Network tab.

    • The Standalone Fabric Server consists of a single Fabric Server IP address. You can access the Fabric Network using the Fabric Server IP address.

    • The Cluster Fabric Server consists of 3, 5, or 7 Fabric Server IP addresses. You can access the Fabric Network using any one or all of the Fabric Server IP addresses.

    • For the correct Director setup, at least two Fabric Servers must be up and running in the Cluster mode for three servers. Similarly, in the Cluster mode for five servers, at least three Fabric Servers must be up and running.

    • To make the Fabric Network publicly accessible, you must configure the public IP addresses from the Fabric Server. For details, see Configuring Public IP for the Fabric Server.

  3. Change the vpn client password and fill it in the Password field.

  4. Enter the Maximum Transmissions Unit MTU in bytes. All the packets transferred from the LPSM to other components of the Director setup are chunked into the size of the specified MTU.

    • The default value of the MTU is 1500.

    • You can enter any MTU value between 1250 and 65535 as your network requirements.

    • To maintain a consistent flow of the packets inside the network, you must set the same MTU throughout all Director components.

  5. Click Save. The system begins to fetch the tunnel IP(s) from the specified Fabric Server(s). Once the Fabric Network is established, the system successfully fetches the Server IP(s) and the Client IP.

    ../_images/LPSM_System_LD_FabricNetwork_FetchedIPServer.png

    Fetched Server and Client IP for Standalone Fabric Server Mode

    ../_images/LPSM_System_LD_FabricNetwork_FetchedIPCluster.png

    Fetched Client and Server IP for Cluster Fabric Server Mode

    Here, the server IP 10.xxxx.1 is the Active Fabric Network Server as the client-server IP 10.xxx.0.2 is obtained from it. The remaining server IPs 10.xxxx.1 and 10.xxx.1 are Standby Fabric Network Servers in the cluster.

    If the Fabric Network fails to establish,

    5.1 Click Refresh to re-poll the configuration status of Fabric Server.

    5.2 Click Clear to stop and delete all the services running on the currently configured Fabric Network and click Yes.

    ../_images/LPSM_System_LD_FabricNetwork_ClearConfirmationBox.png

    Confirmation Dialog Box

After configuring the Fabric Network separately in both the regular Logpoint and the LPSM, a secure communication pathway is established among the Logpoints, the Fabric Server(s), and the LPSM.

Fabric Storage

Fabric Storage is a placeholder for granting authentication and allowing the LPSM to access the Distributed File Systems. Fabric Storage has to be configured before configuring other sections.

Warning

The Logpoint Director setup does not work if the Fabric Storage is not configured after the configuration step of Fabric Network.

To check if the Fabric Storage has been configured:

  1. Go to Settings >> System from the navigation bar and click Logpoint Director.

  2. Select Fabric Storage. If it shows Configuring status, wait until the Status field is displayed.

    ../_images/LPSM_System_LD_FabricStorage_Configuring.png

    Configuring Fabric Storage

    If the Fabric Storage is correctly configured, the Configured status is displayed.

    ../_images/LPSM_System_LD_FabricStorage_Configured.png

    Fabric Storage Configured

    Displayed above is the Fabric Server IP, which is the active Fabric Proxy. Fabric Proxy is a co-ordinated service used for data and configuration management in the Logpoint Director setup. It allows the distributed processes of the Director setup to coordinate with each other using a standard file system.

    If the configuration for Fabric Storage is not successful, the Reconfiguration required status is displayed.

    ../_images/LPSM_System_LD_FabricStorage_Reconfiguration.png

    Reconfiguration required for Fabric Storage

  3. Click Configure. The action configures the LPSM to the Fabric Cluster or the Fabric Server.

Warning

The Logpoint Director setup does not work if Fabric Storage is not configured.

Fabric Authenticator

The Fabric Authenticator needs to be authenticated to access the Distributed File Systems located in the Fabric Storage. It ensures that only the authenticated and authorized users are allowed to access the files hosted on the Fabric Storage.

The Fabric Authenticator is similar to a login page where the uploaded files and patches retained in the Fabric Storage can be accessed. The default credentials are:

user: hdfs/admin
password: Welcome@123

The default password can be changed using the change-fabric-authpwd command available to cmdr-admin users. The command is exposed only in the API Server. The same default or changed credential should be provided here.

To configure Fabric Authenticator:

  1. Go to Settings >> System from the navigation bar and click Logpoint Director.

  2. Select Fabric Authenticator.

    ../_images/LPSM_System_LD_FabricAuthenticator.png

    Fabric Authenticator

  3. Click Save.

After setting up the Fabric Network, Fabric Storage, and Fabric Authenticator sequentially, you can create the Logpoint Pools. The LPSM users can then subscribe to the Logpoints for Dashboard, Report, and Incident and carry out the search operation in the Fabric-enabled Logpoint instances.

Sync Pools

LPSM stores all the updated pool information and credentials. The pool information comprises of the pool (UUID), the credentials of Fabric Authenticator, Fabric Proxy nodes, and Fabric Storage folders.

Sync Pool restores the pool information when the connection between the Fabric server and LPSM is disrupted. You must sync pools in the following cases:

Note

  • If a Fabric-enabled Logpoint crashes, you need a configuration backup to restore the data. For details, refer to the Backup and Restore guide.

LPSM displays a notification in the Notification Center to sync Logpoint Pools whenever required. Go to Settings >> System >> Logpoint Director and click Sync Pools to restore the pool information.

../_images/LPSM_System_LD_SyncPools_notification.png

Sync Pools

Note

You must manually clear out the notification message after restoring the pool information.

Sync from Fabric Proxy

If LPSM is unavailable, is down, or crashes, the latest pool information can be recovered by importing the updated data from Fabric Proxy. The following occurs while syncing data from Fabric Proxy:

  1. Recovery of LPSM is dependent on the state of the Fabric Server.

  2. The new LPSM server is installed.

  3. The sync only restores the pool information.

To restore data from Fabric Proxy:

  1. Go to Settings >> System from the navigation bar and click Logpoint Director.

  2. Select Sync Pools.

    ../_images/LPSM_System_LD_SyncPools_Box.png

    Sync Pools

  3. Select the Sync from Fabric Proxy section. The LPSM Synchronization displays the IP(s) of the connected Standalone or Cluster Fabric Servers.

  4. Enter the Username and the Password of the Fabric Proxy Authentication.

    user: zkacl
    password: Welcome@123
    

The default password can be changed using the command change-fabric-proxyacl available to cmdr-admin users. The command is exposed only in the API Server.

../_images/LPSM_System_LD_SyncPools_FromFabricProxy.png

Fabric Proxy Authentication

  1. Click Sync.

    ../_images/LPSM_System_LD_SyncPools_FromFabricProxy_Confirmation.png

    Sync Fabric Proxy to LPSM Dialog Box

  2. Click Yes. Another confirmation dialog box appears, warning that the syncing is permanent. Proceed with caution.

    ../_images/LPSM_System_LD_SyncPools_FromFabricProxy_Confirmation2.png

    Confirmation Dialog Box

  3. Click Yes.

Sync to Fabric Proxy

If the Fabric Proxy crashes or if there is a loss of data (pool information) in the Fabric Proxy, the Sync to Fabric Proxy option can be used to sync the pool information present in LPSM to Fabric Proxy.

Note

  • Sync to Fabric Proxy only restores the pool information from the LPSM.

  • To restore the information of the Fabric-enabled Logpoints, each Fabric-enabled Logpoint must be synced with the Fabric Server individually. Refer to the Sync from Fabric-enabled Logpoint section for details.

To restore data to Fabric Proxy:

  1. Go to Settings >> System from the navigation bar and click Logpoint Director.

  2. Select Sync Pools.

    ../_images/LPSM_System_LD_SyncPools_ToFabricProxy.png

    Sync to Fabric Proxy

  3. Select Sync to Fabric Proxy. The Fabric Proxy Synchronization displays the IP(s) of the connected Standalone or Cluster Fabric Servers.

    ../_images/LPSM_System_LD_SyncPools_ToFabricProxy_Sync.png

    Sync to Fabric Proxy

  4. Click Sync.

    ../_images/LPSM_System_LD_SyncPools_ToFabricProxy_Confirmation1.png

    Sync LPSM to Fabric Proxy Dialog Box

  5. Click Yes. Another confirmation dialog box appears, warning that the syncing is permanent. Proceed with caution.

    ../_images/LPSM_System_LD_SyncPools_ToFabricProxy_Confirmation2.png

    Confirmation Dialog Box

  6. Click Yes.

Once Fabric Connect is enabled in a regular Logpoint, it is referred to as Fabric-enabled Logpoint. Also, certain features and functionalities are disabled from the user interface. Those functionalities, however, are accessible via API Exposed Applications. Refer to the API Exposed Applications section for details about the applications exposed to the API.


Helpful?

We are glad this guide helped.


Please don't include any personal information in your comment

Contact Support