300-415 · Question #135
Refer to the exhibit. vManage logs are available for the past few months. A device name change deployed mistakenly at a critical site. How is the device name change tracked by operation and design…
The correct answer is D. Filter by Severity: Major, Component: Events, System IP: vEdge Cloud (10.4.4.4), Event name: control-connection-tloc-ip-change. To track a device name change in vManage logs, operations and design teams should filter for events with a 'Major' severity, specifically looking under the 'Events' component for the affected system IP and relevant event name.
Question
Options
- AFilter by Severity: Major, Component: Control, System IP: vEdge Cloud (10.4.4.4), Event name: control-connection-tloc-ip-change
- BFilter by Severity: Major, Component: System, Filter By: Major, System IP: vEdge Cloud (10.4.4.4), Event name: control-connection-tloc-ip-change
- CFilter by Severity: Major, Component: Software, System IP: vEdge Cloud (10.4.4.4), Event name: control-connection-tloc-ip-change
- DFilter by Severity: Major, Component: Events, System IP: vEdge Cloud (10.4.4.4), Event name: control-connection-tloc-ip-change
How the community answered
(54 responses)- A4% (2)
- B9% (5)
- C15% (8)
- D72% (39)
Why each option
To track a device name change in vManage logs, operations and design teams should filter for events with a 'Major' severity, specifically looking under the 'Events' component for the affected system IP and relevant event name.
While a device name change can affect control plane elements, 'Component: Control' is less precise for a configuration change event than 'Component: Events'.
'Filter By: Major' is redundant if 'Severity: Major' is already specified, and 'Component: System' is too broad compared to 'Component: Events' for tracking configuration changes.
'Component: Software' typically relates to software image management or software-related issues, not direct configuration changes like a device name change.
In Cisco vManage, configuration changes and operational events are logged under the 'Monitor' > 'Events' section. A device name change would typically trigger an event with a 'Major' severity and be categorized under the 'Events' component, allowing specific tracking by System IP and event name, such as 'control-connection-tloc-ip-change' if it impacts control plane connectivity due to a system IP (part of identity) change.
Concept tested: vManage event logging and monitoring
Source: https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/sdwan-xe-gs-book/m-sdwan-monitor.html#concept_v3b_pgd_r4b
Topics
Community Discussion
No community discussion yet for this question.