Ideally you’d want to have it the transmit hash the same...but so long load is being pretty evenly spread over all the links in the lag, then you’re fine. Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: mabi<mailto:mabi@xxxxxxxxxxxxx> Sent: 16 June 2021 09:29 To: Andrew Walker-Brown<mailto:andrew_jbrown@xxxxxxxxxxx> Cc: huxiaoyu@xxxxxxxxxxxx<mailto:huxiaoyu@xxxxxxxxxxxx>; Joe Comeau<mailto:Joe.Comeau@xxxxxxxxxx>; ceph-users<mailto:ceph-users@xxxxxxx> Subject: Re: Re: Fwd: Re: Issues with Ceph network redundancy using L2 MC-LAG ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, June 16, 2021 10:18 AM, Andrew Walker-Brown <andrew_jbrown@xxxxxxxxxxx> 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 whatever hashing policy you want. Does the transmit hash policy need to be the same on the Linux server and on the switch side? or can they be different? _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |