VNX100 Questions and Answers

Versa Director acts as an orchestrator within the Versa SD-WAN ecosystem, providing centralized configuration management and monitoring of controllers, branch sites, and hubsites. It does not function as a log forwarder, BGP route reflector, or VPN concentrator. As an orchestrator, it manages the lifecycle of Versa VOS instances, enabling zero-touch provisioning and other orchestration functionalities through a single pane of glass.

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.

To monitor a Versa CPE interface's live data, you would use the Versa Director. The Versa Director provides a comprehensive interface for real-time monitoring and management of SD-WAN infrastructure, including the visualization of traffic flows and performance metrics. Through Versa Director, network operators can gain insights into transmission data for all traffic or SD-WAN-specific traffic, updated every few seconds, and detailed information about interface statistics​​.

By default, when configuring Direct Internet Access (DIA) through workflows, the protocol that runs between the tenant virtual router (VRF) and the transport WAN Virtual Router (VR), connected by the TVI interfaces, is EBGP (External Border Gateway Protocol). This protocol is used to control route distribution and is a fundamental part of the VOS Edge Device DIA Architecture. In such a configuration, the tenant VRF uses EBGP to advertise the default route, which is resolved using the logical tunnel created for DIA​​.

To identify and diagnose intermittent network performance issues that occurred in the past,Versa Analytics dashboards (Answer B)are the most suitable component. Versa Analytics provides deep insights into historical data, enabling network administrators to analyze trends, performance metrics, and potential bottlenecks that occurred previously. The dashboards offer a comprehensive view of the network's operational performance over time, allowing for effective troubleshooting of issues that are not currently manifesting but did impact users in the past.

References:Versa Analytics dashboards are specifically designed to handle retrospective and real-time network data analysis, making them an essential tool for diagnosing past issues as described in Versa's official documentation on network analytics and performance monitoring.

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 a scenario where a device is onboarded with two Internet interfaces and Direct Internet Access (DIA) is being configured, the following statements hold true:

• Each underlay interface belongs to its own VR instance (Answer B): Typically, in Versa SD-WAN configurations, each underlay interface is assigned to its own virtual router (VR) instance. This approach allows for greater flexibility and isolation in managing routing and security policies specific to each interface. It supports independent operation and control, which is crucial for optimizing performance and security management.
• Both Internet interfaces can be selected for DIA in workflows (Answer C): In Versa workflows, it is possible to configure both Internet interfaces for DIA. This configuration enhances redundancy and ensures that there is always an active path for Internet access, which is critical for maintaining high availability and network resilience.

The option A (All underlay interfaces belong to the same VR instance) is not typically true in complex deployments where separation of control and data planes is required for better management and security. Option D (Only one Internet interface can be selected for DIA in workflows) is incorrect because Versa SD-WAN allows multiple interfaces to be configured for DIA to leverage failover and load-balancing capabilities.

References:This explanation is based on the standard practices of deploying Versa SD-WAN solutions, where the architecture supports multiple virtual routers and the capability to configure multiple interfaces for DIA.

When a Versa CPE security policy rule is configured to generate and send logging information on policy hits using the Default Logging Profile, Versa Analytics is the component that would allow you to view these logs. Versa Analytics provides extensive visibility into network traffic and security events, which includes logging information from security policies in action.​

Versa Analytics offers REST APIs that facilitate northbound integration with third-party tools, allowing for enhanced automation and the ability to pull data into external systems for additional processing or visualization. Moreover, it provides real-time traffic monitoringdashboards that deliver visibility into network performance, application usage, and security events, aiding in swift and informed decision-making. These dashboards are crucial for maintaining an overview of the network's current state and rapidly diagnosing issues.​

Versa Analytics offers a suite of features aimed at enhancing visibility and control over SD-WAN networks. The true statements about Versa Analytics are:

