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.

Cluster TabTable 2-9: Cluster Tab Fields, continuedFieldWhile connected, declareconnection failure if nomessage for n secondsDescription• Specify the number of seconds that a controller and the master wait forconnection verification messages before the controller is declared to be incommunications failure. The master and the controller send these messages toeach other during periods of low system activity to confirm that the path betweenthem is operating correctly.• The sum of this value and the value you entered in the While connected,declare connection failure if no message field in the Primary tab must beless than or equal to 85. If you entered 40 seconds in the Primary tab, you canenter a value between 1 and 45 seconds here; if you specified 80 seconds in thePrimary tab, you can enter a value between 1 and 5 seconds here.• The value you specify in this field determines how often the connectionverification message is sent between the master and controllers — if you specify40 seconds, the message is sent every 10 seconds — if you specify 5 seconds,the message is sent every 1.25 seconds.• For example, if you specify 40 seconds in this field, controllers receiveconnection verification messages every 10 seconds during periods of lowsystem activity. If a controller does not receive at least one message within 40seconds, the controller is declared to be in communications failure.• If a communications failure occurs, the following connections are attemptedsimultaneously:• If the secondary communications path uses an alternate master, the controllerattempts to connect to the alternate master, which passes the controller’smessages to the host. At the same time, the controller tries to re-establish aconnection with the master at the rate specified in the After connection failure,controller attempts to reconnect every XX seconds field in the Cluster tab.• If the secondary communications path does not use an alternate master, thecontroller attempts to re-connect to the master forever or until a connection isestablished. The controller attempts to connect to the master at the ratespecified in the After connection failure, controller attempts to reconnectevery XX seconds field in the Cluster tab.• The controller broadcasts a request across its subnet for the master’s IPAddress. The master responds to the request. If the master does not respond ina set amount of time and the iSTAR <strong>Configuration</strong> Utility is configured for autoresponse,the utility can respond to the controller. See the iSTAR eX Installationand <strong>Configuration</strong> <strong>Guide</strong> for information.C•CURE <strong>800</strong>/<strong>800</strong>0 <strong>Hardware</strong> <strong>Configuration</strong> <strong>Guide</strong> 2–49

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

Saved successfully!

Ooh no, something went wrong!