i.LON® 600 LonWorks®/IP Server ReadMe File
Release 1.04, August 2005
Copyright © 1998 – 2005 Echelon
Corporation
All Rights Reserved
This file describes i.LON 600 Release 1.04, which is created by applying i.LON 600 Service Pack 4 (“SP4”) to a Release 1, 1.01, 1.02, or 1.03 i.LON 600 installation, and is included on i.LON 600 servers that come with the i.LON 600 Service Release 4 (“SR4”) CD. Release 1.04 provides important updates to the i.LON 600 firmware. The service pack is delivered as a self-extracting executable file of approximately 2.2 megabytes, whereas the service release is delivered on a CD.
Update and upgrade notifications will be sent to registered users, so be sure to register your software.
If you are using the LonMaker® Integration Tool or other LNS application with an IP-852 channel interface on your computer, you must use the latest service packs for these products. LonMaker and LNS service packs are available from Echelon’s Download Center at www.echelon.com/downloads.
This file contains important information not included in the i.LON 600 LonWorks/IP Server User's Guide or the i.LON 600 LonWorks/IP Server help file. Additional information and updates, including critical updates, may be available on the i.LON 600 Internet Server Web page at www.echelon.com/ilon. See Echelon’s Knowledge Base at www.echelon.com/support for answers to frequently asked questions.
4 Identifying your i.LON 600 Release
5 Installing i.LON 600 Service Pack 4
6 Installing i.LON 600 Service Release 4
7.3 Config.sys File Corruption
9.7 Channel Configuration Timestamps
10 Known Problems and Workarounds
10.1 i.LON 1000 Internet Server Upgrade
10.2 Configuration Server Icon Color
Release |
Date |
i.LON 600 LonWorks/IP Server Release 1 (V1.00.24) |
December 2003 |
i.LON 600 LonWorks/IP Server Release 1 Service Pack 2 (V1.02.05) |
March 2005 |
i.LON 600 LonWorks/IP Server Release 1 Service Pack 3 (V1.03.03) |
April 2005 |
i.LON 600 LonWorks/IP Server Release 1 Service Pack 4 (V1.04.01) |
August 2005 |
i.LON 600 LonWorks/IP Server Release 1 Service Release 3 (V1.03.03) |
April 2005 |
i.LON 600 LonWorks/IP Server Release 1 Service Release 4 (V1.04.01) |
August 2005 |
You can determine whether or not you already have Release 1.04 firmware installed on your i.LON 600 server. To determine the firmware version running on your i.LON 600 server, follow these steps:
You must install i.LON 600 Service Pack 4 over an existing i.LON 600 installation. To install i.LON 600 Service Pack 4, follow these steps:
You can install Release 1.04 from an i.LON 600 Service Release 4 CD with or without a prior i.LON 600 installation. To install an i.LON 600 Service Release 4 CD, follow these steps:
This section describes the problems fixed and other changes in Release 1.04 that were not included in the Release 1 i.LON 600 server. Numbers in parentheses at the end of the change descriptions are Echelon's internal problem tracking IDs. Release 1.04 includes all changes from Releases 1.02 and 1.03, which are described following this section.
There were incompatibilities in certain versions of the i.LON 600 system software and boot-ROM software which, in conjunction with a design error in manufacturing revision F or lower of the Models 72603 and 72604 i.LON 600 power failure detection circuit, could result in continuous rebooting of the system or boot-ROM software. Models 72603 and 72604 with a manufacturing revision F or lower and with system software version 1.02 or 1.03, or with boot-ROM software version 1.03 require SP4 to be installed to remedy this condition. (37999)
The hardware version number is now shown on the System Info Web page below the model number. It is also available from the console using the show hwinfo command.
The config.sys file may have been corrupted during a power failure. (38040)
This section describes the changes in Release 1.03.
The i.LON 600 can now be used as a remote network interface for Echelon’s LonScanner™ Protocol Analyzer.
This section describes the problems fixed and other changes in Release 1.02.
The Ethernet interface would lock up after receiving a number of certain unsupported packets, particularly ARP broadcasts using IEEE 802 Ethernet framing, which may be sent by Novell Netware servers. (30857 and 34192)
HTTP requests containing a URL longer that 1024 bytes could crash the i.LON 600 Web server. (33328)
Changing the channel priority of the TP/FT-10 or TP/XF-1250 side of the i.LON 600 router would cause communications over that channel to fail. (34626 and 35273)
The i.LON 600 TCP/IP stack was vulnerable to certain known Denial-of-Service attacks. Refer to the NISCC Vulnerability Advisory Notice 236929 for more details. (35276)
Changing the IP-852 IP port on the i.LON 600 and rebooting it without first updating the IP-852 channel with the Configuration Server could cause communications to the i.LON 600 over the IP-852 channel to fail. (35367 and 35283)
The TXID field in the program ID for the IP-852 channel side of the i.LON 600 router has been changed to 154, the LonMark designated ID for IP-852 channels. (35274)
Rebooting the i.LON 600 through the Web interface or the console no longer causes an automatic change to the IP-852 channel definition timestamps, provided none of the actual configuration data has changed. (35284)
This section lists known problems and their workarounds for this release. Numbers in parentheses at the end of the problem/workaround descriptions are Echelon's internal problem tracking IDs.
Uninstalling a previous i.LON 1000 Internet Server installation can damage the i.LON 600 server installation. If you install the i.LON 600 software over an existing i.LON 1000 Internet Server installation and then uninstall the i.LON 1000 software, the i.LON 600 Configuration Server is also removed. (30171) Workaround:
When setting up an IP-852 channel using the configuration server, the health and state of the devices in the channel are indicated by the icon color in the configuration server’s channel list. Generally speaking “green” indicates that all devices are responding and are active members of the channel. The color of the device icon, however, is not a definitive indication of device health—it only indicates that the device has passed common device setup. Workaround: If you have a channel that seems to lose communication, click Diagnose on either the channel or device shortcut menu to diagnose the channel. This provides a more definitive diagnostic than icon the color. Look for error messages in the configuration server’s log window when using the Diagnose command.
Due to variations in the IP-852 implementation, the diagnose function may not work properly with some non-Echelon IP-852 devices.