Labapp 2001 (Guide)

2008 Cisco Systems, Inc.
All rights reserved 1 of 161

WAAS 4.1 Lab Session
LABAPP-2001

Outline
This guide includes these activities:
Lab 1: Cisco WAAS Quick Start (Inline)
Lab 2: Configure the Cisco NM-WAE and WCCP
Lab 3: Configure Custom Application Traffic Policies
Lab 4-: Configure Cisco WAAS NFS Acceleration
Lab 5: Configuring Cisco WAAS MAPI Acceleration
Lab 6: Configuring Windows Server on WAAS
Sponsored by
Firefly Training
www.fireflycom.net

2008 Cisco Systems, Inc. All rights reserved 2 of 161
.
Lab 1: Ci sco WAAS Qui ck Start (Inl i ne)
Complete this lab activity to practice what you learned in the related module.
Activity Objective
In this activity, you will configure a Cisco WAAS implementation with three Cisco WAEs, two
routers, and WAN emulation. After completing this activity, you will be able to meet these
objectives:
Create a baseline from unoptimized application response
Configure the Central Manager Cisco WAE
Configure the Data Center Cisco WAE
Configure the Branch Office Cisco WAE
Test application response with Cisco WAAS enabled
Monitor Cisco WAAS operation using the Central Manager GUI
Monitor Cisco WAAS operation using the Command Line Interface (CLI)


Visual Objective
The figure illustrates what you will accomplish in this activity.
2008 Cisco Systems, Inc. All rights reserved. WAAS v4.0.131
WAAS Lab Topology
WAN Data Center
WANBr idge
10.10.90.254
Centr al Manager WAE
10.10.100.24X
Domai n NetBIOS name: WAAS
FQDN: waas.l ocal
X = your pod number
Cor e WAE 10.10.100.23X
DC Router
WAN: VLAN 201
10.10.200.1X
LAN: 802.1q
VLAN 100: 10.10.100.X
VLAN 110: 10.10.101.X WMS
Windows XP PC
Linux/Solari s Cli ent
Edge Router
WAN: VLAN 200
10.10.200.X
LAN: 802.1q
VLAN X0: 10.10.X0.1
VLAN X1: 10.10.X1.1
VLAN X3: 10.10.x3.1 for WMC
Internal (NME-WAE)
VLAN X2: 10.10.X2.1
Edge NME-WAE
VLAN X2: 10.10.X2.230
Edge WAE 674
10.10.X1.230
VLAN X1
Branch Office
V
B
2
V
B
3
V
B
1
Cisco WAAS
Mobile client
Cisco WAAS
Mobil e Server
SOHO/Mobi le User
Wi ndows XP PC
Wi ndows 2003
Ser ver (CIFS, FTP,
HTTP, HTTPS Vi deo)
Exchange Ser ver
2003 (MAPI)
Linux/Solar is (NFS)

.
The figure illustrates the VLAN configuration for this activity.
2008 Cisco Systems, Inc. All rights reserved. WAAS NPI v4.1-#-2
VLAN Configuration
WAN Branch Office
VLAN 201 VLAN 200
VLAN X3
VLAN X0
VLAN X1
VLAN 100
Data Center

Required Resources
These are the resources and equipment that are required to complete this activity:
Two Cisco 2800 routers
Three Cisco WAEs
One Microsoft Windows workstation
One Application Server with HTTP and Windows File shares
Task 1: Create Baseline Measurements for Applications
In this task, you will create baseline measurements for several applications including a
Microsoft (MS) Windows file transfer and an http file transfer. This baseline will be used to
test relative application performance after Cisco WAAS is installed and configured on the
network. All tests will be performed from the MS Windows workstation shown in the lab
diagram. Attach to it by clicking the green Desktop oval..


Activity Procedure 1: Determine the Baseline Measurement for a Common Internet
File System (CIFS) File Transfer
Complete these steps:
Step 1 Login: Connect to the Branch Office MS Windows XP workstation and login.
Username: administrator
Password: cisco
Step 2 Determine WAN latency: Select Start/Run, enter cmd to access a command
window. Issue the command: ping 10.10.100.100. Note the latency of the WAN.
Note If you do not see 80ms latency, contact the instructor

Step 3 Go to Cisco WAAS CIFS Demonstration Webpage: Open Internet Explorer type
Step 4 Type http://10.10.100.100/cifs.html in the address field and press Enter.

.

Step 5 Ensure that the Free Download Manager software has been enabled: double
click the button in the system tray. This will allow tracking of the elapsed file
download time.

After you click Save be
patient, it may take a little
time to continue.


Step 6 Execute a native MS Windows download performance test for a transfer
occurring over the WAN with no optimization: Click on the 15MB.ppt link.
Choose Save file and select the Desktop as the save location, then click OK to
use the Free Download Manager to monitor the progress of the CIFS download.

.

Step 7 Record test results: Note the Starting download time and the Download
complete time. The elapsed time will be compared against response after Cisco
WAAS has been enabled.
Application File size Time to transfer
Wi ndows f i l e Tr ansf er
( CI FS)
15MB

Step 8 Perform Housekeeping: Delete the 15MB.ppt file from the desktop.


Activity Procedure 2: Determine the Baseline Measurement for a Web Page
download
Step 1 To verify the HTTP page download performance natively over the WAN with no
optimization, open Firefox on the client and browse to http://10.10.100.100/

Step 2 Access the Firebug tool: Select Tools/Firebug/Open Firebug.

Notice that the firebug window appears at the bottom of the page. Please confirm that it is
Enabled for All and that the Net tab is selected.

.
Step 3 Select the Stop button on the browser.

Step 4 Clear the web cache: Select Tools/Clear Private Data, or press
Ctrl+Shift+Del then Enter.


Step 5 Load the test webpage: type http://10.10.100.100/index1.html in the address field
and press Enter.

Step 6 Record the results: When the download is complete, note, at the bottom of the
Firebug report, the number of requests and the time that it took to download all
objects.
Application Number of requests Time to transfer
Web page downl oad
( HTTP)

.

Activity Verification
You have completed this task when you attain these results:
You have completed unoptimized CIFS file transfer and web page download and recorded
the baseline results.


Task 2: Configure the Central Manager Cisco WAE
In this task, you will configure the Central Manager Cisco WAE using the setup script. You
will assign addressing and interface configuration, device mode, and interception mode..
Activity Procedure: Configure the Central Manager Cisco WAE
Complete these steps on the Central Manager Cisco WAE:
Step 1 Connect to the Central Manager console port: Click the green Console oval
next to the Central Manager WAE icon.
Step 2 Login to Central Manager: You may need to press the Enter key one or two times
to see the login prompt.
Ci sco Wi de Ar ea Appl i cat i on Ser vi ces Cent r al Manager Consol e

Username: admin
Password: default
Syst emI ni t i al i zat i on Fi ni shed.
Step 3 Start the setup procedure: Type setup.
Note While a default configuration can be applied, as shown below, do not use the default for this
exercise. The default setup configures the device as an Application Accelerator, not as a.
Central Manager Type n to enter the quick configuration and bypass the default setup.
NO- HOSTNAME#setup

WARNI NG: Changi ng any of t he net wor k set t i ngs f r oma
t el net sessi on may r ender t he devi ce i naccessi bl e on
t he net wor k. Ther ef or e i t i s suggest ed t hat you have
access t o t he consol e bef or e modi f yi ng t he net wor k set t i ngs.

Thi s devi ce i s conf i gur ed as cent r al - manager
St ar t i ng qui ck conf i gur at i on mode
St ep 1:
Conf i gur e WAAS Set t i ngs
- - - - - - - - - - - - - - - - - - - - - - - -
Sel ect devi ce mode :

.
1. appl i cat i on- accel er at or
2. cent r al - manager
Ent er your choi ce [ 2] : 2
Pr ess t he ESC key at any t i me t o qui t t hi s sessi on
Step 4 Select 2 and press enter to Configure the device mode as Central Manager: Type
2 to select Central Manager and press the Enter key.
Step 5 Choose the interface to configure for the CM: When prompted choose a primary
interface that will be used for management communication; press 1 for gigabit
ethernet 1/0 and press the enter key.
St ep 2:
Conf i gur e net wor k set t i ngs
- - - - - - - - - - - - - - - - - - - - - - - - - - -
Sel ect i nt er f ace t o conf i gur e:

NO I NTERFACE NAME STATUS I P ADDRESS NETMASK
1: Gi gabi t Et her net 1/ 0 UP unassi gned unassi gned
2: Gi gabi t Et her net 2/ 0 DOWN unassi gned unassi gned
Ent er choi ce [ 1] : 1
Step 6 Continue the setup process: Referring to the lab topology for addressing, complete
the following entries:
Note Any time you see an x listed below, use your pod number to replace the x.
St ep 3: Conf i gur e aut osense f or dupl ex and speed on t hi s
i nt er f ace( y/ n) [ y] : y
St ep 4: Enabl e DHCP on t hi s i nt er f ace ( y/ n) [ n] : n
St ep 5: I P addr ess of i nt er f ace: 10.10.100.24x
St ep 6: Net mask of t hi s i nt er f ace: 255.255.255.0
St ep 7: Def aul t gat eway: 10.10.100.x
St ep 8: Domai n name ser ver i p: 10.10.100.101
St ep 9: Domai n name: waas.local
St ep 10: Ent er host name[ none] : podX-CM-WAE
St ep 11: Conf i gur e NTP [ none] : 10.10.100.101
St ep 12: Ent er t i mezone [ UTC 0 0] : PST -8 0


Based on t he i nput , t he f ol l owi ng conf i gur at i ons wi l l be done:
i nt er f ace Gi gabi t Et her net 1/ 0
i p addr ess 10. 10. 100. 247 255. 255. 255. 0
no shut down
aut osense
exi t
i p def aul t - gat eway 10. 10. 100. 7
i p name- ser ver 10. 10. 100. 101
i p domai n- name waas. l ocal
pr i mar y- i nt er f ace Gi gabi t Et her net 1/ 0
host name pod7- CM- WAE
nt p ser ver 10. 10. 100. 101
cl ock t i mezone PST - 8 0
cms enabl e
Do you accept t hese conf i gur at i ons ( y/ n) [ y] : y

Woul d you l i ke t o appl y t he conf i gur at i ons ( y/ n) [ y] : y
Step 7 Answer yes to accept and apply the configurations type y and press enter
Pl ease wai t . Runni ng ' cms enabl e' . .
Al l CLI conf i gur at i ons wer e appl i ed successf ul l y.

For your r ef er ence, conf i gur at i on gener at ed
dur i ng t hi s set up sessi on i s avai l abl e at
/ l ocal 1/ set up_gen_conf i g. t xt .
You can vi ew t hi s f i l e wi t h t he command, " t ype
/ l ocal 1/ set up_gen_conf i g. t xt " .

Pr ess any key t o cont i nue. .
Step 8 Ping the configured gateway for the CM
Note Replace the x with your assigned pod number; If the default gateway is unreachable, verify your
network configuration.
podx- cm- wae# ping 10.10.100.x

.

Step 9 Verify that the Central Management Service is running: Type the following
entries to complete this step:
podX- cm- wae#sh cms info
Devi ce r egi st r at i on i nf or mat i on :
Devi ce I d = 164
Devi ce r egi st er ed as = WAAS Cent r al Manager
Cur r ent WAAS Cent r al Manager r ol e = Pr i mar y

CMS ser vi ces i nf or mat i on :
Ser vi ce cms_ht t pd i s r unni ng
Ser vi ce cms_cdmi s r unni ng
Note If your CM shows an output different from above, contact the instructor. The Device Id will
always be different.
Step 10 Disconnect from the Cisco WAE by closing the terminal window.


You have successfully verified that Central Manager is running.

.
Task 3: Configure the Data Center Cisco WAE
In this task, you will configure the Data Center accelerator Cisco WAE using the setup script.
You will assign device mode, interception method, and interface addressing as part of the setup
script.
Activity Procedure: Configure the Data Center Cisco WAE
Complete these steps on the data center Cisco WAE:
Step 1 Connect to the Data Center console port: Click the green Console oval next to
the Data Center Core WAE icon.
Step 2 Login: Type the username and password shown below:
Note You may need to press the Enter key one or two times to see the login prompt.
Ci sco Wi de Ar ea Appl i cat i on Engi ne Consol e

User name: admin
Passwor d: default

Step 3 Start the setup procedure: Type setup at the NO_HOSTNAME#prompt.
NO- HOSTNAME#setup
Note A default configuration can be applied as shown below. The default will not work for this lab
exercise because this device will be using the in-line interception method. Type n when
prompted to enter the quick configuration mode.

St ep 1: The f ol l owi ng def aul t s can be conf i gur ed:
Devi ce mode: Appl i cat i on- accel er at or
I nt er cept i on Met hod: I nl i ne


Management I nt er f ace: I nl i neGr oup 1/ 0
Aut osense: yes
Ti mezone: UTC 0 0

To keep above def aul t s and cont i nue conf i gur at i on, pr ess ' y'
To change above def aul t s and cont i nue conf i gur at i on, pr ess ' n'
[ y] : n
3
Step 4 Bypass default setup: Type n to enter the quick configuration mode.
Step 5 Configure device mode of the Data Center Cisco WAE: Type 1 to configure the
Application Accelerator and press the Enter key.
St ep 2:
- - - - - - - - - - - - - - - - - - - - - - - -
Ent er your choi ce : 1

