Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > WARNING: Config change detected, aborting

WARNING: Config change detected, aborting

Table of contents
Created by Bill Corgey, last modified by Rodim Suarez_ret on Jun 29, 2016

Views: 1,211 Votes: 0 Revisions: 5

Updated

Overview

The emails for Real Time Change Detection shows the following message as part of the configuration:

WARNING: Config change detected, aborting

This may be a rare case scenario.

Envionment

  • NCM 7.5

Detail

This anomaly is due to a runaway RTN event generally caused by a loop where the trigger action spawns a config download of the config, and the the command to download a config, spawns a Real Time Change detection and thus creating a loop and eventually the Cache is overwhelmed.

The message being displayed in the config is not in any NCM coding and could not come from the NCM application.

It is assumed that the message is being sent from the device, but no confirmation has been established on that side.

As for now, you need to make sure that the Real Time Change Detection trigger is based on the Syslog message: *end configuration: OK*

This message is only sent upon one exiting config mode.

 

 

Last modified

Tags

Classifications

Public