Troubleshooting Cisco APIC-EM Multi-Host

Similar documents
Troubleshooting Cisco APIC-EM Single and Multi-Host

Configure the Cisco DNA Center Appliance

Configure the Cisco DNA Center Appliance

Configure the Cisco DNA Center Appliance

Upgrading the Cisco APIC-EM Deployment

Upgrading the Cisco APIC-EM Deployment

Managing the Cisco APIC-EM and Applications

Installing Cisco APIC-EM on a Virtual Machine

Cisco APIC-EM Components and Architecture, page 3. About the Cisco Application Policy Infrastructure Controller Enterprise Module (APIC-EM), page 1

Preparing Virtual Machines for Cisco APIC-EM

Preparing Virtual Machines for Cisco APIC-EM

Troubleshooting Commands

Back Up and Restore Cisco DNA Center

Read the following information carefully, before you begin an upgrade.

Parallels Virtuozzo Containers 4.6 for Windows

The Balabit s Privileged Session Management 5 F5 Azure Reference Guide

Migrate Data from Cisco Secure ACS to Cisco ISE

Installing or Upgrading ANM Virtual Appliance

Release Notes for Cisco Application Policy Infrastructure Controller Enterprise Module, Release x

VMware Horizon View Configuration Tool 2.0 QUICK START GUIDE

Install and Configure FindIT Network Manager and FindIT Network Probe on a VMware Virtual Machine

SUREedge MIGRATOR INSTALLATION GUIDE FOR VMWARE

Troubleshooting the Cisco APIC-EM

IBM Single Sign On for Bluemix Version December Identity Bridge Configuration topics

SQL Server AlwaysOn setup on ObserveIT environment

Installing the Cisco Virtual Network Management Center

Using the Cisco NCS Command-Line Interface

Installing Active Directory on a Windows 2008 Server

Table of Contents 1 V3 & V4 Appliance Quick Start V4 Appliance Reference...3

Quick Start Guide for Vmware. Version 2.5 Vmware vsphere Instance

How to Deploy vcenter on the HX Data Platform

Install and Configure FindIT Network Manager and FindIT Network Probe on Microsoft Hyper-V Manager

VMware Identity Manager Connector Installation and Configuration (Legacy Mode)

Smart Call Home Deploying thetransport Gateway on Cisco Unified Computing System and Red Hat Linux

Parallels Containers for Windows 6.0

Configuring Cisco Mobility Express controller

CounterACT 7.0 Single CounterACT Appliance

Installation. Power on and initial setup. Before You Begin. Procedure

Getting Started with ESX Server 3i Installable Update 2 and later for ESX Server 3i version 3.5 Installable and VirtualCenter 2.5

System Requirements. System Requirements for Cisco DCNM, Release 10, page 1 Deployment Best Practices for Cisco DCNM, Release 10.

SUSE Cloud Admin Appliance Walk Through. You may download the SUSE Cloud Admin Appliance the following ways.

Getting Started with ESX Server 3i Embedded ESX Server 3i version 3.5 Embedded and VirtualCenter 2.5

Overview of the Cisco NCS Command-Line Interface

Cisco Application Policy Infrastructure Controller Enterprise Module Hardware Installation Guide

Cisco Emergency Responder Installation

Installation of Cisco Business Edition 6000H/M

Deploying VMware Identity Manager in the DMZ. JULY 2018 VMware Identity Manager 3.2

UDP Director Virtual Edition Installation and Configuration Guide (for Stealthwatch System v6.9.0)

ForeScout Extended Module for IBM BigFix

Installing Active Directory on a Windows 2012 Server

Cisco Stealthwatch. Update Guide 7.0

AutomaTech Application Note July 2015

Installing Cisco Virtual Switch Update Manager

Configuring High Availability for VMware vcenter in RMS All-In-One Setup

Azure Marketplace Getting Started Tutorial. Community Edition

