Application Control Engine Module Getting Started Guide (Software Version A1(2))
Configuring the ACE and Performing Basic VIP Load Balancing
Download this chapter
Configuring the ACE and Performing Basic VIP Load BalancingConfiguring the ACE and Performing Basic VIP Load Balancing
Download the complete book
Cisco Application Control Engine Module Getting Started Guide Book-Length PDF (Software Version 3.0(0)A1(2))Cisco Application Control Engine Module Getting Started Guide Book-Length PDF (Software Version 3.0(0)A1(2)) (PDF - 590 KB)
give_us_feedback

Table Of Contents

Configuring the ACE and Performing Basic VIP Load Balancing

Initially Configuring the ACE

Configuring VLANs for the ACE Using Cisco IOS Software

Sessioning and Logging in to the ACE

Assigning a Name to the ACE

Assigning an IP Address to the ACE

Configuring a Default Route

Configuring Remote Access to the ACE

Accessing the ACE through a Telnet Session

Configuring Basic VIP Load Balancing on the ACE

Configuring Real Servers

Configuring a Server Farm

Configuring the VIP Traffic Policy

Configuring an ACL

Verifying the VIP Load-Balancing Configuration

Where to Go Next


Configuring the ACE and Performing Basic VIP Load Balancing

This chapter provides procedures to configure the ACE to allow traffic and perform basic VIP load balancing. It also includes document references for more detailed configuration information.

Before performing the procedures in this chapter, you should install the ACE in the Catalyst 6500 series switch. For information on how to install the ACE, see the Cisco Application Control Engine Module Installation Note.

This chapter contains the following major sections:

•Initially Configuring the ACE

•Configuring Basic VIP Load Balancing on the ACE

•Where to Go Next

Initially Configuring the ACE

The initial configuration of the ACE allows you to do the following tasks:

•Pass traffic from the supervisor engine in the Catalyst 6500 series switch to the ACE

•Allow network connectivity

•Perform remote management through Telnet

This section describes how to accomplish these tasks:

•Configuring VLANs for the ACE Using Cisco IOS Software

•Sessioning and Logging in to the ACE

•Assigning a Name to the ACE

•Assigning an IP Address to the ACE

•Configuring a Default Route

•Configuring Remote Access to the ACE

•Accessing the ACE through a Telnet Session

Configuring VLANs for the ACE Using Cisco IOS Software

Before the ACE can receive traffic from the supervisor engine in the Catalyst 6500 series switch, you must create VLAN groups on the supervisor engine, and then assign the groups to the ACE. After you configure the VLAN groups on the supervisor engine for the ACE, you can configure the VLAN interfaces on the ACE.

In Cisco IOS software, you can create one or more VLAN groups, and then assign the groups to the ACE. For example, you can assign all the VLANs to one group, or you can create a group for each customer.

You cannot assign the same VLAN to multiple groups; however, you can assign multiple groups to an ACE. VLANs that you want to assign to multiple ACEs, for example, can reside in a separate group from VLANs that are unique to each ACE.

Note Before you begin, contact your network administrator to determine which VLANs and addresses are available for use by the ACE.

To configure the VLANs for the ACE using the Cisco IOS software, perform the following steps:

1. Connect to the supervisor engine to open a session. For example, use Telnet to connect to the supervisor at the IP address 172.19.110.5, enter: 

linux$ telnet 172.19.110.5

User Access Verification


Password: cisco

Router#

2. Assign VLANs to a group by using the svclc vlan-group group_number vlan_range command in configuration mode. You can configure a maximum of 16 VLAN groups on an ACE. For example, to create three VLAN groups, 50 with a VLAN range of 55 to 57, 51 with a VLAN range of 75 to 86, and 52 with a VLAN 100, enter the following commands: 

Router# config

Router(config)# svclc vlan-group 50 55-57

Router(config)# svclc vlan-group 51 70-85

Router(config)# svclc vlan-group 52 100

3. Assign the VLAN groups to the ACE by using the svc module slot_number vlan-group group_number_range command. For example, to assign VLAN-groups 50 and 52 to the ACE in slot 5, and VLAN-group 51 and 52 to the ACE in slot 8, enter: 

