Hi, Thanks Stefan. Yes I do have separate port-channel interfaces, for public and cluster networks. I just didn't understand the documentation (which is sometimes not that clear). For me when you put forward the --cluster_network option, it meant that --mon-ip was in the public network by default and that you want to define a separate network for your cluster to use as private net. I was reading the documentation when I came across : *ceph config set mon public_network* command, it's then when I saw what could be my mistake. I redid the deployment and so far so good :-) I did use *ceph config set mon public_network* to specify my public net, now I have to test my clients if they can connect to it. Regards. Le ven. 15 mars 2024 à 08:20, Stefan Kooman <stefan@bit.nl> a écrit :
On 15-03-2024 08:10, wodel youchi wrote:
Hi,
I found my error, it was a mismatch between the monitor network ip address and the --cluster_network which were in different subnets. I misunderstood the --cluster_network subnet, I thought that when creating a cluster, the monitor IP designed the public Network, and if I wanted to separate public and private (cluster) networks, I needed to use the --cluster_network option. Maybe I was in over my head, but sometimes it is not that clear.
Ah, good that you found the error. Do you have separate interfaces / port-channels for public and cluster networks? Note that a cluster network is not required and makes things more complicated (as you have noted) and might not give you any benefits when the infrastructure does not match this separation of functions.
Gr. Stefan