Network connection related problems - Metasys - LIT-12013352 - M4-SNE10500-0 - M4-SNE10501-0 - M4-SNE11000-0 - M4-SNE11001-0 - M4-SNE110L0-0 - M4-SNE110L1-0 - M4-SNE22000-0 - M4-SNE22001-0 - Supervisory Device - SNE10 Network Engine - SNE11 Network Engine - SNE22 Network Engine - SNE Supervisory Network Engine - 12.0

SNE Commissioning Guide

Brand
Metasys
Product name
SNE10 Network Engine
SNE11 Network Engine
SNE22 Network Engine
SNE Supervisory Network Engine
Document type
Commissioning Guide
Document number
LIT-12013352
Version
12.0
Revision date
2022-12-12
Product status
Active
Language
English

Many network connection and communication problems result from incorrect device names, incorrect IP addresses, or other attribute value errors entered into the Site Management Portal UI or into the UI of the associated network devices. If the SNE attribute values do not match the values entered in the devices connected to the SNE, the SNE and associated devices may not establish network connections or communications.

Check the device names, IP addresses, gateway, subnet masks, ports, baud rates, and other network parameters in the Site Management Portal UI. Also check the servers, computers, and field devices connected to the SNE, and ensure that the attribute values are correct for each computer or device.

For example, communication between a Site Director and an SNE could be lost after downloading the network engine with SCT. This may occur on a network where device name resolution is not implemented. To resolve this communication issue, log in to the SNE after the download and change the Local Site Director field back to the IP address of the Site Director. Within minutes after you save this change, the engine comes back online to the Site Director.

See Determining the SNE IP address and device name for a network connection and Verifying Ethernet network communications (Ping).