/*
** SellaNMS
** $Id: BUGS,v 1.13 2006/01/23 07:43:21 sella Exp $
** Copyright (c) 2001-2006 Digital Genesis Software. All Rights Reserved.
** Released under the GPL Version 2 License.
** http://www.digitalgenesis.com
*/

SNMP Discovery Bug
------------------
SellaNMS's SNMP discovery processes may hang (won't complete) for network elements that respond to ICMP however are not configured to properly respond to SNMPGET requests, due to a bug in the Net-SNMP library. If your dsc.snmpd process remains in the process list for over 30 minutes, it is likely experencing this issue.

If you expereience this issue on your install of SellaNMS, configure the 'discovery icmp prefix' section to include only specific IPs that are configured to properly respond to SNMPGET requests (The ICMP discovery module instructs the SNMP discovery module which hosts to poll). Optionally, try an older version of Net-SNMP.

You can find the host that is triggering the bug by setting 'threads 1' and 'trace-options [ debug internal ]' within the 'discovery snmp' section of your sella_nms.conf configuration file and re-running discovery. The last host to be logged for a SNMPGET request will be the host that is not configured properly for SNMP.

We will be implementing a fix for this bug in a post-2.0.0 release of SellaNMS. 


WebGUI w/PHP5
-------------
PHP 5.1 doesn't work out of the box with the SellaNMS WebGUI. Until a proper fix is available, enable PHP4 compatibility mode for PHP5 by setting 'zend.ze1_compatibility_mode = On' in your php.ini file and restarting Apache. The php.ini file usually exists in /usr/local/lib/ or /usr/lib/.


Major Bugs
----------

If a table is missing from the database, sella_nms will seg-fault. Believed to be a bug in libdbi. (Seg-fault in libdbi _disjoin_from_conn()).

If a SQL delete fails due to a corrupt table, sella_nms will seg-fault. Believed to be a bug in libdbi.


Minor Bugs
----------

Sub-policies don't get compiled and therefore fail, unless they are listed in a policy import/export statement within the main config. This forces them to be compiled and available for execution within the sub-policy execution call.

Interfaces with multiple IP's within the same netblock, build connections to themselves (eg: MILW-HAGG-01: ae0.996)

If autoconf is run on a RH6.2 box, the configure script fails to compile with STLPort with gcc 2.95.3. Workaround is to run autoconf on another box and just use the configure script on the RH6.2 box.
