CCNA Operations And Monitoring Questions

Monitor > Network > [Device] > Control Connections is the exact vManage path showing live control connection state per device, including system IP, local colour, remote colour, and state. It satisfies the stem's requirement to check active control connections directly, unlike tunnel, interface, or alarm views that omit per-connection control-plane status.

The Monitor > Network > [Device] > Tunnel path opens the tunnel dashboard for the selected vEdge, showing real-time state, uptime, latency, loss and jitter per tunnel. Other Monitor submenus cover interfaces or control connections, not tunnel statistics.

The device-level Control Connections view shows every controller relationship for that router, including whether the DTLS or TLS session is up and which local TLOC and color carry it. This directly answers whether all control connections are established and encrypted for that single device, which is exactly what the engineer must verify.

In vManage, historical bandwidth utilisation for a site is produced under Monitor > Reports, which offers prebuilt report types including bandwidth and application usage. This satisfies the stem's requirement to generate a historical bandwidth report.

This command displays the BFD sessions on a Cisco IOS XE SD-WAN device, including the remote system IP, color, state, and the measured latency, loss, and jitter for each tunnel. It directly provides the per-tunnel BFD detail needed to diagnose why traffic is dropping on the specific tunnel.

The Network Health Dashboard aggregates fabric-wide telemetry into a single composite score covering control, data, and transport planes, giving the at-a-glance status the stem requests. It is the vManage component purpose-built for whole-fabric health rather than per-device or per-tunnel views.

Flow Analytics in vManage provides detailed visibility into individual flows, including the path taken, the application, and the reason for path selection. It shows the actual egress interface and the policy decision, enabling the administrator to see why the less desirable link was chosen. This directly answers the need to examine per-flow path selection.

The Tools > Reports section in vManage allows you to create custom reports based on historical data, including application bandwidth consumption. You can specify the time range (e.g., past week), the site, and the metric (e.g., top ten applications by bandwidth). This is the correct feature to generate the required report.

BFD on each tunnel combined with enhanced application-aware SLA classes continuously measures loss, latency, and jitter per transport. When a threshold is crossed, the tunnel is marked out of SLA and traffic is steered to a compliant path. This detects brownouts, not just hard failures, which is exactly what the requirement asks for on a per-transport basis.

This command displays the OMP route table on the vSmart controller, showing all routes received from vEdges and their attributes such as originator, VPN, and path. It directly confirms whether the branch's routes were received and propagated, making it the correct tool for verifying OMP route exchange in this scenario.

The Path Trace tool in vManage Real-Time Monitoring initiates a live, hop-by-hop probe from a selected WAN Edge router to a destination, displaying each device and interface along the path with latency and loss. This directly answers the team's need to identify where latency is introduced. It uses the SD-WAN fabric's native tracing capability and works across the overlay without requiring CLI access to each hop.

The Tunnel view under Monitor > Network > WAN Edge displays the status of all tunnels, including BFD session state, latency, jitter, and loss. This is exactly where the administrator can verify if BFD sessions are up and if performance metrics are within acceptable thresholds for voice. It provides per-tunnel granularity, allowing correlation of BFD health with voice quality issues. Other views do not offer this combined BFD and performance detail.

Lower preference ensures that traffic prefers other paths unless the DCI path is the only one remaining.

This dashboard correlates application traffic with the transport selected and whether each path met its SLA class across a chosen window. That directly produces the per-application, time-aligned evidence the auditor requires, showing the preferred transport was used and exactly when failover to the backup occurred, without relying on inference from unrelated counters.

Essential for daily monitoring of the fabric.

The `show control local-properties` command displays the WAN Edge's configured organization name, VBOND, and controller IPs. If these are incorrect or mismatched, the DTLS/TLS handshake will fail and control connections will remain in 'connect' state. This is the most direct first step to validate control plane configuration before deeper troubleshooting.

This real-time view for a selected WAN edge device lists the control connections to the vBond orchestrator, vSmart controllers, and vManage, including their state and system IP. It directly answers whether the device has established the expected control connections to all controller roles after onboarding.

The most direct next step is to inspect the application-aware routing policy statistics. These statistics show which path is selected for the traffic and the reason, such as which SLA class was met or if fallback occurred. This will reveal if the policy is matching the traffic correctly and if the better path is being considered. It provides actionable data to pinpoint the cause.

SoO tags are specifically designed to prevent loops in multi-homed BGP/OMP environments.

The Tunnel Health Dashboard reports per-tunnel metrics such as latency, jitter, packet loss, and state for each WAN link in the fabric. This satisfies the stem's requirement for the most detailed view of individual tunnel health.

The Real Time flows view under a WAN edge device in vManage shows active and recent flow information, including source, destination, and the path chosen by the fabric. This is the correct place to inspect the actual forwarding decision for the specific application flow and confirm whether the policy steered it as intended.

vManage records each template push as a Device Task containing the granular error returned by the device. Inspecting that log first reveals whether the failure is a CLI mismatch, connectivity issue or template variable error, avoiding guesswork before attempting any retry or rollback.

This command displays all active BFD sessions on the device, including the source and destination IP addresses, the negotiated hello and multiplier values, and the current state (up/down). In this scenario, it directly reveals whether the intervals match the vManage configuration and whether the sessions are actually flapping, making it the correct diagnostic step.

TLOC Preference is an OMP attribute advertised per TLOC; higher values win path selection for DCI traffic between data centres. It directly satisfies the stem's requirement by ranking transport locations before other tie-breakers such as cost or tag.

The Tunnels screen displays the status of data plane tunnels (such as IPsec) between vEdges, including whether they are up and the source/destination. Checking this screen confirms that the data plane is operational and that tunnels have been established after the upgrade.

