Echelon LonMaker - Manual (Page 236)

220 Maintaining Networks
2. Ensure that all components of the network are present and functioning properly before starting
recovery. Any missing devices or routers will cause portions of the network design to be missing.
For example, if a router is not recovered, all devices on the router’s far side will not be included in
the recovered network design.
3. Run the LNS Network Database Recovery Wizard. The recovery wizard includes an option to
automatically generate the LonMaker drawing.
4. Verify that the recovered network appears to be correct. The recovery wizard logs the recovery
tasks as well as any errors that occurred in the detailed recovery log. A trace log lists the steps,
with the times and dates, that the wizard took to recover the database. You can view the logs after
the database has been recovered. These logs are useful for tracking any errors that the recovery
process encounters, such as connection errors or lost data.
5. To actively manage the recovered network, change the management mode to OnNet (open the
LonMaker menu, click Network Properties, click the Network Interface tab, and under the
Management Mode box, select OnNet).
The following sections detail each of these steps. The subsystem recovery options that you can set in a
LonMaker network design are also described. These subsystem recovery options help you recover
your network in the event you lose the network design and all backups.
Subsystem Recovery Options
You can make your LonMaker network designs easier to recover and enhance a recovered network
design by storing recovery data in the physical devices. You can store the subsystem ID of a device in
its location string and its subsystem path in its SCPTlocation configuration property (if it has one).
This recovery data is not part of the network configuration of a device.
When you recover a network, the following data is used in the listed order:
1. Subsystem path stored in a CSV file.
2. Subsystem path stored in a SCPTlocation configuration property that is associated with the Node
Object, if present, or associated with the application device.
3. Subsystem ID stored in the location property (the most-significant bit of the first byte of the
location string must be set).
4. The “Recovered” subsystem. A device is placed in a subsystem named “Recovered” if a CSV file
is not imported or subsystem data is not included in the file, and the device does not have a valid
subsystem ID or a valid SCPTlocation configuration property
By default, both subsystem recovery options are enabled in new networks. For LonMaker network
designs created with previous versions of the LonMaker tool, they are disabled. To enable the
subsystem recovery options and update existing devices in a network, follow these steps:
1. Open the
LonMaker menu and then click LonMaker Options.
2. Select Recovery in the Options Category list.
3. Select the check boxes under the Subsystem Recovery Options box. This will enable subsystem
location data to be stored and updated in all future application devices and routers you create.
You can update the recovery data in the physical devices in a network after setting the subsystem
recovery options and after recovering a network. To update the recovery data, follow these steps:
1. Open the
LonMaker menu, point to Synchronization, and then click Resynchronize. The
Synchronize LonMaker Drawing dialog opens.