CCNP TSHOOT 6.0 - Cisco Learning Home

CCNPv6 TSHOOT
ack frequency [0]:
delayed ACK [y]:
show tcp information at end [n]:
ttcp-r: buflen=32768, align=16384/0, port=5001
rcvwndsize=32768, delayedack=yes tcp
b. On switch ALS1 (transmitter), enter the command sequence:
ALS1#ttcp
transmit or receive [receive]: transmit
Target IP address: 10.1.100.253
calculate checksum during buffer write [y]:
perform tcp half close [n]:
send buflen [32768]:
send nbuf [2048]:
bufalign [16384]:
bufoffset [0]:
port [5001]:
sinkmode [y]:
buffering on writes [y]:
show tcp information at end [n]:
ttcp-t: buflen=32768, nbuf=2048, align=16384/0, port=5001 tcp ->
10.1.100.253
ttcp-t: connect
ttcp-t: 67108864 bytes in 68434 ms (68.434 real seconds) (~957 kB/s)
+++
ttcp-t: 2048 I/O calls
ttcp-t: 0 sleeps (0 ms total) (0 ms average)
c. Record the time required to complete the TTCP data transfer.
________________________________________________________________________________
Note: Referring to the above results, the TTCP utility transmitted over 67 million bytes in
approximately 68 seconds. This is comparable to the baseline performance, which indicates that this
router is not significantly loaded. Different devices and network links will produce different results.
Step 5: Test R3 with load applied.
Note: In this lab, the TCP utility creates a load that lasts for about 60–120 seconds. The actual length of time
depends on the capabilities of the devices and links in use.
Use Cisco IOS commands and pings to record the router performance figures simulating a condition in which
large file transfers are currently 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.
a. Ping from PC-B to R2 Lo1 and record the results.
____________________________________________________________________________
Include the minimum, maximum, and average round-trip times. The times should be about the same as
without the TTCP load on R3.
C:\>ping 172.20.0.1
Pinging 172.20.0.1 with 32 bytes of data:
Reply from 172.20.0.1 : bytes=32 time=12ms TTL=64
Reply from 172.20.0.1 : bytes=32 time=11ms TTL=64
All contents are Copyright © 1992–2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 18 of 32