Flow Networking is a feature that enables software-defined networking for AHV clusters. It allows users to create and manage virtual private clouds (VPCs), subnets, and network services such as NAT, DHCP, routing, and VPN. Flow Networking also supports service insertion and chaining, which enables integration with third-party network functions such as firewalls and load balancers. Flow Networking is built on top of the microservices infrastructure (MSP) in Prism Central, which provides the platform for running various Nutanix services such as Calm, Karbon, and Objects. Therefore, to enable Flow Networking, the MSP must be enabled first on Prism Central1. The MSP can be enabled from the Prism Central settings page or from the command line interface (CLI) of the Prism Central VM2. Enabling the MSP will also enable Flow Microsegmentation, which is another feature that provides network security and visibility for AHV clusters.

According to the web search results, the two impacts on the cluster that will result from increasing the vCPU count on all of the VDI VMs are:
Increase CPU utilization%: CPU utilization is the percentage of time that a CPU is busy executing instructions5. By increasing the vCPU count on all of the VDI VMs, the administrator will increase the demand for CPU resources on the cluster, which will increase the CPU utilization percentage6.
Increase CPU ready%: CPU ready is the percentage of time that a vCPU is ready to run but is waiting for a physical CPU to become available5. By increasing the vCPU count on all of the VDI VMs, the administrator will increase the contention for physical CPU resources on the cluster, which will increase the CPU ready percentage6. A high CPU ready percentage can indicate performance issues such as latency or slowdowns5.

According to the image description, the update source for LCM is configured to use the Nutanix Portal URL, which is a web address that requires internet access. The LCM inventory operation needs to download the latest manifest file and module files from the Nutanix Portal URL using port 801. If port 80 is blocked by a firewall, the LCM inventory will fail with an error message such as "Failed to get size of file at 5" or "The requested URL returned error: 403 Forbidden" as shown in the web search results23. To resolve this issue, the firewall rules need to be updated to allow port 80 traffic from the CVMs to the Nutanix Portal URL1.