Smarts NCM: pull config failing, errors seen "Compiler::expectError: Invalid value [convertHexToDot] specified", "DIALOG /apps/smarts-ncm/package/cisco/wlc/getStaticRoutes.dlg FAILED TO COMPILE!"

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:



When running a pull config on some cisco devices, the following errors were seen in the autodisc and commmgr logs on the DS:

Jun 01 07:56:45 -1379461152#3:                         ^
Jun 01 07:56:45 -1379461152#3: Compiler::expectError: Invalid value [convertHexToDot] specified, unknown function or variable identifier (ExpressionCompiler.cpp#278) Jun 01 07:56:45 -1379461152#1: DIALOG /apps/smarts-ncm/package/cisco/wlc/getStaticRoutes.dlg FAILED TO COMPILE!
Jun 01 07:56:45 -1379461152#1: !> Error processing dialog:
Jun 01 07:56:45 -1379461152#1: !> Compiler::expectError: Invalid value [convertHexToDot] specified, unknown function or variable identifier (ExpressionCompiler.cpp#278)
Jun 01 07:56:45 -1379461152#1: !> Error In   :
Jun 01 07:56:45 -1379461152#1: !> Dialog State: kernel_route Jun 01 07:56:45 -1379461152#1: !> Dialog Line #47 Jun 01 07:56

Environment

VMware Smart Assurance - NCM

Cause

The DSR was upgraded to DSR 21 and files in the new DSR version clash with some custom files of the customers. 

In this case it, these files were in the wlc folder:

/apps/smarts-ncm/package/cisco/wlc/ 

Resolution

To resolve,

1. backup the folder in question from the custompackage directory. For example in this case, the folder is 

/apps/smarts-ncm/custompackage/cisco/wlc/

Use tar cvf or gunzip to compress the wlc folder and save the compressed folder to a safe place
 2. Remove the custom folder contents 

rm -rf *.* /apps/smarts-ncm/custompackage/cisco/wlc/ 

3. Remove the dir : 

rmdir  /apps/smarts-ncm/custompackage/cisco/wlc/ 

4. Rerun the pull config and you should see the DSR compiling fine in the logs and pull config complete 

5. Check the custom files to see if customisations are required for these devices and update the custompackage folder if necessary. If there are further problems with this please raise an SR and contact Customer Support, referencing this KB.