> I am having a problem with mibII entries that return an IpAdress,
> as in the atTable and tcpConnTable. The management application is
> complaining about the 8 byte values being returned.
Is this on a 64-bit architecture system, by any chance?
> Wondering what the best way to fix this would be or is the
> management app incorrect by erroring when an 8 byte address value
> is returned.
No - the management application is quite correct to complain.
It's expecting to receive a four-octet string value.
The best way to fix this properly is for the agent to move away from
using implicitly-sized types for numeric values ("long", "int",
"long long", etc) and switch to using explicitly-sized types
("int32", "int64" or whatever), with suitable typedefs for each
architecture.
That's perhaps a bit of a drastic change for this particular problem,
but is likely to be the best long-term solution.
In the short term, the easiest fix would probably be to replace the
use of "long_return" in the solaris version of var_ipAddrEntry (and
elsewhere) with a different variable, declared as a 32-bit integer.
Dave
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
|
