A couple of thoughts on using WhatsupGold 7.0. We have two WUG servers, both running on dual-P4 933 Mhz / 1G RAM / 40G RAID array with Windows 2000 SP2. Each server is monitoring the same approximately 1000 devices - lots of SNMP polls, NT services, special services, etc. We use Perl script to stop the services remotely on 2nd server, copy all WUG and WUI files over to 2nd server and then restart service - essentially a replicator.
Here are some of the peculiarities I've run into.. 1. SNMP traps do not log in device history display (known bug) 2. SNMP traps that cause an SMTP alert to go out with %m in subject line cause WUG to crash with Dr. Watson 3. When going to Settings option from top page, clicking on Submit causes user to lose privileges to add/remove nodes or view map settings 4. Changes made to certain notifications do not stick when made from web interface, while changes made certain other notifications DO stick 5. Stopping the Windows Service for Whatsup often does not stop the process WhatsUpG.exe 6. Unable to add/delete Program Notifications from Recurring Notifications from web interface - security ? 7. ASP for classic / alternate - meta tag for refresh is missing quotes around the word REFRESH - causing screen refreshes to fail. 8. Redundancy - SMTP relay for notifications still cannot use DNS name, but must use explicit IP. This prevents Whatsup from running in a truly mission critical environment unless a availability-based VIP is made for mail servers -Jason ________________________________________ Jason Dennis FactSet Research Systems +1 203 863 1579 phone +1 203 863 5779 fax +1 203 249 2578 mobile [EMAIL PROTECTED] Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/whatsup_forum%40list.ipswitch.com/
