Centralized Policy Definitions applied to Site Groups allow for consistent, scalable configuration across many sites. This approach ensures all branch offices get the same policy set (like hub preference and local breakout rules) from a single definition, dramatically reducing manual configuration effort and ensuring consistency.

Application-Aware Routing (AAR) policies with SLAs based on jitter, latency, and packet loss are the Versa mechanism for making path selection decisions based on real-time application performance, not just link state. This allows voice traffic to automatically move to a better-performing path when SLA thresholds are breached.

The Versa Gateway (specifically configured as a Secure Access Gateway) is the public-facing endpoint. Users connect to it, authenticate (often via integration with an identity provider), and it brokers the secure tunnel to the private applications, enforcing the defined access policies.

The Versa CPE includes an integrated NGFW stack. By tunneling all branch traffic (both internet and private) to a hub site, you can centralize inspection and policy enforcement using this integrated functionality. This meets the security requirement without needing external firewall appliances, simplifying architecture and management.

The Path Quality and Application Flow analytics drill-down is designed for this exact task. It allows you to select a specific application, view the paths it’s using, and see the detailed performance metrics (latency, jitter, loss, throughput) for those paths over time, enabling rapid root-cause analysis.

For Zero-Touch Provisioning (ZTP), the device’s serial number must be registered in Versa Director along with an associated bootstrap configuration (which includes details like organization, site, and connectivity to Director). When the device powers on, it uses this serial number to phone home, authenticate, and pull down its full configuration automatically.

This is a classic use of floating static routes. The primary default route points to the internet next-hop with a default metric (e.g., 1). The backup default route points to the MPLS next-hop with a higher metric (e.g., 10). The route with the lowest metric is installed in the routing table, so the MPLS route only becomes active if the primary route is withdrawn (i.e., the interface goes down).

A key principle of Versa SPA is micro-segmentation through granular routing. The gateway injects only the precise routes (e.g., /32 host routes) for the resources a user or group is authorized to access into their specific routing instance or tunnel. If the route isn’t advertised, the user’s device has no path to reach it, providing a strong network-level enforcement of policy.

A Guaranteed Bandwidth Queue (also known as a Minimum Bandwidth Queue) reserves a specified amount of bandwidth for a specific class of traffic. This ensures the video conferencing traffic will always have at least 5 Mbps available, even during congestion, which is different from priority (which doesn’t reserve bandwidth) or shaping/policing (which limit bandwidth).

Centralized Policy Definitions applied to Site Groups allow for consistent, scalable configuration across many sites. This approach ensures all branch offices get the same policy set (like hub preference and local breakout rules) from a single definition, dramatically reducing manual configuration effort and ensuring consistency.0