St ep 3: Ent er Cent r al Manager addr ess [ none] : 10.10.100.24X
Step 6 Configure the interception method for the Data Center Cisco WAE: Type
inline.
St ep 4: Sel ect i nt er cept i on met hod ( i nl i ne| wccp| ot her )
[ i nl i ne] : inline
Step 7 Choose the interface for the Data Center Cisco WAE: When prompted choose a
primary interface that will be used for management communication; press 3 for
gigabit ethernet 1/0 and press the enter key.
St ep 5:
- - - - - - - - - - - - - - - - - - - - - - - - - - -
Sel ect i nt er f ace t o conf i gur e:

1: I nl i neGr oup 1/ 0 UP unassi gned unassi gned

.
St ep 8: I P addr ess of i nt er f ace: 10.10.100.23x
St ep 10: Def aul t gat eway: 10.10.100.x
St ep 13: Ent er host name[ none] : podX-DC-WAE

Step 9 Configure Inline Group for interception: Press 1 to select Inline Group 1/0
St ep 16: Sel ect I nl i neGr oup:
1. I nl i neGr oup 1/ 0
Ent er choi ce : 1
Conf i gur e aut osense f or dupl ex and speed on t hi s

Step 10 Configure the license you wish to activate: Press 2 to select Enterprise
St ep 17:
Ent er t he l i cense t o act i vat e:
1. Tr anspor t
2. Ent er pr i se


3. Ent er pr i se & Vi deo

The l i cense i s not conf i gur ed. I t i s r ecommended t o pur chase
Ent er pr i se l i cense.
Pl ease ent er t he l i cense name opt i on i f you pur chased i t
al r eady: 2
Step 11 Review and accept configuration: Type y to accept the configuration.
cent r al - manager addr ess 10. 10. 100. 247
i p addr ess 10. 10. 100. 237 255. 255. 255. 0
aut osense
exi t
i p def aul t - gat eway 10. 10. 100. 7
i p name- ser ver 10. 10. 100. 101
host name pod7- DC- WAE
nt p ser ver 10. 10. 100. 101
cl ock t i mezone PST - 8 0
i nt er f ace I nl i neGr oup 1/ 0
no shut down
aut osense
exi t
cms enabl e

Step 12 Apply the configuration: Type y to apply the configuration.
Thi s may t ake f ew moment s. Pl ease wai t . .
Pl ease wai t . Runni ng ' cms enabl e' . .

. Al l CLI conf i gur at i ons wer e appl i ed successf ul l y.

.


Step 13 Confirm the configuration: Ping your default gateway and the Central Manager
Cisco WAE. If the default gateway or Central Manager Cisco WAE are
unreachable, check your network configuration and make appropriate corrections.
Note In the following commands, replace the x with your assigned pod number
podx- dc- wae# ping 10.10.100.x
podx- dc- wae# ping 10.10.100.24x

Step 14 Verify that the Device is registered to the Central Manager: Type the following
podX- dc- wae#sh cms info
Devi ce I d = 220
Devi ce r egi st er ed as = WAAS Appl i cat i on Engi ne
Cur r ent WAAS Cent r al Manager = 10. 10. 100. 24x
Regi st er ed wi t h WAAS Cent r al Manager = 10. 10. 100. 24x
St at us = Onl i ne
Ti me of l ast conf i g- sync = Fr i J un 20 14: 49: 04
2008
Note If the device status shows Pending (CM is Busy) retry later, wait a moment and try the
show cms info command again.
You have confirmed that the device is registered to the Central Manager.


Task 4: Configure the Branch Office Cisco WAE
In this task, you will configure the Branch office accelerator Cisco WAE using the setup script.
You will assign device mode, interception method, and interface addressing as part of the setup
script.
Activity Procedure: Configure the Branch Office Cisco WAE
Complete these steps on the branch office Cisco WAE:
Step 1 Connect to the Branch Office console port: Click the green Console oval next to
the Edge WAE 674 icon.
Step 2 Login: Type the username and password shown below:

User name: admin
Passwor d: default


Step 3 Start the setup procedure: Type setup at the NO_HOSTNAME#prompt.
NO- HOSTNAME#setup


Note A default configuration can be applied as shown below. The default will not work for this lab
exercise because this device will be using the in-line interception method. Type n when
prompted to enter the quick configuration mode.

.
I nt er cept i on Met hod: I nl i ne
Management I nt er f ace: I nl i neGr oup 2/ 0
Aut osense: yes
Ti mezone: UTC 0 0
[ y] : n
Pr ess t he ESC key at any t i me t o qui t t hi s sessi on

Step 4 Bypass default setup: Type n to enter the quick configuration mode.
Step 5 Configure device mode of the Branch Office Cisco WAE: Type 1 to configure
the Application Accelerator and press the Enter key.
St ep 2:
- - - - - - - - - - - - - - - - - - - - - - - -
Ent er your choi ce : 1
Step 6 Configure the CM address
Step 7 Configure the interception method for the Branch Office Cisco WAE: Type
inline.
St ep 4: Sel ect i nt er cept i on met hod ( i nl i ne| wccp| ot her )
[ i nl i ne] : inline
Step 8 Choose the interface for the Branch Office Cisco WAE: When prompted choose
a primary interface that will be used for management communication; press 3 for
gigabit ethernet 1/0 and press the enter key.
St ep 5:
- - - - - - - - - - - - - - - - - - - - - - - - - - -
Sel ect i nt er f ace t o conf i gur e as management i nt er f ace:



St ep 8: I P addr ess of i nt er f ace: 10.10.X1.230
St ep 10: Def aul t gat eway: 10.10.X1.1
St ep 13: Ent er host name[ none] : podX-BR-WAE
Step 10 Configure Inline Group for interception: Press 1 to select Inline Group 2/0
St ep 16: Sel ect I nl i neGr oup:
Ent er choi ce : 1
Conf i gur e aut osense f or dupl ex and speed on t hi s
Step 11 Configure the license you wish to activate: Press 4 to select Enterprise and Virtual
Blade.
St ep 17:
Ent er t he l i cense t o act i vat e:
1. Tr anspor t

.
2. Ent er pr i se
4. Ent er pr i se & Vi r t ual bl ade
5. Ent er pr i se, Vi deo & Vi r t ual bl ade
Ent er your choi ce[ 2] : 4

Step 12 Review and accept configuration: Type y to accept the configuration.
Based on t he i nput , t he f ol l owi ng CLI s wi l l be conf i gur ed:
devi ce mode appl i cat i on- accel er at or
cent r al - manager addr ess 10. 10. 100. 24X
i p addr ess 10. 10. X1. 230 255. 255. 255. 0
aut osense
exi t
i p def aul t - gat eway 10. 10. X1. 1
i p name- ser ver 10. 10. 100. 100
host name podX- BR- WAE
nt p ser ver 10. 10. 100. 100
cl ock t i mezone pst - 8 0
i nt er f ace I nl i neGr oup 2/ 0
no shut down
aut osense
exi t
cms enabl e

Do you accept t hese conf i gs ( y/ n) [ y] : y

Step 13 Apply the configuration: Type y to apply the configuration.
Thi s may t ake f ew moment s. Pl ease wai t . .


Pl ease wai t . Runni ng ' cms enabl e' . . Al l CLI conf i gur at i ons wer e
appl i ed successf ul l y.

Step 14 Confirm the configuration: Ping your default gateway and the Central Manager
Cisco WAE. If the default gateway or Central Manager Cisco WAE are
unreachable, check your network configuration and make appropriate corrections.
Note In the following commands, replace the x with your assigned pod number
podx- BR- wae# ping 10.10.x1.1
podx- BR- wae# ping 10.10.100.24x

Step 15 Verify that the Device is registered to the Central Manager: Type the following
pod1- BR- WAE#sh cms info
Devi ce I d = 904
Cur r ent WAAS Cent r al Manager = 10. 10. 100. 24x
Regi st er ed wi t h WAAS Cent r al Manager = 10. 10. 100. 24x
St at us = Onl i ne
Ti me of l ast conf i g- sync = Fr i J un 20 22: 47: 55
2008

Ser vi ce cms_ce i s r unni ng
Note If the device shows Pending (CM is Busy) retry later, wait a moment and try the show cms
info command again.

.
Complete these steps to verify that all Cisco WAE devices are online in Central Manager.
Step 16 Connect and Login to the Workstation: Connect to the Branch Office Windows
XP workstation and login using the credentials supplied by the instructor.
Step 17 Browse to the Central Manager: Open Internet Explorer from the remote desktop
and browse to the Central Manager Cisco WAE at the URL of
https://10.10.100.24x:8443 (where x is your pod number).
Step 18 Login to the Central Manager: Login using the default credentials
(admin/default). You will see the Central Manager home page.
Step 19 Verify Status of Devices: Click on Manage Devices under My WAN and
verify that devices are online and there are no major alarms.


Task 5: Measurement of Application Performance with Cisco
WAAS enabled
In this task, you will run application optimization tests for windows file transfer and HTTP file
transfer. The response times measured in this task will be compared against the baseline times
taken earlier, which tested native WAN response time. This cold transfer test of Cisco WAAS
will show TCP optimization and application optimization for the first user to request the
content. This will populate the data redundancy elimination (DRE) cache and the CIFS file
cache. The subsequent hot transfer test will measure optimization of requests from the next
user.
Activity Procedure 1: Measure the Optimized CIFS File transfer

Step 1 Disconnect existing CIFS sessions: From client workstation, select Start/Run,
enter cmd to open a command window. Enter net use /delete * to disconnect
any existing CIFS session. When prompted, enter Y to confirm.
Note This is important because Cisco WAAS will not disconnect existing sessions in attempt to
optimize.

Step 2 Verify that the CIFS accelerator is Enabled, Running Normally and Registered
on both Cisco WAEs. From the Data Center Cisco WAE, type the following
entries to begin this step:

pod1- DC- WAE# #show accelerator cifs

.

Accel er at or Li censed Conf i g St at e Oper at i onal St at e
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ci f s Yes Enabl ed Runni ng

CI FS:
Pol i cy Engi ne Conf i g I t em Val ue
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
St at e Regi st er ed
Def aul t Act i on Use Pol i cy
Connect i on Li mi t 750
Ef f ect i ve Li mi t 740
Keepal i ve t i meout 5. 0 seconds
Step 3 From the Branch Office Cisco WAE, type the following entries to complete this
step:
pod1- BR- WAE# #show accelerator cifs

Accel er at or Li censed Conf i g St at e Oper at i onal
St at e
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - -

CI FS:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Step 4 Ensure that the Free Download Manager software has been enabled: If it is not,
double click the button in the system tray. This will allow tracking of the elapsed
file download time.


Step 5 Clear the browser cache
Step 6 From the browser pull down menu select Tools > Internet Options, from the
General tab select Delete Cookies and Delete Files

Step 7 Perform a Cold File Transfer with Cisco WAAS CIFS Acceleration: Browse to
http://10.10.100.100/cifs.html and Select the 15MB.ppt

.

After you click Save be
patient, it may take a little
time to continue.


Step 8 Record the results: Note the elapsed time that it took to complete the Cisco WAAS
cold file transfer. The standard Cisco WAAS optimizations provide a good
reduction in WAN traffic.

Application File size Baseline Time to
transfer
Current Time to
transfer
Wi ndows f i l e copy
( col d)
15MB

Step 9 Prepare for the Hot File Transfer test: Delete the 15MB.ppt from the desktop.
Step 10 Clear the browser cache

.
Step 11 From the browser pull down menu select Tools > Internet Options, from the
General tab select Delete Cookies and Delete Files

Step 12 Perform a Hot File Transfer with Cisco WAAS CIFS Acceleration. Again,
select the 15MB.ppt from http://server/cifs.html as you did in Step 4. You should
see very fast response at the client desktop.


Step 13 Record the results: Note the elapsed time that it took to complete the Cisco WAAS
hot file transfer. Compare the time to transfer against the initial measurements in
Task 1, Activity Procedure 1.

transfer
Current Time to
transfer
( col d)
15MB
( hot )
15MB

.
Activity Procedure 2: Measure the Optimized Web page download
Step 1 Verify that the HTTP accelerator is Enabled, Running Normally and Registered on
both Cisco WAEs: From the Data Center Cisco WAE, type the following entries to
begin this step:
pod1- DC- WAE#show accelerator http
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ht t p Yes Enabl ed Runni ng

CI FS:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
From the Branch Office Cisco WAE, type the following entries to complete this
step:
pod1- BR- WAE# show accelerator http

St at e
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

CI FS:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


Step 2 To verify the optimized HTTP page download performance over the WAN, open
Firefox on the client


Step 4 Perform a Cold load the test webpage: Type http://10.10.100.100/index1.html in
the address field and press Enter.
Step 5 Open the Firebug tool: Select Tools/Firebug/Open Firebug.

.
Note Notice that the firebug window appears at the bottom of the page. Please confirm that it is

Step 6 Record the results: When the download is complete, note, at the bottom of the
Firebug report, the number of requests and the time that it took to download all
objects.


HTTP Web page
downl oad( col d)


Step 8 Hot load the test webpage: Repeat steps 4-5 to perform a hot web page download.
Step 9 Record the results: When the download is complete, again note, at the bottom of
the Firebug report, the number of requests and the time that it took to download all
objects and record them here.

HTTP Web page
downl oad( col d)

HTTP Web page
downl oad( hot )

Step 10 Compare the optimized time to transfer against the initial measurements in Task 1,
Activity Procedure 2.
You have completed cold and hot optimized CIFS file transfers and web page downloads
and recorded the results.

.
Task 6: GUI Monitoring of Cisco WAAS
In this task, you will view the statistics for the traffic requests issued in the previous tasks. You
will use the Central Manager GUI to monitor system-wide performance, as well as the
performance on individual devices.
Step 1 Connect and Login: Connect to the Branch Office Windows XP workstation and
login using the credentials supplied by the instructor.
Step 2 Access the Central Manager GUI: Open Internet Explorer from the remote
desktop and browse to the Central Manager Cisco WAE at the URL of

