User Guides
CTE-U Quick Start Guide
- Terminology and Components
- Install and Configure CTE-U with CipherTrust Manager
  - Installation Prerequisites
  - Installation and Registration
  - Verifying Package Signatures
  - Setting the SE Linux state
- Guarding with CTE-U and CipherTrust Manager
  - Access the CipherTrust Manager Domain
  - Create an Encryption Key
  - Guarding CTE files with CTE-U
- Exporting GuardPoints over NFS
- Migrating CTE Agents to CTE-U
- Multifactor Authentication for CTE-U
  - Introduction to Multifactor Authentication
  - Using [CTE-U,MFA]
  - Use Cases for MFA on CTE
  - Exempting some users from authentication with a Whitelist
  - Setting up Multifactor Authentication with a One-Time-Password
  - Setting up Multifactor Authentication with an Inactivity Time Out
  - Administrator Tasks for Multifactor Authentication
  - Troubleshooting Multifactor Authentication
CTE-U Health Manager Utility
- Performing Health Check
- Using the Monitor
- Service Commands
- Viewing the Service Status
- Gathering the Technical Dump
- Troubleshooting/ Debugging CTE-U
CTE-U Agent Advanced Configuration Guide for Linux
- CTE-U Overview
- Getting Started
  - Configuring CTE-U with CipherTrust Manager
- Enhanced Encryption Mode
- CTE with systemd
  - CTE Agent Control Changes on systemd
- Utilities
  - CTE-U Linux Authentication and Client Settings
  - Individual GuardPoint Tuning
  - Secfsd Utility
- Upgrading CTE-U on Linux
- Uninstalling CTE-U from Linux
Using FreeBSD with CTE-U
- FreeBSD Jail
- Install CTE-U Dependencies
- FreeBSD Services
- Upgrade CTE-U Packages
- Remove CTE-U Packages
- Unsupported Features for CTE-U with FreeBSD

Performing Health Check

Run the issues command to perform a health check of the local CTE-U software. If no problems are detected, There are 0 issues is displayed. It indicates a healthy system. However, if any issues are detected (that is, the system is sick), the number of issues with additional details about each issue is displayed.

Healthy

For example, if no issues are detected:

sudo /usr/bin/cte_u_manager  issues
There are 0 issues

Sick

For example, if some issues are detected:

sudo /usr/bin/cte_u_manager  issues
There are 2 issues
keyManager: connect() failed.
gdb (PID 97446) is attached to 100611.

Suggest A Change

Performing Health Check

Healthy

Sick

On this page