ACE Live on RSP: Installation Instructions

Installing and Configuring VMware Identity Manager Connector (Windows) OCT 2018 VMware Identity Manager VMware Identity Manager 3.

Installing VMware vsphere 5.1 Components

Deploying VMware Identity Manager in the DMZ. SEPT 2018 VMware Identity Manager 3.3

Connect using Putty to a Linux Server

Connectra Virtual Appliance Evaluation Guide

Bitnami Apache Solr for Huawei Enterprise Cloud

Important notice regarding accounts used for installation and configuration

Forescout. eyeextend for IBM BigFix. Configuration Guide. Version 1.2

SUREedge MIGRATOR INSTALLATION GUIDE FOR HYPERV

Migrating vrealize Automation 6.2 to 7.2

SUREedge MIGRATOR INSTALLATION GUIDE FOR NUTANIX ACROPOLIS

Configuring the Management Access List

Threat Response Auto Pull (TRAP) - Installation Guide

dctrack Quick Setup Guide Virtual Machine Requirements Requirements Requirements Preparing to Install dctrack

UDP Director Virtual Edition

Proofpoint Threat Response

Migrating vrealize Automation 6.2 to 7.1

MediaSense Installation

Creating Application Containers

Vidyo Server for WebRTC. Administrator Guide

Configuring the JUNOS Software the First Time on a Router with a Single Routing Engine

Cisco ACI Simulator VM Installation Guide

SUREedge DR Installation Guide for Windows Hyper-V

CounterACT 7.0. Quick Installation Guide for a Single Virtual CounterACT Appliance

Cisco Expressway Cluster Creation and Maintenance

ForeScout CounterACT. Cisco PIX/ASA Firewall Integration Module. Configuration Guide. Version 2.1

Office and Express Print Release High Availability Setup Guide

ForeScout Extended Module for IBM BigFix

Creating Application Containers

Figure 5-25: Setup Wizard s Safe Surfing Screen

Installation of Cisco HCM-F

TANDBERG Management Suite - Redundancy Configuration and Overview

Installing and Configuring vcloud Connector

Implementing Infoblox Data Connector 2.0

Using SSL to Secure Client/Server Connections

SAML-Based SSO Configuration

Configuring the Cisco APIC-EM Settings

Deploying Cisco UCS Central

VMware vrealize Log Insight Getting Started Guide

on VMware Deployment Guide November 2018 Deployment Guide for Unitrends Free on VMware Release 10.3 Version Provide feedback

Deployment of FireSIGHT Management Center on VMware ESXi

Infoblox Trinzic V-x25 Series Appliances for AWS

Deploy Oracle Spatial and Graph Map Visualization Component to Oracle Cloud

How to Deploy an AMI Test Agent in Amazon Web Services

Transcription:

The following procedures may be used to troubleshoot a Cisco APIC-EM multi-host configuration: Changing the Settings in a Multi-Host Cluster, page 1 Removing a Single Host from a Multi-Host Cluster, page 3 Removing a Faulted Host from a Multi-Host Cluster, page 4 Changing the Settings in a Multi-Host Cluster To troubleshoot an issue with a multi-host cluster, you may need to change its configuration settings. This procedure describes how to change the Cisco APIC-EM external network settings, NTP server address, and/or password for the Linux grapevine user in a multi-host cluster. The external network settings that can be changed include: Host IP address Virtual IP address DNS server Default gateway Static routes In order to change the external network settings, NTP server address, and/or the Linux grapevine user password in a multi-host deployment, you need to first break up the multi-host cluster. As a result, controller downtime occurs. For this reason, we recommend that you perform this procedure during a maintenance time period. For information about changing settings for a single host configuration, see Updating the Configuration Using the Wizard 1

