Configure the Traffic Nodes in an Atlas Cluster

For each traffic node that you want to have in your Bomgar cluster, perform the following steps on the primary master node:

Management > Cluster
Atlas Cluster Primary Node Management Page

  1. Go to /login > Management > Cluster.
  2. Look at the Cluster :: Traffic Nodes section.
  3. Click Add New Traffic Node.

 

Atlas Add New Traffic Node Section

  1. Enter the following information on the Cluster :: Add Traffic Node page:
    • Name: Enter a name that you will use to remember this node in the cluster. This name must be unique among all nodes in the cluster.
    • Public Address:
      1. Enter the node hostname that you set up in DNS for this node. (See Prerequisites to Set Up Multiple Appliances in Atlas Clusters.)
      2. Enter the port over which clients will communicate with the node.
    • Internal Address: This can be the same as the public address. Advanced configurations can optionally set this to a different hostname for inter-appliance communication. (See Optional Considerations when Setting Up Multiple Appliances in Atlas Clusters.)
    • Accepting New Client Connections: Be sure this is checked; otherwise, clients will not use the traffic node.
    • Network Address Prefixes: When this field is populated, the master node attempts to assign a client to this traffic node if the client's IP address matches one of the network address prefixes. If the client's IP address matches more than one traffic node's network address prefixes, the client is assigned to the traffic node with the longest matching prefix. If the matching prefixes are of equal length, one of the matching traffic nodes is chosen at random. If a client's IP address does not match any network address prefixes, the client is assigned using the method configured on the main Cluster page (see Methods for Choosing Traffic Nodes in an Atlas Cluster).

      Enter network address prefixes, one per line, in the form of ip.add.re.ss[/netmask]. Netmask is optional and can be given in either dotted-decimal format or as an integer bitmask. If netmask is omitted, as single IP address is assumed.

      You may leave this field blank.

    • Timezone Offset: This is used only if the method for choosing traffic nodes is set to Timezone Offset. This process involves detecting the time zone setting of the machine hosting the client and using that setting to match the appropriate traffic node which has the closest time zone offset. The time zone offset is derived from the customer time zone setting relative to Coordinated Universal Time (UTC).
  2. Click Add Traffic Node.