Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[SBR] How does the LDAP/SQL server target number determine when to activate the specified server?

0

0

Article ID: KB27024 KB Last Updated: 08 Mar 2017Version: 3.0
Summary:
This article provides information on how the target number is determined, when multiple server instances are configured in the LDAP and SQL authentication files.

Note: This is only for the JDBC type of SQL connection, as the Oracle Client controls the number of connections and the activation of each connection.
Symptoms:
The Target number that is associated with a server in the configuration file determines when it is activated; but certain servers are required to always be on and other servers have to activated, only when a failure occurs. How does this function and what is the proper configuration?
Cause:
 
Solution:
The Target number sets the activation priority of the server. SBR will read the [Server] section from the top down and activate each server with an activation number that is greater than the number of active server connections. In the following example, four servers have been configured:
[Server]
s1=1
s2=1
s3=2
s4=2
When SBR is started and the .aut file is activated, SBR will read the [Server] section and see that s1=1. As no servers are connected and s1 has an target number of 1, then 1 is greater than 0; so SBR will connect to this server. Moving down the list, s2 is equal to 1 and SBR currently has 1 server connection; so, as 1=1, SBR will not activate this server.

Continuing down the list, server s3 is equal to 2 and SBR currently has 1 active connection to the s1 server. As 2 is greater than 1, SBR will connect to this server. Finally, s4=2 and 2=2; so this server connection will not be activated.

When SBR is started, the connections will look like this:
[Server]
s1=1 ------> connected
s2=1 ------x not connected
s3=2 ------> connected
s4=2 ------x not connected
Now, if the s1 server fails, SBR will again use the activation number to determine which server has to be activated. The result will be as follows:
[Server]
s1=1 ------x failed
s2=1 ------x not connected (Target number is not greater than the number of active connections)
s3=2 ------> Connected
s4=2 ------> Connected (Target number 2 is greater than the number of active connections after the failure)
At this point, the only time the s2 server will be connected is when the s1 server fails to load at startup or all of the other servers fail; making it a last resort server.
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search