The Talari controller provides centralized intelligence for the entire SD-WAN. Within the Talari SD-WAN, any Talari appliance can be designated as the Controller, and is referred to as the Network Control Node (NCN). The appliance designated as the Controller can be located in a data center, co-location facility or cloud, with sufficient bandwidth and connectivity to establish a connection with each Talari appliance in the network.
The Controller can be setup as a high-availability pair, with active-standby appliances. A second appliance, or high-availability pair, in a geographically separate location can also be designated as a backup Controller that will take over if a complete failure of the primary NCN pair occurs. The appliance form factor at the geo-redundant locations does not have to be the same. For example, a cloud Controller can be backed up with an on premises Controller.
These levels of redundancy ensure the Controller function is highly available. Even with these measures, it is possible to experience periods where the Controller is not accessible. However, the Talari SD-WAN is designed to continue to function, even when the NCN is temporarily unavailable.
- Can be a physical or virtual appliance. All Talari appliances, with the exception of the E50, can be designated as the controller
- Can reside in the cloud, co-lo, or on premises
- Can be installed on a client appliance, or stand-alone
Centralized Policy Functions
Policies that control the behavior of the Talari SD-WAN are defined within a single, centralized location. The NCN is responsible for centrally storing the application and traffic handling policies, and pushing changes to the client appliances.
- Learns topology and pushes to client appliances
- Synchronizes time between appliances
- Arbitrates bandwidth reservation
- Establishes dynamic connections
- Synchronizes one-touch push of OS upgrades