Specifications

E-6
Cisco Internet Streamer CDS 2.0-2.3 Software Configuration Guide
OL-13493-04
Appendix E CLI Commands
Configuring Last-Resort Routing
Device Mode = se
Current CDSM address = 4.0.5.5
Registered with CDSM = 4.0.5.5
Status = Online
Time of last config-sync = Thu May 3 16:56:54 2007
CMS services information :
Service cms_se is running
In the Devices Table page on the CDSM (Devices > Devices), the SE or SR status should be “Online.”
The IP address for the device always shows the IP address of the primary interface.
Configuring Last-Resort Routing
Last-resort routing is applicable when load-based routing is enabled and all Service Engines have
exceeded their thresholds or all Service Engines in the domain are offline. The Service Router can
redirect requests to a configurable alternate domain when all Service Engines serving a client network
region are overloaded.
Note If the last-resort domain is not configured and the Service Engine thresholds are exceeded, requests are
redirected to the origin server.
To configure last-resort routing use the service-router global configuration command, where domain is
the service routing domain name, and alternate is where to route requests.
service-router lastresort domain domain alternate alternate
In the example below, srfqdn.cisco.com is the service routing domain name, and www.cisco.com is the
alternate domain name.
SR(config)# service-router ?
lastresort Configure lastresort domain
leastloaded Enable Load Based Routing
location-based-routing Configure location based routing
SR(config)# service-router lastresort ?
domain Configure domain
SR(config)# service-router lastresort domain srfqdn.cisco.com ?
alternate Configure alternate domain
SR(config)# service-router lastresort domain srfqdn.cisco.com alternate ?
WORD Configure alternate domain name
SR(config)# service-router lastresort domain srfqdn.cisco.com alternate www.cisco.com ?
<cr>
SE(config)# service-router lastresort domain srfqdn.cisco.com alternate www.cisco.com
Configuring Standby Interfaces
You can configure one ore more interfaces to act as a backup interface (a standby interface) for another
interface on a Service Engine. This feature is called standby interface support. Standby groups, which
are logical groups of interfaces, are used to implement this feature. When an active network interface
fails (because of cable trouble, Layer 2 switch failure, high error count, or other failures) and that
interface is part of a standby group, a standby interface can become active and take the load off the failed
interface.