TSS WAAS DEMO GUIDE

DATE: Tuesday, May 04, 2010

PREPARED BY: Richard Bocchinfuso

VERSION: 1.0

1. Login (RDP) to the server (192.168.100.51) and client machines (192.168.200.51)a. Note: FTP server is running on 192.168.100.51, we will use an FTP client on 192.168.200.51 to demonstrate

WAAS2. Verify the local routing on server and client machines

a. Execute “route print”i. Notice that the default gateway is .1 and no static route exists to the .100 or .200 networks

b. Ping from client to server to demonstrate LAN connectivity with no latency3. Transfer a file from the client to the server to demonstrate local transfer speeds4. Login to Network Nightmare to show settings5. Open console session to the EDGE WAE

a. Clear the DRE on the edge WAEb. Shut inlinegroup 1/0

i. Note: This is so we can demonstrate a native WAN transfer without acceleration

Page 1 of 2

TSS WAAS DEMO GUIDE

6. Change route on server and client to use the WAN simulator as the default gatewaya. Server

i. route add 192.168.200.0 mask 255.255.255.0 192.168.100.251 (this tells the server to use the 251 gateway)ii. route print (verify the route)

iii. ping 192.168.200.51 (should see 40ms of latency)b. Client

i. route add 192.168.100.0 mask 255.255.255.0 192.168.200.251 (this tells the server to use the 251 gateway)ii. route print (verify the route)

iii. ping 192.168.100.51 (should see 80ms of latency)7. Execute ftp file transfer from server to client

a. Observe the transfer speed8. Open console session to the EDGE WAE

a. no shut inlinegroup 1/09. Execute initial ftp file transfer from server to client

a. This transfer is being accelerated but is not cached10. Execute second ftp file transfer from server to client

a. This transfer should be serviced from cache, occasionally it takes a couple of transfers to see the cache effect11. Execute third ftp file transfer from server to client

Page 2 of 2