Echelon SmartServer 2.2 - Manual (Page 221)

222 Using the SmartServer as Network Management Tool
8. If the Network Management Service property is set to LNS Auto, the SmartServer automatically
begins synchronization with the new OpenLNS network database. If the Network Management
Service property is set to LNS Manual, manually synchronize the SmartServer to the new
OpenLNS network database following the steps described in Manually Synchronizing the
SmartServer to an OpenLNS network database earlier in this chapter.
9. When the synchronization operation on the SmartServer has been completed, synchronize
OpenLNS CT or other OpenLNS application to the OpenLNS network database. This updates
OpenLNS CT or other OpenLNS application with the functional blocks on the SmartServer’s
internal App device that are displayed in the SmartServer tree.
Switching to LNS Mode and Synchronizing to an OpenLNS Network
Database
You can switch the SmartServer from standalone to LNS mode (LNS Auto or LNS Manual) and then
synchronize the network attached to the SmartServer to an OpenLNS database. To switch a network
from standalone to LNS mode, you select an OpenLNS network database on an OpenLNS Server to be
synchronized to the network. After the OpenLNS database has been updated, you can synchronize an
OpenLNS application such as OpenLNS CT to the OpenLNS database and then use it to manage the
network.
The changes made to the OpenLNS network database depend on whether it is empty (contains only the
default “OpenLNS network Interface” and default “Channel 1”).

If the OpenLNS network database is empty, the following changes are made to it:
o The domain length and domain ID properties in the database are changed to those currently
used by the network attached to the SmartServer;
o The default “Channel 1” in the database is re-named to the name of the first L
ON W ORKS
channel on the SmartServer tree, which is usually “LON”.
o The transceiver type in the database is changed to the one used on the first L
ON W ORKS
channel on the SmartServer.
o All other L
ON W ORKS channels and devices on the SmartServer tree are merged into the
database.
Note: If there are any naming conflicts between the SmartServer and the OpenLNS network
database, the OpenLNS network database has precedence. For example, if the i.LON App
(Internal) device is named “SmartServer” in the OpenLNS network database, then it will be
re-named as such in the SmartServer tree after the synchronization.