Architecture and strategies
Networks
U41855-J-Z125-3-76
33
D
ok
us
ch
a
bl
on
en 1
9x
24 V
e
rs
ion 7.
4
de f
ür
F
ram
e
M
ak
er
V
7.
x
vo
m
09
.0
2.
20
10
©
c
og
ni
ta
s Gm
b
H
20
01
-20
10
19
. M
ar
ch
201
8 S
ta
nd 18
:2
5.
47
P
fad
: P
:\F
T
S
-B
S
\S
er
ve
r\
S
E
-S
er
ve
r\
S
E
-D
ok
u\
13
039
12
_B
uV
_0
62
\B
u
V
_
e\
bu
v.
k0
2
Figure 2: Block diagram of the Net Unit
2.3.1 Services
2.3.1.1
IPv6 autoconfiguration
IPv6 autoconfiguration based on the "radvd" (Router Advertisement Daemon) which runs
on the MU is provided for communication in the MCNPR network segment. Optionally IPv6
autoconfiguration is also provided for the private network segments MONPR and DANPR.
The prefix "fd5e:5e5e:<vlan-id>:0::/64" (for MCNPR where vlan-id 600 =
fd5e:5e5e:600:0::/64) is preconfigured. When conflicts occur on the customer side,
Customer Support can set a different prefix (change the first 32 bits of the prefix).
Connected units (with enabled IPv6 autoconfiguration) are then assigned an IPv6 address
based on the MAC address (e.g. fd5e:5e5e:600:0:219:99ff:fee2:79d/64).
IPv6 autoconfiguration is automatically enabled for MCNPR by means of the installation
and is required for the management functions for the units. IPv6 autoconfiguration can
optionally be activated for private network segments.
Each MU is assigned its own static IPv6 address during configuration in MCNPR (e.g.
fd5e:5e5e:600::101/64 = IPv6 suffix <mu-id>0<se-id>) with which the MU in the
network segment can be addressed.
Summary of Contents for BS2000
Page 12: ...Content U41855 J Z125 3 76 ...
Page 102: ...Working with the SE Manager Operating the SE Manager 100 U41855 J Z125 3 76 ...
Page 296: ...Managing energy settings Managing hardware 294 U41855 J Z125 3 76 ...
Page 300: ...Managing an SU Cluster Managing a cluster 298 U41855 J Z125 3 76 ...
Page 332: ...Alarm management Managing logging functions 330 U41855 J Z125 3 76 ...
Page 356: ...Working with EMDS Appendix 354 U41855 J Z125 3 76 ...
Page 366: ...Related publications 364 U41855 J Z125 3 76 ...