Looks like the extra $$ for the pro isn't worth it really

Well I forgot to cancel my order so now I have shipping confirmation for both PRO and EVO for my skull canyon nuc. Will probably return the PRO

yes indeed, not worth it, and next year there will be a newer and better model 🙂

If you were using it in a box with enough RAM to put a density of VMs on that would stress it then sure, go with the Pro. But by being limited to 32GB, you are not going to run out of IOPS before you run out of RAM 🙂

Thanks guys! Agreed. I had ordered both trying to see which would get here first since both were on backorder. Good points.

Right, as long as you're on NVMe you're all good

What color coding are you guys using for Ethernet cables? I'm thinking about something like this: • Blue = switch A • Green = switch B • Yellow = PoE devices • Red = WAN links

Pink and green stripes = least-favorite customers

@Jason Samuel Whatever cables I can find laying around!

Haha, trying to be somewhat organized. Right now I have a jumble of colors and it's hard to see what's doing what sometimes. I probably need colors for IPMI/iLO/LOM and uplinks too.

I just paste labels on both ends so I or anyone else can tell what it is.

Will be doing that too. I just see organization like this and want to see if I can pull off something similar.

1. I don't have enough devices to need that. 2. My servers look like the spiderwebs I grew up troubleshooting 🙂

Haha geez I could wish

how. i can't stop staring at that picture

*wow

Woot

"Resolved" the usb nic issue

👍

I say that because i'm not quite sure, other than a driver issue, it is happening

what fixed it?

openvswitch: vif8.0: dropped over-mtu packet: 1502 > 1500

ah ha. so it was MTU!

I changed the mtu on the interface to be 1505 and volia

Those were in dmesg

But it doesn't make sense

the interfaces were set for 1500. I tested pinging with a 1472 packet

Which worked

1473 failed, which is normal

odd that increasing the MTU fixed it. Usually I have to lower it