Modifying "Statistics Configuration > Collection Interval" in a vManage Cluster

Available Languages

Download Options

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

Updated:October 31, 2023

Document ID:221148

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.

Background Information

Introduction

This document describes the process of modifying the Statistics Configuration > Collection Interval in a vManage cluster.

Prerequisites

Requirements

Cisco recommends that you have knowledge of vManage cluster 3 nodes in Active Data Center (DC) and 3 nodes in Disaster Recovery (DR) running 20.6.3 code 3 node vManage cluster.

Components Used

The information in this document is based on the 3-node vManage cluster on the 20.6.3 version.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.

Background Information

When Deep Packet Inspection (DPI) is enabled, you must set the Statistics Collection timer to 30 minutes or higher. In case, if user has less than 30 minutes configured, you need to configure 30 minutes or higher.

Configure

If you need to change the Database collection Statistics Configuration, it requires a reload of vManage. If it is a cluster of vManage, you need to follow these steps.

Ensure the status of the transport interface on DR vManage cluster nodes is Down.
From the Cisco vManage menu, navigate to Administration > Disaster Recovery page and pause the DR on Active cluster from any one of the vManage.
Change the Statistics collection interval to 30 minutes on Administration > Settings page on one vManage in an active cluster. It changes the timer on other vManages as well. Please validate the same before proceeding to the next step.
Reboot all three vManages in the active cluster to confirm the change. Login to all three vManages once they are up (approximately after 30 minutes) and validate that the change has been performed and cluster connectivity is restored.
Navigate to Administration > Disaster Recovery page and resume the DR back again.
Wait for the next Replication to occur as per the replication interval timer.
After replication, the same configuration is present in the DR cluster as well. Please validate the same before proceeding to the next step.
Now, you can either pause the DR again and reboot the backup cluster vManages or you can reboot them as it is. Just ensure it is not in the process of replication while the DR vManages is rebooted.