ENLYZE
🇬🇧 ENLYZE
🇬🇧 ENLYZE
  • Welcome to ENLYZE
  • Getting Started
    • Quickstart
  • Guides
    • Platform Configuration
    • Machine Setup
      • Variable Selection
      • Configuring OEE Data Collection
      • Machine Data Sheet Template
    • Defining Downtime Reasons
    • Downtime Contextualisation
    • Connecting Booking Data
      • Integration of MES, BDE, or ERP-Systems
      • Synchronising Production Context via Machine Data
      • Booking Production Orders via the ENLYZE App
    • SPARK Setup
      • Preparations
      • Installation
      • Connecting to the Manufacturing Data Platform
    • ENLYZE EDGE
      • Accessing the Interface
      • Configuring the Network
      • Setting Up Routes
      • Managing Routes
      • Network Tools
      • Troubleshooting
  • PLATFORM
    • Integrations
      • Grafana
        • Structure of the ENLYZE Data Sources for Grafana
        • Connecting ENLYZE to Grafana
        • Tutorials
          • First steps with Platform Grafana
          • Grafana Basics for Process Monitoring
          • OEE data with Infinity data source
          • Mapping UUIDs to Display Names with Infinity Data Source
      • Power BI
        • Installing the ENLYZE Power BI Integration
        • Structure of the ENLYZE Power BI Connector
        • Tutorials
          • Getting Started with the ENLYZE Power BI Connector
          • Querying Time Series Data from Machine Variables
          • Querying Machine Productivity Metrics
          • Mapping UUIDs to Display Names
          • Calculating Aggregated Timeseries Data
  • EDGE
    • Overview EDGE Functionalities
    • SPARK Edge Device
    • ENLYZE EDGE
  • IT Security
    • IT Security
  • Why is the connection secure even though a warning is displayed
  • How to Choose the Right Integration Scenario?
  • Resources
    • Glossary
Powered by GitBook
On this page
  • Ping for IPv4 Addresses
  • Accessing Network Tools
  • Enter IP Address and Start the Query
  • Display of Terminal Output
  • Interpreting the Terminal Output
  • Possible Reasons for Failed ping Queries
  1. Guides
  2. ENLYZE EDGE

Network Tools

Check the Reachability of Data Sources in the Network

PreviousManaging RoutesNextTroubleshooting

Last updated 14 days ago

Ping for IPv4 Addresses

With the ENLYZE Edge ping query, you can check the connection to an IPv4 address.

1

Accessing Network Tools

To execute a ping query using ENLYZE Edge, open the for the respective SPARK and navigate to “Network Tools”.

2

Enter IP Address and Start the Query

Enter the IP address of the device you want to ping and click the “Dispatch Ping” button.

3

Display of Terminal Output

ENLYZE Edge displays the terminal output of the ping command. This provides insights into whether the network device is reachable via ICMP Echo requests.

A successful ping confirms that the target network participant is reachable at the specified IP address from the SPARK. As a next step, you can proceed to add the data source to be connected.

Interpreting the Terminal Output

A successful ping response confirms the network participant is reachable via the given IP address from the SPARK. This allows for the subsequent connection of the desired data source.

Example of a successful ping:

PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=117 time=19.646 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=18.460 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=117 time=21.537 ms

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 18.460/19.881/21.537/1.267 ms

If the query fails, as shown below, this does not necessarily mean there is no network connection between the SPARK and the other device:

PING 172.192.20.2 (172.192.20.2): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1

--- 172.192.20.2 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss

Possible Reasons for Failed ping Queries

  1. Device is turned off The target device might be powered off or not connected to the network.

  2. Device blocks ICMP

    Some devices can be configured to suppress ICMP Echo replies.

    Note: ICMP replies can be disabled or enabled via the device's OS settings.

  3. A firewall blocks ICMP

    If traffic between the SPARK and the device passes through a firewall, certain rules might block ICMP Echo replies.

    Note: ICMP replies can also be managed in the firewall settings.

  4. No, or incorrect route If the device is not part of the SPARK’s link-local networks, a missing or misconfigured route could cause the ping to fail. Routes can be easily configured and managed via the ENLYZE Edge web interface.

Even if a ping fails, the device may still offer services over TCP or UDP. Tools like telnet <host> <port>, curl, or port scanners such as nmap can help verify connectivity using alternative protocols.

interface
ENLYZE EDGE Homepage