From: Uwe Sauter <uwe.sauter.de@gmail.com>
To: Mark Schouten <mark@tuxis.nl>,
Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] How to configure which network is used for migration
Date: Thu, 15 Dec 2022 09:11:45 +0100 [thread overview]
Message-ID: <d80eadf7-d068-3695-b55c-e944b6b5079b@gmail.com> (raw)
In-Reply-To: <em7e8e2199-2131-46e9-8480-80695f479cc6@4148cfe7.com>
Mark, Alexandre,
thanks for pointing that out.
@Mark: as these are private, isolated networks I'm unsure how IPv6 would help with the issue. I
could use link-local addresses (fe80::) but would need to append to every request the "%interface"
postfix in order to tell the system which interface to use…
Using unique local unicast addresses is no different in using private IPv4 networks…
So please enlighten me how IPv6 would help in that situation.
Besides that I agree – we should switch to IPv6 where it is sensible and possible (from an
organization's point of view).
Regards,
Uwe
Am 15.12.22 um 09:04 schrieb Mark Schouten:
> Hi,
>
> Some unsolicited advice, switch to IPv6 ;)
>
> As for your question, you can set that up in the datacenter -> options tab. See
> https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_guest_migration
>
> Regards,
>
> —
> Mark Schouten, CTO
> Tuxis B.V.
> mark@tuxis.nl / +31 318 200208
>
>
> ------ Original Message ------
> From "Uwe Sauter" <uwe.sauter.de@gmail.com>
> To "Proxmox VE user list" <pve-user@lists.proxmox.com>
> Date 12/15/2022 8:23:41 AM
> Subject [PVE-User] How to configure which network is used for migration
>
>> Good morning,
>>
>> I'm currently replacing one PVE cluster with another. The new hardware has a bunch of different
>> network interfaces that I want to use to separate VM traffic from Corosync/Ceph/migration traffic.
>>
>> Is there a way to configure the interface/network that is used for migration or does this depend on
>> the combination of hostname resolution and which hostname was used to create the cluster?
>> (I have various hostnames configured per host, for each configured network one, so that I can
>> explicitly choose which interface I use to connect to a host.)
>>
>> Regards,
>>
>> Uwe
>>
>>
>> Interface configuration:
>>
>> eno1np0 --+-- untagged VLAN X -- Corosync ring 1/management network (192.168.1.0/24)
>>
>> eno2np1 N/C
>>
>> enp3s0 --+
>> +-- bond0 --+-- bond0.100 -- vmbr100 \
>> enp4s0 --+ +-- bond0.101 -- vmbr101 +-- VM traffic
>> +-- bond0.102 -- vmbr102 /
>>
>> enp5s0 --+
>> +-- bond1 --+-- untagged VLAN Y -- Corosync ring 0/Ceph (172.16.1.0/24)
>> enp6s0 --+
>>
>> _______________________________________________
>> pve-user mailing list
>> pve-user@lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
>
prev parent reply other threads:[~2022-12-15 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 7:23 Uwe Sauter
2022-12-15 8:01 ` DERUMIER, Alexandre
[not found] ` <em7e8e2199-2131-46e9-8480-80695f479cc6@4148cfe7.com>
2022-12-15 8:11 ` Uwe Sauter [this message]
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=d80eadf7-d068-3695-b55c-e944b6b5079b@gmail.com \
--to=uwe.sauter.de@gmail.com \
--cc=mark@tuxis.nl \
--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