i.LON® 600 LonWorks®/IP-852 Router ReadMe
Release 1.07, May 2011
Copyright © 1998 –
2011 Echelon Corporation
All Rights Reserved
This document describes i.LON 600 LonWorks/IP-852 Router Service Release 7 (SR7) and Service Pack 7 (SP7). The i.LON 600 SR7 software is shipped with i.LON 600 routers that include an i.LON 600 SR7 CD, and you can download and apply i.LON 600 SP7 to update previous i.LON 600 installations to the same version of the i.LON 600 software that is included with i.LON 600 SR7. The i.LON 600 SP7 update is available from www.echelon.com/ilon.
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 www.echelon.com/downloads.
Additional information and updates, including critical updates, may be available at www.echelon.com/ilon. See Echelon’s Knowledge Base at www.echelon.com/support for answers to frequently asked questions.
See Documentation for a description of changes to the documentation for the i.LON 600 router and software.
4 Identifying your i.LON 600 Release
5 Installing i.LON 600 Service Pack 7
6 Installing i.LON 600 Service Release 7
7.1.1 Standalone Echelon IP-852 Configuration Server
7.1.2 64-bit Windows Compatibility
7.2.1 Ethernet Speed and Duplex Override
7.2.3 Flash Disk Driver Improvement
7.4.3 Config.sys File Corruption
7.6.4 TCP/IP Denial-of-Service
7.6.7 Channel Configuration Timestamps
8 Known Problems and Workarounds
8.1 i.LON 1000 Internet Server Upgrade
8.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 Pack 5 (V1.05.01) |
September 2005 |
|
i.LON 600 LonWorks/IP Server Release 1 Service Pack 6 (V1.06.01) |
August 2006 |
|
i.LON 600 LonWorks/IP-852 Router Release 1 Service Pack 7 (V1.07.06) |
May 2011 |
|
|
|
|
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 |
|
i.LON 600 LonWorks/IP Server Release 1 Service Release 5 (V1.05.01) |
September 2005 |
|
i. LonWorks/IP Server Release 1 Service Release 6 (V1.06.01) |
August 2006 |
|
i.LON 600 LonWorks/IP-852 Router Release 1 Service Release 7 (V1.07.06) |
May 2011 |
You can determine whether or not you already have Release 1.07 firmware installed on your i.LON 600 router. To determine the firmware version running on your i.LON 600 router, follow these steps:
If you received the i.LON 600 software on a CD packaged with an i.LON 600 router, follow the SR7 installation instructions in the next section. If you received the i.LON 600 software as a service pack that you downloaded from the Echelon Web site, follow the instructions in this section.
The i.LON 600 service pack is compatible with the following versions of Windows:
· Windows 7 (64-bit and 32-bit versions)
· Windows Server 2008 R2 (64-bit version)
· Windows Vista (32-bit versions)
· Windows XP (32-bit versions)
You must install the i.LON 600 service pack over an existing i.LON 600 software installation. To install i.LON 600 Service Pack 7, follow these steps:
If you received the i.LON 600 software on a CD packaged with an i.LON 600 router, follow the SR7 installation instructions in this section. If you received the i.LON 600 software as a service pack that you downloaded from the Echelon Web site, follow the instructions in the previous section.
The i.LON 600 service release is compatible with the following versions of Windows:
· Windows 7 (64-bit and 32-bit versions)
· Windows Server 2008 R2 (64-bit version)
· Windows Vista (32-bit versions)
· Windows XP (32-bit versions)
You can install the i.LON 600 SR7 software from an i.LON 600 Service Release 7 CD. A prior installation of the i.LON 600 software is not required, but may be present. If you are installing the i.LON 600 software on Windows 7, you may see several warning dialogs during the installation process. You can safely ignore these warnings. To install the i.LON 600 SR7 software from an i.LON 600 SR7 CD, follow these steps:
This section describes the problems fixed and other changes in Release 1.07. Numbers in parentheses at the end of the change descriptions are Echelon's internal problem tracking IDs. Release 1.07 includes all changes from Releases 1.02, 1.03, 1.04, 1.05 and 1.06, which are described following this section.
The configuration server required to use the i.LON 600 router as an IP-852 to LonWorks router and previously included with the i.LON 600 software is now available as a free download from www.echelon.com/ilon. Unlike previous releases, this release can be used with any combination of Echelon and CEA-852 compliant third party IP-852 routers.
The Echelon IP-852 Configuration Server required to use the i.LON 600 router as a LonWorks/IP-852 router, and the OpenLDV driver required to use the i.LON 600 router as a remote network interface (RNI) are now both compatible with both 64-bit and 32-bit versions of Windows 7 and with the 64-bit version of Windows Server 2008 R2.
The following problems have been fixed:
· The Ethernet interface would lock up after receiving a number of certain unsupported packets, including mal-formed ARP broadcasts. (56691)
· Acknowledgements would sometimes be delayed by approximately 300 ms on a heavily loaded TP/XF-1250 channel. (59755)
A new i.LON 600 diag network console command has been added to show network-related information for diagnostic puposes. To use the new command, enter the following: diag_network <category>, where category is one of the following values:
inetstatShow
ipstatShow
tcpstatShow
udpstatShow
ifShow
sysPoolShow
dataPoolShow
netPoolShow
or all to show all of the above
Use the all category to collect comprehensive diagnostic information.
This section describes the problems fixed and other changes in Release 1.06. Numbers in parentheses at the end of the change descriptions are Echelon's internal problem tracking IDs. Release 1.06 includes all changes from Releases 1.02, 1.03, 1.04 and 1.05, which are described following this section.
You can now set the Ethernet speed and duplex system to a fixed value, overriding the automatic negotiation setting. Using the new Ethernet Mode property on the TCP/IP configuration Web page, you can select one of the following Ethernet modes: auto-negotiation (this is the default), 100 MB full-duplex, 100 MB half-duplex, 10 MB full-duplex, and 10 MB half-duplex.
Alternatively, you can set the Ethernet mode from the console by entering the following command: ethernetspeed <mode>, where mode is either auto (auto-negotiation), 100f (100 MB full-duplex), 100h (100 MB half-duplex), 10f (10 MB full-duplex), or 10h (10 MB half-duplex).
You must reboot your i.LON 600 server to implement changes made to the Ethernet mode. (41233)
You can now use the i.LON 600 server as a remote network interface (RNI). If you are updating an i.LON 600 router using a firmware release prior to Release 1.06, you must do the following to use it as an RNI (if you have Release 1.06 or newer you can skip step 1):
NOTE: The LonWorks Interfaces application is part of the OpenLDV driver. The OpenLDV driver is available as a free download from www.echelon.com/ilon, and is also included as part of a number of Echelon products including the LonMaker Integration Tool, LonScanner Protocol Analyzer, and the SmartServer Energy Manager.
These steps are further explained in the following sections.
For updated i.LON 600 servers, you can create and activate the i.LON 600 RNI application using one of the following two methods. If you are using an i.LON 600 router with software release 1.06 or newer, this step is not required.
· Method 1: Connect an EIA-232 USB interface or a serial cable to the console connector of your i.LON 600 router (further instructions are under section 5, step 9) and then enter the following command: createapp RNI. The RNI application is created in the console application with an index of 3 and is activated. Enter the listapp command to verify this.
· Method 2: Using an FTP client, go to the root directory of your i.LON 600 router and then delete the ltConfig folder (this deletes the current LonTalk configuration data of your i.LON 600 router), reboot your i.LON 600 router, and then recommission the i.LON 600 router. This method is useful if you do not have console access to your i.LON 600 router.
To verify that the RNI is enabled on your i.LON 600 router, follow these steps:
If the Enable RNI check box is cleared, perform a Security Access Reset, go back to the Security Web page, select the check box, and then click Submit. You will then need to do a normal reboot.
If you have access to the i.LON 600 server console, you can avoid the Security Access Reset by entering the enable secureAccess console command. After that refresh the Security Web page, select the check box, and then click Submit. You do not need to reboot the i.LON 600 router when using this method, but remember to disable secure access after your changes are complete by entering the disable secureAccess console command.
To create an RNI definition on your Windows computer, follow these steps:
NOTE: You must be logged in as an Administrative user to configure your i.LON 600 server as an RNI if you are using Windows XP or Windows 2000.
WARNING: If you use the i.LON 600 RNI as the network interface for an LNS-based application (such as the LonMaker tool), then later switch to use some other network interface for LNS (on the same network), and you still want to use the i.LON 600 IP-852 router on the network, you must either disable the i.LON 600 RNI from the Security Web page (see Verifying RNI is Enabled) or unconfigure it from the console using the unconfigapp RNI command. Failing to do this may cause the i.LON 600 RNI to intercept all messages from the router to the LNS network interface, resulting in various network communication failures.
You can increase the maximum number of RNI receive and/or transmit transactions, as well as adjust the transaction database timeout, if needed. To set the maximum receive transactions, use the setL5MIPMaxRxTransactions(n) command. You can set n to a value between 1 and 32,767; otherwise, it will be reset internally to the default value, which is 16. To set the maximum transmit transactions, use the setL5MIPMaxTxTransactions(n) command. You can set n to a value between 1 and 32,767; otherwise, it will be reset internally to the default value, which is 256. To adjust the transaction database timeout, use the setTxDatabaseTimeout(n) command. You can set n to a value between 1 and 24,576; otherwise, it will be reset internally to the default value, which is 24,576.
You can invoke these commands from /root/config/startup.scr. They must each be on a separate line and must be placed just before the line containing "startLonTalkApplications". For example, you could enter the following code to invoke the setL5MIPMaxRxTransactions command. (41957, 41159):
...
ld 0,1,"/root/modules/lonScanner.mod"
setL5MIPMaxRxTransactions(1000)
startLonTalkApplications
All models of the i.LON 600 router contain 32 MB NAND flash memory that is used to store the operating system, Web pages, and configuration. Some early i.LON 600 routers in the field experienced failures, the cause of which was traced to a new version of the NAND flash part. Manufacturing variations in that part, relative to the previous version, made the part susceptible to errors while writing to the flash disk. The result was a possible loss of data and/or potential corruption of the flash disk. The driver has been improved to recover from write failures without data loss.
You can now display flash disk errors in the console application. To display flash disk errors, enter the following command: diag flashdisk errors. The console application will list the total failed blocks, failed blocks during use (a new flash chip may contain some failed blocks from the factory, as determined by the chip manufacturer), maximum recommended number of failed blocks, and correctable ECC errors since reboot. Adding the optional all parameter to the end of the command will list the individual block numbers that have failed. (40359)
This section describes the problems fixed and other changes in Release 1.05. Numbers in parentheses at the end of the change descriptions are Echelon's internal problem tracking IDs. Release 1.05 includes all changes from Releases 1.02, 1.03, and 1.04, which are described following this section.
The time zone setting is now persistent, and will be preserved after a reboot. (38185, 38421, 38185)
This section describes the problems fixed and other changes in Release 1.04. 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 firmware 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 Service Pack 5 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 router 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 Echelon IP-852 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 the icon 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 third-party IP-852 devices.
This section describes updates to the i.LON 600 documentation.
The following product and component names have changed since the publication of the original i.LON 600 User’s Guide. References to these names may still appear in the software and documentation:
· LonWorks/IP-852 Router—formerly called the i.LON 600 LonWorks/IP Server or the i.LON 600 Internet Server. The new name reflects the primary function of the i.LON 600, which is to serve as a router from an IP-852 channel to a native LonWorks channel. The i.LON 600 router can also be used as a remote network interface (RNI) as described in this document.
· Echelon IP-852 Configuration Server—formerly called the LonWorks/IP Configuration Server. The new Echelon IP-852 Configuration Server can be used with any IP-852 compliant router, not just Echelon LonWorks/IP routers and servers.
Some of the software required to use the i.LON 600 router is provided as a free download from the Echelon, Microsoft, Mozilla, and Adobe Web sites and is not included on the i.LON 600 CD. Some of this software was previously included on the i.LON 600 CD. Following is a summary of the software that you may have to download, and a description of when you need it and where to get it:
· Echelon IP-852 Configuration Server (formerly called the LonWorks/IP Configuration Server)—this is required if you are using the i.LON 600 router as an IP-852 to LonWorks router. It is now available as a free download from www.echelon.com/ilon. Unlike previous releases, this version of Echelon’s Configuration Server can be used with any combination of Echelon and third-party IP-852 routers that comply with the CEA-852 standard, and is compatible with 64-bit and 32-bit versions of Windows.
· OpenLDV 4.0 Driver—this is required if you are using the i.LON 600 as a remote network interface (RNI). It is available as a free download from www.echelon.com/ilon. Unlike previous versions, this version of Echelon’s OpenLDV driver can be used with any combination of Echelon network interfaces and third-party network interfaces with OpenLDV-compatible drivers, and is compatible with 64-bit and 32-bit versions of Windows.
· Microsoft Internet Explorer and Mozilla Firefox—the i.LON 600 Web pages can be viewed with Internet Explorer SP1 or newer, or with Firefox 3.0 or newer. If you are using an older version, you can get updates for Internet Explorer from Windows Update, and you can get the latest version of Firefox from www.mozilla.com/firefox. If you are using Firefox, you must also download and install the IETab plugin.
· Adobe Reader—you will need Adobe Reader or Adobe Acrobat to read the i.LON 600 documentation. A free download of Adobe Reader is available from get.adobe.com/reader.