Router(config)# svc module 5 vlan-group 50,52

Router(config)# svc module 8 vlan-group 51,52

4. View the group configuration for the ACE and the associated VLANs by using the show svclc vlan-group command. For example, enter: 

Router(config)# exit

Router# show svclc vlan-group

5. View VLAN group numbers for all modules, by using the show svc module command. For example, enter: 

Router# show svc module

Sessioning and Logging in to the ACE

To initially session and log in to the ACE, perform the following steps:

1. Session into the ACE from the supervisor engine by using the session command from the supervisor engine. For example, to session into the ACE in slot 5, enter: 

Router# session slot 5 processor 0

2. At the login prompt, log into the ACE by entering the login username and password. By default, the username and password are admin. For example, enter: 

switch login: admin

Password: admin

You are ready to use the ACE CLI when the following prompt appears: 

switch/Admin#

To change the default login username and password, see the Cisco Application Control Engine Module Administration Guide.

3. Prevent this current session from timing out by using the terminal session-timeout command and setting it to 0. By default, a session on the ACE is automatically logged out after 5 minutes of inactivity. For example, enter: 

switch/Admin# terminal session-timeout 0

4. Disable the inactivity timeout when you log in to the ACE again by using the login timeout command in configuration mode. For example:

a. Access configuration mode by using the configure command in Exec mode. For example, enter: 

switch/Admin# configure

Enter configuration commands, one per line. End with CNTL/Z

switch/Admin(config)#

b. Disable the inactivity timer by setting the login timeout command to 0. For example, enter: 

switch/Admin(config)# login timeout 0

Assigning a Name to the ACE

The hostname is used for the command-line prompts and default configuration filenames. If you establish sessions to multiple devices, the hostname helps you track where you enter commands. By default, the hostname for the ACE is switch.

Change the hostname for the ACE by using the host command. Enter a case-sensitive name that contains from 1 to 32 alphanumeric characters. For example, to change the hostname of the ACE from switch to host1, enter: 

switch/Admin(config)# hostname host1

The prompt appears with the new host name: 

host1/Admin(config)#

Assigning an IP Address to the ACE

After you assign the VLANs to the ACE, you can assign an IP address to the ACE for client connectivity over the network.

Note The ACE requires a route back to the client before it can forward a request to a server. Otherwise, a flow cannot be established.

Use the show vlans command in Exec mode for the Admin context to display the ACE VLANs downloaded from the supervisor engine. Because show commands are available in Exec mode, you can use these commands from any configuration mode by including the do command. For example, enter: 

host1/Admin(config)# do show vlans

Vlans configured on SUP for this module

 vlan55-57 vlan100

To configure a VLAN interface on the ACE and access interface mode to configure the interface attributes, perform the following steps:

1. Access interface configuration mode for the VLAN by using the interface vlan command. For example, to create VLAN 55, enter: 

host1/Admin(config)# interface vlan 55

host1/Admin(config-if)#

2. Assign an IP address to a VLAN interface for client connectivity by using the ip address command. For example, to set the IP address of 172.19.110.8 255.255.255.192 for the ACE, enter: 

host1/Admin(config-if)# ip address 172.19.110.8 255.255.255.192

3. Provide a description for the interface by using the description command. For example, enter: 

host1/Admin(config-if)# description Client side connectivity

4. Enable the interface by using the no shutdown command. For example, enter: 

host1/admin(config-if)# no shutdown

5. Verify that VLAN 55 is up by using the show interface command. For example, enter: 

host1/admin(config-if)# do show interface vlan 55

6. Verify the network connectivity by using the ping command. For example, enter: 

host1/admin(config-if)# do ping 172.19.110.1

7. Display the ARP table by using the show arp command. For example, enter: 

host1/admin(config-if)# do show arp

8. Reenter configuration mode by using the exit command. For example, enter: 

host1/admin(config-if)# exit

host1/admin(config)#

Configuring a Default Route

The default route identifies the IP address where the ACE sends all IP packets for which it does not have a route. To set a default route, use the ip route dest_ip_prefix netmask gateway_ip_address command.

For example, to set the IP address and subnet mask for the default route (0.0.0.0/0) and the default gateway to 172.19.110.1, an address on the same network as VLAN 55, enter: 

host1/Admin(config)# ip route 0.0.0.0 0.0.0.0 172.19.110.1

To display the ACE routing table, use the show ip route command. For example, enter: 

host1/Admin(config)# do show ip route

Configuring Remote Access to the ACE

Before remote network access can occur on the ACE, you must create a configuration that includes the following features:

•A class map to specify the traffic allowed access to an ACE interface

•A policy map to decide what to do with the class-map traffic

•A service policy to apply the policy map to an interface

To configure remote network management, perform the following steps:

1. Create a class map by using the class-map type management command. For example, to create a management type class map named REMOTE_ACCESS that matches any traffic and to access class map configuration mode, enter: 

host1/Admin(config)# class-map type management match-any 
REMOTE_ACCESS

host1/Admin(config-cmap-mgmt)#

2. Provide a description for the class map by using the description command. For example, enter: 

host1/Admin(config-cmap-mgmt)# description Remote access traffic 
match

3. Configure the match protocol that permits network management traffic by using the match protocol command. For example, to permit traffic based on the protocol of SSH, Telnet, and ICMP for any source address, enter: 

host1/Admin(config-cmap-mgmt)# match protocol telnet any

host1/Admin(config-cmap-mgmt)# match protocol ssh any

host1/Admin(config-cmap-mgmt)# match protocol icmp any

4. Reenter configuration mode by using the exit command. For example, enter: 

host1/Admin(config-cmap-mgmt)# exit

host1/Admin(config)#

5. Create a policy map for traffic destined to an ACE interface and access policy map management configuration mode by using the policy-map type management first-match command. For example, to create the REMOTE_MGMT_ALLOW_POLICY policy map, enter: 

host1/Admin(config)# policy-map type management first-match 
REMOTE_MGMT_ALLOW_POLICY

host1/Admin(config-pmap-mgmt)#

6. Apply the class map to this policy and access policy map class configuration mode by using the class command. For example, to apply the previously created REMOTE_ACCESS class map to this policy, enter: 

host1/Admin(config-pmap-mgmt)# class REMOTE_ACCESS

host1/Admin(config-pmap-mgmt-c)#

7. Allow the ACE to receive the configured class map management protocols by using the permit command. For example, enter: 

host1/Admin(config-pmap-mgmt-c)# permit

8. Reenter configuration mode by using the exit command. For example, enter: 

host1/Admin(config-pmap-mgmt-c)# exit

host1/Admin(config-pmap-mgmt)# exit

host1/Admin(config)#

9. Access interface configuration mode for the VLAN to which you want to apply the policy map. For example, access the interface configuration mode for VLAN 55, enter: 

host1/Admin(config)# interface vlan 55

host1/Admin(config-if)#

10. Apply the policy map to the interface by using the service-policy input command. For example, to apply the REMOTE_MGMT_ALLOW_POLICY policy map to the interface, enter: 

host1/Admin(config-if)# service-policy input 
REMOTE_MGMT_ALLOW_POLICY

11. View the applied service policy on the interface by using the show service-policy command. For example, to display the REMOTE_MGMT_ALLOW_POLICY policy applied to the interface, enter: 

host1/Admin(config-if)# do show service-policy 
REMOTE_MGMT_ALLOW_POLICY

12. Save your configuration changes from the running configuration to the startup configuration. 

host1/Admin(config-if)# do copy running-config startup-config

13. Display the running configuration by using the show running-config command. For example, enter: 

host1/Admin# show running-config

Generating configuration....


login timeout 0

hostname host1


class-map type management match-any REMOTE_ACCESS

  10 match protocol telnet any

  20 match protocol ssh any

  30 match protocol icmp any


policy-map type management first-match REMOTE_MGMT_ALLOW_POLICY

  class REMOTE_ACCESS

    permit


interface vlan 55

  ip address 172.19.110.8 255.255.255.192

  description Client side connectivity

  service-policy input REMOTE_MGMT_ALLOW_POLICY

  no shutdown


ip route 0.0.0.0 0.0.0.0 172.19.110.1

Accessing the ACE through a Telnet Session

