So, ich kann nun mit ein paar Logs und Mitschnitten dienen.
In der Version hat sich ja einiges getan, wie ich aus einem LDAP-Diff herauslesen konnte:
jetzt:
dn: univentionAppID=dhcp-server_10.0.1,cn=dhcp-server,cn=apps,cn=univention,
vorher:
dn: univentionAppID=dhcp-server_8,cn=dhcp-server,cn=apps,cn=univention,dc=
Das Verhalten ist eben wie oben beschrieben:
Der Client holt sich eine IP vom Master (erster tcpdump-Mitschnitt). Dann fällt der Master aus. (zumindest der DHCP-Dienst)
Wenn dann am Client ein renew gemacht wird, sieht man nur am Master Traffic und natürlich dass auf dem entsprechenden Port niemand lauscht. (2. Mitschnitt)
Macht man nun ein Release am Client, teilt er dies ebenfalls dem nicht laufenden Master mit (3.) - der das aber natürlich nicht mitkriegt.
Ein anschließender Renew geht dann auf beide Server und am Backup geht ein erfolgreiches DHCPACK raus. (4.+5.)
1. Master: dhcp läuft, Client bekommt IP, Backup: kein Traffic
09:44:34.944608 IP notebook22.buero.company.com.bootpc > ucs-master.buero.company.com.bootps: BOOTP/DHCP, Request from 74:2b:62:8b:9e:c0 (oui Unknown), length 324
09:44:34.965361 IP ucs-master.buero.company.com.bootps > notebook22.buero.company.com.bootpc: BOOTP/DHCP, Reply, length 300
2. Master: dhcp offline, Am Client: renew, Backup: kein Traffic
09:46:02.302927 IP notebook22.buero.company.com.bootpc > ucs-master.buero.company.com.bootps: BOOTP/DHCP, Request from 74:2b:62:8b:9e:c0 (oui Unknown), length 324
09:46:02.303050 IP ucs-master.buero.company.com > notebook22.buero.company.com: ICMP ucs-master.buero.company.com udp port bootps unreachable, length 360
09:46:05.297356 IP notebook22.buero.company.com.bootpc > ucs-master.buero.company.com.bootps: BOOTP/DHCP, Request from 74:2b:62:8b:9e:c0 (oui Unknown), length 324
09:46:05.297456 IP ucs-master.buero.company.com > notebook22.buero.company.com: ICMP ucs-master.buero.company.com udp port bootps unreachable, length 360
09:46:13.299495 IP notebook22.buero.company.com.bootpc > ucs-master.buero.company.com.bootps: BOOTP/DHCP, Request from 74:2b:62:8b:9e:c0 (oui Unknown), length 324
09:46:13.299586 IP ucs-master.buero.company.com > notebook22.buero.company.com: ICMP ucs-master.buero.company.com udp port bootps unreachable, length 360
3. Master: Am Client: release, Backup: kein Traffic
09:47:54.186992 IP notebook22.buero.company.com.bootpc > ucs-master.buero.company.com.bootps: BOOTP/DHCP, Request from 74:2b:62:8b:9e:c0 (oui Unknown), length 300
09:47:54.187106 IP ucs-master.buero.company.com > notebook22.buero.company.com: ICMP ucs-master.buero.company.com udp port bootps unreachable, length 336
4. Master: Am Client: renew (nach release)
09:48:14.543134 IP notebook22.buero.company.com.bootps > ucs-master.buero.company.com.bootps: BOOTP/DHCP, Request from 74:2b:62:8b:9e:c0 (oui Unknown), length 300
09:48:14.543236 IP ucs-master.buero.company.com > notebook22.buero.company.com: ICMP ucs-master.buero.company.com udp port bootps unreachable, length 336
09:48:14.543263 IP notebook22.buero.company.com.bootps > ucs-master.buero.company.com.bootps: BOOTP/DHCP, Request from 74:2b:62:8b:9e:c0 (oui Unknown), length 300
09:48:14.543278 IP ucs-master.buero.company.com > notebook22.buero.company.com: ICMP ucs-master.buero.company.com udp port bootps unreachable, length 336
5. Backup: Am Client: renew (nach release)
09:48:14.543627 IP notebook22.buero.company.com.bootps > ucs-backup.buero.company.com.bootps: BOOTP/DHCP, Request from 74:2b:62:8b:9e:c0 (oui Unknown), length 300
09:48:14.543717 IP notebook22.buero.company.com.bootps > ucs-backup.buero.company.com.bootps: BOOTP/DHCP, Request from 74:2b:62:8b:9e:c0 (oui Unknown), length 300
09:48:14.544479 IP ucs-backup.buero.company.com.bootps > notebook22.buero.company.com.bootpc: BOOTP/DHCP, Reply, length 300
09:48:14.544824 IP ucs-backup.buero.company.com.bootps > notebook22.buero.company.com.bootpc: BOOTP/DHCP, Reply, length 300
09:48:14.545045 IP dc01.buero.company.com.domain > ucs-backup.buero.company.com.33352: 27200* 2/0/0 PTR notebook22.buero.company.com., PTR notebook03.buero.company.com. (110)
Ausschnitte aus der daemon.log:
Apr 13 09:45:48 ucs-backup dhcpd: peer failover-partner: disconnected
Apr 13 09:45:48 ucs-backup dhcpd: failover peer failover-partner: I move from normal to communications-interrupted
Apr 13 09:48:09 ucs-backup dhcpd: DHCPOFFER on 10.2.1.102 to 74:2b:62:8b:9e:c0 via 10.2.1.253
Apr 13 09:48:09 ucs-backup dhcpd: DHCPDISCOVER from 74:2b:62:8b:9e:c0 via 10.2.1.254
Apr 13 09:48:09 ucs-backup dhcpd: DHCPOFFER on 10.2.1.102 to 74:2b:62:8b:9e:c0 via 10.2.1.254
Apr 13 09:48:10 ucs-backup dhcpd: Dynamic and static leases present for 10.2.1.102.
Apr 13 09:48:10 ucs-backup dhcpd: Remove host declaration NOTEBOOK22 or remove 10.2.1.102
Apr 13 09:48:10 ucs-backup dhcpd: from the dynamic address pool for 10.2.1.0/24
Apr 13 09:48:10 ucs-backup dhcpd: DHCPREQUEST for 10.2.1.102 (10.1.1.205) from 74:2b:62:8b:9e:c0 via 10.2.1.253
Apr 13 09:48:10 ucs-backup dhcpd: DHCPACK on 10.2.1.102 to 74:2b:62:8b:9e:c0 via 10.2.1.253
Apr 13 09:48:10 ucs-backup dhcpd: Dynamic and static leases present for 10.2.1.102.
Apr 13 09:48:10 ucs-backup dhcpd: Remove host declaration NOTEBOOK22 or remove 10.2.1.102
Apr 13 09:48:10 ucs-backup dhcpd: from the dynamic address pool for 10.2.1.0/24
Apr 13 09:48:10 ucs-backup dhcpd: DHCPREQUEST for 10.2.1.102 (10.1.1.205) from 74:2b:62:8b:9e:c0 via 10.2.1.254
Apr 13 09:48:10 ucs-backup dhcpd: DHCPACK on 10.2.1.102 to 74:2b:62:8b:9e:c0 via 10.2.1.254
Apr 13 09:48:14 ucs-backup dhcpd: DHCPINFORM from 10.2.1.102 via 10.2.1.254
Apr 13 09:48:14 ucs-backup dhcpd: DHCPACK to 10.2.1.102 (74:2b:62:8b:9e:c0) via eth0
Gibt es Ideen dazu? Etwas das ich prüfen noch kann?
LG,
Roland.