Home
Smart Polling
Learn how to configure and manage Smart Polling to actively query OT and IoT devices for detailed information.
Strategies
Reference information for all Smart Polling strategies.
Strategies overview
Smart Polling strategies are network-based methods that directly reach the monitored assets with concise, safe, and effective protocol-specific messages, enhancing visibility in the Nozomi Networks solution.

Smart Polling
Learn how to configure and manage Smart Polling to actively query OT and IoT devices for detailed information.
- Introduction
  An overview of Smart Polling.
- Requirements
  License requirements for Smart Polling.
- Smart Polling in Vantage
  Centralized Smart Polling management across sensors in Vantage.
- Smart Polling in CMC
  View Smart Polling information across sensors in CMC.
- Smart Polling in Guardian
  Manage and monitor Smart Polling in Guardian.
- Smart Polling in Arc
  Enable and configure Smart Polling execution on Arc sensors.
- Strategies
  Reference information for all Smart Polling strategies.
  - Strategies overview
    Smart Polling strategies are network-based methods that directly reach the monitored assets with concise, safe, and effective protocol-specific messages, enhancing visibility in the Nozomi Networks solution.
  - Advantech EdgeLink
    Use this strategy on Advantech EdgeLink devices that expose the proprietary UDP protocol.
  - Advantech EKI HTTPS
    Use this strategy on Advantech EKI wireless access point devices that expose the HTTPS protocol.
  - AutomationDirect Productivity
    Use this strategy on AutomationDirect devices that expose the Productivity protocol.
  - Avalue UWB TCP
    Use this strategy on Ultra Wide Band Avalue devices that expose their own protocol.
  - Axis HTTP(S)
    Use this strategy on Axis devices that expose the HTTP(s) protocol.
  - BACnet
    Use this strategy on devices that expose the BACnet protocol.
  - Beckhoff
    Use this strategy to poll Beckhoff devices through their HTTP interface.
  - Belden/Hirschmann Rail Data Diode HTTP(S)
    Use this strategy on Belden/Hirschmann Rail Data Diode devices that expose the HTTP(S) protocol.
  - Bently Nevada
    Use this strategy on Bently Nevada devices exposing their own protocol.
  - Bosch RCP+ cameras HTTP(S)
    Use this strategy on Bosch Security Systems camera devices that expose RCP+ over the HTTP(S) protocol.
  - Dahua DHIP/DVRIP devices
    Use this strategy on DAHUA devices that expose the DHIP/DVRIP protocols.
  - Eaton EasyProtocol
    Use this strategy on Eaton devices that expose the easyProtocol protocol.
  - EtherNet/IP
    Use this strategy on devices that expose the EtherNet/IP protocol, such as Rockwell Automation/Allen-Bradley devices.
  - GE MDS TD Series Telnet
    Use this strategy on GE MDS TD Series radio control devices that expose the Telnet protocol.
  - GE Telnet
    Use this strategy on General Electric devices that expose GE's telnet protocol flavor (e.g. controllers, or Mark panels).
  - Bosch Rexroth HTTP(S)
    Use this strategy on Bosch Rexroth devices that expose the HTTP(S) protocol.
  - Cognex HTTP(S)
    Use this strategy on Cognex devices that expose the HTTP(S) protocol.
  - Fanuc HTTP(S)
    Use this strategy on Fanuc devices that expose the HTTP(S) protocol.
  - GE Healthcare HTTP
    Use this strategy on General Electric devices hosting the Common Service Desktop web application.
  - GE Grid Solutions HTTP
    Use this strategy on General Electric Grid Solutions devices that expose the HTTP(S) protocol, such as the N60 Network Relay.
  - Lanner BMC HTTP(S)
    Use this strategy on Lanner devices mounting an American MegaTrends MegaRAC SP-X BMC solution that expose HTTP(S).
  - Schneider HTTP(S)
    Use this strategy on Schneider APC devices that expose the HTTP(S) protocol.
  - Sewio HTTP(S)
    Use this strategy on SEWIO UWB devices that expose the HTTP(S) protocol.
  - Tyan BMC HTTP(S)
    Use this strategy on Tyan devices mounting an American MegaTrends MegaRAC SP-X BMC solution that expose the HTTP(S) protocol.
  - Ubisense HTTP(S)
    Use this strategy on Ubisense assets that expose an HTTP user interface.
  - Inaba Choco Tei HTTP
    Use this strategy on Inaba Choco Tei devices that expose the HTTP protocol.
  - Mitsubishi Electric MELSOFT
    Use this strategy on Mitsubishi Electric devices that expose the MELSOFT protocols, such as: GOT1000, GOT2000, Q-Series, iQ-R Series.
  - IEC 61850-8-1 (MMS)
    Use this strategy on IED devices that expose the IEC 61850-8-1 protocol.
  - Modbus
    Use this strategy on devices that expose the Modbus protocol, e.g. Schneider Electric (SE) Modicon and PowerLogic ION, Emerson iPRO, Siemens S7 series. Note: Generic collected items are an approximate list. Specific items vary depending on the specific target OS version or local configuration and might not be available.
  - Moxa
    Use this strategy on Moxa devices that expose the Moxa proprietary protocol.
  - Moxa HTTP(S)
    Use this strategy on Moxa devices that expose the HTTP(S) protocol.
  - ONVIF HTTP(S)
    Use this strategy on devices that expose the ONVIF protocol on HTTP/HTTPS.
  - Owl OPDS SSH
    Use this strategy on Owl OPDS devices that expose the SSH protocol.
  - Phoenix Contact FL SWITCH TSN 2000 Series HTTP(S)
    Use this strategy on Phoenix Contact FL SWITCH TSN 2000 series devices that expose the HTTP/HTTPS protocol.
  - Phoenix Contact WP6000 HTTPS
    Use this strategy on Phoenix Contact WP6000 (HMI) devices that expose the HTTPS protocol.
  - Phoenix Contact mGuard
    Use this strategy on Phoenix Contact mGuard devices that expose the HTTPS protocol.
  - Phoenix Contact PLCNext HTTPS
    Use this strategy on Phoenix Contact PLCNext-based devices (e.g. AXC F 3152) that receive information by using the HTTPS protocol.
  - Reolink Baichuan
    Use this strategy on Reolink devices that expose the TCP Baichuan protocol.
  - Siemens STEP7
    Use this strategy on Siemens devices that expose the S7 protocol, such as 300/400/1200/1500.
  - SEL telnet
    Use this strategy on Schweitzer Engineering Laboratories devices exposing SEL's telnet protocol flavor.
  - SEL Axion HTTPS
    Use this strategy on SEL Axion/RTAC devices that expose the REST API over HTTPS.
  - Sensor Net Connect
    Use this strategy on Sensor Net Connect devices that expose their proprietary UDP-based protocol.
  - Shelly mDNS
    Use this strategy on Shelly devices that expose the mDNS protocol.
  - Siemens SIPROTEC HTTP(S)
    Use this strategy on SIPROTEC 4 or SIPROTEC 5 devices that expose the HTTP(S) protocol.
  - SNMP
    Use this strategy on devices that expose the SNMP protocol (v1, v2c, v3). It includes vendor-specific data extraction for the following device types: Brocade switches, Fortinet switches, Hirschmann switches, N-Tron switches, Schneider Electric APC PDUs.
  - SSH
    Use this strategy on devices that expose the SSH protocol. Note: generic collected items are an approximate list. Specific items vary depending on the specific target OS version or local configuration and might not be available. It includes vendor-specific data extraction for the following device types: Tridium Niagara (e.g. JACE 8000 and 9000 controllers).
  - Tattile NTCP
    Use this strategy on Tattile devices that expose the NTCP protocol.
  - Tyco exacqVision
    Use this strategy on Tyco exacqVision assets that receive information by using the HTTP protocol.
  - UPnP
    Use this strategy on devices that expose the UPnP service over HTTP(S).
  - Wago Management
    Use this strategy on Wago devices that expose the Wago management protocol.
  - WinRM
    Use this strategy on Windows devices that expose the WinRM service. Note: generic collected items are an approximate list. Specific items vary depending on the specific target OS version or local configuration and might not be available.
  - WMI
    Use this strategy on Windows devices that expose the WMI interface. Note: generic collected items are an approximate list. Specific items vary depending on the specific target OS version or local configuration and might not be available.
  - Zettler/Ezcare TCP Gateway HTTP
    Use this strategy on Zettler/Ezcare TCP gateway devices that expose the HTTP protocol.
