You can install the IzoT Router in a self-installed network using the ISI protocol, or you can install the IzoT Router in a network managed by an IzoT Net Server, OpenLNS Server, or an LNS Server. The three network management servers are referred to collectively as the IzoT Net Server in this documentation—except where limitations are described for the LNS Server.

By default, the IzoT Router is configured as a repeater so that it can be used in ISI networks without any further configuration. You can enable the IzoT Server as described in Configuring the IzoT Server to support custom Web pages that you develop to discover, monitor, and control devices in an ISI network.

Each of the device interfaces in a LonTalk/IP network may have two types of IP addresses—host IP addresses and LonTalk/IP addresses. LonTalk/IP addresses can be represented as IPv4 addresses, such as 10.133.3.1, and as ISO/IEC 14908-1 addresses, such as domain 133, subnet/node 3/1. On an Ethernet or Wi-Fi LAN, the two addresses are assigned as follows:

• A host IP address is typically assigned by a DHCP server, or is assigned statically when the host is installed.
• A LonTalk/IP address is assigned by the ISI engine for self-installed ISI networks, and is assigned by the IzoT Net Serve, OpenLNS Server, or LNS Serverr for managed networks. The ISI engine sets the LonTalk/IP address to equal the host IP address if the host IP address can be mapped to an ISO/IEC 14908-1 address. The IzoT Net Server, OpenLNS Server, or LNS Server will typically assign a LonTalk/IP address that is different from the host address.

ISI devices typically use broadcast messaging for all network communication. These broadcast messages are automatically forwarded by IzoT Routers in the default repeater configuration, and as a result no special configuration of the IzoT Routers is required to support an ISI network with multiple channels.

Devices in managed networks will often use unicast messaging to address datapoint updates to a single specified destination. In addition, the IzoT Server uses unicast messaging to poll datapoints from the devices in the network. In both cases, if the destination device is on a different subnet than the source device, or if the destination address is a LonTalk/IP address that is not also a host IP address, the update will be forwarded to the configured IP network gateway for routing. In that case, you must configure the IP network gateway to forward the update to the appropriate IzoT Router. You will specify two routes per IzoT Router—one to route the LAN-side LonTalk/IP address to the LAN-side host IP address, and one to route the LON-side LonTalk/IP subnet to the LAN-side host IP address. In the latter case, the IzoT Router will handle the forwarding of LonTalk/IP packets received from the gateway to the LON subnet.

To use the IzoT Router in a network managed with an IzoT Net Server or LNS Server, commission the IzoT Router from an IzoT Net or LNS network management tool such as the IzoT Commissioning Tool, OpenLNS Commissioning Tool, or LonMaker Integration Tool. The network management server will configure the IzoT Router and handle LonTalk/IP network management of the IzoT Router. You can use the network management tool to configure the IzoT Router to be a configured or learning router, or to be a repeater. To optimize network bandwidth utilization, configure the IzoT Router to be a configured router. If you are using a protocol analyzer such as Wireshark on the LAN channel, you can configure the IzoT Router to be a repeater. This will increase network traffic on the LAN channel, but is useful when doing diagnostics from a tool attached to the LAN channel.

To use the IzoT Router in a self-installed ISI network after it has been commissioned by an IzoT Net Server, use one of the following methods:

• Restore the IzoT Router factory defaults as described in Restoring the IzoT Router Factory Defaults.
• Use a network management tool such as IzoT CT to reconfigure the IzoT Router as a repeater.

To use the IzoT Router in a network managed with an IzoT Net Server, attach the IzoT Net Server computer to the LonTalk/IP-LAN (IP-70) channel.

To use the IzoT Router in a network managed with an LNS Server, enable the remote network interface feature (RNI) as described in Using the RNI and IP-852 Network Interfaces, then use the IzoT Router as a remote network interface with the LNS Server and LNS network management or diagnostic tools. The LNS Server cannot be attached directly to the LonTalk/IP-LAN (IP-70) channel, but it can be attached to the IP-852 or one of the LON channels, and it can also be connected using the IzoT Router RNI. The IzoT Net Server can be attached to any of the channels, including the LonTalk/IP-LAN (IP-70) channel.

Example

The following example illustrates an IzoT Commissioning (CT) Tool network with an IzoT Router and two devices on an FT LON channel. The network interface for the IzoT CT computer is on the IP-70 LAN channel and communicates with the LON devices through the IzoT Router.

IzoT Router Host IP and LonTalk/IP Addresses

The following table summarizes the host IP and LonTalk/IP addresses for the IzoT Router in the example network:

IP Routes

The following table summarizes the required IP routes:

The first route specifies the route for messages addressed to the LonTalk/IP address of the LAN side of the router. The second route specifies the route for messages address to the LonTalk/IP subnet on the LON side of the router.

There are two methods to configure the routes in the IP network:

Specify the routes in the IP network gateway.  If the network is behind a local router such as a Wi-Fi router, the network gateway will typically be integrated with the local router.  The steps to define the required routes depend on the type of IP network gateway that you are using. See Installing Multiple IzoT Routers in a Network for an example with an Asus Wi-Fi router.

Specify routes in each of the devices on the LAN channel. If there is only one IzoT Router on the LAN channel, the IzoT Router automatically creates the required IP routes for itself. With this approach, you must manually add routes to every other LonTalk/IP device on the LAN channel. In this example, the IzoT CT computer is the only other device on the LAN channel. You can add IP routes to the IzoT CT computer by entering the following commands at the Windows console:

route -p add 10.133.1.1 mask 255.255.255.255 10.3.124.186
route -p add 10.133.2.0 mask 255.255.255.0 10.3.124.186