Depending on the size, complexity, and hardware of your cluster the defaults for monitoring may be too aggressive. Below are several common steps you can implement to reduce the aggressiveness of the monitoring if you are experiencing issues. Option 1: Enable fuzzyoffset on the monitoring objects. If you are seeing…
This article applies to Bright 8.2 and later releases If another authentication mechanism is to be used, SSSD for example, NSLCD will need to be disabled within Bright. In Bright 8.2 and later releases, the nslcd service is inherited by a special in-built role, which isn’t exposed in BrightView or…
In terms of the LDAP parameters, the cmd.conf file contains some of the required values that cmdaemon uses to bind with the Bright provided LDAP. You can review the values with this command. [root@headnode ~]# grep LDAP /cm/local/apps/cmd/etc/cmd.conf The bind dn you could use is : cn=readonlyroot,dc=cm,dc=cluster Below is an example…
NOTE: Shorewall provides a NAT Masquerade rule that allows the compute nodes to access networks that are outside the cluster via the head node. If you are okay with the compute nodes not having access to external networks or aren’t using the head node as the default gateway for the…
This article assumes that HA is setup and configured properly, and that one of the nodes has completely died and is being replaced with new hardware. Bright’s license is tied to the MAC addresses of both headnodes. First unlock the product key via the support portal http://customer.brightcomputing.com (left hand menu)…
The following procedure was tested on Bright 9.1 on CentOS 7.9. WARNING: Please note that an update of certain Bright packages can remove some of the changes that were done manually here. If the packages node-installer or node-installer-nfsroot are updated/reinstalled on the head node, then step 7 of this article…