Re: carp/pfsync-problem: carp states stuck in "INIT" on boot on both machines but work correctly if called manually via /etc/netstart

2015-10-02 Thread Andre Ruppert

...I don't believe it...

I ssh'd all the time to the gateways and never had a look to the 
bootmessages


2x "ifconfig  invalid argument" was the hint at boot.

The fault (syntax typo?) was included in hostname.carp[0,1] -
"\" for a 2-liner didn't work... despite the usage of blanks only.

Crunched it to a 1-liner and all worked...

Seems that the parsing is different at booting?

Andre

Am 02.10.15 um 10:37 schrieb Andre Ruppert:

Hello @list,

perhaps I'm stupid but I've got a problem with two CARPed gateways
running  5.7-amd64 stable.

Hardware:
two supermicro-board machines with four network interfaces each (em0 ..
em3).

Networks:
LAN A : 172.16.210/24 via em0
LAN B : 172.16.0/24   via em1
direct connect for pfsync: 1.1.1.0/30 via em3


Gateway A setup --- (master) ---

hostname.em0:
"inet 172.16.210.2 255.255.255.0"

hostname.em1:
"inet 172.16.0.30 255.255.255.0"

hostname.em3
"inet 1.1.1.1 255.255.255.252 1.1.1.3"

hostname.carp0
"inet 172.16.210.1 255.255.255.0 172.16.210.255 vhid 1 \
   carpdev em0 pass gwvoip01carppass advskew 0"

hostname.carp1
"inet 172.16.0.29  255.255.255.0 172.16.0.255 vhid 2 \
   carpdev em1 pass gwvoip01carppass advskew 0"

hostname.pfsync0
"up syncdev em3 syncpeer 1.1.1.2"

sysctl net.inet.carp ->
net.inet.carp.allow=1
net.inet.carp.preempt=1
net.inet.carp.log=7  #debugging


Gateway B setup --- (backup) ---

hostname.em0:
"inet 172.16.210.3 255.255.255.0"

hostname.em1:
"inet 172.16.0.31 255.255.255.0"

hostname.em3
"inet 1.1.1.2 255.255.255.252 1.1.1.3"

hostname.carp0
"inet 172.16.210.1 255.255.255.0 172.16.210.255 vhid 1 \
carpdev em0 pass gwvoip01carppass advskew 100"

hostname.carp1
"inet 172.16.0.29 255.255.255.0 172.16.0.255 vhid 2 \
carpdev em1 pass gwvoip01carppass advskew 100"

hostname.pfsync0
"up syncdev em3 syncpeer 1.1.1.1"

sysctl net.inet.carp ->
net.inet.carp.allow=1
net.inet.carp.preempt=1
net.inet.carp.log=2


problem description --

(remark: failover-switching works on both machines in both directions)

If one of the machines reboots, the local carp-interfaces stuck in
"INIT" state. Same behavior on both systems.

The log (A) after reboot:
carp: carp0 demoted group carp by -1 to 162 (carpdev)
carp: carp1 demoted group carp by -1 to 161 (carpdev)
carp: pfsync0 demoted group carp by -1 to 32 (pfsync bulk done)
carp: pfsync0 demoted group pfsync by -1 to 32 (pfsync bulk done)
carp: pfsync0 demoted group carp by -32 to 0 (pfsync init)
carp: pfsync0 demoted group pfsync by -32 to 0 (pfsync init)

If the carp-interfaces are subsequently restartet via netstart command,
all works like a charm again...

The log (A) after "sh /etc/netstart [carp0,carp1]":
carp0: state transition: INIT -> BACKUP
state transition: BACKUP -> MASTER
state transition: INIT -> BACKUP
state transition: BACKUP -> MASTER

No PF-ruleset-problem!


resulting question -

what the heck is going on here? ;-)
alternative: what did I forgot to configure?

Thanks for reading...


Andre Ruppert




carp/pfsync-problem: carp states stuck in "INIT" on boot on both machines but work correctly if called manually via /etc/netstart

2015-10-02 Thread Andre Ruppert

Hello @list,

perhaps I'm stupid but I've got a problem with two CARPed gateways 
running  5.7-amd64 stable.


Hardware:
two supermicro-board machines with four network interfaces each (em0 .. 
em3).


Networks:
LAN A : 172.16.210/24 via em0
LAN B : 172.16.0/24   via em1
direct connect for pfsync: 1.1.1.0/30 via em3


Gateway A setup --- (master) ---

hostname.em0:
"inet 172.16.210.2 255.255.255.0"

hostname.em1:
"inet 172.16.0.30 255.255.255.0"

hostname.em3
"inet 1.1.1.1 255.255.255.252 1.1.1.3"

hostname.carp0
"inet 172.16.210.1 255.255.255.0 172.16.210.255 vhid 1 \
  carpdev em0 pass gwvoip01carppass advskew 0"

hostname.carp1
"inet 172.16.0.29  255.255.255.0 172.16.0.255 vhid 2 \
  carpdev em1 pass gwvoip01carppass advskew 0"

hostname.pfsync0
"up syncdev em3 syncpeer 1.1.1.2"

sysctl net.inet.carp ->
net.inet.carp.allow=1
net.inet.carp.preempt=1
net.inet.carp.log=7  #debugging


Gateway B setup --- (backup) ---

hostname.em0:
"inet 172.16.210.3 255.255.255.0"

hostname.em1:
"inet 172.16.0.31 255.255.255.0"

hostname.em3
"inet 1.1.1.2 255.255.255.252 1.1.1.3"

hostname.carp0
"inet 172.16.210.1 255.255.255.0 172.16.210.255 vhid 1 \
carpdev em0 pass gwvoip01carppass advskew 100"

hostname.carp1
"inet 172.16.0.29 255.255.255.0 172.16.0.255 vhid 2 \
carpdev em1 pass gwvoip01carppass advskew 100"

hostname.pfsync0
"up syncdev em3 syncpeer 1.1.1.1"

sysctl net.inet.carp ->
net.inet.carp.allow=1
net.inet.carp.preempt=1
net.inet.carp.log=2


problem description --

(remark: failover-switching works on both machines in both directions)

If one of the machines reboots, the local carp-interfaces stuck in 
"INIT" state. Same behavior on both systems.


The log (A) after reboot:
carp: carp0 demoted group carp by -1 to 162 (carpdev)
carp: carp1 demoted group carp by -1 to 161 (carpdev)
carp: pfsync0 demoted group carp by -1 to 32 (pfsync bulk done)
carp: pfsync0 demoted group pfsync by -1 to 32 (pfsync bulk done)
carp: pfsync0 demoted group carp by -32 to 0 (pfsync init)
carp: pfsync0 demoted group pfsync by -32 to 0 (pfsync init)

If the carp-interfaces are subsequently restartet via netstart command,
all works like a charm again...

The log (A) after "sh /etc/netstart [carp0,carp1]":
carp0: state transition: INIT -> BACKUP
state transition: BACKUP -> MASTER
state transition: INIT -> BACKUP
state transition: BACKUP -> MASTER

No PF-ruleset-problem!


resulting question -

what the heck is going on here? ;-)
alternative: what did I forgot to configure?

Thanks for reading...


Andre Ruppert