Highlighted
Honored Contributor.
Honored Contributor.
446 views

config specify NNM node devices in OMW policy.

Jump to solution
Hi,

I have create one genaral policy SNMP Interceptor for all devices (External node), It can received event from NNM.

But when I config specify node in OMW policy, can not received any event from NNM. I have try to use both ip and host name. It's make any differance.

Thank you,
Pinion,
-/\-
0 Likes
1 Solution

Accepted Solutions
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
hi,


as Martin said, you need to verify the above steps and from your reply i couldn't see SNMP interceptor policies

you need to deploy SNMP interceptor policy on the NNM ( which generated when you run the NNM adapter)


by the way there are a latest patch for the OMW #58 , download and install it on the OMW as it will solve a lot of problems.

thanks
Mohamed

View solution in original post

8 Replies
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
hi,

could you please specify the following:
1- OMW version and the latest patch.
2- nnm version.
3- the agent version installed on the nnm
4- did you deployed the nnm forwarding policy on the NNM.
5- if you didn't install the agent on the NNM, did you allow forwarding traps to the OMW.

Abdou
0 Likes
Highlighted
Honored Contributor.
Honored Contributor.
Hi Abdou,

1- OMW 8.1
2- nnm 7.5
3- the agent version installed on the nnm
4- deployed the nnm forwarding policy on the NNM.

Thank you,
-/\-
0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
could you please run the following and send to me the output:

1- on the nnm >>> opcagt -version
2- on the nnm >>> ovc
3- on the nnm >>> opctemplate
4- on the OMW >>>> opctemplate


thanks
Abdou
0 Likes
Highlighted
Absent Member.
Absent Member.
Hello Pinion

The normal procedure to handle this is as follows:

- First make sure the OMW server, and all the desired managed nodes are correctly configured in your DNS (Forward and reverse lookups must go 100% ok).
- HP software relies big time on DNS lookups.

- Create "SNMP" nodes within OMW. Set the node specifics to "Other - SNMP -V1"

- Make sure the name of the SNMP is exactly the same as the name of the node within NNM.

- Make NNM a managed node within OMW (you probable had this one covered already, but I wanted to put it here)
- The communication between NNM and OMW must go ok, so check this with a simple "opcmsg" test message.

- After this deploy the SNMP interceptor policy to the NNM node.

Please verify all this and let me know 🙂


(if you like our ideas, please assign points)
Highlighted
Honored Contributor.
Honored Contributor.
Hi Abdou,

1- on the nnm >>> opcagt -version 8.60.6

2- on the nnm >>> ovc

ovcd OV Control CORE (2848) Running

coda OV Performance Core COREXT (2312) Running

opcacta OVO Action Agent AGENT,EA (2964) Running

opcmsga OVO Message Agent AGENT,EA (2180) Running

opcmona OVO Monitor Agent AGENT,EA (3044) Running

opcmsgi OVO Message Interceptor AGENT,EA (4104) Running

opctrapi OVO SNMP Trap Interceptor AGENT,EA (4376) Running

ovbbccb OV Communication Broker CORE (4608) Running

ovconfd OV Config and Deploy COREXT (5248) Running


3- on the nnm >>> opctemplate

Type Name Status Version
--------------------------------------------------------------------
monitor "CPU-WINDOWS-MONITORING" enabled 0001.0008
monitor "MEMORY-WINDOWS-MONITORING" enabled 0001.0001
monitor "DISK-WINDOWS-MONITORING" enabled 0001.0001
msgi "opcmsg" enabled 0008.0000
trapi "NNM" enabled 0001.0026


4- on the OMW >>>> opctemplate

* List installed policies for host 'localhost'.

Type Name Status Version
--------------------------------------------------------------------
monitor "DISK-WINDOWS-MONITORING" enabled 0001.0001
msgi "OS Messages_joblog" disabled 0001.0016
msgi "opcmsg" disabled 0008.0000
msgi "opcmsg_SM" enabled 0001.0006
sched "Enable Policy A_JOB_MON daily" enabled 0001.0000
trapi "MOM2005" enabled 0001.0016
wbemi "Forward message changes to ServiceCenter" enabled 0001.0037
wbemi "Forward messages to ServiceCenter" enabled 0001.0040
wbemi "FwdMsgAsEmail_APPLICATION7" enabled 0001.0001
wbemi "FwdMsgAsEmail_APPLICATION8" enabled 0001.0001
wbemi "FwdMsgAsEmail_S" enabled 0001.0004


The latest installed patches are:
OMW_00003, OMW_00044, OMW_00051

-/\-
0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
hi,


as Martin said, you need to verify the above steps and from your reply i couldn't see SNMP interceptor policies

you need to deploy SNMP interceptor policy on the NNM ( which generated when you run the NNM adapter)


by the way there are a latest patch for the OMW #58 , download and install it on the OMW as it will solve a lot of problems.

thanks
Mohamed

View solution in original post

Highlighted
Honored Contributor.
Honored Contributor.
With your guide, OMW can received event from NNM but we have so many network devices, So I have to create many rules for 3 regions?

Can I have your input about this?

If I use this policy OMW can process event from NNM and How is about performance of HP OM agent?.

Thankyou,!
-/\-
0 Likes
Highlighted
Absent Member.
Absent Member.
For each device you want to monitor, then the device needs this:

- Make sure the desired network nodes are managed with NNM

- Make NNM a managed node of OMW, because via this managed node all the network messages will come into OMW (as a sort of proxy)

- Within OMW define SNMP nodes, for each device managed by NNM. Configure each node in OMW as "Other - SNMP - V1"

- Also be sure all the DNS resolving is working ok, so it needs to work properly for forward and reverse DNS lookups.

After you have added the nodes, a SNMP interceptor policy needs to be deployed this managed node. The policy will forward every message to a SNMP node in NNM corresponding to the network node.

(if you like our ideas please assign points)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.