Hi, sorry for the delay, but in the meantime we were able to find a workaround. Inspired by this: > Side note: Configuring the loopback IP on the physical interfaces is > workable if you set it on **all** parallel links. Example with server1: > > > > “iface enp3s0f0 inet static > > address 10.10.100.21/32 > > iface enp3s0f1 inet static > > address 10.10.100.21/32 > > iface enp4s0f0 inet static > > address 10.10.100.21/32 > > iface enp4s0f1 inet static > > address 10.10.100.21/32” > > > > This should guarantee that the loopback ip is advertised if one of the 4 > links to switch1 and switch2 is up, but I am not sure if that’s workable > for ceph’s listening address. We added the loopback ip as well on lo as on dummy0. This solves the issue for us and the Ceph cluster works as intended. Regards Jan -- Artfiles New Media GmbH | Zirkusweg 1 | 20359 Hamburg Tel: 040 - 32 02 72 90 | Fax: 040 - 32 02 72 95 E-Mail: support@xxxxxxxxxxx | Web: http://www.artfiles.de Geschäftsführer: Harald Oltmanns | Tim Evers Eingetragen im Handelsregister Hamburg - HRB 81478
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
