Smarts NCM: Nokia (ALU) CSRs devices pulling config on every Syslog event type, causing application slowness
Article ID: 330883
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
Symptoms:
When syslog is enabled for Nokia ALU CSR devices, configuration pull jobs are scheduled on all event types causing application slowness due to the number of pulls triggered.
When syslog is enabled for Nokia ALU CSR devices, configuration pull jobs are scheduled on all event types causing application slowness due to the number of pulls triggered.
Environment
VMware Smart Assurance - NCM
Cause
$VOYENCE_HOME/package/pkgxml/AlcatelSR/AlcatelSRSysLog.xml match string is too broad and triggers pulls on every event.
Resolution
Copy the file AlcatelSRSysLog.xml from $VOYENCE_HOME/package/pkgxml/AlcatelSR/ to $VOYENCE_HOME/custompackage/pkgxml/AlcatelSR/
Note: $VOYENCE_HOME is equal to /opt/smarts-ncm in a standard install. Your voyence home location may be different. You can check /etc/voyence.conf for the $VOYENCE_HOME variable setting.
Modify the entries in $VOYENCE_HOME/custompackage/pkgxml/AlcatelSR/AlcatelSRSysLog.xml match string to the desired string. In this case, pulls will only be scheduled when the string 'Configuration file saved to' is matched in Syslog for this device type (1302).
Be sure 'IsActive' is set to 'true' so NCM will perform the match test.
Be sure 'PullConfig' is set to '1' to schedule the pull operation upon successful match.
Ex: Content of AlcatelSRSysLog.xml file -
<!--
__COPYRIGHT__, All Rights Reserved
Version ==version==.==build==
$Date: 2009-11-04 16:36:00 $
$RCSfile: AlcatelSRSysLog.xml,v $
$Revision: 1.1.2.1 $
Do not change any information in this file. All scripts in this file
will be overwritten during the update process.
-->
<SysConfig>
<Package>
<IsActive>true</IsActive>
<PackageID>1302</PackageID>
<Event>
<MatchString>Configuration file saved to</MatchString>
<!-- <ChangedBy></ChangedBy> -->
<PullConfig>1</PullConfig>
</Event>
</Package>
</SysConfig>
Note: $VOYENCE_HOME is equal to /opt/smarts-ncm in a standard install. Your voyence home location may be different. You can check /etc/voyence.conf for the $VOYENCE_HOME variable setting.
Modify the entries in $VOYENCE_HOME/custompackage/pkgxml/AlcatelSR/AlcatelSRSysLog.xml match string to the desired string. In this case, pulls will only be scheduled when the string 'Configuration file saved to' is matched in Syslog for this device type (1302).
Be sure 'IsActive' is set to 'true' so NCM will perform the match test.
Be sure 'PullConfig' is set to '1' to schedule the pull operation upon successful match.
Ex: Content of AlcatelSRSysLog.xml file -
<!--
__COPYRIGHT__, All Rights Reserved
Version ==version==.==build==
$Date: 2009-11-04 16:36:00 $
$RCSfile: AlcatelSRSysLog.xml,v $
$Revision: 1.1.2.1 $
Do not change any information in this file. All scripts in this file
will be overwritten during the update process.
-->
<SysConfig>
<Package>
<IsActive>true</IsActive>
<PackageID>1302</PackageID>
<Event>
<MatchString>Configuration file saved to</MatchString>
<!-- <ChangedBy></ChangedBy> -->
<PullConfig>1</PullConfig>
</Event>
</Package>
</SysConfig>
Feedback
Yes
No
Powered by
