--- title: "Enrolling a managed sensor through a proxy" slug: "enrolling-a-managed-sensor-through-a-proxy" updated: 2026-08-24T20:40:19Z published: 2026-08-24T20:40:19Z canonical: "docs.trellix.com/enrolling-a-managed-sensor-through-a-proxy" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Enrolling a managed sensor through a proxy Use the commands in this section to enroll a managed sensor with an IVX cluster managed by another Central Management appliance. In this scenario, the local Central Management appliance that manages the sensor will act as a proxy for the enrollment. This procedure changes the enrollment service address for the local Central Management appliance to the IP address of the Central Management appliance that manages the IVX cluster. The enrollment service address for the sensor will continue to be the IP address of the local Central Management appliance. ##### To enroll a managed sensor through a proxy: 1. Log in to the local Central Management CLI. 2. Go to CLI configuration mode: ``` cm-hostname > enable cm-hostname # configure terminal ``` 3. Change the enrollment service type to DTI, and configure the enrollment service address (the IP address of the Central Management appliance that manages the cluster): ``` cm-hostname (config) # fenet dti enrollment service type DTI address ``` where <`cluster CM address`> is the IP address of the Central Management appliance that manages the IVX cluster. 4. Set DTI as the default enrollment service type: ``` cm-hostname (config) # fenet dti enrollment service default DTI ``` 5. Verify your changes: ``` cm-hostname (config) # show fenet dti configuration ``` 6. Save your changes. ``` cm-hostname (config) # write memory ``` 7. Log in to the sensor CLI. 8. Verify the enrollment service settings: ``` sensor-hostname (config) # show mvx cluster enrollment service ``` **Example** In this example, the nx-1 sensor is managed by the local Central Management appliance (cm-1) with an IP address of 172.1.2.3. The local Central Management appliance will act as a proxy to enroll the sensor with Cluster-02, which is managed by another Central Management appliance (cm-2) with an IP address of 10.11.10.11. ``` cm-1 (config) # fenet dti enrollment service type DTI address 10.11.10.11 cm-1 (config) # fenet dti enrollment service default DTI cm-1 (config) # show fenet dti configuration DTI CLIENT CONFIGURATIONS:    ACTIVE SETTINGS:    Mode : online    Download source            : DTI (User8@cloud.fireeye.com)    Upload destination         : DTI (User8@up-cloud.fireeye.com)    Mil service                : DTI (User8@mil-cloud.fireeye.com)    Enrollment service         : DTI (User8@10.11.10.11) ... nx-1 (config) # show mvx cluster enrollment status MVX Cluster Enrollment Status    Enrollment Client :        Status ok              : yes        Status description     : enrolled        Last checked at        : 2019/08/14 14:56:01    Enrollment Service :        Auto enabled           : yes        Service address        : CMS (172.1.2.3)        Preferred cluster      : any (less loaded)        Cloud enabled          : no        Cloud License enabled  : no        Connect on demand      : no    Broker Info :        Cluster Name           : Cluster-02        Broker Name            : vx-4        Broker ID              : 002XXXXXXXXX        Broker Address         : 10.11.12.13        Broker State           : Connected        Failure Reason         : None        Last Connection Attempt: 2019/08/12 15:01:11        Connection Last Formed : 2019/08/12 15:01:12        Connection Last Broken : ```