Refer to the exhibit.
Which command is required to validate that an IP SLA configuration matches the traffic between the branch office and the central site?
Refer to the exhibit.
Which command is required to validate that an IP SLA configuration matches the traffic between the branch office and the central site?
To validate that an IP SLA configuration matches the traffic between two sites, you need to check if the IP SLA operation is functioning correctly and capturing the correct traffic. The 'show ip sla statistics' command provides real-time information on the performance and statistics of the IP SLA operations, including success rates, response times, and operation counts. These statistics reflect the actual traffic being monitored and help determine if the IP SLA matches the intended traffic patterns. Therefore, this command is necessary to validate that the IP SLA configuration is matching the traffic correctly.
Question says to "validate" that the configuration matches the traffic - D, sh ip sla statistics has the counters that show the "matched" traffic.
I think its C. What if now traffic has passed between the sites yet? statistics and counters won't validate anything
The answer is D. R1# show ip sla statistics
show ip sla statistics
The answer is D. lab ouput provided int he discussions already.
Correct answer is C Information can be found here https://www.cisco.com/c/en/us/td/docs/ios/ipsla/command/reference/sla_book/sla_04.html
Agree, "configuration" provides better info then "stat
D is more accurate. we are using 1 command on 1 router, showing the conf will not help if we can't compare it with the conf of the other router. and the question is asking about matching the "traffic"
D is more accurate. we are using 1 command on 1 router, showing the conf will not help if we can't compare it with the conf of the other router. and the question is asking about matching the "traffic"
C focuses specifically on the configuration details, while D provides statistics related to the operation
Option D (show ip sla statistics) would provide information about the statistics of the IP SLA operations, such as success or failure counts, response times, and other performance metrics. While it gives insights into the performance of the IP SLA operations, it doesn't directly show the details of the configuration, like the source and destination addresses, type of operation, and other configuration parameters. To validate that the IP SLA configuration matches the traffic between the branch office and the central site, it's better to use show ip sla configuration as it specifically displays the configured parameters for the IP SLA operations. Once you've verified the configuration, you can then use show ip sla statistics to check the performance metrics.
to validate the configuration BRCC-LAN-B#show ip sla configuration IP SLAs Infrastructure Engine-II Entry number: 10 Owner: Tag: Type of operation to perform: icmp-echo Target address/Source address: 1.1.1.1/11.11.11.11 Operation timeout (milliseconds): 3000 Type Of Service parameters: 0x0
Router# show ip sla configuration 3 Entry number: 3 Owner: Tag: Type of operation: echo Target address/Source address: 1.1.1.1/0.0.0.0 Operation timeout (milliseconds): 5000 Type Of Service parameters: 0x0 Vrf Name: Request size (ARR data portion): 28 Verify data: No Schedule: Next Scheduled Start Time: Start Time already passed Group Scheduled: False Operation frequency (seconds): 60 Life/Entry Ageout (seconds): Forever/never Recurring (Starting Everyday): FALSE Status of entry (SNMP RowStatus): Active Threshold (ms): 5000 Distribution Statistics: Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 5 Statistic distribution interval (milliseconds): 10 Number of history Lives kept: 0 Number of history Buckets kept: 15 History Filter Type: None Enhanced History:
Router# show ip sla statistics Current Operational State Entry Number: 3 Modification Time: *22:15:43.000 UTC Sun Feb 11 2001 Diagnostics Text: Last Time this Entry was Reset: Never Number of Octets in use by this Entry: 1332 Number of Operations Attempted: 2 Current Seconds Left in Life: 3511 Operational State of Entry: active Latest Completion Time (milliseconds): 544 Latest Operation Start Time: *22:16:43.000 UTC Sun Feb 11 2001 Latest Oper Sense: ok Latest Sense Description: 200 OK Total RTT: 544 DNS RTT: 12 TCP Connection RTT: 28 HTTP Transaction RTT: 504 HTTP Message Size: 9707
my fault, It should be D, "matches the traffic" DNS RTT: 12 TCP Connection RTT: 28 HTTP Transaction RTT: 504 HTTP Message Size: 9707
When the IP SLA operation is scheduled, it can be verified with the show ip sla configuration command. Example 24-55 illustrates the configuration steps to schedule the IP SLA 1 operation with a start time of now and a lifetime of forever. This example also shows the verification that it is running and configured properly. OCG
C is more correct. It shows configuration. Statistics shows counters. Successes and Failures. "Which command is required to validate that an IP SLA configuration"
"Which command is required to validate that an IP SLA configuration matches the traffic". To validate, you need to check if the SLA is successful or failing and that's "sh ip sla statistics". Please ignore my first comment, D is correct
show ip sla statisic