Re: CARP on -CURRENT
On Feb 3, 2012, at 1:02 PM, Freddie Cash wrote:
> On Fri, Feb 3, 2012 at 1:35 AM, Andrew Hobbs wrote:
>>> On 2 February 2012 04:26, Andrew Hobbs wrote:
I much appreciate the responses and I was able to get CARP functioning
using the new ifconfig syntax under -CURRENT. Having done that, CARP
is now acting as it should, though now I have a new challenge with
devd and automatic firing of scripts during CARP failover. It appears
that the documented method of doing this at
http://www.freebsd.org/doc/handbook/disks-hast.html no longer works
with the suggested devd.conf setup; notify 30 {
match "system" "IFNET";
match "subsystem" "carp0";
match "type" "LINK_UP";
action "/usr/local/sbin/carp-hast-switch master"; };
notify 30 {
match "system" "IFNET";
match "subsystem" "carp0";
match "type" "LINK_DOWN";
action "/usr/local/sbin/carp-hast-switch slave";
Is it likely that the triggers associated with CARP for devd have changed
due to the recent new CARP overhaul? Does anyone know what the new
triggers may be?
>>>
>>> You will need to change this to something like (as taken from man carp):
>>> match "system" "CARP";
>>> match "subsystem" "[0-9]+@";
>>> match "type""(MASTER|BACKUP)";
>>>
>>> The subsystem now is generated as
>>> snprintf(subsys, IFNAMSIZ+5, "%u@%s", sc->sc_vhid,
>>> sc->sc_carpdev->if_xname);
>
>> Thanks for the info. I was able to get the triggers firing from devd. I also
>> noticed that the man page on 'carp' references a "carpcontrol.sh" script as
>> an action. Has this script been prototyped anywhere yet?
>
> Mind posting the devd.conf entries you are using? Maybe submitting a
> docs PR with them included, to update the HAST page?
>
> Thanks. I haven't played with HAST and the new CARP code yet.
>
> --
> Freddie Cash
> fjwc...@gmail.com
The entirety of the cogent entry in /etc/devd.conf that I am using follows;
notify 0 {
match "system" "CARP";
match "subsystem" "[0-9]+@";
match "type""(INIT|MASTER|BACKUP)";
# action "/root/carpcontrol.sh $subsystem $type";
action "/etc/test_carp.sh $subsystem $type";
};
This differs from the example in "man 4 carp" only by one line. I substituted
the 'action "/etc/test_carp.sh $subsystem $type";' for the line above it, as I
cannot seem to locate a 'carpcontrol.sh' script anywhere on my 10.0-CURRENT
test platform. Hence my earlier inquiry as to if it had been prototyped
anywhere yet. I did locate several CARP related action scripts in
/usr/share/examples/hast/ but I'm not sure how they different from this
ephemeral 'carpcontrol.sh' script without seeing it.
-Andrew___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CARP on -CURRENT
On Fri, Feb 3, 2012 at 1:35 AM, Andrew Hobbs wrote:
>> On 2 February 2012 04:26, Andrew Hobbs wrote:
>> > I much appreciate the responses and I was able to get CARP functioning
>> > using the new ifconfig syntax under -CURRENT. Having done that, CARP
>> > is now acting as it should, though now I have a new challenge with
>> > devd and automatic firing of scripts during CARP failover. It appears
>> > that the documented method of doing this at
>> > http://www.freebsd.org/doc/handbook/disks-hast.html no longer works
>> > with the suggested devd.conf setup; notify 30 {
>> > match "system" "IFNET";
>> > match "subsystem" "carp0";
>> > match "type" "LINK_UP";
>> > action "/usr/local/sbin/carp-hast-switch master"; };
>> >
>> > notify 30 {
>> > match "system" "IFNET";
>> > match "subsystem" "carp0";
>> > match "type" "LINK_DOWN";
>> > action "/usr/local/sbin/carp-hast-switch slave";
>> >
>> > Is it likely that the triggers associated with CARP for devd have changed
>> > due to the recent new CARP overhaul? Does anyone know what the new
>> > triggers may be?
>> >
>>
>> You will need to change this to something like (as taken from man carp):
>> match "system" "CARP";
>> match "subsystem" "[0-9]+@";
>> match "type" "(MASTER|BACKUP)";
>>
>> The subsystem now is generated as
>> snprintf(subsys, IFNAMSIZ+5, "%u@%s", sc->sc_vhid, sc->sc_carpdev->if_xname);
> Thanks for the info. I was able to get the triggers firing from devd. I also
> noticed that the man page on 'carp' references a "carpcontrol.sh" script as
> an action. Has this script been prototyped anywhere yet?
Mind posting the devd.conf entries you are using? Maybe submitting a
docs PR with them included, to update the HAST page?
Thanks. I haven't played with HAST and the new CARP code yet.
--
Freddie Cash
fjwc...@gmail.com
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
RE: CARP on -CURRENT
> -Original Message-
> From: Sergey Kandaurov [mailto:pluk...@gmail.com]
> Sent: Thursday, February 02, 2012 2:00 AM
> To: Andrew Hobbs
> Cc: freebsd-current@freebsd.org
> Subject: Re: CARP on -CURRENT
>
> On 2 February 2012 04:26, Andrew Hobbs wrote:
> > I much appreciate the responses and I was able to get CARP functioning
> > using the new ifconfig syntax under -CURRENT. Having done that, CARP
> > is now acting as it should, though now I have a new challenge with
> > devd and automatic firing of scripts during CARP failover. It appears
> > that the documented method of doing this at
> > http://www.freebsd.org/doc/handbook/disks-hast.html no longer works
> > with the suggested devd.conf setup; notify 30 {
> > match "system" "IFNET";
> > match "subsystem" "carp0";
> > match "type" "LINK_UP";
> > action "/usr/local/sbin/carp-hast-switch master"; };
> >
> > notify 30 {
> > match "system" "IFNET";
> > match "subsystem" "carp0";
> > match "type" "LINK_DOWN";
> > action "/usr/local/sbin/carp-hast-switch slave";
> >
> > Is it likely that the triggers associated with CARP for devd have changed
> > due to the recent new CARP overhaul? Does anyone know what the new triggers
> > may be?
> >
>
> You will need to change this to something like (as taken from man carp):
> match "system" "CARP";
> match "subsystem" "[0-9]+@";
> match "type""(MASTER|BACKUP)";
>
> The subsystem now is generated as
> snprintf(subsys, IFNAMSIZ+5, "%u@%s", sc->sc_vhid, sc->sc_carpdev->if_xname);
>
> --
> wbr,
> pluknet
Thanks for the info. I was able to get the triggers firing from devd. I also
noticed that the man page on 'carp' references a "carpcontrol.sh" script as an
action. Has this script been prototyped anywhere yet?
-Andrew
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CARP on -CURRENT
On 2 February 2012 04:26, Andrew Hobbs wrote:
> I much appreciate the responses and I was able to get CARP functioning using
> the new ifconfig syntax under -CURRENT. Having done that, CARP is now acting
> as it should, though now I have a new challenge with devd and automatic
> firing of scripts during CARP failover. It appears that the documented method
> of doing this at http://www.freebsd.org/doc/handbook/disks-hast.html no
> longer works with the suggested devd.conf setup;
> notify 30 {
> match "system" "IFNET";
> match "subsystem" "carp0";
> match "type" "LINK_UP";
> action "/usr/local/sbin/carp-hast-switch master";
> };
>
> notify 30 {
> match "system" "IFNET";
> match "subsystem" "carp0";
> match "type" "LINK_DOWN";
> action "/usr/local/sbin/carp-hast-switch slave";
>
> Is it likely that the triggers associated with CARP for devd have changed due
> to the recent new CARP overhaul? Does anyone know what the new triggers may
> be?
>
You will need to change this to something like (as taken from man carp):
match "system" "CARP";
match "subsystem" "[0-9]+@";
match "type""(MASTER|BACKUP)";
The subsystem now is generated as
snprintf(subsys, IFNAMSIZ+5, "%u@%s", sc->sc_vhid, sc->sc_carpdev->if_xname);
--
wbr,
pluknet
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
RE: CARP on -CURRENT
I much appreciate the responses and I was able to get CARP functioning using
the new ifconfig syntax under -CURRENT. Having done that, CARP is now acting as
it should, though now I have a new challenge with devd and automatic firing of
scripts during CARP failover. It appears that the documented method of doing
this at http://www.freebsd.org/doc/handbook/disks-hast.html no longer works
with the suggested devd.conf setup;
notify 30 {
match "system" "IFNET";
match "subsystem" "carp0";
match "type" "LINK_UP";
action "/usr/local/sbin/carp-hast-switch master";
};
notify 30 {
match "system" "IFNET";
match "subsystem" "carp0";
match "type" "LINK_DOWN";
action "/usr/local/sbin/carp-hast-switch slave";
Is it likely that the triggers associated with CARP for devd have changed due
to the recent new CARP overhaul? Does anyone know what the new triggers may be?
Love,
Andrew
-Original Message-
From: Sergey Kandaurov [mailto:pluk...@gmail.com]
Sent: Wednesday, January 18, 2012 4:24 PM
To: Andrew Hobbs
Cc: freebsd-current@freebsd.org
Subject: Re: CARP on -CURRENT
On 19 January 2012 00:54, Andrew Hobbs wrote:
> Is CARP implemented on -CURRENT (FreeBSD 10)?
>
> I'm playing around with some test boxes in the office running
> -CURRENT; testbox# uname -a FreeBSD testbox.ai.net 10.0-CURRENT
> FreeBSD 10.0-CURRENT #0: Wed Jan 18 19:21:12 EST 2012
> r...@testbox.ai.net:/usr/obj/usr/src/sys/CARP amd64
>
> I can't seem to create a carp interface despite having compiled a
> kernel with "device carp" in it. Attempts to create a carp
> interface fail; # ifconfig carp create
> ifconfig: SIOCIFCREATE2: Invalid argument
>
> >From what I've read in the handbook entry on CARP
> >(http://www.freebsd.org/doc/handbook/carp.html), I should be able to
> >either compile in the carp device, as above, or load the if_carp.ko
> >kern module. There doesn't appear to be a if_carp.ko module in the
> >-CURRENT source tree, however. Only the carp module itself;
> # ls -ald /usr/src/sys/modules/*carp*
> drwxr-xr-x 2 root wheel 512 Dec 27 15:12 /usr/src/sys/modules/carp
>
> Am I missing something completely obvious? Was the functionality of
> if_carp.ko rolled into another module?
You should definitely read this changeset:
http://svn.freebsd.org/changeset/base/228571
and the updated carp ifconfig syntax in man carp. As for if_carp.ko, it was
renamed into carp.ko as part of the CARP implementation overhaul.
This only affects CURRENT.
--
wbr,
pluknet
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CARP on -CURRENT
On 19 January 2012 00:54, Andrew Hobbs wrote: > Is CARP implemented on -CURRENT (FreeBSD 10)? > > I'm playing around with some test boxes in the office running -CURRENT; > testbox# uname -a > FreeBSD testbox.ai.net 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Wed Jan 18 > 19:21:12 EST 2012 r...@testbox.ai.net:/usr/obj/usr/src/sys/CARP amd64 > > I can't seem to create a carp interface despite having compiled a kernel with > "device carp" in it. Attempts to create a carp interface fail; > # ifconfig carp create > ifconfig: SIOCIFCREATE2: Invalid argument > > >From what I've read in the handbook entry on CARP > >(http://www.freebsd.org/doc/handbook/carp.html), I should be able to either > >compile in the carp device, as above, or load the if_carp.ko kern module. > >There doesn't appear to be a if_carp.ko module in the -CURRENT source tree, > >however. Only the carp module itself; > # ls -ald /usr/src/sys/modules/*carp* > drwxr-xr-x 2 root wheel 512 Dec 27 15:12 /usr/src/sys/modules/carp > > Am I missing something completely obvious? Was the functionality of > if_carp.ko rolled into another module? You should definitely read this changeset: http://svn.freebsd.org/changeset/base/228571 and the updated carp ifconfig syntax in man carp. As for if_carp.ko, it was renamed into carp.ko as part of the CARP implementation overhaul. This only affects CURRENT. -- wbr, pluknet ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CARP on -CURRENT
On Wed, Jan 18, 2012 at 12:54 PM, Andrew Hobbs wrote: > Is CARP implemented on -CURRENT (FreeBSD 10)? Search through the mailing list archives for -current, and possibly -stable. There's a major reworking of CARP underway in -CURRENT. It's no longer a separate interface, but options assigned to an interface. There's a couple really long messages that cover it in the archives. -- Freddie Cash fjwc...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
