Solaris Cluster 3.x or 4.x How to Establish Permanent guds Performance Monitoring to cover Probe Timeouts from SUNWsczone or other Agent / Data Service
(Doc ID 1914195.1)
Last updated on SEPTEMBER 04, 2024
Applies to:
Solaris Cluster - Version 3.2 to 4.4 [Release 3.2 to 4.4]Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)
Goal
The Solaris Cluster HA data service for Solaris zones (package SUNWsczone) sometimes gets into probe timeouts causing an unwanted restart of the zone. In many of these cases no exact root cause can be provided due to missing diagnostic data covering the probe timeout. These service request mostly end up in a prophylactic raise of the probe timeout as addressed in:
RFE 15756457: SUNBT7114158 Increase the default timeout of the probe for Container Agent.
This document describes how to set up 24x7 guds-monitoring to trap probe timeouts from the HA container agent with suitable diagnostic data, without piling up huge amounts of performance data.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |