IP-852 Channel User’s Guide 078-0312-01C
Echelon, LON, LonWorks, Neuron, 3120, 3150, i.LON, LNS, LonMaker, LONMARK, LonTalk, NodeBuilder, and the Echelon logo are trademarks of Echelon Corporation registered in the United States and other countries. LonSupport, OpenLDV, and LNS Powered by Echelon are trademarks of Echelon Corporation. Other brand and product names are trademarks or registered trademarks of their respective holders.
Table of Contents Preface ..................................................................................................... v Purpose .......................................................................................................... vi Audience......................................................................................................... vi Content ...........................................................................................................
iv Preface
Preface You can use an IP-852 channel to implement a LONWORKS® control network over an IP network, and you can use an IP-852 channel to integrate multiple native LONWORKS® networks into one large network that uses a high-speed IP-852 channel as a backbone.
Purpose This document describes how to create an IP-852 channel and how to use the channel with any IP-852 device. The IP-852 protocol is defined by the ISO/IEC 14908-4 standard. IP-852 devices are available from multiple manufacturers, and the Echelon IP-852 Configuration Server may be used with any IP-852 compliant device from any manufacturer. Echelon IP-852 devices include the SmartServer Energy Manager, i.LON 100 Internet Server, i.LON 600 IP-852 Router, and LNS server.
Related Manuals The documentation related to the Echelon IP-852 Configuration Server is provided as Adobe® PDF files and online help files. The PDF files are installed in the Echelon IP-852 Configuration Server program folder when you install the IP-852 Configuration Server. You can download the latest version of this guide, from Echelon’s Web site at www.echelon.com/docs. The following manuals provide supplemental information to the material in this guide.
viii Region Languages Supported Contact Information The Americas English Japanese Echelon Corporation Attn. Customer Support 550 Meridian Avenue San Jose, CA 95126 Phone (toll-free): 1-800-258-4LON (258-4566) Phone: +1-408-938-5200 Fax: +1-408-790-3801 lonsupport@echelon.com Europe English German French Italian Echelon Europe Ltd.
1 Introduction This chapter provides an introduction to IP-852 channels, and describes the devices you can use to create and manage these channels.
Introduction to the IP-852 Channel An IP-852 channel carries ISO/IEC 14908-1 packets enveloped in ISO/IEC 14908-4 packets. Unlike traditional LONWORKS channels that use a dedicated physical wire to create connections between the devices on the channel, an IP-852 channel uses a shared IP network to connect IP-852 devices and is defined by a group of IP addresses. These IP addresses form a channel that connects IP-852 devices on a shared control network so they can communicate with each other.
Configuration Server must be running anytime you modify the configuration of the devices on the IP-852 channel. You can run the IP-852 Configuration Server on any computer with access to the IP network containing the IP-852 channel. Chapters 2 and 3 of this document describe how to use the IP-852 Configuration Server. The IP-852 Configuration Server is available as a free download from www.echelon.
4 Introduction
2 Creating an IP-852 Channel This chapter describes how to create an IP-852 channel with the Echelon IP-852 Configuration Server.
Creating an IP-852 Channel You can create an IP-852 channel by configuring the IP-852 devices that are to be attached to the IP-852 channel, and entering information about each IP-852 device in the IP-852 Configuration Server. This section describes how create an IP-852 channel using an example network with two devices on an IP backbone to illustrate the process. In Figure 2.1, a LONWORKS device on channel 1 is bound to a device on channel 2 across an IP-852 backbone.
Figure 2.2 Echelon IP-852 Configuration Server 4. Verify that the IP-852 Configuration Server is attached to your IP network. The Network status box should indicate Enabled. If it does not, select Enabled from the Network menu. The IP-852 Configuration Server should correctly detect and display the IP address of your computer in the Channel Description window. To verify the IP-852 Configuration Server computer’s IP address, click Network and then click Settings. The Network Settings dialog opens.
Figure 2.3 IP-852 Configuration Server Network Settings 5. If your computer has more than one IP address assigned to it, you can click Local IP and specify the IP address to be used by the IP-852 Configuration Server. 6. The defaults for the channel properties will work in cases where network delays are low.
Figure 2.4 IP-852 Configuration Server Device Properties: Address Tab 11. Enter the IP address of the IP-852 device and click Apply. This is the same address that you assigned to the IP-852 device using the setup Web pages. If you use a host name, it must be registered in a DNS server that is available to the IP-852 Configuration Server computer. 12. Click the SNTP tab, and then select the Use Channel Default check box. 13. Click the Protocol tab, and then select the Use Channel Default check box.
14. Click the i.LON Time Zone tab, and then set the time zone to correspond with the geographical area of the device. 15. Click Apply. 16. Repeat steps 6 – 15 for each IP-852 device to be added to the IP-852 channel. You can change the IP-852 device’s settings (for example, IP address, local port, and so on) later. When you modify IP-852 device settings, update the device’s configuration with the device software before modifying the device’s settings in the IP-852 Configuration Server.
Checking IP-852 Device Status If any information between IP-852 devices on the IP-channel needs to be updated, the IP-852 Configuration Server will send updated information to each IP-852 device. Success or failure of this step is reflected in the IP-852 Configuration Server log screen and the color of the devices in the navigation pane on the left side of main dialog. The meaning of each color of the device status is listed in Table 2.1. Table 2.
Red/White Checkerboard Disabled. Typically, the user right clicked on the IP-852 device in the IP-852 Configuration Server tree and selected Disable Device from the shortcut menu. Cyan The IP-852 Configuration Server has not yet attempted to communicate with the IP-852 device. The IP-852 Configuration Server may be busy communicating with other channel members (this is common on a large channel).
IP-852 Channel LonMaker Computer/ IP-852 Configuration Server TCP/IP Network Channel 1 (FT-10) SmartServer Channel 2 (FT-10) SmartServer Figure 2.8 Typical Network Containing an IP-852 Channel To create a LonWorks network with an IP-852 channel using an LNS network management tool such as the LonMaker tool, follow steps: 1. Create an IP-852 channel containing the LONWORKS/IP-852 routers for the channel as described in the previous section. 2.
Figure 2.9 Add Network Interface Wizard Dialog 4. Enter the following properties for the IP-852 interface: Name Enter a name for the IP-852 interface definition that is unique to your computer. IP Address / Hostname IP Address Enter the IP address to be used by the IP-852 interface definition on your computer. Each IP-852 interface definition must use a unique IP address/port combination. This property defaults to the IP address of your computer's IP network card.
You can change the port number; however, you must avoid any conflicts with other applications that are using the IP network card. Each IP-852 interface definition you create with the LONWORKS Interfaces application must use a unique port. If you modify the port used by an IP-852 interface definition, the change will be implemented once all applications using the IP-852 interface definition are closed. Channel Timing Authentication Select the channel delay. You have the following two choices: • LAN.
Figure 2.10 Creating a New Channel Using LonMaker 2. Drag channel shapes to the drawing representing the FT-10 Channel 1 and FT-10 Channel 2 and assign TP/FT-10 as the Transceiver Type for both channels. 3. Drag two LONWORKS Router shapes to the drawing: • iLONRTR_1. Connects IP-852 Channel (Channel A) to FT-10 Channel 1 (Channel B). • iLONRTR_2. Connects IP-852 Channel (Channel A) to FT-10 Channel 2 (Channel B). 4. Commission the iLONRTR_1 and iLONRTR_2 routers, and leave them in the Online state.
Figure 2.11 IP-852 Routers Configured on a LONWORKS Network Verifying LONWORKS/IP-852 Router Functionality You can verify that an IP-852 device that you have configured as a LONWORKS/IP-852 router is functioning as a LONWORKS network. You will typically use the network management tool that you used to configure the IP-852 device as a LONWORKS router to do the verification. This section describes how to use the LonMaker Integration Tool to do the verification.
Table 2.2 Troubleshooting the IP-852 Device 18 Symptom Probable Cause Corrective Action No service pin message is received from the near router (iLONRTR_1 in Figure 2.10). There is a problem with network connectivity, or the network interface in the computer may not be functioning properly. Test connectivity between the network interface driver and the network interface card in the computer using LONWORKS Interfaces in the Windows Control Panel .
Symptom Probable Cause Corrective Action The near router (iLONRTR_1) commissions successfully, but no service pin message is received from the far router (iLONRTR_2). There is a problem with the IP-852 channel setup. Be sure the IP-852 Configuration Server is running when you commission the devices on the IP-852 channel. Verify that the near router is online and that the IP-852 Configuration Server reports connectivity among all members of the IP-852 channel (for example, all icons are green).
20 Symptom Probable Cause Corrective Action The IP-852 device on the IP-852 channel pings successfully, but will not commission. Address translation may take place somewhere between the two devices. Make sure that the IP address of the target IP-852 device matches the IP address defined for it in the IP-852 Configuration Server. The router application does not exist. If you are using an i.
3 IP-852 Channel Parameters This chapter provides details on the channel parameters you can set when creating an IP-852 channel with the Echelon IP-852 Configuration Server.
Channel Mode You can set the IP-852 device channel mode using one of three options in the New Channel Properties dialog box. If you are using an LNS Turbo Edition server (LNS 3.2) or higher, it is compatible with all three channel modes. To access the New Channel Properties dialog box, start the IP-852 Configuration Server, right-click the New Channel entry, and then click Channel Properties on the shortcut menu. Figure 3.
Table 3.1 describes each channel mode. Table 3.1 Channel Modes Setting Backward Compatible Description Select this option if your channel will contain any legacy i.LON 1000 servers or LNS 3.0 LONWORKS /IP network interfaces. This causes the IP-852 device to operate using a protocol that is compatible with these devices, but is not strictly EIA-852 compliant. In backward compatible mode, you can use a maximum of 40 devices.
packets. The resolution of the timer depends on the IP-852 device. The resolution for SmartServer and i.LON devices is in multiples of 10 milliseconds. The default aggregation time is 16 milliseconds. Figure 3.2 Aggregation Settings If the network is idle and a single LONWORKS packet arrives at the IP-852 device, the aggregation timer starts and the first packet is sent across the IP channel without delay. If the network remains idle, the timer resets.
packet. If the digests match, the packet is authentic. If the digests do not match, the packet is considered to have been corrupted, tampered with, or otherwise unacceptable, and is discarded. The digest includes the entire packet, which contains a time stamp for preventing replay attacks when used in conjunction with a configured channel timeout value. For more information on the MD5 algorithm refer to RFC 1321. Note: MD5 authentication should not be confused with authenticated LONWORKS messaging.
All authentication keys within a single network must match. Verify that you have previously entered the same authentication key on all the IP-852 devices defined on this channel To disable authentication on a channel that has authentication enabled, clear the Authenticate check box and click Apply.
Set a channel timeout when using MD5 authentication. When using MD5 authentication, start with a minimum channel timeout of 100 ms and a channel delay of 200 ms. The following factors in affect the Channel Timeout property: • Variations on each leg of a round trip. Factor the maximum delay into one leg of the trip. • Maximum difference between the times on the IP-852 devices.
1. In the IP-852 Configuration Server, click Network, click Settings, and then click the SNTP tab. Figure 3.4 Setting the System SNTP Server 2. Enter the IP address or host name of the primary and secondary SNTP servers. The IP addresses must be static IP addresses. You can typically use the default port numbers of 123. 3. The Use SNTP Server on Device check box is selected by default. This means that the IP-852 device fetches the time from the specified SNTP time server to update its clock.
If the IP-852 Configuration Server is not on a domain, you should keep this check box selected because your computer’s clock may drift too much as a result of Windows synchronizing to the system clock infrequently (once per week) by default. The Maximum Time Correction and Update Every properties only apply if the Run SNTP Client on Configuration Server check box is selected. The IP-852 device SNTP options are self-adjusting and cannot be configured. 5. Click OK to save and return to the main dialog.
Choosing an SNTP Server You can obtain an IP address for an SNTP server for your IP-852 Channel in any of the following ways: 30 • Ask your network administrator for the IP address of an SNTP server in your corporate network. • Connect to a time server on the Internet. There are many available public access servers; a comprehensive list may be found at http://ntp.isc.org/bin/view/Servers/StratumTwoTimeServers. • Install an SNTP server on any computer in your LAN.
4 Using NAT, DHCP, and DNS on an IP-852 Channel This chapter describes how to use NAT, DHCP, and DNS on an IP-852 channel.
Network Address Translation (NAT) Network address translation (NAT) allows multiple computers (hosts) to share a single IP address. The address is normally set up at the gateway between a private network and the Internet, allowing the computers on the private network to share a global, ISP assigned address. This is achieved by modifying the headers of each packet traveling through the NAT gateway. At a minimum, an IP address in each packet header is replaced (translated).
Figure 4.2 Setting up Multiple Firewalls with Multiple IP-852 Devices 6. Right-click the channel and click Update Members in the shortcut menu, or right-click the device and select Update Device in the shortcut menu. NAT Example: Simple Home Network If you have a home network with DSL or cable Internet access, you can setup all of your computers to communicate on the same IP address (assigned by your ISP) with the help of a NAT gateway.
Home Network 192.168.1.100 WAN Side 131.28.203.17 LAN Side NAT Gateway 192.168.1.101 ISP WAN Side Address is Assigned by ISP Internet 192.168.1.1 Figure 4.3 NAT Gateway Structure Ports and Port Mapping A fully qualified URL consists of an IP address and a port. The URL www.echelon.com:80 is a fully qualified URL. Port 80 is recognized as the default port for Web servers worldwide. Browsers typically append a URL with port 80 so you do not have to enter the full URL when accessing a Web site.
IP-852 Device Ports The IP-852 device uses IANA designated ports for LONWORKS traffic (ports 1628 and 1629). Continuing with the example described above, you could connect an IP-852 device to your network with an IP address of 192.168.1.102. Home Network 192.168.1.100 WAN Side 131.28.203.17 LAN Side WAN Side Address is Provided by ISP (assigned) ISP i.LON 600 192.168.1.102 Internet NAT Gateway 192.168.1.101 192.168.1.1 Figure 4.
TP-1250 High Speed Backbone FT/TP-1250 Router FT-10 Channel Figure 4.5 Connecting Devices on a Network The high-speed backbone is a physical wire and, since all TP/XF-1250 to TP/FT-10 routers are connected to the same physical wire, communication proceeds unimpeded. IP-852 devices are logically identical to TP/XF-1250 or TP/FT-10 routers, but use IP as their high-speed backbone instead of a TP/XF-1250 backbone. They may not be connected to the same physical wire.
Figure 4.
Note: The diagnostic information provided about the IP-852 devices (indicated by the varying IP-852 device icon colors) is more complete than the diagnostics provided by the changing colors of the NAT gateways. The IP-852 Configuration Server cannot acquire the same level of diagnostic information about an NAT gateway as it can about IP-852 devices. See Table 2.1 for the descriptions of the different IP-852 Configuration Server icon colors.
However, if you are in control of your DHCP server, you may be able to configure your DHCP server to always assign your SmartServer or i.LON dev ices the same IP address. This is called making a static reservation, and is supported by most DHCP servers. Using DHCP with static reservations is acceptable and is similar to using static IP addresses. If you decide to use this technique, each SmartServer and i.
DNS DNS is a mechanism that translates an IP host name like www.echelon.com into a numeric IP address like 205.229.51.8. For example, when you enter www.echelon.com in your Web browser, your Web browser queries a DNS server to find the IP address. It then requests the home page from the numeric IP address—not the IP host name. Because the process is transparent, many people are not aware of the existence of numeric IP addresses. IP host names are usually used to reference servers such as a Web server (www.
Figure 4.8 IP Host Names Tab 2. Select the Enable Continuous IP Host Names Translation check box, and then specify an update interval time (if applicable). 3. To issue an immediate IP word-based address translation, click Network and then select Translate IP Host Names. This will perform a retranslation on all channels. Note: When enabling the Translate IP Host Names option, the local DNS server and the Echelon IP-852 Configuration Server must be continuously running.
channel outages due to IP address changes, use static addresses that do not change. Linking DNS and DHCP DNS and DHCP are separate standards. A network can use DNS without using DHCP, and vice versa. You can, however, link DNS and DHCP servers in a single network so that all IP addresses on the network could be allocated dynamically, but still be referenced by name. While this can work for private networks, usually within corporations, it is not practical for the Internet.
When using DDNS, each time a new DHCP lease is given (for example, each time the computer’s IP address changes) the DDNS server is notified. The DDNS server keeps track of each client’s current address. To let external users see the Web server in your LAN, instead of telling the registrar that www.mylan.com is linked to 131.23.203.17, you tell the registrar that www.mylan.com is linked to mylan.ddns.org (for example). When an Internet user types in www.myhouse.
44 Using NAT, DHCP, DNS on an IP-852 Channel
Appendix A Troubleshooting This appendix can be used to diagnose common problems that could occur when you create an IP-852 channel with the Echelon IP-852 Configuration Server.
Common Troubleshooting Problems The following lists the most common problems encountered when creating and configuring an IP-852 channel with the Echelon IP-852 Configuration Server. Disabled IP-852 devices will not configure properly when the IP-852 Configuration Server is taken off the network. If you reattached the IP-852 Configuration Server and select Update Members, the IP-852 device is still not configured properly.
• Click the Show Log button to display the IP-852 Configuration Server log. Right-click a device and click Diagnose Device on the shortcut menu. Watch for any error or warning messages that appear in the log window. To simultaneously write the messages to a file, click the Log File button and supply a file name. Figure A.
www.echelon.
