A Versa Analytics reporting view provides the capability to send reports by email, generate reports periodically, and create custom reports. This means administrators can set up automated report generation to be received at specific intervals, providing insights into the network's performance and security posture. These reports can be tailored to specific needs through custom report creation, ensuring relevant data is highlighted and presented as required.

The diagram in the exhibit illustrates a hub and spoke topology where the spokes connect through a central hub. This is evident from the dashed lines that show the data flow between the spokes is mediated by the hub (Hub1). In this topology, while the spokes may have direct connections, the data flows between them pass through the hub. This kind of topology is commonly used in SD-WAN deployments to simplify routing and policy enforcement, which are managed centrally at the hub, as opposed to setting up direct paths between all spoke sites, which would be indicative of a full mesh or spoke-to-spoke direct topology.
Top of Form

In SD-WAN policy rules, two parts used to steer traffic are Schedules and Applications. Schedules allow administrators to define when certain policy rules should be active, effectively determining the timing for when traffic steering decisions should be applied. Applications, on the other hand, enable traffic steering decisions based on the type of application traffic being detected. This allows for more granular control and optimization of traffic flows based on application requirements and characteristics.

To configure an SD-WAN branch so that Internet-bound traffic uses the local Internet link, the Service Chain Template is used. This template is part of the Director Workflows and allows the local breakout of internet traffic directly from the branch, bypassing the central or regional breakout points. This is an essential component of the Versa Secure SD-WAN design, where traffic intended for the internet can be directed through the most efficient route, often through a local Internet link at the branch site, instead of being backhauled to a central location.

The SLA profile shown in the exhibit appears to be set with thresholds for various metrics such as jitter, packet loss, and latency. These thresholds determine the acceptable performance criteria for the network. The profile is configured with specific maximums for packet loss, both in the forward and reverse directions, and for latency. If any of these configured values are exceeded, the SLA profile is triggered, indicating a breach of the desired service level agreement parameters. Therefore, if the packet loss value exceeds the maximum set in the profile, it will trigger an event or alert, which can then be used for remediation or for activating pre-defined traffic steering rules to maintain application performance.