Prevent LSF from dispatching jobs to problematic hosts consistently

Some jobs are dispatched to a host and failed because the communication between MBATCHD and SBATCHD is failed. The host keeps in OK status and the jobs keep dispatching to the host, which makes the job can not run for a long time. The communication issue between MBATCHD and SBATCHD could be triggered by the following reasons:
1. The SBATCHD is busy and it can not process the requests from MBATCHD timely.
2. The network problem which makes the communication from MBATCHD to SBATCHD failed.
The issue has been occurred for several times in our different sites. Since the issue can not be found timely, the end user is not satisfied with the service provided by LSF. So we need an alarm mechanism to report the issue to LSF admin and close the problematic host automatically.
Currently, we know there is a feature in LSF to detect the host exceptions which is attached below. However, the feature can not cover this case because the jobs can not be dispatched to the problematic host and no exit code for the jobs. So please enhance the feature to cover the case that jobs are dispatched failed due to the communication issues. Or create a new feature to resolve this issue separately.

Host exceptions LSF can detect
==============================
If you configure host exception handling, LSF can detect jobs that exit repeatedly on a host. The host can still be available to accept jobs, but some other problem prevents the jobs from running. Typically jobs dispatched to such “black hole”, or “job-eating” hosts exit abnormally. By default, LSF monitors the job exit rate for hosts, and closes the host if the rate exceeds a threshold you configure (EXIT_RATE in lsb.hosts).
If EXIT_RATE is not specified for the host, LSF invokes eadmin if the job exit rate for a host remains above the configured threshold for longer than 5 minutes. Use JOB_EXIT_RATE_DURATION in lsb.params to change how frequently LSF checks the job exit rate.
Use GLOBAL_EXIT_RATE in lsb.params to set a cluster-wide threshold in minutes for exited jobs. If EXIT_RATE is not specified for the host in lsb.hosts, GLOBAL_EXIT_RATE defines a default exit rate for all hosts in the cluster. Host-level EXIT_RATE overrides the GLOBAL_EXIT_RATE value.