James, I went ahead and did load all the Cisco mibs that ship with v6.02.
One question I have though: Does the /usr/OV/newconfig/SNMP-RUN process
handle adding the traps for all of the Cisco mibs that got loaded? Do I need
to mib2trap each of these?
-----Original Message-----
From: Barr, Scott [mailto:Scott_Barr@csgsystems.com]
Sent: Tuesday, September 04, 2001 10:49 AM
To: IBM NetView Discussion
Subject: RE: [NV-L] Cisco MIBs
James, thanks for the response - here is some feedback:
===> What I can tell you about Cisco MIBs and traps is this. We added a
bunch of Cisco traps to 6.0./6.0.21 which you can merge into trapd.conf with
nvaddtrapdconf on the one shipped in /usr/OV/newconfig/SNMP-RUN as the
Release Notes explain.
*** I have loaded the traps as mentioned here.
===> As for MIBs, all the MIBs shipped in /usr/OV/snmp-mibs which do not
specifically say they are V2 should load just fine into either the SNMP V1
MIB loader (xnmloadmib) so you can use them easily with snmpCollect.
*** I have had no trouble loading the MIBs provided, the only issue is which
of them to load. I am using only V1 stuff right now.
===> And if you find you must load SNMPV2 MIBs to support your Cisco device,
then I would load our versions of any Cisco MIBs in place of any with the
same name or content that you pull off the Cisco web site. The ones we
shipped have already been checked for syntax errors and problems. This is
essentially the same advice I gave you in my last append on this subject.
Start with our cisco-tc-smi.mib and snmpv2-tc-v1 rather than Cisco's
cisco-tc-v1smi.my and snmpv2-tc-v2smi.my when you build your SNMPV2 MIB
library.
*** I understand this. Again, the only question is which mibs..... Leslie
actually suggested a good idea of just doing walk of the devices and seeing
what does not get resolved, I will try this on each type of device to see
what I get back. Right now, my production system is messed up, mibs cannot
be successfully unloaded. Much data collection is going on so I can't just
whack the mib file back to default. It appears to be the microsoft MIB that
whacked it.
Thanks for the feedback, I will sally forth.
James Shanks
Level 3 Support
Tivoli NetView for UNIX and NT
Please note that my new id is jshanks@us.ibm.com
"Barr, Scott" <Scott_Barr@csgsystems.com>@tkg.com on 09/04/2001 10:15:50 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "IBM NetView Discussion (E-mail)" <nv-l@tkg.com>
cc:
Subject: [NV-L] Cisco MIBs
Okay, this message is primarily for James.
We had a conversation a while back on Cisco MIBs and which ones to load
etc.
I am about to upgrade my servers to Solaris 2.8 and I am starting fresh. I
need to load MIBs to support the following Cisco devices:
Cisco 7200
Cisco 4000
Cisco 3620/40
Cisco 25xx
Cisco 65xx (switch)
Cisco 55xx (switch)
Cisco 2948 (switch)
Cisco 35xx (switch)
Cisco "probe" (for use with Traffic Director)
Cisco Pix 520 Firewalls
I would like to load "everything" I might need. Where would you believe to
be the minimum / maximum set of MIBs to be loaded or if you haven't the
time to answer that, what methodology (re: puny brain process) could I
apply to make rational decisions about which MIBs to load?
Scott Barr
Network Systems Engineer
CSG Systems
Phone: 402-431-7939
Fax: 402-431-7413
Email: Scott_Barr@csgsystems.com
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|