VMware Smart Assurance NCM: Model name and OS version not shown for Teldat devices post Autodiscovery/Pull All in DSR 28 HF2

Products

• VMware

Issue/Introduction

Symptoms:
Model name and OS version is not being not shown for Teldat devices in DSR 28 HF2 installation post autodiscovery or pull all operation.

Environment

VMware Smart Assurance - NCM

Cause

After pull running config, to pull system properties, NCM is trying to enter "p 3" from "p 4" mode; this process is failing. Currently, there's no "exit" accommodated in the NCM code to come out of "p 4" mode from device after pull running config capture, so that device can enter "p 3" mode next when NCM pulls system properties.

Resolution

This issue has been identified as a bug and is resolved in DSR 29 HF1. Upgrade to DSR 29 HF1 or higher for the issue fix.
https://docs.vmware.com/en/VMware-Smart-Assurance/10.1.3/rn/Network-Configuration-Manager-Device-Services-Support--DSr--Release-Notes-290-Hotfix-1.html

Workaround:
Below workaround can be implemented on Device Server/Combination Server in DSR 28 HF2 until DSR upgrade.

1. Create directory structure $VOYENCE_HOME/custompackage/teldat/router if it doesn't exist already and copy pull.inc file from $VOYENCE_HOME/package/teldat/router to $VOYENCE_HOME/custompackage/teldat/router.

2. Add code "send(session, "end"+stdEOL);" after 41st line in $VOYENCE_HOME/custompackage/teldat/router/pull.inc file. 

3. Save and close the file. Restart voyence service with command "service voyence restart". 

4. Schedule 'Autodiscovery with Pull All' or 'Pull All' on affected Teldat devices. Model name and OS version should be shown successfully now. 

Note: Modified pull.inc is attached to the KB article along with a screenshot of the suggested code change.