--- sourceDocument: Australia Operational Technology Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/operational-technology Release : - australia ft:locale : - en-US ft:publication_title : - Australia Operational Technology Management ft:clusterId : - optm bundleId : - optm workflow : - Technology --- # Requirements for Discovery Console for OT installation # Requirements for Discovery Console for OT installation {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Requirements for Discovery Console for OT installation The Discovery Console for OT is a critical component for operational technology discovery, requiring specific infrastructure, system, and network configurations to function correctly. This guide outlines the necessary prerequisites and licensing requirements to ensure a successful installation and operation. Show full answer Show less ## Infrastructure and System Requirements * **Operating System:** A Linux OS capable of running in a virtualized environment or on bare-metal hardware. * **Deployment:** Installation must occur on a virtual machine (VM) with at least 10 GB of free disk space after OS and Console installation. * **System Resources:** Minimum of 16 GB RAM, 100 GB hard drive space, and 2 CPUs are required. * **Dependency:** The Console requires .NET version 10 (updated from version 8). ## Network Requirements To ensure proper communication and functionality, the following ports must be open inbound to the Discovery Console for OT: * **TCP 5671:** For Discovery Sensors to communicate and receive updates from the Console. * **TCP 8443:** Access to the Discovery Console's web interface and API. * **TCP 5002:** Enables Sensors to receive updates from the Console. * **TCP 443:** For communication from the Console to ServiceNow instances or MID Servers via the Service Graph Connector for OT Discovery. * **UDP 123:** Critical for time synchronization between Sensors and Console; prevents clock drift that can disrupt feature functionality. **Note:** If access issues arise, verify firewall rules to ensure the necessary IP addresses and ports are unblocked. ## Configuration and Licensing * **Configuration Wizard:** The Console includes an interactive setup wizard to guide initial configuration, including license upload prompts. * **License Requirement:** A valid license is mandatory before using the Console; licenses must be requested from your ServiceNow account representative. * **License Upload:** Upload via the Console's Settings page as a ZIP file containing license.pem and pubkey.pem files. ## License Impact on Features The license controls access to key features. If expired or absent, the following capabilities become inactive, though background data is retained: * Running Auto Query and asset scans. * Consuming network connection data. * Creating and viewing API tokens. * Exporting collections, such as assets, to files (RAW XML export is disabled without a valid license). Warnings are displayed within the Console as the license approaches expiration to prompt timely renewal and uninterrupted service. For remote deployment at a facility or on a network, verify that the following requirements are met before installing the Discovery Console for OT. ## Infrastructure requirements {#reqs-ot-console-installation__section_kd3_3bz_4gc} You must have a Linux operating system installed that can operate in a virtualization environment or on a Bare-metal server. Install the Discovery Console for OT on a virtual machine. Note: After installing the Console and the Operating System (OS) on a virtual machine (VM), the VM must have a minimum of 10-GB of unused space available. ## System requirements {#reqs-ot-console-installation__section_ust_3rx_vgc} The table lists the minimum resource requirements for the Discovery Console for OT. For more information, see [OT Discovery System Resources](https://servicenow-prod.fluidtopics.net/tolf~qFiLKjZV~Bu62rbPQ "You can review the OT Discovery component resources before setting up your OT network.").{#reqs-ot-console-installation__table_i5f_kpx_vgc__entry__2} | Component | System Requirements | |-|-| | Discovery Console for OT | * 16 GB RAM * 100 GB Hard drive * 2 CPUs {#reqs-ot-console-installation__ul_c12_cqx_vgc} | [Table 1. System Requirements] {#reqs-ot-console-installation__table_i5f_kpx_vgc} Note: The required dependency version has been changed to .NET 10 from .NET 8 ## Network requirements {#reqs-ot-console-installation__section_l5d_p1z_4gc} The Discovery Console for OT requires the following ports to be open inbound (from the connection source to the Console) to operate. {#reqs-ot-console-installation__table_pxw_hym_33c__entry__2} | Ports | Description | |-|-| | TCP 5671 | Used by Discovery Sensor for OT to communicate with the Discovery Console for OT. This port is used by the Sensor to report data and receive configuration updates from the Console. | | TCP 8443 | Used to connect to the Discovery Console for OT Web interface. This port is used by the API. | | TCP 5002 | Enables Sensors to communicate with the Discovery Console for OT to receive updates. | | TCP 443 | Used for network communication from the Console to a ServiceNow instance or MID Server via the Service Graph Connector for OT Discovery. | | UDP 123 (Required) | Enables Sensor devices to synchronize time (real-time clock) with the Discovery Console for OT to verify that the time associated with reported data and events is both precise and accurate. **Note:**Without port UDP 123 open on the firewall, the clocks of Sensors drift apart from the clock of the Console. When clock drift is present, various features that rely on precise clock synchronization don't work as expected. | [Table 2. Network requirements] {#reqs-ot-console-installation__table_pxw_hym_33c} Note: If there are problems accessing the Discovery Console for OT, check the firewall rules and unblock the specific IP addresses and ports used for the installation. If you have any errors or difficulties while using the Discovery Console for OT, [contact Customer Service and Support](https://support.servicenow.com/now?draw=case) ## Discovery Console for OT configuration wizard {#reqs-ot-console-installation__section_mj3_tyd_k3c} The Discovery Console for OT now provides a configuration wizard to guide you through your initial setup and configuration of the Console. If you choose to use the interactive configuration wizard after logging into the Console, it alerts you automatically to upload a Console license. For more information, see [Use the Discovery Console for OT interactive configuration wizard](https://servicenow-prod.fluidtopics.net/k4kYI4dFLx6kZGRugc5i_w "The Discovery Console for OT provides an interactive configuration wizard that steps you through setting up your Console, Sensor, Collector, assets, queries, and sites."). ## Discovery Console for OT license {#reqs-ot-console-installation__section_rnp_22x_qgc} Note: Before you can use the Console, you must have a license. Request a Console license from your ServiceNow account representative. When you first sign into the Console, a warning banner alerts you that there is no license. To upload a license for the Discovery Console for OT, do the following: 1. From the Home page, navigate to the Settings page. 2. On the Settings page in the License section, select the Upload License button. 3. Upload your license as a .zip file. 4. Verify the ZIP file contains the license.pem and pubkey.pem files. {#reqs-ot-console-installation__ol_c3m_t3l_23c} Once you have uploaded your license, you can use the Console.
## Console features that require a license {#reqs-ot-console-installation__section_vmf_qyd_k3c} It is important to understand that certain features are rendered inactive if the Discovery Console for OT license is expired. After the license expires, the locking mechanism is triggered and deactivates these features. No data is lost in the background. When a valid license is uploaded, the you can start or continue working. When the license is about to expire, the Console displays a warning banner as an alert. The license: * Enables the ability to run Auto Query and asset scans (inactive on expiration). * Enables the consumption of network connection data (inactive on expiration). * Enables the creation and viewing of API tokens (inactive on expiration). * Enables the export of collections (for example, assets) to files (inactive on expiration). {#reqs-ot-console-installation__ul_kbb_p2x_qgc} Note: You can't export RAW XML results if your Console license is invalid (absent or expired).