Configure LPSM

You can configure system settings, monitor system performance, upload patches, backup and restore configurations, manage applications, and configure the Director setup settings from the System section.

System
System Setting

You can also customize general settings, search related settings, date/time settings, notification settings and change the system password from the My Preferences section.

My Preferences

System Monitor

System Monitor contains widgets that display the system status.

System Monitor Tab

You can view the status of different menu items such as Services, System Processes, Network Stack, Routing Table, ARP Table, Network Interfaces, and Disk Usage.

System Monitor Options

Services

Services lists all the service applications running in LPSM. You can view the status of each application and start, stop, or restart the services.

chevron-rightStart Serviceshashtag

To initiate an application service, click the Start Service () icon from the Actions column.

To start all services, click Start All. Starting All Services

chevron-rightStop Serviceshashtag

To stop an application service, click the Stop Service (stop) icon from the Actions column.

To stop all services, click Stop All. Stopping All Services

chevron-rightRestart Serviceshashtag

To restart an application service, click the Restart Service (restart) icon from the Actions column.

To restart all services, click Restart All. Restarting All Services

System Processes

System Processes shows all the processes running on the operating system where LPSM is installed. The process list shows information such as users, memory used by processes, commands on the run, and process IDs.

Network Stack

Network Stack shows information about the used network protocols and their corresponding network details.

Routing Table

Routing Table displays the routes to particular network destinations.

Address Resolution Protocol (ARP) Table

ARP Table displays a protocol for mapping an Internet Protocol address (IP address) to a physical machine address that is recognized in the local network. The item data lists the connection status for this protocol.

Network Interfaces

Network Interfaces displays the network status of LPSM. It also displays the status of all the active interfaces such as eth0, l0, he-ipv6, tun0, tun1, and tun10000.

Disk Usage

Disk Usage displays the total disk space used by the LPSM file systems. It also displays the available disk, disk usage, and location of the file system.

System Monitoring via SNMP

You can use SNMPv2 or SNMPv3 to monitor the status of the LPSM system components and services using their respective OIDs.

LPSM uses the base OID 1.3.6.1.4.1.54322.4 to get a list of the exposed OIDs and their corresponding information. You can also use the OID of the individual system components and services in LPSM to get their status.

Syntax for snmpwalk via SNMPv2:

Syntax for snmpwalk via SNMPv3:

circle-info
  • You must enable SNMP from Settings >> System >> System Settings >> SNMP to monitor the status of LPSM.

  • The default values of the parameters used in SNMP monitoring are as follows:

    Parameter

    Default Value

    <community-string>

    public

    <user name>

    director

    <user password>

    changeme

    AES key

    5nMpvEenC^pt

chevron-rightList of SNMP OIDs in LPSMhashtag

OID

Description

1.3.6.1.4.1.54322.4.1

LPSM Version

1.3.6.1.4.1.54322.4.2

I/O Wait

1.3.6.1.4.1.54322.4.3

VM Swapiness

1.3.6.1.4.1.54322.4.4

  • 1.3.6.1.4.1.54322.4.4.1.x

  • 1.3.6.1.4.1.54322.4.4.2.x

  • 1.3.6.1.4.1.54322.4.4.3.x

  • 1.3.6.1.4.1.54322.4.4.4.x

  • 1.3.6.1.4.1.54322.4.4.5.x

  • 1.3.6.1.4.1.54322.4.4.6.x

  • 1.3.6.1.4.1.54322.4.4.7.x

  • 1.3.6.1.4.1.54322.4.4.8.x

ZFS Pool Statistics

  • Name

  • Health

  • Disk Allocation

  • Free disk

  • Read operations

  • Write operations

  • Read bandwidth

  • Write bandwidth

1.3.6.1.4.1.54322.4.5

  • 1.3.6.1.4.1.54322.4.5.1

  • 1.3.6.1.4.1.54322.4.5.2

  • 1.3.6.1.4.1.54322.4.5.3

  • 1.3.6.1.4.1.54322.4.5.4

  • 1.3.6.1.4.1.54322.4.5.5

  • 1.3.6.1.4.1.54322.4.5.6

  • 1.3.6.1.4.1.54322.4.5.7

  • 1.3.6.1.4.1.54322.4.5.8

  • 1.3.6.1.4.1.54322.4.5.9

  • 1.3.6.1.4.1.54322.4.5.10

  • 1.3.6.1.4.1.54322.4.5.11

  • 1.3.6.1.4.1.54322.4.5.12

  • 1.3.6.1.4.1.54322.4.5.13

  • 1.3.6.1.4.1.54322.4.5.14

  • 1.3.6.1.4.1.54322.4.5.15

  • 1.3.6.1.4.1.54322.4.5.16

  • 1.3.6.1.4.1.54322.4.5.17

  • 1.3.6.1.4.1.54322.4.5.18

  • 1.3.6.1.4.1.54322.4.5.19

  • 1.3.6.1.4.1.54322.4.5.20

  • 1.3.6.1.4.1.54322.4.5.21

  • 1.3.6.1.4.1.54322.4.5.22

  • 1.3.6.1.4.1.54322.4.5.23

  • 1.3.6.1.4.1.54322.4.5.24

  • 1.3.6.1.4.1.54322.4.5.25

  • 1.3.6.1.4.1.54322.4.5.26

  • 1.3.6.1.4.1.54322.4.5.27