For automatic failover, WAN Edge devices must know the IP addresses of all vSmart controllers in the domain. They are typically configured with the vBond address, which provides the list of vSmart controllers. The WAN Edge then establishes control connections to multiple vSmarts. If one fails, the WAN Edge can use the remaining connection, ensuring continuous control plane operation without manual intervention.

The App Route view displays the application-aware routing decisions for each flow, including the chosen path, the available paths, and the policy criteria that matched. It shows which SLA class or preference was applied and why a particular TLOC was selected. This is exactly the view needed to diagnose why broadband was not chosen despite the policy intent.

Peak-hour packet loss signals that demand exceeds the transport's committed capacity, forcing buffers to overflow and drop traffic. Because the loss correlates with the busiest period rather than occurring randomly, it directly evidences oversubscription of the WAN circuit.

WAN Edge routers maintain a local copy of OMP routes and policies received from vSmart. If the vSmart connection fails, they continue forwarding based on this cached information while attempting to establish a control connection to another vSmart controller. This ensures data plane continuity and is the correct description of the failover behavior.

Enabling SNMP traps for specific OIDs and configuring the trap receiver allows the WAN Edge device to send asynchronous notifications for events like BFD session state changes and control connection status. This complements syslog and provides another channel for proactive monitoring. The trap receiver must be configured with the correct community string and destination to receive these alerts. Without this, SNMP-based monitoring would miss critical events.

Alarm Notifications under Administration allows the engineer to configure alarm rules, including conditions such as control connection loss, and set thresholds and notification methods (email, SNMP trap, syslog). This directly meets the requirement to receive alerts when a WAN Edge device loses its vSmart connection for more than five minutes. It is the correct place to define and manage proactive alerts for fabric health.

The Tunnel monitoring view provides real-time and historical statistics for each tunnel, including latency, jitter, packet loss, and bandwidth utilization. This directly addresses the engineer's need to determine whether the slow SaaS access is caused by transport latency or packet loss. It is the correct view for per-tunnel performance verification.

BFD and data-plane tunnel state reflect the actual forwarding path between TLOCs. If OMP peerings are up but tunnels are down, the problem lives in the data plane, such as keys, ports, or reachability. This cleanly separates a tunnel failure from an OMP or policy issue, which is the isolation the engineer needs.

The Device Health Dashboard surfaces per-device reachability, control-plane status and resource utilisation, so failed or degraded edges are spotted immediately. This satisfies the daily operational health check by confirming every node in the SD-WAN fabric is up and functioning.

The command 'show control connections' on a vEdge displays the status of control plane connections to vSmart controllers, including whether they are up or down, the remote system IP, and the local/remote IP addresses. It directly helps diagnose why vManage might see the device as unreachable, as vManage relies on control plane connectivity.

The Tunnel Health dashboard in vManage displays BFD session status, latency, jitter, and packet loss for each tunnel. This directly indicates whether packet loss is occurring within the overlay tunnel. By comparing tunnel health across different tunnels, you can determine if the issue is specific to one tunnel or the underlay.

The Control Plane Health widget displays the status of control connections between vSmart controllers and WAN Edge devices. It is critical for daily health checks because it quickly identifies if any control plane disruptions could affect routing and policy enforcement. A healthy control plane ensures that OMP routes and policies are propagated correctly, which is foundational for SD-WAN operations.

When vManage pushes a configuration or policy change, the device must receive and apply it to reach the intended state. If the change is pending, rejected, or failed to apply, the device reports out of sync. Verifying whether a pending change has been applied is therefore a correct troubleshooting condition.

The Monitor > Applications section in vManage provides detailed application performance and path quality metrics, including latency, jitter, packet loss, and application-specific data. This is the correct location to monitor real-time application experience and path health for a site, as it aggregates data from the Application Aware Routing engine.

Correlating BFD session state changes with tunnel statistics timestamps identifies which tunnel and which path (e.g., a specific TLOC) is flapping. This narrows the issue to a particular transport or remote TLOC without changing configuration, which is the correct first step in an isolation workflow before applying any remediation.

The most likely cause is that the SLA class referenced in the application-aware routing policy does not match the intended criteria. For example, if the SLA class is configured with a higher latency threshold, the policy may select a path that meets that threshold but is not the lowest-latency path. The engineer should verify the SLA class configuration and ensure it aligns with the desired path selection criteria.

Monitor > Network > App Route in vManage shows real-time application-aware routing statistics, including per-application and per-path latency, loss, and jitter, as well as the selected path. This is the correct location to verify AAR behavior for a site.

The App Route statistics in vManage show the path selected for specific applications based on the application-aware routing policy. This directly verifies whether the voice traffic is taking the expected path and whether the SLA criteria are being met. It provides per-application path visibility, which is essential for troubleshooting policy effectiveness.

OMP session down is a control-plane alarm indicating that the Overlay Management Protocol session between a WAN Edge router and a controller (vSmart or vBond) has gone down. This directly affects control-plane connectivity and route exchange, making it a correct choice.

Equal TLOC preference and OMP cost make both DCI paths equally preferred, so the vEdge forwards flows across them rather than selecting one. Any difference in either metric causes deterministic path selection instead of load balancing.

A Soft Shutdown drains traffic and hands over the active role cleanly, so sessions and tunnels fail over without dropping. This satisfies the graceful-transition constraint in the stem, unlike a hard shutdown, which forces an abrupt failover.

The application-aware flow test records the full forwarding decision for the synthetic flow, including the local egress interface and the WAN transport chosen in each direction. Reading the flow details lets the team confirm the exact path the test took, which is essential before drawing conclusions about a production voice path that may use a different tunnel.