RE: [nv-l] Looking for advice
2002-02-12 09:44:02
I
agree with James.
HP
OpenView Network Node Manager (NNM) uses pmd-to-pmd communications over TCP in
order to forward events from one system to another. ovtrapd doesn't forward
traps, but you can configure ovactiond to use e.g. snmpnotify to forward the
trap using SNMP/UDP. Forwarding traps (in both directions) is probably the best
you can do.
As
James says the databases are no longer compatible and this is also the case for
a number of the API's.
What
other integration did you have in mind? The GUI's could be integrated using the
registration files with e.g. URL's for the web interfaces.
NNM
uses either an embedded SQL database from Solid Technologies or MS SQL-Server or
Oracle for a data repository for report generation. I'm not sure about NetView,
but he NNM schemas are described in the documentation and this could be a way to
integrate report or inventory data.
Let me
know if you need more info and we can take it offline.
Best
regards,
Michael.
+-----------------------------------------------------------------------+ |
Michael Imhoff Nielsen Phone:
+45 4599
1000
| | IT Management Consultant Direct: +45 4599
1431
| | HP
Consulting
Fax: +45 4599
1001
| |
Hewlett-Packard
Mobile: +45 4060
1431
| | Kongevejen
25
Internet:
michael_imhoff AT hp DOT com
| | DK-3460 Birkeroed
TN:
546-1431
| |
Denmark
http://www.hp.com/hps/hpc/i_management.htm
| +-----------------------------------------------------------------------+
Good luck. In
my opinion, HP has spent no small amount of time and effort to stop using the
APIs they initially wrote when NetView was cloned from OpenView (back in the
Version 1 days, almost ten years ago) to prevent exactly this. They no
longer even support the direct forwarding of traps from our trapd to theirs,
though you could configure NetView's trapd to forward all his traps to OpenView
using udp. But what OpenView will do with them, other than display them,
is anyone's guess. Ditto for the reverse flow.
I know for a fact that the databases are not
transferable.
You could have a
NetView and an OpenView monitoring the same devices, but other than having
two separate management systems polling the same devices, I don't know what this
would accomplish.
James
Shanks Level 3 Support for Tivoli NetView for UNIX and NT Tivoli
Software / IBM Software Group
| "Allison, Jason (JALLISON)"
<JALLISON AT arinc DOT com>
02/11/2002 05:09 PM
| To:
"'nv-l AT lists.tivoli DOT com'"
<nv-l AT lists.tivoli DOT com> cc:
"Allison, Jason (JALLISON)" <JALLISON AT arinc DOT com>
Subject:
[nv-l] Looking for advice
|
I know
this may not be the best question, but it is an initiative I will be working
on in the near future.
Has anyone gotten Tivoli Netview and HP Openview
to 'communicate' by any means?
I know this is a very broad question,
but my company uses both Netview and Openview. I have been asked to
look into how to get them to talk to each other if at all possible. If
they cannot communicate on the surface, I will be looking to write an
application at the socket level for communication with respect to traps and
status delivery.
All input is appreciated,
Jason
Allison Principal Engineer ARINC Incorporated Office: (410)
266-2006 FAX: (410)
573-3026
--------------------------------------------------------------------- To
unsubscribe, e-mail: nv-l-unsubscribe AT lists.tivoli DOT com For additional
commands, e-mail: nv-l-help AT lists.tivoli DOT com
*NOTE* This is not an
Offical Tivoli Support forum. If you need immediate assistance from Tivoli
please call the IBM Tivoli Software Group help line at
1-800-TIVOLI8(848-6548)
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [nv-l] Looking for advice, Allison, Jason (JALLISON)
- Re: [nv-l] Looking for advice, James Shanks
- RE: [nv-l] Looking for advice, Allison, Jason (JALLISON)
- Re: [nv-l] Looking for advice, Stephen Hochstetler
- RE: [nv-l] Looking for advice,
IMHOFF,MICHAEL (HP-Denmark,ex1) <=
- RE: [nv-l] Looking for advice, Allison, Jason (JALLISON)
- RE: [nv-l] Looking for advice, Stephen Hochstetler
- RE: [nv-l] Looking for advice, Allison, Jason (JALLISON)
|
|
|