| ||||||||||||||||||||||||||||
|
Network Monitoring with Trap Ringer 3.5 MIB Browser's Trap Ringer is an integral part of that product and cannot be replaced by the full-featured Trap Ringer product. However, MIB Browser and Trap Ringer products can be used simultaneously (i.e., MIB Browser does not prevent Trap Ringer from receiving traps). Unfortunately, Net Inspector 1.5 cannot receive traps at the same time as MIB Browser or Trap Ringer. These applications can be used concurrently if Net Inspector is invoked last, but then Net Inspector will not receive any traps. This conflict will be corrected in Net Inspector 2.0. If we had our druthers, we would replace both Net Inspector and MIB Browser trap handlers with Trap Ringer's filters and a common event manager. Reporting These Mail and Web Messengers uses common vectors to meet two different needs: Urgent reports notify the administrator about events in near real-time, while periodic reports track events over time, in summary or detail. For example, we sent mail for critical events, but recorded critical and warning events in an HTML report, refreshed daily. At first, multi-level settings led us to overwrite reports; each critical event replaced the previous "urgent" HTML report. Once we got the hang of it, Messengers proved quite useful. Net Inspector also lets you know when it sends mailand when it cannot reach the mail server. This is important to spot lost notifications (i.e., did anything important happen yesterday that I didn't hear about?) During our evaluation, MG-SOFT's support crew responded to most problems within a daybut we also experienced several unexplained access violation faults during user/GUI interaction. One worrisome side effect: We lost a few events when the application to fault was Net Inspector.
|
|
||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||