VCP-VMC 2022 2V0-33.22 VMware Study Notes

"It is a good idea to periodically monitor the CPU usage of the host. This can be done through the vSphere Client, using the VMware vRealizeOperations management suite, or by using resxtop. Below we describe how to interpret resxtop" https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/vmc-aws-performance.pdf

• Use the VMware vSphere Client to connect to the VMware vCenter which manages the virtual machine and examine its performance statistics. You can use charts, alarms, and events to identify CPU bottlenecks or contention.
• Use the Troubleshooting Workbench in VMware vRealize Operations Cloud to look for potential evidence. You can use dashboards, alerts, metrics, logs, and recommendations to diagnose and resolve CPU performance issues.

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/vmc-aws-performance.pdf

Kubernetes is an open-source container orchestration system that provides automated deployment, scaling, and management of containers. It can be used to set up an automated restart policy for containers in the event of a failure, ensuring that containers are automatically restarted when they fail.

VMware Stage Manager User's Guide

https://www.vmware.com/pdf/stagemanager1_Users_Guide.pdf

Port mirroring is a VMware Cloud tool that an administrator can use to forward all the monitored traffic to a network appliance for analysis and remediation. The network appliance can then analyze the mirrored traffic and take the appropriate remedial action. Port mirroring can also be used to identify and troubleshoot network issues, as well as monitor network activities.

Port mirroring lets you replicate and redirect all of the traffic coming from a source. The mirrored traffic is sent encapsulated within a Generic Routing Encapsulation (GRE) tunnel to a collector so that all of the original packet information is preserved while traversing the network to a remote destination.

Port mirroring is used in the following scenarios:

• Troubleshooting - Analyze the traffic to detect intrusion and debug and diagnose errors on a network.
• Compliance and monitoring - Forward all of the monitored traffic to a network appliance for analysis and remediation.

Port mirroring includes a source group where the data is monitored and a destination group where the collected data is copied to. The source group membership criteria require VMs to be grouped based on the workload such as web group or application group. The destination group membership criteria require VMs to be grouped based on IP addresses. Port mirroring has one enforcement point, where you can apply policy rules to your SDDC environment.

The traffic direction for port mirroring is Ingress, Egress, or Bi Directional traffic:

• Ingress is the outbound network traffic from the VM to the logical network.
• Egress is the inbound network traffic from the logical network to the VM.
• Bi Directional is the traffic from the VM to the logical network and from the logical network to the VM. This is the default option.

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws-networking-security/GUID-3268A0D3-89D0-406F-B44F-156DD1A30E00.html

According to the VMware Cloud on AWS documentation, the minimum capacity of an i3.metal host is 8 vCPUs and 64 GB of memory. Therefore, to meet the demand of an additional 60 cores and 640 GB of memory, the administrator should add two i3.metal hosts to the cluster. For more information, please refer to the official VMware Cloud on AWS documentation at: https://docs.vmware.com/en/VMware-Cloud-on-AWS/index.html.