Network zones enforce the connectivity order for OneAgents and ActiveGates. This page describes connectivity priority for OneAgents. For information about ActiveGates, see ActiveGate connectivity in network zones.
A network zone instructs OneAgent to communicate with ActiveGates from the same network zone. If that isn't possible, OneAgent tries to connect to another ActiveGate. To organize these fallback connections, all ActiveGates are sorted into priority groups:
- Group 1—ActiveGates from the same network zone.
- Group 2—ActiveGates from the alternative network zone.
- Group 3—ActiveGates from the default network zone.
- Group 4—All other ActiveGates.
In every group, ActiveGates are further prioritized depending on the type:
- Index 1—Environment ActiveGates
- Index 2—Cluster ActiveGates
- Index 3—Embedded ActiveGates
OneAgents are load-balanced to use an ActiveGate with the lowest possible index. That is, if several ActiveGates with the low index are available, OneAgents will try to switch between the available ActiveGates on a regular basis.
If the preferable ActiveGate is not available, OneAgent tries the next higher index, until a connection is established. In that case, OneAgent will regularly check in the background for availability of ActiveGates with a lower index.
Multi-environment ActiveGate can have only one zone that is valid across all connected environments.
For example, if three ActiveGates are available:
- Environment ActiveGate from the same network zone (index 1.1)
- Environment ActiveGate from an alternative network zone (index 2.1)
- Cluster ActiveGate from the same network zone (index 1.2)
the ActiveGate with the index 1.1 is used. If it becomes unavailable, the next choice is the ActiveGate with index 1.2. If OneAgent fails to connect to this one, the ActiveGate with index 2.1 is used.
OneAgents with no network zone configured (that includes all OneAgents from the Default network zone) work as if the network zone doesn't exist.
Such OneAgents try to connect to any ActiveGate in a random order and choose the first responding Environment ActiveGate. For load balancing, after a few minutes they try to switch to the next responding Environment ActiveGate.
Managed If no Environment ActiveGate can be reached, OneAgents connect to the first responding Cluster ActiveGate. For load balancing, after a few minutes they try to switch to the next responding Cluster ActiveGate. In that case, OneAgent traffic goes to the Managed cluster uncompressed.