**************************************************************************** Software Release: Secomea RDM 5.1 build 13025 - public release Release Date: 2013-01-11 **************************************************************************** (c) Copyright 2013, Secomea A/S. All rights reserved. **************************************************************************** **************************************************************************** Scope and production information **************************************************************************** This is Secomea Remote Device Management release 5.1 build 13025. This release note describes changes since release 5.0 build 12155, including changes in interrim release 5.0a (12224) and 5.0b (12266). Products covered: -------------------------------------------------------------------- SiteManager 3439 - Hardware, DIN mount, 4-port switch, integrated 3G SiteManager 1439 - Hardware, DIN mount, 4-port switch, integrated 3G SiteManager 3429 - Hardware, DIN mount, 4-port switch, ext 3G (USB) SiteManager 1429 - Hardware, DIN mount, 4-port switch, ext 3G (USB) SiteManager 3239 - Hardware, DIN mount, integrated 3G interface SiteManager 1039 - Hardware, DIN mount, integrated 3G interface SiteManager 3229 - Hardware, DIN mount, external 3G interface (USB) SiteManager 1029 - Hardware, DIN mount, external 3G interface (USB) SiteManager 3129 - Hardware, DIN mount, external 3G interface (USB) SiteManager 3034 - Hardware, DIN mount, 4-port switch SiteManager 3134 - Hardware, DIN mount, 4-port switch SiteManager 2029 - Hardware, external 3G interface (PCMCIA) SiteManager 2129 - Hardware, external 3G interface (PCMCIA) SiteManager 2034 - Hardware, dual DEV interfaces SiteManager 2134 - Hardware, dual DEV interfaces SiteManager Soft 6040 - Software, external agent support SiteManager PC 6240 - Software, internal agent support LinkManager 6041 - Software Related Products: -------------------------------------------------------------------- GateManager software release 5.1 or later is required to fully utilize the new features of RDM release 5.1. LinkManager Mobile software is released as part of the GateManager server, and is not covered by this release note. **************************************************************************** 1. Highlights of this release **************************************************************************** - SiteManagers with integrated UMTS modem now support local transmission of SMS Alert messages. Received SMS messages are also available via TCP or the serial port (by configuring the serial port as an "SMS modem"). - SMS Wakeup functionality has been modified to support receiving SMS'es. - Static server and device relays now support the FTP protocol. - Connectivity from LinkManager is no longer terminated if a USB attached device is restarted. - Improved USB plug'n'play handling, new Custom > USB agent. (#4824) [5.0b] - Support for new SiteManager 3429/3439/1429/1439 hardware models with 4-port switch, integrated 3G modem and USB interface. [5.0b] - SiteManager 1029 and 1039 now have support for AutoSubnet Agent [5.0a] - LinkManager and SiteManager Soft/PC tested on Windows 8. **************************************************************************** 2. New features and improvements **************************************************************************** LinkManager ------------------------------ - LinkManager will now automatically restore the USB connection to a USB attached device if the device disconnects and reconnects to the SiteManager USB interface (for example after downloading new program code to the USB device). Both LinkManager and SiteManager must run release 5.1 to facilitate this. (#5155, #5156) - Fix tray icon display of number of licenses used / available. (#4127) - Improve feedback to user when there are no free licenses on server. - Improved USB Agent handling in LinkManager. [5.0b] When connecting to a USB-enabled device, Windows' New Hardware Wizard will now display the Manufacturer and/or Product as device description. This resembles more closely the behavior of the native USB drivers, so there's a better chance of having the system load the correct driver automatically, and not handing it over to the composite parent driver unnecessarily. In case the system cannot find a suitable driver automatically, the user should now get a better clue to which driver to install, and not just go searching for a driver for "USB Device Over IP". (#4824) - LinkManager's connection trouble-shooter now offers to add a static DNS entry for the specified GateManager host name, if the host name is unknown or DNS lookup fails. [5.0b] SiteManager ------------------------------ - SiteManagers with integrated UMTS modem (xx39) now support sending SMS alerts via the integrated modem. (#4179 #5250) An SMS alert can be triggered via one of the INPUT ports, via the serial port, or by sending a suitable TCP or UDP request to the SiteManager. The recipient mobile number and message text of the SMS alerts are configured on the GateManager > Alerts page in the SiteManager. Or they can be included in the TCP/UDP alert request. NOTE: Only KNOWN devices (with a corresponding agent) can make TCP/UDP SMS alert requests, or query / receive SMS messages via TCP. It is possible to specify different recipients depending on "time of day" and "day of week". See the online help for more information. Locally transmitted SMS messages are logged in the GateManager audit log with pseudo username "(SMS)". GateManager 5.1 or later is required to properly display these messages in the audit log. - The serial port on SiteManagers with integrated UMTS modem, can be now be configured as an "SMS Modem" which can both send and receive SMS messages using the standard AT+CMG... commands and the +CMTI receive indication. Note that delivery of SMS messages is never guaranteed, so it is highly recommended to use the "request delivery receipt" feature of your mobile phone when you send an SMS to a SiteManager. Also notice that there is currently no access control or other types of validation or authentication of received SMS messages. Disclaimer: This is classified as an experimental feature in release 5.1. This means that it has passed the Secomea functional tests and QA, while it has not been verified to work as a plug-in replacement for other serial SMS modems in any specific customer applications. - SMS Wakeup functionality has been modified to work smoothly with receiving and forwarding of (other) SMS messages to agents (#5450): The SMS wakeup secret now defaults to "Wakeup" (it used to be empty). The wakeup wecret is now stored in a separate text field on UPLINK2 page. An existing secret configured as part of the "SMS Wakeup" field is automatically migrated to the new field. The SMS text must now start with the wakeup secret for the SMS to be recognized as a wakeup request (and then deleted); all other messages are saved and made available to agents (when applicable). The wakeup secret is NOT case sensitive! - Static Server and Device relays using TCP port 21 now support the FTP protocol in active and passive mode. Requires GateManager server running 5.1 or later. (#4089) - IP aliases can now be crated on SiteManager UPLINK interface. (#4657) - Improve responsiveness for multiple GateManagers and LinkManagers connected to the SiteManager at the same time. (#5191) - There is now an explicit GateManager "Connection Watchdog" parameter that controls the "reboot SiteManager if no GateManager connection" 1 hour timer. By default, the connection watchdog is now DISABLED on SiteManagers with an integrated 4-port switch and/or an integrated UMTS modem. - For SiteManagers with an integrated UMTS modem, there is now an additional (and independent) connection timer which will reset just the UMTS modem periodically if there is no GateManager connection. - Some network routing policies do not allow ToS (*) enabled (low-latency) frames, and will simply terminate such connections without notice. Initially changed in 5.0b, with further changes in 5.1. The SiteManager's connection to the GateManager and the EasyTunnel VPN traffic will try to utilize ToS to get the best end-to-end performance, but it failed to get a reliable connection in such ToS restrictive networks. SiteManager will now test for and avoid any ToS restrictions that may interfere with the GateManager and VPN connections. (#5149, 5153) (*) ToS = Type Of Service or DS(Diffrenciated Service) - It is also possible to completely disable ToS (if the normal ToS detection fails) by adding ::1 to the GateManager address, e.g. gm01.secomea.com::1 (or gm01.secomea.com:11444:1 if port number is specified). - SiteManager did not inform GateManager immediately when a LinkManager disconnected after doing "Connect All". (#5211) - SiteManager no longer terminates LinkManager connections for a USB agent if the USB device disconnects (assuming that it will reconnect soon). If LinkManager runs older firmware than 5.1, SiteManager will still terminate the connection, as only LinkManager 5.1 can properly handle USB device reconnect. (#5155, #5156) - The OUTPUT2 port (when available) can now be configured to signal the "GateManager connected" status. (#4838) - New "favourite icon" for SiteManager. - Add support for displaying domain logos in BMP format. (#5288) - Fix timestamp in TLS handshake to please some 3rd party firewalls. [5.0b] - Support FQDN in web-proxy address also when using NTLM. (#4826) [5.0a] - Add more APNs for TDC (4G), 3, and Oister. (#5226, #5420) - The UPLINK2 page now shows which APN is used (if different from the configured APN). (#4840) - Add support for Huawei HiLink modems (such as the E303). (#5221) - Added support for additional UMTS/3G dongles like ZTE MF652. (#5097) [5.0a] Device Agents ------------------------------ - When you create a new agent (click "New" on GateManager > Agents page), you just have to select the Agent Type and click on "Save"; by leaving the name or parameters field empty the Agent's Parameter Details page opens automatically to let you complete the agent configuration. (#3264) - Go To Device from GateManager and LinkManager Mobile using relevant WWW, VNC and RDP services is now enabled by default for all vendor agents. This is considered safe, as using Go To Device from GateManager and LinkManager Mobile will now turn on the OUTPUT1 port for these services. If Go To Device for a specific service it is deemed safe, it is possible to disable the OUTPUT1 signal on a per-service, per-agent basis. It is possible to explicitly limit access to a specific service to the LinkManager in the connected state; this may be necessary if the service relies on other connections not available through ordinary Go To Device. Furthermore, additional VNC, RDP, and WWW services can be easily enabled for all vendor agents if a device supports those services. (#5315) - All vendor agents now support adding specific ports and services. [5.0b] The standard agent ports are shown by hovering the mouse over the fields. (#5140, #5141) - New Custom > USB Agent. [5.0b] This agent is used to setup a USB agent for USB devices which do not have a pre-defined vendor agent. Note that although it is possible to configure an agent for any USB device, not all USB enabled devices will be fully functional, and the only way to verify the compatibiliy of a device is by Trial-and-Error. (#5118) - The https/http proxy function on the GateManager can now be disabled on a per-agent basis by specifying the +noproxy option on the agent. (#5201) - Serial agents can now overrule the port settings normally controlled by LinkManager's virtual COM Port). To do so, add a `!' mark before the speed setting, e.g. !19200. (#5150) - Forwarding Agent may now use an alias IP in the IN_IFACE part. (#4657) - Recognize USB devices with zero product id. (#5205) - New Device Agents: - Beijer iX (#5121) [5.0b] - Crouzet Millenium 3 [USB] - Crouzet Serial PLC (#5272) - Exor UniOP HMI (Serial) (#5293) - Hakko HMI [USB] - ifm AS-i safety monitor [USB] - Kawasaki Robotics Ethernet - Kvaser USB/CAN Adapter - Lenze Ethernet - Lenze USB - Omron NE1A-SCPU Safety Controller [USB] - Omron NQ HMI [USB] - Panasonic HMI GT32 [USB] - Phoenix Contact PSR-TRISAFE safety controller [USB] [5.0b] - Rockwell Automation/Allen-Bradley USB-Serial Adapters - Saia-Burgess Ether-S-Bus devices (*1) - Sauer-Danfoss CG150 (use Kvaser USB/CAN Adapter agent) - Schneider Magelis HMI [USB] [5.0a] - Siemens AG CP 5711 - PROFIBUS adapter [USB] - Siemens USB/PPI Multi-master Cable - Weintek Ethernet HMI (#5405) - Updated Device Agents: - ABB PLC (#5204) - ABB Serial PLC (#5276) - B&R Ethernet - B&R HMI model 300/400 (*2) - Beckhoff PLC (option to enable Shared Folder access) - Fatek PLC (#5263) - Hilscher NetLink - IMO Ethernet (#5032) [5.0a] - Mitsubishi PLC - Mitsubishi Serial PLC (option to disable flow-control) (#5422) - Pro-Face HMI (#5329) - Schneider Ethernet (#5063) - Siemens Ethernet (optional HTTPS service) (#5400) - Siemens PPI (improved serial protocol stability) (#5046) [5.0b] - VIPA Panels (HTTP support) (#5158) [5.0b] *1) The Ether-S-Bus agent has optimized program and data exchange over the UDP protocol (experimental). Both SiteManager and LinkManager must run 5.1 release or later. (#5305) *2) B&R HMI model 300/400 Agent now supports TCP-based up- and downloading for significantly improved performance. For more information, see the B&R documentation for /APN and /ANSL options (default enabled). (#5160) [5.0b] **************************************************************************** 3. Bug Fixes. **************************************************************************** LinkManager ------------------------------ - SMS Wakeup information was shown incorrectly in LinkManager Console. - A race in the TCP connection setup between LinkManager and a SiteManager using UPLINK2 would sometimes drop data from the device if it was the first party to send data on the new connection. (#5444) SiteManager ------------------------------ - In areas with limited 2G/3G coverage, SiteManagers with built-in UMTS modem would sometimes fail to connect, or only connect with 2G even when 3G is available. (#5383) - Ignore/reset stored configurations in built-in modem; in some cases, the modem would remember - and use - previous DNS settings, which led to failures if the SiteManager was moved to another location/network. (#5450) - Opening an Agent Details page would cause the configuration to be marked as changed, forcing a configuration backup on GateManager on the next heartbeat. (#5341) - Setup Assistant would sometimes incorrectly report that the GateManager connection had failed, even though a working connection exists. (#5379) - The WAN probe did not recover correctly if hostnames could not be resolved due to DNS lookup failures. (#5377) - During system reboot, random data was sometimes output on the serial port. (#5378) - Prevent irrelevant "save username and password" popup from browser, when saving configuration pages which includes a password field. - Don't attach agents that have failure status, like a Siemens USB Agent that is unplugged. Previous firmware would still show the agent in LinkManager and could result in a crash of LinkManager if the user [5.0a] - Modify auto-login for Go To Appliance function in GateManager to work with Chrome 19 and other browsers which ignore the user name [5.0a] - Fix random "Invalid handshake" failures when connecting to GateManager [5.0a] - Fix problem with partial loss of configuration in rare cases. (#5064) [5.0a] - It is now possible to move from one GateManager 5 server to another by using Appliance Launcher (as well as in the web GUI). (#5070) [5.0a] Device Agents ------------------------------ - Fix connection issues with Danfoss AKM Gateway. (#5059) [5.0a] - Fix UDP broadcast support in ABB PLC, KUKU Controller, and Generic 2-way NAT agents. [5.0b] **************************************************************************** 4. Upgrade information. **************************************************************************** Software Products ----------------------------------- - Please notice that all Software products - LinkManager, SiteManager Soft, and SiteManager PC - must be upgraded by running the corresponding Setup program using an administrator account. Except for SiteManager Soft, you must use the Setup program corresponding to the Windows architecture (32 or 64 bit). - LinkManager and SiteManager PC come with a set of Windows drivers that will be installed or upgraded when running the Setup program. You may have to confirm the installation of these drivers. - First time you start LinkManager after the upgrade (or after a new installation), you may be prompted to accept the installation of Secomea's CA certificate as a trusted root certificate. You should allow this to prevent Windows from looking for new drivers on the Windows Update site each time you establish a serial or USB connection. - SiteManager Soft requires VMware to operate, also after the update. **************************************************************************** 5. Known issues or limitations **************************************************************************** - Due to restrictions on secure web-site certificate authentication, Internet Explorer 7, Firefox 3, or newer may prevent you from accessing https based services via the LinkManager's Go To Appliance functionality in the non-activated state (Domain view). This is because the Go To Appliance function uses a different IP address than the actual IP address of the remote device, so the browser suspects that the target device's certificate (typically self-signed) may be a forgery. There is no easy way to get around this problem, so you will have to follow the somewhat tedious procedure of your browser to bypass the warnings and connect to the device anyway. Note: You should not store the certificate permanently in Firefox. Using Go To Appliance in GateMananger or LinkManager Mobile does not have this issue. - SiteManager Soft currently does not run as a service under Windows 7 & 8 64 bit OS. Instead it must be started in User mode, by adding it to the Startup folder. - Please note that using the PPI option require optimal bandwidth for both the LinkManager and the SiteManager. This is due to the PPI protocol and Step7 software per design does not take into account the delays (latency) that may occur when relaying the communication over long distances. - Even though it is possible to configure multiple USB agents on a given SiteManager, it is currently not possible to connect to more than one at a time from a given LinkManager. This means that if multiple USB agents exist on a SiteManager, you should *not* use . This limitation will be resolved in a future LinkManager version. **************************************************************************** END ****************************************************************************