10-31-2013 09:28 PM
I have config the OMW - NNMi integration using northbound setting. The OMW can receive NNMi SNMP trap message.
But we found all the message only store in NNMi node. Which can't store in corresponding external node.
I have create the external node using IP matching pattern. <*>.<*>.<*>.<*>
But it still doesn't work.
The OA agent in NNMi is 11.12 version. OMW server are 9.0 version.
The policy we have setting use $21 for the node name in the rule.
We have check the message. Find the the varbind $21 which can include in SNMP trap message. But the policy seem can't place the value in the node name field.
Solved! Go to Solution.
11-01-2013 04:15 PM
There is a defect in the 11.12 version of the Operations Agent that leads to this issue: QCCR1A165270.
That's fixed in the 11.13 agent patch.
11-05-2013 11:32 AM
NAME DESCRIPTION VERSION TYPE OSTYPE
HPOvAgtLc HP Operations agent L10N Package 11.11.025 pkg Windows
HPOvBbc HP Software HTTP Communication 11.12.009 pkg Windows
HPOvConf HP Software Configuration 11.11.025 pkg Windows
HPOvCtrl HP Software Process Control 11.12.009 pkg Windows
HPOvDepl HP Software Deployment 11.12.009 pkg Windows
HPOvEaAgt HP Software E/A Agent 11.12.009 pkg Windows
HPOvPacc HP Software Performance Access 11.11.025 pkg Windows
HPOvPerfAgt HP Software Performance Agent 11.12.009 pkg Windows
HPOvPerfMI HP Software Measurement Interface 11.12.009 pkg Windows
HPOvPerlA HP Software Perl 05.08.096 pkg Windows
HPOvSecCC HP Software Certificate Management 11.12.009 pkg Windows
HPOvSecCo HP Software Security Core 11.12.009 pkg Windows
HPOvXpl HP Software Cross Platform Component 11.12.010 pkg Windows
Operations-agent HP Operations agent Product 11.12.009 bdl Windows
11-06-2013 10:10 AM
The issue is only present in Operations Agent 11.12. OA 11.11 and earlier versions do not have that problem.
Your ovdeploy -inv shows that you have OA 11.12.
OA 11.12 (and 11.13) are agent patches that are installed on top of the base version.
That means that not all packages and files are replaced (patches are selectively replacing parts).
And that's why some components and files still show 11.11 while others show 11.12.
Therefore you need to be careful using "ovc -version", as that only shows the version of the ovc binary.
The best way to determine agent version is using "ovdeploy -inv" like you did.