Step 4 View Statistics: Click Monitor to view the system-wide performance statistics.
Step 5 View Network Traffic Summary: Click the Traffic tab to view a summary of the
traffic that has passed through your Cisco WAAS devices.


Step 6 View Device Status: Choose My WAN and Click Manage Devices and click the
device named podX-BR-WAE

Step 7 Monitor the Device: Click and expand the Monitor option.
Step 8 View Device Statistics: Click Network Traffic Summary Report to view statistics
for an individual Cisco WAE
You have used the Central Manager GUI to monitor system-wide performance as well as
the performance on individual devices.

.
Task 7: CLI Monitoring of Cisco WAAS
will use the CLI to monitor the individual devices.
Step 9 View HTTP Acceleration Statistics: On the Branch Office Cisco WAE type
Show stat accelerator http to view the time saved (in msec) through the HTTP
application optimizer.
podX- BR- WAE#show stat accelerator http

HTTP:
Gl obal St at i st i cs
- - - - - - - - - - - - - - - - -
Ti me Accel er at or was st ar t ed: Sun J un 22 21
19: 02: 35 2008
Ti me St at i st i cs wer e Last Reset / Cl ear ed: Sun J un 22 21
19: 02: 35 2008
Tot al Handl ed Connect i ons: 3413
Tot al Opt i mi zed Connect i ons: 3413
Tot al Connect i ons Handed- of f wi t h Compr essi on Pol i ci es Unchanged: 0
Tot al Dr opped Connect i ons: 0
Cur r ent Act i ve Connect i ons: 0
Cur r ent Pendi ng Connect i ons: 0
Maxi mumAct i ve Connect i ons: 34
Tot al Ti me Saved ( ms) : 42203
Cur r ent Act i ve Connect i ons Fr ee For Fast Connect i on Use: 0
Tot al Connect i ons Handed- of f : 0
Tot al Connect i ons Handed- of f wi t h Compr essi on Pol i ci es Di sabl ed: 0
Tot al Fast Connect i ons: 3086
Maxi mumFast Connect i ons on a Si ngl e Connect i on: 91
Per cent age of Connect i on Ti me Saved: 88
Tot al Round Tr i p Ti me For Al l Connect i ons ( ms) : 5461
Tot al Fast Connect i ons I ni t i at ed by Peer : 0

Step 10 View CIFS Acceleration Statistics: On the Branch Office Cisco WAE type Show
stat accelerator cifs detail to view the connections optimized.
pod3- BR- WAE#show stat accelerator cifs detail
CI FS:
- - - - - - - - - - - - - - - - -
Ti me Accel er at or was st ar t ed: Sun J un 22 21
16: 36: 12 2008
Ti me St at i st i cs wer e Last Reset / Cl ear ed: Sun J un 22 21
16: 36: 12 2008


Number of l ocal r epl y gener at i ng r equest s: 6727
Number of r emot e r epl y gener at i ng r equest s: 3799
Aver age t i me t o gener at e a l ocal r epl y ( msec) : 3
Aver age t i me t o r ecei ve a r emot e r epl y ( msec) : 131

Pol i cy Engi ne St at i st i cs
- - - - - - - - - - - - - - - - - - - - - - - - -
Sessi on t i meout s: 1, Tot al t i meout s: 1
Last keepal i ve r ecei ved 00. 1 Secs ago
Last r egi st r at i on occur r ed 5: 04: 54: 34. 9 Days: Hour s: Mi ns: Secs ago
Hi t s: 1131, Updat e Rel eased: 0
Act i ve Connect i ons: 1, Compl et ed Connect i ons: 1130
Dr ops: 0
Rej ect ed Connect i on Count s Due To: ( Tot al : 0)
Not Regi st er ed : 0, Keepal i ve Ti meout : 0
No Li cense : 0, Load Level : 0
Connect i on Li mi t : 0, Rat e Li mi t : 0
Mi ni mumTFO : 0, Resour ce Manager : 0
Gl obal Conf i g : 0, TFO Li mi t : 0
Ser ver - Si de : 0, DM Deny : 0
No DM Accept : 0

Aut o- Di scover y St at i st i cs
- - - - - - - - - - - - - - - - - - - - - - - - -
Connect i ons queued f or accept : 303
Accept queue add f ai l ur es: 0
AO di scover y successf ul : 303
AO di scover y f ai l ur e: 0
You have used the CLI to monitor individual devices.

.
Lab 2: Confi gure the Ci sco NM-WAE and WCCP
Complete this lab activity to practice what you learned in the related lessons.
Activity Objective
In this activity, you will configure the Network Module WAE and configure WCCP
interception for the Network Module, Branch and Data Center Cisco WAEs. After completing
this activity, you will be able to meet these objectives:
Configure the Cisco NM-WAE
Configure WCCP for network interception
Verify WCCP load balancing
Visual Objective
WAAS Lab Topology
WAN Data Center
WANBr idge
10.10.90.254
10.10.100.24X
FQDN: waas.l ocal
X = your pod number
Cor e WAE 10.10.100.23X
DC Router
WAN: VLAN 201
10.10.200.1X
LAN: 802.1q
VLAN 100: 10.10.100.X
VLAN 110: 10.10.101.X WMS
Windows XP PC
Edge Router
WAN: VLAN 200
10.10.200.X
LAN: 802.1q
VLAN X0: 10.10.X0.1
VLAN X1: 10.10.X1.1
Internal (NME-WAE)
VLAN X2: 10.10.X2.1
Edge NME-WAE
VLAN X2: 10.10.X2.230
Edge WAE 674
10.10.X1.230
VLAN X1
Branch Office
V
B
2
V
B
3
V
B
1
Cisco WAAS
Mobile client
Cisco WAAS
Mobil e Server
SOHO/Mobi le User
Wi ndows XP PC
Wi ndows 2003
Ser ver (CIFS, FTP,
HTTP, HTTPS Vi deo)
Exchange Ser ver
2003 (MAPI)


VLAN Configuration
WAN Branch Office
VLAN 201 VLAN 200
VLAN X3
VLAN X0
VLAN X1
VLAN 100
Data Center

Required Resources
These are the resources and equipment required to complete this activity:
Four Cisco WAEs (three appliances, one Cisco NM-WAE network module)
One Windows workstation
Access to the central server
Task 1: Configure the Branch Office Cisco Network Module
WAE
In this task, you will configure the Branch Office Cisco NM-WAE using the setup script.
Activity Procedure: Configure the Branch Office Cisco NM-WAE using the setup
script.
Step 1 Connect to the Branch Office router console port.

.
Step 2 Type admin for the username and cisco for the password.
User Access Ver i f i cat i on

User name: admin
Passwor d: cisco
Step 3 Enter enable mode, and examine the router hardware to verify that the Cisco NM-
WAE is present and recognized by the router.
podx- br - r t r > enable
Passwor d: cisco
podx- br - r t r # show hardware
(portions removed)
1 ci sco I nt egr at ed Ser vi ce Engi ne( s)
Ci sco Wi de Ar ea Appl i cat i on Ser vi ces Sof t war e 4. 1. 0 ( b1 J ul
22 2007 05: 55: 52) i n sl ot 1
Step 4 Configure or verify the router internal interface dedicated to the Cisco NM-WAE.
podx- br - r t r # config term
podx- br - r t r ( conf i g) # int integrated-service-engine 1/0
podx- br - r t r ( conf i g- i f ) # ip address 10.10.x2.1 255.255.255.0
podx- br - r t r ( conf i g- i f ) # service-module ip address 10.10.x2.230
255.255.255.0
podx- br - r t r ( conf i g- i f ) # service-module ip default-gateway
10.10.x2.1
podx- br - r t r ( conf i g- i f ) # no shut
podx- br - r t r ( conf i g- i f ) # end
Step 5 Verify that the service module is running and the Cisco Wide-Area Application
Services (WAAS) software is running.
podx- br - r t r # service-module integrated-service-engine 1/0
status
Ser vi ce Modul e i s Ci sco I nt egr at ed- Ser vi ce- Engi ne1/ 0
Ser vi ce Modul e suppor t s sessi on vi a TTY l i ne 66
Ser vi ce Modul e i s i n St eady st at e
Get t i ng st at us f r omt he Ser vi ce Modul e, pl ease wai t . .


Ci sco Wi de Ar ea Appl i cat i on Ser vi ces Sof t war e 4. 1. 0 ( b1 J ul
22 2007 05: 55: 52)
Rest ar t ed at Fr i J un 7 08: 47: 25 2007
Step 6 Connect to the Cisco NM-WAE console using the router CLI.
podx- br - r t r # service-module integrated-service-engine 1/0
session
Step 7 You may need to press the Enter key one or two times to see the login prompt. Type
admin for the username and default for the password.
Ci sco Wi de Ar ea Appl i cat i on Ser vi ces Engi ne Consol e

User name: admin
Passwor d: default
Step 8 Erase the current configuration.
podx- nm- wae# restore factory-default
Thi s command wi l l wi pe out al l of dat a on t he di sks and wi pe
out al l CLI conf i gur at i ons you have ever made. I f t he box i s
i n eval uat i on per i od of cer t ai n pr oduct , t he eval uat i on
pr ocess wi l l not be af f ect ed t hough. I f t he devi ce i s i n a
t i med eval uat i on per i od f or opt i onal sof t war e, t he eval uat i on
pr ocess wi l l not be af f ect ed.
I t i s hi ghl y r ecommended t hat you st op al l act i ve ser vi ces
and/ or ensur e user t r af f i c i s not bei ng ser vi ced by t hi s
devi ce bef or e t hi s command i s r un.
Step 9 Type yes to proceed.
Ar e you sur e you want t o go ahead?[ yes/ no] yes
Step 10 Type yes and press the Enter key again to confirm the restoration of factory default
settings. The Cisco NM-WAE will automatically reboot.
Ar e you r eal l y sur e you want t o go ahead?[ yes/ no] yes
Step 11 After the reload process is complete, the Cisco WAE CLI setup script prompt will
appear for 30 seconds, allowing initial device configuration to be applied. Press the
Enter key when you see this prompt.
WAAS boot : det ect ed no saved syst emconf i gur at i on
Do you want t o ent er basi c conf i gur at i on now?
hi t RETURN t o ent er basi c conf i gur at i on: <Enter>
admi n passwor d: default
r e- ent er passwor d: default

.
Note If you miss the setup script prompt, log in using the default username admin and the
password default, and then type setup at the prompt.
Step 12 Answer no to change the above defaults and continue the configuration press n and
select enter.

I nt er cept i on Met hod: WCCP
Management I nt er f ace: Gi gabi t Et her net 1/ 0
Aut osense: yes
DHCP: yes
Ti mezone: UTC 0 0
[ y] : n
1
Step 13 Enter the Central Manager IP address of 10.10.100.24X
Step 14 Select other interception method.
St ep 3: Sel ect i nt er cept i on met hod ( i nl i ne| wccp| ot her ) [ wccp] :
other
Note You will manually configure WCCP later in this lab
Step 15 Choose a primary interface: Select 1 to choose GigabitEthernet 1/0
Sel ect i nt er f ace t o conf i gur e as management i nt er f ace:



Note Any time you see an x listed below, use your pod number to replace the x
St ep 5: Domai n name ser ver I P: 10. 10. 100. 101
St ep 6: Domai n name: waas. l ocal
St ep 7: Ent er host name[ none] : podX- nm- wae
St ep 8: Conf i gur e NTP [ none] : 10. 10. 100. 101
St ep 9: Ent er t i mezone [ UTC 0 0] : pst - 8 0
St ep 10:

The pr oduct suppor t s t he f ol l owi ng l i censes:
1. Tr anspor t
2. Ent er pr i se
The l i cense i s not conf i gur ed. I t i s r ecommended t o pur chase
Ent er pr i se l i cense.

Pl ease ent er t he l i cense name opt i on i f you pur chased i t
al r eady: 2

Step 17 Review the configuration, and then type y to accept and apply the configuration
Note There is no prompt for interface configuration because the NME-WAE interface
configuration was done from the router.

cent r al - manager addr ess 10. 10. 100. 24X
i p name- ser ver 10. 10. 100. 101

.
host name pod1- nm- wae
nt p ser ver 10. 10. 100. 101
cl ock t i mezone pst - 8 0
cms enabl e

Step 18 Press y to apply configurations.

Press any key to continue..


Complete these steps to verify your configuration:
Step 19 If you are not already logged on, log on to the Branch Office Cisco NM-WAE.
Ci sco Wi de Ar ea Appl i cat i on Ser vi ces Engi ne Consol e

User name: admin
Passwor d: default


podx- nm- wae#
Step 20 Ping your default gateway and Central Manager Cisco WAE (where x is your pod
number). If the default gateway or Central Manager Cisco WAE are unreachable,
verify your network configuration.
podx- nm- wae# ping 10.10.x2.1
podx- nm- wae# ping 10.10.100.24x

Step 21 Verify that the Central Management Service is running: Type the following
entry to complete this step:
pod1- nm- wae#sho cms info
Devi ce I d = 1317
Cur r ent WAAS Cent r al Manager = 10. 10. 100. 241
Regi st er ed wi t h WAAS Cent r al Manager = 10. 10. 100. 241
St at us = Onl i ne
Ti me of l ast conf i g- sync = Wed Aug 13 00: 26: 38
2008

Ser vi ce cms_ce i s r unni ng
Note If your NM-WAE status does not show Online contact the instructor.
Step 22 Disconnect from the Cisco NM-WAE by pressing Ctrl-Shift-6 and then x.

.
pod7- nm- wae# < Ctrl-Shift-6 t hen x>
pod7-br-rtr#


Task 2: Verify Activation of the Cisco NM-WAE
In this task, you will activate the Cisco NM-WAE using Central Manager.
Step 1 Connect to the Branch Office Windows XP workstation and login using the
credentials supplied by the instructor.
Step 2 Open Internet Explorer from the remote desktop and browse to the Central Manager
Cisco WAE at the URL of https://10.10.100.24x:8443 (where x is your pod
number).
Step 3 Login using the default credentials (admin/default). You will see the Central
Manager home page.
Step 4 Select Manage Devices.
Step 5 Notice that all Cisco WAEs including the Cisco NM-WAE are Online.

You have verified that Cisco NM-WAE is online.

.
Task 3: Configure WCCP for Network Interception
In this task, you will configure WCCPv2 using the Cisco WAE CLI and router CLI.
Activity Procedure 1: Configure the Branch Office Router and WAEs for WCCPv2
Step 1 Connect to the Branch Office router console port.
admin for the username and cisco for the password if necessary
Step 3 Verify that WCCP is not configured or enabled in your router.
podx- br - r t r # show ip wccp
%WCCP ver si on 2 i s not enabl ed
podx- br - r t r # show running-config | include wccp
podx- br - r t r #
Step 4 Connect to the Branch Office router console port and enable WCCP debugging.
podx- br - r t r # debug ip wccp events
WCCP event s debuggi ng i s on
Step 5 Enter configuration mode, and enable WCCP.
podx- br - r t r ( conf i g) # ip wccp version 2
podx- br - r t r ( conf i g) # ip wccp 61
podx- br - r t r ( conf i g) # end
Step 6 Display the router IP interfaces
podx- br - r t r #sh ip int br
I nt er f ace I P- Addr ess OK? Met hod St at us Pr ot ocol
Gi gabi t Et her net 0/ 0 unassi gned YES manual up up
GigabitEthernet0/0.x0 10.10.x0.1 YES manual up up
GigabitEthernet0/0.x1 10.10.x1.1 YES manual up up
Gi gabi t Et her net 0/ 1 unassi gned YES NVRAM up up
Gi gabi t Et her net 0/ 1. x3 10. 10. x3. 1 YES manual up up
Gi gabi t Et her net 0/ 1. 200 10. 10. 200. x YES manual up up


I n1/ 0 10. 10. x2. 1 YES manual up up
Step 7 Enter interface commands.
podx- br - r t r ( conf i g) # interface gig0/0.x0 (user LAN interface)
Note Your router might have FastEthernet interfaces rather than Gigabit Ethernet interfaces.
podx- br - r t r ( conf i g- subi f ) # ip wccp 62 redirect in
podx- br - r t r ( conf i g- subi f ) # ip wccp 61 redirect out
podx- br - r t r ( conf i g- subi f ) #exit
podx- br - r t r ( conf i g) #int gigabitEthernet 0/0.x1
podx- br - r t r ( conf i g- subi f ) # interface gig0/0.x1 (user WAE
interface)
podx- br - r t r ( conf i g- subi f ) # ip wccp redirect exclude in
podx- br - r t r ( conf i g) # interface integrated-service-engine 1/0
podx- br - r t r ( conf i g- i f ) # ip wccp redirect exclude in
Caution This configuration is largely academic and leverages outbound interception in order to
display the use and necessity of the redirect exclude in statement on the WAE interfaces
recommended practice is to use inbound interception on both LAN and WAN interfaces and
to load balance based on source address with WCCPv2 service group 61 inbound on the
LAN facing interface.
Note You will be using WCCP Group 62 to redirect traffic leaving the branch. This will load
balance per destination IP. The objective is to load balance across the Branch WAE and the
Network Module WAE for traffic being routed to and from multiple destinations in the Data
Center.
Step 8 Exit config mode and save the configuration.
podx- br - r t r ( conf i g- subi f ) # end
podx- br - r t r # copy run start
Step 9 Examine the output of the following command. Verify the location of the WCCP
service groups and the redirect exclude. Use show running-config to verify the
correct service group numbers.
podx- br - r t r # sh ip wccp interfaces
WCCP i nt er f ace conf i gur at i on:

.
Gi gabi t Et her net 0/ 0. x0
Out put ser vi ces: 1
I nput ser vi ces: 1
Mcast ser vi ces: 0
Excl ude I n: FALSE

Gi gabi t Et her net 0/ 0. x1
Mcast ser vi ces: 0
Excl ude I n: TRUE

I nt egr at ed- Ser vi ce- Engi ne1/ 0
Mcast ser vi ces: 0
Excl ude I n: TRUE
Step 10 Connect to the Branch Office Cisco WAE console port, and disable the inline
interface groups.
podx- br - wae# config
podx- br - wae( conf i g) # interface inlinegroup 2/0
podx- br - wae( conf i g- i f ) # shut
podx- br - wae( conf i g- i f ) # exit
podx- br - wae( conf i g) # interface inlinegroup 2/1
podx- br - wae( conf i g- i f ) # shut
podx- br - wae( conf i g- i f ) # exit
Step 11 Type the following commands to configure WCCP.
podx- br - wae( conf i g) # wccp version 2
podx- br - wae( conf i g) # wccp router-list 1 10.10.x1.1
podx- br - wae( conf i g) # wccp tcp-promiscuous router-list-num 1
WCCP conf i gur at i on f or TCP Pr omi scuous ser vi ce 61
succeeded. WCCP conf i gur at i on f or TCP Pr omi scuous
succeeded. Pl ease r emember t o conf i gur e WCCP ser vi ce 61 and 62
on t he cor r espondi ng r out er


podx- br - wae( conf i g) # end
podx- br - wae# copy run start
Step 12 Connect (return) to the Branch Office Router console.
Step 13 Review the debug messages on the router console, they will be similar to these
(notice the notice the Service Acquired messages, and the Router View messages
indicating usable WCCP clients).
*J an 17 15: 00: 17. 862: %WCCP- 5- SERVI CEFOUND: Ser vi ce 61
acqui r ed on WCCP cl i ent 10. 10. 81. 230
*J an 17 15: 00: 17. 862: WCCP- EVNT: D61: Bui l t new r out er vi ew: 1
r out er s, 1 usabl e
WCCP cl i ent s, change # 00000002
*J an 17 15: 00: 17. 862: %WCCP- 5- SERVI CEFOUND: Ser vi ce 62
acqui r ed on WCCP cl i ent 10. 10. 81. 230
Step 14 Hit Enter twice at the branch router prompt to connect to the existing session with
the Branch Office Cisco NM-WAE, type the following commands to configure
WCCP.
Tip If there is not an existing session with the NM-WAE on the Branch router connect with the
podx-br-rtr#service-module integrated-Service-Engine 1/0 session command
podx- br - r t r # <ENTER><ENTER>

User name: admin
Passwor d: default
podx- nm- wae# config
podx- nm- wae( conf i g) # wccp version 2
podx- nm- wae( conf i g) # wccp router-list 1 10.10.x2.1

.
podx- nm- wae( conf i g) # wccp tcp-promiscuous router-list-num 1
podx- nm- wae( conf i g) # end
podx- nm- wae# copy run start
Step 15 Press CTRL-Shift-6-X to return to the router console.


Activity Procedure 2: Configure the Data Center for WCCPv2
Step 1 Connect to the Data Center router console port.
admin for the username, and cisco for the password.
Step 3 Enter enable mode on the router.
podx- dc- r t r # enable
Passwor d: cisco
Step 4 Verify that WCCP is not configured or enabled in your router.
podx- dc- r t r # show ip wccp
%WCCP ver si on 2 i s not enabl ed
podx- dc- r t r # show running-config | include wccp
podx- dc- r t r #
Step 5 If WCCP is configured, remove all commands related to WCCP from the
configuration.
Step 6 Display and identify the routers LAN and WAN interfaces
podx- dc- r t r #sh ip int br
I nt er f ace I P- Addr ess OK? Met hod St at us Pr ot ocol
Gi gabi t Et her net 0/ 0 10. 10. 100. x YES manual up up
Gi gabi t Et her net 0/ 1 unassi gned YES NVRAM up up
Gi gabi t Et her net 0/ 1. 110 10. 10. 110. x YES manual up up
Gi gabi t Et her net 0/ 1. 201 10. 10. 200. 1x YES manual up up

Step 7 Enter configuration mode and type the WCCP global and interface commands.
podx- dc- r t r # config term
podx- dc- r t r ( conf i g) # ip wccp version 2
podx- dc- r t r ( conf i g) # ip wccp 61
podx- dc- r t r ( conf i g) # ip wccp 62
podx- dc- r t r ( conf i g) # interface gig0/0 (Data Center LAN interface)

.
Note Your router might have FA interfaces rather than Gigabit Ethernet interfaces. Use the
#show ip interface brief command to determine the LAN and WAN facing interfaces.
podx- dc- r t r ( conf i g- i f ) # ip wccp 62 redirect in
podx- dc- r t r ( conf i g- i f ) # interface gig0/1.201
podx- dc- r t r ( conf i g- i f ) # ip wccp 61 redirect in
Step 8 Save the configuration.
podx- dc- r t r ( conf i g- i f ) # end
podx- dc- r t r # copy run start

Step 9 Use the show running config interface command to verify WCCP configuration.
podx- dc- r t r # sh run int gig 0/0
i p addr ess 10. 10. 100. x 255. 255. 255. 0
i p wccp 62 r edi r ect i n

podx- dc- r t r # sh run int gig 0/1.201
i p addr ess 10. 10. 200. 1x 255. 255. 255. 0
i p wccp 61 r edi r ect i n
Step 10 Connect to the Datacenter WAE console port, and disable the inline interface
groups.
Note If the Data Center Cisco WAE has an inline interface card, enabled for inline interception,
follow these steps before configuring WCCP to disable inline interception. WCCP and Inline
Interception cannot coexist in the same Cisco WAE.
podx- dc- wae# config
podx- dc- wae( conf i g) # interface inlinegroup 1/0
podx- dc- wae( conf i g- i f ) # shut
podx- dc- wae( conf i g- i f ) # exit
podx- dc- wae( conf i g) # interface inlinegroup 1/1
podx- dc- wae( conf i g- i f ) # shut
podx- dc- wae( conf i g- i f ) # exit


Step 11 Connect to the Data Center Cisco WAE console port, and type the following
commands to configure WCCP (where x is your pod number).
Note You will be configuring GRE encapsulation for Cisco WAE-to-Router traffic via Negotiated
Return. See the note below if you get error messages due to the presence of an inline
interface card enabled for inline interception.
podx- dc- wae( conf i g) # wccp version 2
podx- dc- wae( conf i g) # wccp router-list 1 10.10.100.x
podx- dc- wae( conf i g) # wccp tcp-promiscuous router-list-num 1
WCCP conf i gur at i on f or TCP Pr omi scuous ser vi ce 61
succeeded. WCCP conf i gur at i on f or TCP Pr omi scuous
succeeded. Pl ease r emember t o conf i gur e WCCP ser vi ce 61 and 62
on t he cor r espondi ng r out er
podx- dc- wae( conf i g) # exit

Step 12 Display the current egress method for the Data Center Cisco WAE.
podx-dc-wae#show egress-methods

I nt er cept met hod : WCCP

TCP Pr omi scuous 61 :
WCCP negot i at ed r et ur n met hod : WCCP GRE
Egr ess Met hod Egr ess Met hod
Dest i nat i on Conf i gur ed Used
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
any I P For war di ng I P For war di ng

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

.
any I P For war di ng I P For war di ng

I nt er cept met hod : Gener i c L2
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
any not conf i gur abl e I P For war di ng

Step 13 Configure the negotiated return egress method on the Data Center Cisco WAE.
podx- dc- wae# config
podx- dc- wae( conf i g) # egress-method negotiated-return
intercept-method wccp
podx- dc- wae( conf i g) # end
podx- dc- wae# copy run start
Step 14 Display the new egress method for the Data Center Cisco WAE.
podx- dc1- wae#show egress-methods

I nt er cept met hod : WCCP


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
any WCCP Negot i at ed Ret ur n WCCP GRE


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


any WCCP Negot i at ed Ret ur n WCCP GRE

I nt er cept met hod : Gener i c L2

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
any not conf i gur abl e I P For war di ng

Step 15 On the Data Center Cisco WAE, examine the output of the following command.
Verify that all necessary WCCP services are configured.
podx- dc- wae#sh wccp services
Ser vi ces conf i gur ed on t hi s Fi l e Engi ne
TCP Pr omi scuous 61
TCP Pr omi scuous 62
Verify that all necessary WCCP services are enabled, and the negotiated return
method is GRE.
pod1- dc- wae#sh wccp services detail

Ser vi ce Det ai l s f or TCP Pr omi scuous 61 Ser vi ce
Ser vi ce Enabl ed : Yes
Ser vi ce Pr i or i t y : 34
Ser vi ce Pr ot ocol : 6
Appl i cat i on : Unknown
Ser vi ce Fl ags ( i n Hex) : 501
Ser vi ce Por t s : 0 0 0 0
: 0 0 0 0
Secur i t y Enabl ed f or Ser vi ce : No
Mul t i cast Enabl ed f or Ser vi ce : No
Wei ght f or t hi s Web- CE : 0
Negot i at ed f or war di ng met hod : GRE
Negot i at ed assi gnment met hod : HASH
Negot i at ed r et ur n met hod : GRE

.
Recei ved Val ues:
Sour ce I P mask ( i n Hex) : 0
Dest i nat i on I P mask ( i n Hex) : 0
Sour ce Por t mask ( i n Hex) : 0
Dest i nat i on Por t mask ( i n Hex) : 0
Cal cul at ed Val ues:

