The http fields are for launching the web-based management capability
on the devices themselves, for those devices that support it. So the
default url is correct in most cases. I know a number of IBM Nways devices
support this sort of management, as opposed to the telnet-type of
configuration utility, or the ftp kind.
What you are asking for, Joel, is I think what the CW2K integration utility
provides. That is the stuff you download from Cisco and install on Netview
and point it at your CW2k server. There was recently a posting on it:
Details on the integration of Tivoli NetView with CiscoWorks2000 and
software
downloads from Tivoli are available at:
http://www.tivoli.com/products/index/netview/cisco2000_integration.html.
I've seen this, and it is very cool. I suspect it is
what you are looking for.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Joel A. Gerber" <joel.gerber@usaa.com>@tkg.com on 08/24/2000 01:10:35 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "'IBM NetView Discussion'" <nv-l@tkg.com>
cc:
Subject: RE: [NV-L] Vendor Web Integration
OK, we're making some progress. Being able to use the nvdbimport utility
is
a lot better than having to manually update those database fields on every
device on the NetView GUI. That's still not automated enough, though.
Let's dream a little . . .
What if you have a customer with 1600+ Cisco devices that are being managed
by both NetView and CiscoWorks 2000. They need to integrate the web
interfaces from both products. The management URL for every device needs
to
point to a web page on the CW2000 server, e.g. the Device Center page.
When
a new device is discovered, or even at initial discovery of all 1600+
devices, they want the managementURL field to be updated to this custom
URL.
The update needs to be automatic without having to go through gyrations
like
Blaine set up with a Smartset and weekly e-mails that notify him to update
the fields. Does anyone have any ideas for implementing something like
this? Simplicity and ease of maintenance are key requirements. Oh, and
it's got to work reliably.
Thanks!
Joel Gerber - I/T Networking Professional - USAA Information Technology Co.
- San Antonio, TX
* (210)913-4231 * mailto:Joel.Gerber@USAA.com "
http://www.usaa.com
-----Original Message-----
From: lclark@US.IBM.COM [SMTP:lclark@US.IBM.COM]
Sent: Thursday, August 24, 2000 09:01
To: IBM NetView Discussion
Subject: RE: [NV-L] Vendor Web Integration
In V6 there are the fields isHTTPSupported and isHTTPManaged, and
managementURL http.
If, in the oid_to_type file, you indicate that a type of device is
http-managable by adding the W flag,
then these fields will be set to their defaults at discovery. That is, the
fields will be there, and
will be TRUE, TRUE, and //hostname respectively. If the management url is
other than this,
you can change it as Blaine has described. Or you can use the nvdbimport
command to set
these fields, given a list of nodes by Selection Name. See the man page and
the examples
(in /usr/OV/conf/nvdbtools) for more info on nvdbimport.
Note that these fields are NOT refreshed on subsequent configuration polls
in order to
allow you to make any needed customization.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Owens, Blaine C" <bowens@EASTMAN.COM>@tkg.com on 08/24/2000 09:17:29 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "'IBM NetView Discussion'" <nv-l@tkg.com>
cc:
Subject: RE: [NV-L] Vendor Web Integration
Joel, right-click on the icon for the device then click "Edit" -->
"Modify/Describe" --> "Object". Then click "HTTP", then click "View/Modify
Object Attributes". This is where you set the "HTTP supported" and the
"HTTP managed" fields. I manually (ugh) did this for all of our Fore
switches (about 100) and then defined a collection for any Fore switch
which
did not have "HTTP supported" set in order to catch any new switches. I run
a cron job once a week to execute nvUtil and email me if any devices are in
this collection. If there is a more automatic way of doing this I don't
know
what it is. Would probably be a nice feature to add to oid_to_type. After
all, more and more vendors and moving toward HTTP management of their
devices.
If anyone knows of a more automated way of doing this I would like to know
as well. Thanks.
Blaine Owens
Eastman Chemical Company
Phone - (423)-229-3579
Fax - (423)-229-1188
bowens@eastman.com
-----Original Message-----
From: Joel A. Gerber [mailto:joel.gerber@USAA.COM]
Sent: Wednesday, August 23, 2000 3:53 PM
To: 'IBM NetView Discussion'
Subject: [NV-L] Vendor Web Integration
Blaine,
Can you provide some details on how you added the "HTTP supported" fields
to
the devices? Also, are you using the "HTTP managed" field at all? We are
trying to integrate the NetView and CiscoWorks web interfaces. We got it
working (somewhat), by manually defining the management URL for a device,
but would like some automated way of defining the database fields for all
the devices, and correctly setting the fields on newly-discovered devices.
Joel Gerber - I/T Networking Professional - USAA Information Technology Co.
- San Antonio, TX
* (210)913-4231 * mailto:Joel.Gerber@USAA.com "
http://www.usaa.com
-----Original Message-----
From: Owens, Blaine C [SMTP:bowens@EASTMAN.COM]
Sent: Tuesday, August 22, 2000 13:00
To: 'IBM NetView Discussion'
Subject: RE: [NV-L] Fore Hubs and switches
We are managing all of this using NetView and Fore's Foreview. There are
numerous mibs to be loaded and traps to be defined - it would be a chore to
load and define all manually - the Foreview install does this for you with
one big gotcha - all of the Fore mibs are SNMP V2. Forget how, but somehow
you can change the install to execute xnmloadmib2 rather than xnmloadmib.
If you choose not to get Foreview then you should be able to get all of the
mibs you need from Fore. There are quite a few mibs to load for each of
these models.
The latest version of Foreview was for HP Openview only. We got HP Openview
for this reason only but we were so disappointed in the new version of
Foreview that we dumped it. Most of the Fore switches are HTTP supported. I
created collections on NetView for all our ATM switches, added the "HTTP
supported" to the objects, created another collection to capture any
switches which did not have the "HTTP supported" set so I could catch new
switches. This gives us just about all that HP Openview added to management
of these switches.
Blaine Owens
Eastman Chemical Company
Phone - (423)-229-3579
Fax - (423)-229-1188
bowens@eastman.com
-----Original Message-----
From: Mark Malki [mailto:m_malki@HOTMAIL.COM]
Sent: Tuesday, August 22, 2000 1:26 PM
To: nv-l@tkg.com
Subject: [NV-L] Fore Hubs and switches
Hi Folks
I have a customer who want to manage some Fore Hubs and Switchs, he
like to know if he could manage the following through Netview, he need s to
know if he could manage the following in anything else other than IP
address, here what he has. i think he is trying to manage them through ATI
or ATM.
Fore ESX 3000
Fore ESX 2000
NSC-1 ESX 2400 Controller
ASX-200 BX
Power Hub 7000
Has anyone dealt with problem before, is there a mib file thant i
could use to manage these Hubs, and Switches in anything else instead IP.
and if yes could anyone provide me the information please....
Mark Malki
Please reply to m_malki@hotmail.com <mailto:m_malki@hotmail.com> or
mark.malki@xacta.com <mailto:mark.malki@xacta.com>
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|