Message Queue Statistics

  • Node Name

  • State

  • Uptime

  • PID

  • Disk Free

  • Disk Free Limit

  • Disk Free Alarm

  • VM Memory

  • VM Memory Limit

  • VM Memory Alarm

  • Process Used

  • Process Limit

  • File Descriptor Used

  • File Descriptor Limit

  • Limit for File descriptors used as sockets

  • File descriptors used as sockets

  • Total Consumers

  • Total Queues

  • Total Exchanges

  • Total Connections

  • Total Channels

  • Queue Total Messages

  • Queue Total Messages Ready

  • Queue Total Messages Unacknowledged

  • Message Published

  • Messages Delivered

  • Queues not running

1.3.6.1.4.1.54322.4.6.x

  • 1.3.6.1.4.1.54322.4.6.1.x

  • 1.3.6.1.4.1.54322.4.6.2.x

  • 1.3.6.1.4.1.54322.4.6.3.x

  • 1.3.6.1.4.1.54322.4.6.4.x

Service Statistics

  • Name

  • Status

  • CPU Usage

  • Memory Usage

circle-info

Note:

  • The OIDs for the ZFS Pool statistics provide information for the ZFS pools. To retrieve the information for a single pool, add the corresponding value of the respective pool after the ZFS pool base OID.

    OID

    Description

    1

    app_pool

    2

    app_store_pool

    3

    data_pool

    4

    rpool

    For example, you can use 1.3.6.1.4.1.54322.4.4 to retrieve the names of all the ZFS pools and 1.3.6.1.4.1.54322.4.4.1.1 to retrieve the name of the ZFS app pool.

  • The OIDs for the Service Statistics provide information for LPSM services. To retrieve the information of a LPSM service, add the corresponding value of the respective service after the Service Statistics base OID.

    OID

    Description

    1

    webserver

    2

    mongodb

    3

    jobprocessor

    4

    commander_vpnclient

    5

    incoherent_updater

    6

    pool_reader

    7

    msui_cleaner

    8

    scheduled_lpsm_backup

    9

    support_connection_timeout

    10

    system_metrics

    11

    system_notifications

    For example, you can use 1.3.6.1.4.1.54322.4.6 to retrieve the names of all the LPSM services and 1.3.6.1.4.1.54322.4.6.1.1 to retrieve the name of the webserver.

System Settings

System Settings allows you to configure all system related settings for LPSM. It enables you to configure general settings, SMTP settings, NTP settings, SNMP settings, HTTPS settings, support connection settings and allows you to set the SSH Key Pair for li-admin.

System Settings

Each setting needs to be saved separately before moving on to the next setting.

chevron-rightGeneral hashtag
  1. Go to Settings >> System >> System Settings.

  2. Select General. General System Settings

  3. Enter a Logpoint Name, a Browser tab title, and a Server Alias.

    Updating the Server Alias does not update the system IP Address or the DNS. If the Server Alias field is empty, copy the value of the IP field into it.

    The Identifier is the unique value given to each Logpoint.

  4. Select Default Login Screen From either Logpoint Authentication or LDAP Authentication. Once a mode of authentication is chosen, the default login screen is always the same unless changed.

  5. In Session Inactivity Timeout, enter the Timeout (minutes) period. If you are inactive for longer than the specified period, you are logged out of the system.

  6. In Remote Request Timeout, enter the Timeout (seconds) period . If the request from LPSM to Logpoint takes longer than the specified period, the request is closed.

  7. Click Save.

chevron-rightSMTPhashtag

SMTP is used to send emails from LPSM for the following:

  • To send the email for resetting the user password. To reset password, click Forgot Password? on login.

  • To send the email after the Data Privacy Request has been granted. Go to Email Template for more information.

circle-info

