CARP Problem

Started by Sven-J, February 17, 2019, 10:45:08 PM

Previous topic - Next topic
Moin zusammen,

solangsam bin ich mit meinem Latein am Ende.

Folgende Situation:

2x DL360p Gen8 als Firewall OPNsense 19.1 installiert

LAGG / LACP für folgende Interface Konfiguriert: bge0 / bge1 (WAN)
bxe0 / BXE1 - Trunk und zig vlans Konfiguriert

WAN mit meinem Transfernetz konfiguriert
Allen interfacen auf beiden Nodes jeweils 251 Node 1 und 252 Node 2, CARP IPs immer die 254 bzw. die .142.178 als CARP für das WAN.

HA ist auf einem eigenen Interface direkt mit dem anderen Node verbunden, das funktioniert auch.

Nur ich bekomme immer folgenden Fehler:

CARP has detected a problem and this unit has been demoted to BACKUP status.
Check link status on all interfaces with configured CARP VIPs.

Und ich weiß einfach nicht WO?! Gibts irgendwie ne möglichkeit herauszufinden welches Problem er denn hat?

Danke !

Viele Grüße
Sven-Jendrik

Überprüfe in Interfaces : Overview ob bei allen Interfaces die Zuordnung gleich ist, also z.B. vlan100 auf beiden Maschinen opt60

Quote from: mimugmail on February 18, 2019, 06:06:37 AM
Überprüfe in Interfaces : Overview ob bei allen Interfaces die Zuordnung gleich ist, also z.B. vlan100 auf beiden Maschinen opt60

Moin hab ich, passt alles :!

Verwendest du IP Alias zusätzlich zu CARP Adressen?

Quote from: mimugmail on February 18, 2019, 08:47:35 AM
Verwendest du IP Alias zusätzlich zu CARP Adressen?

Nope only CARP Adressen

Bei VIP Status, wie ist bei beiden der Status?

Falsche Werte bei "VHID Group" und "Advertising Frequency" könnten auch die Ursache sein.
Poste die doch mal (bei Firewall: Virtual IPs: Settings).

Quote from: bewue on February 18, 2019, 11:06:59 AM
Falsche Werte bei "VHID Group" und "Advertising Frequency" könnten auch die Ursache sein.
Poste die doch mal (bei Firewall: Virtual IPs: Settings).

Kann man das irgendwie auch per Shell ausgeben? dann ist es einfacher zu Poste


Wenn bei einem alle master und beim anderen alle backup sind dann passt's doch?

Quote from: mimugmail on February 18, 2019, 06:39:46 PM
Wenn bei einem alle master und beim anderen alle backup sind dann passt's doch?

Ja aber ich kriege trotzdem folgenden Fehler:

CARP has detected a problem and this unit has been demoted to BACKUP status.
Check link status on all interfaces with configured CARP VIPs.

Aber da fehlt doch der Kontext vom Log. Kann doch sein dass CARP gestartet hat und dann per DHCP am WAN das Interface resettet wird, das produziert z.B. so eine Meldung.

Quote from: mimugmail on February 18, 2019, 09:30:44 PM
Aber da fehlt doch der Kontext vom Log. Kann doch sein dass CARP gestartet hat und dann per DHCP am WAN das Interface resettet wird, das produziert z.B. so eine Meldung.

Wo finde ich diesen Log?

system.log .. guck mal ins Wiki und such nach logging

