On Wed, 2018-06-06 at 07:47 +0800, Confidential Company wrote:
> On Sat, 2018-06-02 at 22:14 +0800, Confidential Company wrote:
> > On Fri, 2018-06-01 at 22:58 +0800, Confidential Company wrote:
> > > Hi,
> > >?
> > > I have two-node active/passive setup. My goal is to failover a
> > > resource
On Sat, 2018-06-02 at 22:14 +0800, Confidential Company wrote:
> On Fri, 2018-06-01 at 22:58 +0800, Confidential Company wrote:
> > Hi,
> >?
> > I have two-node active/passive setup. My goal is to failover a
> > resource once a Node goes down with minimal downtime as possible.
> > Based on my
On Sat, 2018-06-02 at 22:14 +0800, Confidential Company wrote:
> On Fri, 2018-06-01 at 22:58 +0800, Confidential Company wrote:
> > Hi,
> >
> > I have two-node active/passive setup. My goal is to failover a
> > resource once a Node goes down with minimal downtime as possible.
> > Based on my
On Fri, 2018-06-01 at 22:58 +0800, Confidential Company wrote:
> Hi,
>
> I have two-node active/passive setup. My goal is to failover a
> resource once a Node goes down with minimal downtime as possible.
> Based on my testing, when Node1 goes down it failover to Node2. If
> Node1 goes up after
On Fri, 2018-06-01 at 22:58 +0800, Confidential Company wrote:
> Hi,
>
> I have two-node active/passive setup. My goal is to failover a
> resource once a Node goes down with minimal downtime as possible.
> Based on my testing, when Node1 goes down it failover to Node2. If
> Node1 goes up after
Hi,
I have two-node active/passive setup. My goal is to failover a resource
once a Node goes down with minimal downtime as possible. Based on my
testing, when Node1 goes down it failover to Node2. If Node1 goes up after
link reconnection (reconnect physical cable), resource failback to Node1
even
