> 5.1.1 > hrStorageEntry.hrStorageDescr.2 = STRING: Real Memory > hrStorageEntry.hrStorageDescr.3 = STRING: Swap Space > > 5.0.9 > hrStorageEntry.hrStorageDescr.101 = STRING: Real Memory > hrStorageEntry.hrStorageDescr.102 = STRING: Swap Space
Yes - that's correct. The old arrangement put an artificial limit on the number of mounted filesystems that could be reported before running into these "oddity" entries. By putting them at the start instead, it's made it possible to handle significantly larger numbers of mounted filesystems. > Doesn't seem like a good idea to have ifindex values change between > versions, but if their is a good reason than it must be done. Please note that in general, MIB index values are not guaranteed to remain constant when an agent re-starts. It is quite common for the same information to be provided in a different order, and monitoring tools really need to be able to cope with this. I'm a little surprised that Cricket didn't spot the change and adjust automatically. Dave ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Net-snmp-users mailing list [EMAIL PROTECTED] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
