Comprehensive and Detailed Explanation with Exact Extracts:
Exhibit Analysis:
The output shows real-time ICMP packet captures (echo requests/replies) with detailed metadata (interface, source/destination IP, protocol, size, TTL).
The command tools system traffic-monitor protocol icmp confirms this is a tcpdump-like utility (packet capture tool), not a log file.
Mechanism for Packet Capture:
Capture-filter ACL is required to copy data-plane packets (like ICMP between hosts) to the CPM for analysis by traffic-monitor.
Extract from Nokia SR Linux Troubleshooting Guide:
"traffic-monitor is a CPM-based packet capture tool. To capture data-plane traffic (e.g., host-to-host ICMP), a capture-filter ACL must be applied to interfaces to copy packets to the CPM."
Extract from Nokia SR Linux ACL Configuration Guide:
"Unlike cpm-filter (for control-plane protection), capture-filter ACLs are designed to mirror user traffic to the CPM for debugging via traffic-monitor."
Why Other Options Are False:
A: Generic "ACL filter" is ambiguous. Only capture-filter ACLs copy data-plane traffic to the CPM for traffic-monitor.
C: cpm-filter policer rate-limits control-plane traffic (e.g., ICMP to the router), not host-to-host ICMP. It does not enable packet capture.
D: cpm-filter handles control-plane traffic destined for the router (e.g., ICMP to router IPs), not transit traffic. It does not support traffic-monitor.
[References:, Nokia SR Linux Troubleshooting Guide: Section "Packet Capture (traffic-monitor)"., Nokia SR Linux ACL Configuration Guide: Sections "Capture-filter ACLs", "CPM-filter ACLs"., ]
Question # 10
Based on the exhibit output, which of the following is NOT the reason the user runs the “baseline diff†command?
A.
User admin is not able to commit their changes.
B.
Another user has committed changes.
C.
User admin wants to check if there are differences between the current running config and their baseline datastore.
D.
User admin notices that “!†appears in the CLI prompt.
The "baseline diff" command is used to compare the candidate configuration against the baseline datastore to see changes or conflicts, especially when multiple users are involved or to verify differences. It does not indicate that the user is unable to commit changes.