Skip to main content

Resource and Deployment Architecture Overview

Learn about the Device42 core resources and how they fit into the deployment architecture.

Device42 Resources​

Device42 consists of the Main Appliance, one or more Remote Collectors (RCs), and a Windows Discovery Service (WDS). The Main Appliance is an interface for configuring and running discovery jobs, viewing and managing discovered Configuration Items (CIs), generating reports, and managing any third-party integrations.

During discovery, the RC and WDS collect data of your IT environment.

Main Appliance​

The Device42 Main Appliance is the kick-off point for all the discovery and insights that will proliferate through your environment. It is a preconfigured virtual appliance (built on Linux) hosted by you, for full protection under your organization's data center security architecture and policies.

Device42 operates with only five ports open to the virtual appliance:

  • Port 80: Redirects to port 443
  • Port 443: Web (HTTPS)
  • Port 4242: Redirects to port 4343
  • Port 4343: Appliance Manager (HTTPS)
  • Port 404: SSH for limited console menu operations
caution

Device42 is delivered as a virtual appliance. Root access to the appliance is not supported, and the VM will cease to function if you attempt to break into the root account.

Manage the Main Appliance using the Appliance Manager (AM), from which you can restart and stop the Device42 application, generate logs or SNMP walks for tech support, and more.

Remote Collector​

The Remote Collector is a much lighter preconfigured virtual appliance (built on Linux) used to perform agentless discovery across network segments. It provides scalability by offloading discovery workloads from the MA. You need to install at least one RC with any deployment of Device42.

Windows Discovery Service​

The Windows Discovery Service is a .NET service that runs on a Windows system and makes WMI queries on behalf of the Linux-based RC and MA. To run Windows discoveries, you need to deploy at least one WDS instance and connect it to an RC.

Deployment Architecture​

The Device42 deployment architecture is similar to a hub-and-spoke model, with each RC/WDS collecting data and syncing back to the centralized MA. If you require Windows discovery, we recommend you deploy RCs and WDS instances in pairs.

Device42 Deployment Example​

The following image illustrates the segmented network structure used for Device42 deployments.