Pass the Nutanix NCS Professional NCS-Core Questions and answers with ExamsMirror

When VMs on the same node can communicate but fail to connect to other parts of the network following changes made to Top of Rack switches, the issue often stems from a VLAN configuration error on the switches. VMs on the same node communicating successfully indicates that the local switch configuration is intact, but inability to reach external network segments points to an incorrect VLAN setup on the broader network, likely introduced during the recent changes to the Top of Rack switches.References: Nutanix Networking Guide, Troubleshooting Network Connectivity in Nutanix.

Before arriving onsite, the consultant should set up the SMTP server to allow emails from both the Cluster Virtual IP Address (VIP) and the Controller Virtual Machine (CVM) IP addresses. This setup ensures that Prism can successfully send email notifications through the customer's mail server about any errors or notifications generated by the Nutanix environment, as both the Cluster VIP and CVM IPs are sources from which Prism sends alerts.References: Nutanix Bible, Nutanix University NCS-Core 6.8 learning materials

Considering the equipment setup with one Out-of-Band Management (OOBM) Ethernet switch and two 10GbE SFP+ Top of Rack (ToR) switches, the consultant should recommend six DAC (Direct Attach Cable) 10GbE cables and three Ethernet cables. The DAC 10GbE cables are suitable for connecting the nodes to the ToR switches to handle high-speed data transfers, while the Ethernet cables are necessary for connections related to management purposes, such as connecting to the OOBM switch for remote management tasks. This recommendation ensures adequate connectivity for both data and management networks.References: Nutanix Hardware and Installation Guide, Best Practices for Network Cable Management.

ref http://www.joshodgers.com/tag/cpu-ready/

Ref: https://portal.nutanix.com/page/documents/details?targetId=Files-v3_6:fil-file-server-quotas-c.html#nconcept_amp_xsm_bx

In this scenario, the connectivity issue arises because the VLAN settings require a specific configuration on the vSwitch settings when using LACP. When using LACP for load balancing network traffic, the vSwitch or Distributed Switch must be configured with the "Route based on IP hash" load balancing algorithm. This setting is necessary to properly distribute the traffic across the LACP bonded links. Not selecting this setting in vSwitch0 settings would result in improper handling of network packets over the LACP bonded links, thereby causing the hosts and CVMs to be unreachable. Adjusting the vSwitch settings to "Route based on IP hash" should resolve the connectivity issue.References: VMware vSphere Networking documentation, Nutanix Bible LACP configuration guidelines.

To verify that a Nutanix cluster can tolerate a single-node failure, the consultant should use the command nutanix@cvm~$ ncli cluster get-domain-fault-tolerance-status type=node. This command is executed from the Controller Virtual Machine (CVM) and checks the cluster's fault tolerance status specifically for node failures, providing insights into how the cluster's data resiliency and redundancy configurations are holding up against potential single-node failures.References: Nutanix CLI Guide, Nutanix Fault Tolerance Documentation.

For continuing the cluster deployment without an NTP server immediately available: A. An NTP server is not required for the initial foundation process of the cluster and can indeed be added later. This allows the deployment to proceed without delays, although it's critical to add NTP synchronization as soon as possible post-deployment to ensure proper cluster time management. B. If an NTP server is to be provided using an FQDN, then a DNS server must indeed be available. This is because the FQDN needs to be resolved to an IP address, which requires DNS resolution services. Options C and D are not strictly required as per Nutanix deployment standards; a single NTP server can suffice initially, and there's no requirement for it to be external or in a comma-separated list unless specifically dictated by network or organizational policies.References: Nutanix Installation and Configuration Guide, Nutanix Foundation Tool documentation.

Before going on-site to deploy a Nutanix cluster, the following prerequisites are crucial:

A. Complete the kickoff call and validate the BOM (Bill of Materials): This ensures that all necessary components are accounted for and any discrepancies or missing items are addressed prior to installation.

C. Validate whether the cluster questionnaire is complete and if the physical switch configurations are complete: Ensuring that all relevant customer and network information is obtained and validated is critical to avoid delays or issues during the physical installation and configuration of the cluster.

References:

Nutanix Bible (https://www.nutanixbible.com ), particularly sections on pre-deployment planning and validation.

Nutanix University: NCS-Core 6.8 Training (https://university.nutanix.com ), covering the importance of thorough preparation and documentation before on-site engagements.