After you have completed the previous configurations, you should be able to use Telnet to access the ACE using its IP address. To use Telnet to access the ACE, perform the following steps:

1. Connect to the supervisor engine to open another session. For example, enter 

linux$ telnet 172.19.110.5

User Access Verification


Password: cisco

Router#

2. Use Telnet to verify that you can access the ACE interface. For example, to access the ACE from the VLAN IP address of 172.19.110.8, enter: 

Router# telnet 172.19.110.8

Trying 172.19.110.8 ... Open

3. At the prompt, log in to the ACE. Enter the admin login username and the admin password. For example, enter: 

host1 login: admin

Password:

Cisco Application Control Software (ACSW)

TAC support: http://www.cisco.com/tac

Copyright (c) 2002-2006, Cisco Systems, Inc. All rights reserved.

The copyrights to certain works contained herein are owned by

other third parties and are used and distributed under license.

Some parts of this software are covered under the GNU Public

License. A copy of the license is available at

http://www.gnu.org/licenses/gpl.html.

host1/Admin#

4. Display the Telnet session by using the show telnet command. For example, enter: 

host1/Admin# show telnet

Configuring Basic VIP Load Balancing on the ACE

A basic load-balancing configuration allows the ACE to perform the following tasks:

•Match VIP destined traffic flows

•Load balance these flows to real servers on the network

Class maps classify client traffic destined to a VIP address. The ACE load balances traffic to a server farm and selects one of the real servers to respond to the client request.

This section provides the following topics to accomplish these tasks:

•Configuring Real Servers

•Configuring a Server Farm

•Configuring the VIP Traffic Policy

•Configuring an ACL

Configuring Real Servers

Real servers are dedicated physical servers that you typically configure in groups called server farms. These servers provide services to clients, for example, HTTP or XML content. You identify real servers with names and characterize them with IP addresses, connection limits, and weight values.

To configure real servers on the ACE, perform the following steps:

1. Enter configuration mode by using the configure command in Exec mode. For example, enter: 

host/Admin# config  
Enter configuration commands, one per line. End with CNTL/Z

host1/Admin(config)#

2. Create a real server and access real server host configuration mode by using the rserver command. For example, to create a real server named SERVER1 as a host type (the default), enter: 

host1/Admin(config)# rserver SERVER1

host1/Admin(config-rserver-host)#

3. Enter a description of the real server by using the description command. For example, enter: 

host1/Admin(config-rserver-host)# description web-one content 
server

4. Assign the real server IP address in dotted-decimal notation by using the ip address command. For example, to assign the IP address of 192.168.4.11, enter: 

host1/Admin(config-rserver-host)# ip address 192.168.4.11

5. Place the real server in service by using the inservice command. For example, enter: 

host1/Admin(config-rserver-host)# inservice

6. Reenter configuration mode by using the exit command. For example, enter: 

host1/Admin(config-rserver-host)# exit

host1/Admin(config)#

7. Configure additional real servers by repeating Steps 2 through 5. For example, to add a real server named SERVER2 with an IP address of 192.168.4.12, enter: 

host1/Admin(config)# rserver SERVER2

host1/Admin(config-rserver-host)# description web-two content 
server

host1/Admin(config-rserver-host)# ip address 192.168.4.12

host1/Admin(config-rserver-host)# inservice

8. Reenter configuration mode by using the exit command. For example, enter: 

host1/Admin(config-rserver-host)# exit

host1/Admin(config)#

9. Display the configuration of the real servers by using the show running-config rserver command. For example, enter: 

host1/Admin(config)# do show running-config rserver

Configuring a Server Farm

After you create and configure the real servers, add them to a server farm. To create a server farm, perform the following steps:

1. Create a server farm and access server farm host configuration mode by using the serverfarm command. For example, to create a server farm of type host (the default) named SFARM1, enter: 

host1/Admin(config)# serverfarm SFARM1

host1/Admin(config-sfarm-host)#

2. Associate an existing real server with the server farm and enter server farm host real server configuration mode by using the rserver command. For example, to associate SERVER1 real server to the server farm, enter: 

host1/Admin(config-sfarm-host)# rserver SERVER1

