Echelon SmartServer 2.2 - Manual (Page 196)

SmartServer 2.2 User’s Guide 197
SmartServer transmits all network management commands to the devices attached to its channel, and
network configuration changes are stored in XML files on the SmartServer’s internal database (the
/config/network folder on the SmartServer flash disk). In standalone mode, the network functions as
a master-slave system, where the SmartServer is the master to the slave devices.
Note: For FT-10 networks, you need to attach a physical layer repeater to the network to exceed the
64-device limit posed by the physical channel.
The following graphic demonstrates the SmartServer operating as a standalone network manager:
FT-10 or PL-20 Channel
SOAP
SmartServer Tree in
SmartServer Web Interface
Internal
SmartServer
Network
Database
Device
1
Device
2
Device
3
Device
4
Device
5
Device
~200
Using the SmartServer as a Standalone OpenLNS Network Tool
You can use the OpenLNS tree in the SmartServer Web interface as a complete OpenLNS network
management tool for designing, installing, and maintaining your network. Using the OpenLNS tree as
a network tool is comparable to using OpenLNS CT: you can create new networks, add devices and
functional blocks to the network, configure the devices and functional blocks with LNS plug-ins, and
then create network variable connections. The OpenLNS tree, however, does not provide the same
graphical representation of your network and its data flow as does OpenLNS CT.
When you configure a network in the OpenLNS tree, the LNS Proxy Web service directly propagates
the network configuration changes to the OpenLNS network database. The following graphic
demonstrates the SmartServer operating as a standalone OpenLNS network tool: