From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 8D9A861D20 for ; Sat, 19 Feb 2022 20:01:32 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7C0B932EBC for ; Sat, 19 Feb 2022 20:01:02 +0100 (CET) Received: from mail-yw1-x1134.google.com (mail-yw1-x1134.google.com [IPv6:2607:f8b0:4864:20::1134]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 7E5C932EA9 for ; Sat, 19 Feb 2022 20:01:01 +0100 (CET) Received: by mail-yw1-x1134.google.com with SMTP id 00721157ae682-2d68d519a33so97263647b3.7 for ; Sat, 19 Feb 2022 11:01:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ExVRc6wRkPL2QT1JeIDAgrVrU2RoQwEohnLM8GXXa64=; b=nhddeXAIDNA/FDWI1cyjwt/6y+5W0ZjG6sOD4YkeXsl9auTFsI1I5gWbyQ0zVjgsGO gyriqlgQiI5+ZRSWGSzLyI0I4YnfhEW+7I1yq8+iK8loQwmQvL+4XVbwJWrLBy30KCOY ocDpJt3PvU3tsDRf/GxGBuJ4ufmF4Qwu+6XcwUO7kyoRrbWt9OQHSxis3d/Pq8Hzg0Is 3Jx6d2BOs4aAgjt/P9rQIm5CdkGShbA2+CN3eUZOKFcrwu7qgD8a0Cp6PFrI2QyfTUZM clDujg9zxmMsfJMCxsjUuCn89Shd+7it6V91nrWcy/+nkoYZNRppvVkJDyX/RPTNtW9Y SL0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=ExVRc6wRkPL2QT1JeIDAgrVrU2RoQwEohnLM8GXXa64=; b=ors3PcQWV4CoJpTnmATe/D04nO3cMwvN4VRdUxhQS3A8lMcjRkxXj8tyKLwugzs4vT dJsYql9apxlJ+BDa2JXMDV1wb0ctdMkxXZ08lFmScK2OX7xUfBBGEBmz/YBhaiL2mJhi MckY1FHyWHmppYQ89dCgjYM+z7tqMb+qo3aGdhqjGjYJPYXMa8Grl+6hs/a0b3yxOSEN chHJQz88GPn3rguP5dOY3Du/52QH4RCfLqVe7vKR+L0ejAcpD1i7ITVrnTkTL6q2YGxM zxZmsHP83kfy/ueLvtbkkIZMdwsryitqzKb6PPK6H0m7rwJn/uSppDk9W4oxfAkAi9iS cd0Q== X-Gm-Message-State: AOAM531/brwazij2WqEKY0bkdDwaacoZ3MrWrOR1tozugLXrmevgRSU8 3fYxzPOFekxuDAHJeR3WYEUdSw/XxYRSfmLZRfyjCS+5 X-Google-Smtp-Source: ABdhPJzdfntVFoqVleITU1HYncdcGDbqiA6Mu1PYAR/Lwr0FmUxibKhg/Ej6vzLvpGJjEnz0sfYMeZLKf/HseX2BuIc= X-Received: by 2002:a0d:fd83:0:b0:2d0:bab6:d0d5 with SMTP id n125-20020a0dfd83000000b002d0bab6d0d5mr13450682ywf.386.1645297253629; Sat, 19 Feb 2022 11:00:53 -0800 (PST) MIME-Version: 1.0 References: <4535ei-8j11.ln1@hermione.lilliput.linux.it> In-Reply-To: <4535ei-8j11.ln1@hermione.lilliput.linux.it> From: GM Date: Sat, 19 Feb 2022 19:00:43 +0000 Message-ID: To: Proxmox VE user list X-SPAM-LEVEL: Spam detection results: 0 BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain FREEMAIL_ENVFROM_END_DIGIT 0.25 Envelope-from freemail username ends in digit FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider HTML_MESSAGE 0.001 HTML included in message KAM_SHORT 0.001 Use of a URL Shortener for very short URL NUMERIC_HTTP_ADDR 1.242 Uses a numeric IP address in URL POISEN_SPAM_PILL_4 0.1 random spam to be learned in bayes SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [PVE-User] 2 host cluster, direct link: best configuration? X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Feb 2022 19:01:32 -0000 I'd personally use option 1, dedicated nic(s) or vlans for LAN and Corosync network.Then I'd use the dedicated 10G link only for storage replication. All 3 networks would be setup on different network subnets. Storage replication uses "migration network" for the replication, so you could setup that on the dedicated 10G link, so that it does not interfere with the corosync/lan traffic. Migration network can be setup either via the datacenter.cfg or via the web gui (Datacenter -> Options -> Migration settings). On Sat, 19 Feb 2022 at 16:10, Marco Gaiarin wrote: > > We have to setup a little 2 node cluster, with symmetrical nodes, using > replication. > > For that, we have added a 10G interface, and setup a direct link between > the > two server. > > But how is better to setup the link? Some ideas: > > 1) another network, different from LAN > > pro: simple > cons: replica happen only on cluster/corosync interface? So i have to > setup corosync on direct link addresses? > > > 2) ip override; eg LAN interfaces are 10.37.5.21/21 and 10.37.5.22/21; > direct link interfaces are 10.37.5.21/32 and 10.37.5.22/32, and an > explicitly route to other host > > pro: if direct link go down, we can simple tear down interfaces > cons: no auto, interfaces have to tear down manually > > > 3) setup a bridge around LAN and direct link cable, setup STP and leave the > switches all the work. > > This config suggested, more or less, by: > https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server > > > Thanks. > > -- > Io chiedo quando sara` che l'uomo potra` imparare > a vivere senza ammazzare e il vento si posera` (F. Guccini) > > > > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > >