CCNP TSHOOT 6.0 - The Cisco Learning Network

CCNPv6 TSHOOT
Referring to the above results, the TTCP utility transmitted over 67 million bytes in approximately 106
seconds or about 613 Kilobytes per second (kB/s). As a comparison, the baseline configuration without the
errors in this trouble ticket took approximately 70 seconds to transmit the same amount of data but at a rate of
about 898 kB/s. Different devices and network links produce different results.
Note: You cannot issue any commands on the console of either device until the transfer finishes. The
transmission can be interrupted at any point in time from the transmitting side using the key combination Ctrl-
Shift-6.
Caution: This utility can overload a router with test traffic. It is not recommended to use it on production
devices. Read the TTCP documentation before using the TTCP utility.
Step 6: Test R3 with load applied.
Note: For this lab, TTCP utility creates a load that lasts 60–120 seconds. The actual length of time
depends on the capabilities of the devices and links being used.
On R3, use Cisco IOS commands and pings to record the router performance figures simulating a
condition where large file transfers are being transmitted. These results can be compared to the baseline
output (selected baseline information is shown) and the output obtained when using the TTCP utility.
Try to issue the following Cisco IOS commands on R3 while TTCP is generating traffic between ALS1 and
DSL2. If it stops, restart the transmit-receive process between switches ALS1 and DLS2. You can also
increase the length of time traffic runs by increasing the send buflen parameter, which defaults to
32768 (for example, you can increase it 65536 or higher).
a. While TTCP is running, ping from PC-B to SRV1 and record the minimum, maximum, and average
round-trip results.
____________________________________________________________________________________
____________________________________________________________________________________
The times should be 10 times or more higher than without the TTCP load on R3.
C:\>ping 10.1.50.1
Pinging 10.1.50.1 with 32 bytes of data:
Reply from 10.1.50.1: bytes=32 time=39ms TTL=64
Reply from 10.1.50.1: bytes=32 time=38ms TTL=64
Reply from 10.1.50.1: bytes=32 time=38ms TTL=64
Reply from 10.1.50.1: bytes=32 time=38ms TTL=64
Ping statistics for 10.1.50.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 39ms, Average = 38ms
b. On Fa0/0, change the period over which the loads are computed to 30 seconds.
interface fa0/0
load-interval 30
c. Issue the show interfaces fa0/0 command and note the values for txload and rxload.
___________________________________________________________________________
R3#show interfaces fa0/0
FastEthernet0/0 is up, line protocol is up
Hardware is Gt96k FE, address is 001b.530d.6028 (bia 001b.530d.6028)
Internet address is 10.1.80.1/24
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
All contents are Copyright © 1992–2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 9 of 32