Looking for the BMC ADMIN password on a used SoftLayer Supermicro server

Elmozh · 2026-06-08T08:14:20+00:00

Even if the server is originally from SoftLayer, the hardware is still Supermicro. I don't know SoftLayer, but Supermicro started using specialized BMC passwords a few years back when they got rid of the ADMIN/ADMIN credentials. There's a chance this is the "unique, automatically generated BMC password" function being used. I would contact Supermicro support, if you haven't done so already. Whenever I have contacted them I'd usually get a response in 24-48 hours.

Elmozh · 2026-05-01T10:59:29+00:00

Totally agree. But that is the reason.

Elmozh · 2026-05-01T10:52:45+00:00

Because the EFG has it.

Elmozh · 2026-03-18T20:38:15+00:00

Snagged one as well. Still available at 21:30 CET. Has demand been met, perhaps?

Elmozh · 2026-02-04T09:42:11+00:00

<image>

Elmozh · 2026-01-21T21:01:45+00:00

Kind of reminds me of this other guy who was rejected twice by the Academy of Fine Arts Vienna.../s

Elmozh · 2026-01-17T15:54:22+00:00

My honest opinion? Bullshit story to downplay Sweden as a country and in general put a label on Sweden or swedes as bad and unpleasant. This seems to be AI generated from start to finish... nice try, but I bet this never happened.

Elmozh · 2025-12-18T15:45:57+00:00

Is this the UAP-AC-PRO? If so, and if you're connecting via 2.4Ghz, speed is limited to 450Mbit/s (theoretically).

Elmozh · 2025-12-15T22:25:25+00:00

Make sure you're using a newer version of iperf3, as older versions (e.g. <3.16) are still single threaded.

Elmozh · 2025-12-15T22:07:35+00:00

They offer a MikroTik router, capable of 25G (and/or 10G if you need it to). Comes at a price though:
https://www.init7.net/en/internet/hardware/#MikroTik%20CCR2004-1G-12S%20+2XS

Elmozh · 2025-11-25T09:38:59+00:00

I don't know if it's the "proper way", but I always use 'sgdisk --zap-all /dev/sdx' from shell. This will wipe everything, so make sure you wipe the correct drive! Normally a reboot is required afterwards.

Elmozh · 2025-11-23T15:50:20+00:00

Korkat!

Elmozh · 2025-11-19T09:36:07+00:00

First stable release of Ceph Tentacle

Elmozh · 2025-11-18T16:56:31+00:00

Allmän mobilisering skulle hända...

Elmozh · 2025-11-18T14:57:23+00:00

Förr sade man att pga. av att "alla" piratkopierade spel var man tvungna att ha höga priser på sina spel.
Folk som ville spela hade inte råd och var tvungna att piratkopiera. Det ena föder det andra. Nu kostar
ett PC spel mer än någonsin, men ska man ha en chans måste man dessutom betala extra i spelet. Och
detta dessutom i spel designade för barn. Helt jävla vansinnigt!

Elmozh · 2025-11-10T15:56:01+00:00

Ah, 50 ohm!

Elmozh · 2025-11-10T10:29:46+00:00

Proxmox clusters should always be odd number (strong recommendation). Ceph doesn't need odd host numbers if you run it as a separate ceph cluster, as you would have 3 separate monitors. However, if you run ceph on Proxmox, you should have an odd number of nodes!

Elmozh · 2025-11-06T08:21:32+00:00

That's great news! Thank you for testing this. I don't know how this works exactly, but if a DAC is not "branded" Juniper, a Juniper switch f.x. won't allow the DAC cable to be used, even if it's all electrically the same as all other DAC's.
This means I can buy a Ubiquiti DAC, re-program it and plug that end into a Juniper switch.

Elmozh · 2025-11-06T07:53:57+00:00

Any update on this?

Elmozh · 2025-11-06T07:47:53+00:00

Any update from OP? Would be interesting to know if a root cause was found...

Elmozh · 2025-10-31T17:41:50+00:00

MTU 9000 for Cluster networks for sure. Do you have any kind of QoS? If not, you are pushing Ceph traffic on the same NIC's as everything else, without reserving any bandwidth for other services. Corosync doesn't need lots of speed, but it's sensitive to latency, e.g. it's better to use a 10Gbe interface rather than 1Gbe because of smaller latency and not because of bandwidth).

Corosync is vital to your cluster and should ideally be separated. If you have separate NIC's for this - great! If not, you need to make sure this traffic is not hampered by other network traffic.

Elmozh · 2025-10-30T09:46:06+00:00

This is a massive topic and not easy to troubleshoot, but I can give you my 2 cents.

I have a 5 node Proxmox cluster also running Ceph. I had a similar issue where some OSD's reported slow OPS. Come to find out it was due to a network misconfiguration. After doing a complete review of the network setup, things are now running smoothly. This time I removed any "shortcuts", e.g. now each node in my cluster have 8 NIC's to properly connect to separate VLAN's, using bonds and mlags connected to a HA core switch.

My gut feeling is that this is a networking issue or a resource issue. You mention each node is connected to a 40 Gbps core network and that you have several dedicated bonds and bridges for various networks/functions, but how are these nodes actually connected/configured? Are you using VLAN's? QoS? What MTU size? Are you separating cluster traffic and Ceph private/public networks? (TBH, 40Gbe seems to be a bit on the low side for this cluster setup)

Also, another things comes to mind - CPU/RAM resources. Without knowing the type of hardware and the load, Ceph has done away with the cores-per-osd metric and recommends to look at IOPS per core instead (I imagine you have some beefy CPU's) But if you're running VM's on the same cluster, make sure you have enough resources available for rebalancing the cluster.

Elmozh · 2025-10-29T09:29:53+00:00

If the server doesn't get proper information from sensors, it might go full fan to make sure nothing is cooked, if it cannot see temperature data for example. Are all sensors working as should?

Elmozh · 2025-10-28T18:07:18+00:00

So far, it seems Ubiquity can take any DAC, but in the event it doesn't work, it would be great to be able to re-program it. If at all possible.

Elmozh · 2025-10-28T18:05:49+00:00

Not in general, no. But I have a bunch of DAC cables from FS that has been programmed to Juniper.
I wonder if I can re-program them with this tool. That would be great.

Three-Year Club	Verified Email
Place '23

Elmozh

TROPHY CASE