Alerts are not being sent to HP Openview when there are spaces in the rule name. The second string in the rule name is reported in an opcmsg error message in the Management Server log. Following are example errors received:
When the alarm for the "Foglight Memory Usage Check" rule is triggered the following error message is reported in the Management server log:
Option Memory is not valid for this command. (OpC30-902)
When the alarm for the "Remote Agent Managers State per Host" rule is triggered the following error message is reported in the Management server log:
Option Agent is not valid for this command. (OpC30-902)
When the alarm for the "ServiceLevelEvaluation - FMSServiceSLP" rule is triggered the following error message is reported in the Management server log:
Option - is not valid for this command. (OpC30-902)
The spaces in the rule name are causing a problem when the opcmsg.exe call is made.
RESOLUTION:
Add quotes around the ruleName parameter used in the call to the opcmsg.exe command, as follows:
system("\"C:\\path_to_opcmsg\\opcmsg.exe\" appl=$ci_agent msg_grp=group_string sev=$severity_enum node=$ci_hostname obj=\"$ruleName\" msg_text=\"$message\" -option GUID=$ci_unique");
The example forward-alerts-to-ovo-win.pl script that comes with the V5.5 Integration cartridge contains quotes around the ruleName parameter.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy