17-MAR-2004: Release 0.1.5
Lots of changes. See ChangeLog for a complete list. Most important changes
and features are:
1. RRD file structure has changed for IF-MIB counters. For the sake of
performance optimization in large installations, the number of files
has been minimized. If keeping the old RRD data files is critical,
"configsnapshot" is the right utility for you. See 0.1.4bf2 release
notes for compatibility information. In short, you would need first
to upgrade to 0.1.4bf3, use configsnapshot, and then upgrade to 0.1.5.
Some old versions of important XML template files are stored in
xmlconfig/old.
2. In devdiscover, output file, as well as most other activities, are
controlled only from the input XML file. The number of commandline
options is very minimalistic. See snmpdiscovery.pod for details.
The most important new parameters are: 'output-file', 'output-bundle'.
The devdiscover input file is now referred to as "DDX", or
device-discovery XML.
3. New discovery modules: AscendMax, CiscoFirewall, CompaqCIM, F5BigIp,
NetScreen, MicrosoftWindows, RFC2737_ENTITY_MIB, Xylan; other modules
improved.
4. RRFW is now compatible with BerkeleyDB 4.2. It is highly recommended
to upgrade your installations of BerkeleyDB, because of some bugs
confirmed.
5. For site management purposes, a new utility "genlist" might be useful.
6. Dual configuration database. Now there are two instances of configuration
database: active and passive. Collector and other programs always work
with the active instance. XML compiler first operates with passive
instance, and then makes it active. Thus collector interruption due to
compilation and errors is minimized.
7. Collectors record runtime statistics which are available at any moment.
Those include running time and late start stats. The "schedulerinfo"
utility is used to generate the statistics reports.
8. Aliases are expanded recursively. This gives you extra means of
organizing your data structures.
9. userguide.pod has a description how to set up several instances
of RRFW on one host.
10. For large installations, dispersed collector offset might be a useful
feature.
11. Collector and monitor logfiles are reopened at SIGHUP. This helps
you to set up log rotation if needed.