Veganism Social

Thomas JensenLots of things changed in my <a href="https://fosstodon.org/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a> the last few weeks.- Replaced the Lenovo Thinkstation E32 node - 4 <a href="https://fosstodon.org/tags/Proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Proxmox</a> servers in cluster - <a href="https://fosstodon.org/tags/ProxmoxBackupServer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ProxmoxBackupServer</a> with qdevice - Each server having 2x <a href="https://fosstodon.org/tags/10Gbit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#10Gbit</a>, one being a dedicated SAN network - Enterprice NVMe for ZFS datastore - Replaced all fibers in the rack with DACsI'm seeing high temperatures in both my SFF nodes. Need to figure out a way to push some more air in. No fan headers, so I've ordered some <a href="https://fosstodon.org/tags/Noctua" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Noctua</a> S-ATA to 4-pin adapter (NA-SAC5).

Thomas JensenAfter a lot of back and forth; I decided to buy a <a href="https://fosstodon.org/tags/MikroTik" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MikroTik</a> CRS309-1G-8S+IN and dedicate it to the SAN. I thought a lot about 25 and 100 Gbit, but ultimately decided I'm not ready for the investment. Each server will have 2x <a href="https://fosstodon.org/tags/10Gbit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#10Gbit</a>, which will just have to do for now 🙂

Kevin Karhan :verified:<a href="https://infosec.space/tags/WasFehlt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WasFehlt</a>: vorgeschriebene <a href="https://infosec.space/tags/Kindersicherung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kindersicherung</a> bei <a href="https://infosec.space/tags/Koaxialkabel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Koaxialkabel</a>|n und <a href="https://infosec.space/tags/Kabelsanschluss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kabelsanschluss</a>-Dosen...Denn so sieht das aus wenn ein [mutmaßliches Nachbars-] Kind mutmaßlich ne Büroklammer in ne Kabeldose klemmt:<ul><li>Latenzen wie bei <a href="https://infosec.space/tags/Eutelsat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Eutelsat</a> <a href="https://infosec.space/tags/tooway" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tooway</a> ohne <a href="https://infosec.space/tags/PerformanceProxy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PerformanceProxy</a> und <a href="https://infosec.space/tags/Paketverlust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Paketverlust</a> wie <a href="https://infosec.space/tags/KaBand" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KaBand</a> in nem Schneesturm!</li></ul>Wenigstens ne Art Abdeckkappe wie bei Herdanschluss wäre 1NICE!<ul><li>die korrekte Lösung wäre natürlich <a href="https://infosec.space/tags/RechtAufGlasfaser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RechtAufGlasfaser</a> samt <a href="https://infosec.space/tags/FTTH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FTTH</a> in jede <a href="https://infosec.space/tags/Wohnung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Wohnung</a> in Form von <a href="https://infosec.space/tags/10GBit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#10GBit</a>/s <a href="https://infosec.space/tags/Ethernet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ethernet</a> auf <a href="https://infosec.space/tags/OS2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OS2</a> (oder bei kurzer Inhouse-Verkabelung <a href="https://infosec.space/tags/OM5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OM5</a>)-Faserpaaren!</li></ul>Und ja, <a href="https://infosec.space/tags/SharedMedia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SharedMedia</a> wie <a href="https://infosec.space/tags/GPON" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPON</a> / <a href="https://infosec.space/tags/XGPON" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XGPON</a> sind nur was <a href="https://infosec.space/tags/Funkst%C3%B6rungen" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Funkstörungen</a> angeht weniger problematisch als <a href="https://infosec.space/tags/DOCSIS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DOCSIS</a>-<a href="https://infosec.space/tags/Kabel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kabel</a>! <ul><li>Immerhin: <a href="https://infosec.space/tags/TechnikeristInformiert" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnikeristInformiert</a> und bestätigte meine Mutmaßung...</li></ul>

Recent searches

Search options

Administered by:

Server stats:

#10gbit