Configuring IBM BigFix DSA

adityowicaksono · March 6, 2017, 9:32am

Hi there,

I planned to configure DSA on my environment, but I have one query about the DSA configuration. Since the installation must use the same installer from primary server, and also using the same masthead, so the hostname for DSA server must be same with my primary server? Is it possible to use the same hostname in same domain controller?

vikki · March 6, 2017, 9:42am

No need to be same, In my environment details like below,

Root Server : IBM Primay
DSA Server : IBM Secondary

I just mentioned replicate DB while while installing DSA server that’s all.

Thanks & Regards
Vicky

adityowicaksono · March 6, 2017, 10:41am

Hi Vikki,

So if we use the different name, how can we install the secondary server using the same masthead? As far as I know when we install the server using same masthead we need to enter the same previous hostname. And how can the client report to DSA server if the hostname is different?

vikki · March 6, 2017, 12:36pm

Dear @adityowicaksono

Name does not a matter, You just use the masthead file for config the DSA server, it will work fine and in case your root server is failure all the clients are redirected to your DSA server by default.

The below link provide you the brief info about DSA,

https://www.ibm.com/support/knowledgecenter/SS63NW_9.1.0/com.ibm.tem.doc_9.1/Platform/Adm/c_installing_additional_servers_.html

Thanks & Regards
Vicky

vnovik · March 6, 2017, 9:18pm

During the install of a secondary DSA Server (using the same masthead), you will be asked about a primary Server’s database location. After install is finished, the Relays.dat file, which contains information used in the IBM BigFix relay selection algorithm, will be updated in the actionsite of the deployment (by default it’s Windows location is: C:\BigFix Enterprise\BES Client__BESData\actionsite). That way every Client knows about all the available Servers and Relays.
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 IBM BigFix 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.

For more details: