P. 1


|Views: 7|Likes:
Published by Derrick Chong

More info:

Published by: Derrick Chong on Jan 02, 2013
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





In this task, you will add a configuration for the real servers within the pod. The Cisco ACE has
administrative connectivity already enabled for the client. You will also create the Cisco
Modular Policy CLI Layer 3 and 4 load-balancing policy maps and class map at the same time
with the quick configuration tools available in the Cisco ACE 4710 Appliance Device
Manager. The Modular Policy CLI classifies incoming traffic with class maps, which are then
used in policy maps to force an action based on the class map match. The simplest type of these
matches is load balancing based on a client’s attempt to reach a virtual IP address. This type of
match is considered Layer 3 because it matches only the destination IP and then makes a load-
balancing decision.

Activity Procedure

Complete these steps:

Step 1

Connect to your client PC.

Step 2

Make a Telnet connection to LAB-OPT-PC context at address 172.16.PC.20 and
roll back the configuration to baseline-mgmt.

Step 3

Connect to the Cisco ACE appliance at through your web
browser and log in with username/password of admin/admin123.

Step 4

View the Lab-OPT-PC context that will be used for the remainder of this lab. You
can double-click your context from Config > Virtual Contexts. When you complete
your changes, click the Deploy Now button at the bottom right of the screen.

Context Name:


Resource Class:



2PC, 4PC

Policy Name:


Management VLAN:


Management IP Address:


Management IP Netmask:

Protocols to Allow:

Select all

Default Gateway IP:


SNMP v2c Community



You might need to synchronize the web configuration to the CLI configuration, using the
Sync button at the bottom of the Config > Virtual Context screen.


Implementing the Cisco ACE Appliance (ACEAP) v1.0

© 2008 Cisco Systems, Inc.

Step 5

Create an Admin user for the Lab-OPT-PC context with the username/password of
Click Admin > Role-Based Access Control (under new context).

© 2008 Cisco Systems, Inc.

Lab Guide 45

Step 6

Open another browser and log into your new context at https://172.16.PC.20 using
the username and password that you just created.


If you failed to add all protocols in step 4, you will not be able to log into the web browser
login for your context.


Implementing the Cisco ACE Appliance (ACEAP) v1.0

© 2008 Cisco Systems, Inc.

Step 7

Add a new interface VLAN4PC to allow the Cisco ACE appliance to communicate
with the real servers. Use IP address for VLAN 4PC.
Click Config > Virtual Contexts > Network > VLAN Intefaces > Click “+”
button to Add.

Step 8

The Cisco Device Manager makes it simple to configure load balancing. Start by
creating a VIP named VIP-150, with IP address 172.16.PC.150. For Protocol,
choose any and assign this to 2PC VLAN. This is done from
Config > Virtual Contexts > Load Balancing > Virtual Server > Add.

© 2008 Cisco Systems, Inc.

Lab Guide 47

Step 9

Before clicking Deploy Now, choose Server Farm New. This will open a new
menu to create a server farm. Create a server farm called WEBFARM.

Step 10 One more step before deploying this VIP is to create rservers. Create five rservers,
using the following convention and details.
LINUX- Port = 80

Real Server Details: rserver LINUX-1

Real Server Details: rserver LINUX-2

Real Server Details: rserver LINUX-3

Real Server Details: rserver LINUX-4

Real Server Details

rserver LINUX-5

Ensure that the servers are inservice. When finished, click Deploy Now.


Implementing the Cisco ACE Appliance (ACEAP) v1.0

© 2008 Cisco Systems, Inc.

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->