Daniel Micanek virtual Blog – Like normal Dan, but virtual.
vExpert Applications are Open! Don’t miss out on the opportunity to join this amazing program & community. Applications will be open from June 1st, 2020 to July 19th, 2020 and the awards will be announced on July 17th. Apply for vExpert 2020 What the Program is About The vExpert Program is […]
VCPs and VCAPs Around the World: Are you on the map?
VMware Certified Professional (VCP) and VMware Certified Advanced Professional (VCAP) represents two of the most popular levels of certification offered by VMware to validate your knowledge and skills. These certifications provide many benefits and span across five tracks including: Data Center Virtualization Cloud Management and Automation Desktop and Mobility Network Virtualization Digital Workspace. The post VCPs and VCAPs Around the World: Are you on the map? appeared first on VMware…Read More
Lets take a quick look at eVPN and find out how to configure eVPN between NSX-T and a Cisco ASR9000!
After one year of writing, 51.142 words, and 280 pages; I’m very excited to announce that the vRealize Network Insight Cookbook is now available!
SAP HANA is very intensive for memory operation. With ADDDC Sparing We can add System reliability. It is optimized by holding memory in reserve so that it can be used in case other DIMMs fail. But there Could be another problem with.
For more information – Intel® Xeon® Processor Scalable Family Specification Update, # SKX108:
Problem: Under complex microarchitectural conditions, a memory controller that is in VirtualLockstep (VLS) may hang on a partial write transaction.
Workaround: It is possible for BIOS to contain a workaround see below.
Implication: The memory controller hangs with a mesh-to-mem timeout Machine Check Exception(MSCOD=20h, MCACOD=400h). The memory controller hang may lead to other machine check timeouts that can lead to an unexpected system shutdown.
Cisco applied BIOS workaround for this scenario.
| Defect ID | Symptom |
|---|---|
| CSCvr79388 | Cisco UCS servers stop responding and reboot after ADDDC virtual lockstep is activated. This results in #IERR and M2M timeout in the memory system. This issue is resolved. |
| CSCvr79396 | On Cisco UCS M5 servers, the Virtual lock step (VLS) sparing copy finishes early, leading to incorrect values in the lock step region. This issue is resolved. |
I recommended to update ASAP, firmware 4.1(1c) is stable. Cisco THX!
On April 9th, 2020 VMSA-2020-0006 was published. This advisory documents a critical severity sensitive information disclosure vulnerability identified by CVE-2020-3952.
The vulnerability received a CVSSv3 score of 10 out of 10. Which means this is a very serious security issue. Response matrix is VMSA-2020-0006.
Additional Documentation for VMSA-2020-0006: Determining if a vCenter 6.7 deployment w/embedded or external Platform Services Controller (PSC) is affected by CVE-2020-3952 (78543)
https://kb.vmware.com/s/article/78543
Virtual Appliance Log File Location: /var/log/vmware/vmdird/vmdird-syslog.log or in /var/log/vmware/vmdird/vmdird-syslog.log.*.gz
zgrep "ACL" /var/log/vmware/vmdird/*.gz /var/log/vmware/vmdird/vmdird-syslog.log.x.gz:2020-xx-xxTxxxxxx+00:00 info vmdird t@xxxxxx: ACL MODE: Legacy
Notes from KB:
It is recommended to block any access over the LDAP port (389) except for administrative use.
Clean installations of vCenter Server 6.7 (embedded or external PSC) are not affected.
vCenter Server 6.7 (embedded or external PSC) prior to 6.7u3f is affected by CVE-2020-3952 if it was upgraded from a previous release line such as 6.0 or 6.5.
Path it ASAP because:
Thank You William for these Quick Tip.
On my HomeLAB I have older server with NOT supported CPU for ESXi 7.0. During install I had an error:
CPU_SUPPORT ERROR: The CPU in this host is not supported by ESXi 7.0.0. Please refer to the VMware Compatibility Guide (VCG) for the list of supported CPUs.
It could be fix during boot SHIFT-O:
allowLegacyCPU=True
CPU_SUPPORT WARNING: The CPU in this host is not supported by ESXi 7.0.0. Please refer to the VMware Compatibility Guide (VCG) for the list of supported CPUs.
On ISO image VMware-VMvisor-Installer-7.0.0-15843807.x86_64.iso is \UPGRADE\PRECHECK.PY script which is checking it during instalation.
On line 1720 we could see our solution allowLegacyCPU = True …
Disclaimer: This is not officially supported by VMware and you run on your own risk.
Automated vSphere 7 and vSphere with Kubernetes Lab Deployment Script
I know many of you have been asking me about my vSphere with Kubernetes automation script which I had been sharing snippets of on Twitter. For the past couple of weeks, I have been hard at work making the required changes between the vSphere 7 Beta and GA workflows, some additional testing and of course […]
After sucessfull ESXi 7.0 upgrade. We can start using vSphere Lifecycle Manager and convert VUM Baselines -> vLCM Image.
We are excited to announce the general availability of VMware NSX-T™ 3.0, a major release of our full stack Layer 2 to Layer 7 networking platform that offers virtual networking, security, load balancing, visibility, and analytics in a single platform. NSX-T 3.0 includes key innovations across cloud-scale networking, security, containers, and operations that help enterprises achieve one-click public cloud experience wherever their workloads are deployed. As enterprises adopt cloud,…Read More