host1/Admin(config-sfarm-host-rs)#

3. Place the real server in service by using the inservice command. Otherwise the ACE considers it out of service and the server farm cannot receive or respond to client requests. For example, enter: 

host1/Admin(config-sfarm-host-rs)# inservice

4. Reenter server farm host configuration mode by using the exit command. For example, enter: 

host1/Admin(config-sfarm-host-rs)# exit

host1/Admin(config-sfarm-host)#

5. Associate the SERVER2 real server to the server farm. For example, enter: 

host1/Admin(config-sfarm-host)# rserver SERVER2

host1/Admin(config-sfarm-host-rs)#

6. Place the real server in service. For example, enter: 

host1/Admin(config-sfarm-host-rs)# inservice

7. Reenter configuration mode by using the exit command. For example, enter: 

host1/Admin(config-sfarm-host-rs)# exit

host1/Admin(config-sfarm-host)# exit

host1/Admin(config)#

8. Verify that the real servers appears as operational, even though network connectivity had not been established by using the show rserver command. For example, to display the SERVER1 real server, enter: 

host1/Admin(config)# do show rserver SERVER1

9. Add an interface to allow the ACE to communicate with the real servers by using the interface vlan command. For example, to configure VLAN 57 and access its configuration mode, enter: 

host1/Admin(config)# interface vlan 57

host1/Admin(config-if)#

10. Configure the IP address that is associated with the real server addresses by using the ip address command. For example, to configure the IP address of 192.168.4.1 255.255.255.0, enter: 

host1/Admin(config-if)# ip address 192.168.4.1 255.255.255.0

11. Provide a description for the interface by using the description command. For example, enter: 

host1/Admin(config-if)# description Server-side Interface

12. Enable the interface by using the no shutdown command. For example, enter: 

host1/admin(config-if)# no shutdown

13. Save the running configuration to the startup configuration. For example, enter: 

host1/Admin(config-if)# do copy running-config startup-config

14. Reenter configuration mode by using the exit command. For example, enter: 

host1/Admin(config-if)# exit

host1/Admin(config)#

15. Display how the ACE populates the ARP table with the real server (RSERVER) by using the show arp command. For example, enter: 

host1/Admin(config)# do show arp

Configuring the VIP Traffic Policy

The ACE classifies incoming traffic with class maps that are associated with policy maps to perform an action based on the class map match. The simplest match is server load balancing based on a client's attempt to reach a virtual IP address and port. This type of match is a Layer 3 and Layer 4 traffic policy. It matches only the destination IP address and port and then makes the server load-balancing decision.

To create a VIP traffic policy, perform the following steps:

1. Create a Layer 7 SLB policy map that attempts to match class maps in the order in which they occur for load balancing by using the policy-map type loadbalance first-match command. For example, to create a load balancing policy map named L7_VIP_LB_ORDER_POLICY, enter: 

host1/Admin(config)# policy-map type loadbalance first-match 
L7_VIP_LB_ORDER_POLICY

host1/Admin(config-pmap-lb)#

2. For a simple load-balancing policy, assign the ACE default class map that has an implicit match any statement in it for matching any traffic classification. Use the class class-default command. For example, enter: 

host1/Admin(config-pmap-lb)# class class-default

host1/Admin(config-pmap-lb-c)#

3. Add the server farm to this class by using the serverfarm command. For example, to add the previously created SFARM1 server farm, enter: 

host1/Admin(config-pmap-lb-c)# serverfarm SFARM1

4. Use the exit command to reenter configuration mode. 

host1/Admin(config-pmap-lb-c)# exit

host1/Admin(config-pmap-lb)# exit

host1/Admin(config)#

5. Create a Layer 3 and Layer 4 load-balancing class map by using the class-map command. For example, to create a class map named L4_VIP_ADDRESS_CLASS, enter: 

host1/Admin(config)# class-map L4_VIP_ADDRESS_CLASS

host1/Admin(config-cmap)#

6. Define a virtual IP (VIP) address match statement using the match virtual-address command. For example, to define a match statement for the IP address 172.19.110.9 for any IP protocol, enter: 

host1/Admin(config-cmap)# match virtual-address 172.19.110.9 any

