So I guess you want to teach me I should use an other MTU? is also the value from the guide
The time did differ to my local time over 8hours, but how much the difference between all 3 nodes was, I didn't take a look at.
your command succeeded as well, this was/is the output:
root@pve01:~# ping -M do -s 3972 10.0.0.82
PING 10.0.0.82 (10.0.0.82) 3972(4000) bytes of data.
3980 bytes from 10.0.0.82: icmp_seq=1 ttl=64 time=0.527 ms
3980 bytes from 10.0.0.82: icmp_seq=2 ttl=64 time=0.483 ms
3980 bytes from...
just edited my post above, right now timesync is not working :) will report back.
I did tests like ping/ssh from one node to each other, working on all 3 nodes, but this was also the case with @scyto documentation
Ok adjusted everything, same problem, now it is done like documentation of your proxmox link. Here for comparison the new frr file:
root@pve03:~# cat /etc/frr/frr.conf
# default to using syslog. /etc/rsyslog.d/45-frr.conf places the log in
# /var/log/frr/frr.log
#
# Note:
# FRR's configuration...
followed the guide from @scyto but will try to add the parts that are not mentioned by him to my config now :)
just for later comparison, this is my actual frr.conf:
root@pve03:~# cat /etc/frr/frr.conf
frr version 9.1
frr defaults traditional
hostname pve03
no ipv6 forwarding
service...
that is correct followed the guide from scyto (https://forum.proxmox.com/threads/intel-nuc-13-pro-thunderbolt-ring-network-ceph-cluster.131107/page-5#post-625262), will test with 29
@jsterr
Ok I setup everything from scratch and have my working thunderbolt network up and running. Unfortunately it leads all to the same error.
I installed it with the following commands:
pve01 = 10.0.0.81
pve02 = 10.0.0.82
pve03 = 10.0.0.83
pveceph install --repository no-subscription...
Ok now I have the problem with CEPH :/
Installed the reef version as it is the latest one.
root@pve03:~# pveceph mon create --mon-address 10.0.0.83
monmaptool: monmap file /tmp/monmap
epoch 2
fsid bfe7330e-54a8-47e7-9fff-9a0fe263d43b
last_changed 2024-01-17T17:40:07.141415+0100
created...
something I noticed during my tests with the FRR configuration (maybe you could add this to your guide?)
I tryed just starting with a complete empty /etc/frr/frr.conf and restarted the service afterwards and checked if nothing was added by the daemon itself (it was still empty)
then I take a...
Hi Scyto, this is already my 2nd attempt to get it up and running. Last time I tried it with IPv6 now I try the IPv4 route. Here are all the answers to your questions, but first of all: thank you for your awesome work!
1. yes a real INTEL NUC not one from an other manufacturer (here the output...
Hey guys, just hope someone can help here. I followed the gist to the end and ended up with a 3 node cluster (NUC 13 pro) that is having a working connection after the 'vtysh -c "show openfabric topology"' was done the first time. I see 10.0.0.81, 82 and 83 there on any node.
If I reboot one...
Hey guys,
I have setup my new thunderbolt 4 cluster that can connect to each other over the Thunderbolt 4 cables. (SSH to each of the others from each other tested f.e., also iperf ping etc.).
Unfortunately I'm trying hard to get my Ceph up and running, I always run into timeouts on creating...
If I remember right, it was the mainboard or something hardware related to my PC from minisforum. But 2 years have past… I’m not 100% sure! Bought a new conbee stick and other mini PC to run my small homelab and never got and issue again. Sry that I can’t help you really with this answer :/
Hey guys, I recently bought 3 Intel NUC 13th gen mini PCs that have 1 M2 and 1 M2-Bkey SATA inside. Unfortunately they lack of mutiple LAN ports.
I plan on using CEPH on those 3 devices with the NVMe M2 SSDs. The OS should be installed on the M2 B-Key SATA drive.
So I read through the forum /...
Hi "Max",
I followed the instructions exactly, I restarted the Raspberry yesterday and since then it is running again... I guess the service was "broken", but I keep an eye on it next time it is 0 again.
Hey there, I have a QDevice that seems to not vote from time to time, how can I fix this?
Yes the raspberry Pi is running and the service as well on this device.
Ok first thing is solved now... just found out that the host I was trying to ping got only a subnet /29 instead of the correct /28....
The problem with the DNS still exists, maybe you can help with that? :)
First thank you for taking a bit of your time for my issue.
Here is what you wanted:
/etc/resolv.conf
root@gateway:~# cat /etc/resolv.conf
search mydomain.local
nameserver 10.0.42.2
nameserver 10.0.42.3
pct config 47007
root@gateway:~# pct config 47007
arch: amd64
cores: 4
hostname: testLXC...
Hey Guys,
i have setup a new LXC with Ubuntu 22.04.
My host is setup to use my adguard as its DNS server. All other LXCs should use exactly the hosts settings for DNS.
you guessed it, the /etc/resolv.conf is showing the gateways IP instead for the nameserver.
Tested this on 3 other test LXC...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.