rown
Sent: 16 June 2021 10:18:02
To: huxia...@horebdata.cn
Cc: Joe Comeau; ceph-users
Subject: [ceph-users] Re: Fwd: Re: Issues with Ceph network redundancy using L2
MC-LAG
Depends on when you configure the switch port. For dell :
Interface Ethernet 1/1/20
No switchport
Channel-group 10 mode activ
‐‐‐ Original Message ‐‐‐
On Wednesday, June 16, 2021 10:18 AM, Andrew Walker-Brown
wrote:
> With active mode, you then have a transmit hashing policy, usually set
> globally.
>
> On Linux the bond would be set as ‘bond-mode 802.3ad’ and then
> ‘bond-xmit-hash-policy layer3+4’ - or what
e 2021 09:29
To: Andrew Walker-Brown<mailto:andrew_jbr...@hotmail.com>
Cc: huxia...@horebdata.cn<mailto:huxia...@horebdata.cn>; Joe
Comeau<mailto:joe.com...@hli.ubc.ca>; ceph-users<mailto:ceph-users@ceph.io>
Subject: Re: [ceph-users] Re: Fwd: Re: Issues with Ceph
You cannot do much if the link is flapping or the cable is bad.
Maybe you can write some rules to shut the port down on the switch if
the error packet ratio goes up.
I also remember there are some config on the switch side for link flapping.
On Wed, Jun 16, 2021 at 10:57 AM huxia...@horebdata.cn
Depends on when you configure the switch port. For dell :
Interface Ethernet 1/1/20
No switchport
Channel-group 10 mode active
!
‘Mode active’ set it as a dynamic lacp lag. Otherwise it would be ‘mode static’
With active mode, you then have a transmit hashing policy, usually set
globally.
On
Is it true that MC-LAG and 803.2ad, by its default, are working on
active-active.
What else should i take care to ensure fault tolerance when one path is bad?
best regards,
samuel
huxia...@horebdata.cn
From: Joe Comeau
Date: 2021-06-15 23:44
To: ceph-users@ceph.io
Subject: [ceph-users] Fw