- Print format documentation
  A list of all the print-format documentation that is available for Smart Polling.

Strategies overview

Smart Polling strategies are network-based methods that directly reach the monitored assets with concise, safe, and effective protocol-specific messages, enhancing visibility in the Nozomi Networks solution.

Strategies

Smart Polling strategies use various protocols to gain visibility in the network. They contact monitored assets directly, based on your configuration or through Discovery.

These strategies sometimes require credentials or other settings in the Smart Polling configuration. Make sure the Nozomi Networks sensor has network access to monitored assets and that firewalls do not block communications.

Credentials

Whether the strategy requires credentials to access target devices, and the credential scope it requires. Some strategies do not require credentials at all.

Device-side ports

The port or ports that must be reachable on the target device for the strategy to work. Make sure firewalls allow this traffic.

Arc availability

The Arc version since which the strategy is supported. Not every strategy is available on Arc.

Guardian availability

The Guardian version since which the strategy is supported. Not every strategy is available on Guardian.

Discovery trigger

For some strategies, whether devices found through a matching Discovery strategy are automatically polled by this strategy. Not every strategy has a corresponding Discovery strategy.

Collected items

The device attributes and properties that the strategy collects to enrich the monitored node. Collected items can vary depending on the device and its configuration.

Asset merging capabilities

Whether the strategy can merge nodes that represent the same physical device into a single asset, based on the information it collects.

Progressive mode queries

The query or queries that Progressive mode uses to automatically identify nodes that are suitable targets for the strategy.

Configuration parameters

For some strategies, the protocol-specific parameters you can configure from the command-line interface (CLI) to fine-tune its behavior. Not every strategy has configurable parameters.