Cisco APIC Getting Started Guide, Release 6.2(x)

PDF

Cisco NX-OS to Cisco ACI POAP auto-conversion

Updated: January 12, 2026

Overview

This topic explains the Cisco NX-OS to Cisco Application Centric Infrastructure (ACI) power-on auto-provisioning (POAP) auto-conversion feature, which automates software upgrades and configuration installations for newly deployed network nodes.

Cisco NX-OS to Cisco Application Centric Infrastructure (ACI) power-on auto-provisioning (POAP) auto-conversion feature automates the process of upgrading software images and installing configuration files on nodes that are being deployed in the network for the first time. If a Cisco NX-OS node with the POAP auto-conversion feature boots without a startup configuration, the node enters the POAP mode and starts DHCP discovery on all ports. The node locates a DHCP server and bootstraps itself with its interface IP address, gateway, and DNS server IP addresses. The device also obtains the IP address of a TFTP server and downloads a configuration script that enables the node to download and install the appropriate software image and configuration file. This process converts the Cisco NX-OS node from standalone mode to Cisco ACI-mode.

To auto-convert a Cisco NX-OS node to a Cisco ACI node using POAP, you need to specify an interface on a Cisco ACI switch node that is connected to the Cisco NX-OS node that needs to be auto-converted. The interface specified on the Cisco ACI switch enables the handling of POAP and allows the Cisco NX-OS node to use the Cisco Application Policy Infrastructure Controller (APIC) as its DHCP server for auto-conversion. The Cisco ACI switch node must be already registered with the Cisco ACI fabric and be active. This means the node is reachable from the Cisco APIC cluster. This auto-conversion can be used when adding a new switch to the fabric or when replacing an existing Cisco ACI switch.

Guidelines and limitations for Cisco NX-OS to Cisco ACI POAP auto-conversion

Supported hardware for Cisco NX-OS to Cisco ACI POAP auto-conversion

Cisco NX-OS to Cisco ACI POAP auto-conversion supports these switches:

  • Switches with -EX, -FX, -GX, or newer PIDs

  • Cisco N9K-C9364C and N9K-C9332C switches

Guidelines for Cisco NX-OS to Cisco ACI POAP auto-conversion

These guidelines apply when using Cisco NX-OS to Cisco Application Centric Infrastructure (ACI) power-on auto-provisioning (POAP) auto-conversion:

  • Because a Cisco NX-OS node that is being converted starts to send discover packets on all interfaces including management, any external DHCP server (apart from the Cisco Application Policy Infrastructure Controller's (APIC's) server) should be removed, as they may intercept POAP discover packets and disrupt the conversion.

  • After you auto-convert a spine or leaf node, the show system reset-reason CLI command does not display any information regarding conversion. The output only states this:

    reset-requested-by-cli-command-reload

Limitations for Cisco NX-OS to Cisco ACI POAP auto-conversion

These limitations apply when using Cisco NX-OS to ACI POAP auto-conversion:

  • Cisco NX-OS to Cisco ACI POAP auto-conversion is supported only when the NX-OS device to be converted is connected to an existing Cisco ACI switch node that has reachability to the Cisco APIC cluster. Due to this reason, these scenarios are not supported:

    • When discovering the first Cisco ACI switch from APIC 1.

    • When replacing a Cisco ACI leaf node when a Cisco APIC is single-homed to the leaf node.

    • When adding or replacing a Cisco ACI switch that reaches to the Cisco APIC cluster only through an IPN device. That is, when adding a Cisco NX-OS node as a new remote leaf node, adding a Cisco NX-OS node as a first spine node in a new pod, replacing a remote leaf node, or replacing a spine node in a Cisco ACI Multi-Pod setup with only one spine node in the pod. This scenario is supported beginning with the Cisco APIC 5.2(4) release with the required configurations on the IPN device.

  • Modular spine node supervisor replacement is not supported.

  • You must use optical cables between Cisco ACI switches and Cisco NX-OS switches. You cannot use copper cables in this case.

  • The Cisco ACI switch image that needs to be used for auto-conversion must be present on the Cisco APIC cluster's firmware repository. You can use the GUI to check that the image is present by going to Admin > Firmware > Images.

  • Cisco NX-OS to Cisco ACI auto-conversion using POAP is not supported when the target switch release is 16.0(3) or later while the current release running on the switch is Cisco NX-OS 9.3(12) or earlier. If you attempt to use the Cisco NX-OS to ACI auto-conversion by using POAP under this condition, the switch may get stuck indefinitely. To convert Cisco NX-OS to Cisco ACI under these conditions, you must perform the upgrade manually.

Convert a Cisco NX-OS node to Cisco ACI with POAP Auto-conversion using the GUI

Use this task when migrating a standalone Cisco NX-OS node to Cisco ACI mode without decommissioning the node.

Before you begin

Enable Auto Firmware Update on Switch Discovery with the target Cisco ACI firmware version. For more information, see the Cisco APIC Getting Started Guide.

Follow these steps to convert a Cisco NX-OS node to Cisco ACI with POAP Auto-conversion using the GUI.

Procedure

1.

On the menu bar, choose Fabric > Inventory.
2.

In the Navigation pane, choose Fabric Membership.
3.

In the Work pane, choose the Registered Nodes tab.
4.

(Optional) When replacing an existing Cisco ACI switch node with a new switch that may be running NX-OS, right-click the node to be replaced and choose Remove From Controller as you would do for a regular replacement scenario.
5.

In the action menu at the top right of the table, choose Add with NXOS to ACI Conversion.

In the replacement scenario, if the switch node to be replaced is decommissioned or inactive, you can alternatively right-click the node and choose Replace with NXOS to ACI Conversion. This will perform actions Remove From Controller from step 4 and Add with NXOS to ACI Conversion from step 5 at the same time.
6.

In the dialog, fill out the fields as follows:

  • Node ID: Choose the ID of a node that is connected to the node that you want to convert. You can click the trash can to delete a node or + to add another node. Specify at least one node. You can click Hide Interfaces to hide the interface information if you need more space in the GUI when configuring additional nodes.

  • Interface ID: Choose the ID of one of the node's interfaces that is connected to the node that you want to convert. You can click the trash can to delete an interface or + to add another interface. Configure only one interface in each node to handle POAP for POAP auto-conversion.
7.

Click Submit.
8.

Choose the Nodes Pending Registration tab.

After the node appears in this tab, the node registration procedure is the same as for regular Cisco ACI switches.
9.

(Optional) After the switch is registered and has joined the fabric with the Active status, you may delete the POAP auto-conversion setting on the interface that you configured in step 6. After the conversion completes, delete the POAP settings from the connected node:

  1. Choose the Registered Nodes tab.

  2. Double-click the row of the node from which you want to delete the POAP settings.

  3. In the dialog, choose the NXOS Conversion Policy tab.

  4. Select the pathname that you want to delete, then click the delete icon (the trashcan).

The Cisco NX-OS node is converted to Cisco ACI mode and registered in the fabric. You can now remove POAP auto-conversion settings from associated interfaces.

What to do next

  • Verify the node’s operational status in the fabric.

  • Reconfigure any necessary POAP settings on remaining interfaces.