Ser vi ce Det ai l s f or TCP Pr omi scuous 62 Ser vi ce
Ser vi ce Enabl ed : Yes
Ser vi ce Pr i or i t y : 34
Ser vi ce Pr ot ocol : 6
Appl i cat i on : Unknown
Ser vi ce Fl ags ( i n Hex) : 502
Ser vi ce Por t s : 0 0 0 0
: 0 0 0 0
Secur i t y Enabl ed f or Ser vi ce : No
Mul t i cast Enabl ed f or Ser vi ce : No
Wei ght f or t hi s Web- CE : 0
Negot i at ed f or war di ng met hod : GRE
Negot i at ed assi gnment met hod : HASH
Negot i at ed r et ur n met hod : GRE
Recei ved Val ues:
Cal cul at ed Val ues:


podx- dc- wae# sh wccp routers
Which router IP address is the Cisco WAE using to send packets to the router?
___________________________________________________________________
Step 18 On the Data Center router CLI, examine the output of the following command, and
answer these questions.
podx- dc- r t r # show ip wccp

Which service identifiers are listed?

How many cache engines have been identified?

How many routers have been identified?

Are packets being redirected?

Step 19 On the Data Center router CLI, examine the output of the following command. Does
the output of the command agree with the router configuration?
podx- dc- r t r # show ip wccp interfaces
WCCP i nt er f ace conf i gur at i on:
Gi gabi t Et her net 0/ 0
Mcast ser vi ces: 0
Excl ude I n: FALSE

Gi gabi t Et her net 0/ 1
Mcast ser vi ces: 0
Excl ude I n: FALSE
Step 20 From the Branch Office Cisco NM-WAE, execute these commands and use their
output to answer the questions that follow.

.
podx- nm- wae# show wccp routers
Which router(s) was WCCP registration attempted with?

Is any router not seeing the WAE?

podx- nm- wae# show wccp services
Which services are configured on the WAE?

What are the differences between these services?

Step 21 Conduct some simple testing to validate that WCCP is working properly (Repeat the
performance testing that was done for Inline mode in Lab 2-1).
Step 22 From the Branch Office router, execute this command to obtain a quick snapshot of
the router WCCP status and discovered clients (Cisco WAEs).
podx- br - r t r # sh ip wccp 61 view
WCCP Rout er s I nf or med of :
10. 10. 200. x

WCCP Cl i ent s Vi si bl e:
10. 10. x1. 230
10. 10. x2. 230

WCCP Cl i ent s NOT Vi si bl e:
-none-


Activity Procedure 3: Verify WCCPv2 Load Balancing
Step 1 Connect to your Data Center router and issue the following command to clear
statistics for WCCP.
podx- dc- r t r # clear ip wccp
Step 2 Repeat the command at the Branch router.
podx- br - r t r # clear ip wccp
Step 3 Connect to your Data Center WAE and issue the following command to clear cache
and all statistics.
podx- dc- wae# clear cache dre
TFO appl i cat i on needs t o be r est ar t ed ( al l exi st i ng
connect i ons wi l l be r eset , al ar ms may be r ai sed and syst emmay
r eboot i f r equi r ed) .
Do you want t o Cont i nue? [ yes/ no] yes
Rest ar t i ng pr ocesses.
Cl ear i ng DRE cache
Cl ear i ng DRE st at i st i cs
Done. No r eboot was r equi r ed.
podx- dc- wae# clear statistics all
Cl ear i ng DRE st at i st i cs
Step 4 Repeat the previous step at the Branch WAE and the Network Module WAE.
Step 5 Log in to the Client PC and browse to WAAS HTTP Page at
http://10.10.100.100/http.html

.
Step 6 From the Client PC, initiate a file download from the DC Server. Use the 15MB PPT
file.

Step 7 Return to the Branch Office router console.
Step 8 While the file is transferring, use the show ip wccp 62 detail command to determine
which Cisco WAE (Branch Cisco WAE or Cisco NM-WAE) is being used to
redirect the file transfer being optimized. Be sure to specify the WCCP service
group 62 as this is the group is being used to identify optimized traffic leaving
the branch.
Note Notice the Packet s s/ w Redi r ect ed: counter output of the command. One of the
WAEs will show the counter incrementing at a greater rate than the other this is the WAE
that is optimizing the flow. Use the IP addresses in the WCCP Cl i ent I D section of the
output to identify the optimizing WAE for the connection. The example below shows the
Network Module WAE as the WAE used to optimize this particular connection.
Note You may see different results in your lab, in terms of the WAE being selected for
optimization in your case. The highlighted counters may be different.


Step 9 While the file is being transferred, navigate to theManage Devices page on your
Central Manager GUI and select the Central Manager (podx-cm-wae). Click on
the Telnet button to initiate a telnet connection to the WAE.

Step 10 Login to the WAE in the telnet session and issue the show tech-support command
twice in order to generate enough output and enough packets to test.

.
Complete these steps to verify your configuration:
Step 11 Connect to your Branch Router and verify that both the Branch WAE and the
Network Module WAE are being used for traffic redirection and optimization (the
Packets s/w Redirected: counters should increase for both WAEs in the output of
the command).
podx- br - r t r # sh ip wccp 61 detail
WCCP Cl i ent i nf or mat i on:
WCCP Cl i ent I D: 10. 10. x2. 230
Pr ot ocol Ver si on: 2. 0
St at e: Usabl e
I ni t i al Hash I nf o: 00000000000000000000000000000000
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Assi gned Hash I nf o: 00000000000000000000000000000000
Hash Al l ot ment : 128 ( 50. 00%)
Packet s s/ w Redi r ect ed: 2304
Connect Ti me: 03: 53: 43
Bypassed Packet s
Pr ocess: 0
Fast : 0
CEF: 0

WCCP Cl i ent I D: 10. 10. x1. 230
St at e: Usabl e
I ni t i al Hash I nf o: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
00000000000000000000000000000000
Assi gned Hash I nf o: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
00000000000000000000000000000000
Hash Al l ot ment : 128 ( 50. 00%)


Bypassed Packet s
Pr ocess: 0
Fast : 0
CEF: 0
Note The previous output shows the Branch WAE optimizing the management GUI connections,
and the Network Module WAE optimizing the file transfers. You may see a different load
balancing where the different connections are optimized by different WAEs.

podx- br - r t r # show ip wccp 62 detail
WCCP Cl i ent i nf or mat i on:
WCCP Cl i ent I D: 10. 10. x2. 230
St at e: Usabl e
I ni t i al Hash I nf o: 00000000000000000000000000000000
Assi gned Hash I nf o: 00000000000000000000000000000000
Hash Al l ot ment : 128 ( 50. 00%)
Bypassed Packet s
Pr ocess: 0
Fast : 0
CEF: 0

WCCP Cl i ent I D: 10. 10. 81. 230
St at e: Usabl e
I ni t i al Hash I nf o: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
00000000000000000000000000000000
Assi gned Hash I nf o: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
00000000000000000000000000000000
Hash Al l ot ment : 128 ( 50. 00%)

.
Bypassed Packet s
Pr ocess: 0
Fast : 0
CEF: 0


Lab 3: Confi gure Custom Appl i cati on Traffi c
Pol i ci es
Complete this lab activity to practice what you learned in the related lessons.
Activity Objective
In this activity, you will configure default application policies, create and apply a nonstandard
policy, create a device group, and configure and verify disk encryption. After completing this
activity, you will be able to meet these objectives:
Create and apply a nonstandard application traffic policy for a custom application
Verify the configuration and functionality of custom application settings
Visual Objective
WAAS Lab Topology
WAN Data Center
WANBr idge
10.10.90.254
10.10.100.24X
FQDN: waas.l ocal
X = your pod number
Cor e WAE 10.10.100.23X
DC Router
WAN: VLAN 201
10.10.200.1X
LAN: 802.1q
VLAN 100: 10.10.100.X
VLAN 110: 10.10.101.X WMS
Windows XP PC
Edge Router
WAN: VLAN 200
10.10.200.X
LAN: 802.1q
VLAN X0: 10.10.X0.1
VLAN X1: 10.10.X1.1
Internal (NME-WAE)
VLAN X2: 10.10.X2.1
Edge NME-WAE
VLAN X2: 10.10.X2.230
Edge WAE 674
10.10.X1.230
VLAN X1
Branch Office
V
B
2
V
B
3
V
B
1
Cisco WAAS
Mobile client
Cisco WAAS
Mobil e Server
SOHO/Mobi le User
Wi ndows XP PC
Wi ndows 2003
Ser ver (CIFS, FTP,
HTTP, HTTPS Vi deo)
Exchange Ser ver
2003 (MAPI)

.
VLAN Configuration
WAN Branch Office
VLAN 201 VLAN 200
VLAN X3
VLAN X0
VLAN X1
VLAN 100
Data Center

Required Resources
Three Cisco WAEs
One Application Server


Task 1: Configuring a New Application Policy
In this task, you will use the Central Manager to configure a new Application policy for your
company custom web application running on TCP port 8808.
Step 1 Connect to the Branch Office Windows XP workstation and log in using the
Cisco WAE at the URL of https://10.10.100.24X:8443 (where X is your pod
number).
Step 3 Log in using the default credentials (admin/default). You will see the Central
Manager home page.
Step 4 From Central Manager select My WAN > Manage Device Groups > and select the
AllDevicesGroup
Step 5 Select Restore default Application Policies

Step 6 Answer OK to apply the default Application Policy for all devices in the group
Step 7 Configure a new application. Choose Configure > Acceleration > Applications
and click the Create button.

.

Step 8 Assign the name HR-Web to the new Application and check the Enable Statistics
checkbox, which will allow the CM to gather statistics for the custom application.
Step 9 Select Submit


Step 10 Assign the Application to the All Devices device group. Click the Assign Device
Groups tab and then click the blue X to assign the new Application to the device
group.
Step 11 Click Submit.

Step 12 Verify that the policy is applied to the All Devices Group and that the green check
bubble is under the Assigned field.

.

Step 13 Configure the policy definition; select Configure > Acceleration > Policy
Definitions. Click the Create button.

Step 14 Choose HR-Web from the Application list box and click New Classifier to create a
new Application Classifier.


Step 15 The Application Classifier window appears. Enter HR-Class in the Name field and
click Create to create a new application match condition.

Step 16 OK Answer to navigate away from the page
Step 17 Enter the server IP address of 10.10.100.100 in the Destination IP address field and
8808 in the Destination Port Start and Destination End fields.
Step 18 Click Update Classifier.
Note The custom web application is running on http://10.10.100.100:8808.

.
Step 19 Click Submit to accept the Application Classifier Settings.

Step 20 The Application Policy screen reappears. From the Action list box, choose Full
Optimization if it is not already the selected action.
Step 21 Choose HTTP from the Accelerate list box to use the HTTP AO for the custom
application. Click Submit.


Step 22 Verify that the HR-Class Classifier and the HR-Web Application appear.

.
Step 23 Select Home

Step 24 Use the Central Manager to monitor HR-Web. Choose Monitor >Optimization >
Network Traffic Application Mix and scroll to the second page for the HR-
Application.

Step 25 Verify that the HTTP accelerator is Enabled, Running Normally, and Registered on
all Cisco WAEs: From the Data Center Cisco WAE, enter the following entries to
begin the verification process:
podX- dc- wae#show acc http

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

HTTP:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Note: If your HTTP
state does not show
Registered, contact
your instructor.



.
Step 26 From the Branch Office Cisco WAE, enter the following entries to finish the
verification process:
podX- br - wae#show acc http

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

HTTP:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Step 27 To verify the optimized HTTP page download performance over the WAN, open
Firefox on the client.
Step 28 To clear the web cache, choose Tools > Clear Private Data, or press

Note: If your HTTP
state does not show
Registered, contact
your instructor.


Step 29 To test the test webpage, enter http://10.10.100.100:8808 in the address field and
press enter.

Step 30 Select Tools > Firebug > Open Firebug. to open the Firebug tool.

.
Note Notice that the Firebug window appears at the bottom of the page. Please confirm that it is

Step 31 When the download is complete, notice at the bottom of the Firebug report, the
number of requests and the time that it took to download all objects. Record the
results in the table:
HTTP Web page
downl oad

will use the Central Manager GUI to monitor system-wide performance.
Step 1 Connect to the Branch Office Windows XP workstation and log in using the
Cisco WAE by entering the URL of https://10.10.100.24x:8443 (where X is your
pod number).
Step 3 Log in using the default credentials (admin/default). You will see the Central
Manager home page.


Step 4 Click Monitor to view the system-wide performance statistics.
Step 5 Click Network Traffic Application Mix and scroll to the second page for the HR-
Application.
Note It may take a few minutes for the report to update due to the systemdatafeed.pollrate setting,
which is set to 5 minutes. This is the frequency of reporting from the Cisco WAEs to the CM.

.

Step 1 View connection statistics to see the acceleration applied to connections on port
8808 requests. Look for the H showing that the HTTP AO is being used. If you do
not see the H, contact your instructor.
pod1- br - wae# show stat conn closed server-port 8808
D: DRE, L: LZ, T: TCP Opt i mi zat i on,
C: CI FS, E: EPM, G: GENERI C, H: HTTP, M: MAPI , N: NFS, V: VI DEO

ConnI D Sour ce I P: Por t Dest I P: Por t Peer I D Accel er at or
5008 10. 10. 10. 10: 1087 10. 10. 100. 100: 8808 0: 14: 5e: 95: af : a3 T, D, L, H

5035 10. 10. 10. 10: 1086 10. 10. 100. 100: 8808 0: 14: 5e: 95: af : a3 T, D, L, H


