Echelon OpenLNS - Manual (Page 970)

OpenLNS Programmer's Reference 933
caused by attaching a new device to the
network which was previously configured as
part of another network or by two networks
sharing the same media and domain ID.
This condition could also occur if the
unexpected device was supposed to be
removed from the system, but the OpenLNS
Server was unable to update the device’s
network image during a Remove method;
meanwhile, the removed subnet/node
address has been reused for the device
being tested.
7 lcaTestResultMismatchDomain
The OpenLNS Server was able to
communicate with the device using Neuron
ID addressing but could not communicate
with the device using subnet/node
addressing. Using Neuron ID addressing,
the OpenLNS Server found that the domain
ID configured in the device does not match
the database. This result will be returned if
the device’s domain address has not be
configured or the device has become
unconfigured due to a checksum error.
8 lcaTestResultMismatchNeuronId
The OpenLNS Server was unable to
communicate with the device using Neuron
ID addressing. However, the device that
responded to the subnet/node addressed test
message contains a different Neuron ID. It
appears that the subnet/node address is
configured in the responding device but not
the tested device. One possible cause is that
the tested device is supposed to replace the
responding device, but the network images
in both devices have not been updated yet.
You can resolve this problem by physically
removing the obsolete device.
9 lcaTestResultMismatchSnode
The OpenLNS Server was able to
communicate with the device using Neuron
ID addressing, but could not communicate
with the device using its subnet/node
addressing. Through the use of Neuron ID
addressed messages, the NSS has found
that the subnet/node address configured in
the device does not match the database.
This result will be returned if the device’s
domain address has not been configured.