I like to upgrade to 5.1.3, but nobody help me out.
I ask at IBM, at Tivoli and at my local trader since 8 weeks
but nobody is able to support me the patch.
Normaly I have to recive it for free but it never arrived.
Is there a place in the net to get it???
Michael
James_Shanks@
tivoli.com To: IBM NetView Discussion
<nv-l@tkg.com>
Sent by: cc:
owner-nv-l@tk Subject: Re: [NV-L] MIB table is
bad
g.com
11/10/00
04:30 PM
Please
respond to
IBM NetView
Discussion
That should read "at least 5.1.3" and I think you may still need to call
Support about obtining an e-fix if one of your MIBs uses the BITS
construct.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
James_Shanks@tivoli.com on 11/10/2000 10:15:31 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: IBM NetView Discussion <nv-l@tkg.com>
cc: (bcc: James Shanks/Tivoli Systems)
Subject: Re: [NV-L] MIB table is bad
First of all, there have been MANY fixes to the SNMP V2 MIB loader since
5.1.1 and you will need to be on at leats 5.13 if you expect this to work.
5.1.1 is not current.
Second, not everything Cisco tells you is correct. You do not need to load
RFC1213-MIB.my at all, and I am not certain that you need SNMPv2-TC.my to
load before anything else.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
michael.hamm@tudor.lu on 11/10/2000 09:05:23 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: nv-l@tkg.com
cc: (bcc: James Shanks/Tivoli Systems)
Subject: [NV-L] MIB table is bad
I follow the documentation of CISCO to install the latest
CISCO MIB on my NetView 5.1.1.
They explain:
"Following is a list of MIBs from which many other MIBs import definitions
and the order in which you should load these MIBs:
1. SNMPv2-SMI.my
2. SNMPv2-TC.my
3. SNMOv2-MIB.my
4. RFC1213-MIB.my
5. IF-MIB.my
6. CISCO-SMI.my
7. CISCO-PRODUKTS-MIB.my
8. CISCO-TC.my
"
I install the first MIB successfully. During importing the "SNMPv2-TC.my"
MIB
I recieve the following ErrorMessage from NetView:
" Error Detected.......
linkDown ::= { snmpTraps 3 } (0)
linkDown ::= { snmpTraps 3 } (0)
Textual convention doesnt map to real type.(clause): On or around line
21422
bad parse of ASN type definition.: On or around line 21422. Mib table is
bad."
any hints????
_________________________________________________________________________
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
|