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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Primary TabTable 2-7: Primary Tab FieldsField/ButtonController having primarycommunications with host:Method of communicationbetween host and controller:Controller attempts to connectto host every n secondsController declares connectionfailure after n failed attemptsDescriptionEnter the name of the controller from the cluster that you are designating as themaster. Double-click on this field to display a list of controllers from which you canmake a selection. If you select a controller that is not a cluster member, C•CURE<strong>800</strong>/<strong>800</strong>0 displays an error message telling you to choose another controller.NOTE: This field is unavailable if the cluster is online. See the note on page 2-37 forthe procedure to put the cluster offline.Specify the type of connection that the master uses to communicate with the host:• TCP/IP. The master communicates with the host using TCP/IP over an Ethernetnetwork.NOTE: This field is unavailable if the cluster is online. See the note on page 2-37 forthe procedure to put the cluster offline.Specify the number of seconds that the master waits between attempts to firstconnect to the host on the primary communications path. Use the Controllerdeclares connection failure afterXX failed attempts field to specify the number ofconnection attempts the master makes before a communications failure is declaredfor the primary communications path.Specify the number of attempts that the master makes to first connect to the hostbefore a communications failure is declared for the primary communications path. Ifa connection is established, the master and host use connection verificationmessages to maintain the connection. See the While connected, declareconnection failure if no message for XX seconds field in the Primary tab forinformation.If a connection is not made in the specified number of attempts, a communicationsfailure is declared for the primary communications path; the master sends a clusterinformation message to its cluster members telling them that the primarycommunications path is in communications failure, and the following activity isattempted simultaneously:• The cluster tries to establish a connection with the host on the secondarycommunications path.• The master attempts to re-connect to the host on the primary communicationspath at the rate specified in the After connection failure, controller attemptsto reconnect every XX seconds field in the Primary tab. The master tries toestablish a connection with the host forever or until a connection is established.• The master broadcasts a request across its subnet for the host’s IP Address. Ifthe iSTAR <strong>Configuration</strong> Utility is configured for auto-response, it responds tothe master. See the iSTAR eX Installation and <strong>Configuration</strong> <strong>Guide</strong> forinformation.2–40 C•CURE <strong>800</strong>/<strong>800</strong>0 <strong>Hardware</strong> <strong>Configuration</strong> <strong>Guide</strong>

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

Saved successfully!

Ooh no, something went wrong!