Viewing the health of appliance services using the CLI
Prerequisites
The Email Security - Server appliance must have an established connection to the Internet.
You must have Admin or Operator access to the Email Security - Server appliance.
Use the CLI commands in this procedure to view the health of:
All appliance services
Services in a specified category
Only services in a specified category that are in critical or warning state
To view the health of all appliance services:
Go to CLI enable mode.
hostname > enable hostname # configure terminal
View the status of all appliance health services.
hostname # show health all Health Status: Last Updated at: : 2020-01-30T11:42:00 Service: :FENET Cloud Services Health Status: :Warning Details :One or more security content uploads have failed to perform the security contents upload Service: :Disk Storage Heath Status :Healthy Details: :Healthy Service: :System load Health Health Status :Healthy Details: :Healthy Service: :CMS Server Connectivity Health Status: :Disabled Details: :No CMS configured yet . . .
To view the health of appliance services in a category:hostname # show health <category>
The example displays appliance health for Cloud-Detection services.
hostname# show health Cloud-Detection Health Status: Last Updated at: : 2020-02-07T11:26:00 Service: Retroactive Detection Health Status: Healthy Details: Healthy Service: Global Cache Health Status Healthy Details: Healthy Service: Advanced URL Defense Health Status: Healthy Details: Healthy hostname #
To view the health status of appliance services in one category that are in critical or warning state:hostname # show health <category> [critical | warning]
The example displays appliance health for DTI services in warning state only.
hostname # show health DTI warning Health Status: Last Updated at: : 2020-02-07T10:55:00 Service: : FENET Cloud Services Health Status: : Warning Details: : One or more security content uploads have failed: Failed to perform the security contents upload Recovery Steps: : 1. Check the fenet server connection 2. Check the fenet server username and password using CLI 'show fenet dti configuration' 3. Check proxy configuration using CLI 'show fenet' 4. Check if firewall is blocking the outbound connections 5. Call Trellix Customer Support if the failure persists