• InterMapper can now send secure e-mail using SSL/TLS1; STARTTLS is now
  supported.

• Outages log now uses 24-hour time rather than AM/PM notation to make it
  easier for log processors to process.

• Host Resources probes can now display more than 255 characters in the
  reason portion of the Status Window.

• Fixed an issue where InterMapper would crash on particular Linux systems
  (CLOCK_MONOTONIC not available) at times that were a multiple of 2.25 years
  since the Unix epoch.

• Log setting for Web, Telnet, and Remote servers are once again remembered
  correctly.

Read the What's New? page for an overview of the release, or the Release Notes for the full details of changes to this release.

You can download the current version from the Download Page.

Although we will be checking e-mail from time to time, we may not be as responsive as usual. Our telephone number will remain the same: 603-643-9600.

Our physical address will be:

Dartware, LLC
66 Benning Street, Suite 7
West Lebanon, NH 03784

We look forward to serving you from our new location.

The problem has to do with an error in computing the internal timer used to schedule operations. This problem could occur within a 12-hour window preceding 9:51am local time on 24 July 2008. At that time, the InterMapper server would lock up or crash. It could be safely restarted after 9:51am local time. If uncorrected, this bug would recur in 2.25 years.

The short-term workaround is to restart the InterMapper process after 9:51am local time on 24 July. Because the bug only affects an InterMapper installation that is running at that specific time, you will be able to continue operation afterwards. To restart the InterMapper server, use this command:

/etc/init.d/intermapperd start

We have prepared a new beta version — InterMapper 5.0.3b3 — that addresses this bug. It is available from this URL. A final version will follow early next week.

Download InterMapper 5.0.3b3

We apologize for the inconvenience that this error has caused.

• It is now possible to disable IPv6 support within InterMapper server using a command-line argument (--no-ipv6) or a configuration file option (IPv6 false).

• The --listen command-line argument is now honored in InterMapper server. It only supports IPv4 addresses and implicitly disables IPv6 support.
• InterMapper now starts faster with large Chart Data folders.
• IPv6 addresses are bracketed when passed to Helper Apps.
• InterMapper Database: Greatly reduced processor and memory usage when an import is in progress.
• Many other minor fixes.

Read the What's New? page for an overview of the release, or the Release Notes for the full details of changes to this release.

You can download the current version from the Download Page.

• Bug Fixes: Works with Gnome 2.22 desktop entries; Status and Ack filter buttons are preserved across map closing; Update to Xserve RAID probe when a RAID was 'degraded'; Fixes to SMTP probes and the SMTP notifier;

• Many other minor fixes.

Read the What's New? page for an overview of the release, or the Release Notes for the full details of changes to this release.

You can download the current version from the Download Page.

It is not. The SNMPv3 code within all versions of InterMapper checks the length of the authentication parameter before trusting it.

For more on this advisory, see:

http://www.us-cert.gov/cas/techalerts/TA08-162A.html

InterMapper 5.0 brings a host of new features, including:

1. IPv6 Support: InterMapper 5.0 tests devices that have IPv6 addresses, and
   supports IPv6 client connections. You can test devices with IPv6 addresses
   using Pings, TCP- and UDP-based probes, and IPv6-based DNS queries.
2. InterMapper Database Technology Preview: InterMapper 5.0 can collect data
   from networked devices, inserting it into a SQL database. You can write your
   own SQL queries, based on various Crystal Reports and sample reports.
   Note: We have chosen to label the InterMapper Database as "technology
   preview" because it is stable, but not ready for production use. We have
   tested it enough to believe that the fundamentals all work. However, a great
   deal more testing is required before we can claim that it meets our
   standards for a final product, and there are a number of optimizations yet
   to be implemented.
3. Enhanced Nagios Plug-in support: InterMapper has long supported
   command-line probes and has supplied a template specific to Nagios plugins.
   In Version 5.0, there is a new Nagios Plugin probe
   (Miscellaneous/Nagios/Nagios Plugin in the Set Probe... window) that
   displays the plugin's output string and makes chartable values for all the
   performance data ("perfdata").
4. Folders in the Map List: You can now organize your maps into folders,
   reducing clutter for those who have lots of maps.
5. Ack Filtering in List views: There are two new buttons (at the top right
   of the window) that hide or show devices that have been acknowledged. This
   will make it easier to spot new trouble areas.
6. Server-wide find on DNS name, IP address, label or IMID: The "Find
   Devices..." menu item allows you to search either a map or the entire
   InterMapper Server for a given DNS name, IP address, label or IMID.
   Searching by IMID can be helpful for relating a device in InterMapper
   Database to a device on the map.
7. Server Discovery Preference: InterMapper RemoteAccess now implements a
   preference allowing you to turn off server discovery, so that the only
   servers which appear in the Map List window are those servers you have added
   yourself.

As always, thanks for your interest and enthusiasm for InterMapper.

The InterMapper Team

LINKS:

Download

Release Notes

What's New

User Guide

Developer Guide

InterMapper Database Overview Tech Note

Disk Space Estimator for InterMapper Database

• Riverbed Steelhead Probe
  Andrey Gordon from Epic Systems sends a probe that monitors the CPU, temperature, optimization service status, and connection counts for Riverbed Steelhead appliances. more...

