For Gateway software known issues, see EcoStruxure IT Gateway known issues
If you’re experiencing Gateway appliance issues not on this list or if you have other feedback, please open a support ticket.
-
When the Gateway appliance starts up for the first time, a lost communication message may be displayed briefly while the appliance is initializing. Communication is automatically re-established without intervention.
-
When the Gateway appliance starts up for the first time, it takes a few minutes for its public network IP address to be assigned.
-
As of Gateway version 1.10, the Gateway appliance no longer supports IPv6.
-
Changes to NTP server settings cause an immediate reboot with no confirmation message.
-
When the appliance is reset to defaults, the time zone setting remains. Manually adjust the time zone on the Time Settings tab of the appliance private network user interface if needed.
-
The Gateway appliance NUC (INNUC0119) does not support the 24-hour time preference.
-
After restoring a Gateway appliance from backup, an error stating a certificate failed to restore may occur. This error is erroneous and can be disregarded.
-
Configuring an invalid subnet mask using the Gateway appliance private network CLI prevents the DHCP server from starting. You can no longer access the CLI or the Gateway application on the private network. Contact support for assistance.
-
Typing a backup config command incorrectly in the Gateway appliance private network CLI can change the location where backups are stored. No error is displayed; the new path is displayed in the console.
-
When you use the network configuration command net config --private --ip <some IP> in the appliance private network CLI to change the IP address of the Gateway appliance to a non-default address, you must change the IP address starting or ending address first to exclude that address from the DHCP scope.
You can then change the IP address of the Gateway appliance. Otherwise, an error occurs.
These changes require that you restart the DHCP server.
See How to restart the DCHP server on a Gateway appliance - version 1.1.0 and newer -
If you configure a Gateway for the private network interface in the private network CLI via SSH client, it can only be removed by setting its value to 0.0.0.0: net config --private --gateway 0.0.0.0.
Note: Making the private network routable by adding a Gateway on the appliance can cause connectivity issues, and is not recommended. -
An update failure message may be displayed when updating the Gateway software on the appliance to version 1.10.x or newer.
If your network configuration does not allow access to download yum packages, remote backups will not be available after updating the Gateway software on the appliance. The fs mount command to perform remote backups will fail. Local backups can be performed as expected.
Contact support for assistance resolving this issue.
Known issues in Gateway appliance version 1.9 and earlier
-
Starting with Gateway version 1.8.0, the Gateway appliance troubleshooting tool in Webmin incorrectly reports the HTTP status code for the Gateway Server Web API as 403 when the system is actually working normally. This is a false failure and should be disregarded.
Comments
0 comments
Please sign in to leave a comment.