<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd" MadCap:tocPath="" MadCap:InPreviewMode="false" MadCap:PreloadImages="false" MadCap:RuntimeFileType="Topic" MadCap:TargetType="WebHelp" lang="en-US" xml:lang="en-US" MadCap:PathToHelpSystem="../" MadCap:HelpSystemFileName="Default.xml" MadCap:SearchType="Stem">
    <head>
        <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><title>The Redundant License Manager Leader</title>
        <link href="Resources/Stylesheets/SFNT_Flare.css" rel="stylesheet" />
        <script src="SkinSupport/MadCapAll.js" type="text/javascript">
        </script>
    </head>
    <body>
        <p class="MCWebHelpFramesetLink MCWebHelpFramesetLinkTop" style="display: none;"><a href="../Default_CSH.htm#The_Redundant_License_Manager_Leader.htm" style="font-weight: bold;">Open the Table of Contents</a>
        </p>
        <h2><a name="kanchor127"></a>The Redundant License Manager Leader</h2>
        <p><a name="kanchor128"></a>One of the License Managers in the pool is designated as the leader—the 
 remainder of the License Managers are known as the followers. The leader 
 is the operating server with the highest preference set in the lservrlf 
 file. The licenses tokens always remain with the leader server and are 
 not distributed among other servers in the pool. </p>
        <h3 class="SpacedHead"><span style="font-weight: bold;">Tip:</span> <![CDATA[ ]]></h3>
        <p class="SpacedPara">Because the 
 leader must communicate with all other redundant License Managers, the 
 leader should be in an area of the network with good bandwidth.</p>
        <p style="font-weight: normal;">The leader synchronizes communication between 
 the License Managers in the pool. The leader also makes sure that all the 
 License Managers in the pool are using the same version of the redundant 
 license file. If this file is changed on one of the License Manager computers, 
 after one of the License Managers is stopped and restarted, the leader 
 detects the change in the file and automatically updates the rest of the 
 License Manager computers to the newer version.</p>
        <p style="font-weight: bold;">What if the Leader Goes Down?</p>
        <p>When the leader server goes down then the next follower server (in preference 
 order) becomes the leader of the pool. And all the tokens move to new 
 leader server. However, when the original leader comes up again, it reclaims 
 the leadership from the current leader. </p>
        <p style="font-weight: bold;">When a License on the Leader Server Expires</p>
        <p>When a license on the leader server expires (the end date is reached):</p>
        <p>The new license requests will fail and the LS_LICENSE_EXPIRED error 
 will be returned. </p>
        <p>The license update requests will be moved to the next (follower) server, 
 however, the LS_INSUFFICIENTUNITS error will be returned. This is because 
 the next server will have zero available tokens. </p>
        <p>&#160;</p>
        <script type="text/javascript" src="SkinSupport/MadCapBodyEnd.js">
        </script>
    </body>
</html>