Recover from a Single APIC Hardware Failure

Available Languages

Download Options

PDF (201.6 KB)
View with Adobe Reader on a variety of devices
ePub (258.1 KB)
View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle) (212.0 KB)
View on Kindle device or Kindle app on multiple devices

Updated:February 6, 2025

Document ID:118918

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

Problem

Solution

Introduction

This document describes the process that is used in order to replace a single APIC in a fabric cluster that fails due to a hardware issue.

Problem

There is an operable Application Centric Infrastructure (ACI) fabric that exists and an Application Policy Infrastructure Controller (APIC) that has failed. The failure is determined to be related to a hardware issue and the entire unit must be replaced.

Solution

Complete these steps in order to resolve this issue:

Identify the failed APIC and the current fabric settings:
1. From the web interface of an operational APIC, choose System > Controllers.
2. On the left-hand side of the screen, choose Controllers > (any APIC) > Cluster.
3. The failed APIC appears as Unavailable in the Operational State column. Take note of the Fabric Name, Target Size, and Node ID for the failed APIC, as well as the Tunnel End Point (TEP) address space:
Tip: You can also enter the acidiag avread command into the CLI of the APIC in order to obtain this information.
Decommission the failed APIC:
1. Highlight the failed APIC.
2. From the Actions drop-down list, choose Decommission. The APIC can now change to an Out of Service Admin state.
Remove the failed APIC from your rack and install the replacement. The new APIC can boot to the initial setup script.
Use the information that you gathered in Step 1 in order to match the values of the failed APIC and proceed through the setup script.

Note: Ensure that you use the same configuration settings that you noted from the old APIC (such as the Fabric Name, Controller ID, and TEP Address Pool). Failure to configure the APIC with the same settings can provoke the fabric to enter a partially diverged state. Additionally, the replacement APIC must run the same version of ACI software as the remaining two APICs in order to join the cluster.
Commission the new APIC:
1. Once the APIC has booted up, highlight the currently Out of Service APIC on the Cluster page.
2. From the Actions drop-down list, choose Commission.
  
  The APIC receives an IP address, which is reflected in the web interface of the APIC.
  
  Note: It can take up to ten minutes before this occurs. The new APIC can also cycle between the Available and Unavailable Operational States before its Health State appears as Fully Fit.
3. In order to verify that the new APIC has joined the fabric, use the CLI of the new APIC in order to log into the fabric. Use the credentials that are configured for the rest of the fabric when you log in.