Re: BITS limitation to 32bits vs new MAU-MIB

2006-06-21 Thread Dominique bastien
Yes, I used MFD code. The command is: env MIBS="+MAU-MIB" mib2c mib2c.mfd.conf ifMauTable The error message is: ** ACK! I cannot handle BITS longer than 4 bytes! In file "details-enums.m2i" I'm working on a 32-bits machine. I going to stay with my workaround for this first pass. Dominique --

Re: udpTable byte order issues (again)

2006-06-21 Thread Thomas Anders
Robert Story wrote: > I'd be more impressed w/tests on Solaris x86 vs Solaric Sparc. > > I can't see how just reversing the patch, which fixed some platform, is going > to work w/out breaking that platform again. Well, I think the original patch didn't fix that platform. It didn't even change the

Re: udpTable byte order issues (again)

2006-06-21 Thread Robert Story
On Wed, 21 Jun 2006 17:38:47 +0200 Thomas wrote: TA> Thomas Anders wrote: TA> > I've attached a patch against 5.3.x CVS that adjusts the change to how TA> > it was probably meant in the first place. It finally brings TA> > udpLocalAddress handling in line with udpLocalPort handling. TA> > TA> > I'

Re: BITS limitation to 32bits vs new MAU-MIB

2006-06-21 Thread Robert Story
On Wed, 21 Jun 2006 08:31:13 -0400 (EDT) Dominique wrote: DB> I currently work on an implementation of the DB> EtherLike-MIB and the MAU-MIB inside netSNMP. When I DB> generate the code for the ifMauTable the mib2c stop DB> with the error about the limitation of BITS to 32 DB> bits. the object ifMa

Unsnarling an rpmdb from the HR MIB

2006-06-21 Thread Jeff Johnson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi -- A long time ago in a far and distant place, I sent a patch to ucd- snmp in order to support extraction of package names and install times from an rpmdb. Well, that wasn't the bestest hack I've ever done. Tying a network daemon into an instal

Re: udpTable byte order issues (again)

2006-06-21 Thread Thomas Anders
Thomas Anders wrote: > I've attached a patch against 5.3.x CVS that adjusts the change to how > it was probably meant in the first place. It finally brings > udpLocalAddress handling in line with udpLocalPort handling. > > I'm calling for votes to apply this to 5.3.1. Works for me at least for Li

BITS limitation to 32bits vs new MAU-MIB

2006-06-21 Thread Dominique bastien
Hi, I currently work on an implementation of the EtherLike-MIB and the MAU-MIB inside netSNMP. When I generate the code for the ifMauTable the mib2c stop with the error about the limitation of BITS to 32 bits. the object ifMauTypeListBits is now 41 bits long to support 10G interfaces. I remove

Re: udpTable byte order issues (again)

2006-06-21 Thread Thomas Anders
Thomas Anders wrote: > Checking 5.3.x CVS, I still/again(?) see byte order issues in udpTable > for a number of platforms, including Linux/x86. Examples: > > Linux/x86: > UDP-MIB::udpLocalAddress.10.8.2.1.123 = IpAddress: 1.2.8.10 > UDP-MIB::udpLocalAddress.127.0.0.1.123 = IpAddress: 1.0.0.127 > U

Hp-OpenView gives an error "TrapID Already in use"

2006-06-21 Thread Tanmoy, Sil
Hi,   In HP-Open View unloading of MIB is not proper, I have two MIB, which has same trap name " adpAlarmStateEnabled " (id:9001) , but Trap OID is different, ie, in one MIB it is " 1.3.6.4.1.x.9001", and in second MIB "1.3.6.4.1.y.9001".   When X MIB is Loaded after Loading Y MIB, HP-Open View g