Replace – Echelon OpenLNS User Manual
Page 558
OpenLNS Programmer's Reference
521
if you install a new network interface on the computer). In all
other scenarios (e.g. when operating as a Local client and
upgrading the computer or network interface card, or when
moving a layer 5 network interface card from one computer
to another) you will not need to perform this procedure.
To re-associate a remote Full client with the correct network
service device and re-attach the client to the network, follow
these steps:
1. Get the network service device to be attached to from the
NetworkServiceDevices collection.
2. Call the PreReplace method with the selected network
service device as an argument.
3. Close the network and release all references to the
network.
4. Get the network and call the Network object's Replace
method.
5. Call the Network object's Open method to open the
network with all previously created monitor sets present.
Availability
Full clients.
Syntax
networkObject.PreReplace sourceNSD
Element
Description
sourceNSD
object associated with the remote Full
client that is to reattach to the network.
Added to API
LNS Release 3.0.
Replace
Summary
Completes the network service device replacement started by
method
.
Under normal circumstances, when a remote full client
re-opens a network, any network variables, connections and
monitor sets created previously will still be available to the
client, so long as original NSD still exists in the database.
However, under some circumstances, the correlation between
the client and the NSD configuration may be lost, and this
method may be used in conjunction with the procedure
described below to re-associate the client with the correct
NSD. To ensure that the NSD is not deleted from the
OpenLNS database, the NSD must be configured as a
permanent device on the network. You can do so by setting
the
lcaNsdType
property of the
object
to lcaNsdTypePermanent (1).
For example, you will need to use this method if you open a
network remotely from a new computer, and want that client