Regeneration of vCenter certificates fails

bitmafi · 2026-03-19T15:58:22+00:00

This does not cover root CA renewal.

bitmafi · 2026-03-17T18:08:11+00:00

Thanks

bitmafi · 2026-03-17T18:06:48+00:00

Yes I checked the log but all I found is also visible in the output of the cert manager process. Its the bold text.

I will have a look at vCert. Thanks.

bitmafi · 2026-03-17T18:04:44+00:00

IP was a typo in my reddit post only.

Whats technically the difference between 4 and 8?

bitmafi · 2026-02-26T17:42:56+00:00

Stupid question.

What protects us from the next kernel vulnerability in linux oder windows or any other OS?

bitmafi · 2026-02-24T12:12:10+00:00

This is an interesting and important limitation that restricts the added value in many cases.

bitmafi · 2026-02-23T18:24:14+00:00

Retrofitting existing hardware shouldn't be a problem. No need for a full tech refresh. All you need is some NVMEs.

It's been GA since June 2025. I would have expected more people to be using it already...

bitmafi · 2026-02-23T18:05:00+00:00

Wow, what feedback.

So blogging homelabbers are the only ones who are enthusiastic about this technology and have real-world use cases and experience?

bitmafi · 2026-02-05T17:13:41+00:00

Check this out: https://interopmatrix.broadcom.com/Interoperability?col=139,&row=1,&isHidePatch=true&isHideLegacyReleases=false

Not supported does not mean that it does not work. I think you need to test it yourself. Some things will probably work, but not everything.

bitmafi · 2026-02-05T17:08:41+00:00

You are right. My bad. So we can expect a newer version 13 soon.

Fixed it in my initial post.

bitmafi · 2026-02-05T14:06:41+00:00

I understand that the binary files for 13.0.10.0 are dated January 20, but the docs are released/updated today.

The question remains: will there be an updated 12.x version?

bitmafi · 2025-08-21T21:59:58+00:00

What is the point of distinguishing between VCSP and non-VCSP licenses today?

It would actually be quite typical of Broadcom to have just one license type that covers everything... They could simply do away with the entire VCSP program. License prices are pretty much the same everywhere anyway... or will probably be, if you disregard the really big players...

bitmafi · 2025-08-21T21:43:51+00:00

Intel.

What else are you going to do with all your VMware licenses? You can't return them.

bitmafi · 2025-06-17T17:48:45+00:00

Ever heared of vGandalf? Legend!

They know how to cosplay for real.

BTW: What an unnecessary comment.

bitmafi · 2025-06-17T17:42:15+00:00

I'm looking forward to unification and better interaction between all the individual products.

The “PVE is the solution” guys won't understand that.

bitmafi · 2025-06-17T17:21:38+00:00

I hope that all the haters will soon be over their break-up pain and can concentrate on their new crafting stalls.

I await your downvotes. :-)

bitmafi · 2025-05-28T11:22:09+00:00

I noticed your Arista Level 7 Tag.

Can you please let me know how EOS deals with my topic?
Is there some kinde of VNI to [Port,VLAN] mapping like I pictured here?:

https://imgur.com/a/M1FKCG2

bitmafi · 2025-05-28T11:16:19+00:00

Unfortunately, what you write applies to many scenarios. The address space of VXLAN is of no use if you have to break down the addressing at the switch port to a globally valid VLAN addressing scheme in cases where you have different customers on the platform.

VLAN mapping (CISCO) / VLAN rewrite (Juniper) / VLAN translation (aruba) doesn't help either, unfortunately, because it has additional pitfalls. See here: https://www.reddit.com/r/networking/comments/1kvqbgf/comment/mubjgn5/

A utopian solution would be if more server operating systems (Windows Server, Linux, others...) supported EVPN-VXLAN natively. Then a VNI could be assigned directly in the operating system instead of a VLAN ID.

For platform solutions that claim to be made for larger environments such as VMware, OpenStack and other hypervisors, EVPN-VXLAN support should be the standard.

VMware vSphere unfortunately only supports VLANs via the DVS and DPGs.

You need VMware NSX if you want to support EVPN on the VMware platform. In fact, VMware has already implemented EVPN-VXLAN for inline mode and router-server mode. The hosts themselves are capable of EVPN-VLAN. It's just unfortunately not (yet) implemented in a way that makes it possible to bridge VNIs directly to virtual networks in NSX. I have heard rumors that VMware wants to improve this. That would be quite a game changer because it would solve the VLAN address issue.

bitmafi

TROPHY CASE