Check Health of DRTR Service

Symptoms:

– Cannot establish connection to service drtr_service
– BlueCoat Device was not able to contact the BlueCoat categorization service.

Problem:

There are numerous geographically dispersed (external) sources for DRTR (Dynamic Categorization) updates.  The threshold for a “sick” status is currently set to 1.  This means that if a connection to *any* of the DRTR sources fails for more than ten seconds, we will get an incident.  **We need to check health before reporting these to the customer**

To check the health status of DRTR (Dynamic Real Time Rating service)

Solution:

Log into the device:

To check from the GUI: Management Console–> Health Checks–>”Perform Health Check”

To check from the CLI enter the following command: show health-checks statistics

Example output:

RAZBC01>show health-checks statistics
Health Check Statistics

External Services

drtr.rating_service    Domain name: sp.cwfservice.net         DNS status: success
Enabled   Functioning properly    UP
IP address: 8.21.4.203            Enabled         Functioning properly    UP
Last status: Success.
Successes (total): 793          (last): Tue, 27 Oct 2009 21:01:29 GMT   (consecutive): 461
Failures  (total): 3133         (last): Tue, 01 Sep 2009 23:57:58 GMT   (consecutive): 0        (external): 0
Last response time: 429 ms      Average response time: 445 ms
Minimum response time: 426 ms   Maximum response time: 3434 ms
IP address: 208.115.138.201               Enabled         Functioning properly    UP
Last status: Success.
Successes (total): 1372         (last): Tue, 27 Oct 2009 21:01:06 GMT   (consecutive): 277
Failures  (total): 5184         (last): Thu, 24 Sep 2009 20:59:17 GMT   (consecutive): 0        (external): 0
Last response time: 303 ms      Average response time: 368 ms
Minimum response time: 301 ms   Maximum response time: 6548 ms
IP address: 8.21.4.201            Enabled         Functioning properly    UP
Last status: Success.
Successes (total): 793          (last): Tue, 27 Oct 2009 21:01:29 GMT   (consecutive): 461
Failures  (total): 3125         (last): Tue, 01 Sep 2009 23:57:56 GMT   (consecutive): 0        (external): 0
Last response time: 429 ms      Average response time: 446 ms
Minimum response time: 426 ms   Maximum response time: 3419 ms
IP address: 119.27.62.201                 Enabled         Functioning properly    UP
Last status: Success.
Successes (total): 1276         (last): Tue, 27 Oct 2009 21:04:13 GMT   (consecutive): 461
Failures  (total): 5072         (last): Tue, 01 Sep 2009 23:57:57 GMT   (consecutive): 0        (external): 0
Last response time: 789 ms      Average response time: 812 ms
Minimum response time: 752 ms   Maximum response time: 10168 ms
IP address: 208.115.138.203               Enabled         Functioning properly    UP
Last status: Success.
Successes (total): 1275         (last): Tue, 27 Oct 2009 21:00:57 GMT   (consecutive): 277
Failures  (total): 5521         (last): Thu, 24 Sep 2009 20:59:22 GMT   (consecutive): 0        (external): 0
Last response time: 307 ms      Average response time: 317 ms
Minimum response time: 302 ms   Maximum response time: 797 ms
IP address: 85.92.222.203                 Enabled         Functioning properly    UP
Last status: Success.
Successes (total): 1451         (last): Tue, 27 Oct 2009 20:11:33 GMT   (consecutive): 100
Failures  (total): 6912         (last): Fri, 16 Oct 2009 05:11:08 GMT   (consecutive): 0        (external): 0
Last response time: 152 ms      Average response time: 221 ms
Minimum response time: 150 ms   Maximum response time: 6326 ms
IP address: 85.92.222.201                 Enabled         Functioning properly    UP
Last status: Success.
Successes (total): 1450         (last): Tue, 27 Oct 2009 21:48:48 GMT   (consecutive): 12
Failures  (total): 6857         (last): Mon, 26 Oct 2009 12:48:36 GMT   (consecutive): 0        (external): 0
Last response time: 151 ms      Average response time: 182 ms
Minimum response time: 151 ms   Maximum response time: 515 ms

 

Was this article helpful?

Related Articles

Leave A Comment?

You must be logged in to post a comment.