devolo dLAN 200 DSpro

devolo dLAN 200 DSpro
®
dLAN 200 DSpro
Manual
© 2007 devolo AG, Aachen (Germany)
While the information in this manual has been compiled with great care, it may not be deemed an assurance of product characteristics. devolo shall be liable only to the degree specified in the terms of sale and delivery.
The reproduction and distribution of the documentation and software supplied with this product and the use of its contents is
subject to written authorization from devolo. We reserve the right to make any alterations that arise as the result of technical
development.
You can find all declarations and certifications of compliance for the products, as long as they were available at the time of
publication, in the appendix of this documentation.
Trademarks
Windows® and Microsoft® are registered trademarks of Microsoft, Corp.
Linux® is a registered trademark of Linus Torvalds.
dLAN® is a registered trademark of devolo AG.
devolo and the devolo logo are registered trademarks of devolo AG. All other names mentioned may be trademarks or registered trademarks of their respective owners.
Subject to change without notice. No liability for technical errors or omissions.
devolo AG
Sonnenweg 11
52070 Aachen
Germany
www.devolo.com
Aachen, February 2007
|
3
Content
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.1 Thank you for placing your trust in this devolo product! . . . . . . . . 6
1.2 About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 For further information, please visit www.devolo.com . . . . . . . . . 6
1.4 Package contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2 Recommended Software Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3 Connection and Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2 Connection and display elements . . . . . . . . . . . . . . . . . . . . . . . . 8
3.3 Use of coax filters and attenuator . . . . . . . . . . . . . . . . . . . . . . . 10
4 Factory Default dLAN 200 DSpro Adapter Configuration . . . . . . 10
5 Starting Up the dLAN 200 DSpro Adapter . . . . . . . . . . . . . . . . . . 11
6 Providing an IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7 Telnet to the dLAN 200 DSpro Adapter . . . . . . . . . . . . . . . . . . . . 13
8 Writing an Autoconfiguration File . . . . . . . . . . . . . . . . . . . . . . . . 16
9 Configuring the DHCP/TFTP Server. . . . . . . . . . . . . . . . . . . . . . . . 18
10 Using the dLAN 200 DSpro Adapter Console . . . . . . . . . . . . . . . . 21
11 Useful Console Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
11.1 Resetting the dLAN 200 DSpro adapter from the Console . . . . . 22
11.2 Showing the Table of the Bridge . . . . . . . . . . . . . . . . . . . . . . . . 23
11.3 Checking and Changing Gains. . . . . . . . . . . . . . . . . . . . . . . . . . 23
11.4 Checking the Bits per Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
11.5 Changing the Boot Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
11.6 Setting a Static Network Configuration . . . . . . . . . . . . . . . . . . . 24
11.7 Changing the Frequency Band. . . . . . . . . . . . . . . . . . . . . . . . . . 25
11.8 Changing the MAC Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
| devolo dLAN 200 DSpro Manual |
4
|
12 Auto- configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
12.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
12.2 Boundary Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
12.3 Autoconfiguration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
12.3.1 Autoconfiguration at dLAN 200 DSpro adapter Boot. . 28
12.4 IFCP Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
12.4.1 IFCP Booting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
12.4.2 Incompatibilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
12.5 Translation Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
12.5.1 Transferring the Translation Table. . . . . . . . . . . . . . . . 32
12.5.2 Example of a Translation Table . . . . . . . . . . . . . . . . . . 33
12.5.3 Additional Information about Transferring IFCP. . . . . . 34
12.6 Wisconsin Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
12.7 Autoconfiguration & Networking . . . . . . . . . . . . . . . . . . . . . . . . 37
12.7.1 VLAN Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
12.7.2 noVLAN Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
12.7.3 OVLAN Configuration and Root Interface . . . . . . . . . . 38
12.8 Autoconfiguration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
12.8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
12.8.2 Parameter Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
12.8.3 Parameter Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
12.8.4 Supported Parameters in the Autoconfiguration File . . 41
12.9 NVRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
12.10 Equipment Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
12.10.1 End User Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . 64
12.11 Master-Side Access Protocol Tasks & User Profiles . . . . . . . . . . . 65
12.11.1 User Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
12.11.2 Working with RADIUS Authentication . . . . . . . . . . . . . 65
12.11.3 Working without RADIUS Authentication . . . . . . . . . . 66
12.12 DHCP Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
12.12.1 DHCP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
12.12.2 DHCP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
12.12.3 DHCP Server Configuration File Example . . . . . . . . . . . 67
12.13 RADIUS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
12.13.1 RADIUS Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
12.13.2 RADIUS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
12.14 Autoconfiguration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
12.14.1 Configuring Boot Mode from the Console . . . . . . . . . . 71
| devolo dLAN 200 DSpro Manual |
|
5
13 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
13.1 Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
13.2 Important safety instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
13.3 CE conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
13.4 Declaration of conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
13.5 Warranty conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
13.6 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
| devolo dLAN 200 DSpro Manual |
6
Introduction
|
1
Introduction
1.1
Thank you for placing your trust in this devolo
product!
The dLAN 200 DSpro is a network device that uses power and coaxial cables
which have already been installed in order to provide data communication for
applications such as Video streaming (Video on Demand), Internet telephony,
and fast Internet connection. Once it has been installed successfully, the dLAN
network behaves like a conventional LAN. The dLAN 200 DSpro supports a network speed of up to 200 Mbps and provides a powerful encryption function with
maximum data security.
1.2
About this manual
This document describes the basic steps required to setup a small demonstration
network with dLAN 200 DSpro adapters. It also explains the procedure to start
up a dLAN 200 DSpro adapter with the default factory configuration, get access
to the console, provide dynamic configuration through DHCP, and set a static
configuration.
1.3
For further information, please visit
www.devolo.com
Our online services (www.devolo.com) are available to you around the clock
should you have any queries or require any further support.
1.4
Package contents
Please ensure that the delivery is complete before beginning with the installation
of your dLAN 200 DSpro:
쎲
쎲
쎲
쎲
쎲
dLAN 200 DSpro
Network cable
Ethernet cable
Coaxial cable
Coaxial adapter
| devolo dLAN 200 DSpro Manual |
|
쎲
쎲
쎲
쎲
Recommended Software Tools
7
HF-Filter (part number 69722)
HF-attenuator (part number 69723)
Printed information leaflet
CD containing online documentation
devolo AG reserves the right to change the package contents without prior
notice.
2
Recommended Software Tools
A certain number of tools are required to configure and access the dLAN 200
DSpro adapter. All of these tools are available for Windows and Linux. In order
to reduce the learning cycle of the tools, we will describe the configuration process using Windows-based tools only.
The following tools can be downloaded from the network and used free of
charge:
쎲 Win Pcap is a packet capture library required by Wireshark to sniff the
packets arriving to the Ethernet port. It can be downloaded from
http://www.winpcap.org/
쎲 Wireshark is the graphical packet capture tool used to inspect the traffic
generated by the dLAN 200 DSpro adapter. It can be downloaded from
http://www.wireshark.org/
쎲 Hane Win DHCP / TFTP server is an easy to use DHCP + TFTP server all in one
tool. It is very useful to configure the dLAN 200 DSpro adapters at startup.
It can be downloaded from
http://www.hanewin.net/
쎲 Putty is a terminal emulator required to open a telnet session on the dLAN
200 DSpro adapter. The telnet client bundled with Windows will not work
well on the dLAN 200 DSpro adapter. It can be downloaded from
http://putty.mirroring.de/download.html
쎲 TFTP32 is a cute TFTP and DHCP server that provides detailed information
on the file download process. It is useful to perform firmware upgrades. It
can be downloaded from
http://tftpd32.jounin.net/
쎲 Iperf is a network performance test tool. It is useful to test the speed of a
network link. It can be downloaded from
http://www.noc.ucf.edu/Tools/Iperf/default.htm
| devolo dLAN 200 DSpro Manual |
8
3
Connection and Startup
|
Connection and Startup
This chapter covers the connectors and display elements of your dLAN 200
DSpro and explains how to connect the device.
3.1
System Requirements
To be able to follow the described procedures in the documents, it is recommended to have a PC equipped with a Fast Ethernet network card and running Windows 2000 or Windows XP. The computer must have one static IP assigned to
its network interface.
Make sure that there is no firewall or anti-virus running in the system. If Windows Service Pack 2 is installed on the PC running Windows XP, disable the
DHCP server service and the firewall service.
All of the tools and examples described in this document have been tested on a
computer running Windows XP.
3.2
Connection and display elements
The dLAN 200 DSpro features 5 control LEDs as well as an Ethernet, coaxial, and
a power connection:
Power
Lit steady when the dLAN 200 DSpro is ready for operation;
flashes when the dLAN 200 DSpro is in Power Save mode.
dLAN Link/Act
Lit steady when a connection with the dLAN 200 DSpro network exists; flashes when data is being sent or received via the
power or coaxial circuits.
ETH 100/Act
Lit steady when a 100 Mbps connection to the Ethernet network exists; flashes when data is being transmitted.
| devolo dLAN 200 DSpro Manual |
|
Connection and Startup
9
ETH 10/Act
Lit steady when a 10 Mbps connection to the Ethernet network
exists; flashes when data is being transmitted.
ETH Col
Flashes at a faster rate if the network is experiencing increasing
use.
ETH
This is the connection point on the dLAN 200 DSpro for connecting it to a computer or another device with the network cable
(included).
The Auto-MDI(X) interface in the dLAN 200 DSpro automatically detects when a contact is seized and determines the transmission rate of the connected network device.
Coax
Here you connect the dLAN 200 DSpro to the coaxial connector
using the coaxial cable supplied.
Coax/Hybrid
The switch must have been set to "Hybrid" to allow transmission across the power supply grid.
The switch must have been set to "Coax" to allow transmission
across the coaxial network.
AC
Here you connect the dLAN 200 DSpro to the power supply
using the power cable (included).
If no device that is switched on (e.g. computer) is connected to the Ethernet port,
the dLAN 200 DSpro device switches to Power Save mode after about 20 minutes (Power LED flashes). In Power Save mode, the dLAN 200 DSpro device cannot be accessed via the power supply grid or the coaxial network. As soon as the
device that is connected to the Ethernet port is switched on again, your dLAN
200 DSpro is available again via the power supply grid or the coaxial network.
| devolo dLAN 200 DSpro Manual |
10
3.3
Factory Default dLAN 200 DSpro Adapter Configuration
|
Use of coax filters and attenuator
The transmission frequency of the wanted signal across coaxial circuits is between 2 and 30 MHz. It can happen that interference is emitted above this frequency range, which may interfere with the wanted signals of other
applications. In this case, it is advisable to connect the added filter (standard
accessory: part number 69722) with the F-connector of the dLAN 200 DSpro.
The filter can be used in many communication applications, such as CATV, satellite and other systems to filter out unnecessary channels, frequencies or interference frequencies.
If the feed signal levels to TVs or CATV tuners are too high, picture distortions
will occur. It is recommended that by inserting an added attenuator (standard
accessory: part number 69723) into the distribution system, the signal is reduced at the customer outlet.
It is recommended to use a high pass filter (not part of the standard accessory)
to decouple the dLAN 200 DSpro signals from the transfer point of the TV signal.
A filter should be used
쎲 when you want to isolate your dLAN 200 DSpro network from the rest of the
coax infrastructure, or to prevent the dLAN 200 DSpro signal from interfering with other devices that are not included in your network.
쎲 when you want to shield your dLAN 200 DSpro network from interference
by other transmissions in the same frequency range.
쎲 when you want to protect your dLAN 200 DSpro network from interference
by a DOCSIS modem (or other cable modem) In this case, install a filter between the cable modem and the dLAN 200 DSpro network.
For more answers to frequently asked questions (FAQs), please visit our website
at www.devolo.com.
4
Factory Default dLAN 200 DSpro
Adapter Configuration
All dLAN 200 DSpro adapters are set to run the autoconfiguration process by
default. This process uses DHCP and TFTP to obtain the network settings and the
dLAN 200 DSpro adapter configuration. It also uses a proprietary protocol called
IFCP to learn the management VLAN.
| devolo dLAN 200 DSpro Manual |
|
5
Starting Up the dLAN 200 DSpro Adapter
11
Starting Up the dLAN 200 DSpro
Adapter
It is advisable to run Wireshark during the startup and configuration of the dLAN
200 DSpro adapter in order to ascertain the correct execution of this process and
diagnose potential configuration problems.
The first sign of life exhibited by the dLAN 200 DSpro adapter are the Spanning
Tree Protocol (STP) packets. After a few STP packets, the dLAN 200 DSpro adapter will issue a DHCP discover packet, as shown in Figure 1.
Figure 1: Packet Trace
of the Startup of the
Adapter
If you cannot see the DHCP packets coming from the dLAN 200 DSpro adapter,
the cause may be:
쐃 The firewall is filtering out these packets.
쐇 You are not running Wireshark on the physical Ethernet interface.
쐋 The dLAN 200 DSpro adapter does not have the factory default configuration.
6
Providing an IP Address
This section describes how to give an IP address to the dLAN 200 DSpro adapter,
without actually configuring the dLAN 200 DSpro adapter. As soon as the dLAN
200 DSpro adapter has an IP address, we can access its console using the telnet
application.
| devolo dLAN 200 DSpro Manual |
12
Providing an IP Address
|
We will use the HaneWin DHCP server to provide a dynamic IP to the dLAN 200
DSpro adapter. Follow the steps below to configure a dynamic range of IP leases
(see Figure 2):
쐃 Start HaneWin DHCP server.
쐇 Go to Options > Default Client Profile.
쐋 In the "Basic Profile" lid, set a rule for "Interface IP".
쐏 Write a range for dynamic IP addresses in the fields "from" and "until".
쐄 Write a subnet mask that is compatible with your computer's subnet mask.
쐂 In the lid "Other", select option 120. Then select type "Binary" and in the
Value field type "0 0 0 0" putting spaces between the zeroes. Finally click
"Add".
Figure 2: Configuration
of the DHCP Server for
Dynamic IP Leases
Shortly after you click OK, the application will provide a dynamic IP address to
the dLAN 200 DSpro adapter. Thisprocess is reflected in Wireshark as shown in
Figure 3.
The option 120 is used to disable IFCP in the DHCP response. This will prevent
that the dLAN 200 DSpro adapter tries to obtain the management VLAN from
another PLC node. In some cases, IFCP has been known to interfere with Windows XP network services.
| devolo dLAN 200 DSpro Manual |
|
Telnet to the dLAN 200 DSpro Adapter
13
Figure 3: DHCP Configuration Process
The process involves 4 steps: DHCP discover, DHCP offer, DHCP request, and
DHCP acknowledge. Discover and request are issued by the dLAN 200 DSpro
adapter, while offer and acknowledge are issued by the computer.
Once the dLAN 200 DSpro adapter has an IP address, you should be able to ping
it and telnet to it.
7
Telnet to the dLAN 200 DSpro Adapter
The dLAN 200 DSpro adapter has a console where the configuration can be
changed and checked. The console can provide useful information about the
status of the dLAN 200 DSpro adapter and the connectivity to its neighbours.
To open a telnet session to the dLAN 200 DSpro adapter, we must use a fullfeatured telnet client, such as Putty or Secure CRT. From Linux, the regular telnet
will work.
Putty is a free application that provides all of the functionality required to telnet
to the dLAN 200 DSpro adapter.Follow these steps to configure the application:
쐃 Execute the application.
쐇 In the Session section, write the IP of the dLAN 200 DSpro adapter under
"Host Name" and 40000 under "Port".
쐋 In the Terminal section, check the case "Implicit CR in every LF".
쐏 In the Terminal section, select the option "Force On" under "Local Line Editing".
| devolo dLAN 200 DSpro Manual |
14
Telnet to the dLAN 200 DSpro Adapter
|
쐄 In the Keyboard section, select "Linux" under "The function keys and keypad".
쐂 In the Telnet section, select "Passive" under "Telnet negotiation mode".
쐆 Finally, go back to Session, write a name under "Saved Sessions" and click
"Save".
Figure 4: Putty Configuration Details
Once the session is saved, click on "Open" to connect to the dLAN 200 DSpro
adapter. A window will come up with the welcome message from the dLAN 200
DSpro adapter, as shown in Figure 5.
To obtain information from the dLAN 200 DSpro adapter, type "i" at the command prompt. The dLAN 200 DSpro adapter will produce the output presented
in figure 6.
Figure 5: Welcome
Message in the Console of the Adapter
FIRMWARE VERSION
alma_dr100_ha v2_8_48_cvs running
Compiled on jue dic 2 18:34:13 CET 2004 by [email protected]
EXTRA_FLAGS=-DBPC_DEBUG -DSNR_MODE_TRAINING=1 DSNR_MODE_MONITORING=1
| devolo dLAN 200 DSpro Manual |
|
Telnet to the dLAN 200 DSpro Adapter
15
DWRONG_ACKS=1 DCOEX_ESCALABLE=1 -DNEW_BCAST DUSE_ARC_TIMER=0 -O2
Type 'h' for help
#[email protected]/>
Figure 6: General
Information Provided by the Adapter
FIRMWARE VERSION alma_dr100_ha v2_8_48_cvs running Compiled on jue dic 2 18:34:13 CET 2004 by [email protected]
EXTRA_FLAGS=-DBPC_DEBUG -DSNR_MODE_TRAINING=1 DSNR_MODE_MONITORING=1 -DWRONG_ACKS=1 - DCOEX_ESCALABLE=1
-DNEW_BCAST -DUSE_ARC_TIMER=0 -O2
Type 'h' for help
OK #[email protected]/>i
Slave Access
MAC: 00:50:C2:12:6E:13
IP: 192.168.1.2
SYNC: -MODE: 5 AGC
RX: enabled RXG = 0 AGC TX: disabled TXG
= 1
ACCESS PROTOCOL: DO_NOTHING
AUTOCONFIGURATION: DONE
AVAILABLE CONNECTIONS:
------------------------------------------------------EXTA: 100 Mbps Forwarding
------------------------------------------------------MAC PHY TX XPUTPHY RX XPUT BR STATE
------------------------------------------------------Number of boots: 32
OK #[email protected]/>
Several important things are reported with this command:
쐃 MAC mode(whether the dLAN 200 DSpro adapter is in master, slave or
repeater mode)
쐇 MAC address of the dLAN 200 DSpro adapter
| devolo dLAN 200 DSpro Manual |
16
Writing an Autoconfiguration File
|
쐋 IP address of the TCP/IP stack of the dLAN 200 DSpro adapter's processor
쐏 PLC SYC status and PLC frequency band (mode)
쐄 AGC and gain settings for transmission and reception
쐂 Access protocol status
쐆 Autoconfiguration status
쐊 Direct cable connections (EXTA or EXTB) and speed
쐎 PLC connections, reporting MAC address of the other nodes, physical Tx and
Rx speeds, and status of the bridge.
쐅 Number of boots since the last factory reset
Additional instructions concerning dLAN 200 DSpro adapter configuration
through the console are given in Section 10.
8
Writing an Autoconfiguration File
There are hundreds of parameters that can be configured in a dLAN 200 DSpro
adapter. These parameters are assigned in the configuration file, which is a
human-readable text file. The configuration file can have any name (not including spaces) and any extension. The explanation of all possible parameters is
given in Section 12.
| devolo dLAN 200 DSpro Manual |
|
Writing an Autoconfiguration File
17
For a basic network with one master and several slaves only two configuration
files are needed. The simplest configuration file for a master is shown in Figure
7. Figure 8 presents the simplest configuration file for a slave.
Figure 7: Simplest
Master Configuration
#File : master.conf
#General parameters
GENERAL_USE_AUTOCONF = yes
GENERAL_MAC_MODE = ACCESS
#Configure the node as Master (HE)
GENERAL_TYPE = HE
GENERAL_FW_TYPE = LV
GENERAL_AUTHENTICATION = none
GENERAL_STP = yes
# Signal parameters
GENERAL_SIGNAL_MODE = 6
AGC_TX_GAIN = 0
# QoS Configuration
QOS_ENABLE = no
# Vlan configuration
VLAN_ENABLE = no
Figure 8: Simplest
Slave Configuration
#File : slave.conf
#General parameters
GENERAL_USE_AUTOCONF = yes
GENERAL_MAC_MODE = ACCESS
#Configure the node as Slave (CPE)
GENERAL_TYPE = CPE
GENERAL_FW_TYPE = LV
GENERAL_AUTHENTICATION = none
GENERAL_STP = yes
# Signal parameters
AGC_TX_GAIN = 0
# QoS Configuration
QOS_ENABLE = no
# Vlan configuration
VLAN_ENABLE = no
With these two files and some configuration to the DHCP/TFTP server, a simple
one-level network can be built.
| devolo dLAN 200 DSpro Manual |
18
9
Configuring the DHCP/TFTP Server
|
Configuring the DHCP/TFTP Server
The HaneWin DHCP/TFTP server works based on profiles. For every lease there is
a profile assigned. For a basic network only two profiles are needed: a master
profile and a slave profile. The parameters that are defined in a profile are:
쎲
쎲
쎲
쎲
쎲
Netmask
Gateway
TFTP server IP
Autoconfiguration file name
DHCP extensions
Upon reception of the DHCP reply, the dLAN 200 DSpro adapter will download
the autoconfiguration file specified in the reply, from the given IP address.
The first thing you need is a basic set of autoconfiguration files. You can use the
examples provided in Section 8 as a baseline. Create a new directory and put
those two files in there.
You must then specify this directory in the DHCP application under Options >
Preferences. Then go to the "TFTP" lid and set "TFTP Root Directory" to the directory where the configuration files are, as shown in Figure 9.
The next step is creating a profile. To create the master profile follow the steps
below:
쐃 Go to Options > Manage Profiles.
쐇 Type the name of the profile (e.g. "Master") in the lower window and click
"Add". A new window will appear (see Figure 10).
쐋 In the lid "Basic Profile", set a subnet mask that is compatible with your
computer settings. As gateway, set the static IP of your computer or leave it
blank.
쐏 In the lid "Boot", type the IP of your computer under "Next Server IP
Address" and "Name". Then check the case "Always use option 66/67 for
Name and File".
쐄 In the lid "Other", select option 18 and type the name of the master's configuration file in the value field (e.g. "master.conf"). Then click "Add" to add
this option.
쐂 In the same lid, add option 120 with binary value "0 0 0 0", as described in
Section 7.
| devolo dLAN 200 DSpro Manual |
|
Configuring the DHCP/TFTP Server
19
Figure 9: Setting the
Autoconfiguration Files
Directory
Figure 10: Configuring
the Master Profile
Now repeat the same steps to create the slave profile. The only difference is the
name of the autoconfiguration file under extension 18; it must be "slave.conf".
Once you have the profiles, you can proceed to assign a profile to each of your
dLAN 200 DSpro adapters. The assignment is done based on the MAC address.
Choose one of your dLAN 200 DSpro adapters to be the master, and the rest will
be slaves.
In the main window of the HaneWin server, click the button labeled "New" in
the lower button bar. A new window will appear, as shown in Figure 11.
In this window, you must enter the MAC address of the dLAN 200 DSpro adapter, the IP that you want to assign to this dLAN 200 DSpro adapter, and the configuration profile. When you click OK, it will create an entry in the static leases
list.
| devolo dLAN 200 DSpro Manual |
20
Configuring the DHCP/TFTP Server
|
Figure 11: Assigning
an IP and a Profile to a
given Adapter (by MAC
Address)
Note that the MAC address must be typed putting a colon ":" to separate the
bytes. You cannot assign the same IP to two different dLAN 200 DSpro adapters
running at the same time.
Once you have all entered all of the dLAN 200 DSpro adapters in the list, connect the one that will become master to your computer and the rest through the
powerline. Then switch them all on and wait for the DHCP requests to appear.
At startup time, all dLAN 200 DSpro adapters behave as slaves. Then they will
search for a connection to the DHCP server, through Ethernet or PLC, and they
will finally be configured (one as master and the rest as slaves).
If everything is properly configured, the master will request an IP first and then
all of the slaves will also request an IP. The DHCP server reports the time and
date of the last request in the static leases list.
If any of the dLAN 200 DSpro adapters does not get an IP, the possible causes
are:
쐃 The MAC address is mistyped.
쐇 The dLAN 200 DSpro adapter does not have the factory default configuration.
쐋 The dLAN 200 DSpro adapter is not linked to the master.
If none of the slaves gets an IP, the probable cause is that the master was not
properly configured. If the master node does not become the master, the slaves
will never be able to find a PLC signal to link to.
| devolo dLAN 200 DSpro Manual |
|
Using the dLAN 200 DSpro Adapter Console
21
Figure 12: Static
Leases list Showing
Time and Date of
recently Configured
Node
10
Using the dLAN 200 DSpro Adapter
Console
The console of the dLAN 200 DSpro adapter is interactive and allows issuing
commands and reading outputs. The possible commands are organized in
menus and the menus are organized in a tree structure. The operation is similar
to invoking programs that are placed in different directories.
Most commands will produce some output in the console. If the command was
understood, the dLAN 200 DSpro adapter will report "OK". If the command was
wrong, the dLAN 200 DSpro adapter will report "KO". The commands are typed
at the command prompt, which looks like "#[email protected]/>".
To enter a menu, you must type the name of the menu or the short alias and
then press ENTER. For example, to enter the "network" menu, you must type
"network" or "net".
Also every command has a short name or alias. For example, instead of typing
"mode 6" you could type "m 6".
To go up to the previous menu level, you must type "..".
At any point you can type "ls" to see the list of commands available at a given
level. You can also type "help" or "h" to see additional information. There are
only two levels of directories.
There are three ways to invoke a command that is inside a submenu:
쐃 Enter the menu, and then type the command. For example, from the root
menu, type "s + ENTER" to enter the synchronization menu and then type
"m 6 + ENTER" to switch to mode 6.
| devolo dLAN 200 DSpro Manual |
22
Useful Console Commands
|
쐇 From the root menu, type the submenu name, then a space and the command name and arguments. For example, from the root menu type "s m 6
+ ENTER" to switch to mode 6.
쐋 From any place, type the absolute path: / + sub-menu name + command
name + arguments. For example, inside the mac menu, type "/s m 6 +
ENTER" to change mode without going up one level and then down into the
synchronization menu.
There are two levels of permission in the console:
쎲 User, no password
쎲 Administrator (admin), password "maxibon"
To enter the administrator level, you must type "mode admin" at the root menu
and press ENTER. The dLAN 200 DSpro adapter will ask for a password. Type
"maxibon" and press ENTER. When using Putty, the password fails the first time.
Using SecureCRT there is not such a problem.
Line editing is not allowed at the dLAN 200 DSpro adapter level. You can do
what your terminal client allows, usually copy and paste. There is no command
history and you can only type or erase at the end of the line.
11
Useful Console Commands
As user, the root level contains the following commands:
쎲 ver: Reports the firmware version running in the dLAN 200 DSpro adapter.
쎲 i: Basic status and connectivity information.
쎲 mode: Allows changing the permission level (to admin or back to user).
As administrator, there are many commands available in several submenus. The
most important features are described below.
11.1
Resetting the dLAN 200 DSpro adapter from the
Console
Type "hw rst" from root or "/hw rst" from any place.
| devolo dLAN 200 DSpro Manual |
|
11.2
Useful Console Commands
23
Showing the Table of the Bridge
The dLAN 200 DSpro adapter contains a bridge that learns the MAC addresses
and ports of all incoming packets. To see the addresses learned by the bridge,
type "/b t t". The dLAN 200 DSpro adapter will report a table with three colons.
First colon is the MAC address, second colon is the port number and third colon
is the age of the learned address.
Concerning the port numbers, the correspondence is as follows:
11.3
5
Ethernet A
6
Ethernet B (DR200 and DR300 only)
7
Internal Microprocessor
9-127
PLC Logical Ports
128
PLC Broadcast Port
Checking and Changing Gains
The AGC menu contains several commands related to the physical signal level.
The most useful command in this menu is the transmission gain control. When
two dLAN 200 DSpro adapters are very close, the transmitter may saturate the
receiver. In this case, you must change the transmission gain to 0 (default is 1).
To change the transmission gain, type "/a txg 0". If you are experiencing saturation between any two dLAN 200 DSpro adapters, you must reduce the transmission gain in both of them to obtain symmetrical behavior.
You can check the gains typing "i" at the AGC menu or the root menu.
11.4
Checking the Bits per Carrier
The quality of the channel is reflected in the number of bits per carrier (BPC) or
in its aggregate, the number of bits per symbol (BPS).
You can check the number of bits per carrier of any of the PLC ports (9 to 127)
in transmission and reception. For example, to check the BPCs in reception for
port 9, type "/bpc g rx 9". To check the BPCs in transmission for port 9, type "/
bpc g tx 9". The output of this command is a vector of numbers, each digit showing the number of bits assigned to one carrier. Values range from 2 to A (2 to
10).
| devolo dLAN 200 DSpro Manual |
24
Useful Console Commands
|
The sum of all the BPCs is the BPS. To check the BPS of port 9, for example, type
"/a bps 9".
The dLAN 200 DSpro adapter is very conservative with increasing the number of
bits per carrier. It will quickly decrease its value if a degradation of the channel
is observed, but it will take some time to return to the optimal value. To speed
up the adaptation of the BPCs, you can disable the moving average filter that
controls this process. Type "/a filter off" to force the dLAN 200 DSpro adapter to
immediately negotiate the optimal BPC value.
11.5
Changing the Boot Mode
You have two options to configure the dLAN 200 DSpro adapter: retrieve the
configuration dynamically from a server, oruse a static configuration stored in
the flash memory.
To know in which mode you are, you can type "/ac i". This will report the last
boot mode, the next boot mode, and the last known autoconfiguration file and
TFTP server from which it was downloaded.
If you want to set a static configuration in the dLAN 200 DSpro adapter, you
must issue the command "/ac bm NVRAM". You must also issue "/ac dhcp
disable" if you want static network settings. To go back to the dynamic configuration mode, type "/ac bm AUTO". All of these changes take effect when you
reboot.
If you decide to have static network settings, you have to configure it before
rebooting. Not doing so will leave the dLAN 200 DSpro adapter with an undefined IP and therefore unreachable.
11.6
Setting a Static Network Configuration
If you disabled DHCP in the autoconfiguration menu, you must set the static network settings in the network menu. You must at least set the IP of the dLAN 200
DSpro adapter and the netmask.
To set the IP of the dLAN 200 DSpro adapter, type "/net ip ip 192 168 1 1". Note
that there are spaces, not dots, between the numbers. To se the netmask of the
dLAN 200 DSpro adapter, type "/net ip nm 255 255 0 0". Finally, to set the gateway type "/net ip gw 192 168 1 252". All of the values presented above are
examples.
| devolo dLAN 200 DSpro Manual |
|
Useful Console Commands
25
If you want to check the current network configuration, type "/net ip". The dLAN
200 DSpro adapter will report its MAC address, its IP, subnet mask and gateway.
11.7
Changing the Frequency Band
In the master dLAN 200 DSpro adapter, you can set the band in which the dLAN
200 DSpro adapter will transmit. All slaves linking to this master will use the
same band. The frequency band is called "PLC mode" and its value is between
1 and 13.
You do not need to specify the PLC mode in the slave dLAN 200 DSpro adapter
because it will automatically search through all possible modes until it finds a
master.
To change the PLC mode, you must type, for example, "/s m 6" to switch to mode
6.
To change the PLC mode and make it permanent, type "/s m w 6". This will store
the mode in the flash memory and the next time the dLAN 200 DSpro adapter
boots it will start using this mode.
11.8
Changing the MAC Mode
The dLAN 200 DSpro adapter can take three different roles in the MAC protocol:
master, slave, or time division repeater (TDR).
쎲 To set the dLAN 200 DSpro adapter as a master, type "/m c n m" (stands for
"mac change node master").
쎲 To set the dLAN 200 DSpro adapter as a slave, type "/m c n s".
쎲 To set the dLAN 200 DSpro adapter as a repeater, type "/m c n r".
If you are running in static configuration mode, these changes are permanent.
The dLAN 200 DSpro adapter will start in the selected mode the next time it
boots.
| devolo dLAN 200 DSpro Manual |
26
Auto-configuration
|
12
Auto-configuration
12.1
Introduction
The following equipment is covered this document: end user CPE, intermediary
equipment of the meter room (Home Gateway, or HG), and medium voltage
equipment.
12.2
Boundary Conditions
The boundary conditions are as follows:
쐃 The network operator knows the MAC address of all equipment in the network before they are e installed in the meter rooms or on the client’s premises.
쐇 Each piece of equipment has a reserved static management IP address associated with it that is assigned by DHCP.
쐋 The network operator has stored the detailed configuration that each piece
of equipment has to receive (associated with its PLC MAC) in its Information
System prior to installation in the field. When not available, a default configuration will be utilized.
쐏 The Management VLAN of all PLC equipment of a transformer station may
be different for each transformer station, even though it will be the only one
for each transformer station. (Management VLAN is understood to be that
which all hosts of the PLC equipment access for its configuration.)
쐄 The number of data VLAN_IDs per transformer station can vary. In other
words, there can be more than one data VLAN per transformer station.
쐂 The number of voice VLAN_IDs per transformer station can vary. In other
words, there can be more than one voice VLAN per transformer station.
쐆 The equipment may not be equipped with R/W memory to store all configuration parameters.
쐊 Only the end users (CPEs) can hang in different transformer stations. However, if this CPE is not generic (meaning private VLANs or private OVLANs), it
can hang only in the correct transformer station and HG.
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
27
쐎 Adding a new non-generic CPE requires manual configuration over all HG/
LV/MV equipment. Automatic VLAN/OVLAN reconfiguration is not allowed.
쐅 Every MV node has a specific configuration file because the MV node gets
the translation table inside this file. Any LV node hanging from this MV
node gets the translation table from the MV node.
쐈 The transformer station of each HG and LV repeater is known. The HG or the
LV repeater cannot change transformer stations.
12.3
Autoconfiguration Overview
The objective of the autoconfiguration process is the centralized management of
a Wisconsin network using configuration files stored in a centralized database
that are transferred to each piece of equipment when it boots. These files contain all of the information that a node needs in order to function in a correct
manner.
Below is a brief description of the process which is discussed in more detail later
in the manual:
쐃 Every node starts with the same default factory configuration: Access CPE;
쐇 Using IFCP (explained in Section 12.4) the dLAN 200 DSpro adapter discovers if it is booting in a network with VLANs or not. If a network has been
built using VLANs to isolate traffic between data, voice over IP or management traffic, it is necessary to know the Management VLAN of that network
segment for the DHCP request to reach the backbone. The information
passed between dLAN 200 DSpro adapters during IFCP is called the translation table;
쐋 Using DHCP protocol, each node gets its IP configuration (IP address, netmask and gateway), the phone number (in the case of CPEs) and the name
of its corresponding autoconfiguration file;
쐏 Using TFTP protocol, the nodes download the autoconfiguration file and
configure the firmware accordingly.
In addition to the main steps outlined above, but there is further point to consider:
쎲 In order to achieve a secure network, powerline (PL) authentication is introduced. When a new slave is trying to access the PL network and connecting
to a master or a repeater, the master or repeater may perform a RADIUS
request to authenticate the user. The RADIUS server will reply with informa-
| devolo dLAN 200 DSpro Manual |
28
Auto-configuration
|
tion used to configure the master’s interface to the new user. However,
autoconfiguration also has a way to avoid using the RADIUS server if desired. This consists of declaring a list of MACs, profiles and FW type in the
autoconfiguration file and using this list instead of RADIUS to authenticate
the users. See Sections 12.11 and 12.13 for more information.
If the node is the first dLAN 200 DSpro adapter in the network and connected
directly through the Ethernet port to the backbone, the autoconfiguration process is different:
쐃 This node starts with the same default factory configuration: Access CPE;
쐇 Using DHCP protocol, each node gets its IP configuration (IP address, netmask and gateway) and the name of its corresponding autoconfiguration
file. There is also another parameter called ifcp-code that indicates if VLAN
is used and the value of the management VLAN if needed. Once this parameter is obtained the IFCP protocol finishes;
쐋 Using TFTP protocol, the nodes download the autoconfiguration file and
configure the firmware accordingly.
12.3.1
Autoconfiguration at dLAN 200 DSpro adapter Boot
When any node boots, there is a parameter stored in the NVRAM called
GENERAL_USE_AUTOCONF. When this value is ‘yes’, the node boots in autoconfiguration mode and when ‘no’, it boots in NVRAM mode.
There are two autoconfiguration possibilities inside the autoconfiguration boot
mode depending on whether or not IFCP is performed.
12.3.1.1
Autoconfiguration-IFCP Boot
In this autoconfiguration boot modality, the node always initiates as a slave
(CPE) and starts to send IFCP requests. When this protocol ends, the dLAN 200
DSpro adapter has the minimum information to successfully connect to the
backbone and execute DHCP and TFTP.
The node then performs a DHCP request to get an IP configuration, the phone
number (if required) and the name of the autoconfiguration file, as well as the
TFTP server where the file is located. It then downloads the file and configures
the firmware accordingly.
| devolo dLAN 200 DSpro Manual |
|
12.3.1.2
Auto-configuration
29
Autoconfiguration-noIFCP Boot
In this autoconfiguration boot modality, the dLAN 200 DSpro adapter has been
already configured (see Section 12.4 for more information) to successfully execute DHCP and TFTP so it skips IFCP.
12.3.1.3
NVRAM Boot
When a node starts in NVRAM mode, it collects all of the configured parameters
from the NVRAM memory and configures the firmware accordingly. There are
some basic parameters that are always configured in this mode:
쎲 GENERAL_TYPE: Node type – HE, CPE, or TDREPEATER.
쎲 GENERAL_IP_USE_DHCP: Use DHCP – yes or no. If this parameter is set to
no, the IP configuration parameters and the phone number are also configured from NVRAM.
All the other parameters are only configured if they have been downloaded from
a file first, and a GENERAL_USE_AUTOCONF = no line was in that autoconfiguration file. This is equivalent to performing a Save as Permanent.
12.4
IFCP Protocol
The IFCP (Inter Firmware Communication Protocol) is used to transfer the translation table between dLAN 200 DSpro adapters at booting.
Although the translation table is comprised mainly of VLAN parameters, currently there is one parameter that is not related to VLAN – the
TRANSLATION_ROOTPATH_OVLAN. In future releases, new parameters independent of VLANs may be included in the translation table. Because of this, it
is advisable not to relate the IFCP only with the use of VLANs.
When a dLAN 200 DSpro adapter boots using autoconfiguration mode with the
current FW version, it ALWAYS performs IFCP requests if a byte allocated in the
NVRAM has not been written (by default the NVRAM is set to run the IFCP client).
12.4.1
IFCP Booting
When a dLAN 200 DSpro adapter boots in autoconfiguration mode, it starts
sending IFCP requests. The dLAN 200 DSpro adapter needs to know if it is booting in a network with VLANs before requesting an IP through DHCP. For this
reason, and because the LV node does not know if communication to the MV
node is through PL or Ethernet, the FW-to-FW protocol uses a special IFCP MAC
| devolo dLAN 200 DSpro Manual |
30
Auto-configuration
|
(01:80:C2:00:00:0E) - if communication is via Ethernet the LV node does not
know the MAC of the MV node. The IFCP petitions are performed in the following steps:
쎲 Step 1: An IFCP request is made without VLANs and waits for a response;
쎲 Step 2: It then switches to VLAN mode and makes an IFCP request using tag
#1 (reserved in the Wisconsin network) and waits for a response;
쎲 Step 3: Returns to Step1.
When a node receives a packet with this IFCP MAC, the packet is sent to the FW.
In transmission, this request is forwarded to all active interfaces.
Finally it will connect to a node that will transfer the translation table. The dLAN
200 DSpro adapter switches automatically to use/not use VLANs with the same
configuration as the node sending the translation table.
In this way all dLAN 200 DSpro adapters configure themselves to use/not use
VLANs. This avoids having to write the use or non-use of VLANs in the NVRAM
of all dLAN 200 DSpro adapters, a circumstance that can be extremely frustrating if an operator wants to change the entire network to use VLANs.
A dLAN 200 DSpro adapter must not perform IFCP (Autoconfiguration-noIFCP
Boot) in the NVRAM in the following two cases:
쎲 If it is the first node of the network (directly connected to the backbone);
쎲 If it is going to receive the translation table in the autoconfiguration file.
In the first instance, this node will transfer the translation table (included in the
autoconfiguration file) to other dLAN 200 DSpro adapters when requested, but
in this case there is no other dLAN 200 DSpro adapter from which to request this
information because it will be the first node to know it.
To avoid using IFCP in the boot process, two methods are available:
쐃 Using the DHCP server (must be accessible through VLAN #1 or without
VLAN), the IFCP protocol can be skipped. In the DHCP reply, the server can
supply the dLAN 200 DSpro adapter with the management VLAN (in the
event the dLAN 200 DSpro adapter boost in VLAN mode) or tell the dLAN
200 DSpro adapter not to use VLANs;
쐇 Write a byte in the NVRAM using console. In this type of boot the dLAN 200
DSpro adapter reads its NVRAM to check if it has to use/not use VLANs and
the Management VLAN (if needed), requests an IP from the DHCP server and
finally receives its autoconfiguration file via TFTP.
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
31
The second method is not advisable, because the access to the console is poor
while using IFCP due to the change between VLAN/noVLAN modes. Method 1
should therefore be used if possible.
To disable IFCP through DHCP (method 1), see Section 12.12.
If no OVLANs/VLANs are going to be used in the network, the IFCP protocol can
be disabled in all of the dLAN 200 DSpro adapters. To disable IFCP manually
(method 2) in the next dLAN 200 DSpro adapter boot, see Section 12.14.1.3.
12.4.2
Incompatibilities
A slave using this version of firmware that is not using VLANs will not work with
a master that is using VLAN. The reason is that with the new FW version, the
slave always makes IFCP requests during booting, and because of that, LV nodes
always start their IFCP servers whether using VLANs or not. A master with a previous FW version that is not using VLANs does not start the IFCP server to answer
the requests of the slave, so it will not be able to complete this stage of the autoconfiguration.
12.5
Translation Table
The translation table contains information about the VLAN/OVLANs (in future
releases more parameters can be added) used for all nodes hanging from MV/
LV equipment. The autoconfiguration file of each piece of LV equipment is a
parametric file, which means that, for example, the LV equipment knows, using
the autoconfiguration file, that the VLAN DATA OPERATOR 1 is allowed. However the equipment needs to know what is the number of this VLAN DATA OPERATOR 1 in the LV equipment.
| devolo dLAN 200 DSpro Manual |
32
Auto-configuration
|
Figue 13: Translation
Table Example
In the example shown in Figure 13, Node A does not need any information
about translations because no LV nodes are hanging from the HV/MV substation.
Node B gets the autoconfiguration file using TFTP. In the file, Node B gets the
translations used in all LV nodes hanging from it. This translation information is
different from the translation information used by Node C and all LV nodes hanging from it.
The translation file is useful because Node D and Node F can have the same
autoconfiguration file if that is what the network operator wants. This means,
for example, that the data VLAN of Node D and Node F is DATA VLAN OPERATOR 2, but the translation table that Node D gets from Node B indicates that
DATA VLAN OPERATOR 2 is VLAN 34 and the translation table Node F gets indicates that it is VLAN 55. From the point of view of the network operator, this is
easier than having two files, one for Node D and one for Node F.
12.5.1
Transferring the Translation Table
Using the NVRAM, the MV node knows if it has to perform IFCP or not. If it does
not need to perform IFCP, the dLAN 200 DSpro adapter checks if it has to use
VLAN and the Management VLAN. Using DHCP, it knows the IP and the autoconfiguration file. Finally, using TFTP, the MV node gets the autoconfiguration
file with the translation table information inside it.
All LV nodes perform IFCP when booting (the default boot mode), but they do
not have any VLAN information in the NVRAM. For this reason, LV nodes need
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
33
this information before they request an IP through DHCP, in particular, they have
to check if they are included in a VLAN network or not. So they perform IFCP as
explained before.
As explained in Section 12.4.1, IFCP is performed in a mixed state (with VLAN
#1 and without VLAN). Finally one of the requests will succeed and the nearest
node will reply, transferring the translation table that includes:
쎲 Parameter “USE VLAN” (explained later) to fix the VLAN mode;
쎲 Parameters related to VLAN (if needed), the main one being the Management VLAN. If the parameter USE VLAN = 1, then the dLAN 200 DSpro
adapter configures itself to use the Management VLAN included in the
translation table;
쎲 Parameter “TRANSLATION_ROOTPATH_OVLAN” (explained later).
NOTE: VLAN 1 is reserved in a Wisconsin PLC network.
12.5.2
Example of a Translation Table
TRANSLATION_MNMT_VLAN = 5
TRANSLATION_DATA_VLAN.1 = 10
TRANSLATION_DATA_VLAN.2 = 11
TRANSLATION_DATA_VLAN.3 = 12
TRANSLATION_DATA_VLAN.4 = 13
TRANSLATION_DATA_VLAN.5 = 25
TRANSLATION_VOIP_VLAN.1 = 30
TRANSLATION_VOIP_VLAN.2 = 31
TRANSLATION_VOIP_VLAN.3 = 32
TRANSLATION_VOIP_VLAN.4 = 33
TRANSLATION_VOIP_VLAN.5 = 45
TRANSLATION_ROOTPATH_OVLAN = 77
The node can be configured using this information and the autoconfiguration
file. When the node receives an autoconfiguration file with the following parameter:
VLAN_DATA_TAG = %DATA2
The correct value (11) is obtained from the translation table.
| devolo dLAN 200 DSpro Manual |
34
Auto-configuration
|
There is one mandatory parameter included in the translation table that is not
configurable by the user in the autoconfiguration file, namely:
USE VLAN = [0|1]
If the dLAN 200 DSpro adapter is using VLAN the parameter will be set to 1,
otherwise the parameter will be set to 0 and this information is transferred when
it receives an IFCP request. This parameter is what the dLAN 200 DSpro adapter
performing the IFCP request uses in order to know if it has to use VLAN or not.
12.5.3
Additional Information about Transferring IFCP
Take care regarding IFCP in those cases where a dLAN 200 DSpro adapter is able
to connect with dLAN 200 DSpro adapters not belonging to its own network,
because they may have different VLAN configurations (this may occur in MV
rings or LV nodes that can communicate with MV nodes); the translation table
transferred by IFCP may be non-compatible with the real network the dLAN 200
DSpro adapter must stay in. To solve this situation (where a dLAN 200 DSpro
adapter gets IFCP from a different master than should be the case), if the autoconfiguration file downloaded by the dLAN 200 DSpro adapter includes the
translation table, this information is re-written, solving the problem. It is not a
problem that the dLAN 200 DSpro adapter has, temporarily, a wrong translation
table because with this information, the dLAN 200 DSpro adapter should be
able to reach the backbone and thus the file to download.
It should be noted that only the parameters declared explicitly in the file are
changed in the translation table; information that is not declared will retain the
same values that were received through IFCP. This should not be a problem
because if the information is not declared explicitly, it is because it will not be
used inside its network.
For example, dLAN 200 DSpro adapter “A” has its translation table with the following values and transfers this information to dLAN 200 DSpro adapter “B”:
#Translation Table dLAN 200 DSpro adapter A
TRANSLATION_MNMT_VLAN = 250
TRANSLATION_DATA_VLAN.1 = 21
TRANSLATION_DATA_VLAN.2 = 11
TRANSLATION_DATA_VLAN.3 = 12
TRANSLATION_DATA_VLAN.4 = 13
TRANSLATION_DATA_VLAN.16 = 25
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
35
TRANSLATION_VOIP_VLAN.1 = 30
TRANSLATION_VOIP_VLAN.2 = 31
TRANSLATION_VOIP_VLAN.3 = 32
TRANSLATION_VOIP_VLAN.4 = 33
TRANSLATION_VOIP_VLAN.16 = 45
TRANSLATION_ROOTPATH_OVLAN = 666
After IFCP, dLAN 200 DSpro adapter “B” downloads its file including the following translation table:
#Translation Table in the Autoconf file of dLAN 200
DSpro adapter B
TRANSLATION_MNMT_VLAN = 254
TRANSLATION_DATA_VLAN.1 = 21
TRANSLATION_DATA_VLAN.3 = 19
TRANSLATION_DATA_VLAN.4 = 1333
TRANSLATION_DATA_VLAN.16 = 22
TRANSLATION_ROOTPATH_OVLAN = 666
The translation table that the dLAN 200 DSpro adapter will then use (and the
one that will be transferred if it is requested from another node) is:
#Translation Table resulting in dLAN 200 DSpro adapter B
TRANSLATION_MNMT_VLAN = 254
TRANSLATION_DATA_VLAN.1 = 21
TRANSLATION_DATA_VLAN.2 = 11
TRANSLATION_DATA_VLAN.3 = 19
TRANSLATION_DATA_VLAN.4 = 1333
TRANSLATION_DATA_VLAN.16 = 22
TRANSLATION_VOIP_VLAN.1 = 30
TRANSLATION_VOIP_VLAN.2 = 31
TRANSLATION_VOIP_VLAN.3 = 32
TRANSLATION_VOIP_VLAN.4 = 33
TRANSLATION_VOIP_VLAN.16 = 45
| devolo dLAN 200 DSpro Manual |
36
Auto-configuration
|
TRANSLATION_ROOTPATH_OVLAN = 666
12.6
Wisconsin Nodes
In a PLC network there are several types of nodes depending on the position in
the line.
The type of node is described using the parameter
GENERAL_FW_TYPE, which indicates the role of the dLAN 200 DSpro adapter
in the network (MV, LV or EU).
쎲 MV Network: The GENERAL_FW_TYPE should be MV.
쎲 LV Network: All of them run the LV Access MAC but there are two types
depending on the role in the network:
쑗 LV Nodes: They are all dLAN 200 DSpro adapters installed in transformer stations, meter rooms, etc. They should be configured with
GENERAL_FW_TYPE equal to LV;
쑗 EU (End User) Nodes: They are the terminal nodes installed in customer
homes. The configuration of this dLAN 200 DSpro adapter is always oriented towards protection against customer actions, and this node
should be associated with a QoS profile contracted by the customer.
The configuration will be GENERAL_FW_TYPE equal to EU.
The main differences between configuring a dLAN 200 DSpro adapter as EU or
LV are the following:
쎲 Local VLAN Configuration:
쑗 The EU node will configure the Ethernet port as an ACCESS port, which
means that all traffic coming into the PLC network is untagged and the
EU dLAN 200 DSpro adapter will add the tag;
쑗 The LV node will configure the Ethernet port as a TRUNK port with a list
of allowed tags in the translation table.
쎲 Remote Profile Configuration: All EU nodes have a profile known by their
master. When a node enters the network its master asks the RADIUS server,
or its own list, in order to know the type of node and the profile assigned to
this user. If the node is a:
쑗 LV Node: The profile is not taken into account. The configuration on the
master side for this node is setting the PLC port as trunk with all of the
allowed tags in the translation table;
쑗 EU Node: The configuration on the master side for this node depends
on the profile that describes the VLAN and OVLAN allowed for this user
and the QoS configuration.
| devolo dLAN 200 DSpro Manual |
|
12.7
Autoconfiguration & Networking
12.7.1
VLAN Network
12.7.1.1
Auto-configuration
37
VLAN Network Description
The network model is described as follows:
쎲 The PLC network is a switched network with different VLAN tags;
쎲 The firmware of all nodes is inside the Management VLAN and VLAN 1. PLC
management protocols (IFCP, BPC, etc.) use VLAN 1, while high-level
management protocols (DHCP, TFTP, HTTP, NTP, SNMP, etc.) use the
management VLAN configured by the autoconfiguration procedure. The
Management VLAN may be different in different LV cells;
쎲 The end user node receives untagged traffic from the external interface and
this traffic is tagged with the correct Data VLAN according to the ISP operator that the customer belongs to. So there can be more than one Data
VLAN per LV cell;
쎲 The end user node generates traffic from VoIP tagged with the correct VoIP
VLAN according to the voice operator that the customer belongs to. So there
can be more than one VoIP VLAN per LV cell;
쎲 It is possible to add private VLANs between specific customers that do not
belong to any ISP or voice operator. In this case, VLAN trunks must be defined in the intermediary equipment in order to allow all of that tagged traffic;
쎲 All of the traffic is tagged inside the PLC network.
Each Wisconsin node must receive its VLAN configuration inside the autoconfiguration file. In addition to this, and in order to reduce the number of autoconfiguration files for end user (EU) nodes (the highest number), there will be a
translation table transferred between nodes which contains information about
the Management, Data and VoIP VLANs used in a LV cell.
12.7.2
noVLAN Network
The use of VLANs is not mandatory but is advisable for privacy reasons. Nevertheless this privacy can be implemented with different tools or if the operator
simply wants to establish a LAN.
In this kind of network, a dLAN 200 DSpro adapter will not have the problems
associated with a VLAN network. It will perform its IFCP requests, switching between VLAN #1 and not using VLAN, and finally a master will answer with the
translation table that will at least contain the parameter “USE VLAN”.
| devolo dLAN 200 DSpro Manual |
38
Auto-configuration
|
Once the dLAN 200 DSpro adapter has received the translation table and does
not need to configure anything with regards to VLANs, it can complete the following steps: DHCP, TFTP and configuration.
12.7.3
OVLAN Configuration and Root Interface
The basic OVLAN configuration in Wisconsin avoids the visibility between customers connected to the end user nodes in a simple way. All of the customer
data packets in the same LV cell are tagged with the Rootpath OVLAN. This tag
is the only allowed tag in the entire path to the backbone. In the path from the
backbone to the customers, the packets are tagged with the ALL_VLAN tag
(4095) in equipment that is connected to the backbone, and no tag is allowed
in this path. However, packets with the ALL_VLAN tag are not filtered.
An example of the basic OVLAN configuration is shown in Figure 14. OVLAN
filtering is done with egress lists. The lists are shown between {…}. The root
interfaces lists are always filled with the Rootpath OVLAN, while the other interfaces are void allowed lists (only packets with the ALL_VLAN tag are allowed).
The result is that only the depicted downstream and upstream paths are allowed.
The root interface is discovered automatically as the root port of the spanning
tree protocol, so it is mandatory to have the STP enabled for the OVLAN to
work. When a node is going to be the root node (the HE in the figure for
instance) the root interface must be specified inside the autoconfiguration file.
It will always be one of the external interfaces.
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
39
Figue 14: Basic OVLAN
Configuration Example
The following configuration must be set therefore, in all end users:
OVLAN_ENABLE = yes
OVLAN_DATA_TAG = %ROOTPATH
The node that connects to the backbone must have:
GENERAL_IFACE_ROOT = EXTA
…
OVLAN_ENABLE = yes
OVLAN_DATA_TAG = 4095
| devolo dLAN 200 DSpro Manual |
40
Auto-configuration
|
12.8
Autoconfiguration File
12.8.1
Introduction
An autoconfiguration file contains the configuration parameters needed by each
node.
In the case of MV nodes, there are no parametric values. These MV autoconfiguration files are specific for each node and contain the translation table for the
MV, LV and end user nodes hanging from each MV node. There is a particular
file for each MV node.
As stated before, LV, EU and certain MV nodes have parametric autoconfiguration files. For this reason, all EU nodes, with no specific quality of service or
VLAN/OVLAN configuration, could use the same autoconfiguration file. Thus,
LV nodes with no specific QoS or VLAN/OVLAN parameters should receive a different generic file. The network operator can use specific configuration files for
non-generic LV, EU and MV nodes.
12.8.2
Parameter Types
There are three types of parameters inside the autoconfiguration file:
쐃 Scalar: PARAMETER = value
쐇 List: PARAMTER.index1 = value
쐋 Table: PARAMETER.index1.index2 = value The first valid index for lists and
tables is 1.
12.8.3
Parameter Format
The format of the parameters is:
쎲 PARAMETER_LABEL[.x][.y] = value
For constant parameter values.
쎲 PARAMETER_LABEL[.x][.y] = %parametric_value
For parametric parameter values.
For example, the following parameter could be inside an end user autoconfiguration file:
VLAN_DATA_TAG = 452
or
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
41
VLAN_DATA_TAG = %DATA3
In the second case, the parametric value must be translated to its correct value
using the translation table.
12.8.4
Supported Parameters in the Autoconfiguration File
It is important that the order in which these parameters appear in the
autoconfiguration file is preserved.
All of the parameters that do not appear inside the autoconfiguration files keep
their default values. Parsing is case-insensitive for parameter values only (all
values except ones like the RADIUS shared secret where there is a difference between upper and lowercase letters).
12.8.4.1
General Parameters
쎲 GENERAL_USE_AUTOCONF = [yes|no]
This is the first parameter in the autoconfiguration file. When this parameter
is set to no, all of the parameters in the file are stored in the NVRAM when
the file is downloaded, and the node boots in NVRAM mode the next time.
Default value: yes.
WARNING: When the dLAN 200 DSpro adapter boots in NVRAM mode,
IFCP is not performed, so the translation table is not exchanged between
different nodes. It is mandatory to add the translation table to all files in the
network to configure the dLAN 200 DSpro adapter for booting from
NVRAM.
쎲 GENERAL_TYPE = [HE|CPE|TDREPEATER]
Configures the type of node. Default value: CPE.
쎲 GENERAL_FW_TYPE = [MV|LV|EU]
Configures the firmware type of the node. This parameter affects the QoS
and VLAN/OVLAN configuration. Default value: LV.
쎲 GENERAL_AUTHENTICATION = [RADIUS|AUTHLIST|NONE]
Authentication method:
쑗 If RADIUS is selected, a RADIUS server is in charge of accepting new
users and assigning the profile and fw_type;
쑗 If AUTHLIST is selected, authentication is done by checking a list provided in the autoconfiguration file. This option avoids the installation of
a RADIUS server;
| devolo dLAN 200 DSpro Manual |
42
Auto-configuration
|
쑗 If NONE is selected, all of the users are accepted.
Default value: NONE.
쎲 GENERAL_STP = [yes|no]
Enables/disables the Spanning Tree Protocol in the node. Default value: yes.
쎲 GENERAL_COMMON_STP_EXTA = [yes|no]
Enables/disables the Common STP feature in Ethernet interface A (EXTA). It
only makes sense to use this parameter if VLANs are enabled. If it is set to
“yes”, STP pakkets will be released and accepted through EXTA without
VLAN tags (even if VLANs are enabled). If its value is “no”, STP packets will
be released with the management VLAN tag (if VLANs are active).
WARNING: With this parameter enabled, all packets without VLAN tags will
be accepted through EXTA.
쎲 GENERAL_COMMON_STP_EXTB = [yes|no]
Same as GENERAL_COMMON_STP_EXTA but for EXTB.
쎲 GENERAL_IP_ADDRESS = <ddd.ddd.ddd.ddd>
IP address of the dLAN 200 DSpro adapter (for the next boot if DHCP is
disabled).
쎲 GENERAL_IP_NETMASK = <ddd.ddd.ddd.ddd>
IP netmask of the dLAN 200 DSpro adapter (for the next boot if DHCP is
disabled).
쎲 GENERAL_IP_GATEWAY = <ddd.ddd.ddd.ddd>
IP default gateway of the dLAN 200 DSpro adapter (for the next boot if
DHCP is disabled).
쎲 GENERAL_IP_USE_DHCP = [yes|no]
The node does/does not use DHCP for the next boot if NVRAM mode is used.
쎲 GENERAL_SIGNAL_MODE = [1-14]
In HE: Signal mode for transmitting. Mode 9 does not exist; now the same
configuration corresponds to a mode 5 submode 4.
쎲 GENERAL_SIGNAL_MODE_LIST.x = [1-14]
In CPE and TDREPEATER: The list represents the allowed signal modes used
by the Search Link to find a master. (x=1…14). CPE and TDEREPEATER
nodes that do not implement Search Link can use this parameter, but only
the last mode in the autoconfiguration file will be taken into consideration.
Default value: all modes allowed.
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
43
쎲 GENERAL_SIGNAL_POWER_MASK = 00Ffa0(…)00FF
This parameter sets the power mask. Each pair of two characters represents
the attenuation for a carrier, so this parameter is 1536x2 characters long.
Default value: 0A in all carriers.
WARNING: This power mask is only set after getting the file. When the
dLAN 200 DSpro adapter boots, it starts transmitting without power mask.
Therefore this is not a secure parameter to avoid interfering with radio-amateur transmissions.
쎲 GENERAL_SIGNAL_REG_POWER_MASK_ENABLE= [yes|no]
This parameter enables or disables the use of the Regulation Power Mask
(RPM). It is always saved in NVRAM to be used in the next boot without
need for the autoconfiguration file. The RPM notches should be previously
stored in NVRAM. By default the radio-amateur notches are stored in the
NVRAM.
쎲 GENERAL_IFACE_ROOT = [EXTA|EXTB]
Root interface assignment. The root interface is the interface where the
autoconfiguration file is received. The system automatically obtains the root
interface from the STP root port, but in some cases it must be fixed to EXTA
or EXTB (for example when the node is the STP root).
The STP bridge priority in Wisconsin dLAN 200 DSpro adapters has been
modified in the 2 bytes reserved by the standard in the following way:
쑗 0x9010 MV MASTER
쑗 0x9020 MV TDREPEATER
쑗 0x9030 LV MASTER
쑗 0x9040 LV TDREPEATER
쑗 0x9050 LV CPE
The tree topology of the STP can be affected by FD repeaters (MV or LV)
because it is compounded by a master dLAN 200 DSpro adapter. To avoid
this happening, when the parameter GENERAL_IFACE_ROOT is defined, the
2 bytes reserved will change to:
쑗 ( (MV MASTER) – 0x8) = 0x9008 for MV nodes
쑗 ( (LV MASTER) – 0x8) = 0x9028 for LV nodes
In this way, a stand-alone master will have preference over a master allocated in a FD repeater, regardless of its particular MAC.
| devolo dLAN 200 DSpro Manual |
44
Auto-configuration
|
쎲 SIGNAL_SUB_MODE = [0| 2| 4| 6]
In HE: Signal mode for transmitting. Each mode has several submodes: 0, 2,
4 and 6. 0 is the default submode and is equivalent to the current definition
of mode. The characteristic that distinguishes the submodes is that every
submode cannot communicate with a different submode from the same
mode and all submodes of a given mode occupy almost the same spectrum.
12.8.4.2
Reception and Transmission Gains Control Parameters
The following parameters must be handled with special care. A poor configuration can produce loss of communication with the dLAN 200 DSpro adapter
through PLC. Normally all of these settings are related to a SIGNAL_MODE.
Correct settings in one mode do not mean it is correct in others.
Reception Gain Parameters (Automatic Gain Control parameters)
쎲 AGC_RX_ENABLE = [0|1]
Disables/enables the HW AGC. Default value: 1.
WARNING: If the AGC is disabled, it will remain disabled, even if the signal
mode changes.
쎲 AGC_RX_FIX_GAIN = [0-7]
Fix reception gain, only valid if the HW AGC is disabled. Default value: 7.
WARNING: If the reception gain is fixed, it will remain fixed, even if the signal mode changes.
쎲 AGC_MAX_RX_GAIN = [0-7]
Fix the maximum reception gain for the HW AGC. Default value: 7.
WARNING: If the maximum reception gain is fixed, it will remain fixed, even
if the signal mode changes.
쎲 AGC_MIN_RX_GAIN = [0-7]
Fix the minimum reception gain for the HW AGC. Default value: 0.
WARNING: If the minimum reception gain is fixed, it will remain fixed, even
if the signal mode changes.
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
45
Transmission Gain Parameters (Power Control parameters)
쎲 AGC_TX_GAIN = [0|1]
Configures the transmission gain of the DSS7700. The gains are separated
in steps of 12 dB. Default value: 1.
WARNING: If the transmission gain is configured, it will remain configured,
even if the mode changes. If the AFE is different from the DS2 AFE then it
is possible to configure the AGC_TX_GAIN from 0 to 7.
쎲 POWER_CONTROL_ENABLE = [YES | NO]
It allows the node to change its transmitted power following certain rules.
The node tries to minimize the power injected into the powerline while
maintaining a good throughput with the other nodes.
WARNING: The power control is only allowed in CPEs. It must never be
used in a HE or TD repeater.
12.8.4.3
RADIUS Parameters
쎲 RADIUS_SERVER_IP = <ddd.ddd.ddd.ddd>
RADIUS server IP address.
쎲 RADIUS_SERVER_PORT = ddddd
RADIUS client UDP port.
쎲 RADIUS_SHARED_SECRET = <string>
RADIUS shared secret. It is limited to 16 characters.
All three parameters must be set up in order for the RADIUS client to work
properly.
12.8.4.4
Class of Service (CoS) Parameters
Using the autoconfiguration file, two classes of service criteria can be defined,
assigning priorities from 0 to 7.
쎲 COS_CUSTOM_CRITERION_OFFSET.i = [1-531]
Custom i-criterion frame offset, in bytes (i = 1, 2).
쎲 COS_CUSTOM_CRITERION_PATTERN.i = 0xXXXXXXXXXXXXXXXX
Custom i-criterion 8-byte pattern, in hexadecimal digits (i = 1, 2).
쎲 COS_CUSTOM_CRITERION_BITMASK.i = 0xXXXXXXXXXXXXXXX
Custom i-criterion 8-byte bitmask, in hexadecimal digits (i = 1, 2).
| devolo dLAN 200 DSpro Manual |
46
Auto-configuration
|
쎲 COS_CUSTOM_CRITERION_CLASSES_OFFSET.i = [1-531]
Custom i-criterion classes frame offset, in bytes (i = 1, 2).
쎲 COS_CUSTOM_CRITERION_CLASSES_BITMASK.i=
0xXXXXXXXXXXXXXXX
Custom i-criterion classes 8-byte bitmask, in hexadecimal digits (i = 1, 2).
쎲 COS_CUSTOM_CRITERION_CLASSES_PATTERN.i.j=
0xXXXXXXXXXXXXXXX
Custom i-criterion j-class 8-byte pattern, in hexadecimal digits (i=1, 2; j =
1…8).
쎲 COS_CUSTOM_CRITERION_CLASSES_PRIO.i.j = [0-7]
Custom i-criterion j-class priority (i=1, 2; j = 1…8).
쎲 COS_CRITERION.k = [8021p|TOS|CUSTOM1|CUSTOM2]
k-criterion definition (k = 1, 2). Assigns up to 2 criteria to classify traffic.
There are two predefined criteria (8021p based on VLAN tag priority field,
TOS IP type of service), and two custom criteria defined with the parameters
above.
쎲 COS_DEFAULT_PRIO = [0-7]
Configures the CoS default priority, that is, the priority assigned to packets
that do not match a criterion. Default value: 2.
12.8.4.5
Quality of Service (QoS) Parameters
쎲 QOS_ENABLE = [YES|NO]
This parameter enables/disables the quality of service in the node. If this
parameter is set to no, all other parameters related to QoS are not configured. Default value is NO.
쎲 QOS_PRIOACK.prio+1 = [0|1]
This list configures the Layer-2 ACK protocol depending on the priority
transmitted by the dLAN 200 DSpro adapter (can be useful for those applications with tough settings in latency but not in PLR). If several priorities
are sniffed, the policy will be fixed by the maximum priority detected. Keep
in mind that Layer-2 ACK does not use priorities. There is not an independent Layer-2 ACK for every priority. If the Layer-2 ACK is disabled for one
priority (for example, the VoIP priority to obtain better performance for voice
service), then if this priority is present in the line, the Layer-2 ACK protocol
is stopped. This means that for the period when packets with this priority
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
47
are present, the Layer-2 ACK is not used and no packets have Layer-2 ACK,
independent of their priority. Default value: 1 for all priorities.
Slave Node Parameters (CPE or REPEATER)
쎲 QOS_MAX_TXPUT_TX = xxxx (in kbps)
Configures the maximum transmission throughput for that CPE/TDREPEATER. Default value is 512 for CPEs and 4096 for TDREPEATERs.
쎲 QOS_UPBWLIMIT = [YES|NO]
In a slave, limits its own transmission. Set to YES by default in CPEs and NO
in TDREPEATERs. If disabled, the user will transmit data constantly. Every
time it receives a data token, no limit will be imposed by the slave when
transmitting data back to its master.
Master Node Parameters (HE or REPEATER)
쎲 QOS_LATENCY_STEP = [20-400] (in ms)
Configures the minimum latency step for the different slaves when using
QoS. Default value: 60.
쎲 QOS_BW_POLICY = [0|1]
Configures the policy in which the QoS manages the excess of bandwidth.
0 is fair mode and 1 is priority-based mode. Default value: 1.
쎲 QOS_LATENCY.prio+1 = [1|2|4|8]
This list configures the latency for each priority level in QOS_LATENCY_STEP
unities. Default values are:
쑗
쑗
쑗
쑗
쑗
쑗
쑗
쑗
QOS_LATENCY.1 =8
QOS_LATENCY.2 =8
QOS_LATENCY.3 =4
QOS_LATENCY.4 =4
QOS_LATENCY.5 =4
QOS_LATENCY.6 =2
QOS_LATENCY.7 =1
QOS_LATENCY.8 =8
12.8.4.6
Profile Parameters
To define a profile at least five parameters are needed. If any of them is not present, it will take the default value:
| devolo dLAN 200 DSpro Manual |
48
Auto-configuration
|
쎲 PROFILE_MAX_TXPUT_TX.i = xxxx (in kbps)
Maximum transmission throughput (from the slave point of view: upstream)
for users with profile i. Default value is 4096 for the default profile (profile
1).
쎲 PROFILE_MAX_TXPUT_RX.i = xxxx (in kbps)
Maximum reception throughput (from the EU point of view: downstream)
for users with profile i. Default value is 4096 for the default profile (profile
1).
쎲 PROFILE_PRIORITIES.i = [0x00-0xFF]
Priorities allowed for a user of profile i. Each bit represents a priority. The
default value is 0x85, so priorities 7, 2 and 0 are allowed. To include another priority, set the appropriate bit in the profile priorities flag. The maximum and minimum priorities are always set even if they are not
configured (0x81).
쎲 PROFILE_UPBWLIMIT.i = [YES|NO]
In a master or a TD repeater, limit the upstream (slave’s transmission) for
users with profile i. If disabled, the user will receive tokens constantly. Every
time the master node has transmitted all required tokens to all the slaves
with upstream bandwidth limited, then it will transmit tokens to the slaves
without upstream bandwidth limited until the rest of the slaves can receive
tokens again. Default value is NO for the default profile (profile 1).
쎲 PROFILE_DWBWLIMIT.i = [YES|NO]
In a master or a TD repeater, limit the downstream (slave’s reception) for
users with profile i. If disabled, the master node will never stop transmitting
data to that user. Every time the master node has transmitted all required
data to all slaves with downstream bandwidth limited, then it will transmit
data to the slaves without downstream bandwidth limited until the rest of
slaves can receive again. Default value is NO for the default profile (profile
1).
The following parameters can be added to the profile definition but they are
not mandatory if VLAN or OVLAN is not enabled:
쎲 PROFILE_MNMT_VLAN.i = [2-4093] | %<PARAMETRIC VALUE>
Management VLAN for that user.
쎲 PROFILE_DATA_VLAN.i = [2-4093] | %<PARAMETRIC VALUE>
Data VLAN for that user.
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
49
쎲 PROFILE_VOIP_VLAN.i = [2-4093] | %<PARAMETRIC VALUE>
VoIP VLAN for that user.
쎲 PROFILE_VLAN_ADD_TAG.i.j = [2-4093] or parametric
This parameter is of table type. For the user of profile i, up to 16 VLANs can
be defined in the filter list. When the list is ALLOWED, these tags are
added to the base configuration. Otherwise, if the list is changed to
FORBIDDEN, the base tags are removed and only the tags defined here
are included for security reasons.
쎲 PROFILE_VLAN_TAGGED_ONLY_IFACE_USER.i = [yes/no]
For the user of profile i, this parameter indicates whether or not to drop
input packets without a VLAN tag from the user with profile i (PL interface).
쎲 PROFILE_VLAN_OUTFORMAT_TAG_IFACE_USER.i = [yes/no]
For the user of profile i, this parameter indicates whether or not to send
packets with a VLAN tag to the user interface with this profile.
쎲 PROFILE_VLAN_IS_ALLOWED_IFACE_USER.i = [yes/no]
Indicates if the tags on the list are allowed or forbidden for the user with
profile i. When the list is ALLOWED the tags are added to the base configuration; when the list is FORBIDDEN, the list is reset and only tags defined
with PROFILE_VLAN_ADD_TAG will be in the list.
쎲 PROFILE_OVLAN_ADD_TAG.i.j = [2-4094] or parametric
This parameter is of table type. For the user of profile i, up to 16 OVLANs
can be defined in the filter list. When the list is ALLOWED, these tags
are added to the base configuration. Otherwise, if the list is changed
to FORBIDDEN, the base tags are removed and only the tags defined
here are included for security reasons.
쎲 PROFILE_OVLAN_TAGGED_ONLY_IFACE_USER.i = [yes/no]
For the user of profile i, this parameter indicates whether or not to drop
input packets without an OVLAN tag from the user with profile i (PL interface).
쎲 PROFILE_OVLAN_OUTFORMAT_TAG_IFACE_USER.i = [yes/no]
For the user of profile i, this parameter indicates whether or not to send
packets with a VLAN tag to the user interface with this profile.
쎲 PROFILE_OVLAN_IS_ALLOWED_IFACE_USER.i = [yes/no]
Indicates if the tags on the list are allowed or forbidden for the user with
profile i. When the list is ALLOWED the tags are added to the base confi-
| devolo dLAN 200 DSpro Manual |
50
Auto-configuration
|
guration; when the list is FORBIDDEN, the list is reset and only tags defined
with PROFILE_OVLAN_ADD_TAG will be in the list.
쎲 PROFILE_FWTYPE.i = [MV|LV|EU]
Indicates the firmware type of the user of profile i. If this parameter is not
defined, the firmware type of the RADIUS response or the authorization list
will be applied, if they are available. Otherwise, the value LV will be applied.
In the current FW version, the maximum number of profiles is 16.
12.8.4.7
Translation Table Parameters
쎲 TRANSLATION_MNMT_VLAN = [2-4093]
Translation table management VLAN tag.
쎲 TRANSLATION_DATA_VLAN.i = [2-4093]
Translation table data operator i VLAN tag. Up to 16 tags.
쎲 TRANSLATION_VOIP_VLAN.i = [2-4093]
Translation table VoIP operator i VLAN tag. Up to 16 tags.
쎲 TRANSLATION_ROOTPATH_OVLAN = [2-4094]
Translation table rootpath OVLAN.
WARNING: When the dLAN 200 DSpro adapter is going to boot in NVRAM
mode, IFCP is not performed, so the translation table is not exchanged between the different PLC nodes. It is mandatory to add the translation table
to all configuration files (MV, LV and EU) to configure any dLAN 200 DSpro
adapter for booting from NVRAM.
12.8.4.8
VLAN Parameters
쎲 VLAN_ENABLE = [yes|no]
Enables/disables the use of VLAN.
WARNING: Normally this parameter is not needed because the dLAN 200
DSpro adapter itself discovers the use of VLAN, but it is necessary in case of
booting from NVRAM.
쎲 VLAN_MNMT_TAG = [2-4093] | %<PARAMETRIC VALUE>
Management VLAN tag of high-level FW management protocols. Often
taken from the translation table.
WARNING: This parameter is mandatory to add in all autoconfiguration
files (MV, LV or EU dLAN 200 DSpro adapters) if the dLAN 200 DSpro adapters are going to boot from NVRAM after the next reset.
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
51
쎲 VLAN_MNMT_PRIO = [0-7]
Configures the VLAN priority for the high-level management (FW) packets.
쎲 VLAN_DATA_TAG = [2-4093] | %<PARAMETRIC VALUE>
Parameter for EU nodes. Configures the VLAN tag for the data packets
(packets coming from the external interfaces).
쎲 VLAN_DATA_PRIO = [0-6]
Parameter for EU nodes. Configures the VLAN priority for the data packets
(packets coming from the external interfaces).
쎲 VLAN_VOIP_TAG = [2-4093] | %<PARAMETRIC VALUE>
VLAN tag for VoIP packets (RTP and signaling). Often taken from the translation table.
쎲 VLAN_VOIP_PRIO = [0-7]
Configures the VLAN priority for the RTP packets.
쎲 VLAN_VSIG_PRIO = [0-7]Configures the VLAN priority for the VoIP signalling pakkets.
쎲 VLAN_TRUNK.i = [2-4093] Parameter for LV and MV nodes. Configures a
list of VLAN trunks different from the ones inside the translation table
that must be allowed in the node interfaces. It is necessary to configure
these trunks for private VLANs between EUs in all intermediary equipment.
쎲 VLAN_RETAG_EXTA_SRC = [0 | 2-4095]
VLAN retagging: External (Ethernet) interface A (EXTA) source tag. When a
packet comes from EXTA with a tag specified in this parameter, it is sent
through PLC with the tag specified in the VLAN_RETAG_EXTA_DST parameter. With 0, the retagging is disabled in the EXTA interface.
쎲 VLAN_RETAG_EXTA_DST = [0 | 2-4095]
VLAN retagging: External (Ethernet) interface A (EXTA) destination tag.
When a pakket coming from PLC with a tag specified in this parameter is
sent through EXTA, the tag will be changed to the tag indicated in
VLAN_RETAG_EXTA_SRC. With 0, the retagging is disabled in the EXTA
interface.
쎲 VLAN_RETAG_EXTB_SRC = [0 | 2-4095]
VLAN retagging: External (Ethernet) interface B (EXTB) source tag. When a
packet comes from EXTB with a tag specified in this parameter, it is sent
through PLC with the tag specified in the VLAN_RETAG_EXTB_DST parameter. With 0, the retagging is disabled in the EXTB interface.
| devolo dLAN 200 DSpro Manual |
52
Auto-configuration
|
쎲 VLAN_RETAG_EXTB_DST = [0 | 2-4095]
VLAN retagging: External (Ethernet) interface B (EXTB) destination tag.
When a pakket coming from PLC with a tag specified in this parameter is
sent through EXTB, the tag will be changed to the tag indicated in
VLAN_RETAG_EXTB_SRC. With 0, the retagging is disabled in the EXTB
interface.
12.8.4.9
OVLAN Parameters
The OVLAN parameters are used to configure the basic OVLAN configuration,
which avoids visibility between different customers in the access network.
쎲 OVLAN_ENABLE = [yes|no]
Enables/disables the use of OVLAN filtering. Default value is no.
쎲 OVLAN_DATA_TAG = [2-4094] | %ROOTPATH OVLAN tag assigned to
the packets coming from the external interfaces. It should be the same as
in the translation table to perform the basic OVLAN operation in all equipment except the one connected to the backbone, which will have the
ALL_VLAN tag (4095).
쎲 OVLAN_ARP_TAG_ENABLE = [ yes | no ]
If enabled, ARP packets sent by the dLAN 200 DSpro adapter are tagged
with the ROOTPATH ovlan tag. This prevents Forwarding Tables of LV equipments becoming filled with MAC addresses and overflow in very large networks (hundreds of nodes). MAC addresses learnt do not always belong to
the same branch as the overflowed dLAN 200 DSpro adapter. If the OVLAN
feature is enabled, these entries will never be used because communication
between paths other than the ROOT_PATH is forbidden. The ARP OVLAN
tag prevents the dLAN 200 DSpro adapter from learning MAC addresses
from paths other than the ROOTPATH. With this solution, it is necessary to
have a device acting as a local proxy arp in the backbone.
쎲 OVLAN_TRUNK.i = [2-4094] Parameter for LV and MV nodes. Configures
a list of OVLAN trunks different from the one inside the translation table
that must be allowed in the node interfaces. It is necessary to configure
these trunks for private OVLANs between EUs in all intermediary equipment.
12.8.4.10 Access Protocol Parameters
쎲 AP_MIN_NUMBER_HOPS = [0|1|…]
Configures the minimum number of hops to the HE from a slave. 0 means
that no extra hop must be taken to reach the HE, so the slave always con-
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
53
nects to the HE directly (if able). 1 means 1 extra hop is forced to reach the
HE, that is, the equipment will connect to a TD repeater (if able).
쎲 AP_FORBID_MASTER.i = 0xXXXXXXXXXXXX
List of forbidden masters for a given slave by MAC address.
쎲 AP_PREFER_MASTER = 0xXXXXXXXXXXXX
Preferred master for a given slave by MAC address. This parameter is useful
because the slave will try to connect to the preferred master if it is present.
If not, it will connect to any other master.
쎲 AP_FIX_MASTER = 0xXXXXXXXXXXXX
Fixed master for a given slave by MAC address. If the slave was connected
to other master, disconnects and only will connect to this FIXED master.
WARNING: This parameter can be dangerous because the slave cannot connect
to other masters.
The selection of the best master will be modified according to the four autoconfiguration parameters presented above:
쎲 If AP_FIX_MASTER is configured, this will be the only master possible for
the new node (regardless of the number of hops, reception gain, or values
of the other autoconfiguration parameters);
쎲 If AP_PREFER_MASTER is configured (and AP_FIX_MASTER is not used) the
best master selected will be the preferred master value if that selected master is detected in the network;
쎲 The list of masters of the AP_FORBID_MASTER will not be selected as best
master (they will never be adequate masters regardless of number of hops,
gain, BPS, etc.);
쎲 Masters that have a number of hops less than AP_MIN_NUMBER_HOPS
will not be selected as best master (they will never be adequate masters
regardless of gain, BPS, etc.).
The order of precedence is AP_FIX_MASTER, AP_PREFER_MASTER,
AP_FORBID_MASTER and AP_MIN_NUMBER_HOPS.
When a parameter AP_FIX_MASTER, AP_PREFER_MASTER or
AP_FORBID_MASTER is present in the downloaded autoconfiguration file,
the list of fixed, preferred and forbidden masters already configured before
this autoconfiguration operation is discarded. This implies that only complete lists of masters can be configured in each autoconfiguration operation.
The parameter AP_PREFER_MASTER (with any valid MAC address) can be
used to discard the configured list of fixed, preferred and forbidden masters.
| devolo dLAN 200 DSpro Manual |
54
Auto-configuration
|
쎲 AP_CHECK_BEST_MASTER_ENABLE = [yes|no]
Enables/disables a periodical check of the best master of the access protocol. Default value: yes.
쎲 AP_CHECK_BEST_MASTER_PERIOD = <time>
Configures the period time of the best master check. The time is in minutes.
Default value: 180.
쎲 AP_CURRENT_MASTER_MIN_BPS = <bps_thr>
Minimum bits per symbol with the current master that forces a change of
master in check best master phase. Default value: 1750.
쎲 AP_NEW_MASTER_MIN_BPS = <bps_thr>
Minimum bits per symbol with the new master that allows a change of master in check best master phase. Default value: 1750.
쎲 AP_RADIUS_UPDATE_PERIOD = [0-255]
Period of the RADIUS update process. A value of 0 means that no periodic
RADIUS update is performed. A value of [1-255] means that the RADIUS
update is performed with this period, in hours. Default value: 24.
쎲 ACCESSP_AUTHLIST_MAC.i = 0xXXXXXXXXXXXX
List of allowed MAC addresses. The length of the list is 128 (i=1…128).
쎲 ACCESSP_AUTHLIST_PROFILE.i = [1-16]
List of profiles associated to a MAC address. The length of the list is 128
(i=1…128). Default value: 1.
쎲 ACCESSP_AUTHLIST_FWTYPE.i = [MV|LV|EU]
List of FWTYPE. The length of the list is 128 (i=1…128). Default value: LV.
NOTE: This parameter is obsolete and is maintained to ensure backwards
compatibility. The firmware type of the new node should be assigned by
means of the parameter PROFILE_FWTYPE. ACCESSP_AUTHLIST_FWTYPE is
only applied if the parameter PROFILE_FWTYPE is not defined in the corresponding profile.
12.8.4.11 STP Parameters
쎲 STP_PRIO = [0-65535]
Configures the 2 bytes added to the MAC used by the STP standard to decide
the root path. Default values:
쑗 36880 = 0x9010 MV MASTER
쑗 36880 = 0x9010 MV MASTER
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
55
쑗 36896 = 0x9020 MV TDREPEATER
쑗 36912 = 0x9030 LV MASTER
쑗 36928 = 0x9040 LV TDREPEATER
쑗 36944 = 0x9050 LV CPE
쎲 STP_PORT.i = [EXTA|EXTB|PLC]
The following two parameters will be configured depending on this parameter. For instance if STP_PORT.2 = EXTA, then STP_PORT_PRIO.2 = xx and
STP_PORT_COST.2 = xxx are referred to EXTA. Only EXTA, EXTB and PLC
can be configured. If PLC is selected, the priority and cost will be changed
for ALL PLC ports.
쎲 STP_PORT_PRIO.i = [0-255]
Priority of the port (necessary if costs are equal). Default value (for ETHA,
ETHB and PLC): 80.
쎲 STP_PORT_COST.i = [0-200000000]
Cost of the port is represented by 4 bytes. It is recommended not to use a
number greaterthan 200000000 so as not to exceed the accumulated maximum of 4294967296. Default values:
쑗 ETHA = 2000000
쑗 ETHB = 2000000
쑗 PLC = 4000000
쎲 STP_HELLO_TIME = [10-100]
Hello time expressed in decisecs. Default value: 20 decisecs.
쎲 STP_MAX_AGE = [60-400]
Max. age time expressed in decisecs. Default value: 200 decisecs.
쎲 STP_FORWARD_DELAY = [40-300]
Forward delay time expressed in decisecs. Default value: 150 decisecs.
NOTE: Although values are configured in tenths of a second, the bridge has
a time resolution of 1 second. Non integer values will be correctly codified
but changes will take effect in the next integer second. For example: if a
hello time of 3.1 seconds is set, hellos are sent every 4 seconds.
쎲 STP_FRONTIER = [NONE|EXTA|EXTB]
Drops all STP packets in an external port. Default value: NONE.
쎲 STP_MODE = [STP|RSTP]
STP protocol version: Common (802.1d) or Rapid (802.1w). Default value:
RSTP.
| devolo dLAN 200 DSpro Manual |
56
Auto-configuration
|
쎲 STP_PTP_EXTA = [yes|no]
Configure the EXTA interface to be considered as point-to-point (by default
if connected through the backplane).
쎲 STP_PTP_EXTB = [yes|no]
Configure the EXTB interface to be considered as point-to-point (by default
if connected through the backplane).
12.8.4.12 MAC Ingress Filtering Parameters
쎲 MAC_INGRESS_FILTERING_ENABLE = [yes|no]
Enables the use of MAC ingress filtering. If enabled, the dLAN 200 DSpro
adapter filters by the source MAC address. If the source MAC of the frame
coming from Ethernet is not in the list, the frame is discarded. Default value:
no.
쎲 MAC_INGRESS_FILTERING_MAX_ALLOWED = [1-4]
Sets length of the MAC filtering ingress list. The maximum is 4 instead of 5
to allow the WISC MAC to be in the FW; this is done automatically. Default
value: 4.
쎲 MAC_INGRESS_FILTERING_MODE = [FIXED|AUTO]
쑗 If FIXED: Enables the INGRESS MAC FILTERING and registers the list of
MAC_INGRESS_FILTERING_FIXED_MAC (the following parameter) in
the list, up to the MAC_INGRESS_FILTERING_MAX_ALLOWED.
쑗 If AUTO: Deletes all MACs registered in the bridge associated to ETH
ports, and sets the AUTO flag. When the bridge receives a new MAC
coming from ETH, it registers it in the INGRESS_MAC_FILTERING list. If
the length of this list reaches the maximum allowed then it enables the
MAC_INGRESS_FILTERING.
쎲 MAC_INGRESS_FILTERING_FIXED_MAC.i = 0xXXXXXXXXXXXX
Only valid in FIXED mode, up to 4 MACs. If the MAX is set to lower than 4,
then only the first MACs until the length of MAX is completed are registered.
12.8.4.13 NTP Parameters
쎲 NTP_ENABLE = [enabled | disabled]
NTP feature enabled or disabled. Default value: enabled.
쎲 NTP_SERVER_IP = <ddd.ddd.ddd.ddd>
IP address of the NTP server.
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
57
쎲 NTP_TIMEZONE = [-12 - 12] * 60
Time zone for the NTP clock server. 0 corresponds to Greenwich. Default
value: 0.
쎲 NTP_DST = [yes | no]
Time correction for daylight savings time. Applied if yes. Default value: yes.
12.8.4.14 Custom VLAN/OVLAN Parameters
쎲 USE_CUSTOM_VLAN_OVLAN = [yes/no]
This parameter enables other VLAN/OVLAN parameters. Default value: no.
If set to no, the previous configuration is used. If set to yes, it will configure
the parameters that are set in the autoconfiguration file. If set to yes, the
connection will be lost if the new parameters are not properly configured in
the autoconfiguration file. It is necessary to specify several parameters with
care or no connection will be possible between the dLAN 200 DSpro adapters.
As a general rule, this configuration overrides the basic VLAN/OVLAN configuration. In order to decrease the risk of loosing the connection, the
VLAN/OVLAN filtering follows these rules:
쑗 When the list is ALLOWED, the tags specified here are added to the existing ones. This solution simplifies the configuration and decreases the
risk of misconfiguration.
쑗 When the list is FORBIDEN, the lists are reset before inserting the tags
specified here, for the same reasons.
The VLAN/OVLAN custom configuration must be complemented with the
profile parameters referring to VLAN/OVLAN to configure interfaces different from EXTA, EXTB, ROOT and OTHERS.
Custom VLAN Parameters
쎲 VLAN_FILTER_INGRESS = [yes/no]
VLAN filtering using input interface. By default only egress filtering (output
interface) is performed. Default value: no.
쎲 VLAN_TAGGED_ONLY_IFACE_ROOT = [yes/no]
Drops packets without a VLAN tag entering the root interface
(IFACE_ROOT). Default value: no.
| devolo dLAN 200 DSpro Manual |
58
Auto-configuration
|
쎲 VLAN_TAGGED_ONLY_IFACE_EXTA = [yes/no]
Drops packets without a VLAN tag entering external (Ethernet) interface A.
Default value: no.
쎲 VLAN_TAGGED_ONLY_IFACE_EXTB = [yes/no]
Drops packets without a VLAN tag entering external (Ethernet) interface B.
Default value: no.
쎲 VLAN_TAGGED_ONLY_IFACE_OTHER = [yes/no]
Drops packets without a VLAN tag entering other interfaces
(IFACE_OTHER). Default value: no.
쎲 VLAN_OUTFORMAT_TAG_IFACE_ROOT = [yes/no]
Sends packets with a VLAN tag to the root interface (IFACE_ROOT). Default
value: yes.
쎲 VLAN_OUTFORMAT_TAG_IFACE_EXTA = [yes/no]
Sends packets with a VLAN tag to external (Ethernet) interface A. Default
value: yes.
쎲 VLAN_OUTFORMAT_TAG_IFACE_EXTB = [yes/no]
Sends packets with a VLAN tag to external (Ethernet) interface B. Default
value: yes.
쎲 VLAN_OUTFORMAT_TAG_IFACE_OTHER = [yes/no]
Sends packets with a VLAN tag to other interfaces (IFACE_OTHER). Default
value: yes.
쎲 VLAN_PVID_PL = [2-4095]
802.1Q VLAN tag for tagging untagged packets from the powerline interface (PL). Default value: 0.
쎲 VLAN_PVID_EXTA = [2-4095] 802.1Q VLAN tag for tagging untagged
packets from the external interface A (EXTA). If EU, default value:
VLAN_DATA_TAG. If LV or MV, default value: 0.
쎲 VLAN_PVID_EXTB = [2-4095] 802.1Q VLAN tag for tagging untagged
packets from the external interface B (EXTB). If EU, default value:
VLAN_DATA_TAG. If LV or MV, default value: 0.
쎲 VLAN_PVID_FW = [2-4095]
802.1Q VLAN tag for tagging untagged packets from the firmware interface
(FW). Default value: 1.
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
59
쎲 VLAN_DEFAULT_PRIO_PL = [0-7]
802.1p priority for tagging untagged packets from the powerline interface
(PL). Default value: 0.
쎲 VLAN_DEFAULT_PRIO_EXTA = [0-7] 802.1p priority for tagging
untagged packets from external (Ethernet) interface A (EXTA). If EU, default
value: VLAN_DATA_PRIO. Default value: 0.
쎲 VLAN_DEFAULT_PRIO_EXTB = [0-7] 802.1p priority for tagging
untagged packets from external (Ethernet) interface B (EXTB). If EU, default
value: VLAN_DATA_PRIO. Default value: 0.
쎲 VLAN_DEFAULT_PRIO_FW = [0-7]
802.1p priority for tagging untagged packets from the firmware interface
(FW). Default prio: 0.
쎲 VLAN_IS_ALLOWED_IFACE_ROOT = [yes/no] Private VLANs list: Root
interface (IFACE_ROOT) list is an allowed tag list if YES or forbidden if NO.
Default value: yes.
쎲 VLAN_LIST_IFACE_ROOT.i = [2-4095]
Private VLANs list: Root interface (IFACE_ROOT) tag list. Up to 16 values
can be configured.
쎲 VLAN_IS_ALLOWED_IFACE_EXTA = [yes/no] Private VLANs list: External
(Ethernet) interface list is an allowed tag if YES or forbidden if NO. Default
value: yes.
쎲 VLAN_LIST_IFACE_EXTA.i = [2-4095]
Private VLANs list: External (Ethernet) interface tag list. Up to 16 values can
be configured.
쎲 VLAN_IS_ALLOWED_IFACE_EXTB = [yes/no] Private VLANs list: External
(Ethernet) interface list is an allowed tag if YES or forbidden if NO. Default
value: yes.
쎲 VLAN_LIST_IFACE_EXTB.i = [2-4095]
Private VLANs list: External (Ethernet) interface tag list. Up to 16 values can
be configured.
| devolo dLAN 200 DSpro Manual |
60
Auto-configuration
|
Custom OVLAN Parameters
쎲 OVLAN_FILTER_INGRESS = [yes/no]
OVLAN filtering using input interface. By default only egress filtering (output interface) is performed. Default value: no.
WARNING: Enabling the OVLAN ingress filtering is very dangerous
because the basic OVLAN configuration relies on avoiding ingress filtering. In the downstream interfaces, there are empty lists, which
imply that no packet will pass if ingress filtering is activated and the
OVLAN rootpath tag is not allowed. Enabling ingress filtering needs a
complete OVLAN configuration.
쎲 OVLAN_TAGGED_ONLY_IFACE_ROOT = [yes/no]
Drops packets without an OVLAN tag entering the root interface
(IFACE_ROOT).
쎲 OVLAN_TAGGED_ONLY_IFACE_EXTA = [yes/no]
Despite the name of this parameter, the meaning of it is different for Ethernet interfaces. If set to NO, drops packets with an OVLAN tag entering
external (Ethernet) interface A. If set to YES, accepts tagged packets with
an OVLAN tag. Default value: no.
쎲 OVLAN_TAGGED_ONLY_IFACE_EXTB = [yes/no]
Despite the name of this parameter, the meaning of it is different for Ethernet interfaces. If set to NO, drops packets with an OVLAN tag entering
external (Ethernet) interface B. If set to YES, accepts tagged packets with an
OVLAN tag. Default value: no.
WARNING: If the root port is an Ethernet port, the meaning of the parameter OVLAN_TAGGED_ONLY_IFACE_ROOT is the same as the parameters
described previously, OVLAN_TAGGED_ONLY_IFACE_EXTA
or
OVLAN_TAGGED_ONLY_IFACE_EXTB.
쎲 OVLAN_TAGGED_ONLY_IFACE_OTHER = [yes/no]
Drops packets without an OVLAN tag entering other interfaces
(IFACE_OTHER).
쎲 OVLAN_OUTFORMAT_TAG_IFACE_ROOT = [yes/no]
Sends packets with an OVLAN tag to the root interface (IFACE_ROOT).
Default value: yes.
쎲 OVLAN_OUTFORMAT_TAG_IFACE_EXTA = [yes/no]
Sends packets with an OVLAN tag to external (Ethernet) interface A. Default
value: yes.
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
61
쎲 OVLAN_OUTFORMAT_TAG_IFACE_EXTB = [yes/no]
Sends packets with an OVLAN tag to external (Ethernet) interface B. Default
value: yes.
쎲 OVLAN_OUTFORMAT_TAG_IFACE_OTHER = [yes/no]
Sends packets with an OVLAN tag to other interfaces (IFACE_OTHER).
Default value: yes.
쎲 OVLAN_PVID_PL = [2-4095]
OVLAN tag for tagging untagged packets from the powerline interface (PL).
Default value: 0.
쎲 OVLAN_PVID_EXTA = [2-4095]
OVLAN tag for tagging untagged packets from external interface A (EXTA).
If EU, the default value is equal to OVLAN_DATA_TAG. If LV or MV, the
default value is 0.
쎲 OVLAN_PVID_EXTB = [2-4095]
OVLAN tag for tagging untagged packets from external interface B (EXTB).
If EU, the default value is equal to OVLAN_DATA_TAG. If LV or MV, the
default value is 0.
쎲 OVLAN_PVID_FW = [2-4095]
OVLAN tag for tagging untagged packets from the firmware interface (FW).
Default value: 0.
쎲 OVLAN_IS_ALLOWED_IFACE_ROOT = [yes/no]
Private OVLANs list: Root interface (IFACE_ROOT) list is an allowed tag if YES
or forbidden if NO. Default value: yes.
쎲 OVLAN_LIST_IFACE_ROOT.i = [2-4095]
Private OVLANs list: Root interface (IFACE_ROOT) tag list. Up to 16 values
can be configured.
쎲 OVLAN_IS_ALLOWED_IFACE_EXTA = [yes/no]
Private OVLANs list: External (Ethernet) interface list is an allowed tag if YES
or forbidden if NO. Default value: yes.
쎲 OVLAN_LIST_IFACE_EXTA.i = [2-4095]
Private OVLANs list: External (Ethernet) interface tag list. Up to 16 values
can be configured.
쎲 OVLAN_IS_ALLOWED_IFACE_EXTB = [yes/no]
Private OVLANs list: External (Ethernet) interface list is an allowed tag if YES
or forbidden if NO. Default value: yes.
| devolo dLAN 200 DSpro Manual |
62
Auto-configuration
|
쎲 OVLAN_LIST_IFACE_EXTB.i = [2-4095]
Private OVLANs list: External (Ethernet) interface tag list. Up to 16 values
can be configured.
12.8.4.15 Powerline Header Parameters
쎲 PLC_HEADER_EXTA = [0-1]
쎲 Powerline header extension. Default value: 0. The two peers must be configured in the same way.
쑗 0: The PLC header is not sent/received.
쑗 1: Forces external interface A to keep the powerline header for outgoing
traffic.
쎲 PLC_HEADER_EXTB = [0-1]
Powerline header extension for interface B. Default value: 0.
NOTE: These parameters configure the PLC out format of the external interfaces. Changing these parameters on the fly can cause loss of connection
so the autoconfiguration of those parameters does not imply the use of that
configuration. The values of those parameters are stored in the NVRAM and
will be used in the next boot.
12.8.4.16 SNMP Parameters
쎲 SNMP_TRAP_IP_ADDRESS = <ddd.ddd.ddd.ddd>
Configures the IP address to which traps are sent when produced.
쎲 SNMP_TRAP_COMMUNITY_NAME = community
Configures the trap community access. This parameter is a string with maximum length 25 characters.
12.8.4.17 Multiplier Parameter
쎲 TD_MULTIPLIER = [-300, -265, -220, -190, -170, -150, -135, -125, 115, -105, -95, -85, -80, -70, -65, -60, -55, -50, -45, -40, -35, -30, 25, -20, -15, -10, -5, 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60,
65, 70, 75, 80, 85, 90, 95, 100, 105, 110, 115, 120]
Value of gain of the time domain multiplier. The values that can be configured to go from -30dB to +12dB, allowed values are shown above. The
format in which the value is read is the value in dB multiplied by 10. The
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
63
value must be divisible by 5. For example, -3.5dB will be expressed:
TD_MULTIPLIER = -35.
Each transmission mode and product has a different maxim value (higher
values are not allowed):
TX Mode
DU100
DR100
DR200 DR300
DH10EU
Other Products
1
30
50
30
20
30
2
30
50
30
20
30
3
30
50
30
20
30
4
25
50
45
20
25
5
25
50
45
20
25
6
25
50
35
20
25
7
50
80
50
20
50
8
50
80
50
20
50
9
25
50
45
20
25
10
30
50
30
20
30
11
30
55
40
20
30
12
25
50
45
20
25
13
25
50
35
20
25
14
25
50
45
20
25
15
25
25
25
25
25
16
30
30
30
30
30
쑗 Be careful to avoid saturation in the DAC.
쑗 WARNING: Be careful with positive values because if the impedance in
the line is low, a positive value can break the line driver (damage the
dLAN 200 DSpro adapter).
12.9
NVRAM
The NVRAM contains the following information, necessary before the autoconfiguration file is received:
쎲 Its own MAC address;
쎲 If required, the PLC signal bandwidth and the central frequency. This is needed if the autoconfiguration is done through PLC and the frequency band is
| devolo dLAN 200 DSpro Manual |
64
Auto-configuration
쎲
쎲
쎲
쎲
|
not a standard mode. When the firmware detects a non-standard signal
mode in the NVRAM, it creates a new mode for it and adds it to the Search
Link list with the highest priority;
A variable indicating whether working with or without VLANs, necessary
only if the IFCP client is going to be disabled, otherwise it will be discovered
by the dLAN 200 DSpro adapter itself;
A variable indicating whether the IFCP client is or is not being used;
A variable indicating whether working in autoconfiguration or NVRAM boot
mode;
MV nodes: The default Management VLAN tag value used by DHCP and
TFTP protocols. This value can be changed manually. To use this configuration the IFCP client must be disabled.
Because the MV FW has to get the translation information through TFTP, the MV
NVRAM stores the Management VLAN that this node uses to get the IP through
DHCP. Also the IFCP client has to be disabled otherwise the Management VLAN
will not be used.
Note that this tag is only mandatory when there is no other node to get the
Management VLAN tag from through IFCP protocol.
When the IFCP client is enabled, this means that the node must perform an IFCP
request to get the translation table, in the same way as the LV and EU nodes do.
All of the necessary values in the NVRAM can be modified using autoconfiguration console commands. See Section 12.14: Autoconfiguration Console for
further information.
12.10
Equipment Requirements
12.10.1
End User Equipment
End user equipment is only one chipset with two connections: one Ethernet and
one LV PL (with LV FW on the other side of the connection).
12.10.1.1 End User NVRAM
The end user node NVRAM has information about the MAC of this node and, if
necessary, the signal bandwidth and the central frequency.
12.10.1.2 End User FW: Autoconfiguration Task
The autoconfiguration task in the end user FW has the following steps:
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
65
쐃 Initially, no Ethernet interface is enabled. This node only searches for a correct band to synchronize with another node;
쐇 When the EU is synchronized with a LV node, it sends the IFCP request
packet to the PL interface to get the Management VLAN;
쐋 Using DHCP (through the Management VLAN), the node gets an IP address,
the phone number (if required) and the name of the autoconfiguration file;
쐏 Using TFTP (through the Management VLAN), the node gets the autoconfiguration file. In this autoconfiguration file, there are parameters to configure this node. Using the translation table, the autoconfiguration file is
decoded.
12.10.1.3 End User FW: Translation Transferring Task
When a packet with an IFCP MAC is received by the FW, the packet is not
handled.
12.11
Master- Side Access Protocol Tasks & User Profiles
A MV or LV master or repeater node has to look for slaves. When a new slave
is found, it can be authenticated using RADIUS protocol or automatically added
to the system if the authentication is disabled.
The master should also configure its interface to that new user in QoS and VLAN/
OVLAN terms. This configuration is done according to user profiles.
12.11.1
User Profiles
Inside a HE/TDREPEATER autoconfiguration file, there is a section with user profiles. These profiles contain the information a master needs to know to configure a port to a new user (slave) that enters the network. The information is
basically related to QoS and VLAN/OVLAN configuration.
There will always be an invited profile, profile number 1, applied to the users
with no specific profile or if the corresponding profile is not available. This invited profile, as well as the other profiles, can be redefined with autoconfiguration.
12.11.2
Working with RADIUS Authentication
When RADIUS authentication is active, the repeater or HE sends an AccessRequest message to the RADIUS server, which checks if the MAC address corre-
| devolo dLAN 200 DSpro Manual |
66
Auto-configuration
|
sponds to one that was accepted and, if that is the case, it responds with an
Access-Accept message containing the profile number as an attribute. The message can also contain the type of firmware (MV, LV or EU), but it is recommended to associate this information with the profile by means of the parameter
PROFILE_FWTYPE. Otherwise, the server replies with a RADIUS Access-Reject
message and the authentication fails.
Once authentication is achieved, the slave is authorized and a QoS and VLAN/
OVLAN configuration takes place between the master and slave. The master
uses the profile number to get these parameters. The slave uses the parameters
inside the downloaded autoconfiguration file. The slave node downloads the
file during its autoconfiguration process, after the RADIUS request on the master-side has been successful.
12.11.3
Working without RADIUS Authentication
If there is no RADIUS authentication, two ways of operation are possible.
The first one is ‘NO AUTHENTICATION’. The master will configure a default QoS
and VLAN/OVLAN configuration (the invited profile) for the slave.
The other one is the use of an ‘AUTHORIZATION LIST’.
With
‘ACCESSP_AUTHLIST_x’, up to 128 different users can be added with their related profiles and fw_type. The user is searched for in that list, and if an entry
coincides with the new user, the QoS and VLAN/OVLAN configuration related to
that entry is used for the new user. Otherwise, the user is rejected.
12.12
DHCP Support
12.12.1
DHCP Client
The nodes perform a DHCP request with extended custom options. Not only is
the basic IP configuration (IP address, netmask and gateway) requested, but the
client also requests three custom options in order to obtain the autoconfiguration file:
쎲 tftp-server-name: String with the IP address of the TFTP server.
쎲 extensions-path-name: String with the path and file name of the autoconfiguration file inside the TFTP server.
쎲 ifcp-code: 32-bit integer that represents IFCP behaviour:
쑗 0: Boot without VLANs and skip IFCP;
쑗 1: Keep on requesting IFCP (does nothing);
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
67
쑗 [2-4095]: Boot with Management VLAN = ifcp-code. Skip IFCP.
If the phone number has to be downloaded using DHCP, another custom option
should be requested:
쎲 phone-number: Text with the phone number.
12.12.2
DHCP Server
A DHCP server that supports DHCP extensions is needed in order to provide the
different Wisconsin nodes with the custom options requested.
WARNING: Although the first two custom options needed by the DHCP client
are supposed to be standard, sometimes it is necessary to define the extensionspath-name option in the header of the dhcpd.conf file. It is mandatory to define
the ifcp-code option:
option extensions-path-name
option ifcp-code
code 18 = string;
code 120 = unsigned integer 32;
It is also necessary to define the phone-number in the header of the dhcpd.conf
file if the phone number of some CPEs is to be configured via DHCP:
option phone-number code 135 = text;
WARNING: The option phone-number code number has changed from previous
versions to the same number as in MADBRIC (135).
12.12.3
DHCP Server Configuration File Example
The following is an example of the dhcpd.conf file (Linux DHCP server configuration file).
option extensions-path-name
option ifcp-code
code 18 = string;
code 120 = unsigned integer 32;
option phone-number code 135 = text;
subnet 10.10.1.0 netmask 255.255.255.0 {
default-lease-time 36000;
max-lease-time 36000;
# --- default gateway
option routers
10.10.1.1;
option subnet-mask
255.255.255.0;
| devolo dLAN 200 DSpro Manual |
68
Auto-configuration
|
option domain-name
"ds2.es";
option domain-name-servers 154.15.255.230;
option time-offset
-5; # Eastern Standard Time
range dynamic-bootp 10.10.1.30 10.10.1.55;
option nis-domain
"ds2.es";
host node1 {
hardware ethernet 00:50:C2:00:00:11;
fixed-address 10.10.1.41;
option phone-number
“961366004”;
option tftp-server-name
"10.10.1.28";
option extensions-path-name
"cpe.txt";
}
host node2 {
hardware ethernet 00:50:C2:00:00:15;
fixed-address 10.10.1.15;
option tftp-server-name
option extensions-path-name
"10.10.1.28";
"he.txt";
option ifcp-code 35;
}
host node3 {
hardware ethernet 00:50:C2:12:6b:b3;
fixed-address 10.10.1.179;
option phone-number
“961366005”;
option tftp-server-name
"10.10.1.28";
option extensions-path-name
12.13
"du100.txt"; }
RADIUS Support
Every Wisconsin master or repeater node implements a RADIUS client in order
to authenticate users (slaves) connected through the powerline to that node.
The dLAN 200 DSpro adapter acts as a NAS, which requests authentication,
gives authorization, and allocates resources.
| devolo dLAN 200 DSpro Manual |
|
12.13.1
Auto-configuration
69
RADIUS Client
The RADIUS client implemented in the Wisconsin nodes is configured through
the autoconfiguration file with three parameters:
쎲 RADIUS server IP address
쎲 RADIUS server UDP port
쎲 Shared secret password between client and server
It also sends two RADIUS standard attributes within a RADIUS request:
쎲 MAC address of the slave trying to join the network as User name.
쎲 MAC address of the master as NAS-Identifier.
12.13.2
RADIUS Server
12.13.2.1 Installing Freeradius Server (v0.8.1)
Any RADIUS server is suitable to work with the Wisconsin RADIUS clients. The
following is an example with the Linux freeradius server.
Extract the freeradius tar file, compile, and install the RADIUS server:
tar zxvf freeradius 0.8.1.tar.gz
cd freeradius 0.8.1
./configure
make
make install
The configuration RADIUS files are then installed in /usr/local/etc/raddb/ and the
log file can be seen in /usr/local/var/log/radius/radius.log.
IMPORTANT: Each time a configuration file is changed, the RADIUS server
daemon must be restarted:
killall radiusd
radiusd
12.13.2.2 Configuring Freeradius Server with DS2 Options
The RADIUS server must be configured to respond to client queries in the correct
way. It must supply the client with the following information:
쎲 Access-Accept or Access-Reject message;
쎲 Profile number. Attribute DS2-profile.
| devolo dLAN 200 DSpro Manual |
70
Auto-configuration
|
Optionally, the RADIUS server can also supply the client with the following information:
쎲 Type of firmware: MV, LV or EU. Attribute DS2-fw.
NOTE: This optional information will not be used if the parameter
PROFILE_FWTYPE is defined in the profile associated with the new user. It is
recommended to use the PROFILE_FWTYPE parameter and to not include this
information in the RADIUS response.
The first point is decided by the RADIUS standard procedures depending on the
User name and NAS-Identifier attributes sent by the client. The last two are
vendor-specific attributes (from DS2) and are defined in a new RADIUS dictionary file, dictionary.ds2, that must be included in the RADIUS server (dictionary
file in the Linux RADIUS server):
$INCLUDE dictionary.ds2
All possible clients must then be defined in the clients.conf file of the RADIUS
server. A set of clients in the same sub-network can be included in the same
declaration:
client 10.10.1.0/8 {
secret
= test
shortname
= private-network-2
}
To only use a specific RADIUS client (master), then write its IP address (without
netmask):
client 10.10.1.15 {
secret
shortname
= test
= private-network-2
}
The secret password must be the same as the one configured inside the autoconfiguration file of the Wisconsin nodes.
Finally, the file users must contain all the MAC addresses to be authenticated
with their corresponding attributes, including the USER-PASSWORD with the
value “ANONYMOUS”. The file users also gives the possibility to force the NASIdentifier. If the NAS-Identifier is defined, the user will be authenticated only if
the client that requested (the master) is the one configured in the file. Otherwise,
the user will be rejected:
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
71
0050C2000011 Auth-Type := Local, User-Password ==
"anonymous", NAS-Identifier == "0050C2000015" DS2profile = 2
To configure a dLAN 200 DSpro adapter with a special configuration if it connects to a specific master, and a default profile if it connects to other masters,
the file users can be written as follows:
DEFAULT
Fall-Through = Yes
0050C2000011 Auth-Type := Local, User-Password ==
"anonymous", NAS-Identifier == "0050C2000015"
DS2-profile = 2
0050C2000011 Auth-Type := Local, User-Password ==
"anonymous"
DS2-profile = 2
DEFAULT
Auth-Type := Reject
12.14
Autoconfiguration Console
12.14.1
Configuring Boot Mode from the Console
The boot mode can be obtained and changed through the console. Going to the
autoconfiguration menu (ac) and typing i for information (i) will give the following information:
Autoconfiguration Info ======================
...
Autoconf Boot Mode: NVRAM|AUTOCONF
Autoconf_next: NVRAM|AUTOCONF
DHCP status: enabled|disabled
Autoconf VLAN mode: ENABLED
Management VLAN: 5
...
The first line shows the current autoconfiguration boot mode. It can be AUTO
for autoconfiguration or NVRAM. The next line is only shown if the current boot
| devolo dLAN 200 DSpro Manual |
72
Auto-configuration
|
mode is AUTO, and refers to the next boot mode. For example, if a node has
been auto-configured, but the GENERAL_USE_AUTOCONF parameter of the file
was set to no, the autoconfiguration information will show:
Autoconf Boot Mode: AUTOCONF
Autoconf_next: NVRAM
The line of DHCP status only appears if in NVRAM boot mode and shows whether or not DHCP is enabled.
12.14.1.1 Boot Mode
To change the boot mode, use the bm command:
bm [AUTO|NVRAM]
To enable or disable DHCP when working in DHCP mode, use the dhcp command:
dhcp [enable|disable]
12.14.1.2 VLAN Configuration
The VLAN mode is also shown in the autoconfiguration information, and can be
enabled or disabled. When the VLAN mode is enabled, the information also
shows the management VLAN taken from the NVRAM, or the IFCP if the
management VLAN was obtained through IFCP.
To change the VLAN working mode, use the vconf command:
vconf [0|1] <mnmt_vlan_msb> <mnmt_vlan_lsb>
The first argument enables or disables the VLAN mode. Then enter the two bytes
composing the management VLAN. All of this information is stored in the
NVRAM and takes effect after rebooting the equipment.
12.14.1.3 IFCP MODE
By default the dLAN 200 DSpro adapter starts with IFCP enabled, that is, after
booting, the dLAN 200 DSpro adapter will try to get the translation table
through IFCP requests. Note that some dLAN 200 DSpro adapters should not
boot in IFCP mode (see Section 12.4: IFCP Protocol).
To disable IFCP manually in the next boot of a dLAN 200 DSpro adapter, follow
the steps below:
쎲 Using a DHCP server, give an IP to the dLAN 200 DSpro adapter; this may
take some time because, sometimes, the dLAN 200 DSpro adapter will be
sending DHCP requests with VLAN #1 and others without VLAN active;
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
73
쎲 Once the dLAN 200 DSpro adapter has an IP, log in to the console and execute the commands below (NOTE: Due to VLAN switching, the console may
seem to hang; if this occurs, log out from the console and log in again):
쑗 ac stop: Stops the autoconfiguration process (and also IFCP) and disables the VLANs. It is advisable to execute this command first to work comfortably with the dLAN 200 DSpro adapter. This command does not
write anything in the NVRAM, so it only takes effect when the dLAN 200
DSpro adapter is reset;
쑗 ac ifcpmode set 0: Disables IFCP in the next boot, writing in the
NVRAM. (“ac ifcpmode set 1” enables IFCP in the next boot, writing in
the NVRAM);
쑗 ac ifcpmode get: Checks the IFCP state for the next boot, reading the
NVRAM.
NOTE: DHCP should be used (if possible) to disable IFCP.
12.14.1.4 Configuration Show Command
To show the running or stored NVRAM configuration, use the csh command:
csh {RUN|NVRAM|?} [params_set]
To show help, execute the csh ? command.
Usage: csh {run|nvram|?} [params_set]
run : Shows the running configuration
nvram: Shows the configuration stored in NVRAM
? : Shows this help
params_set:
general:
General configuration parameters set
radius :
Radius parameters set
cos :
Class of Service parameters set
qos :
Quality of Service parameters set
profile:
Profile parameters set
transt : Translation table paramters set vlan :
VLAN parameters set
ovlan : OVLAN parameters set accessp:
tocol parameters set
Access Pro-
| devolo dLAN 200 DSpro Manual |
74
Auto-configuration
|
stp : Spanning Tree Protocol parameters set macfilt:
MAC filtering parameters set
custv : Custom VLAN parameters set
custProfv :
Custom VLAN Profile parameters set
custov : Custom OVLAN parameters set
custProfov:
agc :
Custom OVLAN profile parameters set
Automatic Gain Control parameters set
plch :
PLC Header extension parameters set
snmp :
SNMP Trap parameters set
td :
Time domain Multiplier parameter set
To get the running configuration for STP parameters, execute the csh run stp
command:
Showing running-configuration...
# - Spanning Tree Protocol Parameters Set STP_PRIO = 780
STP_PORT.1 = EXTA
STP_PORT.2 = PLC
STP_PORT.3 = EXTB
STP_PORT_PRIO.1 = 5
STP_PORT_PRIO.2 = 60
STP_PORT_PRIO.3 = 73
STP_PORT_COST.1 = 1480
STP_PORT_COST.2 = 3941
STP_PORT_COST.3 = 14
STP_HELLO_TIME = 15
STP_MAX_AGE = 250
STP_FORWARD_DELAY = 50
Any one of the parameter sets described above in the csh ? command can be
used.
To get the NVRAM-stored configuration, execute the csh nvram stp command:
Showing NVRAM-stored configuration...
| devolo dLAN 200 DSpro Manual |
|
Auto-configuration
75
# - Spanning Tree Protocol Parameters Set -
If the parameters are not stored in the NVRAM, that is ‘use_autoconf = no’, no
parameters will be shown except for the basic configuration which is needed
before the autoconfiguration process is performed. They are the following (they
are in general set): csh nvram general.
Showing NVRAM-stored configuration...
# - General Configuration Parameters Set GENERAL_USE_AUTOCONF = YES
GENERAL_TYPE = HE
GENERAL_FW_TYPE = LV
GENERAL_STP = YES
GENERAL_IP_ADDRESS = 10.0.0.101
GENERAL_IP_NETMASK = 255.0.0.0
GENERAL_IP_GATEWAY = 10.0.0.1
GENERAL_IP_USE_DHCP = NO
GENERAL_SIGNAL_MODE = 6
NOTE: The csh run all command can be copied and pasted in a new autoconfiguration file for the next time.
| devolo dLAN 200 DSpro Manual |
76
Appendix
|
13
Appendix
13.1
Technical data
dLAN 200 DSpro
Standards
쎲 Ethernet specifications IEEE 802.3, IEEE 802.3x, IEEE 802.3u
쎲 Auto MDI / X
쎲 UPA
Protocol
TDMA (Time Division Multiplex Access)
Transmission speed
200 Mbps
Frequency band
2-30 MHz
Modulation
OFDM - 1536 carriers
Data path
switchable:
쎲 Ethernet to coaxial
쎲 Ethernet to power supply grid
Range
쎲 at least 200m over household power supply grid
쎲 800m - 1500m over coaxial
Security
Setup VLANs (Virtual LAN)
QoS (Quality of Service)
Supported protocols:
쎲 IEEE 802.1 p/Q
쎲 Type of Service (ToS)
쎲 Service Classifier (CoS)
Bridging
쎲 32 active connections at the same time
쎲 MAC table with 64 entries
쎲 Packets from MAC addresses that are not listed in the MAC table are sent via broadcast
LEDs
쎲 Ethernet (10/100 Link/Act CollisionDetection)
쎲 dLAN (Link/Act)
dLAN port
Euro mains plug
Device interface
쎲 Ethernet RJ45
쎲 Coaxial
Power consumption
6W
Power supply
Integrated 110-240 V AC supply via power socket
Temperature
Storage: -25°C - 70°C
Operation: 0°C - 40°C
Ambient conditions
10-90% humidity (non-condensing)
System requirements
Ethernet port
Operating systems
All operating systems with TCP/IP support
| devolo dLAN 200 DSpro Manual |
|
Appendix
77
dLAN 200 DSpro
Design
Tabletop plastic case with wall-mount bracket
Dimensions
153 x 105 x 35 mm (height x width x depth)
Weight
243 g
Package dimensions
188 x 302 x 115 mm (height x width x depth)
13.2
Important safety instructions
It is essential to have read and understood all safety and operating instructions
before the device is used for the first time; these should then be kept safely for
future reference.
쎲 Do not open the dLAN 200 DSpro. There are no user-serviceable parts inside
the dLAN 200 DSpro.
쎲 Do not attempt to service the product yourself, call on qualified technicians
for assistance with all service tasks! There is a danger of electric shock!
쎲 Use the dLAN 200 DSpro only in a dry location.
쎲 Do not insert any objects in the openings in the dLAN 200 DSpro.
쎲 To disconnect the dLAN 200 DSpro from the power supply grid, pull out the
plug.
쎲 Do not expose the dLAN 200 DSpro to direct sunlight.
쎲 Slits and apertures in the case are intended to provide ventilation and must
not be blocked or covered.
쎲 The dLAN 200 DSpro must not be set up in close proximity to a radiator.
쎲 The dLAN 200 DSpro should only be set up in locations where adequate
ventilation is assured in accordance with the manufacturer's instructions.
쎲 Disconnect the dLAN 200 DSpro from the power supply grid before cleaning. Never use water, paint thinner, benzene, alcohol or other strong cleaning agents when cleaning the device, as these could damage the case.
Only use a slightly moist soft cloth.
쎲 The dLAN 200 DSpro should be operated exclusively on a public power supply as described on the rating plate. If you are not sure which kind of power
supply you have at home, contact your dealer or your utility company.
쎲 If the equipment is damaged, disconnect the dLAN 200 DSpro from the
mains and contact your after-sales service representative. Damage is deemed to have occurred
쑗 if the power cable or plug is damaged
| devolo dLAN 200 DSpro Manual |
78
Appendix
|
쑗 if the dLAN 200 DSpro is sprayed with liquid or if objects have got inside
the device
쑗 if the dLAN 200 DSpro has been exposed to rain or water
쑗 if the dLAN 200 DSpro does not work, despite the fact that all operating
instructions have been
쑗 followed properly
쑗 if the case of the dLAN 200 DSpro has been damaged.
13.3
CE conformity
The product conforms to the basic requirements of Directive 1999/5/EC (R&TTE)
and the other relevant provisions of the FTEG (Radio and Telecommunications
Terminal Equipment Act), and is designed for use in the EU and Switzerland.
This product is class A equipment. This equipment may cause interference with
radio waves in home use; if this occurs the operator may be required to take corrective action.
| devolo dLAN 200 DSpro Manual |
|
13.4
Appendix
79
Declaration of conformity
KONFORMITÄTSERKLÄRUNG
DECLARATION OF CONFORMITY
Hersteller:
Manufacturer:
devolo AG
Sonnenweg 11
52070 Aachen
Produkt:
devolo dLAN 200 DSpro
®
Product:
Typnummer:
MT2062
Type number:
Verwendungszweck:
PLC, Coax zu Ethernet Adapter
Intended purpose:
PLC, Coax to Ethernet Adapter
Richtlinie:
1999/5/EG (R&TTE)
Directive:
1999/5/EC (R&TTE)
Das Produkt entspricht den grundlegenden Anforderungen und Bestimmungen der
folgenden Normen und Methoden:
The product complies with the essential requirements and provisions of following standards and methods:
Sicherheitsanforderungen:
EN 60950-1:2001
Safety requirements:
Immunitätsanforderungen:
EN 55024:1998+A1:2001+A2:2003
Immunity requirements:
Emissionsanforderungen:
Emission requirements:
EN 55022:1998+A1:2000+A2:2003 (Class B)
und Expert Opinion vom Competent Body EMC
and Expert Opinion by Competent Body EMC
Diese Erklärung wird verantwortlich abgegeben durch:
This declaration is submitted by:
Aachen, 06. November 2006
th
Aachen, 6 November 2006
Heiko Harbers
Vorstandsvorsitzender
CEO
| devolo dLAN 200 DSpro Manual |
80
13.5
Appendix
|
Warranty conditions
The devolo AG warranty is given to purchasers of devolo products in addition to the warranty conditions provided by law and in accordance with the following conditions:
1
Warranty coverage
a)
The warranty covers the equipment delivered and all its parts. Parts will, at devolo's sole discretion, be replaced or repaired free of charge if, despite proven proper handling and adherence to the operating instructions, these parts became defective due to fabrication and/or
material defects. Alternatively, devolo reserves the right to replace the defective product with
a comparable product with the same specifications and features. Operating manuals and any
supplied software are excluded from the warranty.
Material and service charges shall be covered by devolo, but not shipping and handling costs
involved in transport from the buyer to the service station and/or to devolo.
Replaced parts become property of devolo.
devolo is authorized to carry out technical changes (e.g. firmware updates) beyond repair and
replacement of defective parts in order to bring the equipment up to the current technical state.
This does not result in any additional charge for the customer. A legal claim to this service does
not exist.
b)
c)
d)
2 Warranty period
The warranty period for this devolo product is three years. This period begins at the day of delivery
from the devolo dealer. Warranty services rendered by devolo do not result in an extension of the
warranty period nor do they initiate a new warranty period. The warranty period for installed
replacement parts ends with the warranty period of the device as a whole.
3
Warranty procedure
a)
If defects appear during the warranty period, the warranty claims must be made immediately,
at the latest within a period of 7 days.
In the case of any externally visible damage arising from transport (e.g. damage to the case),
the person responsible for the transportation and the sender should be informed immediately.
On discovery of damage which is not externally visible, the transport company and devolo are
to be immediately informed in writing, at the latest within 3 days of delivery.
Transport to and from the location where the warranty claim is accepted and/or the repaired
device is exchanged, is at the purchaser's own risk and cost.
Warranty claims are only valid if a copy of the original purchase receipt is returned with the
device. devolo reserves the right to require the submission of the original purchase receipt.
b)
c)
d)
4 Suspension of the warranty
All warranty claims will be deemed invalid if
a)
b)
c)
d)
e)
f)
g)
the label with the serial number has been removed from the device,
the device is damaged or destroyed as a result of acts of nature or by environmental influences
(moisture, electric shock, dust, etc.),
the device was stored or operated under conditions not in compliance with the technical specifications,
the damage occurred due to incorrect handling, especially due to non-observance of the system description and the operating instructions,
the device was opened, repaired or modified by persons not authorized by devolo,
the device shows any kind of mechanical damage,
the warranty claim has not been reported in accordance with 3a) or 3b).
| devolo dLAN 200 DSpro Manual |
|
Appendix
81
5 Operating mistakes
If it becomes apparent that the reported malfunction of the device has been caused by unsuitable
software, hardware, installation or operation, devolo reserves the right to charge the purchaser for
the resulting testing costs.
6
Additional regulations
a)
b)
The above conditions define the complete scope of devolo’s legal liability.
The warranty gives no entitlement to additional claims, such as any refund in full or in part.
Compensation claims, regardless of the legal basis, are excluded. This does not apply if e.g.
injury to persons or damage to private property are specifically covered by the product liability
law, or in cases of intentional act or culpable negligence.
Claims for compensation of lost profits, indirect or consequential detriments, are excluded.
devolo is not liable for lost data or retrieval of lost data in cases of slight and ordinary negligence.
In the case that the intentional or culpable negligence of devolo employees has caused a loss
of data, devolo will be liable for those costs typical to the recovery of data where periodic security data back-ups have been made.
The warranty is valid only for the first purchaser and is not transferable.
The court of jurisdiction is located in Aachen, Germany in the case that the purchaser is a merchant. If the purchaser does not have a court of jurisdiction in the Federal Republic of Germany
or if he moves his domicile out of Germany after conclusion of the contract, devolo’s court of
jurisdiction applies. This is also applicable if the purchaser's domicile is not known at the time
of institution of proceedings.
The law of the Federal Republic of Germany is applicable. The UN commercial law does not
apply to dealings between devolo and the purchaser.
c)
d)
e)
f)
g)
h)
13.6
Troubleshooting
The dLAN 200 DSpro has been intentionally designed to be as reliable and easy
to operate as possible. This chapter includes a few notes that are designed to
help you locate the possible fault in the event of a malfunction
쎲 The Power LED is flashing
쑗 The device is in Power Save mode. Check whether the device has an
active Ethernet connection.
쎲 The Power LED does not light up
쑗 Check that the power cable is connected properly to the power connector on the device.
쑗 Make sure that the device is connected directly to a socket, and that the
socket is live.
쑗 Try using a different socket.
| devolo dLAN 200 DSpro Manual |
82
Appendix
|
쎲 The dLAN Link/Act LED does not light up
쑗 Make sure that there is not an analog TV amplifier without back channel
or too many T-splitters between the dLAN 200 DSpro devices that
should be communicating with each other.
쑗 Try connecting two dLAN 200 DSpro with a short coaxial cable to carry
out a quick connectivity test.
쎲 The Ethernet LED does not light up
쑗 Make sure that the dLAN 200 DSpro is connected to a device with an
Ethernet port by an RJ-45 cable, and that both devices are switched on.
쎲 Safety instructions
쑗 In order to switch the device off completely, pull the power cable out of
the socket.
쑗 Never install the devices in a wet location or close to radiators/heat
sources.
쑗 Never use the device outside.
쑗 Do not remove the device case under any circumstances.
| devolo dLAN 200 DSpro Manual |
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement