Echelon OpenLNS - Manual (Page 814)

OpenLNS Programmer's Reference 777
could be caused by attaching a new router
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 router was
supposed to be removed from the system,
but the OpenLNS Server was unable to
update the router’s network image during
a Remove method; meanwhile, the
removed subnet/node address has been
reused for the router being tested.
7 lcaTestResultMismatchDomain
The OpenLNS Server was able to
communicate with the router using
Neuron ID addressing but could not
communicate with the router using
subnet/node addressing. Using Neuron
ID addressing, the OpenLNS Server
found that the domain ID configured in
the router does not match the database.
This result will be returned if the router’s
domain address has not be configured or
the router has become unconfigured due
to a checksum error.
8 lcaTestResultMismatchNeuronId
The OpenLNS Server was unable to
communicate with the router using
Neuron ID addressing. However, the
router 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 router but not the tested
router. One possible cause is that the
tested router is supposed to replace the
responding router, but the network
images in both routers have not been
updated yet. You can resolve this problem
by physically removing the obsolete
router.
9 lcaTestResultMismatchSnode
The OpenLNS Server was able to
communicate with the router using
Neuron ID addressing, but could not
communicate with the router 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 router does not