February 18, 2019, 11:17:48 PM #14 Last Edit: February 18, 2019, 11:27:53 PM by Sven-J
Master nach einem Reboot:
Feb 18 22:00:50 DEHAM01-FW01 kernel: carp: 2@lagg1_vlan10: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:00:50 DEHAM01-FW01 kernel: carp: 4@lagg1_vlan42: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:00:50 DEHAM01-FW01 kernel: carp: 6@lagg1_vlan44: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:00:50 DEHAM01-FW01 kernel: carp: 3@lagg1_vlan40: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:00:50 DEHAM01-FW01 kernel: carp: 5@lagg1_vlan43: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:00:50 DEHAM01-FW01 kernel: carp: 7@lagg1_vlan150: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:00:50 DEHAM01-FW01 kernel: carp: 10@lagg1_vlan1002: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:00:50 DEHAM01-FW01 kernel: carp: 9@lagg1_vlan1001: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:00:50 DEHAM01-FW01 kernel: carp: 11@lagg1_vlan1003: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:00:50 DEHAM01-FW01 kernel: carp: 8@lagg1_vlan1000: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:00:50 DEHAM01-FW01 kernel: carp: 13@lagg1_vlan1020: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:00:50 DEHAM01-FW01 kernel: carp: 16@lagg1_vlan4001: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:00:50 DEHAM01-FW01 kernel: carp: 15@lagg1_vlan4000: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:00:50 DEHAM01-FW01 kernel: carp: 12@lagg1_vlan1011: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:00:50 DEHAM01-FW01 kernel: carp: 17@lagg1_vlan47: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:00:50 DEHAM01-FW01 kernel: carp: 14@lagg1_vlan1150: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:06:28 DEHAM01-FW01 kernel: carp: 1@lagg0: MASTER -> BACKUP (more frequent advertisement received)
Feb 18 22:06:28 DEHAM01-FW01 opnsense: /usr/local/etc/rc.syshook.d/carp/20-openvpn: Carp cluster member "XXXX.142.178 -  (1@lagg0)" has resumed the state "BACKUP" for vhid 1
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 1@lagg0: INIT -> BACKUP (initialization complete)
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 2@lagg1_vlan10: INIT -> BACKUP (initialization complete)
Feb 18 22:10:01 DEHAM01-FW01 opnsense: /usr/local/etc/rc.syshook.d/carp/20-openvpn: Carp cluster member "XXX.142.178 -  (1@lagg0)" has resumed the state "BACKUP" for vhid 1
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 3@lagg1_vlan40: INIT -> BACKUP (initialization complete)
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 4@lagg1_vlan42: INIT -> BACKUP (initialization complete)
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 5@lagg1_vlan43: INIT -> BACKUP (initialization complete)
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 6@lagg1_vlan44: INIT -> BACKUP (initialization complete)
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 7@lagg1_vlan150: INIT -> BACKUP (initialization complete)
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 8@lagg1_vlan1000: INIT -> BACKUP (initialization complete)
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 9@lagg1_vlan1001: INIT -> BACKUP (initialization complete)
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 10@lagg1_vlan1002: INIT -> BACKUP (initialization complete)
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 11@lagg1_vlan1003: INIT -> BACKUP (initialization complete)
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 12@lagg1_vlan1011: INIT -> BACKUP (initialization complete)
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 13@lagg1_vlan1020: INIT -> BACKUP (initialization complete)
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 14@lagg1_vlan1150: INIT -> BACKUP (initialization complete)
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 15@lagg1_vlan4000: INIT -> BACKUP (initialization complete)
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 16@lagg1_vlan4001: INIT -> BACKUP (initialization complete)
Feb 18 22:10:01 DEHAM01-FW01 kernel: carp: 17@lagg1_vlan47: INIT -> BACKUP (initialization complete)
Feb 18 22:10:02 DEHAM01-FW01 kernel: carp: demoted by 240 to 240 (pfsync bulk start)
Feb 18 22:10:04 DEHAM01-FW01 kernel: carp: 2@lagg1_vlan10: BACKUP -> MASTER (master timed out)
Feb 18 22:10:04 DEHAM01-FW01 kernel: carp: 3@lagg1_vlan40: BACKUP -> MASTER (master timed out)
Feb 18 22:10:04 DEHAM01-FW01 kernel: carp: 4@lagg1_vlan42: BACKUP -> MASTER (master timed out)
Feb 18 22:10:04 DEHAM01-FW01 kernel: carp: 5@lagg1_vlan43: BACKUP -> MASTER (master timed out)
Feb 18 22:10:04 DEHAM01-FW01 kernel: carp: 6@lagg1_vlan44: BACKUP -> MASTER (master timed out)
Feb 18 22:10:04 DEHAM01-FW01 kernel: carp: 7@lagg1_vlan150: BACKUP -> MASTER (master timed out)
Feb 18 22:10:04 DEHAM01-FW01 kernel: carp: 8@lagg1_vlan1000: BACKUP -> MASTER (master timed out)
Feb 18 22:10:04 DEHAM01-FW01 kernel: carp: 9@lagg1_vlan1001: BACKUP -> MASTER (master timed out)
Feb 18 22:10:04 DEHAM01-FW01 kernel: carp: 10@lagg1_vlan1002: BACKUP -> MASTER (master timed out)
Feb 18 22:10:04 DEHAM01-FW01 kernel: carp: 11@lagg1_vlan1003: BACKUP -> MASTER (master timed out)
Feb 18 22:10:04 DEHAM01-FW01 kernel: carp: 12@lagg1_vlan1011: BACKUP -> MASTER (master timed out)
Feb 18 22:10:04 DEHAM01-FW01 kernel: carp: 13@lagg1_vlan1020: BACKUP -> MASTER (master timed out)
Feb 18 22:10:04 DEHAM01-FW01 kernel: carp: 14@lagg1_vlan1150: BACKUP -> MASTER (master timed out)
Feb 18 22:10:04 DEHAM01-FW01 kernel: carp: 15@lagg1_vlan4000: BACKUP -> MASTER (master timed out)
Feb 18 22:10:05 DEHAM01-FW01 kernel: carp: 16@lagg1_vlan4001: BACKUP -> MASTER (master timed out)
Feb 18 22:10:05 DEHAM01-FW01 kernel: carp: 17@lagg1_vlan47: BACKUP -> MASTER (master timed out)
Feb 18 22:10:07 DEHAM01-FW01 kernel: carp: demoted by 240 to 480 (send error 50 on lagg1_vlan40)
Feb 18 22:10:07 DEHAM01-FW01 kernel: carp: demoted by 240 to 720 (send error 50 on lagg1_vlan10)
Feb 18 22:10:07 DEHAM01-FW01 kernel: carp: demoted by 240 to 960 (send error 50 on lagg1_vlan47)
Feb 18 22:10:07 DEHAM01-FW01 kernel: carp: demoted by 240 to 1200 (send error 50 on lagg1_vlan4001)
Feb 18 22:10:07 DEHAM01-FW01 kernel: carp: demoted by 240 to 1440 (send error 50 on lagg1_vlan4000)
Feb 18 22:10:07 DEHAM01-FW01 kernel: carp: demoted by 240 to 1680 (send error 50 on lagg1_vlan1150)
Feb 18 22:10:07 DEHAM01-FW01 kernel: carp: demoted by 240 to 1920 (send error 50 on lagg1_vlan1020)
Feb 18 22:10:07 DEHAM01-FW01 kernel: carp: demoted by 240 to 2160 (send error 50 on lagg1_vlan1011)
Feb 18 22:10:07 DEHAM01-FW01 kernel: carp: demoted by 240 to 2400 (send error 50 on lagg1_vlan1003)
Feb 18 22:10:07 DEHAM01-FW01 kernel: carp: demoted by 240 to 2640 (send error 50 on lagg1_vlan1002)
Feb 18 22:10:07 DEHAM01-FW01 kernel: carp: demoted by 240 to 2880 (send error 50 on lagg1_vlan1001)
Feb 18 22:10:07 DEHAM01-FW01 kernel: carp: demoted by 240 to 3120 (send error 50 on lagg1_vlan1000)
Feb 18 22:10:07 DEHAM01-FW01 kernel: carp: demoted by 240 to 3360 (send error 50 on lagg1_vlan150)
Feb 18 22:10:07 DEHAM01-FW01 kernel: carp: demoted by 240 to 3600 (send error 50 on lagg1_vlan44)
Feb 18 22:10:07 DEHAM01-FW01 kernel: carp: demoted by 240 to 3840 (send error 50 on lagg1_vlan43)
Feb 18 22:10:07 DEHAM01-FW01 kernel: carp: demoted by 240 to 4080 (send error 50 on lagg1_vlan42)
Feb 18 22:11:07 DEHAM01-FW01 kernel: carp: demoted by -240 to 3840 (pfsync bulk fail)


Habe nun erst Node 2 neugestartet der war dann mit allen vlans plötzlich master nur WAN nicht, habe dann den master neugestartet dann war node 2 master mit allem hat seine ressourcen aber nicht dem Node 1 zurückgegeben. Ich raff es nicht :/

Habe aufm Node 2 jetzt carp wieder deaktiviert damit node 1 wieder master in allem wird.

https://forums.freebsd.org/threads/carp-problem-again-again-and-again.59298/

Das habe ich noch gefunden zu dem Thema... Besteht das immer noch?