LIP User Manual
LIP User Manual
CEA-709/IP Router
User Manual
Version 7.4
Document № 88065915
Contents
1 Introduction ................................................................................................ 11
1.1 Overview ............................................................................................................ 11
1.1.1 L-IP .......................................................................................................... 11
1.1.2 L-IP Redundant ........................................................................................ 13
1.2 L-IP Models ....................................................................................................... 14
1.3 Scope................................................................................................................... 15
2 Disclaimer Cyber Security ......................................................................... 16
3 Safety Instructions ...................................................................................... 17
4 What’s New in L-IP .................................................................................... 21
4.1 New in L-IP 7.4.0 ............................................................................................... 21
4.2 New in L-IP 7.2.0 ............................................................................................... 22
4.3 New in L-IP 7.0.0 ............................................................................................... 24
4.4 New in L-IP 6.4.0 ............................................................................................... 25
4.5 New in L-IP 6.1.0 ............................................................................................... 26
5 Quick-Start Guide ...................................................................................... 28
5.1 Hardware Installation ....................................................................................... 28
5.1.1 L-IP .......................................................................................................... 28
5.1.2 L-IP Redundant ........................................................................................ 28
5.2 IP Configuration of the Client Device ............................................................. 29
5.2.1 Configuration via the Web-Interface ....................................................... 29
5.2.2 Configuration via the LCD Display ......................................................... 31
5.3 Configuration Server Settings .......................................................................... 32
5.4 L-IP Redundant Configuration........................................................................ 33
6 Hardware Installation ................................................................................ 35
6.1 Enclosure............................................................................................................ 35
6.2 Product Label .................................................................................................... 35
6.3 Mounting ............................................................................................................ 36
6.4 LED signals ........................................................................................................ 36
6.4.1 Power LED .............................................................................................. 36
6.4.2 Status LED ............................................................................................... 37
6.4.3 CEA-709 Activity LED ........................................................................... 37
6.4.4 Twin Router Status LED (L-IP Redundant only)..................................... 37
6.4.5 Ethernet Link LED ................................................................................... 37
6.4.6 Ethernet Activity LED ............................................................................. 38
6.4.7 CEA-852 Status LED (CNIP LED) ......................................................... 38
6.4.8 Configuration Server LED ....................................................................... 38
Version 7.4 LOYTEC electronics GmbH
L-IP CEA-709 User Manual 4 LOYTEC
Abbreviations
1 Introduction
1.1 Overview
1.1.1 L-IP
The L-IP is a high performance, reliable, and secure network infrastructure component for
accessing CEA-709 network nodes over the Internet. It can be used to connect remote retail
branches over the Internet, build high-speed backbone channels, or to act as a network
interface for LNS-based network management tools. Its built-in configuration server
manages up to 256 IP devices on one IP channel without the need for a dedicated management
PC. The L-IP can be used behind NAT routers and firewalls, which allows seamless
integration in already existing Intranet networks. It supports DHCP even with changing IP
addresses in an Intranet environment. Easy to understand diagnostic LEDs allow installers
and system integrators to install and troubleshoot this device without expert knowledge and
dedicated troubleshooting tools. The L-IP can be used as a standard CEA-709 configured
router or it can be used as a self-learning plug&play router based on the high-performance,
well-proven routing core from our L-Switch plug&play multi-port router devices (“smart
switch mode”). The self-learning router doesn’t need a network management tool for
configuration but is a true plug&play and easy to use IP infrastructure component. Advanced
built-in network statistics and network diagnostics capabilities allow fast network installation
and guarantee reliable operation over the entire lifetime of the network. The automatic IP
connection keep-alive functionality maintains IP connections during bus idle times. The
multi-port version of the L-IP combines the functionality of two L-IPs in one device. This
device is equipped with a 100-BaseT Ethernet port (CEA-852) and up to four FT-10 ports
(CEA-709).
The L-IP perfectly integrates with our L-Switch multi-port router devices to form a high
performance, fully manageable, highly reliable network infrastructure for your CEA-709
networks. Its smart routing software automatically detects the bit-rates of the connected
channels, learns the configuration of the network (domains, subnet/node addresses, group
addresses) and forwards the packets between the different ports. Thus, using the L-IP together
with L-Switch devices and structured wiring is an easy and cost effective way to avoid
performance problems on the communication media.
Like the L-Switch the L-IP permanently collects statistics information from the attached
network channels (channel load, CRC errors, forwarding statistics, etc.). Using this data the
L-IP software is able to detect problems on these channels (overload, connections problems,
etc.) and warns the system operator via LEDs (see Section 6.4.10). An intuitive user interface
allows fast and easy network troubleshooting without any additional analysis tools and deep
system knowledge. The LSD Tool can be used for a more detailed view of the collected
statistics data. See Chapter 15 for more information on this powerful system diagnostics tool.
The built-in web server allows convenient device configuration through a standard web
browser like Internet Explorer or Firefox. The web interface also allows backup and restoring
the configuration of the configuration server and it provides statistics information for system
installation and network troubleshooting.
Starting with firmware version 2.0 the L-IP supports remote LPA operation. Remote LPA is
an advanced trouble shooting tool that streams the CEA-709 packets on the FT-10 or TP-1250
channel over the IP network to a protocol analyzer connected to the IP network. This allows
remote troubleshooting of the local CEA-709 channels without actually being physically
attached to this channel. Please consult our product literature for the LPA-IP to learn more
about this IP protocol analyzer. This tool is a must for every system integrator using IP-852
channels.
Figure 1: L-IP application example behind and without firewalls and NAT routers
The L-IP series “C” models (product code ending with C) come with two Ethernet ports and
the device setup can be done easily on the LCD display. The remote Wireshark packet capture
feature is also available.
In addition the L-IP series “C” models are also equipped with enhanced security features
such as a built-in firewall and a secure Web interface for installation using HTTPS with self-
signed or installable CA certificates. By configuring separate IP networks on the two Ethernet
ports, the CEA-852 network can be entirely isolated from the configuration interface.
OpenVPN support enables secure remote management.
For perfect integration into building management software such as the LWEB-900 by
LOYTEC, the L-IP series “C” models offers an embedded OPC UA server with certificate
authentication, which exposes important operational parameters as OPC tags. For enhanced
maintainability by IT departments these models provide the same data also through an SNMP
server. Together with the LWLAN-800 adapter these L-IPs can operate CEA-852 on the
WLAN. By setting up an access point on the Ethernet network, the device can be used to
distribute FT channels on a wireless network.
Network interface for LNS based network management tools (LonMaker, NL-220)
Structuring networks
An L-IP Redundant CEA-709/IP Router can be used as a single device to achieve the
redundancy on the CEA-709 (TP/FT-10) channel by building a ring structure. Full
Redundancy on the IP-Channel1 and on the CEA-709 channel can be achieved with two
devices installed in parallel. In this case device redundancy is ensured as well by mutual
monitoring of paired L-IP Redundant devices.
In addition the L-IP Redundant CEA-709/IP Router monitors the nodes on the TP/FT-10
channel and creates an alarm if a node gets offline. Thereby a cable break on the TP/FT-10
channel can be easily located. The L-IP Redundant only supports the “Configured Router
Mode”.
As an IP-Router the L-IP Redundant CEA-709/IP Router can tunnel CEA-709 packets back
and forth through an arbitrary IP based network, such as a LAN, an Intranet, or even the
Internet. The Router connects to the IP network via an Ethernet channel. The IP configuration
can either be obtained via DHCP or entered manually. The user only needs to provide the IP
address of an CEA-852 configuration server. If operated behind a router with network address
translation (NAT or masquerading), the L-IP Redundant CEA-709/IP Router supports Auto-
NAT to work with dynamic public IP addresses. When using the built in CEA-852
configuration server, the user can edit and backup the IP channel configuration through the
built-in web server. The configuration is stored persistently and the device operates
completely standalone. After installation, the L-IP Redundant CEA-709/IP Router is ready
to route packets between the CEA-709 network (ring structure) and the IP network. Thus, all
CEA-709 networks connected to L-IP Routers can exchange data over the IP-852 channel. If
connected to untrusted networks, such as the Internet, all CEA-852 packets can be
authenticated by an MD5 checksum and time stamps. Besides its primary router operation,
the L-IP Router is a powerful network diagnostics device. Its simple and intuitive user
interface provides an immediate overview over the network status. Both the IP-852 channel
1
Redundancy on the IP-Channel requires a redundant IP network infrastructure.
and CEA-709 network can be observed with status LEDs. For trouble-shooting, the Router
supports the remote LPA (LOYTEC Protocol Analyzer) functionality so that the network can
be analyzed from any PC connected to the Internet. With the L-IP Redundant CEA-709/IP
Router, setting up a redundant network which is comfortable to maintain becomes an easy
task.
Full redundancy with two L-IP Redundant CEA-709/IP Router in parallel for the IP-
Cannel and the CEA-709 channel
Messages and alarming via SNVTs and LonMark-Alarming via Node Object
Figure 2: Using L IP Redundant with redundant ring structure and device redundancy
check mark () in the respective column. If a feature is not available in the particular model,
the column is left blank.
Model
LIP-3333ECTC
LIP-33ECTC
LIP-33ECRB
LIP-3ECTC
Features
CEA-709 Router
Redundant Router
CEA-709 Ports 2 1 2 4
Remote LPA
OPC XML-DA
OPC UA
SNMP
LCD Display
Serial Console, DIP switches
USB
Ethernet Switch/Hub
WLAN, LTE 1 1 1
SSH, HTTPS, Firewall, VPN
1
To operate these protocols an expansion module is needed and must be ordered separately
Table 1: Available features in different L-IP models.
1.3 Scope
This document covers L-IP devices with firmware version 7.4.
LOYTEC offers a portfolio of products, solutions and systems with cyber security functions
that enable the secure operation of devices, systems and networks in the field of building
automation and control technology. To ensure that devices, systems, and networks are always
protected against online threats, a holistic security concept is required that is implemented
using the latest technology and is being kept up-to-date. The LOYTEC portfolio is only one
component of such an overall concept.
The customer is responsible for preventing unauthorized access to the devices, systems and
networks. These should only be connected to a network or the Internet if adequate security
measures are in place (e.g. firewalls, separate networks) and a connection is required for
operation. In addition, LOYTEC’s recommendations for securing devices in the Security
Hardening Guide (Chapter 16) must be followed. For additional information, please contact
your support person at LOYTEC or visit our website.
LOYTEC is constantly working on improving the existing products in order to follow the
latest cyber security standards. Therefore, LOYTEC strongly recommends installing updates
as soon as they become available and always using the latest software versions. LOYTEC
explicitly points out that using older versions or refraining from updates increases the risk of
online security threats.
3 Safety Instructions
ATTENTION
Please regard the following general instructions for project planning and
execution:
ATTENTION
CAUTION
Electrical Safety
CAUTION
CAUTION
CAUTION
Device Safety
CAUTION
CAUTION
Functional Earth
CAUTION
The power supply must meet the requirements for SELV or PELV. Permitted
deviation of the nominal voltage:
CAUTION
CAUTION
Power supplies must be designed for 100% duty cycle to supply SELV or
PELV circuits.
U.S.: Class 2 circuits according to UL 5085-3.
For efficiency reasons, the power drawn from the power supply should be at
least 50% of the nominal load.
CAUTION
CAUTION
CAUTION
CAUTION
LPAD-7 Touch Panels require a PoE Class 1 power supply (max. 12W),
which must be compliant to IEEE 802.3at-2009.
For the power supply of the PoE switches observe the manufacturer’s
specifications.
CAUTION
The menu structure on the Web UI has been redesigned to be more intuitive and group
frequent actions together. New top-level menus help keeping the menus organized into
typical tasks, such as statistics, data viewing, commissioning, configuration, programming,
security, and maintenance.
LOYTEC devices now provide a simple user management to create users and passwords on
the go. Users can be assigned roles, such as ‘admin’, ‘operator’ or ‘lweb’ roles. Users having
the ‘lweb’ role are limited to using LWEB-802/803 visualization projects only and have no
other device operation capabilities.
The Web UI on the device allows creating, deleting and modifying users and assigning roles.
As an example, an additional admin user can be created who is allowed to configure the
device without knowing the master admin password. This user account can easily be disabled
again.
To further increase security in a network installation, IT departments support the 802.1X port
authentication method. This standard requires a device to authenticate its port on the network
switch, before traffic into the network is allowed.
LOYTEC devices can enable 802.1X port authentication in the port mode settings. The
authentication methods Protected EAP (PEAP), Tunneled TLS (TTLS) and EAP-TLS (using
certificates) are supported.
LOYTEC devices now support the LTE-800 mobile interface. This interface is connected via
the USB port and offers LTE/UMTS/GSM mobile network access. A SIM card from your
provider needs to be inserted and the LOYTEC device is ready on the mobile network. A
Mobile tab has been added to the port configuration interface for configuring the LTE-800.
Simply enable Mobile Network, enter your APN data and select which protocols shall be run
on LTE.
The VPN client is also ready to be used on the LTE mobile network.
Combined with an LTE-800 mobile interface a LOYTEC device can act as a NAT router to
share the mobile Internet connection with other devices on the LAN. For doing so, the
Internet connection sharing feature can be enabled on the IP Host tab, where the default
router interface is selected. Other devices on the LAN need to specify the IP address of the
LOYTEC device offering connection sharing as their default gateway. This way, local
devices can use NTP, VPN client or other Internet services.
Dynamic DNS
LOYTEC devices can now make use of a dynamic DNS service to register a public DNS
name. This makes the device reachable over a public IP address that can change over time,
for instance an LTE-800 mobile interface using a public IP address assigned by the mobile
carrier. A number of dynamic DNS providers are preconfigured and can be selected on the
IP Host tab of the port configuration as shown in Figure 7.
This firmware version enhances flexibility and control over which building automation
protocols are directly available on the VPN. A separate VPN tab has been added to the port
configuration that allows configuring IP-based control protocols to be running directly on the
VPN client. This effectively secures otherwise unsecured automation protocols such as CEA-
852. When running on the VPN interface, the protocols are assigned the VPN’s IP address
and as a protocol node, the LOYTEC device is also reachable over multi-NAT access
networks, such as LTE.
For example, simply set up the CEA-852 configuration server on the VPN interface and add
all other CEA-852 clients on the same VPN. Each node establishes a secure channel to the
OpenVPN server hub, which routes the traffic between the communicating peer nodes. No
unencrypted traffic will ever be transmitted.
VPN
LOYTEC devices support joining a virtual private network (VPN). This feature is based on
the widely-used and open-protocol OpenVPN technology. An OpenVPN configuration file
(.ovpn) can be installed on the Web interface and makes the LOYTEC device a VPN client
and dial into the OpenVPN server defined by that file. Any standard OpenVPN configuration
file can be used, which is auto-login, i.e. does not require entering a password when
connecting. After having registered, the LOYTEC device can be reached via its VPN address.
Setting up a VPN client on the LOYTEC device may solve NAT router issues, because no
port forwarding rules need to be configured. The device dials out to the OpenVPN server
running on a public IP and establishes the VPN channel. This VPN channel provides a secure
connection for building automation protocols, such as BACnet/IP, Modbus TCP or CEA-
852. Being part of a VPN the LOYTEC device is also reachable over multi-NAT access
networks, such as LTE.
An alternative method is to enable simple server mode on the LOYTEC device. In this mode,
the device provides an OpenVPN server and allows downloading a client configuration file
from the Web interface. This file can be installed on any OpenVPN client and allows that
client connect to the LOYTEC device over the secure VPN channel. Only one client may
connect at a time.
The entire Web interface of the device has been localized to German, French, and Chinese
language. Simply change the language on the LCD display or directly on the Web interface
via the new flag symbol on the upper right corner. Changing language is instant and does not
require a reboot.
Changing IP settings and rebooting could end in a device unreachable, if something was
different than expected. The new safe reboot feature helps out by reverting the changes made,
if not logged in in on the Web interface within 5 minutes after the reboot. Locking oneself
out by entering a mistaken IP address is no longer possible.
Another new feature that helps getting logged in again is the session auto-login. After a
device has rebooted the Web interface restores the session and automatically logs in again.
Even when changing a static IP address the device tries to connect to the new IP or suggests
links for opening the device info page under the new IP address.
The firmware upgrade feature has been made safer by creating a backup before executing the
upgrade. This feature has been added to firmware and Configurator upgrade paths. It is,
however, optional and can be turned off by deselecting the check box.
LCD Interface
The user interface on the LCD display has been localized for the Chinese simplified and
traditional language sets. The language can be selected from the main page and is switched
immediately without a device reboot.
The user interface on the LCD display has been extended by a firmware upgrade menu. This
menu allows installing a new firmware image from an attached USB memory stick. This is
beneficial for WLAN-only devices. When plugging in a USB memory stick, a menu pops up
(Figure 13) on the LCD interface that shows selected quick options, including firmware
upgrade and backup.
The new L-IP models with their product code ending in “C” are now supported. Equipped
with dual Ethernet, a built-in firewall and LCD display, these new models serve as a plug-in
replacement for the older series “B” devices. Existing device backups can be used without
modification. In addition, the new models also support the wireless LAN technology.
Project Documentation
A new feature on the device is a Web UI for creating and viewing project documentation on
the device. The documentation editor requires admin rights and allows storing files on the
device or creating documentation links as URLs. Both items can be viewed by guest users.
Examples include storing cabling plans as PDF or adding links to a Web site containing
manuals, plans or other useful project documentation. Read Section 7.6.3 to learn more about
project documentation on the device.
Series “C” L-IP models with two Ethernet interfaces can be configured to work with separate
and isolated IP networks. For example, one Ethernet interface can be accessed over HTTPS
from a WAN connected to Ethernet 2 while the building network services are running locally
on the LAN connected to Ethernet 1. For configuration the device provides separate Ethernet
tabs in the port configuration, which allow selecting the offered services on each interface.
The example in Figure 14 shows a WAN interface with HTTPS and OPC UA only, while
CEA-709 over IP (CEA-852) are still bound to Ethernet 1 (LAN). For more information on
how to use multiple Ethernet ports please refer to Section 7.3.4.
WLAN Interface
In combination with the external LWLAN-800 interface, the device provides new interface
tabs for wireless IP networks. Similar to the second Ethernet interface, one can choose which
protocols are available on the wireless network. The wireless interface can be configured as
a WLAN client, access point or mesh node. Using the latter, a wireless mesh network of
LOYTEC devices can be built. Please refer to Section 7.3.8 to learn more about the WLAN
interface.
SNMP
For accessing vital operational data in standard IT equipment, L-IP series “C” devices offer
an SNMP management base (MIB). All system registers are available in that MIB. The MIB
file can be downloaded from the device and imported in the SNMP management tool. For
more information on configuring and using SNMP with a LOYTEC device please refer to
Section 11.1.
OPC Server
The L-IP series “C” devices are equipped with an OPC server, which can speak the well-
known OPC XML-DA and OPC UA protocols. The OPC server is used for perfect integration
with the LWEB-900 building management software for device maintenance.
The L-IP series “C” models have the Wireshark packet capture feature. Using this feature
local packet logs can be made and stored on the L-IP. It is also possible to connect a running
Wireshark protocol analyzer on the PC to the L-IP and run a life packet capture. For more
information on how to set up packet capture, please refer to Section 14.9.
5 Quick-Start Guide
This Chapter shows step-by-step instructions on how to configure the L-IP for a simple
network architecture in a LAN environment.
Figure 16: L-IP Redundant in Twin Router mode with Bus Loop Monitoring
Figure 17: L-IP Redundant in Twin Router mode without Bus Loop Monitoring
4. Then open your Web browser and type in the default IP address 192.168.1.254.
5. Click on Config in the left menu. You will be asked to enter the passwords for the
administrator and operator accounts before proceeding.
6. The Config menu opens. Click on Port Config and change to the tab Ethernet. The
TCP/IP settings are selected as shown in Figure 20. Enter the IP address, the IP netmask,
and IP gateway for this device.
7. Press Save Settings and then reset the device by selecting Reset in the highlighted text.
This changes the IP settings of the device.
1. On the LCD main screen set the desired language. Navigate to the flag symbol, press the
button and choose the desired language.
2. Navigate to the IP address on the main screen and press the button.
3. There navigate to the needed input fields, press and change the value. Press again to set
the value. Continue to the next field.
5. Acknowledge the reboot and the device reboots with the new IP address.
1. On the LCD main screen navigate to the address field next to CS and click on it.
2. This leads to the CEA-709 over IP menu. Navigate to the Config Server IP and enter
the IP address into the four fields. Optionally adapt Config Server Port.
3. If the channel requires MD5 authentication, set MD5 to ON and enter the secret key
below.
4. Finally navigate to the bottom, click Save and acknowledge with YES. The device now
tries to register with the configuration server. Observe the status information to see, if
the registration completes.
5. Back in the home screen the configuration server is shown with a checkmark.
Then go to the menu CEA-852 Ch. List and click on the Add Device button to add a new
client device. Enter name and IP address and click the Save button as shown in Figure 21.
Client devices include all other L-IPs and all PCs, which should participate in the
communication on the IP-852 channel.
Verify in the channel list that the device(s) have been registered successfully and show a
green checkmark. The CNIP-LED on all L-IP devices that have one should be green and the
SERVER-LED on the configuration server L-IP should be green as well. L-IP devices with
an LCD display will show the configuration server address (or LOCAL) and a checkmark if
registered correctly at the configuration server as shown in Figure 22.
Add the L-IP router to your network drawing and commission the L-IP. Note that we provide
shapes for LonMaker. You should now be able to communicate via an IP-852 channel. For
detailed instructions on how to configure the configuration server please refer to Section
7.3.14.
The L-IP Redundant comes preconfigured to support bus loop monitoring (see Figure 15).
For operating the device in twin router mode (device redundancy, see Figure 16) some
additional steps have to be performed:
Add one router shape for each L-IP Redundant. Connect both to the same IP-Channel on
one side and to the same FT-10 Channel on the other side of the router.
Add one L-IP Redundant built-in monitoring node “L-IP Redundant Diagnostic FT-10”
device shape for each L-IP Redundant on the FT-10 channel. The corresponding device
template will be installed with the L-IP Redundant Plug-In available from the LOYTEC
webpage http://www.loytec.com.
Add a “Twin Router” functional block for each L-IP Redundant monitoring node.
Connect nvoRedRtr of one L-IP Redundant with the nviRedRtr of its paired L-IP
Redundant and vice versa.
If using LonMaker for Windows the resulting drawing should look like shown in Figure 23.
Furthermore, the PRIM LED on one of the two L-IP Redundant devices should be green and
should be off on the other one.
Figure 23: A pair of L IP Redundant devices configured for twin router operation
For detailed instructions on how to configure the L-IP Redundant refer to Section 10.
6 Hardware Installation
6.1 Enclosure
The enclosure of the product and its terminal layout are shown on the installation sheet found
in the product’s box.
unique node ID and virtual ID of each port (NIDx and VIDx) with bar-code,
Unless stated otherwise, all bar codes are encoded using “Code 128”. An additional label is
also supplied with the L-IP for documentation purposes. The specific contents of the product
label are shown on the installation sheet found in the product’s box.
6.3 Mounting
The device comes prepared for mounting on DIN rails following DIN EN 50 022. The device
can be mounted in any position. However, an installation place with proper airflow must be
selected to ensure that the L-IP temperature does not exceed the specified range.
Every time the L-IP Redundant contacts its twin router the LED is switched off shortly to
signal this activity.
Green: The CEA-852 device is fully functional and all CEA-852 configuration data (channel
routing info, channel membership list, send list) are up-to-date.
Green flicker: If a valid CEA-709 packet is received or transmitted over the IP channel the
CNIP LED turns off for 50 ms. Only valid CEA-709 IP packets sent to the IP address of the
L-IP can be seen. Stale packets or packets not addressed to the device are not seen.
Yellow: Device is functional but some configuration data is not up-to-date (device cannot
contact configuration server but has configuration data saved in Flash memory)
Red: Device is non-functional because it was rejected from the CEA-852 IP channel or shut-
down itself due to an internal error condition.
Off: Device is non-functional because the CEA-852 device has not started. This can be the
case if the device uses DHCP and it has not received a valid IP configuration (address) from
the DHCP server.
Flashing red at 1 Hz: Device is non-functional because the CEA-852 device is started but has
not been configured. Please add the device to a CEA-852 IP channel (register in configuration
server).
Flashing green or orange at 1 Hz: The device’s CEA-709 side of the gateway has not been
commissioned yet. The color indicates the CEA-852 IP channel status as described above.
If the LED does not light up at all this port is not connected to any network segment or
the connected network segment currently shows no traffic.
If the LED is flashing green the network segment connected to this port is ok.
If the LED is flashing red a potential problem exists on the network segment connected
to this port. This state is referred to as overload condition.
the average bandwidth utilization of this port was higher than 70% or
more than 15% CRC errors have occurred on a port with a power-line transceiver or
more than 5% on a port with a transceiver other than power-line or
the L-IP Redundant has detected an open loop (L-IP Redundant only, see Section 10).
For a deeper analysis of the reason of the overload condition it is recommended to use a
protocol analyzer (e.g. LOYTEC’s LPA) or a similar tool. The exact reason of the overload
condition can also be determined with the LSD Tool (see Chapter 15).
Pressing the status button longer than 2 seconds will allow you to select the port to sends out
the “Service Pin Message” message: The port LED of the currently selected port will light
up orange. After 2 seconds the next available port will be selected. When the status button is
released the “Service Pin Message” is sent out on the currently selected port.
Pressing the status button during normal operation for more than 20 seconds resets the
switching tables (see Section 6.5.1).
Clearing the group forwarding, the subnet/node forwarding and the router domain table
when used in smart switch mode.
But does not clear the IP address and CEA-852 configuration settings.
All this is done when the button is released. Afterwards a reset is performed to let the changes
take effect. Once the button is held down for more than 20 seconds the CEA-709 activity and
the CNIP LED are switched to orange and stay orange until the button is released and the
L-IP is reset. This indicates that the forwarding tables will be reset.
Alternatively to holding down the status button the forwarding tables can be reset in the
Device Management menu on the LCD display (see Section 6.6.1).
Important: If the L-IP is operated in smart switch mode and is moved from one location to another or
if major changes to the configuration of the network are made, it is recommended to reset
the L-IP forwarding tables.
Important: Wait at least 30 seconds after power-up of the L-IP before pressing the Status Button to
ensure that the L-IP has booted properly!
Below are menu items. Turn the jog dial to navigate between menu items and press to enter
a menu or go into selection mode. When in selection mode turn the jog dial to alter the value
and press again to quit the selection.
The Device Settings »» menu allows configuring basic device settings. Navigate to the
Device Management »» sub-menu, which is displayed in Figure 29.
This menu gives you the following options for basic device configuration:
HTTP Server: This menu allows to enable/disable the HTTP server and to configure its
TCP port.
HTTPS Server: This menu allows to enable/disable the HTTP server, to configure its
TCP port and to remove an installed certificate.
CEA-709 over IP: This menu allows editing the CNIP client settings that are needed to
register with a configuration server. See Section 6.6.3 for details.
Date/Time: This menu allows setting the system time. A time synchronization
mechanism can be chosen, and the UTC offset and daylight savings can be defined.
Send ID messages: When selecting this menu, the device sends out service pin, BACnet
I-Am, and identification broadcasts for finding the device in the L-Config tool on all
applicable ports.
Reload config: By choosing this menu, the device performs a quick restart by reloading
its configuration only.
Reboot system: By choosing this menu, the device performs a full reboot.
Factory Defaults: By choosing this menu, the user can reset the entire device to its
factory default. Also IP addresses are cleared.
Remote Config: When enabling this option, the LWEB-822/900 master device manager
restores the last saved configuration to the discovered device, if it has no configuration
yet. This feature is beneficial when replacing a device.
PIN: Alter the default PIN to any 4-digit number to protect certain operations on the
LCD UI. The user will be prompted to enter the PIN on protected areas.
Language: By choosing this menu, the user can switch between languages on the LCD
display.
Reset switch tables: Choose this item to reset the forwarding tables in the switch.
This menu gives you the following options for the CEA-709 router port:
Send Nodepin: This menu allows sending a node pin message to the CEA-709 network.
NIDA, NIDB: These items show the Node IDs of the two ports on the selected router.
This opens the CEA-709 over IP menu with the following settings:
Config Server IP: Enter the IP address of the configuration server into the four separate
input fields.
Config Server Port: Enter the configuration server port. The default 1629 can be left
unchanged in most cases.
Config Client Port: Enter the configuration client port. The default 1628 can be left
unchanged in most cases.
MD5: The default is off. Turn this on, if MD5 authentication shall be used on the channel
for security purposes.
Key: If MD5 is turned on enter the MD5 secret key into the 16 input fields.
The title page also shows the CEA-852 client state as a symbol next to the CS address. It can
be normal ( ), waiting for the configuration server ( ), or not registered ( ). If MD5 is
enabled on this device a lock icon is shown.
6.7 Wiring
6.7.1 L-IP
Every network segment connected to the L-IP needs to be terminated according to the rules
found in the specification of the transceiver (see Chapter 12).
Important: All used and unused ports must be properly terminated. LOYTEC recommends the use of
the LOYTEC L-Term series network terminators (LT-13 or LT-33 respectively). For
unused ports, it is recommended to use a 100 Ohm 0.25 W resistor between terminals A
and B as termination.
Important: When using shielded network cables, only one side of the cable should be connected to
earth ground. Thus, the shield must be connected to earth ground either at the L-IP
terminals or somewhere else in the network (see Figure 32)!
Figure 32: Connecting the Earth Ground to the L-IP series “B”.
Important: All used and unused ports must be properly terminated. LOYTEC recommends the use of
the LOYTEC L-Term series network terminators (LT-13 or LT-33 respectively). For
unused ports, it is recommended to use a 100 Ohm 0.25 W resistor between terminals A
and B as termination.
Important: When using shielded network cables, only one side of the cable should be connected to
earth ground. Thus, the shield must be connected to earth ground either at the L-IP
terminal (loop port 1) or somewhere else in the network, but never at more than one place
(see Figure 33)!
Important: If operated with bus loop monitoring enabled (loop port 1 and loop port 2 connected), both
sides of the loop must be terminated at the L-IP terminals (see Figure 33). In this case two
terminators for bus topology must be used.
Important: If operated with bus loop monitoring enabled, the loop must not contain any repeaters!
7 Web Interface
The L-IP comes with a built-in Web server and a Web interface to configure the device and
extract statistics information. The Web interface allows configuring the IP settings,
CEA-709, CEA-852 and other configuration settings.
4. Then open your Web browser and type in the default IP address ‘192.168.1.254’.
The login screen of the device is shown and prompts for initial administrator and operator
passwords to be set. The password strength indicator will inform you about the security
quality of your passwords. Enter the passwords in the screen as shown in Figure 34 and then
click on Set passwords.
The Web UI cannot be used without configuring the passwords. Note that strong passwords
should be chosen (avoid ‘admin’ or ‘loytec4u’). The device information page will appear.
The passwords can be changed later as described in Section 7.4.1.
The Device Status section summarizes the status of the various ports and protocols on the
device. The summary status is displayed as a green OK checkmark. If any of the interfaces,
protocols or operational parameters are non-normal, a warning or error sign is shown instead.
Shown below are further a summary on the active protocols on the respective ports. All items
are links that lead directly to their configuration page.
Below the general status information more specific sections are displayed depending on the
model. The Firmware Info provides version and build times of the primary and fallback
firmware images installed on the device.
The page also includes the unique node IDs (“Neuron IDs”) of the CEA-709 network
interfaces. The multi-port L-IP displays the external node IDs as well as the node IDs for the
internal backbone in separate. This page can also be used to send the CEA-709 service pin
messages. This is a useful feature when commissioning the device, since it is not necessary
to be on-site to press the status button.
If logging in using a local user having the ‘admin’ role, edit the user name in the Account
field.
To save the log click on the Save System Log button. When contacting LOYTEC support,
have a copy of this log ready.
7.2.2 IP Statistics
Figure 38 shows the IP statistics page. The Ethernet tab allows finding possible problems
related to the IP communication. Specifically, any detected IP address conflicts are displayed
(if the device’s IP address conflicts with a different host on the network). It also shows the
routing table, the ARP table (including IPv6 neighbours), DNS configuration, and detailed
connection statistics. The Wireless tab contains statistics specific to the LWLAN-800
interface.
The NTP tab provides information on the contacted NTP servers and their synchronization
status. The PHY tab shown information on the Ethernet link state, link speed and seen MAC
addresses on either Ethernet port.
The Round Trip Time (RTT) is measured as the time a packet sent to the peer device needs
to be routed back to the device. It is a measure for general network delay. If the test to a
specific member fails, a text is displayed to describe the possible source of the problem. The
reasons for failure are summarized in Table 4.
OK, Return path not tested (green Displayed for a device which is reachable but which does not support the
checkmark) feature to test the return path (device sending to this CEA-852 device).
Therefore a potential NAT router configuration error cannot be detected. If
the tested device is an L-IP, it is recommended to upgrade this L-IP to 3.0 or
higher.
Not reachable/not supported This is displayed for the CS if it is not reachable or the CS does not support
(red exclamation) this test. To remove this uncertainty it is recommended to upgrade the L-IP to
3.0 or higher.
Local NAT config. Error This is displayed if the CEA-852 device is located behind a NAT router or
(red exclamation) firewall, and the port-forwarding in the NAT-Router (usually 1628) or the
filter table of the firewall is incorrect.
Peer not reachable Displayed for a device, if it is not reachable. No RTT is displayed. The device
(red exclamation) is either not online, not connected to the network, has no IP address, or is not
reachable behind its NAT router. Execute this test on the suspicious device to
determine any NAT configuration problem.
Table 4: Possible Communication Problems.
Under the first table, the Data Connection status is displayed. For testing purposes, the
button Reconnect allows clearing and re-connecting the LTE data connection. The button
Restart Modem allows restarting the LTE modem. During normal operation, these actions
are not necessary.The second table Mobile Network Statistics provides information on data
and SMS transfer volume per data connection. The Clear Statistics button clears the data of
this table but leaves the aggregated data volume unchanged.
The time sync source can be set to auto, manual or NTP. In the auto mode, the device
switches to the first external time source that is discovered. The option manual allows setting
the time manually in the fields Local Time and Local Date. In manual mode, the device
does not switch to an external time source. Note, that if NTP is selected, the NTP servers
have to be configured on the IP Configuration page (see Section 7.6.1).
The time zone offset must be defined independently of the time source. It is specified as the
offset to GMT in hours and minutes (e.g., Vienna/Austria is +01:00, New York/USA
is -06:00). For setting the daylight saving time (DST) predefined choices are offered for
Europe and USA/Canada. DST can be switched off completely by choosing none or set
manually for other regions. In that case, start and end date of DST must be entered in the
fields below.
The Language setting allows changing the language of the Web interface. When changing
the language setting it becomes effective immediately. Changing this setting is the same as
changing language on the LCD display.
7.3.3 IP Configuration
The TCP/IP configuration is done under the Ethernet port tab as shown in Figure 44. The
mandatory IP settings, which are needed to operate the device, are marked with a red asterisk
(IP address, netmask, gateway). The Enable DHCP checkbox switches between manual
entry of the IP address, netmask, and gateway address, and automatic configuration from a
DHCP server.
The device comes configured with a unique MAC address. This address can be changed in
order to clone the MAC address of another device. Please contact your system administrator
to avoid MAC address conflicts.
The settings for DNS and NTP servers should be made in the IP host settings (see Section
7.3.6). In case an IP interface runs DHCP, the DNS and NTP addresses supplied by DHCP
can be seen here. Models with one Ethernet port only do not have these settings here.
Other standard protocols that are bound to the Ethernet interface are SSH, FTP, Telnet, and
HTTP (Web server). By deselecting the checkbox, those protocols can be individually
disabled. The standard UDP/TCP ports can be changed in the respective protocol settings.
An example for the SSH server is shown for SSH in Figure 45. Note that HTTP for the Web
server can only be disabled on the LCD display or when opening the Web interface using
HTTPS.
For each IP interface configured as a separate network, the various standard protocols can be
enabled separately. As a default, the secure protocols HTTPS, SSH and OPC UA are enabled
on a new separate IP interface. Some protocols can be enabled on multiple interfaces at the
same time, others on one interface only. If one of the latter is enabled on a new separate IP
interface, a warning will be displayed, stating on which other interface the protocol will now
be disabled (e.g., CEA-709 over IP).
The separate network mode can be used, if you want to operate an isolated building network
on the LAN and expose some aspects outside the building network (denoted as WAN).
Physically, the two Ethernet ports will be plugged into different Ethernet switches.
To disable a separate IP interface, choose Disable in the port mode setting. This change is
effective immediately without a reboot. To configure switch mode again, choose Switch
Ethernet 1+2 in the port mode setting.
LOYTEC devices can enable 802.1X port authentication in the Port Mode settings on the
Ethernet tabs of the port configuration (see Figure 47). Set the checkbox Enable 802.1X.
Then choose an authentication EAP Type required by your IT department. The following
EAP types are supported:
Protected EAP (PEAP): For this type define an inner Authentication method (e.g.
MSCHAPv2) and Username and Password. Anonymous identity and CA certificate of
the Radius server are optional. The latter is needed if the Radius server shall be
authorized.
Tunneled TLS (TTLS): For this type define an inner Authentication method (e.g.
PAP) and Username and Password. Anonymous identity and CA certificate of the
Radius server are optional. The latter is needed if the Radius server shall be authorized.
To delete any of the installed certificates, click on the Delete button next to it. Then another
certificate may be installed by clicking the Choose file button. The selected file is noted next
to the button. Click Save Settings to store the selected certificates.
Hostname and Domainname are optional entries and can be left empty. For some DHCP
configurations it may be necessary to enter a hostname. Please contact your system
administrator on how to configure DHCP to acquire an IP address.
If the device possesses more than one IP interface the Default Gateway setting defines the
gateway of a given IP interface, which is going to route all non-local network traffic. One of
the existing IP interfaces with a separate network must be selected here.
Up to three DNS Servers can be defined on this page. These DNS servers will be contacted
by all services on any of the IP interfaces for name resolution. In case the DNS servers are
supplied by DHCP running one of the IP interfaces, change the setting Use DNS servers
from to point to that interface.
The device can be configured to synchronize its clock with NTP time. Enter the IP address
of a primary and, optionally, a secondary NTP server. The device will use NTP as a time
source if the time sync source in the system configuration page is set to NTP (see Section
7.3.1). The field NTP status below the NTP server settings displays the current NTP
synchronization status (out-of-sync, or in-sync). The settings made here apply to all IP
interfaces. In case the NTP servers are supplied by DHCP running one of the IP interfaces,
change the setting Use NTP servers from to point to that interface.
The Connection Keep Alive feature allows the device to automatically ping other devices
on the IP network in order to maintain an IP connection that might be automatically
disconnected after a specific period of time (e.g. DSL routers automatically disconnect if no
activity is detected). When enabled choose one of the options Auto IP or Custom IP.
If auto IP mode is selected and the device has a CEA-852 configuration server, a ping
message is sent to all CEA-852 devices in the channel list of the configuration server. If the
configuration server is disabled on this device a ping message is sent to the configuration
server for the IP-852 channel, if one is known. If custom IP is selected, one specific IP address
can be configured as the ping destination.
12.5. Depending on the required wireless modes, the first configuration step is to select the
port mode on the Wireless tab of the port configuration, as shown in Figure 50.
Separate network: The wireless interface is enabled, but not bridged to any
Ethernet interface. It provides its own, isolated services.
Bridge to Ethernet 1: The wireless interface is enabled and bridged to the Ethernet
1 interface.
Bridge to Ethernet 2: The wireless interface is enabled and bridged to the Ethernet
2 interface.
After having selected the port mode, the IP settings have to be set, if the wireless port is
configured as a separate network. The wireless interfaces are configured in the same way as
Ethernet interfaces described in Section 7.3.4. Depending on the wireless mode, there are
some differences:
Access point mode (separate network): The IP address and netmask are used to
define the network in which client get an IP address from the built-in DHCP
server. DNS and NTP settings are not needed in this mode.
Important! The LWLAN-800 supports a combined maximum of 7 connected clients. When using Mesh
mode on the second wireless interface, the total of all Mesh and AP client connections is
limited to 7.
The wireless client settings are made in the Wireless protocol area. This allows setting the
WIRELESS mode in a drop-down box. The following basic modes are available, which are
described below in more detail:
Access Point Mode: The device provides a WLAN access point where a client can
connect to the wireless network created by the device.
Mesh Mode: This mode is used to create an IEEE 802.11s mesh network.
Client Mode. A wireless interface in client mode has the settings shown in Figure 51.
The following settings are used to configure the wireless client mode:
SSID: This is the service set ID identifying the wireless network to connect to. It
can be entered manually, e.g. if the network is hidden, or scanned using the scan
button. Note that scanning interrupts an active wireless connection, so use this
button only when setting up the wireless connection.
Search Results: The search results list contains the discovered SSIDs and signal
strenghts. Selecting one of the items copies it into the SSID field.
Key Management: This list selects between NONE (no encryption), WEP, WPA
and WPA2 encryption. The recommended setting is WPA2, as WPA and WEP are
not considered secure anymore and are provided for backwards compatibility.
Pre-Shared Key: The preshared key is the encryption key for the wireless network.
The show checkbox shows the PSK in clear text.
Access Point Mode. An access point has the settings shown in Figure 52.
The following settings are used to configure the access point mode:
SSID: This is the service set ID identifying the wireless network provided by this
access point. The hide SSID checkbox hides the SSID, so that it cannot be scanned.
Not that hiding an SSID has more security drawbacks than advantages, so that this
setting should be left deactivated.
Region: This defines the region, Europe, North America or Japan, in which this
access point is deployed. Note that this settings has to be made correctly to comply
with regulatory restrictions. Incorrect settings may cause interference.
Channel: This field selects an available channel. The 2.4 GHz Band provides 13
channels. However these channels overlap and cannot be used without interference.
When possible, use channels 1, 6 or 11 to avoid overlapping networks.
802.11 Protocol: This field selects the wireless protocol to use. The default and
recommended setting is 802.11b/g/n, which provides all protocols. If there are
compatibility issues with some clients, the access point can be restricted to
802.11b/g or 802.11b.
Key Management: This list selects between NONE (no encryption), WEP, WPA
and WPA2 encryption. The recommended setting is WPA2, as WPA and WEP are
not considered secure anymore and are provided for backwards compatibility.
Encryption Type: This list selects between different encryption options, e.g. AES
or TKIP.
Pre-Shared Key: The preshared key is the encryption key for the wireless network.
The show checkbox shows the PSK in clear text. For a secure network, please use
WPA2, AES encryption and a PSK with at least 16 characters.
The buttons in the bottom area allow to export and import the wireless configuration. This
allows to configure a device and to easily transfer the wireless settings to other devices. The
Export button allows to save a file containing the wireless settings. The Import button
imports a wireless configuration which has been selected by the Browse button. After
changing the wireless settings, you need to click on Save Settings and reset the device for
applying the settings.
MeshID: The Mesh ID identifies the wireless network, which the device shall
connect to. It can be entered manually or scanned by clicking the Scan button, which
searches for available Mesh networks. Please note that a scan interferes with the
Search Results: This list shows the scanned Mesh networks, the radio channels in
use and their signal strength. By selecting an entry in this list, the respective settings
are accepted.
Channel: This field selects a radio channel. The 2.4 GHz band has 11 channels.
These channels, however, may overlap. Therefore not all of tem can be used without
interference. When possible, choose the channels 1, 6, and 11 in order to avoid
overlaps. All Mesh nodes in the network must use the same channel.
Signal Strength: This field allows setting the transmission signal strength between
5 and 100%. It can be used to reduce the signal strengh, if interference with nodes
farther away shall be minimized. Ususally, it will be left at the default 100%.
PIN: This field is used to choose an 8-digit PIN code. The Generate PSK button
generates a 64-digit pre-shard key from this PIN code. The PIN code also makes
Mesh setup easier on the LCD display.
Pre-Shared Key: This field defines the password for the Mesh network. By
selecting the check box show the password is shown as clear text.
Mesh Member: This field configures the Mesh Point ID. This ID must be unique
for each Mesh ID domain. The button Generate Whitelist can be used to generate
a default whitelist. Valid Mesh Point IDs are in the range between 1 and 20.
Whitelist: This field allows configuration of up to 7 mesh point IDs, which are
allowed to communicate with this Mesh Point. The button Mesh Graph Editor
opens a graphical editor for a simplified configuration of whitelists in the Mesh
network.
Important! The LWLAN-800 supports a combined maximum of 7 connected clients. When using AP
mode on the second wireless interface, reduce the number of whitelisted Mesh Points by
the number of allowed AP clients.
Visualization Port: This field configures the UDP port used for the Mesh network
visualization. Entering ‘0’ in this field deactivates the visualization traffic.
The buttons in the bottom area allow to export and import the wireless configuration. This
allows to configure a device and to easily transfer the wireless settings to other devices. The
Export button allows to save a file containing the wireless settings. The Import button
imports a wireless configuration which has been selected by the Browse button. After
changing the wireless settings, you need to click on Save Settings and reset the device for
applying the settings.
Mesh Graph Editor. This is a visual editor to assist a simple configuration of whitelists in
the Mesh network as shown in Figure 54 and Figure 55. Depending on the configuration of
Mesh points and connections between them in the Mesh graph, the resulting whitelist for this
Mesh network graph is displayed. When changing the Mesh graph this list is updated. The
following operations are available:
Add a Mesh-Point: Clicking on the unused space of the graph editor creates a new
Mesh Point. A new Mesh Point ID is assigned using the lowest available ID. Up to
20 Mesh Points can be added to the graph editor.
Change a Mesh Point ID: Double-click on a Mesh Point and enter a new Mesh Point
ID.
Change the graph layout: By holding the CTRL key Mesh Point can be moved
around in the graph in order to adapt the graph to the actual layout on site.
Add a floorplan: By clicking the button Load Floorplan graphics can be loaded
from a .jpg or .png file as a floorplan. By holding the CTRL key and clicking on the
background the floorplan can be adapted to your needs.
Scaling the floorplan: The drop-down box beneath the floorplan allows selecting a
scale factor.
By using a floorplan in the Mesh graph the local layout of the building can be considered
when configuring the Mesh network. Figure 54 shows the Mesh network visualization using
a floorplan from the top view of the building. In contrast Figure 55 shows an overview plan
of a building with five floors from the side view. If Mesh network visualization over UDP
has been activated, the current signal strength between the Mesh points is added to the view.
The connections are colored depending on the signal strength. Green stands for a good
connection over -50 dBm, orange stands for a medium connection of about -50 dBm to -70
dBm and red stands for a weak connection under -70 dBm. By looking at the color-coded
connection it is fairly easy to identify weak connections and go forward to troubleshoot weak
spots in the configuration.
Figure 55: Mesh floorplan from side view and online monitor
Mesh Point Statistics. Weak performance or bad reliability in a Mesh network can have
several reasons. One of them is a badly integrated Mesh point in the Mesh network. Such a
weak point is revealed by bad connections to other Mesh points. Figure 56 shows Mesh point
statistics of directly connected Mesh points. The statistics data provides information on Mesh
point ID, MAC address, received and transmitted data, the signal strength, authentication
status and time of inactivity.
One of the most important values are the signal strength and the authentication status. The
authentication status should always indicate successful authentication under normal
operation and the signal strength should be no less than -70 dBm for a reasonable connection.
Mesh Path Statistics. The Mesh path statistics shown in Figure 57 provide information on
the Mesh paths to all Mesh points in the Mesh network. Each line shows a Mesh path with
the receiver Mesh point ID. Additionally, the Mesh point ID of the neighboring node is given
for the respective path, to which packets are forwarded in order to reach the addressed
receiver Mesh point. More statistics information are the Mesh path metric, the sequence
number, the expiration period, the buffered packets and the state of the Mesh path.
The most important figures are the Mesh path metric and the state of the Mesh path. The
Mesh path metric reflects the path quality from the Mesh point to the receiver Mesh point.
The smaller the path metric the better the connection quality to the receiver Mesh point. A
value larger than 500, however, should not be reached. In this case the Mesh point whitelist
should be optimized for this Mesh path. For normal operation the Mesh path state should
always read ‘active’‚ ‘sn_valid’ or ‘resolved’. This indicates an active and resolved Mesh
path with a valid sequence number.
The VNC server can be configured on the Ethernet tab of the port configuration. To turn on
the VNC server, enable the VNC for LCD UI checkbox. The VNC protocol settings are
displayed in the settings box on the right-hand side as shown in Figure 58. The VNC port
and VNC password can be changed. As a default, only one VNC client may connect. This
limit may be increased in Max VNC clients. In order to protect changes made on the LCD
UI over VNC with a PIN code, the Admin PIN code can be configured. To disable PIN
protection, enter ‘0000’.
The CEA-852 protocol settings are displayed in the settings box on the right-hand side as
shown in Figure 60. Typically, the device is added to an IP channel by entering the relevant
information on a configuration server. The configuration server then contacts the CEA-852
device of the L-IP and sends its configuration.
The field Config server address and Config server port display the IP address and port of
the configuration server, which manages the L-IP and the IP channel. The field Config client
port represents the IP port of the device’s CEA-852 device. This setting should be left at its
default (1628) unless there are more than one CEA-852 devices operating behind a single
NAT router. Please refer to Section 8.3 to learn more about NAT configuration.
In the field Device name the user can enter a descriptive name for the L-IP, which will appear
in the IP channel to identify this device. You can enter a device name with up to 15 characters.
It is recommended to use unique device names throughout the IP channel.
The Channel mode field reflects the current channel mode of the CEA-852 device. It is
configured by the configuration server. If there are any two devices in the channel which use
the same IP address but different ports (e.g., multiple devices behind one NAT router) the
channel switches to Extended NAT mode. Please refer to Section 8.3 to learn more about
configuring the Extended NAT mode in the configuration server.
The configuration server sets the SNTP server addresses and the Channel timeout.
The filed Escrow timeout defines how long the CEA-852 device on the L-IP waits for out-
of-sequence CEA-852 data packets before they are discarded. Please enter the time in ms or
‘0’ to disable escrowing. The maximum time is 255 ms.
The field Aggregation timeout defines the time interval in which multiple CEA-709 packets
are combined into a single CEA-852 data packet. Please enter the time in ms or ‘0’ to disable
aggregation. The maximum time is 255 ms. Note that disabling aggregation will negatively
affect the performance of the CEA-852 device of the L-IP.
The field MD5 authentication enables or disables MD5 authentication. In the following field
MD5 secret enter the 16-byte MD5 secret. Note that for security purposes the active MD5
secret is not displayed. You may enter the 16 bytes as one string or with spaces between each
byte, e.g., 00 11 22 33 44 55 66 77 88 99 AA BB CC DD EE FF.
Note: MD5 authentication cannot be used together with the Echelon’s i.LON 1000 since the
i.LON 1000 is not fully compliant with the CEA-852 authentication method. MD5 can be
used with the i.LON 600.
Also note that entering the MD5 secret on the Web interface may pose a security risk. Since
the information is transmitted over the network it can be subject for eavesdroppers on the
line. It is recommended to use a cross-over cable.
In the field Location string the user can enter a descriptive test which identifies the physical
location of the device. A location string can have a maximum length of 255 characters. This
is optional and for informational purposes only.
If the CEA-852 device on the L-IP is used behind a NAT router, the public IP address of the
NAT router or firewall must be known. To automatically detect the NAT address leave the
Auto-NAT checkmark enabled.
The Multicast Address field allows the user to add the CEA-852 device of the L-IP into a
multi-cast group for the CEA-852 IP channel. Enter the channel’s IP multi-cast address here.
Please contact your system administrator on how to obtain a valid multi-cast address. To
learn when it is beneficial to use multi-cast addresses in your channel please refer to Section
8.4.
Choose Configured Router mode if you want to use the L-IP as a standard configured
CEA-709 router that can be commissioned and configured in a network management tool
such as NL-200 or LonMaker.
The Smart Switch mode lets the device act as a self-learning router like the L-Switch. In this
configuration the device’s router doesn’t need to be configured with a network management
tool but is completely transparent in the network. Use this operating mode in a plug&play
networking environment. The switch mode should only be used in LAN networks. In Smart
Switch mode, this page has two more configuration fields: Subnet/node learning and Group
learning.
Per default the router mode is set according to the DIP switches. See Section 8.1 for more
information on the different router modes.
The configuration server port can be changed in the Config server port field. It is
recommended to keep the default port setting of 1629. The field Channel name is
informational only and can consist of up to 15 characters.
The field Channel members displays the current number of members on the IP-852 channel.
The field Channel mode reflects the current channel mode. The L-IP configuration server
automatically determines this mode. Depending on if there are any two devices in the channel
which use the same IP address but different ports (e.g., multiple CEA-852 devices behind
one NAT router). If all IP addresses are unique, the mode is Standard, if some are not unique
the mode is Extended NAT mode. Please refer to Section 8.3.2 to learn more about the
implications of this mode.
Enter NTP timer server address and ports in the fields Primary SNTP and Secondary SNTP.
The L-IP will synchronize to NTP time if primary or primary and secondary NTP servers are
specified. A list of available timeservers can be found at www.ntp.org.
The Channel timeout is an IP-852 channel property and indicates how old a packet can be
before it is discarded. The channel timeout is set in ms. To disable the channel timeout enter
a value of 0. To select the proper value please consult Section 8.5. Setting a channel timeout
other than 0 requires a valid SNTP server entry on the configuration server.
The Auto members option allows members to be automatically added to the channel. If
turned on, CEA-852 devices can register on the IP-852 channel without the device being
explicitly added on the configuration server. This special feature is useful in combination
with the LPA-IP since it can add itself to the configuration server during the debug session.
Non-responding auto members are automatically removed from the channel. This feature is
turned off by default and must be explicitly turned on. Use this option with care because new
CEA-852 devices can add themselves to the channel without knowledge of the system
operator. This could cause a potential security hole.
The Roaming members option allows tracking CEA-852 devices when their IP address
changes. This feature must be turned on if DHCP is used and the DHCP server can assign
different IP addresses to the same device (same Neuron-ID). In combination with Auto-NAT
the device’s router can also be operated behind NAT routers, which change their IP address
between connection setups. For more information on this topic refer to Section 8.3.1. The
roaming member feature is turned on by default. It is recommended to turn off this feature if
DHCP is not used or if the DHCP server always assigns the same IP address to a given MAC
address.
Use the drop-down box MD5 authentication to enable and disable MD5 authentication. If
MD5 authentication is enabled, all devices on the IP-852 channel must have MD5 enabled
and must use the same MD5 secret. The MD5 secret can be entered over the Web interface.
You may enter the 16 bytes as one string or with spaces between each byte, e.g., 00 11
22 33 44 55 66 77 88 99 AA BB CC DD EE FF.
Note: MD5 authentication cannot be used together with the Echelon’s i.LON 1000 since the i.LON
1000 is not fully compliant with the CEA-852 authentication method. MD5 can be used with
the i.LON 600.
It is recommended, however, to enter the secret locally and not over an Internet connection.
It is best to use a cross-over Ethernet cable connected to the PC.
The Add Device button is used to add another CEA-852 device to the IP-852 channel. The
Reload button updates the Web page and the Recontact button contacts all devices to update
their status. The Execute button executes the option selected in the adjacent drop-down box
on the checked members. Each member can be selected for that action in an individual check-
box in the Sel column. Actions available are: disable, enable, delete, assign to NAT, and
remove from NAT. For more information on the actions on NAT routers refer to Section
8.3.2.
The device status information is indicated with descriptive icons of different colors. The
description for the different status indicators is shown in Table 5. The Flags column indicates
with an A that the device is an auto member.
Click on the Edit button to change the device name, IP address, and port number for this
device. Click Edit on a NAT router to change the NAT router address. The Stats button
retrieves the statistics summary page from the client device.
It is possible to enable or disable the SSH server and to change the TCP port of the SSH
server. The default SSH server port is 22. These settings will be active after rebooting.
The SSH configuration page displays the fingerprints of the RSA and DSS host keys. A
random DSS key (fixed to 1024 bits) and RSA key (1024 bits) is generated per default. New
keys can be created by selecting the required RSA key size (1024 or 2048 bits), selecting the
Generate RSA key and/or Generate DSS key check boxes and selecting the Generate
button. The SSH server will load the new keys after rebooting.
Note that recreating the SSH host keys can take up to a minute to complete. SSH clients
which have already accepted the previous host key will refuse to connect to the SSH server
until the host key change is confirmed in the client.
7.3.17 SNMP
The device has a built-in SNMP server. All system registers and OPC-exposed data points
are available as variables in the SNMP management information base (MIB). The MIB
definition can be downloaded from the Web interface as shown in Figure 64. One can choose
between a text and an XML format, depending on the SNMP tool in use. For more
information on SNMP on the device please refer to Section 11.1.
Figure 64: Get the SNMP MIB from the Web interface
Choose Client connect and click on Save Settings to activate VPN client mode. Optionally
select the checkbox Route local subnet to enable the LOYTEC device route VPN traffic to
and from the local IP subnet. This effectively makes devices on the local IP network available
over the VPN, if the IP subnet address is unique on the entire VPN (i.e. each site has its own
unique IP subnet that can be routed).
Under Upload OpenVPN configuration click Choose File button and choose an OpenVPN
(.ovpn) configuration file provided by your OpenVPN server. Then click Upload to transfer
the ovpn file onto the LOYTEC device. Typical OpenVPN servers such as OpenVPN Access
Server or Synology OpenVPN server are supported.
Note: OpenVPN config files must use embedded certificates and be auto-login, i.e., have no
password protection to be entered before connecting to the OpenVPN server.
When connecting to the OpenVPN server the State information is updated. Eventually, it
should display connected state and the assigned IP address in the VPN as shown in Figure
66. To get more detailed information or troubleshoot the connection process, click on the
button Show Log to read out and display the VPN connection log.
On the VPN tab of the port configuration Web UI, certain protocols can be configured to run
on the VPN instead of the local Ethernet. This secures otherwise non-secure protocols such
as CEA-852. For doing so, enable the VPN port in separate network mode. Note, that for
CEA-852 all clients and the configuration server must be configured to run on the VPN
interface.
Select LWEB-900 Registration to register with an LWEB-900 VPN and click Save
Settings. Instead of uploading a configuration file, enter the LWEB-900 VPN Project PIN
Code and optionally the Device PIN Code. The click Start to discover the LWEB-900 VPN
and register the device in it.
Select Simple Server mode to enable the OpenVPN server on the LOYTEC device. Enter
the IP address/hostname and port over which the LOYTEC device is externally reachable
(see Figure 67). The port is shared with the HTTPS port of the device. Then click Save
Settings and reboot the device to start the VPN server. Note, that it may be required to
configure a port forwarding of HTTPS on the NAT router to reach the LOYTEC device.
After the reboot has finished, the OpenVPN server on the device is active. Download the
client configuration by clicking the button Get Client Config. Import this configuration file
into an OpenVPN client (e.g. OpenVPN app on the mobile device or OpenVPN GUI on the
PC). The VPN simple server Web interface displays information on Connected clients.
Currently, only one client is allowed to connect at a time.
This enables the LTE interface and jumps to the Mobile network settings section as shown
in Figure 69. Depending on the information provided by your mobile carrier, enter the APN
information under Access Point Name and additionally Username and Password if required
by your carrier. Then enter the PIN Code of the SIM card. If the PIN function is disabled on
the SIM card leave this field blank. Activate Roaming if your carrier requires roaming on
the home network. Then click Save Settings. Whether the SIM lock has been successfully
removed is indicated by the status text next to the PIN Code field.
The LTE interface now attempts to establish a data connection to its home network. The
status information of the LTE interface is displayed in the bottom part of the Mobile
Network section. The field Data Connection will eventually display “Connected”. Other
information on signal quality and carrier information is also displayed. For information on
consumed data volume refer to the mobile network statistics (Section 7.2.6).
For test purposes, the Reconnect button can be used to reset and reconnect the LTE data
connection. With the Restart modem button you can completely restart the LTE modem.
These actions are not required during normal operation.
If a different carrier than the home network shall be used, deactivate the checkbox Auto
Network Selection and click on the Search button to find other mobile networks. The
Search Results list is filled with the found networks as shown in Figure 70.
⌂ Home network
Select the desired network and save settings. The modem will connect using the new mobile
network.
7.4 Security
7.4.1 Change Passwords
The admin and operator passwords have been configured when contacting the device for the
first time. Passwords for locally created users have been set when creating the user. To
change the password of the logged-in user, click on Passwords in the Security menu, which
opens the password configuration page as shown in Figure 71.
If logged in as the ‘admin’ user, it is allowed to change also ‘operator’ and ‘guest’ passwords.
To change the admin password, select the admin account in the drop-down box. Enter the
new password. The password strength indicator will inform you about the security quality of
your password. If the password is left empty, password protection is turned off and everyone
can access the device without entering a password. Click on Change password to activate
the change.
If logged in as ‘admin’, click Clear all passwords to clear all administrative passwords on
the device. After clearing the passwords, new admin and operator passwords have to be set
before proceeding on the Web UI. Passwords of locally created users are not cleared.
The HTTPS server settings can be configured in the Ethernet Port Configuration page. It is
possible to enable or disable the HTTPS server and to change the TCP port of the HTTPS
server. The default HTTPS server port is 443. These settings will be active after rebooting.
When connecting with a web browser to the LOYTEC device you will be warned that the
server uses a self-signed certificate. You need to accept the certificate in order to continue.
In some browsers this is also called “adding an exception”.
Note that in default configuration, communication is encrypted, but not safely authenticated,
as the default certificate is self-signed and uses a default common name “loytec.local”. If you
operate in a safe environment and your client accepts this, no further action has to be taken.
Some OPC UA clients, however, will not validate the LOYTEC server with the default
certificate. In this case the common name of the self-signed certificate needs to excplicitly
state the IP address or host name used for the client connection.
1. Go to the Certificates configuration page and select the Create Certificate tab. The
radio button Self-Signed is selected and all necessary data is pre-filled as shown in
Figure 72. Note, that Common Name contains the IP address over which the device has
been contacted.
2. Optionally modify any of the fields to your choice and then click Create Certificate.
Certificate creation may take up to a few minutes. When finished, the new self-signed
certificate is shown (see Figure 73 below). Reboot the device to activate the change.
To widen acceptance of the LOYTEC server in a hostile environment (e.g. when using over
the Internet), consider installing a server certificate signed by a certification authority to
prevent man-in-the-middle attacks. HTTPS and OPC UA servers use X.509 certificates to
authenticate themselves to clients. In order to establish communication, the client has to trust
the server certificate. There are two options to accept a server certificate:
LOYTEC devices are configured with a self-signed certificate, but custom server certificates
can be imported in the configuration page. Please follow these steps to install a custom
certificate signed by a CA.
1. Go to the Certificates configuration page and select the Create Certificate tab. Choose
the radio button CA Request as shown in Figure 74. In Common Name provide a valid
DNS host name (e.g., linx-g01.acme.com) or the IP address for the device. SSL
certificates use host names. Enter organization name, organization unit, city, and state.
Then choose the country and click Create Certificate Request.
2. Copy the X.509 certificate request from the Web page as shown in Figure 75 and follow
up with the instructions provided by the certification authority.
Figure 75: Copy and paste for the X.509 certificate request.
3. Order the certificate. The LOYTEC device requires the certificate to be encoded in PEM
format in order to be pasted easily.
4. After receiving the certificate, copy it to the clipboard or a text file. It should look like
this:
-----BEGIN CERTIFICATE-----
MIICyjCCAjOgAwIQEBBQUAMH4xCzAJBgNV…
… more data follows …
-----END CERTIFICATE-----
5. On the tab Create Certificate paste the information to the Certificate Request Reply
text area as shown in Figure 75 and click Verify & Install.
6. After next reboot, the server uses the imported certificate, so that the web browsers will
indicate the page as trustworthy.
7. Note that certificates have a lifelime, typically 1 or 2 years. You need to repeat these
steps to renew your certificates before they expire.
Optionally, a certificate can also be installed from a file. Go to the Import Certificate tab as
shown in Figure 76 Select the certificate in the Server certificate field and its private key in
the Server private key field. Both can be in PEM or DER (*.der/*.cer) format.
Important! You cannot install a Server certificate without its private key!
It is also possible to create other users locally on the device. These users can be assigned to
different roles. The ‘admin’ and ‘operator’ roles have the same administrative rigths as their
pre-defined counterparts, except of creating/deleting local users. It is good practice to create
separate users with the ‘admin’ role in order to keep the master administrator password a
secret. Locally created users can be disabled or deleted at any time, therefore removing the
administrative rights for any of them when needed.
The ‘lweb’ role can be assigned to users that are solely meant to login over the LWEB-
802/803 clients and operate within the L-WEB visualization project. These users have no
other administrative rigths on the device.
To manage local users go to the User Management page of the Security menu. This page
displays the list of local users (see Figure 77). Managing local users is only allowed when
logged in using the ‘admin’ user account.
Click on Add User to add a new user and edit the username, password and role from the
drop-down box. Then click the save icon. To edit the password or role of a local user, click
the respective edit icon, update the content and click on the save icon.
Other actions on local users include enable, disable, and delete. Select the checkbox on the
right-hand side for one or more users and choose an action from the Action on selected drop-
down. Then click on Execute. Disabled users cannot log in anymore but their credentials
remain on the device and can be enabled again.
7.5 Documentation
The documentation page allows to access documentation related to the device. See Section
7.6.3 on how to configure documentation links and upload documentation files accessible via
this page.
Note: The Documentation page and all files available on it are accessible for all users (incl. Guest).
7.6 Maintenance
7.6.1 Backup and Restore
A configuration backup of the device can be downloaded via the Web interface. Press the
backup link as shown in Figure 79 to start the download. The device assembles a single file
including all required files. A file requestor dialog allows specifying the location where the
backup file shall be stored.
Some contents of the backup archive can be controlled by the option check boxes. By default
passwords and IP settings are included. When clearing the check box from passwords or IP
settings, the respective items are excluded from the backup archive. To restore the device
settings, simply select a previously generated backup file in the Restore Configuration
section of the page by clicking the button next to the Filename field. Then press the Restore
button. By leaving the restore check boxes unset, the respective information is excluded from
restore operation.
Note: Backups created with firmware versions prior to version 6.0 cannot be restored on firmware
versions 6.0 and up! Please make sure you re-create backups when upgrading the firmware!
7.6.2 Firmware
The firmware page allows upgrading the device’s firmware over the Web interface. It offers
two options:
Web Update: With Web update the device searches for the latest available firmware on
the LOYTEC server. Click on the refresh symbol, if no latest version is displayed. Please
note, that the device must have a DNS server configured to find the LOYTEC server.
Click on the Install button to upgrade your device.
Local file: Update the device from a local disk file. For doing so, choose a .dl file on
you hard drive and then click on the Start Update button.
In both cases a device backup will be created and stored in the local download folder of the
Web browser before the firmware upgrade starts. If no backup shall be created, deselect the
checkbox Automatically download a backup.
7.6.3 Documentation
The Documentation page in the Maintenance menu allows uploading documentation files
or configuring links to external documentation (e.g. Wiring plans, etc.). The documentation
configured on this page is accessible via the Documentation menu (see Section 7.5).
To upload a documentation file click on the Choose File button. This opens a file dialog.
Chose the file to upload. Click on the Upload button to start the upload of the selected file.
After the upload is completed the file appears in the Documentation files section. Enter a
link text used to display the uploaded file on the Documentation page.
To add a documentation link, click on the symbol in the header row of the Documentation
links section. Enter the URL and the text used to display the link on the Documentation
page.
Links and files can be set active and inactive on the Documentation page by checking the
Enabled check box. Inactive entries are not displayed on the Documentation page. The
check box New window determines if the link or file is opened in a new browser tab. If Show
in browser is checked the browser will try to render the file in the browser, otherwise it will
try to download the file. To remove a link or file click on the symbol on the right side of
the row. To commit your changes click on the Save button.
Rebooting the device from a remote location. Use Cold Reboot to reboot the device like
after a power loss, while the regular Reboot Device is faster and restarts the application
only.
When resetting into safe reboot mode, the user needs to log in within the next 5 minutes after
the reboot. A list of possible new IP addresses to this device is displayed to help navigating
to the device. If no login is detected (e.g., because the new IP setting breaks connectivity) the
device will revert to the last working settings.
8 Operating Modes
The L-IP routes CEA-709 packets over IP (Internet/Intranet) networks. Depending on the use
case the L-IP supports different operating modes how packets are routed between the
CEA-709 side and the IP side. The L-IP can be used as a client device on the IP channel, as
a configuration server on the IP channel, or as a client device and configuration server at the
same time.
OFF-OFF: The L-IP acts like a standard CEA-709 configured router (i.LON 1000/600
alike)
ON-ON: The L-IP acts as a self-learning plug&play router (“smart switch mode”)
OFF-ON: The L-IP learns the network topology but doesn’t flood subnet broadcasts
Figure 83 shows the proper DIP-switch settings for configured router mode, assuming all
other DIP-switches remain in the factory default position. This DIP-switch setting is the
factory default setting. The series “C” L-IP models do not have DIP switches.
off
on
1234567
Figure 83: OFF-OFF: DIP-switch settings for configured router mode (factory default).
This operating mode uses the “channel routing” routing strategy on the IP channel. In this
mode the device is fully compatible with i.LON 1000/600 devices. This operating mode
should also be used in networks with more than 10 IP devices on one IP channel and heavy
network traffic on the IP channel (more than 500 packets/s) since channel routing sends the
IP packet only to the IP-852 device(s) that connect to the CEA-709 node(s) addressed in this
IP packet and not to all IP-852 devices on the IP channel. This is the standard operating mode.
Figure 84 shows the proper DIP-switch setting to put the L-IP into smart switch mode. The
series “C” L-IP models do not have DIP switches.
off
on
1234567
Note: All messages, which are received on an unknown domain, are forwarded to all ports!
Note: All messages with a destination subnet/node address not yet learned are forwarded!
The router supports group learning. Groups can span multiple router ports.
Note: Group learning only works for messages using acknowledged or request/response service.
Note: All messages with a destination group address not yet learned are forwarded!
The router has no learning strategy for broadcast addresses. As a result, all subnet or domain
wide broadcasts are always forwarded. If subnet wide broadcasts shall not be forwarded,
please use the smart switch operating mode without subnet broadcast forwarding (see Section
8.1.4).
The router has no learning strategy for unique node ID addresses. Node ID addressed
messages are always forwarded.
This operating mode uses the “channel routing” strategy on the IP channel to distribute IP
packets. It uses flooding to send all packets on the IP channel to all IP devices on this IP
channel. The advantage of this operating mode is that it is fully plug&play and no router
configuration is required. The disadvantage is that this operating mode doesn’t scale very
well with larger networks. We do not recommend this operating mode for IP channels with
more than 10 IP-852 devices and packet rates of more than 500 packets/s. Please use the
configured router mode from Section 8.1.1 for larger IP channel configurations.
Further, it is recommended to configure a multi-cast group for routers in the smart switch
mode to reduce the traffic burden and improve scalability. Refer to Section 8.4 on how to
configure the device to use multi-cast.
DIP-switch number 1 must be on, refer to the installation sheet of the product.
DIP-switch number 2 must be off, refer to the installation sheet of the product.
The forwarding tables must be reset by pressing the status button for at least 20 seconds
(see Section 6.5.1).
Figure 85 shows the proper DIP-switch settings for repeater mode, assuming all other DIP
switches remain in the factory default position. The series “C” L-IP models do not have DIP
switches.
off
on
1234567
This operating mode uses the “channel routing” strategy on the IP channel to distribute IP
packets. It uses flooding to send all packets on the IP channel to all IP devices on this IP
channel. The advantage of this operating mode is that it is fully plug&play and no router
configuration is required. The disadvantage is that this operating mode doesn’t scale very
well with larger networks. We do not recommend this operating mode for IP channels with
more than 10 L-IP devices and packet rates of more than 500 packets/s.
Figure 86 shows the proper DIP switch settings for smart switch mode without subnet
broadcast flooding, assuming all other DIP switches remain in the factory default position.
The series “C” L-IP models do not have DIP switches.
off
on
1234567
Figure 86: OFF-ON: DIP-switch settings for smart switch mode without subnet broadcast flooding.
This operating mode uses the “channel routing” strategy on the IP channel to distribute IP
packets. It uses flooding to send all packets on the IP channel to all IP devices on this IP
channel. The advantage of this operating mode is that it is fully plug&play and no router
configuration is required. The disadvantage is that this operating mode doesn’t scale very
well with larger networks. We do not recommend this operating mode for IP channels with
more than 10 L-IP devices and packet rates of more than 500 packets/s.
Further, it is recommended to configure a multi-cast group for the router in the smart switch
mode to reduce the traffic burden and improve scalability. Refer to Section 8.4 on how to
configure the device to use multi-cast.
A configuration server keeps a list of all devices on a logical IP-852 channel and distributes
the routing information between those devices. If a device wants to join an IP-852 channel,
it needs to register itself at the configuration server. Traditionally, a dedicated Windows PC
is used to act as the configuration server. The L-IP contains an embedded configuration server
and can therefore replace the PC.
Figure 87: IP channel that consists of two IP devices. The left L-IP with IP address 135.23.2.51 acts
as router and as a configuration server for this IP channel. It manages both IP devices 135.23.2.51 and
135.23.2.52.
Please consult Sections 7.3.3 and 7.3.12 on how to setup a CEA-852 device.
The L-IP can be used together with the PC based i.LON Configuration Server utility or with
the built-in configuration server. The built-in configuration server can be enabled in the
CEA-852 server configuration menu in Section 7.3.14. This configuration server can manage
one IP-852 channel and up to 256 devices on this IP-852 channel. In order to setup the
configuration server, one must specify the following parameters:
IP address/netmask/gateway (either via DHCP or manual entry), see Section 7.6.1
NAT address if used behind a firewall/NAT router, see Section 7.3.12
MD5 secret if authentication is required, see Section 7.3.12
Enable the configuration server, see Section 7.3.14 (server LED lights up green)
A list of IP-852 channel members, see Section 7.3.15.
Note: If the L-IP is also used as a configuration server it needs a fixed IP address.
There are two different scenarios how a device can join an IP-852 channel. Either the device
has a valid IP address of a configuration server stored and contacts the configuration server
direct or the configuration server has a list of the IP addresses of the devices and the
configuration server contacts the device.
Figure 88: The configuration server manages the devices on an IP-852 channel.
If multiple CEA-852 devices behind one NAT router are added, the Auto-NAT setting in the
L-IP is recommended to be used with the CEA-852 configuration server.
If the “Auto member” feature is enabled in the configuration server, the CEA-852 device can
add itself to the IP-852 channel without explicitly adding the device at the configuration
server. Note, that enabling auto member is a potential security hole since any device can add
itself to the IP-852 channel.
Configuration Server menu (see Section 7.3.15). This ensures that no unwanted device can
join the IP-852 channel.
Note that also i.LON 1000/600, VNI and LOYTEC NIC852 based network nodes (e.g.,
LonMaker or NL-220 applications) can join the IP-852 channel managed by the configuration
server. Note that the built-in configuration server should be used if LOYTEC CEA-852
devices are communicating across firewalls/NAT routers.
For adding multiple devices behind a NAT router, the configuration server supports the
extended NAT mode (see Section 8.3.2). The configuration server automatically switches the
channel mode to extended NAT if needed. Note that the i.LON 600 must be configured with
the i.LON CS to extended NAT mode before adding the i.LON 600 to the configuration
server, because the i.LON 600 does not switch to that mode automatically.
The i.LON configuration server utility version 2.00.24 and up also supports the extended
NAT mode (see Section 8.3.2) to add more than one device behind a NAT router. The L-IP
can be used with the i.LON configuration server in this mode. Note, that the i.LON
configuration server channel mode needs to be manually switched to “Extended NAT” mode.
Note: If the L-IP is used behind a NAT router with the i.LON configuration server, the Auto-NAT
feature must be disabled and the correct NAT address must be entered manually.
LOYTEC’s newer devices such as the L-IP and the L-INX family support more than one
CEA-852 channel member behind a NAT router. This mode of operation is referred to as
“Extended NAT” channel mode. This mode introduces extensions to the standard mode
which need to be supported by all members. Other devices supporting the extended NAT
mode are the i.LON 600. See Section 8.2.2.3 on compatibility with the i.LON 600.
Specify the NAT address (public IP address: 135.23.2.1) or use automatic NAT router
discovery,
Enable port forwarding for ports 1628 and 1629 in the NAT router for TCP and UDP,
Note that an L-IP must be used as configuration server when the device is installed behind a
firewall or NAT router. The L-IP with the configuration server can also be located behind a
firewall.
When using multiple devices behind a NAT router, each device needs a separate port-
forwarding rule in the NAT router. This implies that each device must use a unique client
port (e.g., 1628, 1630, 1631, etc). The port-forwarding rules must be setup so that each port
points to one of the IP-852 devices. In the L-IP, change the client port in the CEA-852 device
configuration menu. Figure 90 shows an example configuration for three L-IP devices behind
the NAT router 135.23.2.1.
It is recommended that both ports 1628 and 1629 are forwarded to the same private address.
It is then also possible to turn on the configuration server behind a NAT router. In this case,
activate the CS on the L-IP which has port-forwarding to 1628 and 1629. In the example in
Figure 90, the L-IP with private address 192.168.1.100 also acts as a configuration server.
If the CS is activated on a L-IP behind a NAT router, the NAT router must have a fixed public
IP address. The L-IP with the CS also cannot use automatic NAT discovery. In this case,
enter the NAT address of the NAT router manually in the IP configuration menu (Auto-NAT
can no longer be enabled on a L-INX with a CS). To diagnose possible problems in the NAT
configuration with port forwarding, use the enhanced communications test (see Section
7.2.4).
After the NAT router has been configured with the port-forwardings and the CS has been
turned on, the channel members can be added. This can be done either on the console UI or
through the Web interface of the CS.
In the Web UI, add the members with their private IP addresses and the client ports as defined
by the port-forwarding. Then select the added member by checking the check box and select
the action Assign to NAT. Enter the public NAT address of the NAT router. An example to
add the two IP-852 devices in Figure 90 through the Web UI is depicted in Figure 91. To
remove a device from a NAT router but not delete it, select it and choose Remove from NAT
as the action.
Figure 91: Adding a member with extended NAT Mode on the Web UI.
Figure 92: Application that uses multiple L-IP devices behind a NAT router firewall.
The L-IP with IP address 192.168.1.100 is member of IP Channel 1 and can be accessed
through the Internet. The L-IP devices with IP addresses 192.168.101 to 192.168.1.110 form
another logical IP Channel 2 that communicates with the devices on the IP Channel 1 over
the TP-1250 channel, which is used in high-speed backbone mode for optimum networking
performance. Note that devices on both IP Channels 1 and 2 can of course connect to the
same physical network wiring. Furthermore both IP Channels 1 and 2 must have a separate
configuration server that manages the L-IP devices on the different channels. In the example
in Figure 92 the L-IP with address 192.168.1.100 acts as the configuration server for IP
Channel 1 and the L-IP with IP address 192.168.1.101 acts as the configuration server for IP
Channel 2.
The L-IP supports both unicast and multi-cast delivery of CNIP data packets. Using multi-
cast is recommended when using L-IPs in the Smart Switch Mode. For those L-IPs configure
a multi-cast address in the IP configuration menu. Please contact your system administrator
to obtain a valid multi-cast address for your network. All L-IPs must be configured with the
same multi-cast address and use the same client port (1628 is recommended). Also note, that
multi-cast addresses cannot be routed on the Internet. They can only be used in a LAN or
VPN environment.
If you configure multi-cast there may be some devices, which do not support this feature. In
this case, the L-IP uses a hybrid scheme and sends unicast to those devices, which are not
configured for multi-cast. Note, that the L-IP determines automatically, when to switch to
the multi-cast mode depending what types of devices are in the channel and on the traffic
burden for those devices. As a rule of thumb multi-cast is used when there are only
switches/repeaters in the channel and it is not used when there are only configured routers.
To detect, if the L-IP utilizes the multi-cast feature to send to other devices, contact the
Extended CEA-852 device statistics in the statistics menu (Section 7.2). The entry “Channel
Routing Mode” reads SL (send list) if packets are routed to the multi-cast group. It reads CR
(channel routing) if the normal unicast method is employed. Also the entry “Multi-cast
packets sent” in the CEA-852 device statistics menu (Section 7.2) counts the number of
multicast packets transmitted to the group. If this item remains zero, no multi-cast is used by
the L-IP.
Table 6 summarizes the timing values that must be set when operating the device under WAN
conditions.
Please use a PC to determine the average ping delay between the different CEA-852 devices
in the network. If multiple devices are communicating with each other always use the largest
measured average ping delay for the input value for the calculations in Table 6.
Escrowing should be disabled in a LAN (0 ms). The Channel Delay in LonMaker should be
set to 2*Aggregation Timeout in a LAN if MD5 is disabled.
In LANs, Channel Timeout is only required if MD5 authentication is enabled. Set Channel
Timeout to 200 ms and Channel Delay to 20 ms.
If an LNS based network management tool like LonMaker or NL220 is used on a network
that has channel timeout enabled, please install an NTP client program (e.g., achron4.exe) on
this PC that synchronizes the PC clock to the NTP time. Otherwise the PC clock and the
clock inside the CEA-852 device will drift apart and communication between the PC and the
device will terminate.
Do not use the Escrowing Timer in LANs since the packet order is always guaranteed in a
LAN. This will add unnecessary delays, which negatively impacts the performance of your
CEA-852 devices if a packet is lost or destroyed.
If enabled or disabled, out-of-sequence packets are never sent to the CEA-709 channel.
Please refer to Section 7.3.12 on how to enable or disable escrowing.
In larger IP-852 networks like the Internet with possibly long packet delays, one must specify
an SNTP server to synchronize the local clocks of the CEA-852 devices. The local clocks
must be synchronized to a common notion of time in order to make CEA-852 protocol
features like Escrowing and Channel Timeout work properly.
The SNTP timeserver can be specified on the IP-852 channel level in the configuration
server, which distributes the timeserver address to all CEA-852 devices on the IP-852
channel. A primary and a secondary SNTP server can be defined please refer to Section
7.3.12 and Section 7.3.14 on how to enable the SNTP server.
8.6.3 DHCP
When using DHCP the configuration server must always get the same IP address assigned.
Client devices can get different IP addresses assigned as long as the “Roaming Member”
function is activated on the configuration server. Do not use DHCP with dynamic IP
addresses in applications with NAT routers.
A consequence of this monitoring process is that the device contacts the CS every 45 seconds
to probe for the NAT address. This causes a small amount of additional traffic on the Internet
link. The Auto-NAT feature also causes any shut-down connection to be re-established. The
NAT monitoring functions as a keep-alive for the connection. If neither the additional traffic
nor the automatic initiation of a new connection is tolerable, the Auto-NAT feature must be
disabled and the NAT address configured manually. In this case, the Internet service provider
needs to assign a fixed public IP address to the NAT router.
The L-IP is based on LOYTEC’s powerful L-Core and L-Chip technology. It is designed
to be very robust and reliable in real-life applications. The L-IP either behaves completely
transparent in a network or can be configured to behave like a configured CEA-709 router.
Before the L-IP can start routing CEA-709 packets over IP channels, the L-IP must be added
to an IP-852 channel. Please refer to Section 8.2.2 on how to add the L-IP to an IP-852
channel.
After adding the device to an IP-852 channel, a network management tool like LonMaker or
NL-220 must be used to add and commission the L-IP as a configured router. We provide
LonMaker shapes for the different operating modes of the L-IP. You can download those
shapes from our website at http://www.loytec.com.
The multi-port L-IP contains multiple standard CEA-709 routers, one for each port, and an
internal TP-1250 backbone. The internal TP-1250 is neither visible nor accessible from the
outside and its sole task is to connect the individual routers. Figure 93 shows an example for
the multi-port L-IP (LIP-33ECTB).
Router
Router
Router
FT-10
FT-10
Ethernet
Figure 93: Internal structure of the multi-port L-IP in configured CEA-709 router mode.
Each router must be commissioned separately, reflecting the structure of the internal TP-1250
channel. The port LEDs of unconfigured routers are flashing green with a frequency of 1 Hz
(once per second).
Pressing the status button longer than 2 seconds will allow you to cycle through the ports and
select the port, which shall send out the “Service Pin Message” message: The port LED of
the currently selected port will light up orange. After 2 seconds the next available port will
be selected. When the status button is released the “Service Pin Message” is sent out on the
currently selected port/router.
If an LNS-based installation tool (e.g. LonMaker) is used, the individual routers of the L-IP
must be commissioned separately. Refer to application note AN003E “Using the L-IP with
LNS-based Installation Tools” for more details.
When using a standard binding tool (e.g. LonMaker), bindings between nodes connected to
different ports can be done without considering the L-IP. Further, an L-IP can be added
anywhere to an already configured network without reconfiguring the nodes in the network.
Due to the plug and play installation capability of the L-IP, it does not support any CEA-709
Router network management commands. However, it accepts all other standard network
management commands (e.g. to set the channel parameters on every port).
Detailed instructions on how to use the L-IP together with LNS based network management
tools can be found in Section 15.
9.4 Using the L-IP as the Network Interface for LNS Applications
The L-IP can be used as a local or remote network interface for LNS based applications like
LonMaker to access CEA-709 networks. Therefore the CEA-852 network interface must be
enabled on the PC where the LNS application program is installed and the IP address of the
PC must be added to the configuration server:
1. Add the IP address of the PC to the configuration server’s list of devices (see Section
7.3.15).
2. Select the LonWorks Interfaces utility program from your Control Panel and select
the IP-852 tab.
3. Click on Add.
4. And specify a name for the interface in the Name field. The IP Address field shows
the IP address of your PC. Leave the IP port at 1628. Leave the MD5 authentication
key field empty. Click OK.
Figure 97: Disable the SNTP client if you have a local NTP client installed on your PC.
5. Click on Properties in the SNTP Client section. Do not enable the SNTP Client if
the network interface is used in a local network like an Intranet. If the network
interface is also accessed over a large network like the Internet one should specify
an address for a Time Server and enable the SNTP Client. If you already have an
NTP client installed on your PC, which synchronizes your PC clock to an NTP timer
server, you must not enable the SNTP Client otherwise it will compete with the NTP
client already installed on your PC.
6. You can now start the LNS application and select the “L-IP Interface” as your
interface to the CEA-709 network.
nviSwitchFb1 nvoSwitch1
Func Block 1
Node 1
Channel 1
IP Channel (Local)
LNS Network Interface
Figure 98: Move the LNS Network Interface to the newly created IP Channel.
7. If the L-IP is used as a CEA-709 configured router one should add the L-IP in the
LonMaker drawing. Create a new Channel with channel type IP-10L in an Intranet
or IP-10W in an Internet environment. Move the LNS Network Interface to this
newly created IP channel as shown in Figure 98 by selecting the LNS Network
Interface and choosing “Change Channel” from the context menu.
Figure 99: Drag the L-IP (Router) shape onto the drawing area and commission the device.
8. Now drag the L-IP (Router) shape from the “LoytecShapes” stencil onto the drawing
area. Choose the existing channel “IP Channel” for the first router port and the
existing channel “Channel 1” for the second port. Finally you must commission the
new L-IP router. LonMaker can now use the L-IP as a local or remote network
interface that connects directly to the Ethernet network as shown in Figure 99.
The LPA-IP runs on a Windows PC that is connected to the Ethernet network. In a device
selection window, one can e.g. select the L-IP with IP address 192.168.1.210 and display all
packets on the FT-10 channel connected to the L-IP with IP address 192.168.1.210. For this
operation, the LPA-IP does not need to be a member of the IP-852 channel. Note that this
functionality is only available with LOYTEC CEA-852 devices.
10 L-IP Redundant
1. Broken connection on the backbone: The router is not connected to the backbone
anymore. Therefore the nodes are unable to communicate with nodes in other segments
or the building management system (A).
2. Router device failure: The router device fails due to power failure or device failure.
Again the nodes are unable to communicate with nodes in other segments or the building
management system across the router (A,B).
Broken connection to
backbone (1)
Node device
failure (4)
3. Broken cable in the segment: The nodes cannot communicate across the point of
fracture. Thus, nodes behind the point of fracture cannot communicate with nodes before
the point of fracture (C) and with the router (B) and therefore with nodes in other
segments (A).
4. Node device failure: A node fails due to power failure or device failure. As a result the
node cannot perform its function anymore and cannot be reached by its communication
partners (A,B,C).
IP Backbone
FT Ring
Broken cable
Now the L-IP Redundant is able to detect a cable fracture by permanently comparing the
traffic on both sides of the bus: If the L-IP Redundant sees different traffic on its two
terminals, the cable is deemed to be broken. In this case it starts to duplicate the traffic from
2
Assuming a redundant backbone.
loop port 1 to loop port 2 and vice versa. Further an alarm is issued (see Sections 10.5.5 and
10.6.3). Once messages are received on both sides again the ring is considered closed and the
cable fracture is deemed gone.
The L-IP Redundant is shipped with bus loop monitoring enabled. If bus loop monitoring is
not desired it must be switched off to avoid a permanent “Ring open” alarm. Bus loop
monitoring parameters can be configured using the L-IP Redundant plug-in (see Section
10.5.7) or the web interface (see Section 10.6.5).
The current bus loop monitoring state can be determined via network variables (see Section
10.7), in the L-IP Redundant plug-in (see Section 10.5.3), and in the web interface (see
Section 10.6.1).
Important: To guarantee proper function of the bus loop monitoring algorithm it is required to keep
average bandwidth utilization on the monitored segment below 50%! Bandwidth utilization
can be monitored using the LOYTEC LPA or the built in diagnostic functions (see Sections
10.5.4 and 10.6.1).
IP Backbone
Broken IP cable
IP Infrastructure Failure
Device failure
Power failure
FT Ring
Broken cable
Figure 103: Router Redundancy with two paired L-IP Redundant routers
During power-up the two L-IP Redundant routers automatically negotiate, which one
becomes the active router (primary router) and which one the inactive standby router
(secondary router)3. The active router forwards packets, performs bus loop monitoring, and
has node monitoring enabled, while the inactive devices has all these functions disabled.
After this initial startup-phase the devices periodically monitor each other on the CEA-709
and on the CEA-852 (IP) side. If the secondary router no longer reaches the primary router
on either side it becomes active and issues an alarm, if the primary router no longer reaches
the secondary router just an alarm is issued.
Further, the secondary device, even though it is inactive and does not forward packets, it
counts the number it would forward based on the packets it receives and on its routing tables.
Now the two devices periodically compare these numbers and if these numbers significantly
differ over multiple monitoring intervals an alarm is issued. This algorithm ensures that the
routing tables of both devices are consistent and the secondary router is correctly configured
and able to take over if the primary device fails. Further, if the primary device does not
forward any packets in one direction, while the secondary would forward packets the
secondary devices takes over and the primary device becomes inactive.
Router redundancy can be used with or without bus loop monitoring enabled (see Section
10.2.1).
To enable router redundancy both routers must be commissioned and added to the same
IP-852 channel. Further, the two routers must be linked by binding certain network variables,
which are used for communication between the two paired L-IP Redundant routers. Please
see Section 10.4.3.2 on how to configure the L-IP Redundant for router redundancy.
Redundant router monitoring parameters can be configured using the L-IP Redundant plug-
in (see Section 10.5.7) or the web interface (see Section 10.6.5).
The current router state can be determined via network variables (see Section 10.7), in the
L-IP Redundant plug-in (see Section 10.5.3), and in the web interface (see Section 10.6.1).
Secondly the L-IP Redundant can be used to monitor other nodes in the network. For this
purpose a list of nodes can be entered using the L-IP Redundant plug-in (see Section 10.5.6)
or the web interface (see Section 10.6.4). If node monitoring is enabled, the L-IP Redundant
periodically pings the nodes in this list using a Query Status network diagnostic request. If a
node is not reachable or (soft) offline an alarm is issued. Further, the state of each node can
be determined via a network variable (see Section 10.7), in the L-IP Redundant plug-in (see
Section 10.5.3), and in the web interface (see Section 10.6.1). In addition the web interface
shows detailed statistic information for each node (e.g. number of CRC errors).
If bus loop monitoring is enabled (see Section 10.2.1) the L-IP Redundant also determines
from which loop port each node is reachable (both ports, loop port 1 only, or loop port 2
only). Thus, if the nodes were entered in the order they are connected to the bus this allows
the L-IP Redundant to determine the exact location of a cable fracture by finding the last
node reachable from port 1 and the last one reaching from port 2. This information is also
provided to the user via network variables, in the L-IP Redundant plug-in, and in the web
interface.
3
The primary router is the device with the higher VID1.
Diagnostic
Router
Ethernet
FT-10
FT-10
The router in the L-IP Redundant can only be used as Configured Router and thus requires
to be commissioned with a network management tool (e.g. LonMaker) like any other router.
Smart Switch Mode, Repeater Mode and Bridge Mode are not supported.
Since the diagnostic node resides on the CEA-709 side of the router, the router must be
commissioned before the diagnostic node. To configure the diagnostic node with an LNS
based network management tool, LOYTEC provides the “L-IP Redundant Plug-In” (see
Section 10.5).
10.4 Installation
10.4.1 Installing the L-IP Redundant Plug-In
The L-IP Redundant Plug-In is used to configure the L-IP Redundant node monitoring (see
Section 10.2.3), configure the various parameters influencing the behavior of the L-IP
Redundant, download the L-IP Redundant Alarm Log, and view the current state of the L-IP
Redundant. This configuration utility is installed as a plug-in tool for all LNS based network
management tools.
System requirements:
The L-IP Redundant Plug-In can be downloaded from the LOYTEC website
http://www.loytec.com. To install the configuration utility double click on Setup and follow
the installation steps.
Open LonMaker and create a new network. When the “Plug-in Registration” dialog window
pops up select the L-IP Redundant Configuration Plug-In from the list of “Not Registered
Plug-Ins” (see Figure 110). Click “Add” and “Finish” to register the plug-in. Device
templates for the L-IP Redundant diagnostic node are added automatically and XIF files are
copied into the LNS import directory.
Note: If you are using multiple databases (projects) make sure you have registered the plug-in in
each project.
Under LonMaker => Network Properties => Plug-In Registration make sure that the L-IP
Redundant Configuration Plug-In shows up under “Already Registered”.
Figure 111: Double check that the L-IP Redundant Configuration Plug-In is properly registered
Add a single router shape. Connect it to an IP-Channel on one side and to a FT-10
Channel on the other side of the router.
Add one L-IP Redundant built-in diagnostic node “L-IP Redundant Diagnostic FT-10”
device shapes on the FT-10 channel. The corresponding device template will be installed
with the L-IP Redundant Plug-In (see Section 10.4.1).
To get a service pin message for commissioning the diagnostic node, press the Status
button on the L-IP Redundant (see Section 6.5) or use the Send Service Pin Msg button
in the corresponding section of the Device Information Page in the Web interface (see
Section 7.1).
If using LonMaker for Windows the resulting drawing should look like shown in Figure 112.
Figure 112: A single L-IP Redundant device configured for standalone operation.
Be sure to commission the router and the diagnostic node. Once they were successfully
commissioned, the PRIM LED on the device should be green.
Add two router shapes. Connect both to the same IP-Channel on one side and to the same
FT-10 Channel on the other side of the router.
Add two L-IP Redundant built-in diagnostic node “L-IP Redundant Diagnostic FT-10”
device shapes on the FT-10 channel. The corresponding device template will be installed
with the L-IP Redundant Plug-In (see Section 10.4.1).
To get a service pin message for commissioning the diagnostic node, press the Status
button on the L-IP Redundant (see Section 6.5) or use the Send Service Pin Msg button
in the corresponding section of the Device Information Page in the Web interface (see
Section 7.1).
Add two “Twin Router” functional blocks, one for each L-IP Redundant diagnostic node.
Connect nvoRedRtr of one L-IP Redundant with the nviRedRtr of its paired L-IP
Redundant and vice versa.
If using LonMaker for Windows the resulting drawing should look like shown in Figure 113.
Figure 113: A pair of L-IP Redundant devices configured for twin router operation.
Be sure to commission both routers and both diagnostic nodes. Once both routers and both
diagnostic nodes were successfully commissioned, the PRIM LED on one of the two L-IP
Redundant devices should be green and should be off on the other one.
Important: If bus loop monitoring (see 10.2.1) is not used and thus the loop port 2 terminal of the L-IP
Redundant routers is not connected be sure to first commission the router and the
diagnostic node of one L-IP Redundant and switch off bus loop monitoring on this L-IP
Redundant before connecting the second L-IP Redundant!
After the router and the diagnostic node have been configured, use the L-IP Redundant
Plug-In (see Section 10.5) or the web interface (see Section 10.6) to enter a node list for node
monitoring or to change the parameters for bus loop monitoring and twin router monitoring.
This is the preferred method to use the configuration utility and allows using the full
functionality of the plug-in. The network management tool is attached to the network and all
network changes are directly propagated into the network. This mode must be used to
commission the device, download and upload the node list, download and clear the alarm
log, and get the current device state.
The off-line mode can be used for all operations requiring LNS, that is, to add the device
using the device templates, change the device properties, and create a node list including the
automatic generation of a node list (LNS import). However, no communication with the
device is possible (e.g. to download the node list).
The L-IP Redundant Plug-In can also be executed as a standalone program. This operation
mode offers least functionality. It allows creating and editing a node list or loading, altering
and saving a configuration file.
10.5.2 Overview
Figure 114 shows the L-IP Redundant Configuration Plug-In. The window is separated in
three main areas:
The view selection allows selecting different configuration and diagnostic pages.
Depending on the selected view the current view area contains different information (e.g.
the node list).
The log window shows different all actions performed by the plug-in and any errors or
warnings messages that occurred.
At the top of the window the toolbar allows selecting different actions depending on the
currently selected view. The standard commands “load”, “save” and “new” are always
possible. “Save” allows storing all configuration data (node list, properties) and the alarm log
to a file, while “load” will restore all this information from a file. The information shown in
the status and in the channel statistics view are not stored.
The “Twin Router Selection” shows the name of the primary and – if present – the secondary
router. The one currently selected is marked. By clicking on the other one the selection can
be changed on the fly.
The “Plug-In Mode” shows the operation mode of the plug-in (see 10.5.1) and whether the
device is accessible over the network.
Note: Most of the diagnostic information is only available if the plug-in is running in online mode
and the device is accessible over the network.
Devices
Shows the name and the subsystem of the primary and – if present – the secondary device.
By clicking on the “Wink” button the corresponding L-IP Redundant can be winked (see
6.4.9). Further the device currently selected by the plug-in is shown (“selected”) and if the
plug-in can communicate with the device (“ok”/”fail”). Finally the unique node ID of the
monitoring node on the routers is given.
Loop Monitor
Shows whether the loop is open, closed or bus loop monitoring disabled.
Twin Monitor
Twin Router: Shows whether the device has a twin router installed.
Status: Shows whether the device is primary, secondary, still negotiating or the
secondary has temporary taken over since the primary failed.
CEA-709/CEA-852 Communication: Shows whether its twin router is reachable via the
CEA-709 and CEA-852 segment respectively.
This list shows all the nodes in the node list of the device with the current status. If a node is
not reachable/offline or the ring is open and the node is only reachable via one loop port the
corresponding alarm is shown in the column “Node Alarm”. By selecting one or multiple
nodes in the list and clicking on the “Wink selected node(s)” button the corresponding nodes
can be winked using the CEA-709 wink network management command.
If the checkbox “automatically refresh data” is checked data in the device status view is
refreshed every 15 seconds. The page can be refreshed manually by pressing the “refresh”
button.
Note: Most of the diagnostic information is only available if the plug-in runs in online mode and
the device is accessible over the network.
Device up-time
The following data is shown for each channel the L-IP Redundant is attached to
(CEA-709/CEA-852):
Elapsed time
Shows the time since L-IP Redundant powered up or since the statistics for this port where
reset.
Bandwidth utilization
Shows the current and the maximum value of the bandwidth utilization of the corresponding
channel. The bar shows the current bandwidth utilization.
CRC errors
Shows the current and the maximum percentage as well as the total number of packets with
CRC errors observed on the corresponding channel.
Missed Packets
Shows the current and the maximum percentage as well as the total number of packets, which
could not be processed or received on the corresponding channel.
Packets
Shows the current and the maximum number of packets per second as well as the total number
of packets on the corresponding channel.
Missed Preambles
Shows the current and the maximum number of missed preambles per second as well as the
total number of missed preambles observed on the corresponding channel. A missed
preamble is detected, whenever the link layer receives a preamble, which is shorter than the
defined preamble length. A large number in this counter is usually due to noise on the
channel.
Overload
Signals an overload condition of the channel during the last statistic interval. A channel can
be overloaded due to one of the following conditions:
The bandwidth utilization during the last statistic interval exceeded the limit defined by
the parameter “Bandwidth Utilization Limit” (default 70%) OR
The CRC Error Rate during the last statistic interval exceeded the limit defined by the
parameter “CRC Error Limit” (default 5%) OR
The Missed Packets Rate during the last statistic interval was not zero OR
The Missed Preamble Rate during the last statistic interval exceeded the limit defined by
the parameter “Missed Preamble Limit” (default switched off).
Overload Ratio
Ratio between statistic intervals during which the channel was in overload condition and
intervals during which the channel was not in overload condition.
If the checkbox “automatically refresh data” is checked data in the channel statistics view is
refreshed every 15 seconds. The page can be refreshed manually by pressing the “refresh”
button. Finally all statistic data can be cleared by pressing the “clear statistics” button.
The alarm log view is used to access the alarms logged in the L-IP Redundant. To access the
alarm log click on the “Alarm Log” icon on the left side of the L-IP Redundant Plug-In
window (see Figure 117).
If the plug-in is running in online mode you can download the alarm log from the L-IP
Redundant either by double-clicking on the “click to upload alarm log” entry in the list, via
“Upload Alarm Log” in the “Alarm Log” menu, or by clicking on the corresponding icon in
the tool bar (see Figure 117). Similar the alarm log can be cleared.
Figure 118 shows a typical alarm log. For each alarm an description, a start time an end time
and an alarm code is logged. All alarm times refer to the time set on the L-IP Redundant.
Currently the following alarms are possible:
"Ring open": Bus loop monitoring has detected an open loop (see Section 10.2.1).
"Twin error CEA-709": Twin router is not reachable any more via the CEA-709 side
(see Section 10.2.2).
"Twin error IP": Twin router is not reachable any more via the CEA-852 side (see
Section 10.2.2).
"Fwd warning CEA-709": Packets forwarded from the CEA-709 to the CEA-852 side
on the selected device is significantly lower than on the remote twin router (see Section
10.2.2).
"Fwd warning IP": Packets forwarded from the CEA-852 to the CEA-709 side on the
selected device is significantly lower than on the remote twin router (see Section 10.2.2).
"Fwd error CEA-709": The selected device does not forward any packets from the
CEA-709 to the CEA-852 side, while the remote twin router does.
"Fwd error IP": The selected device does not forward any packets from the CEA-852 to
the CEA-709 side, while the remote twin router does.
“Side 1 disconnect”/”Side 2 disconnect”: The selected device does not reach its twin
router via its port 1 or port 2 respectively. This error can only occur on the secondary
(inactive) twin router.
“Dev No <no> error” or “<desc> error”: Node with number <no> or description <desc>
is either not reachable or not configured online.
The alarm log can by transferred to another application using Copy & Paste or by export to
a CSV-file (see Figure 119).
To create a new node list or edit an existing node list, go to the node list view by clicking on
the “Node List Config” icon on the left side of the L-IP Redundant Plug-In window (see
Figure 120).
Further, the order of the nodes in the node lists can be changed and a node list can be exported.
Finally the node list can be downloaded to the device and an existing node list can be
uploaded from the device.
As you type the node address, it will be checked and the result of the syntax check is indicated
by the dialog icon and the text field. Press the “Save” – Button to save the node address into
the node list.
Existing nodes can be edited by double clicking on the row containing the node in the list.
Figure 122: Tried to save entry which is identical to an already existing one.
Note that the address is checked against double entries while saving and an error message
will appear if you try to add a new entry or change the address of an existing entry into an
address which already exists (see Figure 122). If you press OK here, entry number 2 will be
deleted and entry number 1 updated.
You can choose to delete the current node list prior to import. If this option is not selected
only nodes not present in the current node list are added. Further the address format used to
contact the node can be selected. You can choose between the Subnet/Node address format
and the Unique Node ID (“Neuron ID”) address format.
LNS import is only available in on-line and off-line operation mode, but not in standalone
operation mode.
Further, the node list can be exported and imported to/from a CSV-file. This allows using a
spreadsheet application (e.g. Microsoft Excel) to create and edit the node list (see Figure
126).
Figure 125: Transfer the node list between applications with Copy & Paste.
If the router redundancy is used, a dialog will ask whether to copy the same node list to the
twin router (see Figure 128) after the download to the selected device has finished. It is
strongly recommended to answer this dialog with “Yes”.
10.5.7 Parameters
The properties view is used to access the configuration properties used to define the
behaviour of the L-IP Redundant. To access the properties view click on the “Parameters”
icon on the left side of the L-IP Redundant Plug-In window (see Figure 129).
This parameter influences the heart beat functionality in the node object of the diagnostic
node (see Section 10.7.1). If set to 0 the heart beat functionality is disabled, any other value
will enable heart beat functionality and nvoStatus, nvoAlarm and nvoAlarm_2 will be sent
out with the interval defined by this value.
Deselecting this check box will disable bus loop monitoring (see Section 10.2.1).
This parameter influences the heart beat functionality in the bus loop monitor object of the
diagnostic node. If set to 0 the heart beat functionality is disabled, any other value will enable
heart beat functionality and nvoLoopOK and nvoLoopStatus will be sent out with the interval
defined by this value.
Deselecting this check box will disable twin router monitoring (see Section 10.2.2). Note: If
no twin router is present it is not required to turn off twin router monitoring.
This parameter influences the heart beat functionality in the twin router object of the
diagnostic node. If set to 0 the heart beat functionality is disabled, any other value will enable
heart beat functionality and nvoTwinStatus will be sent out with the interval defined by this
value.
This value defines the twin router monitoring interval. It must be identical on both twin
routers.
Max Retries
This value defines the number of retries used by the twin router monitoring algorithm if the
twin router does not respond. Thus, the maximum time it takes until a twin router failure will
be detected calculates to:
History Size
This value defines the number of monitoring intervals used to compare the number of packets
forwarded by both twin routers. It must be identical on both twin routers.
Warning Limit
This value defines the limit for issuing the “Forwarding Warnings” (see nvoTwinStatus,
Section 10.7.4 or alarm log, Section 10.6.3): If the number of packets forwarded by the local
router is less then <Warning Limit> % of the number of packets forwarded by the twin router
an warning is triggered.
Min Messages
This value defines minimum number of packets to be forwarded on the twin router to issue a
“Forwarding Error” (see nvoTwinStatus, Section 10.7.4 or alarm log, Section 10.6.3): If the
number of packets forwarded by the local router is zero but the number of packets forwarded
by the twin router is at least < Min Messages > the alarm is issued. Further, if the device is
the primary router the secondary router will take over (standby mode).
Deselecting this check box will disable node monitoring (see 10.2.3).
This parameter influences the heart beat functionality in the device monitor object of the
diagnostic node. If set to 0 the heart beat functionality is disabled, any other value will enable
heart beat functionality and nvoNodeMonAlarm, nvoNodeMonStatus, nvoRingALastNode,
nvoRingBLastNode, nvoRingAReceived and nvoRingAReceived will be sent out with the
interval defined by this value.
This value defines the interval used to send query status messages to the nodes in the node
list. Thus, the maximum delay until a node failure is detected and the duration of a complete
scan pass calculates to:
This value defines the interval which is used by the channel monitor objects to accumulate
statistic data and to calculate the resulting average values.
Deselecting these check boxes will disable the corresponding channel monitor object (see
Section 10.2.3).
This value defines the upper bandwidth utilization limit for the calculation of the overload
condition. If the current bandwidth utilization exceeds this limit the corresponding channel
is considered to be in overload state. Set this value to 0 to exclude the bandwidth utilization
from the calculation of the overload state.
This value defines the upper CRC error rate limit for the calculation of the overload condition.
If the current CRC error rate exceeds this limit the corresponding channel is considered to be
in overload state. Set this value to 0 to exclude the CRC error rate from the calculation of the
overload state.
This value defines the upper missed preamble rate limit for the calculation of the overload
condition. If the current missed preamble rate exceeds this limit the corresponding channel
is considered to be in overload state. Set this value to 0 to exclude the missed preamble rate
from the calculation of the overload state.
If the plug-in runs in online mode the changes can be saved in the LNS database and
downloaded to the device by pressing the “Save Settings” button, if the plug-in is in offline
mode changes are only saved in the LNS database and will be downloaded to the device the
next time the network management tool is in online mode.
If router redundancy is used and a twin router is assigned the configuration can also be
synchronized with the twin router. Simply click “Yes” in the dialog shown after the
configuration was stored for the selected router (see Figure 130). It is strongly recommended
to always keep the configuration properties in both routers identical to guarantee smooth
operation.
Default settings can be restored by pressing the “Set Defaults” button. To copy the values
currently used by the device to the LNS database press the button “Load from Device”.
10.6.1 Status
Figure 131 shows the status page. This page offers similar information as the status view of
the L-IP Redundant Plug-In (see Section 10.5.3).
When clicking on the “Send Service Pin Message” button a service pin message is sent
by the L-IP Redundant Diagnostic node.
For each node in the “Node Monitor Details” table, which is responding over the network, a
“Stats” button is present. This button allows viewing the node statistics of the remote node
(see Figure 132).
Figure 132: The L-IP Redundant Web Interface – Device Statistics Page.
Figure 133: The L-IP Redundant Web Interface – Channel Statistics Page
Figure 134: The L-IP Redundant Web Interface – Alarm Log Page
Figure 135: The L-IP Redundant Web Interface – Node List Config Page
Clicking on the link “import” allows importing/uploading a node list from a CSV-file
Multiple nodes can be selected by checking the check box at the end of each column. The
drop down box “Action on Selected” allows choosing an action (Move up, Move down,
Delete). Clicking on the “Execute” button executes the chosen action on the selected nodes
list entries.
If router redundancy is used the node list can be copied to the twin router by clicking on the
“Copy to Twin” button. It is strongly recommended to always copy the node list to the twin
router if a node list has been created or edited.
Note that the node list is included in the backup and restore operation offered by the web
interface (see Section 7.6.1).
10.6.5 Parameters
Figure 136 shows the parameters page. This page offers similar information as the parameters
view of the L-IP Redundant Plug-In (see Section 10.5.7).
If router redundancy is used, the button “Save & Copy to Twin” allows saving changes in the
configuration to the local device and its twin router. It is strongly recommended to always
copy the parameters to the twin router to guarantee smooth operation.
Node Object
nviRequest nvoStatus
nviFileReq nvoFileStat
nviFilePos nvoAlarm
nviClearStat nvoAlarm_2
nvoSupplyVolt
nvoSystemTemp
nvoUpTime
o RQ_NORMAL
o RQ_UPDATE_STATUS
o RQ_REPORT_MASK
o RQ_ENABLE
o RQ_DISABLE
o RQ_UPDATE_ALARM
o RQ_CLEAR_ALARM
The network variable nvoSupplyVolt (SNVT_volt) holds the current supply voltage of
the L-IP Redundant, while nvoSystemTemp (SNVT_temp) contains the current internal
temperature. With these two network variables a simple health monitoring can be
performed.
The statistic counters of all Channel Monitor objects (see Section 10.7.5) can be reset by
setting the network variable nviClearStat (SNVT_switch) to {100, ON} and back to {0,
OFF}.
The network variable nvoUpTime (SNVT_elapsed_tm) gives the time elapsed since the
L-IP was (re-)booted.
nvoLoopStatus
SNVT_switch nvoLoopOK
This network variable represents the loop state. It can have the following values:
SNVT_state_64 nvoLoopStatus
This network variable represents the current state of the loop object. Currently the following
bits are used:
bit0: 0 if bus loop monitoring is enabled, 1 if bus loop monitoring is disabled. Bus loop
monitoring can be disabled either manually (e.g. by disabling the object) or because the
L-IP is in twin router mode and the device is in standby mode and thus inactive.
SNVT_state_64 nvoNodeMonStatus
This network variable represents the current state of the device monitor object. Currently the
following bits are used:
bit1: 0 if all monitored nodes node is reachable and online or was not yet queried, 1
otherwise.
nvoNodeMonAlarm[2]
nvoRingALastNode
nvoRingBLastNode
nvoRingAReceived[2]
nvoRingBReceived[2]
SNVT_state_64 nvoNodeMonAlarm[2]
Shows the state of the monitored nodes. Each bit corresponds to one node in the node list
(e.g. bit0 -> index 1, bit1 -> index 2, etc.). Array element nvoNodeMonAlarm[0] represents
nodes with index 1- 64, while array element nvoNodeMonAlarm[1] represents nodes with
index 65-128. If the bit is 0 the corresponding node is reachable and online or was not yet
queried, if the bit is 1 the corresponding node is not reachable or not in configured online
state.
SNVT_count nvoRingALastNode
SNVT_count nvoRingBLastNode
These two network variables allow detecting the point of fracture if the loop is interrupted
by showing the two nodes closest to the fracture. nvoRingALastNode contains the index of
the last node reachable from loop port 1, while nvoRingBLastNode contains the index of the
last node reachable from loop port 2. The value is encoded as follows:
1-128: Loop interrupted. Value corresponds to index of last node reachable from this port.
Note: Only valid if bus loop monitoring is enabled and the node list order corresponds to the order
of the nodes within the loop (node closest to loop port 1 has index 1, node closest to loop port
2 has highest index). Otherwise the network variable is set to 0.
SNVT_state_64 nvoRingAReceived[2]
SNVT_state_64 nvoRingBReceived[2]
Shows on which port(s) the monitored nodes were responding to the last query status request
sent by the device monitor object. Each bit corresponds to one node in the node list (e.g. bit0
-> index 1, bit1 -> index 2, etc.). Array element nvoRingXReceived[0] represents nodes with
index 1- 64, while array element nvoRingXReceived[1] represents nodes with index 65-128.
If the corresponding bit in nvoRingAReceived[X] is set to 1 the node was responding on loop
port 1, if it is set in nvoRingBReceived[X] the node was responding on loop port 2. This
allows the combinations shown in Table 7.
RingAReceived RingBReceived Significance
0 0 No response received
Node is responding from other subnet (i.e. across the router)
Bus loop monitoring disabled
1 0 Node responds on port 1 only
Loop is open
0 1 Node responds on port 2 only
Loop is open
1 1 Node responds on both ports
Loop is closed
Table 7: Significance of nvoRingXReceived bit combinations.
UNVT_red_rtr nviRedRtr
UNVT_red_rtr nvoRedRtr
As already mentioned in Section 10.4.3.2 these two network variables are used to establish
the connection between paired L-IP Redundant devices.
nviRedRtr nvoRedRtr
nvoTwinStatus
SNVT_state_64 nvoTwinStatus
This network variable represents the current state of the twin router object. Currently the
following bits are used:
bit0: 0 if twin router monitoring is enabled, 1 if twin router monitoring is disabled. Twin
router monitoring can be disabled only manually (e.g. by disabling the object).
bit1: 0 if the device is the secondary router, 1 if the device is the primary router.
bit2: 0 if the device is in normal operation mode (primary -> active, secondary ->
inactive), 1 if the secondary router has taken over (primary -> inactive, secondary ->
active).
bit3: 0 if the device is in normal operation, 1 if the device is currently negotiating with
its twin router to determine which one is primary and which secondary router.
bit4: 0 if the twin router address is not known yet, 1 if the twin router address is known.
If the twin router address is not yet known CEA-852 monitoring (bit9) and the
forwarding warnings and errors (bit10-bit13) are not applicable.
bit8: 1 if the twin router is not reachable via the CEA-709 segment (local segment), 0
otherwise.
bit9: 1 if the twin router is not reachable via the IP-852 channel (IP backbone), 0
otherwise.
bit10: 1 if the packets forwarded from the CEA-709 to the CEA-852 side on the local
device is significantly lower than on the remote twin router. 0 if the router is working
properly.
bit11: 1 if the packets forwarded from the CEA-852 to the CEA-709 side on the local
device is significantly lower than on the remote twin router. 0 if the router is working
properly.
bit12: 1 if the local device does not forward any packets from the CEA-709 to the
CEA-852 side, while the remote twin router does. 0 if the router is working properly.
bit13: 1 if the local device does not forward any packets from the CEA-852 to the
CEA-709 side, while the remote twin router does. 0 if the router is working properly.
nvoPort
nvoElapsedTime
nvoAvgPackets
nvoIvalBandUtil
nvoIvalCrcError
nvoIvalMissPkt
nvoIvalPackets
nvoTotalCrcError
nvoTotalMissPkt
nvoTotalPackets
nvoMaxBandUtil
nvoMaxCrcError
nvoMaxMissPkt
nvoMaxPackets
nvoIvalMissPrea
nvoTotalMissPrea
nvoMaxMissPrea
nvoOverload
nvoOverloadRatio
SNVT_count nvoPort
Index of port associated with this Channel Monitor Object instance. Port 1 corresponds to the
CEA-709 side of the L-IP Redundant, while port 2 corresponds to the CEA-852/IP side of
the L-IP Redundant. Polled only.
SNVT_elapsed_tm nvoElapsedTime
Time since L-IP Redundant powered up or since the statistics for this port where reset. The
statistics can be reset using the web interface (see Section 10.6), the network variable
nvoClearStat (see Section 10.7.1) or if the node is reset with a network management
command (e.g. while the device is commissioned). Polled only.
SNVT_count_32 nvoAvgPackets
The average number of packets per second received or transmitted via the associated channel
since power-up or since the statistics for this port where reset.
SNVT_lev_cont nvoIvalBandUtil
Bandwidth utilization of associated channel during the last interval. For a smooth operation
of the CEA-709 segment the bandwidth utilization must remain below 50%.
SNVT_lev_cont nvoIvalCrcError
Percentage of packets with CRC error received on the associated channel during the last
interval.
SNVT_lev_cont nvoIvalMissPkt
Percentage of packets from the associated channel which could not be processed during the
last interval.
SNVT_count_32 nvoIvalPackets
Number of packets received or transmitted via the associated channel during the last interval.
SNVT_count_32 nvoTotalCrcError
Total number of packets with CRC error received via the associated channel since power-up
or since the statistics for this port where reset.
SNVT_count_32 nvoTotalMissPkt
Total number of packets from the associated channel which could not be processed since
power-up or since the statistics for this port where reset.
SNVT_count_32 nvoTotalPackets
Total number of packets received or transmitted via the associated channel since power-up
or since the statistics for this port where reset.
SNVT_lev_cont nvoMaxBandUtil
Maximum value of nvoIvalBandUtil since power-up or since the statistics for this port where
reset. For a smooth operation of the CEA-709 segment the bandwidth utilization must remain
below 50%.
SNVT_lev_cont nvoMaxCrcError
Maximum value of nvoIvalCrcError since power-up or since the statistics for this port where
reset.
SNVT_lev_cont nvoMaxMissPkt
Maximum value of nvoIvalMissPkt since power-up or since the statistics for this port where
reset.
SNVT_count_32 nvoMaxPackets
Maximum value of nvoIvalPackets since power-up or since the statistics for this port where
reset.
SNVT_count_32 nvoIvalMissPrea
Number of missed preambles per second on the associated channel measured during the last
interval. A missed preamble is detected, whenever the link layer receives a preamble, which
is shorter then the defined preamble length. A large number in this counter is usually due to
noise on the channel.
SNVT_count_32 nvoTotalMissPrea
Total number of missed preambles per second on the associated channel measured since
power-up or since the statistics for this port where reset.
SNVT_count_32 nvoMaxMissPrea
Maximum value of nvoIvalMissPrea since power-up or since the statistics for this port where
reset.
SNVT_switch nvoOverload
Signals an overload condition of the channel during the last statistic interval. A channel can
be overloaded due to one of the following conditions:
The bandwidth utilization during the last statistic interval (nvoIvalBandUtil) exceeded
the limit defined by the CP nciBandUtilLim (default 70%) OR
The CRC Error Rate during the last statistic interval (nvoIvalCrcError) exceeded the
limit defined by the CP nciCrcErrorLim (default 5%) OR
The Missed Packets Rate during the last statistic interval (nvoIvalMissPkt) was not zero
OR
The Missed Preamble Rate during the last statistic interval (nvoIvalMissPrea) exceeded
the limit defined by the CP nciMissPreaLim (default switched off).
If an overload is detected the network variable is set to {100, ON}, while if no error occurred
it is set to {0, OFF}.
SNVT_lev_cont nvoOverloadRatio
Ratio between statistic intervals during which the channel was in overload condition and
intervals during which the channel was not in overload condition since power-up or since the
statistics for this port where reset.
11 Operating Interfaces
SNMP allows querying status and statistics data from devices and also allows devices to
alarm network management applications using SNMP traps. A managed device contains an
SNMP agent which communicates with a management system using UDP. The SNMP agent
holds collects and provides its data items in a tree. The data provided by an SNMP agent is
defined by Management Information Bases (MIBs). These define the names and data types
of the management data. Every data item is assigned an object ID (OID). A device can
support an arbitrary number of MIBs, such as CPU statistics or network traffic statistics.
11.1.2 Configuration
The SNMP agent can be configured in the Web UI and in the configuration software. Figure
142 shows the Web interface. The settings in the configuration software are similar.
SNMP Protocol version: This setting selects between version 2C, 3 and 2C+3.
Protocol version 2C is more common, but lacks encrypted authentication.
SNMP agent port:This select the UDP port on which the SNMP agent listens. It
is recommended to keep this port at its default setting, port 161.
SNMP Trap address: This setting defines the destination IP address to which
traps (alarms) are sent.
SNMP Trap port: This setting defines the destination UDP port to which traps
(alarms) are sent.
SNMP Trap user: This setting defines the user name when sending traps (SNMP
v3)
SNMP Community string: This defines the (read) community string used for
SNMP v2c.
SNMP User name: This defines the user name required to access the SNMP agent
(SNMP v3)
SNMP User password: This defines the user password required to access the
SNMP agent (SNMP v3).
Expose data points: This switch allows to access data points exposed to OPC also
to be accessed via SNMP.
As SNMP has several restrictions on what can be represented, the following mappings are
made:
Binary data points. Binary data points are mapped to the INTEGER type. FALSE
is mapped to 0, TRUE is mapped to 1 and an invalid value is mapped to -1.
Analog data points: SNMP has no standard way to represent floating point values,
so their values are mapped to the STRING type. A value of “--“ identifies an invalid
value
Multistate data points: Multistate data points are mapped to the STRING data type.
Their values are represented by the multi-state text labels.
SNMP variable names have to be unique within their MIB, so data points with the same name
in different folders are made unique by the following name scheme: dpNNNNXUUUUUUUU, e.g.
dpFreeMemoryX00000003. NNNN is the data point name with all forbidden characters
removed (only a-z, A-Z and 0-9 is allowed). UUUUUUUU is replaced with the unique ID of
the data point.
Figure 143 shows the Web UI page which allows downloading the device specific MIB file.
The “Download MIB file” buttons generates a MIB file which can be used by a network
management tool. The “Download XML file” button generates an XML-encoded
representation of the MIB contents.
Note that the MIB files are dependent on the data point configuration, so that changes in the
data point configuration will change the MIB contents.
SNMP Version 2C uses unencrypted authentication and payload. The community string is
transmitted in clear text and can be easily extracted from captured network traffic.
12 Network Media
12.1 TP-1250
The TP-1250 uses transformers for galvanic isolation. The topology of a TP-1250 network is
a bus. Thus, both ends of the bus cable need to be terminated. LOYTEC recommends using
its L-TERM network terminators (LT-13) for network termination (see Figure 144).
If the collision-less backbone mode (recommended, default behavior) is disabled, the L-IP
TP-1250 ports are fully compatible to the parameters specified by LONMARK for this channel
(TP/XF-1250). If the collision-less backbone mode is enabled, proprietary channel
parameters are used. In this case no Neuron Chip based nodes or other nodes with standard
TP-1250 communication parameters are permitted on the same channel.
12.2 FT-10
The L-IP FT-10 ports are fully compatible to the parameters specified by LONMARK for this
channel. FT-10 ports can also be used on Link Power (LP-10) channels. However, the L-IP
does not provide the power supply for Link Power channels.
When using the Free Topology Segment feature of the FT-10, only one termination is
required and can be placed anywhere on the free topology segment. In a double terminated
bus topology, two terminations are required. These terminations need to be placed at each
end of the bus.
LOYTEC recommends using its L-TERM network terminators (LT-13, LT-33 or LT-03) for
network termination (see Figure 144).
12.3 RS-485
The L-IP RS-485 ports are fully compatible with the parameters specified by TIA/EIA
RS-485 for this channel. A maximum of 32 L-IP RS-485 ports can be connected to one
channel.
The RS-485 ports support bit-rates between 300 kbps and 2.5 Mbps. When using bit-rate
auto-detection the L-IP checks for the following bit-rates: 0.61 kbps, 1.221 kbps, 2.441 kbps,
4.883 kbps, 9.766 kbps, 19.531 kbps, 39.0625 kbps, 78.125 kbps, 156.25 kbps, 312.5 kbps,
625 kbps, 1,250 kbps and 2,500 kbps. Standard Neuron Chip compatible channel parameters
with a channel priority of 4, but no node priority are used with these bit-rates. If bit-rate auto-
detection is switched off, the channel parameters for the LONMARK TP-RS485-39 channel
(39 kbps) are used.
RS-485 can only be used in a bus configuration and must be terminated on both ends. The
maximum stub length between the main bus and a single node is 0.3 m.
LOYTEC recommends using its L-TERM network terminators (LT-04 or LT-B4) for
network termination (see Figure 145).
The L-IP supports bit-rate auto-detection on RS-485 channels. The factory default DIP-
switch setting enables bit-rate auto-detection on all RS-485 ports. Figure 146 shows the DIP-
switch settings to disable bit-rate auto-detection, assuming all other DIP switches remain in
the factory default position.
off
on
1234567
Alternatively the bit-rate auto-detection can be enabled/disabled via the console menu.
Further the console menu allows restarting the bit-rate auto-detection on selected ports. While
the port is auto-detecting the activity LED is flashing orange.
Redundant cabling options are enabled by the Rapid Spanning Tree Protocol (RSTP) which
is implemented in most managed switches. Please note, that this is a feature of the switch,
not of the L-IP, so that LOYTEC cannot give a guarantee that this will work with a particular
switch model. In no case redundant cabling options will work with unmanaged switches. The
older Spanning Tree Protocol (STP) should not be used for this type of application, as it
converges too slowly.
Star topology: In the most basic setup, a device is connected to an Ethernet switch with one
cable. This is called a star cabling because all devices are connected to a common upstream
device. In this setup, the cable and the switch are single point of failures.
Chain topology: Because the L-IP itself acts as an Ethernet switch, this device can be
connected to a chain. This is a special form of the star topology. Its advantage is the reduced
cabling costs. The disadvantage is the connection loss to downstream devices when an
upstream device is powered-off, reset or removed. Also, the Ethernet bandwidth (100 MBit/s)
is shared among all members of the chain. The last device has one unused Ethernet port, as
it is not allowed to create Ethernet loops without STP. The recommended maximum number
of daisy-chained devices is 20.
1 2 3 4 1 2 3 4
1
1
LINX-151
2
2
192.168.44.2
192.168.44.3
192.168.44.10
Switch1
Switch2
1 2
3
3
4
4
LINX-151
192.168.44.11
5
5
1 2
LINX-151
192.168.44.12
1 2
Fully redundant topology: Both Ethernet ports are connected to a different upstream switch.
Thus, a single cable or upstream switch problem can be tolerated. This topology requires
RSTP. In Figure 147, the L-IP with IP addresses 192.168.44.10 to 192.168.44.12 are
connected in this way. This connection scheme increases switch and cabling costs, but
increases network resilience. Note that the upstream network is connected via the lowest-
numbered ports. If this is not possible, the ports need to be configured to the lowest STP port
priority value (which is the highest priority).
Ring topology: In this setup, the devices are connected in a chain and each end of the chain
is connected to a different upstream switch. This topology requires RSTP. If a single device
is powered off, the RSTP will automatically recalculate the spanning tree so that all other
devices in the chain are reachable. Only if two devices are power-off at the same time, the
devices between them will not have an Ethernet connection. In Figure 148, the L-IP devices
with IP addresses from 192.168.44.10 to 192.168.44.12 are connected in this way. The
recommended maximum number of daisy-chained devices is 20.
1 2 3 4 1 2 3 4
1
1
192.168.44.3
2
192.168.44.2
Switch2
Switch1
LINX-151 LINX-151 LINX-151
3
3
192.168.44.10 192.168.44.11 192.168.44.12
4
1 2 1 2 1 2
4
5
5
Single upstream connection: Switch1 (or Switch2, but not both) is connected to the
upstream network while Switch2 only provides a redundant path to the Loytec devices. The
redundant path is created by a direct Ethernet cable between Switch1 and Switch2 which
needs to be plugged into a lower-numbered port than the L-IP devices are connected to. If
this is not possible, the STP port priority for the cross-connection cable needs to be set to a
low value. The RSTP domain should be restricted to Switch1 and Switch2. This can be done
by enabling a BPDU filter on the port on Upstream Switch 1. This will block all RSTP
packets to enter the upstream network. A sample setup for this topology is shown in Figure
149.
Upstream Switch 1
1 2 3 4
1
1
192.168.44.3
2
192.168.44.2
Switch2
Switch1
1 2 1 2 1 2
5
5
Redundant upstream connection: Switch1 and Switch2 are both connected to the upstream
network, either to two ports on the same switch or to two redundant upstream switches. In
this case, RSTP is needed to ensure a loop-free topology between the upstream switches,
Switch1 and Switch2, so the RSTP domain includes the upstream network and the chained
L-IP devices. The configuration of Switch1 and Switch2 need to ensure that they are not
selected as the root bridge. If possible device communication should be bound to a separate
VLAN and MSTP (Multiple Spanning Tree Protocol) should be employed to isolate the
spanning tree operations. This topology is shown in Figure 147.
12.4.3 Preconditions
For the fully redundant and ring topology, the following preconditions have to be met:
The upstream switches have to support the Rapid Spanning Tree Protocol (RSTP),
as defined in IEEE 802.1w.
Two distinct switches are required for each end of the device chain.
The STP bridge priority should be set to the minimum (61440), so that these
switches are not elected as root bridges.
The bridge mode should match the upstream bridge modes, preferable 802.1s or
802.1w.
If the upstream network uses RSTP, the timing parameters of the upstream networks must be
used. Else the timing parameters should be set to minimum values for fast convergence:
If a single upstream connection is used, the connected port on the upstream switch
should have BPDU filtering enabled.
If redundant upstream connections are used, the connected ports on the upstream
switches should have a BPDU root guard enabled.
12.4.5 Testing
When the switches are configured and the devices are connected, the following tests are
recommended. These tests are important to confirm that the STP changes due to topology
changes to not interfere with the rest of the network.
Check that no broadcast storms are sent into the upstream network by capturing
traffic between Switch1, Switch2 and the Upstream switch. This test should be done
continuously, especially during switch and device power cycles.
Power up all switches and devices. Wait until all devices are up, then test.
Power-on Switch2, power-off Switch1. Wait until Switch2 has booted, then test.
Reboot all L-IP devices. Wait until the devices have booted, then test.
Remove a single Ethernet cable. Wait approx. 10 seconds, then test. This test should
be repeated for different cables. Make sure that at least the following connections
are tested:
Upstream switches:
config
spanning-tree
spanning-tree priority 8
spanning-tree 3,4 root-guard
spanning-tree hello-time 1
spanning-tree forward-delay 4
spanning-tree maximum-age 6
exit
12.5 WLAN
12.5.1 Introduction
Devices supporting the LWLAN-800 wireless adapter can be connected to IEEE 802.11
wireless networks. The following operation modes are supported:
only a subset of the services of the device. For example, the WLAN interface
could expose the Web UI, but not BACnet communication.
Access point mode (separate network): In the isolated access point mode, a
client can connect to the wireless network created by the device. The device will
assign an IP address to the client and will redirect all traffic to itself. This mode is
used to configure a device with a mobile device.
Access point mode (bridged): In the bridged access point mode, a client can
connect to the access point and also can use the network devices on the bridged
Ethernet device. In this mode, the DHCP server is deactivated to avoid
interference with an existing DHCP server in the Ethernet network.
Mesh point (separate network): This mode is used to create an IEEE 802.11s
mesh network. Mesh points communicate with other mesh points in their radio
vicinity and automatically choose the best route. Mesh networks can be used to
extend the range of a wireless network or to create redundant radio links.
Mesh point (bridged): This mode is like the mesh point mode and also bridges
the mesh point to an Ethernet network. Thus devices in the Ethernet network can
communicate with devices in the mesh network. Only one mesh point should be in
the bridged mode to avoid network loops.
The LWLAN-800 interface can use two WLAN functions at the same time. This can be used
for advanced setups, like:
Wireless 1 is used as an access point for configuring the device, while the
Wireless 2 interface is used to participate in a mesh network.
Wireless 1 is used as a bridged access point for configuring the device and the
devices on the Ethernet network while Wireless 2 connects to another wireless
network to reach a remote device.
However, there are restrictions when using both interfaces at the same time:
A mesh network removes the roles of clients and access points. Every node in a mesh network
can send and receive data, as in a normal wireless network. However, every mesh node also
routes packets to other mesh nodes. It observes the signal strength to all reachable nodes and
distributes this information to other mesh nodes. Thus, the mesh network can transmit data
between nodes with are not in their radio vicinity. In this case, a path between sender and
receiver is selected and the intermediate nodes transmit the packet over several hops.
As the signal strenght and thus the range of a node can change over time, as well as nodes
can be added and removed, the best path can change. The 802.11s routing protocol takes this
into account and changes paths dynamically.
802.11s also provides strong encryption using the AuthSAE (Simultaneous Authentication
of Equals) protocol, so that each pair of mesh nodes use an encrypted link. It is resistant to
passive, active and dictionary attacks, given a strong pre-shared key.
Mesh Node
1 3 5 6
Mesh Portal
2 4
Ethernet
Figure 150 shows the roles of mesh nodes and possible links. Mesh point 1 can communicate
with point 2 and point 3. It learns that the mesh point 2 is the mesh portal, so all traffic leaving
the mesh network is automatically routed towards mesh point 2.
Mesh point 4 has mesh point 2 and 3 in its radio vicinity, but cannot communicate directly
with mesh point 1. So mesh points 1 to 4 have two ways to reach each other and can tolerate
the failure of a single node. This makes a mesh network resilient to node failure or fading
radio links.
Mesh point 6 is an example on how mesh networks can be used to extend radio range. If point
2 communicates with point 6, there are two possible paths: 2-4-5-6 and 1-3-5-6. It selects the
better path and mesh point 5 will extend the network range.
This example shows that every additional mesh point can make the network more resilient to
failures or can extend the range far beyond the range of a single radio.
The LWLAN-800 supports two antennas which should be mounted outside any metallized
housing.
The L-IP firmware supports remote upgrade over the network and the serial console.
To guarantee that the L-IP cannot be destroyed due to a failed firmware update the L-IP
firmware consists of two images:
Fall-back image
The fall-back image is write protected in flash memory and provides everything needed to
talk to the L-IP platform over the network. The L-IP application image is designed to be
updated over the network whenever there is a need to do so.
The fall-back image makes sure that the L-IP comes up in a status where the maintenance
software can at least talk to the L-IP platform and can download a new L-IP application
image.
When the L-IP boots up with the fall-back image, all port LEDs are flashing red. In this state
it does not forward any messages.
When running the software the window shown in Figure 151 appears. Enter the IP Address
of the L-IP you want to update, choose the firmware *.dl in the field Firmware File,
optionally check the check-box Reboot device after download and press the button Start
Download.
14 Troubleshooting
LonMaker reports an error when commissioning the L-IP as shown in Figure 153.
Explanation
Solution
Please make sure to set the DIP-switches according to Figure 83 as CEA-709 configured
router and reboot the L-IP. If the L-IP is used in smart switch mode simply do not commission
the L-IP.
If the problem still persists please contact LOYTEC support (see Section 14.8).
Explanation
Most likely the local clocks are not synchronized and the stale packet detection might drop
all packets received from other L-IPs.
Solution
Make sure that a proper Channel Timeout according Table 6 and that at least one SNTP server
is specified for the IP-852 channel. If the L-IP is operated behind a firewall make sure that
the firewall doesn’t block SNTP requests at port 123.
The L-IP reports the error “Can’t set default route:” during the boot process.
LOYTEC electronics GmbH
www.loytec.com
Explanation
The default gateway address is set to a wrong address or to an address that doesn’t exist.
Solution
In the configuration menu “[5] IP configuration” select item “[4] IP Gateway” and enter a
valid gateway address. Even if you don’t use a gateway enter the gateway address for this
subnet e.g. IP address: 192.168.1.34 => Gateway Address: 192.168.1.1.
Messages are not forwarded to or from the TP-1250 port(s). All other ports work properly.
Explanation
This problem might be due to mixing backbone mode and non-backbone mode devices on
one channel.
Solution
If the TP-1250 channel is used in backbone mode make sure all devices on the network have
backbone mode enabled, only L-IP or L-Switch devices are connected to this backbone and
every L-IP/L-Switch has a unique station ID set.
If the TP-1250 channel is not used in backbone mode make sure that all L-IP and L-Switch
devices on that channel have the backbone mode disabled.
The CEA-709 activity LED is flashing red whenever there is traffic on the channel (instead
of green).
Explanation
The L-IP has a built-in network analysis functionality (see Section 6.4.10): Whenever it
detects a potential problem on one port, the activity LED will change its color to red.
Solution
Most likely this behavior is due to a wiring problem. Check the wiring and termination of the
network connected to the affected port. If this does not solve your problem use a protocol
analyzer (e.g. LOYTEC’s LPA) and/or a network diagnostics tool (e.g. LOYTEC’s LSD
Tool or Echelon’s Nodeutil) to find the source of the problem.
14.6 The CEA-709 activity LED and the status LED are flashing red
Problem
The CEA-709 activity LED and the status LED are flashing red at a rate of approx. once per
second and the L-IP does not forward any messages.
Explanation
Somehow the primary image was destroyed and the fall-back image was booted (see Section
7). This image does not support forwarding of messages. It only allows downloading a new
firmware.
Solution
If this problem occurs because a firmware update was attempted (and failed somehow),
simply retry downloading the new firmware image.
If no firmware update was attempted, please contact LOYTEC support (see Section 14.8).
In a setup where CNIP routers are used to send data in one direction only (unacknowledged
services), the receiving CNIP router never sends out any data, therefore its position in the
network becomes unknown after a while (due to the aging mechanism of Ethernet switches)
and the traffic is then flooded to the entire network.
Explanation
Ethernet switches use an aging mechanism to store and manage Ethernet MAC addresses.
After some time the switch forgets the MAC address and forwards the Ethernet packets with
the forgotten MAC address to all ports.
Solution
Please activate the keep alive function on the configuration server to establish two-way
communication with the CNIP router.
e-mail : [email protected]
Web : http://www.loytec.com
tel : +43/1/4020805-100
fax : +43/1/4020805-99
or
e-mail: [email protected]
Web: http://www.loytec-americas.com
tel: +1 (512) 402 5319
fax: +1 (262) 408 5238
The default Port setting may be changed to the desired port. Normally, this can be left at its
default. If No authentication is selected, the device will allow incoming capture connections
without requiring any credentials. If Username and Password is selected as authentication
method, the client Wireshark will be required to provide valid credentials before the capture
session can be started. Note, that only the users admin and operator are allowed to connect
if this authentication method is selected.
Click the Save Settings button to save the configuration. The changes take effect and do not
require to reboot the device. The remote capture can also be disabled again without a reboot.
Verify that the Ethernet ports are listed in the Available capture ports table and that the
Remote capture status for these ports reads Disconnected.
To log offline without a Wireshark attached to the device, click the check box Local
Capture. The device will then start capturing packets and stores them in a ring buffer. The
log file can be downloaded by clicking on the button Download capture files. This stores a
ZIP archive of the packet capture to your local hard drive. Capture files can be cleared by
clicking Clear Files. After a reboot all local capture files are lost.
For local Ethernet capture additional capture filters can be added to narrow down the amount
of logged packets to those of interest. Select the line Ethernet port line and enter a basic filter
expression at the bottom of the page. Then click on Add and add more filters. Finally click
on Save Filters to store and activate the local capture filters. Figure 156 shows an example
filter for packets with IP address 192.168.24.100.
1. Open Wireshark and choose the menu Capture Options… . This opens the Capture
Options dialog as shown in Figure 157.
2. Click the Manage Interfaces button to open the Add new interfaces dialog.
3. Select the Remote Interfaces tab and click Add as shown in Figure 158.
4. Enter the correct settings for Host and Port (default 2002) and, if authentication is
enabled, enter Username and Password in the corresponding fields as shown in Figure
159.
5. Note that only the users admin and operator are allowed to connect.
7. If the connection to the device was established successfully, the Remote Interfaces list
will be updated with information about all capture ports available on the device as shown
in Figure 160.
8. Close the window and Capture Options dialogs to return to the main window.
1. Select the created remote interface from the interface list in the main window. It is named
‘Raw Ethernet traffic’ for remote Ethernet capture.
3. Wireshark will attempt to establish a connection to the device and, if successful, start
displaying packets. An example capture is shown in Figure 162.
15 Application Notes
Please refer to the application notes listed in Table 8 for further information on using the L-IP
in different application scenarios.
AN002E How to use the enhanced statistic features of the L-IP with
LSD Tool the LOYTEC system diagnostics tool (LSD tool)
AN003E How to use the L-IP with LonMaker and other network
L-IP and LNS management tools
AN005E This document shows how to combine L-Switches with an L-
L-Switch XP with IP (Ethernet) backbone.
L-IP Backbone
AN007E This application note provides information on how to use
Network LOYTEC network infrastructure products (L-Switch, L-IP,
Infrastructure L-Proxy, and NIC) together with LOYTEC network
interfaces in different example use cases. It also explains how
the different operating modes of the devices work and which
operating mode should be chosen for specific applications.
Table 8: L-IP related application notes.
This guide contains security-relevant information for operating the product on IT networks.
The information refers to the firmware version and the instructions found in the previous
chapters of this User Manual.
16.2 Firmware
The device is equipped with one piece of software. This is the firmware image and its related
firmware version. The firmware is distributed as a downloadable file. The device can be
upgraded by placing the firmware image onto the device using the procedure described in
Chapter 13. The device firmware is signed by LOYTEC and its signature integrity is verified
before the upgrade is allowed.
There exists exactly one firmware image for all L-IP models. The firmware has built-in auto-
detection of the fieldbus ports the device is equipped with. It adds virtual routers to an internal
channel. For the function of the device on the IP side this makes absolutely no difference, as
the IP connection is also tapped on to this internal channel.
16.3 Ports
This Section lists all ports, which may be used by the device. The ports are default settings
for their respective services. If not stated otherwise, the ports can be changed.
Required Ports:
1628 udp/tcp: This is the data exchange port for CEA-852 (LON over IP). It is required
for the primary function of the device to exchange control network data between routers
over the IP network. Each device needs this port open. The port can be changed.
1629 udp/tcp: This is the configuration server port of CEA-852. Exactly one device in
the system needs this port open. Other devices register with the configuration server to
form the IP-852 channel list. The port can be changed.
Optional ports not necessary for the primary product function. They can be disabled as
described in the installation instructions in Section 16.1:
21 tcp: This port is opened by the FTP server. This port is disabled by default.
22 tcp: This port is opened by the SSH server. The port can be changed and disabled.
23 tcp: This port is opened by the Telnet server. This port is disabled by default .
80 tcp: This port is opened by the Web server. It can be disabled.
161 tcp: This port is opened by the SNMP server. This port is disabled by default. The
port can be changed.
443 tcp: This port is opened by the secure Web server for HTTPS. It can be disabled.
2002 tcp: This port is opened by the Wireshark protocol analyzer front-end. This port is
disabled by default. The port can be changed.
4840 tcp: This port is opened by the OPC UA server. This port is disabled by default.
The port can be changed.
5900 tcp: This port is opened by the VNC server, if it is enabled. This port is disabled
by default. The port can be changed.
16.4 Services
Required services:
CEA-852 (LON over IP): Primary function of the device. This service is in accordance
with the standard ANSI/CEA-852-B.
Optional services not necessary for the primary product function. They can be disabled as
described in the installation instructions in Section 16.1:
HTTP: Web server. It provides a Web-based configuration UI. The Web UI can be
disabled after setting up the device.
FTP and Telnet: The FTP and Telnet server is used for connection to the device for
remote configuration (L-WEB), firmware upgrade, and access to the log file. The service
is disabled by default.
SSH: SSH server. It provides secure access to the device console menu over the network,
firmware upgrade, and access to the log file.
HTTPS: Secure Web server. It provides a Web-based configuration UI using HTTPS. It
is also used for connection to the device for remote configuration (L-WEB), firmware
upgrade, and access to the log file.
VNC: The VNC server can be used for remote access to the LCD display on devices that
have it. The service is disabled by default.
OPC UA: This secure service provides access to data points over the OPC UA standard.
The service is disabled by default.
SNMP: SNMP server. It provides network management information on the device used
by standard IT tools. The service is disabled by default.
Wireshark front-end: The Wireshark protocol analyzer may connect to this service and
retrieve online protocol analyzer logs. The service is disabled by default.
Logged events:
Time of the last power-on reset of the device.
Time and version of the last firmware upgrade.
Time when the device configuration has been cleared or the device was reset to factory
defaults.
Commission of the CEA-709 node/router.
Static errors in the device and its configuration.
System overload situations as one-time log messages since last power-on.
Crucial communication errors as they occur.
Logins and login failures.
To protect usage of the admin password, the admin user can create additional user accounts
with an admin role. Those additional user accounts can be disabled as needed.
17 Specifications
17.1.3 LIP-3333ECTC
Operating Voltage 12-35 VDC or 12-24 VAC ±10%
17.3 CE Warning
This is a Class B product. In a domestic environment, this product may cause radio
interference in which case the user may be required to take adequate measures.
18 Revision History
2019-09-25 7.0 STS Updated for firmware version 6.4. Added Section 6.2.19 VPN
configuration. Updated Chapter 15 Security Hardening Guide.
2021-04-26 7.4 STS Updated for firmware version 7.4. Removed Chapter Console interface.
Chapter 7: Reorganized to match new menu structure. Section 7.1.1:
Updated device setup and password enforcement. Section 7.3.5: Added
802.1X port authentication. Added Section 7.3.7 dynamic DNS. Section
7.3.18: Added description of the VPN tab. Section 7.3.19: Added LTE
configuration. Updated Chapter 16 Security Hardening Guide.