DIVUS HEARTBEAT user manual .
10
2.1.2
ISOLATED NETWORK SCHEME
So, what happens when the network has no router in the beginning but one will
be connected later on?
1.
All the steps of the quick start guide should be followed. (All devices are connected, the first setup
procedure on the DIVUS HEARTBEAT is completed by the network scan)
2.
In this situation, the DIVUS SECURE intranet and the RESIDENTIAL INTERCOM are fully functional (except,
of course, the online services).
3.
Automatically detecting that there is no router active, the DIVUS HEARTBEAT will take control of the
a.
role
b.
Through DHCP and NETBIOS/WINS, it will assign IP addresses and names to the devices and
make sure that special devices (e.g. a DIVUS KNX SERVER) are reachable from anywhere.
4.
To open additional communication channels to/for custom devices, you can use special pre-sets or
define your own new rules. See chapters 3.14, 6.5, 6.6 for details.
At this point, an isolated system is ready to be used. A system where a router will follow in the future can
also work with this configuration without any problems.
When the router is finally installed and connected, what happens to a previously
configured system with a DIVUS HEARTBEAT?
When the router is connected to the DIVUS HEARTBEAT:
•
The DIVUS HEARTBEAT detects the new device and its roles
•
The DIVUS HEARTBEAT will pass the general network management roles to the newcomer:
o
DHCP server role is passed to the router. This means that all the DHCP addresses leased will
be renewed by another server which might also move all the devices to a completely different
network.