To receive email alerts specific to Logpoint, you need to configure SMTP on the fabric-enabled Logpoint. Go to SMTP for more information.

  1. Go to System >> Settings >> System Settings.

  2. Select SMTP. SMTP

  3. Enter the Server/Port address to enable SMTP service.

  4. Enter a Sender Name and a Email address.

  5. If you enable the Login Required option, you need to enter the Username and Password.

  6. Click Save.

To test the configuration:

  1. Click the SMTP Test section. SMTP Test

  2. Enter the Subject of the test email.

  3. Enter an Email address.

  4. Enter a test Message.

  5. Click Test SMTP. The email address mentioned above gets an email if the SMTP setting is configured correctly.

chevron-rightNTP hashtag

NTP synchronizes the time of your server with a network time server.

  1. Go to Settings >> System >> System Settings.

  2. Select NTP. NTP

  3. Check the Is NTP enabled? option.

  4. Enter the Server address. You can add multiple server addresses by clicking the Add (add) icon.

  5. Click Save.

chevron-rightSNMPhashtag

If you enable the SNMP port, LPSM listens to the OIDs (Object Identifiers) that are forwarded to the 161 port.

  1. Go to Settings >> System >> System Settings.

  2. Select SNMP.

  3. Select Enable or Disable SNMPD port (UDP 161).

  4. Enter the Community String if you select Enable.

  5. Click Save.

To know the exposed OID for the LPSM machine, run the snmpwalk command snmpwalk -v 2c -c public <ip_of_Logpoint Search Master>.

chevron-rightHTTPShashtag

The HTTPS service authenticates LPSM and prevents eavesdroppers from accessing the data in the network. HTTPS secures the server connection so that the LPSM users can safely access it from the internet.

  1. Go to Settings >> System >> System Settings.

  2. Select HTTPS. HTTPS

  3. Browse for the HTTPS Certificate and Key, and upload them.

  4. Click Save.

chevron-rightSupport Connectionhashtag

Support Connection creates an encrypted end-to-end communication channel between the Logpoint Search Master and the Logpoint Support. It is used by the Logpoint Support team to understand, troubleshoot, and fix issues with your deployment.

Before enabling the support connection, make sure that your firewall is not blocking the connection from the LPSM to reverse.logpoint.com on port 1193/UDP.

  1. Go to Settings >> System >> System Settings.

  2. Select Support Connection.

    Support Connection

  3. Check the Enable Support Connection checkbox.

  4. Enter the Support Connection Enable Duration. The support session expires after the duration exceeds. Support connection stays enabled if: - You select 0:0:0 as the time duration. - You check the Enable Support Connection Forever checkbox.

  5. Click Save.

chevron-rightSSH Key Pair for li-adminhashtag

An LPSM Administrator can generate SSH certificates for the li-admin user to access the LPSM through the console.

  1. Go to Settings >> System >> System Settings.

  2. Select SSH Key Pair for li-admin. SSH Key Pair for li-admin

  3. Enter a PASS PHRASE.

  4. Click Re-Generate Key Pair.

  5. Copy the Private Key and save it in a file.

  6. Use the following command to make the key accessible for an SSH connection:

  7. Use the following command to establish an SSH connection:

  8. Enter the PASS PHRASE to establish the SSH connection from the remote device.

chevron-rightLockout Policyhashtag

The Lockout Policy lets you control user login and password security attributes. LPSM locks your account for a specific lockout duration if you make multiple failed login attempts.

Lockout threshold: The Lockout threshold determines the number of failed login attempts that cause a user account to be locked. By default, the lockout threshold value is five. You can set a threshold value from 0 to 999, where 0 means a user account is never locked.

After three consecutive failed login attempts, you need to enter a CAPTCHA in addition to the username and password. If you make additional unsuccessful login attempts, that is, if you enter a wrong username, password, or CAPTCHA and reach the specified lockout threshold, your account is locked out for the specified lockout duration.

Lockout duration: The Lockout duration determines the number of minutes that an account remains locked out. By default, the lockout duration value is 30 minutes. After the lockout duration is over, you get one more login attempt. If this attempt fails, your account is locked for an additional specified lockout period. This process continues until you login with valid credentials. You can set a lockout duration value from 1 to 99999.

After a user is locked out, a User Locked icon appears in the Actions column of the respective user under Settings >> User Accounts >> Users. The LPSM administrator can unlock the locked users by clicking the icon.

Configure Lockout Policy

  1. Go to Settings >> System >> System Settings.

  2. Select Lockout Policy. Configuring Lockout Policy

  3. Enter the Lockout threshold. By default, the lockout threshold value is set to 5.

  4. Enter the Lockout duration (in minutes). By default, the lockout duration value is set to 30 minutes.

  5. Click Reset to reset the values to default.

  6. Click Submit.

Applications

You can upload application packages and import Plugins in LogPoint Search Master from the Applications page. An application package is a collection of pluggable components such as Authentication and System Notification. LPSM provides the LPSM_Default package by default.

Applications
chevron-rightAdd an Application Packagehashtag
  1. Go to Settings >> System >> Applications.

  2. Click Import. Import: Import

    Import application: Import Application

  3. Browse the file with the .pak extension. The released .pak files can be downloaded from the LogPoint Help Centerarrow-up-right.

  4. Click Upload.

circle-info
  • Click Details () from the Actions column to view the packages included in the application. Use Filter to browse different categories of the packages.

  • Click Jobs to view the status details of all the imported applications.

Plugins

Enables connection to external data and systems so you can add specific features and functionality to your Logpoint platform. Termed ”Plugins” in the Logpoint UI, they are a synonymous with Authentication, Process Commands, Collectors, Fetchers and Enrichment integrations.

Currently, there are three out-of-the-box authentication integrations for Director LPSM:

  1. LDAP Authentication

Plugins

You can request new features from Logpoint Customer Service. When the feature is developed, the .pak file of the new integration is uploaded in Integrations of the Logpoint Service deskarrow-up-right. You can then download the latest version of the integration and import the .pak file from Settings >> System >> Applications in LPSM.

To install, import the .pak file. After installation it is listed in INSTALLED PLUGINS in Settings >> System >> Plugins.

LDAP Authentication

LDAP (Lightweight Directory Access Protocol) integration in LPSM offers User Authentication, User Management, Role-Based Access Control, and Centralized Data Management.

You can use LDAP for LPSM login authentication and configure it to pull user authentication and role-based access control rules from your LDAP directory. LPSM users are already defined in LDAP so you don’t need to recreate them.

By default, LDAP Authentication is automatically installed in LPSM and cannot be deleted. Configure the LDAP Strategy in LPSM to use LDAP. LDAP strategy is the rules and configurations for deploying and maintaining LDAP services for your organization. LDAP strategy can vary depending on what your needs and objectives are.

chevron-rightConfigure LDAP Strategyhashtag
  1. Go to Settings >> System >> Plugins. LDAP Authentication Plugin

  2. Click Manage for the LDAP Authentication. Add LDAP Strategy

  3. Click Add. LDAP Strategy

  4. Enter a Name and its Description for the LDAP strategy.

  5. Enter the Host/Port address for the LDAP server that authenticates the user.

  6. Enable the SSL (Secure Sockets Layer) option to establish an encrypted link.

  7. Enter a Bind DN which is a distinguished name for the LDAP server.

  8. Enter and confirm the Password to authenticate the user.

    1. For the User contains group info, enter the memberOf information.

    2. For the Group contains user info, enter the member information.

      circle-info

      The fields in User Settings and Group Settings are automatically populated according to the values entered in the LDAP Connection Settings.

      In User Settings:

      1. The User Base DN is the node under which the LDAP users are present.

      2. The Group Mem Attr and the User Name Attr are attributes of the group member and the user provided in the database respectively.

      3. The Filter is the string that filters the user results.

      4. Select the Authenticate Using parameter from the drop-down which is required for login.

        1. Select dn to use standard DN format for login.

        2. Select uid to use uid for login (uid for Linux system).

        3. Select SAM Account Name to use SAM Account Name for login (SAM Account Name for Windows).

      In Group Settings:

      1. Group Base DN is the node under which the LDAP groups are present.

      2. Mem Group Attr contains group members.

      3. Group Name Attr is the group name attribute from the database.

  9. Select Enable or Disable the Enable Paginated Search option. You can choose to paginate the search if the remote server offers a paginated search.

  10. Enter the Username Template and the Fullname Template in the jinja format.

    For example: If the user attributes inside the Active Directory are displayName, FirstName and LastName, then:

    Username Template = {{displayName}}

    Fullname Template = {{FirstName}}{{LastName}}

  11. Click Submit. LDAP Strategy Created

chevron-rightMap LDAP Groups to LPSM User Groupshashtag

After configuring an LDAP Strategy, LDAP groups can be mapped to LPSM User Groups. There is a particular scenario called LDAP concatenation of Users and Permission Groups, which maps multiple LDAP User Groups to LPSM User Groups. This scenario is described below in LDAP Concatenation of Users and Permission Groups.

  1. Click the Map LDAP Groups to LogPoint User Groups (map) icon from the Actions column of an existing LDAP Strategy. LDAP Groups

  2. Click the LDAP Group Name. Edit LDAP Group

  3. Select LogPoint User Group and TimeZone from the drop-down. The LDAP Group Name and LDAP Group DN are populated by default.

  4. Click Submit. LDAP Groups Mapped to LPSM User Groups

