From analysis of a simple ifstated.conf to more compex example

Damien Fleuriot ml at my.gd
Tue Feb 7 16:02:08 UTC 2012


On 2/7/12 3:36 PM, peter knezel wrote:
> Hello all,
> 
> I would like to ask somebody to explain me how the ifstated works according to
> the following configuration file.
> I have three virtual carp interfaces carp0,carp1 and carp2.
> 
> I try to understand the following setting:
> The server is in state one (all carp interfaces are up) and if there
> is carp down of any:
> one (carp0 or carp1 or carp2),
> two ([carp0 and carp1] or [carp0 and carp2] or [carp1 and carp2]),
> three interfaces (carp 0 and carp1 and carp2), server
> runs the script testdown.sh and put the server into state two.
> If all carp interfaces are up, the server runs the testup.sh and set
> the state to one.
> 

That is my understanding.


> Is it the way the system works?
> Or am I wrong?
> 
> ===
> init-state one
> 
> net = '( "ifconfig -a -u |grep carp0 > /dev/null" every 3 && "ifconfig -a -u
> |grep carp1 > /dev/null" every 3 && "ifconfig -a -u |grep carp2 > /dev/null"
> every 3)'
> 
> state one {
>        if ( ! $net ) {
>                run "/usr/local/testdown.sh"
>                set-state two
>        }
> }
> 
> state two {
>        if ( $net ) {
>                run "/usr/local/testup.sh"
>                set-state one
>        }
> }
> ===
> 
> Is there any possibility to define and set ifstated.conf that reacts when:
> 
>  any one of the carp interfaces is down - followed by another any
> other carp interface down
> 
> 
> I tried to define states:
> 
> duu ="!carp0.link.up && carp1.link.up && carp2.link.up"
> udu ="carp0.link.up && !carp1.link.up && carp2.link.up"
> uud ="carp0.link.up && carp1.link.up && !carp2.link.up"
> ddu ="!carp0.link.up && !carp1.link.up"
> dud ="!carp0.link.up && !carp2.link.up"
> udd ="!carp1.link.up && !carp2.link.up"
> 
> and used them but somehow I cannot incorporate all state changes and
> include it in ifstated.conf.
> 


Works fine here, did you not have any luck with the file I posted earlier ?


More information about the freebsd-questions mailing list