Step 2 On the Branch Office Cisco WAE, enter the following command to view the time
saved (in msec) through the HTTP application optimizer. (Your numbers will vary):
podX- br - wae#show stat acc http

HTTP:
- - - - - - - - - - - - - - - - -
Ti me Accel er at or was st ar t ed: Thu Aug 7
Ti me St at i st i cs wer e Last Reset / Cl ear ed: Thu Aug 7
Tot al Ti me Saved ( ms) : 420
Cur r ent Act i ve Connect i ons Fr ee For Fast Connect i on Use: 0
Tot al Connect i ons Handed- of f : 0
Tot al Connect i ons Handed- of f wi t h Compr essi on Pol i ci es Di sabl ed: 0
Tot al Fast Connect i ons: 409
Maxi mumFast Connect i ons on a Si ngl e Connect i on: 100
Per cent age of Connect i on Ti me Saved: 97
Tot al Round Tr i p Ti me For Al l Connect i ons ( ms) : 10
Tot al Fast Connect i ons I ni t i at ed by Peer : 0

Step 3 On the Branch Office Cisco WAE, enter show stat application HR-Web to view
the connections optimized.
pod1- br - wae#show stat app HR-Web
Appl i cat i on I nbound Out bound
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

HR- Web
Opt TCP Pl us:
Byt es 7882 5904
Packet s 87 72
Or i g TCP Pl us:
Byt es 7285 6854
Packet s 66 60
Opt Pr eposi t i on:
Byt es 0 0

.
Packet s 0 0
Or i g Pr eposi t i on:
Byt es 0 0
Packet s 0 0
Opt TCP Onl y:
Byt es 0 0
Packet s 0 0
Or i g TCP Onl y:
Byt es 0 0
Packet s 0 0
I nt er nal Cl i ent :
Byt es 0 0
Packet s 0 0
I nt er nal Ser ver :
Byt es 0 0
Packet s 0 0
PT Cl i ent :
Byt es 0
Packet s 0
PT Ser ver :
Byt es 0
Packet s 0
Act i ve Compl et ed
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Opt TCP Pl us 0 13
Pr eposi t i on 0 0
Opt TCP Onl y 0 0
I nt er nal Cl i ent 0 0
I nt er nal Ser ver 0 0
PT No Peer 0 0
PT Conf i g 0 0
PT I nt er medi at e 0 0
PT_Ot her 0 0


Lab 4: Confi guri ng Ci sco WAAS NFS
Accel erati on
Activity Objective
In this activity, you will configure a Cisco WAAS implementation for NFS Acceleration with
three Cisco WAEs, two routers, and WAN emulation. After completing this activity, you will
be able to meet these objectives:
Create a baseline from an unoptimized NFS application response
Test NFS application response with Cisco WAAS enabled
Monitor Cisco WAAS NFS operation using the Central Manager GUI
Monitor Cisco WAAS NFS operation using the Command Line Interface (CLI)
Visual Objective
WAAS Lab Topology
WAN Data Center
WANBr idge
10.10.90.254
10.10.100.24X
FQDN: waas.l ocal
X = your pod number
Cor e WAE 10.10.100.23X
DC Router
WAN: VLAN 201
10.10.200.1X
LAN: 802.1q
VLAN 100: 10.10.100.X
VLAN 110: 10.10.101.X WMS
Windows XP PC
Edge Router
WAN: VLAN 200
10.10.200.X
LAN: 802.1q
VLAN X0: 10.10.X0.1
VLAN X1: 10.10.X1.1
Internal (NME-WAE)
VLAN X2: 10.10.X2.1
Edge NME-WAE
VLAN X2: 10.10.X2.230
Edge WAE 674
10.10.X1.230
VLAN X1
Branch Office
V
B
2
V
B
3
V
B
1
Cisco WAAS
Mobile client
Cisco WAAS
Mobil e Server
SOHO/Mobi le User
Wi ndows XP PC
Wi ndows 2003
Ser ver (CIFS, FTP,
HTTP, HTTPS Vi deo)
Exchange Ser ver
2003 (MAPI)

.
VLAN Configuration
WAN Branch Office
VLAN 201 VLAN 200
VLAN X3
VLAN X0
VLAN X1
VLAN 100
Data Center

Required Resources
Three Cisco WAEs
One Linux Client for NFS file access
One Application Server with NFS File shares
In this task, you will create baseline measurements for the NFS application. This baseline will
be used to test relative application performance without Cisco WAAS. All tests will be
performed from the MS Windows workstation shown in the lab diagram. Attach to it by
clicking the green Desktop oval..


Activity Procedure 1: Determine the Baseline Measurement for a Network File
System (NFS) File Transfer
Password: cisco
Note If you do not see at least 80ms latency, contact the instructor

Step 3 Connect to the Branch Office Router console port.
Step 4 Login to Branch Office Router: You may need to press the Enter key one or two
times to see the login prompt.
Username: admin
Password: cisco

.
Step 5 Disable WCCP interception on the Branch Office Router:
podx- br - r t r ( conf i g) # no ip wccp 61
podx- br - r t r ( conf i g) # no ip wccp 62

Step 6 From the Client PC open the Putty Application on the desktop: double click the
Putty icon on the desktop

Step 7 Provide the information to connect to the NFS client:
Type the IP address 10.10.x0.20 in the Hostname or IP address Field
and select SSH as the Protocol and click open to connect to the NFS
client.


.
Step 8 Login to the NFS client:
Login as nfsx where x is your pod number. The password is cisco
l ogi n as: nfs1
nf s1@10. 10. 10. 20' s passwor d: cisco
Li nux nf s1 2. 6. 18- 5- 686 #1 SMP Tue Dec 18 21: 24: 20 UTC 2007
i 686

The pr ogr ams i ncl uded wi t h t he Debi an GNU/ Li nux syst emar e
f r ee sof t war e;
t he exact di st r i but i on t er ms f or each pr ogr amar e descr i bed i n
t he
i ndi vi dual f i l es i n / usr / shar e/ doc/ */ copyr i ght .

Debi an GNU/ Li nux comes wi t h ABSOLUTELY NO WARRANTY, t o t he
ext ent
per mi t t ed by appl i cabl e l aw.
You have new mai l .
Last l ogi n: Mon Sep 15 15: 17: 47 2008 f r om10. 10. 10. 10

Step 9 Verify that the server share folder is not already mounted using the sudo
command:
nf s1@nf s1: ~$ sudo umount /home/share

Step 10 Mount the server share folder using the sudo command:
nf s1@nf s1: ~$ sudo mount /home/share

Step 11 Display the contents of the local default path using the LS command:
nf s1@nf s1: ~$ ls
Document s Mai l Pr oj ect s

Step 12 Display the contents of the remote /home/share directory using the LS
command:
nf s1@nf s1: ~$ ls -l /home/share


t ot al 86780
- r w- r - - r - - 1 r oot 1002 11153408 2008- 08- 11 14: 03 10MB. doc
- r w- r - - r - - 1 r oot 1002 15978496 2008- 08- 11 14: 04 15MB. ppt
- r w- r - - r - - 1 r oot 1002 6288384 2008- 08- 11 14: 04 6MB.ppt
- r w- r - - r - - 1 r oot 1002 55328580 2008- 08- 11 13: 42 l i nux- 2. 6. 21. t ar . gz

Step 13 Perform a file transfer from the NFS server to the local client using a
destination filename of nfs-native.ppt and record your results below

transfer
NFS f i l e copy
( Nat i ve)
6MB
nfs1@nfs1:~$time cp /home/share/6MB.ppt nfs-native.ppt
real 1m0.831s
user 0m0. 000s
sys 0m0. 156s
Step 14 Verify that the file has been copied to the local PC using the LS command
nf s1@nf s1: ~$ ls
nfs-native.ppt Document s Mai l Pr oj ect s
Step 15 Prepare to test NFS application response with WAAS enabled by un mounting
the server resource using the UMOUNT command:
Note Notice the command is umount not unmount.
Note Keep the Putty session open to the NFS client, it will be used in the following Procedures.
You have completed unoptimized NFS file transfer viewed the baseline results.

.
Task 2: WAAS Optimization for NFS Applications
In this task, you will re-enable in-line interception and perform cold and hot measurements for
the NFS application. All tests will be performed from the MS Windows workstation shown
in the lab diagram.

Activity Procedure 1: Test cold NFS application response with Cisco WAAS enabled
Step 1 Re-enable WCCP interception on the Branch Office Router:

Step 2 Clear the DRE cache on the Branch WAE to ensure a cold DRE cache hit:

podx- BR- WAE#clear cache DRE

Rest ar t i ng pr ocesses

Step 3 Verify the NFS accelerator is enabled and functioning properly:
podx- BR- WAE#Show accel er at or nf s

pod7- BR- WAE#show acc nf s

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


nf s Yes Enabl ed Runni ng

NFS:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

If your NFS Accelerator State is not Enabled and Running
contact your instructor

Step 4 From the Putty session on the client PC, mount the server share folder using
the sudo command:

Step 5 Display the contents of the local default path using the LS command:
nf s1@nf s1: ~$ ls
Document s Mai l nf s- nat i ve. ppt Pr oj ect s

Step 6 Display the contents of the remote /home/share directory using the LS
command:
nf s1@nf s1: ~$ ls -l /home/share
t ot al 86780
- r w- r - - r - - 1 r oot 1002 11153408 2008- 08- 11 14: 03 10MB. doc
- r w- r - - r - - 1 r oot 1002 15978496 2008- 08- 11 14: 04 15MB. ppt
- r w- r - - r - - 1 r oot 1002 6288384 2008- 08- 11 14: 04 6MB.ppt
- r w- r - - r - - 1 r oot 1002 55328580 2008- 08- 11 13: 42 l i nux- 2. 6. 21. t ar . gz

destination filename of nfs-ao1.ppt and record your results below

.
transfer
Cold Time to transfer
NFS f i l e copy
( col d)
6MB

nf s1@nf s1: ~$time cp /home/share/6MB.ppt nfs-ao1.ppt
real 0m30.459s
user 0m0. 000s
sys 0m0. 136s

nf s1@nf s1: ~$ ls
Document s Mai l nf s- ao1. ppt nfs-ao1.ppt Pr oj ect s

Step 9 Prepare to test NFS application response with WAAS enabled and the DRE
cache populated by un mounting the server resource using the UMOUNT
command:
You have completed a cold NFS file transfer with WAAS enabled and compared the results
to the baseline results.

Activity Procedure 2: Test hot NFS application response with Cisco WAAS enabled

Step 1 From the Putty session on the client PC, mount the server share folder using the
sudo command:


destination filename of nfs-ao2.ppt and record your results below
transfer
Cold Time to transfer Hot Time to transfer
NFS f i l e copy
( hot )
6MB

nf s1@nf s1: ~$time cp /home/share/6MB.ppt nfs-ao2.ppt
real 0m5.361s
user 0m0. 000s
sys 0m0. 196s

nf s1@nf s1: ~$ ls
Document s Mai l nf s- ao1. ppt nf s- ao2. ppt nfs-native.ppt
Pr oj ect s

You have completed a hot NFS file transfer with WAAS enabled and compared the results
to the baseline results.


.
Step 4 View Statistics: Click Monitor > Acceleration > NFS Acceleration Report to
view the system-wide NFS performance statistics.

Step 5 View Branch WAE Status: Choose My WAN and Click Manage Devices and
click the device named podX-BR-WAE


Step 7 View Device Statistics: Click Connection Statistics to view statistics for an
individual Cisco WAE
Note Look for Destination Port 2049, which is NFS and view the Original bytes vs. Optimized
Bytes, this difference between the bytes is the savings across the WAN for this individual
connection.
Step 8 View Detailed Connection Statistics: Click the magnifying glass icon
to view live detailed information about the connection. Notice the size of the original Reads
and Write bytes versus the optimized bytes that traversed the WAN.

.

Step 9

Step 1 View NFS connections: On the Branch Office Cisco WAE type Show statistics
connection closed
Note The show stat connection all command can be used, but it will only show active
connections. The show stat connection all command will only work when the NFS file
transfer is in process.
podX- BR- WAE#show stat connection closed

podx- BR- WAE#show stat connection closed



ConnI D Sour ce I P: Por t Dest I P: Por t Peer I D Accel
630 10.10.10.20:971 10.10.100.102:2049 0:14:5e:95:af:a3 TNDL
634 10. 10. 10. 20: 957 10. 10. 100. 102: 2049 0: 14: 5e: 95: af : a3 TNDL

Step 2 View the NFS application Savings: On the Branch Office Cisco WAE type show
stat application savings File-System

podx- BR- WAE#show stat application savings File-System
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Fi l e- Syst em
TCP Pl us:
Byt es 7223748 19296919
Packet s 8104 14862
Compr essi on Rat i o 2: 1 40: 1
Pr eposi t i on:
Byt es 0 0
Packet s 0 0
TCP Onl y:
Byt es 0 0
Packet s 0 0
Over al l :
Byt es 7223748 19296919
Packet s 8104 14862

Step 3 View NFS Acceleration Statistics: On the Branch Office Cisco WAE type Show
stat accelerator nfs detail to view the connections optimized.
podx- BR- WAE#show stat accelerator nfs detail

.

