Enrolling a standalone sensor

Prev Next

Use the commands in this section to enroll a standalone sensor with an IVX cluster.

To enroll a standalone sensor:
  1. Log in to the sensor CLI.

  2. Go to CLI configuration mode:

    sensor-hostname > enable
    sensor-hostname # configure terminal
  3. Configure the enrollment service address (the IP address of the Central Management appliance that manages the cluster):

    sensor-hostname (config) # fenet dti enrollment service type DTI address <cluster CM address>

    where <cluster CM address> is the IP address of the Central Management appliance that manages the IVX cluster.

  4. Verify your changes:

    sensor-hostname (config) # show fenet dti configuration
  5. Verify the enrollment service settings:

    sensor-hostname (config) # show mvx cluster enrollment service
  6. Save your changes:

    sensor-hostname (config) # write memory

Example

In this example, the standalone nx-5 sensor is enrolled with a cluster that is managed by a Central Management appliance with an IP address of 10.11.10.11.

nx-5 (config) # fenet dti enrollment service type DTI address 10.11.10.11
nx-5 (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@up-cloud.fireeye.com)
    Enrollment service : DTI (User8@10.11.10.11)
...
nx-5 (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       : DTI (10.11.10.11)
    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 Address        : 10.11.12.13
    Broker ID             : 002XXXXXXXXX
    Broker State          : Connected
    Failure Reason        : None
    Last Connection Attempt: 2019/08/12 15:01:11
    Connection Last Formed : 2019/08
    Connection Last Broken :