Pass the Nutanix Certified Professional (NCP) NCP-MCI-6.5 Questions and answers with ExamsMirror

Prism is the central service control used by Nutanix to manage the clusters. It provides a unified view of the entire system, and it is used to control the HTML5 UI, the nCLI, and the REST API. Prism is used to manage the resources of the system, such as the nodes, storage, and networks, as well as to monitor the performance of the system and the applications running on it.

https://www.nutanixbible.com/2f-book-of-basics-cluster-components.html

PrismKey Role: UI and API

·  Prism is the management gateway for components and administrators to configure and monitor the Nutanix cluster.  This includes Ncli, the HTML5 UI, and REST API. 

·  Prism runs on every node in the cluster and uses an elected leader like all components in the cluster. All requests are forwarded to the leader using Linux Iptables. This allows access to PRISM using any CVM Ip address.

·  Prism communicates with Zeus for cluster configuration data and Cassandra for statistics to present to the user. It also communicates with the ESXi hosts for VM status and related information

These are only some of the essential services that make up the CVM functionality. For more information on all the services and various Nutanix Cluster components, refer to the portal documentation.

According to the Nutanix Prism Element Guide, Prism Element uses a single SSL certificate on a Nutanix cluster. The certificate is used to secure the communication between the web browser and the Prism web console. The certificate is also used to authenticate the cluster to external services, such as Active Directory, SMTP, and SNMP. The certificate can be either self-signed or signed by a trusted certificate authority (CA). The certificate can be replaced or renewed through the Prism web console or the ncli command-line interface.

One of the possible reasons for a cluster to transition out of NearSync is insufficient network bandwidth between the source and target clusters. NearSync requires a minimum network bandwidth of 10 Mbps per VM for replication3. If the network bandwidth is lower than the required amount, the replication of recovery points may take longer than the configured RPO, resulting in an Out of NearSync condition. To address this issue, you can increase the network bandwidth between the clusters or reduce the number of VMs protected by NearSync4.

References: 1: Stargate - Nutanix Bible 2: Nutanix Cluster Architecture Overview - Nutanix Bible 3: NearSync Disaster Recovery (RPO <= 15 minutes) - Nutanix Support & Insights 4: Transitioning in and out of NearSync - Nutanix Support & Insights

According to the web search results, one possible cause of inter-VM communication failure between hosts is that the switch is not configured to allow VLAN 15 traffic. VLAN 15 is the default VLAN ID used by AHV for internal communication between CVMs and hosts. If the switch blocks or drops VLAN 15 packets, it will prevent inter-VM communication across hosts4. To enable full inter-VM communication, the administrator should update the switch to specifically allow VLAN 15 traffic on the ports connected to the AHV hosts.

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 Nutanix Support & Insights web search result1, the name of the internal bridge used by AHV nodes and CVMs is br0. The internal bridge is an Open vSwitch (OVS) bridge that connects the AHV host management interface, the CVM interface, and the VM vNICs. The internal bridge also acts as a gateway for the CVM and VM traffic to reach the external network through the host physical NICs.

A Compute Only node is a node that does not have any local storage devices and only provides compute resources to the cluster2. A Compute Only node does not run a CVM, but instead relies on the CVMs of other nodes to access the distributed storage fabric2

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.