Sites

Prev Next

A Site groups related aspects of appliance behavior, primarily for Gateways. Sites are also used with LogForwarders, Metrics Aggregators, and Connectors.

A default Site configured with entitlement-based routing (EBR) is included in every new Collective. When setting up a new Collective, you can edit this default Site. To start, add a DNS resolver and leave all other settings at their defaults.

Sites support the following use cases:

  1. Gateway grouping. A Site groups Gateways together so they share the work of provisioning access to protected hosts in a subnet, geographical location, or business unit.

  2. Log forwarding. The LogForwarder uses Sites to consolidate log records from one or more Sites and forward them.

  3. Metrics aggregation. The Metrics Aggregator uses Sites to aggregate metrics from one or more Sites for subsequent collection.

  4. Connector HA upgrades. sdpctl uses Sites to identify which Connectors operate as a high availability (HA) pair and upgrades them one at a time.

  5. Express Connector placement. The Express Connector must belong to a Site, which defines the source of its down traffic from users.

The primary use case is Gateway grouping. The Site provides the link between entitlements and the Gateways in front of the protected hosts. This link determines how client routing is configured:

  • Directly, when using site-based routing (SBR)

  • Indirectly, when using entitlement-based routing (EBR)

For Sites that contain Gateways, the Site health is also displayed, which reflects the health of the underlying Gateways.

See the following section to learn how to configure a Site.