Echelon i.LON 600 LonWorks/IP Server User Manual
Page 94
Section 3: Appendixes
Note that the diagnostic information provided about the i.LON 600s (indicated by the
varying i.LON 600 icon colors) is more complete than the diagnostics provided by the
changing colors of the NAT gateways. The Configuration Server cannot acquire the same
level of diagnostic information about an NAT gateway as it can about i.LON 600s.
describes the meanings of the different icon colors.
Table 16. Configuration Server Icon Colors
Color Description
Green
Configuration Server has communicated with the i.LON 600 and configuration is
up to date.
Yellow The
i
.LON 600’s time differs from the time on the PC running the Configuration
Server by more than a few milliseconds. This usually means that either the
i
.LON 600 or the PC is not referencing an SNTP server to set the local time. The
system may work with some yellow devices, but the probability of data loss is
increased. You should provide an SNTP server to both the PC and the i.LON 600
so that their time bases can be synchronized. When synchronized, the yellow icon
should turn green.
Red
The Configuration Server can not communicate with the i.LON 600. This may
happen if the i.LON 600 is powered down, disconnected from the IP network, or
has been configured improperly with the wrong IP address/subnet mask/gateway
etc. It may also occur if an intervening NAT gateway has not been configured to
statically map ports to the i.LON 600 as described above.
Orange The
i
.LON 600’s configuration is out of date or the IP address has not been
specified (0.0.0.0). This indicates work in progress. When the Configuration
Server updates the i.LON 600, the icon will turn green. Note that in a large
channel (> 40 devices) this can take several minutes. Also note that changing a
bind in LonMaker can require that the routing tables in EVERY i.LON be updated.
In this case, you may see many icons turn orange, and then one-by-one turn
green again when their routing tables have been updated.
Red/White
Checkerboard
Disabled. Typically, the user right clicked on the i.LON 600 in the Configuration
Server tree and selected Disable Device from the pop-up menu.
Cyan
The Configuration Server has not yet attempted to communicate with the
i.
LON 600. The Configuration Server may be busy communicating with other
channel members (this is common on a large channel). If the Configuration Server
appears not to be attempting communication, click on the Show Log button and
monitor the progress. Select Update Members from the Channel menu.
The Configuration Server acts as a “relay station” for all information pertaining to
channel members, including which LonTalk subnets are on the far side of which IP
address.
Whenever a LonTalk routing table changes (this can happen while making a bind) or a
new member is added to the L
ON
W
ORKS
/IP channel (virtual wire), the Configuration
Server relays this information to all devices on the channel that need to know. Note that
some devices on the L
ON
W
ORKS
/IP channel can be unaware of other devices on the
channel.
Once all channel devices have been inaugurated into the L
ON
W
ORKS
/IP channel, and all
binds have been made, you can shut down the Configuration Server software (though
there is no harm in leaving it running).
86
Using NAT, DNS, DHCP & DDNS with a L
ON
W
ORKS
Network