i.LON® 600 LonWorks®/IP Server ReadMe File
Release 1.06, August 2006
Copyright © 1998 – 2006 Echelon
Corporation
All Rights Reserved
This file describes i.LON 600 Release 1.06, which provides important updates to the i.LON 600 firmware. The i.LON Release 1.06 is created by applying i.LON 600 Service Pack 6 (“SP6”) to a Release 1, 1.01, 1.02, 1.03, 1.04 or 1.05 i.LON 600 installation. It is included on i.LON 600 servers that come with the i.LON 600 Service Release 6 (“SR6”) CD. The service pack is delivered as an approximately 2.2 MB self-extracting executable file; the service release is delivered on a CD.
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 6
6 Installing i.LON 600 Service Release 6
7.1 Ethernet Speed and Duplex Override
7.2.1 Creating and Activating the i.LON 600 RNI Application
7.2.2 Verifying RNI is Enabled
7.2.3 Creating an RNI Definition under Windows
7.2.4 RNI Transaction Configuration
7.3 Flash Disk Driver Improvement
9.3 Config.sys File Corruption
11.7 Channel Configuration Timestamps
12 Known Problems and Workarounds
12.1 i.LON 1000 Internet Server Upgrade
12.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 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.LON 600 LonWorks/IP Server Release 1 Service Release 6 (V1.06.01) |
August 2006 |
You can determine whether or not you already have Release 1.06 firmware installed on your i.LON 600 server. To determine the firmware version running on your i.LON 600 server, follow these steps:
1. If you have copied any updated firmware files to your i.LON 600 server, reboot it before checking the version number. See the final step of the Installation instructions below for instructions on how to reboot an i.LON 600 server.
2. If you have rebooted the i.LON 600 server, wait for the reboot to be completed. You can tell when the i.LON 600 has completed initialization when the green Power/Wink LED on the i.LON 600 server stops blinking and stays on solidly.
3. Enter your i.LON 600 server’s IP address in Internet Explorer (6.0 or newer).
4. On the Setup menu, click System Info.
5. Enter your user name and password when prompted. By default this is ilon/ilon, but you may have changed that.
6. The version number will be displayed in the first section of Properties, labeled Firmware Version. Possible version numbers are shown in the Version History, above. If the version is 1.06.01 or later, you do not need this firmware upgrade. If the version is earlier than 1.06.01, you should upgrade your firmware to Release 1.06.
You must install i.LON 600 Service Pack 6 over an existing i.LON 600 installation. To install i.LON 600 Service Pack 6, follow these steps:
1. Use an FTP client such as Internet Explorer to backup a copy of all files on your i.LON 600 to another computer.
2. Download the iLON600_SP6.exe file from Echelon’s Web site to any directory on your computer.
3. Click the Windows Start menu, click Run, and then browse to the directory where you downloaded iLON600_ SP6.exe.
4. Double-click iLON600_ SP6.exe.
5. Select a folder to copy the setup files to, and then click Unzip. The default is c:\LonWorks\iLON600\Images.
6. Complete the installation on your computer. The updated i.LON 600 firmware will be copied to your specified folder. This will create two folders in the target folder— iLON600 1.06, which contains the system software files, and BootROM, which contains the new boot-ROM image.
7. Use an FTP client such as Internet Explorer to copy all the extracted files in the iLON600 1.06 folder except this ReadMe file to your i.LON 600 server. The iLonSystem file must go in the highest-level folder, and the contents of the Modules and Config folders on your computer should go in the folders of the same names on the i.LON 600 server. Some of these files will replace an existing file of the same name on the i.LON 600 server.
8. Copy the bootrom.upd file in the BootROM\iLON600 1.06 folder to the top level directory on your i.LON 600 server.
9. Attach a serial cable from the i.LON 600 DB-9 Console Port to a serial port on your computer using a null modem crossover cable. Start a terminal emulation program such as Windows HyperTerminal to communicate over that serial port. The proper communications parameters are 9600/8/N/1 and no flow control. Make sure the i.LON 600 server responds with a prompt when you press the Enter key.
10. Enter the following command in your terminal emulation program: update bootrom. You should see a confirmation that the bootrom.upd file will be used to update the boot ROM. Type y to confirm. When the update is complete, the i.LON 600 server will automatically reboot.
You can install Release 1.06 from an i.LON 600 Service Release 6 CD with or without a prior i.LON 600 installation. To install an i.LON 600 Service Release 6 CD, follow these steps:
1. Insert the i.LON 600 SR6 CD and the installation program should start automatically. If the installation program does not start automatically when the CD is inserted, run the setup.exe at the root of the CD. In most cases, you can accept all defaults.
2. If you have any Release 1.05 or earlier i.LON 600 servers to upgrade, download the i.LON 600 Service Pack 6 update from www.echelon.com/downloads and follow the above instructions for upgrading. The system software image files from the service pack are the same as those in the service release, but the service pack includes the bootrom image, and that should be upgraded at the same time.
This section describes the problems fixed and other changes in Release 1.06 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.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). This feature had previously only been supported on the i.LON 100 server. If you are upgrading your i.LON 600 server, you must do the following to use it as an RNI (if you purchased a Release 1.06 i.LON 600 server, skip step 1):
1. Create and activate the i.LON 600 RNI application in the console application.
2. Verify that the new Enable RNI check box on the Security configuration Web page is selected (it is selected by default). (39955)
3. Create an RNI definition in the LonWorks Interfaces application in the Windows Control Panel.
NOTE: The LonWorks Interfaces application is not included with the i.LON 600 server. You must have one of the following programs installed on your computer to use it: LonMaker Integration Tool, LNS network operating system, OpenLDV driver interface, LonScanner Protocol Analyzer, or the i.LON 100 server.
These steps are further explained in the following sections.
For upgraded i.LON 600 servers, you can create and activate the i.LON 600 RNI application using one of the following two methods. Note that new i.LON 600 servers shipped with Release 1.06 do not require this step.
· Method 1: Connect a serial cable to the console connector of your i.LON 600 server (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 command listapp to verify this.
· Method 2: Using an FTP client, go to the root directory of your i.LON 600 server and then delete the ltConfig folder (note that this deletes the current LonTalk configuration data of your i.LON 600 router), reboot your i.LON 600 server, and then recommission the i.LON 600 router. This method is useful if you do not have console access to your i.LON 600 server.
To verify that the RNI is enabled on your i.LON 600 server, follow these steps:
1. Open the Security configuration Web page of your i.LON 600 server.
2. Check that the new Enable RNI check box is selected.
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 console command enable secureAccess. After that you should refresh the Security web page, select the check box, and click Submit. You do not need to reboot the i.LON 600 server when using this method, but remember to disable secure access after your changes are complete by entering the console command disable secureAccess.
To create an RNI definition on your Windows PC, follow these steps:
1. Open the Windows Control Panel and double-click the LonWorks Interfaces icon. The LonWorks Interfaces application opens and the RNI tab appears.
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.
2. Select the Default Profile and then click Add. The Add Network Interface Wizard opens and the Network Interface Name dialog appears.
3. Enter a unique name for the i.LON 600 RNI. This will be used as a lookup key to access the proper registry entry each time xDriver initiates a connection to this RNI. Click Next. The Network Interface Type dialog appears.
4. Select Other and then click Next. The Network Interface IP Address dialog appears.
5. Enter the IP address of your i.LON 600 server in the Hostname or IP Address box. Click Finish. You are returned to the RNI tab. The IP address and name of the RNI definition you created is now listed in the tab. The name to use for the RNI is x.Default.<name>, where name is the name you entered in step 3.
6. Optionally, you can further configure your i.LON 600 RNI by selecting its network interface and then clicking Properties under the Network Interface box. The Network Interface Properties dialog appears. In this dialog, you can verify or change the IP port used to listen for messages from the LNS Server; click RNI Device to configure the IP address and authentication properties; or click Test to verify that the LNS Server can communicate with the RNI. You should not set the Uplink Connectivity properties, as the i.LON 600 RNI does not support uplink connections. See the online help for more information on this dialog.
7. Your i.LON 600 server is now configured as an RNI. You can use it to connect applications running on your computer to the network, just as you would with any other LonWorks network interface, with the exception that it does not support LNS uplink connections (unlike the i.LON 100 RNI).
WARNING: If you use the i.LON 600 RNI as the network interface for an LNS-based application (such as LonMaker), 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 server contain 32 MB NAND Flash memory that is used to store the operating system, Web pages, and configuration. Echelon was recently notified that some i.LON 600 servers 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 originally contain some failed blocks, as determined by the chip manufacturer), maximum recommended number of failed blocks, and correctable ECC errors since reboot. Adding the optional parameter all 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 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.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 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 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 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:
1. From the Windows control panel, double-click Add/Remove Software.
2. From the Currently Installed Programs list, click Echelon i.LON 600, and then click Change. The Program Maintenance dialog appears.
3. Click Repair.
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.