Echelon OpenLDV - Manual (Page 117)

OpenLDV Programmer’s Guide 109
Field Description
Uplink Lookup Key The uplink lookup key is an ASCII string (105 characters
maximum) passed to the lookup extension component by the RNI
during an uplink session. It is used by the lookup extension to
access the database record for the RNI that requested the uplink
session, so that the lookup extension component can fill in the rest
of the fields into the SCO. For a SmartServer or i.LON 600, the
uplink lookup key uses the following naming convention:
[Hostname].[DNS Suffix]
[Hostname] represents the hostname assigned to the SmartServer
or i.LON 600 during its configuration. [DNS Suffix] is optional,
and represents the DNS suffix or domain name assigned to the
SmartServer or i.LON 600 during its configuration.
For example, if the hostname for an SmartServer or i.LON 600 is
“myiLON” and the DNS suffix is “xyz.com”, the uplink key would
be “myiLON.xyz.com”.
This field is read-only during uplink sessions, and can be
optionally filled in during downlink sessions. You can set the
downlink key to match the uplink key.
Authentication Flag This Boolean flag specifies whether authentication between the
OpenLDV application and the RNI is enabled for the session. This
field is always set to true for the SmartServer and i.LON 600.
Current Authentication
Key
If the authentication flag is enabled, this field represents the
authentication key to be used for the session. This authentication
key must match the MD5 authentication key supplied to the RNI
during its configuration. Using an MD5 authentication key
prevents the OpenLDV application or the RNI from responding to
unauthorized messages during an xDriver session.
The authentication key must be entered as a 32-character
hexadecimal string representing a 128-bit MD5 key. For example:
0102030405060708090A0B0C0D0E0F10
Setting the authentication key to all 0s causes xDriver to use the
pre-defined, default factory authentication key for the RNI. The
default factory authentication key is not secure.
For more information about how the lookup extension component
handles authentication, see Authentication Key Handling on page
111.