Search results

  1. D

    new cluster, ceph monitor unknown status

    It must have been something in the workflow when I created that other cluster. Must have done something wrong. Created everything again and adding the two additional monitors just worked. I did have a clock sync problem but got that worked out in short order. Thank you.
  2. D

    new cluster, ceph monitor unknown status

    Right but a successful ping proves two-way traffic but I will humor you. The only way it would establish one direction and not in the other would be the presence of something like a stateful firewall and there is no such thing on this segment. From pve0 (172.29.99.48): Last login: Wed Feb 10...
  3. D

    new cluster, ceph monitor unknown status

    They can communicate on both the cluster and public networks. The nodes seem to be able to communicate on the webgui/dashboard only connecting to .48. I can motion VMs around the ceph cluster, etc. Not sure what communication channel is thought to be not working? root@pve0:~# ip ad 1: lo...
  4. D

    new cluster, ceph monitor unknown status

    I am seeing the same. Attempting to get a test cluster working on three Dell 1950s. The nodes can freely communicate on 172.29.99.0/24 on .48, .49, .50. This is the ceph configuration I ended up with: Proxmox Virtual Environment 6.3-2 Node 'pve0' [global] auth_client_required = cephx...