View the passive health check settings for all health check profiles configured on the system. Passive probes are out-of-band health checks that skip regularly scheduled health check probes if in-line probes continue to report good server health. Using passive health checks will optimize system performance and reduce the load on the servers.
By default, passive server health checks are OFF. To enable this feature, set the SuccessiveCount argument to a number greater than 0. All real servers in the service group must be UP and reporting good health for the passive health checking feature to operate.
exec
show vSwitch-name loadBalance healthCheckProfile passive
| Heading | Description | Filter |
|---|---|---|
| Name | A text string identifying the health check profile. You cannot specify the text string none as the name. | name text |
| Successive Count | The maximum number of successive passive probes allowed, before forcing at least one normal probe. Once the number is reached, at least one normal poll will be performed. The value of 0 is used to disable this feature. Valid values are from 0 to 100. |
successiveCount integer |
| Activity Threshold | The maximum time, in seconds, when an RS's activity reflects good status. If this time has been exceeded, then the previous inline activity is no longer used for doing passive probes, and normal probes will be used. Valid values are from 6 to 3600. |
activityThreshold integer |
| Update Tolerance | The length of time, in seconds, that an update (between the DB Process and the Probe Process) is considered valid. Once this time has expired a new update sample (from the DB proc) is required before passive probes are used again. Valid values are from 5 to 60. |
updateTolerance integer |
| Min Poll Cycles | The smallest number of normal probes required before passive probes are used. Valid values are from 2 to 1000. |
minPollCycles integer |
| Inter Process Timeout | The amount of time, in milliseconds to wait for a SHC DB response for an activity update for a service group. Valid values are from 10 to 2000. |
interProcessTimeout integer |
You can do the following