From: Piviul <piviul@riminilug.it>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] ceph
Date: Mon, 9 Jan 2023 12:47:52 +0100 [thread overview]
Message-ID: <ba410dbf-58c2-26a5-4b0a-b54dce28620a@riminilug.it> (raw)
In-Reply-To: <mailman.191.1673258105.458.pve-user@lists.proxmox.com>
On 1/9/23 10:54, Eneko Lacunza via pve-user wrote:
> Hi,
>
> You need to route traffic between LAN network and Ceph network, so
> that this works. When you have all monitors using ceph network IPs,
> undo the routing.
the routing table on a CEPH/PVE node is:
$ ip route
default via 192.168.64.1 dev vmbr0 proto kernel onlink
192.168.64.0/20 dev vmbr0 proto kernel scope link src 192.168.70.30
192.168.254.0/24 dev vmbr2 proto kernel scope link src 192.168.254.1
192.168.255.0/24 dev vmbr1 proto kernel scope link src 192.168.255.1
vmbr2 is the CEPH network, vmbr1 is the PVE network and vmbr0 is the LAN
network. So you suggest me to add first the 3 ceph monitors using the
CEPH IPs network and then destroy the 3 monitors having LAN IPs?
Similarly for the ceph managers?
Piviul
next prev parent reply other threads:[~2023-01-09 11:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 9:14 Piviul
[not found] ` <mailman.191.1673258105.458.pve-user@lists.proxmox.com>
2023-01-09 11:47 ` Piviul [this message]
[not found] ` <mailman.203.1673265308.458.pve-user@lists.proxmox.com>
2023-01-10 7:23 ` Piviul
[not found] ` <mailman.215.1673337884.458.pve-user@lists.proxmox.com>
2023-01-10 13:29 ` Piviul
[not found] ` <mailman.232.1673430028.458.pve-user@lists.proxmox.com>
2023-01-11 11:19 ` Piviul
[not found] ` <mailman.235.1673444838.458.pve-user@lists.proxmox.com>
2023-01-11 15:51 ` Piviul
-- strict thread matches above, loose matches on Subject: below --
2021-09-08 12:46 Leandro Roggerone
2021-09-08 12:55 ` Gilberto Ferreira
2021-09-08 20:07 ` Alex K
2021-09-08 22:11 ` ic
2021-09-13 11:32 ` Leandro Roggerone
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ba410dbf-58c2-26a5-4b0a-b54dce28620a@riminilug.it \
--to=piviul@riminilug.it \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox