Let me start by saying that I am extremely impressed by your posting James.
It sure raises my respect for Tivoli's commitment to making the NetView
product what the customers need it to be (what are you guys
smoking/drinking?). Why didn't they ask this in the NetView 6.0 Managed
Beta program? (just a rhetorical question; you don't need to answer).
My first reaction is to answer "all of them", but then I woke up from my
dream. Cisco has hundreds of MIB files, and it's probably not a realistic
expectation for Tivoli to include them "all". Another possibility is to
include the "bare minimum" number of MIB files that will benefit the most
customers. I think that all of the files supporting Cisco routers, and
IOS12.0 should be included. Instead of listing them all here, just look in
the Cisco MIB Support list at:
the way, all of the "OLD-CISCO*" files are now obsolete with IOS 12.0.
Beyond the routers, I would vote for adding MIBs that support the following
Catalyst 5000 series switches
Catalyst 6000 series switches
Catalyst 8500 series switches
Again, if you want a list of MIB files, let me know, but it's a whole lot
easier to just get them off of CCO (see links below).
If I could add a slightly different perspective from a customer that's
committed to both Cisco and Tivoli, there is a lot of improvement needed in
the area of CiscoView and NetView integration. Because we have so many
Cisco devices, we purchased the CiscoView product. The fact that NetView
does not have MIBs and traps defined for Cisco devices is not that big a
deal to us because they're provided (partly) with CiscoView. When we
install/update CiscoView device packages, we get the MIB files needed to
support that device. Not very many traps are defined with the CiscoView
install, but we've used the mib2trap utility, and gotten along OK. While it
would be a big improvement if the base NetView product has more Cisco MIB
and trap support, a CiscoView install can wipe it all out. When CiscoView
installs a device package, MIBs are loaded (optionally), and some, but not
all, traps are (re)defined (NOT optional). I know that Cisco has a big part
to play in this, and Tivoli has no control over them, but if the two vendors
can achieve better integration in their products, then the customers will
truly benefit. Please exploit the "renewing and deepening our strategic
partnership with Cisco" that you mentioned.
Here are some good resources on CCO for looking up MIB info:
Cisco MIB "home page"
Cisco "Public" MIB files http://www.cisco.com/public/mibs/
Joel Gerber - I/T Networking Professional - USAA Information Technology Co.
- San Antonio, TX
* (210)456-4231 * mailto:Joel.Gerber AT USAA DOT com "
From: James Shanks [SMTP:James_Shanks AT TIVOLI DOT COM]
Sent: Tuesday, February 29, 2000 10:31
To: NV-L AT UCSBVM.UCSB DOT EDU
Subject: What Cisco MIBs should NetView include?
Hello everyone -
I have been asked by development what Cisco MIBs (V1 versions) should be
to the /usr/OV/snmp_mibs directory in NetView to make it more useful to the
broad range of customers. Right now, as you know, the only Cisco MIB
with NetView is the 1992 draft version which outlines their products,
/usr/OV/snmp_mibs/cisco. Not very useful.
Since just about everybody with Cisco routers (and who doesn't have them?)
more MIBs and runs mib2trap to define a bunch of Cisco traps, some bright
(finally) thought we could make life easier by simply including them with
NetView product, especially since we are renewing and deepening our
partnership with Cisco. So we could ask Cisco what they would add, but we
don't want just their opinion. We want yours.
Anybody care to provide a list of which ones they would like to see
If you want to send along a copy of the MIB, please do, but don't send that
the list because of space considerations. You can send those to me
james.shanks AT tivoli DOT com
Tivoli (NetView for UNIX and NT) L3 Support