CML lab supports C not D.
Question is: "Which command is required to validate that an IP SLA configuration matches the traffic between the branch office and the central site?"
Stats are missing some key config items, so you cannot compare between sites:
SW02#sh ip sla statistics
IPSLAs Latest Operation Statistics
IPSLA operation id: 10
Latest RTT: 4 milliseconds
Latest operation start time: 17:48:11 UTC Wed Nov 13 2024
Latest operation return code: OK
Number of successes: 10 <---validates operation, but not configuration
Number of failures: 0
Operation time to live: Forever
//end
part 1 - site gives dns timeouts with too much text
Versus C/config:
!
SW02#sh ip sla configuration 10
IP SLAs Infrastructure Engine-III
Entry number: 10
Owner:
Tag:
Operation timeout (milliseconds): 3000
Type of operation to perform: icmp-echo
Target address/Source address: 1.1.1.1/172.16.2.2
<snip defaults>
Schedule:
Operation frequency (seconds): 5 (not considered if randomly scheduled)
Next Scheduled Start Time: Start Time already passed
Group Scheduled : FALSE
Randomly Scheduled : FALSE
Life (seconds): Forever
Entry Ageout (seconds): never
Recurring (Starting Everyday): FALSE
Status of entry (SNMP RowStatus): Active
Threshold (milliseconds): 250
<snipped the rest>
//end
part 2
HTH
show ip sla configuration
Displays configuration values including all defaults for all IP SLAs operations or the specified operation.
show ip sla statistics
Displays the current operational status and statistics of all IP SLAs operations or a specified operation.
https://www.cisco.com/c/en/us/td/docs/ios/ipsla/command/reference/sla_book/sla_02.html
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"
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
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
This section is not available anymore. Please use the main Exam Page.350-401 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Jeff555566
Highly Voted 2 years, 2 months ago3c38e31
1 year agoBrian9296
Highly Voted 2 years, 3 months agoNetworkJanitor
Most Recent 6 months, 3 weeks agoNetworkJanitor
6 months, 3 weeks agowasbe
6 days, 20 hours agoJust_little_me
7 months ago05b11e1
10 months, 2 weeks ago[Removed]
12 months ago[Removed]
1 year agoShri_Fcb10
1 year agoteems5uk
1 year, 4 months agoeearmani
1 year, 5 months agoCCNPWILL
1 year, 8 months agoAsombrosso
1 year, 9 months agoAsombrosso
1 year, 9 months agoAsombrosso
1 year, 9 months agoAsombrosso
1 year, 9 months agoolaniyijt
2 years, 1 month agoolaniyijt
2 years, 1 month agoClauster
2 years, 2 months agosnarkymark
2 years, 2 months agokalachuh
2 years, 2 months agoNickplayany
2 years, 2 months ago