• Check SNMPTT Probe
  Anthony Rodgers from the District of North Vancouver sends a command-line probe that uses SNMPTT (SNMP Trap Translator) to translate SNMP traps into human-readable messages. more...

There is a new tool for creating these tables using values from a MIB. You can read more about the tool at the On-Demand Table Maker page.

• Bug Fixes: no failure importing a group with null users; fixed problem with shared polling; fixed error with ridiculously high (4.2 million seconds) response times; fixed error in Host Resources probe handling.

Read the What's New? page for an overview of the release, or the Release Notes for the full details of changes to this release.

You can download the current version from the Download Page.

• Updates to interface display options; checks ifSpeed every poll cycle.
• A number of bug fixes for: MS-CHAPv2 when using IAS or Radius; auto-login for map status probes; syslog notifiers.

Read the What's New? page for an overview of the release, or the Release Notes for the full details of changes to this release.

You can download the current version from the Download Page.

This zip archive contains both the probe and three MIBs, all of which must be imported into InterMapper. more...

Compatibility Note: Time Machine
Within your InterMapper Settings folder, the InterMapper Logs, Chart Data, and Temporary folders contain large, frequently updated files that will quickly fill up your backup disk. Starting with InterMapper 4.6.5, these folders in your InterMapper Settings folder have been automatically marked as “off-limits” for Time Machine backups:

- InterMapper Logs
- Chart Data
- Temporary

Do not rely on Time Machine to back up these folders on Leopard.

If you are running an earlier version (pre-4.6.5) of InterMapper on Leopard with Time Machine enabled, Dartware recommends that you manually exclude these three folders from Time Machine backups. Installing 4.6.5 fixes this automatically.

Compatibility Note: Leopard Firewall
If the Leopard firewall is enabled, you must add exceptions for intermapperd and intermapperauthd. Without these exceptions in the Leopard firewall, intermapperd will be unable to check the status of devices using UDP or ICMP-based probes; instead, all devices will be reported as unreachable and therefore down.

Earlier versions of intermapperd (pre-4.6.5) are not compatible with the Leopard firewall. When added as a firewall exception, intermapperd will run once then cease to function.

Installing 4.6.5 installs a new binary, replacing a damaged one, but does not automatically add a firewall exception. You still have to add the exception manually. To do this, open the Security system preference and click on the Firewall tab. Click the “+” button to bring up the Open... dialog and type cmd-shift-G to show the “Go to the folder:” sheet. Type /usr/local/bin and press return. You should see the contents of the /usr/local/bin directory. Add both intermapperd and intermapperauthd from this directory to the list of firewall exceptions and set their status to “Allow incoming connections”.

Background: Leopard’s Application Layer Firewall & Ad-Hoc Code-Signing
Leopard includes a new application layer firewall that controls access to the network based on the program that is running instead of arcane protocol numbers. The Leopard Firewall settings lets you specify individual programs as “exceptions” that can access the network.

For InterMapper to run on a Leopard system with the firewall enabled, two of its executable files must be added as exceptions to the firewall rules: intermapperd and intermapperauthd. Without these exceptions, InterMapper cannot monitor the network.

When you add an exception to the firewall, Leopard uses a program’s code-signature to authenticate it. If the program’s code was not signed by its developer, Leopard temporarily signs the program for you. This process is called ad-hoc code-signing, and it’s also used by other parts of the OS that need to identify programs with particular privileges (e.g. Parental Controls).

Unfortunately, the ad-hoc code-signing process on Leopard irretrievably damages the intermapperd binary. When it rewrites the executable to add the code signature, it chops off about 700 Kbytes from the original binary. From that point on, intermapperd will refuse to run.

A symptom of a damaged binary is that InterMapper will run fine when you first install it, but it won’t start up again if you try to restart it or simply reboot the computer. You may see a complaint in the system.log that says, “Executable has no resource section: /usr/ local/bin/intermapperd”. There is nothing you can do at this point except re-install InterMapper.

Starting with version 4.6.5, Dartware now signs the intermapperd binary. This fix prevents Leopard from applying an ad-hoc code signature and breaking intermapperd.

• InterMapper Helps One Family Reduce its Carbon Footprint

• InterMapper Database Enhancement

• Hardware Survey

• Training: Custom Probe Creation Class

• Gallery of Map Screen Shots

• New Knowledge Base: Tips for Using InterMapper

You can read it at http://dartware.com/support/newsletters/nov2007.html

We will be sharing a booth with System & Project, a Dartware Enterprise Technology Partner and VAR, within the Cisco show area at INTEROP in Berlin on November 6th to 8th. We invite all to come and see us demonstrate the latest version of InterMapper.

You will find us in Hall 2.2, Stand A 164. If you haven't made arrangements yet, complimentary tickets are available for customers and people still evaluating the software.

• Cisco 4400 LWAPP Controller Probe This probe displays CPU utilization, total RAM, free RAM, the first three WLANs, and tables for Connected APs and Rougue APs. more...
• MGE EPC 6000 Series UPS Probe This probe is a modification of Bill McHargue's MGE EXL5 UPS probe. It provides basic monitoring of an MGE EPC 6000 UPS with a UM-Link Ethernet interface, including phases B and C. more...