Skip to main content

Device42 Remote Collector - Installation

The Remote Collector (RC) is shipped as a virtual appliance and can be downloaded from our Autodiscovery software download page.

This guide provides step-by-step instructions for configuring your Remote Collector after initial deployment.

Step 1: Change User Password​

  1. Navigate to the Virtual Machine console of the Remote Collector Appliance.
  2. Log in using the default credentials (Username is client and Password is device42).
  3. Choose option (p) to enter the Change Password (user client) menu.
  4. Enter and verify the new password.
  5. Choose the Save button.

Change password

Step 2: Specify Hostname​

  1. Choose option (s) to enter the Server Settings menu.
  2. Enter a hostname.
  3. Choose the Save button.

Change password

Step 3: Configure the Network Interface​

  1. Choose option (u) to enter the Network, Connectivity and Utilities menu.

  2. Choose option (n) to enter the Network Interfaces menu.

    Change password

  3. Select the default interface (highlighted in white) and press Enter.

    Change password

  4. If using a Static IP, deselect Use DHCP and enter the IP Address, Subnet, Gateway, and DNS server(s). If using IPv6, specify the IPv6 Address and Gateway.

    Change password

  5. Choose Save, then Exit, then Exit.

Step 4: Configure the NTP Settings​

  1. Choose option (n) to enter the NTP Client Settings menu.

  2. Ensure Daily sync is chosen.

  3. Optionally choose to sync on reboot (this enables an admin to reboot the RC within the Device42 interface, which can help resolve unusual RC behavior).

  4. Choose Manual Sync should you choose to perform a manual sync now, else choose the Save button.

    Change password

Step 5: Connect the Remote Collector to the Main Appliance​

  1. Choose option (r) to enter the Remote Collector Setup menu.
  2. Enter the name of the Remote Collector.
  3. Enter either the Hostname or IP Address of the Main Appliance.
  4. Generate a One Time Password (OTP) from the Main Appliance, which will be entered later into this menu:
    • Log into the Main Appliance.
    • Choose Discovery > Remote Collectors.
    • Click the Generate OTP button.
  5. Enter the OTP.
  6. Choose the Register button. Note the green acknowledgement text at the top of the main Appliance Management menu.
  7. Navigate back to the Main Appliance and confirm the RC in the Remote Collectors menu shows a State of "connected".

Deployment Example​

RCs are extremely flexible and make discovery with Device42 easier than ever. You can deploy one or more, with no logical limit to the number of RCs you can use.

main menu

In the deployment example pictured above, an RC is deployed within each isolated DMZ network segment that, per firewall rules typical of a DMZ, the Device42 MA is normally unable to reach or discover directly. Deploying an RC to these segments bolsters security by saving the network administrator from making multiple temporary (or permanent and insecure) firewall rules (aka 'holes') to allow discovery traffic to pass from the MA over the wide range of ports used by various vendor APIs.

Please note that the diagram doesn't show the majority of network connectivity that would be present, and instead focuses on what is discovered by the MA and the RC, and the communication between them.

As mentioned briefly in the introduction, all communication and discovery information is securely transmitted between the RC and the MA once a connection is established via Port 443 (HTTPS/SSL). This means a single, secure, and easily monitored 1:1 rule allows for comprehensive and continuous discovery of the secured network segment - as often as scheduled or desired - without compromising its isolation or security.

Proxy Settings​

The proxy settings within the MA and RC are set independently but are often identical. To reduce the potential for error, the RC can pick up preconfigured proxy settings. You can also view and edit the RC proxy settings within the RC view of the MA.

Scalability​

Device42 RCs provide robust scalability by offloading discovery workloads from your MA. You can deploy multiple RCs for each MA. We recommend using one RC with one WDS for every 1,000 workloads.