Smarts NPM: Remote Syslog Adapter does not start and run correctly; Errors logged related to 'TraceSyslog' of object 'MSI_AdapterManager::OSPF-Adapter-Manager'

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:




The following conditions, events or system behaviors may be observed with this issue:

• Smarts NPM Remote Syslog Adapter does not start properly.
• The following can be see in the logs:

[November 11, 2013 10:18:06 PM GMT +981ms] t@1381996288 main

ASL-W-ERROR_RULE_SOURCE-While executing rule set '/opt/InCharge9/NPM/smarts/rules/ospf/ospf-syslog.asl'

 ASL-ERROR_ACTION-While executing action at:

 ASL-CALL_STACK_RULE-   RuleName: __INIT__, Line: 46

 ASL-ERROR_INIT_ACTION-While executing initialization actions

 ASL-ERROR_GET-While attempting to get property 'TraceSyslog' of object 'MSI_AdapterManager::OSPF-Adapter-Manager'

 MR-CLASS_NOT_FOUND-Class of given name 'MSI_AdapterManager' not found; in file "/work/tancurrent/DMT-9.2.0.0/19/smarts/repos/mr/dyn_acc.c" at line 1636

 

[November 11, 2013 10:18:06 PM GMT +981ms] t@1381996288 main

ASL-W-ERROR_INIT_ACTION-While executing initialization actions

Environment

VMware Smart Assurance - SMARTS

Cause

Incorrect command syntax used to load the models. When Smarts NPM runs the sm_adapter, any models required must be loaded with the --model option.

Resolution

To address this issue, ensure that the --model=sm_msi option is included in the command syntax when starting your adapters as in the following

sm_adapter --name=SMARTS-NPM-BGP --server=localhost --model=sm_msi --output --daemon bgp/bgp-syslog.asl