10.07.2015 Views

C•CURE 800/8000 Hardware Configuration Guide - Tyco Security ...

C•CURE 800/8000 Hardware Configuration Guide - Tyco Security ...

C•CURE 800/8000 Hardware Configuration Guide - Tyco Security ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Misc TabTable 2-10: Misc Tab FieldsFieldController automaticallyperforms test every n hoursWhen test fails, controller willrepeat test every (hh:mm:ss)Controller activates this eventwhen secondary test failsMaximum number ofunacknowledged messages foreach controllerDescriptionSpecify the number of hours that the controller responsible for secondarycommunications waits between test messages. The controller sends thesemessages to the host via the secondary communications path to let the host knowthat the secondary communications path will operate correctly if a failure occurs onthe primary communications path.Specify the time that the controller waits between attempts to retest the secondarycommunications path. The controller retests the secondary communications pathwhen the first test fails.Enter the event that the controller activates when the test of the secondarycommunications path fails. You can double-click on the field to display a list ofevents.Specify an event that is located on the controller responsible for the secondarycommunications path. If the event is located on another controller, the systemdisplays an error message.Specify the maximum number of unacknowledged messages that are allowed foreach controller in the cluster.If you have a network with high latency, you may want to set this value to a highernumber; if the network has low latency, the default value (10) should be sufficient.C•CURE <strong>800</strong>/<strong>800</strong>0 <strong>Hardware</strong> <strong>Configuration</strong> <strong>Guide</strong> 2–51

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!