CCNP TSHOOT 6.0 - Cisco Learning Home

CCNPv6 TSHOOT
219 0 469096 18304 436816 0 0 VLAN Manager
25 0 260308 0 270512 99792 0 EEM ED Syslog
170 0 218420 504 215916 0 0 Crypto HW
Proc
221 0 196192 0 203396 0 0 EEM Server
183 0 114340 532 123012 0 0 Crypto WUI
167 0 76476 252 83428 0 0 HTTP Process
i. Issue the show memory statistics command on R3. Note the amount of used and free memory
for the processor for later comparison. By comparing the amount of memory used to the baseline
(shown below), you can determine how much is used when the trouble ticket issues are introduced.
You can also compare this to the memory when running the TTCP utility. The baseline memory
amounts and after the TT was loaded are provided here for comparison.
Note: As can be seen below, the trouble ticket issues cause an increase of nearly 70 KB of memory
over the baseline. This is not enough to cause serious memory depletion issues with the router but
serves to illustrate the type of problem that can occur in a lab environment. Actual results might be
very different in a production environment.
Baseline
R3#show memory statistics
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor 64E822C0 101178688 24016328 77162360 75584536 75588172
I/O EAF00000 17825792 5421744 12404048 12363136 1238780
After TT Issues Are Introduced
R3#show memory statistics
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor 64E822C0 101178688 24085092 77093596 75584536 75579176
I/O EAF00000 17825792 5421744 12404048 12363136 1238780
Step 4: Generate loads on R3 using the TTCP utility.
To initiate a TTCP connection and generate test traffic from switch ALS1 at the branch office to switch DLS2
at headquarters, use the following procedure.
a. On switch DLS2 (receiver), enter the command sequence.
DLS2#ttcp
transmit or receive [receive]:
receive packets asynchronously [n]:
perform tcp half close [n]:
receive buflen [32768]:
bufalign [16384]:
bufoffset [0]:
port [5001]:
sinkmode [y]:
rcvwndsize [32768]:
All contents are Copyright © 1992–2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 17 of 32