HP OVO for windows Agent configuration 1

[JPJoanany]

Hello,
I am quite new on HP OVO. I have installed the manager on a W2000 Server and a agent on my machine. I would like to verify wether the agent is able to communicate with the manager. I generate a trap on my machine and nothing happen.
Is there somewhere into the agent where I can set the port numbre or anything like that.

Thanks you

jean-paul

 

[vlan52]

Hi JPJoanany, are you sure from your pc, can resolve the name of the management server?
Is there a firewall in the middle?
When you talk about a trap, have you generated an snmp trap?Because your OVO server will expect a trap with an OID that is properly configured under NNM, or a properly configured message sent through "opcmsg" from the agent.
If you have a firewall in the middle you may want to specify a port range for the agent to use, right below I'll attach a little config.
Usually, your OVO server will need to use as source the folowing port range: 12001-12060 and the agent I usually have it answering from 13001-13010, with full access to port 135, all of these TCP ports of course.

Once again, make sure you can resolve the name of the OVO server from the agent, if not possible, add a line to your /winnt/drivers...../etc/hosts file, ok?Or proper DNS resolution would be great.

The following configuration applies to the /opt/OV/bin/OpC/install/opcinfo file, no blank lines are expected, aprtuicularly after de "OPC_RESTRICT_TO_PROCS" lines!!!
-----------------------------------
OPC_DIST_MODE DIST_RPC
OPC_RESTRICT_TO_PROCS opcctla
OPC_COMM_PORT_RANGE 13001
OPC_RESTRICT_TO_PROCS opcdista
OPC_COMM_PORT_RANGE 13002-13003
OPC_RESTRICT_TO_PROCS opcmsga
OPC_COMM_PORT_RANGE 13004-13006
OPC_RESTRICT_TO_PROCS opccma
OPC_COMM_PORT_RANGE 13007
OPC_RESTRICT_TO_PROCS opcvterm
OPC_COMM_PORT_RANGE 13008-13009
OPC_MAX_PORT_RETRIES 70
-----------------------------------------

Hope this helps, regards,
vlan52


vlan52
The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.

 

[JPJoanany]

Hi Vlan52,

I am testing on my LAN so there is no firewall in the middle. I am using the Windows version of OVO, I didn't find any opcinfo file on the server, there is one on the managed node. Currently all the information you have related to me are not set into that file, Should I modify it?

JPJoanany

 

[vlan52]

Just after the install, on the managed node, make sure you have "name resolution" from your management server (resolving the name of the managed node).
Have you set up or discover the pc you are trying to monitor under OVO / NNM?
Is the pc/object assigned to your Node Bank/Node Group?
Have you assigned templates to this pc?
Have you distributed those templates?

Let us know please, best regards,
vlan52


vlan52
The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.

 

[bas1080]

Hi,

To be more concise add OPC_RESOLVE_IP x.y.z.q(ip address) of Management server in opcinfnce agent is added to the Management server syncronise the polocies from the task option.

bas10180

 

[bas1080]

Forgot to tell one thing the opcinfo file will be on the managed node where the agent is installed.

 

[vlan52]

Yes, the opcinfo file is on the managed node, under /opt/OV/bin/OpC/install/opcinfo (Unix)and look under /usr/opt/OV/bin/install (Windows).
OPC_RESOLVE_IP x.y.x.a helps a lot, you could, if you have multiple interfaces on one managed node, set the interface's IP address you are interested in, using OPC_IP_ADDRESS x.y.z.a

Good luck!
vlan52


vlan52
The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.

 

[JPJoanany]

Thanks for all,

everything is running well now.

JPJoanany