Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > NCM config comparison between two configs never finishes for large config files

NCM config comparison between two configs never finishes for large config files

Updated: July 26, 2016

Overview

When you do a comparison between two configuration files (running vs startup) that are very large (about 16.000 lines), NPM sometimes does not finish the comparison.  

The first config you chose is loaded nearly instantly but as soon as the comparison begins, it does not continue. However, the comparison of smaller config-files (1500-2000) works fine.

 

Environment

NCM, all supported versions

Cause 

This behavior is known in NCM with very large config files.

 

Resolution

Use the Config Change report Job when comparing large configs.  

 

 

Last modified

Tags

Classifications

Public