The reason I'm thinking about this is primarily that it would be useful for setting up an appropriate keep-alive frequency. However, in production the response time could also be monitored as an early warning sign of performance degradation (and alerted by your usual network management system).
Use the dns-boomerang client domain command to create a domain record in the Content Routing Agent DNS server for each of the domains you associated the agent with when you configured domains on the Content Router. If the matching domain record keepalive messaging succeeds, the CSS uses this record for DNS resolutions. There is no Content Routing Agent configuration mode
Anyone else reading this conversation might be interested to know that F5 Big-IP load balancers have the facility to set the maximum response time that a keep-alive ("performance monitor" in Big-IP terminology) is allowed to take and this is independent of interval between the keep-alives. E.g. you can say the keep-alive must respond within 5 seconds but only run it every 30 seconds.
In comparison on the CSS (v7.20 on) the timeout is the frequency minus 2 seconds, e.g. for a default 5 second frequency the timeout is 3 seconds.
Just an idea of what *might* be possible in future CSS versions...
I still think it would be useful to have the last keep-alive response time exposed via SNMP - I doubt it would add any/much additional load to the CSS and the more information you have the better IMHO.
Hopefully someone in Cisco CSS development might be reading this...
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...