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

Products

• VMware

Issue/Introduction

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.



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

Environment

VMware Smart Assurance - NCM

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.

Resolution

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.

Additional Information

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


Impact/Risks:
This change would be applicable to all device classes in NCM.