• Versa Analytics provides REST APIs for northbound integration with third-party tools (Answer B): Versa Analytics is equipped with REST APIs that facilitate northbound integration, allowing organizations to seamlessly connect and integrate Versa's network data with third-party management, monitoring, and analytics tools. This integration capability is crucial for enterprises that utilize a diverse set of tools for network management and need to consolidate their network operations on a single platform.
• Versa Analytics provides real-time traffic monitoring dashboards (Answer D): One of the key features of Versa Analytics is its real-time traffic monitoring dashboards. These dashboards provide network administrators with live insights into network performance, traffic flows, and usage patterns, enabling them to make informed decisions quickly and effectively manage the network.

Option A (Versa Analytics provides the ability to configure logging parameters on SD-WAN CPEs) is incorrect because while Versa Analytics does involve extensive logging capabilities, the configuration of logging parameters typically occurs at the device or controller level, not within the analytics platform itself. Option C (Versa Analytics provides centralized logging information about the SD-WAN environment) is somewhat misleading; while Versa Analytics does centralize data for analysis, it primarily focuses on providing analytical insights and data visualizations rather than merely centralizing logging information.

References:This explanation is based on the functionalities provided by Versa Analytics as part of the Versa SD-WAN solution, emphasizing its capabilities in network data integration and real-time monitoring.

Service templates are used to apply an identical QoS configuration to multiple CPEs, ensuring consistent quality of service across the network. Additionally, these templates are also employed to share an identical service configuration across different tenants within a multi-tenant architecture, ensuring uniform policy application while maintaining tenant separation.

The provisioning of Versa SD-WAN CPE devices can be accomplished through multiple methods, including:

• URL-based provisioning (Answer B): This method involves directing the CPE to a URL where it can download configuration files automatically. This is an efficient way to provision devices remotely and is widely used for initial device setup and configuration.
• Script-based provisioning (Answer C): This method allows network administrators to use scripts to automate the configuration process of CPEs. Scripts can be customized to apply specific configurations and policies based on the deployment requirements.

References:Both URL-based and script-based provisioning are standard practices detailed in Versa's deployment guides, which provide step-by-step instructions on using these methods for efficient and scalable CPE deployments.

The policy shown in the exhibit appears to match traffic flows based on multiple conditions involving the source zone and the application. Given the information in the screenshot:

• The policy is configured with multiple zones as source zones:Intf-LAN1-ZoneandIntf-WLAN-Zone.
• An application is specified:SHAREPOINT.

The policy is likely to be applied to traffic originating from either of the specified zones and specifically related to the SharePoint application. This implies that both conditions related to the source zones are not mutually exclusive but rather a union; the same goes for the application condition.

Given this interpretation, the correct set of conditions that match the policy shown would be:

B.Traffic flows that meet any of the following two conditions:

• Source Zone - Intf-LAN1 Zone
• Source Zone - Intf-WLAN-Zone

In addition, the below condition must also match:

• Application - SharePoint

This means that traffic will match the policy if it comes from either theIntf-LAN1-Zoneor theIntf-WLAN-Zoneandis SharePoint application traffic.

However, to be more precise in the context of Versa SD-WAN configurations, it's important to note that policies are usually applied when all conditions within a single rule are met. If the configuration in the screenshot intends to express that traffic is matched if it comes from either of the two zones and is for the SharePoint application, then the correct answer should reflect this logic. If the configuration system is set up to require all conditions in a rule to be met, then the answer could potentially be different. Since the user interface design can sometimes vary, it’s important to understand the specific logic of the system in question.

When a CPE device appears in the unknown device list in Versa Director Inventory during Zero Touch Provisioning (ZTP), it typically indicates a discrepancy in device identification details. Specifically,the device workflow configuration not having the correct serial number of the CPE defined (Answer C)can lead to this issue. The workflow configuration must accurately include the serial number so that Versa Director can recognize and authenticate the device as part of the organization’s network infrastructure. If the serial number in the workflow configuration does not match the serial number of the actual device, the Director will not be able to properly identify and classify the device, thus placing it in the unknown device list.

References:Versa’s official documentation on ZTP outlines the importance of accurate device identifiers in the workflow configuration to ensure successful device onboarding and recognition by the Versa Director.