Guest

Cisco CSS 11000 Series Content Services Switches

Configuring a Backup Sorry Server for the Cisco CSS 11xxx

Document ID: 12597

Updated: Jan 31, 2006

   Print

Introduction

This document provides a sample configuration that shows you how to set up a backup (failover) server. This configuration is useful when you use only one web server and want to keep the other server as a backup or as a sorry server. Use the primarySorryServer command in order to configure the primary sorry service for a content rule. The Cisco CSS 11xxx Series Content Services Switch directs content requests to the primary sorry server when all the other services are unavailable. You can configure this service to contain content or to provide a drop or redirect message. This service is not used in load balancing.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on these software and hardware versions:

  • CSS Web Network Services (WebNS) Software Release 3.x and later

  • All platforms of CSS 11xxx

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to the Cisco Technical Tips Conventions for more information on document conventions.

Configure

In this section, you are presented with the information to configure the features described in this document.

Note: Use the Command Lookup Tool (registered customers only) to obtain more information on the commands used in this section.

Network Diagram

This document uses this network setup:

css_sorry_server.gif

Configuration

This document uses this configuration:

CSS 11xxx
!
CSS150-4#show run
!Generated on 08/09/2001 19:07:10
!Active version: ap0410017s

configure

!*************************** GLOBAL ***************************
� ip route 0.0.0.0 0.0.0.0 172.17.63.193 1�

!************************* INTERFACE *************************
interface e11
� bridge vlan 10�

interface e12
� bridge vlan 10�

!************************** CIRCUIT **************************
circuit VLAN1

� ip address 172.17.63.246 255.255.255.192�

circuit VLAN10

� ip address 10.10.10.10 255.255.0.0�
���������
!************************** SERVICE **************************
service server1

!--- This is your main server.
������������������ �����
� ip address 10.10.10.11�
� keepalive type tcp�
� port 80�
� active�

service sorry�

!--- This is the server to which you want to default
!--- if the primary fails.�
����������������� 
� ip address 10.10.10.12������������� �������
� keepalive type tcp�
� port 80�
� active�

!*************************** OWNER ***************************
owner Scott�

� content Green�
��� vip address 172.17.63.239�
��� protocol tcp�
��� add service server1�
��� primarySorryServer sorry
    
!--- This is important here.
 
��� active�

CSS150-4#�

Note: After the CSS 11xxx directs requests to a primary sorry server, the switch continues to use the primary sorry server, even�when the original server becomes functional. In order to force the connection back to the original server, you must suspend the primary sorry server or wait until the connection is dropped or times out. When the CSS 11xxx initiates a new session, the connection goes back to the original server.

Verify

Use this section to confirm that your configuration works properly.

  • show service summary—Displays summary information for all services. This information includes the service state, connections, weight, and load.

    This example provides sample output:

    CSS150-4#show service summary 
    
    Service Name������� State���� Conn����� Weight���    Avg Load���� State Transitions
    
    server1�������������Alive������  0���������1��������  2�����������  2 
       sorry������������Alive������� 0���������1��������  2�����������  0 
    
    CSS150-4# 
  • show keepalive-summary—Displays summary information for all keepalives. This information includes the name, status, and IP address.

    This example provides sample output:

    CSS150-4#show keepalive-summary 
       Keepalives: 
       AUTO_nexthop00005���������������    State: Alive��������172.17.63.193    
       AUTO_server1������������������������State: Alive��������10.10.10.11    
       AUTO_sorry��������������������������State: Alive�����  �10.10.10.12 
  • show flows—Displays the flow summary for a source IP address or for a specific source address and its destination IP address on a Switch Fabric Processor (SFP).

  • show running-config—Displays the running configuration.

Troubleshoot

There is currently no specific troubleshooting information available for this configuration.

Related Information

Updated: Jan 31, 2006
Document ID: 12597