Use this procedure after you deploy the Trellix Wise appliance on a supported cloud environment or hypervisor.
Prerequisites
Before you begin, make sure that you have:
Completed the Trellix Wise appliance deployment on a supported cloud environment or
hypervisor.The activation code provided during onboarding.
An appliance IP address that is reachable from the network where you run SSH.
SSH access to the appliance with the admin account.
An online connection from the appliance to Trellix services.
Activate and license the appliance
If you did not enter the activation code while configuring the VM, you can enter in this step.
The activation code activates the appliance and enables licensing. For an online deployment,
use online activation.
From the appliance CLI, enter the activation code:
<hostname> (config) # license activation code <activation-code>Verify the license status:
<hostname> (config) # show licensesAccess and verify the appliance
After licensing the appliance, access the appliance through SSH and verify the appliance before
enabling the container cluster.
Connect to the appliance using SSH:
ssh admin@<appliance-ip>If you enabled Enable fenet license update service? during VM configuration, update the license:
fenet license updateIf you did not enable Enable fenet license update service?, manually install the license:
license install <license>Verify the appliance version:
show versionVerify the installed licenses:
show licenses
Enable the container cluster
If you enabled the container cluster during appliance configuration, you do not need to enable the container cluster again. Use the following commands to monitor the installation progress and verify the cluster status.
If the container cluster is already enabled
Monitor the cluster installation progress and status:
<hostname> (config) # show fenet cluster update statusVerify the container cluster:
<hostname> (config) # show cluster health
If the container cluster is not enabled
If you did not enable the container cluster during appliance configuration, enable the container cluster using the following steps.
A valid license is required to enable the container cluster.
Enable the container cluster:
<hostname> (config) # cluster enableThe process can take several hours to complete.
Monitor the cluster installation progress and status:
<hostname> (config) # show fenet cluster update statusVerify the container cluster:
<hostname> (config) # show cluster health
Deploy Trellix Wise™ for Private Cloud
For an online deployment, complete the following steps to install Trellix Wise™ for Private Cloud .
Allow OIDC authentication for the web policy:
<hostname> (config) # aaa authentication oidc web policy allowedVerify that the OIDC client ID was fetched:
<hostname> (config) # show aaa authentication oidc clientIf the client ID is displayed, the oci-auth.conf file was also created on the appliance.
Enable the container cluster:
<hostname> (config) # cluster enableVerify the cluster status:
<hostname> (config) # show cluster statusWait for the RKE2 cluster to reach the active and running state before continuing.
Refresh the appliance metadata:
<hostname> (config) # fenet metadata refreshInstall the Trellix Wise for Private Cloud workload:
<hostname> (config) # fenet cluster install workloadMonitor the installation progress:
<hostname> (config) # show fenet cluster update progressApply security content
For an online deployment, security content updates automatically every 15 minutes when the applicable content license is active.
Verify the security-content status:
<hostname> (config) # show fenet security-content statusValidate the deployment
Verify the appliance version:
<hostname> (config) # show versionVerify the license status:
<hostname> (config) # show licensesVerify the container cluster:
<hostname> (config) # show cluster healthVerify the security-content status:
<hostname> (config) # show fenet security-content statusThe show cluster health command verifies the status of the cluster nodes, etcd, and pods.
The show fenet security-content status command verifies the security-content channel, version, and update status.