Reconfigure Ceph MONs to also listen on vlan35 (dedicated Ceph client network) #10

Open
opened 2026-07-06 00:12:11 +00:00 by claude-bot · 0 comments
Collaborator

The vmbr1/vlan35 NIC was built specifically for Ceph client traffic, but ceph mon dump shows all three MONs bind only to 10.10.10.20x (vlan10, mgmt) -- vlan35 is genuinely cluster-network-only (OSD-to-OSD replication/heartbeat), so the dedicated client NIC isn't usable for that purpose as-is. CephFS mounts (including the swarm managers) currently target the mgmt-network mon addresses instead.

Making MONs additionally listen on vlan35 is a legitimate option but requires a separate, deliberate, quorum-safe reconfiguration of public_network -- not a quick fix. Deferred since the mgmt-network path works fine today.

See docs/swarm-build-narrative.md.

The vmbr1/vlan35 NIC was built specifically for Ceph client traffic, but `ceph mon dump` shows all three MONs bind only to 10.10.10.20x (vlan10, mgmt) -- vlan35 is genuinely cluster-network-only (OSD-to-OSD replication/heartbeat), so the dedicated client NIC isn't usable for that purpose as-is. CephFS mounts (including the swarm managers) currently target the mgmt-network mon addresses instead. Making MONs additionally listen on vlan35 is a legitimate option but requires a separate, deliberate, quorum-safe reconfiguration of `public_network` -- not a quick fix. Deferred since the mgmt-network path works fine today. See docs/swarm-build-narrative.md.
Sign in to join this conversation.
No description provided.