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

VMware Smart Assurance NCM: Pull Interfaces via SNMP on any device shows Interface name and description same in NCM (71085)

Last Updated: 7/22/2019Categories: TroubleshootingTotal Views: 19222Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

Interface name and description are shown same on the device in NCM.

Purpose

To share a workaround by which NCM can pull OID .1.3.6.1.2.1.2.2.1.2 for Interface Name and OID .1.3.6.1.2.1.31.1.1.1.18 for Interface Description. With workaround details would look like below.

Cause

In NCM, by default SNMP is taken precedence for Pull Interfaces on a device.
For most of the device classes, NCM makes use of generic code from $VOYENCE_HOME/package/stdlib directory for Pull Interfaces, where by design it is designed to pull interface name from OID .1.3.6.1.2.1.2.2.1.2 and same is set as interface description.

Impact / Risks

This change would be applicable to all device classes in NCM.

Workaround

Follow the below steps on Device Server/Combination Server to implement the workaround.
1) Create the directory structure $VOYENCE_HOME/custompackage/stdlib if it doesn't exist already.
2) Place the attached stdmib.inc and stdcmdfuncs.inc files at $VOYENCE_HOME/custompackage/stdlib
3) Restart voyence service with command: service voyence restart
4) Execute Pull Interfaces on the device.

Related Information

Device should have Interface with description configured, otherwise the description field would be empty.
Example:

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

stdmib

stdcmdfuncs

Additional Resources

KB
•
Ubuntu 18.4、16.4、SLED12SP3、SLES12SP3、および SLED11SP4 でスマート カードの取り外し時に画面を自動的にロックする (71068)

KB
•
組み込みの Orchestrator ポート 8283 に CA 署名の SSL 証明書を適用する (71060)

KB
•
UAC が有効な Windows に vRealize Operations Manager 7.5 Telegraf エージェントをインストールできない (70780)

Results 1-3 of 3

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