Dhcp (Dynamic Host Configuration Protocol); Table 63: Bootp Options - WAGO -I/O-SYSTEM 750 XTR Manual

Fc ethernet g3 xtr fieldbus coupler ethernet; 3rd generation; extreme
Hide thumbs Also See for WAGO-I/O-SYSTEM 750 XTR:
Table of Contents

Advertisement

WAGO-I/O-SYSTEM 750 XTR
750-352/040-000 FC ETHERNET G3 XTR

Table 63: BootP Options

Option
[OPT1] Subnet mask
[OPT2] Time zone
[OPT3] Gateway
[OPT6] DNS server
[OPT12] Host name
[OPT15] Domain name
Pos : null /Serie 750 (WAGO-I/O-SYST EM)/Funktions bes chr eibung/F eldbus kommuni kation/ETHERNET /BootP - Tabelle BootP-Opti onen [OPT 42] NT P-Ser ver (750- 831, -880, -881) @ 10\mod_1298391107653_21.doc x @ 69991 @ @ 1
[OPT42] NTP server
Pos : 84 /Serie 750 ( WAGO-I/O-SYST EM)/F unktions beschr eibung/Fel dbus kommuni kati on/ETH ERNET /BootP - Ü ber die WBM-Seite "F eatur es" kann ferner ....(Restbes chr eibung) 750-880, - 881, -882 @ 9\mod_1283243412431_21.doc x @ 64373 @ @ 1
The "Features" WBM page can also be used to select the "BootP Request before
static IP" option. After the restart, 5 BootP queries are sent. If there is no
response to any of these queries, the fieldbus coupler/controller tries to configure
itself with the IP parameters saved in the EEPROM.
If you want the IP address and subnet mask are stored in the EEPROM when
using the Bootstrap protocol, then the option "use IP from EEPROM" has to be
switched (via the WBM, HTML page "Port") following the configuration via BootP.
When booting next the fieldbus coupler/controller uses the parameters saved in
the EEPROM.
By default, BootP is activated in the fieldbus coupler/controller.
When BootP is activated, the fieldbus coupler/controller expects the BootP server
to be permanently available.
If there is no BootP server available after a PowerOn reset, the network will
remain inactive.
If there is an error in the saved parameters, the I/O LED reports a blink code and
configuration via BootP is turned on automatically.
Pos : 85 /Serie 750 ( WAGO-I/O-SYST EM)/F unktions beschr eibung/Fel dbus kommuni kati on/ETH ERNET /DHCP (D ynamic H ost Configur ati on Pr otocol) ( 750-880, - 881, -882) @ 7\mod_1265297441531_21.doc x @ 49809 @ 4 @ 1
11.1.2.2

DHCP (Dynamic Host Configuration Protocol)

The fieldbus coupler/controller internal HTML page opened via the "Port" link
provides the option to configure the network using the data saved in the
EEPROM or via DHCP instead of via the BootP protocol.
DHCP (Dynamic Host Configuration Protocol) is a further development of BootP
and is backwards compatible with BootP.
Both BOOTP and DHCP assign an IP address to the fieldbus node (Client) when
starting; the sequence is the same as for BootP.
For configuration of the network parameters via DHCP, the fieldbus
coupler/controller sends a client request to the DHCP server e.g., on the
connected PC.
A broadcast request is transmitted to Port 67 (DHCP server) via the protocol that
contains the hardware address (MAC ID) for the fieldbus coupler/controller.
Meaning
32-bit address mask that displays which bits of the IP address
identify the network and which identify the network stations.
Time difference between the local time and the UTC (Universal
Time Coordinated).
IP address of the router that permits access to other networks.
IP address of the name servers that converts a name into an IP
address. Up to 2 DNS servers can be configured.
The name of the host is the unique name of a computer in a
network. The host name can contain up to 32 characters.
The name of the domain is the unique name of a network. The
domain name can contain up to 32 characters.
IP address of the Network Time Server. This address is only
accepted if the protocol "SNTP" is enabled via the WBM.
Fieldbus Communication 145
Version 1.3.0
Manual

Advertisement

Table of Contents
loading

This manual is also suitable for:

750-352/040-000

Table of Contents