In modern data center architectures, the ability to deploy high-performance infrastructure without the complexity of Fabric Interconnects is a significant advantage. Running Nutanix Cloud Infrastructure (NCI) on Cisco UCS C-Series servers in Intersight Standalone Mode (ISM) provides a streamlined, cloud-managed footprint ideal for edge sites and enterprise data centers alike.

By leveraging the native integration between Nutanix Foundation Central and Cisco Intersight, the deployment process is highly automated, transforming manual hardware provisioning into a zero-touch software-defined workflow.

Infrastructure Strategy & Prerequisites

Before starting the deployment, it is critical to ensure all components are prepared for communication.

Architecture Overview

In ISM, Cisco UCS servers connect directly to standard Ethernet switches. This mode removes the requirement for Cisco Fabric Interconnects, while still providing full management through the Cisco Intersight cloud.

Software Requirements

• Prism Central (PC): An existing PC instance must be deployed with Foundation Central enabled from the marketplace.
• Cisco Intersight: A valid SaaS, Connected, or Private Virtual Appliance account is required.
• Network Services: Reliable NTP and DNS must be configured for all endpoints.
• Future Roadmap: Nutanix is developing Foundation Central as a standalone appliance. Once released, this will eliminate the current requirement for a pre-existing Prism Central during initial “greenfield” deployments.

Figure 1: High-level deployment workflow for Nutanix on Cisco UCS ISM.

Detailed Deployment Workflow

Phase 1: Claim Nodes into Cisco Intersight

The physical servers must be added to your Intersight account to enable remote orchestration.

1. CIMC Setup: Configure the Cisco Integrated Management Controller (CIMC) on each server with a static IP and DNS.
2. Retrieve Codes: Access the CIMC web interface, navigate to Admin > Device Connector, and copy the Device ID and Claim Code.
3. Target Claim: In Cisco Intersight, go to System > Targets > Claim a New Target. Select Cisco UCS Server (Standalone) and enter the codes to finish the claim.

Phase 2: Establish the Management Plane

Configure the Nutanix orchestration layer to manage the deployment.

1. Deploy Prism Central: If not already present, deploy a PC instance in your environment.
2. Enable Foundation Central: Within Prism Central, navigate to the Marketplace and enable the Foundation Central service.

Phase 3: Secure API Integration

Create a secure bridge between Nutanix and Cisco using API keys.

1. Generate Intersight Key: In Intersight, go to Settings > Keys > Generate API Key.
2. Configuration: Select API key for OpenAPI schema version 3.
3. Authentication: Save the API Key ID and download the Secret Key file.
4. Connect Hardware Provider: In Foundation Central, go to Settings > Connect Hardware Provider. Select Cisco Intersight, enter your API Key ID, and upload the Secret Key.

Phase 4: Initiate Automated Deployment

Launch the final orchestration process to form your cluster.

1. Node Discovery: In Foundation Central, navigate to Nodes > Onboard Nodes > Intersight Standalone Mode (ISM). Select the discovered nodes and click Onboard.
2. Cluster Configuration: Select your onboarded nodes and click Create Cluster. Enter the following:
   • Cluster Identity: Name, RF (Replication Factor), and Intersight Organization.
   • Software Images: URLs for the AOS and Hypervisor (AHV or ESXi) installers.
   • Networking: IP addresses for the CVMs, Hypervisors, Gateway, and Netmask.
3. Finalize: Submit the configuration. Foundation Central will automatically create the Intersight policies, assign server profiles, reimage the nodes, and form the cluster.

Conclusion

The combination of Nutanix Foundation Central and Cisco Intersight ISM provides a highly scalable and consistent deployment model. By removing manual hardware configuration steps, teams can focus on delivering application services with greater agility.

This guide is part of our internal technical knowledge base for hybrid infrastructure. If you are a technical lead managing a team in the field, ensure all ToR switch ports are set to trunk mode before starting Phase 4.

Modernizing your infrastructure doesn’t always require complex migrations. The Nutanix In-Place Hypervisor Conversion allows you to transform an entire cluster from VMware ESXi to AHV while keeping your data local and secure. This native “1-click” feature simplifies the transition significantly.

Critical Technical Prerequisites

Before initiating the conversion, verify these specific cluster and networking requirements:

• NGT Tools: You must install Nutanix Guest Tools (NGT) on all guest VMs, as they include the virt-io drivers required for VMs to boot up after the conversion.
• Networking: Every host must have one external vSwitch configured with a homogeneous uplink NIC team.
• NIC Selection: The NIC team should include all physical NICs of the chosen speed.
• Load Balancing: Note that LACP-based load balancing is not supported on the NIC team during this process.
• Post-Conversion State: The NIC team will automatically be set to an active/passive state once the conversion is complete.
• Disaster Recovery: All DR activities must be paused for the duration of the cluster conversion.
• VMware Features: Ensure both HA (High Availability) and DRS are enabled on the source ESXi cluster.

Step-by-Step Conversion Procedure

Following the official Nutanix workflow, here are the steps to execute the conversion via Prism Element:

1. Initial Configuration

• Log into the Prism Element web console.
• Click the Gear Icon (Settings) in the top-right menu.
• Select Convert Cluster from the Settings page.

2. Hypervisor and Boot Selection

• From the Available Hypervisor drop-down menu, select AHV.
• Choose your VM Boot Options:
  • Preserve power state: Select this to keep the original power state of your VMs (recommended for automated startup).
  • Power Off User VMs: Select this if you prefer to shut down all VMs manually before the process starts.

3. vCenter Validation

• Click Validate.
• Enter the vCenter Server IP Address and the administrator Username and Password.
• The system will run a validation check to ensure all prerequisites (Networking, NGT, and DR status) are met.

4. Binary Upload and Execution

• In the Software Upload dialog, upload the AHV ISO binary you downloaded from the Nutanix Support Portal.
• Click Convert Cluster.
• A confirmation message will appear. The cluster will transition to Read-Only mode for administrative tasks while the rolling conversion takes place.

Post-Conversion Expectations

• Duration: The total process usually takes 3 to 4 hours, depending on the size of the cluster.
• Availability: Because the conversion is performed in a rolling manner, individual VM downtime is typically less than 5 minutes.
• Tracking: You can monitor the live progress of the conversion through the Prism Task dashboard.

Conclusion

Transitioning to AHV reduces licensing overhead and prepares your environment for native Nutanix automation. By following these steps and prerequisites, you ensure a stable and predictable outcome for your critical workloads.