NFS:
- - - - - - - - - - - - - - - - -
Ti me Accel er at or was st ar t ed: Tue Sep 16
07: 56: 19 2008
Ti me St at i st i cs wer e Last Reset / Cl ear ed: Tue Sep 16
07: 56: 19 2008
Tot al RPC Cal l s per Aut hent i cat i on Fl avor : 7
1140 0 0
Tot al RPC Cal l s wi t h Unknown Aut hent i cat i on Fl avor : 0
Tot al RPC Cal l s per NFS Ver si on: 0
0 0 1138 0
Tot al RPC Cal l s wi t h Unknown NFS Ver si on: 0
Tot al Request s: 1138
Tot al Local Repl i es: 891
Per cent age of Request s Ser ved Local l y: 78
Per cent age of Request s Ser ved Remot el y: 22
Aver age Ti me t o Gener at e Local READ Repl y ( ms) : 1179
Aver age Ti me t o Gener at e Local WRI TE Repl y ( ms) : 0
Aver age Ti me t o Gener at e Local Repl y ( ms) : 421
Aver age Ti me t o Recei ve Remot e Repl y ( ms) : 1331

- - - - - - - - - - - - - - - - - - - - - - - - -


Last r egi st r at i on occur r ed 08: 47: 13. 5 Hour s: Mi ns: Secs ago
Dr ops: 0
No DM Accept : 0

- - - - - - - - - - - - - - - - - - - - - - - - -

Lab cleanup
Step 1 Delete local ppt files from the NFS client:
nf s1@nf s1: ~$ r m- f *. ppt

Step 2 Display directory listing on local NFS client to verify deletion of ppt files using
the LS command:
nf s1@nf s1: ~$ l s
Document s Mai l Pr oj ect s

.
Step 3 Unmount the server resource using the UMOUNT command:


Lab 5: Confi guri ng Ci sco WAAS MAPI
Accel erati on
Activity Objective
In this activity, you will configure a Cisco WAAS implementation for MAPI Acceleration with
three Cisco WAEs, two routers, and WAN emulation. After completing this activity, you will
be able to meet these objectives:
Create a baseline from an unoptimized MAPI application response
Test MAPI application response with Cisco WAAS enabled
Monitor Cisco WAAS MAPI operation using the Central Manager GUI
Monitor Cisco WAAS MAPI operation using the Command Line Interface (CLI)
Visual Objective
WAAS Lab Topology
WAN Data Center
WANBr idge
10.10.90.254
10.10.100.24X
FQDN: waas.l ocal
X = your pod number
Cor e WAE 10.10.100.23X
DC Router
WAN: VLAN 201
10.10.200.1X
LAN: 802.1q
VLAN 100: 10.10.100.X
VLAN 110: 10.10.101.X WMS
Windows XP PC
Edge Router
WAN: VLAN 200
10.10.200.X
LAN: 802.1q
VLAN X0: 10.10.X0.1
VLAN X1: 10.10.X1.1
Internal (NME-WAE)
VLAN X2: 10.10.X2.1
Edge NME-WAE
VLAN X2: 10.10.X2.230
Edge WAE 674
10.10.X1.230
VLAN X1
Branch Office
V
B
2
V
B
3
V
B
1
Cisco WAAS
Mobile client
Cisco WAAS
Mobil e Server
SOHO/Mobi le User
Wi ndows XP PC
Wi ndows 2003
Ser ver (CIFS, FTP,
HTTP, HTTPS Vi deo)
Exchange Ser ver
2003 (MAPI)

.
VLAN Configuration
WAN Branch Office
VLAN 201 VLAN 200
VLAN X3
VLAN X0
VLAN X1
VLAN 100
Data Center

Required Resources
Three Cisco WAEs
One Microsoft Windows workstation with Outlook 2003 configured
One Microsoft Exchange Server with client Mailboxes and Public folders
In this task, you will create baseline measurements for the MAPI application. This baseline
will be used to test relative application performance without Cisco WAAS. All tests will be
performed from the MS Windows workstation shown in the lab diagram. Attach to it by
clicking the green Desktop oval..


Activity Procedure 1: Determine the Baseline Measurement for a Microsoft Outlook
and Exchange over Messaging Application Programming Interface (MAPI)
Password: cisco
Note If you do not see at least 80ms latency, contact the instructor

Step 3 Connect to the Branch WAE console port: Click the green Console oval next to
the Central Manager icon.
Step 4 Login to Branch WAE: You may need to press the Enter key one or two times to
see the login prompt.
Username: admin
Password: default

.
Ci sco Wi de Ar ea Appl i cat i on Ser vi ces Appl i cat i on Engi ne
Consol e

User name: admin
Passwor d: default

Devi ce i s conf i gur ed wi t h a ( wel l known) def aul t
user name/ passwor d
f or ease of i ni t i al conf i gur at i on. Thi s def aul t
user name/ passwor d
shoul d be changed i n or der t o avoi d unwant ed access t o t he
devi ce.



Step 5 Disable WCCPv2 interception on the Branch Router:
podx- br - r t r #conf t
podx- br - r t r ( conf i g) #no ip wccp 61
podx- br - r t r ( conf i g) #end

Step 6 From the Client PC open the Outlook Application on the desktop: double click
the Outlook icon on the desktop

Note You may be prompted for the Outlook 2003 startup, if so, continue with step 7. If you are
taken directly to your Outlook 2003 inbox, continue with step 15.
Step 7 On the Outlook 2003 startup screen click Next:

.
Step 8 On the Account configuration screen, click Next.

Step 9 On the Email Accounts screen, select Microsoft Exchange Server and click Next


Step 10 On the Exchange Server Settings Screen, type exchange in the Microsoft
Exchange Server field and podX in the Username field, where X is your pod
number. Click Next to continue.

Step 11 A Connect window will appear, prompting for a username and password. The
username is podx and the password is podx where x is your pod number.
Click the Remember my password box and click OK.

.
Step 12 If another connect prompt appears, verify the username is podx and the
password is podx, where x is your pod number. Click the Remember my
password box and click OK.

Step 13 On the Congratulations Page, click Finish.


Step 14 When Outlook first opens, you will be prompted for your name and initials,
type Podx for name and Px for initials, where x is your pod number:

Step 15 If there are any existing emails in your inbox, delete them:

Step 16 Compose an new email to Administrator and attach the 5MB.ppt file from your
My Documents folder and click Send.

.

Step 17 Record the amount of time it takes for the Sending Message 1 of 1 message to
disappear. (It should take about 90 seconds)

