Re: MIB Table Index

Hi, Brian Beattie wrote: > I'm down to implementing the table in my MIB and in "Understanding SNMP > MIBs" I read the following: > > "The encoding of the values of all the index items for a table man not > cause SNMP variables to contain more than 128 components > (sub-identifiers)" I think you

udpTable byte order issues (again)

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 UDP-MIB::udpLocalAddress.127.0.0.1.8

MIB Table Index

I'm down to implementing the table in my MIB and in "Understanding SNMP MIBs" I read the following: "The encoding of the values of all the index items for a table man not cause SNMP variables to contain more than 128 components (sub-identifiers)" I'm having trouble understanding that. The best I

Re: 0-based or 1-based indexing

Thanks for the clarification, David. You are quite correct - I was thinking/talking in terms of the full OID of an entry in a table (i.e. a column instance). And specifically one indexed by a single integer. The final subidentifier of the OID of a MIB definition cannot be 0, regardless of whether

Re: 0-based or 1-based indexing

HI, Let me be stronger in response than Dave Shield. See inline below. On Tue, 20 Jun 2006, Dave Shield wrote: > [EMAIL PROTECTED] wrote: > > But are _all_ OIDs that end in > >0 scalars? Is that just a convention or is it a contraint imposed by > >SNMP or an

Re: 5.3.1.rc1 build test status

Thomas Anders wrote: >Dave Shield wrote: > > >> net-snmp-V5-3-patches# make test >> 37:testing snmpd embedded perl support (using NetSNMP::agent)...FAIL >> Summary: 58 / 59 succeeded >> >> > >I think Robert and I managed to track it down yesterday on IRC. I've >just checked in a fix (5

Re: 5.3.1.rc1 build test status

Dave Shield wrote: >net-snmp-V5-3-patches# make test >37:testing snmpd embedded perl support (using NetSNMP::agent)...FAIL >Summary: 58 / 59 succeeded I think Robert and I managed to track it down yesterday on IRC. I've just checked in a fix (5.3.x and MAIN). Can you please confirm tha

Re: Net-snmp compilation issue

Hi Thomas,   Thanks for your reply. Currently I am trying to compile the source in Solaris 10.  With --enable-ipv6 --with-transports="UDP UDPIPv6  TCPIPv6 TCP" enabled. It failes to configure with below errror <> | #if HAVE_UNISTD_H | # include | #endif | int | main () | { | if ((u_int64_t

Re: Net-snmp compilation issue

Pradhap D wrote: > I am trying to compile latest net-snmp 5.3.1 with the options > #./configure --enable-ipv6 --with-mib-modules='host disman/event-mib > ucd-snmp/diskio' --with-cflags=-Dsolaris_2 --with-transports='UDP UDPIPv6 > TCPIPv6 TCP' > > But it thows error as > > checking for uint64_t

Re: 0-based or 1-based indexing

[EMAIL PROTECTED] wrote: > But are _all_ OIDs that end in >0 scalars? Is that just a convention or is it a contraint imposed by >SNMP or an unavoidable outcome of how OIDs are generated and handled? > > It's a convention. There's nothing to say that you *can

Net-snmp compilation issue

Hi ,   I am trying to compile latest net-snmp 5.3.1 with the options #./configure --enable-ipv6 --with-mib-modules='host disman/event-mib ucd-snmp/diskio'  --with-cflags=-Dsolaris_2  --with-transports='UDP UDPIPv6 TCPIPv6 TCP' But it thows error as checking for uint64_t... yes checking for u_in