Viewing information about a cluster node
16 April 2024
ID 201759
To view information about a cluster node:
- In the application web interface window, select the Nodes section.
- Select the node whose information you want to view.
A window containing information about the node opens.
For a description of the information displayed, refer to the table below.
Node information
Group of settings | Setting | Description |
|---|---|---|
Node information | Certificate fingerprint | Certificate fingerprint of the server. |
Comment | Additional information about the node. Optional setting. | |
Current server role | Role of the current node in the cluster. | |
Scan threads | The number of message streams that KSMG can scan simultaneously. | |
Settings | Applied | Control node setting. Last time when settings were successfully applied to application modules. |
Synchronized | Secondary node setting. Last time when settings were successfully received from the Control node. If settings were received, you can assign the Control role to this Secondary node without losing the defined settings. | |
Applied | Secondary node setting. Last time when settings were successfully applied to application modules. | |
Database information
| Database update | State of the application databases and the result and time of their last successful update. Possible values:
|
Anti-Virus | State of the Anti-Virus module databases. Possible values:
| |
Anti-Phishing | State of the Anti-Phishing module databases. Possible values:
| |
Anti-Spam | Current state of the Anti-Spam module databases. Possible values:
| |
External services | KSN/KPSN status | State of the connection to KSN or KPSN services. |
KATA status | State of the connection to the KATA server: This is displayed only when KATA integration is configured. | |
Kerberos keytab file status | Existence of SPN entries about all Secondary nodes in the keytab file. Displayed only if Kerberos authentication is enabled. | |
LDAP status | Displayed only if integration with an Active Directory domain is configured:
| |
Server time | Time | Displayed only for Secondary nodes. State of time synchronization with the server hosting the Control node. If the status is Failure, you can copy error information to the clipboard by clicking the button to the right of the status. |
License information | License expiration date | Date and time when the license key expires. |
License | Information about the status of the license key. For an active license key, expiration date and the number of days to expiration is also displayed. | |
Application | Name of the application for which the added license key was issued. | |
Functionality level | Application operation mode depending on the added license key. | |
License type | Type of license (trial, commercial, or subscription). | |
Serial number | Serial number of the license key. |
If duplicated data is found in accounts after successful synchronization with the Active Directory domain, a warning is displayed in the table of cluster nodes and in the LDAP status group of settings. The following data are checked for duplicates:
- Names of all domain users.
For users with duplicate names, Active Directory spoofing protection and personal allow and denylists do not work, messages are not placed in personal Backup, and personal lists are not available in the application.
- Groups to which domain users belong.
For groups with duplicated names, protection against Active Directory spoofing is disabled.
- Active Directory contacts.
For contacts with duplicated names, protection against Active Directory spoofing is disabled.
- Kerberos user accounts.
For users with duplicate Kerberos names, personal allow and denylists do not work, messages are not placed in personal Backup, and personal lists are not available in the application.
- NTLM user accounts.
For users with duplicate NTLM names, personal allow and denylists do not work, messages are not placed in personal Backup, and personal lists are not available in the application.
- Email addresses of domain users.
Messages intended for duplicated addresses are not placed in users' personal Backup, and personal allow and denylists of sender addresses are not applied to duplicated addresses.
You can save the data of duplicated accounts to a file. To do so, in the warning area click Save duplicates to CSV.