Changing the Settings in a Multi-Host Cluster Before You Begin You must have successfully configured the Cisco APIC-EM as a multi-host cluster using the configuration wizard, as described in the Cisco APIC-EM deployment guide. Step 1 Step 2 Step 3 Using a Secure Shell (SSH) client, log into one of the hosts in your cluster. Log in using the IP address that you specified using the configuration wizard. The IP address to enter for the SSH client is the IP address that you configured for the network adapter. This IP address connects the appliance to the external network. When prompted, enter your Linux username ('grapevine') and password for SSH access. Enter the following command to access the configuration wizard. Step 4 Step 5 The config_wizard command is in the PATH of the 'grapevine' user, and not the "root" user. Either run the command as the "grapevine" user, or fully qualify the command as the "root" user. For example: /home/grapevine/bin/config_wizard Review the Welcome to the APIC-EM Configuration Wizard! screen and choose the option to remove the host from the cluster: Remove this host from its APIC-EM cluster A message appears with the following options: [cancel] Exit the configuration wizard. [proceed] Begin the process to remove this host from its cluster. Choose proceed>> to begin. After choosing proceed>>, the configuration wizard begins to remove this host from its cluster. At the end of this process, this host is removed from the cluster. Step 6 Step 7 Repeat the above steps (steps 1-5) on a second host in the cluster. You must repeat the above steps on each host in your cluster, until you only have a single host remaining. You must make your configuration changes on this final remaining host. Using a Secure Shell (SSH) client, log into that final host in your cluster and run the configuration wizard. After logging into the host, begin the configuration process. Step 8 Step 9 Make any necessary changes to the configuration values for the external network settings, NTP server address, and/or password for the Linux grapevine user using the wizard. After making your configuration change(s), continue through the configuration process to the final message. At the end of the configuration process, a final message appears stating that the wizard is now ready to proceed with applying the configuration. The following options are available: [back] Review and verify your configuration settings. 2

Removing a Single Host from a Multi-Host Cluster [cancel] Discard your configuration settings and exit the configuration wizard. [save & exit] Save your configuration settings and exit the configuration wizard. [proceed] Save your configuration settings and begin applying them. Enter proceed>> to complete the installation. After entering proceed>>, the configuration wizard applies the configuration values that you entered above. At the end of the configuration process, a CONFIGURATION SUCCEEDED! message appears. Step 10 Log into the other hosts in your multi-host cluster and use the configuration wizard to recreate the cluster. Refer to Cisco Application Policy Infrastructure Controller Enterprise Module Deployment Guide for information about this specific procedure. Removing a Single Host from a Multi-Host Cluster To troubleshoot an issue with a multi-host cluster, you may need to remove a single host from a multi-host cluster. This procedure describes how to remove one of the hosts running Cisco APIC-EM from a multi-host cluster. You use the Cisco APIC-EM configuration wizard to perform this procedure. The configuration wizard option to remove a host only appears if the host on which you are running the configuration wizard is part of a multi-host cluster. If the host is not part of a multi-host cluster, then the option to remove a host does not display. When performing this procedure, controller downtime occurs. For this reason, we recommend that you perform this procedure during a maintenance time period. Before You Begin You should have deployed Cisco APIC-EM on a multi-host cluster as described in the Cisco APIC-EM deployment guide. You must perform this procedure on the single host that is to be removed from the multi-host cluster. Step 1 Step 2 Step 3 Using a Secure Shell (SSH) client, log into the host (appliance, server, or virtual machine) with the IP address that you specified using the configuration wizard. The IP address to enter for the SSH client is the IP address that you configured for the network adapter. This IP address connects the appliance to the external network. When prompted, enter your Linux username ('grapevine') and password for SSH access. Enter the following command to access the configuration wizard. 3