transfer
Out l ook emai l
send
( nat i ve
5MB


Step 18 View your inbox for a mail message from the Administrator. There is a policy on
the Administrators inbox that will immediately reply with an email when email
messages are received. The message contains a 1MB.ppt attachment to increase
MAPI traffic.

.

Step 19 Delete All mail messages and close Outlook.

You have completed unoptimized MAPI email transfer and experienced slow message
processing.

Task 2: WAAS Acceleration for Outlook Applications
In this task, you will re-enable in-line interception and perform cold and hot measurements for
the MAPI application. All tests will be performed from the MS Windows workstation
shown in the lab diagram.

Activity Procedure 1: Test cold MAPI application response with Cisco WAAS
enabled
Step 1 Re-enable WCCPv2 interception on the Branch Router:


podx- br - r t r #conf t
podx- br - r t r ( conf i g) #end

Step 2 Clear the DRE cache on the Branch WAE to ensure a cold DRE cache hit:

podx- BR- WAE#clear cache DRE

Rest ar t i ng pr ocesses

Step 3 Verify the EPM and MAPI accelerators are enabled and functioning properly:
podx- BR- WAE#Show accel er at or
St at e
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
epm Yes Enabled Running
mapi Yes Enabled Running
nf s Yes Enabl ed Runni ng
vi deo No Enabl ed Shut down
waf s- cor e Yes Di sabl ed Shut down
waf s- edge Yes Di sabl ed Shut down
Note If your EPM or MAPI Accelerator State is not Enabled and Running contact your instructor

.



disappear. You should notice it takes noticeably less time to for the email message
to send. (It should take about 55 seconds)
transfer
Cold Time to transfer
Out l ook emai l
send
( col d)
5MB
Step 7

MAPI traffic. This time you should see the email from the administrator much
sooner.
Note If you do not see the message immediately, click the Send/Receive button on the toolbar.

.
Step 9 View MAPI connections and verify acceleration: On the Branch Office Cisco
WAE type Show statistics connection all and look for the
podX- BR- WAE#show stat connection all



775 10.10.10.10:1549 10.10.100.101:1126 0:14:5e:95:af:a3 TMDL

Step 10 Delete All mail messages and close Outlook.
You have completed a cold MAPI file transfer with WAAS enabled and compared the
results to the baseline results.


Activity Procedure 2: Test hot MAPI application response with Cisco WAAS enabled


.

disappear. This time, it is almost an immediate completion of the message
transfer, this is due to the population of the DRE database from the previous cold
test of MAPI. (It should take about 10 seconds)
transfer
Cold Time to transfer Hot Time to
transfer
Out l ook emai l
send( hot )
5MB
Step 4


MAPI traffic.
Note If you do not see the message immediately, click the Send/Receive button on the toolbar.

.

Step 6 DO NOT CLOSE OUTLOOK: leaving it open will allow us to view the existing
connection for the last file transfer.

You have completed a hot MAPI file transfer with WAAS enabled and compared the
results to the baseline results.



Step 4 View Statistics: Click Monitor > Acceleration > MAPI Acceleration Report to
view the system-wide MAPI performance statistics.

Step 5 View Branch WAE Status: Choose My WAN and Click Manage Devices and
click the device named podX-BR-WAE

.

Step 7 View Device Statistics: Click Connection Statistics to view statistics for an
individual Cisco WAE
Note Look for the mail icon to indicate MAPI accelerated connections.
Step 8 View Detailed Connection Statistics: Click the magnifying glass icon
to view live detailed information about the connection. Notice the size of the original Reads
and Write bytes versus the optimized bytes that traversed the WAN.



Step 1 View MAPI connections: On the Branch Office Cisco WAE type Show statistics
connection all
podX- BR- WAE#show stat connection all



775 10.10.10.10:1549 10.10.100.101:1126 0:14:5e:95:af:a3 TMDL
View the MAPI application Savings: On the Branch Office Cisco WAE type show stat
application savings Email-and-Messaging

podx- BR- WAE#show st at app sav Emai l - and- Messagi ng
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Emai l - and- Messagi ng
TCP Pl us:
Byt es 1591966 17757454
Packet s 7428 10284
Pr eposi t i on:
Byt es 0 0
Packet s 0 0
TCP Onl y:
Byt es 0 0
Packet s 0 0

.
Over al l :
Byt es 1591966 17757454
Packet s 7428 10284

Step 2 View MAPI Acceleration Statistics: On the Branch Office Cisco WAE type
Show stat accelerator mapi detail to view the connections optimized.
podx- BR- WAE#show stat accelerator mapi detail
MAPI :
- - - - - - - - - - - - - - - - -
Ti me Accel er at or was st ar t ed: Sun Sep 14
07: 56: 20 2008
Ti me St at i st i cs wer e Last Reset / Cl ear ed: Sun Sep 14
07: 56: 20 2008
number of synch get buf f er : 230
Mi ni mumSynch Get Buf f er Si ze: 31680
Maxi mumSynch Get Buf f er Si ze: 31680


Aver age Synch Get Buf f er Si ze: 31680
Read st r eamNumber : 10
Mi ni mumr ead st r eamBuf f er Si ze: 31744
Maxi mumr ead st r eamBuf f er Si ze: 31744
Aver age r ead st r eamBuf f er Si ze: 31744
Mi ni mumaccumul at ed r ead ahead dat a Si ze: 0
Maxi mumaccumul at ed r ead ahead dat a Si ze: 0
Aver age accumul at ed r ead ahead dat a Si ze: 0
Local r esponse number : 1057
Aver age l ocal r esponse t i me: 22310
Remot e r esponse number : 493
Aver age r emot e r esponse t i me: 110808
Cur r ent 2K Accel er at ed Connect i ons: 0
Cur r ent 2K3 Accel er at ed Connect i ons: 1
Cur r ent 2K7 Accel er at ed Connect i ons: 0
Secur ed Connect i ons: 0
Lower t han 2k Connect i ons: 0
Hi gher t han 2k7 Connect i ons: 0

- - - - - - - - - - - - - - - - - - - - - - - - -

.
Last r egi st r at i on occur r ed 10: 56: 32. 1 Hour s: Mi ns: Secs ago
Dr ops: 0
No DM Accept : 0

- - - - - - - - - - - - - - - - - - - - - - - - -
Lab cleanup
Step 1 Delete all emails in the Outlook inbox:


Lab 6: Confi guri ng Wi ndows Server on WAAS
Complete this lab activity to practice enabling and configuring virtual blades on WAAS.
Activity Objective
In this activity, you will enable virtual blades on a WAE and install Windows Server 2008.
After completing this activity, you will be able to meet the following objectives:
Enable virtual blade capability on a WAE
Configure Virtual Blade parameters and learn basic management commands
Connect to the VB console and install and configure Windows Server 2008 core
Visual Objective
WAAS Lab Topology
WAN Data Center
WANBr idge
10.10.90.254
10.10.100.24X
FQDN: waas.l ocal
X = your pod number
Cor e WAE 10.10.100.23X
DC Router
WAN: VLAN 201
10.10.200.1X
LAN: 802.1q
VLAN 100: 10.10.100.X
VLAN 110: 10.10.101.X WMS
Windows XP PC
Edge Router
WAN: VLAN 200
10.10.200.X
LAN: 802.1q
VLAN X0: 10.10.X0.1
VLAN X1: 10.10.X1.1
Internal (NME-WAE)
VLAN X2: 10.10.X2.1
Edge NME-WAE
VLAN X2: 10.10.X2.230
Edge WAE 674
10.10.X1.230
VLAN X1
Branch Office
V
B
2
V
B
3
V
B
1
Cisco WAAS
Mobile client
Cisco WAAS
Mobil e Server
SOHO/Mobi le User
Wi ndows XP PC
Wi ndows 2003
Ser ver (CIFS, FTP,
HTTP, HTTPS Vi deo)
Exchange Ser ver
2003 (MAPI)

.
VLAN Configuration
WAN Branch Office
VLAN 201 VLAN 200
VLAN X3
VLAN X0
VLAN X1
VLAN 100
Data Center

Required Resources
WAE-674 Appliance
Client Workstation
Window Server 2008 ISO image


Task 1: Enable Virtual Blade capability on a WAE and Configure
a Virtual Blade
In this task, you will enable VB capability on a WAE and configure a basic VB, which you will
then start and manage.
Activity Procedure 1
Step 1 Connect to www.labgear.net and login with the credentials provided by your
instructor.
Step 2 From the Labgear interface select the console connection for the branch WAE.

Step 3 Login to the console with the credentials admin / default.
Step 4 From the console CLI Issue theshow license command to ensure the Enterprise and
Virtual Blade licenses are installed and active.
pod7- BR- WAE#sh license
Li cense Name St at us Act i vat i on Dat e Act i vat ed By
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Tr anspor t not act i ve
Ent er pr i se act i ve 08/ 01/ 2008 admi n
Vi deo act i ve 08/ 01/ 2008 admi n
Vi r t ual - Bl ade act i ve 08/ 01/ 2008 admi n

Step 5 From the Labgear interface select the desktop button to launch a remote desktop
session for the Client PC.

Step 6 Login to the client PC with the credentials Administrator / Cisco.

.
Step 7 Browse to the WAAS Central Manager instance in your pod:
https://10.10.100.24X:8443 where X =your pod number
Step 8 Login to Central Manager with the credentials admin / default.

Step 9 Select Login.
Step 10 From Central Manager select My WAN > Manage Devices.

Step 11 Select the device icon to edit the branch WAE podX-BR-WAE, where X =your
pod number.
Step 12 From the navigation pane, chooseAdmin > Virtualization > General Settings.


Step 13 Verify whether the Enable check box is selected.
Step 14 If the check box is already selected skip to Step 22.
Step 15 Select the Enable check box.
Step 16 Select Submit.
Caution You are prompted to confirm that you want to modify guest resources. You will need to
reload the WAE for this to take effect. After the reboot the WAE will have a disk partition and
other resources reserved for virtual blade use. You will not be able to undo this change
unless you restore the WAE from the rescue CD.

Step 17 Click OK.
Step 18 From the Labgear interface select the console connection for the branch WAE.

.
Step 19 Login to the console with the credentials admin / default.
Step 20 From the console CLI Issue theshow disks details command.
pod7- BR- WAE#sh disks details
. . .
Mount ed f i l e syst ems:
MOUNT POI NT TYPE DEVI CE SI ZE I NUSE FREE USE%
/ sw i nt er nal / dev/ sda1 991MB 895MB 96MB 90%
/ swst or e i nt er nal / dev/ sda2 991MB 736MB 255MB 74%
/ st at e i nt er nal / dev/ sda3 7935MB 191MB 7744MB 2%
/ l ocal / l ocal 1 SYSFS / dev/ sda6 22318MB 178MB 22140MB 0%
. . . / l ocal 1/ spool PRI NTSPOOL / dev/ dat a1/ spool 991MB 32MB 959MB 3%
/ obj 1 CONTENT / dev/ dat a1/ obj 247815MB 130MB 247685MB 0%
/ dr e1 CONTENT / dev/ dat a1/ dr e 247815MB 188MB 247627MB 0%
/ ackq1 i nt er nal / dev/ dat a1/ ackq 1189MB 32MB 1157MB 2%
/ pl z1 i nt er nal / dev/ dat a1/ pl z 3570MB 64MB 3506MB 1%

Step 21 Verify that there is no /vbspace mount point displayed.
Step 22 Reload the WAE and save the configuration.
pod7- BR- WAE#reload
Syst emconf i gur at i on has been modi f i ed. Save?[ yes] :
Pr oceed wi t h r el oad?[ conf i r m] y
Step 23 Monitor the WAE boot and look for the creating filesystem on the device message.
Cr eat i ng f i l esyst emon devi ce [ / dev/ dat a1/ vbsp] . . .


Step 24 When the WAE boot is complete, login with the credentials admin / default.
Step 25 From the console CLI Issue the show disks details command.
pod7- BR- WAE#sh disks details
Mount ed f i l e syst ems:
MOUNT POI NT TYPE DEVI CE SI ZE I NUSE FREE USE%
/ sw i nt er nal / dev/ sda1 991MB 895MB 96MB 90%
/ swst or e i nt er nal / dev/ sda2 991MB 736MB 255MB 74%
/ st at e i nt er nal / dev/ sda3 7935MB 191MB 7744MB 2%
/ l ocal / l ocal 1 SYSFS / dev/ sda6 22318MB 178MB 22140MB 0%
/ vbspace GUEST / dev/ dat a1/ vbsp 203804MB 128MB 203676MB 0%
. . . / l ocal 1/ spool PRI NTSPOOL / dev/ dat a1/ spool 991MB 32MB 959MB 3%
/ obj 1 CONTENT / dev/ dat a1/ obj 145914MB 128MB 145786MB 0%

Syst emi s i ni t i al i zi ng. Pl ease wai t . . .
Step 26 Note the presence of the /vbspace GUEST mount point.
Step 27 From the console CLI issue the show disks details command again to verify that the
system initialization has completed.
Caution Consult with your instructor to ensure that WAN Emulation has been disabled before
attempting this step!
Step 28 Copy the guest OS ISO image to the newly created /vbspace mount point.
pod7- BR- WAE#copy ftp disk 10.10.100.100 /software WoW66.iso
/local1/vbs/WoW66.iso
Step 29 Enter the FTP username and password.
Ent er user name f or r emot e f t p ser ver : administrator
Ent er passwor d f or r emot e f t p ser ver : cisco

Step 30 When the transfer completes, verify the contents of the /local1/vbs directory on the
WAE.
pod7- BR- WAE#cd /local1/vbs
pod7- BR- WAE#dir
si ze t i me of l ast change name

.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
10 Tue J ul 29 17: 19: 44 2008 sampl e. i so
Step 31 Verify VB resources with the show virtualblade command.
pod7- BR- WAE#sh virtual-blade
Vi r t ual - bl ade r esour ces:
VB Memor y: 0Mi B conf i gur ed, 6144Mi B avai l abl e.
VB Di sk space: 0Gi B conf i gur ed, 194Gi B avai l abl e.
/ l ocal 1/ vbs: 2656Mi B used, 201142Mi B avai l abl e
CPU( s) assi gned: 3 4
Vi r t ual - bl ade( s) st at e:
No vi r t ual - bl ades have been conf i gur ed
Step 32 Login to the client PC with the credentials Administrator / Cisco.
Step 33 Browse to the WAAS Central Manager instance in your pod:
https://10.10.100.24X:8443 where X =your pod number
Step 34 Login to Central Manager with the credentials admin / default.
Step 35 From Central Manager select My WAN > Manage Devices.

Step 36 Select the device icon to edit the branch WAE podX-BR-WAE, where X =your
pod number.
Step 37 From the navigation pane, chooseAdmin > Virtualization > Virtual Blades.
Step 38 Select Create in the Virtual Blade Entries window.


Step 39 The Virtual Blade configuration pane is displayed.
Step 40 Configure the following virtual blade system parameters:
1. Type 1 in the Blade Number field. (Optional) Type a brief description of the
virtual blade in the Description field.
2. In the Boot From field select cd-room to boot the virtual blade from a CD
image.
3. In the CD Image fields select disk to read the CD image from an ISO file on
the WAE's hard drive.
4. Type ISO file's path: /local1/vbs/WoW66.iso
5. Enter 10 in the Disk Space field.
6. Enter 1024 in the Memory field.
7. From the Disk Emulation list chooseIDE.
8. Choosert18139 from the NIC Emulation list.
9. Chooseqemu64 from the CPU Emulation list.

.
Step 41 Configure the interface bridge you want to use between the virtual blade and the
physical interfaces on your WAE by doing the following:
1. Click the Add button. The Virtual Interface Add pane is displayed.

2. Enter 1 as the Interface number.
3. Select GigabitEthernet 1/0 as the Bridge Interface.
4. Click the Generate button for the MAC Address field.
5. Click the Add to List button to add the virtual interface to the virtual blade
interface list.
6. Select the virtual interface by clicking its radio button on the display.


Step 42 Click Submit.
Step 43 From the WAE console verify the virtual blade parameters with the show virtual
blade command.
pod7- BR- WAE#sh virtual-blade 1
vi r t ual - bl ade 1
conf i g:
descr i pt i on VB1
memor y 1024
di sk 30
no boot f d- i mage
boot cd- i mage di sk / l ocal 1/ vbs/ WoW66. i so
boot f r omcd- r om
i nt er f ace 1 br i dge Gi gabi t Et her net 1/ 0 mac- addr ess
00: 16: 3E: AB: EC: 04
devi ce cpu qemu64

.
devi ce ni c r t l 8139
devi ce di sk I DE
no aut ost ar t
st at e:
st opped


Task 2: Start Virtual Blade and Begin Windows Server 2008
Core Installation
In this task, you will start the virtual blade and begin the installation of Windows Server 2008
Core.
Step 1 From Central Manager select Admin > Virtualization > Actions.

Step 2 From the Actions pane, click the Start Virtual Blade button.
Step 3 Status should reflect Pending then Check.
Step 4 From the WAE console verify the VB state with the show virtual blade command.
pod7- BR- WAE#sh virtual-blade 1
vi r t ual - bl ade 1
conf i g:
descr i pt i on VB1
memor y 1024
di sk 10
no boot f d- i mage
boot cd- i mage di sk / l ocal 1/ vbs/ WoW66. i so
boot f r omcd- r om
i nt er f ace 1 br i dge Gi gabi t Et her net 1/ 0 mac- addr ess
00: 16: 3E: AB: EC: 04
devi ce cpu qemu64
devi ce ni c r t l 8139

.
devi ce di sk I DE
no aut ost ar t
st at e:
r unni ng
ser i al consol e sessi on i nact i ve
cur r ent cd / l ocal 1/ vbs/ WoW66. i so
cur r ent f l oppy [ not i nser t ed]
Step 5 From the XP Client workstation, launch the VNC Viewer.
Step 6 Enter the IP address and the VB number in the format 10.10.X1.230:1 where X =
your pod number and :1 is the VB number.

Step 7 Click Connect.
Step 8 VNC will connect to the Virtual Blade VGA console.


Step 9 The Windows Server 2008 Core guest OS installation will begin.

.

Step 10 The guest OS installation will reboot several times during the install, allow the guest
OS installation to complete.


Step 11 Click theSend CTRL-ALT-DEL button on the VNC toolbar.

Step 12 Select Other User at the Windows 2008 Server login.

.

Step 13 Select OK at the password must be changed dialog.

Step 14 Enter the username administrator.
Step 15 Leave the first password field blank.
Step 16 Enter the p@ssword1 twice in the second and third password fields.
Step 17 Click the button to login.


Step 18 Select OK at the Your password has been changed dialog.
Step 19 Wait while Windows Server prepares the desktop.

Step 20 The Windows Server 2008 Core implementation loads to a command prompt.
Note There is no GUI in Windows Server 2008 Core.

.
Task 3: Configuring Guest OS Basic Network Settings
In this task, you will configure basic network settings and establish an RDP session to the WAE
Virtual Blade guest OS.
Activity Procedure
Step 1 Use the network services shell netsh command to display the NICs Index.
netsh interface ipv4 show interfaces

Step 2 Verify the number in the IDX column of the Local Area Connection target NIC. Use
this value in the following commands.
Step 3 Set the Static IPv4 Address using the following netsh command syntax and values.
Step 4 netsh interface ipv4 set address name="<ID>" source=static
address=<StaticIP> mask=<SubnetMask> gateway=<DefaultGateway>
1. <ID>=2
2. static address =10.10.X1.231 (where X =your pod number)
3. mask =255.255.255.0
4. gateway =10.10.X1.1 (where X =your pod number)


Step 5 Enable RDP on the core server.
cscript C:\Windows\System32\Scregedit.wsf /ar 0

Step 6 Verify RDP settings.
cscript C:\Windows\System32\Scregedit.wsf /ar /v

.

Step 7 Allow RDP connections from down-level RDP client.
cscript C:\Windows\System32\Scregedit.wsf /cs 0

Step 8 Poke a hole in the firewall to allow RDP Management.
netsh advfirewall firewall set rule group="Remote Desktop" new enable=yes


Step 9 Exit the VNC session.
Step 10 From the Client PC, launch the remote desktop client from Start > Run > mstsc.

Step 11 Select OK.

.
Step 12 Enter the IP address of the Guest OS that you set in step 4 10.10.X1.231, where X
=your pod number.
Step 13 Click the Options button.

Step 14 Select the Remote Desktop General tab.
Step 15 Clear any domain information in the Domain field.


Step 16 Select the Display tab.
Step 17 Change the remote desktop size to 800x600.
Step 18 Click Connect.

.

Step 19 Click theAdministrator user.

Step 20 Enter p@ssword1 in the password field.
Step 21 From the command prompt, display the servers randomly generated hostname with
the hostname command.
hostname
Step 22 Rename the server using the netdom command.
net domr enamecomput er <Comput er Name> / NewName: <NewComput er Name>
1. Use the following format: PODX-VB1, where X =your pod number.
Step 23 Answer yes to override dependencies on a fixed machine name.


Labapp 2001 (Guide)

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Labapp 2001 (Guide)

Загружено:

Авторское право:

Доступные форматы

2008 Cisco Systems, Inc.

All rights reserved 1 of 161

Вам также может понравиться