Alerts
This section lists the alerts for LDT over NFS and describes what to do in each case. LDT generates alerts when issues arise that require attention from the Administrator. Without prompt attention, alerts can delay the rekey process or cause the process to remain incomplete.
Linux Alerts
Guard/Unguard alerts
| Label | Alert | Description |
|---|---|---|
| I_LDT_NFS_PTS_ACCESS_FAILED | Failed to preserve time stamps: GuardPoint [GuardPoint] objID [objID] error [error] |
Primary host sends this alert to notify of the failed attempt to preserve time stamps on the specified inode number in the GuardPoint. The reason for the failure is reported using the error code. |
| E_LDT_NFS_REKEY_OP_FAILED | Failed to start or stop rekey on GuardPoint [%s] over NAS share, error [error] | Primary host sends this alert if it fails to start or stop rekey on a specified GuardPoint. The error code in the alert provides the error code associated with the failed attempt. |
LDT Communications Group alerts
| Label | Alert | Description |
|---|---|---|
| W_LDT_COMMGRP_MASTER_DOWN | LDT Communication Master is down | Each member of an LDT GuardPoint Group sends this warning reporting that the LDT Communication Group Master associated with the group is down. |
| I_LDT_COMMGRP_MASTER_UP | LDT Communication Master is up | Each member of LDT GuardPoint Group sends this notice reporting that the LDT Communication Group Master associated with the group is no longer down. |
| W_LDTGRP_PRIMARY_LEFT | LDT Group Primary host left the group for GuardPoint [%s] | This warning reports that the specified GuardPoint has been disabled on the host designated as the primary host for the GuardPoint. LDT immediately designates another member in the LDT GuardPoint Group as the primary host for the group. |
| I_LDTGRP_PRIMARY_ELECTED | LDT Group Primary host has been elected for GuardPoint [GuardPoint] | Every member of an LDT GuardPoint Group for a specific GuardPoint sends this notice to report the election of a member of the group as the primary host for the GuardPoint. |
| I_LDTGRP_PRIMARY_PROMOTED | Host has been promoted to LDT Group Primary role for GuardPoint [GuardPoint] | The host promoted to the primary role for the GuardPoint sends this notice. |
| W_LDTGRP_PRIMARY_REFUSED | Host cannot be promoted to LDT Group Primary role for GuardPoint [GuardPoint] | This warning reports that the host sending the alert was elected for promotion to the primary role for the GuardPoint, and the host rejected the request. Read-only access to a GuardPoint or the host not having the latest policy key version are common reasons for a host to reject the promotion. |
| E_LDTGRP_PRIMARY_EFAILED | Election of this host for LDT Group Primary role has failed for GuardPoint [GuardPoint] | The host elected and accepted the primary role for the GuardPoint sends this error message if the host fails to perform the operations required for promotion to the primary role for the GuardPoint. |
| E_LDTNFS_FOVER_FOP | File operation recovery failed on new primary host after primary election, GuardPoint [%s] objID [%llu] error [%d] source [%d] | This error message reports that the host promoted to primary status was unable to complete the file operation that was initiated prior to the unexpected failure and departure of the previous primary host from the group. The file inode number is the objID in the message. The error code indicates the reason for the failure. The source identifies the operation that the new primary host failed to complete. |
| E_LDTNFS_RECOVERY_FAILED | LDT recovery failed on new primary host after primary election, GuardPoint [%s] objID [%llu] error [%d] | This error message reports that the host promoted to primary status was unable to recover incomplete rekey operation on the specified file inode number in the specified GuardPoint after unexpected failure and departure of the previous primary host from the group. The error code indicates the reason for the failure. The error code indicates the reason for the failure. |
| W_LDTNFS_PROMOTION_TOOLONG | Promotion too long | Promotion process taking too long, causing a delay in file operations, GuardPoint [%s] objID [%llu]. This warning occurs when a request to the primary host is delayed for a long time because a new primary has not been promoted. |
| E_LDTNFS_FOP_FAILED | File operation failed on secondary host, GuardPoint [%s] objID [%llu] error [%d] source [%d] | This alert from the primary host reports primary host failure to update LDT related metadata on behalf of a member performing a file operation that requires making changes to LDT metadata. File operations performed on secondary hosts to files undergoing rekey, such as truncate or rename, involves the primary host to intervene for updating LDT metadata. |
| W_LDTNFS_KEY_ROTATE_ENOKEY | Some members of LDT GuardPoint Group for [%s] have not received latest key version | This warning is initiated by the primary host when at least one member of the group for the specified GuardPoint Group has not received the latest policy key version that the primary host is committing. Make sure that all member of the LDT GuardPoint Group are connected to the CM. |
| W_LDTNFS_LAZY_RK_FAILURE | Lazy rekey operation failed to rekey <file name>, error <error code> | This alert reports failure to rekey the specified file name. The error code provides the reason for the error. |
Windows Alerts
Guard/Unguard alerts
| Label | Alert | Description |
|---|---|---|
| E_LDT_GUARD_FAILED | Failed to enable/apply GuardPoint | Guard operation failed |
| E_LDT_UNGUARD_FAILED | Failed to disable/delete GuardPoint | Unguard operation failed |
Credentials alert
| Label | Alert | Description |
|---|---|---|
| E_LDT_CIFS_INVALID_CRED | Failed to enumerate GuardPoint <..\GP0>, Verify the provided CIFS credentials. | CIFS credentials may be expired or may not have permission to access. |
| E_LDT_CIFS_LOGIN_FAILED | Failed to authenticate a user | Failed to authenticate user using given credential. |
| [CGA] [ERROR] [4] [CGA3142E] | Not guarding path; Reason: Resource not available | If the agent logs display this message during CIFS GuardPoint creation, you can safely disregard. The GuardPoint will be created after the credentials are authorized. It may take a few minutes. |
LDT Communication Group alerts
| Label | Alert | Description |
|---|---|---|
| E_LDT_LGS_JOINING_FAILED | Failed to join GuardPoint group | CTE client was unable to join the LDTGuardPoint group |
| E_LDT_LGS_LEAVING_FAILED | Failed to leave GuardPoint group | CTE client was unable to leave the LDT GuardPoint group |
