From: Gianni Milo <gianni.milo22@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] 5.4 Seeing Corosync TOTEM Retransmits
Date: Tue, 18 Aug 2020 17:36:26 +0100 [thread overview]
Message-ID: <CACzVk9X4KyjX=mKYgkQgdiYZkHufwrL9iitbAskgsaW5V9bxTQ@mail.gmail.com> (raw)
In-Reply-To: <CA+U74VPSXwbU721E7Tpr46t7sR5uEr_zF2-ax1tZh-EUc61ZFQ@mail.gmail.com>
On Tue, 18 Aug 2020 at 14:49, JR Richardson <jmr.richardson@gmail.com>
wrote:
>
> Can I specify what network to use
>
> for migration, like storage (jumbo frame enabled) or management to
>
> relieve any congestion on the heartbeat network segment?
Yes, it is possible to do that. See chapter "5.12.2 Migration Network" on
the PVE Admin guide.
G.
prev parent reply other threads:[~2020-08-18 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 13:48 JR Richardson
2020-08-18 16:36 ` Gianni Milo [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='CACzVk9X4KyjX=mKYgkQgdiYZkHufwrL9iitbAskgsaW5V9bxTQ@mail.gmail.com' \
--to=gianni.milo22@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.