cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
344
Views
5
Helpful
1
Replies

Creating a New Content Rule

cantorb
Level 1
Level 1

I need some help creating a content rule for a service that we offer to our end users. We have a video server that people can hit via the web. Currently it sits on one server in a DMZ and is not going through a CSS. We have just built a new environment and as a prereq for future expansion we want to put the video server behind a CSS. Even though there is currently only one server it will make the addition of another and load balancing easier.

I believe that our video service uses ports 80 and 554. I have created the following services to check this:

Name: video_rtsp Index: 13

Type: Local State: Alive

Rule ( 10.0.1.19 ANY ANY )

Session Redundancy: Disabled

Redirect Domain:

Redirect String: (null)

Keepalive: (ICMP 60 3 60 )

Last Clearing of Stats Counters: 01/09/2005 15:47:20

Mtu: 1500 State Transitions: 14

Total Local Connections: 0 Total Backup Connections: 0

Current Local Connections: 0 Current Backup Connections: 0

Total Connections: 0 Max Connections: 65534

Total Reused Conns: 0

Weight: 1 Load: 2

DFP: Disable

Name: video_www Index: 14

Type: Local State: Alive

Rule ( 10.0.1.19 ANY ANY )

Session Redundancy: Disabled

Redirect Domain:

Redirect String: (null)

Keepalive: (ICMP 60 3 60 )

Last Clearing of Stats Counters: 01/09/2005 15:47:20

Mtu: 1500 State Transitions: 12

Total Local Connections: 0 Total Backup Connections: 0

Current Local Connections: 0 Current Backup Connections: 0

Total Connections: 0 Max Connections: 65534

Total Reused Conns: 0

Weight: 1 Load: 2

DFP: Disable

They are alive as you can see.

If the service is unavailable I would like to redirect to a sorry server. My question is this...what would my content rule(s) have to look like in order to accomplish this! Thanks for the help guys.

bc

1 Reply 1

Gilles Dufour
Cisco Employee
Cisco Employee

create a new service for your sorry server.

Then under the content rule defined for http traffic, you add the following line:

primarySorryServer

Regarding the config you provided, what you show is a 'show service ' and we can clearly see that even if your 2 services have different name, they are identical.

I believe you would want to configure different keepalive.

ie: for HTTP

keepalive port 80

keepalive type http

keepalive uri "/"

for rtsp

keepalive port 554

keepaliave type tcp

Regards,

Gilles.

Review Cisco Networking for a $25 gift card