nblr06
Enthusiast
Enthusiast

log4j workaround for vcenter external PSC?

Jump to solution

i just found  https://kb.vmware.com/s/article/87081

my vcenter is vsersion 6.7 build 48000 with some external PSCs,

does anyone know what is the recommended workaround sequence for such environment?

should I perform on PSC or VC first? some nodes should be shutdown first when performing the workaround?

(i only know that if i want to upgrade vcenter to version 6.7 Update 3p, which is an unmitigated version, then i should do the upgrade first so that i won't waste time on doing the workaround again...)

0 Kudos
1 Solution

Accepted Solutions
Alex_Romeo
Leadership
Leadership

Hi,

it's not important which sequence you run the workaround, but it is important that you run it on both (psc and vCenter).
I would do like this:
1) Update psc and vCenter version 6.7 Update 3p
2) LOG4j workaround at PSC
3) LOG4j workaround at vCenter.

when you upgrade, I recommend that you consider bringing the internal PSC.

https://kb.vmware.com/s/article/87081

Alex_Romeo_0-1640703477245.png

 

regards,

Alex_Romeo

Blog: https://www.aleadmin.it/

View solution in original post

0 Kudos
1 Reply
Alex_Romeo
Leadership
Leadership

Hi,

it's not important which sequence you run the workaround, but it is important that you run it on both (psc and vCenter).
I would do like this:
1) Update psc and vCenter version 6.7 Update 3p
2) LOG4j workaround at PSC
3) LOG4j workaround at vCenter.

when you upgrade, I recommend that you consider bringing the internal PSC.

https://kb.vmware.com/s/article/87081

Alex_Romeo_0-1640703477245.png

 

regards,

Alex_Romeo

Blog: https://www.aleadmin.it/
0 Kudos