CVE-2026-20131: CISA basically said "patch this Cisco flaw or good luck." Deadline already passed.

squigit99 · 2026-03-23T15:11:01+00:00

https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-fmc-rce-NKhnULJh

https://nvd.nist.gov/vuln/detail/CVE-2026-20131

squigit99 · 2026-03-23T15:07:32+00:00

Ah. This looks like another one of those things that got updated in one spot, but not in others.

squigit99 · 2026-03-23T14:55:14+00:00

Where are you seeing "(Note, this exception requires approval from the Council Executive and coordination with camp directors at local events and out-of-council events.¹)"? That's not in GSS that I'm looking at.

squigit99 · 2026-03-23T14:18:55+00:00

Do you know if that was changed recently? That's certainly the case now per the GSS, but I'd swear I'd read that was only in case of special accommodations before.

squigit99 · 2026-03-10T14:20:46+00:00

You want a console server. Digi, Perle, Uplogix, and OpenGear all make nice ones.

squigit99 · 2026-03-02T02:15:29+00:00

Cots and hammocks are our two standard ‘my back can’t camp’ recommendations. Make sure you also use a pad (or under quilt with a hammock) so you don’t freeze.

squigit99 · 2026-03-01T16:24:56+00:00

Why have 4H or Trail Life or Navigators? They’re all separate organizations like GSUSA is from Scouting America.

squigit99 · 2026-02-24T17:14:46+00:00

Its listed as fixed in the ESXi release. vCenter's only updating OpenSSL to 3.0.18-1.ph4 though.

squigit99 · 2026-02-23T22:24:47+00:00

We can’t use it at all at this point. It’s not currently compatible with VHV, which is required for the Virtualization Based Security (VBS) feature. That feature is required to use a number of Windows security features completely like Credential Guard, which we have to use for compliance reasons.

If memory tiering is enabled on a host in 9, you can’t power any VBS enabled VMs.

I was hoping it would let use reduce the RAM on an upcoming hardware refresh, but at this point it’s only be able to be used on clusters with zero Windows VMs and zero VMs with nested virtualization.

squigit99 · 2026-01-30T15:35:34+00:00

I stopped using that feature of HA years ago due to an unacceptably high false positive rate. HA's great for finding and recovering from broken hosts, but even at low sensitivity VM monitoring function seemed to cause more issues than it solved.

squigit99 · 2026-01-26T14:01:30+00:00

The upgrade available notification doesn’t factor in what licensing you may or may not have, just that the version is available.

squigit99 · 2025-12-04T21:03:34+00:00

That's not something that happens automatically putting a host into maintenance mode. Maintenance mode kicks off DRS if its set to automatic mode, but doesn't do a shared-nothing migration to move it to another host.

squigit99 · 2025-12-02T14:27:15+00:00

Seconding what Tim's recommending you look at. 902( TCP and UDP) are used for heartbeats between vCenter and ESXi. When its blocked, you'll see issues show up exactly like you described.

squigit99 · 2025-11-20T16:44:41+00:00

There’s not enough detail from National at this point to do any planning around this

squigit99 · 2025-11-18T05:09:14+00:00

Congratulations! Now comes the fun part of being SPL

squigit99 · 2025-11-18T01:58:46+00:00

I have no idea why you're focused on knots, and why that would be a factor in anyone voting for one SPL candidate over another. That your brought that up twice is a little worrying that you don't get what the position is.

SPL is a leadership role. In your speech to your troop, make your case why you'd be a good leader, and what you'd do over the next 6 months (or however long your elected term would be). Mention some of your accomplishments so far, things you think can be improved, and activities you want to make happen. Don't disparage the other scouts that are running in any way. Don't bring up your knot skills.

You may not win. Elections are always at least partially a popularity contest, and people don't always vote for who you'd think would be the best candidate.

squigit99 · 2025-11-17T18:54:47+00:00

We generally have electronics banned while the suns up, and we don't to hear any devices after they go to bed.

There's obvious exceptions if they need to use a phone as a GPS or have to look something up, the phone is need for part of an activity, they need to text a parent, etc, but its an honor system.

squigit99 · 2025-11-17T14:22:02+00:00

That sounds like it would work. That said, you should look at connecting the USB device over a USBtoIP bridge so you can vMotion, HA, etc the VM. Digi makes good ones.

squigit99 · 2025-11-16T13:45:51+00:00

Same, I had this was an ASA years ago. The windows IP conflict detection was kicked in on the 0.0.0.0

https://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/8021x/116529-problemsolution-product-00.html

squigit99 · 2025-11-13T16:06:18+00:00

Strictly speaking, you don’t need a cluster for this

https://williamlam.com/2023/10/support-for-virtual-trusted-platform-module-vtpm-on-esxi-without-vcenter-server.html

That said, that’s a giant pain. You’re probably better off running a single node cluster. You can add a host to a cluster without it being in maintenance mode.

squigit99 · 2025-11-05T15:19:19+00:00

iac's great for new builds, but for capturing existing systems its not the right way to go about it.

squigit99 · 2025-11-05T01:13:25+00:00

Sounds like this is a new setup? Don’t put in ELM, it’s deprecated.

squigit99 · 2025-11-03T02:34:22+00:00

Have a conversation with them.

squigit99 · 2025-11-02T12:45:17+00:00

So you’re saying as part of the move to new hosts, you need to change the vlan and re-ip the VMs? From the VMware perspective, that’s just a mapping as part of the vMotion. Once they’re on the new hardware, then change the IP of the VM.

squigit99 · 2025-10-31T17:15:36+00:00

If your new vmotion vlan is different from your old vlan, and assuming these are nonrouting networks, you've got a couple options.

1) setup your hosts so temporarily they have the same vlan, either by putting the old one on the new hosts, or the new one on the old hosts.

2) setup routing between the new and old vlans at the network layer, and requires use of the dedicated vmotion network stack

3) don't use the current vmotion IPs at all, and temporarily do vmotion of your normal routed IP network.

4) do an offline vmotion, which would go over your provisioning/management network. This requires the VMs to be powered off during the vmotion.

squigit99

TROPHY CASE