This document provides information on Content Services Switch (CSS)
There are no specific prerequisites for this document.
The information in this document is based on these software and
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.
Technical Tips Conventions for information on document
GET is issued to the backend service, and a checksum on the page is
computed and stored by the switch as a reference point. Subsequent GETs require
a 200 OK status, and they require that the checksum equal the reference
checksum. If a non-200 status is returned (after the 15 second timer period) or
if a 200 status is returned, but the checksum is different, the service is
considered down. If the page that is accessed for the keepalive changes,
suspend and activate the service for a new checksum to be calculated.
Refer to the HTTP Keepalive with GET
section for more information.
HEAD is issued and a 200 OK status is required. No checksum is computed
for this type of keepalive.
This output provides a GET example:
ip address 10.10.4.221
keepalive type http
keepalive method get
keepalive uri "/index.html"
Issue the show keepalive-summary command in
order to show all keepalives. Issue the show keepalive
[service] command in order to see full keepalive details.