Smarts NCM: The device driver for the DDT tool is not compiling and I cant create a custom driver

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


A customer is using the DDT toolkit to create a custom driver but it doesnt work and the autodisc.log file shows:


May 07 17:11:36 -1135228960#1: -----------------------------------------------
May 07 17:11:36 -1135228960#1: +++++++ /app/smarts-ncm/custompackage/metamako/testdriver_metamako/devMetamakoTestDriver_Metamako.dasl ++++++++
May 07 17:11:36 -1135228960#1: ===>Compiling additions to deviceDriver(30002,30001): Metamako TestDriver_Metamako
May 07 17:11:36 -1135228960#1: Called From:
May 07 17:11:36 -1135228960#1: /app/smarts-ncm/custompackage/metamako/testdriver_metamako/devMetamakoTestDriver_Metamako.dasl:18
May 07 17:11:36 -1135228960#1: DASLDriver::addObjVar: Duplicate Variable Name: modelsFile (DASLDriver.cpp#159)
May 07 17:11:36 -1135228960#1: PACKAGE /app/smarts-ncm/custompackage/metamako/testdriver_metamako/devMetamakoTestDriver_Metamako.dasl FAILED TO COMPILE!
May 07 17:11:36 -1135228960#1: !> Error In   : /app/smarts-ncm/custompackage/metamako/testdriver_metamako/devMetamakoTestDriver_Metamako.dasl#17:
May 07 17:11:36 -1135228960#1: !>         var modelsFile="MetamakoTestDriver_Metamako/MetamakoTestDriver_MetamakoModels.xml";  # relative to pkgxml dir
May 07 17:11:36 -1135228960#1: !>                                                                                           ^
May 07 17:11:36 -1135228960#1: !> DriverCompiler::bnfDeviceDriver: DASLDriver::addObjVar: Duplicate Variable Name: modelsFile (DASLDriver.cpp#159) (DriverCompiler.cpp#316)
May 07 17:11:36 -1135228960#1: Compilation failed to compile all drivers... To recompile again:
May 07 17:11:36 -1135228960#1: #1) Correct the error above
May 07 17:11:36 -1135228960#1: #2) Signal using "kill -HUP <pid>" of the 'autodisc' process.
May 07 17:11:36 -1135228960#2: DASL::Compile: Completed with Errors
May 07 17:11:36 -1135228960#1: DASL Version 21.0.0.0 Release 75, Build 75; VC Version 9.4.1.0 Initialized
May 07 17:11:36 -1135228960#2: Loading changed config...
May 07 17:11:36 -1135228960#2: Loading changed config...done

Environment

VMware Smart Assurance - NCM

Cause

Non unique device driver ID - every device driver needs a unique ID

Resolution

Using Metamako as an example device driver:

The device driver id 30004 of this driver was already in use and was not unique

To find if an ID is already in use:
cd $VOYENCE_HOME/package
(let's take for example 30008 as device driver id )
find . -name "*.dasl" | xargs grep 30008

The output of the find command should be empty, it should not display any files.That id can then be used for creating a new device driver

If it is unique, then you can change the device driver id in the following files (or else just start again using the unique ID):
MetamakoTestDriver_MetamakoTrap.xml, MetamakoTestDriver_Metamako.pkg, MetamakoTestDriver_MetamakoSyslog.xml, devMetamakoTestDriver_Metamako.dasl