LDAP Concatenation of Users and Permission Groups

The LDAP user “LDAP User 1” belongs to LDAP Groups “LDAPG-1” and “LDAPG-2” in the LDAP directory.

There are two Permission Groups PG1 (with Read Site Permission only) and PG2 (with Read, Create, and Delete Site Permissions) created in Logpoint.

PG1 is mapped to User Group UG1, and PG2 is mapped to UG2.

UG1 has the Object Permission of Device-1 and Repo-1, and UG2 has the Object Permission of Device-2 and Repo-2.

If you map the LDAPG-1 to UG1 and LDAPG-2 to UG2, the LDAP User 1 has the concatenated Site and Object Permissions of UG1 and UG2. In this case, the Site Permission is Read, Create, and Delete and the Object Permission is of Device-1, Repo-1, Device-2, and Repo-2.

You can now use LDAP Authentication to log in to LPSM.

LDAP Authentication

Strategy-User group Mapping - UI

LDAP server data is connected with LPSM and stored in the database. First, the connection is made with the LDAP server using data from the LDAP strategy. Once the connection is established, the data (LDAP group) from the server is obtained. After the LDAP groups are obtained, they are listed in the User Group Mapping. Here, the user must select the required LDAP group to map to the LPSM user group. Once the mapping is established, the content: LDAP group, user group, and the DN associated with it are stored in the database. Any update to user group mapping is reflected every time the user logs in to Logpoint.

chevron-rightActivate LDAP Strategyhashtag
  1. Go to Settings >> System >> Plugins.

  2. Click Manage from the LDAP Authentication plugin.

  3. Click the Activate LDAP Strategy () icon from the Actions column of the LDAP Strategy.

    1. To activate multiple LDAP Strategies, select the relevant LDAP Strategies. Click the More drop-down and select Activate Selected. Activate Selected

    2. To activate all LDAP Strategies, click the More drop-down and select Activate All. Activate All

To deactivate the LDAP Strategy, follow the same procedure.

chevron-rightDelete LDAP Strategyhashtag
  1. Go to Settings >> System >> Plugins.

  2. Click Manage from the LDAP Authentication plugin.

  3. Click the Delete () icon from the Actions column of the LDAP Strategy.

    1. To delete multiple LDAP Strategies, select the concerned LDAP Strategies. Click the More drop-down and select Delete Selected. Deleting Selected

    2. To delete all LDAP Strategy, select the concerned LDAP Strategy. Click the More drop-down and select Delete All. Deleting All

  4. Click Yes.

chevron-rightConfigure Default Domain for LDAP Authenticationhashtag

Configuring a default domain for LDAP Authentication automates the domain selection process during login. LPSM automatically uses the configured default domain when you login using LDAP Authentication.

To configure a default domain:

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

  2. Search for LDAP Authentication.

  3. Click Manage.

  4. Click Settings.

  5. Select your domain from the Default Domain drop-down. LDAP Authentication Default Settings

  6. Click Save.

Supported Login formats (LDAP)

The following three parameters can be used to log in via LDAP.

Using DN:

Using sAMAccountName:

Using uid:

Communication

The parameters used for communication are:

  • Host

  • Port

  • Bind DN

  • Bind DN password

  • SSL enabled or not

There are two ways to communicate:

  • Simple communication

  • Communication using SSL

For simple communication, the Python-LDAP library is used. The host and the 389 port are used to connect to the LDAP server. Once the connection is established, Bind DN and Bind Password are used to bind to the required user.

For SSL communication, the first step is to set the certificate for the SSL connection. After the certificate is set, the process is similar to simple communication. Here, the port used is 636.

My Preferences

Click the User drop-down on the top-right corner of the interface and select My Preferences.

My Preferences Option
chevron-rightGeneralhashtag
  1. Select Show settings item help to display help on various items on the Settings page. After enabling the option, when you hover the mouse on any one of the items, you can see the details of the settings item on the right side of the screen.

  2. Select the Result limit from the drop-down to customize the display size of pages in the Settings page.

  3. Click Submit.

General
chevron-rightDate Timehashtag

Select Time Zone, Date Format, and Hour Display Format. By configuring the date and time from the Date Time Preference section, you can have the same date and time displayed in all parts of the application.

circle-info

The logs are collected in Coordinated Universal Time (UTC) irrespective of the Time Zone selected by the user.

chevron-rightNotificationhashtag

Select Top Left, Bottom Left, Top Right, or Bottom Right to position growl notification accordingly.

Notification

Last updated

Was this helpful?