From: Mazhar Rana
Date: Tue, 7 Jul 2015 15:04:50 +0530
> From: Mazhar Rana
>
> When "primary_reselect" is set to "failure", primary interface should
> not become active until current active slave is down. But if we set first
> member of bond device as a "primary" interface and
From: Mazhar Rana ranamazh...@gmail.com
Date: Tue, 7 Jul 2015 15:04:50 +0530
From: Mazhar Rana mazhar.r...@cyberoam.com
When primary_reselect is set to failure, primary interface should
not become active until current active slave is down. But if we set first
member of bond device as a
Mazhar Rana wrote:
>From: Mazhar Rana
>
>When "primary_reselect" is set to "failure", primary interface should
>not become active until current active slave is down. But if we set first
>member of bond device as a "primary" interface and "primary_reselect"
>is set to "failure" then whenever
From: Mazhar Rana
When "primary_reselect" is set to "failure", primary interface should
not become active until current active slave is down. But if we set first
member of bond device as a "primary" interface and "primary_reselect"
is set to "failure" then whenever primary interface's link get
Mazhar Rana ranamazh...@gmail.com wrote:
From: Mazhar Rana mazhar.r...@cyberoam.com
When primary_reselect is set to failure, primary interface should
not become active until current active slave is down. But if we set first
member of bond device as a primary interface and primary_reselect
is set
From: Mazhar Rana mazhar.r...@cyberoam.com
When primary_reselect is set to failure, primary interface should
not become active until current active slave is down. But if we set first
member of bond device as a primary interface and primary_reselect
is set to failure then whenever primary
6 matches
Mail list logo