7. Reenter configuration mode by using the exit command. For example, enter: 

host1/Admin(config-cmap)# exit

host1/Admin(config)#

8. Create a Layer 3 and Layer 4 multi-match policy map to direct classified incoming requests to the load-balancing policy map by using the policy-map multi-match command. For example, to create the policy map named L4_LB_VIP_POLICY, enter: 

host1/Admin(config)# policy-map multi-match L4_LB_VIP_POLICY

host1/Admin(config-pmap)#

9. Associate the Layer and Layer 4 class map that defines the VIP address with the policy map by using the class command. For example, to associate the previously created L4_VIP_ADDRESS_CLASS class map, enter 

host1/Admin(config-pmap)# class L4_VIP_ADDRESS_CLASS

host1/Admin(config-pmap-c)#

10. Associate the Layer 7 load-balancing policy map with the Layer 3 and Layer 4 policy map by using the loadbalance command. This association determines the actions that the ACE takes when network traffic matches a class map. For example, to associate the previously created L7_VIP_LB_ORDER_POLICY policy map, enter: 

host1/Admin(config-pmap-c)# loadbalance policy 
L7_VIP_LB_ORDER_POLICY

11. Enable a VIP for load-balancing operations by using the loadbalance vip inservice command. For example, enter: 

host1/Admin(config-pmap-c)# loadbalance vip inservice

12. Reenter configuration mode by using the exit command. For example, enter: 

host1/Admin(config-pmap-c)# exit

host1/Admin(config-pmap)# exit

host1/Admin(config)# exit

13. Access the client-facing interface to which you want to apply the multi-match policy map by using the interface vlan command. For example, to access interface configuration mode for VLAN 55, enter: 

host1/Admin(config)# interface vlan 55

host1/Admin(config-if)#

14. Apply the multi-match policy map by using the service-policy input command. For example, to apply the L4_LB_VIP_POLICY policy map, enter: 

host1/Admin(config-if)# service-policy input L4_LB_VIP_POLICY

15. Reenter configuration mode by using the exit command. For example, enter: 

host1/Admin(config-if)# exit

host1/Admin(config)#

16. Save the running configuration to the startup configuration. 

host1/Admin(config)# do copy running-config startup-config

17. Verify that the ACE will respond to traffic to the VIP address by using the show service-policy command. This command displays whether the VIP state is inservice. For example, to display the service policy state for the L4_LB_VIP_POLICY policy map, enter: 

host1/Admin(config)# do show service-policy L4_LB_VIP_POLICY

Configuring an ACL

An access control list (ACL) provides an extra layer of security on the services that the ACE provides. For traffic destined to a class map that is applied to a multi-match policy map, you must configure an ACL and apply it to an interface. Otherwise, the ACE denies all traffic on the interface.

To configure an ACL, perform the following steps:

1. Create an ACL for the interface by using the access-list command. For example, to create an ACL named ALL for access control on IP traffic through the ACE extended ACL and permit the forwarding of any source IP address to any destination address, enter: 

host1/Admin(config)# access-list ALL extended permit any

2. Access interface configuration mode for the interface configured with the multi-match policy map by using the interface vlan command. For example, to access interface configuration mode for VLAN 55, enter: 

host1/Admin(config)# interface vlan 55

host1/Admin(config-if)#

3. Apply the ACL to the interface by using the access-group input command. For example, to apply the previously created ALL ACL, enter: 

host1/Admin(config-if)# access-group input ALL

4. Reenter Exec mode by using the end command. 

host1/Admin(config-if)# end

host1/Admin#

5. Verify that the ACL is applied and is active by using the show access-list command. For example, enter: 

host1/Admin# show access-list ALL

6. Save the running configuration to the startup configuration. 

host1/Admin# copy running-config startup-config

7. Display the configuration information by using the show running-config command. In this example, the basic load-balancing configuration is bolded. For example, enter: 

host1/Admin# show running-config 

Generating configuration....


login timeout 0

hostname host1


access-list ALL line 10 extended permit any ip any any


rserver SERVER1

  description web-one content server

  ip address 192.168.4.11

  inservice


rserver SERVER2

  description web-two content server

  ip address 192.168.4.12

  inservice


serverfarm SFARM1

  rserver SERVER1

    inservice

  rserver SERVER2

    inservice


class-map type management match-any REMOTE_ACCESS

  10 match protocol telnet any

  20 match protocol ssh any

  30 match protocol icmp any

class-map match-all L4_VIP_ADDRESS_CLASS

  10 match virtual-address 172.19.110.9 any


policy-map type management first-match REMOTE_MGMT_ALLOW_POLICY

  class REMOTE_ACCESS

    permit


policy-map type loadbalance first-match L7_VIP_LB_ORDER_POLICY

  class CLASS-DEFAULT

   serverfarm SFARM1


policy-map multi-match L4_LB_VIP_POLICY

  class L4_VIP_ADDRESS_CLASS

   loadbalance vip inservice

   loadbalance policy L7_VIP_LB_ORDER_POLICY


interface vlan 55

  ip address 172.19.110.8 255.255.255.192

  description Client side connectivity

  access-group input ALL

  service-policy input REMOTE_MGMT_ALLOW_POLICY

  service-policy input L4_LB_VIP_POLICY

  no shutdown

interface vlan 57

  ip address 192.168.4.1 255.255.255.0

  description Server-side Interface

  no shutdown


ip route 0.0.0.0 0.0.0.0 172.19.110.1

Verifying the VIP Load-Balancing Configuration

To verify the load-balancing configuration, use the show service-policy command to display the incrementing of the counters as connections are handled. For example, to display the counters for the L4_LB_VIP_POLICY policy map, enter: 

host1/Admin# show service-policy L4_LB_VIP_POLICY

Interface: vlan 55

  service-policy: L4_LB_VIP_POLICY

    class: L4_VIP_ADDRESS_CLASS

      loadbalance:

        L7 policy: L7_VIP_LB_ORDER_POLICY, VIP state: INSERVICE

        curr conns       : 0         , hit count        : 20

        dropped conns    : 0

        client pkt count : 100       , client byte count: 13000

        server pkt count : 127       , server byte count: 92381

You can also verify access to the real servers by using a Telnet session to connect to the VIP address. If you are able to receive the login and password prompt from the ACE, access to the real servers is available through the VIP address. For example, enter: 

linux$ telnet 172.19.110.9

Trying 172.19.110.9... Open


host1 login: admin

Password:

Where to Go Next

After you have configured the ACE to allow traffic and remote access, and configured it for basic load balancing, you can configure more advanced features on the ACE.

Table 2-1 lists additional advanced ACE features, including document references where you can obtain configuration information. For information on the ACE command-line interface and commands for each mode, see the Cisco Application Control Engine Module Command Reference.

Table 2-1 Additional ACE Features 

Advanced Feature
For more information, see...

Application protocol inspection

Cisco Application Control Engine Module Security Configuration Guide

Chapter 3, Configuring Application Protocol Inspection

Connection persistence using HTTP-cookie, HTTP header, or IP netmask stickiness

Cisco Application Control Engine Module Server Load-Balancing Guide

Chapter 5, Configuring Stickiness

Health monitoring including probes

Cisco Application Control Engine Module Server Load-Balancing Guide

Chapter 4, Configuring Health Monitoring

Layer 7 server load-balancing traffic policy, including class maps and policy maps

Cisco Application Control Engine Module Server Load-Balancing Guide

Chapter 3, Configuring Traffic Policies for Server Load Balancing

Network Address Translation (NAT)

Cisco Application Control Engine Module Security Configuration Guide

Chapter 5, Configuring Network Address Translation

Redundancy

Cisco Application Control Engine Module Administration Guide

Chapter 8, Configuring Redundant ACE Modules

SSL functionality

Cisco Application Control Engine Module SSL Configuration Guide

TCP/IP normalization

Cisco Application Control Engine Module Security Configuration Guide

Chapter 4, Configuring TCP/IP Normalization and IP Reassembly Parameters

User authentication and accounting

Cisco Application Control Engine Module Security Configuration Guide

Chapter 2, Configuring Authentication and Accounting Services

Virtualization and role-based access control (RBAC)

Cisco Application Control Engine Module Virtualization Configuration Guide