After an onsite cluster deployment, the As-Built Guide is a crucial document that provides detailed information about the final configuration of the system. However, certain data in the As-Built Guide might require adjustment or might be missing completely.
In this case, the Nutanix Node Port Layout (Option A) and the Physical Rack Layout (Option C) are two data that might require adjustment or might be missing completely. The Nutanix Node Port Layout provides a visual representation of the network connections for each node in the cluster, while the Physical Rack Layout provides a visual representation of the physical arrangement of the nodes in the rack. Both of these data are crucial for understanding the physical and network configuration of the cluster, and any inaccuracies or omissions in these data could lead to confusion or issues in the future.
Therefore, the consultant should ensure that the Nutanix Node Port Layout and the Physical Rack Layout in the As-Built Guide are accurate and complete.
References:
* [Nutanix Support & Insights]
* [Nutanix Community]
* [Nutanix Documentation]
* [Nutanix Certified services - core (NCS-Core) 6.8 - Nutanix University]
* [Nutanix Bible]
* [Nutanix Certified services - core (NCS-Core) 6.8 Playlist - YouTube]

For a newly deployed Nutanix system where the customer has specified VLAN 10 for management traffic, the consultant should recommend using VLAN 10 for both CVM and AHV host traffic. This VLAN designation ensures that all management, monitoring, and internal cluster communication are on a dedicated network, separate from production VM traffic (VLAN 20) and backup/replication traffic (VLAN 30), thereby enhancing network security and performance.References:
* Nutanix University - NCS-Core 6.8 Learning Path
* The Nutanix Bible, Network Configuration chapter (https://www.nutanixbible.com/)

Explanation
Ref:https://next.nutanix.com/installation-configuration-23/physical-relocation-of-nutanix-clusters-38403

The As-Built Guide is a comprehensive document typically prepared at the end of a Nutanix deployment project. It includes detailed information about the Nutanix environment, such as IP addresses, storage container settings, hardware and software configurations, and other deployment specifics. This document serves as a reference for the customer to understand their deployed infrastructure and for any future modifications or troubleshooting needs.
References:
* Nutanix Bible: Documentation and Reporting
* Nutanix University: Deployment Best Practices

Ref:
rx_crc_errors are caused either by faults in layer 1 (in the past, we have seen failed twinax cables and incorrect types of fibre being used), or issues with jumbo frames on the network. In an environment with 10 Gig switches that use cut-through forwarding (Cisco Nexus, Arista, Cisco devices using IOS default to Store and Forward switching), any packets that come into the switch will get forwarded out the destination interface once the switch has read the destination MAC address. If that packet has an MTU over what is configured on the interface, it will cut off the packet at the designated MTU, causing the server to receive a malformed packet, which will throw a CRC error.
If you have a layer 1 issue, you will see rx_crc_errors, not on all but one or two nodes.