Removing a Faulted Host from a Multi-Host Cluster Step 4 The config_wizard command is in the PATH of the 'grapevine' user, and not the "root" user. Either run the command as the "grapevine" user, or fully qualify the command as the "root" user. For example: /home/grapevine/bin/config_wizard Review the Welcome to the APIC-EM Configuration Wizard! screen and choose the option to remove the host from the cluster: Remove this host from its APIC-EM cluster Step 5 A message appears with the following options: [cancel] Exit the configuration wizard. [proceed] Begin the process to remove this host from its cluster. Choose proceed>> to begin. After choosing proceed>>, the configuration wizard begins to remove this host from its cluster. At the end of this process, you must then either run the configuration wizard again to configure the host as a new Cisco APIC-EM or join the Cisco APIC-EM to a cluster. What to Do Next If you wish to use this host again as either a stand-alone controller or operating within a cluster, then you must run the configuration wizard again and re-install the Cisco APIC-EM. Do not attempt to use this host again as either a standalone host or within a cluster without re-installing the Cisco APIC-EM. Removing a Faulted Host from a Multi-Host Cluster Perform the steps in the following procedure to remove a faulted or inoperative host (running Cisco APIC-EM) from a multi-host cluster. You use the Cisco APIC-EM configuration wizard to perform this procedure. A host becomes faulted when it can no longer participate in the cluster due to hardware or software issues. After following this procedure on a three host cluster (moving from three hosts to two hosts), you will lose high-availability protection against loss of a host. After following this procedure for a two host cluster, then the cluster will become inoperable until that second host is brought back up and added to the cluster. The fact that the host becomes "faulted" results in replacement instances of the services on the faulted host being grown on the remaining hosts in the cluster. During the time period when the replacement instances are being grown and depending on the types of services being grown, certain Cisco APIC-EM functionality may not be available. Before You Begin You have deployed Cisco APIC-EM on a multi-host cluster following the procedure described in the Cisco APIC-EM deployment guide. You must perform this procedure on an active host in the multi-host cluster. You cannot perform this procedure on the faulted host that is to be removed from the multi-host cluster. A faulted host is displayed as red in the Hosts view in the Grapevine developer console. 4

Removing a Faulted Host from a Multi-Host Cluster You should always first attempt to bring the faulted host back online. After determining that the faulted host can no longer participate in the cluster, then try to remove the faulted host using the Remove this host from its APIC-EM cluster configuration wizard option. You should only follow this procedure and the Remove a faulted host from this APIC-EM cluster configuration wizard option, if that other option is tried first and is unsuccessful in removing the host. Step 1 Step 2 Step 3 Using a Secure Shell (SSH) client, log into the host (appliance, server, or virtual machine) with the IP address that you specified using the configuration wizard. The IP address to enter for the SSH client is the IP address that you configured for the network adapter. This IP address connects the appliance to the external network. When prompted, enter your Linux username ('grapevine') and password for SSH access. Enter the following command to access the configuration wizard. Step 4 Step 5 The config_wizard command is in the PATH of the 'grapevine' user, and not the "root" user. Either run the command as the "grapevine" user, or fully qualify the command as the "root" user. For example: /home/grapevine/bin/config_wizard Review the Welcome to the APIC-EM Configuration Wizard! screen and choose the option to forcibly remove the faulted host from the cluster: Remove a faulted host from this APIC-EM cluster A message appears with the following options: <Remove IP Address from cluster> Forcibly removes the faulted host (identified by its IP address) from the multi-host cluster. <exit> Exit the configuration wizard without removing the faulted host. Choose <Remove IP Address from cluster> to begin. After choosing <Remove IP Address from cluster>, the configuration wizard begins to remove this faulted host from its cluster. At the end of this process, you must then either run the configuration wizard again to configure the host as a new Cisco APIC-EM or join the Cisco APIC-EM to a cluster. What to Do Next If you wish to use this host again as either a stand-alone controller or operating within a cluster, then you must run the configuration wizard again and re-install the Cisco APIC-EM. Do not attempt to use this host again as either a standalone host or within a cluster without re-installing the Cisco APIC-EM. 5

Removing a Faulted Host from a Multi-Host Cluster 6