IBM Support

How do I ensure proper fail-over of Clients and Relays to my Secondary Disaster Server (DSA) Server in case of an outage on my Primary Server?

Technote (troubleshooting)


Problem(Abstract)

The following information describes setting up DSA for proper disaster fail over.

Cause

DSA Configuration

Environment

TEM DSA Servers

Resolving the problem

In order for the fail over process to successfully occur you must set the DSA Server as the Secondary Relay in client settings (manually using __RelayServer2) for the top-level Relays (or via the Console Computer right-click settings user interface). When a failure on the Primary TEM Server occurs and lower level Relays are unable to report they will use the Secondary relay value during normal relay selection process to find and report to the Secondary Server.

Note: The fail over process is not immediate and depends on the setting (_BESClient_RelaySelect_ResistFailureIntervalSeconds) set at 600 seconds (10 minutes) by default. A properly configured Relay architecture will allow the entire deployment to begin to fail over in about 600 seconds (10 minutes) by default. Deployments that do not have a Relay infrastructure setup can take significantly longer.

strong>Note: You may also want to adjust the setting for _BESClient_Register_IntervalSeconds:
Type: Numeric Version: 5.1
MinNumeric: 600 (10 mins)
MaxNumeric: 82800 (23 hours)
Default: 21600 (6 hours)
Requires Client Restart: NO
Description: Interval in seconds between successful client registrations. At the end of that interval, the agent will attempt to register, which requires successfully communicating with the root server. If that fails, the agent will perform a relay selection.

Please see the following guide to setting up Disaster Server Architecture (DSA)
here:

Please see the following client settings guide:
http://www-01.ibm.com/support/docview.wss?uid=swg21506050

Historical Number

1814

Document information

More support for: IBM BigFix family

Software version: All Versions

Operating system(s): Platform Independent

Reference #: 1506249

Modified date: 29 June 2012


Translate this page: