Cartographer Project Release Notes

From Krupczak.org
Revision as of 12:12, 24 September 2009 by Rdk (Talk | contribs)

Jump to: navigation, search

Contents


Release 1.1

Whats New in Release 1.1?

Minor Tweaks and Enhancements

  • Windows installer officially released. It previously had been beta.
  • Support for Windows 64-bit on Vista and higher.
  • Tweaks for Vista.
  • Added CPU total counters to Cartographer CPU table.
  • Added system-wide scalar CPU totals.
  • More tweaks and enhancements for 64-bit Linux kernels.
  • XML schemas for XMP SMI and protocol are now defined and included in release.
  • Routing dependency enhancements.
  • Support for Win2k dropped (really, this is a feature). WinXP and higher are supported.

Bug Fixes

  • Various memory leaks in agent and plugins tracked down using Valgrind and Helgrind.
  • mib2 - LinkUp and LinkDown Traps would sometimes incorrectly report ifIndex value. ifIndex value is worthless but it is sometimes expected by management software.
  • mib2 - Include interface name in LinkUp and LinkDown Traps to more easily identify the interface that is changing state.
  • Cartographer plugin - peer dependency discovery was not properly handling peers that had dependencies to themselves.
  • xmpd - Update DNS hostname resolution functions to properly call re-entrant functions rather than thread-unsafe versions.
  • Cartographer plugin - updated to properly call re-entrant functions instead of thread-unsafe versions.
  • mib2 - ifSpeed improperly set to 0 for IPv6 interfaces.
  • mib2 - support for (worthless) ifIndex now included for backwards compatibility
  • restartxmpd.sh - improperly called chmod. Fix to include correct path.
  • mib2 - ifSpeed improperly set to 0 for tunnel interfaces.
  • Cartographer plugin - 127.127.1.0 is improperly showing up in dependency tables for local dependencies to NTP.
  • Cartographer plugin - diskReadKB = diskWriteKB for Solaris and Linux. Fixed typo.
  • Cartographer plugin - Drive (filesystem) C:\ could be skipped due to incorrect bitmask manipulation

Release 1

Whats New in Release 1?

Everything is "new" in this release. While it is the first publicly available release, the software has been in continuous usage for quite some time (see the different copyright dates in various source files) and is stable.

Why are the version numbers less than one when this release is termed Release 1? Version 1.x will signify a stable API and protocol. Since this is the first publicly available release, we felt it best to gather community feedback prior to codifying a version 1.0.

The first, initial release consists of the following components/versions.

  • Cartographer GUI version 0.27
  • Agent engine (xmpd) version 0.72
  • MIB2 plugin version 0.91
  • Cartographer plugin version 0.41

Known Issues in Release 1

  • Some default installations of 64-bit Linux do not automatically include 32-bit versions of libxml, libz, and libgcc and thus need to be installed by hand. On Redhat/Fedora 64-bit systems, one can add them very simply by executing the following command:
yum install libxml2.i386 libgcc.i386
  • Some default installations of 64-bit Linux do not automatically include a 32-bit libgcc_s which is required by pthreads_cancel(). If not present, the library can be installed by hand.
yum install libgcc.i386
  • Rare segmentation-fault on UNIX.
  • New and improved Windows Vista security makes running ntsetup and cartographertray a real chore.
  • Automatic upgrades sometimes (very rarely) fail because agent engine takes too long to stop and re-start.
  • Windows use of reserved ports during dynamic binding fools some dependency determination. For example, an application may ask for a dynamically-bound TCP port and be assigned the well-known and/or reserved port of 1812 thus triggering a false Radius dependency.
  • Dependencies determined via TCP port allocation may be missed of the connections are short-lived.
  • XML DTDs or Schemas are needed for XMP and MIBs.
  • IPv6 support is included but still needs more work with respect to DNS.
  • NAT'ing routers obstruct inward-bound XMP communication.
  • Self-deployment is still under development but self-upgrading functionality is complete and included in this release.
Personal tools