Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts NCM: Pull running configuration job on Cisco WLC device shows successful, but on GUI junk data is shown (516209)

Last Updated: 5/29/2020Categories: TroubleshootingTotal Views: 7050Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

WLC device is showing some junk data in NCM GUI for running config rather than the original configuration. Other configurations available on device - readable_run-config and readable_running-config are shown correctly.

Cause

In NCM, pull config on Cisco WLC devices for readable_run-config and readable_running-config is via Terminal and running config is via Term/TFTP.

Enable debug and session logging on DS as per steps in KB article: https://support.emc.com/kb/323701

Execute the pull running configuration job operation on the device. In the $VOYENCE_HOME/logs/session.log, below entries are found:

Dec 28 06:48:49 666887936/ssh#1: RCV-1001>(ric100wc-01) >
Dec 28 06:48:49 666887936/ssh#1: SND>transfer upload start
Dec 28 06:48:50 666887936/ssh#1: RCV-9999>transfer upload start
Dec 28 06:48:50 666887936/ssh#1: RCV-9999>Mode............................................. TFTP
Dec 28 06:48:50 666887936/ssh#1: RCV-9999>TFTP Server IP................................... 146.xx.xx.xx
Dec 28 06:48:50 666887936/ssh#1: RCV-9999>TFTP Path........................................ /
Dec 28 06:48:50 666887936/ssh#1: RCV-9999>TFTP Filename.................................... 58120.pull
Dec 28 06:48:50 666887936/ssh#1: RCV-9999>Data Type........................................ Config File
Dec 28 06:48:50 666887936/ssh#1: RCV-9999>Encryption....................................... Enabled
Dec 28 06:48:50 666887936/ssh#1: RCV-9999>Are you sure you want to start? (y/N)
Dec 28 06:48:50 666887936/ssh#1: SND>y
Dec 28 06:49:20 666887936/ssh#1: RCV-1001> y
Dec 28 06:49:20 666887936/ssh#1: RCV-1001>TFTP Config transfer starting.
Dec 28 06:49:20 666887936/ssh#1: RCV-1001>File transfer operation completed successfully.
Dec 28 06:49:20 666887936/ssh#1: RCV-1001>(ric100wc-01) >

The highlighted section shows that TFTP encryption is enabled on the device. Hence, NCM will show encrypted data on GUI, rather than original configuration.

Resolution

TFTP encryption is device level setting/configuration, check with your device network admin to change this setting. It needs to be disabled on device.

Once the change is done & pull is executed on device, running configuration can be seen correctly on NCM.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant