Auto-configuration
|
|
devolo dLAN 200 DSpro Manual
|
32
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 substa-
tion.
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 han-
ging 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 OPERA-
TOR 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 indi-
cates 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 auto-
configuration 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
Summary of Contents for dLAN 200 DSpro
Page 1: ...dLAN 200 DSpro Manual...
