Author: "Hageman, Arjen (A)" <AHAGEMAN AT DOW DOT COM>
Date: Tue, 11 Jan 2000 05:36:34 -0500
To all. We have installed Netview Ver 5.1.2 on NT Ver 4.0. We use the seed file to limit the discovery of our nodes. During implementation, I ran into the following problems. * 3Com devices have a we
Author: James Shanks <James_Shanks AT TIVOLI DOT COM>
Date: Tue, 11 Jan 2000 14:10:45 -0500
Arjen - Your problem descriptions confuse me greatly, because you are assuming some things to be true which are not. I'll try to explain. (1) The W function in oid_to_type does not exist is NetView 5
Author: "Matthew Moore (DSL AK)" <MattM AT DATACOM.CO DOT NZ>
Date: Wed, 12 Jan 2000 09:46:21 +1300
(2) From my experience with Netview/NT, if Netview "discovers" an OID that is not in oid_to_type, then it will "put" in 1.3.6.1.3.1.1.98 or 1.3.6.1.3.1.1.99 (an snmpwalk displays the correct OID). To
Author: James Shanks <James_Shanks AT TIVOLI DOT COM>
Date: Tue, 11 Jan 2000 15:55:41 -0500
OK, Matt, I will bow to experience. We seldom have badoids in our networks here because they are so vanilla and this is not what I saw (or rather it is not what I remember from a year ago). But the N
Author: "Matthew Moore (DSL AK)" <MattM AT DATACOM.CO DOT NZ>
Date: Wed, 12 Jan 2000 10:10:45 +1300
My OID values were actually slightly wrong (I cut and paste from Arjens post, but I'm assuming that these OID's below are what you meant). The following is from oid_to_type: 1.3.6.1.4.1.3.1.1.98:IBM: