If Security Monitor has been upgraded to 2.0 or 2.0.1 and a circular path has accidentally been configured between Security Monitor hosts, the system resources may become overwhelmed with updating the database with duplicate events. The system or database could become unuseable if the configuration is left uncorrected.
With Security Monitor 2.0 or 2.0.1, if a circular path is configured between Security Monitor hosts, a single event can be forwarded along the path and stored in each host's database many times. As a result, much of the system resources can become involved with receiving and sending this single event, and the database will be filled with copies of this single event.
