Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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: How to set up a device diagnostic (503480)

Last Updated: 5/29/2020Categories: How toTotal Views: 3209Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

In many cases, it may be desirable to obtain additional information from devices that can be useful to end users of NCM in administering devices under NCM management, but that do not qualify as formal configuration files that could be pushed back to a device. For example, it may be beneficial to know the amount of free memory available on a device before attempting to push a new device Operating System (OS) out to a device, especially if significant storage or memory on the device is being consumed by copies of older versions of the OS that were kept as a rollback option from the last time the OS on the device was updated. You may even want to see a quick list of all the device OS images currently present on the device so you know which ones need to be deleted to free up storage space on the device. In these cases, a compliance pass based on testing the available free storage on the device to find out which devices could support an OS image push could possibly yield a report or NCM Client UI flag for devices under management that need attention prior to any NCM OS image push.

There are many other examples of situations where additional information about a device may prove useful, even though it is not part of a configuration file normally stored in the NCM PostgreSQL Control Database (controldb). Many of these needs can be met by collecting the output of arbitrary commands you wish to run in a Command Line Interface (CLI) session with the device every time a configuration change (new revision) is detected on the device. The mechanism that NCM offers to accomplish this is the device diagnostic. The output of any diagnostic commands you set up for a specific device, or an entire device class, are stored in a read-only file called the 'Diagnostic Result', and are visible in similar fashion to more interactive configuration files under any given revision.

To set up a diagnostic on any single device in NCM, you can use the following selection sequence:

Networks Navigation pane >> Right-click on target device >> Quick Commands >> Setup Diagnostic

To set up a diagnostic on an entire device class globally across the entire application, you can use the following selection sequence:

Tools >> System Administration >>

Global >> Device Classes >> Select a device class name >> Diagnostic Button

This will cause the Device Diagnostic window to appear for the selected device class. Commands can now be entered into this window that will be executed any time a new revision is generated for a target device that is created due to NCM becoming aware that the device configuration has changed. To apply the changes, click the Apply button at the bottom of the Device Diagnostic Window.

Related Information

Because of the arbitrary nature of commands that can be run in device diagnostic setups, Dell EMC cannot warrant the effect of any commands you intend to run in this way. The capability is offered as a convenience only, and Dell EMC does not warrant the effect of any commands you choose to enter into the diagnostic setup window.

If a specific privilege mode on the device is required to run a user supplied diagnostic command, the session must achieve that privilege level on initial login. NCM does not currently provide a means of navigating to a desired privilege mode prior to running a diagnostic command. Typically, this can be achieved by supplying the correct password for the desired privilege mode as the account password for the credential associated with the device in NCM, but this is dependent on the capabilities of the device in question and cannot be guaranteed by Dell EMC.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

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