CSS 11506 Default "Site is down" Page

Unanswered Question
Jan 23rd, 2008

The Company that I work for needs to bring down our servers for some hardware upgrades for a period of time. Is it possible to configure the CSS so that it will display an HTML page any time that it cannot find one of the servers that it should be looking for? If it is possible, how would I go about doing that,or where would I look for directions on setting that up? Thank you very much for any help provided.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Diego Vargas Wed, 01/23/2008 - 11:09

Hi Joe,

There is no way to have the CSS responding with a page saying that the servers are out for maintenance, but you can configure a sorry server and have the CSS send the requests to a server that will answer with the sorry page that you need.

So all the servers on a given content rule are out for maintenance the sorry server will get the traffic and answer the sorry page.

This is the sorry server configuration:


Hope it helps!!

joecunningham Wed, 01/23/2008 - 13:56

Thanks again. I have a quick question about setting up the Sorry server. I saw the information in the document that you gave me in regards to verifying the configuration, but I am being asked if there is anyway to test the sorry server without bringing down the active servers, I am guessing that their is not, but I thought I would ask. Thank you.

Diego Vargas Wed, 01/23/2008 - 14:09

Well, there is no way for the CSS to send traffic to the sorry server if all other services are up on that content rule but if you would like to make sure that traffic balanced to the sorry server would work you can create a dummy content rule with a dummy VIP a add that service as a normal service instead of sorry server.

Hope it helps!!

joecunningham Sun, 01/27/2008 - 10:21

Another question, we've brought down our content servers and the sorry server is sending out the sorry page that we have set up. I added all the settings indicated in the link about you gave me, and based on some of the other articles that I have seen while troubleshooting I have changed some of the persistence settings. Here are my configurations, any ideas?

!*************************** GLOBAL ***************************

no restrict web-mgmt

no restrict xml

dns primary

ip route 1

!************************* INTERFACE *************************

interface 1/1

phy 1Gbits-FD-sym

!************************** CIRCUIT **************************

circuit VLAN1

router-discovery lifetime 1000

ip address


!************************** SERVICE **************************

service Blade01

ip address


service Blade02

ip address


service Blade03

ip address


service Blade04

ip address


service sorry

ip address


!*************************** OWNER ***************************

owner OWNER


content server1

vip address

balance aca

add service Blade01

add service Blade02

primarySorryServer sorry

no persistent


content server2

vip address

add service Blade03

add service Blade04

balance aca


!*************************** GROUP ***************************

group server1

vip address

add destination service Blade01

add destination service Blade02

add destination service sorry

group server2

add destination service Blade03

add destination service Blade04

vip address

joecunningham Mon, 01/28/2008 - 10:15

I'm sorry, in my haste I made a typo. My previous message should have said that the Sorry server is NOT sending out the page that we set up. Thank you for responding despite my confusing error.

Diego Vargas Mon, 01/28/2008 - 10:29

Are other services working with the group "server1" not active? Can you activate the group and retest?

If you go directly to the server, do you get the page?

The CSS is checking only for layer 3 connectivity with the servers, are you sure the server is responding at application level?

joecunningham Mon, 01/28/2008 - 10:59

The other services in the "server1" group are working, we brought things back online after the upgrade and they worked as normal. We had to bring the servers down again this morning for something else and the Sorry server is still not sending the page.

I do get the page if I go directly to the server.

I've double check, and yes, the server is responding at the application level.

joecunningham Mon, 01/28/2008 - 15:09

Looking at your questions again, I'm not sure that I looked at the correct thing in regards to the third question. Do we want to have the server responding on the application level? If so is that a change that I need the person in charge of the web server to make? Thanks again.

luqmankondeth Tue, 04/15/2008 - 02:05

Hi Joe,

Did you get your sorry page to work? I noticed that the documentation at



"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".

We have a similar situation here and I would like to know if you can configure a backup server when u define more than one services in a content rule.


My situation is slightly different.

We are defining a threshold load for the servers which will indicate when the sorry server is to be used.

We want new requests to goto a sorry page and existing active connections to keep going to the web servers. Im planning to do this by using either

1)checking load on servers


2) Using DFP


In both cases, I suppose I would need to use Arrowpoint cookie awareness. I would then add the primarysorry page into the content rule.

Is my approach correct? Am I missing something ?



This Discussion