This article applies to BoKS Manager 6.7.0, 6.7.1 and 7.0.0.


If you have a BoKS domain, then install a second BoKS Master using the same ports and import the database from the domain or know the nodekeys for the hosts in the domain, then add the hosts to the second Master, that Master can communicate with the machines in the domain.

Resolution / Workaround

To resolve this issue, apply hotfix HFBM-0159 for BoKS 6.7 or HFBM-0160 for BoKS 7.0, available for download from the HelpSystems Community Portal.

To stop the second Master talking to the hosts in the domain, a new ENV variable has been added, BRIDGE_ACCEPT_MASTER_IPS. This can either be set to a space-separated list of IP addresses for hosts allowed to act as Master, or the string BCASTADDR. The value can be either a list of IP addresses or the keyword, not both.

If a list of IP addresses is used, it must include the actual Master and any Replica designated as a failover Master.

If the BCASTADDR keyword is used it implies that all IP addresses in the $BOKS_etc/bcastaddr file are allowed. In that case it is vital that the IP address(es) of the Master and any failover Master are present in the bcastaddr file on all hosts where the ENV variable is applied. (This includes the current Master in case it is converted to a Replica in a failover scenario).

This setting affects the clntd receive bridge on all BoKS hosts, and the servm receive bridge on Replicas. If BRIDGE_ACCEPT_MASTER_IPS is set and the bridge gets a connection from another IP address, it will write a warning to the boks_errlog file and ignore it.

If there is an error in the list of IP addresses in BRIDGE_ACCEPT_MASTER_IPS or in the bcastaddr file, or the file is missing and BRIDGE_ACCEPT_MASTER_IPS is set to BCASTADDR, the bridge will print a warning to the $BOKS_var/boks_errlog file and ignore the BRIDGE_ACCEPT_MASTER_IPS setting and will accept connections from any IP address.

Note, you must install the hotfix on your Replicas and BoKS Server Agents to be able to use this functionality.

Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: May 25, 2018