Troubleshooting

EcoStruxure IT Gateway restore fails when the locale of the Windows computer where the Gateway is installed is set to Italian, Portuguese, or Spanish. Set the operating system locale to English to perform the restore.  

Issue Some Gateway Appliances were shipped with bad ISO images. The networking functionality does not work properly on affected units.    Symptoms A system plugged into LAN 2 is unable to receive a DHCP address  A system plugged into LAN 2 with a statically assigned IP is unable to reach Webmin  The appliance does not receive an IP address when connected on LAN1  Affected Units Affected units were assembled in or prior to November 2019.  The assembled date is found on the package label.   appliance_assembly_date_360016634397.png   What To Do Contact Customer Support for assistance with this issue.      

When the Gateway is unable to keep up with the polling interval for a device, a Device Communication Alert warning alarm is generated. The alarm message is <device name> is responding slowly to polling. The Device Communication Alert alarm is generated after five consecutive polls exceed the polling interval. The alarm clears after five consecutive polls complete within the polling interval. You can do one or more of the following: Reduce the number of devices the Gateway is polling at 1 minute (Gateway 1.13 and newer). Reduce the number of devices the Gateway is polling. Add more CPU and memory to the Gateway. Investigate network latency issues, or put the Gateway on the same local area network (LAN) as the device.  

  Some Galaxy UPSs report serial numbers that are not unique, such as XXXXXXXXXX or 0123456789. These serial numbers are unsupported in EcoStruxure IT Gateway version 1.9.0 and newer. If you discovered a Galaxy device that reports these generic serial numbers, the Galaxy device will show as offline after the Gateway is updated to version 1.9.0 or newer, and a new Galaxy device will be added with a unique identifier. You can delete the offline Galaxy devices from the device list.

The EcoStruxure IT Gateway must uniquely identify devices to support data analytics and sensor history. The Gateway attempts to use the device's serial number as the unique identifier whenever possible, since IP addresses change, devices are removed and re-added to a network, or a device is connected to different Gateways.  In some cases, the device serial number must be set manually. Device serial number is missing or invalid In most cases, if the serial number is missing or empty, or it matches a list of invalid values like1234567890 or N/A, the Gateway attempts to use the MAC address for SNMP or the IP Address + server ID + port for Modbus. This not perfect for this situation, but it is the best alternative. If the Gateway fails to find a unique identifier, the device discover fails and is reported the Gateway's discovery log. Devices have the same unique identifier If two devices have the same unique identifier, usually one device will be discovered, and then when the second is discovered, the first will be removed and replaced by the second since it appears to be the same device. In some cases, depending on the timing, both devices could be discovered, and then will lose connectivity when the Gateway is updated to the next version.  Manually set the serial number on a device You might need to set the serial number on a device if a unique identifier cannot be not found. Consult the documentation or the device's manufacturer for how to do this if necessary. If you can update the serial number manually, it's most likely done through the device's own user interface. It might also be possible to set it using SNMP or Modbus. Contact customer support if you need assistance. You may need to supply the SNMP MIB or Modbus map to determine the address of the serial number.    

  When you replace a device and reuse the IP address and device configuration credentials from the old device, the new device will show as offline in the Gateway. Delete the offline device from the Gateway device list, and then manually rediscover the new device. How to replace a device in EcoStruxure IT Gateway

Support for unsafe ciphers was removed as part of a security update in EcoStruxure IT Gateway version 1.8.0. Devices using the Redfish protocol must now support 2048 bit certificates.  Symptom Devices that do not meet this requirement do not discover in Gateway 1.8.0 and newer. There is no indication of a certificate error when you run a new discovery. When you update your Gateway from a previous version, Redfish devices are listed as offline. Resolution Install a new certificate on the Redfish device that supports 2048 bit server certificates.

Support for unsafe ciphers was removed as part of a security update in EcoStruxure IT Gateway version 1.8.0. NetBotz 4.x devices must now support 2048 bit certificates.  Symptom Devices that do not meet this requirement do not discover in Gateway 1.8.0 and newer. There is no indication of a certificate error when you run a new discovery. When you update your Gateway from a previous version, NetBotz devices are listed as offline. Resolution Install a new 2048 bit certificate on the NetBotz device. Self-signed automatically generated SSL certificates use 2048-bit encryption as of NetBotz version 4.5.4.

This tool can walk SNMP1, SNMP3, Modbus, Redfish, NetBotz, and FTP devices, gathering current values or files to facilitate DDF development or debugging for Data Center Expert or EcoStruxure IT Gateway.   Specific information about how to create a walk file for different DCE versions is here.   Modbus.org announced it is expunging all occurrences of inappropriate language of the query and response paradigm of Modbus communications. This tool was updated to comply as of version 1.9.1. More...   Requirements   Windows 10+ or Windows Server 2012+ Admin access to Command Line or Windows PowerShell   Getting started   Unzip the file walker_version_Windows.zip Navigate to the folder you unzipped in step 1.  There should be a file called "walk.bat" in the folder. Right click the folder and click Open.   How to run your first command   The general usage is: <protocol> -ip <ip> <options>   Example: snmp -ip 192.169.0.10   Note: To read more about each command while you run the program, type help followed by the command you need help for. Example: help snmpv3   idea_icon_360009259237.png There are several example commands below. Make sure to follow the structure carefully.   Running a command generates a walk file that is named using the IP address and a *.walk, *.json, *.txt", or *.xml extension. The file is saved to the folder where you ran the .bat script. If you are running a walk that retrieves raw files, such as FTP, these are saved as files.zip.   Example output: 192.169.0.10.xml Example with file retrieval: 192.169.0.10.txt and files.zip   Troubleshooting   If you're having trouble connecting to a physical device, check with your network administrator to confirm that the device is enabled for the protocol and login credentials (if applicable) you are using to connect.   Device walks can take a long time to complete. A walk usually completes within 20 minutes for a slow connection.   If your walk fails to complete, it might be worth taking a break. Many protocols struggle to handle excessive repeated requests. If the walk seems to be hanging, try waiting a few hours and try again; this gives the device time to discard any old sessions and start accepting new ones. If the walk still fails, contact support for assistance.   Usage details   SNMP V1   Defaults   - ip: REQUIRED - port: 161 - file: <ip>.walk - read: public - write: private - retries: 2 - timeout: 5 - enableBulkRequest: false   Examples   snmp -ip 192.169.0.10 snmp -ip 192.169.0.10 -port 8161 snmp -ip 192.169.0.10 -read pass   SNMP V3   Argument valid values   - authType: MD5, SHA - encType: DES, DES3, AES128, AES192, AES256   Defaults   - ip: REQUIRED - port: 161 - file: <ip>.walk - username: REQUIRED - authType: - authPassword: - encType: - encPassword: - retries: 2 - timeout: 5 - enableBulkRequest: false   Examples   snmpv3 -ip 192.169.0.10 -port 161 -username XXXX -authType MD5 -authPassword XXXX -encType DES -encPassword XXXX   snmpv3 -ip 192.169.0.10 -port 161 -username XXXX -authType SHA -authPassword XXXX -encType AES128 -encPassword XXXX    snmpv3 -ip 192.169.0.10 -port 161 -username XXXX    snmpv3 -ip 192.169.0.10 -port 161 -username XXXX -authType SHA -authPassword XXXX    Modbus   This requires a separate text file specifying which registers to read. See input.txt for formatting and examples.   WARNING: Excessive Modbus requests can overwhelm the device. Keep the number of selected registers as small as possible.   Defaults   - <ip>: REQUIRED - port: 502 - file: - server: 1 - input: input.txt - maxReads: 100 - walk: true - function: - start: 1 - count: - print:   Examples   modbus -ip 192.169.0.10   modbus -ip 192.169.0.10 -port 5020 -server 2 -input registers.txt   Redfish   Defaults   - ip: REQUIRED - port: 443 - file: <ip>.json - username: REQUIRED - password: REQUIRED   Example   redfish -ip 192.168.0.10 -username user1 -password pass   NetBotz   Defaults   - ip: REQUIRED - port: 80 - file: <ip>.json - username:  - password:  - useSSL: false   Examples   netbotz -ip 192.168.0.10 -username user1 -password pass   netbotz -ip 192.168.0.10 -username user1 -password pass -useSSL   FTP   Defaults   - ip: REQUIRED - port: 21 - file: <ip>.json - username:  - password: - walk: true - download_file:   Example   ftp -ip 10.155.55.55 -username apc -password apc