Lab Appendix

The appendix lists all the different labs that will be carried during the course by the users or the instructor. Each lab description contains: A list of objectives that the user should experience during the lab. A network diagram that corresponds to that lab. A list of detailed phases to be taken by the user. A list of commands that the user will need to configure for the different phases. Among different labs, the user has to make sure that the equipments dont have any irrelevant configuration; such leftover commands might interfere with the new objectives.

Lab Installation and Initial Configuration and Link creation

Lab objectives Get acquainted with Accelerators. Configure Accelerators from scratch. Install an On-LAN Accelerator. Install an On-Path Accelerator. Create an accelerated link and verify its compression. Troubleshoot routing deployment.

Network diagram
WAN
Client .100 192.168.1.0/24 WAN Sim. 192.168.20X.0/24 WAN Sim. ROUTER ROUTER VACCX .2 .1 .241 .231 .1 .1 .1 .2

Branch

Center
192.168.150.0/24 VACC EV .16 FS .13 Win. .11 DC .10

BW=1500Kbps Latency=75ms

Phases Lab verification: 1. With no Accelerators running, make sure you have communications between the client and server. Make sure the all PCs default gateway is their router. 2. Verify that you have connection between the client and the server. Make note of the delay in the network. 3. Verify using traceroute that traffic going from the client to the server and vice versus passes through the local Router. 4. Transfer 10MB.doc using FTP (ftp://anonymous:anything@192.168.150.13/10MB.doc) and HTTP (http://192.168.150.13/10MB.doc). Take measurements of duration of

transfer and WAN statistics using the router. Calculate the actual bandwidth. Accelerator installation: 5. Connect the Accelerators to your network. Minimally configure the Accelerators to allow communication to resume between the client and server; to achieve this, you need to configure the IP address and default gateway for both Accelerators. Also, configure non-acceleration commands, such as time, hostname, etc. 6. Verify that the traffic in both ways is flowing through the local Accelerator using traceroute. 7. Transfer the files again - expect no change. However, browse to the WebUI of the Accelerator and view the relevant graphs. Link creation: 8. Create a 1500Kbps accelerated link between the Accelerators. Verify using traceroute that traffic from both sides jumps from one Accelerator to the other. 9. Transfer the same file using FTP and HTTP again (first iteration). Take measurements of the transfer duration and packet statistics again. Compare the non-accelerated transfers with the accelerated transfers. 10. Transfer the same file using FTP and HTTP again (second iteration). Take measurements of the transfer duration and packet statistics again. Compare the first accelerated transfers with the second accelerated transfers.

Commands List: Basic commands: Configuring IP address and default gateway:

accelerator> enable accelerator# configure accelerator(config)# interface local accelerator(local interface)# ip address 192.168.234.2/24 accelerator(local interface)# ip default-gateway 192.168.234.1 accelerator(local interface)# exit accelerator(config)# exit accelerator# disable accelerator>

Configuring the hostname:

accelerator(config)# hostname TheBestAccelerator

TheBestAccelerator(config)# Setting the time:

accelerator(config)# clock set 01-30-2000 20:00 Sun Jan 30 20:00:00 GMT 2000 accelerator(config)#

Setting speed and duplex for a port:

accelerator(config)# interface ethernet 0/0 accelerator(interface)# link-mode 100Mbit-full accelerator(interface)# exit

Fixating the deployment:

accelerator(config)# interface local accelerator(local interface)# deployment onlan accelerator(local interface)# exit accelerator(config)#

Modifying the resources to match links:

accelerator(config)# core-allocation accelerator(CORE ALLOC)# resource-policy topology-size 1 Warning: Modifying this parameter will cause all links to reconnect. You must save the new configuration and reboot the Accelerator. Are you sure? (y/n) y accelerator(CORE ALLOC)# exit

Rebooting the device: accelerator(config)# reboot The system is going to reboot. Are you sure? (y/n) y The system attempts to reboot, please wait...

Displaying the running configuration:

accelerator# show running-config Creating configuration ... # AcceleratorOS configuration file # Generated by AcceleratorOS v6.1(2) build 6.12 on Jan 30, 2000 at 11:03 ! ! interface local ip address 192.168.234.2 255.255.255.0 ip default-gateway 192.168.234.1 deployment onlan ! End accelerator#

Viewing the routing table:

accelerator# show ip route Codes: K - kernel route, C - connected, S - static, R - RIP, O OSPF, B - BGP, > - selected route, * - FIB route K>* 0.0.0.0/0 via 192.168.234.1, bridge K * 127.0.0.0/8 is directly connected, lo C>* 127.0.0.0/8 is directly connected, lo C>* 192.168.234.0/24 is directly connected, bridge K>* 224.0.0.0/4 is directly connected, bridge accelerator#

Viewing the subnets table:

accelerator# show subnets Local subnets ---------------------------------------------------------------| NETWORK ADDRESS | METRIC | ADVERTISE | TYPE ------+--------------------+------------+-----------+----------1 | 192.168.234.0/24 | 1 | enable | automatic ---------------------------------------------------------------Remote subnets No remote links exist.

Links commands:

Creating a link:
accelerator(config)# interface link Creating new link... accelerator(LINK)# link destination 1.1.1.1 accelerator(LINK)# bandwidth 1000 accelerator(LINK)# exit Updating link parameters New link was created with ID = 1

Displaying a link and its parameters and statistics:

accelerator(config)# show interface link 1 Link ID...........................1 Description.......................L-1.1.1.1 Destination IP....................1.1.1.1 Source IP.........................primary(192.168.234.2) Bandwidth out (Kbps)..............1000 Bandwidth in (Kbps)...............unlimited . . .

Displaying a summary of all links:

accelerator(config)# show interface link summary ---------------------------------------------------------------------------LINK | DEST IP ADDRESS | DESCRIPTION | BANDWIDTH | LINK STATUS -----+--------------------+-------------+----------------+-----------------1 | 1.1.1.1 | L-1.1.1.1 | 1000/ N/A | drop non | N/A | non-link | 100000/ N/A | virtual ----------------------------------------------------------------------------

Lab Quality of Service and Monitoring

Lab objectives Monitor usage of links. Discover and monitor applications running in the network. Configure a new application. Create QoS rules as needed and verify their operation.

Network diagram
WAN
Client .100 192.168.1.0/24 WAN Sim. WAN Sim. 192.168.20X.0/24 ROUTER ROUTER VACCX .2 .1 .241 .231 .1 .1 .1 .2

Branch

Center
192.168.150.0/24 VACC EV .16 FS .13 Win. .11 DC .10

BW=512Kbps Latency=50ms

Phases No QoS observing the problem: 1. Verify that the network is running. As before, measure the bandwidth and delay. 2. Re/configure the link to matches the bandwidth. Make sure the clientserver traffic gets accelerated. 3. Run a continuous ping from client to server (ping XXX t). Pay attention to the initial delay. 4. Open a terminal services window from the client to the server. Pay heed to the interactivity of the session. 5. Transfer 10MB using FTP (ftp://anonymous:anything@192.168.150.13/10MB). Measure the time.

During the transfer, look at the changes to the ping measurements and the interactivity of the terminal services session. 6. Monitor the link and notice the congestion. 7. Monitor what applications are running. 8. Devise your QoS solution. Creating QoS: 9. Create QoS real-time policy rules for ICMP and terminal services in the center Accelerator, for outbound traffic for your link. 10. Transfer the FTP file again. Compare the ping times and the terminal services interactivity.

Commands List: Showing the link usage:

FBD# show interface link 1 throughput ------------------------------------------------------------------------------Link 1 Throughput --------------+------------------------+-----------------------+--------------Data (Bytes) | System Up (KB) | Since Clear (KB) | Last 5 Secs --------------+------------------------+-----------------------+--------------In | 0| 0| 0 Kbps Out | 0| 0| 0 Kbps Raw In | 0| 0| 0 Kbps Raw Out | 0| 0| 0 Kbps . . .

Showing active applications:

Accelerator# show application -------------------------------------------------------------------------APPLICATIONS (IN) -------------------------------------------------------------------------Name | Accelerated | Post-Accelerated | Acceleration -------------------+-------------------+-------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------APPLICATIONS (OUT) -------------------------------------------------------------------------Name | Pre-Accelerated | Accelerated | Acceleration -------------------+-------------------+-------------------+-------------telnet | 0.09 Kbps| 0.09 Kbps| 0% -------------------------------------------------------------------------Accelerator#

Crating an application:

accelerator(config)# application newApplication tcp from 15400 to 15405 accelerator(config)#

Creating a QoS rule:

accelerator(config)# policy-rule link 1 outbound Creating new rule... accelerator(RULE)# match application newApplication accelerator(RULE)# set policy priority real-time accelerator(RULE)# exit Updating parameters New rule was created with ID = 1

Lab TCP Acceleration and Web Acceleration

Lab objectives Configure and experience TCP Acceleration. Configure and experience HTTP Acceleration. Configure and experience FTP Acceleration.

Network diagram
WAN
Client .100 192.168.1.0/24 WAN Sim. 192.168.20X.0/24 WAN Sim. ROUTER ROUTER VACCX .2 .1 .241 .231 .1 .1 .1 .2

Branch

Center
192.168.150.0/24 VACC EV .16 FS .13 Win. .11 DC .10

BW=512Kbps Latency=300ms

Phases TCP Acceleration: 1. Verify that the network is running. As before, measure the bandwidth and delay. 2. Without a link, Transfer 10MB.doc using FTP (ftp://anonymous:anything@192.168.150.13/30MB.doc). Measure the time and WAN traffic. 3. Re/configure a link that matches the bandwidth. Make sure the clientserver traffic gets accelerated. 4. Transfer 30MB.doc using FTP (ftp://anonymous:anything@192.168.150.13/30MB.doc). Measure the time and WAN traffic. View the graph for the transfer in the Accelerator. You should see that although there is enough bandwidth, the PCs cant fill the pipe. 5. Enable TCP Acceleration on the link.

6. Retransfer the 30MB.doc using FTP (ftp://anonymous:anything@192.168.150.13/30MB.doc). Measure the time and WAN traffic again and view the graph for the transfer in the Accelerator. The transfer should now fill the pipe. FTP Acceleration: 7. Transfer 10MB.doc using FTP (ftp://anonymous:anything@192.168.150.13/10MB.doc). Measure the time and WAN traffic. View the graph for the transfer in the Accelerator. 8. Transfer the same file a couple of times and see that it is being traversed over the WAN every time. 9. Enable FTP Acceleration on the Accelerator of the remote branch. 10. Retransfer the file. Measure the time and WAN traffic again and view the graph for the transfer in the Accelerator. Because you have just enabled Web acceleration, the cache was not populated before; therefore the transfer should traverse the WAN. 11. Again, transfer the same file. Because it was already been cached, the new request should be instantaneous and there should be no major WAN traffic. HTTP Acceleration: 12. Transfer 10MB.doc using HTTP (http:// 192.168.150.13/10MB.doc). Measure the time and WAN traffic. View the graph for the transfer in the Accelerator. 13. Transfer the same file a couple of times and see that it is being traversed over the WAN every time. 14. Enable HTTP Acceleration on the Accelerator of the remote branch. 15. Retransfer the file. Measure the time and WAN traffic again and view the graph for the transfer in the Accelerator. Because you have just enabled Web acceleration, the cache was not populated before; therefore the transfer should traverse the WAN.

16. Again, transfer the same file. Because it was already been cached, the new request should be instantaneous and there should be no major WAN traffic.

Commands List: Enabling TCP acceleration on a link:

accelerator(config)# interface link 1 accelerator(LINK)# tcp-acceleration accelerator(TCP-ACC)# use-global-tcp-acceleration disable accelerator(TCP-ACC)# tcp-acceleration enable accelerator(TCP-ACC)# typical-round-trip 300 accelerator(TCP-ACC)# typical-acceleration-rate 800 accelerator(TCP-ACC)# exit accelerator(LINK)# exit Updating link parameters

Allocating disk space for FTP and HTTP acceleration:

accelerator(config)# active-cache web-cache-only This operation may take some time. Please be patient..

Enabling FTP Acceleration:

accelerator(config)# web-acceleration accelerator(web-acceleration)# ftp-acceleration accelerator(ftp-acceleration)# ftp-acceleration enable accelerator(ftp-acceleration)# exit Updating FTP acceleration params Warning: Save the configuration and reboot the Accelerator for new settings to take effect.

Enabling HTTP acceleration:

accelerator(config)# web-acceleration accelerator(web-acceleration)# http-acceleration accelerator(http-acceleration)# http-acceleration enable accelerator(http-acceleration)# exit Updating HTTP acceleration params Warning: Save the configuration and reboot the Accelerator for new settings to take effect. accelerator(web-acceleration)# exit

Showing web (HTTP and FTP) acceleration parameters:

accelerator(config)# show web-acceleration HTTP acceleration HTTP acceleration mode..........disable Cache size (GB).................0 . . . FTP acceleration FTP acceleration mode...........disable Cache size (GB).................0 . . .