Theben 9070771, Product Manual

Page: 25 / 29

IPsecure Interface KNX
Planning and application
27
4 Planning and application
4.1 The IPsecure Interface in the network
The IPsecure Interface is designed for use in 10/100 BaseT networks compliant to IEEE 802.3. The device features
an AutoSensing function and sets the baud rate (10 or 100 Mbit) automatically.
4.1.1 Assignment of IP address
DHCP/AutoIP
The IP address of the device can be received from a DHCP server. This requires setting automatic IP address
assignment in ETS, see parameter window IP settings . If no DHCP server is found with this setting, the device
starts an AutoIP procedure and autonomously assigns itself an IP address from the range 169.254.xxx.yyy.
The IP address that the device receives (via DHCP or AutoIP) during startup will be retained until
• the next reboot (switching off/on or reprogramming).
• a DHCP server is available
•
the DHCP lease expires
No DHCP server is available during startup
If no DHCP server is available during startup of the IP Interface Secure, the device will assign itself an AutoIP
address. The Interface then cyclically (three telegrams at intervals of 3 seconds, followed by a pause of 20
seconds) searches for a DHCP server. As soon as a server is available again, the address assigned by the DHCP
server is used.
DHCP server fails (device has already received IP address from DHCP)
Each IP address assigned by a DHCP has a validity time for use (lease time). This validity time is extended prior to
expiry by means of a request from the device to the DHCP server. If the device’s validity time for use is not
extended, the device searches for an AutoIP address after expiry of the validity time.
Static IP address
If the IP address of the IPsecure Interface KNX is to have a fixed assignment, a static IP address (as well as a
subnet mask and a default gateway) can be set in ETS, see parameter window
IP settings .
If no default gateway is available, the value must be set to 0.0.0.0.
4.1.2 Monitoring an IPsecure Interface KNX
If the device is to be monitored by a Visualisation that maintains a tunneling connection to the device, the active
tunneling connection should be used for monitoring.
If the device is to be monitored by a Monitoring Unit, monitoring should take place for the device address and not
for one of the tunneling connections.